Hi Sigi,

I'm guessing that you are using SFW-HA 5.1 SP2 - the windows product.  If this is not what you are using please let us know.

With the upgrade to 5.1 SP2 there are some types changes that happen with a few agents including the MountV resource.  There can be a issue with the types.cf file if performing a rolling upgrade and not following the steps as outlined in the Installation and Upgrade Guide exactly where the types.cf file is acidently reverted back to an older version after the upgrade.

Please open your type.cf file in the %vcs_home%\conf\config folder and check the MountV entry.  

For SFW-HA 5.1 SP2 it should appear as follows for :

type MountV (
    static i18nstr ArgList[] = { MountPath, VolumeName, "VMDGResName:DiskGroupName", ForceUnmount, ListApplications, AutoFSClean, "VMDGResName:DGGuid", PurgeStaleMountPoints, CheckFSAccess }
    i18nstr MountPath
    str VolumeName
    str VMDGResName
    str ForceUnmount = READ_ONLY
    boolean ListApplications = 1
    boolean AutoFSClean = 1
    str MountResName
    boolean PurgeStaleMountPoints = 1
    boolean CheckFSAccess = 0
)
 

Here is an example of what SFW-HA 5.1 SP1 MountV types looks like:

type MountV (
static keylist SupportedActions = {CheckFSAccess}
static i18nstr ArgList[] = {MountPath, VolumeName,
"VMDGResName:DiskGroupName", ForceUnmount, ListApplications,
AutoFSClean, "VMDGResName:DGGuid", "MountResName:MountPath",
PurgeStaleMountPoints}
i18nstr MountPath
str VolumeName
str VMDGResName
str ForceUnmount = READ-ONLY
boolean ListApplications = 0
boolean AutoFSClean = 0
str MountResName
boolean PurgeStaleMountPoints = 0
)

Notice the change in the CheckFSAccess line between the two versions (hightlighted in bold.)

If you find that you are using the older types.cf file/MountV definition, please open a case with Symantec Technical Support so that we can work with you to get a new 5.1 SP2 Types.cf file that matches your configuration with the correct enterprise agents that you are running.

Thanks,

Wally