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
Attributes for Application agent
Table: Required attributes
Required attribute | Description |
|---|---|
StartProgram | The executable, which starts the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. Note: The agent logs the return value of the StartProgram executable. The agent does not treat a non-zero return value as failure of execution and brings the resource online. Note: Do not use the opening and closing ({ }) brace symbols in this string. Note: In the script, specify a return value that is between 0 and 255. Type and dimension: string-scalar Example: "/usr/sbin/sample_app start" |
StopProgram | The executable, which stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. Note: The agent logs the return value of the StopProgram executable. The agent does not treat a non-zero return value as failure of execution and takes the resource offline. Note: Do not use the opening and closing ({ }) brace symbols in this string. Note: In the script, specify a return value that is between 0 and 255. Type and dimension: string-scalar Example: "/usr/sbin/sample_app stop" |
At least one of the following attributes:
|
Table: Optional attributes
Optional attribute | Description |
|---|---|
CleanProgram | The executable, which forcibly stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. Note: Arctera recommends to have the CleanProgram on the local storage so that in case of loss of storage connectivity VCS can take appropriate action to stop the application. Note: If the CleanProgram executable returns a non-zero value, the agent treats it as a clean failure and the resource will not fault. Type and dimension: string-scalar Example: "/usr/sbin/sample_app stop" |
MonitorProcesses | A list of processes that you want monitored and cleaned. Each process name is the name of an executable. Qualify the executable name with its complete path if the path starts the executable. The process name must be the full command line argument that the ps -u user -eo pid,args command displays for the process. Type and dimension: string-vector Example: { "/usr/bin/sh /user/app/process1", "/usr/bin/sh /user/app/process2" } |
MonitorProgram | The executable, which monitors the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and have spaces separating them. This executable can be on local storage or shared storage. MonitorProgram can return the following states: OFFLINE value is 100 or 1; ONLINE values range from 101 to 110 or 0 (depending on the confidence level); 110 equals confidence level of 100%. Any other value = UNKNOWN. If MonitorProgram is configured and not available, then resource state will be:
Note: Do not use the opening and closing ({ }) brace symbols in this string. Type and dimension: string-scalar Example: "/usr/sbin/sample_app_monitor all" |
PidFiles | A list of PID (process ID) files that contain the PID of the processes that you want monitored and cleaned. These are application generated files. Each PID file contains one monitored PID. Specify the complete path of each PID file in the list. The process ID can change when the process restarts. If the application takes time to update the PID file, the agent's Monitor function may return an incorrect result. If incorrect results occur, increase the ToleranceLimit in the resource definition. Type and dimension: string-vector Example: "/etc/sample/sample_app.pid" |
User | The user ID for running StartProgram, StopProgram, MonitorProgram, and CleanProgram. The processes that are specified in the MonitorProcesses list must run in the context of the specified user. Monitor checks the processes to make sure they run in this context. Note: If the configured user does not exist, the resource state will be UNKNOWN. Type and dimension: string-scalar Default: root Example: user1 |
EnvFile | The environment file that should get sourced before running any of the StartProgram, StopProgram, MonitorProgram or CleanProgram. Note: Make sure that the EnvFile adheres the default shell syntax of the configured user. Type and dimension: string-scalar Default: "" Example: /home/username/envfile |
UseSUDash | When the value of this attribute is 0, the agent performs an su user command before it executes the StartProgram, the StopProgram, the MonitorProgram, or the CleanProgram agent functions. When the value of this attribute is 1, the agent performs an su - user command before it executes the StartProgram, the StopProgram, the MonitorProgram or the CleanProgram agent functions. Type and dimension: boolean-scalar Default: 0 Example: 1 |
DelayAfterOnline | Specifies the number of seconds that elapse after the Online entry point is complete and before the next monitor cycle is invoked. Type and dimension: integer-scalar Default: 0 |
DelayAfterOffline | Specifies the number of seconds that elapse after the Offline entry point is complete and before the next monitor cycle is invoked. Type and dimension: integer-scalar Default: 0 |