AWS Storage Gateway - Page 248

AWS Storage Gateway User Guide
Performing Tasks on the VM Local Console (File Gateway)
Configuring Your Gateway to Use the VMXNET3 Network Adapter
AWS Storage Gateway supports the E1000 network adapter type in both VMware ESXi and Microsoft
Hyper-V Hypervisor hosts. However, the VMXNET3 (10 GbE) network adapter type is supported
in VMware ESXi hypervisor only. If your gateway is hosted on a VMware ESXi hypervisor, you can
reconfigure your gateway to use the VMXNET3 (10 GbE) adapter enter. For more information on this
adapter, see the VMware website.
Important
To select VMXNET3, your guest operating system enter must be Other Linux64.
Following are the steps you take to configure your gateway to use the VMXNET3 adapter:
1. Remove the default E1000 adapter.
2. Add the VMXNET3 adapter.
3. Restart your gateway.
4. Configure the adapter for the network.
Details on how to perform each step follow.
To remove the default E1000 adapter and configure your gateway to use the VMXNET3
adapter
1. In VMware, open the context (right-click) menu for your gateway and choose Edit Settings.
2. In the Virtual Machine Properties window, choose the Hardware tab.
3. For Hardware, choose Network adapter. Notice that the current adapter is E1000 in the Adapter
Enter section. You replace this adapter with the VMXNET3 adapter.
4. Choose the E1000 network adapter, and then choose Remove. In this example, the E1000 network
adapter is Network adapter 1.
Note
Although you can run the E1000 and VMXNET3 network adapters in your gateway at the
same time, we don't recommend doing so because it can cause network problems.
5. Choose Add to open the Add Hardware wizard.
6. Choose Ethernet Adapter, and then choose Next.
7. In the Network Enter wizard, select VMXNET3 for Adapter Enter, and then choose Next.
8. In the Virtual Machine properties wizard, verify in the Adapter Enter section that Current Adapter is
set to VMXNET3, and then choose OK.
9. In the VMware VSphere client, shut down your gateway.
10. In the VMware VSphere client, restart your gateway.
API Version 2013-06-30
241