Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Update Physical Resource Assignments (Datacenter)

You can assign resources, release previously used resources and go to resource pool management. The resource assignment section has a convenient shortcut button, Manage resource pools, that takes you to resource pool management. From there, you can monitor resource usage and create additional resource pools, as needed.

Update Physical Resource Assignments

  1. From the blueprint, navigate to Staged > Physical > Build > Resources. (The build panel is on the right side.)
  2. Red status indicators mean that resources need to be assigned. Click a red status indicator, then click the Update assignments button.
  3. Select a pool from which to pull the resources, then click the Save button. The required number of resources are automatically assigned to the resource group. When the red status indicator turns green, the resource assignment has been successfully staged.
    Note:

    You can also assign resources on a per-device basis (especially useful if you have a predefined resource mapping). Select the device from the Topology view or Nodes view, then assign the resource from the Properties section of the Selection panel (right-side). Since you'd not be using a resource pool to assign from, the No pools assigned message remains in the Build panel. (This is also where you can see the specific resource that was assigned from a resource pool.)

Reset Physical Resource Group Overrides

Certain blueprint operations require resource allocations to be retained even when you've removed a device from a blueprint. Overridden resource groups re-use previously allocated resources when a device is re-used. For example, if you've deleted a rack, then you rollback to a version with that rack, the same resources must be used. Otherwise, the topology would change (for example, it might have different IP addresses). In the case of a revert operation, the originally assigned resources appear in the table view to indicate that they have been retained (but the build section shows that no resources are assigned). Situations like this can (but do not always) result in build errors. Examples of where we want resources to persist include:

  • Particular time voyager rollbacks (rack removal/addition and so on).
  • Revert operations.
  • Using the Update Stated Cabling Map from LLDP feature.

If you don't need to re-use the same resources, reset the resource groups by clicking the Reset resource group overrides button (shown in the overview image above). Then you can unallocate resources, and allocate new ones, as applicable.

See Also