White Papers

Create virtual I/O pools
34 Server Hardware Provisioning and OS Deployment by using Dell EMC OpenManage Essentials
14.3.1.2 Import identities from a CSV file
To import identities from a file:
1. Under the Create Virtual I/O Pool in the identity type screen (example Ethernet Identities screen)
click Import from file
2. Click Import.
3. In the import dialog box, click Import.
4. Select a file.
5. Wait for the import to finish (progress bar shows the status).
6. Review results and close the results.
7. (Optional) import additional files (repeat steps 3—6).
8. Click Close.
The imported identities may be viewed in this wizard by clicking the View button in the Create Virtual I/O
pool wizard.
14.4 Increase the size of Virtual I/O Pool
While assigning or deploying identities, a Virtual I/O pool may run out of identities. The number of identities in
a Virtual I/O pool may be increased. This section describes how to increase the size of a Virtual I/O pool.
14.4.1 Increase the size of start address‒based identity
To increase the number of identities for an identity defined by a start address, increase the number of
identities. This can be done by editing the Virtual I/O pool and increasing the number of identities field.
14.4.2 Increase the size of import-based identity
To increase the number of identities for an identity defined by an import file, import more identities by using
file. The import operation does not overwrite the previous identities and is an additive operation. To know how
to import identities to a Virtual I/O pool, see Import identities from a CSV file.
14.5 Lock and unlock the Virtual I/O pool
The lock state of the Virtual I/O pool is determined by the lock state of all the compute pools associated to
that Virtual I/O pool. A locked Virtual I/O pool cannot change the identity type definitions or imported identities
of the Virtual I/O pool. To unlock the Virtual I/O pool, unlock all the locked compute pools associated to the
Virtual I/O pool. The Compute Pool Summary page is useful for sorting by Virtual I/O pool and the lock state.
It is suggested to perform this only if you plan about redeploying to call devices in the previously locked
compute pools.