Dell VNXe3200 Secure Remote Support for VNXe Requirements and Configuration - Page 6

ESRS Communication, Con ESRS, Prerequisites, Enable ESRS

Page 6 highlights

Configure ESRS restarting ESRS if it fails. The VNXe operating environment (OE) is responsible for persisting the configuration and certificates needed for ESRS to work. ESRS is supported in full service mode (both SPs are in service mode). If you have already enabled ESRS, the system functions as configured. If you have not enabled ESRS, you can temporarily enable it. In this latter situation, the configuration will not persist once your VNXe system has recovered to normal operation. ESRS Communication Access to a DNS server is required for the ESRS to work. By default your ESRS will attempt to use a configured proxy server to communicate with EMC backend systems. If the proxy server is not available, the ESRS will attempt to bypass the proxy server and communicate directly to the EMC backend systems. The ESRS service is the primary (default) method used by ConnectEMC to communicate with EMC backend systems. If ESRS is not enabled, ConnectEMC will automatically fallback to the secondary configuration and use the SMTP server, if configured. Configure ESRS Prerequisites As a prerequisite for enabling ESRS on your VNXe system, you must have an existing EMC Online Support account with Full Access support credentials (see Upgrading to Full Access privileges). Your Full Access support credentials are associated with your site ID/location which is associated with your system's serial number. Note: It can take up to 48 hours for your initial account with full access support credentials to be activated. Enable ESRS In Unisphere, you can configure ESRS support for a VNXe system in several ways: Unisphere tool Unisphere Configuration wizard Unisphere Post-upgrade wizard Description Wizard for configuring global VNXe system settings which runs when you first access the system with Unisphere. Wizard available in VNXe OE version 3.0 or later for configuring 6 EMC Secure Remote Support for VNXe Requirements and Configuration Technical Notes

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13

6
restarting ESRS if it fails. The VNXe operating environment (OE) is
responsible for persisting the configuration and certificates needed for
ESRS to work.
ESRS is supported in full service mode (both SPs are in service mode). If
you have already enabled ESRS, the system functions as configured. If
you have not enabled ESRS, you can temporarily enable it. In this latter
situation, the configuration will not persist once your VNXe system has
recovered to normal operation.
ESRS Communication
Access to a DNS server is required for the ESRS to work.
By default your ESRS will attempt to use a configured proxy server to
communicate with EMC backend systems. If the proxy server is not
available, the ESRS will attempt to bypass the proxy server and
communicate directly to the EMC backend systems.
The ESRS service is the primary (default) method used by ConnectEMC
to communicate with EMC backend systems. If ESRS is not enabled,
ConnectEMC will automatically fallback to the secondary configuration
and use the SMTP server, if configured.
Configure ESRS
Prerequisites
As a prerequisite for enabling ESRS on your VNXe system, you must
have an existing EMC Online Support account with Full Access support
credentials (see Upgrading to Full Access privileges). Your Full Access
support credentials are associated with your site ID/location which is
associated with your system’s serial number.
Note:
It can take up to 48 hours for your initial account with full access
support credentials to be activated.
Enable ESRS
In Unisphere, you can configure ESRS support for a VNXe system in
several ways:
Unisphere tool
Description
Unisphere Configuration wizard
Wizard for configuring global VNXe system settings which runs when
you first access the system with Unisphere.
Unisphere Post-upgrade wizard
Wizard available in VNXe OE version 3.0 or later for configuring
EMC Secure Remote Support for VNXe Requirements and Configuration Technical Notes