Unsolved
This post is more than 5 years old
12 Posts
0
3528
November 24th, 2015 20:00
ESRS IP client vs ConnectEMC
Hi EMC,
I would very much appreciate if you can answer the following questions for me.
We have recently rolled out ESRS VE 3.06 and our current dail home alerts are going through our mail server using Dail home templates.
Couple of VNX arrays recenlty upgraded to latest code which they have option to use ConnectEMC for Dialhome to EMC.
We are on the way to upgrade other VNXs to the latest code, they all will have ConnectEMC at somepoint.
Do you still recommed us to install ESRS ipclient in the environment? The main reason for installing ESRS IPclient is the benefits it has like automatically send SP logs to EMC, events notification to EMC and config files to EMC which normal dial home template does not have those additional features or benefits.
I am not sure if ConnectEMC does work exactly same as ESRS IP client.
Your earliest response is much appreciated.
ryanbrancel1
53 Posts
0
November 25th, 2015 14:00
The embedded ConnectEMC component of VNX Block arrays starting with system code 33 patch 81 and 32 patch 216 provides the same functionality of previous ESRS IP Client. Therefore utilizing the new embedded VNX Block ConnectEMC, along with ESRS VE, provides the best support functionality.
Nadimpalli
12 Posts
0
November 26th, 2015 00:00
Thanks for the reply Ryan.
What about polling?
Does either ConnectEMC or ESRS VE 3.06 do the heartbeat polling for the devices that are added to them?
I believe ESRS IP client does the regular polling for the devices that are added to it?
Please list out the functions of ESRS IP client.
We have ESRS VE 3.06 and our arrays will be upgraded to 32.218 comes with inbuilt connectEMC feature.
Using both ESRS VE 3.06 and ConnectEMC in our environment, do you think we can definitely avoid ESRS IP client install in our environment.
Thanks once again
ryanbrancel1
53 Posts
0
November 27th, 2015 16:00
If you are referring to the ESRS heartbeat polling (every 30 seconds to verify uptime), then that still occurs with ESRS Device Client (VNX Block Embedded) as it does with ESRS IP Client and ESRS VE 3.06. The ESRS Device Client contains the UDoctor components on each VNX storage processor (as it did with the ESRS IP Client). UDoctor consists of 3 components: Array Health Analyzer (AHA), Triiage Real Time (TRT), and Triiage on Management Station (TOMS). There is also an Array Configuration and Capture Upload (ACU) component that runs every 4 weeks. If you have a VNX Unified array (File/Block), then the UDoctor component exists on the control station. If you have multiple VNX Block arrays then a case could be made to have those managed by one ESRS IP Client Workstation. Otherwise the ESRS Device Client and built-in ConnectEMC contains the same functionality embedded in to the VNX storage processors now (or control stations if File).