Multi-Area And Multi-Instance Support - Nokia 7705 SAR-W Series Manual

Service aggregation router, mpls
Table of Contents

Advertisement

MPLS and RSVP-TE
The user must perform a no shutdown of the template before it takes effect. When
a template is in use, the user must shut down the template before changing any
parameters except for those LSP parameters for which the change can be handled
with the Make-Before-Break (MBB) procedures (see
Procedures for LSP and Path Parameter Configuration
template is shut down and parameters are added, removed, or modified, the existing
instances of the LSP using this template are torn down and resignaled.
MBB procedures for manual and timer-based resignaling of the LSP, and for TE
graceful shutdown, are supported.
The tools>perform>router>mpls>update-path command is not supported for
mesh LSPs.
The one-to-one option under the fast-reroute command is also not supported.
If the TE database loses the router ID while the LSP is up, it will perform an update
to the MPLS that states that the router ID is no longer in the TE database. This occurs
whether the bypass backup path is activated or not. This will cause MPLS to tear
down all mesh LSPs to this router ID. However, if the destination router is not a
neighbor of the ingress LER and the user shuts down the IGP instance on the
destination router, the router ID corresponding to the IGP instance will only be
deleted from the TE database on the ingress LER after the LSA/LSP times out. If the
user brings the IGP instance back up before the LSA/LSP times out, the ingress LER
will delete and reinstall the same router ID at the receipt of the updated LSA/LSP.
The RSVP-TE LSPs destined for this router ID will be deleted and re-established. All
other failure conditions will cause the LSP to activate the bypass backup LSP or to
go down without being deleted.
3.5.3.1
A router that does not have TE links within a given IGP area or level will not have its
router ID discovered in the TE database by other routers in this area or level. In other
words, an auto-created LSP mesh cannot be signaled to a router that does not
participate in the area or level of the ingress LER.
A mesh LSP can be signaled using TE links that belong to the same IGP area even
if the router ID of the ingress and egress routers are interfaces reachable in a
different area. In this case, the LSP is considered to be an intra-area LSP.
If multiple instances of IS-IS are configured on a router, each with its own router ID,
the TE database on other routers will be able to discover TE links advertised by each
instance. In this case, an instance of an LSP can be signaled to each router ID with
a CSPF path computed using TE links within each instance.
58

Multi-Area and Multi-Instance Support

Use subject to Terms available at: www.nokia.com
© 2022 Nokia.
MPLS Guide
Make-Before-Break (MBB)
Changes). When the
3HE 18686 AAAB TQZZA

Advertisement

Table of Contents
loading

Table of Contents