HP XP P9000 Command View Advanced Edition Software - Manual (Page 442)

• A P9000 RAID Manager configuration definition file must be present.
If a copy pair is created using storage system operation management software (such as Remote
Web Console) and there is no configuration definition file, configuration definition information is
not displayed in the pair configurations view.
• The P9000 RAID Manager configuration definition file must be stored in the following default
directory:
Windows: system-folder (the folder represented by the
%windir% environment variable)
Systems other than Windows: / etc-directory
• When more than one copy pair is set to a single volume (when a multi-target or cascade config-
uration is being used), each combination of a copy group name and copy pair name defined in
the configuration definition file must be unique.
• The copy group name and copy pair name defined in the configuration definition file on a primary
volume must match the copy group name and copy pair name defined in the configuration defin-
ition file on the secondary volume.
• When the pair management server is managing multiple copy pairs, every port number, copy
group name, and copy pair name combination defined in the configuration definition file must be
unique in the pair management server.
• The settings specified in the configuration definition file must be within the ranges supported by
the Device Manager agent.
Depending on the version of Device Manager agent you are using, there are a number of limitations
that apply to the specification format and settings in the P9000 RAID Manager configuration definition
file. The range of specification formats (in the configuration definition file) that are supported by P9000
RAID Manager are the same as the range supported by Device Manager. For details about the
specification settings supported in configuration definition files, see the HP StorageWorks P9000
Command View Advanced Edition Suite Software Administrator Guide.
To view an example configuration in which copy groups containing copy pairs in simplex status and
a configuration definition file exist, see “
Configuration in which copy groups containing copy pairs
in simplex status and a configuration definition file exist (open systems) ” on page 442.
For mainframe systems
In the Hosts view or Storage Systems view, only the paired volumes (the volumes constituting copy
pairs) belonging to the host or storage system are displayed. However the volumes constituting copy
pairs in simplex status are not displayed, since they are nominal copy pairs and do not exist.
In the pair configurations view, configuration definition information, including the information about
the copy pairs in simplex status, is displayed based on the copy group definition file (prefix). However,
if a copy pair is created using storage system operation management software (such as Remote Web
Console) and there is no copy group definition file, the configuration definition information is not
displayed in the pair configurations view.
To view an example configuration in which two copy group definition files are used for the same
copy group (for mainframe systems), see “
Example configuration in which two copy group definition
files are used for the same copy group (for mainframe systems) ” on page 443.
Configuration in which copy groups containing copy pairs in simplex status and a configuration
definition file exist (open systems)
In this example, copy groups containing copy pairs in simplex status and a configuration definition
file exist. In the example, in the Hosts or Storage Systems view, volumes
5:11 and 4:88 , which
belong to copy group CG.CntAc-A01 , are displayed in the Paired list, and volumes 6:11 and 5:88 ,
which belong to copy group CG.CntAc-A02 , are displayed in the Unpaired list. In the pair
Exceptions 442