Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Creating a Service Definition for E-Line Pseudowire Access into a Layer 3 VPN

Creating a pseudowire between two terminating PE devices allows you to encapsulate traffic from the Layer 2 VPN into a Layer 3 VPN, thereby providing access to Layer-3 services. Also known as pseudowire stitching, the benefit of this feature is that devices running older technologies will continue to function when networks are upgraded and Layer-3 technologies are in play.

To use this feature, the following prerequisites must be met:

  • An existing Layer 3 VPN must be used as the target VPN.

  • A device with an LT interface must be used to create the pseudowire.

To create the pseudowire, in the Network Services > Connectivity view pane, select Service Design > New > E-Line Service Definition.

  1. Define the general settings for the service definition.

    Field

    Action

    Name

    Provide a name for the service definition.

    Service type

    The service type is E-Line pseudowire

    Comments

    Enter any comments that will help describe the service definition and its purpose.

    Interface type

    Specify the type of interface as Ethernet. Also check the box to enable pseudowire access into the Layer 3 VPN network.
  2. Click Next to display the Connectivity window.

    Field

    Action

    VC ID selection

    Choose from Auto pick or Select Manually for VC ID assignment.

    Default MTU (Bytes)

    Indicate the MTU size or use the default that appears in the field.
  3. Click Next to display the Site Settings window.
  4. Define the UNI settings for the service definition. This definition can be created as a port-to-port or 802.1q link. This procedure shows the port-to-port Ethernet settings.

    Site Settings Field

    Action

    Traffic Treatment Settings

    Ethernet option

    Indicate the Ethernet option to use for this E-Line service definition. Choices are port-port or dot1q.

    Customer traffic type

    This field can be left blank.

    VLAN ID selection

    This field can be left blank.

    Interface Settings

    Physical IF encapsulation

    The interface encapsulation for the port-to-port link must be specified as ethernet-ccc.

    Logical IF encapsulation

    This field is not used.

    MTU Settings

    Default MTU (Bytes)

    This field is populated with the default MTU value of 1522. If you are not using the default value, enter the MTU value in bytes.

    MTU range (Bytes)

    If you are specifying a custom MTU value, indicate the range of values in bytes.

    If you are creating an 802.1q link, use the following settings:

  5. Click Finish and then create the service order.
    Note:

    On the Review page, in the Service Templates section, the names of the service templates with which the service definition is associated are displayed. The Default Service Template column indicates whether the attached template is the default template.

Related Documentation