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
This section summarizes the required and optional attributes of the VMwareDisks agent.
Required attribute | Description |
|---|---|
ESXDetails | The list of hostnames and credentials of the ESX hosts or vCenter on which the virtual machines are configured. The key is ESX or vCenter hostname or IP address. The value must be in the format:
Example - IPv6: ESXDetails = { "[2620:128:f0a2:900d::150]" = "root=28:af:ab:3e:e4:71:ca:6b:99:9d:e3:dd:b1:bc:bc:50:d0:f2:f2:8c:36:9f:11:dc:63:93:5f:2c:e1:e7:14:25" } Example - IPv4: ESXDetails = { "192.168.0.100" = "root=28:af:ab:3e:e4:71:ca:6b:99:9d:e3:dd:b1:bc:bc:50:d0:f2:f2:8c:36:9f:11:dc:63:93:5f:2c:e1:e7:14:25" } Type and dimension: string-association |
DiskPaths | The list of disks paths to be managed by the VMwareDisks resource. The key is of the form '[Data store name] Disk path'. The value is of the form 'SCSI controller key: Target ID (unit number of the disk)'. For example, 0:2. For RDM, add prefix 'RDM:' to the disk path. Alternatively, the key can be of the form 'Disk_UUID: [Data store name] Disk_path'. In case of RDM, 'RDM:Disk_UUID:[Data store name] Disk_path'. If the disk UUID is not provided, the agent will discover the UUID and modify the attribute to have UUID of the disk. Type and dimension: string-association |
Optional attribute | Description |
|---|---|
HAInfoDetails | Determines whether or not vSphere HA is enabled. This attribute uses the vCenter Server hostname or IP address to determine the status of vSphere HA. The value must be specified in the format: Key=Value. Where:
Example - IPv6: HAInfoDetails = {"[2001::15]" = "Administrator@IAG=JPLvPXoVNvQVo"} Example - IPv4: HAInfoDetails = {"192.168.0.100" = "Administrator@IAG=JPLvPXoVNvQVo"} If you do not specify a value for this attribute, the agent considers the vSphere HA setting based on the IsVMHAEnabled attribute value. Type and dimension: string-association |
IsVMHAEnabled | Defines whether vSphere HA is enabled. The value 1 indicates that vSphere HA is enabled. This attribute value should match the vSphere HA settings in the VMware vSphere HA cluster. If vSphere HA is turned on, set this attribute value to 1 (True). If vSphere HA is turned off, set this attribute value to 0 (False). vSphere HA settings are considered based on this attribute only if the HAInfoDetails attribute is not set, or if the agent fails to retrieve the vSphere HA details based on the HAInfoDetails attribute. Default: 1 (True) Type and dimension: boolean-scalar |
PanicVMOnESXLoss | Set this attribute value to 1 (True) to trigger panic on the virtual machine when the ESX host loses network connectivity. Default: 0 (False) Type and dimension: boolean-scalar |
ForceRegister | For internal use only. |
VMRegisterWait | The specified time interval, in seconds, during which VMware HA registers the virtual machine on any other ESX host when an ESX host fails. This is applicable only if IsVMHAEnabled is set to true. Default value: 120 seconds Type and dimension: integer |
VirtualDiskMode |
Specifies the mode to be used when the disk is attached. You can set the value of this attribute to one of the following:
You must modify the value after you configure application monitoring. Note: The VMwareDisks agent does not detect the mode in which the disk is configured. After a failover, the disk is attached in the mode that is defined in the attribute value. For details about the disk modes, refer to the VMware documentation. Default value: persistent Type and dimension: string-association |
DeleteSnapshot | Specifies the action to take when the agent detects that the disk is part of a NetBackup or a user-initiated snapshot. The agent takes one of the following actions depending on the value of this attribute:
Default value: 0 Type and dimension: integer-scalar |
SnapshotRemovalRetry | Specifies the number of times to retry the snapshot removal task as part of the disk detach operation.
Default value: 3 Type and dimension: integer-scalar Note: The acceptable range of values is 0 through 3. If a value outside this range is set, the agent disregards it and proceeds with the default value. |
NBUPrimaryDetails | Specifies the details required to make NetBackup API calls to manage snapshots. This value must be specified in the format: { "NetBackup_primary_server" = " APIKey: "api_key_value", CACert: "CA_certificate_filename_with_path", VMID: "virtual_machine_ID" }
The agent uses these values to continuously monitor the connection with NetBackup server. If any of these values is incorrect, the VMwareDisks resource goes into the UNKNOWN state. Default value: None Type and dimension: string-association |