Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configure Resource Pools for Resource Instances

After you add a new resource instance, you must configure the resource pool for the instance. You can configure resource pools by using the Routing Director GUI. You can upload a preconfigured JSON file or use the GUI fields to create a resource pool.

Configure a Network Resource Pool

To configure a network resource pool for a resource instance:
  1. Add a resource instance. See Add a Resource Instance.
    The Modify Resource-Instance-Name page appears and displays the Resource Editor and Inventory panes.
  2. You can configure resource pools in either one of the following ways:

    • Upload a preconfigured JSON file that contains the resource configurations.

      1. Click Upload on the Resource Editor pane.

      2. Browse and select the preconfigured JSON file on your computer.

      3. Click Open to upload the file. The values specified in the file are automatically populated in the corresponding GUI fields.

    • Enter the values in the GUI fields to create the resource pool.

      1. Configure the following resource pools for the corresponding resource designs:

      2. (Optional) Click Download on the Resource Editor pane of the Modify Resource-Instance-Name page to download and save the VPN resource configuration in the JSON format on your local computer.

  3. (Optional) Click Download on the Inventory pane to download and save the resource inventory in the JSON format on your local computer.
  4. Click Proceed.
    The Compare Resource Definition page appears.

    You can view the configuration updates you made in the current resource instance in comparison to the previously saved resource instance configurations in the database.

  5. Click Inline for an inline view of the comparisons and click Side-by-side for an adjacent view.
  6. Click Save and Commit.
    A service order is generated and the Monitor Order Status page appears. The page displays the execution status of the service order.
  7. Click the service-order-name hyperlink to monitor the execution state of the service order. See View Workflow Run Details.
  8. Click the Restore instance hyperlink if the service order fails to commit.
    An order is generated to restore the last service order for the resource instance and the Monitor Order Status page appears. The page displays the execution status of the order.
    Note:

    A modify service order for a resource instance is saved but fails to commit if you modify resources that are in use for a service.

  9. Click OK.

Create a Routing Resource Pool

A routing resource pool defines the Autonomous System (AS) details, BGP route reflector clusters, and Segment Identifiers (SIDs). The routing resource pool must be configured for provisioning the infrastructure service.

To create a routing resource pool using the GUI fields:

  1. Add a routing resource instance. See Add a Resource Instance.
    The Modify Resource-Instance-Name page appears and displays the Resource Editor and Inventory panes.
  2. On the Resource Editor pane of the Resource-Instance-Name page, expand routing.
  3. Click the add (+) icon above the Autonomous System table.
    The Autonomous System page appears.
  4. Enter the values by referring to the following table:
    Table 1: Fields on the Autonomous System Page

    Field

    Description

    Name*

    Enter the AS number of the network in which you want to configure your infrastructure or VPN service.

    Enter a value in the range 0 through 4,294,967,295.

    Count*

    Enter the number of routes available in the specified AS.

    Enter a value in the range 0 through 65,535.
  5. Click OK.
    The autonomous system details are listed in the Autonomous System table.
  6. (Optional) To edit or delete an entry, select the entry and click the edit or delete icons present above the table.
  7. Expand Route Reflector and click the add (+) icon above the Clusters table.
    The Clusters page appears. Use this page to manage the BGP Route Reflector Cluster IDs available in the resource pool for auto-allocation when provisioning a service.
  8. In the Cluster field, enter the cluster ID that the BGP route reflector supports.
    A route reflector can support multiple clusters. You can enter multiple cluster IDs for a route reflector.
  9. Click OK.
    The cluster details are listed in the Clusters table.
  10. Expand Spring > Sids.
  11. In the Size* field, enter the number of SIDs available in the resource pool.
    Enter a value in the range 0 through 65,535.
  12. Expand Base and enter the values by referring to the following table:
    Table 2: SIDs Base Parameters

    Field

    Description

    IPv4

    Enter the starting or base value for IPv4 SIDs in the routing resource pool.

    Enter a value in the range 0 through 65,535.

    IPv6

    Enter the starting or base value for IPv6 SIDs in the routing resource pool.

    Enter a value in the range 0 through 65,535.
  13. Go to 2.b of the Configure a Network Resource Pool procedure to save and download the resource configuration and proceed with the resource instance edition.

Create a Layer 3 Resource Pool

A Layer 3 resource pool defines resources such as IPv4 and IPv6 prefixes and loopback prefixes. The Layer 3 resource pool must be configured for provisioning infrastructure services.

