Search the VMware Knowledge Base (KB)
View by Article ID

Installing vSphere Storage Appliance fails with the error: Failed to complete network configuration for specified host: 'hostname' (2037665)

  • 3 Ratings


  • Cannot install vSphere Storage Appliance (VSA)
  • Installing VSA fails
  • You see the error:

    Cannot create VSA Cluster: Failed to complete network configuration for specified host: 'hostname', hence reverted all other hosts. Could not find 2 NICs on the system
    Cluster creation rollback will undo any tasks that were completed. This may take a couple of minutes to complete.
  • The VSA logs report entries similar to:
    11:09:11,606 51 [PNICSelectorImpl] [pool-135-thread-1] INFO  - Getting NICs to use for switch vSwitch0
    11:09:11,606 561 [SessionService] [pool-135-thread-1] ERROR - Failed to configure network on host: host-xx
    java.lang.IllegalStateException: Could not find 2 NICs on the system.
            at com.vmware.sva.manager.config.NetworkConfigurator.getAvailableNics(
            at com.vmware.sva.manager.config.NetworkConfigurator.getAvailablePrimaryAndSecondaryNics(
            at com.vmware.sva.manager.config.NetworkConfigurator.configureSwitch(
            at com.vmware.sva.manager.config.NetworkConfigurator.configure(
            at com.vmware.sva.manager.config.NetworkConfigurator.configureHostNetwork(
            at com.vmware.sva.manager.service.SessionService.configureNetwork(
            at com.vmware.sva.manager.jobservices.tasks.TaskNetworkConfig.execute(
            at com.vmware.sva.manager.jobservices.impl.DefaultTaskRunner.handleTaskStart(
            at com.vmware.sva.manager.jobservices.impl.SyncTaskGroup.execute(
            at java.util.concurrent.Executors$
            at java.util.concurrent.FutureTask$Sync.innerRun(
            at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(
            at java.util.concurrent.ThreadPoolExecutor$
    11:09:11,616 89 [DefaultTaskRunner] [pool-135-thread-1] INFO  - Notifying listeners of task exception. TaskID:NetworkConfig
    2012-10-10 11:09:11,616 80 [DefaultJobRunner] [pool-135-thread-1] ERROR - Exception caught. Starting rollback for job if rollback support . JobName:ClusterCreation-datacenter-21
    java.lang.IllegalStateException: Failed to complete network configuration for specified host:, hence reverted all other hosts.  Could not find 2 NICs on the system.

  • The VSA cluster includes an ESXi 5.1 host which has one Quad port NIC


This issue occurs because the installer fails the NIC validation step if a host has a single quad-port NIC. VSA is designed to achieve increased availability and redundancy, and having a single quad-port NIC is inconsistent with the redundancy principle. If a quad-port NIC fails, the host becomes isolated, resulting in HA restarts for the virtual machines that are registered on that host.
The datastores go into a degraded state, leaving the cluster vulnerable to total outage in the event of an additional failure anywhere in the remaining networking infrastructure or the remaining host(s).

This issue may also occur when one or more NICs have negotiated a speed less than 1 Gb/s, and the remaining NICs do not fulfill VSA requirements.


To resolve this issue, configure the hosts with Brownfield networking that is available with VSA 5.1, instead of Greenfield (fresh ESXi install).

For more information on Brownfield network configurations, see the Considerations for Brownfield Installation section in the vSphere Storage Appliance Installation and Administration guide.

Note: If one or more NIC(s) have negotiated < 1 Gb speed or half duplex, ensure to correct the NIC connections before proceeding.
To deploy VSA with a Brownfield networking configuration in an existing vSphere cluster, ensure to use this exact network configuration:
  • vSwitch name: vSwitch0
    Network Adapters: vmnic0, vmnic2
    NIC Teaming policy: Originating Virtual Port ID
    NIC Teaming: vmnic0 active / vmnic2 active

    • Port group name: VM Network
      NIC Teaming: vmnic2 active / vmnic0 standby

    • Port group name: Management Network
      NIC Teaming: vmnic2 active / vmnic0 standby
      Configure a management vmkernel port

    • Port group name: VSA-Front End
      NIC Teaming: vmnic0 active / vmnic2 standby

  • vSwitch name: vSwitch1
    Network Adapters: vmnic1, vmnic3
    NIC Teaming policy: Originating Virtual Port ID
    NIC Teaming: vmnic1 active / vmnic3 active

For more information, see:
  • The vSwitch and Port Group names are case sensitive.
  • vMotion and Management portgroups should be configured as vmkernel port groups.
  • In similar configurations, VMware recommends that you maintain a tested and compatible spare hardware equipment at the host location, so that a hardware failure can be rectified as quickly as possible.

Additional Information

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)

Please enter the Captcha code before clicking Submit.
  • 3 Ratings