WARNING V-16-2-13139 ERROR V-16-2-13027

Hi Zahid,

The monitor cycle timing out should cause the resource to go into an "Unknown" state.  The cluster does not know how to handle unknown states so it is not able to do anything to correct the situation expect wait until for a monitor cycle to complete successfully with online or offline state of the resource.

The resource being in an Uknown state will not directly cause an issue with another resource.  However, if the resoure monitor completes successfully and causes a fault, then the rest of the resource may be brought offline as a result.  If the resource is set to non-critical and it has no critical resources depended on it then the group should not fault.  The bottom line is that it depends on a lot of factors to say if it will evently cause the group to fault or not.

You should check the agent log to see if it gives you more details on why the monitor did not complete in the time expected. 

Thank you,

Wally

As Wally says, "it depends on a lot of factors to say if it will evently cause the group to fault or not".

Therefore, also check to see what your FaultOnMonitorTimeouts attribute is set to for the DiskGroup Type, and consider localizing and then increasing it. 

-$ hatype -display DiskGroup | grep -i fault
DiskGroup    FaultOnMonitorTimeouts 4

Usually when VCS resource monitor routines do not complete within their alloted timeout periods, it means you've got to either add more physical resources to your server (RAM, CPUs, etc), or you need to move some workloads off your server. 

Thanks all for your valueable comments. Is it possible that we can use the new Diskgroup but VCS dont monitor it ?

As this is not a production Diskgroup and removing it from VCS monitoring will not cause us anything. Furthermore these WARNINGS and ERRORS ( WARNING V-16-2-13139 ERROR V-16-2-13027 ) will not be appear on Production if we can disable monitoring on new DIskgroup

Disable a service group to prevent it from coming online. This process temporarily stops VCS from monitoring a service group on a system that is undergoing maintenance operations

Above is the extract from the below link

https://sort.symantec.com/public/documents/sfha/6.0/linux/productguides/html/vcs_admin/ch06s12s07.htm

Correct me if I am wrong.

I disabled the ServiceGroup (while my DG and MOUNT resource is online) in which the new Diskgroup exist. This will prevent Servicegroup and its resources from being monitored by VCS.

I think you are wrong in that assumption...

On my VRTSvcs-6.1.1.000-RHEL6.i686 system, if I bring a service group online, and then disable the service group:
 

hagrp -modify service_group Enabled 0

The resources contained within that service group are still being monitored.  I think this is the correct behaviour, though I might have argued that the attempt to "disable" an online service group should have been prevented by the VCS state engine (but I guess somebody had a use-case to support that).

Now, eventhough the service group is ONLINE (and disabled), you can now offline the service group, no problem.  However, if you now try to start the "disabled" service group, you get:

VCS WARNING V-16-1-10161 Group service_group is not enabled on system n0-rhel64

I am not sure what exactly it is your are trying to achieve, but in general, if you do not want the "non-production" Disk Group to be monitored by VCS, why don't you leave it outside of VCS management and simply manually import the Disk Group when you want to?

simply manually import the Disk Group when you want to?

Its easy for me but not for my client simple :)

Thanks for your words. What about the document which is saying that when service group is disabled it will no longer monitored by VCS.

I dont want to offline the servicegroup. I just want that the new DG should not be monitored by VCS and keep online too. So If I disable the DG it will not be online but if I disable the SG it keeps my DG online. thats why I disabled the SG to use the DG as well as not monitored by VCS.

I agree - simply remove the new DG resource from VCS and import manually.

Extract from the below Symantec document

Disable a service group to prevent it from coming online. This process temporarily stops VCS from monitoring a service group on a system that is undergoing maintenance operations

https://sort.symantec.com/public/documents/sfha/6.0/linux/productguides/html/vcs_admin/ch06s12s07.htm

As per my understanding. The above Symantec document only apply when the diskgroup(under service group) is offline. If the diskgroup is online then the above Symantec document cannot apply.