Building Disaster Recovery Serviceguard Solutions Using Metrocluster with Continuous Access EVA A.05.01

C smiseva.conf file
##############################################################
## ##
## smiseva.conf CONFIGURATION FILE (template)for use with ##
## the smispasswd utility in the Metrocluster Continuous ##
## Access EVA Environment. ##
## Note: This file MUST be edited before it can be used. ##
## For complete details about Management Server/SMI-S ##
## configuration for use with Metrocluster Continuous ##
## Access EVA, consult “Designing Disaster Tolerant High ##
## Availability Clusters. ##
##############################################################
## This file provides input to the smispasswd utility, ##
## which you use to set up secure access paths between ##
## cluster nodes and SMI-S services. ##
## Edit this file to include the appropriate information ##
## about the SMI-S services that will be used in your ##
## Metrocluster Continuous Access EVA environment. ##
## After entering all the desired information, run the ##
## smispasswd command to generate the security ##
## configuration that allows cluster nodes to communicate ##
## with the SMI-S services. ##
## Below is an example configuration. The data is ##
## commented out. ##
## Hostname/IP_Address User_login_name Secure Namespace ##
## IP_Address Connection ##
## 15.13.244.182 administrator y root/EVA ##
## 15.13.244.183 administrator y root/EVA ##
## 15.13.244.192 admin12309 y root/EVA ##
## SANMA04 admin y root/EVA ##
############################################################
## The example shows a list of 4 Management Server/SMI-S ##
## data in the Metrocluster Continuous Access EVA ##
## environment. Each line represents a different SMI-S’s ##
## data; fields on each line should be separated either by ##
## space(s)or tab(s). The order of fields is significant. ##
## The first field must be a hostname or IP address, the ##
## second field must be a user login name on the host. The ##
## third field must be ‘y’ or ‘n’ to use SSL connect. The ##
## last field must be the namespace of the SMI-S service. ##
## For details of each field data, refer to the smispasswd ##
## man page, ‘man smispasswd’. ##
#############################################################
## Note: Lines beginning with the pound sign (#) are ##
## comments. You # cannot use the ‘#’ character in your ##
## data entries. Enter your SMI-S services data under the ##
## dashed lines: ##
## Hostname/IP_Address User_login_name Secure Namespace ##
## IP_Address Connection ##
## 15.13.172.11 administrator n root/EVA ##
## 15.13.172.12 administrator n root/EVA ##
###############################################################
86 smiseva.conf file