[c-nsp] MPLS-TE on ME3600
Pshem Kowalczyk
pshem.k at gmail.com
Wed Sep 11 15:35:37 EDT 2013
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 <eric at atlantech.net> 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/release/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 cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list