Performing a silent installation of the Avaya Hybrid Cloud Gateway non-seed node

Last Updated : Oct 21, 2024 |
Prolog information
Metadata
Keywords:
You can perform a silent installation of the Avaya Hybrid Cloud Gateway non-seed node by configuring the settings in the properties file according to your system requirement.
Before you begin
  • Ensure that you have the System Manager enrollment password.
    Note:
    To get the System Manager enrollment password, contact the System Manager administrator.
  • Ensure that the Avaya Hybrid Cloud Gateway seed node is up and running.
  • Ensure that you deploy Avaya Hybrid Cloud Gateway Open Virtualization Appliance (OVA).
    Note:
    Avaya Cloud Delivery is responsible for downloading and deploying Avaya Hybrid Cloud Gateway as part of the Avaya Experience Platform™ (On-Prem + Connect) service activation. Customers cannot download Avaya Hybrid Cloud Gateway from Avaya PLDS.
  • Ensure that the single.properties default file is available at /opt/Avaya on the deployed Avaya Hybrid Cloud Gateway machine.
  • Ensure that you configure the DNS entries for the Avaya Hybrid Cloud Gateway cluster Fully Qualified Domain Name (FQDN) with virtual IP and for all the Avaya Hybrid Cloud Gateway nodes FQDN.
  1. Connect to the Avaya Hybrid Cloud Gateway node virtual machine.
  2. Do one of the following:
    • Copy the single.properties file from /opt/Avaya to the home directory of the administrator.
      For example, /home/cust is the home directory of the administrator user cust.
    • Download the Avaya Hybrid Cloud Gateway binary file to the home directory of the administrator user.
      $ wget --no-check-certificate --auth-no-challenge --user <your_global_handle> --ask-password <url-to-AHCG-1.x.x.x.<build-number>.bin>
      $ Extract silent install property file from bin using command - ./<AHCG-*.bin> --tar -xvf ./single.properties
  3. Ensure that the binary has enough permissions before the installation: $ chmod 770 AHCG-1.x.x.x.<build-number>.bin
  4. Configure the settings following your system requirement in the properties file.
    ADDITIONAL INFORMATION:
    You can use the properties file template at Properties file template for silent installation of the Avaya Hybrid Cloud Gateway non-seed node to configure the settings. The following are the properties file settings for the non-seed node with virtual IP:
    • ETH1_FQDN: An optional field. The network interface to use for FQDN. For on-premise OVA-based installation, do not enter any field value.
    • CLOUD_SIGNALING_NETWORK_INTERFACE: An optional field. The network interface for cloud signaling. By default, the interface is eth0. For on-premise OVA based installation, use the default value.
    • CLOUD_OAMP_NETWORK_INTERFACE: An optional field. The network interface for cloud operations, administration, maintenance, and provisioning (OAMP). By default, the interface is eth0. For on-premise OVA based installation, use the default value.
    • ENTERPRISE_SIGNALING_NETWORK_INTERFACE: An optional field. The network interface for enterprise signaling. By default, the interface is eth0. For on-premise OVA based installation, use the default value.
    • ENTERPRISE_OAMP_NETWORK_INTERFACE: An optional field. The network interface for enterprise OAMP. By default, the interface is eth0. For on-premise OVA based installation, use the default value.
    • AHCG_ADMIN_PORTAL_INTERFACE: An optional field. The network interface between Avaya Hybrid Cloud Gateway and Application Center Administration. By default, the interface is eth0. For on-premise OVA based installation, use the default value.
    • INTERNODE_NETWORK_INTERFACE: An optional field. The network interface for internode. By default, the interface is eth0. For on-premise OVA based installation, use the default value.
    • SYSTEM_MGR_IP: A mandatory field. The System Manager FQDN.
    • SYSTEM_MGR_HTTPS_PORT: The HTTPS port for contacting System Manager. The default value is 443.
    • SYSTEM_MGR_PW: A mandatory field. The System Manager enrollment password.
    • KEYSTORE_PW: A mandatory field. The keystore password for Avaya Hybrid Cloud Gateway certificates.
    • SYSTEM_NAME: A mandatory field. The name of the system. The maximum length is 100 characters.
    • HCM_ADDRESS: A mandatory field. The Hybrid Cloud Manager FQDN. You can get the FQDN address from your account administrator.
    • ISO3166_SUBDIVISION_CODE: A mandatory field. The country code and the region code.
    • INITIAL_NODE: The initial node is a seed or a non-seed node. Enter n for non-seed node.
      Note:
      When the value of the initial node is n, the installation process ignores the SYSTEM_NAME, HCM_ADDRESS, and ISO3166_SUBDIVISION_CODE parameters.
    • LOCAL_FRONTEND_HOST: A mandatory field. The FQDN of the non-seed node hostname.
    • SEED_NODE: A mandatory field. The IP address of the seed node.
    • REST_FRONTEND_HOST: A mandatory field. The FQDN of the virtual IP.
    • KA_ENABLED: The indicator for enabling or disabling virtual IP handling on this node. Enter y to enable the usage of virtual IP handling.
    • KA_VIRTUAL_IP: A mandatory field. The IP address of the Avaya Hybrid Cloud Gateway cluster FQDN virtual IP.
    • KA_INTERFACE: The network interface to use for the virtual IP. By default, the interface is eth0.
    • KA_MASTER_YN: A mandatory field. Enter n to set the node as the non-seed node.
    • KA_AUTHENTICATION_PASSWORD: A mandatory field. The virtual IP authentication password for the Avaya Hybrid Cloud Gateway cluster.
    • SIP_SIGNALING_PORT: An optional field. The Avaya Hybrid Cloud Gateway SIP listening port.
  5. Run the Avaya Hybrid Cloud Gateway binary with a parameter that represents the full path to the properties file from the home directory of the administrator: app install <directory>/single.properties
    ADDITIONAL INFORMATION:
    For example, app install /home/cust/single.properties
    ADDITIONAL INFORMATION:
    If the Avaya Hybrid Cloud Gateway binary name is not provided, the app install command picks the default binary name from /opt/Avaya/
    ADDITIONAL INFORMATION:
    After the silent installation, all the Call Signaling Agent (CSA) services are up and running. You must be able to configure the remaining items on the Application Center Administration.
  6. To check the status of nodes in the cluster, do the following:
    ADDITIONAL INFORMATION:
    1. Connect to a node.
    2. Run the command: app listnodes. The status is Live for the nodes that are up and running.
  7. Configure the remaining items on Application Center Administration.
    ADDITIONAL INFORMATION:
    Note:
    • Post-installation, you can add new or change existing settings using the configuration utility.
    • The value of SYSTEM_MGR_IP, SYSTEM_MGR_HTTPS_PORT, SYSTEM_MGR_PW, KEYSTORE_PW, SYSTEM_NAME, HCM_ADDRESS, ISO3166_SUBDIVISION_CODE, and REST_FRONTEND_HOST must remain the same for every node in the cluster.
    • To enable virtual IP or FQDN configuration, the value of KA_VIRTUAL_IP, KA_INTERFACE, and KA_AUTHENTICATION_PASSWORD must remain the same for every node in the cluster.
    • For security reasons, each time you perform a silent install, the settings file clears the following passwords: KEYSTORE_PW, SYSTEM_MGR_PW, and REST_FRONTEND_HOST.
    • After every silent install, the settings file deletes the value of REST_FRONTEND_HOST, KA_ENABLED, KA_VIRTUAL_IP, KA_INTERFACE, KA_MASTER_YN, and KA_AUTHENTICATION_PASSWORD.
    • After every complete silent installation, # gets added to KA_ENABLED, KA_VIRTUAL_IP, KA_INTERFACE, KA_MASTER_YN, and KA_AUTHENTICATION_PASSWORD fields.
Related links
Avaya Hybrid Cloud Gateway installation options