Cluster Server 8.0.1 Agent Developer's Guide - 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
- Files for use in agent development
- Creating the type definition file for a custom agent
- Building a custom agent on UNIX
- Defining resources for the custom resource type
- 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
State transitions with respect to ResFaultPolicy attribute
This section show state transition diagrams with respect to the ResFaultPolicy attribute.
By default, the ResFaultPolicy attribute is set to FaultPropagateAll, in which case the agent calls the clean entry point. Based on the value of the resource type level attribute RestartLimit, the agent attempts to restart the resource before declaring it as FAULTED. In general, when ResFaultPolicy attribute is set to FaultHold, the behavior is the same as when it is set to FaultPropagateAll. Further actions depend on the group level attribute GrpFaultPolicy.
The next set of diagrams illustrate the following state transitions:
Bringing a resource online, ResFaultPolicy set to FaultNone
Taking a resource offline, ResFaultPolicy set to FaultNone
Resource fault, ResFaultPolicy set to FaultPropagateAll or FaultHold
Resource fault (unexpected offline), ResFaultPolicy set to FaultNone
Resource fault (monitor hung), ResFaultPolicy set to FaultPropagateAll
Resource fault (monitor hung), ResFaultPolicy set to FaultNone