InfoScale™ 9.0 Cluster Server Bundled Agents Reference Guide - Solaris
- Introducing bundled agents
- Storage agents
- About the storage agents
- 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
- Disk 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
- 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
- Support for loopback file system
- Enabling Level two monitoring for the Mount agent
- ZFS file system and pool creation example
- Support for VxFS direct mount inside non-global zones
- Sample configurations for Mount agent
- Debug log levels for Mount agent
- Zpool agent
- VMwareDisks agent
- SFCache agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- About the IPMultiNICB and MultiNICB agents
- IPMultiNICB agent
- Dependencies for IPMultiNICB agent
- Requirements for IPMultiNICB
- Agent functions for IPMultiNICB agent
- State definitions for IPMultiNICB agent
- Attributes for IPMultiNICB agent
- Resource type definition for IPMultiNICB agent
- Manually migrating a logical IP address for IPMultiNICB agent
- Sample configurations for IPMultiNICB agent
- Debug log levels for IPMultiNICB agent
- MultiNICB agent
- Base and Multi-pathing modes for MultiNICB agent
- Oracle trunking for 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
- Optional attributes for Base and Mpathd modes for MultiNICB agent
- Optional attributes for Base mode for MultiNICB agent
- Optional attributes for Multi-pathing mode for MultiNICB agent
- Resource type definition for MultiNICB agent
- Solaris operating modes: Base and Multi-Pathing for MultiNICB agent
- Base mode for MultiNICB agent
- Failover and failback for MultiNICB agent
- Multi-Pathing mode for MultiNICB agent
- Configuring MultiNICB and IPMultiNICB agents on Solaris 11
- 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
- NetBios agent
- Service and application agents
- About the services and applications agents
- AlternateIO agent
- 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
- LDom agent
- Configuring primary and logical domain dependencies and failure policy
- IMF awareness
- Dependencies
- Agent functions
- State definitions
- Attributes
- Resource type definition
- LDom agent notes
- About the auto-boot? variable
- Notes for the DomainFailurePolicy attribute
- Using VCS to migrate a logical domain
- Configuring the LDom agent for DR in a Global Cluster environment
- Using the LDom agent with IMF
- Sample configuration 1
- Sample configuration 2
- Configuration to support user-initiated LDom migration
- Configuration for VCS-initiated migration
- Sample configuration (Dynamic virtual machine service group failover)
- 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
- Project agent
- RestServer agent
- Zone agent
- Infrastructure and support agents
- Testing agents
- Replication agents
Attributes
Table: Required attributes
Attribute | Description |
|---|---|
RvgResourceName | The name of the RVG resource type that this agent promotes. The name RVG resource type which has been configured using the RVG agent. Type and dimension: string-scalar |
AutoTakeover | A flag to indicate whether the agent should perform a takeover on online if the original Primary is down. AutoTakeover and AutoResync are mutually exclusive attributes. When AutoTakeover=0, the primary-elect feature is not applicable; therefore, it is not supported. Type and dimension: integer-scalar |
AutoResync | Indicates whether the agent should attempt to automatically perform a fast-failback resynchronization of the original Primary after a takeover and after the original Primary returns. You can use the following values for this attribute:
AutoTakeover and AutoResync are mutually exclusive attributes. When AutoTakeover=0, the primary-elect feature is not applicable; therefore, it is not supported. Type and dimension: integer-scalar |
BunkerSyncTimeOut | The value for the BunkerSyncTimeOut attribute determines if you want the bunker to perform a replay or not. You set the value in seconds for the time that you want to allot for the replay. Use one of the following values for the BunkerSyncTimeOut attribute:
The RVGPrimary agent's OnlineTimeout and OnlineRetryLimit attribute values determine the available time for an RVGPrimary resource to complete its online operation. Use the following formula to get the Time Available for Online to Complete (TAOC): TAOC = (OnlineTimeout + (OnlineRetryLimit * OnlineTimeout)) |
BunkerSyncTimeOut (cont.) | When you set the BunkerSyncTimeOut value in seconds, the value of TAOC for the RVGPrimary agent should be greater than the desired BunkerSyncTimeOut value. Using a TAOC value that is greater than BunkerSyncTimeOut value ensures that the bunker replay and the RVG takeover can complete in the allotted time for that particular online operation. If the TAOC is smaller than BunkerSyncTimeOut value and the bunker replay does not complete within the allotted time for the online process, the resource faults. If the resource faults, clear the fault. Try the online operation again if the resource has not failed over to other cluster node in the configuration. If you increase the value of the BunkerSyncTimeOut attribute, you need to increase the value of the OnlineTimeout or OnlineRetryLimit attribute so that TAOC remain greater than changed value. This is to ensure to have bunker replay completed within allotted time for online. If the value of the AutoResync attribute is 2, you must set the value of the BunkerSyncTimeOut attribute to 0 (to disable automated bunker replay). Type and dimension: string-scalar Default value: "" |
Table: Optional attributes
Attribute | Description |
|---|---|
NumThreads | Number of threads used within the agent process for managing resources. This number does not include threads used for other internal purposes. Do not modify this attribute for this agent. Setting this attribute to a higher value may result in agent function timeouts due to serialization of underlying commands. Default: 1 |
ResyncType | Allows you to choose between automatic synchronization and difference-based synchronization. By default, difference-based synchronization is enabled for resynchronization. To enable automatic synchronization, run the following commands: # haconf -makerw # hares -modify RVGPrimary_resource_name ResyncType 1 # haconf -dump -makero # hares -value RVGPrimary_resource_name ResyncType To track automatic synchronization progress, run the following commands: # vxrlink -g dg_name -i time_interval status rlk_name # vradmin -g dg_name repstatus rvg_name Type and dimension: integer-scalar Default: 0 |
Table: Internal attribute
Attribute | Description |
|---|---|
BunkerSyncElapsedTime | For internal use only, do not modify. This value in seconds signifies the amount of time that a Secondary RVG has waited for synchronization from the bunker host to complete. Type and dimension: integer-scalar |
Note:
Default settings of AutoTakeover=1 and AutoResync=0 cause the first failover to succeed when the original Primary goes down, and upon the original Primary's return, the RDS (Replicated Data Set) has a Primary-Primary configuration error. Set the default value of the AutoResync attribute of the RVGPrimary and RVGSharedPri agents to 1 if you want the agent to automatically attempt a fast-failback resynchronization of the original Primary after a takeover and after the original Primary returns. This prevents the Primary-Primary configuration error.