Support



Troubleshooting

Connectivity check failed.

There may be instances when the appliance configuration process may fail and a user may encounter a “failed” message upon concluding the process.

This may be caused by firewall rules, internet router, IP address clash (already in use), etc. or incorrect entry of values on configuration screens. Please discuss with your network administrator and rerun the configuration by issuing the following command:

sudo /opt/tools/initial_config.sh

Appliance fails to appear in console after configuration.

Please make sure you have provided iQuate with the correct public IP address for the appliance server which must be registered with iQuate support.

Patch upgrades.

From time to time it may be necessary to upgrade your appliance server. This can be done either as a new VM download and configuration (you can follow the above steps to upgrade to a new version of the appliance) or as a patch to an existing server.

In the case of a patch upgrade, a link to the new software may be emailed to you from the iQuate support team.

Upgrade the Appliance with the upgrade-appliance.sh script (Build 1353 and above)

From Appliance version 1353, the directory /opt/iqas/server contains a script called upgrade-appliance.sh.

This script facilitates upgrading the Appliance using a newer Appliance compressed assembly.

The compressed assembly can be retrieved using S3(AWS) or from an already downloaded .zip file. In this second case, the file must be in the same folder as the script.

Upgrade the Appliance manually

Download the server patch zip file and follow these steps:

  • Connect to the appliance via SSH with the appropriate username and password
    ssh USER@HOSTNAME

  • Stop the associated services and processes
    USER@APPLIANCE:~$ sudo service monit stop
    USER@APPLIANCE:~$ sudo /opt/communication/stop-communication-layer.sh
    USER@APPLIANCE:~$ sudo systemctl stop iqas.service

  • Backup the configuration of the service and keychains that are stored on the Appliance
    USER@APPLIANCE:~$ cd /opt/iqas/
    USER@APPLIANCE:/opt/iqas$ rm -rf server-4.5.old
    USER@APPLIANCE:/opt/iqas$ mv server-4.5 server.old; mv server server.old

  • Download the desired update version for the appliance scan engine
    USER@APPLIANCE:/opt/iqas$ wget https://iquate-apscout.s3.eu-west-2.amazonaws.com/Fishbowl/releases/main/server-4.5.1-<patch-build number>appliance.zip

  • Where access is not available from the appliance server then the file should be downloaded and manually copied over to the appliance server to the /opt/iqas folder

  • Unzip archive
    USER@APPLIANCE:/opt/iqas$ unzip server-4.5.1-1027-appliance.zip -d server

  • Copy the configuration from the backup to the newly extracted discovery service folder USER@APPLIANCE:/opt/iqas$ mkdir -p server/db/ server/conf/Appliance/
    USER@APPLIANCE:/opt/iqas$ cp -fT server.old/conf/Appliance/config.properties server/conf/Appliance/config.properties
    USER@APPLIANCE:/opt/iqas$ cp -fT server.old/db/keychain.mv.db server/db/keychain.mv.db
    USER@APPLIANCE:/opt/iqas$ cp -fT server.old/db/account.mv.db server/db/account.mv.db

  • Optional: copy previous catalog (alternatively you can resynchronize the catalog from the cloud down to the appliance).
    USER@APPLIANCE: cp server.old/db/catalog.mv.db server/db/catalog.mv.db

  • Update iqas service path and reload
    USER@APPLIANCE: sudo sed -i "s|/opt/iqas/server-4.5|/opt/iqas/server|g" /lib/systemd/system/iqas.service
    USER@APPLIANCE: sudo systemctl daemon-reload

  • Update monit scripts
    USER@APPLIANCE: sudo sed -i "s|/opt/iqas/server-4.5|/opt/iqas/server|g" /opt/tools/*

  • Update monit scripts
    USER@APPLIANCE: sudo sed -i "s|/opt/iqas/server-4.5|/opt/iqas/server|g" /opt/communication/start-communication-layer.sh

  • Restart services
    USER@APPLIANCE:~$ sudo /opt/communication/start-communication-layer.sh

  • Allow the Discovery Service some time to reconnect & resynchronise with the Cloud platform

  • Check the cloud UI under Settings → Appliances and verify that the appliance Last Status is recent, and confirm the appliance version is showing as you would expect

FAQs

What are the different VMware Disk Provisioning types: Thick or Thin?

When you deploy the iQCloud Virtual Appliance files on your ESX / ESXi servers, you can specify the storage option types as Thick (Flat) or Thin, depending upon your hardware resources. The Thick provisioning option pre-allocates all hard disk space (total 20 GB) for the Virtual Appliance while the Thin provisioning option dynamically allocates the storage space for the Virtual Appliance (up to 20 GB).

What are the standard Private IP Address?

Private IP Address Range

Subnet Mask

Class Description

Private IP Address Range

Subnet Mask

Class Description

10.0.0.0 – 10.255.255.255

255.0.0.0

Class A Network

172.16.0.0 – 172.31.255.255

255.240.0.0

Class B Network

192.168.0.0 – 192.168.255.255

255.255.0.0

Class C Network


Where do I download the iQCloud Virtual Appliance from?

The appliance can be downloaded from within the iQCloud console (Help → Download Virtual Appliance) or by requesting the download link from the support team at iQuate.

What is the iQCloud Virtual Appliance?

The iQCloud Virtual Appliance is a software bundle that includes the iQCloud Appliance Manager, the Java Development Kit, MySQL database, and a RabbitMQ Messaging server all pre-installed on Ubuntu 16.04 Server OS.

Why would I want to use the iQCloud Virtual Appliance?

The iQCloud Virtual Appliance is used to run discovery jobs from within the enterprise network without requiring direct access to the iQCloud platform from all the endpoint systems. The iQCloud Virtual Appliance consolidates the communication between the endpoint systems and the iQCloud platform.

How is the iQCloud Virtual Appliance licensed?

There is no additional license fee or time limit for the iQcloud Virtual Appliance. However, a separate license key is needed to activate the virtual appliance.

What protocol is used between the virtual appliance and the iQCloud platform?

All communication between the iQCloud Virtual Appliance and the iQCloud platform is over secure communication channels via the HTTPS protocol.

Can the iQCloud VA also be used to discover physical servers?

Yes, you can use the iQCloud Virtual Appliance to discover physical servers as well as virtual servers and public cloud servers.

Contact us

Further help guides are available through the online help available through your iQCloud login console.