• Downloads
• Creating a Point-to-Point Ethernet Service Order    

• Related Topics
• Viewing Service Orders
• Viewing Scheduled Jobs in the Junos Space Network Application Platform User Guide
• Service Attributes Overview
• Adding a New Customer
• Deploying a Service
• Creating a Multipoint-to-Multipoint Ethernet Service Order
• Creating a Point-to-Multipoint Ethernet Service Order

Creating a Point-to-Point Ethernet Service Order

To create a point-to-point Ethernet service order, follow the steps in these procedures:

1. Selecting the Service Definition
2. Entering General Settings Information
3. Specifying the Connectivity
4. Specifying Endpoint Information
5. Deploying the New Service

Selecting the Service Definition

To select a service definition on which to base the new service order, follow these steps:

1. In the Ethernet Activator task ribbon, select the Service Provisioning workspace icon.
2. In the task ribbon, select the Manage Service Orders task icon.
3. In the task ribbon, select the Create P2P Service Order task icon.

   The Select Service Definition screen appears and shows an inventory of all available point-to-point service definitions. An example follows:

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

   A graphical image of a service order appears as shown in the following example:

   

   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.

   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 previous example.

Entering General Settings Information

In the General Settings box, enter the following information:

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

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

2. In the Customer field, select the customer who is 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. This description will appear in information screens about the request or service instance created from the request.

Specifying the Connectivity

In the Connectivity Settings box, enter VCID and MTU information, as allowed by the service definition. This box might include:

• VCID—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 could 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 who have their own systems for allocating VCIDs will choose 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 checkbox to override the service definition setting. The form expands to include an additional field for entering the VCID manually as follows:

  
• MTU for the connection across the network.

  Again, 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 the General/Connectivity Settings panel, a warning icon appears next to the cloud image.

  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.

Specifying Endpoint Information

An example Endpoint Settings screen follows:

The fields in this example are for a service with Q-in-Q endpoint interfaces. Some of the fields differ from one interface type to another and also differ depending on permissions assigned in the service definition.

Fill in the requested information as follows:

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 need to pick a device that has available UNIs.

   This step is required for all service orders.

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

   The dropdown list includes all UNIs available on the selected device.

   This step is mandatory for all service orders.

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

3. In the Traffic type field, designate whether the service will transport all traffic, a single VLAN, or multiple VLANs.

   Althought this field is present for all service orders, it is predetermined for some types of interface. For example, a port-to-port interface will always transport all traffic. Moreover, for interface types that do support mutiple 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
4. 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.

5. In the C-Vlan Start and C-Vlan End fields, enter the beginning and end of the range of customer VLANs that the service will transport.

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

6. Select the Auto pick S-VLAN ID checkbox 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.

7. In the S-VLAN ID field, enter the service VLAN ID that will 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 S-VLAN ID checkbox is cleared.

8. In the MTU (Bytes) field, enter 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.

9. 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 on another graphic element in the main graphic area, the selected device name and interface name appear beneath the endpoint image in the main graphic.

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

11. Click Create.

    The deployment options window appears.

Deploying the New Service

An example of the deployment options window follows:

To deploy the new service, follow these steps:

1. Perform one of these actions:
   • To save the request without deploying the service, select Save only, and then click OK.

     See Deploying a Service 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. To monitor the progress and status of the deployment, use the Jobs workspace. See Viewing Scheduled Jobs in the Junos Space Network Application Platform User Guide for details.