vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded
VMWARE-NSX-MIB ·
.1.3.6.1.4.1.6876.120.1.0.43.0.93
Object
notification
Service vmwNsxTDataCenterNappServiceName is degraded. The service may still be able to reach a quorum while
pods associated with vmwNsxTDataCenterNappServiceName are not all stable. Resources consumed by these
unstable pods may be released.
Action required:
In the NSX UI, navigate to System | NSX Application Platform | Core Services to check which service
is degraded. Invoke the NSX API GET /napp/api/v1/platform/monitor/feature/health to check which
specific service is degraded and the reason behind it. Invoke the following CLI command to restart
the degraded service if necessary:
`kubectl rollout restart <statefulset/deployment> <service_name> -n <namespace>`
Degraded services can function correctly but performance is sub-optimal.
Context
- MIB
- VMWARE-NSX-MIB
- OID
.1.3.6.1.4.1.6876.120.1.0.43.0.93- Type
- notification
- Status
- current
- Parent
- vmwNsxTNSXApplicationPlatformHealthFeature
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workNotifications are emitted by an agent; they cannot be read with snmpget or walked.
Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'VMWARE-NSX-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-NSX-MIB::vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'VMWARE-NSX-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-NSX-MIB::vmwNsxTNSXApplicationPlatformHealthServiceStatusDegraded'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of