VxRail : La mise à niveau échoue avec l’erreur « Échec de l’exécution de la sous-tâche : EnableVCVMSSHSubTask » ou « Échec de l’exécution de la sous-tâche : UnlockCDROMSubTask"
Summary: Dell VxRail : La mise à niveau vers la version 7.0.350 ou une version ultérieure peut échouer lors de la tentative de mise à niveau de VxRail Internal vCenter Server Appliance.
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.
Symptoms
La mise à niveau de VxRail vers la version 7.0.350 ou une version ultérieure peut échouer à EnableVCVMSSHSubTask ou UnlockCDROMSubTask lors de la tentative de mise à niveau de l’appliance vCenter Server interne à VxRail.
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]"
ou
"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
Les hôtes ESXi ont une adresse IPv4 configurée sur vmk0 et l’adresse n’est pas accessible à partir de VxRail Manager, comme 169.254.x.x.
Généralement, ces hôtes ont été mis à niveau à partir de la version 4.5 à un moment donné de leur durée de vie. Dans la version 4.7.x, la gestion IPv4 VxRail a été déplacée vers vmk2. Par conséquent, il est possible que vmk0 dispose d’un paramètre restant qui marque toujours vmk0 comme adresse de gestion IPv4, ce qui définit une adresse 169.254.x.x sur vmk0
Resolution
- Désactivez IPv4 pour vmk0 sur tous les hôtes ESXi. vmk0 doit uniquement avoir une adresse IPv6.
- Réessayer la mise à niveau
Affected Products
VxRail, VxRail Appliance Series, VxRail SoftwareArticle 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.