aggsvc-framework' could not be found on the host.VMware NSX-T Data Center
VMware NSX
This alarm is triggered when there is no packet reception for 10 seconds. However, if the reception thread is temporarily blocked, it may result in a false alarm.
This issue is resolved in NSX version 4.2.1
Log Snippet :
nsx-syslog:
2025-01-21T11:46:45.045Z <hostname> NSX 3943 MONITORING [nsx@6876 alarmId="xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx" alarmState="OPEN" comp="nsx-manager" entId="00000000-0000-0000-0000-000000000xxx" errorCode="MP701099" eventFeatureName="infrastructure_service" eventSev="CRITICAL" eventState="On" eventType="service_status_unknown" level="FATAL" nodeId="xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxx" subcomp="monitoring"] The service aggsvc-framework has been unresponsive for 10 seconds.
The fix in NSX version 4.2.1 changes the service name from aggsvc-framework to nsx-exporter, nsx-edge-exporter, or nsx-host-node-status-reporter, depending on the platform.
Command to check the status:
ESXi:/etc/init.d/nsx-exporter status
EDGE:/etc/init.d/nsx-edge-exporter status
UA:systemctl status nsx-host-node-status-reporter.service
There is no manual action required, upgrading to NSX version 4.2.1 or later will resolve the issue.