acollard83
IS-IT--Management
Need a bit of advise on some configuration. Attached is a basic layout of the network. We have 2 remote sites that we are trying to connect back to our core network. We run EIGRP in the core (probably not effectivley either) and BGP to the internet edge.
In the core, we talk BGP to Zayo and Paetec, and EIGRP to other routers in our core. We also have iBGP right now talking to the 2 remote sites over 2 separate GRE Tunnels to each site. Each of the 2 remote sites has an AT&T primary fiber connection and a U-Verse DSL connection for backup. We run BGP over the fiber connection and the DSL connection only has a GRE Tunnel running over it back to our core network, which BGP is the protocol over noth tunnels (one over the fiber and one over DSL). We have static routing entries for the tunnel destination IP's. From AT&T, we are receiving default and customer routes. From our core, we are receiving local, customer and default routes. Right now, we are announcing a /23 at each remote site (we only need a /24, and a /26) both to AT&T and to our core network, and the core is announcing a mixture of /24, /23 and /22's. We want to announce our aggregate full route instead of all the hodge-podge prefixes.
What would be the best configuration for the way this network is setup? Routing protocol (EIGRP, OSPF, iBGP, a mixture)? We want to be able to utilize the DSL if the fiber goes down (understanding it would be GRE tunnel back to our core). We do have plans to run fiber from our core to each remote site, but that will take some time, each site is 20-40 miles away. How would you configure this setup if you had it?
In the core, we talk BGP to Zayo and Paetec, and EIGRP to other routers in our core. We also have iBGP right now talking to the 2 remote sites over 2 separate GRE Tunnels to each site. Each of the 2 remote sites has an AT&T primary fiber connection and a U-Verse DSL connection for backup. We run BGP over the fiber connection and the DSL connection only has a GRE Tunnel running over it back to our core network, which BGP is the protocol over noth tunnels (one over the fiber and one over DSL). We have static routing entries for the tunnel destination IP's. From AT&T, we are receiving default and customer routes. From our core, we are receiving local, customer and default routes. Right now, we are announcing a /23 at each remote site (we only need a /24, and a /26) both to AT&T and to our core network, and the core is announcing a mixture of /24, /23 and /22's. We want to announce our aggregate full route instead of all the hodge-podge prefixes.
What would be the best configuration for the way this network is setup? Routing protocol (EIGRP, OSPF, iBGP, a mixture)? We want to be able to utilize the DSL if the fiber goes down (understanding it would be GRE tunnel back to our core). We do have plans to run fiber from our core to each remote site, but that will take some time, each site is 20-40 miles away. How would you configure this setup if you had it?