InfoScale™ 9.0 Cluster Server Bundled Agents Reference Guide - Linux
- 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
- 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
- LVMLogicalVolume agent
- LVMVolumeGroup agent
- Dependencies for LVMVolumeGroup agent
- Agent functions for LVMVolumeGroup agent
- State definitions for LVMVolumeGroup agent
- Attributes for LVMVolumeGroup agent
- Resource type definition for LVMVolumeGroup agent
- LVMVolumeGroup agent notes
- Sample configurations for LVMVolumeGroup agent
- Debug log levels for LVMVolumeGroup 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
- Support for spaces in directory names
- Support for multiple bindfs
- High availability fire drill
- VxFS file system lock
- IMF usage notes
- Enabling Level two monitoring for the Mount agent
- RHEL 7 and RHEL 8: NFS file system version
- RHEL 7 and RHEl 8: Configuring bind mounts
- Support for Amazon EFS
- Sample configurations for Mount agent
- Debug log levels for Mount agent
- Mount agent limitations
- VMwareDisks agent
- SFCache agent
- AWS EBSVol agent
- AzureDisk agent
- GoogleDisk agent
- Network agents
- About the network agents
- IP agent
- NIC agent
- Dependencies for NIC agent
- Bonded network interfaces for NIC agent
- Agent functions for NIC agent
- State definitions for NIC agent
- Attributes for NIC agent
- Resource type definition for NIC agent
- Notes for the NIC agent
- Case 1
- Case 2
- Case 3
- Sample configurations for NIC agent
- Debug log levels for NIC agent
- IPMultiNIC agent
- MultiNICA agent
- Dependencies for MultiNICA agent
- IP Conservation Mode (ICM) for MultiNICA agent
- Performance Mode (PM) for MultiNICA agent
- Agent function for MultiNICA agent
- Attributes for MultiNICA agent
- Resource type definition for MultiNICA agent
- Sample configurations for MultiNICA agent
- IPv6 configuration for MultiNICA agent
- Mixed mode configuration - IPv4 and IPv6 for MultiNICA agent
- Debug log levels for MultiNICA 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
- AWSIP agent
- AWSRoute53 agent
- AzureIP agent
- AzureDNSZone agent
- GoogleIP agent
- OCIIP 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
- 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
- Using Application agent with IMF
- Level two monitoring through MonitorProgram
- Using Application agent with ProPCV
- Requirement for programs
- Requirement for default profile
- Support for cloned Application agent
- Application monitoring inside Docker container
- Using the hadockersetup utility
- Requirement for systemd support
- Sample configurations for Application agent
- Debug log levels for Application agent
- AppMonHB agent
- AzureAuth agent
- CoordPoint agent
- KVMGuest agent
- Dependencies for KVMGuest agent
- Agent functions for KVMGuest agent
- State definitions for KVMGuest agent
- Attributes for KVMGuest agent
- Resource type definition for KVMGuest agent
- Notes for KVMGuest agent
- Support for guests created on RHEL 6, RHEL 7 (KVM environment), and SuSE Enterprise Linux 11 SP2 and SP3
- Storage and network configurations
- Guest live migration
- Managing virtual machines in RHEV environment
- Managing ISO image in SuSE KVM
- Using VCS to migrate virtual machines
- Configuring the KVMGuest agent for DR in a global cluster setup
- Configuring a non-admin user for RHEV-M that is using AD-based domain
- Virtual machine failover if host crashes
- KVMGuest agent requires curl and xpath commands in RHEV environment
- RHEV environment: If a node on which the VM is running panics or is forcefully shutdown, VCS is unable to start the VM on another node
- Sample configurations for KVMGuest environment
- Sample configurations for RHEV environment
- Sample Configuration for SuSE KVM
- Debug log levels for KVMGuest agent
- 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
- Infrastructure and support agents
- Testing agents
- Replication agents
- About the replication agents
- RVG agent
- RVGPrimary agent
- RVGSnapshot
- RVGShared agent
- RVGLogowner agent
- RVGSharedPri agent
- VFRJob agent
- Overview
- Dependencies for VFRJob agent
- High availability of scheduler and replicator daemons
- Agent functions for VFRJob agent
- State definitions for VFRJob agent
- Attributes for VFRJob agent
- Resource type definitions for VFRJob agent
- High availability of VFR daemons
- Configuration of VFRJob service groups on the source system
- Sample configuration of VFRJob agent on source system
- Configuration for VFRJob service groups on the target system
- Sample configuration of VFRJob agent on target system
- Changing file replication direction
- Notes for the VFRJob agent
GoogleIP agent
The GoogleIP agent manages the following networking resources in a Google Cloud Platform (GCP) environment:
Private IP - A private IP is a private numerical address that networked devices use to communicate with one another. It is used for communication between a GCP virtual private cloud (VPC) network and an on-premises network. A private IP is also referred to as Alias IP in GCP. To extend an on-premises network to a GCP VPC network, you use a VPN gateway.
Overlay IP - An overlay IP provides IP failover functionality for the InfoScale cluster nodes that are spread across subnets. It lets you redirect IP address traffic to another cluster node belonging to different subnet within the same VPC. An overlay IP must be defined outside the VPC Classless Inter-Domain Routing (CIDR) block.
The GoogleIP agent performs the following activities:
Fetches the NIC details, associates the private IP with the NIC, and disassociates the private IP from the NIC
Manages the route table entries of the overlay IP for failover across subnets
The GoogleIP agent uses GCP Python APIs to associate IP resources with a GCP VM instance.
Note:
An InfoScale deployment in GCP does not support IPv6 because VPC networks in GCP do not support IPv6 traffic within the network. For details, refer to the GCP documentation on VPC networks.
The Google service account associated with the VM instance have the following roles assigned, at a minimum:
compute.globalOperations.get
compute.instances.get
compute.instances.updateNetworkInterface
compute.networks.updatePolicy
compute.projects.get
compute.routes.create
compute.routes.delete
compute.routes.get
compute.routes.list
compute.zoneOperations.get
iam.serviceAccountUser
To access Google APIs, the
google-api-python-clientPython module must be present on the InfoScale cluster nodes.You can install Python SDK for GCP on each of the cluster nodes by running the following command:
# /opt/VRTSpython/bin/pip install google-api-python-client
A GoogleIP resource depends on the IP and the NIC resources.
Online |
|
Offline and Clean |
|
Monitor |
|
ONLINE |
|
OFFLINE |
|
UNKNOWN | This state indicates that one of the following situations may have occurred:
|
FAULTED | Indicates that the IP resources cannot be brought online or were abruptly stopped outside of VCS control. |
When an IP address that is associated with an OverlayIP resource is already online elsewhere in the VPC network, the GoogleIP service group with that OverlayIP resource should not come online. However, the service group does come online, and then the IP resource faults in both the clusters.
Workaround: Do not configure the IP address that is associated with the OverlayIP resource for any other device within the same VPC network.
Table: Required attributes
Attribute | Description |
|---|---|
PrivateIP | Secondary private IP address, also known as Alias IP, of the Google VM. You must specify a value for this attribute if no value is specified for OverlayIP. Type and dimension: string-scalar |
Device | Name of the network device. Run the ip addr command on the system to list all its network adapters. Example: eth0 (Indicates that the private IP address should be assigned to the next available alias of eth0.) Type and dimension: string-scalar |
OverlayIP | Overlay IP provides IP failover functionality for the InfoScale cluster nodes that are spread across subnets. Overlay IP must be outside of the VPC CIDR block in which the nodes are present. You must specify a value for this attribute if no value is specified for PrivateIP. Type and dimension: string-scalar |
Table: Optional attributes
Attribute | Description |
|---|---|
ProjectID | The customized name that you choose when you create a GCP project, or when you activate an API that requires you to create a project ID. Type and dimension: string-scalar |
VMName | Name of the GCP VM instance on which the agent is running. Type and dimension: string-scalar |
Zone | The GCP zone to which the VM instance belongs. Type and dimension: string-scalar |
type GoogleIP (
static keylist RegList = { Device }
static str ArgList[] = { PrivateIP, Device, OverlayIP,
ProjectID, Zone, VMName, tempProjectName, tempVMName,
tempZoneName, tempRouteName, tempDeviceName }
temp str tempProjectName
temp str tempRouteName
temp str tempZoneName
temp str tempVMName
temp str tempDeviceName
str PrivateIP
str Device
str OverlayIP
str ProjectID
str Zone
str VMName
)Sample configuration with Private IP:
GoogleIP Googlevipres (
PrivateIP = "10.209.1.5"
Device = eth0
)
IP ipres (
Device = eth0
Address = "10.209.1.5"
NetMask = "255.255.255.255"
)
NIC nicres (
Device = eth0
)
Googlevipres requires ipres
ipres requires nicresSample configuration with Overlay IP:
GoogleIP Googleipres (
Device = eth0
OverlayIP = "192.168.10.10"
)
IP ipres (
Device = eth0
Address = "192.168.10.10"
NetMask = "255.255.255.255"
)
NIC nicres (
Device = eth0
)
ipres requires nicres
Googleipres requires ipresThe GoogleIP agent uses the DBG_1 debug log level.
Arctera has tested and approved the GoogleIP agent with the following modules:
GCP Python module | Version |
|---|---|
cachetools | 5.3.0 |
google-api-python-client | 2.85.0 |
google-auth | 2.14.1 |
google-auth-httplib2 | 0.1.0 |
httplib2 | 0.22.0 |
pyasn1 | 0.4.8 |
pyasn1-modules | 0.2.8 |
rsa | 4.9 |
six | 1.16.0 |
uritemplate | 4.1.1 |