Views:

Procedure

  1. Go to AdministrationNetworkInterfaces.
    The data interface supports users' Internet traffic to and from the internal network. This screen displays information on all data interfaces available for the on-premises gateway.
    Note
    Note
    If you need to select another data interface to use by the on-premises gateway, you can configure the required data interface on this screen first, and go to Deployment WizardNetwork to select it and complete the process at a later time.
    1. Select a data interface and click Edit.
      The Edit Interface window appears.
    2. Configure the data interface.
      Select an IP address allocation mode from the Mode drop-down list:
      • Static: Configure the IP settings (IP addresses, gateways, and DNS servers) for the data interface manually.
      • DHCP: Have a DHCP server allocate IP settings to the data interface.
      Select the Web console, Ping, and SSH check boxes as necessary.
      • Web console: Allow access to the web console through this data interface.
        Note
        Note
        If there is only one data interface, Web console must be selected to ensure connection to the web console.
      • Ping: Allow the connection to be checked with the ping utility.
      • SSH: Allow access to the on-premises gateway via SSH.
      If the IP address changes, the admin user will be automatically logged off the web console and re-log on to the web console using the new IP address.
    3. Click Save.
      The data interface information displays on the Interfaces screen.
    4. To view the latest information of each data interface, click Refresh.
  2. Go to AdministrationNetworkGeneral.
    1. Configure a primary and optionally secondary DNS server for the on-premises gateway for domain name resolution.
    2. Type the host name of the VM where the on-premises gateway is installed in the Host name text box.
    3. Click Save.
      A window appears, indicating that the system needs reboot to apply the configuration. To reboot the system, click OK. To go back to the General screen, click Cancel.
  3. Go to AdministrationNetworkStatic Routes.
    Static routes allow the TMWS on-premises gateway to overcome problems routing traffic to and from network segments beyond the next router hop to which the TMWS on-premises gateway connects. Static routes allow you to manually control the router connection used to send traffic to the Internet or back to the end users.
    1. Click Add.
      The Add Static Route window appears.
    2. Configure the following:
      • Protocol: IPv4 or IPv6.
        Note
        Note
        In this version, only IPv4 is supported.
      • Network ID: Network ID.
      • IPv4 netmask: IPv4 netmask that matches the network ID.
      • Router: IP address of the router.
      • Interface: Data interface used by the on-premises gateway.
    3. Click Save.
      The static route displays on the Static Routes screen.
      Make sure that the static route meets the actual network environment of your organization.
    4. To delete a static route, select it and click Delete.