VPC Traffic Flows
In order to understand the traffic flow, for data to flow, following steps are Nexus follows:
- ARP Request
- ARP Reply
- Data Traffic between Source & Destination
We will use the following topology to send the traffic from Server A to Sever B
- Let’s suppose Server With MAC A ( 10.10.10.2 ) want to talk to Server with MAC B ( 10.10.10.3) and Host A will search for Host B MAC address ins it ARP table and will be a MISS.
- Now Host A will Send ARP Request with following header details:
- DMAC : FFFFF
- SMAC : MAC A
- SIP: 10.10.10.2
- DIP: 10.10.10.3
- Now when this ARP request will hit to S3 on Eth1/5, Source MAC A will be learned on this interface on its MAC table.
- Now as this is ARP, HASH algo will be used between DMAC FFFF and SMAC MAC A, and will find one link from Port-channel vPC 10 and let suppose it will select the port E1/1 and ARP will traverse on it.
- ARP request will hit to Eth1/1 of S1 and puts its entry on MAC table and because of CFS running the Same SMAC MAC A will also be learned on Eth1/2 or port-channel interface on S2.
- The ARP request will be forwarded to Eth1/2 and Po100 peer-link on S1.
- Switch S2 and S4 will receive this broadcast and update its MAC table with its respective receiving port-channel interface also S4 will forward the ARP request to any of vPC member port due to Loop avoidance. Likewise S4 will also not forward this ARP request in vPC 20 but will forward this packet to Eth1/4 where destination Host B resides.