Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Routing Protocol Help

Routing Protocol Help

Routing Protocol Help

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?

RE: Routing Protocol Help

eigrp and ospf would both count the costs of your links hence preferring the fiber over the DSL link as long as you correctly setup the speeds.

you can also go for :
bgp - as padding.
ospf or eigrp : offset lists on the more costly path.

either way whatever works the best with your current design which seems to be eigrp since it is already established within your core.
if you go with eigrp then remember two things:
1- correctly setup filters both for incoming and outgoing at the remote sites AND your core.
2- setup offset lits for outgoing advertised routes such that you add +1000 (number i pulled out of my ...) to the DSL tunnels.

then when the fiber goes down the DSL paths will take over.

We must go always forward, not backward
always up, not down and always twirling twirling towards infinity.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close