One interesting thing we ran into with FabricPath couple years ago is that you have to forget about the notion of "set of special vlans just for this switch" . In other words your list of vlans needs to be consistent and always the same in whole FabricPath. This is due to the fact that by default there is only one multidestination tree for broadcasts.
One of the beautiful side effects of this is that if misconfigured it WILL work just fine, until the next power failure when you failover into a multidestination tree that has one vlan missing. Good luck troubleshooting that.... For the rest of suggestions read Cisco FabricPath Best Practices Whitepaper -pavel 2017-01-23 11:41 GMT+01:00 Nikolai Nespor <use...@nespor.at>: > Neither supports FabricPath. EVPN+VXLAN is only supported on the 9300. > > Regards, > > Nikolai > -- > Ich verwalte sie. Ich zähle sie und zähle sie wieder. > Das ist nicht leicht. Aber ich bin ein ernsthafter Mann. > \ > ---> Antoine de Saint-Exupery, "Der kleine Prinz" > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
