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
Adding IMF and IMFRegList attributes in configuration
You need to add IMF and IMFRegList attribute in configuration files. Adding IMFRegList is optional.
See IMF.
See IMFRegList.
To add these attributes, you can either modify the configuration file if VCS is not running or modify the running configuration by ha - command if VCS is running. Refer to the following examples for this purpose.
Example of type definition for a custom agent to supports IMF when VCS is not running:
type MyCustomIMFApp ( static int IMF{} = { Mode=3, MonitorFreq=1, RegisterRetryLimit=3 } static str IMFRegList[] = { PathName, Arguments } static str ArgList[] = { PathName, Arguments, HomeDir } str PathName str Arguments str HomeDir )
Example of modify configuration for a custom agent to supports IMF when VCS is running:
Command to add IMF attribute:
haattr -add -static IMF MyCustomIMFApp -integer -assoc Mode 3 MonitorFreq 1 RegisterRetryLimit 3
Command to add IMFRegList attribute:
haattr -add -static Zone IMFRegList -string -vector PathName, Arguments
See IMFRegList.
You can modify these IMF attribute values at the Agent Type or Resource level to suite your requirement. The following example describes how you can modify the values for Mode attribute.
In case of Online only Monitoring (PRON), Mode value can be set to 2. Run the following commands at the respective levels to modify the Mode value:
- At the type level:
# hatype -display <resource-type> -attribute IMF #Type Attribute Value CustomProcess IMF Mode 3 MonitorFreq 1 RegisterRetryLimit 3 # hatype -modify <resource-type> IMF -update Mode 2 # hatype -display <resource-type> -attribute IMF #Type Attribute Value CustomProcess IMF Mode 2 MonitorFreq 1 RegisterRetryLimit 3
- At the Resource level, first check that whether static attribute IMF is overridden or not.
# hares -display <resource-name> -attribute IMF VCS WARNING V-16-1-10554 No resource exists with attribute IMF
In case not overridden , you can now override static attribute IMF at resource level using following command:
# hares -override <resource-name> IMF # hares -display <resource-name> -attribute IMF #Resource Attribute System Value pres1 IMF global Mode 3 MonitorFreq 1 RegisterRetryLimit 3 # hares -modify pres1 IMF -update Mode 2 # hares -display pres1 -attribute IMF #Resource Attribute System Value pres1 IMF global Mode 2 MonitorFreq 1 RegisterRetryLimit 3