VCS Application resource unable to monitor / offline when losing access to shared disks

book

Article ID: 100024451

calendar_today

Updated On:

Cause

An application agent checks for the existence of the Start/Stop/Monitor programs on a node. On nodes that cannot access the shared disk, this check fails. As a result, on such nodes, the agent marks the status of the application as UNKNOWN. Further, if an application goes down on an active node, then the application cannot fail over to nodes where the status of the application is UNKNOWN. This issue is tracked via etrack incident # 2334796.

Resolution

Veritas has modified the Application agent to check for non-null values of the attributes associated with the Start/Stop/Monitor programs, instead of checking for the existence of the programs. As a result, for nodes that cannot access the shared disks, the agent now marks the application resources as Offline, instead of Unknown.

This issue is fixed in the following VCS hotfix patch release.

- VRTSvcsag 5.1SP1RP1HF4 (Solaris SPARC and Solaris x64)

- VRTSvcsag 5.1SP1RP1HF2 (AIX)

The issue will also be fixed in the following VCS Rolling Patch (RP) release.

- VCS 5.1SP1RP2 (all platforms)

Issue/Introduction

If the Start/Stop/Monitor programs is stored on shared disks, and a VCS (Veritas Cluster Server) node is unable to access the shared disks, then the Application agent cannot monitor an application on the node. Further, VCS cannot fail over applications on such a node.

Additional Information

ETrack: 2334796

Was this article helpful?

thumb_up Yes

thumb_down No

Welcome to "KB Articles"