Video Screencast Help

SFHA Solutions 6.0.1: Understanding and responding to common VCS resource issues

Created: 07 Aug 2013 • Updated: 07 Aug 2013
samg_writer's picture

When you work with Veritas Cluster Server (VCS) resources, you may encounter one of the following situations:

  • The resource goes offline unexpectedly.
  • The command to bring the resource online is rejected.
  • The monitor procedure does not complete within the expected time.

For background information about VCS resources, see:

When a resource goes offline

A resource may go offline unexpectedly and outside of VCS control. By default, VCS detects this situation and automatically fails over the resource. Error message V-16-2-13067 is written to the agent log or engine log file:

Agent is calling clean for resource(%s) because the resource became OFFLINE unexpectedly, on its own

For more information on the agent log and engine log, see:

VCS message logging

When you receive this error, no action is required. VCS takes action on the faulted resource.

However, if you do not want VCS to take action when the resource goes offline, increase the value of the ToleranceLimit attribute. This attribute defines how many times the monitor entry point reports the resource offline before it declares the resource faulted.

Note: If you set this value to a higher number, it could delay detecting a genuinely faulted resource.

For more information, see:

When the command to bring the resource online is rejected

VCS can bring a resource online only if it can probe the resource and determine the resource’s initial state. If VCS cannot probe the resource before you issue the hares –online command, error message V-16-1-10283 is written to the engine log file:

Resource has not been probed on system system_name

To resolve this issue, you can:

  • Wait until the agent probes the resource before you enter the hares –online command.
  • Check the agent log and engine log to identify and correct any reported issues by the Monitor agent function. A very common issue is that the resource is in the UNKNOWN state due to a configuration issue.

If you are a Solaris user running Storage Foundation and High Availability (SFHA) 5.0 MP3, the following TechNote describes the error in the context of your environment:

TechNote 88123 - Resource has not been probed

To learn more about the Monitor agent function and probing resources, see:

hares (1M) manual pages:

AIX
HP-UX
Linux
Solaris

When the Monitor agent function does not complete within the expected time

The Monitor agent function tests the status of a resource to determine whether it is online or offline. If the Monitor agent function does not complete within the expected time, and there are no other issues with the system, error message V-16-2-13027 is written to the agent log or engine log:

Resource(%s) - monitor procedure did not complete within the expected time

For information on correcting this error, see:

TechNote 70442
 
Veritas Storage Foundation and High Availability documentation for other releases and platforms can be found on the SORT website.