VCF Domain bringup with vVol iSCSI fails with error "A specified parameter was not correct: Vim.Host.VirtualNic.Specification.Ip"
search cancel

VCF Domain bringup with vVol iSCSI fails with error "A specified parameter was not correct: Vim.Host.VirtualNic.Specification.Ip"

book

Article ID: 400207

calendar_today

Updated On:

Products

VMware SDDC Manager

Issue/Introduction

  • Performing a domain bringup on VCF using vVol-iSCSI fails with "A specified parameter was not correct: Vim.Host.VirtualNic.Specification.Ip"

  • Issue is seen if the iSCSI vmkernel portgroup and VASA provider network requires Layer-3 routed network
  • /var/log/vmware/vcf/domainmanager/domainmanager.log: (SDDC Manager)

YYYY-MM-DDTHH:MM:SS INFO  [vcf_dm,<>,deab] [c.v.e.s.c.c.v.vsphere.VcManagerBase,dm-exec-17]  VmkNic IP Conf: address: <vmkernel IP> , mask: <subnet mask> , dhcp: false, pgName: <Portgroup Name>
YYYY-MM-DDTHH:MM:SS ERROR [vcf_dm,<>,deab] [c.v.e.s.o.model.error.ErrorFactory,dm-exec-17]  [DBV63I] VSPHERE_HOST_CREATE_VMKNIC_FAILED Could not create vmknic with ip <vmkernel IP> on the host <ESXi FQDN>
com.vmware.evo.sddc.orchestrator.exceptions.OrchTaskException: Could not create vmknic with ip <vmkernel IP> on the host <ESXi FQDN>
        at com.vmware.vcf.common.fsm.plugins.action.impl.HostNetworkConnectivityValidator.createVmkNic(HostNetworkConnectivityValidator.java:191)
        at com.vmware.vcf.common.fsm.plugins.action.impl.ValidateHostToVasaStorageDataPathConnectivityAction.execute(ValidateHostToVasaStorageDataPathConnectivityAction.java:99)
                at com.google.common.eventbus.Subscriber.lambda$dispatchEvent$0(Subscriber.java:71)
        at com.vmware.vcf.common.tracing.TraceRunnable.run(TraceRunnable.java:59)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)
Caused by: com.vmware.vim.binding.vmodl.fault.InvalidArgument: A specified parameter was not correct: Vim.Host.VirtualNic.Specification.Ip

  • /var/log/hostd.log: (ESXi host)

YYYY-MM-DDTHH:MM:SS In(166) Hostd[PID]: [Originator@6876 sub=Vimsvc.TaskManager opID=<> sid=<>user=<vcf user>] Task Completed : haTask-ha-host-vim.host.NetworkSystem.addVirtualNic-<ID>Status error
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: [Originator@6876 sub=Solo.Vmomi opID=<> sid=<> user=<vcf user>] Arg portgroup:
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: --> "<Portgroup Name>"
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: [Originator@6876 sub=Solo.Vmomi opID=<> sid=<> user=<vcf user>] Arg nic:
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: --> (vim.host.VirtualNic.Specification) {
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->    ip = (vim.host.IpConfig) {
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->       dhcp = false,
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->       ipAddress = "<vmkernel IP>",
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->       subnetMask = "<subnet mask>",
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->    },
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->    portgroup = "<vmkernel IP>",
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->    mtu = <MTU>,
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: -->    netStackInstanceKey = "defaultTcpipStack",
YYYY-MM-DDTHH:MM:SS Db(167) Hostd[PID]: --> }
YYYY-MM-DDTHH:MM:SS In(166) Hostd[PID]: [Originator@6876 sub=Solo.Vmomi opID=<> sid=<> user=<vcf user>] Throw vmodl.fault.InvalidArgument
YYYY-MM-DDTHH:MM:SS In(166) Hostd[PID]: [Originator@6876 sub=Solo.Vmomi opID=<> sid=<> user=<vcf user>] Result:
YYYY-MM-DDTHH:MM:SS In(166) Hostd[PID]: --> (vmodl.fault.InvalidArgument) {
YYYY-MM-DDTHH:MM:SS In(166) Hostd[PID]: -->    invalidProperty = "Vim.Host.VirtualNic.Specification.Ip",
YYYY-MM-DDTHH:MM:SS In(166) Hostd[PID]: -->    msg = "",

Cause

This is a limitation where vVol-iSCSI in Layer-3 segregated network configuration is not supported for VCF automation/bringup.

Resolution

Broadcom is working towards a permanent fix for this issue.

Please refer to the workaround below

  • Option A: 

Configure the iSCSI network in Layer-2 segment with VASA Provider Controller network

  • Option B:

Proceed to configure the Workload Domain with NFS/vSAN/Fibre Channel based storage during bringup. Refer to Managing Storage in VMware Cloud Foundation

Additional Information

Powered by Wolken Software