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.

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

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).