1. Support
  2. Knowledge base
  3. 100020966

The message "VCS ERROR V-16-2-13027 (node_name) Resource (resource_name); - monitor procedure did not complete within the expected time" occurs intermittently, while the system has no other indication of performance issues.

Article: 100020966
Last Published: 2014-03-04
Ratings: 1 2
Product(s): InfoScale & Storage Foundation

Problem

The message "VCS ERROR V-16-2-13027 Resource - monitor procedure did not complete within the expected time" occurs intermittently, while the system has no other indication of performance issues.

Error Message

VCS ERROR V-16-2-13027 Resource - monitor procedure did not complete within the expected time

Cause

 This is best a practice configuration when multiple service groups are in use on the same Ethernet interface.   As the number of MultiNIC resources instances increase, so does the frequency the resource is probed, and ultimately the possibility of a deadlock occurring.

Solution

The issue:
 
The message "VCS ERROR V-16-2-13027 <node_name> Resource <resource> - monitor procedure did not complete within the expected time" occurs intermittently, while system is running without any performance issue.
 

 
To resolve the issue:
 
The issue can occur if a specific network interface is used by more than one resource at the same time.
 
This can be verified by reviewing the "/etc/VRTSvcs/conf/config/main.cf" file.
 
For example, if "bge0" were specified as follows for multiple resources in the main.cf:
 

 
NIC csgnic (
 
Device = bge0
 
)
 

 
MultiNICA multinica_resource (
Device = { bge0 = "10.1.1.25", bge1 = "10.1.1.26" }
 
)
 

 
Changing the cluster configuration will resolve the issue.
 
Use the specific network interface only once in the configuration.
 
If the resource is needed by multiple service groups, the proper way to configure the cluster to utilize the resource multiple times is to:
 
1) Create a new parallel service group that only has:
 
a. A NIC or MultiNIC defined with the network interface
 
b. A phantom resource
 

 
2) In each service group that requires use of the network interface:
 
a. Delete the existing NIC / MultiNIC resource that is a duplicated network interface.
 
b. Create a proxy linked to the NIC / MultiNIC resource in the group from #1.
 
c.  Make sure to set the Device attribute (for a NIC) or BaseResName ( which is the MultiNIC resouce name) for IPMultiNIC as the same item in use for the resource located in the parallel service group from Step 1a.
 
d. Link the IP dependency in each service group to the proxy. IP is parent, proxy is child.
 

 
The above configuration allows all nodes in the cluster to have the network interface online concurrently.
 
The configuration also allows that the defined service groups may be online on either node, and failover or a switch of a single service group will work correctly without affecting other service groups.
 

 

 

 

Was this content helpful?

Article Languages