Choose Manage→Service→Services from the NFM-P main menu. The Manage Services form opens.

Choose a VPLS and click Properties. The VPLS Service (Edit) form opens.

On the service tree, expand Sites→site→L2 Access Interfaces.

Right-click on L2 Access Interfaces and choose Create I-L2 Access Interface. The I-L2 Access Interface (Create) form opens.

Configure the required parameters.

Tunnel Fault Notification is configurable on interfaces where the device has ports configured in access or hybrid mode with QinQ encapsulation.

If you are configuring a tunnel facility MEP, Tunnel Fault Notification must be set to Accept.

Select a transit prefix policy for the interface in the Transit Prefix Policy panel.

Select an SHG for the interface in the Split Horizon Group panel.

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

Click on the Port tab.

Select a port for the I-L2 access interface.

Note: The form lists only ports in access or hybrid mode. To choose a port that is not listed, you must set the Mode parameter for the port to Access or Hybrid. After you do this, the port is listed when you click Search.

If you select an Ethernet Tunnel Endpoint, the Port form is refreshed and an Ethernet Tunnel tab is added.

CAUTION Service Disruption

The creation of a SAP that uses the same port and encapsulation values as an existing inactive MSAP fails under the following conditions:

• If you try to use the NFM-P to create a SAP, the configuration fails and the NFM-P displays an error message.

• If you use a CLI to create a SAP in a service other than the service that contains the MSAP, the configuration succeeds but the MSAP is inactive until the regular SAP is deleted. Although the NFM-P displays the SAP and MSAP, the MSAP remains inactive and consumes resources.

• If you use a CLI to create a SAP in the service that contains the MSAP, the SAP creation fails.

Nokia recommends that you delete an inactive MSAP from the NFM-P if you need to create a regular SAP on the same port using the same encapsulation values.

Configure the required parameters.

For an I-L2 access interface, only Null, dot1q, and QinQ encapsulations are supported. In the case of I-MPVLS L2-access interfaces, Null encapsulation is not supported. I-MPVLS L2-access interfaces with MSTP configured support QinQ. These ports must also be of Ethernet type PBB.

When the selected port uses dot1q encapsulation, you can enable the Auto-Assign ID parameter to have the Outer Encapsulation Value parameter automatically assigned. If you choose this, the system assigns the lowest unused encapsulation value.

Note: You can set the Auto-Assign ID parameter to be the default parameter for dot1q encapsulation by enabling the Access Interface Encap Value (Dot1q only) parameter in the User Preferences form. Choose Application→ User Preferences from the main menu.

The Inner Encapsulation Value is configurable only when the port is an Ethernet with QinQ encapsulation.

SAP types X.0 and X.* as well as SAP types *.null and *.* can be configured on the same Q in Q port. You must enable the Enable Q in Q Untagged Sap parameter on the NE which allows the creation of the following default SAP types:

• The SAP type *.null functions as a default SAP for single-tagged frames on a Q in Q port. This SAP accepts single tags in the range 0 to 4095 as well as untagged traffic.

• The SAP type *.* functions as a default SAP for double-tagged frames on a Q in Q port. This SAP accepts untagged, single-tagged, and double-tagged frames with tags in the range 0 to 4095.

See To enable a Q in Q untagged SAP on an NE for more information.

If the port you have chosen is an Ethernet Tunnel Endpoint, you will be able to set the Outer Encapsulation Value to 8191. This automatically enables the Ethernet Tunnel Endpoint Control SAP parameter.

Configure the Ethernet Tunnel Endpoint Control SAP parameter.

Note: Enabling the Ethernet Tunnel Endpoint Control SAP parameter creates the control L2 Access Interface (also known as a Control SAP). It also automatically sets the value of the Outer Encapsulation Value parameter to 8191.

If you are currently creating a same-fate SAP, the Ethernet Tunnel Endpoint Control SAP parameter must not be enabled.

Depending on the port that you have chosen, the Egress Multicast Group tab is configurable. To configure the EMG:

1. Click on the Egress Multicast Group tab.

2. Select an EMG.

   Note:

   The Egress Multicast Group-L2 Interface form lists only EMGs that have the same egress filter and encapsulation type as the interface.

If the selected port uses FR encapsulation, configure Frame Relay for the interface:

1. Click on the Frame Relay tab.

