Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Removing Deep Security Service Manager in NSX using REST API

    • Updated:
    • 18 Feb 2019
    • Product/Version:
    • Deep Security 9.5
    • Deep Security 9.6
    • Platform:
    • Windows 2008 Server R2
Summary

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.

Unable to configure 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.

Details
Public

Do the following:

  1. 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.

  2. On Google Chrome or Firefox, search for a REST API app (e.g. Postman) and launch the add-on.
  3. 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/servicemanagers

     
    In some instances, you need to be logged in to the NSX Manager from a web console to make the REST call work.

    Get the list of registered service managers

    The REST call will outline all the service managers on NSX.

    List of registered service managers

  4. 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-XX

    Find the Deep Security Service Manager entry

     
    You 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".
  5. 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

    Delete the registration of Deep Security Manager

    It should return the message "Destroyed" after running the command.

  6. Go back to the Deep Security Manager web console and try adding NSX Server into the vCenter properties.
Premium
Internal
Rating:
Category:
Troubleshoot
Solution Id:
1104002
Feedback
Did this article help you?

Thank you for your feedback!

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.