Quantcast
Channel: Ethernet Switching topics
Viewing all articles
Browse latest Browse all 2326

QFX5100 VXLAN Multi-Tenant Compute Nodes

$
0
0

Greetings Members:

 

I am trying to figure out how to implement the below (what I thought would be simple) topology.

I've been reading a ton of documentation and examples on the Internet but can't seem to find any examples that cover my desired implementation, or I am really not understanding VXLAN (which is most likely the case). The majority of what I am finding is DCI implementations or are not definitive enough for me see that it would cover my current design.  I will eventually get to the DCI setup, but just not yet.

 

Networking Hardware:

Juniper MX80 Routers (x2), Juniper QFX5100-48T Switches (x2) 

 

Hypervisor Environment:

Ubuntu 18.04 Compute Node w/Libvirt-QEMU 

Open vSwitch 

 

Goal:

Customer VMs on private vSwitches need to communicate to multiple compute-nodes within the network.

The customer can have 10 VMs spread across 10 compute nodes, and the L2 network needs accessible between all VMs.

 

Example: 

Customer 12345 VM#1 (172.16.10.2/24) on Compute Node #1 needs to be able to talk to VM#2 (172.16.10.3/24) on Compute Node #2.  These compute nodes are all within the same Data Center / Location.

 

Eventually, this will need to be extended to support multi-data center (DCI) interconnection of the customer VXLANs.

 

qfx5100_vxlan_kvm-host.png

 

 

Here is where I'm having an understanding issue -- On Open vSwitch (OVS), I can make two compute nodes share VXLAN communication if I directly peer the OVS configuration to each other.  Unfortuantely, this is not scaleable and I need to have a VTEP gateway (I assume the QFX5100) to "centralize" the connectivity points.

 

Example OVS Configuration:

node01# ovs-vsctl add-port 12345 vxlan_12345 --  \
   set interface vxlan_12345 type=vxlan options:remote_ip={{node02-ipv4}} options:key=12345

node02# ovs-vsctl add-port 12345 vxlan_12345 --  \
   set interface vxlan_12345 type=vxlan options:remote_ip={{node01-ipv4}} options:key=12345

This allows my two VMs to directly communication, but again, not scalable if I had 100 compute nodes (configurations will become a HUGE mesh nightmare).

 

In my simplistic thought, the "remote_ip" would be the QFX5100 switching fabric setup as a VTEP L2 Gateway ... but how do you configure the QFX5100 to BE this VTEP gateway?

 

Any help or directions / links to documentation and examples would be greatly appreciated!

 


Viewing all articles
Browse latest Browse all 2326

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>