HP 3PAR Command Line Interface Administrator's Manual: HP 3PAR OS 3.1.2 (QR482-96525, September 2013)

Managing Domain Objects
Domain objects can be moved in and out of a domain, or have their domain associations entirely
removed. In doing so, all objects related either directly or indirectly to the domain object being
managed are also moved or removed. These relationships include, but are not limited to, VLUNs
between hosts and VVs, VVs which are drawing from CPGs and multiple VVs sharing the same
LD. In order to move or remove a domain object or domain association, you must have Super or
Edit user rights with access to all domains.
NOTE: Before proceeding with any domain management activities, you may want to view the
domain associations for your system objects as described in “Viewing Domains” (page 59).
Moving Domain Objects to Another Domain
To move a domain object in or out of a domain, issue the movetodomain -vv|-cpg|-host
<object_name><domain_name>|set:<set_name> command, where:
• -vv|-cpg|-host is the type of object (VV, CPG, host, respectively) you are moving.
• <object_name> is the name of the VV, CPG, or host you are moving.
• <domain_name> is the name of the domain to which you are moving the specified object.
• <set_name> is the name of the domain set to which you are moving the specified host.
NOTE: If a CPG or VV in a CPG is part of an Adaptive Optimization configuration (aocfg), then
if the VV or CPG is specified as the target of a movetodomain command, all CPGs and related
VVs in the aocfg will also be moved to the target domain.
Removing the Domain Association from a Domain Object
To remove the domain association from a domain object, issue the movetodomain
-vv|-cpg|-host <object_name> -unset command, where:
• -vv|-cpg|-host is the type of object (VV, CPG, host, respectively) from which you are
removing the domain association.
• <object_name> is the name of the VV, CPG, or host from which you are removing the
domain association.
Managing Virtual Domain Autonomic Groups
Virtual domains can be combined into autonomic groups. A autonomic groups are sets of objects
that can be managed as one object. If you have a group of domains that require the same
administrative procedures, it is easier to group those domains into a set and manage them together.
For example, you can create a domain set and put all of the hosts in a cluster into a host set. By
setting the domain of the hosts in the host set to the newly created domain set, all the virtual volumes
exported to one host in the cluster are accessible to all the hosts in the cluster. If one of the hosts
in the cluster is a backup host, all of the virtual volumes in the domain set can access the backup
host. Without domain sets there is no way for a host to access volumes from different domains at
the same time. Individual domains can be members of multiple domain sets.
Hosts are the only objects that can be members of a domain set. All other objects can only belong
to a single domain. If a host that is a member of a domain set is moved with the movetodomain
command to an individual domain, then all objects associated with the host must be members of
the destination domain or the command will fail. Moving a host to a domain set does not change
the domain of any objects associated with the host. If a volume is exported to a host that is a
member of a domain set that is selected directly or indirectly by the movetodomain command,
and if the domain set includes the destination domain of the volume, the move does not propagate
to the host or any of the volumes exported to the host.
60 Managing HP 3PAR Virtual Domains