2. Set the FRF-12 Mode parameter to Enabled.

3. Configure the required parameters.

To assign ingress and egress QoS policies to the interface:

1. Click on the QoS tab.

   Note:

   Items such as policies, schedulers, and filters can be applied later to multiple service components at once by selecting and right-clicking the components in the service navigation tree, choosing Properties, and configuring the parameters on the appropriate tab. This action opens a properties form in a new window for the component that was right-clicked. The navigation tree is not displayed in this new window.

2. Configure the Ingress Match QinQ Dot1P parameter.

   The Ingress Match QinQ Dot1P parameter is configurable only when the encapsulation type of the port is dot1q or QinQ.

3. Select an ingress Qos policy in the Ingress Policy panel.

   Note:

   If you select an access ingress policy which has a forwarding class mapped to an ingress queue group, you must ensure that port that you are configuring for the VPLS L2 access interface has the access ingress queue group with the same name created on it.

   See To configure Ethernet ports in Chapter 16, Port and channel object configuration for more information about how to configure Ethernet ports. See Chapter 49, Policies overview for more information about queue group template policies.

4. Select an ingress queue group template policy in the Forwarding Plane Redirect panel to choose a policy.

5. Configure the Instance ID parameter.

6. Configure the Egress Mark QinQ Top Bits Only parameter.

   The Egress Mark QinQ Top Bits Only parameter is configurable only when the encapsulation type of the port is dot1q or QinQ.

7. Select an egress QoS policy in the Egress Policy panel.

   Note:

   If you select an access egress policy which has a forwarding class mapped to an egress queue group, you must ensure that port that you are configuring for the VPLS L2 access interface has the access egress queue group with the same name created on it.

   See To configure Ethernet ports in Chapter 16, Port and channel object configuration for more information about how to configure Ethernet ports. See Chapter 49, Policies overview for more information about queue group template policies.

8. If the port you selected is not an HSMDA port then go to Step 15 .

9. Configure the Packet Byte Offset (bytes) parameter. Before you can configure the parameter, you must enable the associated Override parameter.

10. Select a WRR policy in the Egress HSMDA Override panel.

11. Select an HSMDA egress secondary shaper policy in the Egress HSMDA Override panel.

12. Select an HS secondary shaper in the HS Overrides panel, if required.

13. Configure the required parameters.

Click on the Schedulers tab to configure scheduling:

Note: The Schedulers tab is configurable only when a port is assigned to the interface.

Perform one of the following.

1. To specify that an aggregation scheduler policy is not applied to the interface.

   1. Set the Aggregation parameter to off.

      Note:

      The Aggregation parameter is not configurable if the port you selected is an HSMDA port.

   2. Configure the required parameters.

      Note:

      The Aggregate Rate Limit (kbps) and Frame-Based Accounting parameters are configurable only when there is no scheduler specified in the Egress Scheduler panel.

      The Frame-Based Accounting parameter is not configurable if the port you selected is an HSMDA port.

      You cannot specify an egress scheduler when the Aggregate Rate Limit (kbps) parameter is set to a value greater than zero.

   3. Select and ingress scheduler in the Ingress Scheduler panel.

   4. Select an ingress policer control policy in the Ingress Policer Control Policy panel.

   5. If the port you selected is an HSMDA port, go to Step 17 .

   6. Select an egress scheduler in the Egress Scheduler panel.

   7. Select a policer control policy in the Egress Policer Control Policy panel.

   8. Go to Step 17 .

2. To specify that an access scheduler policy is applied to the interface:

   Note: You cannot specify an access scheduler policy if the port you selected is an HSMDA port. Go to Step 17 .

   1. Set the Aggregation parameter to on.

   2. Select an aggregation scheduler in the Aggregation Scheduler panel.

To assign ingress and egress ACL filters to the interface:

1. Click on the ACL tab.

2. Select an ingress ACL filter in the Ingress Filter panel.

3. Select an egress ACL filter in the Egress Filter panel.

4. Select an IPv6 ingress ACL filter in the IPv6 Ingress Filter panel.

5. Select an IPv6 egress ACL filter in the IPv6 Egress Filter panel.

To assign an accounting policy to the interface:

1. Click on the Accounting tab.

2. Configure the Collect Accounting Statistics and Ingress Counter Type parameters.

3. Select an accounting policy.

To configure BPDU Termination, STP, and FIB parameters for the interface:

