04-13-2016 04:06 PM - edited 03-01-2019 08:14 AM
Hi guys,
What's the difference between VPC fabricpath switch-id and fabricpath switch-id and how to configure each of them? I know of one command to configure the switch-id #fabricpath switch-id <value>
Thanks
Solved! Go to Solution.
04-18-2016 07:55 AM
Fabricpath Switch-id ==> To configure the switch with the number to identify in the fabricpath domain.
VPC fabricpath Switch-id:- I believe you are taking about VPC+.
The vPC+ feature was introduced to allow interoperability between FabricPath and vPCs. The functionality and behavior of a vPC+ and a vPC is identical. The same rules apply in both technologies. That is, both require peer link and peer keepalive messages, the configurations must match between the vPC peers, and consistency checks still take place. In a vPC+ domain, a unique FabricPath switch ID is configured and the peer link is configured as a FabricPath core port. This FabricPath switch ID under the vPC+ domain is called the Emulated switch ID. The Emulated switch ID must be the same between the two peers and must be unique per vPC+.
The benefits of using a vPC+ at the edge of a domain are as follows:
•Allows you to attach servers to the device using Link Aggregation Control Protocol (LACP) uplinks
•Allows you to attach other CE devices in vPC mode
•Allows you to attach Cisco Nexus 2000 Fabric Extenders in Active/Active mode
•Prevents orphan ports in a failure scenario. When a peer link fails in the vPC+ domain, the orphan port still has FabricPath uplinks for communication.
•Provides numerous paths
Please go through the below link which gives you complete information:-
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_ops_fabricpath.html#wp1053135
HTH
Regards
Inayath
**(*Please rate the post if helpful***)
04-18-2016 07:55 AM
Fabricpath Switch-id ==> To configure the switch with the number to identify in the fabricpath domain.
VPC fabricpath Switch-id:- I believe you are taking about VPC+.
The vPC+ feature was introduced to allow interoperability between FabricPath and vPCs. The functionality and behavior of a vPC+ and a vPC is identical. The same rules apply in both technologies. That is, both require peer link and peer keepalive messages, the configurations must match between the vPC peers, and consistency checks still take place. In a vPC+ domain, a unique FabricPath switch ID is configured and the peer link is configured as a FabricPath core port. This FabricPath switch ID under the vPC+ domain is called the Emulated switch ID. The Emulated switch ID must be the same between the two peers and must be unique per vPC+.
The benefits of using a vPC+ at the edge of a domain are as follows:
•Allows you to attach servers to the device using Link Aggregation Control Protocol (LACP) uplinks
•Allows you to attach other CE devices in vPC mode
•Allows you to attach Cisco Nexus 2000 Fabric Extenders in Active/Active mode
•Prevents orphan ports in a failure scenario. When a peer link fails in the vPC+ domain, the orphan port still has FabricPath uplinks for communication.
•Provides numerous paths
Please go through the below link which gives you complete information:-
http://www.cisco.com/en/US/docs/switches/datacenter/nexus5000/sw/mkt_ops_guides/513_n1_1/n5k_ops_fabricpath.html#wp1053135
HTH
Regards
Inayath
**(*Please rate the post if helpful***)
04-18-2016 08:20 AM
Well explained thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide