ā01-30-2025 06:25 AM - edited ā01-30-2025 08:18 AM
Hello colleagues! Have a question that I couldn't sort by myself. There is a WS-C3650-48TS with IOS-XE 16.12.08 , and I would like to know if it supports VXLAN\EVPN ? Wanted to connect it as a leaf switch for migration process temporary. I see that there are all VXLAN\EVPN commands in the OS , except that it doesn't support both L2 and L3 vni on the same NVE interface, but ok. I could configure the BGP\EVPN afi , and got control plane working , I can see all routes type2 and 5, but the data plane doesn't work and I can't ping other C9k leafs from a Looopback interface in a VRF, it should be over the L3VNI. I started googling and there is no official doc about the c3650 models that proves if it supports or not VXLAN , some docs say that it supports in SDA mode only, some say that it works partially , so absolutely unclear. So can someone from the vendor share an official claim about this ? And another one: I wanted to captire the VXLAN traffic for checking if it even sends from interfaces, but in the pcap file I don't see any UDP at all , even from the C9k, looks strange. Does enyone know how to capture VXLAN from a catalyst ?
Thanks!
Solved! Go to Solution.
ā01-30-2025 07:48 AM
@mikhailov.ivan The Cisco Catalyst 3650 with IOS-XE 16.12.08 does not officially support VXLAN/EVPN as a fully functional leaf switch in a VXLAN/EVPN fabric. While the CLI may show some VXLAN/EVPN commands, the 3650 is primarily designed for SDA mode, where VXLAN is limited to specific use cases and lacks comprehensive functionality, such as full L2 and L3 VNI support on the same NVE interface. The issues youāre facing with the data plane and the inability to ping through L3VNI confirm that the hardware and software lack full VXLAN/EVPN capabilities.
As for capturing VXLAN traffic, Catalyst switches like the 3650 and even the 9Ks might not show encapsulated VXLAN traffic easily via standard packet capture methods due to hardware offloading. You may need to use an external device for inline captures or specific hardware tools designed for deep inspection of VXLAN encapsulated packets. For official confirmation, I recommend contacting Cisco TAC or referring to the Catalyst 3650 product documentation.
ā01-30-2025 07:39 AM
Based on datasheet, It does not support. Considering that datasheet shows what the device support only. We Will not find any mention to what It does not.
Indeed this device can be onboard on DNAC from version 16.12.x and as fabric node It must support vxlan.
If you can open a TAC I believe that would be the right place. The documentation is really not helping about this.
ā01-30-2025 07:48 AM
@mikhailov.ivan The Cisco Catalyst 3650 with IOS-XE 16.12.08 does not officially support VXLAN/EVPN as a fully functional leaf switch in a VXLAN/EVPN fabric. While the CLI may show some VXLAN/EVPN commands, the 3650 is primarily designed for SDA mode, where VXLAN is limited to specific use cases and lacks comprehensive functionality, such as full L2 and L3 VNI support on the same NVE interface. The issues youāre facing with the data plane and the inability to ping through L3VNI confirm that the hardware and software lack full VXLAN/EVPN capabilities.
As for capturing VXLAN traffic, Catalyst switches like the 3650 and even the 9Ks might not show encapsulated VXLAN traffic easily via standard packet capture methods due to hardware offloading. You may need to use an external device for inline captures or specific hardware tools designed for deep inspection of VXLAN encapsulated packets. For official confirmation, I recommend contacting Cisco TAC or referring to the Catalyst 3650 product documentation.
ā01-30-2025 08:00 AM
Thanks mates! I suppose that for now we can use these claims as a proof that it doesn't support vxlan. GPT said the same
Thanks, I hope this tred will be cashed in search engines for a future.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide