Which statement about Cisco FabricPath is true?
A. It’s the best solution for interconnecting multiple data centers.
B. It optimizes STP throughout the Layer 2 fabric.
C. It’s a simplified extension of Layer 3 networks across a single data center.
D. FabricPath domain appears as a single STP bridge, each edge port uses the same MAC address.
FabricPath leverages many of the best characteristics of traditional Layer 2 and Layer 3 technologies, combining them into a new control-plane and data-plane implementation that combines the plug-and-play deployment model of a bridged Spanning Tree environment with the stability, reconvergence characteristics and ability to leverage multiple parallel paths typical of a Layer 3 routed environment. The result is a scalable, flexible and highly-available Ethernet fabric suitable for the most demanding Data Center environments. Spanning tree protocol does not run within the FabricPath domain, instead a layer 2 version of ISIS is running to build and distribute a layer 2 routing table. At the edge of the FabricPath domain, for backwards compatibility, it will interoperate with the Spanning Tree domain, appearing as if it is a single bridge, with a shared bridge ID. Typically, you would configure the virtual bridge as root for the STP domain as all forwarding paths would be in the direction of the FabricPath.
DCUCI – Data Center Unified Computing Implementation v5.0
DCUFI – Implementing Cisco Data Center Unified Fabric v5.0
DCUCD – Designing Cisco Data Center Unified Computing v5.0
DCUFD – Designing Cisco Data Center Unified Fabric v5.0
DCUCT – Troubleshooting Cisco Data Center Unified Computing v5.0
DCUFT – Troubleshooting Cisco Data Center Unified Fabric v5.0
CCNP Data Center