Part 3 Cisco SDA: Client communication between two different SDA fabric

Cisco SDA: Client communication between two different SDA fabric

We are came up with our third part where now we are talking about the traffic flow between the hosts ( Client 1 and Client 2) residing in two different SDA fabric and we have an IP transit network between them.

IP Transit network will be the traditional IP network or SDWAN infrastructure fabric used. We are not going to discuss on the traffic flow on Transit network or SDWAN but will discuss purely on the traffic flow in the SDA fabric.

Fig 1.1-Client communication between two different SDA fabric

Step 1: Client 1 initiates traffic to Client 2

Step 2: Edge node 1 send map request to Control node for Client 2 VTEP address

Step 3: Map-reply from Control node to send the traffic border node

Step 4: Now Edge node 1 sends the traffic to Border node (BN1) and Border edge node checks and knows this not available in the local fabric anywhere, so send query to Transit Control Node(CN) about the destination IP address

Step5: Transit Control Node (TCN) checks for the destination prefix's and respond back with the VTEP IP of the border node of the destination site.

Step 6: Local Border node (BN1) tunnels packet across transit network to destination side Border node (BN4).

Step 7: Remote Border node (BN4) check with remote control node for the VTEP IP of the destination Client 2 and forwards the traffic to specified remote end Edge node (EN4), from where the packet is de-encapsulates, removing the VXLAN tunnel header and forward to client 2.

ARP flow in Cisco SD-Access
Part 2 Cisco SD-Access: ARP Enhanced Forwarding
DHCP process works in Cisco SD-Access