Multi-Area And Multi-Instance Support; Mesh Lsp Name Encoding And Statistics - Alcatel-Lucent 7450 Manual

to this router-id will get 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.
There is no overall chassis mode restrictions enforced with the mesh LSP feature. If the chassis-
mode, network chassis-mode or IOM type requirements for a feature are not met, the
configuration of the corresponding command will not be allowed into the LSP template on the
system.

Multi-Area and Multi-Instance Support

A router which does not have TE links within a given IGP area/level will not have its router-id
discovered in the TE database by other routers in this area/level. In other words, an auto-LSP of
type P2P mesh cannot be signaled to a router which does not participate in the area/level of the
ingress LER.
A mesh LSP can however be signaled using TE links all belonging 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 ISIS or OSPF are configured on a router, each with its own router-id value,
the TE database in other routers will be able to discover TE links advertised by each instance. In
such a case, an instance of an LSP can be signaled to each router-id with a CSPF path computed
using TE links within each instance.
Finally, if multiple instances of ISIS or OSPF are configured on a destination router each with the
same router-id value, a single instance of LSP will be signaled from other routers. If the user shuts
down one IGP instance, this will be no op as long as the other IGP instances remain up. The LSP
will remain up and will forward traffic using the same TE links. The same behavior exists with a
provisioned LSP.

Mesh LSP Name Encoding and Statistics

When the ingress LER signals the path of a mesh auto-LSP, it includes the name of the LSP and
that of the path in the Session Name field of the Session Attribute object in the Path message. The
encoding is as follows:
Session Name: <lsp-name::path-name>, where lsp-name component is encoded as follows:
TemplateName-DestIpv4Address-TunnelId
Where DestIpv4Address is the address of the destination of the auto-created LSP.
At ingress LER, the user can enable egress statistics for the auto-created mesh LSP by adding the
following configuration to the LSP template:
7450 ESS MPLS Guide
MPLS and RSVP
Page 151