RFC 4105 and its impact on dynamic routing over inter-area TE
RFC 4105 states:
"The use of IGP shortcuts MUST be precluded when TE-LSP head-end and
tail-end LSRs do not reside in the same IGP area. It MAY be used when they reside in the same area.
The advertisement of an inter-area TE LSP as a link into the IGP, in order to attract traffic to an LSP source, MUST be precluded when TE-LSP head-end and tail-end LSRs do not reside in the same IGP area. It MAY be used when they reside in the same area."
So how does one use dynamic methods (like FA and IGP shortcuts) to forward traffic over inter-area TEs ? Static routes is obviously not scalable at all.
Looking for some best practices in this regard. I am happy with one-hop TEs but still have reservations with regards to how (just using one Loopback on ABR) we can achieve this ? its probably not possible.
I read a new feature in Cisco talking about "autoroute destination" - is that more of a hack or workaround?
Re: RFC 4105 and its impact on dynamic routing over inter-area T
In this case, each ABR will maintain 2 databases, one for IGP routing and one for MPLS-TE topology. Although the routing databases are exchanged, the TE topologies are not and the head-end and tail-end being in different areas, are not aware of each other in the TE topology.
The way around this is to confiure the head-end and tail-end to have explicit-paths with the next-hop addresses as loose objects to each ABR and last hop to tail-end/head-end. As the head-end dosn't know the prefixes reachable by the tail-end, autoroute announce is not an option and the only way to push traffic down these tunnels is via a static route. Although this is not scalable to use static routing to push the traffic down the tunnel, for now it is the only way, as I have explained above.
I have configured this in a lab if you wish to see my conigurations.
1. Introduction Internet security is important with the increasing
attacks that are happening every day. Many internet and browsing
security solutions exist, but some are not very easy to use or maybe the
question is how can I enable them? In this referen...
Cisco Software Manager Server API Guide This document describes the
programmatic interfaces, RESTful APIs, which are supported by Cisco
Software Manager Server (CSM Server). Overview CSM Server supports a set
of finite RESTful APIs. The first step to use ...
If you are using Cisco's new linux-based Cisco Software Manager server,
then you probably want to make sure there is a startup service for
it.I'll assume that you've already installed the CSM server on a
systemd-based linux system. The commands given belo...