iWorkflow connect with NSX problem

Hi Valen,

I am going to put some the logs of one of the failures below so it can be more easily looked at. I cut them short to make more readable.

[I][2001][07 Mar 2017 07:45:02 UTC][8100/cm/cloud/connectors/vmware-nsx NsxConnectorCollectionWorker] Successfully updated 2 host certificates in whitelist

[WARNING][2012][07 Mar 2017 07:45:05 UTC][8100/cm/cloud/connectors/vmware-nsx NsxConnectorCollectionWorker] GET call to NSX API (https://10.77.76.9/api/1.0/appliance-management/global/info) fa iled: $HttpException: status:403, body: ...

[WARNING][2013][07 Mar 2017 07:45:05 UTC][8100/cm/cloud/connectors/vmware-nsx NsxConnectorCollectionWorker] Error occured in VMware NSX Connector 6d2b14c8-d50d-48aa-a6f0-96c9bd3733af Step SETU P_NSX_CONNECTION. Details: Unable to connect to NSX manager at 10.77.76.9 because $HttpException: status:403, body:

...

I think it is trying to access the below api on the NSX and request is a being processed by the NSX device but is being refused access and for permission reasons.

This is what I think NSX is not permitting access to:

NSX API https://10.77.76.9/api/1.0/appliance-management/global/info 

I am not very familiar with the NSX side of things. Is sounds like the user may not have access to the URI of the API. Is it possible that some additional permissions may need to be configured on the NSX manager?

Do you have access to the NSX logs? perhaps they could provide a clue.

I got this from VMware web site:

Collecting diagnostic information for VMware NSX for vSphere

To collect diagnostic information for VMware NSX for vSphere:

 1) Log in to the NSX Manager virtual appliance through a web browser.

        For example, http://NSX_Manager_IP

 2) In NSX Manager Virtual Appliance Management,

        click Download Tech Support Log.
        Click Download > Save.



See more information here:
    https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2074678

I am commenting here to see if anyone with more NSX knowledge may have any ideas.

Tim T

Hi Tim,

 

Thank you for your help, it was auth failure, now it is working.