I’d suggest BGP at all locations when building an MPLS network – MPBGP to be specific….
Sometimes folks who are just starting into MPLS presume that by having a full BGP mesh everywhere means that you need to carry the full Internet routing table … not the case and different routing table often (depending on the hardware/os being used). Also, a lot of networks will put the Internet BGP tables into a separate routing instance and leave just their IGP routes in the primary table – provides for a nice level of separation between your routes From: Af [mailto:af-boun...@afmug.com] On Behalf Of Sterling Jacobson Sent: Thursday, August 6, 2015 11:13 PM To: af@afmug.com Subject: Re: [AFMUG] Routed vs bridge with a twist MPLS is where we are heading. In the planning phases right now for MPLS ring network. Seems like it works well if the network has multiple paths, but heads in essentially one location. I think it may break a bit if it’s necessary to involve BGP at multiple locations though. That’s what I’m debating right now. From: Af [mailto:af-boun...@afmug.com] On Behalf Of Mike Hammett Sent: Thursday, August 6, 2015 7:43 PM To: af@afmug.com <mailto:af@afmug.com> Subject: Re: [AFMUG] Routed vs bridge with a twist MPLS-enabling a network also reduces your latency on Mikrotik. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com _____ From: "George Skorup" <geo...@cbcast.com <mailto:geo...@cbcast.com> > To: af@afmug.com <mailto:af@afmug.com> Sent: Thursday, August 6, 2015 7:52:23 PM Subject: Re: [AFMUG] Routed vs bridge with a twist If you already have a routed core network, especially if you have OSPF rings (like we do), I figure it'd make more sense to put MPLS on top. I haven't done it yet because we haven't needed to do anything like customer tunnels for multi-site interconnects, but we're getting there. On 8/6/2015 4:32 PM, Glen Waldrop wrote: I'm running Mikrotik, all routed, got a different subnet for each tower, got a different subnet between each tower, public IP's routed to the customers, all the fun stuff. I'm thinking of restructuring my network so the entire backbone is one big L2 network. If I plug into the switch at the tower at tower 5 it will be no different than tower 1 or 7. Each AP would still have it's own subnet, but the backside of each AP would be on the same L2 as the rest. I'm planning on looping it all the way around and building redundancy into the network, haven't quite decided how I'm going to do that yet, might use STP, that is a little ways down the road. I'll have another fiber feed in case the main goes down and I'd like to have a level of redundancy should a tower go out, I'll only lose the one rather than the ones behind it as well. I've fried my brain today, so if I'm sounding half crazy, just tell me to take the rest of the day off... I'm thinking it might be best to have a few large L2 segments to the backbone, maybe three or four, rather than one big L2 and much simpler than 12+ subnets from tower to tower. Input is appreciated.
