The following MPLS commands and modes are supported:
global [router] MPLS-level commands and modes:
interface, lsp, path, shutdown
LSP-level commands and modes:
bfd, bgp-transport-tunnel, exclude, hop-limit, include, metric, primary, retry-limit, retry-timer, shutdown, to, from, vprn-auto-bind
primary path-level commands and modes:
bandwidth, bfd, exclude, hop-limit, include, shutdown
secondary path-level commands and modes:
bandwidth, bfd, exclude, hop-limit, include, path-preference, shutdown, standby
The following MPLS commands and modes are not supported:
global MPLS-level commands and modes not applicable to SR-TE LSPs (configuration is ignored):
admin-group-frr, auto-lsp, bypass-resignal-timer, cspf-on-loose-hop, dynamic-bypass, frr-object, hold-timer, least-fill-min-thd, least-fill-reoptim-thd, logger-event-bundling, lsp-template, srlg-frr, static-lsp, static-lsp-fast-retry
LSP-level commands and modes not supported with SR-TE LSPs (configuration is blocked):
adaptive, adspec, fast-reroute, least-fill, propagate-admin-group, rsvp-resv-style
LSP-level commands and modes not supported with SR-TE LSPs (configuration is ignored):
cspf, igp-shortcut
primary path-level commands and modes not supported with SR-TE LSPs (configuration is blocked):
adaptive, record, record-label
secondary path-level commands and modes not supported with SR-TE LSPs (configuration is blocked):
adaptive, record, record-label
The user can associate an empty path or a path with strict or loose explicit hops with the primary paths of the SR-TE LSP using the hop, primary, and secondary CLI commands.
A hop that corresponds to an adjacency SID must be identified with its far-end host IP address (next hop) on the subnet. If the local-end host IP address is provided, this hop is ignored because this router can have multiple adjacencies (next hops) on the same subnet.
A hop that corresponds to a node SID is identified by the prefix address.
Details of processing the user-configured path hops are provided in SR-TE LSP Instantiation.