fluidFSEventClientAccessMountFromInsecurePort
FLUIDFS-CLUSTER-MIB ·
.1.3.6.1.4.1.674.11000.2000.200.20.11.89
Object
notification
NFS mount failure. Wrong port was used for secure export {{nfsExport}}. Description: NFS mount failure: Client {{clientIpAddr}} attempted to mount the secure export {{nfsExport}} on NAS Volume {{nasContainerIdIntegerName}} but used port {{nfsClientPort}} instead of a well-known port (under 1024) on the client side. Action Items: Secure exports require that the client accessing them will perform the mount using a well-known port (under 1024). This is done as a security measure.
Context
- MIB
- FLUIDFS-CLUSTER-MIB
- OID
.1.3.6.1.4.1.674.11000.2000.200.20.11.89- 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::fluidFSEventClientAccessMountFromInsecurePort'
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::fluidFSEventClientAccessMountFromInsecurePort'
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.