In this example a GMU Migration - migrateOut attempt resulted in the below error:
===============================================================
[restmanscg@gateway1 ~]$ ./GatewayMigrationUtility.sh migrateOut --folderName grp_SCGSI/grp_PacerMob/shr_PacerMob/ratelimits --dest ./scg_migrations/output/SCGSI_PACER_RATELIMIT_DEVX.xml --argFile ./argfiles/scgdevx.args
Warning: TLS hostname verification has been disabled
Warning: TLS server certificate check has been disabled
Running.....................................
Execution failed. Reason: Internal Server Error. Detail: naming exception. Could not establish context on any of the ldap urls.
===============================================================
Release : 10.x
Component : Gateway Migration Utility migrateOut command
The LDAP Identity Provider Configuration on the Destination Gateway is incorrectly configured causing any GMU related LDAP dependency to fail the migration
This issue can be resolved by bringing up the Policy Manager on the Destination Server and identifying incorrect configurations with the LDAP Identity Provider being referenced in your GMU Migration as a dependency.
Use the LDAP Identity Provider Wizard to verify and test the LDAP Configurations as successful and then retry the Gateway Migration Utility attempt for better results.
Gateway Migration Utility Documentation:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/10-0/gateway-migration.html
Gateway LDAP Identity Provider Wizard:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/10-0/security-configuration-in-policy-manager/identity-providers/ldap-identity-providers/ldap-identity-provider-wizard.html
Troubleshooting Migrations:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/layer7-api-management/api-gateway/10-0/gateway-migration/troubleshoot-migrations.html