This section provides a brief overview of the tasks that must be performed to configure a management VPLS for spoke-SDP protection and provides the CLI commands. The following tasks should be performed on all four nodes providing the protected VPLS service.
Before configuring a management VPLS, please first read Configuring VPLS redundancy Configuring VPLS redundancy for an introduction to the concept of management VPLS and spoke-SDP redundancy:
Create an SDP to the local peer node (node ALA-A2 in the following sample).
Create an SDP to the remote peer node (node ALA-B1 in the following sample).
Create a management VPLS.
Create a spoke-SDP in the m-vpls using the SDP defined in Step 1. Ensure that this mesh-spoke-SDP runs over a protected LSP (see following note).
Enable the management VPLS service and verify that it is operationally up.
Create a spoke-SDP in the m-vpls using the SDP defined in Step 2. Optionally, modify STP parameters for load balancing.
Create one or more user VPLS services with spoke-SDPs on the tunnel SDP defined by Step 2.
As long as the user spoke-SDPs created in step 7 are in this same tunnel SDP with the management spoke-SDP created in step 6, the management VPLS will protect them.
Use the following syntax to create a management VPLS for spoke-SDP protection.
— config>service# sdp sdp-id mpls create
— far-end ip-address
— lsp lsp-name
— no shutdown
— vpls service-id customer customer-id [m-vpls] create
— description description-string
— spoke-sdp sdp-id:vc-id create
— stp
— no shutdown
The following is a sample VPLS configuration output.
*A:ALA-A1>config>service# info
----------------------------------------------
...
sdp 1 mpls create
shutdown
no description
signaling tldp
no ldp
no sr-isis
no sr-ospf
no bgp-tunnel
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
...
----------------------------------------------
*A:ALA-A1>config>service#