To configure a distributed VPLS service, you must configure service entities on originating and far-end nodes. You must use the same service ID on all ends (for example, create a VPLS service ID 9000 on ALA-1, ALA-2, and ALA-3). A distributed VPLS consists of a SAP on each participating node and an SDP bound to each participating node.
The following is a sample configuration output of VPLS SAPs configured for ALA-1, ALA-2, and ALA-3.
*A:ALA-3>config>service# info
----------------------------------------------
vpls 100 customer 1 svc-sap-type any create
shutdown
no description
service-mtu-check
service-mtu 1514
no def-mesh-vc-id
no disable-learning
no disable-aging
no discard-unknown
fdb-table-size 250
fdb-table-high-wmark 95
fdb-table-low-wmark 90
no host-connectivity-verify
no shcv-policy-ipv4
no send-flush-on-failure
local-age 300
no mfib-table-size
mfib-table-high-wmark 95
mfib-table-low-wmark 90
remote-age 900
no propagate-mac-flush
bgp
no route-distinguisher
no vsi-export
no vsi-import
no route-target
exit
----------------------------------------------
*A:ALA-3>config>service#