From: JOSE ANGEL MARTINEZ DE LA VARA (jamartinez@xxxxxxxxxxxxxxxx)
Date: Mon Mar 04 2002 - 06:24:06 GMT-3
Hi,
Perhaps I do not know enough to answer your question, but perhaps my point
of view would help you.
In your MPLS backbone you are surely running OSPF or ISIS, aren't you? It
works well because those protocols where designed for that use. You run BGP
to carry labels and routes among the VPN clients. All of this makes your
MPLS backbone look like a full mesh of WAN connections to your VPN
customers. Then, I think you should just forget about MPLS and think about a
design for running over IP the dynamic routing protocol you would run over a
WAN full mesh network. Would you use BGP for that? I do not think so. I'd
use OSPF.
Please, tell me your reasons and let us learn more about MPLS and everything
around it. Most of us have no way to see such a MPLS backbone running all
that good stuff. (And it will be very helpfull for since my final degree
project is exactly what you have in your hands, MPLS)
Thanks
Jose Angel
-----Mensaje original-----
De: Tarek Sabry [mailto:tsabry@houston.sns.slb.com]
Enviado el: lunes, 04 de marzo de 2002 09:21
Para: ccielab@groupstudy.com
Asunto: EGP vs IGP vs static routes
To the design specialists:
I'd like to pose a question that may actually seem naive. In fact I was
reading Halabi's Internet Routing Architectures and started asking myself
about the fundamental differences between the applications of IGPs and EGPs.
I think Halabi makes his favourite protocol seem really attractive!!!
I have an MPLS backbone, over which I run VPNs and will also be running QoS
and Traffic Engineering and all that good stuff. Attached to the global MPLS
backbone are multinational customer POPs and also different service enclaves
that tend to those customers. Firewalls exist between the backbone and the
POP and between the POP and the customer's network in each location.
Currently we have static routes running between the POPs and poining to the
customers as well. I am tasked with evaluating dynamic routing protocols as
a viable replacement for those static routes. The operations personnel are
not really complaining that much about managing the static routes, but some
"experts" in my organization feel that static routes will not scale well. We
currently have about 50-100 static route entries per router/firewall.
Now to the question: If I am to decide on dynamic routing between my POPs,
how should I be deciding on a routing protocol? I am considering
- staying with static and distributing into the BGP MPLS backbone.
- EIGRP (but this will not run on my firewalls that have GATED, so I may
need more redistribution work!)
- OSPF
- IBGP inside the POP (consisting of Cisco routers and Checkpoint firewalls)
and EBGP into the backbone.
Is this latter alternative stupid? Is it just me liking BGP too much after I
bought Halabi's book?
Thanks a lot
Tarek
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:52 GMT-3