Hi All, I'm revisiting this topic/thread again. (bare in mind, I'm studying MPLS TE but not experienced in it yet)
Does MPLS TE make sense without using IGP extension for CSPF ? Reason I ask is. Page 144 of Cisco Press "QOS for IP/MPLS Networks", under section "Enabling MPLS TE" first paragraph of that section says. "In addition, you may want to enable the TE extensions for your IGP to perform constraint-based routing." It seems that the author is presenting the idea of enabling TE extensions for the IGP to perform constraint routing as optional. if this is true, then what is MPLS TE without TE extentions in the IGP ? Aaron From: Darren O'Connor [mailto:[email protected]] Sent: Monday, September 16, 2013 11:17 AM To: Aaron Subject: RE: [c-nsp] MPLS-TE on ME3600 That, and FRR. You need a TED to run FRR. Also it allows you to do CSPF LSPs which is very handy (link colouring, etc) Thanks Darren http://www.mellowd.co.uk/ccie _____ From: [email protected] To: [email protected] Subject: RE: [c-nsp] MPLS-TE on ME3600 Date: Mon, 16 Sep 2013 11:14:17 -0500 Darren, thanks, I currently have a single ospf area, but am not doing mpls-te.yet. Not sure what would compel me to do it really. Traffic steering to make use of underutilized links ? other reasons? Aaron From: Darren O'Connor [mailto:[email protected]] Sent: Monday, September 16, 2013 10:48 AM To: Aaron Subject: RE: [c-nsp] MPLS-TE on ME3600 It works best in a single area, but not impossible to go through multiple areas. Note that certain things like FRR don't work properly over multiple areas as only the border router have a full TED. I wrote a post on inter-area TE over here: http://mellowd.co.uk/ccie/?p=4069 Thanks Darren http://www.mellowd.co.uk/ccie > From: [email protected] > To: [email protected]; [email protected] > Date: Wed, 11 Sep 2013 15:05:22 -0500 > CC: [email protected] > Subject: Re: [c-nsp] MPLS-TE on ME3600 > > Is it true that mpls traffic engineering requires single area ospf ? > (something about mple te attributes within ospf getting lost between areas, > or unable to be passed into other areas) > > Aaron > > -----Original Message----- > From: cisco-nsp [mailto:[email protected]] On Behalf Of > Pshem Kowalczyk > Sent: Wednesday, September 11, 2013 2:36 PM > To: Eric Van Tol > Cc: [email protected] > Subject: Re: [c-nsp] MPLS-TE on ME3600 > > Hi, > > We use ME3600x with MPLS TE. I can't comment on the first point (we don't > have multiple areas), but on the second one - path protection is protection > end-to-end, whilst FRR uses a local repair mechanism, so these two are quite > different in the way they work. FRR on that device works fine and provides > protection for both originated and transit LSPs. On the third point - yes, > that's a limitation. I'm not sure if it's a hardware or a software one. > > kind regards > Pshem > > > On 12 September 2013 04:15, Eric Van Tol <[email protected]> wrote: > > Hi all, > > I'm a bit confused about the documentation for the ME3600 with regard to > its MPLS-TE support. Specifically, the 'MPLS TE' section > (http://www.cisco.com/en/US/docs/switches/metro/me3600x_3800x/software/relea > se/15.3_3_S/configuration/guide/swmpls.html#wp1183331) states: > > > > The switch does not support these MPLS TE features: > > *Interarea TE support for OSPF and IS-IS *TE path protection > > > > On the first bulletpoint, does this simply mean that it cannot pass > through areas without an explicit path set up? > > > > On the second bulletpoint, I'm confused about this because the next > section in the documentation deals with Fast Reroute. Does this bulletpoint > mean that the ME3600 cannot provide protection for transit LSPs? > > > > And finally, within the Fast Reroute section, I see this little nugget: > > > > "The switch supports MPLS TE fast reroute over only routed ports and not > over SVIs or EtherChannels." > > > > Huh? Really? > > > > -evt > > > > _______________________________________________ > > cisco-nsp mailing list [email protected] > > https://puck.nether.net/mailman/listinfo/cisco-nsp > > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
