To create a VLL L2 access interface on a terminating site

Prerequisites

If you are configuring access dual-homing with local switching over PBB tunnels, you must configure two L2 access interfaces. The L2 access interfaces can be on LAGs that participate in the MC LAG, or they can be just regular or Ethernet tunnel access interfaces.

If the Use SAP Backbone MAC Address parameter is enabled on both B-Sites:

  • MC-LAG access interfaces for the PBB Epipe local switching must be on IOM3 MDAs for the feature to work properly. There is no NFM-P or CLI validation.

  • Other access interfaces may be on IOM1 or IOM2 MDAs.

If you configure an L2 access interface on a PBB Epipe site you cannot configure a spoke SDP binding on the same site. They are mutually exclusive.

When you configure a 3-plus-tag Epipe service, only ports with QinQ encapsulation as one endpoint can be selected. When the other endpoint is an L2 access interface, you must choose a port with dot1q or QinQ encapsulation as the other L2 access interface. Both endpoints must be on the same site. See Epipe (Ethernet VLL) in VLL service management overview for more information. See To configure a spoke SDP binding on a VLL site and To create a VLL L2 access interface on a terminating site for additional configuration requirements for a 3-plus-tag Epipe service.

The parameters displayed may vary depending on the NE type or release.

Steps
 
1 

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

2 

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

3 

On the navigation tree, expand Site, right-click on L2 Access Interfaces and choose Create L2 Access Interface. The L2 Access Interface (Create) form opens.

For information on adding a GNE service interface to a VLL service, see To configure a GNE site on a VLL service .

4 

Configure the required parameters.

The ATM Connection Type parameter is configurable only in a VLL Apipe service that has the VC Type parameter set to ATM-cell.

The MC Ring Node and Hold Service Up On SAP Failure parameters are configurable only in a VLL Epipe service.

The Tunnel Fault Notification parameter is configurable on L2 access interfaces where the device has ports configured in access or hybrid mode with QinQ encapsulation. If you are configuring a tunnel facility MEP, this parameter must be set to Accept, in order to receive the fault notification from the tunnel facility MEP.

The Enable AIS parameter is configurable only in a VLL Epipe service where the device has ports configured in access or hybrid mode with QinQ encapsulation to forward AIS frames generated by a tunnel facility MEP.

5 

If you are creating a redundant L2 access interface, select an endpoint in the Redundancy panel.

6 
CAUTION 

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 port:

  1. Click on the Port tab.

  2. Select a port in the Terminating Port panel.

    Only ports in access or hybrid mode are listed. To choose a port that is not listed, you must set the Mode parameter for the port to Access or Hybrid. The port is then listed when you click Search.

    On Epipe L2 access interfaces, only PW ports that are bound to a service tunnel are listed. See To create an IP/MPLS service tunnel for information about how to create a service tunnel with a PW port binding.

    On Epipe L2 access interfaces, 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 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.

    When you configure a 3-plus-tag Epipe service, you must choose a port with QinQ encapsulation as one endpoint (SAP). When the other endpoint is an L2 access interface, you must choose a port with dot1q or QinQ encapsulation as the other L2 access interface. Both endpoints must be on the same site. See  Epipe (Ethernet VLL) in VLL service management overview for more information. See To configure a VLL site and To configure a spoke SDP binding on a VLL site for additional configuration requirements for a 3-plus-tag Epipe service.

    If you are configuring a port as a VLAN range SAP, you must choose a port with dot1q encapsulation type.

    If you choose an Ethernet tunnel endpoint, the form is refreshed and an Ethernet Tunnel tab is added.

    If you choose a port that is associated with a 7705 SAR MW link, the form is refreshed and a Microwave tab appears. See To configure a 7705 SAR MW link and To configure a 7705 SAR MW link member for more information about configuring a 7705 SAR microwave link and MW link member. If you are configuring microwave compression, see To configure microwave compression on an MW link SAP on a VLL L2 access interface .

    If you are configuring a 7705 SAR-8 or 7705 SAR-18 that has SCADA configured, you can add SCADA branches as SAPs to an Epipe or Cpipe service site. See To configure SCADA on a 7705 SAR for more information about configuring SCADA on a 7705 SAR.

  3. Configure the required parameters.

    When the selected port uses dot1q encapsulation, you can enable the Auto-Assign ID check box 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 parameter is configurable only when the port encapsulation type is QinQ.

    When you configure a 3-plus-tag Epipe service with L2 access interfaces as both endpoints, you must observe the following requirements:

    • One endpoint must be a QinQ SAP

    • The other endpoint must be a dot1q SAP or a QinQ SAP.

    • When the other endpoint is a dot1q SAP, the outer encapsulation value for the dot1q SAP must match the inner encapsulation value of the QinQ SAP that shares the L2 connection.

    • When the other endpoint is a QinQ SAP, the inner encapsulation values for both QinQ SAPs on the service must match.

    See  Epipe (Ethernet VLL) in this chapter for more information. See To configure a VLL site and To configure a spoke SDP binding on a VLL site for additional configuration requirements for a 3-plus-tag Epipe service

    The Outer Encapsulation Value (VPI) parameter is configurable only when the port encapsulation type is ATM.

    The Inner Encapsulation Value (VCI) parameter is configurable only when the port encapsulation type is ATM.

    The LLF Enabled parameter is configurable only for Epipe L2 access interfaces on ports with Null encapsulation.

    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.

    For Apipes, the Encapsulation Value parameter and the Encapsulation Value parameter are configurable only when the VC Type parameter is set to ATM-cell or ATM-VPC in Step 3 of To create a VLL service and the ATM Connection Type parameter is set to PVT in Step 4 of this procedure.

    For Apipes, the LLF Enabled parameter is configurable only for SAPs with “Port” ATM Connection Type and on a clear channel under 4 port OC3-STM1 ASAP MDA.

    For Apipes, the Connection Profile ID parameter is configurable only when the Signalling VC Type Override parameter is set to ATM-VCC or None. The Connection Profile ID parameter can only be associated with an Apipe when the VC Type parameter is set to ATM-cell.

  4. If you are creating an Epipe and use dot1q or QinQ encapsulation, you can enable ingress VLAN translation. Configure the required parameters in the VLAN Translation panel.

  5. For QTag Manipulation on the 7250 IXR, configure the parameters in the QTag Manipulation panel.

    For the Ingress Action parameter, when you select the Push Outer or Replace Outer option, the Outer Tag parameter is available. You must configure the Outer Tag parameter.

    If required, click Reset to restore the default values.

  6. For VLAN ranges on 7210 SAS Epipes, enable the VLAN Range SAP parameter and select a VLAN range.

    You can configure the VLAN Range SAP parameter only when the SAP Type parameter is set to dot1q-range. See Step 4 in To configure a VLL site .

    See Chapter 63, Connection profile policies for more information about VLAN ranges for the 7210 SAS. See To configure a VLAN range for a 7210 SAS VPLS or VLL Epipe service for information about how to create a connection profile with a VLAN range.

