Specifications

Configuration

Introduction

There are no technical restrictions on the network location of the

Gateway Client server, other than its connectivity to your devices and

Policy Manager as well as to the EMC enterprise. EMC strongly

recommends the use of a firewall to block network ports not required

by ESRS.

VMware/Hyper-V

requirements

VMware servers must be version ESX 2.52 and later.

Minimum requirements:

◆ 15 GB partition

◆ 2.2 GHz virtual CPU

◆ 512 MB memory allocated (2 GB recommended, 3GB preferred)

Note: EMC strongly recommends that virtual hosts meet the same hardware

and OS recommendations as for physical hardware so as to minimizes

performance issues.

Optional components:

◆ SMB modules

◆ VMotion functionality (for Policy Manager only, and cannot be

used for the ESRS Client due to RSA LockBox Technology)

Note: The customer MUST be aware the over provisioning of the underlying

VMware ESX/Hyper-V infrastructure may have significant negative impact

on the operation and functionality of ESRS.

VMware/Hyper-V

examples

Scenario 1

Two physical ESX servers with three VMware partitions—two on the

first server and one on the second server. The first server hosts a

Gateway Client and the Policy Manager. The second server hosts

another Gateway Client. This enables you to put applications on the

same server that normally would not be co-located.

Scenario 2

Three or more physical servers in an existing VMware environment.

You install two or more Gateway Clients and Policy Manager on any

of the existing physical servers, independent of physical location.

High Availability

Gateway Cluster

configuration

To enable maximum remote access availability, EMC recommends

deployment of a High Availability Gateway Cluster configuration to

eliminate single point of failure. A Gateway Cluster refers to the

relationship created between two or more Gateway Clients.