Hi Community
We are in the process of configuring VXLAN's between three DC's.
All three DC's utilizes S8 core switches (S180 Blades)
Essentially allowing L2 vlans across the l3 underlay.
The VXlan tunnels is all working as expected, using OSPF VXLAN extensions to dynamically advertise the VXLAN info.
The question I have is around best practice for the tbp.0.* mappings.
Currently I have the following configured on all the Cores:
On the Router side:
interface tun.0.1
tunnel mode vxlan l2 tbp.0.1
tunnel source 1.1.1.1
no shutdown
exit
on the Switch Side:
set tunnel logical-switch create name TEST1
set tunnel map logical-switch TEST1 keyword 200 vlan 200
set tunnel logical-switch create name TEST
set tunnel map logical-switch TEST keyword 100 vlan 100
set vlan egress 100 tbp.0.1 tagged
set vlan egress 100 ge.8.48 untagged
set vlan egress 200 tbp.0.1 tagged
set vlan egress 200 ge.8.46 untagged
Vlan 100 and Vlan 200 is extended between all three DC's and is working as expected.
However I am still using the same Source Tbp.0.1 and just mapping more and more vlans to the same port.
Should we not use a separate Tbp for each vlan. for example:
interface tun.0.1
tunnel mode vxlan l2 tbp.0.1
tunnel source 1.1.1.1
no shutdown
exit
interface tun.0.2
tunnel mode vxlan l2 tbp.0.2
tunnel source 1.1.1.1
no shutdown
exit
set tunnel logical-switch create name TEST1
set tunnel map logical-switch TEST1 keyword 200 vlan 200
set tunnel logical-switch create name TEST
set tunnel map logical-switch TEST keyword 100 vlan 100
set vlan egress 100 tbp.0.1 tagged
set vlan egress 100 ge.8.48 untagged
set vlan egress 200 tbp.0.2 tagged
set vlan egress 200 ge.8.46 untagged
(Using different TBP ports I will enable the split horizon)
What is best practice, one Tbp for the vxlan tunnel and map multiple vlans to the same Tbp or
a seperate Tbp for each vlan with split horizon enable?
Regards
