vPC and vPC+ at edge, understanding the differences
With Cisco FabricPath's introduction vPC+ was also introduced.
lets see how different vPC+ is and how vPC+ overcomes some problems that vPC has in a fabricpath environment.
Below is a diagram where standard vPC is configured in a fabricpath environment.
Server A with MAC (aaa.aaa.aaa) is connected to nexus 5k-1 and 5k-2 in a vPC.
so lets take it step wise:
- Server A sends traffic to Server B
- Server A can use either of the links in vPC depending on the hashing
- lets say Server A takes outgoing path via 5k-1 (using switch ID of 5k-1)
- 5k-1 sends traffic to 7k-4 via fabricpath
- 7k-4 sends traffic to 5k-3 and finally Server B receives the frame as classical ethernet
now the problem arises in the reverse path
5k-3 has to send traffic back to Server A , so MAC(aaa.aaa.aaa) is behind which Switch ID. 5k-1 or 5k-2 ??? so it send back to 5k-1 and we do not achieve multipathing
This problem is resolved by using vPC+
Below is an example of vPC+ with Fabric path domain
So lets take it step wise:
- Server A sends traffic to Server B with source MAC(aaa.aaa.aaa)
- Server A uses either links in vPC+ depending on hashing
- say 5k-1 receives the frame , it encapsulates the frame in cisco Fabric path header with source switch-id 12(emulated switch ID)
- 5k-1 forwards the frame to 5k-3 via 7k-4 (basically the best fabric path SPT)
- 5k-3 forwards the frame as classical Ethernet to the host server B
So now in reverse path the frame from 5k-3 will be sent to emulated switch ID-12 which is physically either 5k-1 or 5k-2 , thus achieving true Multipathing
So now lets talk about the benefits of using vPC+ at edge
Functions that are enabled by vPC+ at the edge include:
No comments:
Post a Comment