SDPs

An SDP used for MPLS-TP supports the configuration of an MPLS-TP identifier as the far end address, as an alternative to an IP address. IP addresses are used if IP/MPLS LSPs are used by the SDP, or MPLS-TP tunnels identified by IPv4 source or destination addresses. MPLS-TP node identifiers are used if MPLS-TP tunnels are used.

Example: MPLS-TP options

config
    service
        sdp
            no description
            network-domain "default"
            signaling off
            far-end node-id 0.0.0.43 global-id 4294967295
            no mixed-lsp-mode
            no ldp
            no bgp-tunnel
            lsp "unnumberedLSP"
            no vlan-vc-etype
            no pbb-etype
            no path-mtu
            no adv-mtu-override
            keep-alive
                shutdown
                hello-time 10
                hold-down-time 10
                max-drop-count 3
                timeout 5
                no message-length
            exit
            no metric
            no collect-stats
            no accounting-policy
            binding
                no port
            exit
            no shutdown
----------------------------------------------
*A:7210SAS>config>service>sdp#

The far-end node-id ip-address global-id global-id command is used to associate an SDP far end with an MPLS-TP tunnel whose far end address is an MPLS-TP node ID. If the SDP is associated with an RSVP-TE LSP, then the far-end must be a routable IPv4 address.

The system accepts the node-id being entered as either 4-octet IP address format <a.b.c.d> or unsigned integer format.

The SDP far-end refers to an MPLS-TP node-id or global-id only if:

delivery type is MPLS
signaling is off
keep-alive is disabled
mixed-lsp-mode is disabled
adv-mtu-override is disabled

An LSP is allowed to be configured only if the far-end info matches the LSP far-end info (whether MPLS-TP or RSVP):

Only one LSP is allowed if the far-end is an MPLS-TP node-id or global-id.
MPLS-TP or RSVP-TE LSPs are supported. However, note that LDP and BGP LSPs are not blocked in CLI.

Signaling TLDP or BGP is blocked if:

far-end node-id/global-id configured
control-channel-status enabled on any spoke (or mate vc-switched spoke)
PW-path-id configured on any spoke (or mate vc-switched spoke)

The following commands are blocked if a far-end node-id or global-id is configured:

class-forwarding
tunnel-far-end
mixed-lsp-mode
keep-alive
ldp-tunnel or bgp-tunnel
adv-mtu-override