After you create the FA-LSPs and TE
links, you can configure end-to-end LSPs to travel across the FA-LSPs.
Here are some general guidelines for this step:
In general, it is best to start your end-to-end LSP at
least one hop before the ingress of the FA-LSP and terminate your
LSP at least one hop after the egress of the FA-LSP. If you do originate
both the end-to-end LSP and the FA-LSP on the same routing platform,
you must disable CSPF and configure strict paths for the LSPs.
If you configure CSPF, OSPF, and RSVP to create the FA-LSP,
the LSP should automatically use the FA-LSP because of the preferred
lower metric generated by the reduced number of hops.
If you disable CSPF on the FA-LSP with the no-cspf option
at the [edit protocols mpls label-switched-path] hierarchy
level, you must configure the peer interface as a strict next hop
in the path for your regular LSP. To manually configure an LSP to
travel over the FA-LSP, include the peer-name statement at the [edit protocols mpls path path-name] hierarchy level and include the strict option.
For more information about creating RSVP
LSPs, see the JUNOS MPLS Applications Configuration Guide.
