Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Creating a Point-to-Multipoint VPLS Service Order

 

The Network Activate software implements point-to-multipoint Ethernet services as virtual private LAN (VPLS) services. These services are also referred to as hub-and-spoke services.

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

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 VPLS Service Order.

    The Create VPLS Service Order page displays a filtered inventory view of only those published service definitions that are designed to work with multipoint Ethernet services. You can select the service definition based on the signaling type.

  2. Select the point-to-multipoint service definition you want to base your service order on and then click Next.

    The Enter Order Information page appears.

Entering General Settings Information

This part of the create point-to-multipoint Ethernet service order procedure sets general information about the service order in the General Settings box of the Enter Order Information page:

To specify general settings information:

  1. In the Name field, type a unique name for the point-to-multipoint 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, type a description of the service. This description appears in information page about the request or service instance created from the request.

    You cannot select the Customer traffic type. Its value is set in the service definition.

    You cannot change the Signaling type in the service order.

    The following check boxes are displayed based on the service definition you have selected:

    • Enable PW Extension

    • Enable PW Resiliency

    • Allow access to L3 network

    You cannot change these check boxes in the service order.

  4. If QoS is enabled, continue with "Specifying QoS Settings," next. Otherwise skip to "Setting Attributes for all Endpoints."

Configuring Connectivity Settings

In this procedure, you specify the attributes that define the connectivity among remote sites across the service provider network and the service security. The following illustration is a sample Connectivity page.

To configure connectivity settings for connectivity between sites across the network:

  1. Specify whether the route distinguisher can be selected automatically or manually.Note

    You cannot edit the route distinguisher if you have not selected the Editable in Service Order check box in the service definition.

    • To assign the route distinguisher automatically, select the Autopick Route Distinguisher check box.

    • To assign the route distinguisher manually, clear the Autopick Route Distinguisher check box.

      If you choose to assign the route distinguisher manually, the page expands to include the Route distinguisher field. In the Route distinguisher field, type a value. Junos Space accepts either of the following two formats:

      • prefix-number: assigned-number

        Where prefix-number can be any numeric value from 1 through 65,535, and assigned-number can be any numeric value from 0 through 2,147,483,647

      • IPV4-address: assigned-number

        Where IPV4-address can be any valid IPv4 address, and assigned-number can be any numeric value from 0 through 65,535

    Note

    The Route distinguisher field is available in either of the following cases:

    • The Signaling type is BGP.

    • The Signaling type is LDP and Auto Discovery is enabled.

  2. Specify whether the route target can be selected automatically or manually.Note

    You cannot edit the route target if you have not selected the Editable in Service Order check box in the service definition.

    • To assign the route target automatically, select the Autopick Route target check box.

    • To assign the route target manually, clear the Autopick Route target check box.

      If you choose to assign the route target manually, the page expands to include the Route Target field. In the Route Target field, type a value. Junos Space accepts either of the following two formats:

      • prefix-number:assigned-number

        Where prefix-number can be any numeric value from 1 through 65,535, and assigned-number can be any numeric value from 0 through 2,147,483,647

      • IPV4-address:assigned-number

        Where IPV4-address can be any valid IPv4 address, and assigned-number can be any numeric value from 0 through 65,535

    Note

    The Route Target field is available in either of the following cases:

    • The Signaling type is BGP.

    • The Signaling type is LDP and Auto Discovery is enabled.

  3. In the Revert time (sec) field, specify the revert time for redundant Layer 2 circuits and VPLS pseudowires.

    Default: 5 seconds

    Range: 0 through 65,535 seconds

    This field is available only if you have enabled the Enable PW Resiliency check box in the selected service definition.

  4. In the Switch Over Delay (sec) field, specify the time to wait before the backup pseudowire takes over.

    Default: 0 seconds

    Range: 0 through 180 seconds

    This field is available only if you have enabled the Enable PW Resiliency check box in the selected service definition.

  5. Continue with specifying the QoS settings.

