What is procedure to add or reconnect Cisco ESA partner to RSA DLP?
Originally Published: 2014-01-09
Article Number
Applies To
Issue
Error: "invalid serverUID" in CiComponentShell.log with TRACE enabled
Resolution
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
Notes
Related Articles
Configure Device History Settings for a Risk-Based Authentication Policy Number of Views Error: 'Unable to contact RuntimeAPI' in RSA Federated Identity Manager (FIM) Number of Views RSA Governance & Lifecycle Advanced Dashboards Library Release Notes - Revision 2.0 Number of Views In RSA Identity Governance & Lifecycle, the change request manual activity assignment link (Assign to Specific Group or Ro… Number of Views RSA Authentication Manager 8.3 RADIUS Reference Guide Number of Views
Trending Articles
Passwordless Authentication in Windows MFA Agent for Active Directory – Quick Setup Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Authentication Manager Upgrade Process RSA Authentication Manager 8.7 SP2 Setup and Configuration Guide An example of SSO using SAML and ADFS with RSA Identity Management and Governance 6.9.x
Don't see what you're looking for?
