000014700 - What is procedure to add or reconnect Cisco ESA partner to RSA DLP?

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014700
Applies ToRSA Data Loss Prevention
IssueWhat is procedure to add or reconnect Cisco ESA partner to RSA DLP?
Error: "invalid serverUID" in CiComponentShell.log with TRACE enabled
ResolutionAllow the Cisco ESA to add itself to the RSA DLP Enterprise Manager.
Adding the device manually to the EM may result in duplicate entries and communication failures.
Confirm the following setting in application.properties:
          interop.enableOnStartup=true
Note: if you recently upgraded from 9.5 to 9.5 SP1 the setting may have been changed to false during the upgrade
Stop the Enterprise Manager and Local Site Interop services
Delete the RSA\Site\ci.db file
Remove all entries for this partner from the following tables:
DV_DEVICE, DV_DEVICE_IP_ADDRESSES, DV_DEVICE_PACKAGE_LEVEL, DV_DEVICE_STATUS
Remove the ci.db from the Cisco ESA (contact Cisco regarding procedure for this action)
Start the
Enterprise Manager and Local Site Interop services
Allow time for the Cisco to communicate to the Enterprise Manager and the partner device record should be automatically generated in DLP
NotesTo see activity on the interop service, enable TRACE logging using knowledgebase article a63258
Legacy Article IDa63666

Attachments

    Outcomes