Server and Network Prerequisites

General Prerequisites

• Use dedicated machines for hosting the Cloud Connector and do not install any other components on these machines.

• Ensure the node on which the AppViewX Cloud Connector is installed has access to the enterprise’s internal network devices.

• On the node on which the AppViewX Cloud Connector is installed, ensure that the node's clock is synchronized with the network time using NTP/PTP.

  For the ntpd package (for CentOS, RHEL, and Amazon Linux 2), execute the following sequence of commands:

  sudo yum install -y ntp
  sudo systemctl enable ntpd
  sudo systemctl start ntpd

  For the chronyd package , execute the following sequence of commands:

  • For CentOS, RHEL, and Amazon Linux 2

    sudo yum install -y chrony
    sudo systemctl enable chronyd
    sudo systemctl start chronyd

    OR
  • For Ubuntu

    sudo dnf install -y chrony
    sudo systemctl enable chronyd
    sudo systemctl start chronyd

• Ensure that the AppViewX Cloud Connector can establish connectivity with the AppViewX SaaS server endpoints over HTTPS (port 443).

  Note: In the instance a proxy being used, the proxy has to be configured as a pass-through.
  Note: The Cloud Connector URL to be whitelisted for connectivity can be obtained from the Cloud Connector Settings Page of your SaaS account. Example of the AppViewX Cloud Connector URL:

  https://<example-tenant>-cc.appvx.com:443/

  Also, ensure that the cloud connector URL is not blocked by your puppet scripts, anti-virus software settings, and/or firewall rules.
  Tip: : To verify connectivity with the AppViewX SaaS servers, use the cURL utility.

  1. Install the cURL utility.
     • On Ubuntu: sudo apt-get install curl
     • On CentOS, RHEL, and Amazon Linux 2: sudo yum install curl
  2. To check connectivity, execute the following command:
     • If proxy is not enabled:

       curl -k --max-time 20 --connect-timeout 20 -s -o /dev/null -w "%{http_code}" "<<https://AppViewX SaaS server URL>>/socket.io/?EIO=3&transport=polling&t=O11wka_"

     • If proxy is enabled:

       curl -k --proxy "<<http://proxyhost:proxyport>>" --max-time 20 --connect-timeout 20 -s -o /dev/null -w "%{http_code}" "<<https://AppViewX SaaS server URL>>/socket.io/?EIO=3&transport=polling&t=O11wka_"

     If connectivity has been established successfully, the command will return the HTTP code 200. If the command returns any other code, it indicates that connectivity is not established.

• Disable the firewalld in the tenant’s node (Ubuntu) where the AppViewX Cloud Connector is to be installed.

  To check the current status of firewalld, execute the command given below:

  sudo ufw status 

  To permanently disable firewalld, execute the command given below:

  sudo ufw disable 

• Disable the firewalld in the tenant’s node (CentOS, RHEL, and Amazon Linux 2) where the AppViewX Cloud Connector is to be installed.

  To check the current status of firewalld, execute the command given below:

   sudo systemctl status firewalld --now

  To permanently disable the firewalld, execute the command given below:

   sudo systemctl disable firewalld --now

  To restrict other devices from enabling the firewalld, execute the command given below:

  sudo systemctl mask firewalld --now 

• Disable the nftables service.
  • For Ubuntu

    sudo apt purge -y nftables

  • FoCentOS, RHEL, and Amazon Linux 2

    sudo yum remove -y nftables

• If you are utilizing the IP ranges 10.42.0.0/16 and 10.43.0.0/16, modify them before installing the cloud connector.

  (These are the default CIDR ranges for the AppViewX Cloud Connector and should be modified to prevent IP conflicts).

  To adjust the IP range:

  1. To modify install.sh, execute the command: vi install.sh.
  2. For a k3d installation:
     1. In the install.sh file, search for the text k3d cluster create.
     2. At the end of this line, paste the following: --k3s-arg '--cluster-cidr=<preferredcidr>/16' --k3s-arg '--service-cidr=<preferredcidr>/16'.

        Here, replace <preferredcidr> with your preferred CIDR address.

     OR

     For a standard k3s installation:

     1. In the install.sh file, search for the text --disable=metrics-server.
     2. Add a space and paste the following text: --cluster-cidr=<preferredcidr>/16 --service-cidr=<preferredcidr>/16.

        Here, replace <preferredcidr> with your preferred CIDR address.

  3. Save the file.
  4. Execute the following command: ./install.sh

Additional Prerequisites for Installation on RHEL8+

Additional Prerequisites for Installation on Amazon Linux 2