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
Enhancing First Failure Data Capture (FFDC) to troubleshoot VCS resource's unexpected behavior
FFDC is the process of generating and dumping debug information on unexpected events.
Earlier, FFDC information is generated on following unexpected events:
Segmentation fault
When agent fails to heartbeat with engine
From VCS 6.2 version, the capturing of the FFDC information on unexpected events has been extended to resource level and to cover VCS events. This means, if a resource faces an unexpected behavior then FFDC information will be generated.
The current version enables the agent to log detailed debug logging during unexpected events with respect to resource, such as,
Monitor entry point of a resource reported OFFLINE/IO when it was in ONLINE state.
Monitor entry point of a resource reported UNKNOWN.
If any entry point times-out.
If any entry point reports failure.
Now whenever an unexpected event occurs FFDC information will be automatically generated. And this information will be logged in their respective agent log file.