Mount resources in UNKNOWN state after upgrading/modifying the Veritas Cluster Server (VCS) cluster configuration

Article:TECH157024  |  Created: 2011-03-31  |  Updated: 2011-03-31  |  Article URL http://www.symantec.com/docs/TECH157024
Article Type
Technical Solution

Product(s)

Environment

Issue



Mount resources in UNKNOWN state after upgrading/modifying the VCS cluster configuration


Error



# hares -display mnt1 -sys blender

mnt1 State blender OFFLINE|STATE UNKNOWN
 


Cause



When upgrading Veritas Cluster Server (VCS) the file types.cf (/etc/VRTSvcs/conf/config/types.cf) used to define bundled resource types was not updated.
This lead to agent binaries/scripts being passed an unexpected number of arguments during resource probe and meant that the cluster high availability daemon (had) was unable to determine the state of cluster resources after start up.


Solution



To solve the issue had should be stopped and /etc/VRTSvcs/conf/config/types.cf replaced with the correct copy for the currently running version of VCS. This is normally placed at /etc/VRTSvcs/conf/types.cf during the VCS upgrade/installation.


Supplemental Materials

Description

The following shows an example of the scenario for a single node cluster with a Mount resource where VCS has just been upgraded from 5.0 to 5.0MP1 on HP-UX 11.31. Note that it is possible for similar issues to occur regardless of operating system as VCS requires the correct types.cf to be in place when started to sucessfully monitor resources/

blender# hastatus -sum

-- SYSTEM STATE
-- System               State                Frozen

A  blender      RUNNING              0

-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State

B  sg1               blender                        N              Y               OFFLINE

-- RESOURCES NOT PROBED
-- Group           Type                 Resource             System

D  sg1             Mount                mnt1                 blender    <<<<<<<<< mnt1 is NOT probed
blender# hares -state
#Resource    Attribute           System          Value
mdg          State               blender              OFFLINE
mnt1         State               blender              OFFLINE|STATE UNKNOWN    <<<<<<<<<<<< and here we see it was set to UNKNOWN

After upgrading VCS was simply restarted using hastart command without copying the new types.cf into place.
The following shows the difference between the old and new types.cf files:

Old types.cf:


type Mount (
        static keylist SupportedActions = { "mountpoint.vfd", "mounted.vfd", "vxfslic.vfd" }            static str ArgList[] = { MountPoint, BlockDevice, FSType, MountOpt, FsckOpt, SnapUmount, CkptUmount, SecondLevelMonitor, SecondLevelTimeout }

New types.cf:
type Mount (
        static keylist RegList = { VxFSMountLock }
        static keylist SupportedActions = { "mountpoint.vfd", "mounted.vfd", "mountentry.vfd", "vxfslic.vfd", chgmntlock }
        static str ArgList[] = { MountPoint, BlockDevice, FSType, MountOpt, FsckOpt, SnapUmount, CkptUmount, SecondLevelMonitor, SecondLevelTimeout, VxFSMountLock, State }

As shown the new VCS 5.0MP1 Mount Agent needs some additional entries from the types.cf to properly managed the Mount resources.

To solve the issue simply stop the high availability daemon, replace the types.cf and restart the high availability daemon.

blender# hastop -all # it will work for both single and multi node clusters
blender# cp /etc/VRTSvcs/conf/config/types.cf /etc/VRTSvcs/conf/config/types.cf_pre50mp3upgrade
blender# cp /etc/VRTSvcs/conf/types.cf /etc/VRTSvcs/conf/config
blender# hastart -onenode # if it is a single node cluster. hastart without any options if it is a multi node cluster
blender# hastatus -sum
-- SYSTEM STATE
-- System               State                Frozen
A  blender            RUNNING              0
-- GROUP STATE
-- Group           System               Probed     AutoDisabled    State
B  sg1             blender                         Y                 N               OFFLINE
                                                                                                           <<<<<<<<<<<<<<<<< Resources are no longer in NOT PROBED state!
# hares -state
#Resource    Attribute           System          Value
mdg          State               blender                  OFFLINE
mnt1         State               blender                  OFFLINE         <<<<<<<<<< mnt1 now is properly probed and is currently OFFLINE

IMPORTANT! If the types.cf was previously customised i.e. via hatype -modify commands or using the VOM/HAGUI, such changes will need to be re-applied after types.cf replacement.



Article URL http://www.symantec.com/docs/TECH157024


Terms of use for this information are found in Legal Notices