fluidFSEventClientAccessMountExportDoesntExist
FLUIDFS-CLUSTER-MIB ·
.1.3.6.1.4.1.674.11000.2000.200.20.11.90
Object
notification
NFS mount failure. The path {{mountPath}} is not exported by {{TenantName}}. Description: NFS mount failure: Client {{clientIpAddr}} attempted to mount the path ({{mountPath}}) from {{TenantName}} which is not exported to NFS clients. Action Items: This failure is commonly caused by spelling mistakes done on the client machine or when accessing the wrong server. List all available exports on the NAS and verify everything is as expected, all the needed exports exist and nothing has been changed unintentionally.
Context
- MIB
- FLUIDFS-CLUSTER-MIB
- OID
.1.3.6.1.4.1.674.11000.2000.200.20.11.90- 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::fluidFSEventClientAccessMountExportDoesntExist'
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::fluidFSEventClientAccessMountExportDoesntExist'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.