ESRS VE and various EMC system configurations

Have you been able to successfully manage the VNX onto the ESRSVE?  In other words, If you launch the ESRSVE GUI, click on Devices and Manage Device, does the VNX appear?

There are many product connect homes that pass thru the ESRS VE and are configured though the Product end. There is no "one set of procedures since various products that pass through ESRS VE are different, some use Https, others go through SMTP.   Some  go through a pre-filter process that may be filtered prior to reaching ESRS.

Example Unified VNX   Connect Home process  goes through UDoctor which filters connect homes and determines actions to take, some may be benign and are cancelled in UDoctor, those that move forward goes through ConnectEMC

this  then  routes to the protocol that is configured Http:, SMTP, and if configured to pass through ESRS (if not may be email home through customer server) will pass through, which then routes to EMC,  This is another filtering process, and if further action is needed, will create a Service Request. please note; that most Connect Home Test creates a Service Request, again some may not which is determined by the Product Connect Home configuration.  The word Connect Home is generic since Products may have other names for the alert process such as "Reports, Dial Home, etc...

Most products after configurations will perform a test connect home, which results in a cancelled Service request which I believe for VNX may be a 2004 code test event.  you can perform a test event on your VNX with in the GUI or at the command line   Naviseccli -h inserttestevent   (you may need to insert credentials in that command see your product guide or contact product support for further information.   

Note: there are some products that currently qualified  to use Rest Services that pass through ConnectEMC on the VE (not many at this time) again contact your product team to determine if your product is qualified or when (VNX is not at this time).

Thanks Cal,

For us, we have various EMC products(NS480, Centerra, VNX-unified, Isilon, Avamar, Data Domain, Brocade/Connectrix). We followed all the instructions for migrating from a older ESRS to ESRS-VE. The migration of the Policy Manager database as well as the import of devices on the newer ESRS-VE went smoothly.

On our VNX, I had to modify the ConnectHome settings as they were configured to use the ESRS servers for email and FTP. So now I'm looking through documentation on our other products with not much success.

The only outstanding issue is that the secondary control station from our VNX now shows as missing in ESRS and there was a issue our CE is working on with creating the ESRS cluster in servicelink.

The issues are relatively minor, but hoping documentation would exist under ESRS for the various products.

I understand your frustration, ESRS does not manage the product end including their different connect home methods.

the common denominator is  most use ConnectEMC which then uses ESRS as a pass through to EMC, but each product has their own Connect Home configuration.  Some products has 1 item that sends notifications through ESRS to EMC, other products with multiple nodes, get managed and process with in its product software then may send a report ,XLM file etc .  New Products are using Rest API which deploys the ESRS device and sets up connect home through Secure tunnel

and uses ConnectEMC that is on the ESRS VE (which handles multiple products)  So as we move forward Connect Homes will be easy to manage and will be more user friendly.  In the meantime it is the individual product that has their own Connect Home procedures.