After host upgrade from NSX 4.1.0.2 to 4.1.2.3, nsx-cfgAgent crashes.

Products

• VMware NSX-T Data Center
• VMware NSX

Issue/Introduction

Post NSX 4.1.2.3 upgrade, nsx-cfgagent may experience crash.

The following log entries can be seen on the ESXi host:

Log location : /var/run/log/nsx-syslog.log

alarmState="OPEN" comp="nsx-manager" entId="09####0e-2##7-4##c-b##6-48########29" errorCode="MP701099" eventFeatureName="infrastructure_service" eventSev="CRITICAL" eventState="On" eventType="application_crashed" level="FATAL" nodeId="09####0e-2##7-4##c-b##6-48########29" subcomp="monitoring"] Application on NSX node ##-###-####-##### has crashed. The number of core files found is 1. Collect the Support Bundle including core dump files and contact VMware Support team.

alarmState="OPEN" comp="nsx-manager" entId="09####0e-2##7-4##c-b##6-48########29" eventFeatureName="cni_health" eventSev="MEDIUM" eventState="On" eventType="hyperbus_manager_connection_down" level="WARNING" nodeId="#####-###-###-###-#####" subcomp="monitoring"] Hyperbus cannot communicate with the Manager node.

Environment

VMware NSX 4.1.2.3

Cause

This issue happens in a situation where nsx-cfgagent.xml file is changed prior to the upgrade to NSX 4.1.2.3.

The change in this file will cause nsx-cfgagent crash after the upgrade.

 

Resolution

Restore original nsx-cfgagent.xml file.
The file can be accessed at the following path: /etc/vmware/nsx

Additional Information

Avoid manual changes to nsx-cfgagent.xml file.