NSX Manager is already registered with a different McAfee ePO
search cancel

NSX Manager is already registered with a different McAfee ePO

book

Article ID: 307691

calendar_today

Updated On:

Products

VMware NSX for vSphere

Issue/Introduction

Symptoms:

  • Connecting McAfee MOVE through ePO to NSX Manager fails with the error:

    NSX Manager is already registered with different McAfee ePO.

  • Web interface of McAfee does not list any instance under service definition.

  • Running the following API query against NSX Manager returns an instance of McAfee MOVE as a Service Manager:

    GET https://nsxmgr-ip/api/2.0/si/servicemanagers

Environment

VMware NSX for vSphere 6.2.x
VMware NSX for vSphere 6.1.x

Cause

This issue occurs, when registering new instance of ePO with Mcafee Move with NSX Manager before unregistering the existing McAfee ePO from the same NSX Manager. Only one instance of McAfee move can be registered with NSX manager at any time.

Resolution

To resolve this issue,

  1. Ensure that all traces of McAfee are removed from NSX from the Web UI:

    Delete any McAfee MOVE Service Deployments on the Networking & Security -> Installation -> Service Deployments Page
    Delete the McAfee MOVE Service Definition on the Networking & Security -> Service Definitions page.

  2. Run the following API query to list the registered instances with the NSX Manager:

    GET https://nsxmgr-ip/api/2.0/si/servicemanagers

  3. From the response body, note down the objectID of the McAfee MOVE instance within the <objectId>.</objectId> tags.

  4. Run the following API query to confirm the registered instance

    GET https://nsxmgr-ip/api/2.0/si/servicemanager/object id-#

  5. Change the method to DELETE and re-run the API query

    DELETE https://nsxmgr-ip/api/2.0/si/servicemanager/object id-#

  6. Run the below API query againt to confirm that unregistration is successful.

    GET https://nsxmgr-ip/api/2.0/si/servicemanagers

    If above query does not returns any results, then NSX Manager is ready to accept a new instance.

Additional Information

Impact/Risks: