Choose Create→Service→VPLS from the NFM-P main menu. The VPLS Service (Create) form opens.

Select a customer to associate with the VPLS in the Customer panel.

Configure the required parameters.

To configure service tunnel required bandwidth for the service:

Note: To configure service tunnel required bandwidth, you must enable the Multi-Segment Tunnel Selection and Service Bandwidth Management checkboxes on the Services tab on the NFM-P System Preferences form. For more information, see the procedure to configure NFM-P system preferences in the NSP System Administrator Guide.

1. Click on the Bandwidth tab.

2. Configure the Bandwidth Method parameter.

3. If the Bandwidth Method parameter is set to Manual or Calculate, configure LSP Path Booking parameter.

4. If the Bandwidth Method parameter is set to Manual, enter a required bandwidth value for each CoS (see Override Service Configuration).

Perform one of the following.

1. Create an I-site for the VPLS. Go to Step 6 .

2. Complete service creation if I-sites, I-L2 access interfaces, and SDP bindings for the VPLS are to be created later. Go to Step 30 .

On the service tree, right-click on Sites and choose Create VPLS I-Site.

Select a site. The I-Site (Create) form opens.

Configure the general parameters.

Configure the parameters in the Routed VPLS panel.

Configure the parameters in the Load Balancing panel.

Click on the Backbone tab.

Select the Backbone VPLS site.

Note: The selection of the B-site in this step must be repeated for each I-site you create, since you must select the B-VPLS site that is within the same site as the I-site.

Configure the required parameters.

The Force Q Tag Forwarding parameter is only displayed if the NE for this site is in chassis mode D or higher or Sparrow.

To configure MFib, STP, FIB, and MAC Protection parameters for the I-site:

1. Click on the Forwarding Control tab.

2. Configure the required parameters.

3. Click on the STP tab to configure STP parameters for the I-site.

4. Configure the bridge-level STP parameters for the I-site.

   Nokia STP in a VPLS interoperates with customer STP implementations as a mechanism for loop detection and prevention. The bridge-level parameters balance the STP resiliency and speed of convergence.

   Modifying the bridge-level parameters must be done within the constraints of the following formulas:

   • 2 (Bridge Forward Delay – 1.0 s) >= Bridge Max Age

   • Bridge Max Age >= 2 (Bridge Hello Time + 1.0 s)

   Note:

   If you are configuring an MVPLS I-site, set the STP Mode parameter to RSTP or MSTP, depending on the MVPLS type. The MSTP option is available only if you are creating an MVPLS. See To create an MVPLS for more information about creating an MVPLS.

   MSTP is configurable only on the 7450 ESS, 7750 SR, and 7950 XRS.

5. Click on the FIB tab to configure FIB parameters for the I-site.

6. Configure the required parameters.

7. Configure the required MAC move parameters in the Mac Move panel.

8. Click on the MAC Protection tab to configure the list of protected MAC addresses.

9. Click Create. The MAC Protection (Create) form opens.

10. Configure the Protected Mac Address parameter.

11. Save the changes and close the form.

12. To configure an MVPLS I-site that requires MSTP, click on the MSTP tab.

13. Configure the required parameters.

14. Click on the MST Instances tab.

15. Click Create. The MST Instance (Create) form opens.

16. Configure the required parameters.

17. Click on the VLAN Ranges tab. Click Create. The MST Instance Managed VLAN range (Create) form opens.

18. Configure the required parameters.

19. Save the changes and close the forms.

To configure ingress multicast forwarding:

Note: An Operational Channels tab appears when you access the VPLS I-Site form in the Edit mode. It displays data for the operational channels when traffic from a specific multicast source for a specific multicast group passes through the service. You must click Search to refresh the data. See Chapter 49, Policies overview for information about listing the operational channel parameters.

1. Click on the Multicast tab, then on the Mcast Path Mgmt tab.

2. Select an ingress multicast info policy.

To assign test generation options to the site:

1. Click on the OAM tab, then the Configuration tab.

2. Configure the required Test Generation Options parameters.

To configure service tunnel required bandwidth for the site:

Note: To configure service tunnel required bandwidth, you must enable the Multi-Segment Tunnel Selection and Service Bandwidth Management checkboxes on the Services tab on the NFM-P System Preferences form. For more information, see the procedure to configure NFM-P system preferences in the NSP System Administrator Guide.

1. Click on the Bandwidth tab.

2. Enable the Override Service Configuration parameter.

3. Configure the Bandwidth Method parameter.

4. If the Bandwidth Method parameter is set to Manual, enter a required bandwidth value for each CoS (see CoS 0 Bandwidth - CoS 7 Bandwidth).

