Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Creating a Point-to-Point Service Order

    To create a point-to-point service order, complete the following tasks in order:

    1. Selecting the Service Definition
    2. Entering General Settings Information
    3. Specifying the Connectivity
    4. Specifying QoS Settings
    5. Specifying OAM Settings
    6. Specifying Endpoint Information
    7. Specifying Connectivity and Endpoint Information for Managing VLANs
    8. Deploying and Monitoring the Progress of the New Service

    Selecting the Service Definition

    To select a service definition on which to base the new service order:

    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 part of the main display area has multiple selectable elements. The right panel requests information depending on which element is selected.

      If a template is 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 Settings Information

    To enter General Settings in the General Settings box:

    1. In the Name field, 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 VPLS 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 field, 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 field, enter a description of the service that you want to appear in the request or in a service instance created from the request.

      This description is displayed in the Manage Service Order page.

    4. Configure connectivity settings. See Specifying the Connectivity.

    Specifying the Connectivity

    In the Connectivity Settings box of the General/Connectivity Settings panel, specify VCID and MTU information.

    1. Specify the VCID. This is an integer that uniquely identifies the virtual circuit that the service will use.

      The VCID can be either set automatically by the Junos Space software, or it can be set manually by the service provisioner 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.

      This field is displayed only if the selected definition’s signaling type is LDP. You cannot edit this field if you have not selected Editable in Service Order 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.

      In the previous example, by default, the system picks a VCID from its pool automatically, but allows the service provisioner to override this value in the service order. Clear the check box to override the service definition setting. The form expands to include an additional field for entering the VCID manually.


    2. 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.

    3. Select the MC LAG check box if you want the following configuration to be pushed to the selected endpoint.
      set protocols l2circuit neighbor x.x.x.x interface interface name pseudowire-status-tlv

      Note: This check box is available only for an LDP-based point-to-point service order with PW Resilency enabled. The Interface type must be Ethernet.

      For more information on multichassis link aggregation groups (MC-LAGs), see Multichassis Link Aggregation Group Overview.

    4. Specify 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 check box in the service definition.

    5. To specify the Route Target, clear the Auto pick Route Target check box.

      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 check box in the service definition.

    6. The VLAN normalization displays the information based on the option you have selected in the service definition.
    7. If VLAN normalization is Normalize to Dot1q tag, specify the VLAN Tag to stack.

      Default: 1

      Range: 1 through 4094

    8. If VLAN normalization is Normalize to QinQ tags, specify the Outer VLAN Tag to stack and Inner VLAN Tag to stack fields.

      Default: 1

      Range: 1 through 4094

    9. To 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.

    10. If you have enabled QoS, configure QoS settings. See Specifying QoS Settings.

      If QoS is not enabled, configure endpoint settings. See Specifying Endpoint Information.

    Specifying QoS Settings

    If QoS is enabled on the service definition, configure the QoS Settings of the General/Connectivity Settings panel.




    1. In the QoS profile field, select a profile from the list.

      The QoS profile list displays the QoS profiles that are currently configured in the QoS Design software.

      A QoS profile classifies traffic into defined service groups to provide the special treatment of traffic across the network service.

      Note: For OAM Settings, if you specify a CFM profile (for example, a CFM action profile with remote MEP), or an SLA-Iterator profile, first you must ensure that the profile is attached to the same device upon which you intend to deploy the P2P service order. If the profile is not previously attached (using the OAM Insight application), it is not on the device to support the service order.

    2. In the CIR field, select the committed information rate (CIR) from the list.

      The CIR is the guaranteed rate and specifies the minimum bandwidth available if all sources are active at the same time. Make sure that the CIR value is less than the PIR value.

      Note: For bursty traffic, the CIR represents the average rate of traffic per unit time and the PIR represents the maximum amount of traffic that can be transmitted in a given interval.

    3. In the PIR field, select the peak information rate (PIR) from the list. The PIR is the shaping rate.

      Note: If the QoS profile that you selected in Step 1 is configured with a level-three scheduler and interface oversubscription is enabled, then PIR is not used.

    4. Configure endpoint information. See Specifying Endpoint Information.

    Specifying OAM Settings

    If OAM is enabled on the service definition, enter information in the OAM Settings of the General/Connectivity Settings panel.

    1. In the CFM Definition field, select a profile from the list.

      Note: For OAM Settings, if you specify a CFM profile (for example, a CFM action profile with remote MEP), or an SLA-Iterator profile, first you must ensure that the profile is attached to the same device upon which you intend to deploy the P2P service order. If the profile is not previously attached (using the OAM Insight application), it is not on the device to support the service order.

      Note: For Juniper Networks PTX3000 Packet Transport Routers, if you attach a CFM Definition to the service order, the CFM session operates for MEPs in either the Up or Down direction when the service is deployed.

    2. Configure endpoint information. See Specifying Endpoint Information.

    Specifying Endpoint Information

    An example Endpoint Settings window follows.



    If a service template is attached to the service definition, a link to that template is listed at the bottom of the Endpoint Settings section of the window. The service templates settings are same for both the endpoints. For instructions on working with service templates in service orders, see Creating a Service Order Based on a Service Definition with a Template.

    Some of the fields differ from one interface type to another and also differ depending on permissions assigned in the service definition.

    To specify endpoint information:

    1. In the PE device field, 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.

      Note: If this endpoint is a third-party device, select Unmanaged device from the PE Device field list. You need to specify only the IP Address and Unmanaged Interface. For more information, see Provisioning a Single-Ended Point-to-Point Service.

    2. In the UNI interface field, select a UNI.

      The list includes all UNIs available on the selected device.

      This step is mandatory for all service orders.

      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.

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

    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. In the Traffic type field, designate whether you want the service to transport all traffic, a single VLAN, or multiple VLANs.

      Although this field is present for all service orders, the value is predetermined for some types of interfaces. For example, a port-to-port interface always transports all traffic. Moreover, for interface types that do support multiple traffic types, you can select this value only if the service definition allows you to do so.

      If you are allowed to select this field, depending on the interface type, you can choose from the following values:

      • Transport single VLAN
      • Transport VLAN range
      • Transport all traffic

      Note: The Physical IF encapsulation and Logical IF encapsulation fields are not selectable. These values are set in the service definition.

      The Vlan Range for manual input field displays the VLAN range that is specified in the service definition.

      If the Ethernet option is do1q or qinq, and the VLAN selection is Transport single vlan type, the Vlan Range for manual input range is used for validation of manually entered VLAN.

      If the Ethernet option is qinq, and the VLAN selection is Transport vlan range type, the Vlan Range for manual input range is used for validation of manually entered outer VLAN.

      If the Ethernet option is do1q, and the VLAN selection is Transport vlan range type, the Vlan Range for manual input range is used for validation of manually entered customer's VLAN start and VLAN end.

    5. In the C-VLAN ID field (or VLAN ID field), enter the customer’s VLAN ID.

      This field is mandatory for service orders that transport a single customer VLAN. The ID is provided by the customer.

    6. In the C-Vlan Start and C-Vlan End fields, specify the beginning and end of the range of customer VLANs that you want the service to transport.

      This field is mandatory for all services that transport a specific range of customer VLANs. These VLAN IDs are provided by the customer.

    7. Select the Auto pick VLAN ID check box to have the system choose a service VLAN ID automatically.

      This field is present only for interface types that provide double tagging; that is, only for Q-in-Q endpoint interface types. If this field is not set, then you must enter a service VLAN ID manually.

    8. In the VLAN ID field, specify the service VLAN ID that you want be used to provide the outer tag for the service.

      This field is present only for interface types that provide double tagging, and only if the Auto pick VLAN ID check box is not selected.

    9. Specify whether the Autopick UNIT ID can be selected automatically or manually.
      • To assign the UNIT ID automatically, select the Autopick UNIT ID check box.
      • To assign the UNIT ID manually, clear the Autopick UNIT ID check box.

        The window expands to include the UNIT ID field. In the UNIT ID field, type a value.

        Range: 1 through 1073741823

      Note: You can edit this field only if you have selected the Editable in Service Order check box for the VLAN ID selection in the service definition.

    10. In the MTU (Bytes) field, specify the maximum transmission unit size for the UNI.

      This field is present in all service orders. However, you can set this field only if the service definition allows you to do so.

    11. 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.

    12. In the Bandwidth (Mbps) field, select a value from the list to limit the bandwidth of the service you are creating.

      This field is present only if bandwidth limiting is allowed by the service definition, and is configurable in the service order only if the service definition allows you to do so.

      When you click another graphic element in the main graphic area, the selected device name and interface name appear beneath the endpoint image in the main graphic.

    13. To change the committed information rate (CIR) on an endpoint, click the CIR value for the endpoint and select another value from the list. Make sure the CIR value is less than the PIR value.

      Only QoS-enabled services specify CIR and PIR values.

    14. To change the peak information rate (PIR) on an endpoint, click the PIR value for the endpoint and select another value from the list. Make sure the CIR value is less than the PIR value.

      Only QoS-enabled services specify CIR and PIR values.

    15. If you have enabled the Enable PW access to L3 VPN network check box in the selected service definition, fill in the following fields in PW Stitching:
      • L3 routing instance name—Specify the name of the Layer 3 routing instance.
      • Autopick interface IP—If this field is enabled, specify IP block size and IP address pool; otherwise specify the Interface IP address.
      • Autopick peer unit—To select the logical system unit number automatically, select the check box; otherwise specify the Peer unit name.

      Note: These fields are available only if you have selected an LT interface in the UNI interface.

    16. 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.

    17. Select the Enable send-oam config check box to enable the send-oam command. You can enable or disable this check box even in the Modify Service page.
    18. 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.
    19. To provide endpoint information for the second endpoint, click the Endpoint Z graphic element (or click Next).

      The Endpoint Settings form appears in the right panel for the second endpoint. Complete this form as for the first endpoint (repeat Step 1 through Step 18).

    20. Click Create.

      The deployment options window appears.

      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 > Service > NA service order name.

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

    Specifying Connectivity and Endpoint Information for Managing VLANs

    The Network Activate application in Junos Space release 14.1 provides greater flexibility for provisioning VLANs for Point-to-Point service orders.

    Network Activate release 14.1 extends the VLAN normalization options.

    Note: Prior to release 14.1, Network Activate enabled specification of the VLAN normalization types Swap and Normalize to None only.

    You can create logical interfaces that define both the Outer-VLAN-tag-to-stack protocol ID and Inner-VLAN-tag-to-stack protocol ID. The following illustration shows the General/Connectivity window. The Connectivity Settings panel displays the Outer-VLAN-tag-to-stack and Inner-VLAN-tag-to-stack parameters.



    Network Activate now enables you to manually select a value for the Outer VLAN tag to stack and Inner VLAN tag to stack parameters for a service that specifies the qinq Ethernet option.

    The following illustration displays the service order Connectivity Settings based upon a service definition that set the VLAN normalization parameter to Normalize to Dot1q tag.



    For service orders that are based on service definitions that set the Ethernet option to dot1q or qinq, the Unit ID parameter appears in the Logical IF Settings panel in the service order Endpoint Settings window.


    Deploying and Monitoring the Progress of the New Service

    To deploy 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.

    Modified: 2017-02-15