This feature behaves the same way as the RSVP-TE auto-LSP using an LSP template of type mesh-p2p.
The auto-lsp command binds an LSP template of type mesh-p2p-srte with one or more prefix lists. When the TE database discovers a router that has a router ID matching an entry in the prefix list, it triggers MPLS to instantiate an SR-TE LSP to that router using the LSP parameters in the LSP template.
The prefix match can be exact or longest. Prefixes in the prefix list that do not correspond to a router ID of a destination node never match.
The path of the LSP is that of the default path name specified in the LSP template. The hop-to-label translation tool or the local CSPF determines the node SID and adjacency SID corresponding to each loose and strict hop in the default path definition respectively.
The LSP has an auto-generated name using the following structure:
‟TemplateName-DestIpv4Address-TunnelId”
where:
TemplateName = the name of the template
DestIpv4Address = the address of the destination of the auto-created LSP
TunnelId = the TTM tunnel ID
In SR OS, an SR-TE LSP uses three different identifiers:
LSP Index is used for indexing the LSP in the MIB table shared with RSVP-TE LSP. Range:
for provisioned SR-TE LSP, 65536 to 81920
for SR-TE auto-LSP, 81921 to 131070
LSP Tunnel ID is used in the interaction with PCC/PCE. Range is 1 to 65536.
TTM Tunnel ID is the tunnel ID service, shortcut, and steering applications use to bind to the LSP. Range is 655362 to 720897.
The path name is that of the default path specified in the LSP template.