OID reference

fluidFSEventHealthStoreAccessProblem

1.3.6.1.4.1.674.11000.2000.200.20.9.24

Description

Lost communication to storage from NAS controller {{nodeId}}. Description: The system identified a communication problem between NAS controller {{nodeId}} and the storage controllers which may affect system performance. Action Items: The system constantly monitors the validity of communication between NAS controllers …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.674.11000.2000.200.20.9 (fluidFSEventsHealth)
Node code
24
Node name
fluidFSEventHealthStoreAccessProblem
Category
SNMP notification
Numeric OID
1.3.6.1.4.1.674.11000.2000.200.20.9.24
URN notation
urn:oid:1.3.6.1.4.1.674.11000.2000.200.20.9.24
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 674 11000 2000 200 20 9 24}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dell(674) enterpriseSW(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dell(674) enterpriseSW(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dell(674) dellEnterpriseBranch(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dell(674) dellEnterpriseBranch(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dell(674) enterpriseSoftware(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dell(674) enterpriseSoftware(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dellEnterprise(674) enterpriseSW(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dellEnterprise(674) enterpriseSW(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dellEnterprise(674) dellEnterpriseBranch(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dellEnterprise(674) dellEnterpriseBranch(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dellEnterprise(674) enterpriseSoftware(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dellEnterprise(674) enterpriseSoftware(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dell(674) enterpriseSW(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dell(674) enterpriseSW(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dell(674) dellEnterpriseBranch(11000) dellStorageSubBranch(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dell(674) dellEnterpriseBranch(11000) storageMgmt(2000) fluidFS(200) fluidFSEvents(20) fluidFSEventsHealth(9) fluidFSEventHealthStoreAccessProblem(24)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/674/11000/2000/200/20/9/24
  • /ISO/Identified-Organization/6/1/4/1/674/11000/2000/200/20/9/24
  • /ISO/3/6/1/4/1/674/11000/2000/200/20/9/24
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/dell/enterpriseSW/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dell/enterpriseSW/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dell/dellEnterpriseBranch/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dell/dellEnterpriseBranch/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dell/enterpriseSoftware/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dell/enterpriseSoftware/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dellEnterprise/enterpriseSW/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dellEnterprise/enterpriseSW/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dellEnterprise/dellEnterpriseBranch/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dellEnterprise/dellEnterpriseBranch/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dellEnterprise/enterpriseSoftware/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprise/dellEnterprise/enterpriseSoftware/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprises/dell/enterpriseSW/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprises/dell/enterpriseSW/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprises/dell/dellEnterpriseBranch/dellStorageSubBranch/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • /iso/identified-organization/dod/internet/private/enterprises/dell/dellEnterpriseBranch/storageMgmt/fluidFS/fluidFSEvents/fluidFSEventsHealth/fluidFSEventHealthStoreAccessProblem
  • Additional combinations skipped.

The displayed source records contain one distinct definition. Compare its source records.

fluidFSEventHealthStoreAccessProblem NOTIFICATION-TYPE
       OBJECTS { sysName, fluidFSEventsParamsHealthDomainId, fluidFSEventsParamsHealthNodeId, fluidFSEventsParamsHealthSetId }
       STATUS current
       DESCRIPTION
           "Lost communication to storage from NAS controller {{nodeId}}.   Description:  The system identified a communication problem between NAS controller {{nodeId}} and the storage controllers which may affect system performance.   Action Items:  The system constantly monitors the validity of communication between NAS controllers and Storage controller. This event is issued once the system identifies a communication issue. If the system was recently deployed or any of its components were recently moved, verify that all connections and configurations are according to the recommendations. If the system was functioning optimally for a while and this is a new event it is most likely due to a physical problem (like a bad/loose cable) or a change in network configuration which affects the components communication. Verify that all the network cables are correctly connected to the relevant NAS controller. Verify that all the iSCSI switches are up and running. If any change was introduced to the environment (new physical switch, new switch configuration), try to revert this change in order to understand the cause of the problem. Verify that the iSCSI switch is configured according to the recommendation. If the problem is persistent after verifying all the above, it is recommended to power cycle the problematic NAS controller using the UI.   Internal Information:  Domain {{domainId}} setId {{setId}}"
           --#TYPE         "Normal Event"
           --#SUMMARY      Lost communication to storage from NAS controller %d.   Description:  The system identified a communication problem between NAS controller %d and the storage controllers which may affect system performance.   Action Items:  The system constantly monitors the validity of communication between NAS controllers and Storage controller. This event is issued once the system identifies a communication issue. If the system was recently deployed or any of its components were recently moved, verify that all connections and configurations are according to the recommendations. If the system was functioning optimally for a while and this is a new event it is most likely due to a physical problem (like a bad/loose cable) or a change in network configuration which affects the components communication. Verify that all the network cables are correctly connected to the relevant NAS controller. Verify that all the iSCSI switches are up and running. If any change was introduced to the environment (new physical switch, new switch configuration), try to revert this change in order to understand the cause of the problem. Verify that the iSCSI switch is configured according to the recommendation. If the problem is persistent after verifying all the above, it is recommended to power cycle the problematic NAS controller using the UI.   Internal Information:  Domain %d setId %d
           --#ARGUMENTS    {1,2,3}
           --#SEVERITY     INFORMATIONAL
           --#TIMEINDEX    99
           --#STATE        OK
       ::= { fluidFSEventsHealth 24 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

Lost communication to storage from NAS controller {{nodeId}}. Description: The system identified a communication problem between NAS controller {{nodeId}} and the storage controllers which may affect system performance. Action Items: The system constantly monitors the validity of communication between NAS controllers and Storage controller. This event is issued once the system identifies a communication issue. If the system was recently deployed or any of its components were recently moved, verify that all connections and configurations are according to the recommendations. If the system was functioning optimally for a while and this is a new event it is most likely due to a physical problem (like a bad/loose cable) or a change in network configuration which affects the components communication. Verify that all the network cables are correctly connected to the relevant NAS controller. Verify that all the iSCSI switches are up and running. If any change was introduced to the environment (new physical switch, new switch configuration), try to revert this change in order to understand the cause of the problem. Verify that the iSCSI switch is configured according to the recommendation. If the problem is persistent after verifying all the above, it is recommended to power cycle the problematic NAS controller using the UI. Internal Information: Domain {{domainId}} setId {{setId}}

Sources for this description

Dell MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Dell MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

fluidFSEventHealthStoreAccessProblem · currentDell MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: fluidFSEventHealthStoreAccessProblem

Technical details
{
  "smi_kind": "NOTIFICATION-TYPE",
  "definition": [
    "fluidFSEventHealthStoreAccessProblem",
    "NOTIFICATION-TYPE",
    "OBJECTS",
    "{",
    "sysName",
    ",",
    "fluidFSEventsParamsHealthDomainId",
    ",",
    "fluidFSEventsParamsHealthNodeId",
    ",",
    "fluidFSEventsParamsHealthSetId",
    "}",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"Lost communication to storage from NAS controller {{nodeId}}. Description: The system identified a communication problem between NAS controller {{nodeId}} and the storage controllers which may affect system performance. Action Items: The system constantly monitors the validity of communication between NAS controllers and Storage controller. This event is issued once the system identifies a communication issue. If the system was recently deployed or any of its components were recently moved, verify that all connections and configurations are according to the recommendations. If the system was functioning optimally for a while and this is a new event it is most likely due to a physical problem (like a bad/loose cable) or a change in network configuration which affects the components communication. Verify that all the network cables are correctly connected to the relevant NAS controller. Verify that all the iSCSI switches are up and running. If any change was introduced to the environment (new physical switch, new switch configuration), try to revert this change in order to understand the cause of the problem. Verify that the iSCSI switch is configured according to the recommendation. If the problem is persistent after verifying all the above, it is recommended to power cycle the problematic NAS controller using the UI. Internal Information: Domain {{domainId}} setId {{setId}}\"",
    "::=",
    "{",
    "fluidFSEventsHealth",
    "24",
    "}"
  ],
  "syntax_tree": [
    [
      "Objects",
      [
        "sysName",
        "fluidFSEventsParamsHealthDomainId",
        "fluidFSEventsParamsHealthNodeId",
        "fluidFSEventsParamsHealthSetId"
      ]
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "Lost communication to storage from NAS controller {{nodeId}}. Description: The system identified a communication problem between NAS controller {{nodeId}} and the storage controllers which may affect system performance. Action Items: The system constantly monitors the validity of communication between NAS controllers and Storage controller. This event is issued once the system identifies a communication issue. If the system was recently deployed or any of its components were recently moved, verify that all connections and configurations are according to the recommendations. If the system was functioning optimally for a while and this is a new event it is most likely due to a physical problem (like a bad/loose cable) or a change in network configuration which affects the components communication. Verify that all the network cables are correctly connected to the relevant NAS controller. Verify that all the iSCSI switches are up and running. If any change was introduced to the environment (new physical switch, new switch configuration), try to revert this change in order to understand the cause of the problem. Verify that the iSCSI switch is configured according to the recommendation. If the problem is persistent after verifying all the above, it is recommended to power cycle the problematic NAS controller using the UI. Internal Information: Domain {{domainId}} setId {{setId}}"
    ],
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.674)

Wood Eric

Siblings (85)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.674.11000.2000.200.20.9.4 fluidFSEventHealthNodeFailed00
1.3.6.1.4.1.674.11000.2000.200.20.9.5 fluidFSEventHealthNodeOK00
1.3.6.1.4.1.674.11000.2000.200.20.9.6 fluidFSEventHealthLocalPartitionIsFull00
1.3.6.1.4.1.674.11000.2000.200.20.9.7 fluidFSEventHealthHighUseOfSwap00
1.3.6.1.4.1.674.11000.2000.200.20.9.8 fluidFSEventHealthHighUseOfMemory00
1.3.6.1.4.1.674.11000.2000.200.20.9.9 fluidFSEventHealthHighUseOfFileDescriptors00
1.3.6.1.4.1.674.11000.2000.200.20.9.10 fluidFSEventHealthPairPowerProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.11 fluidFSEventHealthPairPowerProblemRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.12 fluidFSEventHealthSafeShutdownBegins00
1.3.6.1.4.1.674.11000.2000.200.20.9.13 fluidFSEventHealthSafeShutdownEnds00
1.3.6.1.4.1.674.11000.2000.200.20.9.14 fluidFSEventHealthPairTemperatureProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.15 fluidFSEventHealthPairTemperatureProblemRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.16 fluidFSEventHealthClientsOnFailback00
1.3.6.1.4.1.674.11000.2000.200.20.9.21 fluidFSEventHealthCacheLossOfUserFiles00
1.3.6.1.4.1.674.11000.2000.200.20.9.22 fluidFSEventHealthCacheLossOfMetadata00
1.3.6.1.4.1.674.11000.2000.200.20.9.23 fluidFSEventHealthCacheLossRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.25 fluidFSEventHealthLunVerificationFailure00
1.3.6.1.4.1.674.11000.2000.200.20.9.27 fluidFSEventHealthFileSystemMajorAccessibilityProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.28 fluidFSEventHealthFileSystemAccessibilityRevival00
1.3.6.1.4.1.674.11000.2000.200.20.9.47 fluidFSEventHealthFSMultipleRmapChecksumError00
1.3.6.1.4.1.674.11000.2000.200.20.9.48 fluidFSEventHealthFSSystemUnrecoverableRmapChecksumError00
1.3.6.1.4.1.674.11000.2000.200.20.9.50 fluidFSEventHealthFSMultipleUserMetaDataMissing00
1.3.6.1.4.1.674.11000.2000.200.20.9.53 fluidFSEventHealthFSLowOnLunSpace00
1.3.6.1.4.1.674.11000.2000.200.20.9.65 fluidFSEventHealthBadClientLoadBalancing00
1.3.6.1.4.1.674.11000.2000.200.20.9.66 fluidFSEventHealthCifsLockingInconsistancy00
1.3.6.1.4.1.674.11000.2000.200.20.9.67 fluidFSEventHealthCifsLockingInconsistancyRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.72 fluidFSEventHealthFSReclaimerOverload00
1.3.6.1.4.1.674.11000.2000.200.20.9.75 fluidFSEventHealthPairStoreSetProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.76 fluidFSEventHealthPairStoreSetProblemRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.77 fluidFSEventHealthPairPowerSuppliesProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.78 fluidFSEventHealthPairPowerSuppliesRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.85 fluidFSEventHealthPairFansProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.86 fluidFSEventHealthPairFansRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.87 fluidFSEventHealthProtocolsStateInconsistancy00
1.3.6.1.4.1.674.11000.2000.200.20.9.88 fluidFSEventHealthProtocolsStateInconsistancyRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.91 fluidFSEventHealthFSDedupSpaceMarginReached00
1.3.6.1.4.1.674.11000.2000.200.20.9.92 fluidFSEventHealthStoreAccessRestored00
1.3.6.1.4.1.674.11000.2000.200.20.9.102 fluidFSEventHealthDuplicateIp00
1.3.6.1.4.1.674.11000.2000.200.20.9.103 fluidFSEventHealthUnmapIsNotSupportedOnLuns00
1.3.6.1.4.1.674.11000.2000.200.20.9.110 fluidFSEventHealthPairHWProblem00
1.3.6.1.4.1.674.11000.2000.200.20.9.111 fluidFSEventHealthPairHWRecovered00
1.3.6.1.4.1.674.11000.2000.200.20.9.112 fluidFSEventHealthUnresponsiveVmwareServerOnAllNodes00
1.3.6.1.4.1.674.11000.2000.200.20.9.113 fluidFSEventHealthUnresponsiveVmwareServerOnNodes00
1.3.6.1.4.1.674.11000.2000.200.20.9.114 fluidFSEventHealthResponsiveVmwareServerOnAllNodes00
1.3.6.1.4.1.674.11000.2000.200.20.9.115 fluidFSEventHealthCouldNotAllocateProtectedMemory00
1.3.6.1.4.1.674.11000.2000.200.20.9.116 fluidFSEventHealthInvalidSizeOfProtectedMemory00
1.3.6.1.4.1.674.11000.2000.200.20.9.117 fluidFSEventHealthCouldNotAllocateUnProtectedMemory00
1.3.6.1.4.1.674.11000.2000.200.20.9.118 fluidFSEventHealthUnresponsiveIscsiPortalsOnAllNodes00
1.3.6.1.4.1.674.11000.2000.200.20.9.119 fluidFSEventHealthUnresponsiveIscsiPortalsOnNodes00
1.3.6.1.4.1.674.11000.2000.200.20.9.120 fluidFSEventHealthResponsiveIscsiPortalsOnAllNodes00