InfoScale/VCS resources are not probed by cluster after VCS upgradation

Problem

VCS Service Groups or resources are not probed by cluster after VCS upgradation due to upgrade issue with types.cf file.

Error Message

No error message will be seen. Service Groups will not come online and resource will be in un-probed state after VCS Cluster upgrade. ( e.g. Disk, Volume, mount,MultiNICB, Application, Phantom etc). The Service Groups may also be put into AutoDisabled in the cluster.

Cause

During VCS Cluster upgrade, a new types.cf file will be copied over from /etc/VRTSvcs/conf/ to /etc/VRTSvcs/conf/config/. This file sometimes does not get copied over correctly. Causing VCS to not be able to probe resources in the cluster.

Solution

To resolve this issue, copy over the types.cf from /etc/VRTSvcs/conf/ to /etc/VRTSvcs/conf/config/. This will ensure you have the most up-to-date types.cf file for VCS to use.

You may see a size difference in the file sizes that confirms an issue during upgrade.

# ls -l /etc/VRTSvcs/conf/types.cf
-r--r--r--   1 root     sys         9842 Jul  1  2008 /etc/VRTSvcs/conf/types.cf

# ls -l /etc/VRTSvcs/conf/config/types.cf
-rw-------   2 root     sys         7762 Mar  7 19:52 /etc/VRTSvcs/conf/config/types.cf

1. Stop the cluster on ALL nodes (applications will continue to run, but not failover) using -
# hastop -all -force

2. Backup the original types.cf file using -
# mv /etc/VRTSvcs/conf/config/types.cf /etc/VRTSvcs/conf/config/types.cf.<date>

3. Copy the types.cf file -
# cp /etc/VRTSvcs/conf/types.cf /etc/VRTSvcs/conf/config/types.cf

4. Verify the size both types.cf file again, they should be identical -
# ls -l /etc/VRTSvcs/conf/types.cf
# ls -l /etc/VRTSvcs/conf/config/types.cf

5. Start the cluster on the node using -
# hastart

NOTES:
* The cp and hastart commands need to executed on all nodes in the cluster.
* Verify the types.cf file did not revert back to the original version.  If so, then the procedure will need to be repeated and LLT and GAB will also need to be shut down after the hastop command is executed.

 Another Option is to do the following:

1) Extract the new types.cf that come with the new (Rolling Patch) version
2) After having updated kernel packages and rebooted, override the current types.cf with the new one
3) Perform non kernel packages upgrading (this step will ensure not losing customized Agent attributes).