The MPLS-OPS Archive
[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index]
RE: IGP
-
From: "Zeevik Neuman" <zeevikn@seriqa.com>
-
Date: Thu, 4 Jul 2002 14:07:53 +0200
-
Resent-Date: Thu, 4 Jul 2002 08:17:17 -0400
-
thread-index: AcIjK6sBL7lnoaXARcG5Opmo2adB8AAKNRjQ
-
Thread-Topic: [MPLS-OPS]: IGP
-
To: "Gowda, Sidde" <sidde.gowda@intel.com>, "amos" <slick@inter.net.il>, <mpls-ops@mplsrc.com>
Note
that both IS-IS and OSPF have TE extensions to support Traffic Engineering. Thus
means that the IGP also holds the amount of reserved and unreserved bandwidth on
each link, affinity of links, etc. so protocols like RSVP-TE can find a path
with the appropriate attributes of the tunnel.
Hi
Not necessarily,
Any Link state protocols are OK for TE
But currently we have two ie OSPF and IS-IS.
So MPLS network uses them.
Siddu
Hi
from all the examples i saw, the
interior gateway routing protocol for an mpls network is
alwayes
ospf or is-is. is there any
particular reason for that ?
i have a production network runing
eigrp as the igp, we are now starting to employ mpls in the
network,
and i would like to avoid migrating
into a different igp at the moment.
10x
Amos
- Follow-Ups:
- RE: IGP
- From: Roger Clark Williams <rogerw@nordlink.com>
| |
|