vmwNsxTManagerHealthMissingDNSEntryForVipFQDN
VMWARE-NSX-MIB ·
.1.3.6.1.4.1.6876.120.1.0.1.0.33
Object
notification
In case of dual stack or CA-signed API certificate for a NSX Manager,
virtual IPv4 address vmwNsxTDataCenterIPv4Address and virtual IPv6 address vmwNsxTDataCenterIPv6Address for
Manager node vmwNsxTDataCenterEntityId should resolve to the same FQDN.
Action required:
Examine the DNS entry for the VIP addresses to see if they resolve to the same FQDN.
Context
- MIB
- VMWARE-NSX-MIB
- OID
.1.3.6.1.4.1.6876.120.1.0.1.0.33- Type
- notification
- Status
- current
- Parent
- vmwNsxTManagerHealthFeature
- 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::vmwNsxTManagerHealthMissingDNSEntryForVipFQDN'
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::vmwNsxTManagerHealthMissingDNSEntryForVipFQDN'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of