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.

Modify 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:

Configure topology resources by specifying them in the network implementation plan. See Configure Topology Resources in Network Implementation Plan. You cannot create a topology resource instance from the Add New Resource Instances page. See Add a Resource Instance.

For resource instances created in releases earlier than release 2.8.0, you can only modify them from the resource instance page.

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

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. Configure the ESI (Ethernet Segment Identifier). 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.
    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 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 name for the ESI pool.

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

      Prefix

      Enter the starting octets of the ESI ID. For example, 01:02:03.

      This value is prepended as the fixed prefix of the ESI ID and can be empty or up to 9 octets.

      The combined length of the prefix, middle range, and suffix must be 10 octets.

      Start*

      Enter the starting value for the variable middle range of the ESI ID.

      The middle range must be between 1 and 4 octets in length. The starting value must be of the same length as the ending value.

      For example, if you enter 00:01 as the Start value and 00:05 as the End value, the middle part of the ESI ID will be a value between 00:01 and 00:05.

      End*

      Enter the ending value for the variable middle range of the ESI ID.

      The middle range must be between 1 and 4 octets in length. The ending value must be the same length as the starting value.

      For example, if you enter 00:01 as the Start value and 00:05 as the End value, the middle of the ESI ID will be a value between 00:01 and 00:05.

      Suffix

      Enter the ending octets of the ESI ID. For example, 08:09:10.

      The number is appended as the suffix of the ESI ID and can be empty or up to 9 octets.

      The combined length of the prefix, middle range, and suffix must be 10 octets.

      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 the EVPN ESI (Deprecated) details:
    Note:

    This section is deprecated and is available only to support service instances provisioned in releases prior to 2.8.0. We recommend that you migrate service instances from earlier releases to the new EVPN ESI configuration. For any newly created multihomed instance, only the new EVPN ESI resource will be allocated.
  5. 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.
  6. 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.
  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. 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 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 10: 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 11: Fields on the Community Page

    Field

    Description

    Prefix*

    Enter a unique identifier for the route target community in the target:ASN format.

    For example, target:10458. A prefix value of target:10458 will derive a community ID of target:10458:20.

    Count*

    Enter the number of route targets included in the target community. Enter a value in the range 1 through 65,535.

    For example, a count of 20 will derive route target community IDs from target:10458:0 through target:10458:19.

    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 12: 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 13: 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 14: 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