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 5Number of Views How do you merge FSM audit logs? 1Number of Views Error: 'Unable to contact RuntimeAPI' in RSA Federated Identity Manager (FIM) 8Number of Views Device Settings for Risk-Based Authentication 8Number of Views RSA Governance & Lifecycle Advanced Dashboards Library Release Notes - Revision 2.0 19Number of Views
Trending Articles
RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide RSA Authentication Manager 8.9 Release Notes (January 2026) RSA Release Notes for RSA Authentication Manager 8.8 Deploying RSA Authenticator 6.2.2 for Windows Using DISM Downloading RSA Authentication Manager license files or RSA Software token seed records
Don't see what you're looking for?