Creating a Point-to-Point ATM or TDM Pseudowire Service Order

Selecting the Service Definition

1. In the Network Activate task pane, select Service Provisioning > Manage Service Orders > Create P2P Service Order.

   The Create P2P Service Order page displays an inventory of all available point-to-point service definitions.

2. Select the service definition you want to base your service order on, and click Next.

   A graphical image of a service order appears.

   
   
   
   

   The image in the left panel of the main display area has multiple selectable elements. The right panel requests information depending on which element is selected.

   If a template was attached to the service definition on which the service order is based, the link to invoke the template editor also appears in the bottom of the right panel.

   The two router images represent the two endpoints of the point-to-point service. Text above the cloud image provides general information about the service. The cloud represents the connectivity across the network between the two endpoints.

   When you select the cloud or the text, the right panel requests general information about the service order as well as connectivity information.

   The General/Connectivity Settings panel appears initially in the right panel, as shown in the example.

Entering General/Connectivity Settings Information

The General Settings panel is displayed on the right side of the service order page.

To configure general settings in the General Settings/Connectivity Settings panel, provide the following information:

1. In the Name box, enter a unique name for the service.

   The service order name can consist of only letters, numbers, and underscores.

   Note

   The name you specify for a service order becomes the routing-instance name in the device configuration when you deploy the service. Consequently, you cannot use any Juniper Networks keywords, for example, “bgp” or “vpls”, as the name of a service order.

2. In the Customer box, select the customer requesting the service.

   If the customer is not in the list, you must add the customer to the database before proceeding. See Adding a New Customer.

3. In the Comments box, enter a description of the service. This description appears in information pages about the request or service instance created from the request.
4. In the Connectivity Settings box, specify the MTU for the connection across the network.

   The service definition can constrain the MTU to a specific value or allow the service provisioner to override it in the service order. In this example, the service definition sets the MTU, but allows the service provisioner to change the value.

   When you advance to the next step in creating your service order, your new connectivity settings appear under the Connectivity image in the main graphic and new general information is added to the text above the cloud. If you have incomplete or invalid information in the General/Connectivity Settings panel, a warning icon appears next to the cloud image.

5. Specify the virtual path identifier (VPI). This field is available only if you have selected an ATM point-to-point service definition.

   The combination of the VPI and VCID defines the next destination for a cell in the ATM network.

   Range: 0 through 255

6. Specify the virtual channel identifier (VCI). This field is available only if you have selected an ATM point-to-point service definition.

   Range: 0 through 65535

7. Enter the virtual circuit identifier (VCID). This integer uniquely identifies the virtual circuit that the service uses.

   The VCID can be set either automatically by the Junos Space software, or the service provisioner can set it manually in the service order. The service definition can force the system to pick the VCID, force the service provisioner to pick the VCID, or allow the service provisioner to override the settings in the service definition.

   We recommend allocating the VCID automatically; however, service providers with their own systems for allocating VCIDs can choose the manual setting.

   By default, the system picks a VCID from its pool automatically, but allows the service provisioner to override this value in the service order. The form expands to include an additional field for typing the VCID manually.

   This field is displayed only if the selected definition’s signaling type is LDP. You cannot edit this field if you have not selected the Editable in Service Order in the service definition.

8. Select the MC APS check box to add the run show aps extensive command.Note

   This check box is available only in an LDP-based point-to-point service order with PW Resilency enabled. The Interface type must be ATM/TDM.

   For more information on MC-APS, see Multi-Chassis Automatic Protection Switching Overview.

9. Enter the Route Distinguisher value.Note

   The IPv4 and IPv6 addresses that you use must be valid addresses. Refer to http://www.iana.org/assignments/ipv4-address-space for the list of restricted IPv4 addresses and http://www.iana.org/assignments/ipv6-address-space for the list of restricted IPv6 addresses.

   This field is displayed only if the selected definition’s signaling type is BGP. You cannot edit this field if you have not selected the Editable in Service Order in the service definition.

10. Specify the Route Target.

    1. Clear the Auto pick Route Target check box.

    2. Enter the Route Target value.

       Note

       The IPv4 and IPv6 addresses that you use must be valid addresses. Refer to http://www.iana.org/assignments/ipv4-address-space for the list of restricted IPv4 addresses and http://www.iana.org/assignments/ipv6-address-space for the list of restricted IPv6 addresses.

    This field is displayed only if the selected definition’s signaling type is BGP. You cannot edit this field if you have not selected the Editable in Service Order in the service definition.

11. Provide endpoint information for the first endpoint: click the Endpoint A graphic element or click Next.

    The Endpoint Settings form appears in the right panel.

