Specifications

Architecture
21
Introduction
the Gateway Client and provides the EMC enterprise with status
information on the connectivity health of the EMC storage devices
and the Gateway Client.
EMC servers receive the data in XML format and acknowledge the
receipt of data using SOAP (Simple Object Access Protocol)
commands. Once this response is received, the Gateway Client
terminates the connection. Figure 2 on page 21 provides an
illustration of the heartbeat communication paths.
Figure 2 Heartbeat communication
To EMC devices managed by the Gateway Client
Once every 60 minutes the Gateway Client determines if each
managed device is available for service by making a socket
connection to the device on one or more support application ports
and verifying that the service application(s) are responding. If a
change in status is detected, the Gateway Client notifies EMC over
the next heartbeat.
The heartbeat is a continuous service. EMC monitors the values sent
and may automatically trigger service requests if an Gateway Client
fails to send heartbeats, or if the values contained in a heartbeat
exceed certain limits.
Remote notification
(Connect Home)
The Gateway Clients also serve as a conduits for EMC products to
send remote notification event files to EMC. EMC hardware
platforms use remote notification for several different purposes.
Errors, warning conditions, health reports, configuration data, and
script execution statuses may be sent to EMC. Figure 3 on page 22
provides an illustration of the remote notification communication
paths.
When an alert condition occurs, the storage system generates an
event message file and passes it to the ConnectEMC service on the
device to format the files and request a transfer to EMC. ConnectEMC
Application socket
SOAP XML
EMC storage
array
EMC web and
access servers
SSL tunnel - TLS with RSA key exchange
3DES with SHA1 encryption
Device monitoring
Client