The following MPLS commands and nodes are supported:
Global MPLS-level commands and nodes:
interface, lsp, path, shutdown
LSP-level commands and nodes:
bfd, bgp-shortcut, bgp-transport-tunnel, cspf, exclude, hop-limit, igp-shortcut, include, metric, metric-type, path-computation-method, primary, retry-limit, retry-timer, revert-timer, shutdown, to, from, vprn-auto-bind
Both primary and secondary paths are supported with a SR-TE LSP. The following primary path level commands and nodes are supported with SR-TE LSP:
bandwidth, bfd, exclude, hop-limit, include, priority, shutdown
The following secondary path level commands and nodes are supported with SR-TE LSP:
bandwidth, bfd, exclude, hop-limit, include, path-preference, priority, shutdown, srlg, standby
The following MPLS commands and nodes are not supported:
Global MPLS level commands and nodes not applicable to SR-TE LSP (configuration is ignored):
admin-group-frr, auto-bandwidth-multipliers, auto-lsp, bypass-resignal-timer, cspf-on-loose-hop, dynamic-bypass, exponential-backoff-retry, frr-object, hold-timer, ingress-statistics, least-fill-min-thd, least-fill-reoptim-thd, logger-event-bundling, lsp-init-retry-timeout, lsp-template, max-bypass-associations, mbb-prefer-current-hops, mpls-tp, p2mp-resignal-timer, p2mp-s2l-fast-retry, p2p-active-path-fast-retry, retry-on-igp-overload, secondary-fast-retry-timer, shortcut-local-ttl-propagate, shortcut-transit-ttl-propagate, srlg-database, srlg-frr, static-lsp, static-lsp-fast-retry, user-srlg-db
LSP level commands and nodes not supported with SR-TE LSP (configuration blocked):
adaptive, adspec, auto-bandwidth, class-type, dest-global-id, dest-tunnel-number, exclude-node, fast-reroute, ldp-over-rsvp, least-fill, main-ct-retry-limit, p2mp-id, primary-p2mp-instance, propagate-admin-group, protect-tp-path, rsvp-resv-style, working-tp-path
The following primary path level commands and nodes are not supported with SR-TE LSP:
adaptive, backup-class-type, class-type, record, record-label
The following secondary path level commands and nodes are not supported with SR-TE LSP:
adaptive, class-type, record, record-label
The user can associate an empty path or a path with strict or loose explicit hops with the paths of the SR-TE LSP using the hop, primary, and secondary 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.