Home/Catalog/FluidFS-MIB

FluidFS-MIB

FluidFS MIB
Main OID:
fluidFSMIBIdentity.1.3.6.1.4.1.674.11000.2000.200.100
1349
Objects
Active
Status
3
Dependencies

Imported Objects

SNMPv2-SMI
SNMPv2-TC
INET-ADDRESS-MIB

Objects

1349 total
Object Name
dell
OBJECT IDENTIFIER
.1.3.6.1.4.1.674
IMPORTS
Unknown
.1.3.6.1.4.1.674
enterpriseSoftware
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000
storageMgmt
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000
fluidFS
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200
fluidFSCluster
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.2
fluidFSCluNameThe name of the cluster.rw
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.2.1
fluidFSCluNodeNameThe name of the node.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.2.4.1.2
fluidFSCluResourceNameThe name of the resource. It must be unique within the cluster.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.2.5.1.2
fluidFSCluResourceOwnerNodeThe node in the cluster where the group of the resource is currently online.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.2.5.1.4
fluidFSGenEventDescA string describing the general event.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.10
fluidFSFileNameThe file name.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.11
fluidFSEvents
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20
fluidFSEventsAdmin
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.1
fluidFSEventAdminGeneralFutureTenantScopeEventInfoTenant scope event. Tenant {{TenantName}} (ID={{TenantId}}): {{generalEventText}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.1
fluidFSEventAdminGeneralFutureVolumeScopeEventInfoNAS Volume scope event. NAS Volume {{VolumeName}} (ID={{FSID}}): {{generalEventText}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.11
fluidFSEventAdminPauseReplicationThe user {{username}} paused the replication from {{replicationSource}} to {{replicationDestination}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.102
fluidFSEventAdminResumeReplicationThe user {{username}} resumed the replication from {{replicationSource}} to {{replicationDestination}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.103
fluidFSEventAdminStartedImmediateReplicationThe user {{username}} started immediate replication from {{replicationSource}} to {{replicationDestination}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.104
fluidFSEventAdminDetachReplicationThe user {{username}} detached the destination NAS volume {{replicationDestination}} from source NAS volume {{replicationSource}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.105
fluidFSEventAdminAttachReplicationThe user {{username}} attached the destination NAS volume {{replicationDestinationVolume}}@{{replicationDestinationCluster}} to NAS volume {{replicationSourceVolume}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.106
fluidFSEventAdminAddTrustedClusterThe user {{username}} added a new replication partner named {{trustedCluster}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.110
fluidFSEventAdminUpdateTrustedClusterConfThe user {{username}} updated the replication partner configuration for {{trustedCluster}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.111
fluidFSEventAdminRemoveTrustedClusterThe user {{username}} removed the cluster {{trustedCluster}} from the list of replication partners.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.112
fluidFSEventAdminSpInstalled{{packageName}} bundle installation completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.122
fluidFSEventAdminServicePackStartedFirmware DellFluidFS-{{spVersion}} installation started Description: Firmware DellFluidFS-{{spVersion}} installation started Action Items: You should follow the installation process in the CLI / WUI and the event log to verify it successfully completes
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.154
fluidFSEventAdminServicePackFailedFirmware DellFluidFS-{{spVersion}} failed to install. Description: Firmware DellFluidFS-{{spVersion}} failed to install, reason: {{spError}}. Action Items: System may be in inconsistent state, please check system validation in CLI / WUI.[[nl]]If system is in unstable state (i.e. some controllers are reported down) then escalate to resolve the situation.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.155
fluidFSEventAdminServicePackFinishedSuccessfully upgraded to firmware DellFluidFS-{{spVersion}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.156
fluidFSEventAdminGeneralFutureEventInfo{{generalEventText}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.162
fluidFSEventAdminGeneralFutureEventMajor{{generalEventText}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.163
fluidFSEventAdminGeneralFutureEventCrit{{generalEventText}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.164
fluidFSEventAdminGeneralFutureEventWarning{{generalEventText}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.165
fluidFSEventAdminCancelReplication{{username}} cancelled the replication from {{replicationSource}} to {{replicationDestination}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.167
fluidFSEventAdminDisableReplicationReplication-policy of NAS volumes {{replicationSource}} and {{replicationDestination}} was disabled. Description: The user {{username}} disabled the replication-policy of the destination NAS volume {{replicationDestination}} and the source NAS volume {{replicationSource}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.170
fluidFSEventAdminEnableReplicationReplication-policy of NAS volumes {{replicationSourceVolume}} and {{replicationDestinationVolume}} was enabled. Description: The user {{username}} enabled replication: re-attached NAS volume {{replicationDestinationVolume}} on cluster {{replicationDestinationCluster}} to local NAS volume {{replicationSourceVolume}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.171
fluidFSEventAdminAdminLoggedInToInterfaceThe user {{username}} logged in to {{ui}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.180
fluidFSEventAdminFormatFileSystemMkfsFailedFormat failed during execution of File System Structures Initialization phase. Internal Information: mkfs.sh failed with error code {{ErrCode}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.181
fluidFSEventAdminIncrementalFormatFileSystemMkfsFailedIncremental Format failed during execution of File System Structures Initialization phase. Internal Information: mkfs.sh failed with error code {{ErrCode}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.182
fluidFSEventAdminControllerAutoAttachStartAuto attach of NAS controller {{controllerId}} in appliance {{applianceId}} has started. Action Items: You should follow the attachment process in the CLI / WUI to verify it successfully completes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.185
fluidFSEventAdminControllerAutoDetachStartAuto detach of NAS controller {{controllerId}} in appliance {{applianceId}} has started. Action Items: You should follow the detachment process in the CLI / WUI to verify it successfully completes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.186
fluidFSEventAdminApplianceCreateStartCreate of NAS Appliance {{applianceId}} ({{applianceServiceTag}}) has started. Action Items: You should follow the appliance create process in the CLI / WUI to verify it successfully completes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.187
fluidFSEventAdminEnableEscalationAccessEscalation access was enabled for {{escalationPeriodInMinutes}} minutes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.188
fluidFSEventAdminConfigurationObjectSoftLimitExceededUser {{username}} created {{objectName}} exceeding the maximum recommended count {{recommendedMaxCount}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.189
fluidFSEventAdminControllerAttachStartAttach of NAS controller {{controllerId}} has started by {{username}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.190
fluidFSEventAdminControllerAttachEndAttach of NAS controller {{controllerId}} has completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.191
fluidFSEventAdminControllerDetachStartDetach of NAS controller {{controllerId}} was started by {{username}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.192
fluidFSEventAdminControllerDetachEndDetach of NAS controller {{controllerId}} has completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.193
fluidFSEventAdminApplianceJoinStartJoin of NAS Appliance {{applianceId}} was started by {{username}}. Action Items: You should follow the appliance join process in the CLI / WUI to verify it successfully completes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.194
fluidFSEventAdminApplianceJoinEndJoin of NAS Appliance {{applianceId}} has completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.1.195
fluidFSEventsHardware
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.2
fluidFSEventHardwareNoPacketLossInSubnetHostNAS Controller {{nodeId}} has no packet loss to host {{hostName}} on {{subnetName}} subnet.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.1
fluidFSEventHardwarePacketLossInSubnetNAS Controller {{nodeId}} had packet loss to {{subnetName}}. Description: NAS Controller {{nodeId}} had {{packetLoss}}% packet loss to IP address {{subnetName}} on host {{hostName}}. Subnet identifier {{network_id}}, prefix {{prefix}}, vlan tag id {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.4
fluidFSEventHardwareNoPacketLossInSubnetNAS Controller {{nodeId}} has no packet loss on {{subnetName}}. Description: NAS Controller {{nodeId}} has no packet loss to IP address {{subnetName}} on host {{hostName}}. Subnet identifier {{network_id}}, prefix {{prefix}}, vlan tag id {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.6
fluidFSEventHardwareNoPacketLossJumboInSubnetHostNAS Controller {{nodeId}} has no packet loss (using jumbo frames) to host {{hostName}} on {{subnetName}} subnet.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.7
fluidFSEventHardwarePacketLossJumboInSubnetNAS Controller {{nodeId}} had jumbo packet loss. Description: NAS Controller {{nodeId}} had {{packetLoss}}% packet loss to IP address {{subnetName}} on host {{hostName}} (using jumbo frames). Subnet identifier {{network_id}}, prefix {{prefix}}, vlan tag id {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.8
fluidFSEventHardwareNoPacketLossJumboInSubnetNAS Controller {{nodeId}} has no jumbo packet loss. Description: NAS Controller {{nodeId}} has no packet loss to IP address {{subnetName}} on host {{hostName}} (using jumbo frames). Subnet identifier {{network_id}}, prefix {{prefix}}, vlan tag id {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.12
fluidFSEventHardwareCantReachSubnetNAS Controller {{nodeId}} cannot reach IP {{subnetName}} Description: NAS Controller {{nodeId}} cannot reach IP address {{subnetName}} on host {{hostName}}. Subnet identifier {{network_id}}, prefix {{prefix}}, vlan tag id {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.13
fluidFSEventHardwareCantReachJumboSubnetNAS Controller {{nodeId}} cannot reach IP using (jumbo frames) Description: NAS Controller {{nodeId}} cannot reach IP address {{subnetName}} on host {{hostName}} (using jumbo frames). Subnet identifier {{network_id}}, prefix {{prefix}}, vlan tag id {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.18
fluidFSEventHardwareEthHasErrors{{ethName}} (part of {{bondName}}) on NAS Controller {{nodeId}} has errors.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.35
fluidFSEventHardwareEthHasDrops{{ethName}} (part of {{bondName}}) on NAS Controller {{nodeId}} has drops.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.36
fluidFSEventHardwareCantReachDefaultGatewayNAS Controller{{nodeId}} cannot reach default gateway {{ip}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.38
fluidFSEventHardwareCanReachDefaultGatewayNAS Controller{{nodeId}} can reach default gateway {{ip}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.39
fluidFSEventHardwarePacketLossInSubnetHostNAS Controller {{nodeId}} had {{packetLoss}}% packet loss to host {{hostName}} on {{subnetName}} subnet.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.56
fluidFSEventHardwareNoLinkInEthOnControllerEth{{ethName}} which belongs to NAS Controller {{nodeId}} is down.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.57
fluidFSEventHardwareEthLinkRestoredOnControllerEth{{ethName}} which belongs to NAS Controller {{nodeId}} is restored.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.58
fluidFSEventHardwarePacketLossJumboInSubnetHostNAS Controller {{nodeId}} had {{packetLoss}}% packet loss (using jumbo frames) to host {{hostName}} on {{subnetName}} subnet.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.59
fluidFSEventHardwareCantReachSubnetHostNAS Controller {{nodeId}} cannot reach host {{hostName}} on {{subnetName}} subnet.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.60
fluidFSEventHardwareCantReachJumboSubnetHostNAS Controller {{nodeId}} cannot reach (using jumbo frames) host {{hostName}} on {{subnetName}} subnet.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.61
fluidFSEventHardwareBpsAccessibilityNormalNAS Controller{{nodeId}} BPS reachability is back to normal (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.109
fluidFSEventHardwareBpsNormalBPS on NAS Controller{{nodeId}} is back to normal operation. Charge is {{bpsBatteryCharge}}% (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.110
fluidFSEventHardwareProcessorCoresCountFailedFailed to validate CPU cores count is equal in NAS Controller {{firstNodeId}} and NAS Controller {{secondNodeId}} (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.120
fluidFSEventHardwareProcessorCoresCountOkCPU cores count test successful. Count is equal in NAS Controller {{firstNodeId}} and NAS Controller {{secondNodeId}} (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.121
fluidFSEventHardwareMemoryNotOptimalMemory device status in NAS Controller{{nodeId}} is not optimal (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.124
fluidFSEventHardwareMemoryErrorMemory device status in NAS Controller{{nodeId}} is critical (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.125
fluidFSEventHardwareMemoryBackToNormalMemory device in NAS Controller{{nodeId}} returned to normal operation (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.126
fluidFSEventHardwareMemoryTempWarnMemory device temperature sensors in NAS Controller{{nodeId}} report warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.127
fluidFSEventHardwareMemoryTempNormalMemory device temperature sensors in NAS Controller{{nodeId}} report normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.128
fluidFSEventHardwareMemoryTempCriticalMemory device temperature sensors in NAS Controller{{nodeId}} report critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.129
fluidFSEventHardwareMemorySizeCountFailedFailed to validate memory size is equal in NAS Controller {{firstNodeId}} and NAS Controller {{secondNodeId}} (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.130
fluidFSEventHardwareMemorySizeCountOkMemory size test successful. Size is equal in NAS Controller {{firstNodeId}} and NAS Controller {{secondNodeId}} (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.131
fluidFSEventHardwareMemoryInfoNotAvailableMemory device status in NAS Controller{{nodeId}} is not available. Internal error in memory monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.132
fluidFSEventHardwareMemoryInfoIsAvailableMemory device status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.133
fluidFSEventHardwareControllerStatusNotAvailableNAS Controller{{nodeId}} hardware status is not available. Internal error in controller status analysis (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.135
fluidFSEventHardwareControllerStatusAvailableNAS Controller{{nodeId}} hardware status is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.136
fluidFSEventHardwareLocalDisksInfoNotAvailableLocal storage status in NAS Controller{{nodeId}} is not available. S.M.A.R.T. info is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.143
fluidFSEventHardwareLocalDisksInfoIsAvailableLocal storage status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.144
fluidFSEventHardwareApplianceIntrusionWarningChassis cover for NAS Appliance{{applianceId}} is open (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.153
fluidFSEventHardwareApplianceIntrusionOkChassis cover for NAS Controller {{applianceId}} was closed (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.154
fluidFSEventHardwareAppFanSystemInfoNotAvailableFans set overall status in NAS Appliance {{applianceId}} is not available. Internal error in fans monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.168
fluidFSEventHardwareAppFanSystemInfoIsAvailableFans set overall status in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.169
fluidFSEventHardwareAppFanErrorFan {{componentName}} in NAS Appliance {{applianceId}} has critical status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.170
fluidFSEventHardwareAppFanWarningFan {{componentName}} in NAS Appliance {{applianceId}} has warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.171
fluidFSEventHardwareAppFanBackToNormalFan {{componentName}} in NAS Appliance {{applianceId}} returned to normal operation (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.172
fluidFSEventHardwareAppFanInfoNotAvailableFan {{componentName}} status in NAS Appliance {{applianceId}} is not available. Internal error in fans monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.173
fluidFSEventHardwareAppFanInfoIsAvailableFan {{componentName}} status in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.174
fluidFSEventHardwarePowerSupplyInfoNotAvailablePower supply status in NAS Controller{{nodeId}} is not available. Internal error in power supply monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.178
fluidFSEventHardwarePowerSupplyInfoIsAvailablePower supply status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.179
fluidFSEventHardwarePsuErrorPower supply unit {{componentName}} in NAS Controller{{nodeId}} has failure status, power supply redundancy lost (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.180
fluidFSEventHardwarePsuWarningPower supply unit {{componentName}} in NAS Controller{{nodeId}} has warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.181
fluidFSEventHardwarePsuBackToNormalPower supply unit {{componentName}} in NAS Controller{{nodeId}} returned to normal operation (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.182
fluidFSEventHardwarePsuInfoNotAvailablePower supply unit {{componentName}} status in NAS Controller{{nodeId}} is not available. Internal error in power supply monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.183
fluidFSEventHardwarePsuInfoIsAvailablePower supply unit {{componentName}} status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.184
fluidFSEventHardwareAppPowerSupplyInfoNotAvailablePower supply status in NAS Appliance {{applianceId}} is not available. Internal error in power supply monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.188
fluidFSEventHardwareAppPowerSupplyInfoIsAvailablePower supply status in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.189
fluidFSEventHardwareAppPsuErrorPower supply unit {{componentName}} in NAS Appliance {{applianceId}} has failure status, power supply redundancy lost (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.190
fluidFSEventHardwareAppPsuWarningPower supply unit {{componentName}} in NAS Appliance {{applianceId}} has warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.191
fluidFSEventHardwareAppPsuBackToNormalPower supply unit {{componentName}} in NAS Appliance {{applianceId}} returned to normal operation (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.192
fluidFSEventHardwareAppPsuInfoNotAvailablePower supply unit {{componentName}} status in NAS Appliance {{applianceId}} is not available. Internal error in power supply monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.193
fluidFSEventHardwareAppPsuInfoIsAvailablePower supply unit {{componentName}} status in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.194
fluidFSEventHardwareAppPsuAmperageErrorCurrent sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports critical status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.195
fluidFSEventHardwareAppPsuAmperageWarningCurrent sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.196
fluidFSEventHardwareAppPsuAmperageNormalCurrent sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports normal status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.197
fluidFSEventHardwareAppPsuTempErrorTemperature sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.201
fluidFSEventHardwareAppPsuTempWarningTemperature sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.202
fluidFSEventHardwareAppPsuTempNormalTemperature sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.203
fluidFSEventHardwareAppPsuVoltageErrorVoltage sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports critical status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.207
fluidFSEventHardwareAppPsuVoltageWarningVoltage sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.208
fluidFSEventHardwareAppPsuVoltageNormalVoltage sensor in power supply unit {{componentName}} in NAS Appliance {{applianceId}} reports normal status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.209
fluidFSEventHardwareMotherBoardAmperageErrorNAS Controller{{nodeId}} system board current sensors report critical status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.213
fluidFSEventHardwareMotherBoardAmperageWarningNAS Controller{{nodeId}} system board current sensors report warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.214
fluidFSEventHardwareMotherBoardAmperageNormalNAS Controller{{nodeId}} system board current sensors report normal status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.215
fluidFSEventHardwareMotherBoardTempErrorNAS Controller{{nodeId}} system board temperature sensors report critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.216
fluidFSEventHardwareMotherBoardTempWarningNAS Controller{{nodeId}} system board temperature sensors report warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.217
fluidFSEventHardwareMotherBoardTempNormalNAS Controller{{nodeId}} system board temperature sensors report normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.218
fluidFSEventHardwareMotherBoardVoltageErrorNAS Controller{{nodeId}} system board voltage sensors report critical status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.219
fluidFSEventHardwareMotherBoardVoltageWarningNAS Controller{{nodeId}} system board voltage sensors report warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.220
fluidFSEventHardwareMotherBoardVoltageNormalNAS Controller{{nodeId}} system board voltage sensors report normal status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.221
fluidFSEventHardwareMotherBoardInfoNotAvailableController system board status in NAS Controller{{nodeId}} is not available. Internal error in system board monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.222
fluidFSEventHardwareMotherBoardInfoIsAvailableController system board status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.223
fluidFSEventHardwareNetworksInfoNotAvailableNetwork status in NAS Controller{{nodeId}} is not available. Internal error in network monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.224
fluidFSEventHardwareNetworksInfoIsAvailableNetwork status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.225
fluidFSEventHardwareNetworkInfoNotAvailable{{networkName}} network status in NAS Controller{{nodeId}} is not available. Internal error in network monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.229
fluidFSEventHardwareNetworkInfoIsAvailable{{networkName}} network status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.230
fluidFSEventHardwareApplianceStatusNotAvailableNAS Appliance {{applianceId}} hardware status is not available. Internal error in appliance status analysis (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.240
fluidFSEventHardwareApplianceStatusAvailableNAS Appliance {{applianceId}} hardware status is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.241
fluidFSEventHardwareLocalIPMIBackToNormalNAS Controller{{nodeId}} IPMI is back to normal (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.245
fluidFSEventHardwarePeerIPMIBackToNormalNAS Controller{{nodeId}} peer IPMI is reachable again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.246
fluidFSEventHardwareLocalIPMIStatusNotAvailableNAS Controller{{nodeId}} local IPMI status is not available. Internal error in IPMI status monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.247
fluidFSEventHardwareLocalIPMIStatusAvailableNAS Controller{{nodeId}} local IPMI status is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.248
fluidFSEventHardwarePeerIPMIStatusNotAvailableNAS Controller{{nodeId}} peer IPMI status is not available. Internal error in IPMI status monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.249
fluidFSEventHardwarePeerIPMIStatusAvailableNAS Controller{{nodeId}} peer IPMI status is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.250
fluidFSEventHardwarePsuNotDetectedPower supply unit {{componentName}} in NAS Controller{{nodeId}} is not detected, power supply redundancy lost. Please make sure the unit is attached properly (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.251
fluidFSEventHardwarePsuDetectedPower supply unit {{componentName}} in NAS Controller{{nodeId}} is detected (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.252
fluidFSEventHardwareAppPsuNotDetectedPower supply unit {{componentName}} in NAS Appliance {{applianceId}} is not detected, power supply redundancy lost. Please make sure the unit is attached properly (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.253
fluidFSEventHardwareAppPsuDetectedPower supply unit {{componentName}} in NAS Appliance {{applianceId}} is detected (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.254
fluidFSEventHardwareBpsNotAccessibleNAS Controller{{nodeId}} failed to reach its BPS (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.257
fluidFSEventHardwareNoLinkInReplicationRelatedEthOnControllerEth{{ethName}} which belongs to NAS Controller{{nodeId}} is down, therefore replication related connectivity may be affected.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.258
fluidFSEventHardwarePsuNoInputPower supply unit {{componentName}} in NAS Controller{{nodeId}} has no input. Please make sure the unit cable is attached properly (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.259
fluidFSEventHardwarePsuInputDetectedPower supply unit {{componentName}} in NAS Controller{{nodeId}} input detected (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.260
fluidFSEventHardwareAppPsuNoInputPower supply unit {{componentName}} in NAS Appliance {{applianceId}} has no input. Please make sure the unit cable is attached properly (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.261
fluidFSEventHardwareAppPsuInputDetectedPower supply unit {{componentName}} in NAS Appliance {{applianceId}} input detected (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.262
fluidFSEventHardwarePeerIPMIReachabilityNAS Controller{{nodeId}} cannot reach peer IPMI (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.264
fluidFSEventHardwareLocalIPMIReachabilityNAS Controller{{nodeId}} IPMI is not working (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.265
fluidFSEventHardwareChassisIntrusionAlertChassis cover for NAS Controller{{nodeId}} is open (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.267
fluidFSEventHardwareChassisIntrusionBackToNormalChassis cover for NAS Controller{{nodeId}} was closed (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.268
fluidFSEventHardwareBpsCalibrationCycleNotAvailableBattery Calibration Cycle status in NAS Controller{{nodeId}} is not available. Internal error in Battery monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.269
fluidFSEventHardwareBpsCalibrationCycleIsAvailableBattery Calibration Cycle status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.270
fluidFSEventHardwareBpsCalibrationCycleInProgressBattery Calibration Cycle is in progress. Description: A Battery Calibration Cycle in NAS Controller{{nodeId}} is in progress. The Battery Pack will go through charge and discharge cycles, therefore battery error events during this process are normal. This process may take up to 7 days from first notification to complete. (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.271
fluidFSEventHardwareBpsForcedCalibrationCyclePendingForced BPS Calibration pending, performance impact expected. Description: Calibration Cycle will be forced in 30 days from first notification. Could not perform normal battery calibration cycle in NAS Controller{{nodeId}} since peer controller battery is not in an optimal condition. If peer battery is not repaired before the Calibration Cycle is forced, then during portions of the Calibration Cycle the file system will move to journaling mode, which may cause a performance impact (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.272
fluidFSEventHardwareBpsForcedCalibrationCycleNotNeededThe Forced Battery Calibration Cycle in NAS Controller{{nodeId}} is no longer required (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.273
fluidFSEventHardwareBpsCalibrationCycleIdleThe Battery Calibration Cycle in NAS Controller{{nodeId}} is idle (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.274
fluidFSEventHardwareBpsCalibrationLowBatteryBPS on NAS Controller{{nodeId}} is not operating properly. This is expected as the battery is under calibration cycle. Charge is {{bpsBatteryCharge}}% (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.275
fluidFSEventHardwareStandardFrameDisconnected{{ethName}} on NAS Controller{{firstNodeId}} cannot access {{targetEthName}} on NAS Controller{{secondNodeId}} (service tag: {{contextBasedServiceTag}}). Check that these interfaces are connected to the same switch, and are properly tagged.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.276
fluidFSEventHardwareStandardFrameConnected{{ethName}} on NAS Controller{{firstNodeId}} can access {{targetEthName}} on NAS Controller{{secondNodeId}} (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.277
fluidFSEventHardwareLargeFrameLDisconnected{{ethName}} on NAS Controller{{firstNodeId}} cannot access {{targetEthName}} on NAS Controller{{secondNodeId}} using large frames (service tag: {{contextBasedServiceTag}}). Check that jumbo-frames are enabled for these interfaces in the switch.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.278
fluidFSEventHardwareLargeFrameConnected{{ethName}} on NAS Controller {{firstNodeId}} can access {{targetEthName}} on NAS Controller {{secondNodeId}} using large frames (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.279
fluidFSEventHardwareBpsLowBatteryBPS charge on NAS Controller{{nodeId}} is too low ({{bpsBatteryCharge}}%). BPS is not operating properly (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.282
fluidFSEventHardwareExtServerJumboFramePacketLossNAS Controller{{nodeId}} had {{packetLoss}}% packet loss to {{extSrvType}} {{ip}}. Please make sure the {{extSrvType}} allows jumbo frames.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.283
fluidFSEventHardwareCantReachExtServeJumboFrameNAS Controller{{nodeId}} cannot reach {{extSrvType}} {{ip}}. Please make sure the {{extSrvType}} allows jumbo frames.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.284
fluidFSEventHardwareCantReachStaticRouteNAS Controller{{nodeId}} cannot reach the gateway {{ip}} to network {{destinationNetwork}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.285
fluidFSEventHardwareCanReachStaticRouteNAS Controller{{nodeId}} can reach the gateway {{ip}} to network {{destinationNetwork}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.286
fluidFSEventHardwareClusterCantSeeAllFormattedLunsFluidFS cannot access any formatted LUN. Please make sure the backend storage is on and appropriately connected to FluidFS.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.287
fluidFSEventHardwareClusterSeesAllFormattedLunsFluidFS connection to all the formatted LUNs is fully restored.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.288
fluidFSEventHardwareNodeCantSeeFormattedLunsMajorNAS Controller{{nodeId}} cannot reach all the formatted LUNs. The system may not be serving. Please make sure that this Controller is properly connected to a storage.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.289
fluidFSEventHardwareNodeCantSeeFormattedLunsWarningNAS Controller{{nodeId}} cannot reach all the formatted LUNs. The performance may be degraded. Please make sure that this Controller is properly connected to a storage.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.290
fluidFSEventHardwareNodeSeesFormattedLunsNAS Controller{{nodeId}} restored connection to all the formatted LUNs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.291
fluidFSEventHardwareClusterCantSeeFormattedLunLUN {{lunId}} is not reachable from FluidFS. Please make sure the LUN exists and is properly mapped from the backend storage.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.292
fluidFSEventHardwareClusterSeesFormattedLunLUN {{lunId}} is now fully reachable from FluidFS.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.293
fluidFSEventHardwareNodeCantSeeLunMajorFluidFS Controller{{nodeId}} can not reach formatted LUN {{lunId}}. The system may not be serving. Please check that this LUN has appropriate permissions to be seen by this FluidFS Controller.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.294
fluidFSEventHardwareNodeCantSeeLunWarningFluidFS Controller{{nodeId}} can not reach formatted LUN {{lunId}}. The performance may be degraded. Please check that this LUN has appropriate permissions to be seen by this FluidFS Controller.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.295
fluidFSEventHardwareMeshDisconnectednode{{fromNode}}.{{fromEth}} cannot reach node{{toNode}}.{{toEth}} in vlan {{vlanTag}} Description: {{fromEth}} on NAS Controller{{fromNode}} cannot access {{toEth}} on NAS Controller{{toNode}} with vlan tag {{vlanTag}}. Action Items: Check that these interfaces are connected to the same switch, and are properly tagged.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.296
fluidFSEventHardwareMeshConnectednode{{fromNode}}.{{fromEth}} can reach node{{toNode}}.{{toEth}} in vlan {{vlanTag}} Description: {{fromEth}} on NAS Controller{{fromNode}} can access {{toEth}} on NAS Controller{{toNode}} with vlan tag {{vlanTag}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.297
fluidFSEventHardwareTapeDeviceNotAccessibleFromNodeTape device {{tapeName}} is not accessible from NAS Controller{{nodeId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.298
fluidFSEventHardwareTapeDeviceNotAccessibleFromAllNodesTape device {{tapeName}} is not accessible from all NAS Controllers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.299
fluidFSEventHardwareTapeDeviceAccessibleFromNodeTape device {{tapeName}} is accessible from NAS Controller{{nodeId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.300
fluidFSEventHardwareDifferentFcHbaSpeedOnControllerFibre Channel port speeds in NAS Controller{{nodeId}} are not identical.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.301
fluidFSEventHardwareBpsAccessibilityNotAvailableBPS reachability in NAS Controller{{nodeId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.302
fluidFSEventHardwareBpsAccessibilityIsAvailableBPS reachability in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.303
fluidFSEventHardwareBpsInfoNotAvailableBPS status info in NAS Controller{{nodeId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.304
fluidFSEventHardwareBpsInfoIsAvailableBPS status info in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.305
fluidFSEventHardwareProcessorNotOptimalProcessor {{cpuName}} status in NAS Controller{{nodeId}} is not optimal (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.306
fluidFSEventHardwareProcessorErrorProcessor {{cpuName}} status in NAS Controller{{nodeId}} is critical (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.307
fluidFSEventHardwareProcessorBackToNormalProcessor {{cpuName}} in NAS Controller{{nodeId}} returned to normal operation (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.308
fluidFSEventHardwareProcessorTempNotAvailableProcessor {{cpuName}} temprature sensor info in NAS Controller{{nodeId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.309
fluidFSEventHardwareProcessorTempIsAvailableProcessor {{cpuName}} temprature sensor info in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.310
fluidFSEventHardwareProcessorTempWarnProcessor {{cpuName}} temperature sensor in NAS Controller{{nodeId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.311
fluidFSEventHardwareProcessorTempNormalProcessor {{cpuName}} temperature sensors in NAS Controller{{nodeId}} report normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.312
fluidFSEventHardwareProcessorTempCriticalProcessor {{cpuName}} temperature sensors in NAS Controller{{nodeId}} report critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.313
fluidFSEventHardwareProcessorVoltageNotAvailableProcessor {{cpuName}} voltage sensor info in NAS Controller{{nodeId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.314
fluidFSEventHardwareProcessorVoltageIsAvailableProcessor {{cpuName}} voltage sensor info in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.315
fluidFSEventHardwareProcessorVoltageWarnProcessor {{cpuName}} voltage sensors in NAS Controller{{nodeId}} report warning status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.316
fluidFSEventHardwareProcessorVoltageNormalProcessor {{cpuName}} voltage sensors in NAS Controller{{nodeId}} report normal status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.317
fluidFSEventHardwareProcessorVoltageCriticalProcessor {{cpuName}} voltage sensors in NAS Controller{{nodeId}} report critical status (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.318
fluidFSEventHardwareProcessorInfoNotAvailableProcessor {{cpuName}} status in NAS Controller{{nodeId}} is not available. Internal error in processor monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.319
fluidFSEventHardwareProcessorInfoIsAvailableProcessor {{cpuName}} status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.320
fluidFSEventHardwareProcessorDisabledProcessor {{cpuName}} in NAS Controller{{nodeId}} is disabled (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.321
fluidFSEventHardwareProcessorEnabledProcessor {{cpuName}} in NAS Controller{{nodeId}} is enabled again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.322
fluidFSEventHardwareMemoryTempNotAvailableMemory device temperature sensors info in NAS Controller{{nodeId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.323
fluidFSEventHardwareMemoryTempIsAvailableMemory device temperature sensors info in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.324
fluidFSEventHardwareBpsErrorBPS on Controller{{nodeId}} (service tag: {{contextBasedServiceTag}}) is not operating properly - battery reports failed state (charge: {{bpsBatteryCharge}}%). Description: BPS on NAS Controller{{nodeId}} (service tag: {{contextBasedServiceTag}}) is not operating properly - battery reports failed state (charge: {{bpsBatteryCharge}}%). This could be the result of a recent calibration process - if you receive this event again after a few days for this specific controller, please contact Support.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.325
fluidFSEventHardwareLocalDiskWearingOutLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}} is wearing out. Consider disk replacement. Overall reads/writes: {{diskOverallReads}} / {{diskOverallWrites}} MB. (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.326
fluidFSEventHardwareLocalDiskLotOfBadSectorsLocal disk {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}} has a lot of bad sectors. Consider disk replacement. Bad sectors count: {{badSectorsCount}} (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.327
fluidFSEventHardwareLocalDiskBadSectorsCountLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}} bad sectors count: {{badSectorsCount}} (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.328
fluidFSEventHardwareLocalDiskLotOfFailedWritesLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}} has a lot of failed writes. Consider disk replacement. Failed writes count: {{failedWritesCount}} (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.329
fluidFSEventHardwareLocalDiskFailedWritesCountLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}} failed writes count: {{failedWritesCount}} (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.330
fluidFSEventHardwareLocalDiskBadS.M.A.R.T. self test is failed for local storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}}. Disk may need a replacement. (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.331
fluidFSEventHardwareLocalDiskBackToNormalLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) in NAS Controller{{nodeId}} returned to normal operation (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.332
fluidFSEventHardwareLocalDiskModelNotSupportedLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) is not supported in NAS Controller{{nodeId}}. Disk monitoring may not work properly. Suppoerted modles are: {{supportedModels}}. (service tag: {{contextBasedServiceTag}})
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.333
fluidFSEventHardwareLocalDiskInfoNotAvailableLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) status in NAS Controller{{nodeId}} is not available. Internal error in local storage monitoring (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.334
fluidFSEventHardwareLocalDiskInfoIsAvailableLocal storage disk drive {{diskName}} (Model: {{diskModel}}; Serial: {{diskSerial}}) status in NAS Controller{{nodeId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.335
fluidFSEventHardwareApplianceIntrusionNotAvailableIntrusion info for NAS Appliance{{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.336
fluidFSEventHardwareApplianceIntrusionIsAvailableIntrusion info for NAS Appliance{{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.337
fluidFSEventHardwareAppPsuAmperageNotAvailableCurrent sensor info in power supply unit {{componentName}} in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.338
fluidFSEventHardwareAppPsuAmperageIsAvailableCurrent sensor info in power supply unit {{componentName}} in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.339
fluidFSEventHardwareAppPsuTempNotAvailableTemperature sensor info in power supply unit {{componentName}} in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.340
fluidFSEventHardwareAppPsuTempIsAvailableTemperature sensor info in power supply unit {{componentName}} in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.341
fluidFSEventHardwareAppPsuVoltageNotAvailableVoltage sensor info in power supply unit {{componentName}} in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.342
fluidFSEventHardwareAppPsuVoltageIsAvailableVoltage sensor info in power supply unit {{componentName}} in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.343
fluidFSEventHardwareAppTopControllerTempNotAvailableTemperature sensor info in top controller in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.344
fluidFSEventHardwareAppTopControllerTempIsAvailableTemperature sensor info in top controller in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.345
fluidFSEventHardwareAppTopControllerTempNormalTemperature sensor in top controller in NAS Appliance {{applianceId}} reports normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.346
fluidFSEventHardwareAppTopControllerTempWarningTemperature sensor in top controller in NAS Appliance {{applianceId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.347
fluidFSEventHardwareAppTopControllerTempErrorTemperature sensor in top controller in NAS Appliance {{applianceId}} reports critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.348
fluidFSEventHardwareAppBottomControllerTempNotAvailableTemperature sensor info in bottom controller in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.349
fluidFSEventHardwareAppBottomControllerTempIsAvailableTemperature sensor info in bottom controller in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.350
fluidFSEventHardwareAppBottomControllerTempNormalTemperature sensor in bottom controller in NAS Appliance {{applianceId}} reports normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.351
fluidFSEventHardwareAppBottomControllerTempWarningTemperature sensor in bottom controller in NAS Appliance {{applianceId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.352
fluidFSEventHardwareAppBottomControllerTempErrorTemperature sensor in bottom controller in NAS Appliance {{applianceId}} reports critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.353
fluidFSEventHardwareAppLeftRaiserCardTempNotAvailableTemperature sensor info in left raiser card in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.354
fluidFSEventHardwareAppLeftRaiserCardTempIsAvailableTemperature sensor info in left raiser card in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.355
fluidFSEventHardwareAppLeftRaiserCardTempNormalTemperature sensor in left raiser card in NAS Appliance {{applianceId}} reports normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.356
fluidFSEventHardwareAppLeftRaiserCardTempWarningTemperature sensor in left raiser card in NAS Appliance {{applianceId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.357
fluidFSEventHardwareAppLeftRaiserCardTempErrorTemperature sensor in left raiser card in NAS Appliance {{applianceId}} reports critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.358
fluidFSEventHardwareAppRightRaiserCardTempNotAvailableTemperature sensor info in right raiser card in NAS Appliance {{applianceId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.359
fluidFSEventHardwareAppRightRaiserCardTempIsAvailableTemperature sensor info in right raiser card in NAS Appliance {{applianceId}} is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.360
fluidFSEventHardwareAppRightRaiserCardTempNormalTemperature sensor in right raiser card in NAS Appliance {{applianceId}} reports normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.361
fluidFSEventHardwareAppRightRaiserCardTempWarningTemperature sensor in right raiser card in NAS Appliance {{applianceId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.362
fluidFSEventHardwareAppRightRaiserCardTempErrorTemperature sensor in right raiser card in NAS Appliance {{applianceId}} reports critical status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.363
fluidFSEventHardwareMotherBoardAmperageNotAvailableNAS Controller{{nodeId}} system board current sensors info is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.364
fluidFSEventHardwareMotherBoardAmperageIsAvailableNAS Controller{{nodeId}} system board current sensors info is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.365
fluidFSEventHardwareMotherBoardTempNotAvailableNAS Controller{{nodeId}} system board temprature sensors info is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.366
fluidFSEventHardwareMotherBoardTempIsAvailableNAS Controller{{nodeId}} system board temprature sensors info is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.367
fluidFSEventHardwareMotherBoardVoltageNotAvailableNAS Controller{{nodeId}} system board voltage sensors info is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.368
fluidFSEventHardwareMotherBoardVoltageIsAvailableNAS Controller{{nodeId}} system board voltage sensors info is available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.369
fluidFSEventHardwareNetworkInterfaceDown{{networkName}} network interface {{ethName}} in NAS Controller{{nodeId}} is down.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.370
fluidFSEventHardwareNetworkInterfaceBackUp{{networkName}} network interface {{ethName}} in NAS Controller{{nodeId}} is back up.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.371
fluidFSEventHardwareNetworkInterfaceUnknown{{networkName}} network interface {{ethName}} in NAS Controller{{nodeId}} has unknown status.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.372
fluidFSEventHardwareFibreChannelPortDownFibre Channel port {{ethName}} in NAS Controller{{nodeId}} is down.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.373
fluidFSEventHardwareFibreChannelPortUpFibre Channel port {{ethName}} in NAS Controller{{nodeId}} is back up.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.374
fluidFSEventHardwareFibreChannelPortUnknownFibre Channel port {{ethName}} in NAS Controller{{nodeId}} has unknown status.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.375
fluidFSEventHardwareSameFcHbaSpeedOnControllerFibre Channel port speeds in NAS Controller{{nodeId}} are identical again.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.376
fluidFSEventHardwareSameEthSpeedOnNetworkNodeEth speeds on {{networkName}} network in NAS Controller{{nodeId}} are identical again.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.377
fluidFSEventHardwareAllIfsAreDownAll {{subnetName}} network interfaces on NAS Controller{{nodeId}} are down.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.378
fluidFSEventHardwareEthSpeedOnSubnetNodeNotEqualEth speeds on {{subnetName}} network in NAS Controller{{nodeId}} are not identical.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.379
fluidFSEventHardwareBpsTempNotAvailableBPS temperature sensor info in NAS Controller{{nodeId}} is not available (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.380
fluidFSEventHardwareBpsTempIsAvailableBPS temperature sensor info in NAS Controller{{nodeId}} is not available again (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.381
fluidFSEventHardwareBpsTempNormalTemperature sensor in BPS in NAS Controller{{nodeId}} reports normal status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.382
fluidFSEventHardwareBpsTempWarningTemperature sensor in BPS in NAS Controller{{nodeId}} reports warning status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.383
fluidFSEventHardwareBpsTempErrorTemperature sensor in BPS in NAS Controller{{nodeId}} reports error status (Ambient temperature: {{temperature}} degrees Celsius) (service tag: {{contextBasedServiceTag}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.384
fluidFSEventHardwarePSUfirmwareUpgradeFailFirmware upgarade for {{id}} failed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.385
fluidFSEventHardwarePSUfirmwareUpgradeSuccessFirmware upgrade for {{id}} finished successfuly
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.386
fluidFSEventHardwareUnsupportedNicUnsupported card installed on Controller{{nodeId}}. Description: An unsupported PCI card was detected in slot {{pciSlot}} on NAS Controller{{nodeId}}: {{pciCard}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.2.387
fluidFSEventsNdmp
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.3
fluidFSEventNdmpNdmpError{{Detail}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.6
fluidFSEventNdmpNdmpWarn{{Detail}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.7
fluidFSEventNdmpNdmpInfo{{Detail}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.8
fluidFSEventNdmpAuthenticationFailureFailed to authenticate: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.9
fluidFSEventNdmpBackupStartedThe backup session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} started. Description: The backup session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} started. The source path is {{Path}} and it is executed on controller {{ExecutedOnNode}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.10
fluidFSEventNdmpBackupFinishedThe backup session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} finished. Description: The backup session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} finished. The source path is {{Path}} and it is executed on controller {{ExecutedOnNode}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.11
fluidFSEventNdmpRestoreStartedThe restore session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} started. Description: The restore session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} started. The target path is {{Path}} and it is executed on controller {{ExecutedOnNode}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.12
fluidFSEventNdmpRestoreFinishedThe restore session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} finished. Description: The restore session by ID {{SessionId}} initiated by DMA {{InitiatorDMAServer}} on {{StartTimestamp}} finished. The target path is {{Path}} and it is executed on controller {{ExecutedOnNode}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.13
fluidFSEventNdmpSessionFailedThe session by ID {{SessionId}} failed: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.14
fluidFSEventNdmpSessionTerminatedThe session by ID {{SessionId}} was terminated: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.15
fluidFSEventNdmpConfigurationValidationErrorFailed to validate configuration: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.16
fluidFSEventNdmpIOErrorIO error: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.17
fluidFSEventNdmpNetworkErrorNetwork error: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.18
fluidFSEventNdmpSnapshotErrorSnapshot error: {{Detail}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.3.19
fluidFSEventsQuota
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.4
fluidFSEventQuotaSystemFreeSpaceThresholdExceededLow system available space. Description: System available space is less than {{systemThreshold}}. Action Items: Add more storage to your system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.7
fluidFSEventQuotaSystemUsedSpaceThresholdExceededSystem usage is higher than {{systemThreshold}}%. Description: System usage is higher than threshold {{systemThreshold}}% of system capacity {{systemCapacity}}. Action Items: Add more storage to your system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.8
fluidFSEventQuotaSystemLeakageBufferThresholdExceededInternal storage reservation is running low. Description: Internal storage reservation is running low. The system capacity is {{systemCapacity}}. Please contact Support.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.10
fluidFSEventQuotaSystemOutOfFreeSpaceSystem is out of available space. Description: System is out of available space. Action Items: Add more storage to your system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.13
fluidFSEventQuotaSystemUsedSpaceOverwhelmedSystem usage reached system capacity of {{systemCapacity}}. Description: System usage reached system capacity of {{systemCapacity}}. Action Items: Add more storage to your system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.14
fluidFSEventQuotaSnapshotThresholdExceededSnapshots space exceeded threshold for NAS volume {{virtualVolumeName}}. Description: NAS volume {{virtualVolumeName}} - Snapshots space exceeded the defined snapshots threshold {{snapshotsSpaceThreshold}}% of the total size {{volumeSize}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.16
fluidFSEventQuotaSnapshotAvailableSpaceBelowThresholdLow space is available for snapshots in NAS Volume {{virtualVolumeName}}. Description: NAS Volume {{virtualVolumeName}} - Space available for snapshots is less than {{snapshotsSpaceThreshold}}% of the total size {{volumeSize}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.17
fluidFSEventQuotaUserQuotaExceededUser soft quota exceeded. User {{userNameName}}, NAS volume {{virtualVolumeName}}. Description: User {{userNameName}} on NAS volume {{virtualVolumeName}} has exceeded its soft limit. Soft limit is {{quotaThreshold}} MB. Action Items: First determine whether this is the outcome of default quota or specific user quota defined for this NAS volume. If there is a fit between the current definition and the required quota enforcement, contact the user and warn him/her that future writes might be denied due to quota violation. If there is a special user requirement, and this is the outcome of a default quota definition, you might consider defining specific user quota for this user.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.18
fluidFSEventQuotaGroupQuotaExceededGroup soft quota exceeded. Group {{groupNameName}}, NAS volume {{virtualVolumeName}}. Description: Group {{groupNameName}} on NAS volume {{virtualVolumeName}} has exceeded its soft limit. Soft limit is {{quotaThreshold}} MB. Action Items: First determine whether this is the outcome of default quota or specific group quota defined for this NAS volume. If there is a fit between the current definition and the required quota enforcement, contact the group manager and warn him/her that future writes might be denied due to quota violation. If there is a special group requirement, and this is the outcome of a default quota definition, you might consider defining specific group quota for this group.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.19
fluidFSEventQuotaVolumeFreeSpaceThresholdExceededAvailable space on NAS volume {{virtualVolumeName}} is running low. Description: NAS volume {{virtualVolumeName}} - Volume available space is less than {{volumeSpaceThreshold}}. Please note that writes to the NAS volume's clones will fail if its base Volume reaches full capacity. Action Items: See if the space shortage is caused by system space shortage or the volume is almost full. If the volume is thick or the shortage is at the volume level, you should consider removing old snapshots, cleanup the volume or increase the volume size. If the volume is thin and it is far from being full, consider removing snapshots and files in other thin volumes that are using unreserved space, purchase more storage and expand LUNs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.20
fluidFSEventQuotaVolumeUsedSpaceThresholdExceededNAS volume {{virtualVolumeName}} exceeded used space threshold. Description: NAS volume {{virtualVolumeName}} - Used space exceeded {{volumeSpaceThreshold}}% of the total size {{volumeSize}}. Please note that writes to the NAS volume's clones will fail if its base volume reaches full capacity.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.21
fluidFSEventQuotaVolumeOutOfFreeSpaceNAS volume {{virtualVolumeName}} is out of available space. Description: NAS volume {{virtualVolumeName}} - Volume is out of available space. Please note that writes to the NAS volume and its clones will fail. Action Items: See if the space shortage is caused by system space shortage or the volume is full. If the volume is thick or the shortage is at the volume level, you should consider removing old snapshots, cleanup the volume or increase the volume size. If the volume is thin and it is far from being full, consider removing snapshots and files in other thin volumes that are using unreserved space, purchase more storage and expand LUNs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.22
fluidFSEventQuotaVolumeUsedSpaceOverwhelmedNAS volume {{virtualVolumeName}} used space reached the volume size (no space). Description: NAS volume {{virtualVolumeName}} - Used space reached the volume size {{volumeSize}}. Please note that writes to the NAS volume and its clones will fail. Action Items: See if the space shortage is caused by system space shortage or the volume is full. If the volume is thick or the shortage is at the volume level, you should consider removing old snapshots, cleanup the volume or increase the volume size. If the volume is thin and it is far from being full, consider removing snapshots and files in other thin volumes that are using unreserved space, purchase more storage and expand LUNs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.23
fluidFSEventQuotaDirectoryQuotaExceededDirectory Quota '{{quotaDirPath}}' in volume {{virtualVolumeName}} exceeded the soft limit Description: Directory Quota '{{quotaDirPath}}' in volume {{virtualVolumeName}} exceeded the soft limit of {{quotaThreshold}} MB. Action Items: Advise the users to clear some space from the directory or consider extending the quota limit.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.4.24
fluidFSEventsReplication
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.5
fluidFSEventReplicationDisconnectionReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The connection between source and destination systems was lost. The replication will continue automatically when the connection is restored.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.14
fluidFSEventReplicationInternalErrorReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: There was an internal error (err: {{errorCode}}), please contact Support.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.15
fluidFSEventReplicationSourceFSIsDownReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The file system of source NAS volume is down. The replication will continue automatically when the file-system is started.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.16
fluidFSEventReplicationSourceFSIsNotOptimalReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The file-system of the source NAS volume is not optimal. The replication will continue automatically when the file-system recovers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.17
fluidFSEventReplicationDestinationFSIsNotOptimalReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The file-system of the destination NAS volume is not optimal. The replication will continue automatically when the file-system recovers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.18
fluidFSEventReplicationDestinationFSIsDownReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The file system of destination NAS volume is down. The replication will continue automatically when the file-system is started.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.19
fluidFSEventReplicationConfigurationErrorReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The source and destination systems resources are not balanced. Please consider to add new applience to the destination system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.20
fluidFSEventReplicationMngConVipChangedCluster VIP {{oldMngConVip}} was changed to {{newMngConVip}}. Please update partnership systems with this change.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.26
fluidFSEventReplicationMngConVipChangedDestinationManage console VIP {{oldMngConVip}} was changed to {{newMngConVip}}. Please, update partnership systems with this change.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.49
fluidFSEventReplicationDestinationVolumeIsDetachedReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The destination NAS volume disconnected from the source NAS volume. Please perform the disconnect action also from the source NAS volume, and if you would like, reconnect the NAS volumes again to allow replication.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.55
fluidFSEventReplicationDestinationClusterIsBusyReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: Temporarily the destination cluster is not available to serve the required replication.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.56
fluidFSEventReplicationIncompatibleVersionsReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The system version of source NAS volume is higher than the system version of the destination system. Please upgrade the destination system to same version as source system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.57
fluidFSEventReplicationNotEnoughSpaceInDestinationReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: There is not enough space in the destination NAS volume. Please increase the destination NAS volume size.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.58
fluidFSEventReplicationSourceVolumeBusyWithReclaimingReplication between {{sourceVolumeName}}@{{sourceCluster}} and {{destinationVolume}}@{{destinationCluster}} experienced a temporary failure. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} experienced a temporary failure because of the following reason: The source NAS volume is busy freeing space. The replication will continue automatically when space is available.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.59
fluidFSEventReplicationDestinationVolumeBusyWithReclaimingReplication between {{sourceVolumeName}}@{{sourceCluster}} and {{destinationVolume}}@{{destinationCluster}} experienced a temporary failure. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} experienced a temporary failure because of the following reason: The destination NAS volume is busy freeing space. The replication will continue automatically when space is available.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.60
fluidFSEventReplicationSourceFSIsBusyReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The file-system of the source NAS volume is busy with replication of other NAS volumes. The replication will continue automatically when the file-system releases part of the resources.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.61
fluidFSEventReplicationDestinationFSIsBusyReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The file-system of the destination NAS volume is busy with replication of other NAS volumes. The replication will continue automatically when the file-system releases part of the resources.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.62
fluidFSEventReplicationJumboFramesBlockedReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: Jumbo frames are blocked over the network.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.63
fluidFSEventReplicationRecoveredReplicationReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} finished. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} successfully recovered from the problem and finished.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.64
fluidFSEventReplicationDestinationVolumeShrinkReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} succeeded. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} succeeded but resizing of the destination volume failed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.65
fluidFSEventReplicationDestinationVolumeIsDisabledReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The replication policy status on the destination volume is currently promoted. Please perform the promote action also from the source NAS volume, and demote to allow replication.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.66
fluidFSEventReplicationDestinationVolumeDedupParamsOptimization policy configuration is not updated. Description: As part of replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} the optimization policy configuration has failed to update.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.67
fluidFSEventReplicationRollbackSnapCloneBaseReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: rollback snapshot failed due to clone snapshot base.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.68
fluidFSEventReplicationReplicationFinishedReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} finished. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} which start at {{startTime}} has transferred {{totalTransferredSize}} MB of data and finished successfully at {{endTime}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.69
fluidFSEventReplicationDisconnectionDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The connection between source and destination systems was lost. The replication will continue automatically when the connection is restored.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.70
fluidFSEventReplicationInternalErrorDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: There was an internal error (err: {{errorCode}}), please contact the support team
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.71
fluidFSEventReplicationSourceFSIsDownDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The file system of source NAS volume is down. The replication will continue automatically when the file-system is started.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.72
fluidFSEventReplicationSourceFSIsNotOptimalDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The file-system of the source NAS volume is not optimal. The replication will continue automatically when the file-system recovers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.73
fluidFSEventReplicationDestinationFSIsNotOptimalDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The file-system of the destination NAS volume is not optimal. The replication will continue automatically when the file-system recovers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.74
fluidFSEventReplicationDestinationFSIsDownDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The file system of destination NAS volume is down. The replication will continue automatically when the file-system is started.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.75
fluidFSEventReplicationConfigurationErrorDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The source and destination systems resources are not balanced. Please consider to add new applience to the destination system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.76
fluidFSEventReplicationDestinationVolumeIsDetachedDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The destination NAS volume disconnected from the source NAS volume, please perform the disconnect action also from the source NAS volume and if you would like reconnect the NAS volumes again.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.77
fluidFSEventReplicationDestinationClusterIsBusyDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: Temporarily the destination cluster is not available to serve the required replication.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.78
fluidFSEventReplicationIncompatibleVersionsDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The system version of source NAS volume is higher than the system version of the destination system. Please upgrade the destination system to same version as source system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.79
fluidFSEventReplicationNotEnoughSpaceInDestinationDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: There is not enough space in the destination NAS volume, Please increase the destination NAS volume size.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.80
fluidFSEventReplicationSourceVolumeBusyWithReclaimingDestinationReplication between {{sourceVolume}}@{{sourceCluster}} and {{destinationVolumeName}}@{{destinationCluster}} experienced a temporary failure Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} experienced a temporary failure because of the following reason: The source NAS volume is busy freeing space. The replication will continue automatically when space is available.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.81
fluidFSEventReplicationDestinationVolumeBusyWithReclaimingDestinationReplication between {{sourceVolume}}@{{sourceCluster}} and {{destinationVolumeName}}@{{destinationCluster}} experienced a temporary failure Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} experienced a temporary failure because of the following reason: The destination NAS volume is busy freeing space. The replication will continue automatically when space is available.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.82
fluidFSEventReplicationSourceFSIsBusyDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The file-system of the source NAS volume is busy with replication of other NAS volumes. The replication will continue automatically when the file-system releases part of the resources .
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.83
fluidFSEventReplicationDestinationFSIsBusyDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The file-system of the destination NAS volume does not have enough resources to proceed with replication of other NAS volumes. The replication will continue automatically when the file-system releases part of the resources.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.84
fluidFSEventReplicationJumboFramesBlockedDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: Jumbo frames are blocked over the network.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.85
fluidFSEventReplicationRecoveredReplicationDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} finished. Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} successfully recovered from the problem and finished.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.86
fluidFSEventReplicationDestinationVolumeShrinkDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} succeeded Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} succeeded but resizing of the desination volume failed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.87
fluidFSEventReplicationDestinationVolumeIsDisabledDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The replication policy status on the destination volume is currently promoted, please perform the promote action also from the source NAS volume, and demote allow replication.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.88
fluidFSEventReplicationDestinationVolumeDedupParamsDestinationOptimization policy configuration is not updated Description: As part of replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} the optimization policy configuration has failed to update.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.89
fluidFSEventReplicationRollbackSnapCloneBaseDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: rollback snapshot failed due to clone snapshot base.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.90
fluidFSEventReplicationReplicationFinishedDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} finished. Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} which start at {{startTime}} has transferred {{totalTransferredSize}} MB of data and finished successfully at {{endTime}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.91
fluidFSEventReplicationNotEnoughSpaceInDestinationRehydSrcVolSizeReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: There is not enough space in the destination NAS volume. Please increase the destination NAS volume size to be at least {{rehydratedVolumeSize}} MBs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.92
fluidFSEventReplicationReplicationFinishedInDomainReplication {{sourceVolumeName}}, {{destinationVolume}}@{{destinationCluster}} finished in domain {{domainId}} s-{{snapshotId}}. Description: Replication {{sourceVolumeName}}, {{destinationVolume}}@{{destinationCluster}} finished in domain {{domainId}} s-{{snapshotId}}. {{domainReplicationStats}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.93
fluidFSEventReplicationDestinationVolumeIsReplicatingReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} failed because of the following reason: The destination NAS volume is in the middle of replicating to another NAS volume. Please temporarily disable the outgoing replications from the destination NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.94
fluidFSEventReplicationDestinationVolumeIsReplicatingDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed. Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} failed because of the following reason: The destination NAS volume is in the middle of replicating to another NAS volume. Please temporarily disable the outgoing replications from the destination NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.95
fluidFSEventReplicationReplicationFinishedWithCompressionReplication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} finished. Description: Replication between NAS volume {{sourceVolumeName}}@{{sourceCluster}} and NAS volume {{destinationVolume}}@{{destinationCluster}} which start at {{startTime}} has transferred {{totalTransferredSize}} MB of data with {{savingsPercent}}% savings due to data reduction and finished successfully at {{endTime}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.96
fluidFSEventReplicationReplicationFinishedWithCompressionDestinationReplication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} finished. Description: Replication between NAS volume {{sourceVolume}}@{{sourceCluster}} and NAS volume {{destinationVolumeName}}@{{destinationCluster}} which start at {{startTime}} has transferred {{totalTransferredSize}} MB of data with {{savingsPercent}}% savings due to data reduction and finished successfully at {{endTime}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.5.97
fluidFSEventsSnapshot
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.7
fluidFSEventSnapshotFailedCreateSnapshotThe snapshot scheduler failed to create {{snapshotName}} snapshot in volume {{volumeName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.1
fluidFSEventSnapshotFailedDeleteSnapshotThe snapshot scheduler failed to delete snapshots in volume {{volumeName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.2
fluidFSEventSnapshotScheduleDeleteSnapshotBySpaceThe snapshot named {{snapshotName}} on {{volumeName}} NAS volume was scheduled for deletion by snapshots space auto-deletion mechanism.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.3
fluidFSEventSnapshotFailedToInitVMSnapshotsCreationFailed initializing the VM snapshot(s) creation Description: Failed to initiate VM snapshot(s) creation on VMWare server(s), thus {{snapshotName}} snapshot of {{FSIDName}} NAS volume will not be consistent from VMWare perspective Action Items: Please check network availability and current load on related VMWare server(s) Internal Information: One (or more) VMWare servers may be unavailable or responds with errors to FluidFS requests
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.8
fluidFSEventSnapshotFailedToPerformVMSnapshotsCreationFailed to create VM snapshot(s) on VMWare server(s) Description: Failed to create VM snapshot(s), thus {{snapshotName}} snapshot of {{FSIDName}} NAS volume will not be consistent from VMWare perspective Action Items: Please check network availability and current load on related VMWare server(s) Internal Information: One (or more) VMWare servers may be unavailable or responds with errors to FluidFS requests
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.9
fluidFSEventSnapshotFailedToPerformVMSnapshotsCleanupFailed removing the VM snapshot(s), created by FluidFS Description: Failed to perform a cleanup of VM snapshot(s), previously created by FluidFS on VMWare server(s) during {{snapshotName}} snapshot of {{FSIDName}} NAS volume creation Action Items: Please check network availability and current load on related VMWare server(s). Try to delete the redundant VM snapshot(s) manually in the vSphere user interface Internal Information: One (or more) VMWare servers may be unavailable or responds with errors to FluidFS requests
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.10
fluidFSEventSnapshotSnapshotIsNotVMConsistentThe {{snapshotName}} snapshot is not consistent from VMWare perspective Description: NAS volume {{FSIDName}} had been restored to the {{snapshotName}} snapshot recovery point, which is not consistent from VMWare perspective Action Items: In case {{FSIDName}} NAS volume indeed serves as VMWare Datastore, please try to restore the volume to a consistent snapshot recovery point
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.11
fluidFSEventSnapshotSnapshotDeltaFailedSnapshot delta process on volume {{FSIDName}} failed Description: NAS volume {{FSIDName}} did not finish properly and therefore aborted Action Items: Please restart the process
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.12
fluidFSEventSnapshotSnapshotDeltaSuccededSnapshot delta process on volume {{FSIDName}} succeded Description: NAS volume {{FSIDName}} has finished properly and file {{outputFileName}} was created in path {{outputPath}} on volume {{outputFSIDName}} Action Items: file {{outputFileName}} was created in path {{outputPath}} on volume {{outputFSIDName}} and is available now for reading
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.13
fluidFSEventSnapshotSnapshotDeltaStartedSnapshot delta process on volume {{FSIDName}} started Description: NAS volume {{FSIDName}} has started with output file {{outputFileName}} in path {{outputPath}} on volume {{outputFSIDName}} Action Items: file {{outputFileName}} will be created in path {{outputPath}} on volume {{outputFSIDName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.7.14
fluidFSEventsHealth
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.9
fluidFSEventHealthNodeFailedNAS controller {{nodeName}} is unavailable.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.4
fluidFSEventHealthNodeOKNAS controller {{nodeName}} is available.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.5
fluidFSEventHealthLocalPartitionIsFullThe used space of local file system partition {{partitionName}} on NAS controller {{nodeName}} is high ({{percentOfUsedSpace}}%). Please contact support.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.6
fluidFSEventHealthHighUseOfSwapThe usage of swap memory on NAS controller {{nodeName}} is high ({{percentOfUsedSwap}}%).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.7
fluidFSEventHealthHighUseOfMemoryThe memory usage on NAS controller {{nodeName}} is high.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.8
fluidFSEventHealthHighUseOfFileDescriptorsFile descriptors usage on NAS controller {{nodeName}} is high ({{percentOfUsedFileDescriptors}}%).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.9
fluidFSEventHealthPairPowerProblemThe system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} BPS is not functioning properly and its peer controller {{peerNodeId}} has health problems as well. Switched Write-Through mode on (journaling).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.10
fluidFSEventHealthPairPowerProblemRecoveredThe system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} verified the power system reliability and switched Write-Through mode off (mirroring).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.11
fluidFSEventHealthSafeShutdownBeginsThe 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 flushed and will orderly shut down in approximately 5 minutes. Please allow it to finish. Action Items: If this process takes longer than expected, don't try to workaround by manually shutting down the NAS controller. Please contact Support.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.12
fluidFSEventHealthSafeShutdownEndsNAS controller {{thisNodeId}} cache was flushed and it is shutting down.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.13
fluidFSEventHealthPairTemperatureProblemThe system switched Write-Through mode on (journaling). Description: The system switched Write-Through mode on (journaling) because both NAS controllers' temperature appears high (or cannot be verified), on the controller pair with IDS {{thisNodeId}} and {{peerNodeId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.14
fluidFSEventHealthPairTemperatureProblemRecoveredThe system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} verified the temperature system reliability and switched Write-Through mode off (mirroring).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.15
fluidFSEventHealthClientsOnFailbackThere are clients ({{numberOfClients}}) that are waiting for manual failback.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.16
fluidFSEventHealthCacheLossOfUserFilesLatest 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 two NAS controllers in the same NAS appliance simultaneously. The system will start an automatic recovery procedure and in few minutes you should receive a completion event. During that time you will have partial or no service, SMB clients will be disconnected and NFS clients will be forced to remount. After the system is fully functional, please check your applications integrity and repeat the latest writes if needed. Action Items: In case repeating the latest writes is not possible or you still experience any difficulties, consider recovering the data from the latest snapshots or from backup. Internal Information: Domain {{domainId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.21
fluidFSEventHealthCacheLossOfMetadataFile 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 provide limited service. Please contact Support for further assistance. Action Items: Search product Knowledge Base for further information. Internal Information: Domain {{domainId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.22
fluidFSEventHealthCacheLossRecoveredFile system recovery successfully finished. Description: File system recovery successfully finished. Action Items: Data written in the day prior to the event might be compromised and should be verified.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.23
fluidFSEventHealthStoreAccessProblemLost 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}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.24
fluidFSEventHealthLunVerificationFailureNAS controller {{nodeId}} encountered a problem accessing a NAS storage pool. Action Items: Please contact Support. Internal Information: Domain {{domainId}} LUN {{lunId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.25
fluidFSEventHealthFileSystemMajorAccessibilityProblemClients 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. Action Items: The NAS file system constantly verifies that it is accessible for read/write operations. This event is issued once it identifies that some operations took more time than expected or failed completely in the last {{timeout}} minutes. This could be caused by an intermittent issue of a HW failure like failed disk or disconnected network port. Verify that no RAID is being rebuilt and you do not have a recently failed drive. Verify that the cluster is connected according to the recommended cabling method and switch configuration.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.27
fluidFSEventHealthFileSystemAccessibilityRevivalFile system back to optimal state. Description: The File System has overcome its accessibility problem and returned back to full functionality.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.28
fluidFSEventHealthFSMultipleRmapChecksumErrorMultiple erroneous file system blocks were identified and fixed. Action Items: If the problem recurs, verify system hardware health.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.47
fluidFSEventHealthFSSystemUnrecoverableRmapChecksumErrorUnrecoverable erroneous block was identified. Description: Unrecoverable erroneous block was identified. The file system is partially serving. Action Items: Contact Support. Internal Information: File {{dsid}} mapping {{fileMapping}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.48
fluidFSEventHealthFSMultipleUserMetaDataMissingMultiple directory entries were identified as missing. Action Items: Recover them from backup.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.50
fluidFSEventHealthFSLowOnLunSpaceHigh NAS pool capacity. Performance might be affected. Description: NAS pool capacity usage has reached high watermark which will affect performance. Action Items: Expand the NAS pool capacity, or free some space.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.53
fluidFSEventHealthBadClientLoadBalancingBad {{protocol}} clients distribution: ({{connectionsVector}}). Description: Bad {{protocol}} clients distribution: ({{connectionsVector}}). Each pair in this set represents NAS controller ID and number of connections separated by a colon. Use the mass rebalance feature available via the clients connections screen.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.65
fluidFSEventHealthCifsLockingInconsistancyInconsistent locks interrupted SMB service. Description: SMB service is interrupted due to inconsistencies in locking mechanism, starting recovery process. Internal Information: Domain {{domainId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.66
fluidFSEventHealthCifsLockingInconsistancyRecoveredInconsistent locks recovered. Description: SMB locking inconsistencies recovery was successfully finished.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.67
fluidFSEventHealthFSReclaimerOverloadHigh 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 be the result of the deletion of a NAS volume and/or multiple snapshots. Action Items: If this event recurs on a daily basis, the file system performance can be improved; Reducing the frequency of snapshot scheduling will make more resources available for clients activity. Internal Information: Domain {{domainId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.72
fluidFSEventHealthPairStoreSetProblemSystem switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} has lost connection to storage subsystem and its peer NAS controller {{peerNodeId}} has health problems as well. Switched Write-Through mode on (journaling).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.75
fluidFSEventHealthPairStoreSetProblemRecoveredSystem switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} verified connection to storage subsystem and switched Write-Through mode off (mirroring).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.76
fluidFSEventHealthPairPowerSuppliesProblemThe system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} has lost full power supplies redundancy and its peer NAS controller {{peerNodeId}} has health problems as well. Switched Write-Through mode on (journaling).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.77
fluidFSEventHealthPairPowerSuppliesRecoveredThe system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} full power supplies redundancy was restored and switched Write-Through mode off (mirroring).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.78
fluidFSEventHealthPairFansProblemThe system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} fans are not working properly and its peer NAS controller {{peerNodeId}} has health problems as well. Switched Write-Through mode on (journaling).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.85
fluidFSEventHealthPairFansRecoveredThe system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} fans are working properly. Switched Write-Through mode off (mirroring).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.86
fluidFSEventHealthProtocolsStateInconsistancyInconsistent state interrupted SMB/NFSv4 service. Description: SMB/NFSv4 services are interrupted due to inconsistencies in locking mechanism, starting recovery process. Internal Information: Domain {{domainId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.87
fluidFSEventHealthProtocolsStateInconsistancyRecoveredInconsistent locks recovered. Description: SMB/NFSv4 locking inconsistencies recovery was successfully finished.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.88
fluidFSEventHealthFSDedupSpaceMarginReachedOptimization paused on volume {{virtualVolume}} - insufficient space. Description: Volume {{virtualVolume}} doesn't have the required free {{dedupSpaceMarginMb}} MB needed for optimization. Action Items: Make sure volume {{virtualVolume}} has at least {{dedupSpaceMarginMb}} MB free.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.91
fluidFSEventHealthStoreAccessRestoredRestored communication to storage from NAS controller {{nodeId}}. Description: The system identified that a communication problem between NAS controller {{nodeId}} and the storage controllers was resolved. Internal Information: Domain {{domainId}} setId {{setId}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.92
fluidFSEventHealthDuplicateIpDuplicate 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 with mac address {{macAddr}}. Action Items: Either change the address {{ipAddr}} on node {{nodeId}}, or on the other device.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.102
fluidFSEventHealthUnmapIsNotSupportedOnLunsUnmap 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 the listed LUNs to the newest version.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.103
fluidFSEventHealthPairHWProblemThe system switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} hardware is not working properly and its peer NAS controller {{peerNodeId}} has health problems as well. Switched Write-Through mode on (journaling).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.110
fluidFSEventHealthPairHWRecoveredThe system switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} hardware is working properly. Switched Write-Through mode off (mirroring).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.111
fluidFSEventHealthUnresponsiveVmwareServerOnAllNodesVMWare service is unavailable on all NAS-Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.112
fluidFSEventHealthUnresponsiveVmwareServerOnNodesVMWare service is unavailable on all NAS-Controllers {{nodeIds}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.113
fluidFSEventHealthResponsiveVmwareServerOnAllNodesVMWare service is available on all NAS-Controlles
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.114
fluidFSEventHealthCouldNotAllocateProtectedMemoryProblem with allocating protected memory Description: Memory detector could not allocate the protected memory Action Items: Please contact support
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.115
fluidFSEventHealthInvalidSizeOfProtectedMemoryProblem with allocating protected memory Description: The model's predefined size of protected memory is not equal to allocated Action Items: Please contact support
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.116
fluidFSEventHealthCouldNotAllocateUnProtectedMemoryProblem with allocating unprotected memory Description: Preallocation script could not allocate the unprotected memory Action Items: Please contact support
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.117
fluidFSEventHealthUnresponsiveIscsiPortalsOnAllNodesiSCSI portals are unavailable on all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.118
fluidFSEventHealthUnresponsiveIscsiPortalsOnNodesiSCSI portals are unavailable on NAS Controllers {{nodeIds}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.119
fluidFSEventHealthResponsiveIscsiPortalsOnAllNodesiSCSI portals are available on all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.120
fluidFSEventHealthUnavailableNtpServiceOnAllNodesNTP service is unavailable on all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.121
fluidFSEventHealthAvailableNtpServiceOnAllNodesNTP service become available on all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.122
fluidFSEventHealthUnavailableNtpServiceOnNodesNTP service is unavailable on NAS Controllers {{nodeIds}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.123
fluidFSEventHealthUnavailableAntivirusOnAllNodesAntivirus is unavailable on all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.124
fluidFSEventHealthAvailableAntivirusOnAllNodesAntivirus become available on all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.125
fluidFSEventHealthUnavailableAntivirusOnNodesAntivirus is unavailable on NAS Controllers {{nodeIds}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.126
fluidFSEventHealthUnavailableAuditingServicesOnAllNodesAuditing subscribers became unavailable for all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.127
fluidFSEventHealthAvailableAuditingServicesOnAllNodesAuditing subscribers became available for all NAS Controllers
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.128
fluidFSEventHealthUnavailableAuditingServicesOnNodesAuditing subscribers became unavailable for NAS Controller/s: {{nodeIds}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.129
fluidFSEventHealthPairCacheArmingProblemSystem switched Write-Through mode on (journaling). Description: NAS controller {{thisNodeId}} has problems with arming the protected memory, as well as it's peer. Switched Write-Through mode on (journaling).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.130
fluidFSEventHealthPairCacheArmingProblemRecoveredSystem switched Write-Through mode off (mirroring). Description: NAS controller {{thisNodeId}} succeeded arming the protected memory, and switched Write-Through mode off (mirroring) .
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.131
fluidFSEventHealthCouldNotArmProtectedMemoryRegionProblem with arming of protected memory regions Description: Memory detector could not arm protected memory region Action Items: Please contact support
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.132
fluidFSEventHealthFSUserMetaDataMissingDirectory entry was identified as missing; Entry {{dirEntry}} in {{parentDirDsidPath}}. Action Items: Recover it from backup. Internal Information: File {{dsid}} volume {{FSIDName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.133
fluidFSEventHealthUnresponsiveLdapServersOnAllNodesLDAP servers, used by {{TenantName}}, are not responding. Description: All LDAP servers ({{serverNames}}), used by {{TenantName}}, are not responding on all NAS Controllers. For each server please check: its server logs for any event that caused it not to respond to requests; that it responds to ping requests from clients on the same subnetwork; that it responds to LDAP requests from clients on the same subnetwork.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.134
fluidFSEventHealthUnresponsiveLdapServersOnSomeNodesAll LDAP servers ({{serverNames}}), used by {{TenantName}}, are unresponsive on some NAS Controllers: {{nodeIds}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.135
fluidFSEventHealthResponsiveLdapServerOnAllNodesFound responsive LDAP server(s) among ({{serverNames}}), used by {{TenantName}}, on all NAS Controllers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.136
fluidFSEventHealthUnresponsiveNisServersOnAllNodesNIS servers, used by {{TenantName}}, are not responding. Description: All NIS servers ({{serverNames}}), used by {{TenantName}}, are not responding on all NAS Controllers. For each server please check: its server logs for any event that caused it not to respond to requests; that it responds to ping requests from clients on the same subnetwork; that it responds to NIS requests from clients on the same subnetwork.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.137
fluidFSEventHealthResponsiveNisServerOnAllNodesFound responsive NIS server(s) among ({{serverNames}}), used by {{TenantName}}, on all NAS Controllers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.138
fluidFSEventHealthUnresponsiveNisServersOnSomeNodesAll NIS servers ({{serverNames}}), used by {{TenantName}}, are unresponsive on some NAS Controllers: {{nodeIds}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.139
fluidFSEventHealthUnresponsiveDnsServersOnAllNodesDNS servers, used by {{TenantName}}, are not responding. Description: All DNS servers ({{serverIps}}), used by {{TenantName}}, are not responding on all NAS Controllers. For each server please check: its server logs for any event that caused it not to respond to requests; that it responds to ping requests from clients on the same subnetwork; that it responds to DNS requests from clients on the same subnetwork.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.140
fluidFSEventHealthResponsiveDnsServerOnAllNodesFound responsive DNS server(s) among ({{serverIps}}), used by {{TenantName}}, on all NAS Controllers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.141
fluidFSEventHealthUnresponsiveDnsServersOnSomeNodesAll DNS servers ({{serverIps}}), used by {{TenantName}}, are unresponsive on some NAS Controllers: {{nodeIds}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.142
fluidFSEventHealthUnresponsiveAdServerActive Directory, used by {{TenantName}}, is not responsive. Description: Active Directory domain {{domainName}}, used by {{TenantName}}, is not reachable. For each domain controller please check: its logs for any event that caused it not to respond to requests; that it responds to ping requests from clients on the same subnetwork; that it responds to AD requests from clients on the same subnetwork.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.143
fluidFSEventHealthResponsiveAdServerActive Directory domain {{domainName}}, used by {{TenantName}}, is reachable.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.144
fluidFSEventHealthSlowResponseSlow response time from {{serverKind}} to {{TenantName}}. Description: Response time from {{serverKind}} servers ({{serverList}}) of {{responseTime}} seconds exceeds {{criticalResponseTime}} seconds on {{TenantName}}. Action Items: Check availability of all {{serverKind}} servers. This error is usually the outcome of a communication error between the NAS and the external server. It could be caused by a network issue, external server overload or a software malfunction in one of environment components. Internal Information: {{internalInfo}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.145
fluidFSEventHealthAdCriticalClockSkewAD (used by {{TenantName}}) and NAS controller {{nodeId}} clocks aren't synchronized Description: Clock of NAS controller {{nodeId}} and AD clock, used by {{TenantName}} (domain {{DomainControllerName}}), are not synchronized (skew of {{adClockSkew}} seconds exceeds critical threshold of {{maxAdClockSkew}} seconds). Kerberos authentication may fail. Fix system clock/Fix AD clock. Enter the time configuration screen and get the configured NTP host. If no NTP is configured, it is recommended to configure one by either using the organization's NTP or the same IP/name used for joining the NAS to the AD.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.146
fluidFSEventHealthCIFSAttachedACLCorruptionFailed 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-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.147
fluidFSEventHealthFSUserUnrecoverableRmapChecksumErrorUnrecoverable erroneous block in user file. Description: Unrecoverable erroneous block was identified in {{dsidPath}} and it is inaccessible. Action Items: Move this file/directory to a different name, and recover it from backup. Internal Information: Mapping {{fileMapping}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.149
fluidFSEventHealthFSVolumeUnrecoverableRmapChecksumErrorNAS Volume {{FSIDName}} is partially serving. Description: Unrecoverable erroneous block was identified in volume {{FSIDName}}. This volume is partially serving. Action Items: Run the file system diagnostics and contact Support. Internal Information: File {{dsid}} mapping {{fileMapping}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.150
fluidFSEventHealthFSRehydrationSpaceMarginReachedRehydration paused on volume {{FSIDName}} - insufficient space. Description: Volume {{FSIDName}} doesn't have the required free {{dedupSpaceMarginMb}} MB needed for rehydration. Action Items: Make sure volume {{FSIDName}} has at least {{dedupSpaceMarginMb}} MB free.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.151
fluidFSEventHealthFSLowOnLunSpaceDedupPostponedHigh 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: Please perform one of the following actions to increase NAS pool free space : expand your NAS pool; Delete old Snapshots; Delete redundant NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.154
fluidFSEventHealthFSLowOnLunSpaceDedupResumedData Reduction resumed on cluster. Description: NAS pool free space increased. Data reduction is resumed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.155
fluidFSEventHealthFSLowOnLunSpaceFSNotAccessibleHigh 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 of the following actions to increase NAS pool free space : expand your NAS pool; Delete old Snapshots; Delete redundant NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.156
fluidFSEventHealthFSLowOnLunSpaceFSAccessibleFile system access is back to normal. Description: NAS pool free space increased. File system can be accessed by all protocols
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.157
fluidFSEventHealthLocalTimeDesynchronizedToNtpLocal time on node {{nodeId}} is desynchronized by {{timeDiffSec}} seconds.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.9.158
fluidFSEventsAntivirus
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.10
fluidFSEventAntivirusAntivirusHostUpAntivirus host {{host}}:{{port}} accessibility is restored. Description: Antivirus host {{host}}:{{port}} accessibility is restored.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.16
fluidFSEventAntivirusAntivirusHostDownAntivirus host {{host}}:{{port}} is not accessible. Description: Antivirus host {{host}}:{{port}} is not accessible.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.17
fluidFSEventAntivirusAntivirusLicenseErrorAntivirus host {{host}}:{{port}} returns license error. Description: Antivirus host {{host}}:{{port}} returns license error.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.18
fluidFSEventAntivirusAntivirusAllDownNo antivirus hosts are accessible. Description: No antivirus hosts are accessible. Virus scanning is not possible. SMB Shares with AV scan configured will not be accessible.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.19
fluidFSEventAntivirusAntivirusServersNotConfiguredAntiVirus servers are not configured. Description: SMB share {{shareName}} is configured to use antivirus checking but no AV servers are configured yet. Access to the files inside the share is denied. Action Items: AntiVirus servers must be configured to provide AntiVirus facility
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.27
fluidFSEventAntivirusAntivirusScanWasTooLong2Antivirus scan for file {{FSIDName}}/{{dsidPath}} took too long Description: Scanning for viruses for file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}} took too long: {{scanningDuration}} seconds (must be less than {{scanningDurationThreshold}}), scanning facility '{{scanningFacility}}'. Action Items: Please check network availability and current load on problematic AntiVirus facility.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.31
fluidFSEventAntivirusAccessDeniedVirus was found in file {{FSIDName}}/{{dsidPath}} but quarantine is not applicable. Description: Virus ({{virusDescription}}) was found in file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Quarantine action is not possible for this file, access to file is denied. Internal Information: Reason why quarantine action is not possible: {{accessDeniedReason}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.32
fluidFSEventAntivirusAccessDeniedDueInternalErrorAn error occurred while scanning the file {{FSIDName}}/{{dsidPath}} for viruses. Description: An error occurred during AV scan of the file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Access to file is denied. Internal Information: Error details: {{accessDeniedReason}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.33
fluidFSEventAntivirusUnexpectedAvResponseError occurred while scanning for viruses. Description: AV server returned unexpected error during the scan for file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Access is denied. Internal Information: ICAP protocol issue: unexpected ICAP status code {{icapStatus}} returned by facility {{server}}:{{port}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.34
fluidFSEventAntivirusQuarantineActionFailedVirus was found in file {{FSIDName}}/{{dsidPath}} but quarantine action has failed. Description: Virus ({{virusDescription}}) was found in file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. Quarantine action failed for this file, access to file is denied. Internal Information: Quarantine action error details: {{accessDeniedReason}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.35
fluidFSEventAntivirusInfectedFileQuarantined2Virus was found in file {{FSIDName}}/{{filePath}}, quarantine action is applied. Description: Virus ({{virusDescription}}) was found in file {{filePath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. File is moved to quarantine (new path is {{dsidPath}}).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.36
fluidFSEventAntivirusInfectedFileRepairedInfected file {{FSIDName}}/{{dsidPath}} was repaired. Description: Virus ({{virusDescription}}) was found in file {{dsidPath}} on NAS volume {{FSIDName}} accessed via SMB share {{shareName}}. The file was repaired automatically.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.37
fluidFSEventAntivirusAccessDeniedLargeFileNotScannedAccess denied: file {{FSIDName}}/{{dsidPath}} is too large for AV verification. Description: File {{dsidPath}} (which is {{fileSizeMb}} MB) on NAS volume {{FSIDName}} accessed via SMB share {{shareName}} cannot be scanned for viruses because it exceeds the maximum scan size ({{largeFileSizeLimitMb}} Mb). This share is configured to block access to un-scanned files. Action Items: Increase the maximum scan size for AV scanning or change the policy to allow un-scanned files for access. Please note, Anti-virus scan of large files may delay the initial open request.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.38
fluidFSEventAntivirusLargeFileNotScannedAccess allowed: file {{FSIDName}}/{{dsidPath}} was opened without AV verification. Description: File {{dsidPath}} (which is {{fileSizeMb}} MB) on NAS volume {{FSIDName}} accessed via SMB share {{shareName}} was not scanned for viruses because it exceeds the maximum scan size ({{largeFileSizeLimitMb}} MB). Action Items: Increase the maximum file size for AV scan or change the policy to deny un-scanned files for access. Please note, Anti-virus scan of large files may delay the initial open request.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.10.39
fluidFSEventsClientAccess
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.11
fluidFSEventClientAccessMountFailureInternalErrorNFS mount failure. Internal mount error {{mountPath}}. Description: NFS mount failure: Internal mount error for the client {{clientIpAddr}} while mounting path {{mountPath}}. Internal Information: NFS error code: {{nfsErrorCode}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.6
fluidFSEventClientAccessResetAdminPasswordFromConsoleAdministrator password was reset from the console. Description: Administrator password was reset from the console.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.51
fluidFSEventClientAccessSMBMemThreshold1Due to SMB high resource usage disabling Large MTU. Description: Due to SMB high resource usage disabling Large MTU on NAS controller {{nasControllerId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.54
fluidFSEventClientAccessSMBMemThreshold2Due to SMB high resource usage new connections not allowed. Description: Due to SMB high resource usage new connections are not allowed on NAS controller {{nasControllerId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.55
fluidFSEventClientAccessLockDBOutOfResourcesFile open or lock denied due to lack of internal resources. Description: NAS controller {{nodeId}} is low on resources and cannot serve SMB and NFSv4 file open and lock requests. Disconnect existing connections to free resources.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.58
fluidFSEventClientAccessSessionDBOutOfResourcesNFSv4 session was denied. Too many sessions currently in use Description: No resources available for new NFSv4 sessions as too many sessions are currently in use. NAS controller {{nodeId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.59
fluidFSEventClientAccessUsersProxyNoServiceNFS/SMB partial service Description: Access to {{serverKind}} directory service is limited or service is temporary unavailable Action Items: This scenario usually happens after directory changes (UNIX database re-configuration, Active Directory join, etc). The problem can occur due poor performance of newly configured directory; please wait some time until new directory will be fully initialized. In case of unexpected or persistent problem please check the operability of directory and network connectivity to directory service. Also problems with '{{service}}' internal service can cause this issue - please check for problematic services.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.70
fluidFSEventClientAccessSecChangeErrorBypassOnSecurity change errors bypassed Description: Errors due to chmod/chown/chgrp on volumes with windows security style now bypassed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.71
fluidFSEventClientAccessSecChangeErrorBypassOffSecurity change errors returned Description: Errors due to chmod/chown/chgrp on volumes with windows security style now returned
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.72
fluidFSEventClientAccessFluidFsNotifyEventsDroppedDue2InternalIssuesFile Access Notifications were dropped. Description: {{droppedNotificationsCounter}} File Access Notifications were dropped due to internal issues
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.80
fluidFSEventClientAccessFluidFsNotifyEventsDroppedDue2ServerIssuesFile Access Notifications were dropped. Description: {{droppedNotificationsCounter}} File Access Notifications were dropped due to auditing server issues
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.81
fluidFSEventClientAccessFluidFsNotifyEncryptionFailureFile Access Notification encryption failed Description: Failed initializing encrypted connection to the auditing server. encryption credentials configuration may be invalid
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.82
fluidFSEventClientAccessMountFromInsecurePortNFS 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.89
fluidFSEventClientAccessMountExportDoesntExistNFS 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.90
fluidFSEventClientAccessMountPathDoesntExistNFS mount failure. Non existent mount path {{mountPath}}. Description: NFS mount failure: Client {{clientIpAddr}} tried to mount nonexistent mount path {{mountPath}} on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.91
fluidFSEventClientAccessMountFailurePermissionDeniedNFS mount failure. Access denied during mount {{mountPath}}. Description: NFS mount failure: Access denied for the client {{clientIpAddr}} while mounting path {{mountPath}} on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.92
fluidFSEventClientAccessMountFailedDueExportOptionsNFS mount failure. Access attempt to limited export {{nfsExport}} Description: NFS mount failure: Client {{clientIpAddr}} is not allowed to access export {{nfsExport}} on NAS Volume {{nasContainerIdIntegerName}}, with defined export options: {{nfsExportOptions}}. Action Items: This error is caused by a client which accesses a limited export. The export was defined with clients limitations (network or netgroup or IP) that did not include the accessing client.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.93
fluidFSEventClientAccessMountFailedDueNetgroupFailureNFS mount failure. Netgroups could not be attained {{nfsExport}}. Description: NFS mount failure: Client {{clientIpAddr}} failed to mount export {{nfsExport}} on NAS Volume {{nasContainerIdIntegerName}} since the required netgroup information could not be attained. Export options: {{nfsExportOptions}}. Action Items: Check availability of NIS/LDAP server. This error is usually the outcome of a communication error between the NAS and the NIS/LDAP server. It could be caused by a network issue, directory server overload or a software malfunction in one of environment components.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.94
fluidFSEventClientAccessClientClockSkewClient 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.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.95
fluidFSEventClientAccessSharePathNotFoundClient connect failure. Share {{cifsShare}} points to invalid directory. Description: SMB client connection failure: Client {{clientIpAddr}} accessed a nonexistent share {{cifsShare}} which refers to an inexistent directory {{nasContainerPath}} in NAS Volume {{nasContainerIdIntegerName}}. Action Items: List all available shares on the NAS and identify the problematic share. It should have an indication that it is not accessible.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.96
fluidFSEventClientAccessIncorrectUserPasswordSMB client login to {{TenantName}} failed. Wrong password for user {{userName}}. Description: SMB client login failure: Client {{clientIpAddr}} with user name '{{userName}}' supplied the wrong password. NAS Controller {{nasControllerId}} of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.97
fluidFSEventClientAccessLoginFailureSMB client login to {{TenantName}} failed. Authorization failed for user {{userName}}. Description: Authorization for user '{{userName}}' failed, client {{clientIpAddr}}, NAS controller {{nasControllerId}} of {{TenantName}}. Internal Information: {{internalInfo}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.98
fluidFSEventClientAccessShareDoesntExistSMB client connection failure. Unavailable share {{cifsShare}} on {{TenantName}}. Description: SMB client connection failure: Client {{clientIpAddr}} attempted to connect to an unavailable share {{cifsShare}} of {{TenantName}}. Action Items: This failure is commonly caused by spelling mistakes done on the client machine or by a user trying to access the home share of a different user.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.99
fluidFSEventClientAccessNfsAccessDeniedNFS user {{nfsUserName}} access to a file denied. Insufficient permissions. Description: NFS access denied: user {{nfsUserName}} does not have sufficient permissions for the file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}. Desired/granted access mask: {{desiredNfsAccessMaskHrf}} / {{grantedNfsAccessMaskHrf}}. Internal Information: {{internalInfo}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.100
fluidFSEventClientAccessNfsModificationOfRoExportNFS access denied. Attempt to modify a read-only export {{nfsExport}}. Description: NFS Access Denied: User {{nfsUserName}} accessing from {{clientIpAddr}} tried to perform modifications on a read-only export: {{nfsExport}}, NAS Volume {{nasContainerIdIntegerName}}. Action Items: Verify that the relevant export definition of read-only was done intentionally. Contact the user who is responsible for this access or for application access to understand the reason for using read-only export with write operations.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.101
fluidFSEventClientAccessNfsAccessFromInsecurePortToSecureExportNFS access denied. Secured port must be used; export {{nfsExport}}. Description: NFS Access Denied: User {{nfsUserName}} tried to access from {{clientIpAddr}} to a secure export {{nfsExport}}, NAS Volume {{nasContainerIdIntegerName}} using a non secure port {{nfsClientPort}}. Action Items: Secure exports require that the client accessing them will use a well-known port (under 1024). This is done as a security measure. Identify the relevant export and the checkbox that marks it as secure/requires secure port. If there is no need for a secure export (e.g. the network is not public) make the export insecure by unchecking the secure export option and try again. If the export must remain secure, please refer to the NFS client documentation in order to change the currently used NFS client port to a well-known port (under 1024).
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.102
fluidFSEventClientAccessModificationOfRoVolumeAccess denied. Attempt to modify a read-only NAS volume {{nasContainerIdIntegerName}}. Description: Access denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} tried to modify the file {{dsidPath}} with operation '{{nfsOp}}' on a read-only NAS volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.103
fluidFSEventClientAccessModifyAccessToSnapshotAccess denied. Attempt to modify a snapshot; NAS volume {{nasContainerIdIntegerName}}. Description: Access denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} tried to modify the file {{dsidPath}} on NAS volume {{nasContainerIdIntegerName}} that is located in a snapshot. Action Items: Snapshot is an exact representation of the NAS volume data at the time of the snapshot creation. For that reason, and by definition, snapshot data can't be modified. Contact the user and instruct him to limit any modifications to the current work area in the NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.104
fluidFSEventClientAccessNfsOpNotAllowedDueVolumeStyleNFS access denied. Operation not permitted on {{volumeStyle}} volume {{nasContainerIdIntegerName}}. Description: NFS access denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} tried to '{{nfsOp}}' on a {{volumeStyle}} NAS volume {{nasContainerIdIntegerName}}, file {{dsidPath}}. [[nl]] Choosing a volume security style dictates which protocol will be used to set permissions on files in this volume. This also sets certain limitations on operations which are not allowed for this security style: [[nl]]1. Setting an ACL for a file in a NAS volume defined with UNIX Security style. [[nl]]2. Setting mode for a file in a NAS volume defined with NTFS Security style. [[nl]]3. Changing the read-only flag for a file in a NAS volume defined with UNIX Security style. [[nl]]4. Setting SID/GSID ownership on UNIX Security style [[nl]]5. Setting UID/GID ownership on NTFS Security style. [[nl]]A user might try to perform one of the above actions and get an 'Access denied' error without understanding why. Action Items: The NAS Volume security style should be chosen according to the main intended usage. If a user needs to perform a security related activity which is forbidden, consider splitting the data into two separate NAS Volumes based on the access pattern.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.105
fluidFSEventClientAccessNotAnOwnerNFS access denied. User {{nfsUserName}} not owner of file. Description: NFS Access Denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} can't perform owner restricted operation {{nfsOp}} on file {{dsidPath}}, NAS Volume {{nasContainerIdIntegerName}}, file owner {{userOwnerName}} : {{groupOwnerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.106
fluidFSEventClientAccessGiveUidOwnershipAwayDeniedNFS access denied. Root privileges needed to give ownership. Description: NFS Access Denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} can't give ownership away by operation {{nfsOp}} on file {{dsidPath}} to {{userOwnerName}} because root privileges are required for that, NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.107
fluidFSEventClientAccessGiveGidOwnershipAwayDeniedNFS access denied. Root privileges needed to give ownership. Description: NFS Access Denied: User {{nfsUserName}} accessing from client {{clientIpAddr}} can't give ownership away by operation {{nfsOp}} on file {{dsidPath}} to {{groupOwnerName}} because root privileges are required for that, NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.108
fluidFSEventClientAccessOwnerOfDifferentTypesNFS access denied. File and group owner are inconsistent. Description: NFS Access Denied: both file owner and group owner must be from the same identity type (NTFS vs UNIX), attempt to set different identity types was detected. Client {{clientIpAddr}} User: {{nfsUserName}}, file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}, setting ownership: {{userOwnerName}} ({{userIdentityType}}) : {{groupOwnerName}} ({{groupIdentityType}}). Action Items: It is impossible to change file owner id to UID if the original file ownership is SID/GSID. If the user wants to change the ownership of the file to UNIX ownership, he must set UID and GID at same time. For example: user chown michael:group and not chown michael.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.109
fluidFSEventClientAccessCifsOpNotAllowedDueVolumeStyleSMB access denied. Operation not permitted on {{volumeStyle}} volume. Description: Access Denied: User {{nfsUserName}} tried to '{{nfsOp}}' on a {{volumeStyle}} NAS Volume {{nasContainerIdIntegerName}}, file {{dsidPath}}. [[nl]]Choosing a volume security style dictates which protocol will be used to set permissions on files in this volume. This also sets certain limitations on operations which are not allowed for this security style: [[nl]]1. Setting an ACL for a file in a NAS volume defined with UNIX Security style. [[nl]]2. Setting mode for a file in a NAS volume defined with NTFS Security style. [[nl]]3. Changing the read-only flag for a file in a NAS volume defined with UNIX Security style. [[nl]]4. Setting SID/GSID ownership on UNIX Security style [[nl]]5. Setting UID/GID ownership on NTFS Security style. [[nl]]A user might try to perform one of the above actions and get an 'Access denied' error without understanding why. Action Items: The NAS Volume security style should be chosen according to the main intended usage. If a user needs to perform a security related activity which is forbidden, consider splitting the data into two separate NAS Volumes based on the access pattern.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.110
fluidFSEventClientAccessConnectionFailurePermissionDeniedShare {{cifsShare}} ACL's denied access to user {{userName}}. Description: Connection for user '{{userName}}' to share {{cifsShare}} denied due to share ACL permissions, client {{clientIpAddr}}, NAS Controller {{nasControllerId}}, NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.111
fluidFSEventClientAccessGeneralAccessDeniedAccess denied. Insufficient permissions, user {{userName}}. Description: Access denied on '{{cifsOp}}' operation. Desired access mask: {{desiredCifsAccessMaskName}}, missing bits: {{missedCifsAccessBitsName}}, client: {{clientIpAddr}}, user: {{userName}}, file '{{dsidPath}}' on NAS Volume {{nasContainerIdIntegerName}}. Internal Information: {{internalInfo}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.112
fluidFSEventClientAccessNfs4WritePseudoFSWrite Access to pseudo-fs of {{TenantName}}, user {{userName}}. Description: Write Access denied to user {{userName}}. Attempted modification of NFS4 Pseudo File System of {{TenantName}}). Client IP: {{clientIpAddr}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.113
fluidFSEventClientAccessAccessDeniedOpenModeConflictAccess Denied. Open mode conflict; user {{userName}}. Description: Access Denied on '{{operation}}' operation due open mode conflict. Desired access mask: {{desiredCifsAccessMaskName}}, open mode mask: {{openModeAccessBitsName}}, client: {{clientIpAddr}}, user: {{userName}}, file '{{dsidPath}}' on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.114
fluidFSEventClientAccessAccessDeniedShareModeConflictAccess Denied. Conflict with share mode; NAS Volume {{nasContainerIdIntegerName}}. Description: Access Denied: User {{userName}} accessing from client {{clientIpAddr}} tried to open file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}, which is opened with conflicting share mode by another user.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.115
fluidFSEventClientAccessDeleteOnCloseIsSetAccess denied. File marked for deletion; File {{dsidPath}}. Description: Access denied: the file is marked for deletion. Client: {{clientIpAddr}}, user: {{userName}}, file {{dsidPath}} on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.116
fluidFSEventClientAccessUserPasswordExpiredSMB client login to {{TenantName}} failed. Password expired for user {{userName}}. Description: SMB client login failure: Password expired for client {{clientIpAddr}} user name '{{userName}}'. NAS Controller {{nasControllerId}} of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.117
fluidFSEventClientAccessNoSuchUserSMB client login to {{TenantName}} failed. The user {{userName}} could not be found. Description: SMB client login failure: The login username '{{userName}}' could not be found for client {{clientIpAddr}}. NAS Controller {{nasControllerId}} of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.118
fluidFSEventClientAccessCifsAccessDeniedDueShareLevelPerms2Share-level permissions denied access; share {{cifsShare}}. Description: SMB access denied on '{{cifsOp}}' operation: share-level permission applied for the share {{cifsShare}} prohibits such actions. Desired access mask: {{desiredCifsAccessMaskName}}, client: {{clientIpAddr}}, user: {{userName}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.119
fluidFSEventClientAccessCifsDotSnapshotsAccessDeniedDueToRestrictionSnapshot Access denied due to restriction Description: SMB snapshot access to share {{cifsShare}} was denied due to '.snapshots' restriction. client: {{clientIpAddr}}, user: {{userName}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.120
fluidFSEventClientAccessNfsDotSnapshotsAccessDeniedDueToRestrictionSnapshot Access denied due to restriction Description: NFS snapshot access to file: {{nasContainerIdIntegerName}}/{{dsidPath}} for user {{nfsUserName}} was denied due to '.snapshots' restriction.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.121
fluidFSEventClientAccessCifsUserHasNoPrivileges2SMB access denied. User {{cifsUser2Name}} has insufficient privileges. Description: SMB access denied: accessing user does not have required privileges {{cifsPrivileges}} to perform '{{cifsOp}}', client: {{clientIpAddr}}, user: {{cifsUser2Name}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.122
fluidFSEventClientAccessCifsUserHasNoPrivileges3SMB access denied. User {{cifsUser2Name}} has insufficient privileges Description: SMB access denied: accessing user does not have required privileges {{cifsPrivileges}} to perform '{{cifsOp}}', client: {{clientIpAddr}}, user: {{cifsUser2Name}}, file '{{dsidPath}}' on NAS Volume {{nasContainerIdIntegerName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.123
fluidFSEventClientAccessNestedNetgroupNotFoundMissing netgroup '{{netgroupName}}' could not be found by {{TenantName}}. Description: Nested netgroup '{{netgroupName}}' of parent netgroup '{{parentNetgroupName}}' was not found while resolving recursive definitions of export access list during NFS mount operation on {{TenantName}}. Missing netgroup was ignored. Action Items: Please check the content of the NIS/LDAP external repository and fix the definition of broken netgroup.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.124
fluidFSEventClientAccessNetgroupRecursionIsTooDeepNetgroup '{{netgroupName}}' has too many levels of nesting on {{TenantName}}. Description: Circular netgroup definitions alert: netgroup has too many levels of nesting. Netgroup '{{netgroupName}}' exceeded the limit of {{netgroupThreshold}} levels of nesting on {{TenantName}}. Action Items: Consider reviewing your NIS/LDAP external repository for circular netgroup definitions.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.125
fluidFSEventClientAccessSMBMemThreshold3Due to SMB high memory access denied on open file operation Description: SMB access denied on open file operation for user: {{cifsUser2Name}}, file '{{nasContainerPath}}' on NAS Volume {{nasContainerIdIntegerName}} due to SMB high memory consumption on NAS controller {{nasControllerId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.126
fluidFSEventClientAccessSMBMemThreshold4Due to SMB high resource usage new sessions not allowed. Description: Due to SMB high resource usage new sessions are not allowed on NAS controller {{nasControllerId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.127
fluidFSEventClientAccessRpcSecGssAuthFailureNFS RPCSECGSS user authentication failure for user {{userName}} on {{TenantName}}. Description: NFS RPCSECGSS authentication for user '{{userName}}' failed, client {{clientIpAddr}}, NAS controller {{nasControllerId}} of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.128
fluidFSEventClientAccessSMBMaxOpenFilesThresholdDue to SMB too many open files denied open file operation. Description: SMB access denied on open file operation due to SMB too many open files on NAS controller {{nasControllerId}}. Allowed number of open files per node is {{maxOpenFilesPerNode}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.129
fluidFSEventClientAccessExtensionIsDeniedOnShareSMB access denied. Extension {{fileExtension}} is denied on share {{cifsShare}}. Description: SMB access denied: Extension based access is configured on share {{cifsShare}} on NAS volume {{nasContainerIdIntegerName}}, and extension {{fileExtension}} of file {{nasContainerPath}} is denied. User {{cifsUser2Name}} is not a member of the users groups to be excluded from filtering.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.130
fluidFSEventClientAccessAutoHomeDirCreationErrorError on creation home directory for user {{cifsUser2Name}}. Description: Auto home directory creation failed for user {{cifsUser2Name}} on NAS volume {{nasContainerIdIntegerName}} with path {{nasContainerPath}}. NT error code {{cifsErrorCode}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.131
fluidFSEventClientAccessMountDeniedOnVipNFS mount Denied. Path denied {{mountPath}} on subnet {{clusterVIP}} Description: NFS client {{clientIpAddr}} was trying to mount NFS export with path {{mountPath}} via cluster VIP {{clusterVIP}} but access from this subnet is not allowed by this NFS export. Access was denied. Client was accessing the export in blind mode that can be considered as security issue.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.132
fluidFSEventClientAccessCifsTreeConnectDeniedOnVipAccess from disallowed subnet to share {{cifsShare}} was denied Description: Connection for user '{{userName}}' to share {{cifsShare}} denied because access from this subnet is not allowed by SMB share settings, client {{clientIpAddr}}, NAS Controller {{nasControllerId}}, NAS Volume {{nasContainerIdIntegerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.133
fluidFSEventClientAccessNoRootForOperationNFS access denied. Root privileges on export needed for {{operation}}. Description: NFS Access Denied: Client {{clientIpAddr}} can't execute operation {{operation}} with volume {{nasContainerIdIntegerName}} because root privileges are required for the client in the relevant NFS export.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.134
fluidFSEventClientAccessFtpLoginFailedFTP user log-in to {{TenantName}} failed Description: FTP access to {{TenantName}} from {{clientIpAddr}} is denied for user {{userName}}. Action Items: When the client attempts FTP connection but provides bad account details, this event is generated. Possible reasons: wrong password, bad username, disabled anonymous access, account is disabled, password is expired and needs to be changed. The user should verify account details.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.135
fluidFSEventClientAccessFtpLoginAccountProblemFTP user log-in to {{TenantName}} failed due to problematic account Description: FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to problematic account Action Items: When the client makes FTP connection but provided account has problems, this event is generated. Possible reasons: account is locked, account is expired, logon with this account is disabled. System administrator might provide support to the user to fix the account problem.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.136
fluidFSEventClientAccessFtpLoginInternalProblemFTP user log-in to {{TenantName}} failed due to an internal problem Description: FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to internal problem Internal Information: {{internalInfo}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.137
fluidFSEventClientAccessFtpLoginSucceededFTP user logged into {{TenantName}} Description: FTP client {{clientIpAddr}} user {{userName}} logged into {{TenantName}} Action Items: When the client makes FTP connection and successfully logs in, this event is generated
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.138
fluidFSEventClientAccessFtpAnonymousLoggedInFTP Anonymous user logged into {{TenantName}} Description: FTP Anonymous user logged into {{TenantName}} with email {{userEmail}} from {{clientIpAddr}}. Action Items: We register an event for every anonymous user logins.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.139
fluidFSEventClientAccessFtpTlsHandshakeVerMismatchFTP user log-in to {{TenantName}} failed due to wrong TLS version Description: FTP client {{clientIpAddr}} log-in to {{TenantName}} failed due to TLS protocol version mismatch Action Items: Please make sure FTP client software supports encryption method version TLS 1.{{tlsVersion}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.140
fluidFSEventClientAccessMaxFtpConnectionsReachedReached Maximum FTP connections on NAS controller {{nasControllerId}} of {{TenantName}}. Maximum connection allowed per controller is {{maxConnections}} Action Items: This failure is common when there are too many FTP connections to the same fsd.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.141
fluidFSEventClientAccessFtpMissingBaseLandingDirFTP user log-in to {{TenantName}} failed due to missing landing path Description: FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to missing landing directory '{{baseLandingPath}}' on volume {{nasContainerIdIntegerName}}}. Action Items: When the client makes FTP connection and successfully logs in but landing directory does not exist, this event is generated. Please create the landing directory.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.142
fluidFSEventClientAccessFtpMissingHomeLandingDirFTP user log-in to {{TenantName}} failed due to missing home landing path Description: FTP client {{clientIpAddr}} user {{userName}} log-in to {{TenantName}} failed due to missing home directory '{{suffixLandingPath}}' within base landing directory '{{baseLandingPath}}' on volume {{nasContainerIdIntegerName}} Action Items: When the client makes FTP connection and successfully logs in but home landing directory does not exist, this event is generated. FTP does not create home folders automatically. Please create them manually.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.143
fluidFSEventClientAccessHdfsMaxConnectionsReachedReached maximum HDFS connections Description: Reached Maximum HDFS connections. Action Items: This failure is common when there are too many HDFS connections to the same fsd.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.144
fluidFSEventClientAccessHdfsUserNotFoundHDFS user name was not found in any of the repositories of {{TenantName}} Description: HDFS access from {{clientIpAddr}} provided the user name {{userName}}, but a corresponding user was not found in any of the repositories of {{TenantName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.145
fluidFSEventClientAccessHdfsDotSnapshotsAccessDeniedDueToRestrictionSnapshot Access denied by {{TenantName}} due to restriction Description: Snapshot access to the HDFS landing directory of NAS Volume {{nasContainerIdIntegerName}} of {{TenantName}} was denied due to '.snapshots' restriction. client: {{clientIpAddr}}, user: {{userName}}, path: '{{baseLandingPath}}'.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.146
fluidFSEventClientAccessGpoExecutionTimeoutFailureGPO Policy was not applied on {{TenantName}}. Took too much time. Description: Policy {{policyGuid}} {{policyName}} was not applied on {{TenantName}}. Took to much time.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.147
fluidFSEventClientAccessGpoOtherFailureGPO Policy was not applied on {{TenantName}} due to system error. Description: Policy {{policyGuid}} {{policyName}} was not applied on {{TenantName}} due to system error.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.148
fluidFSEventClientAccessGpoSuccessGPO Policy was applied successfully on {{TenantName}}. Description: Policy {{policyGuid}} {{policyName}} was applied successfully on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.149
fluidFSEventClientAccessGpoFileSecurityPolicyFailureGPO Policy on target on {{TenantName}} was not applied due to system error Description: Policy {{policyGuid}} {{policyName}} on target {{policyTargetPath}} was not applied due to system error on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.150
fluidFSEventClientAccessGpoFileSecurityPolicyDoNotReplaceFailureGPO Do Not Replace was not applied on {{TenantName}} due to system error. Description: Do not replace logic was not applied in Policy {{policyGuid}} {{policyName}} on target {{policyTargetPath}} due to system error on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.151
fluidFSEventClientAccessGpoInfFileReadFailureGPO Policy .inf file read failure on {{TenantName}}. Description: {{TenantName}} failed to read the .inf file {{filePath}} of the Policy {{policyGuid}} {{policyName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.152
fluidFSEventClientAccessCapLdapQueryFailureCentral Access Policy LDAP query failure on {{TenantName}}. Description: LDAP query for Central Access Policy objects {{searchedObjects}} failed on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.153
fluidFSEventClientAccessCapCentralAccessRuleParsingFailureCentral Access Policy rule parsing failure on {{TenantName}}. Description: Parsing of the Central Access Policy rule {{ruleDN}} of the policy {{policyDN}} failed on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.154
fluidFSEventClientAccessCapCentralAccessPolicyParsingFailureCentral Access policy parsing failure on {{TenantName}}. Description: Parsing of the Central Access policy {{policyDN}} failed on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.11.155
fluidFSEventsLicensing
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.13
fluidFSEventLicensingEulaNotApprovedByUserEnd-user license agreement (EULA) was not accepted by user. Description: FluidFS version {{FluidFsVersion}} has a new end user license agreement. You must accept this agreement in order to use the system. Action Items: To accept the end user agreement go to User Interface System menu.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.13.14
fluidFSEventsExaminer
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.14
fluidFSEventExaminerSystemCorruptionFluidFS Health Scan found an inconsistency in the system. Description: FluidFS Health Scan found an inconsistency in the system. Please contact Support. Internal Information: FluidFS Health Scan has found an error in {{category}} on level {{level}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.14.1
fluidFSEventExaminerExaminingCycleFinishedFluidFS Health Scan finished a scanning cycle. Description: FluidFS Health Scan finished a scanning cycle of the entire system
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.14.3
fluidFSEventsComponent
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.15
fluidFSEventComponentExampleCreateSuccessExample {{Name}} was created by {{userName}}. Result: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.3
fluidFSEventComponentExampleCreateFailedFailed to create Example {{Name}} by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.4
fluidFSEventComponentExampleCreateWarningExample {{Name}} was created by {{userName}}, but with a warning: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.5
fluidFSEventComponentExampleModifySuccessExample {{Name}} was modified by {{userName}}. Result: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.6
fluidFSEventComponentExampleModifyFailedFailed to modify Example {{Name}} by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.7
fluidFSEventComponentExampleModifyWarningExample {{Name}} was modified by {{userName}}, but with a warning: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.8
fluidFSEventComponentExampleDeleteSuccessExample {{Name}} was deleted by {{userName}}. Result: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.9
fluidFSEventComponentExampleDeleteFailedFailed to delete {{Name}} by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.10
fluidFSEventComponentExampleDeleteWarningExample {{Name}} was deleted by {{userName}}, but with a warning: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.11
fluidFSEventComponentTimeModifySuccessTime configuration was modified by {{userName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.12
fluidFSEventComponentTimeModifyFailedFailed to modify time configuration by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.13
fluidFSEventComponentRouteRulesCreateSuccessRoute to {{destinationNetworkID}}/{{destinationPrefix}} with gateway IP {{routeGateway}} was successfully created by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.14
fluidFSEventComponentSnmpModifySuccessSNMP configuration was modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.15
fluidFSEventComponentSnmpModifyFailedFailed to modify SNMP by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.16
fluidFSEventComponentRouteRulesModifySuccessRoute to {{destinationNetworkID}}/{{destinationPrefix}} with gateway IP {{routeGateway}} was successfully modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.30
fluidFSEventComponentMailConfModifySuccessMail configuration was modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.31
fluidFSEventComponentSystemServiceModeChangedSuccessThe System Service Mode is changed to {{systemServiceState}}. Description: The System Service Mode is changed to {{systemServiceState}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.32
fluidFSEventComponentSystemServiceModeChangedFailedFailed to change System Service Mode. Description: The System Service Mode failed to be changed to {{systemServiceState}}: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.35
fluidFSEventComponentNasAppliancesCreateSuccessNAS Appliance {{applianceId}} ({{applianceServiceTag}}) was successfully created by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.36
fluidFSEventComponentNasAppliancesCreateFailedNAS Appliance {{applianceId}} ({{applianceServiceTag}}) could not be created by user {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.37
fluidFSEventComponentNasAppliancesModifySuccessNAS Appliance {{applianceId}} ({{applianceServiceTag}}) was successfully modified by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.38
fluidFSEventComponentNasAppliancesModifyFailedNAS Appliance {{applianceId}} ({{applianceServiceTag}}) could not be modified by user {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.39
fluidFSEventComponentNasAppliancesDeleteSuccessNAS Appliance {{applianceId}} ({{applianceServiceTag}}) was successfully deleted by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.40
fluidFSEventComponentNasAppliancesDeleteFailedNAS Appliance {{applianceId}} ({{applianceServiceTag}}) could not be deleted by user {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.41
fluidFSEventComponentRestoreClusterCompletedSuccessfullyThe configuration of the cluster was restored successfully by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.42
fluidFSEventComponentRestoreClusterFinishedWithErrorsRestore of cluster configuration finished with errors. Description: The configuration of the cluster was restored by user {{userName}} with errors: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.43
fluidFSEventComponentRestoreSystemCompletedSuccessfullyThe configuration of the system was restored successfully by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.44
fluidFSEventComponentRestoreSystemFinishedWithErrorsRestore of system configuration finished with errors. Description: The configuration of the system was restored by user {{userName}} with errors: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.45
fluidFSEventComponentRestoreSystemFromFilesCompletedSuccessfullyThe configuration of the system was restored from files successfully by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.48
fluidFSEventComponentRestoreSystemFromFilesFinishedWithErrorsRestore of system configuration finished with errors. Description: The configuration of the system was restored from files by user {{userName}} with errors: {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.49
fluidFSEventComponentStorageSubsystemCreateSuccessNAS pool was successfully created by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.62
fluidFSEventComponentStorageSubsystemCreateFailedNAS pool could not be created by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.63
fluidFSEventComponentStorageSubsystemModifySuccessNAS pool was successfully expanded by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.64
fluidFSEventComponentStorageSubsystemModifyFailedNAS pool could not be expanded by {{userName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.65
fluidFSEventComponentAuthenticateAdministratorFailureUser {{Domain}}\{{Name}} failed login to FluidFS {{UserInterfaceType}} from {{UserInterfaceClient}} client.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.72
fluidFSEventComponentServicePackRunSuccessEvent{{userName}} successfully upgraded with service pack file {{servicePackFileName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.73
fluidFSEventComponentServicePackRunFailedEvent{{userName}} failed upgrade with service pack file {{servicePackFileName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.74
fluidFSEventComponentEulaApproveSuccessEvent{{userName}} approved the EULA.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.75
fluidFSEventComponentAuthenticateAdministratorSuccessUser {{Domain}}\{{Name}} logged in to FluidFS {{UserInterfaceType}} from {{UserInterfaceClient}} client.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.76
fluidFSEventComponentSetCurrentTimeActionEvent{{userName}} changed the current time.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.77
fluidFSEventComponentDataReductionConfigurationModifySuccessThe user {{userName}} updated the configuration of Data Reduction schedule policy.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.79
fluidFSEventComponentClientNetworkInterfaceModifySuccessClient network interface was successfully modified to MTU {{clientNetworkInterfaceMtu}} and bonding mode {{clientNetworkInterfaceBondMode}} by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.93
fluidFSEventComponentEqlFabricCreateSuccessEQL fabric created by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.94
fluidFSEventComponentEqlFabricCreateWarningEQL fabric created by {{userName}}. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.95
fluidFSEventComponentEqlFabricModifySuccessEQL fabric modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.96
fluidFSEventComponentEqlFabricModifyWarningEQL fabric modified by {{userName}}. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.97
fluidFSEventComponentEqlFabricDeleteSuccessEQL fabric deleted by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.98
fluidFSEventComponentEqlFabricRoutesCreateSuccessEQL fabric route {{networkId}} created by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.99
fluidFSEventComponentEqlFabricRoutesModifySuccessEQL fabric route {{networkId}} modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.100
fluidFSEventComponentEqlFabricRoutesDeleteSuccessEQL fabric route {{networkId}} deleted by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.101
fluidFSEventComponentFabricIscsiV4CreateSuccessiSCSI IPv4 fabric {{Name}} created by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.102
fluidFSEventComponentFabricIscsiV4CreateWarningiSCSI IPv4 fabric {{Name}} created by {{userName}}. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.103
fluidFSEventComponentFabricIscsiV4ModifySuccessiSCSI IPv4 fabric {{Name}} modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.104
fluidFSEventComponentFabricIscsiV4ModifyWarningiSCSI IPv4 fabric {{Name}} modified by {{userName}}. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.105
fluidFSEventComponentFabricIscsiV4DeleteSuccessiSCSI IPv4 fabric {{Name}} deleted by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.106
fluidFSEventComponentStorageEqlGroupModifySuccessEQL storage group modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.107
fluidFSEventComponentStorageIscsiPortalsModifySuccessiSCSI storage portals modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.108
fluidFSEventComponentStorageIscsiPortalsModifyFailureFailure to modify iSCSI storage portals by {{userName}}. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.109
fluidFSEventComponentNasApplianceBlinkSuccessUser {{userName}} set the appliance ID {{applianceId}} blink state for the 1st controller to {{blink1}} and the 2nd controller to {{blink2}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.122
fluidFSEventComponentRebootNasControllerSuccessUser {{userName}} rebooted NAS controller {{controllerId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.123
fluidFSEventComponentMoveClientActionSuccessClient or router with {{ClientIp}} IP, which referred to {{AccessIp}} IP, was moved to controller{{NodeId}} by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.124
fluidFSEventComponentPinClientActionSuccessClient or router with {{ClientIp}} IP, which referred to {{AccessIp}} IP was restricted to the required controller (pin state is {{PinState}}) by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.125
fluidFSEventComponentClientLoadBalancingMassFailbackSuccess{{userName}} had performed failback of all the clients to their preferred controller.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.126
fluidFSEventComponentClientLoadBalancingMassRebalancingSuccess{{userName}} had performed a rebalance of all the clients between the controllers.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.127
fluidFSEventComponentNDMPConfigurationModifySuccessNDMP configuration was modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.128
fluidFSEventComponentAntiVirusHostsModifySuccessThe user {{userName}} updated the antivirus hosts.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.134
fluidFSEventComponentClusterIdModifySuccessThe user {{userName}} updated the cluster identifier.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.136
fluidFSEventComponentClusterNameModifySuccessThe user {{userName}} renamed the cluster to {{ClusterName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.137
fluidFSEventComponentBackupConfigurationObjectsToFileSuccessThe user {{userName}} backed up the cluster configuration to file.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.138
fluidFSEventComponentDestroyClusterSuccessThe user {{userName}} destroyed the cluster.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.140
fluidFSEventComponentEMRecipientsModifySuccessThe user {{userName}} updated the Enterprise Manager recipients.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.141
fluidFSEventComponentFabricFcCreateSuccessThe user {{userName}} created {{FabricName}} Fibre Channel fabric.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.142
fluidFSEventComponentFabricFcModifySuccessThe user {{userName}} updated {{FabricName}} Fibre Channel fabric.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.143
fluidFSEventComponentFabricFcDeleteSuccessThe user {{userName}} deleted {{FabricName}} Fibre Channel fabric.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.144
fluidFSEventComponentFTPConfigurationModifySuccessThe user {{userName}} updated the FTP configuration.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.147
fluidFSEventComponentHealthScanConfigurationModifySuccessThe user {{userName}} updated the file system health scan configuration.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.148
fluidFSEventComponentLanguageModifySuccessThe user {{userName}} updated the language of the cluster.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.150
fluidFSEventComponentLogoffActiveNdmpSessionSuccessThe user {{userName}} killed {{NDMPSessionId}} NDMP session on NAS controller{{controllerId}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.152
fluidFSEventComponentNasPoolConfigurationModifySuccessThe user {{userName}} updated the NAS pool thresholds.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.154
fluidFSEventComponentSupportAccessModifySuccessThe user {{userName}} updated the support access settings.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.155
fluidFSEventComponentSystemConfigurationStateModifySuccessThe user {{userName}} updated the system configuration state.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.156
fluidFSEventComponentTriggerFabricDiscoverySuccessThe user {{userName}} triggered LUNs discovery.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.158
fluidFSEventComponentTrustedSystemCreateSuccessThe user {{userName}} created partnership with {{PartnerIp}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.159
fluidFSEventComponentTrustedSystemModifySuccessThe user {{userName}} updated partnership with {{PartnerIp}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.160
fluidFSEventComponentTrustedSystemDeleteSuccessThe user {{userName}} deleted partnership with {{PartnerIp}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.161
fluidFSEventComponentUIConfigurationModifySuccessThe user {{userName}} updated the UI settings.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.162
fluidFSEventComponentRunFileSystemDiagnosticSuccessThe user {{userName}} ran core file system diagnostic. Description: The user {{userName}} ran core file system diagnostic.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.170
fluidFSEventComponentRunGeneralSystemDiagnosticSuccessThe user {{userName}} ran general system diagnostic. Description: The user {{userName}} ran general system diagnostic.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.171
fluidFSEventComponentRunNetworkDiagnosticSuccessThe user {{userName}} ran networking diagnostic. Description: The user {{userName}} ran networking diagnostic.[[nl]]Diagnostic arguments:[[nl]]ClientIP - {{RunNetworkDiagnosticClientIP}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.172
fluidFSEventComponentRunPerformanceDiagnosticSuccessThe user {{userName}} ran performance diagnostic. Description: The user {{userName}} ran performance diagnostic.[[nl]]Diagnostic arguments:[[nl]]FSID - {{RunPerformanceDiagnosticFSID}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.174
fluidFSEventComponentRunFileSystemDiagnosticActionFailureFile System diagnostic failed. Description: File System diagnostic, which was run by user {{userName}} failed.[[nl]]{{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.178
fluidFSEventComponentRunGeneralSystemDiagnosticActionFailureGeneral System diagnostic failed. Description: General System diagnostic, which was run by user {{userName}} failed.[[nl]]{{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.179
fluidFSEventComponentRunNetworkDiagnosticActionFailureNetwork diagnostic failed. Description: Network diagnostic, which was run by user {{userName}} failed.[[nl]]Diagnostic arguments:[[nl]]ClientIP - {{RunNetworkDiagnosticClientIP}}[[nl]]{{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.180
fluidFSEventComponentRunPerformanceDiagnosticActionFailurePerformance diagnostic failed. Description: Performance diagnostic, which was run by user {{userName}} failed.[[nl]]Diagnostic arguments:[[nl]]FSID - {{RunPerformanceDiagnosticFSID}}[[nl]]{{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.182
fluidFSEventComponentFileSystemCoreDiagnosticsFailedFailed to generate diagnostics package for 'FileSystemCoreDiagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.189
fluidFSEventComponentFileSystemCoreDiagnosticsFailesOkPackage generation for 'FileSystemCoreDiagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.190
fluidFSEventComponentGeneralSystemDiagnosticsFailedFailed to generate diagnostics package for 'GeneralSystemDiagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.191
fluidFSEventComponentGeneralSystemDiagnosticsOkPackage generation for 'GeneralSystemDiagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.192
fluidFSEventComponentNetworkDiagnosticsFailedFailed to generate diagnostics package for 'NetworkDiagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.193
fluidFSEventComponentNetworkDiagnosticsOkPackage generation for 'NetworkDiagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.194
fluidFSEventComponentPerformanceDiagnosticsFailedFailed to generate diagnostics package for 'PerformanceDiagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.197
fluidFSEventComponentPerformanceDiagnosticsOkPackage generation for 'PerformanceDiagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.198
fluidFSEventComponentExampleCreateStartExample {{Name}} create started by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.201
fluidFSEventComponentPostUpgradeActionsEventSystem was successfully upgraded to version {{servicePackVersion}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.203
fluidFSEventComponentRouteRulesDeleteSuccessRoute to {{destinationNetworkID}}/{{destinationPrefix}} with gateway IP {{routeGateway}} was successfully deleted by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.204
fluidFSEventComponentSecureConsoleAccessModifySuccessThe user {{userName}} had modified the Secure Console Access settings Description: The user {{userName}} had modified the Secure Console Access settings
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.205
fluidFSEventComponentSecureConsoleAccessModifyFailure{{userName}} failed to modify the Secure Console Access settings Description: The user {{userName}} had failed to modify the Secure Console Access settings due to the following error: {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.206
fluidFSEventComponentSecureConsoleAccessModifyWarning{{userName}} failed to modify the Secure Console Access settings Description: The user {{userName}} had failed to modify the Secure Console Access settings due to the following error: {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.207
fluidFSEventComponentExampleBackgroundCreateSuccessExampleBackground {{Name}} was created .
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.209
fluidFSEventComponentFilesystemCreatedStartingDomainMigrationThe NAS appliance is now part of the file-system. Starting resource optimization using domain migration.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.211
fluidFSEventComponentStartingJoinNASApplianceThe system is starting to join the NAS appliance to the file-system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.212
fluidFSEventComponentFilesystemCreatedNoDomainMigrationRequiredThe NAS appliance is now part of the file-system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.213
fluidFSEventComponentEventsStoreFilterModifySuccessEvents filter configuration was modified by {{userName}} Description: Events filter configuration was modified by {{userName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.214
fluidFSEventComponentEventsStoreFilterModifyFailure{{userName}} had failed to modify the Events filter configuration Description: {{userName}} had failed to modify the Events filter configuration. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.215
fluidFSEventComponentPhoneHomeModifySuccess{{userName}} updated phone home settings Description: {{userName}} updated phone home settings
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.216
fluidFSEventComponentBMCNetworkConfigurationModifySuccessThe user {{userName}} updated the BMC network configuration.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.219
fluidFSEventComponentFSStorageConfigurationModifySuccessThe user {{userName}} updated the file system storage configuration.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.220
fluidFSEventComponentUpgradeStandbyNodeSuccessEvent{{userName}} successfully flashed standby node with service pack file {{servicePackFileName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.223
fluidFSEventComponentUpgradeStandbyNodeFailedEvent{{userName}} failed to flash standby node with service pack file {{servicePackFileName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.224
fluidFSEventComponentPostUpgradeActionsWarningEventUpgraded with warnings: {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.225
fluidFSEventComponentServicePackValidateSuccessEvent{{userName}} successfully validated service pack file {{servicePackFileName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.226
fluidFSEventComponentServicePackValidateFailedEvent{{userName}}: Failed validation of service pack file {{servicePackFileName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.227
fluidFSEventComponentCloneVMSuccessThe user {{userName}} successfully created {{numberOfClones}} cloned virtual machines from {{sourceVMName}}. on server {{vmWareServerName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.228
fluidFSEventComponentCreateVMWareServerSuccessThe user {{userName}} created VMWare server {{vmWareServerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.229
fluidFSEventComponentModifyVMWareServerSuccessThe user {{userName}} modified VMWare server {{vmWareServerName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.230
fluidFSEventComponentEnableMetadataRedundancyForNewVolumesMetadata redundancy for new NAS volumes was enabled by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.231
fluidFSEventComponentDisableMetadataRedundancyForNewVolumesMetadata redundancy for new NAS volumes was disabled by {{userName}}. Be aware that newly created NAS Volumes will be less resistant to failure
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.232
fluidFSEventComponentModifyVMWareSettingsSuccessThe user {{userName}} modified VMWare settings
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.234
fluidFSEventComponentRunNdmpDiagnosticSuccessThe user {{userName}} ran NDMP diagnostic. Description: The user {{userName}} ran NDMP diagnostic.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.236
fluidFSEventComponentRunNdmpDiagnosticActionFailureNdmp diagnostic failed. Description: Ndmp diagnostic, which was run by user {{userName}} failed.[[nl]]{{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.237
fluidFSEventComponentNdmpDiagnosticsFailedFailed to generate diagnostics package for 'NdmpDiagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.238
fluidFSEventComponentNdmpDiagnosticsOkPackage generation for 'NdmpDiagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.239
fluidFSEventComponentRediscoverLunsSuccessThe system sucessfully triggered iSCSI targets discovery.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.241
fluidFSEventComponentFileAccessNotificationConfigModifySuccessFile Access Notification settings updated Description: File Access Notification settings updated
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.247
fluidFSEventComponentFileAccessNotificationPolicyModifySuccessFile Access Notification Policy changed Description: File Access Notification Policy changed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.248
fluidFSEventComponentFileAccessNotificationSubscriberModifySuccessFile Access Notifications Subscribers changed Description: File Access Notifications Subscribers changed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.249
fluidFSEventComponentTapeDeviceConfigurationCreateSuccessThe user {{userName}} created a new tape device with name {{tapeDeviceName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.250
fluidFSEventComponentTapeDeviceConfigurationModifySuccessThe user {{userName}} modified a tape device name to {{tapeDeviceName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.251
fluidFSEventComponentTapeDeviceConfigurationDeleteSuccessThe user {{userName}} deleted a tape device with name {{tapeDeviceName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.252
fluidFSEventComponentInternalStorageReservationSetSuccessThe user {{userName}} set the internal storage reservation Description: The user {{userName}} set the internal storage reservation. Current configuration: events - {{eventsSpace}} MB
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.253
fluidFSEventComponentBwLimiterCreateSuccessThe user {{userName}} created Bw Limiter {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.254
fluidFSEventComponentBwLimiterModifySuccessThe user {{userName}} updated the configuration of BW Limiter {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.255
fluidFSEventComponentBwLimiterDeleteSuccessThe user {{userName}} deleted BW Limiter {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.256
fluidFSEventComponentStorageDevicesRescanSuccessEventThe user {{userName}} performed rescan storage devices.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.258
fluidFSEventComponentVAppCloningSuccessThe user {{userName}} has successfully cloned VMware Virtual Appliance
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.264
fluidFSEventComponentTenantCreateSuccessThe user {{userName}} created Tenant {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.265
fluidFSEventComponentTenantModifySuccessThe user {{userName}} updated the configuration of {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.266
fluidFSEventComponentTenantDeleteSuccessThe user {{userName}} deleted Tenant {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.267
fluidFSEventComponentVirtualVolumeCreateSuccessThe user {{userName}} created NAS volume {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.268
fluidFSEventComponentVirtualVolumeModifySuccessThe user {{userName}} updated the configuration of NAS volume {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.269
fluidFSEventComponentVirtualVolumeDeleteSuccessThe user {{userName}} deleted NAS volume {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.270
fluidFSEventComponentSnapshotsRestoreSuccessThe user {{userName}} restored snapshot {{SnapshotID}} - {{Name}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.271
fluidFSEventComponentSnapshotModifySuccessThe user {{userName}} modified snapshot {{SnapshotID}} on NAS volume {{FSIDName}} to name {{Name}} and expiry {{Expiry}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.272
fluidFSEventComponentSnapshotModifyFailureThe user {{userName}} failed to rename snapshot {{SnapshotID}} on NAS volume {{FSIDName}} to name {{Name}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.273
fluidFSEventComponentSnapshotDeleteSuccessThe user {{userName}} deleted snapshot {{SnapshotID}} - {{Name}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.274
fluidFSEventComponentSnapshotDeleteFailureThe user {{userName}} failed to delete snapshot {{SnapshotID}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.275
fluidFSEventComponentSnapshotCreateSuccessThe user {{userName}} created snapshot {{SnapshotID}} - {{Name}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.276
fluidFSEventComponentSnapshotCreateFailureThe user {{userName}} failed to create snapshot {{SnapshotID}} - {{Name}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.277
fluidFSEventComponentSnapshotMakeManualSuccessThe user {{userName}} set NDMP lock on snapshot {{SnapshotID}} on NAS volume {{FSIDName}} to {{NdmpLock}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.278
fluidFSEventComponentDnsModifySuccessDNS configuration of {{TenantName}} was modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.279
fluidFSEventComponentDnsModifyWarningDNS configuration of {{TenantName}} was modified by {{userName}}. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.280
fluidFSEventComponentSnapshotsRestoreSuccessNameSnapshot {{SnapshotID}} - {{Name}} was restored on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.281
fluidFSEventComponentSnapshotsRestoreFailureNameSnapshot {{SnapshotID}} - {{Name}} failed to be restored on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.282
fluidFSEventComponentRestoreVirtualVolumeCompletedSuccessfullyThe configuration of the NAS volume {{FSIDName}} was restored successfully by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.283
fluidFSEventComponentRestoreVirtualVolumeFinishedWithErrorsRestore NAS container configuration {{FSIDName}} finished with errors. Description: The configuration of the NAS container {{FSIDName}} was restored by user {{userName}} with errors: {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.284
fluidFSEventComponentRestoreVirtualVolumeFromFilesCompletedSuccessfullyThe configuration of the NAS volume {{FSIDName}} was restored from files successfully by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.285
fluidFSEventComponentRestoreVirtualVolumeFromFilesFinishedWithErrorsRestore NAS volume {{FSIDName}} configuration finished with errors. Description: The configuration of the NAS volume {{FSIDName}} was restored from files by user {{userName}} with errors: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.286
fluidFSEventComponentAdministratorCreateSuccessThe user {{userName}} created new administrator {{AdminName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.287
fluidFSEventComponentAdministratorModifySuccessThe user {{userName}} modified the configuration of administrator {{AdminName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.288
fluidFSEventComponentAdministratorDeleteSuccessThe user {{userName}} deleted administrator {{AdminName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.289
fluidFSEventComponentCifsShareCreateSuccessThe user {{userName}} created the {{shareName}} SMB share on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.290
fluidFSEventComponentCifsShareModifySuccessThe user {{userName}} updated the configuration of {{shareName}} SMB share on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.291
fluidFSEventComponentCifsShareDeleteSuccessThe user {{userName}} deleted the {{shareName}} SMB share on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.292
fluidFSEventComponentCifsHomeShareModifySuccessThe user {{userName}} updated the configuration of home SMB share on {{FSIDName}} NAS volume of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.293
fluidFSEventComponentNfsExportCreateSuccessThe user {{userName}} created the {{NFSExportPath}} NFS export on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.294
fluidFSEventComponentNfsExportModifySuccessThe user {{userName}} updated the configuration of {{NFSExportPath}} NFS export on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.295
fluidFSEventComponentNfsExportDeleteSuccessThe user {{userName}} deleted {{NFSExportPath}} NFS export on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.296
fluidFSEventComponentSnapshotScheduleCreateSuccessThe user {{userName}} created the {{Name}} snapshot schedule on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.297
fluidFSEventComponentSnapshotScheduleModifySuccessThe user {{userName}} updated the configuration of {{Name}} snapshot schedule on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.298
fluidFSEventComponentSnapshotScheduleDeleteSuccessThe user {{userName}} deleted the {{Name}} snapshot schedule on {{FSIDName}} NAS volume.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.299
fluidFSEventComponentReplicationScheduleCreateSuccessThe user {{userName}} created the {{Name}} schedule for replication between {{FSIDName}} and {{remoteVolumeName}}@{{remoteClusterName}} NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.300
fluidFSEventComponentReplicationScheduleModifySuccessThe user {{userName}} updated the configuration of {{Name}} schedule for replication between {{FSIDName}} and {{remoteVolumeName}}@{{remoteClusterName}} NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.301
fluidFSEventComponentReplicationScheduleDeleteSuccessThe user {{userName}} deleted the {{Name}} schedule for replication between {{FSIDName}} and {{remoteVolumeName}}@{{remoteClusterName}} NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.302
fluidFSEventComponentSnapshotDeleteSuccessNoNameThe user {{userName}} deleted snapshot {{SnapshotID}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.303
fluidFSEventComponentReplicationActionAttachSuccessThe user {{userName}} has connected {{FSIDName}} volume to {{remoteVolume}} volume of {{remoteSystemName}} system. Description: The user {{userName}} has connected NAS volume to {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.304
fluidFSEventComponentReplicationActionDetachSuccessThe user {{userName}} has disconnected {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes. Description: The user {{userName}} has disconnected the replication between {{FSIDName}} NAS volume and {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.305
fluidFSEventComponentReplicationActionPauseSuccessThe user {{userName}} has disabled replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes. Description: The user {{userName}} has disabled the replication between {{FSIDName}} NAS volume and {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.306
fluidFSEventComponentReplicationActionResumeSuccessThe user {{userName}} has enabled replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes. Description: The user {{userName}} has enabled the replication between {{FSIDName}} NAS volume and {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.307
fluidFSEventComponentReplicationActionPromoteSuccessThe user {{userName}} has promoted replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes. Description: The user {{userName}} has promoted replication between {{FSIDName}} NAS volume and {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.308
fluidFSEventComponentReplicationActionDemoteSuccessThe user {{userName}} has demoted replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes. Description: The user {{userName}} has demoted replication between {{FSIDName}} NAS volume and {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.309
fluidFSEventComponentReplicationActionStartSuccessThe user {{userName}} has started replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes. Description: The user {{userName}} has started replication from {{FSIDName}} NAS volume to {{remoteVolume}} NAS volume of {{remoteSystemName}} system.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.310
fluidFSEventComponentCreateBlockStorageSuccessBlockStorage {{storageId}} was successfully created.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.311
fluidFSEventComponentModifyBlockStorageSuccessClient subnet {{storageId}} was successfully modified.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.312
fluidFSEventComponentDeleteBlockStorageSuccessClient subnet {{storageId}} was successfully deleted.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.313
fluidFSEventComponentSubnetsCreateSuccessClient subnet {{networkId}}/{{prefix}} was successfully created by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.314
fluidFSEventComponentSubnetsModifySuccessClient subnet {{networkId}}/{{prefix}} was successfully modified by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.315
fluidFSEventComponentSubnetsDeleteSuccessClient subnet {{networkId}}/{{prefix}} was successfully deleted by {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.316
fluidFSEventComponentActiveDirectoryJoinSuccessThe user {{userName}} has successfully joined {{TenantName}} to Active Directory domain '{{Domain}}'.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.317
fluidFSEventComponentActiveDirectoryJoinWarningThe user {{userName}} has joined {{TenantName}} to Active Directory domain '{{Domain}}', but with a warning: {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.318
fluidFSEventComponentActiveDirectoryLeaveSuccessThe user {{userName}} has successfully left {{TenantName}} from Active Directory domain.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.319
fluidFSEventComponentLocalUsersCreateSuccessThe user {{userName}} has successfully added new Local User '{{localAccountName}}' to {{TenantName}} cluster repository.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.320
fluidFSEventComponentLocalUsersDeleteSuccessThe user {{userName}} has successfully deleted Local User '{{localAccountName}}' from {{TenantName}} cluster repository.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.321
fluidFSEventComponentLocalUsersModifySuccessThe user {{userName}} has successfully modified Local User '{{localAccountName}}' in {{TenantName}} cluster repository.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.322
fluidFSEventComponentLocalGroupsCreateSuccessThe user {{userName}} has successfully added new Local Group '{{localAccountName}}' to {{TenantName}} cluster repository.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.323
fluidFSEventComponentLocalGroupsDeleteSuccessThe user {{userName}} has successfully deleted Local Group '{{localAccountName}}' from {{TenantName}} cluster repository.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.324
fluidFSEventComponentLocalGroupsModifySuccessThe user {{userName}} has successfully modified Local Group '{{localAccountName}}' in {{TenantName}} cluster repository.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.325
fluidFSEventComponentUserDatabaseModifySuccessThe user {{userName}} has successfully re-configured UNIX external repository of {{TenantName}} to use '{{userDatabaseType}}' accounts database.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.326
fluidFSEventComponentMappingPolicyModifySuccessThe user {{userName}} has successfully re-configured users mapping policy of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.327
fluidFSEventComponentManualMappingsCreateSuccessThe user {{userName}} has successfully added new manual mapping rule between Windows user '{{windowsUserName}}' and UNIX user '{{unixUserName}}' on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.328
fluidFSEventComponentManualMappingsDeleteSuccessThe user {{userName}} has successfully deleted manual mapping rule between Windows user '{{windowsUserName}}' and UNIX user '{{unixUserName}}' on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.329
fluidFSEventComponentManualMappingsModifySuccessThe user {{userName}} has successfully modified manual mapping rule between Windows user '{{windowsUserName}}' and UNIX user '{{unixUserName}}' on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.330
fluidFSEventComponentQuotaRuleCreateSuccessThe user {{userName}} created quota rule on volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.331
fluidFSEventComponentQuotaRuleModifySuccessThe user {{userName}} modified quota rule on volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.332
fluidFSEventComponentQuotaRuleDeleteSuccessThe user {{userName}} deleted quota rule on volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.333
fluidFSEventComponentCifsProtocolModifySuccessThe user {{userName}} updated the general local users settings of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.334
fluidFSEventComponentFileCloningSuccessThe user {{userName}} cloned ({{FSIDName}}){{SourceFilePath}} to ({{FSIDName}}){{DestinationDir}}/{{DestinationFileName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.335
fluidFSEventComponentFolderCreateSuccessThe user {{userName}} created {{DestinationParentDir}}/{{DestinationDir}} directory on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.336
fluidFSEventComponentNfsProtocolModifySuccessThe user {{userName}} updated the general NFS settings of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.337
fluidFSEventComponentVirtualVolumeFolderCreateSuccessThe user {{userName}} created {{VirtualVolumeFolderName}} NAS volumes folder on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.338
fluidFSEventComponentVirtualVolumeFolderModifySuccessThe user {{userName}} updated {{VirtualVolumeFolderName}} NAS volumes folder on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.339
fluidFSEventComponentVirtualVolumeFolderDeleteSuccessThe user {{userName}} deleted {{VirtualVolumeFolderName}} NAS volumes folder on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.340
fluidFSEventComponentRunHdfsDiagnosticSuccessThe user {{userName}} ran HDFS diagnostic. Description: The user {{userName}} ran HDFS diagnostic.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.341
fluidFSEventComponentRunHdfsDiagnosticActionFailureHdfs diagnostic failed. Description: Hdfs diagnostic, which was run by user {{userName}} failed.[[nl]]{{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.342
fluidFSEventComponentReplicationModifyRetPolicyThe user {{userName}} has modified the replication snapshot retention. Description: The user {{userName}} has modified the replication snapshot retention policy for replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.343
fluidFSEventComponentHdfsDiagnosticsFailedFailed to generate diagnostics package for 'HdfsDiagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.344
fluidFSEventComponentHdfsDiagnosticsOkPackage generation for 'HdfsDiagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.345
fluidFSEventComponentActiveDirectoryPreferredDcSuccessThe user {{userName}} has successfully configured preferred domain controllers of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.346
fluidFSEventComponentFileCopySuccessThe user {{userName}} copied {{SourceFSIDName}}\{{SourceFilePath}} to {{DestinationFSIDName}}\{{DestinationFilePath}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.347
fluidFSEventComponentFileCopyFailureThe user {{userName}} failed to copy {{SourceFSIDName}}\{{SourceFilePath}} to {{DestinationFSIDName}}\{{DestinationFilePath}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.348
fluidFSEventComponentLogoffActiveProtocolSessionGeneralSuccessNAS Administrator '{{administrator}}' closed {{ClientProtocol}} connection(s) on {{TenantName}}. Filter details: {{ClientProtocolDetails}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.349
fluidFSEventComponentCloseOpenFileGeneralSuccessNAS Administrator '{{administrator}}' closed file(s) on {{TenantName}}. Filter details: {{ClientProtocolDetails}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.350
fluidFSEventComponentFlashClusterSuccessEvent{{userName}} successfully flashed cluster with service pack file {{servicePackFileName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.351
fluidFSEventComponentFlashClusterFailedEvent{{userName}} failed to flash cluster with service pack file {{servicePackFileName}}. {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.352
fluidFSEventComponentSmbShareSecurityDescriptorModifySuccessThe user {{userName}} modified ACL on the root folder of SMB share {{shareName}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.353
fluidFSEventComponentRedirectionFolderAddSuccessThe user {{userName}} added redirection on the folder {{FolderPath}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.354
fluidFSEventComponentRedirectionFolderModifySuccessThe user {{userName}} modified redirection on the folder {{DSIDPath}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.355
fluidFSEventComponentRedirectionFolderDeleteSuccessThe user {{userName}} deleted redirection on the folder {{DSIDPath}} on NAS volume {{FSIDName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.356
fluidFSEventComponentFtpProtocolModifySuccessThe user {{userName}} updated the FTP configuration of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.357
fluidFSEventComponentReplicationActionModifyBwLimiterSuccessThe user {{userName}} has modified the BW limiter for replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.358
fluidFSEventComponentGpoModifySuccessGPO configuration of {{TenantName}} was modified successfully Description: The user {{userName}} has successfully modified the GPO configuration of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.359
fluidFSEventComponentGpoTriggerSuccessGroup policy polling was triggered successfully on {{TenantName}} Description: The user {{userName}} has triggered group policy polling successfully on {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.360
fluidFSEventComponentTenantPublicIPsModifySuccessThe user {{userName}} updated the configuration of {{TenantName}} client network Public IPs.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.361
fluidFSEventComponentReplicationActionModifyCompressionAndDedupSuccessThe user {{userName}} has modifyed the compression and deduplication mode for replication between {{FSIDName}} and {{remoteVolume}}@{{remoteSystemName}} NAS volumes.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.362
fluidFSEventComponentExampleActionSyncSuccessExample action with sync succeeded.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.363
fluidFSEventComponentExampleActionSyncFailedFailed to perform example action with sync. Error: {{retcodeString}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.364
fluidFSEventComponentAdminSubnetModifySuccessManagement subnet {{networkId}}/{{prefix}} was successfully modified by {{userName}}. State is {{state}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.365
fluidFSEventComponentTriggerPhoneHomeSuccessThe user {{userName}} triggered phone home.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.366
fluidFSEventComponentInterfaceRolesModifySuccessInterface Roles for NAS Appliance {{applianceId}} were successfully modified by user {{userName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.367
fluidFSEventComponentSmbDiagnosticOkPackage generation for 'SMB Diagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.368
fluidFSEventComponentSmbDiagnosticFailedFailed to generate diagnostics package for 'SMB Diagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.369
fluidFSEventComponentNfsDiagnosticOkPackage generation for 'NFS Diagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.370
fluidFSEventComponentNfsDiagnosticFailedFailed to generate diagnostics package for 'NFS Diagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.371
fluidFSEventComponentFtpDiagnosticOkPackage generation for 'FTP Diagnostics' completed successfully.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.372
fluidFSEventComponentFtpDiagnosticFailedFailed to generate diagnostics package for 'FTP Diagnostics'. {{retcodeString}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.373
fluidFSEventComponentActiveDirectorySetKrbCompoundAuthSuccessThe user {{userName}} has successfully configured Kerberos Compound Authentication support for the cluster {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.374
fluidFSEventComponentHdfsProtocolModifySuccessThe user {{userName}} updated the HDFS configuration of {{TenantName}}.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.15.375
fluidFSEventsSupportShell
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.16
fluidFSEventSupportShellSecureConsoleAccessDisabledReservationSecure Console Access on NAS Controller {{node}} cannot be enabled Description: Secure Console Access session on NAS Controller {{node}} had been disconnected from the server side or the system is disabled on the reservation web server
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.4
fluidFSEventSupportShellSecureConsoleAccessSshTunnelFailureSecure Console Access failure on NAS Controller {{node}} Description: Secure Console Access session on NAS Controller {{node}} had been disconnected due to SSH tunnel failure
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.5
fluidFSEventSupportShellSecureConsoleAccessSessionStartFailedFailed to establish the Secure Console Access session Description: Failed to establish the Secure Console Access session on NAS Controller {{node}} due to error response from the reservation web server
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.6
fluidFSEventSupportShellSecureConsoleAccessSessionExpiredSecure Console Access session on NAS Controller {{node}} had expired Description: Secure Console Access session on NAS Controller {{node}} had been disconnected due to TTL expiry
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.7
fluidFSEventSupportShellSupportShellLoginUser logged-in into Support Shell Description: User {{userName}} logged-in into support shell in NAS Controller {{node}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.8
fluidFSEventSupportShellSupportShellLogoutUser logged-out from Support Shell Description: User {{userName}} logged-out from support shell in NAS Controller {{node}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.9
fluidFSEventSupportShellSupportShellCommandInvokationUser executed command in Support Shell Description: User {{userName}} executed command {{command}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.16.10
fluidFSEventsAuditing
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.17
fluidFSEventAuditingSuccessfulAuditWriteSuccessful Write by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful write operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.23
fluidFSEventAuditingSuccessfulAuditReadSuccessful Read by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful read operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.24
fluidFSEventAuditingSuccessfulAuditDeleteSuccessful Delete by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful delete operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.25
fluidFSEventAuditingSuccessfulAuditReadAttrSuccessful Read Attributes by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful read attributes operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.26
fluidFSEventAuditingSuccessfulAuditWriteAttrSuccessful Write Attributes by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful write attributes operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.27
fluidFSEventAuditingSuccessfulAuditWriteOwnerSuccessful Change Owner by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful change owner operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.28
fluidFSEventAuditingSuccessfulAuditWriteDACLSuccessful Change permissions by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful write to DACL operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.29
fluidFSEventAuditingSuccessfulAuditAccessSACLSuccessful System Security Access by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful access to SACL operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.30
fluidFSEventAuditingSuccessfulAuditReadCtlSuccessful Read Security Descriptor by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a successful read security descriptor operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.31
fluidFSEventAuditingFailedAuditWriteFailed Write by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed write operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.32
fluidFSEventAuditingFailedAuditReadFailed Read by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed read operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.33
fluidFSEventAuditingFailedAuditDeleteFailed Delete by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed delete operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.34
fluidFSEventAuditingFailedAuditReadAttrFailed Read Attributes by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed read attributes operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.35
fluidFSEventAuditingFailedAuditWriteAttrFailed Write Attributes by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed write attributes operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.36
fluidFSEventAuditingFailedAuditWriteOwnerFailed Change Owner by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed change owner operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.37
fluidFSEventAuditingFailedAuditWriteDACLFailed Change permissions by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed write to DACL operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.38
fluidFSEventAuditingFailedAuditAccessSACLFailed Access to SACL by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed access to SACL operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.39
fluidFSEventAuditingFailedAuditReadCtlFailed Read Security Descriptor by {{uName}} on {{nName}}/{{dPath}} Description: The User {{uName}} performed a failed read security descriptor operation on file {{nName}}/{{dPath}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.40
fluidFSEventAuditingFailedAuditDeleteNameFailed Delete by {{uName}} on {{nName}}/{{name}} Description: The User {{uName}} performed a failed delete operation on file {{nName}}/{{name}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.41
fluidFSEventAuditingSuccessfulAuditDeleteNameSuccessful Delete by {{uName}} on {{nName}}/{{name}} Description: The User {{uName}} performed a successful delete operation on file {{nName}}/{{name}}. The Desired access mask: {{desiredCifsAccessMaskName}}
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.17.42
fluidFSEventsUpgrade
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.20.18
fluidFSEventUpgradeFailedToReadFileInformationFail to read information of file {{servicePackName}} while checking for new service pack. File was removed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.1
fluidFSEventUpgradeFailedToGetFileSizeFail to get size of file {{servicePackName}} while checking for new service pack. File was removed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.2
fluidFSEventUpgradeInvalidFileFormatOrChecksumFile {{servicePackName}} is not a valid package for upgrade. File was removed
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.3
fluidFSEventUpgradeServicePackIsOlderThanCurrentVersionThe service pack {{servicePackName}} was removed because its version is older than current one
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.4
fluidFSEventUpgradeServicePackHasOldVersionThe service pack {{servicePackName}} was removed because its version is older than available versions on the current node
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.5
fluidFSEventUpgradeServicePackAlreadyExistsThe service pack {{servicePackName}} was removed because file with the same version already exists
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.6
fluidFSEventUpgradeMonitoringDataCorruptionFailed to recover the monitored data after upgrade because of corruption
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.7
fluidFSEventUpgradeServicePackDownloadedNew service pack {{servicePackName}} downloaded
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.20.18.8
fluidFSEventsParams
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21
fluidFSEventsParamsAdmin
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.1
fluidFSEventsParamsAdminUsernameUser name which performed the operationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.1
fluidFSEventsParamsAdminAdministratorSystem administratorro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.2
fluidFSEventsParamsAdminLocaluserLocal user namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.3
fluidFSEventsParamsAdminLocalgroupLocal group namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.4
fluidFSEventsParamsAdminTenantIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.5
fluidFSEventsParamsAdminVirtualVolumeNAS volumero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.6
fluidFSEventsParamsAdminHostAntivirus hostro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.7
fluidFSEventsParamsAdminPortAntivirus portro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.1.8
fluidFSEventsParamsAdminShareNameSMB share namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.9
fluidFSEventsParamsAdminNodeIdNode idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.1.10
fluidFSEventsParamsAdminPidProcess idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.1.11
fluidFSEventsParamsAdminVirtualInterfaceVirtual interfacero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.12
fluidFSEventsParamsAdminClusterNameCluster namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.13
fluidFSEventsParamsAdminSnapshotNameSnapshot namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.14
fluidFSEventsParamsAdminNewSnapshotNameNew snapshot namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.15
fluidFSEventsParamsAdminStaticRoutesStatic routes listro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.16
fluidFSEventsParamsAdminNFSExportPathPath of NFS exportro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.17
fluidFSEventsParamsAdminQuotaUserNameUser name on which the quota is definedro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.18
fluidFSEventsParamsAdminQuotaGroupNameGroup name on which the quota is definedro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.19
fluidFSEventsParamsAdminFileLevelReplicationScheduleScheduling configuration of file level replicationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.20
fluidFSEventsParamsAdminReplicationSourceSource volume of block level replication (volume@cluster)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.21
fluidFSEventsParamsAdminReplicationDestinationDestination volume of block level replication (volume@cluster)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.22
fluidFSEventsParamsAdminReplicationSourceVolumeSource volume of block level replicationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.23
fluidFSEventsParamsAdminReplicationDestinationVolumeDestination volume of block level replicationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.24
fluidFSEventsParamsAdminReplicationDestinationClusterDestination cluster of block level replicationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.25
fluidFSEventsParamsAdminFileLevelReplicationTaskTask name of file level replicationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.26
fluidFSEventsParamsAdminTrustedClusterTrusted cluster namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.27
fluidFSEventsParamsAdminPackageNamePackage namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.28
fluidFSEventsParamsAdminCIFSShareNamesCIFSShareNamesro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.29
fluidFSEventsParamsAdminSubnetNameSubnet namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.30
fluidFSEventsParamsAdminSrcUsernameSource user for user mappingro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.31
fluidFSEventsParamsAdminDstUsernameDestination user for user mappingro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.32
fluidFSEventsParamsAdminGuestAccountUsernameProtocols guest accountro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.33
fluidFSEventsParamsAdminUsersRepositoryTypeUsers repository type (Windows/Unix...)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.34
fluidFSEventsParamsAdminComponentThe API componentro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.35
fluidFSEventsParamsAdminArgsListThe input argumentsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.36
fluidFSEventsParamsAdminNodeIdEvenEven Controller idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.37
fluidFSEventsParamsAdminNodeIdOddOdd Controller idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.38
fluidFSEventsParamsAdminNewSizeSize being added to the FS (GB)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.39
fluidFSEventsParamsAdminLunsListList of LUN id'sro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.40
fluidFSEventsParamsAdminSpVersionSP Versionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.41
fluidFSEventsParamsAdminUnsignedNodeIdNode idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.42
fluidFSEventsParamsAdminOldSizeCurrent size of the FS (GB)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.43
fluidFSEventsParamsAdminSpErrorSP Error reasonro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.44
fluidFSEventsParamsAdminGeneralEventTextA general free text parameter, that can be sent to EQL which does not support it yetro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.45
fluidFSEventsParamsAdminNewAtimeValueNew value of atime granularityro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.46
fluidFSEventsParamsAdminDiagnosticNameThe diagnostic namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.47
fluidFSEventsParamsAdminWWNPort1WWN Port1ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.48
fluidFSEventsParamsAdminWWNPort2WWN Port2ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.49
fluidFSEventsParamsAdminNumLunsNumber of LUNs added to the FSro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.50
fluidFSEventsParamsAdminUiThe interface namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.51
fluidFSEventsParamsAdminErrCodeInternal code of errorro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.1.52
fluidFSEventsParamsAdminControllerIdController IDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.53
fluidFSEventsParamsAdminApplianceIdNAS appliance IDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.54
fluidFSEventsParamsAdminApplianceServiceTagNAS appliance service tagro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.55
fluidFSEventsParamsAdminEscalationPeriodInMinutesEscalation Expiration Period (Minutes)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.56
fluidFSEventsParamsAdminObjectNameName of the configuration objectro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.57
fluidFSEventsParamsAdminRecommendedMaxCountrecommended maximum amount of the configuration objectro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.1.58
fluidFSEventsParamsAdminFSIDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.1.59
fluidFSEventsParamsAdminTenantNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.60
fluidFSEventsParamsAdminVolumeNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.1.61
fluidFSEventsParamsHardware
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.2
fluidFSEventsParamsHardwareNodeNameController namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.1
fluidFSEventsParamsHardwareNetworkIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.2
fluidFSEventsParamsHardwarePrefixro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.3
fluidFSEventsParamsHardwareCpuNameCPU name in the controllerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.4
fluidFSEventsParamsHardwareCpuTemperatureCPU tempraturero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.5
fluidFSEventsParamsHardwareVlanTagro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.6
fluidFSEventsParamsHardwareDestinationNetworkro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.7
fluidFSEventsParamsHardwareCpuSpeedCPU speedro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.8
fluidFSEventsParamsHardwareAverageSpeedAverage CPU speedro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.9
fluidFSEventsParamsHardwareNodeIdController idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.10
fluidFSEventsParamsHardwareNetworkNameNetwork namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.11
fluidFSEventsParamsHardwarePacketLossPacket loss percentagero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.12
fluidFSEventsParamsHardwareEthNameEth namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.13
fluidFSEventsParamsHardwareLunIdLUN SCSI IDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.14
fluidFSEventsParamsHardwareFromNodero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.15
fluidFSEventsParamsHardwareToNodero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.16
fluidFSEventsParamsHardwareFromEthro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.17
fluidFSEventsParamsHardwareToEthro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.18
fluidFSEventsParamsHardwareTapeNameTape device namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.19
fluidFSEventsParamsHardwareBatteryPercentageBPS battery percentagero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.20
fluidFSEventsParamsHardwareBatteryRemainTimeBPS battery remaining timero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.21
fluidFSEventsParamsHardwareSubnetNameSubnet namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.22
fluidFSEventsParamsHardwareHostNameHost namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.23
fluidFSEventsParamsHardwareBatteryLastReplaceBattery Last Replacero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.24
fluidFSEventsParamsHardwareDeviceTypeNameDevice Type Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.25
fluidFSEventsParamsHardwareDeviceNameDevice Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.26
fluidFSEventsParamsHardwareTemperatureTemperaturero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.27
fluidFSEventsParamsHardwareMeltingDistanceMelting Distancero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.28
fluidFSEventsParamsHardwareDeviceStateDevice Statero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.29
fluidFSEventsParamsHardwareFirstNodeIdFirst Controller IDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.30
fluidFSEventsParamsHardwareSecondNodeIdSecond Controller IDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.31
fluidFSEventsParamsHardwareBondNameBond Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.32
fluidFSEventsParamsHardwareBandwidthBandwidthro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.33
fluidFSEventsParamsHardwareDiskNameLocal disk namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.34
fluidFSEventsParamsHardwareMemoryFirstNodeMemory on first controllerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.35
fluidFSEventsParamsHardwareMemorySecondNodeMemory on second controllerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.36
fluidFSEventsParamsHardwareActualMtuActual MTUro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.37
fluidFSEventsParamsHardwareOptimalMtuOptimal Mturo
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.38
fluidFSEventsParamsHardwareBpsLogInfoBps Log Inforo
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.39
fluidFSEventsParamsHardwareBpsAlarmBPS Alarm messagero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.40
fluidFSEventsParamsHardwarePowerSuppliesRedundancyStatuspower supplies redundancy statusro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.41
fluidFSEventsParamsHardwarePowerSuppliesElementStatuspower supplies element statusro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.42
fluidFSEventsParamsHardwarePowerSuppliesElementLocationpower supplies element locationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.43
fluidFSEventsParamsHardwarePowerSuppliesElementsCountThe number of power supplies elementsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.44
fluidFSEventsParamsHardwareChassisIDAppliance chassis IDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.45
fluidFSEventsParamsHardwareTemperatureSensorNameTemperature sensor namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.46
fluidFSEventsParamsHardwareTemperatureSensorStatusTemperature sensor statusro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.47
fluidFSEventsParamsHardwareTemperatureSensorValueTemperature sensor valuero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.48
fluidFSEventsParamsHardwareTemperatureSensorErrorThresholdTemperature sensor error thresholdro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.49
fluidFSEventsParamsHardwareTemperatureSensorWarningThresholdTemperature sensor warning thresholdro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.50
fluidFSEventsParamsHardwarePowerSupplyNamePower supply namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.51
fluidFSEventsParamsHardwarePowerSupplyStatusPower supply statusro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.52
fluidFSEventsParamsHardwareBpsNameBPS namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.53
fluidFSEventsParamsHardwareBpsStatusBPS statusro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.54
fluidFSEventsParamsHardwareBpsBatteryRuntimeBPS battery runtimero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.55
fluidFSEventsParamsHardwareBpsBatteryChargeBPS battery chargero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.56
fluidFSEventsParamsHardwareComponentIndexComponent index in group of componentsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.57
fluidFSEventsParamsHardwareChassisIddeprecated - a duplication of above parameter chassisIDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.58
fluidFSEventsParamsHardwareApplianceServiceTagAppliance service tagro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.59
fluidFSEventsParamsHardwareApplianceIdAppliance indexro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.60
fluidFSEventsParamsHardwareFcHbaNameFibre channel HBA port namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.61
fluidFSEventsParamsHardwareComponentNameComponent name in group of componentsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.62
fluidFSEventsParamsHardwareContextBasedServiceTagContrller or appliance service tagro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.63
fluidFSEventsParamsHardwareTargetEthNameTarget eth name in mesh connectivity monitoringro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.64
fluidFSEventsParamsHardwareIpMonitored external server ipro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.65
fluidFSEventsParamsHardwareExtSrvTypeMonitored external server ipro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.66
fluidFSEventsParamsHardwareDiskModelLocal disk model namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.67
fluidFSEventsParamsHardwareDiskSerialLocal disk serial numberro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.68
fluidFSEventsParamsHardwareDiskOverallReadsDisk overall reads in MBro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.69
fluidFSEventsParamsHardwareDiskOverallWritesDisk overall writes in MBro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.70
fluidFSEventsParamsHardwareBadSectorsCountHDD bad sectors countro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.71
fluidFSEventsParamsHardwareFailedWritesCountSSD failed writes countro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.72
fluidFSEventsParamsHardwareSupportedModelsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.73
fluidFSEventsParamsHardwareIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.74
fluidFSEventsParamsHardwarePciSlotSlot numberro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.2.75
fluidFSEventsParamsHardwarePciCardFull description of a PCI cardro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.2.76
fluidFSEventsParamsNdmp
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.3
fluidFSEventsParamsNdmpSessionIdNDMP job session idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.3.1
fluidFSEventsParamsNdmpJobTypeNDMP job type (backup/restore)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.3.2
fluidFSEventsParamsNdmpPathTarget pathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.3.3
fluidFSEventsParamsNdmpStartTimestampNDMP session start timestampro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.3.4
fluidFSEventsParamsNdmpInitiatorDMAServerDMA server that initiated the sessionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.3.5
fluidFSEventsParamsNdmpExecutedOnNodeNode that executes the jobro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.3.6
fluidFSEventsParamsNdmpNDMPMessageEvent message sent from NDMPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.3.7
fluidFSEventsParamsNdmpDetailEvent message sent from NDMPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.3.8
fluidFSEventsParamsQuota
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.4
fluidFSEventsParamsQuotaUserNameUser namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.2
fluidFSEventsParamsQuotaGroupNameGroup namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.3
fluidFSEventsParamsQuotaVolumeSizeVolume sizero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.4
fluidFSEventsParamsQuotaVolumeSpaceThresholdVolume space thresholdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.5
fluidFSEventsParamsQuotaSnapshotsSpaceThresholdSnapshots space thresholdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.6
fluidFSEventsParamsQuotaQuotaThresholdQuota threshold for user or groupro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.7
fluidFSEventsParamsQuotaVolumeFreeSpaceVolume free spacero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.8
fluidFSEventsParamsQuotaSystemCapacityCapacity of the systemro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.9
fluidFSEventsParamsQuotaSystemThresholdSystem thresholdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.10
fluidFSEventsParamsQuotaQuotaDirPathThe path of the Directory Quotaro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.11
fluidFSEventsParamsQuotaVirtualVolumeNAS volume FSIDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.4.12
fluidFSEventsParamsQuotaVirtualVolumeNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.13
fluidFSEventsParamsQuotaUserNameNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.14
fluidFSEventsParamsQuotaGroupNameNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.4.15
fluidFSEventsParamsReplication
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.5
fluidFSEventsParamsReplicationSourceClusterSource clusterro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.2
fluidFSEventsParamsReplicationDestinationClusterDestination clusterro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.4
fluidFSEventsParamsReplicationErrorCodeError codero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.5.5
fluidFSEventsParamsReplicationTaskNameTask name of file level replicationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.6
fluidFSEventsParamsReplicationErrorDescError descriptionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.7
fluidFSEventsParamsReplicationOldMngConVipOld manage console VIPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.8
fluidFSEventsParamsReplicationNewMngConVipNew manage console VIPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.9
fluidFSEventsParamsReplicationStartTimereplication start timero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.10
fluidFSEventsParamsReplicationEndTimereplication end timero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.11
fluidFSEventsParamsReplicationTotalTransferredSizetotal transferred sizero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.12
fluidFSEventsParamsReplicationRehydratedVolumeSizerehydrated volume sizero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.13
fluidFSEventsParamsReplicationSourceVolumeSource NAS volume FSIDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.5.14
fluidFSEventsParamsReplicationDestinationVolumeDestination NAS volumero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.5.15
fluidFSEventsParamsReplicationDomainIddomain Idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.16
fluidFSEventsParamsReplicationSnapshotIdsnapshot Idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.17
fluidFSEventsParamsReplicationDomainReplicationStatsdomain replication statsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.18
fluidFSEventsParamsReplicationSavingsPercentro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.19
fluidFSEventsParamsReplicationSourceVolumeNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.20
fluidFSEventsParamsReplicationDestinationVolumeNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.5.21
fluidFSEventsParamsSnapshot
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.7
fluidFSEventsParamsSnapshotSnapshotNameSnapshot namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.7.1
fluidFSEventsParamsSnapshotVolumeNameVolume namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.7.2
fluidFSEventsParamsSnapshotFSIDNAS volume idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.7.3
fluidFSEventsParamsSnapshotOutputFileNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.7.4
fluidFSEventsParamsSnapshotOutputFSIDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.7.5
fluidFSEventsParamsSnapshotOutputPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.7.6
fluidFSEventsParamsSnapshotFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.7.7
fluidFSEventsParamsSnapshotOutputFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.7.8
fluidFSEventsParamsHealth
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.9
fluidFSEventsParamsHealthPercentOfUsedSpacePercentage of system used spacero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.1
fluidFSEventsParamsHealthNodeNameNode namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.2
fluidFSEventsParamsHealthServiceService namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.3
fluidFSEventsParamsHealthPartitionNameLocal partition namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.4
fluidFSEventsParamsHealthPercentOfUsedSwapPercent of used swap memoryro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.5
fluidFSEventsParamsHealthNodeIdsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.6
fluidFSEventsParamsHealthPercentOfUsedFileDescriptorsPercent of used file descriptorsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.7
fluidFSEventsParamsHealthThisNodeIdNode id of the current nodero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.8
fluidFSEventsParamsHealthPeerNodeIdNode id of the peer nodero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.9
fluidFSEventsParamsHealthVirtualVolumeNAS volume namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.10
fluidFSEventsParamsHealthFSIDNAS volume idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.11
fluidFSEventsParamsHealthMinFreeSpaceInBytesFree space in bytesro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.12
fluidFSEventsParamsHealthModuleNameThe BMR module namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.13
fluidFSEventsParamsHealthNumberOfClientsNumber of clientsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.14
fluidFSEventsParamsHealthDomainIdId of the domain from which the event was raisedro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.15
fluidFSEventsParamsHealthServiceNameThe name of the servicero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.16
fluidFSEventsParamsHealthSynchronizedServiceNameThe name of the service being synchronizedro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.17
fluidFSEventsParamsHealthTimeoutThe timeout in minutesro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.18
fluidFSEventsParamsHealthStorageIdInternal id of a storagero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.19
fluidFSEventsParamsHealthSynchronizedStorageIdInternal id of a storage being synchronizedro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.20
fluidFSEventsParamsHealthNodeIdId of a nodero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.21
fluidFSEventsParamsHealthSetIdId of a LUNs' setro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.22
fluidFSEventsParamsHealthLunIdId of a LUNro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.23
fluidFSEventsParamsHealthHealthyNodeIdHealthy NAS controller idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.24
fluidFSEventsParamsHealthFaultyNodeIdFaulty NAS controller idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.25
fluidFSEventsParamsHealthFmsAdminCmdFMS Admin commandro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.26
fluidFSEventsParamsHealthQuorumIPFMS Quorum IPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.27
fluidFSEventsParamsHealthFmsStateFMS NAS controller Statero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.28
fluidFSEventsParamsHealthFsdInstanceFS Daemon instance in the nodero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.29
fluidFSEventsParamsHealthErrorDescriptionDescription of the errorro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.30
fluidFSEventsParamsHealthBacktraceDebug backtrace informationro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.31
fluidFSEventsParamsHealthDsidDSID (internal filesystem ID) of file or directory. Use dsid2name utility to translate dsid to path via command line, also dsid2path translator is designed to do it automatically for eventsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.32
fluidFSEventsParamsHealthFileMappingFS mapping from file range to disk range (hex offsets)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.33
fluidFSEventsParamsHealthParentDirDsidParent directory file idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.34
fluidFSEventsParamsHealthDirEntryDirectory entry pointing to a filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.35
fluidFSEventsParamsHealthPacketLossThresholdPercentPercents threashold for interconnect packet lossro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.36
fluidFSEventsParamsHealthFsLogicalErrorDescriptionInternal description of logical error found in the FS layoutro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.37
fluidFSEventsParamsHealthLowCacheThresholdPercentPercents threashold for low on cachero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.38
fluidFSEventsParamsHealthProtocolProtocolro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.39
fluidFSEventsParamsHealthConnectionsVectorConnections per nodesro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.40
fluidFSEventsParamsHealthAdClockSkewSkew between NAS controller and AD clocksro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.41
fluidFSEventsParamsHealthMaxAdClockSkewCritical skew between NAS controller and AD clocksro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.42
fluidFSEventsParamsHealthServerKindServer kindro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.43
fluidFSEventsParamsHealthResponseTimeResponse timero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.44
fluidFSEventsParamsHealthCriticalResponseTimeCritical response timero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.45
fluidFSEventsParamsHealthInternalInfoInternal failure info for RnD troubleshooting, for example slow request detailsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.46
fluidFSEventsParamsHealthServerIpsList of server IPsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.47
fluidFSEventsParamsHealthOldQuorumIPFMS old Quorum IPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.48
fluidFSEventsParamsHealthDedupSpaceMarginMbFree space needed for optimization of a volume, in Megabytesro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.49
fluidFSEventsParamsHealthOldNumberOfVirtualDomainsOld number of Virtual Domainsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.50
fluidFSEventsParamsHealthNewNumberOfVirtualDomainsNew number of Virtual Domainsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.51
fluidFSEventsParamsHealthNumberOfDomainsInPreviousDistributionNumber of virtual domains in the file's previous distributionro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.52
fluidFSEventsParamsHealthNumberOfDomainsInNewDistributionNumber of virtual domains in the file's new distributionro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.53
fluidFSEventsParamsHealthVirtualDomainThe number of the virtual domainro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.54
fluidFSEventsParamsHealthCurrentPhysicalDomainThe number of the physical domain that is currently holds the virtual domainro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.55
fluidFSEventsParamsHealthNewPhysicalDomainThe number of the physical domain that will hold the virtual domain after the hot migration process endsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.56
fluidFSEventsParamsHealthIpAddrIP Addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.57
fluidFSEventsParamsHealthMacAddrmac addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.58
fluidFSEventsParamsHealthLunsListA list of LUNs, comma separatedro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.59
fluidFSEventsParamsHealthTenantIdTenant unique identifierro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.60
fluidFSEventsParamsHealthServerNamesro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.61
fluidFSEventsParamsHealthDomainNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.62
fluidFSEventsParamsHealthServerListro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.63
fluidFSEventsParamsHealthDomainControllerNameActive Directory domain namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.64
fluidFSEventsParamsHealthFsidro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.65
fluidFSEventsParamsHealthTimeDiffSecro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.9.66
fluidFSEventsParamsHealthFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.67
fluidFSEventsParamsHealthParentDirDsidPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.68
fluidFSEventsParamsHealthTenantNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.69
fluidFSEventsParamsHealthDsidPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.9.70
fluidFSEventsParamsAntivirus
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.10
fluidFSEventsParamsAntivirusShareNamecifs share where scanning occursro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.1
fluidFSEventsParamsAntivirusVirusDescriptionbrief virus descriptionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.2
fluidFSEventsParamsAntivirusFilePathpath of the scanned filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.3
fluidFSEventsParamsAntivirusQuarantinedPathpath of the quarantined filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.4
fluidFSEventsParamsAntivirusInfectedActionaction applied to infected filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.5
fluidFSEventsParamsAntivirusAdsNamename of the ADSro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.6
fluidFSEventsParamsAntivirusSnapNamename of the snapshot for previous versionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.7
fluidFSEventsParamsAntivirusHostantivirus host hostname or IP addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.8
fluidFSEventsParamsAntivirusScanningFacilityactual antivirus host and port used for scanningro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.10
fluidFSEventsParamsAntivirusScanningDurationscanning duration, real number in seconds with enough precisionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.11
fluidFSEventsParamsAntivirusScanningDurationThresholdcritical scanning duration in seconds used as the threshold for eventro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.10.12
fluidFSEventsParamsAntivirusDsidDSID (internal filesystem ID) of file or directory. Use dsid2name utility to translate dsid to path via command line, also dsid2path translator is designed to do it automatically for eventsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.13
fluidFSEventsParamsAntivirusFSIDNAS volume idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.10.14
fluidFSEventsParamsAntivirusAccessDeniedReasonExtended details about reason of returned ACCESS_DENIED errorro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.15
fluidFSEventsParamsAntivirusFileSizeMbSize (in Megabytes) of the file to be scanned for virusesro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.10.16
fluidFSEventsParamsAntivirusLargeFileSizeLimitMbLimit of the file size (in Megabytes) of the file to be scanned for viruses. Larger files are not scanned.ro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.10.17
fluidFSEventsParamsAntivirusIcapStatusro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.18
fluidFSEventsParamsAntivirusServerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.19
fluidFSEventsParamsAntivirusPortantivirus host portro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.20
fluidFSEventsParamsAntivirusFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.21
fluidFSEventsParamsAntivirusDsidPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.10.22
fluidFSEventsParamsClientAccess
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.11
fluidFSEventsParamsClientAccessMaxConnectionsmaximal number of connectionsro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.1
fluidFSEventsParamsClientAccessNfsExportNFS export name, as defined on clusterro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.2
fluidFSEventsParamsClientAccessMountPathNFS mount path as specified by user for mount commandro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.3
fluidFSEventsParamsClientAccessNfsClientPortNFS client port numberro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.4
fluidFSEventsParamsClientAccessNfsExportOptionsNFS export options, as defined on clusterro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.5
fluidFSEventsParamsClientAccessClientIpAddrClient IP addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.6
fluidFSEventsParamsClientAccessNfsUserUser ID as seen from NFS server, either UID or SID. Will be translated to username by 'uidOrSid2name' translator automaticallyro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.7
fluidFSEventsParamsClientAccessCifsUserUser ID as seen from Samba - TUID. Will be translated to username by 'tuid2name' translator automaticallyro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.8
fluidFSEventsParamsClientAccessUserNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.9
fluidFSEventsParamsClientAccessCifsShareSMB share name, as defined on clusterro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.10
fluidFSEventsParamsClientAccessDsidDSID (internal filesystem ID) of file or directory. Use dsid2name utility to translate dsid to path.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.11
fluidFSEventsParamsClientAccessNfsOpNFS operation (NFS verb, command, etc)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.12
fluidFSEventsParamsClientAccessVolumeStyleVolume style - NTFS, UNIX or MIXEDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.13
fluidFSEventsParamsClientAccessUserOwnerUser owner for a filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.14
fluidFSEventsParamsClientAccessGroupOwnerGroup owner for a filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.15
fluidFSEventsParamsClientAccessUserIdentityTypeUser type (NTFS or UNIX, i.e. UID or SID)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.16
fluidFSEventsParamsClientAccessGroupIdentityType6roup type (NTFS or UNIX, i.e. GID or GSID)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.17
fluidFSEventsParamsClientAccessDesiredNfsAccessMask7esired access maskro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.18
fluidFSEventsParamsClientAccessGrantedNfsAccessMaskGranted (maximal) access maskro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.19
fluidFSEventsParamsClientAccessDesiredCifsAccessMaskDesired access maskro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.20
fluidFSEventsParamsClientAccessGrantedCifsAccessMaskGranted (maximal) access maskro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.21
fluidFSEventsParamsClientAccessMissedCifsAccessBitsMissed access bits (mask)ro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.22
fluidFSEventsParamsClientAccessCifsOpSMB operation (SMB verb, VFS verb, generic command, etc)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.23
fluidFSEventsParamsClientAccessCifsPrivilegesSMB User privilegesro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.24
fluidFSEventsParamsClientAccessCifsGuestAccountSMB guest account as configured on the clusterro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.25
fluidFSEventsParamsClientAccessNasContainerIdNAS Volume (volume name)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.26
fluidFSEventsParamsClientAccessNasContainerPathPath related to specified NAS Volumero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.27
fluidFSEventsParamsClientAccessNasControllerIdNAS controller ID (node ID)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.28
fluidFSEventsParamsClientAccessNasContainerIdIntegerNAS Volume ID (volume ID, i.e. FSID uint32 value). Will be translated to volume name by translatorro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.29
fluidFSEventsParamsClientAccessLockingUserUser identity who holds the lock on requested file and causing access conflictro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.30
fluidFSEventsParamsClientAccessInternalInfoInternal failure info for RnD troubleshooting, for example access decision flow or client disconnection reasonro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.31
fluidFSEventsParamsClientAccessNfsErrorCodeNFSERR_x code for troubleshooting purpose (as the part of internal info)ro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.32
fluidFSEventsParamsClientAccessOpenModeAccessBitsOpen mode access bits(mask) used during file openro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.33
fluidFSEventsParamsClientAccessShareLevelPermissionsModeShare-level permission mode applied for current connection, like NONE, READ, CHANGE or FULL-CONTROLro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.34
fluidFSEventsParamsClientAccessOperationoperation being executedro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.35
fluidFSEventsParamsClientAccessUserUser ID (will undergo transformation as required)ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.36
fluidFSEventsParamsClientAccessCifsUser2User SID as seen by likewise/cifs_serverro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.37
fluidFSEventsParamsClientAccessNetgroupNameUNIX external repository netgroup namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.38
fluidFSEventsParamsClientAccessParentNetgroupNameUNIX external repository netgroup namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.39
fluidFSEventsParamsClientAccessNetgroupThresholdCritical threshold of netgroup metric (like size or nesting level)ro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.40
fluidFSEventsParamsClientAccessNodeIdNode Id (NAS controller ID)ro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.41
fluidFSEventsParamsClientAccessMaxOpenFilesPerNodemaximal number of open files per nodero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.42
fluidFSEventsParamsClientAccessAdProviderNameName of active directory providerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.43
fluidFSEventsParamsClientAccessDomainNameDomain namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.44
fluidFSEventsParamsClientAccessFileExtensionFile extensionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.45
fluidFSEventsParamsClientAccessCifsErrorCodeCifs code for troubleshooting purpose (as the part of internal info)ro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.46
fluidFSEventsParamsClientAccessClusterVIPServer VIP addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.47
fluidFSEventsParamsClientAccessServerKindServer kindro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.48
fluidFSEventsParamsClientAccessServiceService namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.49
fluidFSEventsParamsClientAccessUserEmailro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.50
fluidFSEventsParamsClientAccessDroppedNotificationsCountercounts how many events were droppedro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.51
fluidFSEventsParamsClientAccessPolicyNamePolicy namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.52
fluidFSEventsParamsClientAccessPolicyGuidPolicy guidro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.53
fluidFSEventsParamsClientAccessPolicyTargetPathPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.54
fluidFSEventsParamsClientAccessTenantIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.55
fluidFSEventsParamsClientAccessTlsVersionVersion of TLS protocolro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.11.56
fluidFSEventsParamsClientAccessBaseLandingPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.57
fluidFSEventsParamsClientAccessSuffixLandingPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.58
fluidFSEventsParamsClientAccessFilePathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.59
fluidFSEventsParamsClientAccessSearchedObjectsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.60
fluidFSEventsParamsClientAccessRuleDNro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.61
fluidFSEventsParamsClientAccessPolicyDNro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.62
fluidFSEventsParamsClientAccessNasContainerIdIntegerNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.63
fluidFSEventsParamsClientAccessTenantNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.64
fluidFSEventsParamsClientAccessNfsUserNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.65
fluidFSEventsParamsClientAccessDsidPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.66
fluidFSEventsParamsClientAccessDesiredNfsAccessMaskHrfro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.67
fluidFSEventsParamsClientAccessGrantedNfsAccessMaskHrfro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.68
fluidFSEventsParamsClientAccessUserOwnerNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.69
fluidFSEventsParamsClientAccessGroupOwnerNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.70
fluidFSEventsParamsClientAccessDesiredCifsAccessMaskNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.71
fluidFSEventsParamsClientAccessMissedCifsAccessBitsNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.72
fluidFSEventsParamsClientAccessOpenModeAccessBitsNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.73
fluidFSEventsParamsClientAccessCifsUser2Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.11.74
fluidFSEventsParamsLicensing
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.13
fluidFSEventsParamsLicensingFileNameName of the license xml filero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.13.1
fluidFSEventsParamsLicensingInstalledFeaturesList of the features which were installed, seperated by commasro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.13.2
fluidFSEventsParamsLicensingNumOfDaysNumber of days till expiration of featurero
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.13.3
fluidFSEventsParamsLicensingFluidFsVersionFluidFS software versionro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.13.4
fluidFSEventsParamsExaminer
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.14
fluidFSEventsParamsExaminerCategoryCorruption categoryro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.14.1
fluidFSEventsParamsExaminerLevelLevel of the errorro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.14.2
fluidFSEventsParamsComponent
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.15
fluidFSEventsParamsComponentUserNameUser namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.1
fluidFSEventsParamsComponentObjectIdobjectIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.2
fluidFSEventsParamsComponentTimezonetimezonero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.3
fluidFSEventsParamsComponentNameNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.4
fluidFSEventsParamsComponentRetcodeStringRetCode stringro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.5
fluidFSEventsParamsComponentRemoteVolumeRemote Volumero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.6
fluidFSEventsParamsComponentSystemServiceStateSystem Service Modero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.7
fluidFSEventsParamsComponentAdministratorSystem administratorro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.8
fluidFSEventsParamsComponentSnapshotIDSnapshot idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.10
fluidFSEventsParamsComponentNdmpLockNdmpLockro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.11
fluidFSEventsParamsComponentExpiryExpiryro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.12
fluidFSEventsParamsComponentShareNameName of the SMB sharero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.13
fluidFSEventsParamsComponentNFSExportPathPath that is exported by NFS filesystemro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.14
fluidFSEventsParamsComponentDomainDomainro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.15
fluidFSEventsParamsComponentUserInterfaceTypeUser interface typero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.16
fluidFSEventsParamsComponentUserInterfaceClientUser interface clientro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.17
fluidFSEventsParamsComponentRemoteSystemNameSystem (cluster) namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.18
fluidFSEventsParamsComponentApplianceServiceTagNAS appliance service tagro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.19
fluidFSEventsParamsComponentServicePackFileNameService pack file namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.20
fluidFSEventsParamsComponentNetworkIdNetwork IP addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.21
fluidFSEventsParamsComponentNetmaskNetwork netmaskro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.22
fluidFSEventsParamsComponentSubnetAccessSubnet Access typero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.23
fluidFSEventsParamsComponentRouteNameRoute Rules unique namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.24
fluidFSEventsParamsComponentRouteGatewayRoute Rules Gateway IPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.25
fluidFSEventsParamsComponentClientNetworkInterfaceMtuMTUro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.26
fluidFSEventsParamsComponentClientNetworkInterfaceBondModeBonding modero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.27
fluidFSEventsParamsComponentLocalAccountNameLocal user/group namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.28
fluidFSEventsParamsComponentUserDatabaseTypeType of external UNIX accounts repository: NIS, LDAP or None.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.29
fluidFSEventsParamsComponentWindowsUserUser name from Windows repositoryro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.30
fluidFSEventsParamsComponentUnixUserUser name from UNIX repositoryro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.31
fluidFSEventsParamsComponentBlink1Blink first controllerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.32
fluidFSEventsParamsComponentBlink2Blink second controllerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.33
fluidFSEventsParamsComponentControllerIdThe controller IDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.34
fluidFSEventsParamsComponentClientIpClient Ipro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.35
fluidFSEventsParamsComponentAccessIpAccess Ipro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.36
fluidFSEventsParamsComponentNodeIdNode Idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.37
fluidFSEventsParamsComponentNetworkInterfaceNetwork Interfacero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.38
fluidFSEventsParamsComponentPinStatePin or Unpin client to specific controllerro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.39
fluidFSEventsParamsComponentApplianceIdAppliance Idro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.40
fluidFSEventsParamsComponentClusterNameCluster Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.41
fluidFSEventsParamsComponentLicensedFeatureLicensed Featurero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.42
fluidFSEventsParamsComponentFabricNameFabric Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.43
fluidFSEventsParamsComponentSourceFilePathSource File Pathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.44
fluidFSEventsParamsComponentDestinationDirDestination Directoryro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.45
fluidFSEventsParamsComponentDestinationFileNameDestination File Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.46
fluidFSEventsParamsComponentDestinationParentDirDestination Parent Directoryro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.47
fluidFSEventsParamsComponentNDMPSessionIdNDMP Session IDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.48
fluidFSEventsParamsComponentClientComputerNameClient Computer Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.49
fluidFSEventsParamsComponentClientUserNameClient User Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.50
fluidFSEventsParamsComponentPartnerIpPartner IPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.51
fluidFSEventsParamsComponentVirtualVolumeFolderNameVirtual Volume Folder Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.52
fluidFSEventsParamsComponentPrefixNetwork prefixro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.53
fluidFSEventsParamsComponentRunCifsFileAccessibilityDiagnosticShareNameRunCifsFileAccessibilityDiagnosticShareNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.54
fluidFSEventsParamsComponentRunCifsFileAccessibilityDiagnosticClientIPRunCifsFileAccessibilityDiagnosticClientIPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.55
fluidFSEventsParamsComponentRunCifsFileAccessibilityDiagnosticPathRunCifsFileAccessibilityDiagnosticPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.56
fluidFSEventsParamsComponentRunClientConnectivityDiagnosticClientIPRunClientConnectivityDiagnosticClientIPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.57
fluidFSEventsParamsComponentRunClientConnectivityDiagnosticProtocolRunClientConnectivityDiagnosticProtocolro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.58
fluidFSEventsParamsComponentRunNetworkDiagnosticClientIPRunNetworkDiagnosticClientIPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.59
fluidFSEventsParamsComponentRunNfsFileAccessibilityDiagnosticExportPathRunNfsFileAccessibilityDiagnosticExportPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.60
fluidFSEventsParamsComponentRunNfsFileAccessibilityDiagnosticFSIDRunNfsFileAccessibilityDiagnosticFSIDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.61
fluidFSEventsParamsComponentRunNfsFileAccessibilityDiagnosticClientIPRunNfsFileAccessibilityDiagnosticClientIPro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.62
fluidFSEventsParamsComponentRunNfsFileAccessibilityDiagnosticPathRunNfsFileAccessibilityDiagnosticPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.63
fluidFSEventsParamsComponentRunPerformanceDiagnosticFSIDRunPerformanceDiagnosticFSIDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.64
fluidFSEventsParamsComponentFilePathFile pathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.65
fluidFSEventsParamsComponentDestinationFilePathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.68
fluidFSEventsParamsComponentClientProtocolNFS/SMB protocolro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.69
fluidFSEventsParamsComponentClientProtocolDetailsSession or opened file detailsro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.70
fluidFSEventsParamsComponentSourceVMNameSource VM Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.71
fluidFSEventsParamsComponentVmWareServerNameVMWare Server Namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.72
fluidFSEventsParamsComponentNumberOfClonesNumber Of Clonesro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.73
fluidFSEventsParamsComponentServicePackVersionVersion of a service packro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.74
fluidFSEventsParamsComponentDestinationNetworkIDRoute Rules route ip addressro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.75
fluidFSEventsParamsComponentDestinationPrefixRoute Rules route ip prefixro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.76
fluidFSEventsParamsComponentFolderPathFolder pathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.77
fluidFSEventsParamsComponentDSIDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.78
fluidFSEventsParamsComponentTapeDeviceNameConfigured name of tape devicero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.79
fluidFSEventsParamsComponentEventsSpacero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.80
fluidFSEventsParamsComponentGpoTimeoutro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.81
fluidFSEventsParamsComponentTenantIdTenant unique identifierro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.82
fluidFSEventsParamsComponentFSIDNAS volume idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.15.83
fluidFSEventsParamsComponentUIDro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.84
fluidFSEventsParamsComponentRemoteClusterIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.85
fluidFSEventsParamsComponentRemoteFSIDro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.15.86
fluidFSEventsParamsComponentStorageIdro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.87
fluidFSEventsParamsComponentSourceFSIDSource NAS volume idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.15.88
fluidFSEventsParamsComponentDestinationFSIDDestination NAS volume idro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.15.89
fluidFSEventsParamsComponentStatero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.90
fluidFSEventsParamsComponentFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.91
fluidFSEventsParamsComponentTenantNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.92
fluidFSEventsParamsComponentAdminNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.93
fluidFSEventsParamsComponentRemoteClusterNameName of the partner systemro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.94
fluidFSEventsParamsComponentRemoteVolumeNameName of the remote NAS volumero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.95
fluidFSEventsParamsComponentWindowsUserNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.96
fluidFSEventsParamsComponentUnixUserNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.97
fluidFSEventsParamsComponentSourceFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.98
fluidFSEventsParamsComponentDestinationFSIDNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.99
fluidFSEventsParamsComponentDSIDPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.15.100
fluidFSEventsParamsSupportShell
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.16
fluidFSEventsParamsSupportShellNodeNode namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.16.1
fluidFSEventsParamsSupportShellCommandCommand executed in support shellro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.16.2
fluidFSEventsParamsSupportShellUserNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.16.3
fluidFSEventsParamsAuditing
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.17
fluidFSEventsParamsAuditingUUser ID as seen from Samba - TUID. Will be translated to username by 'tuid2name' translator automaticallyro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.1
fluidFSEventsParamsAuditingDDSID (internal filesystem ID) of file or directory. Use dsid2name utility to translate dsid to path.ro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.2
fluidFSEventsParamsAuditingNNAS Volume ID (volume ID, i.e. FSID uint32 value). Will be translated to volume name by translatorro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.17.3
fluidFSEventsParamsAuditingDesiredCifsAccessMaskDesired access maskro
INTEGER
.1.3.6.1.4.1.674.11000.2000.200.21.17.4
fluidFSEventsParamsAuditingNameNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.5
fluidFSEventsParamsAuditingUNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.6
fluidFSEventsParamsAuditingNNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.7
fluidFSEventsParamsAuditingDPathro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.8
fluidFSEventsParamsAuditingDesiredCifsAccessMaskNamero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.17.9
fluidFSEventsParamsUpgrade
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.21.18
fluidFSEventsParamsUpgradeServicePackNameFile name of the Service Packro
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.21.18.1
fluidFSEventsGeneralParams
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.22
sysNameGeneral system namero
DisplayString (SNMPv2-TC)
.1.3.6.1.4.1.674.11000.2000.200.22.1
fluidFSGeneralEvents
OBJECT IDENTIFIER
.1.3.6.1.4.1.674.11000.2000.200.23
fluidFSCluOKThis trap will be sent any time the condition of the cluster becomes ok.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.1
fluidFSCluDegradedThis trap will be sent any time the condition of the cluster becomes degraded.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.2
fluidFSCluFailedThis trap will be sent any time the condition of the cluster becomes failed.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.3
fluidFSCluNodeOKThis trap will be sent any time the condition of a node in the cluster becomes ok.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.4
fluidFSCluNodeDegradedThis trap will be sent any time the condition of a node in the cluster becomes degraded. User Action: Make a note of the cluster node name then check the node for the cause of the degraded condition.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.5
fluidFSCluNodeFailedThis trap will be sent any time the condition of a node in the cluster becomes failed. User Action: Make a note of the cluster node name then check the node for the cause of the failure.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.6
fluidFSCluResourceOKThis trap will be sent any time the condition of a cluster resource becomes ok.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.7
fluidFSCluResourceDegradedThis trap will be sent any time the condition of a cluster resource becomes degraded. User Action: Make a note of the cluster resource name then check the resource for the cause of the degraded condition.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.8
fluidFSCluResourceFailedThis trap will be sent any time the condition of a cluster resource becomes failed. User Action: Make a note of the cluster resource name then check the resource for the cause of the failure.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.9
fluidFSGenNormalEventThis trap will be sent for normal events.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.14
fluidFSGenMinorEventThis trap will be sent for minor events.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.15
fluidFSGenMajorEventThis trap will be sent for major events.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.16
fluidFSGenCriticalEventThis trap will be sent for critical events.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.17
fluidFSAntiVirusEventThe antivirus software on or connected to system detected a virus.
NOTIFICATION-TYPE
.1.3.6.1.4.1.674.11000.2000.200.23.18
fluidFSMIBIdentityFluidFS MIB
MODULE-IDENTITY
.1.3.6.1.4.1.674.11000.2000.200.100