Quick Start Guide (USB)


This document presents the basic information on installing and initial configuration of AcloudA VDAS (rev 1.0). It is a comprehensive step-by-step guide, designed for users who are new to AcloudA product and technologies.

For any technical inquiries please contact us.

Warning !

The device is a hardware iSCSI initiator. Until you install the iSCSI session, the device will not be displayed on the system.

Installing product, downloding plug-ins, changing IQN


1. Turn your computer off first

2. Connect the AcloudA to the USB and plug SATA power

3. Connect the network cable

4. Turn your computer on

5. Open the browser and go to the ip-address of the device

(for the first usage, the device receives an ip-address via DHCP, the device address can be viewed in leasess DHCP-Server)

6. Log in using your login and password

(by default: login – admin, password – password)

7. Click the iSCSI tab

8. Add target

(specifying ip and port, click “add server”)

9. Click on the server you added, and select the target from the list

10. Enter the data for authentication, if necessary

(it should consist only of Latin characters and numbers and be a length of 12 to 16 characters)

11. Select the “USB” connection interface

12. Click “add connection” and continue working like with regular USB device


Changing IQN of device:

1. Select “iSCSI” tab

2. Check “Change IQN” box

3. Enter new IQN and apply

(changing IQN is available only from version 1.55)

AcloudA - GUIDE - Changing IQN

4. To reset the IQN to the factory settings you must completely reset the settings in the “Reset” tab.

Recommendations & Troubleshooting


  • The best performance was achieved with MTU 4400.
  • It is recommended that you allow jumbo frame packets on the network.

To reset the settings, install two jumpers on the board (located near the network connector) and turn on the device.

The existing configuration file will be erased.


Troubleshooting Guide

AcloudA Troubleshooting-1

The board operates with 1 stream; therefore, the speed is directly proportional to the latency.

We do not guarantee correct operation for channel widths to the server lower than 3 Mbit/s with delays greater than 65ms, as errors can occur when working with the file system and the ATA driver.

Some system administrators can partially or completely block certain packets including ICMP, UDP, TCP and ping.

Different file systems can have different timeout parameters for blocks.

Different implementations of iSCSI servers can have different boundary settings for response time and session creation.

The bandwidth of a channel can dynamically change due to the rebuilding of the routing tables of the network. You can check the route changes using the traceroute or MTR console utilities on Linux, and tracert on Windows.

Timeout variables for AcloudA (rev 2):

AcloudA Troubleshooting timeout


Fill the form below to get Extended version of this Guide

Please, fill all fields