fluidFSEventHealthPairStoreSetProblemRecovered
FLUIDFS-CLUSTER-MIB ·
.1.3.6.1.4.1.674.11000.2000.200.20.9.76
Object
notification
System switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} verified connection to storage subsystem and switched Write-Through mode off (mirroring).
Context
- MIB
- FLUIDFS-CLUSTER-MIB
- OID
.1.3.6.1.4.1.674.11000.2000.200.20.9.76- Type
- notification
- Status
- current
- Parent
- fluidFSEventsHealth
- Siblings
- 85
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| fluidFSEventHealthPairPowerProblem The system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} BPS is not functioning properly and its peer controller {{peerNodeId}} has he… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.10 |
| fluidFSEventHealthDuplicateIp Duplicate IP address {{ipAddr}} in use on the node {{nodeId}}. Description: On node {{nodeId}} an ip address {{ipAddr}} in use on this system is being used by another system wi… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.102 |
| fluidFSEventHealthUnmapIsNotSupportedOnLuns Unmap is not supported by some of the LUNs Description: The following LUNs doesn't support the unmap functionallity: {{LunsList}}. Action Items: Please consider to upgrade t… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.103 |
| fluidFSEventHealthPairPowerProblemRecovered The system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} verified the power system reliability and switched Write-Through mode off (mi… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.11 |
| fluidFSEventHealthPairHWProblem The system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} hardware is not working properly and its peer NAS controller {{peerNodeId}} h… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.110 |
| fluidFSEventHealthPairHWRecovered The system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} hardware is working properly. Switched Write-Through mode off (mirroring). | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.111 |
| fluidFSEventHealthUnresponsiveVmwareServerOnAllNodes VMWare service is unavailable on all NAS-Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.112 |
| fluidFSEventHealthUnresponsiveVmwareServerOnNodes VMWare service is unavailable on all NAS-Controllers {{nodeIds}} | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.113 |
| fluidFSEventHealthResponsiveVmwareServerOnAllNodes VMWare service is available on all NAS-Controlles | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.114 |
| fluidFSEventHealthCouldNotAllocateProtectedMemory Problem with allocating protected memory Description: Memory detector could not allocate the protected memory Action Items: Please contact support | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.115 |
| fluidFSEventHealthInvalidSizeOfProtectedMemory Problem with allocating protected memory Description: The model's predefined size of protected memory is not equal to allocated Action Items: Please contact support | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.116 |
| fluidFSEventHealthCouldNotAllocateUnProtectedMemory Problem with allocating unprotected memory Description: Preallocation script could not allocate the unprotected memory Action Items: Please contact support | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.117 |
| fluidFSEventHealthUnresponsiveIscsiPortalsOnAllNodes iSCSI portals are unavailable on all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.118 |
| fluidFSEventHealthUnresponsiveIscsiPortalsOnNodes iSCSI portals are unavailable on NAS Controllers {{nodeIds}} | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.119 |
| fluidFSEventHealthSafeShutdownBegins The power button of NAS controller {{thisNodeId}} was pressed. Description: The power button of NAS controller {{thisNodeId}} was pressed. The NAS controller's cache is being f… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.12 |
| fluidFSEventHealthResponsiveIscsiPortalsOnAllNodes iSCSI portals are available on all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.120 |
| fluidFSEventHealthUnavailableNtpServiceOnAllNodes NTP service is unavailable on all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.121 |
| fluidFSEventHealthAvailableNtpServiceOnAllNodes NTP service become available on all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.122 |
| fluidFSEventHealthUnavailableNtpServiceOnNodes NTP service is unavailable on NAS Controllers {{nodeIds}} | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.123 |
| fluidFSEventHealthUnavailableAntivirusOnAllNodes Antivirus is unavailable on all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.124 |
| fluidFSEventHealthAvailableAntivirusOnAllNodes Antivirus become available on all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.125 |
| fluidFSEventHealthUnavailableAntivirusOnNodes Antivirus is unavailable on NAS Controllers {{nodeIds}} | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.126 |
| fluidFSEventHealthUnavailableAuditingServicesOnAllNodes Auditing subscribers became unavailable for all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.127 |
| fluidFSEventHealthAvailableAuditingServicesOnAllNodes Auditing subscribers became available for all NAS Controllers | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.128 |
| fluidFSEventHealthUnavailableAuditingServicesOnNodes Auditing subscribers became unavailable for NAS Controller/s: {{nodeIds}} | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.129 |
| fluidFSEventHealthSafeShutdownEnds NAS controller {{thisNodeId}} cache was flushed and it is shutting down. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.13 |
| fluidFSEventHealthPairCacheArmingProblem System switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} has problems with arming the protected memory, as well as it's peer. Switched Wri… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.130 |
| fluidFSEventHealthPairCacheArmingProblemRecovered System switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} succeeded arming the protected memory, and switched Write-Through mode off (mirro… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.131 |
| fluidFSEventHealthCouldNotArmProtectedMemoryRegion Problem with arming of protected memory regions Description: Memory detector could not arm protected memory region Action Items: Please contact support | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.132 |
| fluidFSEventHealthFSUserMetaDataMissing Directory entry was identified as missing; Entry {{dirEntry}} in {{parentDirDsidPath}}. Action Items: Recover it from backup. Internal Information: File {{dsid}} volume {{FS… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.133 |
| fluidFSEventHealthUnresponsiveLdapServersOnAllNodes LDAP servers, used by {{TenantName}}, are not responding. Description: All LDAP servers ({{serverNames}}), used by {{TenantName}}, are not responding on all NAS Controllers. Fo… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.134 |
| fluidFSEventHealthUnresponsiveLdapServersOnSomeNodes All LDAP servers ({{serverNames}}), used by {{TenantName}}, are unresponsive on some NAS Controllers: {{nodeIds}}. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.135 |
| fluidFSEventHealthResponsiveLdapServerOnAllNodes Found responsive LDAP server(s) among ({{serverNames}}), used by {{TenantName}}, on all NAS Controllers. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.136 |
| fluidFSEventHealthUnresponsiveNisServersOnAllNodes NIS servers, used by {{TenantName}}, are not responding. Description: All NIS servers ({{serverNames}}), used by {{TenantName}}, are not responding on all NAS Controllers. For … | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.137 |
| fluidFSEventHealthResponsiveNisServerOnAllNodes Found responsive NIS server(s) among ({{serverNames}}), used by {{TenantName}}, on all NAS Controllers. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.138 |
| fluidFSEventHealthUnresponsiveNisServersOnSomeNodes All NIS servers ({{serverNames}}), used by {{TenantName}}, are unresponsive on some NAS Controllers: {{nodeIds}}. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.139 |
| fluidFSEventHealthPairTemperatureProblem The system switched Write-Through mode on (journaling). Description: The system switched Write-Through mode on (journaling) because both NAS controllers' temperature appears hi… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.14 |
| fluidFSEventHealthUnresponsiveDnsServersOnAllNodes DNS servers, used by {{TenantName}}, are not responding. Description: All DNS servers ({{serverIps}}), used by {{TenantName}}, are not responding on all NAS Controllers. For e… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.140 |
| fluidFSEventHealthResponsiveDnsServerOnAllNodes Found responsive DNS server(s) among ({{serverIps}}), used by {{TenantName}}, on all NAS Controllers. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.141 |
| fluidFSEventHealthUnresponsiveDnsServersOnSomeNodes All DNS servers ({{serverIps}}), used by {{TenantName}}, are unresponsive on some NAS Controllers: {{nodeIds}}. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.142 |
| fluidFSEventHealthUnresponsiveAdServer Active Directory, used by {{TenantName}}, is not responsive. Description: Active Directory domain {{domainName}}, used by {{TenantName}}, is not reachable. For each domain cont… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.143 |
| fluidFSEventHealthResponsiveAdServer Active Directory domain {{domainName}}, used by {{TenantName}}, is reachable. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.144 |
| fluidFSEventHealthSlowResponse Slow response time from {{serverKind}} to {{TenantName}}. Description: Response time from {{serverKind}} servers ({{serverList}}) of {{responseTime}} seconds exceeds {{critical… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.145 |
| fluidFSEventHealthAdCriticalClockSkew AD (used by {{TenantName}}) and NAS controller {{nodeId}} clocks aren't synchronized Description: Clock of NAS controller {{nodeId}} and AD clock, used by {{TenantName}} (domai… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.146 |
| fluidFSEventHealthCIFSAttachedACLCorruption Failed to read a file ACL's. Description: ACL of file {{dsidPath}} can not be read. Access will be denied to all users. Action Items: Please reset the file ACL | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.147 |
| fluidFSEventHealthFSUserUnrecoverableRmapChecksumError Unrecoverable erroneous block in user file. Description: Unrecoverable erroneous block was identified in {{dsidPath}} and it is inaccessible. Action Items: Move this file/di… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.149 |
| fluidFSEventHealthPairTemperatureProblemRecovered The system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} verified the temperature system reliability and switched Write-Through mode o… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.15 |
| fluidFSEventHealthFSVolumeUnrecoverableRmapChecksumError NAS Volume {{FSIDName}} is partially serving. Description: Unrecoverable erroneous block was identified in volume {{FSIDName}}. This volume is partially serving. Action Items… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.150 |
| fluidFSEventHealthFSRehydrationSpaceMarginReached Rehydration paused on volume {{FSIDName}} - insufficient space. Description: Volume {{FSIDName}} doesn't have the required free {{dedupSpaceMarginMb}} MB needed for rehydration… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.151 |
| fluidFSEventHealthFSLowOnLunSpaceDedupPostponed High NAS pool space usage. Data Reduction paused on cluster. Description: Cluster does not have the required NAS pool free space needed for Data Reduction Action Items: Plea… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.154 |
| fluidFSEventHealthFSLowOnLunSpaceDedupResumed Data Reduction resumed on cluster. Description: NAS pool free space increased. Data reduction is resumed | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.155 |
| fluidFSEventHealthFSLowOnLunSpaceFSNotAccessible High NAS pool space usage. File system access is limited Description: High NAS pool space usage. File system is accessible only using NFS3. Action Items: Please perform one … | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.156 |
| fluidFSEventHealthFSLowOnLunSpaceFSAccessible File system access is back to normal. Description: NAS pool free space increased. File system can be accessed by all protocols | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.157 |
| fluidFSEventHealthLocalTimeDesynchronizedToNtp Local time on node {{nodeId}} is desynchronized by {{timeDiffSec}} seconds. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.158 |
| fluidFSEventHealthClientsOnFailback There are clients ({{numberOfClients}}) that are waiting for manual failback. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.16 |
| fluidFSEventHealthCacheLossOfUserFiles Latest user writes might have been lost. Description: The system identified that some of the latest user writes might have been lost. This might have been caused by a reboot of… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.21 |
| fluidFSEventHealthCacheLossOfMetadata File System process failed to recover. Description: The system identified that at least one of its File System processes has restarted and failed to recover it. The system will… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.22 |
| fluidFSEventHealthCacheLossRecovered File system recovery successfully finished. Description: File system recovery successfully finished. Action Items: Data written in the day prior to the event might be compro… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.23 |
| fluidFSEventHealthStoreAccessProblem Lost communication to storage from NAS controller {{nodeId}}. Description: The system identified a communication problem between NAS controller {{nodeId}} and the storage contr… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.24 |
| fluidFSEventHealthLunVerificationFailure NAS controller {{nodeId}} encountered a problem accessing a NAS storage pool. Action Items: Please contact Support. Internal Information: Domain {{domainId}} LUN {{lunId}} | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.25 |
| fluidFSEventHealthFileSystemMajorAccessibilityProblem Clients may encounter a long period of partial data access. Description: The file system identified that clients may have partial data access in the last {{timeout}} minutes. … | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.27 |
| fluidFSEventHealthFileSystemAccessibilityRevival File system back to optimal state. Description: The File System has overcome its accessibility problem and returned back to full functionality. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.28 |
| fluidFSEventHealthNodeFailed NAS controller {{nodeName}} is unavailable. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.4 |
| fluidFSEventHealthFSMultipleRmapChecksumError Multiple erroneous file system blocks were identified and fixed. Action Items: If the problem recurs, verify system hardware health. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.47 |
| fluidFSEventHealthFSSystemUnrecoverableRmapChecksumError Unrecoverable erroneous block was identified. Description: Unrecoverable erroneous block was identified. The file system is partially serving. Action Items: Contact Support.… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.48 |
| fluidFSEventHealthNodeOK NAS controller {{nodeName}} is available. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.5 |
| fluidFSEventHealthFSMultipleUserMetaDataMissing Multiple directory entries were identified as missing. Action Items: Recover them from backup. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.50 |
| fluidFSEventHealthFSLowOnLunSpace High NAS pool capacity. Performance might be affected. Description: NAS pool capacity usage has reached high watermark which will affect performance. Action Items: Expand th… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.53 |
| fluidFSEventHealthLocalPartitionIsFull The used space of local file system partition {{partitionName}} on NAS controller {{nodeName}} is high ({{percentOfUsedSpace}}%). Please contact support. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.6 |
| fluidFSEventHealthBadClientLoadBalancing Bad {{protocol}} clients distribution: ({{connectionsVector}}). Description: Bad {{protocol}} clients distribution: ({{connectionsVector}}). Each pair in this set represents NA… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.65 |
| fluidFSEventHealthCifsLockingInconsistancy Inconsistent locks interrupted SMB service. Description: SMB service is interrupted due to inconsistencies in locking mechanism, starting recovery process. Internal Informati… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.66 |
| fluidFSEventHealthCifsLockingInconsistancyRecovered Inconsistent locks recovered. Description: SMB locking inconsistencies recovery was successfully finished. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.67 |
| fluidFSEventHealthHighUseOfSwap The usage of swap memory on NAS controller {{nodeName}} is high ({{percentOfUsedSwap}}%). | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.7 |
| fluidFSEventHealthFSReclaimerOverload High load in snapshots space reclaiming process. Description: The file system has been recently engaged in reclaiming the space of deleted snapshots or NAS volumes. This could … | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.72 |
| fluidFSEventHealthPairStoreSetProblem System switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} has lost connection to storage subsystem and its peer NAS controller {{peerNodeId… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.75 |
| fluidFSEventHealthPairPowerSuppliesProblem The system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} has lost full power supplies redundancy and its peer NAS controller {{peerNod… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.77 |
| fluidFSEventHealthPairPowerSuppliesRecovered The system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} full power supplies redundancy was restored and switched Write-Through mode o… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.78 |
| fluidFSEventHealthHighUseOfMemory The memory usage on NAS controller {{nodeName}} is high. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.8 |
| fluidFSEventHealthPairFansProblem The system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} fans are not working properly and its peer NAS controller {{peerNodeId}} has … | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.85 |
| fluidFSEventHealthPairFansRecovered The system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} fans are working properly. Switched Write-Through mode off (mirroring). | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.86 |
| fluidFSEventHealthProtocolsStateInconsistancy Inconsistent state interrupted SMB/NFSv4 service. Description: SMB/NFSv4 services are interrupted due to inconsistencies in locking mechanism, starting recovery process. Inte… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.87 |
| fluidFSEventHealthProtocolsStateInconsistancyRecovered Inconsistent locks recovered. Description: SMB/NFSv4 locking inconsistencies recovery was successfully finished. | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.88 |
| fluidFSEventHealthHighUseOfFileDescriptors File descriptors usage on NAS controller {{nodeName}} is high ({{percentOfUsedFileDescriptors}}%). | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.9 |
| fluidFSEventHealthFSDedupSpaceMarginReached Optimization paused on volume {{virtualVolume}} - insufficient space. Description: Volume {{virtualVolume}} doesn't have the required free {{dedupSpaceMarginMb}} MB needed for … | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.91 |
| fluidFSEventHealthStoreAccessRestored Restored communication to storage from NAS controller {{nodeId}}. Description: The system identified that a communication problem between NAS controller {{nodeId}} and the stor… | notification | - | .1.3.6.1.4.1.674.11000.2000.200.20.9.92 |
Notification Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| sysName General system name | scalar | SNMPv2-TCDisplayString | .1.3.6.1.4.1.674.11000.2000.200.22.1 |
| fluidFSEventsParamsHealthThisNodeId Node id of the current node | scalar | SNMPv2-TCDisplayString | .1.3.6.1.4.1.674.11000.2000.200.21.9.8 |