Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Add L3VPN Service Site Details

An L3VPN service is provisioned on a collection of sites to exchange network traffic over a shared IP infrastructure. Use the Site Settings section of the Add L3 VPN Service page to enter details of sites that you want to connect to the VPN.

You configure the following in the Site Settings section:

Add L3VPN Site

An L3VPN site refers to the geographical area where the VPN service spans. To add an L3VPN service site in the Site Settings section:

  1. Click the + (Add) icon on the top-right corner of the Sites section.

    The Add Site page appears.

  2. Enter site ID, location, and device values by referring to Table 1.
  3. Enter maximum routes value:
    1. Expand Maximum Routes and click the + (Add) icon on the top-right corner of the Address Family section.
      The Address Family page appears.
    2. Enter the maximum routes value.
      This value indicates the number of routes that the VRF can accept for the IPv4 address family. Paragon Automation currently supports only the IPv4 address family.
    3. Click OK.
      The details you entered are listed in the Address Family table.
    4. (Optional) To edit or delete an entry, use the edit or delete options present above the Address Family table.
  4. Do any of the following:
    • Click Cancel to exit the Add Site page without saving the changes you made.

    • Click OK to save the site details you added. The site you added is listed in the Sites table.

    You can view the configured properties and the number of maximum routes by expanding Properties.
Table 1: Fields on the Add Site Page

Field

Description

Site ID

Enter a unique site ID to identify the site in the network.

The site ID can be a set of alphanumeric characters, space, and special character hyphen (-). The maximum number of characters allowed is 64.

Locations

Location ID

Enter a unique ID for a location in the site. For example, MAN for Manhattan and BRO for Brooklyn in the New York site.

Address

Enter the address (number and street) of the location in a site.

City

Enter the city where the site is located.

Country Code

Enter the ISO alpha-2 code of the country where the site is located. For example, ZA for South Africa and CH for Switzerland,

Postal Code

Enter the postal code of the location in the site.

State

Enter the state or region (in countries where there are no states) where the site is located.

Devices

Devices

Enter or select the CE devices to be used for the L3VPN service at the site.

This parameter allows the customer to request for devices from the service provider to be installed at the site.

Maximum Routes > Address Family

Maximum Routes

Enter the maximum number of routes that a virtual routing and forwarding table (VRF) can accept for the IPv4 address family.

Paragon Automation currently supports only the IPv4 address family.

Add Site Network Access Parameters

After you add a site for the L3VPN service, you must configure the parameters for the network access (connection) between the site and the service provider network. A site network access defines how a site is connected to the service provider network.

To set site network access parameters:

  1. Select and expand the site name in the Sites table.
  2. Click the + (Add) icon above the Site Network Access table.
    The Add Connection page appears.
  3. Enter the site network access ID and device reference values by referring to Table 2.
  4. Expand Access Diversity and add the access diversity parameters. See Add Access Diversity Parameters.
  5. Expand Bearer and add the bearer parameters by referring to Table 2.
  6. Expand IP Connection > IPv4 and add the connection parameters by referring to Table 2.
  7. Expand Routing Protocols and add the routing protocols. See Add Routing Protocols.
  8. Expand Service and add the service parameters by referring to Table 2.
  9. Expand VPN Attachment and enter the value by referring to Table 2.
  10. Do any of the following:
    • Click Cancel to exit the Add Connection page without saving the changes you made.

    • Click OK to save the connection details you added.

      You are returned to the Add L3 VPN Service page and view the connection you added listed in the Site Network Access table.

Add Access Diversity Parameters

A Network Admin can group the connections from a site to the service provider network, assign group ID to each connection group, and apply certain constraints to all the connections included in a group. You can assign one or more group IDs for a connection, specify constraint types, and select the target group ID that the constraint must be applied to, in the Access Diversity section.

To assign group IDs to a connection and apply constraints to target group IDs:

  1. Expand Access Diversity on the Add Connection page.
  2. Add IDs of groups that the connection is to be a part of:
    1. Expand Groups and click the + (Add) icon.
      The Group page appears.
    2. Enter one or more IDs of the groups to which the connection must be assigned and click OK.
      The group ID entries are listed in the Group ID table.
    3. (Optional) Use the edit or delete options above the Group table to edit or delete the entries.
  3. Expand Constraints and click the + (Add) icon above the Constraints table.
    The Constraint page appears.
  4. Add the following parameters on the Constraints page:
    1. Click the Constraint Type drop-down and select constraint type from the available options as listed in Table 2.
    2. Expand Target and click the + (Add) icon above the Group ID table.
      The Group page appears.
    3. Click the Group ID drop-down to select the group to which the constraint must be applied.
      You can add multiple group IDs for target groups. The group IDs you add are listed in the Group ID table.
    4. (Optional) Use the edit or delete options above the Constraints table to edit or delete the entries.
    5. Click OK on the Constraint page.
      The constraint types and target group IDs are listed in the Constraint table.

Add Routing Protocols

The Routing Protocols section defines the routing protocol to be used between the PE and CE routers.

In a customer-managed site, the routing protocol that you define here is used between the PE router and CE router that the customer manages. In a service provider-managed site, the routing protocol that you define here is used between the provider-managed CE router and the customer-managed LAN or router. Paragon Automation supports the static route, direct, OSPF, and BGP protocols for L3VPN service provisioning.

