AWS Storage Gateway User Guide
Troubleshooting On-Premises Gateway Issues
Issue Action to Take
• If you use a firewall or router to filter or limit network traffic, you
must configure your firewall and router to allow these service
endpoints for outbound communication to AWS. For more
information about network and firewall requirements, see Network
and Firewall Requirements (p. 12).
Your gateway's activation
fails when you click the
Proceed to Activation
button in the AWS Storage
Gateway Management
Console.
• Check that the gateway VM can be accessed by pinging the VM from
your client.
• Check that your VM has network connectivity to the Internet.
Otherwise, you'll need to configure a SOCKS proxy. For more
information on doing so, see Routing Your On-Premises Gateway
Through a Proxy (p. 254).
• Check that the host has the correct time, that the host is configured
to synchronize its time automatically to a Network Time Protocol
(NTP) server, and that the gateway VM has the correct time. For
information about synchronizing the time of hypervisor hosts and
VMs, see Synchronizing Your Gateway VM Time (p. 261).
• After performing these steps, you can retry the gateway deployment
using the AWS Storage Gateway console and the Setup and Activate
Gateway wizard.
• Check that your VM has at least 7.5 GB of RAM. Gateway allocation
fails if there is less than 7.5 GB of RAM. For more information, see
Requirements (p. 10).
You need to remove a disk
allocated as upload buffer
space. For example, you
might want to reduce the
amount of upload buffer
space for a gateway, or you
might need to replace a disk
used as an upload buffer that
has failed.
For instructions about removing a disk allocated as upload buffer
space, see Volume Gateway (p. 354)
You need to improve
bandwidth between your
gateway and AWS.
You can improve the bandwidth from your gateway to AWS by setting
up your Internet connection to AWS on a network adapter (NIC)
separate from that connecting your applications and the gateway VM.
Taking this approach is useful if you have a high-bandwidth connection
to AWS and you want to avoid bandwidth contention, especially
during a snapshot restore. For high-throughput workload needs,
you can use AWS Direct Connect to establish a dedicated network
connection between your on-premises gateway and AWS. To measure
the bandwidth of the connection from your gateway to AWS, use the
CloudBytesDownloaded and CloudBytesUploaded metrics of
the gateway. For more on this subject, see Measuring Performance
Between Your Gateway and AWS (p. 207). Improving your Internet
connectivity helps to ensure that your upload buffer does not fill up.
API Version 2013-06-30
317
To Next Page
Loading...