Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add an L2 Circuit Service Instance

As a superuser or network administrator, you can use Routing Director to provision Layer 2 (L2) circuit services in your network. An L2 circuit is a virtual point-to-point L2 connection between two CE devices through a packet-switched network such as Multiprotocol Label Switching (MPLS), in the service provider's network. The CE devices running the same L2 protocol (such as Ethernet) connect to PE devices in the service provider network through a physical or logical attachment circuit.

Note:

  • LDP signaling without BGP autodiscovery is the only variant of L2 Circuit that is supported in this release.

  • Redundant pseudowires for L2 Circuit are not supported in this release.

When you create and save an L2 circuit service instance, Routing Director generates a create service order. After you provision the service instance, Routing Director activates the automated workflow for fulfilling the service order and provisions the service in the network.

To create an L2 circuit service instance, either upload a preconfigured JSON file or enter the details in the GUI fields on the Add E-Line L2Circuit NSM page.

To create an L2 circuit service instance:

  1. Click Orchestration > Instances.

    The Service Instances page appears.

  2. Click + > E-Line L2Circuit NSM.

    The Add E-Line L2Circuit NSM page appears.

  3. In the General section, enter the values by referring to Table 1.
  4. Click Next to proceed to the VPN Nodes section.
  5. Enter VPN node details in the VPN Nodes section. See Add L2 Circuit VPN Nodes.
  6. Click Next to proceed to the Summary section.
    You see a graphical map of your service topology and a summary of the instance details. Zoom in and out using the zoom icons on the map.
  7. (Optional) Click Export to export and save the service details in JSON format on your local system.
  8. (Optional) Click Reset Placements to remove existing placement configurations for the service instance.

    Provisioning of a service instance might fail when existing placement configurations for the service instance are no longer available or applicable. When you reset placement parameters, service orchestration automatically assigns placement options for the instance before provisioning the service.

  9. Click Next to proceed to the Schedule section.
  10. (Optional) Switch the Schedule toggle on if you want to schedule when to provision the service. The Schedule option is disabled by default. When you schedule provisioning, the Save & Provision button on top of the page is disabled and grayed out.

    The Schedule field appears. Perform the following steps to schedule the date and time to provision the service:

    1. Click the calendar icon in the Schedule field.
    2. Select the date and time for provisioning the service, and click OK.
      The scheduled date and time are displayed in the MM/DD/YYYY HH:MM AM/PM format.
      Note:

      • You must set a present or future date and time to schedule provisioning of a service. If you select a past time and save the service order, the service is provisioned immediately.

      • To delete a provisioning schedule, select the service-instance-name on the Service Instances page and click the edit icon. On the Modify Service-Instance-Name page, proceed to the Schedule section. In the Schedule section, switch the Schedule toggle off and click Save. The provisioning schedule is deleted and the service instance is provisioned immediately.

      • Scheduling of service provisioning is a Beta feature in this release.

  11. To save and provision the service instance, click one of the following buttons:

    • Save & Provision—Click this button and confirm when prompted, to save the service instance to the Routing Director database and provision the instance immediately. This option is disabled if you have scheduled the provisioning of a service instance.

    • Save—Click this button to save the service instance to the Routing Director database. The Service Instances page appears and the new service instance is listed in the Service Instances table. To provision the service instance, select the service instance name and click Provision. Alternatively, you can schedule provisioning of the service instance as defined in step 10.

      Note:

      • The Provision button is disabled if you schedule the provisioning of a service instance. The service is provisioned automatically at the scheduled date and time.
Note:

Fields marked with an asterisk (*) are mandatory.
Table 1: Fields in the Add E-Line L2Circuit NSM General Section

Field

Description

Upload JSON File

Click Browse to upload a preconfigured JSON file.

You see a message that the file is successfully imported. The values specified in the file are automatically populated in the corresponding UI fields.

Customer*

Enter the name of the customer for whom you are provisioning the service:

  • If you already added the customer name by using the Customer Inventory page (Orchestration > Service > Customers), click the Customer field to see a drop-down with the customer names that you added. Select the customer name from the drop-down list.

  • Alternatively, click the Add Customer link to create a new customer. See Add a Customer.

The customer name must be unique within an organization. For example, network-operator.

Instance name*

Enter a name for the service instance. For example, l2ckt-171.

The instance name can be a set of alphanumeric characters and the special character hyphen (-). The maximum number of characters allowed is 64.

Pinned Reservation

Configure the service to use reserved resources (pinned resources).

Brownfield

Enable this flag if this is a brownfield service. When enabled, this service would be provisioned by using resources reserved for migrating brownfield services to Routing Director.

Customer

Enable this flag to allow the service to be provisioned by using resources that are exclusively reserved for the customer associated with this service.

Instance

Enable this flag to allow the service to be provisioned by using resources that are exclusively reserved for this service.

Service Settings

Enter common settings applicable for the service.

S-VLAN

Enter the service provider S-VLAN ID to allow VLAN mapping. On an untagged interface, a push operation is performed on incoming traffic and pop operation on outgoing traffic. On a tagged interface, the service VLAN should match the customer VLAN.

Enter a VLAN ID in the range 1 through 4096.

Related Documentation