LCMVIDM71043 error during VMware Identity Manager deployment due to missing F5 LTM auto-map configuration
Article ID: 453222
Updated On:
Products
Issue/Introduction
Deployment of VMware Identity Manager from VMware Aria Suite Lifecycle fails during cluster deployment or scale-out operations where an F5 Local Traffic Manager (LTM) is utilized as the load balancer.
When the failure occurs, the following error is observed in the VMware Aria Suite Lifecycle logs or UI:
Error Code: LCMVIDM71043
Unable to update vIDM FQDN. Ensure the vIDM is able to resolve to the new host and retry.
Environment
VMware Identity Manager 3.3.7
VMware Aria Suite Lifecycle
F5 Local Traffic Manager (LTM)
Cause
The failure can simply be caused by a missing auto-map configuration within the F5 LTM pool or virtual server.
The F5 LTM architecture requires the auto-map configuration for proper Source Network Address Translation (SNAT).
Without this setting enabled, SNAT is not correctly applied to traffic returning from the server pool through the load balancer to the deployment manager.
Consequently, the VMware Identity Manager appliance is unable to resolve or update its FQDN during the deployment process.
Resolution
Review the requirements from the F5 configuration guide for Identity Manager, specifically page 14.
To resolve this issue and allow the deployment to complete, you must enable the auto-map setting on your F5 LTM load balancer by performing the following steps:
Log in to your F5 LTM interface.
Navigate to the virtual server or pool associated with the VMware Identity Manager environment.
Locate the SNAT configuration settings.
Enable the Auto-map option.
Save and apply the configuration changes.
Return to VMware Aria Suite Lifecycle and retry the deployment operation.
Additional Information
For more detailed information regarding F5 SNAT and the auto-map configuration requirement, please refer to the official F5 documentation: https://my.f5.com/manage/s/article/K7820
There may be additional reasons to observe Error Code: LCMVIDM71043, see KB 386210 for more details.
Feedback
