VCF no Dell VxRail: Falha na adição do cluster vi-WLD com o erro "Perform dvs related validations"

Summary: O cluster de domínio de carga de trabalho do VCF on VxRail Add for VI-WLD apresentou falha com o erro "Perform dvs related validations. Vmnic incompatível passou na especificação hostxx.abc.xyz host" no vcf no vxrail 4.4.1.1 com VxRail 7.0.371. ...

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

Durante a adição de cluster do domínio de carga de trabalho para VI-WLD, um usuário pode ver o erro abaixo no painel Tasks do gerenciador do SDDC:

Description: Perform dvs related validations. Failed
Error: Incompatible vmnic passed in host hostxx.abc.com specification

 

mensagem de erro no SDDC Manager

 

Domainmanager.log:

2023-02-03T14:19:05.021+0000 INFO  [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-5]  In total 5 vmnics are in-use: ["vusb0","vmnic3","vmnic7","vmnic2","vmnic5"]
2023-02-03T14:19:05.021+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  In Use Pnics ["vusb0","vmnic3","vmnic7","vmnic2","vmnic5"]
2023-02-03T14:19:05.021+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic0
2023-02-03T14:19:05.021+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed null
2023-02-03T14:19:05.021+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic1
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed null
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic2
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed {"speedMb":25000,"duplex":true}
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic3
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed {"speedMb":25000,"duplex":true}
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic4
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed {"speedMb":25000,"duplex":true}
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic5
2023-02-03T14:19:05.022+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed {"speedMb":25000,"duplex":true}
2023-02-03T14:19:05.023+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic6
2023-02-03T14:19:05.023+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed null
2023-02-03T14:19:05.023+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vmnic7
2023-02-03T14:19:05.023+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed {"speedMb":25000,"duplex":true}
2023-02-03T14:19:05.023+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Translating for vusb0
2023-02-03T14:19:05.023+0000 DEBUG [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.v.v.p.service.NICServicePlugin,dm-exec-5]  Link speed {"speedMb":100,"duplex":true}
2023-02-03T14:19:05.036+0000 ERROR [vcf_dm,cf4d3c3d17f10a83,bd58] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-5]  [46IH24] VSPHERE_INCOMPATIBLE_VMNIC_SPEC_FAILED Incompatible vmnic vmnic6 passed in host vh01-abc.xyz specification

 

Cause

Um status de NIC inválido em um dos hosts do cluster adicionado causa esse erro.
Pode ser que a NIC física esteja inativa ou a velocidade do link da NIC não corresponda a outras NICs no host.

 

Resolution

Para resolver esse problema:

Identifique o host relatado e a NIC física a partir do arquivo de log do domainmanager.
Verifique o status da NIC física e a velocidade do link. Se a porta estiver inativa ou a velocidade do link não estiver correta, execute as etapas abaixo, uma a uma, até que o problema seja resolvido:

  1. Tente recolocar o cabo de rede.
  2. Valide a configuração da porta do switch.
  3. Troque o cabo de rede por outro em boas informações.
  4. Reinicialize o host e verifique o status da vmnic.

 

Depois que o status da NIC física estiver em boas configurações, então:

  1. Repetir cluster de domínio de carga de trabalho com falha Adicionar tarefa no gerenciador do SDDC.

 

Affected Products

VxRail
Article Properties
Article Number: 000209909
Article Type: Solution
Last Modified: 17 Jan 2024
Version:  3
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.