Purpose: To inform users a tier0 service group has state changed on edge. It may not mean service group itself has issue. Please check events from syslog around the time of failover.
Impact: Failover could be triggered by various factors, including peer state. If state change is expected, traffic should be picked up by the active service group.
Resolution
Steps to resolve For 4.0.1 and above
Recommendation Action:
As admin user, on the edge node, invoke the NSX CLI command `get logical-router <service_router_id> service_group` to check all service-groups configured under a given service-router.
Review the result to identify a reason for a service-group leaving active state.