vMotion is blocked due to error "Currently connected network interface ... uses network (nsxa down), which is not accessible"
search cancel

vMotion is blocked due to error "Currently connected network interface ... uses network (nsxa down), which is not accessible"

book

Article ID: 390851

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Destination host is prepared as Host Transport Node for NSX. 
  • vMotion of a VM is blocked with error:
    "Currently connected network interface" 'Network adapter X' uses network 'DVSwitch[50 3e ## ## ## ## ## ##-## ## ## ## ## ## 42 4e] NSX port group [dvportgroup-#####](nsxa down)', which is not accessible."

  • nsxa module on the vDS on the destination host is down. To confirm:
    • SSH to the host
    • Run command below:
      net-dvs -l | grep "switch)\|common.alias\|nsxa"

  • On the destination ESXi host, a python-zdump.000 file may be present in host's /var/core directory.
  • In nsx-syslog on the destination host, logging similar to sample below may be observed:
    /var/log/nsx-syslog.log:
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="INFO"] GetAllSoftwares execution time: 1.000000 seconds
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="WARNING"] Get software version failed for nsx-monitoring.
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="INFO"] Software nsx-monitoring version: expect=3.2.3.2.0-7.0.23214459 actual=
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="WARNING"] Get software version failed for nsx-vdpi.
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="INFO"] Software nsx-vdpi version: expect=3.2.3.2.0-7.0.23214459 actual=
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="WARNING"] Get software version failed for nsx-shared-libs.
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="INFO"] Software nsx-shared-libs version: expect=3.2.3.2.0-7.0.23214459 actual=
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z nsx-sfhc[2102721]: NSX 2102721 - [nsx@6876 comp="nsx-esx" subcomp="nsxsfhc" tid="2102751" level="WARNING"] Get software version failed for nsx-python-protobuf.
  • On NSX Manager, you may see nsxa being set down:
    /var/log/proton/nsxapi.log:
    <YYYY-MM-DD>T<hh:mm:ss.sss>Z  INFO L2HostConfigTaskExecutor1 TransportNodeAsyncServiceImpl 4270 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] TransportNode/f96b####-####-####-####-########1b6c setting forceNsxaDown true as fabric is down

Environment

VMware NSX

VMware NSX-T Data Center

Cause

Python process has crashed due to NSX SHA trying to collect multiple metrics through CLIs at the same time, which will cause the process to run out of memory.

Resolution

This is a known issue that may impact ESXi hosts prepared for NSX.

To workaround this issue, restart nsx-opsagent to start nsxa on the destination ESXi host:

  1. SSH to the ESXi host.
  2. restart nsx-opsagent service:
    /etc/init.d/nsx-opsagent restart
    Running this command will have no impact to the existing data paths and it will not interrupt host's or VM's functionality / networking.

Additional Information

Powered by Wolken Software