Configuration State "Failed" for NSX edge node after resetting edge user password(s)
search cancel

Configuration State "Failed" for NSX edge node after resetting edge user password(s)

book

Article ID: 410731

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Edge node password(s) have expired and followed process Resetting the Passwords of an Appliance to reset the password.
  • In the NSX UI, System - Fabric - Nodes, the Node Status of the edge node is Down or Configuration State is Failed and Node Status is Unknown, after the procedure above is carried out.
  • Checking the NSX manager /var/log/syslog error like the following are seen:

NSX 75711 MONITORING [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="monitoring"] getStub failure: client ac629057-####-####-####-edfa78f81170, application monitoring, java.util.concurrent.ExecutionException: java.util.concurrent.TimeoutException: Channel ClientChannel(vmware.nsx.monitoring.CollectorHostService, 8224493a-####-####-####-2b81b6b54a18) is closed before stream was opened due to Status(code=UNKNOWN, msg=Closed by remote service)

    • Where ac629057-####-####-####-edfa78f81170 is the NSX UUID for the edge node.
  • On the edge node, as admin user, running get services shows nsx-opsagent as stopped
  • As root user, running ./etc/init.d/nsx-opsagent-appliance status shows as inactive, since the password reset procedure was carried out.

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware NSX-T Data Center
VMware NSX 4.x
VMware NSX 9.x

Cause

The procedure in the guide Resetting the Passwords of an Appliance calls for the service nsx-edge-api-server to be stopped, this service in turn stops the service nsx-opsagent-appliance and it does not get started again when the service nsx-edge-api-server is started at the end of the procedure.

Resolution

This is a known issue impacting VMware NSX.

Workaround

Once the password(s) have been reset and the nsx-edge-api-server service has been started again, start the nsx-opsagent-appliance service, as root user, using the command:

/etc/init.d/nsx-opsagent-appliance start