Customer setup a new CVM configuration into an already running VCS cluster. Customer attempted to start CVM using hagrp command and vxclustadm but it failed.
Reviewing the main.cf it was noted that the resource names were capatalized.
PROBLEM main.cf:
group CVM (
SystemList = { sprpe1950-01 = 0, sprpe1950-02 = 1 }
AutoFailOver = 0
Parallel = 1
Authority = 1
AutoStartList = { sprpe1950-01, sprpe1950-02 }
)
CFSfsckd CVM_fsckd (
ActivationMode @sprpe1950-01 = { oradg = sw, testdg = sw, datadg = sw }
ActivationMode @sprpe1950-02 = { oradg = sw, testdg = sw, datadg = sw }
)
CVMCluster CVM_Clus(
CVMClustName = rac_cluster
CVMNodeId = { sprpe1950-01 = 0, sprpe1950-02 = 1 }
CVMTransport = gab
CVMTimeout = 200
)
CVMVxconfigd CVM_vxconfigd (
Critical = 0
CVMVxconfigdArgs = { syslog }
)
CVM_fsckd requires CVM_Clus
CVM_Clus requires CVM_vxconfigd
Note: CVM and CFS resource names are not to be modified as they are special to the CVM/CFS Agent and monitor script. Modification of the resources will result in CVM / CFS failing to start/online.
Solution change the resource names from Upper case to lower case.
group cvm (
SystemList = { sprpe1950-01 = 0, sprpe1950-02 = 1 }
AutoFailOver = 0
Parallel = 1
Authority = 1
AutoStartList = { sprpe1950-01, sprpe1950-02 }
)
CFSfsckd cvm_fsckd (
ActivationMode @sprpe1950-01 = { oradg = sw, testdg = sw, datadg = sw }
ActivationMode @sprpe1950-02 = { oradg = sw, testdg = sw, datadg = sw }
)
CVMCluster cvm_clus (
CVMClustName = rac_cluster
CVMNodeId = { sprpe1950-01 = 0, sprpe1950-02 = 1 }
CVMTransport = gab
CVMTimeout = 200
)
CVMVxconfigd cvm_vxconfigd (
Critical = 0
CVMVxconfigdArgs = { syslog }
)
cvm_fsckd requires cvm_clus
cvm_clus requires cvm_vxconfigd