Installing OVO8 on Veritas cluster.

[kignasiak]

I am installing OVO8 in a Veritas cluster enironment. After the install, I noticed the folwoing environmental variables were set to the local agent instead of the HA package name: CERTIFICATE_SERVER/ OPC_MGMT_SERVER, OPC_MGMT_SERVER were set to the local agent of the Management Server name instead of the HA package name(ito00p20) and raised the concerned that the certificate server and management server variables will not follow the package when it moves among the cluster. Any thought?

[0]hp37:bin/OpC/install> sudo ovconfget -ovrg server
[bbc.cb]
LOCAL_CONTROL_ONLY=true
LOCAL_INFO_ONLY=false
REQUEST_TIMEOUT=1
RESTRICT_REG=false
SERVER_BIND_ADDR=10.8.25.180
SERVER_PORT=383
SSL_REQUIRED=true

[bbc.fx]
FX_MAX_RETRIES=3

[bbc.http]
LOCAL_INFO_ONLY=false
LOG_SERVER_ACCESS=false
MAX_CONNECTIONS=0
SERVER_PORT=0

[bbc.http.ext.opc]
HOSTNAME_CACHE_TIMEOUT=-1

[bbc.snf]
MAX_FILE_BUFFER_SIZE=0

[coda]
SSL_SECURITY=NONE

[coda.comm]
LOG_SERVER_ACCESS=false
SERVER_PORT=0

[conf.cluster]
CLUSTER_TYPE=VERITAS Cluster Server (VCS)
MONITOR_MODE=TRUE
POLLING_INTERVAL=10000

[conf.core]
ASYNC_CONTROL_NOTIFY=false
CACHE_CONFIGSETTINGS_POLICIES=true
FORMAT_POLICY_LIST=false
MERGED_POLICY_LIST_FILENAME=ov_policies.txt

[conf.server]
AUDIT_LOGGING=false
AUDIT_LOG_MODE=ALL
LOCATE_SERVER=5
PING_SERVER=15
WAIT_TIME=3

[ctrl]
START_ON_BOOT=true

[ctrl.ovcd]
ACTION_TIMEOUT=60
KILL_TIMEOUT=15
MONITOR_CHECK_INTERVAL=2000
PROCESS_TIMEOUT=30

[ctrl.sudo]
OV_SUDO=""

[depl]
CMD_TIMEOUT=600000

[eaagt]
OPC_BUFLIMIT_SEVERITY=major
OPC_BUFLIMIT_SIZE=10000
OPC_HA_TRAPI=TRUE
OPC_HBP_INTERVAL_ON_AGENT=-1
OPC_INSTALLATION_TIME=Thu Jun 28 12:41:57 EDT 2007
OPC_INSTALLED_VERSION=08.10.160
OPC_IP_ADDRESS=10.8.27.37
OPC_NODE_CHARSET=iso88591
OPC_PRIMARY_MGR=ito00p20.windstream.com

[opc]
DATABASE=ov_net
HA_3TIER_CONFIGURATION=NO
HA_RESOURCE_GROUP=ito00p20
OPC_HA=TRUE
OPC_INSTALLATION_TIME=06/26/07 10:51:39
OPC_INSTALLED_VERSION=A.08.24
OPC_MGMTSV_CHARSET=iso885915
OPC_MGMT_SERVER=hp37.windstream.com
OPC_SG=FALSE
OPC_SVCM_ADD_WARN_IF_EXISTS=FALSE
OPC_SVCM_ERROR_CHECKING=NONE

[opc.patches]
PHSS_35526=Tue Jun 26 12:05:04 EDT 2007

[sec.cm.certificates]
CERT_INSTALLED=TRUE
LAST_CERT_UPDATE=Tue Jun 26 10:10:47 2007
LAST_TRUSTED_CERT_UPDATE=Tue Jun 26 10:10:47 2007

[sec.cm.client]
CERTIFICATE_SERVER=hp37.windstream.com

[sec.cm.server]
OVRG=server

[sec.cm.server.allowed]
SERVER=c19d8bee-60db-7525-183a-81a637306ba8

[sec.core]
CORE_ID=7c1e92f2-5fb9-7525-0cd0-8bbebd88fea4

[sec.core.auth]
MANAGER=ito00p20.windstream.com
MANAGER_ID=7c1e92f2-5fb9-7525-0cd0-8bbebd88fea4

[sec.core.auth.mapping.actionallow]
conf=80
ctrl=4
depl=1280
eaagt.actr=1

[sec.core.auth.mapping.manager]
conf=511
ctrl=15
depl=2047
eaagt.actr=1

[sec.core.auth.mapping.secondary]
conf=511
ctrl=15
depl=2047
eaagt.actr=1

[sec.core.ssl]
SESSION_CACHE_SIZE=5000
SESSION_CACHE_TIME_OUT=64800

[xpl.log]
addlocales=none
apSpecifcUseParent=true
handlers=none
logparent=false

[xpl.log.OvLogFileHandler]
filecount=10
filesize=1

[xpl.trc.server]
IsBindAny=YES

The Admin insist, and I believe true, that he always typed ito00p20 as the management server name during ovinstall.