Which routing protocol do you use?

Years ago EIGRP and OSPF had strong presence in large enterprise networks, BGP was used solely by Internet Service providers and IS-IS was a rarity (and there were people using Banyan Vines).

The situation has probably changed over the last years, I would (sadly) expect EIGRP to decline and (happily) BGP to grow. Let's figure it out; please respond to this week's readers' poll. Of course you can choose more than one routing protocol.

Recent posts in the same categories

11 comments:

  1. Anonymous 15 May 2008 00:43
    If not EIGRP, assuming you're running cisco gear, what's another viable IGP to run inside? I'm still fairly new at all this, so I might be missing something obvious. However I was under the impression that RIP, even V2, wasn't entirely viable in the "enterprise" realm.
  2. Unknown 15 May 2008 01:25
    I wonder how many people would be using EIGRP if it wasn't Cisco proprietory?

    Automated load balancing & ease of configuration with fast convergence, made it exceptionally powerful.

    Is it too late for Cisco to release it?
  3. Anonymous 15 May 2008 02:51
    We use EIGRP in an enterprise setting with thousands of routers. It works well, mostly. EIGRP "stuck in active" can cause flapping adjacencies when a big network is under duress, as happened to us recently when a core router "sort of" crashed. If the device had truly committed to crashing instead of being half-hearted about it, life would be have been better for us. ;-) Instead, we had a lot of withdrawn routes that confused the heck out of an MPLS cloud.

    We use BGP to exchange routes with extranet partners and high-volume customers. I'm planning on using more BGP for things like host route injection - not because BGP is the only option, but because it gives me outstanding flexibility in policy creation.

    We are evaluating pushing EIGRP into outlying islands, and converting the remaining core to OSPF. OSPF gives us the same fast convergence that EIGRP gives us, but it also gives us vendor interoperability. While our L2/L3 infrastructure is Cisco, our load balancers and security devices are generally NOT Cisco. Practically all of our non-Cisco gear talks OSPF. While today we use static routes on our security devices and load-balancers, distributing routes to these devices dynamically via OSPF would have payoffs in terms of automatic error recovery and ease of administration.
  4. Anonymous 15 May 2008 04:30
    We use OSPF as IGP for internal routes and BGP for peering with external neighbors. OSPF as IGP primarily because we use multivendor enviroment
  5. Anonymous 15 May 2008 05:54
    we only use bgp and ospf
  6. Anonymous 15 May 2008 10:26
    Since working for big telco company, we are using wide range of routing protocols. BGP&OSPF in MPLS backbone, EIGRP/RIP inside of customers tunnels, BGP&IS-IS in Internet backbone.
  7. Anonymous 15 May 2008 12:27
    Hi Tennis,


    Which reference do you use for MPLS, kompella or martini?

    regards
    Wan T
  8. Anonymous 15 May 2008 15:34
    I normally recommend the following:

    For PE-CE MPLS-VPN -> BGP

    For strictly IGP -> EIGRP, followed by OSPF if devices aren't Cisco.
  9. Rob 16 May 2008 03:56
    Similar to tenis, we use MPiBGP & OSPF in the backbone, with EIGRP, RIP or BGP inside of customers MPLS VPNs
  10. Anonymous 16 May 2008 05:04
    Working for a regional ilec/clec, we use IS-IS for the backbone IGP, EIGRP for CDN & old dialup gear, OSPF for SONET, and PE-CE MPLS links and transit services via BGP.

    IS-IS has been very good to us, but we are just now beginning the process of migrating all but the /32s out to BGP.
  11. Tassos 16 May 2008 12:14
    BGP, OSPF in the backbone
    EIGRP, BGP in customers

    I guess LAM (local-area mobility) doesn't count as a routing protocol ;)
Add comment
Home
Sidebar