White Papers

12 Create Virtual IO Pools
Virtual IO pools simplify identity management in OME. This section explains how to create a virtual IO pool
from a prefix definition or from an import file. Also covered in this section is how to increase a virtual IO
pool’s size and lock or unlock a virtual IO pool.
12.1 Virtual IO Pool definition
A virtual IO pool is a definition of identity types that describe identities and determines the identities OME
will generate. A virtual IO pool may contain identity definitions for different types of identities.
12.2 Types of identities
Virtual IO pools may contain different identity type definitions. Identity types define the identity properties
required for a specific network protocol; for example an Ethernet MAC address.
An identity type is defined by specifying a prefix and the number of predefined octets (except for IQN
which is defined by an IQN seed string) or by importing identities from a file. The number of predefined
octets is how many octets are defined by the user. All generated identities of that identity type will begin
with the prefix. Any remaining octets are used to generate addresses by OME. The number of predefined
octets allows OME to know when to stop generating address so overlap does not occur. Imported
identities must be unique and pass the restriction checks mentioned below. Imported identities are used
as is by OME.
12.2.1 MAC Address Definition
MAC addresses are used for virtual MAC address properties. It is recommended to define this in all SAN
types.
An example of MAC address is
00-14-22-01-23-45 . Please note that this will vary depending on the
environment and vendor HBA cards.
Restrictions:
MAC address prefixes cannot be a multicast address. A multicast address is an address with a value of 1 in
the least-significant bit of the first octet. (So 01, 03, 0B etc. are not allowed).
Defined by:
- Prefix address
- Number of predefined octets
Or
- Imported identities
22 Stateless Deployment with Dell OpenManage Essentials | Revision A00