To set routing protocols:

  1. Expand Routing Protocols on the Add Connection page.
  2. Click + (Add) present above the Routing Protocols table and set the routing protocol from the supported options:
    Note:
    • The hub-and-spoke VPN topology is a beta feature in this release.

    • The hub-and-spoke topology supports the static route protocol only.

  3. (Optional) To edit or delete an entry, select the entry and click on the edit or delete options icons present above the Routing Protocols table.

Add Static Routing Protocol

To add static route protocol:

  1. Expand Routing Protocols and click Add > Static Route on the Add Connection page.

    The Add Static Route page appears.

  2. Expand Cascaded LAN Prefixes and click the + (Add) icon next to Ipv4 LAN Prefixes.

    The IPv4 LAN Prefixes page appears.

  3. Enter the values as described in Table 2.
  4. Click OK.
    The static route details are listed in the IPv4 LAN Prefixes table.
  5. (Optional) To edit or delete an entry, select the entry and click on the edit or delete icons present above the IPv4 LAN Prefixes table.

Add OSPF Routing Protocol

To add OSPF routing protocol:

  1. Expand Routing Protocols and click Add > OSPF on the Add Connection page.
    The Add OSPF page appears.
  2. Enter the values as described in Table 2.
  3. Click OK.
    The OSPF details are listed in the Routing Protocols table.

Add BGP Routing Protocol

To add BGP routing protocol:

  1. Expand Routing Protocols and click Add > BGP on the Add Connection page.
    The Add BGP page appears.
  2. In the Autonomous System field, enter the autonomous system number of the network in which you want to configure the L3 VPN service.
  3. Click OK.
    The BGP details are listed in the Routing Protocols table.
Table 2: Fields on the Add Connection Page

Field

Description

Site Network Access ID

Enter a unique ID for the connection between the site and the service provider network.

Device Reference

Click the drop-down list to select a CE device for the connection.

The drop-down list displays the devices that you specified on the Add Sites page.

Access Diversity > Constraint

Constraint Type

The following access constraint types are supported:

  • pe-diverse—The site network access must not be connected to the same PE router as the target connections from the site.

  • same-pe—The site network access must be connected to the same PE router as the target connections from the site.

  • pop-diverse—The site network access must not use the same point-of-presence (POP) as the target connections from the site.

Bearer

Bearer Reference

Enter the ID of an existing connection or bearer (access media and other layer 2 properties) between a service provider and customer, which the customer wants to reuse for the L3VPN service.

Requested Type

Select the access media type that the customer prefers to use. Ethernet is the only supported media type in this release.

Strict

Set to True if the requested access type is a strict requirement.

If the requested access type is a strict requirement, the service provider cannot connect the site using any other media. The default setting is False.

IP Connection

Address Allocation Type

Define how to allocate IP addresses when you configure IPv4 subnet. The only supported type is static address, where IP addresses are assigned manually.

Note:

Ensure that the provider and customer addresses are in the same subnet.

Provider Address

Enter the IPv4 address of the service provider for the customer network to connect, in the dotted decimal notation. For example, 10.10.3.4.

Customer Address

Enter the IPv4 address of the customer network to connect with the service provider network, in the dotted decimal notation. For example, 192.168.1.2.

Prefix Length

Enter the subnet prefix length expressed in number of bits. The same prefix length is applied to both customer and provider IPv4 addresses. For example, 20.

Routing Protocols > Add > Static Route > IPv4 LAN Prefixes

LAN

Enter the IPv4 address with prefix of the customer LAN interface connecting to the service provider network. For example, 192.168.0.1/20.

Next Hop

Enter the IPv4 address of the next hop router to reach the service provider network. For example, 10.1.0.1

Routing Protocols > Add > OSPF > Add OSPF

Area Address

Enter the OSPF area address to be used for the interface connecting to the service provider network. For example, 0.0.0.1.

Metric

Enter the cost of using the OSPF link to the service provider network.

Range: 1 through 65.535.

Routing Protocols > Add > BGP > Add BGP

Autonomous System

Enter the autonomous system number of the network in which you want to configure the VPN.

If you do not enter a value, the value is auto-configured if values exist for autonomous system in the resource pool.

Enter a value from 0 to 4,294,967,295.

Service

Service Input Bandwidth

Enter the download bandwidth (in bps) for the site from the provider network.

Enter a value from 0 to 9,223,372,036,854,766,000 bps.

Service MTU

Enter the maximum packet size (in bytes) allowed through the connection for the L3VPN service.

Enter a value from 0 to 65,535 bytes.

Service Output Bandwidth

Enter the upload bandwidth (in bps) from the site to the service provider network.

Enter a value from 0 to 9,223,372,036,854,766,000 bps.

VPN Attachment > Attachment Flavor

Site Role

The role of the site in the VPN service topology.

  • Any-to-any role—In this role, all VPN sites can communicate with each other.

  • Hub role—The site has a hub role in a hub-and-spoke VPN service topology.

  • Spoke role—The site has a spoke role in a hub-and-spoke VPN service topology.

Note:
  • The hub-and-spoke VPN topology is a beta feature in this release.

  • The any-to-any role is supported if you select the any-to-any VPN service topology. The hub and spoke roles are supported if you select the hub-spoke service topology. See Add an L3VPN Service Instance.