InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
- Introduction
- Agent entry point overview
- About agent entry points
- Agent entry points described
- About the action entry point
- About the info entry point
- Considerations for using C++ or script entry points
- About the agent information file
- About the ArgList and ArgListValues attributes
- Creating entry points in C++
- About creating entry points in C++
- Syntax for C++ entry points
- Agent framework primitives
- Agent Framework primitives for container support
- Creating entry points in scripts
- About creating entry points in scripts
- Syntax for script entry points
- Agent framework primitives
- VCSAG_GET_ATTR_VALUE
- Agent Framework primitives with container support
- Example script entry points
- Logging agent messages
- Building a custom agent
- Building a script based IMF-aware custom agent
- Creating XML file required for AMF plugins to do resource registration for online and offline state monitoring
- Testing agents
- Static type attributes
- About static attributes
- Static type attribute definitions
- AdvDbg
- ArgList
- State transition diagram
- Internationalized messages
- Troubleshooting VCS resource's unexpected behavior using First Failure Data Capture (FFDC)
- Appendix A. Using pre-5.0 VCS agents
ManageFaults
A service group level attribute. ManageFaults specifies if VCS manages resource failures within the service group by calling clean entry point for the resources. This attribute value can be set to ALL or NONE. Default = ALL.
If set to NONE, VCS does not call clean entry point for any resource in the group. User intervention is required to handle resource faults/failures. When ManageFaults is set to NONE and one of the following events occur, the resource enters the ADMIN_WAIT state:
The offline entry point was ineffective. Resource state is ONLINE|ADMIN_WAIT.
The offline entry point did not complete within the expected time. Resource state is ONLINE|ADMIN_WAIT.
The online entry point did not complete within the expected time. Resource state is OFFLINE|ADMIN_WAIT.
The online entry point was ineffective. Resource state is OFFLINE|ADMIN_WAIT.
The resource was taken offline unexpectedly. Resource state is OFFLINE|ADMIN_WAIT.
For the online resource the monitor entry point consistently failed to complete within the expected time. Resource state is ONLINE| MONITOR_ TIMEDOUT|ADMIN_WAIT. The value configured in FaultOnMonitorTimeouts attribute indicates number of consecutive monitor failures after which the resource must move into ONLINE| MONITOR_ TIMEDOUT|ADMIN_WAIT state.