VxRail: Habilitar vSphere Lifecycle Manager devuelve un error interno con vCenter externo

Summary: En este artículo, se explica cómo la habilitación de vSphere Lifecycle Manager (vLCM) para VxRail arroja un error interno inesperado. Esta situación ocurre cuando el puerto TCP 5480 está cerrado entre VxRail Manager y vCenter del cliente. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

La habilitación de vSphere Lifecycle Manager (vLCM) devuelve un "error interno inesperado" en la pestaña "Información de identificación de vCenter".

The server has experienced an unexpected internal error.

Ejemplo de error que muestra eror interno

 

El registro /var/log/mystic/lcm-web.log muestra lo siguiente:

2024-12-10T13:43:08.875Z <7a452bd0839bef47d2ea3cb8fa0714d1> lcm [ERROR] <148> ScriptServiceImpl.java runLocalScript() (501): Script command error (/etc/vmware-marvin/scripts/lcm/scripts/ext-vc-root-account-verify.sh): [/bin/sh, /usr/lib/vmware-marvin/marvind/temp/20900
91812276686886.tmp, <vc fqdn> **** ****]
2024-12-10T13:43:08.875Z <7a452bd0839bef47d2ea3cb8fa0714d1> lcm [WARN] <148> ScriptServiceImpl.java runLocalScript() (502): [/etc/vmware-marvin/scripts/lcm/scripts/ext-vc-root-account-verify.sh]: Non-zero return code: 2
2024-12-10T13:43:08.875Z <7a452bd0839bef47d2ea3cb8fa0714d1> lcm [INFO] <148> ScriptServiceImpl.java runLocalScript() (503): [/etc/vmware-marvin/scripts/lcm/scripts/ext-vc-root-account-verify.sh@localhost]: <stdout> 000
Unable to verify account!

2024-12-10T13:43:08.875Z <7a452bd0839bef47d2ea3cb8fa0714d1> lcm [WARN] <148> ScriptServiceImpl.java runLocalScript() (507): [/etc/vmware-marvin/scripts/lcm/scripts/ext-vc-root-account-verify.sh@localhost]: <stderr>   % Total    % Received % Xferd  Average Speed   Time
   Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
^M  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0^M  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
curl: (35) Recv failure: Connection reset by peer

2024-12-10T13:43:08.876Z <7a452bd0839bef47d2ea3cb8fa0714d1> lcm [ERROR] <148> RestErrorHandler.java handleExceptionInternal() (188): Handling exception for request ServletWebRequest: uri=/lcm/mystic/private/vlcm/credential;client=<ip>
java.lang.IllegalStateException: Unable to verify the external VC roo account due to internal server error!
        at com.vce.lcm.service.verifier.AccountCredentialVerifier.verifyExternalVCVMRootAccount(AccountCredentialVerifier.java:294)
        at com.vce.lcm.service.verifier.AccountCredentialVerifier.verifyVCSARootAccount(AccountCredentialVerifier.java:130)
        at com.emc.mystic.manager.upgrade.controller.VlcmControllerImpl.enablementRequestValidate(VlcmControllerImpl.java:445)
        at com.emc.mystic.manager.upgrade.controller.VlcmControllerImpl.verifyCredential(VlcmControllerImpl.java:307)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)

...

2024-12-10T13:43:08.877Z <7a452bd0839bef47d2ea3cb8fa0714d1> lcm [ERROR] <148> RestErrorHandler.java handleExceptionInternal() (189): Get REST error: error code=1, http status code=500, message=The server has experienced an unexpected internal error. Try again later.

Cause

En las configuraciones de vCenter externo administradas por el cliente, el script "/etc/vmware-marvin/scripts/lcm/scripts/ext-vc-root-account-verify.sh" se utiliza para validar el acceso raíz a vCenter.
En entornos bloqueados, el puerto TCP 5480 requerido se puede cerrar desde VxRail Manager hacia vCenter.

Para validar si el puerto se puede comunicar desde VxRail Manager (el código de retorno 200 es correcto):

vxrail_mgr:/home/mystic # curl -k -u 'root:<vc root password>' -H "Content-Type: application/json" -X GET https://<vc ip>:5480/rest/appliance/access/ssh -w %{http_code}
{"value":true}200
vxrail_mgr:/home/mystic #

Resolution

Para pasar el script de comprobación, trabaje con el equipo de redes o firewall para permitir la comunicación de VxRail Manager a vCenter en TCP 5480.

Affected Products

VxRail Appliance Series
Article Properties
Article Number: 000258975
Article Type: Solution
Last Modified: 02 Jan 2025
Version:  2
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.