The traditional Ethernet network designs require termination of the Layer 2 Network at Aggregation or Core layer to limit the fault isolation and broadcast domain due to spanning tree. Due to limitations of spanning tree, each network design is composed of both Layer 2 and Layer 3 to take advantage of routing features (e.g. multipathing and fast convergence, loop mitigation mechanisms like TTL, RPF) to extend their network as shown in Figure 1 below. Cisco's new technology, FabricPath, brings Layer 3 routing benefits to flexible Layer 2-bridged Ethernet networks.
Due to widespread use of virtualization and clustering technologies these days, many organizations are looking to extend their Layer 2 domains across multiple data centers. FabricPath can provide this solution because it has the reliability and HA (High Availability) features just like ISIS protocol. Figure 2 shows the key points of FabricPath from both a Layer 2 and Layer 3 prospective.
Currently FabricPath is available only on the F1-Series module of the Nexus 7000 series. FabricPath is derived from IT Standard TRILL technology with a lot of extra enhanced features. Its switching allows multipath forwarding at the Layer 2 without the use of spanning-tree. FabricPath uses layer 2 ISIS based protocol for its control plane. The FabricPath ISIS process is different than the layer 3 ISIS process.
FP Forwarding Mechanism:
FabricPath creates trees just like spanning tree but uses link-based control based on ISIS protocol rather than distance vector like spanning tree. This is why it is loop free. This allows FabricPath to be in a forwarding state on all paths (maximum 16) without any blocking. It also allows faster convergences in case of failure similar to routing protocol. As shown in Figure 3, the fabric topology is composed of ingress, egress (edge) switches that are connected to the hosts and core switches that provide the fabric to connect all the edge switches. The egress switch can have the ports connected to conventional Ethernet (CE) so the egress switch is the one that has interfaces that are part of fabric path and CE. To forward the traffic to multiple destinations, FabricPath creates the Tree. After electing common roots for the L2 Fabric, "trees" from these roots are calculated from the shared L2 IS-IS routing database. In FB topology, each switch gets a unique switch ID, as depicted in Figure 3, to create the Layer 2 routing table. The ingress switch determines the "Tree" to be used for a flow and add the unique Tree identifier into the Fabric Path header.
Figure 3 depicts the Fabric Path routing table view from each switch. As mentioned before, once the root of the tree is determined, the root assigns dynamic IDs to the members.
One of the major improvements in FabricPath is that not all the switches in the Layer 2 FabricPath domain have to learn all the MAC addresses, which helps scale the MAC address tables. In FabricPath, as shown in figure 4, the MAC address table of the host A where it is showing that the host B is connected locally on the CE, whereas host C and D are connected via FP to the remote switches 101 and 200. When the Host A needs to send traffic to host C and host C's MAC address is not known, it floods the traffic to its root tree and then root forwards the packets to all its member switches. If the destination is not known on a particular edge switch, the switch drops that frame and does not learn the MAC address. However, if the destination is present on that switch, it will keep the source MAC address. To help reduce the MAC address entries, the core FabricPath switches never learn the MAC addresses.
FabricPath is fairly simple to configure.To configure the basic FabricPath network, follow the following steps on each device:
Enable the FP feature set on each device.
switch# config t
switch(config)# feature-set fabricpath
Configure the FP interfaces.
Switch(config)# interface ethernet 1/1
Switch(configif)# switchport mode fabric
Set the VLAN into FabricPath Mode. The default is the CE VLAN mode.
switch(config)# vlan 10
switch(config-vlan)# mode fabricpath
Please visit Cisco.com for more information about FabricPath.
Need to pass traffic from some specific internal IPs out an alternative internet connection.Traffic origin is from vlan on a core switch, which routes to a dedicated 3750x that handles BGP and wan selection. 3750x has a default route, but want to override...
We have a datacenter and several branch offices that connect to the datacenter via MPLS and backup Internet VPN. Our primary routing protocol is EIGRP (LAN and VPN), which is redistributed into our MPLS via BGP. Our primary connection for all IP traffic i...
Hi - I have an ASR903 that is using two QSFP_40GE_SR4 optics (both are recognized in the ASR903 on the appropriate ports) but the optics are not linking together when I connect them. I am using an MTP to MTP Female connector. I will upload an image o...
Attached diagram represents my network. At the Cisco 9500 core switch I have each SVI in its own VRF. I have created 2 VRF's for Internet & MPLS. I am using VRF-lite route leaking to control inter-vlan traffic at core switch level. Also using iBGP to ...
Good afternoon, I'm trying to get SNMP v3 up and running. Here are commands I've entered thus far. My gola is to get SNMP v3 working and to ensure all communications are secure as possible using 3des and sha communications. Step 1. snmp-server g...