000036264 - Error message "Cannot complete login due to an incorrect user name or password" while integrating VMware ESX / ESXi host with Log Collector in RSA Security Analytics 10.6.x

Document created by RSA Customer Support Employee on Apr 19, 2018•Last modified by RSA Customer Support Employee on Apr 21, 2018
Version 2Show Document
  • Comment • 0
  • View in full screen mode

Article Content

Article Number000036264
Applies ToRSA Product Set: Security Analytics, NetWitness Logs & Network
RSA Product/Service Type: Log Collector
RSA Version/Condition: 10.6.x.x
Platform: CentOS, VMware ESX, VMware ESXi
IssueThe error message below is reported when the command perl /etc/netwitness/ng/logcollection/content/collection/vmware/vmware-events/NwVmwareCollector.pl -events -server <ESXi host IP>  -username <user> -password <pass> -count N is executed on the log collector for debugging purpose while doing the VMware ESXi integration:


[root@xxx vmware-events]# perl /etc/netwitness/ng/logcollection/content/collection/vmware/vmware-events/NwVmwareCollector.pl -events -server <ESXi host IP> -username <username> -password <password> -count 1000
Error: Cannot complete login due to an incorrect user name or password.
Perl exited with active threads:
        1 running and unjoined
        0 finished and unjoined
        0 running and detached
TasksDIRECTLY connect to the ESXi host by specifying the IP address in a browser and connect using the same credentials as used in the script above.  It should return with the same error (shown below) as seen when running the script. 

Cannot complete login due to an incorrect user name or password.


User-added image
ResolutionStep 1 of the VMware ESX-ESXi Event Source Configuration Guide states:
 
Log onto the ESXi host using the vSphere Client, with administrative privileges.


However, a customer might unknowingly login to the vCenter, followed by creating a role, local user and assign the permission to the user thinks that all the roles and permissions are assigned to the ESXi host.

Ensure that all the steps performed are on the ESXi host and not on the vCenter. There shouldn't be any requirement for vCenter access for doing this integration successfully. 

Attachments

    Outcomes