Edge service status changed alarm

Products

• VMware NSX

Issue/Introduction

Title: Edge service status changed
Event ID: infrastructure_service.edge_service_status_changed

Alarm Description:

• Purpose: To inform users that a service has changed state from 'STARTED' to 'STOPPED' and is down.
• Impact: This alarm can indicate a service outage. Please check syslog for 'The service <service name> changed from STARTED to STOPPED' for any reported errors.

Environment

• VMware NSX-T Datacenter
• VMware NSX

Resolution

Steps to Resolve
For 3.0.0 and higher

Recommendation Action:

• On the Edge node, verify the service hasn’t exited due to an error by looking for core files using the NSX CLI command `get core-dumps`. In addition, invoke the NSX CLI command `get services` to confirm whether the service is stopped. If so, invoke `start service <service-name>` to restart the service.
  • If NamespaceD is not running and you expect a configuration change on Edge, please put Edge in maintenance-mode and exit out maintenance-mode by selecting the node in NSX Manager UI and click Actions → NSX Maintenance Mode.
  • If DNS is not running, check DNS service by running NSX CLI  'get dns-forwarders status'
  • If VMotion of the Edge is in progress, this alarm for igmpc-underlay service will be created. Once VMotion is complete, this alarm for igmpc-underlay service will be resolved.
  • For load balancer (LB) and DNS service alarms, the alarm can be resolved/acknowledged from the UI when the LB/DNS service is disabled or deleted.

Maintenance window required for remediation? 

• Might be required if NSD is not running, please check Recommendation Action.