Stitching a Pseudowire to an IP Service
You can terminate an E-Line 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 an IP service:
- Create an E-Line service definition.
In the General page of the Create E-Line Service Definition wizard, select the Enable PW access to IP network check box to enable pseudowire access to the Layer 3 VPN network.
For more information on creating an E-Line service definition, see Creating an E-Line Service Definition.
- Create an IP service definition.
For information about creating a full mesh IP service definition, see Creating a Full-Mesh IP Service Definition. For information about creating a hub-and-spoke service definition, see Creating a Hub-and-Spoke (One Interface) IP Service Definition.
- Create and deploy an IP service order.
For information about creating a full mesh IP service order, see Creating a Full Mesh IP Service Order. For information about creating a hub-and-spoke service order, see Creating a Hub-and-Spoke IP Service Order.
- In Deploy mode of Service View, from the Manage Network
Services inventory page, select an IP service that you created and
select Extend PW Service from the Actions menu
The Extend PW Service inventory page lists the E-Line service definitions that are enabled for Layer 3 access. This inventory page must also list the E-Line service definition you created in Step 1.
- Select the E-Line service definition and click Next.
- Create an E-Line service order.
The stitched end of the E-Line service is prepopulated with IP service details.
The fields displayed in the E-Line service order are based on the E-Line service definition selected in Step 5. For example, in the E-Line 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 IP 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 E-Line 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 an E-Line service order, see Creating an E-Line Service Order.
The IP Service Details window now displays the PW Extension details.
When you perform a functional audit for an IP service with pseudowire termination, by default the functional audit is applicable only to the IP service. To perform a functional audit for the pseudowires, select the Include all extensions check box in the Schedule Functional Audit window.
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 window.
You can view the details of the stitched pseudowire in the Functional Audit Results window.