New ESM 6.9.1 server. How to re-register connectors?

Hello,

Here is the situation. We had an ESM 6.5 server we were looking to upgrade, but the server kicked the bucket during the process. No backup available.

We installed a brand new server with ESM 6.9.1. The older 6.5 server was using a self-signed certificate. The new one is using a CA-signed certificate. IMPORTANT: the new server has the exact same name and ip address as the old one.

My question: how do I go about re-registering my smart connectors onto the new ESM server? I've tried adding the CA cert to the certificates repository on the ConApp and then selecting a host, clicking on CERTIFICATES and then updating all of the host's containers. However this did not change anything as the connectors continue to cache events.

I then just for kicks deleted the ESM destination from one of the connectors and re-added it. Then this connector in particular started sending events to the new server and I (of course) could see the connector from the ESM console.

Is there a more batch-like way of doing this?

Parents
  • Exchanged a few emails with support about this.

    Apparently the only way to do this is to either execute the smart connector setup and reregister the ESM destination OR go through the Connector Appliance and delete/recreate the destination. For each and every connector that has an ESM destination of course.

    This works but you end up losing any cached data that has accumulated.

    To this support told me :

    "This cached data is lost when you recreate the destination, our internal resources are working and testing to create a way to prevent these cached data from being lost but unfortunately they are still working on it."

Reply
  • Exchanged a few emails with support about this.

    Apparently the only way to do this is to either execute the smart connector setup and reregister the ESM destination OR go through the Connector Appliance and delete/recreate the destination. For each and every connector that has an ESM destination of course.

    This works but you end up losing any cached data that has accumulated.

    To this support told me :

    "This cached data is lost when you recreate the destination, our internal resources are working and testing to create a way to prevent these cached data from being lost but unfortunately they are still working on it."

Children
No Data