7 

If a VLAN Connection Profile policy was created and you want to use it for an Epipe service, configure the parameters in the VLAN Connection Profile panel on the Port tab. See Chapter 62, VLAN Connection Profile policies for details.

8 

To configure port redundancy for a Cpipe or Epipe service:

Port redundancy is configurable only on a 7705 SAR or 7750 SR.

  1. Enable the Enable Port Redundancy parameter on the Port tab.

  2. Configure the Off-Node Protection parameter in the Backup Port Information panel.

  3. If you enable the Off-Node Protection parameter, select the site that contains the backup port.

    Note:

    The site that you choose must be the same type and release of device as the site that you are configuring.

  4. Select the redundant port.

    Note:

    Only ports with the same encapsulation type as the currently assigned port are listed.

  5. Configure the required parameters.

  6. If you are creating a Cpipe L2 access interface, save the changes and close the form.

9 

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.

10 

To configure policy overrides for Epipe or Ipipe L2 access interfaces:

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, the Access Ingress Queues, Access Egress Queues, Ingress Policer, and Egress Policer tabs are active.

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

  1. Click on the Override Policy Items tab.

  2. Set the policy overrides, as described in To configure QoS policy overrides on an L2 or L3 access interface .

    To configure meter overrides on a 7210 SAS, see To configure QoS policy overrides on access ingress meters for the 7210 SAS . To configure queue overrides on a 7210 SAS, see To configure QoS policy overrides on access ingress queues for a 7210 SAS-X .

11 

To specify Ipipe functionality for Ipipe L2 access interfaces:

  1. Click on the IPIPE tab.

  2. Configure the required parameters.

    The MAC Address parameter, MAC Refresh Interval parameter, and Use Broadcast MAC Address parameters are configurable only when the port encapsulation type is dot1q, QinQ, or Null.

12 

To specify Epipe functionality for Epipe L2 access interfaces:

  1. Click on the Epipe tab.

  2. Configure the required parameters.

  3. Click on the following tabs to view or edit information:

    • General tab—displays the general Epipe properties

    • Port

    • OAM tab—create and execute service-specific diagnostic tests

    • QoS—configure the required parameters and select an Egress Remark policy, Egress VLAN QoS policy, and a Shared Policer policy, as required

    • Schedulers tab

    • ACL

    • Accounting

    • Virtual Port Name—configure the required parameters to assign a virtual port to the interface.

    • Security—configure the required parameters and select a DDoS protection policy

    • TCA

    • Deployment

    • Faults—displays the faults associated with the Epipe L2 access interface

13 

To assign an Application Profile to the spoke SDP binding:

  1. Click on the Application Assurance tab.

  2. Select an application profile string.

    You can select only local profiles on the NE.

  3. To associate a transit IP policy with an Epipe service object, select a transit IP policy in the Transit IP Policy panel.

    See To configure an AA transit IP policy for more information about how to configure a transit IP policy.

  4. To associate an AA transit prefix policy with the service object, select a transit prefix policy in the Transit Prefix Policy panel.

    See To configure an AA transit prefix policy for more information about how to configure a transit prefix policy.

  5. To associate an AA redundant protocol with an Epipe service object, select an AA redundant protocol in the AA Redundant Protocol panel.

14 

Save the changes and close the forms.

Note: If you are configuring access dual-homing with local switching over PBB tunnels, you must configure two L2 access interfaces. The L2 access interfaces must be on LAGs that participate in the MC LAG. See Chapter 43, MC LAG groups for information about MC LAGs.

End of steps