Re: [c-nsp] FabricPath on Nexus Switches
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: > 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/
Re: [c-nsp] FabricPath on Nexus Switches
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/
Re: [c-nsp] FabricPath on Nexus Switches
True. Product line ADD. 3500 and 9300. - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP - Original Message - From: "Tom Hill" <t...@ninjabadger.net> To: cisco-nsp@puck.nether.net Sent: Sunday, January 22, 2017 7:08:09 PM Subject: Re: [c-nsp] FabricPath on Nexus Switches On 23/01/17 00:55, Mike Hammett wrote: > I hadn't realized at the time that these switches also support EVPN + > VXLAN, which would at least be a more modern fit. It's probably wise to start by identifying which range of Nexus switches you're talking about. Some are made with merchant silicon, some are made in house. As you can imagine, that does involve the supported features (and caveats) differing somewhat. :) -- Tom ___ 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/
Re: [c-nsp] FabricPath on Nexus Switches
On 23/01/17 00:55, Mike Hammett wrote: > I hadn't realized at the time that these switches also support EVPN + > VXLAN, which would at least be a more modern fit. It's probably wise to start by identifying which range of Nexus switches you're talking about. Some are made with merchant silicon, some are made in house. As you can imagine, that does involve the supported features (and caveats) differing somewhat. :) -- Tom ___ 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/
Re: [c-nsp] FabricPath on Nexus Switches
I hadn't realized at the time that these switches also support EVPN + VXLAN, which would at least be a more modern fit. - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP - Original Message - From: "Mike Hammett" <cisco-...@ics-il.net> To: "cisco-nsp@pu ck.nether.net" <cisco-nsp@puck.nether.net> Sent: Sunday, January 22, 2017 6:28:28 PM Subject: [c-nsp] FabricPath on Nexus Switches I've used TRILL-based protocols on other platforms before and it pretty much worked as expected. Any gotchas with Cisco's implementation? Is it much more complicated than setting it up, enabling it on particular interfaces and then plug and chug? - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ___ 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/
[c-nsp] FabricPath on Nexus Switches
I've used TRILL-based protocols on other platforms before and it pretty much worked as expected. Any gotchas with Cisco's implementation? Is it much more complicated than setting it up, enabling it on particular interfaces and then plug and chug? - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP ___ 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/