Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA P6000 for Linux B.01.00.00

on the Management Servers and DR groups that will be used in Metrocluster environment. These
tools must be used to create or modify the map file caeva.map.
This product provides two utility tools for users to provide information about the SMI-S service
running on the Management Servers and DR groups that will be used in Metrocluster environment.
smispasswd
Metrocluster retrieves storage information from the SMIS-Server for its startup or failover operations.
To contact the SMIS-server, it requires SMIS Server's hostname/IP address, username/password,
and port number. This information must be available in caeva.map file before you configure any
Metrocluster packages. The smispasswd utility, packaged along with Metrocluster must be used
to create or edit this map file with the above SMI-S server login information.
evadiscovery
When querying HP P6000/EVA storage states through the SMI-S, Metrocluster first needs to find
the internal device IDs. This process takes time. However, this process need not be repeated because
the IDs are static in the P6000/EVA system. This information is cached in the caeva.map file to
improve package startup time. To cache the internal device IDs, run the evadiscovery tool after the
P6000/EVA and HP P6000 Continuous Access are configured, and the storage is accessible from
the hosts. The tool queries the active Management Server for the needed information, and then
saves it in caeva.map. Once the map file is created, it is necessary to distribute it to all the cluster
nodes to communicate with the HP P6000/EVA units.
Defining Management Server and SMI-S information
To define Management Server and SMI-S information use the smispasswd tool. The following
steps describe the options for defining Management Server and SMI-S information:
Creating the Management Server list
On a host that resides on the same data center as the active management server, create the
Management Server list using an input file. To create use the following steps:
1. Create a configuration input file. A template of this file is available at the following location
for Red Hat and SUSE. For an example of the smiseva.conf file, see“smiseva.conf file”
(page 40).
The smiseva.conf is available at:
$SGCONF/mccaeva/smiseva.conf
2. Copy the template file smiseva.conf to the desired location.
# cp $SGCONF/cmcaeva/smiseva.conf <desired location>
3. For each Management Server in your configuration (both local and remote sites), enter the
Management Server’s hostname or IP address, the administrator login name, type of connection
(secure or non-secure), SMI-S name space and SMI-S port.
Creating the Management Server Mapping file
Use the smispasswd command to create or modify the Management Server information stored
in the mapping file.
For each Management Server listed in the file, a password prompt is displayed. A username and
password is created by your system administrator when the Management Server is configured
because of the security protocol for P6000/EVA. Enter the password associated with the username
of the SMI-S, and then re-enter it (as prompted) to verify that it is correct.
# smispasswd -f <desired location>/smiseva.conf
Enter password of <hostname1/ip_address1>: **********
Re-enter password of <hostname1/ip_address1>: **********
Enter password of <hostname2/ip_address2>: **********
14 Configuring an application in a Metrocluster environment