Skip to content

Latest commit

 

History

History
221 lines (136 loc) · 17.4 KB

manage-on-premises-fgw.md

File metadata and controls

221 lines (136 loc) · 17.4 KB
Raw

Performing tasks on the VM local console (file gateway)

For a file gateway deployed on-premises, you can perform the following maintenance tasks using the VM host's local console. These tasks are common to VMware, Microsoft Hyper-V, and Linux Kernel-based Virtual Machine (KVM) hypervisors.

Topics

Logging in to the file gateway local console

When the VM is ready for you to log in, the login screen is displayed. If this is your first time logging in to the local console, you use the default user name and password to log in. These default login credentials give you access to menus where you can configure gateway network settings and change the password from the local console. Storage Gateway enables you to set your own password from the Storage Gateway console instead of changing the password from the local console. You don't need to know the default password to set a new password. For more information, see Logging in to the file gateway local console.

[Image NOT FOUND]

To log in to the gateway's local console

  • If this is your first time logging in to the local console, log in to the VM with the default credentials. The default user name is admin and the password is password. Otherwise, use your credentials to log in. Note
    We recommend changing the default password. You do this by running the passwd command from the local console menu (item 6 on the main menu). For information about how to run the command, see Running storage gateway commands on the local console. You can also set the password from the Storage Gateway console. For more information, see Logging in to the file gateway local console.

Setting the local console password from the Storage Gateway console

When you log in to the local console for the first time, you log in to the VM with the default credentials. For all types of gateways, you use default credentials. The user name is admin and the password is password.

We recommend that you always set a new password immediately after you create your new gateway. You can set this password from the Storage Gateway console rather than the local console if you want. You don't need to know the default password to set a new password.

To set the local console password on the Storage Gateway console

  1. Open the Storage Gateway console at https://console.aws.amazon.com/storagegateway/home.

  2. On the navigation pane, choose Gateways, and then choose the gateway for which you want to set a new password.

  3. For Actions, choose Set Local Console Password.

  4. In the Set Local Console Password dialog box, enter a new password, confirm the password, and then choose Save.

    Your new password replaces the default password. Storage Gateway doesn't save the password but rather safely transmits it to the VM. Note
    The password can consist of any character on the keyboard and can be 1–512 characters long.

Configuring an HTTP proxy

File gateways support configuration of an HTTP proxy.

Note
The only proxy configuration that file gateways support is HTTP.

If your gateway must use a proxy server to communicate to the internet, then you need to configure the HTTP proxy settings for your gateway. You do this by specifying an IP address and port number for the host running your proxy. After you do so, Storage Gateway routes all AWS endpoint traffic through your proxy server. Communications between the gateway and endpoints is encrypted, even when using the HTTP proxy. For information about network requirements for your gateway, see Network and firewall requirements.

To configure an HTTP proxy for a file gateway

  1. Log in to your gateway's local console:

  2. On the AWS Appliance Activation - Configuration main menu, enter 1 to begin configuring the HTTP proxy.
    [Image NOT FOUND]

  3. On the HTTP Proxy Configuration menu, enter 1 and provide the host name for the HTTP proxy server.
    [Image NOT FOUND]

    You can configure other HTTP settings from this menu as shown following.
    [See the AWS documentation website for more details]

  4. Restart your VM to apply your HTTP configuration settings.

Configuring your gateway network settings

The default network configuration for the gateway is Dynamic Host Configuration Protocol (DHCP). With DHCP, your gateway is automatically assigned an IP address. In some cases, you might need to manually assign your gateway's IP as a static IP address, as described following.

To configure your gateway to use static IP addresses

  1. Log in to your gateway's local console:

  2. On the AWS Appliance Activation - Configuration main menu, enter 2 to begin configuring your network.
    [Image NOT FOUND]

  3. On the ** Network Configuration** menu, choose one of the following options.
    [Image NOT FOUND]
    [See the AWS documentation website for more details]

Testing your FSx File gateway connection to gateway endpoints

You can use your gateway's local console to test your internet connection. This test can be useful when you are troubleshooting network issues with your gateway.

Viewing your gateway system resource status

When your gateway starts, it checks its virtual CPU cores, root volume size, and RAM. It then determines whether these system resources are sufficient for your gateway to function properly. You can view the results of this check on the gateway's local console.

To view the status of a system resource check

  1. Log in to your gateway's local console:

  2. In the AWS Appliance Activation - Configuration main menu, enter 4 to view the results of a system resource check.
    [Image NOT FOUND]

    The console displays an [OK], [WARNING], or [FAIL] message for each resource as described in the table following.
    [See the AWS documentation website for more details]

    The console also displays the number of errors and warnings next to the resource check menu option.

Configuring a Network Time Protocol (NTP) server for your gateway

You can view and edit Network Time Protocol (NTP) server configurations and synchronize the VM time on your gateway with your hypervisor host.

To manage system time

  1. Log in to your gateway's local console:

  2. In the AWS Appliance Activation - Configuration main menu, enter 5 to manage your system's time.
    [Image NOT FOUND]

  3. In the System Time Management menu, choose one of the following options.
    [Image NOT FOUND]
    [See the AWS documentation website for more details]

Running storage gateway commands on the local console

The VM local console in Storage Gateway helps provide a secure environment for configuring and diagnosing issues with your gateway. Using the local console commands, you can perform maintenance tasks such as saving routing tables, connecting to Amazon Web Services Support, and so on.

To run a configuration or diagnostic command

  1. Log in to your gateway's local console:

  2. On the AWS Appliance Activation - Configuration main menu, enter 6 for Command Prompt.
    [Image NOT FOUND]

  3. On the AWS Appliance Activation - Command Prompt console, enter h, and then press the Return key.

    The console displays the AVAILABLE COMMANDS menu with what the commands do, as shown in the following screenshot.
    [Image NOT FOUND]

  4. At the command prompt, enter the command that you want to use and follow the instructions.

To learn about a command, enter the command name at the command prompt.

Configuring network adapters for your gateway

By default, Storage Gateway is configured to use the E1000 network adapter type, but you can reconfigure your gateway to use the VMXNET3 (10 GbE) network adapter. You can also configure Storage Gateway so it can be accessed by more than one IP address. You do this by configuring your gateway to use more than one network adapter.

Topics

Configuring your gateway to use the VMXNET3 network adapter

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.

For KVM hypervisor hosts, Storage Gateway supports the use of virtio network device drivers. Use of the E1000 network adapter type for KVM hosts isn't supported.

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.
    [Image NOT FOUND]

  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.

After your gateway restarts, reconfigure the adapter you just added to make sure that network connectivity to the internet is established.

To configure the adapter for the network

  1. In the VSphere client, choose the Console tab to start the local console. Use the default login credentials to log in to the gateway's local console for this configuration task. For information about how to log in using the default credentials, see Logging in to the file gateway local console.
    [Image NOT FOUND]
    [Image NOT FOUND]

  2. At the prompt, enter 2 to select Network Configuration, and then press Enter to open the network configuration menu.

  3. At the prompt, enter 4 to select Reset all to DHCP, and then enter y (for yes) at the prompt to set all adapters to use Dynamic Host Configuration Protocol (DHCP). All available adapters are set to use DHCP.
    [Image NOT FOUND]

    If your gateway is already activated, you must shut it down and restart it from the Storage Gateway Management Console. After the gateway restarts, you must test network connectivity to the internet. For information about how to test network connectivity, see Testing your FSx File gateway connection to gateway endpoints.