Specifications

22
EMC Secure Remote Support Gateway for Linux Release 2.24 Operations Guide
Introduction
uploads the file to the Gateway Client where it is received by one of
the following local transport protocols:
◆ HTTPS, if a device is qualified to send files using HTTPS
◆ Passive FTP
◆ SMTP
When an event file is received, the Gateway Client compresses the
file, opens the SSL tunnel to the EMC servers, and posts the data file
to EMC. At EMC, the file is decompressed and forwarded to the
Customer Relationship Management (CRM) systems.
Figure 3 Remote notification communication
Remote access To establish an EMC Global Services remote access session to a
customer device, ESRS uses asynchronous messaging to ensure that
all communication is initiated outbound from the Gateway Client at
the customer’s site.
After being properly authenticated at EMC, an EMC Global Services
professional makes a request to access a managed device. The remote
access session request includes a unique identifier for the user, the
serial number of the managed device, and the remote application he
or she will use to access the device. It may include the Service
Request number. This request is queued at EMC until an Gateway
Client that manages the device in question sends a heartbeat to EMC.
In response to the Heartbeat XML message, the EMC enterprise sends
a special status in the SOAP response. This response contains the
request information as well as the address of the Global Access Server
and a unique session ID which the Gateway Client would use to
connect. The Gateway Client uses its local repository to determine the
local IP address of the end device, checks the Policy Manager
permissions to see if the connection is permitted, and if approved,
establishes a separate persistent SSL connection to the Global Access
Server for the specific remote access session.
HTTPS POST
EMC storage
array
EMC web and
access servers
SSL tunnel - TLS with RSA key exchange
AES-256 with SHA1 encryption
File monitoring
Client
SOCKS/HTTPS/FTP/SMTP