Showing results for 
Search instead for 
Did you mean: 

Multiple Fabricpath Topologies?

I've seen some mention of multiple fabricpath topologies, but am unable to find much in the way of example configuration.  Is this a supported feature at this time?  I've got Nexus 7004s at one site and 7010s at another both running 6.1(3). 

We've got fabricpath running as a DCI between a current site and a new DC.  Eventually I want to migrate all VLANs from our old 6500 core at the existing location, but I have some VLAN ID overlap with the new DC and I'd like to keep them separate.  In classical ethernet trunking I'd use the "switchport trunk allowed vlan" command, but I'm told that there's no equivelent for fabricpath interfaces.



Accepted Solutions
Shelley Bhalla

5k's support this from 5.2(1)N1(1) and 7k's support is coming soon (6.2).

View solution in original post

Shelley Bhalla

5k's support this from 5.2(1)N1(1) and 7k's support is coming soon (6.2).

View solution in original post

HI Terry,


Multi Topology tree are available now and I am working extensively on them in LAB.


As a small template you can use the following reference from Cisco :


     Command or ActionPurpose
    Step 1switch# configure terminal  Enters global configuration mode.  
    Step 2switch(config)# fabricpath topology id  

    Creates a new fabricpath topology and enters the FabricPath topology configuration mode.

    Step 3switch(config-fp-topology)# member vlan range  

    Configures the VLANs for the topology. The range of the VLAN ID is from 1 to 4094.

    Step 4switch(config-fp-topology)# exit  

    Exits FabricPath topology configuration mode.

    Step 5switch(config)# interface port-channel number  

    Configures a port-channel interface and enters interface configuration mode. You can configure any of the available interfaces.

    Step 6switch(config-if)# fabricpath topology-member id  

    Adds the interface to the topology.

    Step 7switch(config-if)# exit  

    Exits interface configuration mode.

    Step 8switch(config)# exit  

    Exits global configuration mode.

    Step 9switch# show fabricpath topology vlan  (Optional)

    Displays information about the VLANs in the Layer 2 topology.

    Step 10switch# show fabricpath isis topology summary  (Optional)

    Displays information about the IS-IS summary topology.

    Step 11switch# copy running-config startup-config  (Optional)

    Copies the running configuration to the startup configuration.


    This example shows how to create a topology, map VLANs to the topology, and add an interface to the topology.

    switch# configure terminal
    switch(config)# fabricpath topology 1
    switch(config-fp-topology)# member vlan 7-19
    switch(config-fp-topology)# exit
    switch(config)# interface port-channel 1
    switch(config-if)# fabricpath topology-member 1
    switch(config-if)# exit
    switch(config)# show fabricpath topology vlan
    switch(config)# show fabricpath isis topology summary

    Configuring FabricPath IS-IS Multiple Topologies


    You can configure FabricPath IS-IS multiple topologies.

    Before You Begin

    Ensure that you are working on an F Series module.

    Ensure that you have installed the Enhanced Layer 2 license.

    Ensure that you have enabled the FabricPath feature.

    I've been using it for six months now in a production environment and it works great.  :)

    HI Terry,

    Thanks for the wonderful rating, even though I have not helped you anything much.


    I am working more on NZ OS 7.x testing case scenarios these days so that we can implement up-gradations in coming time.

    I have made one lab for proof of concept for one customer although there is not much Multi topology configuration available online in Cisco or other places.


    I have tried for the 3 topologies..


    toplogy 0 

    VLAN 10, 20 , 30


    topology 1

    vlan 101-110


    topology 2

    vlan 201-210


    have you experience when you create port channels, that Vlans are leaking.

    I am experiencing VLAN are leaking.

    Could you please share what you have configured in your production environment.


    best regards


    Sachin Garg

    You may not have helped me personally, but it was a good post and may help someone else.  :)


    In my fabricpath topology I have:

    • Primary Data Center (all VLANs in topology 0)
    • Redundant data center (DC VLANs in 0,  local-only VLANs in 1)
    • Old Data Center we're migrating from (DC VLANs in 0, local-only in 1).

    Both the old Data Center and the redundant Data Center have offices co-located in the same building, thus the desire for the local-only topologies.


    This topology has performed as expected with no issues.


    I'm not sure what you mean by VLAN leaking.