You can edit the VPLS ID field, if you have selected the Select manually option for the VPLS ID field in the service definition.

The Auto Discovery and Autopick VPLS ID fields appears dimmed in Connectivity Settings dialog box. These fields are not editable in the service order.

Specifying QoS Settings

If QoS is enabled in the service definition, enter information in the QoS Settings box.

Note

QoS features appear in the Junos Space user interface only if you deploy the QoS Design application in Junos Space.

  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.

  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. The value for CIR should be less than the value for PIR.

    Note

    For bursty traffic, the CIR represents the average rate of traffic per unit time, and the peak information rate (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.

Specifying OAM Settings

To enable OAM 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 will not be present on the device to support the service order.

    Note

    For Juniper Networks PTX3000 Packet Transport Routers and Junos Space Release 13.1P1, if you attach a CFM Definition to the service order, the CFM session will operate for MEPs in either the Up or Down direction when the service is deployed.

  2. Continue with "Specifying Endpoint Information," next.

Setting Attributes for All Endpoints

This part of the create multipoint Ethernet service order procedure sets the attributes that are usually common for all endpoints in the service.

If a template was attached to the service definition on which the service order is based, the link to invoke the template editor appears on the Endpoint Settings page.

The values that you type varies, depending on the service definition on which the service order is based. Follow the steps in one of the following tasks, depending on whether or not the service provides flexible VLAN tagging. To create a service with flexible VLAN tagging, the service definition that you selected for the service order must include the Ethernet option asymmetric tag depth in the UNI settings step.

If there is a service template attached to the service definition, there is a link to that template at the bottom of the Endpoint Settings section of the page. For instructions on working with service templates in service orders, see Creating a Service Order Based on a Service Definition with a Template.

Setting Attributes for Endpoints on a Service

If these attributes are not the same on all endpoints, you can set them to be the same for now and then make changes later, or you can choose to skip this step and apply the attribute values one at a time later.

This procedure sets the attributes listed in the End Point Settings box of the Enter Order Information page. The attributes shown depend on the interface type and the signaling type. The following example shows the endpoints settings box for a point-to-multipoint service order with Q-in-Q interfaces, transporting a VLAN range.



Note

When the Allow multihoming check box is selected for the service definition on which the service order based, the End Point Settings box displays the Allow multihoming on endpoints check box to indicate that the service can include multihomed groups.

To set attributes common to most endpoints:

  1. In the Bandwidth 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 it.

  2. In the MTU field, type 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 it.

    The Auto-pick VLAN range constraint field is displayed and validates the VLAN range specified in the service definition.

  3. If Autopick VPLS ID is disabled, specify the VPLS ID.

    Range: 1 through 2147483647

    Note

    If the signaling type is LDP and if auto discovery is enabled, Autopick VPLS ID appears dimmed. This field is not editable in the service order.

    If the signaling type is BGP, Autopick VPLS ID is not available.

  4. If Autopick VPN ID is enabled, specify the VPN ID.

    Range: 1 through 65535

    Note

    If the signaling type is LDP and if auto discovery is enabled, Autopick VPN ID appears dimmed. This field is not editable in the service order.

    If the signaling type is BGP, Autopick VPN ID is not available.

  5. In the Customer VLAN Range Start and Customer VLAN Range End fields, type the first and last VLAN ID of the range of customer VLANs to be transported over the network.

    These fields are present only for services with UNIs that have Q-in-Q interface types and allow a range of VLANs to be transported.

  6. In the VLAN Tag to stack field, type a value for the customer VLAN.

    This field is present only for services that specify Normalize to Dot1q tags.

  7. In the Inner VLAN Tag (for QinQ) field, type a value to provide a default inner VLAN tag for the UNI endpoints.

    This field is present only for services that specify Normalize to QinQ tags.

  8. In the Outer VLAN Tag to Stack field, type a value to provide an outer VLAN tag that matches the Outer VLAN tag of at least one of the UNI endpoints.
  9. In the Inner VLAN Tag to Stack field, type a value to provide a default inner VLAN tag for the UNI endpoints to provide a common inner VLAN tag for the routing instance.

    This field is present only for services that specify Normalize to QinQ tags.

  10. The LDP PW Extension Settings field is available only if you have enabled the Enable PW Extension check box in the selected service definition.

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

  11. Specify the Logical If Settings:Note

    The Logical If Settings box is not available if you have selected the Ethernet option as Port.

    • 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 page 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.

    • Specify whether the Autopick VLAN ID can be selected automatically or manually.

      • To assign the VLAN ID automatically, select the Autopick VLAN ID check box.

      • To assign the VLAN ID manually, clear the Autopick VLAN ID check box.

        The page expands to include the VLAN ID field. In the VLAN ID field, type a value.

  12. Click Next.

    The Select Endpoint PE Devices page appears.

  13. Continue with "Selecting N-PE Devices and Multihomed Groups."

Setting Attributes for Endpoints on a Service with Flexible VLAN Tagging

A service with flexible VLAN tagging can include port-based, 802.1Q, and Q-in-Q interfaces.

If these attributes are not the same on all endpoints, you can set them to be the same for now and then make changes later, or you can choose to skip this step and apply the attribute values one at a time later.

This procedure sets the attributes listed in the End Point Settings box of the Enter Order Information page. The attributes shown depend on the signaling type and interface type. The following example shows the endpoints settings box for a point-to-multipoint service order that specifies a service with flexible VLAN tagging that is normalized to Dot1Q and transports a single VLAN.



Note

When the Allow multihoming check box is selected for the service definition on which the service order based, the End Point Settings box displays the Allow multihoming on endpoints check box to indicate that the service can include multihomed groups.

To set attributes common to most endpoints:

  1. In the Bandwidth 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 can be configured in the service order only if the service definition allows it.

  2. In the MTU field, type 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 it.

  3. If the signaling type is LDP and the if the auto discovery is enabled, the Autopick VPN ID appears dimmed. This field is not editable in the service order,
  4. Specify the VPLS ID if the Autopick VPLS ID is disabled.

    Range: 1 through 2147483647

  5. Specify the VPN ID if the Autopick VPN ID is enabled.

    Range: 1 through 65535

  6. The LDP PW Extension Settings is available only if you have enabled the Enable PW Extension check box in the selected service definition.
  7. To configure VLANs, choose from the following options depending on the VLAN transport type and Normalization that the service specifies:
    • If the service transports single VLANs and traffic is Normalized to Dot1Q tag:

      1. In the Inner VLAN (for Q-in-Q) field, type a VLAN ID to swap.
      2. In the VLAN Tag to stack field, type a VLAN ID to push or swap at the relevant UNI endpoints.
    • If the service transports single VLANs and traffic is Normalized to QinQ tags:

      1. To manually assign an VLAN ID:
        1. Clear the Autopick VLAN ID check box. The page expands to include the VLAN ID field.

          This field is present in the service order only if the service definition allows it.

        2. In the VLAN ID field, type a value.

          This field is configurable in the service order only if the service definition allows it.

      2. In the Inner VLAN (for Q-in-Q) field, type a VLAN ID to swap.
      3. In the Outer VLAN Tag to stack field, type a VLAN ID to push or swap at the relevant UNI endpoints.
      4. In the Inner VLAN Tag to stack field, type a VLAN ID to push or swap at the relevant UNI endpoints.
    • If the service transports single VLANs and traffic is Normalized to VLAN none:

      • In the Inner VLAN (for Q-in-Q) field, type a VLAN ID to swap.

    • If the service transports all traffic and specifies Normalize to VLAN all:

      1. In the Customer VLAN Range Start and Customer VLAN Range End fields, type the first and last VLAN ID of the range of customer VLANs to be transported over the network.
      2. In the VLAN Tag to stack field, type a VLAN ID to push or swap at the relevant UNI endpoints.
    • If the service transports a range of VLANs and specifies Normalized VLAN all:

      1. In the Customer VLAN Range Start and Customer VLAN Range End fields, type the first and last VLAN ID of the range of customer VLANs to be transported over the network.
      2. In the VLAN Tag to stack field, type a VLAN ID to push or swap at the relevant UNI endpoints.Note

        A service that transports of a range of VLANs and specifies Normalized VLAN all allows only 802.1Q, and Q-in-Q interfaces for the UNI endpoints.

  8. Click Next.

    The Select Endpoint PE Devices page appears.

  9. Continue with "Selecting N-PE Devices and Multihomed Groups," next.

Selecting N-PE Devices and Multihomed Groups

This part of the create point-to-multipoint Ethernet service order procedure selects the N-PE devices and, optionally, multihomed groups that hosts the service endpoints. The selection is made from the Select Endpoint PE devices page.

Note

If multihoming is enabled on the service definition on which the service order is based and you have configured and imported the connectivity file, you can select PE devices and multihomed groups that are specified in the multihomed groups connectivity file for the service endpoints.

Note

The Select Endpoint PE devices page shows only assigned N-PE devices that have an AS number configured. If you do not see the device you are looking for, use the CLI on the device to check for and assign an AS number.

To select endpoint N-PE devices and multihomed groups:

  1. In the Select Endpoint PE devices page, select the devices and multihomed groups that you want to participate in the service. Use the multiple selection feature to select one or more devices.
  2. Click Next.

    The Endpoint Settings page appears.

Selecting Hubs and Modifying Endpoint Settings

This part of the create point-to-multipoint Ethernet service order procedure selects the devices that are service hubs and sets the attributes for each endpoint in the service. Selection is made using the Endpoint Settings page.

This page shows one endpoint for each device that you selected from the Select Endpoint PE devices page, as described in Selecting N-PE Devices and Multihomed Groups.

The interface shown in the UNI Interface field is automatically selected by the Network Activate software, which chooses the UNI that has the highest available capacity among interfaces that are in the Up state. To calculate the available capacity of the interface, the system subtracts the bandwidth reserved for each service deployed on that interface from the total capacity of the interface.

For each endpoint, the Endpoint Settings page shows the value for each UNI attribute.

  • For port-to-port services, the displayed values are for Bandwidth and MTU.

  • For 802.1Q UNIs, the displayed attributes are for Bandwidth, Autopick VLAN ID, VLAN ID, and MTU.

  • For Q-in-Q UNIs, the displayed attributes include Bandwidth, AutoPick VLAN ID, and VLAN ID. For a service with Q-in-Q UNIs that specifies a customer VLAN range, the displayed attributes also include C-VLAN ID Start and C VLAN End.

The values shown are initially the values you set earlier on the Enter Order Information page, as described in Setting Attributes for Endpoints on a Service.

To modify the endpoint settings:

  1. For a service with flexible VLAN tagging, set the interface type in the Ethernet Option column for each endpoint in the service.
  2. To select a hub, choose the device you want to serve as a hub and, above the device name, select Hub. The Neighbor Hub link is not applicable for hub devices.

    To provide a higher level of availability, you can select multiple hubs.

  3. To fill in the neighbor hub details for a spoke device, click the Neighbor Hub link. The Neighbor Hub Setting page is displayed.

    For spoke devices you can update the Neighbor Hub details only if:

    • The Signaling type is LDP and the Auto discovery check box is disabled

    • The Signaling type is BGP and the Enable PW Extension check box is enabled

    Fill in the following information:

    • Enable P2P-Spoke—If selected, the spoke acts as a stitched point-to-point pseudowire. This check box is available only if you have enabled the Enable PW Extension in the selected service definition. If you have added more than one UNI interface for a spoke device, you cannot select this check box.

    • NeighborHub—Select the neighbor hub device from the list. If the Signaling type is BGP, enable the Enable P2P-Spoke check box to select the neighbor hub.

    • Backup neighbor—Select the backup neighbor hub device from the list. This field is available if the Enable PW Resiliency check box is enabled in the selected service definition. If the Signaling type is BGP, enable the Enable P2P-Spoke check box to select the backup neighbor.

      Note

      You cannot select the same device for NeighborHub and Backup neighbor.

    • PW-Hub Connectivity name— If the Signaling type is BGP and if you have enabled the Enable P2P-Spoke check box, select or type the mesh group name from other pseudowire spoke.

      Range: 1 through 32 characters

      If the Signaling type is LDP, the pseudowire-hub connectivity name is auto generated.

    • Auto pick VC ID—This field is available if the Signaling type is BGP and if you have enabled the Enable P2P-Spoke.

      If the Signaling type is LDP, the VPLS ID of the routing instance is used.

    • VC ID—If the Signaling type is BGP and if you have enabled Enable P2P-Spoke, specify the VC ID.

      You can also modify the VCID field in the Modify Service Order page.

      Range: 1 through 2147483647

      If the Signaling type is LDP, the VPLS ID of the routing instance is used.

  4. To select a different UNI on a device, on the Endpoint Settings page, click the UNI name you want to change and choose another interface from the list.

    Modified values are indicated by a small red triangle in the corner of the table cell.

  5. To enter the description for an UNI interface, click the corresponding Description cell.
  6. To change the bandwidth on an endpoint, click the bandwidth value for the endpoint and select another value from the list.
  7. To change the committed information rate (CIR) on an endpoint, click the CIR value for the endpoint and select another value from the list. The value for CIR should be less than the value for PIR.

    Only QoS-enabled services specify CIR and PIR values.

  8. To change the peak information rate (PIR) on an endpoint, click the PIR value for the endpoint and select another value from the list. The value for PIR should be greater than the value for CIR.

    Only QoS-enabled services specify CIR and PIR values.

  9. The AutoPick UNIT ID and the UNIT ID columns appear, if you have not selected the Ethernet option as port-to-port.
    • To change an automatically selected service UNIT ID to manual selection, clear the AutoPick UNIT ID check box, and type a service UNIT ID value in the UNIT ID field.

    • To change from manual selection to automatic selection, select the AutoPick UNIT ID check box.

    • To change the value of a manually selected service UNIT ID, type a new value in the UNIT ID field.

      Note

      The unit ID value that you have specified in the Enter Order Information page is displayed in the UNIT ID field.

  10. For Q-in-Q interface endpoints, you can change how the service VLAN ID is selected:
    • To change an automatically selected service VLAN ID to manual selection, clear the AutoPick VLAN ID check box, and type a service VLAN ID value in the VLAN ID field.

    • To change from manual selection to automatic selection, select the AutoPick VLAN ID check box.

    • To change the value of a manually selected service VLAN ID, type a new value in the VLAN ID field.

  11. For Q-in-Q interface endpoints with customer VLAN ranges specified, you can also change the range limits for an endpoint.
  12. For 802.1Q interface endpoints, you can change the customer VLAN ID.
  13. To change the MTU for the UNI, click the value in the MTU field and type a new value.
  14. To add a UNI on a selected device, select Add UNI Interface in the Action column, and then select the interface you want from the UNI interface list.

    You can add only one UNI interface for the point-to-point spoke device. If more than one UNI interface exists for a spoke device, you cannot select the Enable P2P-Spoke check box in the Neighbor Hub link.

  15. If the interface you selected in the previous step is already configured (duplicate) you must either type a different value in the service VLAN ID field manually, or select the Autopick VLAN ID check box.
  16. To delete a UNI from a device, in the Action column, click Delete UNI Interface.

    If the deleted UNI is the only UNI selected from the device, then the device is deleted from the service configuration.

    If a hub device is neighbor of a point-to-point spoke device, you cannot delete the device. To delete such device, you must delete the point-to-point spoke device, or change the point-to-point spoke to VPLS spoke.

  17. To enter the value of Outgoing Label for any device, click the Add Label link that is associated with that device. You can enter the value in the Outgoing Label Settings page and click OK to save the value. Select the hub and spoke devices in the Endpoint Settings page.
  18. To view the values of the Incoming Label, Outgoing Label and the Neighboring Device of any device, use the following method:
    1. Select Manage Service Orders > View Service Order Details

    2. Click the Label Details link associated with any device.

    Note

    When the signaling type is BGP and the service type is Point-to-Multipoint Ethernet VPLS, the Label Details link is not available under the Endpoint Settings link when you create or modify a service order. In the Endpoint Settings page, you need to select the devices that are going to act as hub because some devices act as hub and some act as spoke when the service type is Point-to-Multipoint. Now click the Neighbor Hub link that is associated with the devices acting as spokes. The Neighborhub Setting page that appears for the selected spoke device allows you to enter the details of the outgoing label values of P2P-Spokeand neighbor hub. The page displays details about the Neighborhub device, the Backup Neighborhub device, Hub Connectivity Name and VC ID. To specify and view these details, you need to select the Enable P2P-Spoke checkbox. If the Enable P2P-Spoke checkbox is not selected, you cannot specify any of these values.

  19. To specify a different primary device for a multihomed group in the service:

    1. From the list of secondary devices, select a secondary device that you want to specify as the primary device in the multihomed group.
    2. Click Set As Primary.
    3. Click Create.

      The secondary device is configured as the primary device in the multihomed group.

  20. For spoke devices, in the Neighbor Hub select the hub device.
  21. Click on the Advanced link to view the default values for Advanced Settings. If the advanced settings can be edited in the service order, you can override the default values. If you do not click the Advanced link, the default advanced settings are applied to the service order.Note

    The Advanced link is not available for a point-to-point spoke.

    To change settings on an endpoint that has editable advanced settings:

    1. Click Advanced in the Action column.

      The Advanced Setting page displays the security and advanced settings that you can configure for a device.





      See Service Attributes Overview for complete information about MAC security settings and advanced settings.

    2. In the MAC Security Settings box, make selections for MAC learning and MAC statistics and type values for Interface MAC limit, MAC table size, and MAC table aging time.
    3. Enable or disable tunnel services by selecting or clearing the disable-tunnel-service check box.
    4. Enable or disable local switching by selecting or clearing the disable-local-switching check box.
    5. In the Fast reroute priority field, specify the reroute priority for a VPLS routing instance.
    6. In the Label block size field, specify the label block size for VPLS labels.
    7. In the Connectivity type field, select a connection-type to specify when a VPLS connection is taken down, depending on whether the interface for the VPLS routing instance is customer-facing or integrated routing and bridging (IRB)
    8. Click OK to save your changes in the Advanced page.
  22. To add an endpoint on a device not listed in the Endpoint Settings page:
    1. Click Add Endpoints.

      The Add Endpoint PE Devices page displays the available N-PE devices that you did not assign when you first made your device selections from the Select Endpoint PE devices page.

    2. Select additional devices, then click Next.

      The Endpoint Settings page appears with the new devices added.

    3. Modify the endpoint settings for this device, as required.
  23. If you have attached a service template in the service definition, the Flexible Service Attributes link appears. 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.
  24. When you have finished modifying the endpoint settings, click Create.

    The Deployment Options page appears.

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

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

  25. Continue with "Deploying the New Service," next.

Deploying the New Service

This part of the create multipoint Ethernet service order procedure deploys the service.

To deploy the service from the Deployment Options page:



  1. Perform one of the following actions:
    • To validate and save the request without deploying the service, select the Validate check box, 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 save the request without validating the service, clear the Validate check box, 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 and then click OK.

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

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

  2. Monitor the status of the deployment using the Jobs workspace.

The service order is now complete.

The Manage Service Orders page shows the service order you just added. See Viewing Jobs in the Junos Space Network Application Platform User Guide for details about the Jobs workspace.