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
Error: 'Unable to contact RuntimeAPI' in RSA Federated Identity Manager (FIM) Number of Views How do you merge FSM audit logs? Number of Views Configure Device History Settings for a Risk-Based Authentication Policy Number of Views Issue Opening Event Explorer - Device with an invalid character Number of Views Apache will not start - Error logged : Init: Pass phrase incorrect Number of Views
Trending Articles
Troubleshooting RSA SecurID Access Identity Router to RSA Authentication Manager test connection failures RSA SecurID Software Token 5.0.2 Downloads for Microsoft Windows RSA Authentication Manager 8.9 Release Notes (January 2026) Quick Setup Guide - Passwordless Authentication in Windows MFA Agent for Active Directory RSA Authentication Manager 8.8 Setup and Configuration Guide
Don't see what you're looking for?