To create a Layer 3 resource pool:

  1. Add a Layer 3 (L3-Addr) resource instance. See Add a Resource Instance.
    The Modify Resource-Instance-Name page appears and displays the Resource Editor and Inventory panes.
  2. On the Resource Editor pane of the Modify Resource-Instance-Name page, expand l3-addr.
  3. Click the add (+) icon above the IPv4 Prefixes table.
    The IPv4 Prefixes page appears. Use this page to manage the IPv4 address prefixes available in the L3 resource pool for auto-allocation when provisioning a service.
  4. Enter the values by referring to the following table:
    Table 3: Fields on the IPv4 Prefixes Page

    Field

    Description

    Name*

    Enter a name to uniquely identify the IPv4 address pool.

    Prefix*

    Enter the IPv4 prefix in CIDR notation (ipv4-address/prefix length). For example, 10.10.11/24.
  5. Click OK.
    The IPv4 prefix details are listed in the IPv4 Prefixes table.
  6. Click the add (+) icon above the IPv6 Prefixes table.
    The IPv6 Prefixes page appears. Use this page to manage the IPv6 address prefixes available in the L3 resource pool for auto-allocation when provisioning a service.
  7. Enter the values by referring to the following table:
    Table 4: Fields on the IPv6 Prefixes Page

    Field

    Description

    Name

    Enter a name to uniquely identify the IPv6 address pool.

    Prefix

    Enter the IPv6 prefix in CIDR notation (ipv6-address/prefix length). For example, 2001:db8:0::11/64.
  8. Click OK.
    The IPv6 prefix details are listed in the IPv6 Prefixes table.
  9. Click the add (+) icon above the IPv4 Loopbacks table.
    The Loopbacks page appears. Use this page to manage the IP address prefixes available in the L3 resource pool for auto-allocation to loopback interfaces on PE devices when provisioning a service.
  10. Enter the values by referring to the following table:
    Table 5: Fields on the Loopbacks Page

    Field

    Description

    Name*

    Enter a name to uniquely identify the loopback interface.

    Prefix*

    Enter the loopback prefix (in CIDR notation) to define the range of IPv4 addresses that can be assigned to the loopback interface.

  11. Click OK.
    The loopback details are listed in the Loopbacks table.
  12. Click the add (+) icon above the IPv6 Loopbacks table.
    The IPv6 Loopbacks page appears. Use this page to manage the IP address prefixes available in the L3 resource pool for auto-allocation to loopback interfaces on PE devices when provisioning a service.
  13. Enter the values by referring to the following table:
    Table 6: Fields on the IPv6 Loopbacks Page

    Field

    Description

    Name

    Enter a name to uniquely identify the loopback interface.

    Prefix

    Enter the loopback prefix (in CIDR notation) to define the range of IPv6 addresses that can be assigned to the loopback interface.
  14. Click OK.
    The IPv6 loopback details are listed in the IPv6 Loopbacks table.
  15. (Optional) To edit or delete an entry in any of the tables, select the entry and click the edit or delete icons present above the table.
  16. Go to 2.b of the Configure a Network Resource Pool procedure to save and download the resource configuration and proceed with the resource instance edition.

Create a Layer 2 Resource Pool

A Layer 2 resource pool defines resources such as Ethernet VPN (EVPN) Ethernet Segment Identifiers (ESI), LACP administrative keys, and LACP system identifiers. The Layer 2 resource pool must be configured for provisioning EVPN services.

To create a Layer 2 resource pool:

  1. Add a Layer 2 (L2-Addr) resource instance. See Add a Resource Instance.
    The Modify Resource-Instance-Name page appears and displays the Resource Editor and Inventory panes.
  2. On the Resource Editor pane of the Modify Resource-Instance-Name page, expand l2-addr.
  3. Enter the EVPN ESI details:
    Note:

    In an EVPN service multihoming scenario, the ESIs are generated at the IFL level rather than at the IFD level of the AE bundle.
    1. Click the add (+) icon above the EVPN ESI table.
      The EVPN ESI page appears. Use this page to manage Ethernet segment identifiers (ESIs) available in the L2 resource pool for auto-allocation when provisioning a service.
    2. Enter the values by referring to the following table:
      Table 7: Fields on the EVPN ESI Page

      Field

      Description

      Name*

      Enter a unique ESI.

      An Ethernet segment refers to the set of Ethernet links that connect a multihomed CE device to multiple PE devices. The ESI uniquely identifies an Ethernet segment in the network.

      Count*

      Enter the number of EVPN ESIs that are available in the resource pool.

      Pinned Reservation

      Reserve the ESIs for specific services.

      Brownfield

      Enable this flag to reserve the defined EVPN ESIs for migrating brownfield services. The reserved EVPN ESIs would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved segment identifiers are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select a customer whose service would use the defined EVPN ESIs. The EVPN ESIs will be used exclusively by services provisioned for the customer that you enter here.

      Instance

      Enter the name of the customer service that can use the defined EVPN ESIs.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The defined EVPN ESIs will be used exclusively by the service that you enter here for the customer specified in Customer.

    3. Click OK.
      The EVPN ESI details are listed in the EVPN ESI table.
  4. Enter LACP administrative key details:
    1. Expand LACP and click the add (+) icon above the Admin Key table.
      The Admin Key page appears. Use this page to manage the LACP administrative keys available in the L2 resource pool for auto-allocation when provisioning a service.
    2. Enter the values by referring to the following table:
      Table 8: Fields on the Admin Key Page

      Field

      Description

      Start*

      Enter the starting value for the number of LACP administrative keys available in the resource pool.

      Enter a value in the range 0 through 65,535.

      You must specify LACP administrative keys for Multichassis Link Aggregation (MC-LAG) or Link Aggregation Groups (LAGs) that span physical ports across two separate devices.

      Size*

      Enter the number of LACP administrative keys available for auto-allocation in the resource pool, beginning from the start value.

      Enter a value in the range 1 through 65,535.

      Pinned Reservation

      Reserve the LACP administrative keys for specific servies.

      Brownfield

      Enable this flag to reserve the defined LACP administrative keys for migrating brownfield services. The reserved LACP administrative keys would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved administrative keys are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select the customer whose services would use the defined LACP administrative keys. The LACP administrative keys will be used exclusively by services provisioned for the customer that you enter here.

      Instance

      Enter the name of the service instance that can use the defined LACP administrative keys.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The LACP administrative keys will be used exclusively by the service that you enter here for the customer specified in Customer.

    3. Click OK.
      The LACP administrative key details are listed in the Admin Key table.
  5. Enter the LACP system ID details:
    1. Expand LACP and click the add (+) icon above the System ID table.
      The System ID page appears. Use this page to manage the LACP system identifiers available in the L2 resource pool for auto-allocation when provisioning a service.
    2. Enter the values by referring to the following table:
      Table 9: Fields on the System ID Page

      Field

      Description

      Name*

      Enter the unique LACP system ID that is available for auto-allocation in the L2 resource pool.

      You must specify LACP system ID for Multichassis Link Aggregation (MC-LAG) or LAGs that span physical ports across two separate devices.

      Count*

      Enter the number of ports to which the unique LACP system ID is assigned.

      Enter a value in the range 1 through 255.

      Pinned Reservation

      Reserve the LACP system IDs for specific services.

      Brownfield

      Enable this flag to reserve the defined LACP system IDs for migrating brownfield services. The reserved LACP system IDs would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved system IDs are being used by a service will release the reservation. If you reprovision the service without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select a customer whose service would use the defined LACP system IDs. The LACP system IDs will be used exclusively by services provisioned for the customer that you enter here.

      Instance

      Enter the name of service instance that can use the defined LACP system IDs.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The LACP system IDs will be used exclusively by the service that you enter here for the customer specified in Customer.

    3. Click OK.
      The LACP system ID details are listed in the System ID table.
  6. (Optional) To edit or delete an entry in any of the tables, select the entry and click the edit or delete icons present above the table.
  7. Go to 2.b of the Configure a Network Resource Pool procedure to save and download the resource configuration and proceed with the resource instance edition.

