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 MultiNICA agent
Table: Required attributes
Required attribute | Description |
|---|---|
Device | List of interfaces and their base IP addresses. When a network interface or a network adapter of the type MultiNICA under VCS control is renamed, you must update the value of the Device attribute of the MultiNICA resource. Note: Arctera recommends to offline the service groups containing the network resources before renaming the network interfaces and adapters and to update the VCS configuration to avoid any undesired behaviour. For each system you must localize the attribute with a separate base IP address. Type and dimension: string-association Example: { en0 = "10.128.8.42", en1 = "10.128.8.42" } |
Gateway | IP address for the default gateway. Type and dimension: string-scalar Example: "10.192.1.7", "2620:128:f0a2:900c::1" |
One of the following attributes:
| |
BroadcastAddr | Broadcast address Type and dimension: string-scalar Example: "10.192.15.255" |
PrefixLen | Specifies the prefix for the IPv6 address represented as the CIDR value. When you use the IPv6 protocol, you must configure values for this attribute, the Device, Protocol attributes, and the corresponding IPMultiNIC resources' PrefixLen attributes. Type-dimension: integer-scalar Range: 1 - 128 Example: 64 |
Protocol | Required to use the IPv6 protocol. |
Table: Optional attributes
Optional attribute | Description |
|---|---|
HandshakeInterval | Specifies the maximum number of tries the agent makes either to:
To prevent spurious failovers, the agent must try to contact a host on the network several times before it marks an interface as FAULTED. Increased values result in longer failover times, whether between the interface or from system to system in the case of FAULTED interfaces. Type and dimension: integer-scalar Default: 1 |
NetworkHosts | The list of hosts on the network that are pinged to determine if the network connection is alive. Enter the IP address of the host, instead of the host name, to prevent the monitor from timing out. DNS lookup causes the ping to hang. If this attribute is unspecified, the monitor tests the NIC by pinging the broadcast address on the interface. If more than one network host is listed, the monitor returns online if at least one of the hosts is alive. Type and dimension: string-vector Example: {"128.93.2.1", "128.97.1.2"} For a dual-stack or mixed mode configuration: Example: { "10.209.112.1", "2620:128:f0a2:900c::1" } |
Options | The ifconfig command options for the base IP address. Type and dimension: string-scalar Example: "metric 4 mtu 1400" |
PingOptimize | Determines whether to ping every monitor cycle. A value of 0 means that the agent pings either the network hosts or the broadcast address every monitor cycle. It pings every cycle to determine the state of the network interface. A value of 1 means that the agent uses the device statistics from the netstat output to determine the state of the interface. If no activity exists on the interface, the agent then pings the broadcast address to double-check the state of the network interface. Type and dimension: integer-scalar Default: 1 |
RouteOptions | Specifies the routing options that are passed to the route add command when the agent configures an interface. The RouteOptions attribute value is generally formed like this: "destination gateway metric". For details about the route command, refer to the man page for your operating system. When the value of this string is null, the agent does not add routes. Type and dimension: string-scalar Example: "192.100.201.0 192.100.13.7" |
FailoverInProgress | For internal use only. |