I find stability to be the most effective feature of Cisco FabricPath; it is stable. Cisco FabricPath has good scalability; I don't have any problems with scalability as I can add any switches or distributors without any problem. I utilize the multipath routing architecture feature in Cisco FabricPath, and it's good in load balancing. Cisco FabricPath's compatibility to support Dynamic Layer 2 multipath routing in complex virtualized environments is good; I don't have any problems with it. Nothing comes to mind regarding metrics for using the Layer 2 multipath routing feature; it was good, and there were no problems at all with Cisco FabricPath. Cisco FabricPath's integration with Cisco Nexus works with virtual port channel (VPC) and is good for dual home servers and edge switches. We are using VPC in every layer of the Nexus center. Implementing Cisco FabricPath positively impacted my organization by providing minimum downtimes as the service is always up; everything is working properly with the VPC and Cisco FabricPath. I have experienced operational efficiencies with Cisco FabricPath that are 200% better than the old legacy equipment and protocols.

