LB Status is degraded after Pool Status was down.

Products

• VMware NSX

Issue/Introduction

• An alarm "lb_status_degraded" is opened. LB Status is degraded in nsxapi.log (3.2) or policy.log (3.1).
  <TIMESTAMP>  WARN pool-254-thread-1 EventReportSyslogSender 4237 MONITORING [nsx@6876 comp="nsx-manager" entId="<LB_ID>" eventFeatureName="load_balancer" eventSev="warning" eventState="On" eventType="lb_status_degraded" level="WARNING" subcomp="manager"] The load balancer service <LB_ID> is degraded.
• Pool Status was degraded before LB Status is degraded in nsxapi.log (3.2) or policy.log (3.1).
  <TIMESTAMP>  INFO policyProviderTaskScheduler-10 ConsolidatedRealizedStateServiceImpl 4237 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated consolidated state for intentPath:/infra/lb-pools/<POOL_ID> to:DEGRAGED
• LB Status is recovered from Degraded state after Pool Status in nsxapi.log (3.2) or policy.log (3.1).
  LB Status is update in periodic, 5 minutes cycle.
  <TIMESTAMP>  WARN pool-254-thread-1 EventReportSyslogSender 4237 MONITORING [nsx@6876 comp="nsx-manager" entId="<LB_ID>" eventFeatureName="load_balancer" eventSev="warning" eventState="Off" eventType="lb_status_degraded" level="WARNING" subcomp="manager"] The load balancer service <LB_ID> is not degraded.

Environment

NSX-T Data Center 3.2.x, 3.1.x

Cause

NSX Manager unexpectedly calculates LB Status from Pool Status.

It is expected that LB Status does not reflect Pool Status.

Resolution

Fixed in NSX 4.1.1.

If Pool Status is Up, LB Status should become Up in 5 minutes unless there is other reasons.