Universe displays the pools, collections of identities, or physical
or logical resources, that are available in the system. All pools increase the
flexibility of service profiles and allow you to centrally manage your system
resources. Pools that are defined in
Cisco UCS Central are called Global Pools and can be shared between
Cisco UCS domains. Global Pools allow centralized ID management across
Cisco UCS domains that are registered with
Cisco UCS Central. By allocating ID pools from
Cisco UCS Central to
Cisco UCS Manager, you can track how and where the IDs are used, prevent conflicts,
and be notified if a conflict occurs. Pools that are defined locally in
Cisco UCS Manager are called Domain Pools.
The same ID can
exist in different pools, but can be assigned only once. Two blocks in the same
pool cannot have the same ID.
You can pool
identifying information, such as MAC addresses, to preassign ranges for servers
that host specific applications. For example, you can configure all database
Cisco UCS domains within the same range of MAC addresses, UUIDs, and WWNs.
Universe page, you can view the total number IDs for each type of
pool, and how many of the total are
Use, or have a
Conflict. If you click on a
Resource, you can view detailed information about
that ID and where it is used.
IP pools are a
collection of IP addresses. You can use IP pools in
Cisco UCS Central in one of the following ways:
Cisco UCS Managerservers.
For iSCSI boot
external management and iSCSI boot initiators in
Cisco UCS Manager.
The IP pool must not
contain any IP addresses that have been assigned as static IP addresses for a
server or service profile.
A fault is raised if
the same IP address is assigned to two different
Cisco UCS domains. If you want to use the same IP address, you can use the
scope property to specify whether the IP addresses
in the block are public or private:
Cisco UCS Central creates public IP pools by default.
Global IP pools
should be used for similar geographic locations. If the IP addressing schemes
are different, the same IP pool cannot be used for those sites.
Cisco UCS Central supports creating and deleting IPv4 and IPv6 blocks in IP pools.
However, iSCSI boot initiators support only IPv4 blocks.
An IQN pool is a
collection of iSCSI Qualified Names (IQNs) for use as initiator identifiers by
iSCSI vNICs in a
Cisco UCS domain. IQN pools created in
Cisco UCS Central can be shared between
Cisco UCS domains.
IQN pool members are
of the form
you can specify the prefix, suffix, and a block (range) of numbers.
An IQN pool can
contain more than one IQN block, with different number ranges and different
suffixes, but share the same prefix.
A MAC pool is a
collection of network identities or MAC addresses that are unique in their
layer 2 environment and are available to be assigned to vNICs on a server. MAC
pools created in
Cisco UCS Centralcan be shared between
Cisco UCS domains. If you use MAC pools in service profiles, you do not have to
manually configure the MAC addresses to be used by the server associated with
the service profile.
In a system that
implements multi-tenancy, you can use the organizational hierarchy to ensure
that MAC pools can only be used by specific applications or business services.
Cisco UCS Central
uses the name resolution policy to assign MAC addresses from the pool.
To assign a MAC
address to a server, you must include the MAC pool in a vNIC policy. The vNIC
policy is then included in the service profile assigned to that server.
You can specify your
own MAC addresses or use a group of MAC addresses provided by Cisco.
A UUID suffix pool
is a collection of SMBIOS UUIDs that are available to be assigned to servers.
The first number of digits that constitute the prefix of the UUID are fixed.
The remaining digits, the UUID suffix, are variable values. A UUID suffix pool
ensures that these variable values are unique for each server associated with a
service profile which uses that particular pool to avoid conflicts.
If you use UUID
suffix pools in service profiles, you do not have to manually configure the
UUID of the server associated with the service profile. Assigning global UUID
suffix pools from
Cisco UCS Central to service profiles in
Cisco UCS Central or
Cisco UCS Manager allows them to be shared across
Cisco UCS domains.
A WWN pool is a
collection of WWNs for use by the Fibre Channel vHBAs in a
Cisco UCS domain. WWN pools created in
Cisco UCS Central can be shared between
Cisco UCS domain. You create separate pools for the following:
WW node names
assigned to the server
WW port names
assigned to the vHBA
Both WW node
names and WW port names
A WWN pool can
include only WWNNs or WWPNs in the ranges from 20:00:00:00:00:00:00:00 to
20:FF:FF:FF:FF:FF:FF:FF or from 50:00:00:00:00:00:00:00 to
5F:FF:FF:FF:FF:FF:FF:FF. All other WWN ranges are reserved. To ensure the
uniqueness of the
Cisco UCS WWNNs and WWPNs in the SAN fabric, we recommend that you use the
following WWN prefix for all blocks in a pool: 20:00:00:25:B5:XX:XX:XX
If you use WWN pools
in service profiles, you do not have to manually configure the WWNs that will
be used by the server associated with the service profile. In a system that
implements multi-tenancy, you can use a WWN pool to control the WWNs used by
You assign WWNs to
pools in blocks.
A World Wide Node
Names (WWNN) pool is a WWN pool that contains only WW node names. If you
include a pool of WWNNs in a service profile, the associated server is assigned
a WWNN from that pool.
A World Wide Port
Name (WWPN) pool is a WWN pool that contains only WW port names. If you include
a pool of WWPNs in a service profile, the port on each vHBA of the associated
server is assigned a WWPN from that pool.
A WWxN pool is a WWN
pool that contains both WW node names and WW port names. You can specify how
many ports per node are created with WWxN pools. The pool size for WWxN pools
must be a multiple of
ports-per-node + 1. For example, if there are 7 ports
per node, the pool size must be a multiple of 8. If there are 63 ports per
node, the pool size must be a multiple of 64.