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 for NIC agent
Table: Required attributes
Required attribute | Description |
|---|---|
Device | Name of the NIC that you want to monitor. Type and dimension: string-scalar Example: "e1000g0" |
Table: Optional attributes
Optional attribute | Description |
|---|---|
BroadcastTest | Specifies whether to perform a ping test on the broadcast address that is present on the NIC as part the monitor operation. The ping test determines whether the network connection is alive. This attribute is used if the ping test on the hosts specified in the NetworkHosts attribute fails. Disable this attribute if you want to perform the ping test only on the hosts provided in NetworkHosts. Type-dimension: boolean-scalar Default: 1 |
ExclusiveIPZone | ExclusiveIPZone Specifies that a resource is configured for an exclusive IP zone. Set this value to 1 if a resource is configured for exclusive IP zone. When set to 1, it requires a valid ContainerInfo to be configured in the service group. Type-dimension: boolean-scalar Default: 0 |
NetworkHosts | List of hosts on the network that are pinged to determine if the network connection is alive. You can use this attribute to help to save network capacity and reduce monitor time. Arctera recommends that you use the outgoing gateway routers for this value. Enter the IP address of the host, instead of the host name, to prevent the monitor from timing out. DNS causes the ping to hang. If more than one network host is listed, the monitor returns ONLINE if at least one of the hosts is alive. If an invalid network host address is specified, the resource enters an UNKNOWN state. If you do not specify network hosts, the monitor tests the NIC by sending pings to the broadcast address on the NIC. Type and dimension: string-vector Example: { "166.93.2.1", "166.99.1.2", "2620:128:f0a2:9005::1" } |
NetworkType | Type of network. VCS supports only Ethernet. Type and dimension: string-scalar Default: "ether" |
PingOptimize |
Determines whether to ping during every monitor cycle. The value can be:
Type and dimension: integer-scalar Default: 1 |
PingTest | Specifies whether to perform a ping test on the NIC:
Type-dimension: boolean-scalar Default: 1 |
LinkTest | Determines whether the network connection is alive by checking the link status on the data-link layer.
Type and dimension: boolean-scalar Default: 0 |