Enable VXLAN Routing on Cumulus Tomahawk
Overview
Cumulus devices equipped with Tomahawk and Tomahawk+ ASICs do not natively support Routing In and Out of Tunnels (RIOT). Therefore, switch ports for VXLAN routing must be configured to use hyperloop interfaces. Hyperloop interfaces recirculate packets through the ingress pipeline. As packets enter the VXLAN tunnel they are encapsulated, as they exit the VXLAN tunnel they are decapsulated.
To set up the hyperloop interface, you'll create a device profile, make sure your logical device has an unused port (as applicable), create an interface map, update your managed devices, assign the new device profile to the device, and deploy the device.
Create Device Profile for Hyperloop
Update Logical Device for Hyperloop
If you have a logical device that includes the hyperloop port, make sure the port is configured for an Unused role.
Create Interface Map for Hyperloop
Create an interface map using the new device profile.
Update Managed Devices for Hyperloop
- Navigate to the managed device that will use hyperloop.
- Click the Edit button (top-right) and select the new hyperloop device profile from the drop-down list.
- Click Update to save your changes.
Assign Hyperloop Device Profile
In the blueprint, assign the new device profile to the appropriate device, then deploy it.
Verify Loopback Port
After deploying the device, verify that the hyperloop port is set to "loopback" by
looking at the device file /etc/cumulus/ports.conf
.
admin@border-1-leaf:mgmt-vrf:~$ sudo cat /etc/cumulus/ports.conf sudo: unable to resolve host border-1-leaf 1=100G 2=100G 3=100G 4=100G 5=100G 6=100G 7=100G 8=100G 9=100G 10=100G 11=100G 12=100G 13=100G 14=100G 15=100G 16=100G 17=100G 18=100G 19=100G 20=100G 21=100G 22=100G 23=100G 24=100G 25=100G 26=100G 27=100G 28=100G 29=100G 30=100G 31=100G 32=loopback admin@border-1-leaf:mgmt-vrf:~$