VCS Switch Over problem
Hi,
I do have som problems when testing Cluster Switch (2 node cluster VCS 6.2, Solaris 10). We test with init 6. Active node always hangs with :
2014/02/09 08:07:36 VCS ERROR V-16-10001-11511 (node1) Volume:vol_v1:offline:Cannot find Volume v1, either the Volume is a Volume Set or Veritas Volume Manager configuration daemon (vxconfigd) is not in enabled mode
2014/02/09 08:07:36 VCS INFO V-16-6-15002 (node1) hatrigger:hatrigger executed /opt/VRTSvcs/bin/triggers/resstatechange node1 mnt_1 ONLINE OFFLINE successfully
2014/02/09 08:07:37 VCS INFO V-16-2-13716 (node1) Resource(vol_v1): Output of the completed operation (offline)
==============================================
VxVM vxprint ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
==============================================
2014/02/09 08:07:37 VCS ERROR V-16-2-13064 (node1) Agent is calling clean for resource(vol_v1) because the resource is up even after offline completed.
2014/02/09 08:07:37 VCS ERROR V-16-10001-11511 (node1) Volume:vol_v1:clean:Cannot find Volume v1, either the Volume is a Volume Set or Veritas Volume Manager configuration daemon (vxconfigd) is not in enabled mode
2014/02/09 08:07:38 VCS INFO V-16-2-13716 (node1) Resource(vol_v1): Output of the completed operation (clean)
==============================================
VxVM vxprint ERROR V-5-1-684 IPC failure: Configuration daemon is not accessible
==============================================
I noticed that the init script /etc/rc0.d/K99vxvm-shutdown does stop the vxconfigd and also does "/usr/sbin/vxdctl -k stop".
My question is do I need any vxvm init script since the upgrade from 5 to 6.1 is done and we have SMF service in place, or should I increase the timeouts of the VCS stop procedures?
Thanks a lot in advance!
Cheers
I only have access to a 5.1 system. 5.0 has limited support so there are not many customers still running this - see https://sort.symantec.com/eosl/show_matrix:
Product Version Platform Country End of Support
Life DateEnd of Limited Support Date Release Date Storage Foundation for UNIX/Linux 5.0 MP3 Solaris Worldwide 2014-08-31 2012-06-07 2008-10-06 Solaris x86-64 Worldwide 2014-08-31 2012-06-07 2008-10-06 Linux Worldwide 2014-08-31 2012-06-07 2008-08-20 AIX Worldwide 2014-08-31 2012-06-07 2008-10-06 So it is quite likely that VCS 6.0 was not tested with vxvm 5.0 which could be why vxvm is shutting down before VCS or it could be you have some obsolete rc scripts.
As before, I would shut VCS down manually before rebooting system which is good practice in any case, even after you have upgraded vxvm to 6.0 - i.e if you are shutting down node A, then you should manually switch service groups to node B (to ensure they online successfully on node B before shutting down node A), or offline groups if you are shutting both nodes down.
Mike