Create a Topology Resource Pool

A topology resource pool defines resources such as the sites, and PE device parameters such as access, bandwidth, routes, and postal code matches. The topology resource pool must be configured for provisioning L3VPN, EVPN, EVPN-VPWS, and L2 circuit services.

Note:

If you configure topology resources by specifying them in the network implementation plan, you must not add topology resource pools manually. See Configure Topology Resources in Network Implementation Plan.

The default topology resource instance managed through the network implementation plan is a read-only instance and cannot be modified.

To create a topology resource pool:

  1. Add a topology resource instance. See Add a Resource Instance.
    The Modify Resource-Instance-Name page appears and displays the Resource Editor and Inventory panes.
  2. On the Resource Editor pane of the Modify Resource-Instance-Name page, expand topo.
  3. Click the add (+) icon above the POP/Site table.
    The POP page appears. A point-of-presence (POP) refers to a site or physical location that hosts the PE devices.
  4. Click the Name* drop-down list and select the site from the list of available sites.

    The drop-down lists all the sites that you add by using the Sites page (Inventory > Common Resources > Sites). See About the Sites Page.

  5. Enter the node details. Click the add (+) icon above the Node table.
    The Node page appears. Use this page to specify the PE device or node to be used for provisioning VPN services. Enter details about the PE interfaces, aggregated bandwidth capacity of the PE device, and maximum MAC addresses and routes that the PE device supports. Specify the aggregated Ethernet or LAG interfaces available on the PE device for service provisioning. For EVPN services, configure the IRB IDs available for a PE device.
    1. Click the Name* drop-down and select the PE device from the list of available devices.
    2. Click the add (+) icon above the Access Interfaces table.
      The Access page appears. Use this page to enter details about the PE device interface that connects to the CE device.
    3. Configure the PE interface name, type and speed, and specify whether the PE interface connects to a single or multiple CE devices, by referring to the following table:
      Table 10: Fields on the Access Page

      Field

      Description

      Interface Name*

      Enter the name of the physical PE interface that connects to the CE interface. For example, et-0/0/0.

      If you are configuring multihoming on EVPN VPWS services, then enter the pre-provisioned link aggregation group (LAG) Aggregated Ethernet interface name. For example, ae1.

      Note: To configure multihoming you must have pre-provisioned the LAG interface on the device. You can pre-provision a LAG interface through the Routing Director GUI by using network implementation plans. Alternatively, you can log in to the device and manually configure the LAG interface and its member links at the IFD level on the device. For example:

      • For tagged interfaces:

        set interfaces ae1 flexible-vlan-tagging
set interfaces ae1 encapsulation flexible-ethernet-services
set interfaces ae1 aggregated-ether-options minimum-links 1
set interfaces ae1 aggregated-ether-options lacp system-id 00:00:00:00:11:02
set interfaces ae1 aggregated-ether-options lacp admin-key 10001
set interfaces et-0/0/2 gigether-options 802.3ad ae1

      • For untagged interfaces:

        set interfaces ae1 encapsulation ethernet-ccc
