vmwNsxTLoadBalancerLBStatusDegraded

VMWARE-NSX-MIB · .1.3.6.1.4.1.6876.120.1.0.17.0.15

Object

notification
The load balancer service vmwNsxTDataCenterEntityId is degraded.
          
Action required:
For centralized load balancer:
Check the load balancer status on standby Edge node as the degraded status
means the load balancer status on standby Edge node is not ready. On standby
Edge node, invoke the NSX CLI command `get load-balancer <lb-uuid> status`.
If the LB-State of load balancer service is not_ready or there is no output,
make the Edge node enter maintenance mode, then exit maintenance mode.
For distributed load balancer:
1. Get detailed status by invoking NSX API GET
   /policy/api/v1/infra/lb-services/<LBService>/detailed-status?source=realtime
2. From API output, find ESXi host reporting a non-zero instance_number
   with status NOT_READY or CONFLICT.
3. On ESXi host node, invoke the NSX CLI command `get load-balancer
   <lb-uuid> status`.
   If 'Conflict LSP'is reported, check whether this LSP is attached
   to other load balancer service. Check whether this conflict is
   acceptable.
   If 'Not Ready LSP' is reported, check the status of this LSP by
   invoking NSX CLI command `get logical-switch-port status`.
NOTE: You should ignore the alarm if it can be resolved automatically in 5 mins
      because the degraded status can be a transient status.

Context

MIB
VMWARE-NSX-MIB
OID
.1.3.6.1.4.1.6876.120.1.0.17.0.15
Type
notification
Status
current
Parent
vmwNsxTLoadBalancerFeature
Siblings
17

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.

Related Objects

Sibling Objects
Notification Objects