Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Agent Developer's Guide - AIX, Linux, Solaris, Windows
Last Published:
2025-04-13
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: 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
Monitor without IMF but with LevelTwo monitor frequency
If the custom agent monitor does the basic as well as detail monitoring, then detail monitoring code must be conditional. This avoids scheduling of detail monitoring if not required. VCSAG_GET_MONITOR_LEVEL API can be used to check if detail monitoring needs to be scheduled.
VCSAG_GET_MONITOR_LEVEL API fetches and sets the values of the LevelTwoMonitorFreq attribute.
#!/bin/sh # CustomAgent Monitor script . $VCS_HOME/bin/ag_i18n_inc.sh RESNAME=$1 VCSAG_SET_ENVS $RESNAME STATE=${VCS_RES_ONLINE}; # Fetch the value of detail (Level-2) monitoring. # VCSAG_GET_MONITOR_LEVEL will store this values in # VCSAG_MONITOR_LEVEL_TWO environment. VCSAG_GET_MONITOR_LEVEL(); # Logic for custom agent basic monitoring. # Based on logic set STATE to OFFLINE or ONLINE # if basic monitoring of the resource state that resource is ONLINE, # check if detail monitoring (Level-2) need to be performed. if [ ${STATE} -eq ${VCS_RES_ONLINE} ]; then if [ ${VCSAG_MONITOR_LEVEL_TWO} -ne 0 ]; then # Logic for custom agent detail monitoring. # Based on logic return OFFLINE or ONLINE # If resource is found as OFFLINE STATE = ${VCS_RES_OFFLINE}; # If resource is found as ONLINE STATE = ${VCS_RES_ONLINE}; fi fi exit $(STATE);