Host preparation channel health shows down in NSX for vSphere

Products

• VMware NSX

Issue/Introduction

• When preparing a host, the vibs are installed correctly but the channel health shows as down. (No connection to port 5671 or 1234).
   
• The vsfw and netcpa processes are in a wait state.
  
  [esxiadmin@DEMCHHC003X:~] ps -s | grep vsfwd
37594 37594 vsfwd WAIT UFUTEX 0-127
37596 37594 vsfwd WAIT USLP 0-127
   
• In the vsfwd.log file, you see entries similar to:
  
  2017-07-17T11:20:19Z vsfwd: [INFO] Setting glibc memory options...
2017-07-17T11:20:19Z vsfwd: [INFO] Enable cleaning protobuf
2017-07-17T11:20:19Z vsfwd: [INFO] Started main thread
2017-07-17T11:20:19Z vsfwd: [INFO] Fetching rmq configuration...
2017-07-17T12:01:19Z vsfwd: [INFO] Setting glibc memory options...
2017-07-17T12:01:19Z vsfwd: [INFO] Enable cleaning protobuf
2017-07-17T12:01:19Z vsfwd: [INFO] Started main thread
2017-07-17T12:01:19Z vsfwd: [INFO] Fetching rmq configuration...
2017-07-17T13:17:10Z vsfwd: [INFO] Setting glibc memory options...
2017-07-17T13:17:10Z vsfwd: [INFO] Enable cleaning protobuf
2017-07-17T13:17:10Z vsfwd: [INFO] Started main thread
2017-07-17T13:17:10Z vsfwd: [INFO] Fetching rmq configuration...
   
• In the vsm.log file, you see entries similar to:
  
  2017-07-17 13:20:55.228 CEST ERROR TaskFrameworkExecutor-23 EventHandlerManagerImpl$EventHandlerInvokeTask:156 - Error encountered in invoking handler com.vmware.vshield.vsm.common.messaginginfra.UserWorldSetupHandler$HostPreparedEventHandler for event HostPreparedEvent.
(vim.fault.NoPermission) {
faultCause = null,
faultMessage = null,
object = ManagedObjectReference: type = OptionManager, value = EsxHostAdvSettings-27379, serverGuid = 9e1a####-####-####-###-########9682,
privilegeId = Host.Config.AdvancedConfig
}
at sun.reflect.GeneratedConstructorAccessor426.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:526)
at java.lang.Class.newInstance(Class.java:383)
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX for vSphere 6.3.x
VMware NSX for vSphere 6.2.x

Cause

This issue occurs when the user account used to connect the NSX Manager to vCenter Server in the NSX UI does not have enough privileges.

Resolution

To resolve this issue, use the SSO user to connect NSX Manager and vCenter Server.