When you try to register the NSX Manager on the Deep Security Manager (DSM) console, the following error message shows:
Unable to configure NSX Manager 'XX.XX.XX.XX:443': Deep Security Service Manager already exists in NSX Manager.
Rebooting the NSX and DSM as well as following the steps on the article "Uninstall Deep Security from your NSX environment" does not resolve the issue. We can try removing the Deep Security Service on NSX manually through REST API.
Do the following:
- Before we are able to delete the "Deep Security Service Manager" object using REST API, make sure all components are deleted from vCenter Networking & Security. The Deep Security items under the following sections from the vSphere Web Client should be removed.
- Networking & Security Installation Service Deployments
- Networking & Security Service Definitions
- Networking & Security Service Composer
Follow the instructions on this article: Uninstall Deep Security from your NSX environment.
- On Google Chrome or Firefox, search for a REST API app (e.g. Postman) and launch the add-on.
- Get a list of all registered service managers in the NSX Manager using this REST call. Make sure that you use Basic Authentication to connect to the NSX manager.
GET https://[NSX Manager IP]/api/2.0/si/servicemanagersIn some instances, you need to be logged in to the NSX Manager from a web console to make the REST call work.
The REST call will outline all the service managers on NSX.
- Look for the entry with the description "Deep Security Service Manager" and grab its ID. It should be similar to this format: "servicemanager-xx". Verify that you have the correct service manager ID using the following:
GET https://[NSX Manager IP]/api/2.0/si/servicemanager/servicemanager-XXYou may import the list to Notepad++ to view it better. Be careful as there is one object with a very similar name called "Data Security Service Manager".
- Delete the registration of Deep Security Manager on NSX Manager using the second REST call:
DELETE https://[NSX Manager IP]/api/2.0/si/servicemanager/servicemanager-XX
It should return the message "Destroyed" after running the command.
- Go back to the Deep Security Manager web console and try adding NSX Server into the vCenter properties.