fluidFSEventHealthAdCriticalClockSkew

FLUIDFS-CLUSTER-MIB · .1.3.6.1.4.1.674.11000.2000.200.20.9.146
Commands MIB view Table view

Object

notification 
AD (used by {{TenantName}}) and NAS controller {{nodeId}} clocks aren't synchronized   Description:  Clock of NAS controller {{nodeId}} and AD clock, used by {{TenantName}} (domain {{DomainControllerName}}), are not synchronized (skew of {{adClockSkew}} seconds exceeds critical threshold of {{maxAdClockSkew}} seconds). Kerberos authentication may fail. Fix system clock/Fix AD clock. Enter the time configuration screen and get the configured NTP host. If no NTP is configured, it is recommended to configure one by either using the organization's NTP or the same IP/name used for joining the NAS to the AD.

Context

MIB
FLUIDFS-CLUSTER-MIB
OID
.1.3.6.1.4.1.674.11000.2000.200.20.9.146
Type
notification
Status
current
Parent
fluidFSEventsHealth

Net-SNMP examples

How SNMP and these commands work

Notifications are emitted by an agent; they cannot be read with snmpget or walked.

Inspect the notification definition
/usr/bin/snmptranslate -Pud -Ir -Td -m 'FLUIDFS-CLUSTER-MIB' -M '/opt/observium/mibs/dell:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FLUIDFS-CLUSTER-MIB::fluidFSEventHealthAdCriticalClockSkew'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'FLUIDFS-CLUSTER-MIB' -M '/opt/observium/mibs/dell:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FLUIDFS-CLUSTER-MIB::fluidFSEventHealthAdCriticalClockSkew'

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.