Stitching a Pseudowire to an L3VPN Service
You can terminate a point-to-point pseudowire service into an existing Layer 3 VPN, thereby providing access to Layer 3 services. The benefit of the pseudowire stitching feature is that devices running on Layer 2 technology continue to function when networks are upgraded and Layer 3 technologies are used. In order to stitch Layer 2 services to one another and to Layer 3 services, Junos Space utilizes tunnel PICs to peer up a pseudowire and a Layer 3 VPN.
To stitch a pseudowire to a Layer 3 VPN service:
- Create a point-to-point service definition.
In the General tab, select the Enable PW access to L3 VPN network check box to enable pseudowire access to the Layer 3 VPN network.
For more information on creating a point-to-point service definition, see Creating a Point-to-Point Ethernet Service Definition.
- Create a Layer 3 VPN service definition.
For information about creating a full mesh Layer 3 VPN service definition, see Creating a Full Mesh Layer 3 VPN Service Definition. For information about creating a hub-and-spoke service definition, see Creating a Hub-and-Spoke (One Interface) Layer 3 VPN Service Definition.
- Create and deploy a Layer 3 VPN service order.
For information about creating a full mesh Layer 3 VPN service order, see Creating a Full Mesh Layer 3 VPN Ethernet Service Order. For information about creating a hub-and-spoke service order, see Creating a Hub-and-Spoke Layer 3 VPN Service Order.
- In the Manage Services inventory page, right-click a Layer
3 VPN service that you created and select Service > Extend PW Service.
The Extend PW Service inventory page lists the point-to-point service definitions that are enabled for Layer 3 access. This inventory page must also list the point-to-point service definition you created in Step 1.
- Select the point-to-point service definition and click Next.
- Create a point-to-point service order.
The stitched end of the point-to-point service is prepopulated with Layer 3 VPN service details.
The fields displayed in the point-to-point service order are based on the point-to-point service definition selected in Step 5. For example, in the point-to-point service definition, when pseudowire resiliency is enabled, then the Revert time (sec) and the Switch Over Delay (sec) fields are available in the service order.
You can select any one of the devices from the PE device field. Only the devices with logical tunnel interfaces are listed. These devices are associated with the Layer 3 VPN service.
Specify the following information in the PW Stitching box:
L3 routing instance name—Name of the Layer 3 routing instance
This field is prepopulated for a stitched end of the point-to-point service.
Autopick interface IP—If enabled, specify IP block size and IP address pool; otherwise specify the Interface IP address.
Autopick peer unit—To peer logical system unit number, select the check box; otherwise specify the Peer unit name.
For more information on creating a point-to-point service order, see Creating a Point-to-Point Service Order.
The Layer 3 VPN Service Details page now displays the PW Extension details.
When you perform a functional audit for a Layer 3 VPN service with pseudowire termination, by default the functional audit is applicable only to the Layer 3 VPN service. To perform a functional audit for the pseudowires, select the Include all extensions check box in the Schedule Functional Audit page.
For pseudowires, the functional audit is launched as a separate job.
Similarly, to perform a Force Deploy for the pseudowires, select the Include all extensions check box in the Schedule Force Deployment page.
You can view the details of the stitched pseudowire in the Functional Audit Results page.