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
VCSAgGetMonitorLevel
int VCSAgGetMonitorLevel(int *level_one, int *level_two);
The agent developer can use this primitive to query if the LevelOne (Basic) monitoring or the LevelTwo (Detail) monitoring or both need to be scheduled.
Output parameters:
level_one - This parameter will be updated to 1 or 0. The value of 0 indicates that the basic monitoring should not be scheduled. And the value of 1 indicates that the basic monitoring should be scheduled.
See IMF.
level_two - This parameter will be updated to 0, 1, or 2 . The value of 0 indicates that the detail monitoring should not be scheduled, and the value of 1 indicates that the detail monitoring should be scheduled. And the value of 2 indicates that the detail monitoring should be scheduled if basic monitoring (level_ one) reports the state as online in current running monitor.
Return values: It can be set to VCSAgSuccess or VCSAgFailure based on whether the api passes or fails.
The following example outlines the process of setting the output parameters:
For example, if you set LevelTwoMonitorFrequency to 5 and the resource state is ONLINE, then every fifth monitor cycle, level_two will have the value as 1. If the resource state is OFFLINE, then every monitor cycle level_two will have the value as 2.
See LevelTwoMonitorFreq.
If you set MonitorFreq to 5 and the resource is registered with IMF, then every fifth monitor cycle level_one parameter will have the value of 1.
See IMF.
Usage:
int ret = VCSAgFailure; ret = VCSAgGetMonitorLevel(&level_one, &level_two);
Note:
This API can only be used in monitor entry point. It does not reflect correct monitor levels when you call this API in other entry points.