Hello colleagues one more time! I would like to discuss or clarify several questions regarding SD-Access over SD-WAN multi site design or sdwan transit as they call it.
The problem is there are little information in details about this integration , only one doc which I found is this https://www.cisco.com/c/dam/en/us/td/docs/solutions/CVD/Campus/Cisco-SD-Access-SD-WAN-Integrated-Domain-Guide.pdf
We will need the pic on the page 14 and the list of limitation on the top of the page 28.
They say:
The following features are not supported on the colocated SD-Access | IOS-XE WAN Edge device:
o Multicast
o IPv6
o Layer 2 Flooding
o Layer 2 Border Handoff
o SD-Access Transit
o MultiSite Remote Border
But they don't explain each line why. So could anyone describe each line like why it isn't supported?
I am mostly worry about the L2 flooding across sites. Lets imagine particular case: we have 3 or 4 SD-access sites on different continents and they are connected by SD-Wan. An employee(who definitely knows that we have a best network because we've spent a lot of $) asked as to arrange L2 channel(or virtual switch) from one site , let it be any C9300 port , to 2 others sites 9300 as well. Let's imagine that we have an industrial machine connected to 9300 on one site and continent and 2 PLC engineers on other sites and continents who desire to have a L2 connection to the machine together at the same time for some specific configuring. And correct me if I am wrong, it's impossible in this case, right? But it's possible if i take a legacy device and any L2 over L3 protocol like L2tpv3 or EoIP(even if it's p2p only) etc. So the question is: is it really unsupported due to MTU vXlan size and because of vxlan packets can't be fragmented and fragmented will be dropped on vteps? And if so how to solve this problem without workarounds? So, my the main concern is - if we use Cisco SD-Wan as transit technology (it's logical I think because public channels are cheaper obviously) between sd-access sites, which limitations will we have and why, line by line please. In my opinion and again correct me if I am wrong , they didn't do enough for products integration, you still need to do manual config for vManage, DNAc, APIC separately and have dashboard for each separately despite that all appliances (NX-OS, Cat9k, Cat8k) are based on OSs which support almost the same features and approaches and I can't understand any tech reasons why they can't merge all products in a single solution...just philosophic, sorry.
Thanks!
