There is normally no way of VCS knowing why a resource is failing, so in your case the vxconfigd is dying - so VCS just sees it is not there when it checks - it doesn't know why it is down and with several other resources, they are timing out:
2013/05/03 14:28:17 VCS ERROR V-16-2-13027 (EMMDPD07) Resource(Server1) - monitor procedure did not complete within the expected time.
2013/05/03 14:28:26 VCS ERROR V-16-2-13027 (EMMDPD04) Resource(Server2) - monitor procedure did not complete within the expected time.
2013/05/03 14:28:31 VCS ERROR V-16-2-13027 (EMMDPD04) Resource(fmmweb) - monitor procedure did not complete within the expected time.
2013/05/03 14:29:06 VCS ERROR V-16-2-13027 (EMMDPD07) Resource(licserv) - monitor procedure did not complete within the expected time.
2013/05/03 14:31:51 VCS ERROR V-16-2-13027 (EMMDPD05) Resource(cfsmount2) - monitor procedure did not complete within the expected time.
If a resource monitor times out more times than is set by FaultOnMonitorTimeouts then it faults, but this is by default 4, so for most resources you are seeing:
2013/05/03 14:38:06 VCS INFO V-16-2-13026 (EMMDPD07) Resource(licserv) - monitor procedure finished successfully after failing to complete within the expected time for (2) consecutive times.
So the resource does not fault, but I do see
2013/05/03 14:31:52 VCS ERROR V-16-2-13210 (EMMDPD07) Agent is calling clean for resource(cfsmount2) because 1 successive invocations of the monitor procedure did not complete within the expected time.
So this suggests that that maybe FaultOnMonitorTimeouts for the CFSMount resource type has been changed from its default of 4
However this resource recovers on its own:
2013/05/03 14:31:53 VCS INFO V-16-2-13082 (EMMDPD04) Resource(cfsmount2) recovered from fault, on its own.
So as you have several different types of resources timing out, this is probably caused by a system resource issue so the monitors do not have enough system resource (CPU and memory) to complete the monitor entrypoint in time and low system resource, MAY also be causing vxconfigd to be failing.
Mike