Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add an L3VPN Service Instance

A superuser or network administrator can use Routing Director to provision an L3VPN service in their network.

When you create and save an L3VPN 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.

You can create an L3VPN service instance by uploading a preconfigured JSON file or by entering the details in the UI fields on the Add L3VPN Service page.

To create an L3VPN service instance:

  1. Click Orchestration > Instances.

    The Service Instances page appears.

  2. Click Add > L3VPN.

    The Add L3VPN Service page appears.

  3. In the General section, enter the values by referring to Table 1.
    Note:

    Fields marked with an asterisk (*) are mandatory.
    Table 1: Fields in the Add L3VPN Service Page 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*

    Select 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), 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.

    Instance name*

    Enter a name for the service instance. For example, l3vpn.

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

    VPN Id*

    Enter the ID you want to assign to the VPN. For example, vpn10.

    The VPN ID must not exceed 64 characters.

    VPN Service Topology*

    Select a topology for the VPN service:

    • Any-to-any topology—In this service topology, all VPN sites can exchange network traffic with each other without any restrictions.

    • Hub-spoke topology—In this service topology, spoke sites can exchange network traffic with hub sites, but not with other spoke sites. The hub sites can exchange network traffic with other hub sites.

      Note: The minimum release required to configure L3VPN hub and spoke topology on ACX Series routers is 24.2R1.

    Route Distinguisher Type

    Select the route distinguisher (RD) type. The default RD type is Type 0.

    If Type 1 is selected, the Type 1 values are populated from the NIP or topo resource pool in the Route Distinguishers table at the bottom of the page. If Type 0 is selected, the Type 0 values are populated from the VPN resource pool in the Route Distinguishers table at the bottom of the page.

    BGP Color Community

    Select the color of the BGP community that you want to assign to the service.

    This drop-down list is empty when you provision the service instance for the first time. This list is populated when you use the Update Placements option.

    If you want to change a previously assigned color, click the drop-down list and select an alternate color. Or if you do not want to assign any color, click the drop-down list and select the Please select option(s) option to remove the previous selection.

    BGP Link Protection

    Toggle to True to enable BGP link protection to create protected paths for traffic to restore connectivity quickly in case of a link or node failure. The option is set to False, by default.

    Enable BGP PIC Edge

    Toggle to True if you want to enable BGP Prefix-Independent Convergence (PIC) Edge. The option is set to False, by default.

    When BGP PIC Edge is enabled, the protect core statement is configured under the routing-options hierarchy in the PE router.

    BGP PIC Edge allows you to install an L3VPN route, in both IPv4 and IPv6 networks, in the forwarding table as an alternate precomputed path, enabling fast failover when connectivity to a PE router is lost.

    Route Target

    Number

    Enter the number of route targets.

    The block size entered when configuring a VPN resource pool is the upper limit for the route target number. The entered block size is displayed to the right of the text box.

    Pool

    Select a pool value.

    The ASN values specified when configuring a VPN resource pool are available as options in the drop-down list.

    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 exclusively reserved for this service.

    Service Settings

    Enter common settings applicable for the service.

    Use instance name instead of UUID in device configuration.

    Toggle to True to use the service instance name, instead of UUID, in the device configurations. The specified name is used in configuration such as routing instance name, filter name, policer name, community name, policy statement name, and so on. The instance name must be unique across customers and can be a maximum of 32 characters long.

    Disable it to set it to False, so that the service instance name is auto-converted to a UUID and used in the device configuration. The UUID is a system generated alphanumeric value.

    This option is disabled, by default.

    Route Distinguishers

    Update placements and configure the service instance to see the assigned RDs.

    For Type 0 Route Distinguishers

    PE Node

    The name of the PE node device.

    Pool

    The unique RD identifier configured as the ASN in the VPN resource pool.

    When the service is configured, the combination of the pool ID and a Routing Director assigned number is visible in the device CLI in the format pool:number. For example, 60000:9.

    Number

    A unique number assigned to the RD by Routing Director.
    For Type 1 Route Distinguishers

    PE Node

    Name of the PE node device.

    IP Address

    Loopback address of the device.

    If you want to change the loopback address for the device, you can edit the entry from the available preconfigured loopback addresses. To edit, select the RD, click the pencil icon, and select another loopback address from the drop-down list.

    Name

    Unique RD identifier populated from the configured names in the topo resource instance.

    Assigned Number

    A unique number assigned to the RD by Routing Director from the block size configured in the topo resource instance.

    To change the assigned number, select the RD, click the pencil icon, and edit the number from the preconfigured range visible next to the textbox.

    When the service is configured, the combination of the loopback address and the assigned number is visible in the device CLI in the format loopback_IP:number. For example, 192.168.1.1:30.
  4. Click Next to proceed to the Customer Site Settings section.
  5. Enter customer site-specific details in the Customer Site Settings section. See Add L3VPN Service Site Details.
    Note:

    If you upload a preconfigured file, the values specified in the file are automatically populated in the corresponding UI fields.
  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 in the Summary section.

  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.

Related Documentation