Beruflich Dokumente
Kultur Dokumente
We’re all cut from the same cloth, or in other words, fabric. It only makes sense that we connect with each
other in the most immediate way, with all lines of communication open and inviting. In this blog post I’ll be
looking at FabricPath, it’s purpose and how it pertains to the CCIE Data Center lab exam. I’ll also run through
a configuration, observing behaviors along the way. For those just looking for a sample config, a full config is
provided at the bottom of this post.
FabricPath was designed to overcome the limitation of Spanning-Tree Protocol (STP). What
limitations? Some that come to mind are poor convergence, unnecessary flooding and maintenance of full
CAM tables. Oh, and did I mention no ability for equal-cost multipathing (ECMP)?!
With FabricPath, we have the capability to actively forward on all links. If there is a failure on one of the links,
traffic will be redistributed across all the others. When traffic comes into the FabricPath domain, a single
lookup is performed to identify the switch closest to the destination, providing optimal flows.
Starting Topology
We will be using this topology for this walkthrough.
The above topology is STP-only. Before we dive into the configuration, let’s check out the current VLAN
database and Spanning-Tree on N7K3. We’ll take a look at this again in a few minutes.
VLAN0040
Spanning tree enabled protocol rstp
Root ID Priority 24616
Address e8ed.f339.4f44
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
VLAN0050
Spanning tree enabled protocol rstp
Root ID Priority 24626
Address e8ed.f339.4f44
This bridge is the root
Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
FabricPath Topology
Our end-goal will look like this, with FabricPath running between the N7Ks, and Classical Ethernet running to
the bottom two switches.