Please enter search query.
Search <book_title>...
Veritas InfoScale™ 7.4.2 Solutions in Cloud Environments
Last Published:
2020-06-12
Product(s):
InfoScale & Storage Foundation (7.4.2)
Platform: Linux,Windows
- Overview and preparation
- Configurations for Amazon Web Services - Linux
- Configurations for Amazon Web Services - Windows
- Replication configurations in AWS - Windows
- HA and DR configurations in AWS - Windows
- Configurations for Microsoft Azure - Linux
- Configurations for Microsoft Azure - Windows
- Configurations for Google Cloud Platform- Linux
- Configurations for Google Cloud Platform - Windows
- Replication to and across cloud environments
- Migrating files to the cloud using Cloud Connectors
- Troubleshooting issues in cloud deployments
Public access to InfoScale cluster nodes in AWS using elastic IP - Linux
To allow public access to an InfoScale cluster node or to an application configured for HA or DR in AWS, specify the IP to be used in the ElasticIP attribute for the AWSIP resource. For example, if you have an application that needs to be highly available and to be accessible globally, you can use the ElasticIP attribute of the AWSIP agent to ensure both.
Sample service group configuration with elastic IP
The following snippet is a service group configuration from a sample VCS configuration file (main.cf):
group appnetworkSG ( SystemList = { ip-172-34-20-109 = 0, ip-172-34-30-231 = 1 } AutoStartList = { ip-172-34-20-109, ip-172-34-30-231 } ) AWSIP AwsIp_Res ( PrivateIP @ ip-172-34-20-109 ="172.34.20.110" PrivateIP @ ip-172-34-30-231 ="172.34.30.220" ElasticIP = "52.3.20.17" Device = eth0 AWSBinDir = "/usr/local/bin" ) IP Ip_Res ( Device = eth0 Address @ ip-172-34-20-109 ="172.34.20.110" Address @ ip-172-34-30-231 ="172.34.30.220" NetMask = "255.255.240.0" ) NIC Nic_Res ( Device = eth0 ) AwsIp_Res requires Ip_Res Ip_Res requires Nic_Res