AWS storage gateway on KVM

1

Hello!

I've been trying to configure AWS Storage Gateway on KVM. I have successfully created a new KVM using AWS provided qcow image and configured it according to the documentation (network, DNS, storage). All tests have passed. AWS storage gateway is reachable until the init connection - I'm able to create a new storage gateway in the AWS panel, provide IP address (of KVM instance) to connect. The process hangs on " Loading local disks, which can take several minutes. After they load, you must configure them before you can use the gateway.".

After that the Gateway got offline and isn't reachable (I'm not able to telnet to it on port 80 for example). KVM requires to be configured again from the scratch.

Has anyone encounter a similar situation and have any tips on where to look for the problem?

asked 10 months ago276 views
1 Answer
0

Hello,

At a high level, after activation, gateway will download the needed patches from Storage gateway service to update itself. During this process, the gateway software is shutdown for the update, and gateway will go into offline state for a brief moment soon after activation.

However, since your gateway stayed in the offline state after the activation longer, please check below;

  1. Please make sure the gateway meets the minimum resources requirements (4 vCPUs and 16GB RAM). Gateway software might not start up if there is no sufficient resources.

  2. If gateway can connect to endpoint “dp-1.storagegateway.region.amazonaws.com:443”, if using VPCE, then check if gateway can connect VPCE on port 1031. As gateway need to download the patches from dp endpoint. This can be verified using the network connectivity test.

  3. If gateway can connect to endpoint “client-cp.storagegateway.region.amazonaws.com:443”, if using VPCE, then check if gateway can connect VPCE on port 1026. As gateway need to send the status data to cp endpoint. This can be verified using the network connectivity test.

  4. A minimum of 100Mbps is required to successfully download, activate, and update the gateway. If the download speed is too slow, it might take long time for gateway downloading the patches and eventually timeout.

With regards to the port 80, this port is only used for activation purposes and is disabled by the service right after activation. Therefore connectivity to the gateway VM on port 80 will be refused. This is expected behavior.

If the above suggestions do not address the issue, please open a case with AWS support for further investigation.

Thank you!

Harshi
answered 10 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions