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
VCSAG_GET_MONITOR_LEVEL
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 if basic monitoring needs to be scheduled or not. A value of 0 means that basic monitoring should not be scheduled while a value of 1 means that basic monitoring should be scheduled.
See IMF.
level_two: This parameter will be updated to 0, 1, or 2, based on the present state of the resource, and if detail monitoring needs to be scheduled. A value of 0 means that detail monitoring should not be scheduled, a value of 1 means that detail monitoring should be scheduled, and a value of 2 means that detail monitoring should be scheduled if basic monitoring (level_ one) reports state as online
Following example describes setting of output parameters,
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.
This API is typically used as Perl-based or Shell-based script.
Perl-based:
This API return the value of level_one and level__two and status as return value.
Usage:($ret, $level_one, $level_two) = VCSAG_GET_MONITOR_LEVEL();
$ret : Checks whether the API passed or failed.
$level_one : Holds the value of level one monitor flag if API is passed.
$level_two : Holds the value of level two monitor flag if API is passed.
Shell-based:
This API return the value of level_one and level__two as environment variable VCSAG_MONITOR_LEVEL_ONE and VCSAG_MONITOR_LEVEL_TWO, and status as return value.
Usage:VCSAG_GET_MONITOR_LEVEL
Fetches the value of the LevelOne and LevelTwo monitoring flag as below if API passes,
level_one=${VCSAG_MONITOR_LEVEL_ONE}
level_two=${VCSAG_MONITOR_LEVEL_TWO}