Post NSX 4.1.2.3 upgrade, nsx-cfgagent may experience crash
Following entries are found in log file
/var/run/log/nsx-syslog.log
alarmState="OPEN" comp="nsx-manager" entId="09461c0e-2687-48ec-bf76-4869a3ee2e29" errorCode="MP701099" eventFeatureName="infrastructure_service" eventSev="CRITICAL" eventState="On" eventType="application_crashed" level="FATAL" nodeId="09461c0e-2687-48ec-bf76-4869a3ee2e29" subcomp="monitoring"] Application on NSX node xx-xxx-xxxx-xxxxx 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="09461c0e-2687-48ec-bf76-4869a3ee2e29" eventFeatureName="cni_health" eventSev="MEDIUM" eventState="On" even
tType="hyperbus_manager_connection_down" level="WARNING" nodeId="xxxxx-xxx-xxx-xxx-xxxxxx" subcomp="monitoring"] Hyperbus cannot communicate with the Manager node.
NSX 4.1.2.3
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
Restore original nsx-cfgagent.xml
Workaround
Avoid manual changes to nsx-cfgagent.xml
file