1. Click on the Forwarding Control tab. Depending on the device being configured, the BPDU Termination tab is displayed. Otherwise, go to 3 .

2. Configure the required parameters.

   When the L2 Protocol Termination parameter is set to Enabled, a list of L2PT protocols is displayed. Select all that are required.

   The Force L2PT on Managed L2 Access Interface parameter is only available for MVPLS I-L2 access interfaces. When the Force L2PT on Managed L2 Access Interface parameter is set to Enabled, a list of L2PT protocols is displayed. Select all that are required.

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

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

5. If you are creating an MVPLS to run MSTP, Click on the MST Instances tab to edit a SAP MST instance. Otherwise, go to Step 20 .

6. Select an MST instance and click Properties.

7. The I-L2 Access Interface MST Instance (Edit) form opens. Configure the required parameters.

8. Save the changes and close the form.

To assign a DoS protection policy or DDoS protection policy to the interface:

Note: A default DoS protection policy is automatically assigned to the interface.

1. Click on the Security tab.

2. Select a DoS protection policy in the NE DoS Protection panel.

3. Configure the MAC Monitoring parameter.

To assign test generation options to the interface:

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

2. Configure the required Test Generation Options parameters.

To configure an Ethernet tunnel:

Note: You can only configure Ethernet tunnel SAP path parameters if you are creating a same-fate SAP.

1. Click on the Ethernet Tunnel tab.

2. If you are configuring a fate-sharing Ethernet Tunnel Endpoint SAP (also referred to as same-fate SAP) then go to 3 . Otherwise, go to Step 23 .

3. Click Create. The Ethernet Tunnel (Create) form opens.

4. Configure the required parameters.

5. Save the changes and close the form.

To configure a redundant VLAN range:

Note: If an MVPLS site has SAPs that manage traffic on the associated VPLS SAPs, you must define a redundant VLAN range during SAP creation. The redundant VLAN range defines the range of VC IDs for VPLS SAPs that the MVPLS manages.

1. Click on the Redundancy tab.

2. Click Create. The RedundantVlanRange (Create) form opens.

3. Configure the required parameters.

4. Save the changes and close the form.

To configure IGMP snooping for the interface:

1. Click on the IGMP Snooping tab.

2. Configure the required parameters.

   The General Query Interval (seconds), Maximum Response Interval (seconds), Robust count, and IGMP Version parameters are configurable when the Send Queries parameter is enabled.

3. Click on the Static Mcast Group tab to configure one or more static multicast groups. Otherwise, go to Step 26 .

4. Click Create. The Access Interface Igmp Snooping Mcast Group Display (Create) form opens.

5. Configure the required parameters.

6. Save the changes and close the form.

To configure MLD snooping for the interface:

1. Click on the MLD Snooping tab.

2. Configure the parameters in the General tab.

3. Click on the Static Mcast Group tab to configure one or more static multicast groups. Otherwise, go to Step 26 .

4. Click Create. The Access Interface Mld Snooping MCast Group Display (Create) form opens.

5. Configure the required parameters.

6. Save the changes and close the form.

To configure anti-spoofing filters for the interface:

1. Click on the Anti-Spoofing tab.

2. Configure the MAC Pinning parameter.

To specify QoS policy overrides:

1. Click on the Override Policy Items tab.

   Note: The Override Policy Items tab contains a number of tabs. However, the tabs that are displayed depend on the port type that you have chosen for this interface.

   • If you configured a non-HSMDA port, then the Access Ingress Queues, Access Egress Queues, Ingress Policer, and Egress Policer tabs are active.

   • If you configured an HSMDA port, then the Access Ingress Queues, Access Egress HSMDA Queues and Ingress Policer tabs are active.

2. See To configure QoS policy overrides on an L2 or L3 access interface for information about setting policy overrides.

To associate a MEP with the I-L2 Access interface:

1. Click on the OAM tab, then on the ETH-CFM tab.

2. Perform Step 9 to Step 16 in To create MIPs and MEPs on a VPLS L2 access interface .

To assign an ANCP policy to the interface:

1. Click on the ANCP Static Map tab.

2. Click Create. The ANCP Static Map (Create) form opens.

3. Configure the ANCP String parameter.

4. Select an ANCP Policy.

5. Save the changes and close the form.

Save the changes and close the forms.

End of steps