MANAGER and HTTP services are going down frequently causing cluster degraded alarms

Products

• VMware NSX

Issue/Introduction

MANAGER and HTTP services are going down frequently causing cluster degraded alarms.

Following logs are present -

var/log/syslog
NSX 3834 - [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="cbm"] raiseClusterDegradedAlarm: alarmKey=####-####-####-####-#### Member=####-####-####-####-#### of group=MANAGER is DOWN.

NSX 3834 - [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="cbm"] raiseClusterDegradedAlarm: alarmKey=####-####-####-####-#### Member=####-####-####-####-#### of group=HTTP is DOWN.

NSX 4702 MONITORING [nsx@6876 alarmId="####-####-####-####-####" alarmState="OPEN" comp="nsx-manager" entId="####-####-####-####-####" eventFeatureName="clustering" eventSev="MEDIUM" eventState="On" eventType="cluster_degraded" level="WARNING" nodeId="####-####-####-####-####" subcomp="monitoring"] Group member ####-####-####-####-#### of service HTTP is down.

/var/log/proton/nsxapi.log has large number of populateData logs in LdapSyncWorker

INFO LdapSyncWorker-4-1 LdapObjectProcessor 1199231 INVENTORY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] populateData(CN=####,OU=####,OU=####,OU=####,OU=####,DC=####,DC=####): dnModified: false

Environment

VMware NSX

Cause

Active Directory groups are close to maximum allowed, and some groups are very large.

Resolution

Increase form-factor of NSX manager or increase the memory of existing managers.

Additional Information

Please refer to VMware Configuration Maximums officially supported configuration limits.