VxRail: Erro ao configurar a VLAN para validação: Falha ao criar rede para testar
Summary: Erro ao configurar a VLAN para validação: "Falha ao criar rede para testar" durante o procedimento de adição de nó.
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
Um erro é visto ao configurar a VLAN para validação e adicionar nós a um cluster do VxRail. "Falha ao criar rede para teste"
Três novos nós do PowerEdge deveriam ser adicionados a um cluster de cinco nós com quatro nós Quanta e um PowerEdge.
VxRail Hosts
Validate
Validation Errors
Error while setting up the VLAN for validation
Failed creating network to test.
Disk group validation
Failed to get disk information from hosts: {0}.
Marvin.log
[MARVIN] 2021-09-08T23:31:05.979+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.component.tasklet.validation.ExpansionVlanLiveValidationTasklet ExpansionVlanLiveValidationTasklet.useVmotionTcpIpStack:300 - Unable to get entity of host.
com.vce.commons.core.exception.ConnectionException: com.sun.xml.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: The object 'vim.HostSystem:host-24483' has already been deleted or has not been completely created Please see the server log to find more detail regarding exact cause of the failure.
[MARVIN] 2021-09-08T23:31:06.047+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.services.network.SimpleHostNetworkConfig SimpleHostNetworkConfig.removePortgroup:291 - Failed removing portgroup vMotion on host
com.vmware.vim25.NotFoundFaultMsg: The object or item referred to could not be found.
[MARVIN] 2021-09-08T23:30:22.666+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.component.tasklet.ConfigurationTasklet ConfigurationTasklet$1.onError:89 - Attempt 2/1 failed
[MARVIN] 2021-09-08T23:31:05.979+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.component.tasklet.validation.ExpansionVlanLiveValidationTasklet ExpansionVlanLiveValidationTasklet.useVmotionTcpIpStack:300 - Unable to get entity of host.
[MARVIN] 2021-09-08T23:31:05.989+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.component.tasklet.validation.ExpansionVlanLiveValidationTasklet ExpansionVlanLiveValidationTasklet.lambda$runTests$0:224 - Failed creating networks to test vlan connectivity.
[MARVIN] 2021-09-08T23:31:06.047+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.services.network.SimpleHostNetworkConfig SimpleHostNetworkConfig.removePortgroup:291 - Failed removing portgroup vMotion on host
[MARVIN] 2021-09-08T23:31:56.841+0000 ERROR [SimpleAsyncTaskExecutor-1] com.emc.mystic.manager.commons.component.tasklet.validation.MatchingDiskTypeConfigurationValidationTasklet MatchingDiskTypeConfigurationValidationTasklet.validate:121 - Failed to get disks from any hosts in the cluster
ServerName:/home/mystic # tail -f /var/log/vmware/marvin/tomcat/logs/marvin.log | grep ERROR
[MARVIN] 2021-09-09T02:53:38.151+0000 ERROR [SimpleAsyncTaskExecutor-4] com.emc.mystic.manager.commons.c omponent.tasklet.ConfigurationTasklet ConfigurationTasklet$1.onError:89 - Attempt 2/1 failed
ServerName:/home/mystic # tail -f /var/log/mystic/web.log | grep ERROR
2021-09-09T02:56:48.462+0000 ERROR [SimpleAsyncTaskExecutor-5] org.springframework.batch.core.step.Abstr actStep AbstractStep.execute:237 - Encountered an error executing step customizedHostnameValidationStep in job expansionValidationJob
2021-09-09T02:56:51.213+0000 ERROR [myScheduler-10] com.vce.commons.core.connection.services.ConnectionF actoryImpl ConnectionFactoryImpl.createSSLHostConnectionWithInitialAccount:155 - Fail to connect to host : fe80::250:5xff:xxxx:xxx%eth1 with user: root
2021-09-09T02:57:02.751+0000 ERROR [myScheduler-10] com.vce.commons.core.connection.services.ConnectionF actoryImpl ConnectionFactoryImpl.createSSLHostConnectionWithInitialAccount:155 - Fail to connect to host : fe80::250:5xff:xxxx:xxx%eth1 with user: root

marvin.log:
[MARVIN] 2021-09-09T03:45:21.302+0000 INFO [SimpleAsyncTaskExecutor-6] com.emc.mystic.manager.commons.component.listener.ConfigurationActionStepExecutionListener MarvinConfigurationLog.beginTask:12 - [Task 6f02cb4d-e5ec-4f93-83e4-b291ac75e36a] START: Running action config.action.expansion.validation.host.name, stage validation_host [MARVIN] 2021-09-09T03:45:21.302+0000 INFO [SimpleAsyncTaskExecutor-6] com.emc.mystic.manager.commons.component.listener.ConfigurationActionStepExecutionListener MarvinConfigurationLog.updateTask:17 - [Task 6f02cb4d-e5ec-4f93-83e4-b291ac75e36a] UPDATE: This action will be tried 1 times [MARVIN] 2021-09-09T03:45:21.309+0000 INFO [SimpleAsyncTaskExecutor-6] com.emc.mystic.manager.commons.component.tasklet.validation.CustomizedHostnameValidationTasklet CustomizedHostnameValidationTasklet.getReplaceHostHostnames:110 - Found reserved hostname for node replacement : [] ! [MARVIN] 2021-09-09T03:45:21.313+0000 INFO [SimpleAsyncTaskExecutor-6] com.emc.mystic.manager.commons.component.tasklet.validation.HostnameValidationTasklet HostnameValidationTasklet.validateVcPscHostnamesForExternalVc:386 - Validating VC server: vCenterName.company.com for joining external VC. [MARVIN] 2021-09-09T03:45:21.313+0000 INFO [SimpleAsyncTaskExecutor-6] com.emc.mystic.manager.commons.component.tasklet.validation.HostnameValidationTasklet HostnameValidationTasklet.validateVcPscHostnamesForExternalVc:409 - Validating PSC server hostname: null for joining external VC in non-embedded mode - [MARVIN] 2021-09-09T03:45:21.313+0000 ERROR [SimpleAsyncTaskExecutor-6] com.emc.mystic.manager.commons.component.tasklet.ConfigurationTasklet ConfigurationTasklet$1.onError:89 - Attempt 2/1 failed
Cause
Estas são algumas das causas desse problema:
- Nomes DNS para PSC e vCenter no banco de dados Mystic em vez de endereços IP.
- Os config.json e config-journal.json mostram o nome do PSC quando o sistema está no vSphere 6.7 e tem um PSC incorporado no vCenter.
- O config.json e o config-journal.json mostram nonEmbeddedMode como false.
Resolution
Existe uma solução para esse problema, mas é necessária a intervenção da equipe de suporte técnico da Dell. É necessário modificar o banco de dados Mystic do VxRail Manager.
Entre em contato com o Centro de suporte ao cliente da Dell ou com seu representante de serviço para obter suporte técnico e mencione o ID dessa solução.
Entre em contato com o Centro de suporte ao cliente da Dell ou com seu representante de serviço para obter suporte técnico e mencione o ID dessa solução.
Affected Products
VxRail Appliance Family, VxRail Appliance SeriesArticle Properties
Article Number: 000191387
Article Type: Solution
Last Modified: 08 Sept 2025
Version: 8
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.