set interfaces ae1 aggregated-ether-options minimum-links 1
set interfaces ae1 aggregated-ether-options lacp system-id 00:00:00:00:11:02
set interfaces ae1 aggregated-ether-options lacp admin-key 10001
set interfaces et-0/0/2 gigether-options 802.3ad ae1

      CE Spec

      Specify if you want to connect the PE interface to a single CE device or multiple CE devices.

      Click the drop-down and select one of the following options:

      • ce—The PE interface connects to a single CE device.

        When you select ce, the CE and Tag Type fields appear. You can enter the CE name and select a tag type by referring to step 5.d.

      • ces—The PE interface connects to multiple CE devices.

        When you select ces, the Ces section appears. You can enter the CE names and select a tag type by referring to step 5.e.

      Note:

      • Enter VLAN details if you want the access interface type in tagged mode. A tagged interface receives and sends Ethernet frames with VLAN tags.

      • If you optionally specify a VLAN while creating a service instance, service orchestration automatically selects an access interface on a PE device that has the specified VLAN available for use.

      Lag

      Toggle on the Lag button to True to indicate that the interface is an Aggregated Ethernet interface. Enable this button when you configure multihoming in EVPN VPWS services. When the Lag toggle button is enabled, service orchestration only allocates the pre-provisioned LAG interfaces for multihoming site network access. Note that, you must have pre-provisioned the LAG interface on the device.

      If the Lag option is enabled and you configure a single-homed EVPN VPWS service, the Aggregated Ethernet interface behaves as a normal physical interface and can be allocated for single-homed site network access, as well.

      Speed

      Enter the speed (in Mbps) of the physical PE interface.

      The interface speed refers to the maximum data transmission rate that the interface supports. The value entered here is displayed under the Placement option once placement options are updated in the EVPN VPWS service instance.

      The value entered here does not affect the topology resource.

      Type*

      Select the PE access type from the drop-down.

      Access type defines how the PE interface connects to the CE device. Ethernet is the only access type that is supported in this release.

      Units

      Click Add above the Units table to add a range of Ethernet interface units. These units are needed to migrate L3VPN Q-in-Q configuration to Routing Director.

      Name*

      Enter a name for the range of Ethernet interface unit. For example, eth-vpn-100 to eth-vpn-105.

      Size*

      Enter the number of interface units in the range.

      For example, a size of five will configure five distinct interface units on the Ethernet interface.

      Range: 0 through 4095.

      Start*

      Enter the first interface unit in the range.

      For example, assigning 100 as the Start value configures interface units from 100 up to 104 for a range size of five.

      Range: 0 through 4095.

      Pinned Reservation

      Reserve the interface units for specific services.

      Brownfield

      Enable this flag to reserve the interface units in the defined range on the PE access interface for migrating brownfield services. The reserved interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select a customer whose services would use the defined interface units. The interface units will be used exclusively by services provisioned for the customer that you select here.

      Instance

      Enter the name of the customer service instance that can use the defined interface units.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The interface units will be used exclusively by the service that you enter here for the customer specified in Customer.

    4. (For single CE connection) Enter the VLAN details for single CE device connection:

      1. Select ce from the CE Spec drop-down.

      2. (Optional) Enter a CE device name to uniquely identify the device in the network.

      3. Select a tag type from the Tag Type drop-down. You can select dot1q, qinq, or untagged as the tag type.

        The default tag type is untagged.

        1. When you select dot1q from the Tag Type drop-down, the VLANs table appears. Click the add (+) icon above the VLANs table, the VLANs page appears.

          Table 11: Dot1q VLAN Details for Single CE Connection on the VLANs Page

          Field

          Description

          Start*

          Enter the starting VLAN ID for the range of VLANs from the CE device that the PE interface supports.

          Enter a value in the range 1 through 4094.

          For example, if 200 is the starting VLAN ID, the first VLAN supported by the PE interface has a VLAN ID of 200.

          Size*

          Enter the range of VLANs from the CE device that the PE interface supports.

          Enter a value in the range 1 through 4094.
          Note: To configure multihoming in EVPN VPWS services with pre-provisioned LAG interfaces, select dot1q or untagged.

          Click OK. The VLAN details are listed in the VLANs table.

        2. When you select qinq from the Tag Type drop-down, the Inner VLANs and Outer VLANs tables appear.

          • Click the add (+) icon above the Inner VLANs table. The Inner VLANs page appears. Enter details about inner VLANs from a CE device that the PE interface supports. The inner VLAN ID is a CVLAN ID that the customer originally assigned to segment their internal traffic.

            Table 12: Inner VLAN Details for Single CE Connection on the Inner VLANs Page

            Field

            Description

            Start*

            Enter the starting VLAN ID for the range of inner VLANs.

            Enter a value in the range 1 through 4094.

            For example, if 200 is the starting inner VLAN ID, the first inner VLAN supported by PE device has a VLAN ID of 200.

            Size*

            Enter the range for inner VLANs.

            Enter a value in the range 1 through 4094.

            Click OK. The details are listed in the Inner VLANs table.

          • Click the add (+) icon above the Outer VLANs table. The Outer VLANs page appears. Enter details about outer VLANs from a CE device that the PE interface supports. The outer VLAN ID is an SVLAN ID that the service provider adds to identify the customer traffic.
            Table 13: Outer VLAN Details for Single CE Connection on the Outer VLANs Page

            Field

            Description

            Start*

            Enter the starting VLAN ID for the range of outer VLANs.

            Enter a value in the range 1 through 4094.

            For example, if 200 is the starting outer VLAN ID, the first outer VLAN supported by PE device has a VLAN ID of 200.

            Size*

            Enter the range for outer VLANs.

            Enter a value in the range 1 through 4094.

            Click OK. The details are listed in the Outer VLANs table.

        3. Select untagged from the Tag Type drop-down to assign no VLANs to the interface. An untagged interface receives and sends Ethernet frames without VLAN tags.

          If you do not select any tag type, the interface will display only untagged interfaces.

    5. (For multiple CE connections) Enter VLAN details for multiple CE connections.

      You must add the device name, select a tag type, and enter VLAN details for all the CE devices that connect to the PE interface.

      1. Select ces from the CE Spec drop-down.

      2. Enter the name of the PE interface that connects to the CE interface in Interface name. For example, et-0/0/0.

      3. Click the add (+) icon above the CEs table.

        The CEs page appears.

      4. (Mandatory) Enter a CE device name in Name to uniquely identify the devices in the network.

      5. Select a tag type from the Tag Type drop-down. You can select dot1q, qinq, or untagged as the tag type.

        The default tag type is untagged.

        1. When you select dot1q from the Tag Type drop-down, the VLANs section appears. Use this section to enter details about VLANs from a CE device that the PE interface can connect to. Enter VLAN details only if the PE interface is a tagged interface that accepts Ethernet frames with VLAN tags.

          Enter VLANs details by referring to the following table:

          Table 14: Dot1q VLAN Details for Multiple CE Connections on the CEs Page

          Field

          Description

          Start*

          Enter the starting VLAN ID for the range of VLANs from the CE device that the PE interface supports.

          Enter a value in the range 1 through 4094.

          For example, if 200 is the starting VLAN ID, the first VLAN connected from the CE device to the PE interface has a VLAN ID of 200.

          Size*

          Enter the range of VLANs from the CE device that the PE interface supports.

          Enter a value in the range 1 through 4094.
          Note: To configure multihoming in EVPN VPWS services with pre-provisioned LAG interfaces, select dot1q or untagged.

          Click OK. The device names and VLAN details are listed in the CEs table.

        2. When you select qinq from the Tag Type drop-down, the Inner VLANs and Outer VLANs tables appear. Enter Inner VLANs and Outer VLANs details by referring to the following table:

          Table 15: Q-in-Q VLAN Details for Multiple CE Connections on the CEs Page

          Field

          Description

          Inner VLANs

          Start*

          Enter the starting VLAN ID for the range of inner VLANs.

          Enter a value in the range 1 through 4094.

          For example, if 200 is the starting inner VLAN ID, the first inner VLAN supported by the PE interface has a VLAN ID of 200.

          Size*

          Enter the range for inner VLANs.

          Enter a value in the range 1 through 4094.

          Outer VLANs

          Start*

          Enter the starting VLAN ID for the range of outer VLANs.

          Enter a value in the range 1 through 4094.

          For example, if 200 is the starting outer VLAN ID, the first outer VLAN supported by the PE interface has a VLAN ID of 200.

          Size*

          Enter the range for outer VLANs.

          Enter a value in the range 1 through 4094.

          Click OK. The Inner VLANs and Outer VLANs details are listed in the CEs table.

        3. Select untagged from the Tag Type drop-down to assign no VLANs to the interface. An untagged interface receives and sends Ethernet frames without VLAN tags.

          If you do not select any tag type, the interface will display only untagged interfaces.

      6. (Optional) For a quick JSON view of the VLAN details, hover over the Show details hyperlink for a VLAN.

    6. Click OK on the Access page.
      The access details are listed in the Access Interfaces table.
    7. Click the add (+) icon above the Aggregated Ethernet Interfaces table.
      The AE page appears. Aggregated Ethernet (AE) interfaces refer to the Link Aggregation Group (LAG) interfaces that are created on a device while onboarding the device. Use this page to enter the AE interface name that is available on the PE device for service provisioning.
    8. Enter the AE interface name and configure the Pinned Reservation referring to table.
      Table 16: Fields on the Aggregated Ethernet Interface page.
      Field Description

      Name*

      Enter a name for the AE interface. For example, ae0, ae1.

      Pinned Reservation

      Reserve the AE interface for specific services.

      Brownfield

      Enable this flag to reserve the defined AE interface on the provider edge node for migrating brownfield services. The reserved AE interface would be used exclusively by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved AE Interface is in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select the customer whose services would use the AE interface. The AE interface will be used exclusively by services provisioned for the customer that you select here.

      Instance

      Enter the name of the service instance that can use the AE interface.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The AE interface will be used exclusively by the service that you enter here for the customer specified in Customer.
    9. and click OK.
      The AE interface name is listed in the Aggregated Ethernet Interfaces table.

      You can add multiple interface names for all the AE interfaces that are available on the PE device to provision services.

      Note:

      If the AE interface count for the device is not configured in the network implementation plan, you can configure the AE interfaces count on the device by executing the following command on the device CLI:

    10. Configure supported bandwidth, loopback address, MAC addresses, and roles by referring to the following table:
      Table 17: Fields on the Node Page

      Field

      Description

      Bandwidth

      Enter the aggregated bandwidth capacity (in Mbps) of the PE device.

      Aggregated bandwidth is the total amount of bandwidth provisioned across all interfaces on the device.

      IPv4 Loopback

      Select the loopback address for the node. The IPv4 loopback addresses are auto-populated from those configured for the device in the device profile. Do not add any new IP addresses.

      This address is used to generate the route distinguisher.

      Max MAC addresses

      Enter the number of MAC addresses that the PE device can manage.

      The MAC address count is used while allocating topology resources for EVPN and EVPN-VPWS service provisioning.

      Roles

      Click the Roles drop-down and select the node resource role from the list of available nodes.

      PE is the only node resource role supported in this release.

    11. Configure the route distingushers (RDs). If placement resources are enabled and RDs are configured in the NIP, these values are prepopulated in the Route Distinguishers Type 1 table.

      If RDs are not configured in the NIP, you can add RDs by clicking the + icon above the table.

      The Route Distinguishers page appears. Use this page to manage the route distinguishers available in the topo resource pool for auto-allocation when provisioning a service. Route distinguishers uniquely identify routes belonging to different VPNs in the service provider network.

      The values configured here are available when you select the Type 1 Route Distinguisher type when configuring an EVPN or L3VPN service instance.

      Enter the values by referring to Table 18.

      Table 18: Fields on the Route Distinguisher Type1 page
      Field Description

      Name*

      Enter a unique identifier for the route distinguisher. For example, rd-pool1

      Start*

      Enter the first RD in the range.

      For example, assigning 100 as the Start value configures RDs from 192.168.1.1:100 to 192.168.1.1:104 for a block size of five. Here 192.168.1.1 is the IPv4 loopback.

      Enter a value in the range 0 through 4095.

      Block Size*

      Enter the number of RDs in the range.

      For example, a size of 5 will configure five distinct RDs—192.168.1.1:100 to 192.168.1.1:104.

      Enter a value in the range 0 through 4095.

      Pinned Reservation

      Reserve the RDs for specific services.

      Brownfield

      Enable this flag to reserve the defined RDs for migrating brownfield services. The reserved RDs would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved RDs are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select a customer whose service would use the defined RDs. The RDs will be used exclusively by services created for the customer that you select here.

      Instance

      Enter the name of the service instance that can use the defined RDs.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The RDs will be used exclusively by the service that you enter here for the customer specified in Customer.

    12. Click OK on the Route Distinguisher Type1 page.

      The configured RD range is listed in the Route Distinguisher Type1 table.

    13. Enter the number of routes in Max Routes that the VRF table of the PE device can manage.

      The route capacity is used while allocating topology resources for L3VPN service provisioning.

    14. Enable IRBs and to configure a range of IRB interfaces on the node for use by EVPN services.
    15. Enter the size and start value of the range by referring toTable 19 .
    16. Click the + Add icon above the Migration table to configure a range of iRB interfaces to migrate brownfield services, See Table 19.
      Table 19: Fields for configuring IRB Interfaces

      Field

      Description

      Start*

      Enter the starting IRB for the range of IRB IDs.

      For example, assigning 10 as the Start value configures IRB interfaces from irb.10.

      Enter a value in the range 1 through 65,535

      Size

      Enter the number or range of IRB IDs available for a PE device. You can define a range using a starting ID and the number of IRBs required.

      For example, a size of 5 will configure 5 distinct IRB interfaces on the device (for example, irb.10 through irb.14).

      Enter a value in the range 1 through 65,535

      Migration

      Configure a range of IRB interfaces to be used for migrating brownfield services to Routing Director.

      Click Add to add the IRB interface range.

      Name*

      Enter a name for the range of IRB interfaces being configured. For example, IRB-HQ-Access.

      Size*

      Enter the number of IRB interfaces to be defined within the range. For example, a size of 5 will configure 5 distinct IRB interfaces on the device (irb.10 to irb.14 for a range size of 5).

      Range: 0 through 65,535

      Start*

      Enter the starting number of the IRB interface in the defined range. For example, assigning 10 as the Start value configures IRB interfaces from irb.10.

      Range: 0 through 65,535

      Pinned Reservation

      Reserve IRB interface units for specific services.

      Brownfield

      Enable this flag to reserve the defined IRB interface units for migrating brownfield services. The IRB interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      By default, this field is disabled. However, disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select the customer whose service would use the IRB interface units in the defined range. The IRB interface units will be used exclusively by services provisioned for the customer that you select here.

      Instance

      Enter the name of the service instance that can use the defined IRB interface units.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

      The IRB interface units will be used exclusively by the service that you enter here for the customer specified in Customer.
    17. Click OK on the Migration page.

      The configured range of IRB interface units are listed in the Migration table.

    18. Configure the logical tunnels (LT) and the range of LT subinterfaces for service stitching by clicking the + (Add) icon above the Logical Tunnel table. See table.
      Table 20: Fields for configuring Logical Tunnel Interfaces
      Field Description

      Name

      Enter the name for the LT interface. For example, lt-0/0/0 or lt-0/0/0:12.

      Ranges

      Click the + (Add) above the Ranges table to configure the range of LT logical units.

      Name

      Enter a unique name for the range of LT subinterfaces. For example, Range-1.

      Start*

      Enter the starting subinterface number of the defined range. For example, if you specify 200 as the starting value for subinterfaces on lt-0/0/1, the first logical subinterface created will be lt-0/0/1.200.

      Range: 0 through 16,385.

      Size*

      Enter the number of consecutive subinterfaces allocated in this range. For example, a size of 10 will configure 10 distinct subinterfaces (for example, 200 through 219) on the interface.

      Range: 1 through 16,385.

      Pinned Reservation

      Reserve the defined logical tunnel interface units for specific services.

      Brownfield

      Enable this flag to reserve the defined LT interface units for migrating brownfield services. The LT interface units would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

      Disabling this flag while the reserved interface units are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

      Customer

      Select the customer whose service would use the LT interface units in the defined range. The LT interface units will be used exclusively by services provisioned for the customer that you select here.

      Instance

      Enter the name of the service instance that can use the defined route targets.

      Note:

      For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate.

      The route targets will be used exclusively by the service that you enter here for the customer specified in Customer.

    19. Click OK on the Ranges pane.

      The configured range of LT subinterfaces is listed in the Range table on the Logical Tunnel pane.

    20. Click OK on the Logical Tunnel pane.

      The configured LT interface and range of subinterfaces are listed in the Logical Tunnel table on the Node page.

    21. Click OK on the Node page.
      The node details are listed in the Node table.
  6. Enter the postal code match details:
    1. Click the add (+) icon above the Postal Code Matches table.
      The Postal Code Matches page appears.
    2. Enter the values by referring to the following table:
      Table 21: Fields on the Postal Code Matches Page

      Field

      Description

      Name*

      Enter the name of the site where the PE device 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.

      Regex*

      Enter the postal code regex of the site where the PE device is located.
    3. Click OK on the Postal Code Matches page.
      The postal code details are listed in the Postal Code Matches table.
  7. (Optional) To edit or delete an entry in any of the tables, select the entry and click the edit or delete icons present above the table.
  8. Click OK on the POP page.
    The site or POP name, PE details, and postal code match details are listed in the POP/Site table.

    To view PE and postal code details for a POP in the JSON format, hover over the PE and postal code match hyperlinks.

  9. Go to 2.b of the Configure a Network Resource Pool procedure to save and download the resource configuration and proceed with editing the resource instance.
    Note:

    PE nodes and interfaces that connect to CE devices cannot be configured simultaneously in the network implementation plan and in the topology resource pool for provisioning infrastructure services. You must delete PE nodes and interfaces parameters from the topology resource pool if you are defining the same parameters in the network implementation plan.

    To delete the PE nodes and interfaces parameters from the topology resource pool, modify the topology resource instance and upload the modified instance to the Juniper Routing Director database. See Modify a Resource Instance.

