/etc/init.d/aggsvc-framework unresponsive alert in NSX
search cancel

/etc/init.d/aggsvc-framework unresponsive alert in NSX

book

Article ID: 391842

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Alarm Description :
    The service aggsvc-framework has been unresponsive for 10 second reported on the host.

    Alert Details :

    "Verify aggsvc-framework service is still running by invoking /etc/init.d/aggsvc-framework status. If the service is reported as running, it may need to be restarted using /etc/init.d/aggsvc-framework restart. Rerun the status command to verify the service is now running. If the script /etc/init.d/aggsvc-framework is unavailable, invoke systemctl status aggsvc-framework and restart by systemctl restart aggsvc-framework with root privileges."

  • The service named 'aggsvc-framework' could not be found on the host.

Environment

VMware NSX-T Data Center
VMware NSX

Cause

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.

Resolution

This issue is resolved in NSX version 4.2.1

Additional Information

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.