Configure IGMP snooping for the site.

1. Click on the Multicast tab.

2. Click on the IGMP Snooping tab.

3. Configure the required parameters.

   The Query source address parameter is configurable when the Use query source address parameter is enabled.

Configure MLD snooping for the site.

1. Click on the Multicast tab.

2. Click on the MLD Snooping tab.

3. Click on the General tab and configure the required parameters.

4. Click on the MRouters tab to view a list of multicast routers.

If you are configuring an MVPLS I-site, go to Step 22 .

To configure an SHG on the site:

Note: You must configure an SHG or RSHG if you plan to create a spoke circuit from this VPLS I-site to a VLL or to another VPLS.

1. Click on the Split Horizon Groups tab.

2. Click Create. The Site, New Split Horizon Group (Create) form opens.

3. Configure the required parameters.

4. Save the changes and close the form.

To create an I-L2 access interface for the I-site, perform Step 3 to Step 30 of To create a VPLS I-L2 access interface .

To create a virtual MEP on the site, perform Step 3 to Step 12 of To create a Virtual MEP on a VPLS site .

To create a spoke SDP binding between the I-site and regular VPLS sites, click on the Components tab and perform Step 7 to Step 34 of To create a VPLS or MVPLS spoke SDP binding , as required. I-sites can only use spoke SDP bindings.

Note: You cannot create a spoke SDP binding on an MVPLS site that runs MSTP, or enable MSTP on a site that has a spoke SDP binding.

You cannot enable MSTP on an access interface that has a non-zero encapsulation value.

Save the changes and close the form.The I-Site (Create) form closes, and a dialog box appears.

Save the changes and close the form.The VPLS Service (Create) form displays the new I-site on the navigation tree under VPLS.

Repeat Step 6 to Step 26 to create additional I-sites for the I-VPLS.

To add protected MAC addresses at the service level:

1. Click on the Forwarding Control tab.

2. Click on the MAC Protection tab.

3. Click Create. The MAC Protection (Create) form opens.

4. Configure the Protected Mac Address parameter.

5. Save the changes and close the form. Protected MAC addresses that you add on the site level, as performed in Step 14 , are automatically added to the service-level MAC protection list.

To configure bandwidth for the service if required, click on the Bandwidth tab:

Note: The Bandwidth tab is only available if service CAC is configured. See the procedure to configure NFM-P system preferences in the NSP System Administrator Guide for information about enabling and disabling service CAC.

The ability to configure required bandwidth is only applicable to I-sites.

1. For each CoS, configure the CoS Bandwidth (Mbps) parameter.

2. Click on the General tab to determine the CAC status.

   If the Verify CAC button is enabled, the CAC has not been verified. The Probable Cause and CAC Status fields provide details.

   The CAC Status field describes the current CAC status of the service. CAC statuses are as follows.

   • CAC Verified indicates that all tunnels have sufficient bandwidth to admit service and that requested bandwidth for the service is booked on the appropriate physical links.

   • CAC Failed indicates that the attempt made to admit service into the network was unsuccessful. The most likely cause for this is insufficient bandwidth. See the Probable Cause field for more specific information.

   • BW Defined, No CAC Request indicates that the required bandwidth is defined on the service; however, a CAC request has not occurred.

   • CAC To be Verified indicates that a tunnel has been configured on the service either manually or through the CLI; however, the required bandwidth has not been verified in the network.

   The Probable Cause field describes possible reasons for the current CAC state. Probable causes are as follows.

   • No Candidate Tunnels Found indicates that the autobind tunnel function was found, but no suitable tunnels were found.

   • Different PBB Tunnels Applied to Service indicates that two or more different PBB tunnels are configured on this service.

   • Not Enough Bandwidth on any Candidate Tunnels indicates that one or more candidate tunnels were found, but the available bandwidth was insufficient to admit the service.

   • Automatic PBB Tunnel Selection Failed indicates that a suitable PBB tunnel was found, but there were errors when attempting to assign the tunnel to the service. A dialog box will provide more details.

   • Site Missing Tunnel indicates that at least one selected site is not configured with a PBB tunnel.

   • All PBB Tunnels have not been Verified indicates that all sites within the service have a tunnel configured, but the available bandwidth has not been booked or verified in the network.

3. To manually verify the CAC, click on the Verify CAC button if it is enabled. The NFM-P will attempt to find the most appropriate PBB tunnel for the service based on available bandwidth, and to automatically bind the tunnel to the service if one has not already been assigned.

Save the changes and close the forms.

End of steps