Starting with VFVE 8.3/VMware cartridge version 5.6.16, VMwarePerormance agent user credentials are stored in a lockbox instead of hard-coding in agent ASP.
In some cases, after upgrading FVE from any prior version OR upgrading VMware cartridge/agent from prior version to 5.6.16, agent stops collecting data due to existing credentials not properly imported into a Lockbox.
Below errors are logged in the agent log:
2015-12-18 09:41:09.605 ECHO <fb8be857-fbcf-4747-973d-295a8570e581/VMwarePerformance/5.6.16/VMwarePerformance/vcenter3> ERROR [FglAM:IncomingMessage-28] com.quest.vmware.api.util.CredentialManager - No matching credential for current VC.
2015-12-18 09:41:09.605 ECHO <fb8be857-fbcf-4747-973d-95a8570e581/VMwarePerformance/5.6.16/VMwarePerformance/vcenter3> ERROR [FglAM:IncomingMessage-28] com.quest.agent.esx.ESXAgent - Cannot find a valid credential from lockbox
Product Defect VFOG-12076 has been submitted to Development for a fix in a future release.
Please check the release notes of latest version of VMware cartridge to determine which bug fixes have been included in this release.
Manually verify that the credentials information is accurate and the Lockbox is released to the FglAM client hosting VMware agent by navigating to VMware Environment | Administration dashboard and then click on icon in Edit Properties column.
© 2022 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz