Professional Documents
Culture Documents
layer 2 forwarding.
Whether we like or not, there is often a need for layer 2 in the Datacenter for the following reasons:
Reduction/elimination of STP
Better stability and convergence characteristics
Simplified configuration
Leverage parallell paths
Deterministic throughput and latency using typical designs
VLAN anywhere flexibility
The FabricPath control plane consists of the following elements:
Routing table Uses ISIS to learn Switch IDS (SIDs) and build a routing table
Multidestination trees Elects roots and builds multidestination trees
Mroute table IGMP snooping learns group membership at the edge, Group Member LSPs
(GM-LSPs) are flooded by ISIS into the fabric
Observe that LSPs has nothing to do with MPLS in this case and that this is not MAC based routing,
routing is based on SIDs.
FabricPath ISIS learns the shortest path to each SID based on link metrics/path cost. Up to 16 equal
(ECMP) routes can be installed. Choosing a path is based on a hashing function using Src IP/Dst
IP/L4/VLAN which should be good for avoiding polarization.
FabricPath supports multidestination trees with the following capabilities:
Multidestination trees do not dictate forwarding for unicast, only for multidestination packets.
The FabricPath data plane behaves according to the following forwarding rules:
The first design is the most classic one where STP has been replaced by FP in the Access layer and
routing is used above the Aggregation layer.
This design has the following characteristics:
This design is the simplest option and is an extension of regular Access/Aggregation designs. It
provides the following benefits:
Simplified configuration
Removal of STP
Traffic distribution over all uplinks without the use of vPC
Active/active gateways
VLAN anywhere at the Access layer
Topological flexibility
Direct-path forwarding option
Easily provision additional AccessAggregation bandwidth
Easily deploy L4-L7 services
Can use vPC+ towards legacy Access switches
There is also the centralized routing design which looks like the following:
Another design is the multi-pod design which can look like the following:
Define FabricPath VLANs -> map VLANs to topology -> map topology to FabricPath core
port(s)
Thanks to Daniels.