fluidFSEventClientAccessClientClockSkew
FLUIDFS-CLUSTER-MIB ·
.1.3.6.1.4.1.674.11000.2000.200.20.11.95
Object
notification
Client authentication failed on {{TenantName}} due to client clock skew. Description: Kerberos authentication failed because of the client clock skew between client {{clientIpAddr}} and NAS controller {{nasControllerId}} of {{TenantName}}. Action Items: Fix client clock. Your client clock must be within 5 minutes range from the Kerberos server (i.e. AD) clock. Configure the used AD as an NTP server for this client to avoid clock skews errors.
Context
- MIB
- FLUIDFS-CLUSTER-MIB
- OID
.1.3.6.1.4.1.674.11000.2000.200.20.11.95- Type
- notification
- Status
- current
- Parent
- fluidFSEventsClientAccess
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 'FLUIDFS-CLUSTER-MIB' -M '/opt/observium/mibs/dell:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'FLUIDFS-CLUSTER-MIB::fluidFSEventClientAccessClientClockSkew'
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::fluidFSEventClientAccessClientClockSkew'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.