Alcatel-Lucent 7210 SAS-X - VLL Spoke SDP Configuration

Pseudowire Redundancy Service Models
Page 156 7210 SAS-X, R6 OS Services Guide
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 refer to an MPLS-TP node-id or global-id only if:
• Delivery type is MPLS.
• Signalling is off.
• Keep-alive is disabled
• Mixed-lsp-mode is disabled
• Adv-mtu-override is disabled
An LSP will only be allowed to be configured 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 or BGP-tunnel
• Adv-MTU-override
VLL Spoke SDP Configuration
7210 SAS-R6 can be S-PE or T-PE and 7210 SAS-T can only be a T-PE. MPLS-TP OAM related
commands are applicable to spoke-sdps configured under all services supported by MPLS-TP