Hi @phuochoang !
The 5940 series supports EVPN implementation that uses MP-BGP in the control-plane and VXLAN in the data plane. Those services you refer to look to me as part of EVPN over MPLS implementation. Which is not supported by 5940.
If you believe that those service models are valid for the EVPN over VXLAN too, please, refer me to RFCs that describe the details and differences between those models and I'll try to check it in the documentation available to me.
Thank you!
Ok, I have research a little bit, read several 3rd-party docs and seems that the difference between those models is in the way how we map VLAN/-s to a VSI.
If we stick with EVPN over VXLAN, we can say 5940 supports VLAN-based, VLAN-bundle and Port-based services:
- VLAN-based is when on AC you map single VLAN with "service-instance <instance-id> ; encapsulation s-vid <vlan_id>" command to VSI.
- VLAN-bundle is when on AC you map multiple VLANs with "service-instance <instance-id> ; encapsulation s-vid <vlan_id_list>" command to VSI. All VLANs bound to the VSI share single MAC-address table.
- Port-based is when on AC you map ALL traffic to VSI with "service-instance <instance-id> ; encapsulation default" command. An Ethernet service instance that uses the encapsulation default match criterion matches any frames if it is the only instance on the interface.
VLAN-aware service is not supported, at lease I couldn't find any mention for such mode in our docs. Those modes require VSI to keep VLAN IDs together with MAC-addresses, which means to keep separate MAC tables for each VLAN inside one VSI. And I couldn't find the way to achieve this.
Keep in mind that one VSI can be associated with only single VXLAN ID and one VXLAN ID can have only one VSI attached, so there is one-to-one relation between them. And VXLAN Tunnel can traverse multiple VXLANs.
Hope this helps!
Hi @phuochoang !
Was your question aswered? If it was, could you mark my answer as accepted solution?
Thanks!