Configuring Network Adapters for Your Gateway - Amazon Storage Gateway
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Amazon S3 File Gateway documentation has been moved to What is Amazon S3 File Gateway?

Volume Gateway documentation has been moved to What is Volume Gateway?

Tape Gateway documentation has been moved to What is Tape Gateway?

Configuring Network Adapters for Your Gateway

Storage Gateway uses a single VMXNET3 (10 GbE) network adapter by default, but you can configure your gateway to use more than one network adapter so that it can be accessed by multiple IP addresses. You might want to do this in the following situations:

  • Maximizing throughput– You might want to maximize throughput to a gateway when network adapters are a bottleneck.

  • Application separation – You might need to separate how your applications write to a gateway's volumes. For example, you might choose to have a critical storage application exclusively use one particular adapter defined for your gateway.

  • Network constraints – Your application environment might require that you keep your file shares and the initiators that connect to them in an isolated network. This network is different from the network by which the gateway communicates with Amazon.

In a typical multiple-adapter use case, one adapter is configured as the route by which the gateway communicates with Amazon (that is, as the default gateway). Except for this one adapter, initiators must be in the same subnet as the adapter that contains the file shares to which they connect. Otherwise, communication with the intended targets might not be possible. If a target is configured on the same adapter that is used for communication with Amazon, then file share traffic for that target and Amazon traffic flows through the same adapter.

In some cases, you might configure one adapter to connect to the Storage Gateway console and then add a second adapter. In such a case, Storage Gateway automatically configures the route table to use the second adapter as the preferred route. For instructions on how to configure multiple adapters, see the following topics:

Configuring Your Gateway for Multiple NICs on a VMware ESXi Host

The following procedure assumes that your gateway VM already has one network adapter defined, and describes how to add an adapter on VMware ESXi.

To configure your gateway to use an additional network adapter in VMware ESXi host
  1. Shut down the gateway.

  2. In the VMware vSphere client, select your gateway VM.

    The VM can remain turned on for this procedure.

  3. In the client, open the context (right-click) menu for your gateway VM, and choose Edit Settings.

  4. On the Hardware tab of the Virtual Machine Properties dialog box, choose Add to add a device.

  5. Follow the Add Hardware wizard to add a network adapter.

    1. In the Device Type pane, choose Ethernet Adapter to add an adapter, and then choose Next.

    2. In the Network Type pane, ensure that Connect at power on is selected for Type, and then choose Next.

      We recommend that you use the VMXNET3 network adapter with Storage Gateway. For more information on the adapter types that might appear in the adapter list, see Network Adapter Types in the ESXi and vCenter Server Documentation.

    3. In the Ready to Complete pane, review the information, and then choose Finish.

  6. Choose the Summary tab for the VM, and choose View All next to the IP Address box. The Virtual Machine IP Addresses window displays all the IP addresses you can use to access the gateway. Confirm that a second IP address is listed for the gateway.

    Note

    It might take several moments for the adapter changes to take effect and the VM summary information to refresh.

  7. In the Storage Gateway console, turn on the gateway.

  8. In the Navigation pane of the Storage Gateway console, choose Gateways and choose the gateway to which you added the adapter. Confirm that the second IP address is listed in the Details tab.

For information about local console tasks common to VMware, Hyper-V, and KVM hosts, see Performing tasks on the VM local console (File Gateway)

Configuring Your Gateway for Multiple NICs in Microsoft Hyper-V Host

The following procedure assumes that your gateway VM already has one network adapter defined and that you are adding a second adapter. This procedure shows how to add an adapter for a Microsoft Hyper-V host.

To configure your gateway to use an additional network adapter in a Microsoft Hyper-V Host
  1. On the Storage Gateway console, turn off the gateway.

  2. In the Microsoft Hyper-V Manager, select your gateway VM.

  3. If the VM isn't turned off already, open the context (right-click) menu for your gateway and choose Turn Off.

  4. In the client, open the context menu for your gateway VM and choose Settings.

    
                        Microsoft Hyper-V virtual machines screen showing context menu
                            settings for Storage Gateway VM.
  5. In the Settings dialog box for the VM, for Hardware, choose Add Hardware.

  6. In the Add Hardware pane, choose Network Adapter, and then choose Add to add a device.

    
                        Microsoft Hyper-V VM settings screen with Add Hardware and Network
                            Adapter selected.
  7. Configure the network adapter, and then choose Apply to apply settings.

    In the following example, Virtual Network 2 is selected for the new adapter.

    
                        Microsoft Hyper-V VM settings screen with new virtual NIC
                            selected.
  8. In the Settings dialog box, for Hardware, confirm that the second adapter was added, and then choose OK.

  9. On the Storage Gateway console, turn on the gateway.

  10. In the Navigation pane choose Gateways, then select the gateway to which you added the adapter. Confirm that the second IP address is listed in the Details tab.

For information about local console tasks common to VMware, Hyper-V, and KVM hosts, see Performing tasks on the VM local console (File Gateway)