New VM creation or VM clone Failing due to NSXA down error on ESXi host.
search cancel

New VM creation or VM clone Failing due to NSXA down error on ESXi host.

book

Article ID: 409165

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Creation/Provisioning of a new VM or Cloning of a new VM will also fail with the following error.

  • "Currently connected network interface" 'Network adapter X' uses network 'DVSwitch[50 27 ## ## ## ## ## ##-## ## ## ## ## ## 9a be] NSX port group [dvportgroup-#####](nsxa down)', which is not accessible."



  • The NSXA status displays as down in Net-VDS, causing the VM port attachment failure.

  • VM creation then fails, and any attempt to attach the VM port to LS also fails.

  • The net-dvs command outputs of the host display the nsxa status as down.
    For example:      
        net-dvs -l | grep "nsxa"
          "component.nsxa = down"
  • Additionally, the ESXi hosts with NSXA down may appear with "Unknown" status in the NSX UI under System -> Fabric -> Hosts.

Environment

VMware NSX Data Center
VMware NSX

Resolution

  1. Restart ESXi host services: services.sh restart
  2. Wait a few seconds and rerun the check; nsxa should be up. and Provision/Cloning of New VM should succeed 
    For example:      
        net-dvs -l | grep "nsxa"
            "component.nsxa = up"

Additional Information

nsxa service being down might also cause vMotion issue as described in the KB
https://knowledge.broadcom.com/external/article/406081/nsxa-down-error-on-esxi-hosts-causing-vm.html