VxRail: La actualización falla con el error "No se pudo realizar la subtarea: EnableVCVMSSHSubTask" o "No se pudo realizar la subtarea: UnlockCDROMSubTask"

Summary: Dell VxRail: La actualización a 7.0.350 o superior puede fallar en EnableVCVMSSHSubTask o UnlockCDROMSubTask cuando se intenta actualizar el dispositivo vCenter Server interno de VxRail. ...

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 actualización de VxRail a 7.0.350 o superior puede fallar en EnableVCVMSSHSubTask o UnlockCDROMSubTask cuando se intenta actualizar el vCenter Server Appliance interno de VxRail.
Captura de pantalla del error de actualización en el plug-in 

short.term.log

2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[31m [ERROR] <68>[0m vsphere_connector_guestopt_impl.go ExecuteCommandOnVM() (131): Put ""https://169.254.x.x:443/guestFile?id=27&token=52dc49af-ed53-51d1-0898-6c21e791a33327"": dial tcp 169.254.x.x:443: i/o timeout"
2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[36m [INFO] <68>[0m vm_repository_connector_impl.go ToggleSSH() (358): rc: -1"
2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[36m [INFO] <68>[0m vm_repository_connector_impl.go ToggleSSH() (359): Stdout: "
2022-02-27-09:26:28 microservice.cmsvcupgrade-service ""
2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[36m [INFO] <68>[0m vm_repository_connector_impl.go ToggleSSH() (360): Stderr: "
2022-02-27-09:26:28 microservice.cmsvcupgrade-service ""
2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[31m [ERROR] <68>[0m vm.go ToggleSSH() (364): Put ""https://169.254.x.x:443/guestFile?id=27&token=52dc49af-ed53-51d1-0898-6c21e791a33327"": dial tcp 169.254.x.x:443: i/o timeout"
2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[31m [ERROR] <68>[0m enable_vc_vm_ssh_subtask.go PerformSubTask() (80): Put ""https://169.254.x.x:443/guestFile?id=27&token=52dc49af-ed53-51d1-0898-6c21e791a33327"": dial tcp 169.254.x.x:443: i/o timeout"
2022-02-27-09:26:28 microservice.cmsvcupgrade-service "2022-02-27 09:26:28[31m [ERROR] <68>[0m upgrade_flow.go PerformSubTasks() (215): Fail to run sub task: [EnableVCVMSSHSubTask], error: [Put ""https://169.254.x.x:443/guestFile?id=27&token=52dc49af-ed53-51d1-0898-6c21e791a33327"": dial tcp 169.254.x.x:443: i/o timeout]"


O bien,

"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.657905947Z stderr F 2022-07-29 07:45:16[31m [ERROR] <75>[0m vsphere_connector_guestopt_impl.go ExecuteCommandOnVM() (131): Put ""https://169.254.x.x:443/guestFile?id=15&token=524a1709-f64a-bfae-2b76-7f8a144f09a015"": dial tcp 69.254.xxx:443: connect: connection refused"
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.75273638Z stderr F 2022-07-29 07:45:16[36m [INFO] <75>[0m vm_repository_connector_impl.go ToggleSSH() (358): rc: -1"
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752786866Z stderr F 2022-07-29 07:45:16[36m [INFO] <75>[0m vm_repository_connector_impl.go ToggleSSH() (359): Stdout: "
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752790794Z stderr F "
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752795238Z stderr F 2022-07-29 07:45:16[36m [INFO] <75>[0m vm_repository_connector_impl.go ToggleSSH() (360): Stderr: "
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752798003Z stderr F "
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752839333Z stderr F 2022-07-29 07:45:16[31m [ERROR] <75>[0m vm.go ToggleSSH() (364): Put ""https://169.254.x.x:443/guestFile?id=15&token=524a1709-f64a-bfae-2b76-7f8a144f09a015"": dial tcp 169.254.69.254.xxx:443: connect: connection refused"
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752890818Z stderr F 2022-07-29 07:45:16[31m [ERROR] <75>[0m enable_vc_vm_ssh_subtask.go PerformSubTask() (80): Put ""https://69.254.xxx:443/guestFile?id=15&token=524a1709-f64a-bfae-2b76-7f8a144f09a015"": dial tcp 169.254.57.111:443: connect: connection refused"
"2022-07-29 07:45:17,242" microservice.cmsvcupgrade-service "2022-07-29T07:45:16.752937517Z stderr F 2022-07-29 07:45:16[31m [ERROR] <75>[0m upgrade_flow.go PerformSubTasks() (215): Fail to run sub task: [EnableVCVMSSHSubTask], error: [Put ""https://69.254.xxx:443/guestFile?id=15&token=524a1709-f64a-bfae-2b76-7f8a144f09a015"": dial tcp 169.254.xxx:443: connect: connection refused]"

Cause

Los hosts ESXi tienen una dirección IPv4 configurada en vmk0 y no se puede acceder a la dirección desde VxRail Manager, como 169.254.x.x
.Por lo general, estos hosts se actualizaron desde 4.5 en algún momento de su vida útil. En VxRail 4.7.x, la administración de IPv4 se transfirió a vmk2. Como resultado, es posible que vmk0 tenga una configuración sobrante que aún etiquete vmk0 como dirección de administración de IPv4, lo que, como resultado, establecerá una dirección 169.254.x.x en vmk0

Resolution

  1. Deshabilite IPv4 para vmk0 en todos los hosts ESXi; vmk0 solo debe tener la dirección IPv6.
  2. Reintentar la actualización

Affected Products

VxRail, VxRail Appliance Series, VxRail Software
Article Properties
Article Number: 000201456
Article Type: Solution
Last Modified: 11 Nov 2025
Version:  7
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.