InfoScale™ 9.0 Cluster Server Bundled Agents Reference Guide - AIX
- Introducing bundled agents
- Storage agents
- About the storage agents
- DiskGroup agent
- IMF awareness
- Support for online migration for DiskGroup agent
- Dependencies for DiskGroup agent
- Agent functions for DiskGroup agent
- State definitions for DiskGroup agent
- Attributes for DiskGroup agent
- Resource type definition
- Notes for DiskGroup agent
- Sample configurations for DiskGroup agent
- Debug log levels for DiskGroup agent
- DiskGroupSnap agent
- Dependencies for DiskGroupSnap agent
- Agent functions for DiskGroupSnap agent
- State definitions for DiskGroupSnap agent
- Attributes for DiskGroupSnap agent
- Notes for DiskGroupSnap agent
- Resource type definition for DiskGroupSnap agent
- Sample configurations for DiskGroupSnap agent
- Debug log levels for DiskGroupSnap agent
- Volume agent
- VolumeSet agent
- Dependencies for VolumeSet agent
- Agent functions for VolumeSet agent
- State definitions for VolumeSet agent
- Attributes for VolumeSet agent
- Resource type definition for VolumeSet agent
- Sample configurations for VolumeSet agent
- Agent notes for VolumeSet agent
- Inaccessible volumes prevent the VolumeSet agent from coming online
- Debug log levels for VolumeSet agent
- LVMVG agent
- Dependencies for LVMVG agent
- Agent functions for LVMVG agent
- State definitions for LVMVG agent
- Attributes for LVMVG agent
- Resource type definition for LVMVG agent
- Notes for LVMVG agent
- Disks renamed after device renaming
- About the updatepv action
- LVMVG support in a VIO server environment
- Deactivation failure using the varyoffvg command on losing storage connectivity
- LVMVG Agent Supports JFS or JFS2
- Volume group needs to be imported
- Varyonvg options
- SyncODM Attribute
- Major Numbers
- Autoactivate Options
- LVMVG agent support for the Subsystem Device Driver (SDD)
- LVMVG agent support for the Hitachi's HiCommand Dynamic Link Manager (HDLM)
- LVMVG agent support for the EMC PowerPath
- The hadevice utility
- Removing a ghost disk from VxVM control
- Sample configuration for LVMVG agent
- Debug log levels for LVMVG agent
- Mount agent
- IMF awareness
- Dependencies for Mount agent
- Agent functions for Mount agent
- State definitions for Mount agent
- Attributes for Mount agent
- Resource type definition for Mount agent
- Notes for Mount agent
- High availability fire drill
- VxFS file system lock
- IMF usage notes
- IPv6 usage notes
- Bringing a Mount resource online in the WPAR
- Selecting the attribute values for a Mount resource for the WPAR's root file system for NFS mounts
- Support for namefs file system
- Taking a group with the Mount resource offline can take several minutes if the file system is busy
- Example 1
- Example 2
- Example 3
- Enabling Level two monitoring for the Mount agent
- Sample configurations for Mount agent
- Debug log levels for Mount agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- IPMultiNIC agent
- MultiNICA agent
- About the IPMultiNICB and MultiNICB agents
- IPMultiNICB agent
- Dependencies for IPMultiNICB agent
- Requirements for IPMultiNICB
- The haipswitch utility for IPMultiNICB agent
- Agent functions for IPMultiNICB agent
- State definitions for IPMultiNICB agent
- Attributes for IPMultiNICB agent
- Resource type definition for IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- Debug log levels for IPMultiNICB agent
- MultiNICB agent
- The haping utility for MultiNICB agent
- Dependencies for MultiNICB agent
- Agent functions for MultiNICB agent
- State definitions for MultiNICB agent
- Attributes for MultiNICB agent
- Resource type definition for MultiNICB agent
- Trigger script for MultiNICB agent
- Sample configurations for MultiNICB agent
- Debug log levels for MultiNICB agent
- DNS agent
- Dependencies for DNS agent
- Agent functions for DNS agent
- State definitions for DNS agent
- Attributes for DNS agent
- Resource type definition for DNS agent
- Agent notes for DNS agent
- About using the VCS DNS agent on UNIX with a secure Windows DNS server
- High availability fire drill for DNS agent
- Monitor scenarios for DNS agent
- Sample Web server configuration for DNS agent
- Secure DNS update for BIND 9 for DNS agent
- Setting up secure updates using TSIG keys for BIND 9 for DNS agent
- Sample configurations for DNS agent
- Debug log levels for DNS agent
- File share agents
- About the file service agents
- NFS agent
- NFSRestart agent
- Share agent
- About the Samba agents
- The Samba agents
- Before using the Samba agents
- Supported versions for Samba agents
- Notes for configuring the Samba agents
- SambaServer agent
- Dependencies for SambaServer agent
- Agent functions for SambaServer agent
- State definitions for SambaServer agent
- Attributes for SambaServer agent
- Resource type definitions for SambaServer agent
- Notes for SambaServer agent
- Sample configurations for SambaServer agent
- Debug log levels for SambaServer agent
- SambaShare agent
- NetBios agent
- Service and application agents
- About the services and applications agents
- Apache HTTP server agent
- Application agent
- IMF awareness
- High availability fire drill for Application agent
- Dependencies for Application agent
- Agent functions
- State definitions for Application agent
- Attributes for Application agent
- Resource type definition for Application agent
- Notes for Application agent
- Sample configurations for Application agent
- Debug log levels for Application agent
- CoordPoint agent
- LPAR agent
- Dependencies for LPAR agent
- Agent functions for LPAR agent
- State definitions for LPAR agent
- Required attributes for LPAR agent
- Optional attributes for LPAR agent
- Group attribute for LPAR agent
- System attribute for LPAR agent
- Resource type definition for LPAR agent
- Sample configurations for LPAR agent
- Notes for LPAR agent
- VCS requirements to manage the LPAR agent
- Configuring password-less SSH communication between VCS nodes and HMC
- Verifying password-less SSH status
- Live Partition Mobility support for LPARs managed by VCS
- Setting the SysDownPolicy attribute for the LPAR service group
- Configuring the LPAR agent for DR in a Global Cluster environment
- Debug log levels for LPAR agent
- MemCPUAllocator agent
- Dependencies
- Agent functions
- Attributes
- Resource type definition
- MemCPUAllocator agent notes
- Configuring password free SSH communication between VCS nodes and HMC
- Dynamic resource allocation scenarios
- Scenario 1: A DLPAR node has minimum resources
- Scenario 2: Bringing another service group online
- Scenario 3: DLPAR has required resources
- Scenario 4: Cannot allocate required resources
- Scenario 5: Service group failover
- Configuring MemCPUAllocator
- Debug log levels
- Process agent
- IMF awareness
- High availability fire drill for Process agent
- Dependencies for Process agent
- Agent functions for Process agent
- State definitions for Process agent
- Attributes for Process agent
- Resource type definition for Process agent
- Usage notes for Process agent
- Sample configurations for Process agent
- Debug log levels for Process agent
- ProcessOnOnly agent
- RestServer agent
- WPAR agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Agent functions
Online | Runs the executable file with the parameters that are specified in the StartProgram attribute in the context of the specified user. To bring the resource online, the agent function performs the command: su [-] user -c executable_to_online_resource When DelayAfterOnline attribute is set, the monitor function is invoked after completion of online function, and after the number of seconds specified in DelayAfterOnline attribute have elapsed. |
Offline | Runs the executable file with the parameters that are specified in the StopProgram attribute in the context of the specified user. To take the resource offline, the agent function performs the command: su [-] user -c executable_to_offline_resource When DelayAfterOffline attribute is set, the monitor function is invoked after completion of offline function and after the number of seconds specified in DelayAfterOffline attribute have elapsed. |
Monitor |
How the agent performs this function depends on the attributes that you specify:
You can use any combination of the MonitorProgram, PidFiles, or MonitorProcesses attributes to monitor the application. If this function determines that one or more of the processes that are specified in either PidFiles or MonitorProcesses are not running, it returns OFFLINE. If the process terminates ungracefully, the monitor returns OFFLINE, and a failover occurs. To monitor the resource, the agent function performs the command: su [-] user -c executable_to_monitor_resource |
imf_init | Initializes the agent to interface with the asynchronous monitoring framework (AMF) kernel driver. This function runs when the agent starts up. |
imf_getnotification | Gets notification about resource state changes. This function runs after the agent initializes with the AMF kernel driver. The agent continuously waits for notification and takes action on the resource upon notification. |
imf_register | Registers the resource entities, which the agent must monitor, with the AMF kernel driver. For example, the function registers the PID for online monitoring of a process. This function runs for each resource after the resource goes into steady state (online or offline). The Application agent uses IMF for the processes configured with PidFiles and the MonitorProcesses attribute. |
Clean | Terminates processes specified in PidFiles or MonitorProcesses. Ensures that only those processes (that are specified in the MonitorProcesses attribute) running with the user ID specified in the User attribute are killed. If the CleanProgram is defined, the agent executes the CleanProgram. To forcefully stop the resource, the agent function performs the command: su [-] user -c executable_to_clean_resource Note that the agent uses the su - option only when the attribute UseSUDash is enabled (1). The UseSUDash attribute is disabled (0) by default. |
Action | The various functions of the action entry point are as follows:
|
For all agent functions on AIX: If the User attribute is set to a non-root user, the agent checks if this non-root user has any home directory that exists and is accessible. If this non-root user has a home directory and is accessible, then it does the command: su - user -c command. If this non-root user does not have a home directory or the home directory is unaccessible, then it uses the command: su user -c command.