Feature Configuration

About this task

This feature uses three SR-TE LSP template types: one-hop P2P, on-demand P2P, and mesh P2P. For the one-hop P2P and mesh P2P types, the configuration of the commands is the same as that of the RSVP-TE auto-LSP.

Procedure

Create an LSP template using one of the following commands, depending on the type of auto-LSP required.
Classic CLI commands:
- config>router>mpls>lsp-template mesh-p2p-srte
- config>router>mpls>lsp-template one-hop-p2p-srte
- config>router>mpls>lsp-template on-demand-p2p-srte
MD-CLI commands:
- configure router mpls lsp-template type p2p-sr-te-mesh
- configure router mpls lsp-template type p2p-sr-te-one-hop
- configure router mpls lsp-template type p2p-sr-te-on-demand
In the template configure the common LSP and path level parameters or options shared by all LSPs using this template.

Note: These types of LSP templates contain the SR-TE LSP-specific commands and other LSP or path commands that are common to RSVP-TE and SR-TE LSPs, and are supported by the existing RSVP-TE LSP template.
Bind the LSP templates as follows:
- For SR-TE mesh P2P LSP template, use the config>router>mpls>lsp-template template-name policy peer-prefix-policy1 [peer-prefix-policy2] command.
- For SR-TE one-hop P2P LSP template, use the config>router>mpls>lsp-template template-name one-hop command.
- For on-demand SR-TE LSP template, the user binds the template to the creation of SR-TE auto-LSPs using the config>router>mpls>auto-lsp template-name command and configures the create-mpls-tunnel command as an action in a route import policy statement.
See Configuring and operating SR-TE for an example SR-TE auto-LSP creation using an LSP template type mesh-p2p-srte.