Create a VPN Resource Pool

A VPN resource pool defines resources such as the route distinguishers, route targets and route target community details, and virtual circuits. The VPN resource pool must be configured for provisioning L3VPN, EVPN, or L2 circuit services.

To add a VPN network resource pool:

  1. Add a VPN resource instance. See Add a Resource Instance.
    The Modify Resource-Instance-Name page appears and displays the Resource Editor and Inventory panes.
  2. On the Resource Editor pane of the Modify Resource-Instance-Name page, expand vpn-resources.
  3. Enable automated traffic steering. Click the add (+) icon above the Colors table.
    The Colors page appears. Use this page to map a color (Gold for low latency, Silver for high bandwidth etc.) to the BGP color community value. Assign these colors to the BGP color community when provisioning an L3VPN service.
  4. Enter the values by referring to the following table:
    Table 22: Fields on the Colors Page

    Field

    Description

    Name*

    Enter the name of the BGP color community. For example, Gold-Low-Latency.

    The name can contain alphanumeric characters and special characters.

    Color Attribute*

    Enter a numeric value for the BGP color community.

    Enter a value in the range 0 through 4,294,967,295.

  5. Click OK.
    The colors details are listed in the Colors table.
  6. Click the add (+) icon above the Community table.
    The Community page appears. Use this page to manage the VPN communities available in the resource pool for auto-allocation when provisioning a service. A VPN route target community is a group of route targets that have similar routing policies.
  7. Enter the values by referring to the following table:
    Table 23: Fields on the Community Page

    Field

    Description

    Name*

    Enter a unique name for the route target community.

    Count*

    Enter the number of route targets included in the target community.

    Enter a value in the range 1 through 65,535.

    Pinned Reservation

    Reserve the community for specific services.

    Brownfield

    Enable this flag to reserve the route targets in the defined community for migrating brownfield services. The reserved route targets would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

    Disabling this flag while the reserved route targets are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

    Customer

    Select the customer whose services would use the route targets in the defined community. The route targets will be used exclusively by services created for the customer that you select here.

    Instance

    Enter the name of the service instance that can use the route targets in the defined community.

    Note:

    For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

    The route targets will be used only by the service that you enter here for the customer specified in Customer.

  8. Click OK.
    The route target community details are listed in the Community table.
  9. Add Type 0 Route Distinguishers (RDs) by clicking the + icon above the Route Distinguisher table.

    The Route Distinguisher page appears. Use this page to manage the route distinguishers available in the VPN resource pool for auto-allocation when provisioning a service. Route distinguishers uniquely identify routes belonging to different VPNs in the service provider network.

    The values configured here are available when you select the Type 0 Route Distinguisher type when configuring an EVPN or L3VPN service instance.

  10. Enter the values by referring to the following table:
    Table 24: Fields on the Route Distinguisher Type0 Page

    Field

    Description

    ASN*

    Enter a unique ID for the RD. Enter a value in the range 0 through 65,535.

    Block Size*

    Enter the number for the range of RDs with the unique ID available in the resource pool.

    Enter a value in the range 1 through 65,535.

    Pinned Reservation

    Reserve the RDs for specific services.

    Brownfield

    Enable this flag to reserve the defined route distinguishers (RDs) for migrating brownfield services. The reserved RDs would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

    Disabling this flag while the reserved RDs are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

    Customer

    Select a customer for whose service would use the defined route distinguishers (RDs). The RDs will be used exclusively by services created for the customer that you select here.

    Instance

    Enter the name of the service instance that can use the defined route distinguishers (RDs).

    Note:

    For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

    The RDs will be used exclusively by the service that you enter here for the customer specified in Customer.

  11. Click OK.
    The route distinguisher details are listed in the Route Distinguisher table.
    Note:

    Route distinguishers are automatically allocated if you do not define the route distinguisher details in the VPN resource pool.

  12. Click the add (+) icon above the Route Target table.
    The Route Target page appears. Use this page to manage the route targets available in the VPN resource pool for auto-allocation when provisioning a service. Route targets define the routes to be imported to or exported from a virtual routing and forwarding (VRF) table.
  13. Enter the values by referring to the following table:
    Table 25: Fields on the Route Target Page

    Field

    Description

    ASN*

    Enter a unique ID for the route target.

    Enter a value in the range 0 through 65,535.

    The values entered here are assigned using the Update Placements option when creating EVPN and L3VPN service instances. The ASN values are available as options in the Pool drop-down list.

    Block Size*

    Enter the maximum number of route targets to be made available in the resource pool.

    Enter a value in the range 1 through 4,294,967,295.

    The value entered here is assigned using the Update Placements option when creating EVPN and L3VPN service instances. The block size value is the upper limit for the route target Number.

    Pinned Reservation

    Reserve the route targets for specific services.

    Brownfield

    Enable this flag to reserve the defined route targets for migrating brownfield services. The reserved route targets would be used by services that are configured to use pinned resources and have the Brownfield flag enabled.

    Disabling this flag while the reserved route targets are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

    Customer

    Select the customer whose service would use the defined route targets. The route targets will be used exclusively by services provisioned for the customer that you select here.

    Instance

    Enter the name of the service instance that can use the defined route targets.

    Note:

    For migrating a brownfield service, the service instance name that you enter here must match with the service that you want to migrate.

    The route targets will be used exclusively by the service that you enter here for the customer specified in Customer.

  14. Click OK.
    The route target details are listed in the Route Target table.
  15. Click the add (+) icon above the Virtual Circuit Id table.
    The Virtual Circuit Id page appears. Use this page to manage the virtual circuit IDs available in the VPN resource pool for auto-allocation when provisioning a service.
  16. Enter the values by referring to the following table:
    Table 26: Fields on the Virtual Circuit ID Page

    Field

    Description

    Start*

    Enter the starting value for the range of virtual circuit IDs available in the resource pool.

    Enter a value in the range 0 through 4,294,967,295.

    Count*

    Enter the number of virtual circuit IDs available in the resource pool.

    Enter a value in the range 1 through 4,294,967,295.

    Pinned Reservation

    Reserve the virtual circuit IDs for specific services.

    Brownfield

    Enable this flag to reserve the virtual circuit IDs on the provider edge node for migrating brownfield services. The reserved virtual circuit IDs are used by services that are configured to use pinned resources and have the Brownfield flag enabled.

    Disabling this flag while the reserved virtual circuit IDs are in use by a service will release the reservation. If the service is reprovisioned without disabling the Brownfield flag, the service will be disrupted due to missing resource allocation.

    Customer

    Select a customer whose services would use the defined virtual circuit IDs. The defined virtual circuit IDs will be used exclusively by services provisioned for the customer that you select here.

    Instance

    Enter the name of the service instance that can use the defined virtual circuit IDs.

    Note:

    For migrating a brownfield service, the service instance name that you enter here must match with the name of the service that you want to migrate.

    The virtual circuit IDs will be used exclusively by the service that you enter here for the customer specified in Customer.

  17. Click OK.
    The virtual circuit details are listed in the Virtual Circuit Id table.
  18. (Optional) To edit or delete an entry in any of the tables, select the entry and click the edit or delete icons present above the table.
  19. Go to 2.b of the Configure a Network Resource Pool procedure to save and download the resource configuration and proceed with the resource instance edition.

See Also