Specifying Endpoint Information

On M Series, MX Series, and ACX routers:

• The ATM interfaces always appear as an AT interface.

• The TDM interfaces with SAToP encapsulation always appear as a T1 interface; TDM interfaces with CESoPSN encapsulation always appear as a DS interfaces.

The service templates settings are the same for both the endpoints.

1. In the PE Device box, select the N-PE device you want to use for the first endpoint.

   If you are unsure about which PE device to choose, go to the Prestaging Devices workspace landing page, which shows capacity information about UNIs on PE devices. You must pick a device that has available UNIs.

   This step is required for all service orders.

2. In the UNI interface box, select a UNI. The list includes all UNIs available on the selected device.

   You can enter the description of the UNI interface in the UNI description field.

   If you have selected the Enable Multi Segment Pseudowire check box in the service definition, the UNI interface of the second endpoint lists the interworking (iw) interfaces only.

   For more information on point-to-point pseudowire stitching, see Stitching Two Point-to-Point Pseudowires.

   This step is required for all service orders.

   You cannot change the type of Physical IF encapsulation. This value is set in the service definition.

   Based on the type of Physical IF encapsulation, the corresponding fields are displayed. For example, if the Physical IF encapsulation is CESoPSN, the following fields are displayed:

   • Jitter buffer

   • Idle pattern

   • Excessive packet loss rate

     Note

     These fields are editable if you have selected the Editable in Service Order check box in the service definition.

3. Specify the stitching unit.

   Default: 0

   Range: 0 through 255

   Note

   This field is displayed only in the second endpoint. You must have selected the Enable Multi Segment Pseudowire check box in the service definition.

4. If the Physical IF encapsulation type is CESoPSN, specify the Packetization Latency. Packetization latency is the time required to create packets.

   Range: 1000 through 8000 microseconds

   Note

   Based on the number of time slots, the default Packetization Latency value is as follows:

   • If the number of time slots is equal to 1, the default value is either 5000 microseconds or 8000 microseconds.

   • If the number of time slots is 2, 3, or 4, the default value is 4000 microseconds.

   • If the number of time slots is greater than 4, the default value is 1000 microseconds.

5. In the LSP tunnel name box, select the LSP tunnel you want to use for this device.

   You must supply an LSP tunnel name for the interface on BX devices. If one is not defined, you must first use the Transport Activate application to create an LSP on the BX7000 Gateway.

   On the M Series router, the LSP tunnel is chosen automatically.

   This field is displayed only if the selected definition’s signaling type is LDP.

6. Specify the cell bundle size. The value of the cell bundle size can be from 1 through 34.
7. If you have enabled the Enable PW Resiliency check box in the selected service definition, fill in the following fields in the Backup settings and Resiliency settings:

   • Enable

   • PE device

   • UNI interface

   • MTU (Bytes)

   • LSP tunnel name

   • Revert time (sec)

   • Switch Over Delay (sec)

   For more information of pseudowire redundancy, see Redundant Pseudowires for Layer 2 Circuits and VPLS.

8. If you selected the Static pseudowire check box in the selected service definition, you need to specify the Outgoing label for the static pseudowire.

   Range: 1000000 through 1048575

   In case of multi-segment pseudowire, you have to specify a new outgoing label for the second segment. The outgoing label for the second segment is not prepopulated from the first segment.

   Note

   You must manually compare the encapsulation, TDM bit rate, and control word of the router with the remote peer router and ensure that these parameters match; otherwise the static pseudowire might not work.

9. Select the Enable send-oam config check box to enable the send-oam command. You can select or clear this check box even in the Modify Service page.
10. If you have attached a service template in the service definition, the Flexible Service Attributes link appears. To enable this link, select a PE Device. Click the link to modify the service template attributes. For more information about configuring the flexible service attributes, see Configuring Flexible Service Attributes to Modify Service Template Attributes
11. Click Create.

    The service order that you have created is graphically represented in the topology. To view the service order that you have created in the topology, select Platform > Network Monitoring > Topology > Services > NA > service order name.

    For more information on topology, see Junos Space Network Topology Overview.

Deploying the New Service

1. Perform one of the following actions:

   • To save the request without deploying the service, select Save only, then click OK.

     See Deploying a Service Order for information about how to deploy a saved service at a later time.

   • To deploy the service immediately, select Deploy now, then click OK.

   • To deploy the service later, select Schedule deployment, select a date and time, then click OK.

     The time field specifies the time kept by the server, but in the time zone of the client.

2. To monitor the progress and status of the deployment, use the Jobs workspace. See Viewing Jobs in the Junos Space Network Application Platform User Guide for details.