View source for Lab: Configure IPv6 Routing between NSX Segments and external networks

<div class="page-body">

{| class="wikitable simple-table"
|-
!  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
| [https://github.com/luischanu/TinyVM/tree/v2.7/images 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
|}

# Configure IPv6 OSPFv3 routing between the Pod-110 and Pod-120 Routers and the WAN Gateway.

<ol start="2" style="list-style-type: decimal;">
<li>Create a Tier-0 Gateway on Pod-110 and Pod-120 and configure IPv6 BGP between the Tier-0 Gateways and the Pod Routers.</li></ol>

<ol start="3" style="list-style-type: decimal;">
<li>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.</li></ol>

<ol start="4" style="list-style-type: decimal;">
<li>Deploy VMs on all the segments.</li></ol>

<ol start="5" style="list-style-type: decimal;">
<li>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.</li></ol>

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.

<div id="3600f581-b075-47f1-8b5f-9956196dc445" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled.png

</div>
<div id="7b171ff1-fd0b-44cc-9798-b9bdbdcbdee9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%201.png

</div>
<span id="febcf85f-7bf7-41e7-8a80-f5da0421c06a"></span>
= The Steps =
*<span class="far fa-regular fa-square"> STEP 1: Configure IPv6 Routing using OSPFv3 on the WAN Gateway</span>
*<span class="far fa-regular fa-square"> STEP 2: Configure IPv6 Routing using OSPFv3 between the WAN Gateway and the Pod Gateway</span>
*<span class="far fa-regular fa-square"> STEP 3: Prepare Pod Gateways for IPv6 BGP</span>
*<span class="far fa-regular fa-square"> STEP 4: Add IPv6 BGP Uplink Segments in NSX</span>
*<span class="far fa-regular fa-square"> STEP 5: Create a Tier-0 Gateway</span>
*<span class="far fa-regular fa-square"> STEP 6: Configure IPv6 BGP Routing between Tier-0 Gateway and the Pod Gateway</span>
*<span class="far fa-regular fa-square"> STEP 7: Create a Tier-1 Gateway</span>
*<span class="far fa-regular fa-square"> STEP 8: Add IPv6 Web, App and DB Segments in NSX</span>
*<span class="far fa-regular fa-square"> STEP 9: Configure Route Advertise connected Tier-1 Gateway segment networks to BGP</span>
*<span class="far fa-regular fa-square"> STEP 10: Configure route redistribution between BGP and OSPFv3</span>
*<span class="far fa-regular fa-square"> STEP 11: Create Test Virtual Machines and perform ping connectivity tests</span>
<div class="indented">


<span id="75a7451f-11b6-479b-81ce-99c297de359b"></span>
= STEP 1{{fqm}} 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.

<div id="ee94ee56-3adc-477a-9689-de633ad9ee64" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%202.png

</div>
The configuration parameters that I will used are listed in the table below.

{| class="wikitable simple-table"
|-
!  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.

<div class="collapsible">
    <div class="collapsible-alone-header">WAN Gateway OSPFv3 configuration</div>
   <div class="collapsible-content">
<pre class="code">configure
#
set system domain-name sddc.lab
set system host-name WAN-Gateway
set system name-server 10.203.0.5
#
set service ssh port 22
set service ssh protocol-version v2
#
set interfaces ethernet eth1 description 'eth1 - LAN'
set interfaces ethernet eth1 duplex auto
set interfaces ethernet eth1 mtu 9000
set interfaces ethernet eth1 speed auto
#
set interfaces ethernet eth1 vif 203 description 'Router Uplink'
set interfaces ethernet eth1 vif 203 address 10.203.0.1/24
set interfaces ethernet eth1 vif 203 address 'fd00::1/64'
set interfaces ethernet eth1 vif 203 ip ospf dead-interval 40
set interfaces ethernet eth1 vif 203 ip ospf hello-interval 10
set interfaces ethernet eth1 vif 203 ip ospf priority 1
set interfaces ethernet eth1 vif 203 ip ospf retransmit-interval 5
set interfaces ethernet eth1 vif 203 ip ospf transmit-delay 1
set interfaces ethernet eth1 vif 203 mtu 1500
#
set interfaces ethernet eth1 vif 203 ipv6 dup-addr-detect-transmits 1
set interfaces ethernet eth1 vif 203 ipv6 router-advert cur-hop-limit 64
set interfaces ethernet eth1 vif 203 ipv6 router-advert link-mtu 0
set interfaces ethernet eth1 vif 203 ipv6 router-advert managed-flag false
set interfaces ethernet eth1 vif 203 ipv6 router-advert max-interval 600
set interfaces ethernet eth1 vif 203 ipv6 router-advert other-config-flag false
set interfaces ethernet eth1 vif 203 ipv6 router-advert prefix 'fd00::/64' autonomous-flag true
set interfaces ethernet eth1 vif 203 ipv6 router-advert prefix 'fd00::/64' on-link-flag true
set interfaces ethernet eth1 vif 203 ipv6 router-advert prefix 'fd00::/64' valid-lifetime 2592000
set interfaces ethernet eth1 vif 203 ipv6 router-advert reachable-time 0
set interfaces ethernet eth1 vif 203 ipv6 router-advert retrans-timer 0
set interfaces ethernet eth1 vif 203 ipv6 router-advert send-advert true
#
set protocols ospf area 0 area-type normal
set protocols ospf area 0 network 10.203.0.0/24
set protocols ospf parameters abr-type cisco
set protocols ospf parameters router-id 10.203.0.1
set protocols ospf redistribute connected metric-type 2
#
set protocols ospfv3 area 0.0.0.0 area-type normal
set protocols ospfv3 area 0.0.0.0 interface eth1.203
set protocols ospfv3 area 0.0.0.0 range 'fd00::/64'
set protocols ospfv3 parameters abr-type cisco
set protocols ospfv3 parameters router-id 10.203.0.1
set protocols ospfv3 redistribute connected
#
commit
save</pre></div></div>

<span id="38d5e2ad-922b-41cd-a3e6-70f16ca51327"></span>
== OSPF Verification ==

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

<pre class="code">admin@WAN-Gateway:~$ show ip ospf neighbor
admin@WAN-Gateway:~$</pre>
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.

<span id="324e86dd-8c93-4b44-b49f-cd76e1325c66"></span>
= STEP 2{{fqm}} 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.

<div id="17b3fa2a-d97b-4073-9c94-f4d33a4b7830" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%203.png

</div>
<span id="7d3d31b1-e458-4b3b-a8be-2c963ccb26fc"></span>
== Pod 110 ==

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

{| class="wikitable simple-table"
|-
!  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.

{| class="wikitable simple-table"
|-
! |
! 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.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-Router OSPFv3 configuration</div>
   <div class="collapsible-content">
<pre class="code">configure
#
set system domain-name sddc.lab
set system host-name 'Pod-110-Router'
set system name-server '10.203.0.5'
set system name-server 'fd00:0000:0000:0000::0005'
#
set service ssh port 22
set service ssh protocol-version v2
#
set interfaces ethernet eth0 address '10.203.0.110/24'
set interfaces ethernet eth0 address 'fd00:0000:0000:0000::006e/64'
set interfaces ethernet eth0 description 'Router Uplink'
set interfaces ethernet eth0 mtu '1500'
#
set interfaces ethernet eth1 mtu '9000'
set interfaces ethernet eth1 vif 110 address '10.203.110.1/24'
set interfaces ethernet eth1 vif 110 address 'fd00:0000:0000:006e::0001/64'
set interfaces ethernet eth1 vif 110 description 'Management'
set interfaces ethernet eth1 vif 110 mtu '1500'
#
set interfaces ethernet eth1 vif 116 address '10.203.116.1/24'
set interfaces ethernet eth1 vif 116 address 'fd00:0000:0000:0074::0001/64'
set interfaces ethernet eth1 vif 116 description 'NSX Edge Uplink #1'
set interfaces ethernet eth1 vif 116 mtu '1500'
set interfaces ethernet eth1 vif 117 address '10.203.117.1/24'
set interfaces ethernet eth1 vif 117 address 'fd00:0000:0000:0075::0001/64'
set interfaces ethernet eth1 vif 117 description 'NSX Edge Uplink #2'
set interfaces ethernet eth1 vif 117 mtu '1500'
#
set protocols ospf area 0 network '10.203.0.0/24'
set protocols ospf area 110 area-type normal
set protocols ospf area 110 network '10.203.116.0/24'
set protocols ospf area 110 network '10.203.117.0/24'
set protocols ospf log-adjacency-changes
set protocols ospf parameters router-id '10.203.0.110'
set protocols ospf redistribute connected metric-type '2'
set protocols ospfv3 interface eth0 area '0.0.0.0'
set protocols ospfv3 parameters router-id '10.203.0.110'
set protocols ospfv3 redistribute connected
#
set protocols static route 0.0.0.0/0 next-hop 10.203.0.1 distance '250'
#
set service router-advert interface eth0 prefix fd00::/64
set service router-advert interface eth1.110 prefix fd00:0:0:6e::/64
set service router-advert interface eth1.116 prefix fd00:0:0:74::/64
set service router-advert interface eth1.117 prefix fd00:0:0:75::/64
#
set system ntp listen-address '10.203.110.1'
set system ntp server 10.203.0.5
set system ntp server fd00:0000:0000:0000::0005
#
commit
save</pre></div></div>

<span id="d56ce537-4fb3-4700-8b68-0d143069eb48"></span>
== Pod 120 ==

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

{| class="wikitable simple-table"
|-
!  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.

{| class="wikitable simple-table"
|-
! 
!  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.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-Router OSPFv3 configuration</div>
   <div class="collapsible-content">
<pre class="code">configure
#
set system domain-name sddc.lab
set system host-name 'Pod-120-Router'
set system name-server '10.203.0.5'
set system name-server 'fd00:0000:0000:0000::0005'
#
set service ssh port 22
set service ssh protocol-version v2
#
set interfaces ethernet eth0 address '10.203.0.120/24'
set interfaces ethernet eth0 address 'fd00:0000:0000:0000::0078/64'
set interfaces ethernet eth0 description 'Router Uplink'
set interfaces ethernet eth0 mtu '1500'
#
set interfaces ethernet eth1 mtu '9000'
set interfaces ethernet eth1 vif 120 address '10.203.120.1/24'
set interfaces ethernet eth1 vif 120 address 'fd00:0000:0000:0078::0001/64'
set interfaces ethernet eth1 vif 120 description 'Management'
set interfaces ethernet eth1 vif 120 mtu '1500'
#
set interfaces ethernet eth1 vif 126 address '10.203.126.1/24'
set interfaces ethernet eth1 vif 126 address 'fd00:0000:0000:007e::0001/64'
set interfaces ethernet eth1 vif 126 description 'NSX Edge Uplink #1'
set interfaces ethernet eth1 vif 126 mtu '1500'
#
set interfaces ethernet eth1 vif 127 address '10.203.127.1/24'
set interfaces ethernet eth1 vif 127 address 'fd00:0000:0000:007f::0001/64'
set interfaces ethernet eth1 vif 127 description 'NSX Edge Uplink #2'
set interfaces ethernet eth1 vif 127 mtu '1500'
#
set protocols ospf area 0 network '10.203.0.0/24'
set protocols ospf area 120 area-type normal
set protocols ospf area 120 network '10.203.126.0/24'
set protocols ospf area 120 network '10.203.127.0/24'
set protocols ospf log-adjacency-changes
set protocols ospf parameters router-id '10.203.0.120'
set protocols ospf redistribute connected metric-type '2'
set protocols ospfv3 interface eth0 area '0.0.0.0'
set protocols ospfv3 parameters router-id '10.203.0.120'
set protocols ospfv3 redistribute connected
#
set protocols static route 0.0.0.0/0 next-hop 10.203.0.1 distance '250'
#
set service router-advert interface eth0 prefix fd00::/64
set service router-advert interface eth1.120 prefix fd00:0:0:78::/64
set service router-advert interface eth1.126 prefix fd00:0:0:7e::/64
set service router-advert interface eth1.127 prefix fd00:0:0:7f::/64
#
set system ntp listen-address '10.203.120.1'
set system ntp server 10.203.0.5
set system ntp server fd00:0000:0000:0000::0005
#
commit
save</pre></div></div>

<span id="0f3920be-3e48-4933-9947-0c00b006cb74"></span>
== 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.

<pre class="code">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:~$</pre>
On the Pod-110 Router I also have two neighbors.

<pre class="code">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:~$</pre>
On the Pod-120 Router I also have two neighbors.

<pre class="code">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:~$</pre>
<span id="afcbed2a-c692-4bce-8876-3e3f6d543827"></span>
= STEP 3{{fqm}} 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.

<span id="2d7bcb04-8fe2-4e4a-a66f-75b37c726080"></span>
== Pod 110 ==

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

<div id="0e24c47b-aa26-410f-9a51-b706c8fe4b19" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%204.png

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

{| class="wikitable simple-table"
|-
!  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.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-Router IPv6 BGP configuration</div>
   <div class="collapsible-content">
<pre class="code">set protocols bgp local-as '65110'
set protocols bgp neighbor 10.203.0.1 address-family ipv4-unicast
set protocols bgp neighbor 10.203.0.1 description 'Lab-Router'
set protocols bgp neighbor 10.203.0.1 remote-as '65000'
set protocols bgp neighbor 10.203.116.2 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.116.2 description 'Pod-110-T0-EdgeVM-01-1'
set protocols bgp neighbor 10.203.116.2 remote-as '65111'
set protocols bgp neighbor 10.203.116.3 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.116.3 description 'Pod-110-T0-EdgeVM-02-1'
set protocols bgp neighbor 10.203.116.3 remote-as '65111'
set protocols bgp neighbor 10.203.117.2 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.117.2 description 'Pod-110-T0-EdgeVM-01-2'
set protocols bgp neighbor 10.203.117.2 remote-as '65111'
set protocols bgp neighbor 10.203.117.3 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.117.3 description 'Pod-110-T0-EdgeVM-02-2'
set protocols bgp neighbor 10.203.117.3 remote-as '65111'
set protocols bgp neighbor fd00:0000:0000:0000::0001 address-family ipv6-unicast
set protocols bgp neighbor fd00:0000:0000:0000::0001 description 'Lab-Router'
set protocols bgp neighbor fd00:0000:0000:0000::0001 remote-as '65000'
set protocols bgp neighbor fd00:0000:0000:0074::0002 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:0074::0002 description 'Pod-110-T0-EdgeVM-01-1'
set protocols bgp neighbor fd00:0000:0000:0074::0002 remote-as '65111'
set protocols bgp neighbor fd00:0000:0000:0074::0003 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:0074::0003 description 'Pod-110-T0-EdgeVM-02-1'
set protocols bgp neighbor fd00:0000:0000:0074::0003 remote-as '65111'
set protocols bgp neighbor fd00:0000:0000:0075::0002 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:0075::0002 description 'Pod-110-T0-EdgeVM-01-2'
set protocols bgp neighbor fd00:0000:0000:0075::0002 remote-as '65111'
set protocols bgp neighbor fd00:0000:0000:0075::0003 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:0075::0003 description 'Pod-110-T0-EdgeVM-02-2'
set protocols bgp neighbor fd00:0000:0000:0075::0003 remote-as '65111'
set protocols bgp parameters router-id '10.203.110.1'
#</pre></div></div>

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

{| class="wikitable simple-table"
|-
! 
!  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.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-Router IPv6 SDDC VLAN/interface configuration</div>
   <div class="collapsible-content">
<pre class="code">set interfaces ethernet eth1 vif 111 address '10.203.111.1/24'
set interfaces ethernet eth1 vif 111 address 'fd00:0000:0000:006f::0001/64'
set interfaces ethernet eth1 vif 111 description 'vMotion'
set interfaces ethernet eth1 vif 111 mtu '9000'
set interfaces ethernet eth1 vif 112 address '10.203.112.1/24'
set interfaces ethernet eth1 vif 112 address 'fd00:0000:0000:0070::0001/64'
set interfaces ethernet eth1 vif 112 description 'vSAN'
set interfaces ethernet eth1 vif 112 mtu '9000'
set interfaces ethernet eth1 vif 113 address '10.203.113.1/24'
set interfaces ethernet eth1 vif 113 address 'fd00:0000:0000:0071::0001/64'
set interfaces ethernet eth1 vif 113 description 'IP Storage'
set interfaces ethernet eth1 vif 113 mtu '9000'
set interfaces ethernet eth1 vif 114 address '10.203.114.1/24'
set interfaces ethernet eth1 vif 114 address 'fd00:0000:0000:0072::0001/64'
set interfaces ethernet eth1 vif 114 description 'Overlay Transport'
set interfaces ethernet eth1 vif 114 mtu '9000'
set interfaces ethernet eth1 vif 115 address '10.203.115.1/24'
set interfaces ethernet eth1 vif 115 address 'fd00:0000:0000:0073::0001/64'
set interfaces ethernet eth1 vif 115 description 'Service VM Management'
set interfaces ethernet eth1 vif 115 mtu '1500'
set interfaces ethernet eth1 vif 118 address '10.203.118.1/24'
set interfaces ethernet eth1 vif 118 address 'fd00:0000:0000:0076::0001/64'
set interfaces ethernet eth1 vif 118 description 'RTEP Transport'
set interfaces ethernet eth1 vif 118 mtu '1500'
set interfaces loopback lo
#
set service router-advert interface eth1.111 prefix fd00:0:0:6f::/64
set service router-advert interface eth1.112 prefix fd00:0:0:70::/64
set service router-advert interface eth1.113 prefix fd00:0:0:71::/64
set service router-advert interface eth1.114 prefix fd00:0:0:72::/64
set service router-advert interface eth1.115 prefix fd00:0:0:73::/64
set service router-advert interface eth1.118 prefix fd00:0:0:76::/64
#</pre></div></div>

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.

<span id="edfb73ad-b6bb-42d1-80b4-370ed882323e"></span>
== Pod 120 ==

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

<div id="d4caf5fb-2e15-4128-a44e-19fa4207ca5f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%205.png

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

{| class="wikitable simple-table"
|-
!  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.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-Router IPv6 BGP configuration</div>
   <div class="collapsible-content">
<pre class="code">set protocols bgp local-as '65120'
set protocols bgp neighbor 10.203.0.1 address-family ipv4-unicast
set protocols bgp neighbor 10.203.0.1 description 'Lab-Router'
set protocols bgp neighbor 10.203.0.1 remote-as '65000'
set protocols bgp neighbor 10.203.126.2 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.126.2 description 'Pod-120-T0-EdgeVM-01-1'
set protocols bgp neighbor 10.203.126.2 remote-as '65121'
set protocols bgp neighbor 10.203.126.3 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.126.3 description 'Pod-120-T0-EdgeVM-02-1'
set protocols bgp neighbor 10.203.126.3 remote-as '65121'
set protocols bgp neighbor 10.203.127.2 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.127.2 description 'Pod-120-T0-EdgeVM-01-2'
set protocols bgp neighbor 10.203.127.2 remote-as '65121'
set protocols bgp neighbor 10.203.127.3 address-family ipv4-unicast default-originate
set protocols bgp neighbor 10.203.127.3 description 'Pod-120-T0-EdgeVM-02-2'
set protocols bgp neighbor 10.203.127.3 remote-as '65121'
set protocols bgp neighbor fd00:0000:0000:0000::0001 address-family ipv6-unicast
set protocols bgp neighbor fd00:0000:0000:0000::0001 description 'Lab-Router'
set protocols bgp neighbor fd00:0000:0000:0000::0001 remote-as '65000'
set protocols bgp neighbor fd00:0000:0000:007e::0002 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:007e::0002 description 'Pod-120-T0-EdgeVM-01-1'
set protocols bgp neighbor fd00:0000:0000:007e::0002 remote-as '65121'
set protocols bgp neighbor fd00:0000:0000:007e::0003 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:007e::0003 description 'Pod-120-T0-EdgeVM-02-1'
set protocols bgp neighbor fd00:0000:0000:007e::0003 remote-as '65121'
set protocols bgp neighbor fd00:0000:0000:007f::0002 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:007f::0002 description 'Pod-120-T0-EdgeVM-01-2'
set protocols bgp neighbor fd00:0000:0000:007f::0002 remote-as '65121'
set protocols bgp neighbor fd00:0000:0000:007f::0003 address-family ipv6-unicast default-originate
set protocols bgp neighbor fd00:0000:0000:007f::0003 description 'Pod-120-T0-EdgeVM-02-2'
set protocols bgp neighbor fd00:0000:0000:007f::0003 remote-as '65121'
set protocols bgp parameters router-id '10.203.120.1'
#</pre></div></div>

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

{| class="wikitable simple-table"
|-
! 
!  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.

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-Router IPv6 SDDC VLAN/interface configuration</div>
   <div class="collapsible-content">
<pre class="code">set interfaces ethernet eth1 vif 121 address '10.203.121.1/24'
set interfaces ethernet eth1 vif 121 address 'fd00:0000:0000:0079::0001/64'
set interfaces ethernet eth1 vif 121 description 'vMotion'
set interfaces ethernet eth1 vif 121 mtu '9000'
set interfaces ethernet eth1 vif 122 address '10.203.122.1/24'
set interfaces ethernet eth1 vif 122 address 'fd00:0000:0000:007a::0001/64'
set interfaces ethernet eth1 vif 122 description 'vSAN'
set interfaces ethernet eth1 vif 122 mtu '9000'
set interfaces ethernet eth1 vif 123 address '10.203.123.1/24'
set interfaces ethernet eth1 vif 123 address 'fd00:0000:0000:007b::0001/64'
set interfaces ethernet eth1 vif 123 description 'IP Storage'
set interfaces ethernet eth1 vif 123 mtu '9000'
set interfaces ethernet eth1 vif 124 address '10.203.124.1/24'
set interfaces ethernet eth1 vif 124 address 'fd00:0000:0000:007c::0001/64'
set interfaces ethernet eth1 vif 124 description 'Overlay Transport'
set interfaces ethernet eth1 vif 124 mtu '9000'
set interfaces ethernet eth1 vif 125 address '10.203.125.1/24'
set interfaces ethernet eth1 vif 125 address 'fd00:0000:0000:007d::0001/64'
set interfaces ethernet eth1 vif 125 description 'Service VM Management'
set interfaces ethernet eth1 vif 125 mtu '1500'
set interfaces ethernet eth1 vif 128 address '10.203.128.1/24'
set interfaces ethernet eth1 vif 128 address 'fd00:0000:0000:0080::0001/64'
set interfaces ethernet eth1 vif 128 description 'RTEP Transport'
set interfaces ethernet eth1 vif 128 mtu '1500'
set interfaces loopback lo
#
set service router-advert interface eth1.121 prefix fd00:0:0:79::/64
set service router-advert interface eth1.122 prefix fd00:0:0:7a::/64
set service router-advert interface eth1.123 prefix fd00:0:0:7b::/64
set service router-advert interface eth1.124 prefix fd00:0:0:7c::/64
set service router-advert interface eth1.125 prefix fd00:0:0:7d::/64
set service router-advert interface eth1.128 prefix fd00:0:0:80::/64
#</pre></div></div>

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.

<span id="c221bcb8-745d-4b9d-86df-e3c2c67a7ef0"></span>
= STEP 4{{fqm}} 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.

<span id="df8c6d55-af4e-4dd2-8fce-6b6e8fcd98b6"></span>
== Pod 110 ==

<div id="9d54d704-8feb-4b05-a88f-9187a79b18f8" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%206.png

</div>
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.

<ul>
<li>VDS Port Groups
<div id="2085a066-c131-41d5-90b6-0ac5891802f9" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%207.png

</div>
<div id="c924cc56-0ae5-4e35-9fe8-87a363f39c99" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%208.png

</div></li></ul>

<ul>
<li>NSX Edge Uplink Profiles
<div id="c92a80cc-f386-4ab8-af66-a6c7fb6b7dca" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%209.png

</div></li></ul>

<ul>
<li>NSX Edge Transport Zone
<div id="2d79aea5-b552-4c6c-af85-00a0013e12b5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2010.png

</div></li></ul>

<ul>
<li>NSX Edge configuration
<div id="f857ba0f-d775-4094-b20f-33a4b19a577a" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2011.png

</div></li></ul>

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

{| class="wikitable simple-table"
|-
!  Segment Name
!  Transport Zone
!  Uplink Teaming Policy
!  VLAN
!  IPv6 Network
!  IPv4 network
|-
| SEG-T0-Edge-Uplink1_VLAN-116
| TZ-Edge | VLAN
| Tor-A
| 116
| fd00:0:0:74::/64
| 10.203.116.0/24
|-
| SEG-T0-Edge-Uplink2_VLAN-117
| TZ-Edge | 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.

<div id="620f6077-3285-4a27-bd8c-c0e9ac9ee13b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2012.png

</div>
<span id="ff182546-9ad0-4ec1-b76c-cb6195474f46"></span>
== Pod 120 ==

<div id="cc965f1e-05f0-489f-9655-75c230bf186c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2013.png

</div>
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.

<ul>
<li>VDS Port Groups
<div id="68db0e9c-24a2-48e7-bd50-9d395a83c2c8" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2014.png

</div>
<div id="5b93a992-ef14-43d9-9b80-198219f73409" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2015.png

</div></li></ul>

<ul>
<li>NSX Edge Uplink Profiles
<div id="14ad0798-3ed3-4fa7-9c72-bfc7739110cd" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2016.png

</div></li></ul>

<ul>
<li>NSX Edge Transport Zone
<div id="e630c2a5-30f5-4bad-b9a8-4000f10c8551" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2017.png

</div></li></ul>

<ul>
<li>NSX Edge configuration
<div id="b8db6b93-b94c-4519-8e7d-a083ebc85ac6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2018.png

</div></li></ul>

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

{| class="wikitable simple-table"
|-
!  Segment Name
!  Transport Zone
!  Uplink Teaming Policy
!  VLAN
!  IPv6 Network
!  IPv4 network
|-
| SEG-T0-Edge-Uplink1_VLAN-126
| TZ-Edge | VLAN
| Tor-A
| 126
| fd00:0:0:7e::/64
| 10.203.126.0/24
|-
| SEG-T0-Edge-Uplink2_VLAN-127
| TZ-Edge | 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.

<div id="df2f5efa-4cce-4c69-9fd1-84a189604792" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2019.png

</div>
<span id="a75a184f-2f51-4d42-8a66-809a6045cd8c"></span>
= STEP 5{{fqm}} Create a Tier&ndash;0 Gateway =

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

<span id="155f0694-007d-4348-881f-faa8d64d6671"></span>
== Pod 110 ==

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

{| class="wikitable simple-table"
|-
!  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.

<div id="b393e292-bdc0-4eb0-97e6-93b978921e0b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2020.png

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

{| class="wikitable simple-table"
|-
!  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.

<div id="e1bc34e9-df4e-4420-af25-71feefe2c43f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2021.png

</div>
This is the output of the EdgeVM-02 interfaces after I have created them.

<div id="808f3c07-669e-4989-8959-393248946ca0" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2022.png

</div>
<span id="8cb91656-27f5-42b5-be3b-5dbebd22dd9e"></span>
== Pod 120 ==

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

{| class="wikitable simple-table"
|-
!  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.

<div id="ed991fa0-bcec-41a4-904d-110b1fb93025" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2023.png

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

{| class="wikitable simple-table"
|-
!  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.

<div id="1b2895a9-cb03-4f1d-a025-9e46aca778e5" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2024.png

</div>
This is the output of the EdgeVM-02 interfaces after I have created them.

<div id="c00eca36-f7e4-4584-bcd6-e4b7ef639483" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2025.png

</div>
<span id="48d2c4b2-9274-4f39-97b7-cc6fe47e5e36"></span>
= STEP 6{{fqm}} Configure IPv6 BGP Routing between Tier&ndash;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.

<span id="d80cb842-9675-495c-aae6-efa58748ba0c"></span>
== Pod 110 ==

<div id="0949a445-9309-4939-a390-ef632e99cb42" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%204.png

</div>
I have configured BGP using the configuration parameters in the table below.

{| class="wikitable simple-table"
|-
! 
!  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.

<div id="f3d3d27b-ae21-4bfa-bbe8-1a341ca66500" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2026.png

</div>
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.

{| class="wikitable simple-table"
|-
!  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<br />
10.203.116.3<br />

| fd00:0:0:74::1
| fd00:0000:0000:0074::0002<br />
fd00:0000:0000:0074::0003<br />

|-
| Pod-110-Router
| 65111
| 65110
| 10.203.117.1
| 10.203.117.2<br />
10.203.117.3<br />

| fd00:0:0:75::1
| fd00:0000:0000:0075::0002<br />
fd00:0000:0000:0075::0003<br />

|}

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

<div id="31551656-a288-45af-a997-8095526d36f6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2027.png

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

<div id="d0772477-f44d-4171-a8ad-23b252a1b07d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2028.png

</div>
<div id="5d6217df-d7aa-40e4-a26e-6bb8577d2fe1" class="figure block-color-gray_background callout" style="white-space:pre-wrap;display:flex">

<div style="font-size:1.5em">

<span class="icon">💡</span>

</div>
<div style="width:100%">

<span class="mark highlight-blue">'''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).'''</span>

</div>

</div>
<div class="collapsible">
    <div class="collapsible-alone-header">Verify BGP neighbors on the Pod 110 Router</div>
   <div class="collapsible-content">
<pre class="code">vyos@Pod-110-Router:~$ show ip bgp neighbors
BGP neighbor is 10.203.0.1, remote AS 65000, local AS 65110, external link
 Description: Lab-Router
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 6d04h11m, Last write never
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  0          0
    Notifications:          0          0
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:                  0          0
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset 6d04h11m,  Waiting for peer OPEN
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 28 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is 10.203.116.2, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-01-1
Hostname: Pod-110-T0-EdgeVM-01
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 3d10h34m, Last write 3d07h08m
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 66          1
    Notifications:        132          0
    Updates:                6          6
    Keepalives:          3830       3827
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4034       3834
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 1; dropped 1
  Last reset 3d10h31m,   Notification sent (Hold Timer Expired)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 89 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is 10.203.116.3, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-02-1
Hostname: Pod-110-T0-EdgeVM-02
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 20:36:28, Last write 20:36:29
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 77          9
    Notifications:        152          2
    Updates:               15         16
    Keepalives:          4444       4418
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4688       4445
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 9; dropped 9
  Last reset 20:36:14,   Notification received (Cease/Peer Unconfigured)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 32 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is 10.203.117.2, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-01-2
Hostname: Pod-110-T0-EdgeVM-01
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 3d10h34m, Last write 3d07h08m
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 65          1
    Notifications:        130          0
    Updates:                6          6
    Keepalives:          3830       3827
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4031       3834
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 1; dropped 1
  Last reset 3d10h31m,   Notification sent (Hold Timer Expired)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 79 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is 10.203.117.3, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-02-2
Hostname: Pod-110-T0-EdgeVM-02
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 20:36:23, Last write 20:36:25
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 80         10
    Notifications:        156          2
    Updates:               16         17
    Keepalives:          4442       4414
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4694       4443
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 10; dropped 10
  Last reset 20:36:14,   Notification received (Cease/Peer Unconfigured)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 80 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is fd00::1, remote AS 65000, local AS 65110, external link
 Description: Lab-Router
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 6d04h11m, Last write never
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  0          0
    Notifications:          0          0
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:                  0          0
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset 6d04h11m,  Waiting for peer OPEN
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 29 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is fd00:0:0:74::2, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-01-1
Hostname: Pod-110-T0-EdgeVM-01
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 3d10h34m, Last write 3d07h08m
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 65          1
    Notifications:        130          0
    Updates:                7          6
    Keepalives:          3830       3827
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4032       3834
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 1; dropped 1
  Last reset 3d10h31m,   Notification sent (Hold Timer Expired)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 85 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is fd00:0:0:74::3, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-02-1
Hostname: Pod-110-T0-EdgeVM-02
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 20:36:25, Last write 20:36:25
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 78          9
    Notifications:        154          2
    Updates:               16         15
    Keepalives:          4444       4418
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4692       4444
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 9; dropped 9
  Last reset 20:36:13,   Notification received (Cease/Peer Unconfigured)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 64 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is fd00:0:0:75::2, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-01-2
Hostname: Pod-110-T0-EdgeVM-01
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 3d10h34m, Last write 3d07h08m
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 66          1
    Notifications:        132          0
    Updates:                6          6
    Keepalives:          3830       3827
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4034       3834
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 1; dropped 1
  Last reset 3d10h31m,   Notification sent (Hold Timer Expired)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 46 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is fd00:0:0:75::3, remote AS 65111, local AS 65110, external link
 Description: Pod-110-T0-EdgeVM-02-2
Hostname: Pod-110-T0-EdgeVM-02
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.110.1
  BGP state = Active
  Last read 20:36:23, Last write 20:36:23
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 79         11
    Notifications:        156          2
    Updates:               19         16
    Keepalives:          4444       4414
    Route Refresh:          0          0
    Capability:             0          0
    Total:               4698       4443
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  Default information originate, default not sent
  0 accepted prefixes

  Connections established 11; dropped 11
  Last reset 20:36:13,   Notification received (Cease/Peer Unconfigured)
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 39 seconds
Read thread: off  Write thread: off  FD used: -1

vyos@Pod-110-Router:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 110 EdgeVM-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-110-T0-EdgeVM-01&gt; get logical-router
Wed Sep 07 2022 UTC 10:39:35.805
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4       16/5000

322f1657-3057-44cc-8b32-a947837afbf6   1      2      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7       6/20000

85cbb437-7eab-41ca-99d8-f06655c1c339   3      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5       2/20000

23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7       2/20000

Pod-110-T0-EdgeVM-01&gt; vrf 1
Pod-110-T0-EdgeVM-01(tier0_sr[1])&gt; get bgp neighbor summary
BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv4Unicast
Router ID: 10.203.116.2  Local AS: 65111

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

10.203.116.1                        65110       Estab 03:42:03     NC  228     228     1      5
10.203.117.1                        65110       Estab 03:42:03     NC  228     228     1      6

BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv6Unicast
Router ID: 10.203.116.2  Local AS: 65111

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

fd00:0:0:74::1                      65110       Estab 03:42:03     NC  228     228     1      5
fd00:0:0:75::1                      65110       Estab 03:42:03     NC  228     228     1      6

Wed Sep 07 2022 UTC 10:40:00.202
Pod-110-T0-EdgeVM-01(tier0_sr[1])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 110 EdgeVM-02</div>
   <div class="collapsible-content">
<pre class="code">Pod-110-T0-EdgeVM-02&gt; get logical-router
Wed Sep 07 2022 UTC 10:40:33.273
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4       16/5000

85cbb437-7eab-41ca-99d8-f06655c1c339   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5       2/20000

120dbcf7-2d18-4bb6-94a3-b4797adb5b1b   2      8      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7       6/20000

23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7       2/20000

Pod-110-T0-EdgeVM-02&gt; vrf 2
Pod-110-T0-EdgeVM-02(tier0_sr[2])&gt; get bgp neighbor summary
BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv4Unicast
Router ID: 10.203.117.3  Local AS: 65111

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

10.203.116.1                        65110       Estab 03:42:46     NC  228     228     1      5
10.203.117.1                        65110       Estab 03:42:46     NC  228     228     1      6

BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv6Unicast
Router ID: 10.203.117.3  Local AS: 65111

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

fd00:0:0:74::1                      65110       Estab 03:42:46     NC  228     228     1      5
fd00:0:0:75::1                      65110       Estab 03:42:46     NC  228     228     1      6

Wed Sep 07 2022 UTC 10:40:49.136
Pod-110-T0-EdgeVM-02(tier0_sr[2])&gt;</pre></div></div>

<span id="09b254c3-2a6f-4984-9a24-872c81e4dc55"></span>
== Pod 120 ==

<div id="b1736474-ed25-491f-9aed-08e9f1eab24c" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%205.png

</div>
I have configured BGP using the configuration parameters in the table below.

{| class="wikitable simple-table"
|-
! 
!  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.

<div id="8bbab6f9-c984-4cd2-9255-6286e63b710b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2029.png

</div>
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.

{| class="wikitable simple-table"
|-
!  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<br />
10.203.126.3<br />

| fd00:0:0:7e::1
| fd00:0000:0000:007e::0002<br />
fd00:0000:0000:007e::0003<br />

|-
| Pod-120-Router
| 65121
| 65120
| 10.203.127.1
| 10.203.127.2<br />
10.203.127.3<br />

| fd00:0:0:7f::1
| fd00:0000:0000:007f::0002<br />
fd00:0000:0000:007f::0003<br />

|}

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

<div id="b9740513-f62c-4fd0-976d-9de9afb192de" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2030.png

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

<div id="a3d0f96c-ce9c-4fa0-8785-7deccf2a1020" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2031.png

</div>
<div id="4fce52bf-8b2c-409d-b8e6-16f66f0f03eb" class="figure block-color-gray_background callout" style="white-space:pre-wrap;display:flex">

<div style="font-size:1.5em">

<span class="icon">💡</span>

</div>
<div style="width:100%">

'''<span class="mark highlight-blue">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).</span>'''

</div>

</div>
<div class="collapsible">
    <div class="collapsible-alone-header">Verify BGP neighbors on the Pod 120 Router</div>
   <div class="collapsible-content">
<pre class="code">vyos@Pod-120-Router:~$ show ip bgp neighbors
BGP neighbor is 10.203.0.1, remote AS 65000, local AS 65120, external link
 Description: Lab-Router
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.120.1
  BGP state = Active
  Last read 5d18h40m, Last write never
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  0          0
    Notifications:          0          0
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:                  0          0
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset 5d18h40m,  Waiting for peer OPEN
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 95 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is 10.203.126.2, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-01-1
Hostname: Pod-120-T0-EdgeVM-01
  BGP version 4, remote router ID 10.203.126.2, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:39, Last write 00:00:40
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv4 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv4 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-01,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  1          1
    Notifications:          0          0
    Updates:                3          4
    Keepalives:          8196       8196
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8200       8201
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Update group 3, subgroup 3
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 1; dropped 0
  Last reset 5d18h40m,  No AFI/SAFI activated for peer
Local host: 10.203.126.1, Local port: 179
Foreign host: 10.203.126.2, Foreign port: 39979
Nexthop: 10.203.126.1
Nexthop global: fd00:0:0:7e::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 5 ms
Read thread: on  Write thread: on  FD used: 34

BGP neighbor is 10.203.126.3, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-02-1
Hostname: Pod-120-T0-EdgeVM-02
  BGP version 4, remote router ID 10.203.127.3, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:53, Last write 00:00:54
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv4 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv4 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-02,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 61          2
    Notifications:          0          2
    Updates:                3          4
    Keepalives:          8197       8197
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8261       8205
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Update group 3, subgroup 3
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 2; dropped 1
  Last reset 5d18h35m,  No AFI/SAFI activated for peer
Local host: 10.203.126.1, Local port: 179
Foreign host: 10.203.126.3, Foreign port: 46401
Nexthop: 10.203.126.1
Nexthop global: fd00:0:0:7e::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 4 ms
Read thread: on  Write thread: on  FD used: 28

BGP neighbor is 10.203.127.2, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-01-2
Hostname: Pod-120-T0-EdgeVM-01
  BGP version 4, remote router ID 10.203.126.2, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:39, Last write 00:00:40
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv4 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv4 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-01,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  1          1
    Notifications:          0          0
    Updates:                3          4
    Keepalives:          8196       8196
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8200       8201
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Update group 3, subgroup 3
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 1; dropped 0
  Last reset 5d18h40m,  No AFI/SAFI activated for peer
Local host: 10.203.127.1, Local port: 179
Foreign host: 10.203.127.2, Foreign port: 39009
Nexthop: 10.203.127.1
Nexthop global: fd00:0:0:7f::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 5 ms
Read thread: on  Write thread: on  FD used: 35

BGP neighbor is 10.203.127.3, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-02-2
Hostname: Pod-120-T0-EdgeVM-02
  BGP version 4, remote router ID 10.203.127.3, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:53, Last write 00:00:54
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv4 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv4 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-02,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 61          2
    Notifications:          0          2
    Updates:                3          4
    Keepalives:          8197       8197
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8261       8205
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv4 Unicast
  Update group 3, subgroup 3
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 2; dropped 1
  Last reset 5d18h35m,  No AFI/SAFI activated for peer
Local host: 10.203.127.1, Local port: 179
Foreign host: 10.203.127.3, Foreign port: 33637
Nexthop: 10.203.127.1
Nexthop global: fd00:0:0:7f::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 4 ms
Read thread: on  Write thread: on  FD used: 31

BGP neighbor is fd00::1, remote AS 65000, local AS 65120, external link
 Description: Lab-Router
  BGP version 4, remote router ID 0.0.0.0, local router ID 10.203.120.1
  BGP state = Active
  Last read 5d18h40m, Last write never
  Hold time is 180, keepalive interval is 60 seconds
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: NotApplicable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  0          0
    Notifications:          0          0
    Updates:                0          0
    Keepalives:             0          0
    Route Refresh:          0          0
    Capability:             0          0
    Total:                  0          0
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Not part of any update group
  Community attribute sent to this neighbor(all)
  0 accepted prefixes

  Connections established 0; dropped 0
  Last reset 5d18h40m,  Waiting for peer OPEN
BGP Connect Retry Timer in Seconds: 120
Next connect timer due in 111 seconds
Read thread: off  Write thread: off  FD used: -1

BGP neighbor is fd00:0:0:7e::2, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-01-1
Hostname: Pod-120-T0-EdgeVM-01
  BGP version 4, remote router ID 10.203.126.2, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:39, Last write 00:00:40
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv6 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv6 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-01,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  1          1
    Notifications:          0          0
    Updates:                3          4
    Keepalives:          8196       8196
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8200       8201
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Update group 4, subgroup 4
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 1; dropped 0
  Last reset 5d18h40m,  No AFI/SAFI activated for peer
Local host: fd00:0:0:7e::1, Local port: 179
Foreign host: fd00:0:0:7e::2, Foreign port: 33751
Nexthop: 10.203.126.1
Nexthop global: fd00:0:0:7e::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 4 ms
Read thread: on  Write thread: on  FD used: 36

BGP neighbor is fd00:0:0:7e::3, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-02-1
Hostname: Pod-120-T0-EdgeVM-02
  BGP version 4, remote router ID 10.203.127.3, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:53, Last write 00:00:53
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv6 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv6 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-02,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 61          2
    Notifications:          0          2
    Updates:                3          4
    Keepalives:          8197       8197
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8261       8205
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Update group 4, subgroup 4
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 2; dropped 1
  Last reset 5d18h35m,  No AFI/SAFI activated for peer
Local host: fd00:0:0:7e::1, Local port: 179
Foreign host: fd00:0:0:7e::3, Foreign port: 38153
Nexthop: 10.203.126.1
Nexthop global: fd00:0:0:7e::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 4 ms
Read thread: on  Write thread: on  FD used: 32

BGP neighbor is fd00:0:0:7f::2, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-01-2
Hostname: Pod-120-T0-EdgeVM-01
  BGP version 4, remote router ID 10.203.126.2, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:39, Last write 00:00:40
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv6 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv6 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-01,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                  1          1
    Notifications:          0          0
    Updates:                3          4
    Keepalives:          8196       8196
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8200       8201
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Update group 4, subgroup 4
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 1; dropped 0
  Last reset 5d18h40m,  No AFI/SAFI activated for peer
Local host: fd00:0:0:7f::1, Local port: 179
Foreign host: fd00:0:0:7f::2, Foreign port: 40945
Nexthop: 10.203.127.1
Nexthop global: fd00:0:0:7f::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 5 ms
Read thread: on  Write thread: on  FD used: 37

BGP neighbor is fd00:0:0:7f::3, remote AS 65121, local AS 65120, external link
 Description: Pod-120-T0-EdgeVM-02-2
Hostname: Pod-120-T0-EdgeVM-02
  BGP version 4, remote router ID 10.203.127.3, local router ID 10.203.120.1
  BGP state = Established, up for 5d16h35m
  Last read 00:00:52, Last write 00:00:53
  Hold time is 180, keepalive interval is 60 seconds
  Neighbor capabilities:
    4 Byte AS: advertised and received
    Extended Message: advertised
    AddPath:
      IPv6 Unicast: RX advertised and received
    Route refresh: advertised and received(old &amp; new)
    Enhanced Route Refresh: advertised
    Address Family IPv6 Unicast: advertised and received
    Hostname Capability: advertised (name: Pod-120-Router,domain name: n/a) received (name: Pod-120-T0-EdgeVM-02,domain name: n/a)
    Graceful Restart Capability: advertised
  Graceful restart information:
    Local GR Mode: Helper*
    Remote GR Mode: Disable
    R bit: False
    Timers:
      Configured Restart Time(sec): 120
      Received Restart Time(sec): 0
  Message statistics:
    Inq depth is 0
    Outq depth is 0
                         Sent       Rcvd
    Opens:                 62          2
    Notifications:          0          2
    Updates:                3          4
    Keepalives:          8197       8197
    Route Refresh:          0          0
    Capability:             0          0
    Total:               8262       8205
  Minimum time between advertisement runs is 0 seconds

 For address family: IPv6 Unicast
  Update group 4, subgroup 4
  Packet Queue length 0
  Community attribute sent to this neighbor(all)
  Default information originate, default sent
  5 accepted prefixes

  Connections established 2; dropped 1
  Last reset 5d18h35m,  No AFI/SAFI activated for peer
Local host: fd00:0:0:7f::1, Local port: 179
Foreign host: fd00:0:0:7f::3, Foreign port: 42663
Nexthop: 10.203.127.1
Nexthop global: fd00:0:0:7f::1
Nexthop local: fe80::20c:29ff:fee3:7980
BGP connection: shared network
BGP Connect Retry Timer in Seconds: 120
Estimated round trip time: 4 ms
Read thread: on  Write thread: on  FD used: 33

vyos@Pod-120-Router:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 120 EdgeVM-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-T0-EdgeVM-01&gt; get logical-routers
Tue Sep 06 2022 UTC 13:43:16.392
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4       16/5000

e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5       2/20000

06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7       2/20000

157da70b-9636-4163-b175-35e8f7535637   3      2      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7       6/20000

Pod-120-T0-EdgeVM-01&gt; vrf 3
Pod-120-T0-EdgeVM-01(tier0_sr[3])&gt; get bgp neighbor summary
BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv4Unicast
Router ID: 10.203.126.2  Local AS: 65121

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

10.203.126.1                        65120       Estab 5d16h42m     NC  8207    8208    1      5
10.203.127.1                        65120       Estab 5d16h42m     NC  8207    8208    1      6

BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv6Unicast
Router ID: 10.203.126.2  Local AS: 65121

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

fd00:0:0:7e::1                      65120       Estab 5d16h42m     NC  8207    8208    1      5
fd00:0:0:7f::1                      65120       Estab 5d16h42m     NC  8207    8208    1      6

Tue Sep 06 2022 UTC 13:43:40.065
Pod-120-T0-EdgeVM-01(tier0_sr[3])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Verify BGP neighbors on the Tier-0 Gateway VRF on the Pod 120 EdgeVM-02</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-T0-EdgeVM-02&gt; get logical-router
Tue Sep 06 2022 UTC 13:44:05.247
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4       16/5000

e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5       2/20000

06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7       2/20000

9ec0f75a-5f89-4551-9462-96de69c6a38f   3      7      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7       6/20000

Pod-120-T0-EdgeVM-02&gt; vrf 3
Pod-120-T0-EdgeVM-02(tier0_sr[3])&gt; get bgp neighbor summary
BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv4Unicast
Router ID: 10.203.127.3  Local AS: 65121

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

10.203.126.1                        65120       Estab 5d16h43m     NC  8210    8213    1      5
10.203.127.1                        65120       Estab 5d16h43m     NC  8210    8213    1      6

BFD States: NC - Not configured, DC - Disconnected
            AD - Admin down, DW - Down, IN - Init, UP - Up
BGP summary information for VRF default for address-family: ipv6Unicast
Router ID: 10.203.127.3  Local AS: 65121

Neighbor                            AS          State Up/DownTime  BFD InMsgs  OutMsgs InPfx  OutPfx

fd00:0:0:7e::1                      65120       Estab 5d16h43m     NC  8210    8213    1      5
fd00:0:0:7f::1                      65120       Estab 5d16h43m     NC  8210    8213    1      6

Tue Sep 06 2022 UTC 13:44:26.834
Pod-120-T0-EdgeVM-02(tier0_sr[3])&gt;</pre></div></div>

<span id="568a4fbe-ce9c-4db8-a6a9-aeecb2741b55"></span>
= STEP 7{{fqm}} Create a Tier&ndash;1 Gateway =

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

<span id="3f2e6f37-677f-47c4-812c-ad38004392b1"></span>
== Pod 110 ==

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

{| class="wikitable simple-table"
|-
!  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.

<div id="d12150bb-0c80-4b21-8726-91353aefa3f1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2032.png

</div>
<span id="c8342a2c-6ce9-401e-8c46-18efe3b93962"></span>
== Pod 120 ==

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

{| class="wikitable simple-table"
|-
!  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.

<div id="68eb0413-c78e-4d45-8adf-0a8c20875a8d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2033.png

</div>
<span id="05a04607-9bda-4413-8e4e-4b3497d7ae9e"></span>
= STEP 8{{fqm}} 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.

<span id="aa027236-ca52-450a-ac0a-544fad258492"></span>
== Pod 110 ==

<div id="74c1dfd4-08ee-40ae-9c46-6d2a63cc7be0" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2034.png

</div>
I have created the Segments using the configuration parameters in the table below.

{| class="wikitable simple-table"
|-
!  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
| TZ-Overlay | Overlay
| T1-Gateway-01
|-
| Pod-110-App
| fd00:a:b::/64
| fd00:a:b::1
| 192.168.2.0/24
| 192.168.2.1
| TZ-Overlay | Overlay
| T1-Gateway-01
|-
| Pod-110-DB
| fd00:a:c::/64
| fd00:a:c::1
| 192.168.3.0/24
| 192.168.3.1
| TZ-Overlay | Overlay
| T1-Gateway-01
|}

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

<div id="2bb5f0f4-1ae5-4ba7-ae71-a8b9fc06235f" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2035.png

</div>
<span id="46d09c46-7970-476b-b20b-25c1ce89e11c"></span>
== Pod 120 ==

<div id="47d7aed7-714e-483e-b2ae-6bc2aa0a86ac" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2036.png

</div>
I have created the Segments using the configuration parameters in the table below.

{| class="wikitable simple-table"
|-
!  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
| TZ-Overlay | Overlay
| T1-Gateway-01
|-
| Pod-120-App
| fd00:b:b::/64
| fd00:b:b::1
| 192.168.6.0/24
| 192.168.6.1
| TZ-Overlay | Overlay
| T1-Gateway-01
|-
| Pod-120-DB
| fd00:b:c::/64
| fd00:b:c::1
| 192.168.7.0/24
| 192.168.7.1
| TZ-Overlay | Overlay
| T1-Gateway-01
|}

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

<div id="e23cbd8d-f90e-42ab-bddc-d6d79662bae8" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2037.png

</div>
<span id="a123ed9e-2687-4286-9c01-44d1054ee074"></span>
= STEP 9{{fqm}} Configure Route Advertise connected Tier&ndash;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.

<div id="9c2f803d-5c4b-4dea-b986-d8fd7c8418d6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2038.png

</div>
<span id="8104a2d9-e702-4c40-8419-eb3640d54860"></span>
== Pod 110 ==

<span id="dfc08751-cd57-454e-ad76-108205f1e66e"></span>
=== T1&ndash;Gateway ===

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

<div id="36317549-25f0-4dd5-9108-2f53def7d0b1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2039.png

</div>
<span id="a222a5c0-ca70-4ca1-9e5f-23522d0d368f"></span>
=== T0&ndash;Gateway ===

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

<div id="8f0bdcff-e03c-46ac-94a0-6cd23a3b5ba4" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2040.png

</div>
<div id="9b95955d-5c8f-4556-a3d1-e6ab3c8d0c5d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2041.png

</div>
<div id="d0eb1cbb-fb40-4f84-b0a0-b4052fe183d6" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2042.png

</div>
<span id="50891c4f-526d-41ad-ac73-1dc3b1d0e5cc"></span>
== Pod 120 ==

<span id="25e0d913-6c4e-45c7-ae5e-13c497ff7c50"></span>
=== T1&ndash;Gateway ===

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

<div id="3cd49388-3694-491a-ad91-36950da5f542" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2043.png

</div>
<span id="0fbe6f53-df69-4920-a6c2-33395758f5c1"></span>
=== T0&ndash;Gateway ===

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

<div id="df776d8c-f02d-482e-adde-87639921d48e" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2044.png

</div>
<div id="6f5380a3-1c44-4f90-9d97-e8472aa58f25" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2045.png

</div>
<div id="4d809ee7-deaf-477c-a105-68fdd798dd7b" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2046.png

</div>
<span id="aa5d4f62-c9b9-4d8f-9b71-f364fd53c82b"></span>
= STEP 10{{fqm}} 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.

<span id="7aafbe02-ef85-43a2-bd9e-728d55b815f4"></span>
== 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.

<pre class="code">#
set protocols ospf redistribute bgp
set protocols ospfv3 redistribute bgp
#</pre>
<span id="8c016110-901f-45b2-bcab-a415fd54b545"></span>
=== 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:

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-Router (IPv6)</div>
   <div class="collapsible-content">
<pre class="code">vyos@Pod-110-Router:~$ show ipv6 route
Codes: K - kernel route, C - connected, S - static, R - RIPng,
       O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table,
       v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       &gt; - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

O   fd00::/64 [110/1] is directly connected, eth0, weight 1, 02:06:00
C&gt;* fd00::/64 is directly connected, eth0, 11:40:13
C&gt;* fd00:0:0:6e::/64 is directly connected, eth1.110, 11:40:15
C&gt;* fd00:0:0:6f::/64 is directly connected, eth1.111, 11:40:14
C&gt;* fd00:0:0:70::/64 is directly connected, eth1.112, 11:40:14
C&gt;* fd00:0:0:71::/64 is directly connected, eth1.113, 11:40:15
C&gt;* fd00:0:0:72::/64 is directly connected, eth1.114, 11:40:15
C&gt;* fd00:0:0:73::/64 is directly connected, eth1.115, 11:40:14
B   fd00:0:0:74::/64 [20/0] via fe80::250:56ff:fe9e:1748, eth1.117, weight 1, 09:49:24
                            via fe80::250:56ff:fe9e:60a9, eth1.117, weight 1, 09:49:24
                            via fe80::250:56ff:fe9e:72ee, eth1.116, weight 1, 09:49:24
                            via fe80::250:56ff:fe9e:d5d1, eth1.116, weight 1, 09:49:24
C&gt;* fd00:0:0:74::/64 is directly connected, eth1.116, 11:40:14
B   fd00:0:0:75::/64 [20/0] via fe80::250:56ff:fe9e:1748, eth1.117, weight 1, 09:49:24
                            via fe80::250:56ff:fe9e:60a9, eth1.117, weight 1, 09:49:24
                            via fe80::250:56ff:fe9e:72ee, eth1.116, weight 1, 09:49:24
                            via fe80::250:56ff:fe9e:d5d1, eth1.116, weight 1, 09:49:24
C&gt;* fd00:0:0:75::/64 is directly connected, eth1.117, 11:40:14
C&gt;* fd00:0:0:76::/64 is directly connected, eth1.118, 11:40:13
C&gt;* fd00:0:0:77::/64 is directly connected, eth1.119, 11:40:13
O&gt;* fd00:0:0:78::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:79::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:7a::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:7b::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:7c::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:7d::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:7e::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:7f::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:80::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:81::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 02:06:00
O&gt;* fd00:0:0:ffff::/64 [110/20] via fe80::b6fb:e4ff:feca:eb06, eth0, weight 1, 02:06:00
B&gt;* fd00:a:a::/64 [20/0] via fe80::250:56ff:fe9e:1748, eth1.117, weight 1, 09:49:20
  *                      via fe80::250:56ff:fe9e:60a9, eth1.117, weight 1, 09:49:20
  *                      via fe80::250:56ff:fe9e:72ee, eth1.116, weight 1, 09:49:20
  *                      via fe80::250:56ff:fe9e:d5d1, eth1.116, weight 1, 09:49:20
B&gt;* fd00:a:b::/64 [20/0] via fe80::250:56ff:fe9e:1748, eth1.117, weight 1, 09:49:09
  *                      via fe80::250:56ff:fe9e:60a9, eth1.117, weight 1, 09:49:09
  *                      via fe80::250:56ff:fe9e:72ee, eth1.116, weight 1, 09:49:09
  *                      via fe80::250:56ff:fe9e:d5d1, eth1.116, weight 1, 09:49:09
B&gt;* fd00:a:c::/64 [20/0] via fe80::250:56ff:fe9e:1748, eth1.117, weight 1, 09:49:09
  *                      via fe80::250:56ff:fe9e:60a9, eth1.117, weight 1, 09:49:09
  *                      via fe80::250:56ff:fe9e:72ee, eth1.116, weight 1, 09:49:09
  *                      via fe80::250:56ff:fe9e:d5d1, eth1.116, weight 1, 09:49:09
O&gt;* fd00:b:a::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 00:01:20
O&gt;* fd00:b:b::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 00:01:20
O&gt;* fd00:b:c::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth0, weight 1, 00:01:20
C * fe80::/64 is directly connected, eth1.119, 11:40:13
C * fe80::/64 is directly connected, eth1.117, 11:40:13
C * fe80::/64 is directly connected, eth1.118, 11:40:14
C * fe80::/64 is directly connected, eth1.116, 11:40:14
C * fe80::/64 is directly connected, eth1.115, 11:40:14
C * fe80::/64 is directly connected, eth1.113, 11:40:14
C * fe80::/64 is directly connected, eth1.114, 11:40:14
C * fe80::/64 is directly connected, eth1.110, 11:40:15
C * fe80::/64 is directly connected, eth1.111, 11:40:15
C * fe80::/64 is directly connected, eth1.112, 11:40:15
C * fe80::/64 is directly connected, eth0, 11:42:38
C * fe80::/64 is directly connected, eth1, 11:42:38
C&gt;* fe80::/64 is directly connected, lo, 11:42:39
vyos@Pod-110-Router:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-Router (IPv4)</div>
   <div class="collapsible-content">
<pre class="code">vyos@Pod-110-Router:~$ show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       &gt; - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

S&gt;* 0.0.0.0/0 [250/0] via 10.203.0.1, eth0, weight 1, 11:43:14
O&gt;* 10.8.0.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.8.1.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.8.2.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.8.3.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.11.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.14.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.17.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.19.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.20.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.21.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.22.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.23.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.24.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.25.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.31.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.32.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O&gt;* 10.11.111.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
O   10.203.0.0/24 [110/1] is directly connected, eth0, weight 1, 11:43:19
C&gt;* 10.203.0.0/24 is directly connected, eth0, 11:44:27
C&gt;* 10.203.110.0/24 is directly connected, eth1.110, 11:43:28
C&gt;* 10.203.111.0/24 is directly connected, eth1.111, 11:43:27
C&gt;* 10.203.112.0/24 is directly connected, eth1.112, 11:43:27
C&gt;* 10.203.113.0/24 is directly connected, eth1.113, 11:43:27
C&gt;* 10.203.114.0/24 is directly connected, eth1.114, 11:43:27
C&gt;* 10.203.115.0/24 is directly connected, eth1.115, 11:43:27
B   10.203.116.0/24 [20/0] via 10.203.116.2 inactive, weight 1, 09:52:35
                           via 10.203.116.3 inactive, weight 1, 09:52:35
                           via 10.203.117.2, eth1.117, weight 1, 09:52:35
                           via 10.203.117.3, eth1.117, weight 1, 09:52:35
O   10.203.116.0/24 [110/1] is directly connected, eth1.116, weight 1, 11:43:19
C&gt;* 10.203.116.0/24 is directly connected, eth1.116, 11:43:27
B   10.203.117.0/24 [20/0] via 10.203.116.2, eth1.116, weight 1, 09:52:35
                           via 10.203.116.3, eth1.116, weight 1, 09:52:35
                           via 10.203.117.2 inactive, weight 1, 09:52:35
                           via 10.203.117.3 inactive, weight 1, 09:52:35
O   10.203.117.0/24 [110/1] is directly connected, eth1.117, weight 1, 11:43:19
C&gt;* 10.203.117.0/24 is directly connected, eth1.117, 11:43:26
C&gt;* 10.203.118.0/24 is directly connected, eth1.118, 11:43:26
C&gt;* 10.203.119.0/24 is directly connected, eth1.119, 11:43:26
O&gt;* 10.203.120.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.121.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.122.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.123.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.124.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.125.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.126.0/24 [110/2] via 10.203.0.120, eth0, weight 1, 02:08:53
O&gt;* 10.203.127.0/24 [110/2] via 10.203.0.120, eth0, weight 1, 02:08:53
O&gt;* 10.203.128.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
O&gt;* 10.203.129.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 02:08:52
B&gt;* 192.168.1.0/24 [20/0] via 10.203.116.2, eth1.116, weight 1, 09:52:31
  *                       via 10.203.116.3, eth1.116, weight 1, 09:52:31
  *                       via 10.203.117.2, eth1.117, weight 1, 09:52:31
  *                       via 10.203.117.3, eth1.117, weight 1, 09:52:31
B&gt;* 192.168.2.0/24 [20/0] via 10.203.116.2, eth1.116, weight 1, 09:52:20
  *                       via 10.203.116.3, eth1.116, weight 1, 09:52:20
  *                       via 10.203.117.2, eth1.117, weight 1, 09:52:20
  *                       via 10.203.117.3, eth1.117, weight 1, 09:52:20
B&gt;* 192.168.3.0/24 [20/0] via 10.203.116.2, eth1.116, weight 1, 09:52:20
  *                       via 10.203.116.3, eth1.116, weight 1, 09:52:20
  *                       via 10.203.117.2, eth1.117, weight 1, 09:52:20
  *                       via 10.203.117.3, eth1.117, weight 1, 09:52:20
O&gt;* 192.168.5.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 00:04:31
O&gt;* 192.168.6.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 00:04:31
O&gt;* 192.168.7.0/24 [110/20] via 10.203.0.120, eth0, weight 1, 00:04:31
O&gt;* 192.168.111.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 11:42:37
vyos@Pod-110-Router:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-T0-EdgeVM-01 | DR-T0-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-110-T0-EdgeVM-01&gt; get logical-router
Wed Aug 31 2022 UTC 21:21:04.286
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
85cbb437-7eab-41ca-99d8-f06655c1c339   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
322f1657-3057-44cc-8b32-a947837afbf6   2      2      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000
23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000

Pod-110-T0-EdgeVM-01&gt; vrf 1
Pod-110-T0-EdgeVM-01(vrf[1])&gt; get forwarding
Wed Aug 31 2022 UTC 21:21:31.148
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
85cbb437-7eab-41ca-99d8-f06655c1c339   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          10.203.117.1                              route       cbba506e-bd0c-4ce2-8804-c8bbe285bddb   00:0c:29:f4:7f:1d
                   10.203.116.1                                          5740e6e6-f6e7-4124-a71a-09b9137cff05   00:0c:29:f4:7f:1d
10.203.116.0/24                                              route       5740e6e6-f6e7-4124-a71a-09b9137cff05

10.203.116.2/32                                              route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac

10.203.116.3/32    169.254.0.131                             route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1   02:50:56:56:52:02
10.203.117.0/24                                              route       cbba506e-bd0c-4ce2-8804-c8bbe285bddb

10.203.117.2/32                                              route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac

10.203.117.3/32    169.254.0.131                             route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1   02:50:56:56:52:02
100.64.0.0/32                                                route       5a021141-cb97-55d6-ac9e-8aec433dc117

100.64.0.0/31                                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

127.0.0.1/32                                                 route       89d6dd69-bcb1-4f6f-8bcf-870d38a0dd12

169.254.0.0/25                                               route       87b65dce-de55-439a-b215-4fa9ba7ea233

169.254.0.1/32                                               route       5a021141-cb97-55d6-ac9e-8aec433dc117

169.254.0.2/32                                               route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac

169.254.0.128/25                                             route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1

169.254.0.130/32                                             route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac

192.168.1.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

192.168.2.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

192.168.3.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fe80::20c:29ff:fef4:7f1d                  route       5740e6e6-f6e7-4124-a71a-09b9137cff05
::1/128                                                                                 route       89d6dd69-bcb1-4f6f-8bcf-870d38a0dd12
fc3a:f453:da8:9c00::/64                                                                 route       38b49f07-a670-53a7-9532-ef2523ee94a6
fc3a:f453:da8:9c00::1/128                                                               route       5a021141-cb97-55d6-ac9e-8aec433dc117
fd00:0:0:74::/64                                                                        route       5740e6e6-f6e7-4124-a71a-09b9137cff05
fd00::74:250:56ff:fe9e:d5d1/128                                                         route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac
fd00:0:0:74::3/128                            fe80::50:56ff:fe56:5202                   route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1
fd00::74:250:56ff:fe9e:72ee/128               fe80::50:56ff:fe56:5202                   route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1
fd00:0:0:74::2/128                                                                      route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac
fd00:0:0:75::/64                                                                        route       cbba506e-bd0c-4ce2-8804-c8bbe285bddb
fd00::75:250:56ff:fe9e:60a9/128                                                         route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac
fd00:0:0:75::3/128                            fe80::50:56ff:fe56:5202                   route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1
fd00::75:250:56ff:fe9e:1748/128               fe80::50:56ff:fe56:5202                   route       f4fab2ff-46bc-4329-a426-70ef4c30b4d1
fd00:0:0:75::2/128                                                                      route       5ba3c8c8-d2ef-5c83-a39e-1a431c1f0aac
fd00:a:a::/64                                 fc3a:f453:da8:9c00::2                     route       38b49f07-a670-53a7-9532-ef2523ee94a6
fd00:a:b::/64                                 fc3a:f453:da8:9c00::2                     route       38b49f07-a670-53a7-9532-ef2523ee94a6
fd00:a:c::/64                                 fc3a:f453:da8:9c00::2                     route       38b49f07-a670-53a7-9532-ef2523ee94a6

Pod-110-T0-EdgeVM-01(vrf[1])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-T0-EdgeVM-02 | DR-T0-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-110-T0-EdgeVM-02&gt; get logical-router
Wed Aug 31 2022 UTC 21:31:33.980
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
120dbcf7-2d18-4bb6-94a3-b4797adb5b1b   1      8      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000
85cbb437-7eab-41ca-99d8-f06655c1c339   3      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000

Pod-110-T0-EdgeVM-02&gt; vrf 3
Pod-110-T0-EdgeVM-02(vrf[3])&gt; get forwarding
Wed Aug 31 2022 UTC 21:32:04.191
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
85cbb437-7eab-41ca-99d8-f06655c1c339   3      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          10.203.117.1                              route       21944796-95ae-4037-8f53-c6c104a440e3   00:0c:29:f4:7f:1d
                   10.203.116.1                                          450698c4-ecb4-4f70-b4d4-7e447f8694e8   00:0c:29:f4:7f:1d
10.203.116.0/24                                              route       450698c4-ecb4-4f70-b4d4-7e447f8694e8

10.203.116.2/32    169.254.0.130                             route       0eeffa82-94d2-479a-86f3-daddee65c7b0   02:50:56:56:52:01
10.203.116.3/32                                              route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050

10.203.117.0/24                                              route       21944796-95ae-4037-8f53-c6c104a440e3

10.203.117.2/32    169.254.0.130                             route       0eeffa82-94d2-479a-86f3-daddee65c7b0   02:50:56:56:52:01
10.203.117.3/32                                              route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050

100.64.0.0/32                                                route       5a021141-cb97-55d6-ac9e-8aec433dc117

100.64.0.0/31                                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

127.0.0.1/32                                                 route       89d6dd69-bcb1-4f6f-8bcf-870d38a0dd12

169.254.0.0/25                                               route       267b98fb-5783-441b-b91f-03c288b2ffd8

169.254.0.1/32                                               route       5a021141-cb97-55d6-ac9e-8aec433dc117

169.254.0.3/32                                               route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050

169.254.0.128/25                                             route       0eeffa82-94d2-479a-86f3-daddee65c7b0

169.254.0.131/32                                             route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050

192.168.1.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

192.168.2.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

192.168.3.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fe80::20c:29ff:fef4:7f1d                  route       450698c4-ecb4-4f70-b4d4-7e447f8694e8
::1/128                                                                                 route       89d6dd69-bcb1-4f6f-8bcf-870d38a0dd12
fc3a:f453:da8:9c00::/64                                                                 route       38b49f07-a670-53a7-9532-ef2523ee94a6
fc3a:f453:da8:9c00::1/128                                                               route       5a021141-cb97-55d6-ac9e-8aec433dc117
fd00:0:0:74::/64                                                                        route       450698c4-ecb4-4f70-b4d4-7e447f8694e8
fd00::74:250:56ff:fe9e:72ee/128                                                         route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050
fd00:0:0:74::2/128                            fe80::50:56ff:fe56:5201                   route       0eeffa82-94d2-479a-86f3-daddee65c7b0
fd00::74:250:56ff:fe9e:d5d1/128               fe80::50:56ff:fe56:5201                   route       0eeffa82-94d2-479a-86f3-daddee65c7b0
fd00:0:0:74::3/128                                                                      route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050
fd00:0:0:75::/64                                                                        route       21944796-95ae-4037-8f53-c6c104a440e3
fd00:0:0:75::3/128                                                                      route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050
fd00:0:0:75::2/128                            fe80::50:56ff:fe56:5201                   route       0eeffa82-94d2-479a-86f3-daddee65c7b0
fd00::75:250:56ff:fe9e:60a9/128               fe80::50:56ff:fe56:5201                   route       0eeffa82-94d2-479a-86f3-daddee65c7b0
fd00::75:250:56ff:fe9e:1748/128                                                         route       47aa33ab-f598-58c3-9b4c-c0b5fbbea050
fd00:a:a::/64                                 fc3a:f453:da8:9c00::2                     route       38b49f07-a670-53a7-9532-ef2523ee94a6
fd00:a:b::/64                                 fc3a:f453:da8:9c00::2                     route       38b49f07-a670-53a7-9532-ef2523ee94a6
fd00:a:c::/64                                 fc3a:f453:da8:9c00::2                     route       38b49f07-a670-53a7-9532-ef2523ee94a6

Pod-110-T0-EdgeVM-02(vrf[3])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-T0-EdgeVM-01 | DR-T1-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-110-T0-EdgeVM-01&gt; get logical-router
Wed Aug 31 2022 UTC 21:33:04.933
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
85cbb437-7eab-41ca-99d8-f06655c1c339   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
322f1657-3057-44cc-8b32-a947837afbf6   2      2      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000
23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000

Pod-110-T0-EdgeVM-01&gt; vrf 4
Pod-110-T0-EdgeVM-01(vrf[4])&gt; get forwarding
Wed Aug 31 2022 UTC 21:33:19.176
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          100.64.0.0                                route       d02ec573-aa99-4777-983d-16de67c16cde

100.64.0.0/31                                                route       d02ec573-aa99-4777-983d-16de67c16cde

100.64.0.1/32                                                route       49d24744-e3e9-5f35-9684-4f539a05ebcd

192.168.1.0/24                                               route       22774d84-817a-4628-be5c-c5bf8d8da884

192.168.1.1/32                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd

192.168.2.0/24                                               route       1535af50-fb99-48ce-b863-9c83c86241f8

192.168.2.1/32                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd

192.168.3.0/24                                               route       f46e8977-82b6-4bd0-b9bd-a035ca05f0bd

192.168.3.1/32                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fc3a:f453:da8:9c00::1                     route       d02ec573-aa99-4777-983d-16de67c16cde
fc3a:f453:da8:9c00::/64                                                                 route       d02ec573-aa99-4777-983d-16de67c16cde
fc3a:f453:da8:9c00::2/128                                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:a::/64                                                                           route       22774d84-817a-4628-be5c-c5bf8d8da884
fd00:a:a::1/128                                                                         route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:a:0:50:56ff:fe56:4452/128                                                        route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:b::/64                                                                           route       1535af50-fb99-48ce-b863-9c83c86241f8
fd00:a:b::1/128                                                                         route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:b:0:50:56ff:fe56:4452/128                                                        route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:c::/64                                                                           route       f46e8977-82b6-4bd0-b9bd-a035ca05f0bd
fd00:a:c::1/128                                                                         route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:c:0:50:56ff:fe56:4452/128                                                        route       49d24744-e3e9-5f35-9684-4f539a05ebcd

Pod-110-T0-EdgeVM-01(vrf[4])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-110-T0-EdgeVM-02 | DR-T1-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-110-T0-EdgeVM-02&gt; get logical-router
Wed Aug 31 2022 UTC 21:33:56.857
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
120dbcf7-2d18-4bb6-94a3-b4797adb5b1b   1      8      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000
85cbb437-7eab-41ca-99d8-f06655c1c339   3      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000

Pod-110-T0-EdgeVM-02&gt; vrf 4
Pod-110-T0-EdgeVM-02(vrf[4])&gt; get forwarding
Wed Aug 31 2022 UTC 21:34:31.912
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
23184393-a35e-46df-989c-6af86651f127   4      3      DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          100.64.0.0                                route       d02ec573-aa99-4777-983d-16de67c16cde

100.64.0.0/31                                                route       d02ec573-aa99-4777-983d-16de67c16cde

100.64.0.1/32                                                route       49d24744-e3e9-5f35-9684-4f539a05ebcd

192.168.1.0/24                                               route       22774d84-817a-4628-be5c-c5bf8d8da884

192.168.1.1/32                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd

192.168.2.0/24                                               route       1535af50-fb99-48ce-b863-9c83c86241f8

192.168.2.1/32                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd

192.168.3.0/24                                               route       f46e8977-82b6-4bd0-b9bd-a035ca05f0bd

192.168.3.1/32                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fc3a:f453:da8:9c00::1                     route       d02ec573-aa99-4777-983d-16de67c16cde
fc3a:f453:da8:9c00::/64                                                                 route       d02ec573-aa99-4777-983d-16de67c16cde
fc3a:f453:da8:9c00::2/128                                                               route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:a::/64                                                                           route       22774d84-817a-4628-be5c-c5bf8d8da884
fd00:a:a::1/128                                                                         route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:a:0:50:56ff:fe56:4452/128                                                        route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:b::/64                                                                           route       1535af50-fb99-48ce-b863-9c83c86241f8
fd00:a:b::1/128                                                                         route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:b:0:50:56ff:fe56:4452/128                                                        route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:c::/64                                                                           route       f46e8977-82b6-4bd0-b9bd-a035ca05f0bd
fd00:a:c::1/128                                                                         route       49d24744-e3e9-5f35-9684-4f539a05ebcd
fd00:a:c:0:50:56ff:fe56:4452/128                                                        route       49d24744-e3e9-5f35-9684-4f539a05ebcd

Pod-110-T0-EdgeVM-02(vrf[4])&gt;</pre></div></div>

<span id="19ffd194-f404-42c0-a1a1-4f4acb0f128d"></span>
== 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.

<pre class="code">#
set protocols ospf redistribute bgp
set protocols ospfv3 redistribute bgp
#</pre>
<span id="edf6ed79-df51-4d82-a66d-32be1400cab4"></span>
=== 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:

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-Router (IPv6)</div>
   <div class="collapsible-content">
<pre class="code">vyos@Pod-120-Router:~$ show ipv6 route
Codes: K - kernel route, C - connected, S - static, R - RIPng,
       O - OSPFv3, I - IS-IS, B - BGP, N - NHRP, T - Table,
       v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       &gt; - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

O   fd00::/64 [110/1] is directly connected, eth0, weight 1, 02:06:35
C&gt;* fd00::/64 is directly connected, eth0, 02:06:53
O&gt;* fd00:0:0:6e::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:6f::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:70::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:71::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:72::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:73::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:74::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:75::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:76::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:0:0:77::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
C&gt;* fd00:0:0:78::/64 is directly connected, eth1.120, 02:06:56
C&gt;* fd00:0:0:79::/64 is directly connected, eth1.121, 02:06:55
C&gt;* fd00:0:0:7a::/64 is directly connected, eth1.122, 02:06:55
C&gt;* fd00:0:0:7b::/64 is directly connected, eth1.123, 02:06:55
C&gt;* fd00:0:0:7c::/64 is directly connected, eth1.124, 02:06:54
C&gt;* fd00:0:0:7d::/64 is directly connected, eth1.125, 02:06:55
B   fd00:0:0:7e::/64 [20/0] via fe80::250:56ff:fe85:ca6, eth1.127, weight 1, 00:01:39
                            via fe80::250:56ff:fe85:46bb, eth1.126, weight 1, 00:01:39
                            via fe80::250:56ff:fe85:7400, eth1.126, weight 1, 00:01:39
                            via fe80::250:56ff:fe85:74ef, eth1.127, weight 1, 00:01:39
C&gt;* fd00:0:0:7e::/64 is directly connected, eth1.126, 02:06:54
B   fd00:0:0:7f::/64 [20/0] via fe80::250:56ff:fe85:ca6, eth1.127, weight 1, 00:01:39
                            via fe80::250:56ff:fe85:46bb, eth1.126, weight 1, 00:01:39
                            via fe80::250:56ff:fe85:7400, eth1.126, weight 1, 00:01:39
                            via fe80::250:56ff:fe85:74ef, eth1.127, weight 1, 00:01:39
C&gt;* fd00:0:0:7f::/64 is directly connected, eth1.127, 02:06:54
C&gt;* fd00:0:0:80::/64 is directly connected, eth1.128, 02:06:54
C&gt;* fd00:0:0:81::/64 is directly connected, eth1.129, 02:06:54
O&gt;* fd00:0:0:ffff::/64 [110/20] via fe80::b6fb:e4ff:feca:eb06, eth0, weight 1, 02:06:35
O&gt;* fd00:a:a::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:a:b::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
O&gt;* fd00:a:c::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth0, weight 1, 02:06:35
B&gt;* fd00:b:a::/64 [20/0] via fe80::250:56ff:fe85:ca6, eth1.127, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:46bb, eth1.126, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:7400, eth1.126, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:74ef, eth1.127, weight 1, 00:01:39
B&gt;* fd00:b:b::/64 [20/0] via fe80::250:56ff:fe85:ca6, eth1.127, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:46bb, eth1.126, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:7400, eth1.126, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:74ef, eth1.127, weight 1, 00:01:39
B&gt;* fd00:b:c::/64 [20/0] via fe80::250:56ff:fe85:ca6, eth1.127, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:46bb, eth1.126, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:7400, eth1.126, weight 1, 00:01:39
  *                      via fe80::250:56ff:fe85:74ef, eth1.127, weight 1, 00:01:39
C * fe80::/64 is directly connected, eth1.129, 02:06:53
C * fe80::/64 is directly connected, eth0, 02:06:54
C * fe80::/64 is directly connected, eth1.128, 02:06:54
C * fe80::/64 is directly connected, eth1.127, 02:06:54
C * fe80::/64 is directly connected, eth1.125, 02:06:54
C * fe80::/64 is directly connected, eth1.126, 02:06:54
C * fe80::/64 is directly connected, eth1.124, 02:06:55
C * fe80::/64 is directly connected, eth1.123, 02:06:55
C * fe80::/64 is directly connected, eth1.121, 02:06:55
C * fe80::/64 is directly connected, eth1.122, 02:06:55
C * fe80::/64 is directly connected, eth1, 02:06:55
C * fe80::/64 is directly connected, eth1.120, 02:06:56
C&gt;* fe80::/64 is directly connected, lo, 02:06:58
vyos@Pod-120-Router:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-Router (IPv4)</div>
   <div class="collapsible-content">
<pre class="code">vyos@Pod-120-Router:~$ show ip route
Codes: K - kernel route, C - connected, S - static, R - RIP,
       O - OSPF, I - IS-IS, B - BGP, E - EIGRP, N - NHRP,
       T - Table, v - VNC, V - VNC-Direct, A - Babel, F - PBR,
       f - OpenFabric,
       &gt; - selected route, * - FIB route, q - queued, r - rejected, b - backup
       t - trapped, o - offload failure

S&gt;* 0.0.0.0/0 [250/0] via 10.203.0.1, eth0, weight 1, 02:08:46
O&gt;* 10.8.0.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.8.1.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.8.2.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.8.3.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.11.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.14.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.17.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.19.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.20.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.21.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.22.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.23.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.24.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.25.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.31.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.32.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O&gt;* 10.11.111.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
O   10.203.0.0/24 [110/1] is directly connected, eth0, weight 1, 02:08:51
C&gt;* 10.203.0.0/24 is directly connected, eth0, 02:09:02
O&gt;* 10.203.110.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.111.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.112.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.113.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.114.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.115.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.116.0/24 [110/2] via 10.203.0.110, eth0, weight 1, 02:08:34
O&gt;* 10.203.117.0/24 [110/2] via 10.203.0.110, eth0, weight 1, 02:08:34
O&gt;* 10.203.118.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 10.203.119.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
C&gt;* 10.203.120.0/24 is directly connected, eth1.120, 02:09:04
C&gt;* 10.203.121.0/24 is directly connected, eth1.121, 02:09:04
C&gt;* 10.203.122.0/24 is directly connected, eth1.122, 02:09:03
C&gt;* 10.203.123.0/24 is directly connected, eth1.123, 02:09:03
C&gt;* 10.203.124.0/24 is directly connected, eth1.124, 02:09:03
C&gt;* 10.203.125.0/24 is directly connected, eth1.125, 02:09:03
B   10.203.126.0/24 [20/0] via 10.203.126.2 inactive, weight 1, 00:03:46
                           via 10.203.126.3 inactive, weight 1, 00:03:46
                           via 10.203.127.2, eth1.127, weight 1, 00:03:46
                           via 10.203.127.3, eth1.127, weight 1, 00:03:46
O   10.203.126.0/24 [110/1] is directly connected, eth1.126, weight 1, 02:08:51
C&gt;* 10.203.126.0/24 is directly connected, eth1.126, 02:09:03
B   10.203.127.0/24 [20/0] via 10.203.126.2, eth1.126, weight 1, 00:03:46
                           via 10.203.126.3, eth1.126, weight 1, 00:03:46
                           via 10.203.127.2 inactive, weight 1, 00:03:46
                           via 10.203.127.3 inactive, weight 1, 00:03:46
O   10.203.127.0/24 [110/1] is directly connected, eth1.127, weight 1, 02:08:51
C&gt;* 10.203.127.0/24 is directly connected, eth1.127, 02:09:03
C&gt;* 10.203.128.0/24 is directly connected, eth1.128, 02:09:02
C&gt;* 10.203.129.0/24 is directly connected, eth1.129, 02:09:02
O&gt;* 192.168.1.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 192.168.2.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
O&gt;* 192.168.3.0/24 [110/20] via 10.203.0.110, eth0, weight 1, 02:08:33
B&gt;* 192.168.5.0/24 [20/0] via 10.203.126.2, eth1.126, weight 1, 00:03:46
  *                       via 10.203.126.3, eth1.126, weight 1, 00:03:46
  *                       via 10.203.127.2, eth1.127, weight 1, 00:03:46
  *                       via 10.203.127.3, eth1.127, weight 1, 00:03:46
B&gt;* 192.168.6.0/24 [20/0] via 10.203.126.2, eth1.126, weight 1, 00:03:46
  *                       via 10.203.126.3, eth1.126, weight 1, 00:03:46
  *                       via 10.203.127.2, eth1.127, weight 1, 00:03:46
  *                       via 10.203.127.3, eth1.127, weight 1, 00:03:46
B&gt;* 192.168.7.0/24 [20/0] via 10.203.126.2, eth1.126, weight 1, 00:03:46
  *                       via 10.203.126.3, eth1.126, weight 1, 00:03:46
  *                       via 10.203.127.2, eth1.127, weight 1, 00:03:46
  *                       via 10.203.127.3, eth1.127, weight 1, 00:03:46
O&gt;* 192.168.111.0/24 [110/20] via 10.203.0.1, eth0, weight 1, 02:08:33
vyos@Pod-120-Router:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-T0-EdgeVM-01 | DR-T0-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-T0-EdgeVM-01&gt; get logical-router
Wed Aug 31 2022 UTC 21:36:18.561
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000
157da70b-9636-4163-b175-35e8f7535637   3      2      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000

Pod-120-T0-EdgeVM-01&gt; vrf 1
Pod-120-T0-EdgeVM-01(vrf[1])&gt; get forwarding
Wed Aug 31 2022 UTC 21:36:32.331
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          10.203.127.1                              route       8026e680-ed7d-4309-bed3-ce5513000c2b   00:0c:29:e3:79:80
                   10.203.126.1                                          939f4c23-49c5-4bca-be16-41415075316a   00:0c:29:e3:79:80
10.203.126.0/24                                              route       939f4c23-49c5-4bca-be16-41415075316a

10.203.126.2/32                                              route       797e16bb-fcad-5d2b-99aa-652618c4fc95

10.203.126.3/32    169.254.0.131                             route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5   02:50:56:56:52:02
10.203.127.0/24                                              route       8026e680-ed7d-4309-bed3-ce5513000c2b

10.203.127.2/32                                              route       797e16bb-fcad-5d2b-99aa-652618c4fc95

10.203.127.3/32    169.254.0.131                             route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5   02:50:56:56:52:02
100.64.0.0/32                                                route       af741b72-6e71-56b0-b168-d243a06a3a6e

100.64.0.0/31                                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

127.0.0.1/32                                                 route       968b4759-518b-434f-8958-eb06548ec3b0

169.254.0.0/25                                               route       7ac0afcd-108a-4021-a8ce-0a72a9269f1a

169.254.0.1/32                                               route       af741b72-6e71-56b0-b168-d243a06a3a6e

169.254.0.2/32                                               route       797e16bb-fcad-5d2b-99aa-652618c4fc95

169.254.0.128/25                                             route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5

169.254.0.130/32                                             route       797e16bb-fcad-5d2b-99aa-652618c4fc95

192.168.5.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6   02:50:56:56:44:55
192.168.6.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6   02:50:56:56:44:55
192.168.7.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6   02:50:56:56:44:55
IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fe80::20c:29ff:fee3:7980                  route       939f4c23-49c5-4bca-be16-41415075316a
::1/128                                                                                 route       968b4759-518b-434f-8958-eb06548ec3b0
fcb2:6604:2741:3c00::/64                                                                route       38b49f07-a670-53a7-9532-ef2523ee94a6
fcb2:6604:2741:3c00::1/128                                                              route       af741b72-6e71-56b0-b168-d243a06a3a6e
fd00:0:0:7e::/64                                                                        route       939f4c23-49c5-4bca-be16-41415075316a
fd00::7e:250:56ff:fe85:46bb/128                                                         route       797e16bb-fcad-5d2b-99aa-652618c4fc95
fd00:0:0:7e::3/128                            fe80::50:56ff:fe56:5202                   route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5
fd00::7e:250:56ff:fe85:7400/128               fe80::50:56ff:fe56:5202                   route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5
fd00:0:0:7e::2/128                                                                      route       797e16bb-fcad-5d2b-99aa-652618c4fc95
fd00:0:0:7f::/64                                                                        route       8026e680-ed7d-4309-bed3-ce5513000c2b
fd00:0:0:7f::2/128                                                                      route       797e16bb-fcad-5d2b-99aa-652618c4fc95
fd00:0:0:7f::3/128                            fe80::50:56ff:fe56:5202                   route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5
fd00::7f:250:56ff:fe85:ca6/128                fe80::50:56ff:fe56:5202                   route       fbd9c0bd-3d7a-443c-9794-d738aa8b69a5
fd00::7f:250:56ff:fe85:74ef/128                                                         route       797e16bb-fcad-5d2b-99aa-652618c4fc95
fd00:b:a::/64                                 fcb2:6604:2741:3c00::2                    route       38b49f07-a670-53a7-9532-ef2523ee94a6   02:50:56:56:44:55
fd00:b:b::/64                                 fcb2:6604:2741:3c00::2                    route       38b49f07-a670-53a7-9532-ef2523ee94a6   02:50:56:56:44:55
fd00:b:c::/64                                 fcb2:6604:2741:3c00::2                    route       38b49f07-a670-53a7-9532-ef2523ee94a6   02:50:56:56:44:55

Pod-120-T0-EdgeVM-01(vrf[1])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-T0-EdgeVM-02 | DR-T0-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-T0-EdgeVM-02&gt; get logical-router
Wed Aug 31 2022 UTC 21:37:24.788
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000
9ec0f75a-5f89-4551-9462-96de69c6a38f   3      7      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000

Pod-120-T0-EdgeVM-02&gt; vrf 1
Pod-120-T0-EdgeVM-02(vrf[1])&gt; get forwarding
Wed Aug 31 2022 UTC 21:37:35.783
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          10.203.127.1                              route       84a805c2-1f91-4d0a-ba2d-c7f6914359bd   00:0c:29:e3:79:80
                   10.203.126.1                                          de701600-4ebf-4665-bd87-e96de8a0837c   00:0c:29:e3:79:80
10.203.126.0/24                                              route       de701600-4ebf-4665-bd87-e96de8a0837c

10.203.126.2/32    169.254.0.130                             route       2aaca363-d724-4c20-a89e-b8f74798c66a   02:50:56:56:52:01
10.203.126.3/32                                              route       f882f148-e176-51ac-b2a5-2dbe9f5783e6

10.203.127.0/24                                              route       84a805c2-1f91-4d0a-ba2d-c7f6914359bd

10.203.127.2/32    169.254.0.130                             route       2aaca363-d724-4c20-a89e-b8f74798c66a   02:50:56:56:52:01
10.203.127.3/32                                              route       f882f148-e176-51ac-b2a5-2dbe9f5783e6

100.64.0.0/32                                                route       af741b72-6e71-56b0-b168-d243a06a3a6e

100.64.0.0/31                                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

127.0.0.1/32                                                 route       968b4759-518b-434f-8958-eb06548ec3b0

169.254.0.0/25                                               route       d1175ce3-cd04-4a3c-8a6e-ff8f3626e0c8

169.254.0.1/32                                               route       af741b72-6e71-56b0-b168-d243a06a3a6e

169.254.0.3/32                                               route       f882f148-e176-51ac-b2a5-2dbe9f5783e6

169.254.0.128/25                                             route       2aaca363-d724-4c20-a89e-b8f74798c66a

169.254.0.131/32                                             route       f882f148-e176-51ac-b2a5-2dbe9f5783e6

192.168.5.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

192.168.6.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

192.168.7.0/24     100.64.0.1                                route       38b49f07-a670-53a7-9532-ef2523ee94a6

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fe80::20c:29ff:fee3:7980                  route       de701600-4ebf-4665-bd87-e96de8a0837c
::1/128                                                                                 route       968b4759-518b-434f-8958-eb06548ec3b0
fcb2:6604:2741:3c00::/64                                                                route       38b49f07-a670-53a7-9532-ef2523ee94a6
fcb2:6604:2741:3c00::1/128                                                              route       af741b72-6e71-56b0-b168-d243a06a3a6e
fd00:0:0:7e::/64                                                                        route       de701600-4ebf-4665-bd87-e96de8a0837c
fd00:0:0:7e::3/128                                                                      route       f882f148-e176-51ac-b2a5-2dbe9f5783e6
fd00:0:0:7e::2/128                            fe80::50:56ff:fe56:5201                   route       2aaca363-d724-4c20-a89e-b8f74798c66a
fd00::7e:250:56ff:fe85:46bb/128               fe80::50:56ff:fe56:5201                   route       2aaca363-d724-4c20-a89e-b8f74798c66a
fd00::7e:250:56ff:fe85:7400/128                                                         route       f882f148-e176-51ac-b2a5-2dbe9f5783e6
fd00:0:0:7f::/64                                                                        route       84a805c2-1f91-4d0a-ba2d-c7f6914359bd
fd00::7f:250:56ff:fe85:ca6/128                                                          route       f882f148-e176-51ac-b2a5-2dbe9f5783e6
fd00::7f:250:56ff:fe85:74ef/128               fe80::50:56ff:fe56:5201                   route       2aaca363-d724-4c20-a89e-b8f74798c66a
fd00:0:0:7f::2/128                            fe80::50:56ff:fe56:5201                   route       2aaca363-d724-4c20-a89e-b8f74798c66a
fd00:0:0:7f::3/128                                                                      route       f882f148-e176-51ac-b2a5-2dbe9f5783e6
fd00:b:a::/64                                 fcb2:6604:2741:3c00::2                    route       38b49f07-a670-53a7-9532-ef2523ee94a6
fd00:b:b::/64                                 fcb2:6604:2741:3c00::2                    route       38b49f07-a670-53a7-9532-ef2523ee94a6
fd00:b:c::/64                                 fcb2:6604:2741:3c00::2                    route       38b49f07-a670-53a7-9532-ef2523ee94a6

Pod-120-T0-EdgeVM-02(vrf[1])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-T0-EdgeVM-01 | DR-T1-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-T0-EdgeVM-01&gt; get logical-router
Wed Aug 31 2022 UTC 21:39:16.632
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000
157da70b-9636-4163-b175-35e8f7535637   3      2      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000

Pod-120-T0-EdgeVM-01&gt; vrf 2
Pod-120-T0-EdgeVM-01(vrf[2])&gt; get forwarding
Wed Aug 31 2022 UTC 21:39:31.219
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          100.64.0.0                                route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba   02:50:56:56:44:52
100.64.0.0/31                                                route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba

100.64.0.1/32                                                route       e2a59281-05b0-5701-a43f-bf44baf675d0

192.168.5.0/24                                               route       c8cca3a7-5cd8-4071-8963-99d796846834

192.168.5.1/32                                               route       e2a59281-05b0-5701-a43f-bf44baf675d0

192.168.6.0/24                                               route       9dfb3ada-86b4-489d-ae63-bcfcf7eb37e8

192.168.6.1/32                                               route       e2a59281-05b0-5701-a43f-bf44baf675d0

192.168.7.0/24                                               route       b74edb96-54a5-4802-a822-9dad58d872e6

192.168.7.1/32                                               route       e2a59281-05b0-5701-a43f-bf44baf675d0

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fcb2:6604:2741:3c00::1                    route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba   02:50:56:56:44:52
fcb2:6604:2741:3c00::/64                                                                route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba
fcb2:6604:2741:3c00::2/128                                                              route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:a::/64                                                                           route       c8cca3a7-5cd8-4071-8963-99d796846834
fd00:b:a:0:50:56ff:fe56:4452/128                                                        route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:a::1/128                                                                         route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:b::/64                                                                           route       9dfb3ada-86b4-489d-ae63-bcfcf7eb37e8
fd00:b:b::1/128                                                                         route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:b:0:50:56ff:fe56:4452/128                                                        route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:c::/64                                                                           route       b74edb96-54a5-4802-a822-9dad58d872e6
fd00:b:c::1/128                                                                         route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:c:0:50:56ff:fe56:4452/128                                                        route       e2a59281-05b0-5701-a43f-bf44baf675d0

Pod-120-T0-EdgeVM-01(vrf[2])&gt;</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Pod-120-T0-EdgeVM-02 | DR-T1-Gateway-01</div>
   <div class="collapsible-content">
<pre class="code">Pod-120-T0-EdgeVM-02&gt; get logical-router
Wed Aug 31 2022 UTC 21:40:14.160
Logical Router
UUID                                   VRF    LR-ID  Name                              Type                        Ports   Neighbors
736a80e3-23f6-5a2d-81d6-bbefb2786666   0      0                                        TUNNEL                      4
     4/5000
e011df91-bfbc-46d4-8f8a-adbcc2b241d6   1      1      DR-T0-Gateway-01                  DISTRIBUTED_ROUTER_TIER0    5
     2/20000
06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1    7
     2/20000
9ec0f75a-5f89-4551-9462-96de69c6a38f   3      7      SR-T0-Gateway-01                  SERVICE_ROUTER_TIER0        7
     6/20000

Pod-120-T0-EdgeVM-02&gt; vrf 2
Pod-120-T0-EdgeVM-02(vrf[2])&gt; get forwarding
Wed Aug 31 2022 UTC 21:40:24.174
Logical Router
UUID                                   VRF    LR-ID  Name                              Type
06668568-786e-4b5c-8f99-0ff0799c7c9f   2      14     DR-T1-Gateway-01                  DISTRIBUTED_ROUTER_TIER1
IPv4 Forwarding Table
IP Prefix          Gateway IP                                Type        UUID                                   Gateway MAC
0.0.0.0/0          100.64.0.0                                route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba

100.64.0.0/31                                                route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba

100.64.0.1/32                                                route       e2a59281-05b0-5701-a43f-bf44baf675d0

192.168.5.0/24                                               route       c8cca3a7-5cd8-4071-8963-99d796846834

192.168.5.1/32                                               route       e2a59281-05b0-5701-a43f-bf44baf675d0

192.168.6.0/24                                               route       9dfb3ada-86b4-489d-ae63-bcfcf7eb37e8

192.168.6.1/32                                               route       e2a59281-05b0-5701-a43f-bf44baf675d0

192.168.7.0/24                                               route       b74edb96-54a5-4802-a822-9dad58d872e6

192.168.7.1/32                                               route       e2a59281-05b0-5701-a43f-bf44baf675d0

IPv6 Forwarding Table
IP Prefix                                     Gateway IP                                Type        UUID
                     Gateway MAC
::/0                                          fcb2:6604:2741:3c00::1                    route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba
fcb2:6604:2741:3c00::/64                                                                route       9dcf9726-5160-4b17-9d48-d8d0c97da2ba
fcb2:6604:2741:3c00::2/128                                                              route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:a::/64                                                                           route       c8cca3a7-5cd8-4071-8963-99d796846834
fd00:b:a:0:50:56ff:fe56:4452/128                                                        route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:a::1/128                                                                         route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:b::/64                                                                           route       9dfb3ada-86b4-489d-ae63-bcfcf7eb37e8
fd00:b:b::1/128                                                                         route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:b:0:50:56ff:fe56:4452/128                                                        route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:c::/64                                                                           route       b74edb96-54a5-4802-a822-9dad58d872e6
fd00:b:c::1/128                                                                         route       e2a59281-05b0-5701-a43f-bf44baf675d0
fd00:b:c:0:50:56ff:fe56:4452/128                                                        route       e2a59281-05b0-5701-a43f-bf44baf675d0

Pod-120-T0-EdgeVM-02(vrf[2])&gt;</pre></div></div>

<span id="69ad5077-31ce-47c0-b11b-7dbb037471c1"></span>
== WAN ==

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

<span id="6a4103f7-bd9e-46d3-af12-adb0bd13dc61"></span>
=== Verify Routing ===

An output of the routing tables can be found below:

<div class="collapsible">
    <div class="collapsible-alone-header">WAN Gateway (IPv6)</div>
   <div class="collapsible-content">
<pre class="code">ubnt@ubnt:~$ show ipv6 route
IPv6 Routing Table
Codes: K - kernel route, C - connected, S - static, R - RIP, O - OSPF,
       IA - OSPF inter area, E1 - OSPF external type 1,
       E2 - OSPF external type 2, N1 - OSPF NSSA external type 1,
       N2 - OSPF NSSA external type 2, B - BGP
Timers: Uptime

IP Route Table for VRF &quot;default&quot;
C      ::1/128 via ::, lo, 18w1d16h
C      fd00::/64 via ::, eth1.203, 3d08h25m
O E2   fd00::6e:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::6f:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::70:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::71:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::72:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::73:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::74:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::75:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::76:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::77:0:0:0:0/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 11:41:37
O E2   fd00::78:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::79:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::7a:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::7b:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::7c:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::7d:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::7e:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::7f:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::80:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
O E2   fd00::81:0:0:0:0/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 02:07:39
C      fd00::ffff:0:0:0:0/64 via ::, eth1.11, 3d08h25m
O E2   fd00:a:a::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 09:51:08
O E2   fd00:a:b::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 09:51:03
O E2   fd00:a:c::/64 [110/20] via fe80::20c:29ff:fef4:7f13, eth1.203, 09:51:03
O E2   fd00:b:a::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 00:03:04
O E2   fd00:b:b::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 00:03:04
O E2   fd00:b:c::/64 [110/20] via fe80::20c:29ff:fee3:7976, eth1.203, 00:03:04
C      fe80::/64 via ::, vtun5, 1d22h25m
ubnt@ubnt:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">WAN Gateway (IPv4)</div>
   <div class="collapsible-content">
<pre class="code">ubnt@ubnt:~$ show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
       O - OSPF, IA - OSPF inter area
       N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
       E1 - OSPF external type 1, E2 - OSPF external type 2
       &gt; - selected route, * - FIB route, p - stale info

IP Route Table for VRF &quot;default&quot;
S    *&gt; 0.0.0.0/0 [1/0] via 192.168.111.1, eth0
C    *&gt; 0.0.0.0/24 is directly connected, vtun5
C       0.0.0.0/24 is directly connected, vtun7
C       0.0.0.0/24 is directly connected, vtun6
C       0.0.0.0/24 is directly connected, vtun3
C       0.0.0.0/24 is directly connected, vtun4
C       0.0.0.0/24 is directly connected, vtun2
C       0.0.0.0/24 is directly connected, vtun1
C    *&gt; 10.8.0.0/24 is directly connected, vtun6
C       10.8.0.0/24 is directly connected, vtun4
C    *&gt; 10.8.1.0/24 is directly connected, vtun3
C    *&gt; 10.8.2.0/24 is directly connected, vtun5
C    *&gt; 10.8.3.0/24 is directly connected, vtun7
C       10.8.3.0/24 is directly connected, vtun2
C       10.8.3.0/24 is directly connected, vtun1
S    *&gt; 10.10.0.0/16 [1/0] via 10.11.111.100, eth1
C    *&gt; 10.11.11.0/24 is directly connected, eth1.11
C    *&gt; 10.11.14.0/24 is directly connected, eth1.14
C    *&gt; 10.11.17.0/24 is directly connected, eth1.17
C    *&gt; 10.11.19.0/24 is directly connected, eth1.19
C    *&gt; 10.11.20.0/24 is directly connected, eth1.20
C    *&gt; 10.11.21.0/24 is directly connected, eth1.21
C    *&gt; 10.11.22.0/24 is directly connected, eth1.22
C    *&gt; 10.11.23.0/24 is directly connected, eth1.23
C    *&gt; 10.11.24.0/24 is directly connected, eth1.24
C    *&gt; 10.11.25.0/24 is directly connected, eth1.25
C    *&gt; 10.11.31.0/24 is directly connected, eth1.31
C    *&gt; 10.11.32.0/24 is directly connected, eth1.32
C    *&gt; 10.11.111.0/24 is directly connected, eth1
C    *&gt; 10.203.0.0/24 is directly connected, eth1.203
O E2 *&gt; 10.203.110.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.111.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.112.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.113.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.114.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.115.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O IA *&gt; 10.203.116.0/24 [110/2] via 10.203.0.110, eth1.203, 11:41:28
O IA *&gt; 10.203.117.0/24 [110/2] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.118.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.119.0/24 [110/20] via 10.203.0.110, eth1.203, 11:41:28
O E2 *&gt; 10.203.120.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.121.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.122.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.123.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.124.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.125.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O IA *&gt; 10.203.126.0/24 [110/2] via 10.203.0.120, eth1.203, 02:07:52
O IA *&gt; 10.203.127.0/24 [110/2] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.128.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
O E2 *&gt; 10.203.129.0/24 [110/20] via 10.203.0.120, eth1.203, 02:07:52
C    *&gt; 127.0.0.0/8 is directly connected, lo
O E2 *&gt; 192.168.1.0/24 [110/20] via 10.203.0.110, eth1.203, 09:51:34
O E2 *&gt; 192.168.2.0/24 [110/20] via 10.203.0.110, eth1.203, 09:51:29
O E2 *&gt; 192.168.3.0/24 [110/20] via 10.203.0.110, eth1.203, 09:51:29
O E2 *&gt; 192.168.5.0/24 [110/20] via 10.203.0.120, eth1.203, 00:03:30
O E2 *&gt; 192.168.6.0/24 [110/20] via 10.203.0.120, eth1.203, 00:03:30
O E2 *&gt; 192.168.7.0/24 [110/20] via 10.203.0.120, eth1.203, 00:03:30
S    *&gt; 192.168.100.0/24 [1/0] via 10.11.111.100, eth1
C    *&gt; 192.168.111.0/24 is directly connected, eth0
S    *&gt; 192.168.192.0/24 [1/0] via 10.11.111.100, eth1

Gateway of last resort is not set
ubnt@ubnt:~$</pre></div></div>

<span id="ddd5b464-fb56-48a4-a004-34254d0cb812"></span>
= STEP 11{{fqm}} 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.

<span id="65710e08-1795-4c02-8d96-6aab0705dde3"></span>
== Pod 110 ==

<div id="728b91ac-14ce-4f05-9270-93c86d4761ac" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2047.png

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

{| class="wikitable simple-table"
|-
!  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
|}

<span id="0f17b82a-6733-48f7-80fc-eee75ef08524"></span>
== Pod 120 ==

<div id="07535343-e8a3-4d15-9e69-3c83937957cc" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2048.png

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

{| class="wikitable simple-table"
|-
!  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
|}

<span id="230147bd-d261-4531-a8cc-5739c6349afd"></span>
== 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.

<span id="a4fe4719-ce37-4bab-b89f-2ff6a0e6de0b"></span>
=== Pod 110 to Pod 120 IPv6 connectivity ping tests ===

<div class="collapsible">
    <div class="collapsible-alone-header">Ping tests from the Pod 110 Web VM to all Pod 120 VMs</div>
   <div class="collapsible-content">
<pre class="code">tc@TinyVM:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:9E:5F:CE
          inet addr:192.168.1.240  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fd00:a:a:0:250:56ff:fe9e:5fce/64 Scope:Global
          inet6 addr: fd00:a:a::2/64 Scope:Global
          inet6 addr: fe80::250:56ff:fe9e:5fce/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:636 errors:0 dropped:0 overruns:0 frame:0
          TX packets:549 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:57952 (56.5 KiB)  TX bytes:116362 (113.6 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:30 errors:0 dropped:0 overruns:0 frame:0
          TX packets:30 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:19496 (19.0 KiB)  TX bytes:19496 (19.0 KiB)

tc@TinyVM:~$ ping -c 4 fd00:b:a::2
PING fd00:b:a::2 (fd00:b:a::2): 56 data bytes
64 bytes from fd00:b:a::2: seq=0 ttl=58 time=31.348 ms
64 bytes from fd00:b:a::2: seq=1 ttl=58 time=4.846 ms
64 bytes from fd00:b:a::2: seq=2 ttl=58 time=4.887 ms
64 bytes from fd00:b:a::2: seq=3 ttl=58 time=3.872 ms

--- fd00:b:a::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.872/11.238/31.348 ms
tc@TinyVM:~$ ping -c 4 fd00:b:b::2
PING fd00:b:b::2 (fd00:b:b::2): 56 data bytes
64 bytes from fd00:b:b::2: seq=0 ttl=58 time=9.647 ms
64 bytes from fd00:b:b::2: seq=1 ttl=58 time=3.568 ms
64 bytes from fd00:b:b::2: seq=2 ttl=58 time=3.758 ms
64 bytes from fd00:b:b::2: seq=3 ttl=58 time=3.196 ms

--- fd00:b:b::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.196/5.042/9.647 ms
tc@TinyVM:~$ ping -c 4 fd00:b:c::2
PING fd00:b:c::2 (fd00:b:c::2): 56 data bytes
64 bytes from fd00:b:c::2: seq=0 ttl=58 time=9.784 ms
64 bytes from fd00:b:c::2: seq=1 ttl=58 time=2.878 ms
64 bytes from fd00:b:c::2: seq=2 ttl=58 time=3.095 ms
64 bytes from fd00:b:c::2: seq=3 ttl=58 time=5.012 ms

--- fd00:b:c::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.878/5.192/9.784 ms
tc@TinyVM:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Ping tests from the Pod 110 App VM to all Pod 120 VMs</div>
   <div class="collapsible-content">
<pre class="code">tc@TinyVM:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:9E:31:18
          inet addr:192.168.2.240  Bcast:192.168.2.255  Mask:255.255.255.0
          inet6 addr: fd00:a:b::2/64 Scope:Global
          inet6 addr: fe80::250:56ff:fe9e:3118/64 Scope:Link
          inet6 addr: fd00:a:b:0:250:56ff:fe9e:3118/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:136 errors:0 dropped:0 overruns:0 frame:0
          TX packets:129 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16441 (16.0 KiB)  TX bytes:47577 (46.4 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12928 (12.6 KiB)  TX bytes:12928 (12.6 KiB)

tc@TinyVM:~$ ping -c 4 fd00:b:a::2
PING fd00:b:a::2 (fd00:b:a::2): 56 data bytes
64 bytes from fd00:b:a::2: seq=0 ttl=58 time=16.372 ms
64 bytes from fd00:b:a::2: seq=1 ttl=58 time=4.004 ms
64 bytes from fd00:b:a::2: seq=2 ttl=58 time=4.863 ms
64 bytes from fd00:b:a::2: seq=3 ttl=58 time=4.738 ms

--- fd00:b:a::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 4.004/7.494/16.372 ms
tc@TinyVM:~$ ping -c 4 fd00:b:b::2
PING fd00:b:b::2 (fd00:b:b::2): 56 data bytes
64 bytes from fd00:b:b::2: seq=0 ttl=58 time=14.835 ms
64 bytes from fd00:b:b::2: seq=1 ttl=58 time=5.930 ms
64 bytes from fd00:b:b::2: seq=2 ttl=58 time=4.026 ms
64 bytes from fd00:b:b::2: seq=3 ttl=58 time=3.303 ms

--- fd00:b:b::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.303/7.023/14.835 ms
tc@TinyVM:~$ ping -c 4 fd00:b:c::2
PING fd00:b:c::2 (fd00:b:c::2): 56 data bytes
64 bytes from fd00:b:c::2: seq=0 ttl=58 time=3.017 ms
64 bytes from fd00:b:c::2: seq=1 ttl=58 time=3.283 ms
64 bytes from fd00:b:c::2: seq=2 ttl=58 time=3.823 ms
64 bytes from fd00:b:c::2: seq=3 ttl=58 time=5.541 ms

--- fd00:b:c::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.017/3.916/5.541 ms
tc@TinyVM:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Ping tests from the Pod 110 DB VM to all Pod 120 VMs</div>
   <div class="collapsible-content">
<pre class="code">tc@TinyVM:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:9E:AC:7D
          inet addr:192.168.3.240  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fd00:a:c::2/64 Scope:Global
          inet6 addr: fe80::250:56ff:fe9e:ac7d/64 Scope:Link
          inet6 addr: fd00:a:c:0:250:56ff:fe9e:ac7d/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:137 errors:0 dropped:0 overruns:0 frame:0
          TX packets:119 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16152 (15.7 KiB)  TX bytes:41590 (40.6 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6464 (6.3 KiB)  TX bytes:6464 (6.3 KiB)

tc@TinyVM:~$ ping -c 4 fd00:b:a::2
PING fd00:b:a::2 (fd00:b:a::2): 56 data bytes
64 bytes from fd00:b:a::2: seq=0 ttl=58 time=13.181 ms
64 bytes from fd00:b:a::2: seq=1 ttl=58 time=5.612 ms
64 bytes from fd00:b:a::2: seq=2 ttl=58 time=4.381 ms
64 bytes from fd00:b:a::2: seq=3 ttl=58 time=3.248 ms

--- fd00:b:a::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.248/6.605/13.181 ms
tc@TinyVM:~$ ping -c 4 fd00:b:b::2
PING fd00:b:b::2 (fd00:b:b::2): 56 data bytes
64 bytes from fd00:b:b::2: seq=0 ttl=58 time=16.429 ms
64 bytes from fd00:b:b::2: seq=1 ttl=58 time=3.889 ms
64 bytes from fd00:b:b::2: seq=2 ttl=58 time=4.668 ms
64 bytes from fd00:b:b::2: seq=3 ttl=58 time=3.704 ms

--- fd00:b:b::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.704/7.172/16.429 ms
tc@TinyVM:~$ ping -c 4 fd00:b:c::2
PING fd00:b:c::2 (fd00:b:c::2): 56 data bytes
64 bytes from fd00:b:c::2: seq=0 ttl=58 time=5.868 ms
64 bytes from fd00:b:c::2: seq=1 ttl=58 time=3.302 ms
64 bytes from fd00:b:c::2: seq=2 ttl=58 time=4.182 ms
64 bytes from fd00:b:c::2: seq=3 ttl=58 time=3.468 ms

--- fd00:b:c::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.302/4.205/5.868 ms
tc@TinyVM:~$</pre></div></div>

<span id="c11fe814-0a41-4fc9-9d14-b6c33acdcf6f"></span>
=== Pod 120 to Pod 110 IPv6 connectivity ping tests ===

<div class="collapsible">
    <div class="collapsible-alone-header">Ping tests from the Pod 120 Web VM to all Pod 110 VMs</div>
   <div class="collapsible-content">
<pre class="code">tc@TinyVM:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:85:66:7D
          inet addr:192.168.5.240  Bcast:192.168.5.255  Mask:255.255.255.0
          inet6 addr: fd00:b:a::2/64 Scope:Global
          inet6 addr: fe80::250:56ff:fe85:667d/64 Scope:Link
          inet6 addr: fd00:b:a:0:250:56ff:fe85:667d/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:206 errors:0 dropped:0 overruns:0 frame:0
          TX packets:159 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:21572 (21.0 KiB)  TX bytes:46940 (45.8 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:10 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6464 (6.3 KiB)  TX bytes:6464 (6.3 KiB)

tc@TinyVM:~$ ping -c 4 fd00:a:a::2
PING fd00:a:a::2 (fd00:a:a::2): 56 data bytes
64 bytes from fd00:a:a::2: seq=0 ttl=58 time=3.856 ms
64 bytes from fd00:a:a::2: seq=1 ttl=58 time=3.572 ms
64 bytes from fd00:a:a::2: seq=2 ttl=58 time=3.405 ms
64 bytes from fd00:a:a::2: seq=3 ttl=58 time=3.204 ms

--- fd00:a:a::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.204/3.509/3.856 ms
tc@TinyVM:~$ ping -c 4 fd00:a:b::2
PING fd00:a:b::2 (fd00:a:b::2): 56 data bytes
64 bytes from fd00:a:b::2: seq=0 ttl=58 time=23.314 ms
64 bytes from fd00:a:b::2: seq=1 ttl=58 time=6.001 ms
64 bytes from fd00:a:b::2: seq=2 ttl=58 time=4.059 ms
64 bytes from fd00:a:b::2: seq=3 ttl=58 time=5.081 ms

--- fd00:a:b::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 4.059/9.613/23.314 ms
tc@TinyVM:~$ ping -c 4 fd00:a:c::2
PING fd00:a:c::2 (fd00:a:c::2): 56 data bytes
64 bytes from fd00:a:c::2: seq=0 ttl=58 time=10.396 ms
64 bytes from fd00:a:c::2: seq=1 ttl=58 time=2.275 ms
64 bytes from fd00:a:c::2: seq=2 ttl=58 time=3.289 ms
64 bytes from fd00:a:c::2: seq=3 ttl=58 time=3.030 ms

--- fd00:a:c::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.275/4.747/10.396 ms
tc@TinyVM:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Ping tests from the Pod 120 App VM to all Pod 110 VMs</div>
   <div class="collapsible-content">
<pre class="code">tc@TinyVM:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:85:40:F8
          inet addr:192.168.6.240  Bcast:192.168.6.255  Mask:255.255.255.0
          inet6 addr: fd00:b:b:0:250:56ff:fe85:40f8/64 Scope:Global
          inet6 addr: fd00:b:b::2/64 Scope:Global
          inet6 addr: fe80::250:56ff:fe85:40f8/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:170 errors:0 dropped:0 overruns:0 frame:0
          TX packets:145 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20497 (20.0 KiB)  TX bytes:70044 (68.4 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:20 errors:0 dropped:0 overruns:0 frame:0
          TX packets:20 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13000 (12.6 KiB)  TX bytes:13000 (12.6 KiB)

tc@TinyVM:~$ ping -c 4 fd00:a:a::2
PING fd00:a:a::2 (fd00:a:a::2): 56 data bytes
64 bytes from fd00:a:a::2: seq=0 ttl=58 time=10.618 ms
64 bytes from fd00:a:a::2: seq=1 ttl=58 time=4.168 ms
64 bytes from fd00:a:a::2: seq=2 ttl=58 time=3.763 ms
64 bytes from fd00:a:a::2: seq=3 ttl=58 time=3.500 ms

--- fd00:a:a::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.500/5.512/10.618 ms
tc@TinyVM:~$ ping -c 4 fd00:a:b::2
PING fd00:a:b::2 (fd00:a:b::2): 56 data bytes
64 bytes from fd00:a:b::2: seq=0 ttl=58 time=7.505 ms
64 bytes from fd00:a:b::2: seq=1 ttl=58 time=3.095 ms
64 bytes from fd00:a:b::2: seq=2 ttl=58 time=3.237 ms
64 bytes from fd00:a:b::2: seq=3 ttl=58 time=3.434 ms

--- fd00:a:b::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.095/4.317/7.505 ms
tc@TinyVM:~$ ping -c 4 fd00:a:c::2
PING fd00:a:c::2 (fd00:a:c::2): 56 data bytes
64 bytes from fd00:a:c::2: seq=0 ttl=58 time=11.369 ms
64 bytes from fd00:a:c::2: seq=1 ttl=58 time=2.987 ms
64 bytes from fd00:a:c::2: seq=2 ttl=58 time=10.894 ms
64 bytes from fd00:a:c::2: seq=3 ttl=58 time=4.446 ms

--- fd00:a:c::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.987/7.424/11.369 ms
tc@TinyVM:~$</pre></div></div>

<div class="collapsible">
    <div class="collapsible-alone-header">Ping tests from the Pod 120 DB VM to all Pod 110 VMs</div>
   <div class="collapsible-content">
<pre class="code">tc@TinyVM:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:50:56:85:78:4B
          inet addr:192.168.7.240  Bcast:192.168.7.255  Mask:255.255.255.0
          inet6 addr: fd00:b:c::2/64 Scope:Global
          inet6 addr: fd00:b:c:0:250:56ff:fe85:784b/64 Scope:Global
          inet6 addr: fe80::250:56ff:fe85:784b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:178 errors:0 dropped:0 overruns:0 frame:0
          TX packets:166 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20023 (19.5 KiB)  TX bytes:51135 (49.9 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:34 errors:0 dropped:0 overruns:0 frame:0
          TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13731 (13.4 KiB)  TX bytes:13731 (13.4 KiB)

tc@TinyVM:~$ ping -c 4 fd00:a:a::2
PING fd00:a:a::2 (fd00:a:a::2): 56 data bytes
64 bytes from fd00:a:a::2: seq=0 ttl=58 time=3.223 ms
64 bytes from fd00:a:a::2: seq=1 ttl=58 time=3.522 ms
64 bytes from fd00:a:a::2: seq=2 ttl=58 time=3.361 ms
64 bytes from fd00:a:a::2: seq=3 ttl=58 time=3.831 ms

--- fd00:a:a::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 3.223/3.484/3.831 ms
tc@TinyVM:~$ ping -c 4 fd00:a:b::2
PING fd00:a:b::2 (fd00:a:b::2): 56 data bytes
64 bytes from fd00:a:b::2: seq=0 ttl=58 time=10.482 ms
64 bytes from fd00:a:b::2: seq=1 ttl=58 time=2.637 ms
64 bytes from fd00:a:b::2: seq=2 ttl=58 time=2.015 ms
64 bytes from fd00:a:b::2: seq=3 ttl=58 time=4.101 ms

--- fd00:a:b::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.015/4.808/10.482 ms
tc@TinyVM:~$ ping -c 4 fd00:a:c::2
PING fd00:a:c::2 (fd00:a:c::2): 56 data bytes
64 bytes from fd00:a:c::2: seq=0 ttl=58 time=8.601 ms
64 bytes from fd00:a:c::2: seq=1 ttl=58 time=2.742 ms
64 bytes from fd00:a:c::2: seq=2 ttl=58 time=2.583 ms
64 bytes from fd00:a:c::2: seq=3 ttl=58 time=2.850 ms

--- fd00:a:c::2 ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 2.583/4.194/8.601 ms
tc@TinyVM:~$</pre></div></div>

<span id="0d82a75d-70b2-4685-b419-349f9e14006f"></span>
== Testing connectivity 2 〈Traceflow〉 ==

As an extra test I also did some traceflow tests,

<div id="8aa6b41c-0bcb-4942-b0ab-3ebae6e8a8f1" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2049.png

</div>
<span id="05c7bd7b-f677-4a5e-8d4b-6c8c35ee07de"></span>
=== Pod 110 Web to Pod 120 Web IPv6 traceflow test ===

<div id="4f468bc8-bcc1-400c-8b95-e3caea0a858d" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2050.png

</div>
The packets are successfully delivered.

<div id="22bbd60d-34a0-4314-8f24-d140eb1c3231" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2051.png

</div>
<span id="e1d77b83-8980-4ed8-8387-99095289630c"></span>
=== 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.

<div id="a4e93eec-7018-4c2b-be87-3bb4ee0f6377" class="figure image">

https://www.iwanhoogendoorn.nl/images/thumb/blog/15/Untitled%2052.png

</div>

</div>
<span class="sans" style="font-size:14px;padding-top:2em"></span>

[[Category:NSX]]
[[Category:Networking]]
[[Category:VMware]]
[[Category:NSX Academy]]