Deploy a private gateway with an OVA file

This section guides you how to deploy a private gateway with an OVA file

Note these are the minimum VMware Requirements for handling up to 1,000 simultaneous sessions:

  • 2 CPU Cores, Reserved

  • 4GB RAM, Reserved

  • 10 GB Disk Space, Thick Provisioned

It is important to leverage the pooling feature and always use at least two private gateways for redundancy and availability purposes.

  1. Log into MetaAccess console

  2. Click “+ Gateway” button at the top right to navigate to a gateway download page. Download the Private Gateway OVA file.

    Note: This image is suitable for VMware environments. If you don’t have access to an enterprise VMware environment, try https://www.vmware.com/products/workstation-player.html.

  3. Log in as the admin user using the default password.

  4. Update that default password to something more secure.

  5. Give the VM a static IP address. This form will default to the IP address assigned by DHCP, but you can set it to whatever makes sense for your environment.

  6. Go back to MetaAccess console, navigate to Settings > Global, copy the registration code on the Account tab

  7. Go back to the Private Gateway Configuration Tool, enter the registration code as the Code. This step can take a while while it generates keys and calls back to SDP Controller to register itself.

  8. When registration is complete you’ll be notified to go to the MetaAccess console. In this example I’m using the testing stage, your gateway may be linked against your MetaAccess tenant environment. New gateways start in a “pending” state. This means that an administrator must approve them before they can be used.

  9. Navigating to that link, you will see the new gateway in a list of private gateways waiting to be accepted and activated. If somebody else used your registration code and you don’t recognize the entry here you could remove them instead.

  10. Having accepted the gateway, you must now activate it by selecting the gateway, and then activating it.

  11. This should automatically enable private gateways as the access method for the OPSWAT Client, but this is also configurable via the radio buttons on the left.

  12. Test the Private Gateway connection: follow steps in Private Gateway Test App to enable a testing app built-in the private gateway