Specifications

EMC Secure Remote Support Gateway for Linux Release 2.24 Operations Guide

Introduction

Each Gateway Client acts as a proxy, carrying information to and

from managed devices or to a Policy Manager. Gateway Clients can

also queue session requests in the event of a temporary local network

failure.

The Gateway Clients do not have their own user interface, and are

run as Linux services. All Gateway Client actions are logged to a local

rolling runtime log file.

Table 1 on page 19 shows the minimum configuration of the required

hardware and the application software.

Policy Manager The Policy Manager allows you to set permissions for devices that are

being managed by the Gateway Clients. The Gateway Client polls the

Policy Manager every 2 minutes and receives the current policies,

which it then are cached locally. (Because of this polling time interval,

policy updates may take up to 2 minutes before being applied.)

During the periodic poll, the Gateway Client posts all requests and

actions that have occurred which are then written to local log files

and the Policy Manager database. When a remote access request

arrives at the Gateway Client for device access, the access is

controlled by the Gateway Client enforcing the policy set by the

Policy Manager.

The Policy Manager software may be on another application server

(for example, an EMC Navisphere

Management station) or

co-located on a non-high-availability Gateway Client server

(recommended for test purposes only).

Note: Once installed on your server, the Policy Manager application is

inaccessible by third parties, including EMC. For more information about the

Operations and configuration of the Policy Manager, refer to the EMC Secure

Remote Support Policy Manager Operations Guide.

Proxy server Network traffic can be configured to route from the Gateway Clients

through proxy servers to the Internet. Such configurations include

support for auto-configuration, HTTP, and SOCKS proxy standards.

Note: When a customer configuration requires proxy communication

between the Gateway Client and the Policy Manager or between the Gateway

Client and the EMC Enterprise, if the Gateway Client cannot connect to either

the Policy Manager or to the EMC Enterprise through the proxy

communication path, it will continue to attempt to connect multiple times.

After a couple of minutes, if the Gateway Client is unable to connect using

the proxy connection path, it will then attempt a direction connection