Enable and configure BGP on the NEs involved in the BGP VPWS. See BGP configuration workflow and procedures for information about how to configure BGP.

Create and distribute a Service PW template policy to the NEs involved in the VPWS. See Chapter 83, Service PW template policies for more information about how to use Service PW template policies. You must set the VC-Type parameter to VLAN.

Create a routing policy statement to define the required community members. See To configure a routing policy statement . This defines the VSI Import/Export Routing Targets.

Create an Epipe service. See To create a VLL service for information about how to create an Epipe service.

Create the Epipe sites for the BGP VPWS. See To configure a VLL site for information about how to create an Epipe site.

Note: Epipe switching sites can have only one spoke SDP binding configured when BGP VPWS is enabled.

When BGP VPWS is enabled on an Epipe switching site, the tunnel used in the spoke SDP binding must be GRE with no signaling.

You cannot enable BGP VPWS if there are more than one spoke SDP bindings on the switching site, or if there is one or more spoke SDP bindings with a non-GRE tunnel.

Select one of the Epipe sites you created in Step 5 . The Site Epipe Service (Edit) form appears.

Click on the BGP tab.

Enable the Enable BGP parameter. The BGP panel is displayed.

Click Create. The BGP Configuration form opens.

Configure the Route Distinguisher parameter.

Click on the PW Template Binding tab and perform one of the following:

1. Select an existing PW Template Binding.

2. Add a new PW Template Binding. Go to Step 12 .

Create one or more PW Template Bindings:

1. Click Create. The PW Template Binding (Create) form opens.

2. Select the PW Template you created in Step 2 .

3. Select an endpoint if needed.

4. Click on the BFD tab and configure the required BFD parameters.

5. Click on the PW Template Binding Route Target tab and click Create. The PW Template Binding Route Target (Create) form opens.

   Note:

   This Import Route Target is used by the NE to decide which PW Template to use to create SDP bindings. If a far-end neighbor has a matching export target (that is, to the PW Template Import Target being defined here), then this PW Template is selected by the NE to create the pseudowire that is used to link both sites of the VPWS. If nothing is entered, and multiple PW Templates are defined, the first one found by the NE is used (most likely the one with the lowest PW Template Policy ID).

   Enter the required Import Route Target in the field and click OK. The PW Template Binding Route Target (Create) form closes and the entered Import Route Target is displayed in the table on the PW Template Binding Route Target tab.

6. Click OK. The PW Template Binding (Create) form closes and the new PW Template Binding is displayed in the table on the PW Template Binding tab.

7. Select the required entry or entries from the list.

Click on the VSI Import Policies tab and select up to five import policies. Alternatively, you can enter the policy names manually.

Perform one of the following:

1. Enter the Import Route Target name manually in the provided field. The format be “target:x:y”.

2. Select an import route target. The community members you defined when creating a routing policy in Step 3 can be selected.

Click on the VSI Export Policies tab and select up to five export policies. Alternatively, you can enter the policy names manually.

Perform one of the following:

1. Enter the Export Route Target name manually in the provided field. The format must be “target:x:y”.

2. Select an export route target. The community members you defined when creating a routing policy in Step 3 can be selected.

Save the changes and close the BGP Configuration form.

Configure the parameters on the VPWS tab.

Create a remote VE instance, if required.

1. In the Remote VE Instances panel, click Create. The BGP VPWS Remote VE (New) form opens.

2. Configure the parameters.

Configure the parameters in the EVPN tab.

Click Apply.

Repeat Step 6 to Step 21 for each site in the VPWS. When the sites have been configured, endpoints and associated spoke SDP bindings are automatically created by the nodes.

End of steps