AWS Storage Gateway User Guide
Troubleshooting On-Premises Gateway Issues
Troubleshooting Your Gateway
Following, you can find information about troubleshooting issues related to gateways, file shares,
volumes, virtual tapes, and snapshots. The on-premises gateway troubleshooting information covers
gateways deployed on both the VMware ESXi and Microsoft Hyper-V clients. The troubleshooting
information for file shares applies to the file gateway type. The troubleshooting information for volumes
applies to the volume gateway type. The troubleshooting information for tapes applies to the tape
gateway type.
Topics
•
Troubleshooting On-Premises Gateway Issues (p. 316)
•
Troubleshooting Your Microsoft Hyper-V Setup (p. 320)
•
Troubleshooting Amazon EC2 Gateway Issues (p. 323)
•
Troubleshooting Hardware Appliance Issues (p. 326)
•
Troubleshooting File Share Issues (p. 328)
•
Troubleshooting Volume Issues (p. 331)
•
Troubleshooting Virtual Tape Issues (p. 334)
•
Best Practices for Recovering Your Data (p. 338)
Troubleshooting On-Premises Gateway Issues
The following table lists typical issues that you might encounter working with your on-premises
gateways.
Topics
•
Enabling AWS Support To Help Troubleshoot Your Gateway Hosted On-Premises (p. 318)
Issue
Action to Take
You cannot find the IP
address of your gateway.
Use the hypervisor client to connect to your host to find the gateway IP
address.
• For VMware ESXi, the VM's IP address can be found in the vSphere
client on the
Summary
tab. For more information, see
• For Microsoft Hyper-V, the VM's IP address can be found by logging
into the local console. For more information, see
.
If you are still having trouble finding the gateway IP address:
• Check that the VM is turned on. Only when the VM is turned on does
an IP address get assigned to your gateway.
• Wait for the VM to finish startup. If you just turned on your VM,
then it might take several minutes for the gateway to finish its boot
sequence.
You're having network or
firewall problems.
• Allow the appropriate ports for your gateway.
API Version 2013-06-30
316