Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

IP Pools (Resources)

IP Pool Overview

IP addresses are used in the following situations:

Loopback IPs - Spines/Leafs/Generics - the loopback IP is used as the BGP router ID.

SVI Subnets - MLAG Domain - A Switch Virtual Interfaces (SVI) subnet for an MLAG domain is used to allocate an IP address between MLAG leaf switches.

Link IPs - Spines <-> Leafs - Link IPs are used between spine devices and leaf devices to build the L3-CLOS fabric. These IPs are necessary for BGP peering between spine devices and leaf devices, and represent the 'fabric' of the network.

Link IPs - Generics - IP addresses facing generic systems are used to statically-route the generic system loopback and route across that link.

When you're building your blueprint you'll specify which resource pool to use for assigning IP addresses.

Note:

If you need to assign a specific IP address to a specific device, you can assign the IP address individually from the staged blueprint in the Properties panel of a selection.

IP pools include the following details:

Table 1: IPv4 Pool Parameters
Name Description
Pool Name A unique name to identify the resource pool
Total Usage Percentage of IP addresses in use for all subnets in the resource pool. (Hover over the status bar to see the number of IP addresses in use and the total number of IP addresses in the pool.)
Per Subnet Usage The IP addresses included in the subnet and the percentage that are in use. (Hover over the status bar to see the number of IP addresses in use and the total number of IP addresses in that subnet.)
Status Indicates if the pool is in use

From the left navigation menu, navigate to Resources > IP Pools to go to IP pools in the design (global) catalog. You can create, clone, edit and delete IPv4 pools.

Create IPv4 Pool

CAUTION:

IP address ranges are not validated. It is your responsibility to specify valid IP addresses. If you configure a switch with an invalid IP block you may receive an error during the deploy phase. For example, specifying the erroneous multicast subnet 224.0.0.0/4 would be accepted, but it would result in an unsuccessful deployment. If you assign the same range (or overlapping range) of IP addresses to a blueprint, the duplicate assignment is detected and you'll receive a warning in the blueprint. You can commit changes to blueprints with warnings without resolving the issues.
  1. From the left navigation menu, navigate to Resources > IP Pools and click Create IP Pool.
  2. Enter a unique name and valid subnet. To add another subnet, click Add a Subnet and enter a subnet.
  3. Click Create to create the pool and return to the table view.
When you've created your blueprint, you'll assign resources from these pools n the Staged > Physical view of the blueprint.

Edit IPv4 Pool

  1. Either from the table view (Resources > IP Pools) or the details view, click the Edit button for the pool to edit.
  2. Make your changes. You can add, change, and delete subnets, but you cannot delete any subnets if IP addresses are in use.
  3. Click Update to update the pool and return to the table view.

Delete IPv4 Pool

You can delete IP pools as long as none of the IP addresses within the pool are in use.
  1. Either from the table view (Resources > IP Pools) or the details view, click the Delete button for the pool to delete.
  2. Click Delete to delete the pool and return to the table view.