The following SDP subtypes of the MPLS type allow service binding to an SR tunnel programmed in the TTM by OSPF or IS-IS:
config>service>sdp>sr-isis
config>service>sdp>sr-ospf
SDPs of type sr-isis or sr-ospf can be configured with the far-end CLI command. When the sr-isis or sr-ospf command is enabled, a tunnel to the far-end address is selected in the TTM from the lowest preference IS-IS or OSPF instance. If multiple instances have the same lowest preference from the lowest numbered IS-IS or OSPF instance, the SR-ISIS or SR-OSPF tunnel is selected at the time of the binding, using the tunnel selection rules. If a preferred tunnel is subsequently added to the TTM, the SDP does not automatically switch to the new tunnel until the next time the SDP is being re-resolved.
The tunnel-far-end option is not supported. In addition, the mixed-lsp-mode option does not support the sr-isis and sr-ospf tunnel types.
The signaling protocol for the service labels of an SDP using an SR tunnel can be configured to static (off), T-LDP (tldp), or BGP (bgp).
SR tunnels can be configured in a VPRN service with the auto-bind-tunnel command.
VPN-IPv4 and VPN-IPv6 (6VPE) are supported in a VPRN or BGP EVPN service using segment routing transport tunnels with the auto-bind-tunnel command.
See BGP and see the 7210 SAS-Mxp, S, Sx, T Services Guide for more information about the VPRN auto-bind-tunnel CLI command.
The following service contexts are supported with SR tunnels:
VLL and LDP VPLS
BGP-AD VPLS when the use-provisioned-sdp option is enabled in PW template binding
intra-AS BGP VPRN for VPN-IPv4 and VPN-IPv6 prefixes with both auto-bind and explicit SDP
The following service contexts are not supported:
inter-AS VPRN
dynamic MS-PW, PW-switching
BGP-AD VPLS with auto-generation of SDP using an SR tunnel when binding to a PW template