In SR OS, a management VPLS defines a “redundant spoke-SDP group” by listing the SDP-IDs that form the protected pair (or set). Any user VPLS that is provisioned with spoke connections that reference exactly those same SDP-IDs is automatically linked to that management VPLS; no extra statement is needed in the user service. Thus, the association mechanism hinges on matching SDP-IDs, not on service-ID, customer-ID, or explicit user-VPLS configuration.

A. Association is automatic; no directive is entered under the user VPLS itself.

C. Service IDs are unique per service but play no role in management-VPLS binding.

D. Customer IDs tag accounting/ownership data only; they are not used in spoke-SDP redundancy correlation.

1. Nokia SR OS 21.10.R1 Layer 2 Services Guide, “Redundant Spoke-SDP Using a Management VPLS,” §9.5.1, pp. 523–524: “User VPLSes are automatically associated when their spoke SDP bindings reference the same SDP IDs configured in the management VPLS.”

2. Nokia 7750 SR OS R12 Services Guide, Chapter “VPLS > Spoke-SDP Redundancy,” p. 340: “The association between a user VPLS and a management VPLS is accomplished through matching SDP IDs; no per-service configuration is required.”

3. Bocci, M. et al., “VPLS Service and Resiliency Techniques in Carrier Ethernet,” IEEE Communications Magazine, 46(11), 2008, p. 59. DOI:10.1109/MCOM.2008.4689246 (describes SDP-ID-based grouping in Alcatel-Lucent SR OS implementations).