 hwStorageAlarmReportingPrecise
| .1.3.6.1.4.1.2011.2.251.20.1.2.2 | The node is used for reporting the parsed alarm. The ID of each alarm corresponds an independent OID, and different OIDs are used for alarm generation and clearance. |
diskIsFaulty1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.1.1 | Disk Is Faulty |
diskIsFaulty1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.1.2 | Recover: Disk Is Faulty |
hardDiskIsInSingleLinkState1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.12.1 | A Disk Is In The SingleLink Status |
hardDiskIsInSingleLinkState1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.12.2 | Recover: A Disk Is In The SingleLink Status |
diskHasTooManyBitError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.147.1 | A Disk Has Too Many Bit Errors |
diskHasTooManyBitError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.147.2 | Recover: A Disk Has Too Many Bit Errors |
diskMonitoringFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.21.1 | The System Failed To Monitor A Disk In The Disk Enclosure |
diskMonitoringFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.21.2 | Recover: The System Failed To Monitor A Disk In The Disk Enclosure |
unrecognizableDisk-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.262.1 | Unrecognizable Disk |
unrecognizableDisk-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.262.2 | Recover: Unrecognizable Disk |
diskIsAboutToFail-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.263.1 | Disk Is About To Fail |
diskIsAboutToFail-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.263.2 | Recover: Disk Is About To Fail |
diskInEngineMonitoringFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.280.1 | The System Failed To Monitor A Disk In The Controller Enclosure |
diskInEngineMonitoringFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.280.2 | Recover: The System Failed To Monitor A Disk In The Controller Enclosure |
diskWorkingRateAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.281.1 | Working Rate Of A Disk Is Abnormal |
diskWorkingRateAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.281.2 | Recover: Working Rate Of A Disk Is Abnormal |
theNumberOfConnectedDisksExceedsTheUpperLimitOfTheSystem-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.283.1 | The Number Of Connected Disks Exceeds The Upper Limit Of The System |
theNumberOfConnectedDisksExceedsTheUpperLimitOfTheSystem-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.283.2 | Recover: The Number Of Connected Disks Exceeds The Upper Limit Of The System |
diskTemperatureExceedsUpperLimit1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.288.1 | Disk Temperature Exceeds The Upper Limit |
diskTemperatureExceedsUpperLimit1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.288.2 | Recover: Disk Temperature Exceeds The Upper Limit |
slowDiskResponse1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.289.1 | Slow Disk Response |
slowDiskResponse1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.289.2 | Recover: Slow Disk Response |
diskModelIsIncompatible1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.291.1 | Incompatible Disk Model |
diskModelIsIncompatible1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.291.2 | Recover: Incompatible Disk Model |
authenticationOfSEDAccessFails1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.296.1 | Failed To Authenticate SelfEncrypting Disk Access |
authenticationOfSEDAccessFails1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.296.2 | Recover: Failed To Authenticate SelfEncrypting Disk Access |
authenticationOfSEDKeyFails1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.297.1 | Failed To Authenticate A SelfEncrypting Disk Key |
authenticationOfSEDKeyFails1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.297.2 | Recover: Failed To Authenticate A SelfEncrypting Disk Key |
theDiskIsIsolated-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.318.1 | The Disk Is Isolated |
theDiskIsIsolated-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.318.2 | Recover: The Disk Is Isolated |
theAmountOfDataWrittenToTheSystemDiskIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.368.1 | The Amount Of Data Written To The System Disk Is Abnormal |
theAmountOfDataWrittenToTheSystemDiskIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.368.2 | Recover: The Amount Of Data Written To The System Disk Is Abnormal |
diskRepair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.45.1 | Disk Repair |
diskRepair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.45.2 | Recover: Disk Repair |
theEstimatedLifespanOfADiskIsAboutToBeReached-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.565.1 | The Estimated Lifespan Of A Disk Is About To Be Reached |
theEstimatedLifespanOfADiskIsAboutToBeReached-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.565.2 | Recover: The Estimated Lifespan Of A Disk Is About To Be Reached |
theNumberOfConnectedDisksExceedsTheUpperLimitOfASingleEngine-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.567.1 | The Number Of Connected Disks Exceeds The Upper Limit Of A Single Engine |
theNumberOfConnectedDisksExceedsTheUpperLimitOfASingleEngine-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.567.2 | Recover: The Number Of Connected Disks Exceeds The Upper Limit Of A Single Engine |
theDiskIsInsertedIntoAnIncorrectSlot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.568.1 | The Disk Is Inserted Into An Incorrect Slot |
theDiskIsInsertedIntoAnIncorrectSlot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.568.2 | Recover: The Disk Is Inserted Into An Incorrect Slot |
authenticationOfSEDKeyFails-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.573.1 | Failed To Authenticate The Key Of The SelfEncrypting Drive |
authenticationOfSEDKeyFails-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.573.2 | Recover: Failed To Authenticate The Key Of The SelfEncrypting Drive |
authenticationOfSEDAccessFails-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.574.1 | Access Authentication Of The SelfEncrypting Drive Failed |
authenticationOfSEDAccessFails-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.574.2 | Recover: Access Authentication Of The SelfEncrypting Drive Failed |
diskModelIsIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.577.1 | The Disk Model Is Incompatible With The Device |
diskModelIsIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.577.2 | Recover: The Disk Model Is Incompatible With The Device |
slowDiskResponse-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.579.1 | Slow Disk Response |
slowDiskResponse-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.579.2 | Recover: Slow Disk Response |
hardDiskIsInSingleLinkState-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.580.1 | The Disk Is In The SingleLink Status |
hardDiskIsInSingleLinkState-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.580.2 | Recover: The Disk Is In The SingleLink Status |
diskFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.581.1 | The Disk Is About To Fail |
diskFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.581.2 | Recover: The Disk Is About To Fail |
diskTemperatureExceedsUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.582.1 | The Temperature Of The Disk Exceeds The Upper Limit |
diskTemperatureExceedsUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.582.2 | Recover: The Temperature Of The Disk Exceeds The Upper Limit |
theDiskCannotBeIdentified-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.583.1 | The Disk Cannot Be Identified |
theDiskCannotBeIdentified-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.583.2 | Recover: The Disk Cannot Be Identified |
diskIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.584.1 | The Disk Is Faulty |
diskIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.584.2 | Recover: The Disk Is Faulty |
theTemperatureOfMultipleDisksSeriouslyExceedsTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.585.1 | The Temperature Of Multiple Disks Seriously Exceeds The Upper Limit |
theTemperatureOfMultipleDisksSeriouslyExceedsTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.585.2 | Recover: The Temperature Of Multiple Disks Seriously Exceeds The Upper Limit |
theTemperatureOfMultipleDisksExceedsTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.650.1 | The Temperature Of Multiple Disks Exceeds The Upper Limit |
theTemperatureOfMultipleDisksExceedsTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.650.2 | Recover: The Temperature Of Multiple Disks Exceeds The Upper Limit |
theSystemDiskOfTheControllerIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.656.1 | The System Disk Of The Controller Is Faulty |
theSystemDiskOfTheControllerIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.656.2 | Recover: The System Disk Of The Controller Is Faulty |
theSystemDiskOfTheExpansionModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.658.1 | The System Disk Of The Expansion Module Is Faulty |
theSystemDiskOfTheExpansionModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.658.2 | Recover: The System Disk Of The Expansion Module Is Faulty |
theNumberOfConnectedDisksExceedsTheUpperLimitOfASingleControllerEnclosure-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.659.1 | The Number Of Connected Disks Exceeds The Upper Limit Of A Single Controller Enclosure |
theNumberOfConnectedDisksExceedsTheUpperLimitOfASingleControllerEnclosure-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.659.2 | Recover: The Number Of Connected Disks Exceeds The Upper Limit Of A Single Controller Enclosure |
diskIsRiskyLifeCritial-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.831.1 | The Disk In The Device Is About To Fail |
diskIsRiskyLifeCritial-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.831.2 | Recover: The Disk In The Device Is About To Fail |
diskIsRiskyLifeMajor-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.832.1 | The Firmware Version Of The Disk In The Device Is Too Early |
diskIsRiskyLifeMajor-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.832.2 | Recover: The Firmware Version Of The Disk In The Device Is Too Early |
systemDiskIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.833.1 | The System Disk Of The Controller Is Faulty |
systemDiskIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.833.2 | Recover: The System Disk Of The Controller Is Faulty |
expansionModuleSystemDiskIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.846.1 | A System Disk Is Faulty |
expansionModuleSystemDiskIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.846.2 | Recover: A System Disk Is Faulty |
diskLowTemperature-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.847.1 | Disk Temperature Is Below The Lower Limit |
diskLowTemperature-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.847.2 | Recover: Disk Temperature Is Below The Lower Limit |
controllerSystemDiskIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.851.1 | A System Disk Is Faulty |
controllerSystemDiskIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.10.851.2 | Recover: A System Disk Is Faulty |
theLUNIsFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.1.1 | LUN Is Faulty |
theLUNIsFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.1.2 | Recover: LUN Is Faulty |
externalLUNOffline-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.100.1 | External LUN Offline |
externalLUNOffline-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.100.2 | Recover: External LUN Offline |
externalLUNFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.101.1 | External LUN Faulty |
externalLUNFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.101.2 | Recover: External LUN Faulty |
externalLUNIsDownsized-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.102.1 | External LUN Downsized |
externalLUNIsDownsized-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.102.2 | Recover: External LUN Downsized |
theLUNHasMediumError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.2.1 | A Medium Error Occurred On A LUN |
theLUNHasMediumError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.2.2 | Recover: A Medium Error Occurred On A LUN |
externalLunTypeChanged-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.258.1 | External LUN Is Changed To Command Device |
externalLunTypeChanged-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.258.2 | Recover: External LUN Is Changed To Command Device |
remoteLinkExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.264.1 | Number Of The Connected Remote Links Has Exceeded The Upper Limit |
remoteLinkExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.264.2 | Recover: Number Of The Connected Remote Links Has Exceeded The Upper Limit |
remoteArrayExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.265.1 | Number Of The Connected Remote Arrays Has Exceeded The Upper Limit |
remoteArrayExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.265.2 | Recover: Number Of The Connected Remote Arrays Has Exceeded The Upper Limit |
lunHasAMediumError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.266.1 | LUN Has A Medium Error |
lunHasAMediumError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.266.2 | Recover: LUN Has A Medium Error |
localArrayRegPathToHeteroFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.267.1 | Failed To Register Paths From The Local Storage Array To Heterogeneous Storage Array |
localArrayRegPathToHeteroFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.267.2 | Recover: Failed To Register Paths From The Local Storage Array To Heterogeneous Storage Array |
lunStartBgrTaskFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.268.1 | Failed To Start LUN Background Task |
lunStartBgrTaskFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.268.2 | Recover: Failed To Start LUN Background Task |
snapshotStartBgrTaskFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.271.1 | Snapshot Start Bgr Task Failed |
snapshotStartBgrTaskFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.271.2 | Recover: Snapshot Start Bgr Task Failed |
theLUNWriteProtect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.273.1 | LUN Write Protection |
theLUNWriteProtect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.273.2 | Recover: LUN Write Protection |
iscsiLinkDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.292.1 | ISCSI Link Of Heterogeneous Array Disconnected |
iscsiLinkDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.292.2 | Recover: ISCSI Link Of Heterogeneous Array Disconnected |
lunCapacityNotEnough-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.323.1 | The Remaining LUN Capacity Is Insufficient |
lunCapacityNotEnough-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.323.2 | Recover: The Remaining LUN Capacity Is Insufficient |
snapshotLUNIsFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.61.1 | Snapshot LUN Is Faulty |
snapshotLUNIsFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.61.2 | Recover: Snapshot LUN Is Faulty |
incompatibleArrayConnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.82.1 | Incompatible Heterogeneous Array Connected To The System |
incompatibleArrayConnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.82.2 | Recover: Incompatible Heterogeneous Array Connected To The System |
externalLUNToOnlyOneController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.99.1 | An External LUN Has A Link To Only One Controller |
externalLUNToOnlyOneController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.11.99.2 | Recover: An External LUN Has A Link To Only One Controller |
bGPPeerConnectionStatusIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.10.1 | BGP Peer Connection Status Is Abnormal |
bGPPeerConnectionStatusIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.10.2 | Recover: BGP Peer Connection Status Is Abnormal |
bFDSessionStatusOfTheBGPPeerIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.11.1 | BFD Session Status Of The BGP Peer Is Abnormal |
bFDSessionStatusOfTheBGPPeerIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.11.2 | Recover: BFD Session Status Of The BGP Peer Is Abnormal |
theCACertificateIssuedByTheStorageDeviceIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.3.1 | The CA Certificate Issued By The Storage Device Is About To Expire |
theCACertificateIssuedByTheStorageDeviceIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.3.2 | Recover: The CA Certificate Issued By The Storage Device Is About To Expire |
failedToBackUpInternalKeyManagementServiceData-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.56.1 | Failed To Back Up Internal Key Management Service Data |
failedToBackUpInternalKeyManagementServiceData-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.56.2 | Recover: Failed To Back Up Internal Key Management Service Data |
theCACertificateIssuedByTheStorageDeviceExpires-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.6.1 | The CA Certificate Issued By The Storage Device Expires |
theCACertificateIssuedByTheStorageDeviceExpires-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.6.2 | Recover: The CA Certificate Issued By The Storage Device Expires |
theTwoFactorAuthenticationEmailServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.7.1 | The TwoFactor Authentication Email Server Is Unavailable |
theTwoFactorAuthenticationEmailServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.113.7.2 | Recover: The TwoFactor Authentication Email Server Is Unavailable |
hyperMetroIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.1.1 | HyperMetro Is Unavailable |
hyperMetroIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.1.2 | Recover: HyperMetro Is Unavailable |
hyperMetroIsDisconnected3-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.14.1 | The HyperMetro Pair Is Interrupted And The Local LUN Cannot Provide Services |
hyperMetroIsDisconnected3-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.14.2 | Recover: The HyperMetro Pair Is Interrupted And The Local LUN Cannot Provide Services |
hyperMetroIsDisconnected2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.15.1 | The HyperMetro Pair Is Interrupted And The Local LUN Continues To Provide Services |
hyperMetroIsDisconnected2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.15.2 | Recover: The HyperMetro Pair Is Interrupted And The Local LUN Continues To Provide Services |
hostIncorrectAccessForHyperMetroPair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.2.1 | The Host Has An Incorrect Access Permission |
hostIncorrectAccessForHyperMetroPair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.2.2 | Recover: The Host Has An Incorrect Access Permission |
theLocalArrayHasHyperMetroLUNsThatAreNotMappedToTheHost-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.29.1 | The Local Array Has HyperMetro LUNs That Are Not Mapped To The Host |
theLocalArrayHasHyperMetroLUNsThatAreNotMappedToTheHost-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.29.2 | Recover: The Local Array Has HyperMetro LUNs That Are Not Mapped To The Host |
hyperMetroPairAutoDisconnect1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.33.1 | A HyperMetro Pair Is Automatically Disconnected And The Local LUN Cannot Provide Services |
hyperMetroPairAutoDisconnect1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.33.2 | Recover: A HyperMetro Pair Is Automatically Disconnected And The Local LUN Cannot Provide Services |
hyperMetroPairAutoDisconnect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.34.1 | A HyperMetro Pair Is Automatically Disconnected And The Local LUN Continues To Provide Services |
hyperMetroPairAutoDisconnect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.34.2 | Recover: A HyperMetro Pair Is Automatically Disconnected And The Local LUN Continues To Provide Services |
hyperMetroIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.35.1 | The HyperMetro Pair Is Interrupted And The Local LUN Cannot Provide Services |
hyperMetroIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.35.2 | Recover: The HyperMetro Pair Is Interrupted And The Local LUN Cannot Provide Services |
hyperMetroIsDisconnected1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.36.1 | The HyperMetro Pair Is Interrupted And The Local LUN Continues To Provide Services |
hyperMetroIsDisconnected1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.36.2 | Recover: The HyperMetro Pair Is Interrupted And The Local LUN Continues To Provide Services |
failedToStartTheHyperMetroService-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.37.1 | Failed To Start The HyperMetro Service |
failedToStartTheHyperMetroService-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.37.2 | Recover: Failed To Start The HyperMetro Service |
hyperMetroIsInterruptedAndTheLocalFileSystemCannotProvideServices-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.38.1 | HyperMetro Is Interrupted And The Local File System Cannot Provide Services |
hyperMetroIsInterruptedAndTheLocalFileSystemCannotProvideServices-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.38.2 | Recover: HyperMetro Is Interrupted And The Local File System Cannot Provide Services |
theLocalFileSystemContinuesToProvideServicesWhenHyperMetroIsInterrupted-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.39.1 | The Local File System Continues To Provide Services When HyperMetro Is Interrupted |
theLocalFileSystemContinuesToProvideServicesWhenHyperMetroIsInterrupted-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.39.2 | Recover: The Local File System Continues To Provide Services When HyperMetro Is Interrupted |
nasHyperMetraClusterProtectWrite-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.40.1 | The File System HyperMetro Domain Is In The Write Protection Status |
nasHyperMetraClusterProtectWrite-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.40.2 | Recover: The File System HyperMetro Domain Is In The Write Protection Status |
failedToStartTheServiceOfAFileSystemHyperMetroPair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.43.1 | Failed To Start The Service Of A File System HyperMetro Pair |
failedToStartTheServiceOfAFileSystemHyperMetroPair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.43.2 | Recover: Failed To Start The Service Of A File System HyperMetro Pair |
hyperMetroPairConfigurationsAreDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.44.1 | HyperMetro Pair Configurations Are Disconnected |
hyperMetroPairConfigurationsAreDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.44.2 | Recover: HyperMetro Pair Configurations Are Disconnected |
nasHyperMetroIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.45.1 | The File System HyperMetro Pair Is Unavailable |
nasHyperMetroIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.45.2 | Recover: The File System HyperMetro Pair Is Unavailable |
nvmeClusterReservationCommandFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.47.1 | The Host Fails To Deliver The NVMe Cluster Reservation Command |
nvmeClusterReservationCommandFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.47.2 | Recover: The Host Fails To Deliver The NVMe Cluster Reservation Command |
oneStorageArrayOfAHyperMetroPairIsIsolated-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.6.1 | One Storage Array Of A HyperMetro Pair Is Isolated |
oneStorageArrayOfAHyperMetroPairIsIsolated-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.6.2 | Recover: One Storage Array Of A HyperMetro Pair Is Isolated |
registerIncorrectAccessForPair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.9.1 | HyperMetro Arbitration Information Conflicts With The Existing Information |
registerIncorrectAccessForPair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15361.9.2 | Recover: HyperMetro Arbitration Information Conflicts With The Existing Information |
hyperMetroDomainIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.0.1 | The HyperMetro Domain Is Unavailable |
hyperMetroDomainIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.0.2 | Recover: The HyperMetro Domain Is Unavailable |
theHyperMetroDomainIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.4.1 | The HyperMetro Domain Is Faulty |
theHyperMetroDomainIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.4.2 | Recover: The HyperMetro Domain Is Faulty |
hyperMetroDomainIsDisconnected1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.40.1 | The Local End Cannot Provide Services When The HyperMetro Domain Is Disconnected |
hyperMetroDomainIsDisconnected1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.40.2 | Recover: The Local End Cannot Provide Services When The HyperMetro Domain Is Disconnected |
hyperMetroDomainIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.41.1 | The Local End Continues To Provide Services When The HyperMetro Domain Is Disconnected |
hyperMetroDomainIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.41.2 | Recover: The Local End Continues To Provide Services When The HyperMetro Domain Is Disconnected |
hyperMetroDomainIsRecovery-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.6.1 | HyperMetro Domain Is In The Recovering State For A Long Time |
hyperMetroDomainIsRecovery-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15362.6.2 | Recover: HyperMetro Domain Is In The Recovering State For A Long Time |
theCertificateOfQuorumServerIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.10.1 | Certificate Of A Quorum Server Is About To Expire |
theCertificateOfQuorumServerIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.10.2 | Recover: Certificate Of A Quorum Server Is About To Expire |
cACertificateOfAQuorumServerIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.11.1 | CA Certificate Of A Quorum Server Is About To Expire |
cACertificateOfAQuorumServerIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.11.2 | Recover: CA Certificate Of A Quorum Server Is About To Expire |
noBackupLinkForCps-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.2.1 | No Backup Links Available |
noBackupLinkForCps-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.2.2 | Recover: No Backup Links Available |
quorumServerDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.4.1 | Quorum Server Is Disconnected From The Storage Array |
quorumServerDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.4.2 | Recover: Quorum Server Is Disconnected From The Storage Array |
certificateOfAQuorumServerHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.8.1 | Certificate Of A Quorum Server Has Expired |
certificateOfAQuorumServerHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.8.2 | Recover: Certificate Of A Quorum Server Has Expired |
cACertificateOfAQuorumServerHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.9.1 | CA Certificate Of A Quorum Server Has Expired |
cACertificateOfAQuorumServerHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15363.9.2 | Recover: CA Certificate Of A Quorum Server Has Expired |
oneStorageArrayOfAHyperMetroConsistencyGroupIsIsolated-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.10.1 | One Storage Array Of A HyperMetro Consistency Group Is Isolated |
oneStorageArrayOfAHyperMetroConsistencyGroupIsIsolated-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.10.2 | Recover: One Storage Array Of A HyperMetro Consistency Group Is Isolated |
hyperMetroGroupIsDisconnected1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.11.1 | The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Cannot Provide Services |
hyperMetroGroupIsDisconnected1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.11.2 | Recover: The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Cannot Provide Services |
hyperMetroGroupIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.12.1 | The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Continue To Provide Services |
hyperMetroGroupIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.12.2 | Recover: The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Continue To Provide Services |
failedToStartTheHyperMetroConsistencyGroupService-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.13.1 | Failed To Start The HyperMetro Consistency Group Service |
failedToStartTheHyperMetroConsistencyGroupService-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.13.2 | Recover: Failed To Start The HyperMetro Consistency Group Service |
hyperMetroGroupIsDisconnected3-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.16.1 | The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Cannot Provide Services |
hyperMetroGroupIsDisconnected3-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.16.2 | Recover: The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Cannot Provide Services |
hyperMetroGroupIsDisconnected2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.17.1 | The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Continue To Provide Services |
hyperMetroGroupIsDisconnected2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.17.2 | Recover: The HyperMetro Consistency Group Is Disconnected And Member LUNs In The Local Consistency Group Continue To Provide Services |
hyperMetroGroupIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.2.1 | HyperMetro Consistency Group Is Unavailable |
hyperMetroGroupIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.2.2 | Recover: HyperMetro Consistency Group Is Unavailable |
hostIncorrectAccessForHyperMetroGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.3.1 | The Host Has An Incorrect Access Permission For HyperMetro Consistency Group |
hostIncorrectAccessForHyperMetroGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.3.2 | Recover: The Host Has An Incorrect Access Permission For HyperMetro Consistency Group |
registerIncorrectAccessForGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.4.1 | The HyperMetro Consistency Group Arbitration Information Conflicts With The Existing Information |
registerIncorrectAccessForGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15364.4.2 | Recover: The HyperMetro Consistency Group Arbitration Information Conflicts With The Existing Information |
theHyperMetroVStorePairIsInPreferredWorkingModeForALongTime-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15366.5.1 | The HyperMetro VStore Pair Is In Preferred Working Mode For A Long Time |
theHyperMetroVStorePairIsInPreferredWorkingModeForALongTime-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.15366.5.2 | Recover: The HyperMetro VStore Pair Is In Preferred Working Mode For A Long Time |
invalidVStorePair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.156.1.1 | Invalid VStore Pair |
invalidVStorePair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.156.1.2 | Recover: Invalid VStore Pair |
vStorePairConfigurationsAreDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.156.4.1 | VStore Pair Configurations Are Disconnected |
vStorePairConfigurationsAreDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.156.4.2 | Recover: VStore Pair Configurations Are Disconnected |
theRemoteS3DeviceOfSmartMobilityRespondsSlowly-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.107.1 | The Remote S3 Device Of SmartMobility Responds Slowly |
theRemoteS3DeviceOfSmartMobilityRespondsSlowly-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.107.2 | Recover: The Remote S3 Device Of SmartMobility Responds Slowly |
theLDAPCRLHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.108.1 | The LDAP CRL Has Expired |
theLDAPCRLHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.108.2 | Recover: The LDAP CRL Has Expired |
clientNfsORdmaConnMax-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.109.1 | The Number Of Used QPs of A RoCE NIC On A Controller Reaches The Upper Limit |
clientNfsORdmaConnMax-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.109.2 | Recover: The Number Of Used QPs of A RoCE NIC On A Controller Reaches The Upper Limit |
theBranchcacheFunctionIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.110.1 | The Branchcache Function Is Unavailable |
theBranchcacheFunctionIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.110.2 | Recover: The Branchcache Function Is Unavailable |
pwdOfResUserHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.111.1 | The Password Of A Windows User Has Expired |
pwdOfResUserHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.111.2 | Recover: The Password Of A Windows User Has Expired |
thisAlarmIsGeneratedWhenPacketControlOccurs-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.112.1 | This Alarm Is Generated When Packet Control Occurs |
thisAlarmIsGeneratedWhenPacketControlOccurs-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.112.2 | Recover: This Alarm Is Generated When Packet Control Occurs |
windowsUserHasBeenLocked-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.113.1 | A Windows User Has Been Locked |
windowsUserHasBeenLocked-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.113.2 | Recover: A Windows User Has Been Locked |
pwdOfResUserIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.114.1 | The Password Of A Windows User Is About To Expire |
pwdOfResUserIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.114.2 | Recover: The Password Of A Windows User Is About To Expire |
windowsUserIsAboutToBeLocked-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.115.1 | A Windows User Is About To Be Locked |
windowsUserIsAboutToBeLocked-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.115.2 | Recover: A Windows User Is About To Be Locked |
largeClusterLdapServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.116.1 | The Communication Network With The LDAP Domain Server Is Abnormal |
largeClusterLdapServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.116.2 | Recover: The Communication Network With The LDAP Domain Server Is Abnormal |
largeClusterDnsServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.117.1 | The Communication Network With The DNS Server Is Abnormal |
largeClusterDnsServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.117.2 | Recover: The Communication Network With The DNS Server Is Abnormal |
clusterRestrict-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.118.1 | This Alarm Is Generated When An Array Enters Silent Management And Control |
clusterRestrict-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.118.2 | Recover: This Alarm Is Generated When An Array Enters Silent Management And Control |
clusterRestrictFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.119.1 | This Alarm Is Generated When An Array Failed To Enter Silent Management And Control |
clusterRestrictFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.119.2 | Recover: This Alarm Is Generated When An Array Failed To Enter Silent Management And Control |
largeClusterNisServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.120.1 | Communication Network Of The NIS Server Is Abnormal |
largeClusterNisServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.120.2 | Recover: Communication Network Of The NIS Server Is Abnormal |
dataturboConnectionReachUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.126.1 | The Number Of DataTurbo Links On The Controller Is About To Reach The Upper Limit |
dataturboConnectionReachUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.126.2 | Recover: The Number Of DataTurbo Links On The Controller Is About To Reach The Upper Limit |
servicePortConflict-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.41.1 | A Service Port Conflicts |
servicePortConflict-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.41.2 | Recover: A Service Port Conflicts |
ldapServiceUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.42.1 | LDAP Domain Service Is Unavailable |
ldapServiceUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.42.2 | Recover: LDAP Domain Service Is Unavailable |
nisServiceUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.43.1 | NIS Domain Service Is Unavailable |
nisServiceUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.43.2 | Recover: NIS Domain Service Is Unavailable |
adDomainServiceUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.44.1 | AD Domain Service Is Unavailable |
adDomainServiceUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.44.2 | Recover: AD Domain Service Is Unavailable |
domainDNSServiceUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.45.1 | DNS Service Is Unavailable |
domainDNSServiceUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.45.2 | Recover: DNS Service Is Unavailable |
fileLockNumReachUpperLimit2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.46.1 | The Number Of Files Opened On A Single Controller For The NAS Protocol Reaches The Upper Limit |
fileLockNumReachUpperLimit2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.46.2 | Recover: The Number Of Files Opened On A Single Controller For The NAS Protocol Reaches The Upper Limit |
fileLockNumReachUpperLimit1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.47.1 | The Number Of File Open Locks For The NAS Protocol Reaches The Upper Limit |
fileLockNumReachUpperLimit1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.47.2 | Recover: The Number Of File Open Locks For The NAS Protocol Reaches The Upper Limit |
clientConnectionReachUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.5.1 | The Number Of NAS Client Connections On A Controller Reaches The Upper Limit |
clientConnectionReachUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.5.2 | Recover: The Number Of NAS Client Connections On A Controller Reaches The Upper Limit |
fileLockNumReachUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.51.1 | The Number Of File Range Locks For The NAS Protocol Reaches The Upper Limit |
fileLockNumReachUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.51.2 | Recover: The Number Of File Range Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfLockRescResourcesForTheNASProtocolReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.52.1 | The Number Of LockResc Resources For The NAS Protocol Reaches The Upper Limit |
theNumberOfLockRescResourcesForTheNASProtocolReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.52.2 | Recover: The Number Of LockResc Resources For The NAS Protocol Reaches The Upper Limit |
theNumberOfPublicResourceEntryLocksForTheNASProtocolReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.53.1 | The Number Of Public Resource Entry Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfPublicResourceEntryLocksForTheNASProtocolReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.53.2 | Recover: The Number Of Public Resource Entry Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfPublicResourceNameLocksForTheNASProtocolReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.54.1 | The Number Of Public Resource Name Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfPublicResourceNameLocksForTheNASProtocolReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.54.2 | Recover: The Number Of Public Resource Name Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfBlockReqBlockLocksForTheNASProtocolReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.55.1 | The Number Of BlockReq Block Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfBlockReqBlockLocksForTheNASProtocolReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.55.2 | Recover: The Number Of BlockReq Block Locks For The NAS Protocol Reaches The Upper Limit |
theNumberOfSessionsForTheSMB2ProtocolReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.56.1 | The Number Of Sessions For The SMB2 Protocol Reaches The Upper Limit |
theNumberOfSessionsForTheSMB2ProtocolReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.56.2 | Recover: The Number Of Sessions For The SMB2 Protocol Reaches The Upper Limit |
adDomainServerNetworkAbnormal1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.62.1 | The Communication Network Of The AD Domain Server Is Abnormal |
adDomainServerNetworkAbnormal1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.62.2 | Recover: The Communication Network Of The AD Domain Server Is Abnormal |
domainDNSServerNetworkAbnormal1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.63.1 | The DNS Server Communication Network Is Abnormal |
domainDNSServerNetworkAbnormal1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.63.2 | Recover: The DNS Server Communication Network Is Abnormal |
ldapServerNetworkAbnormal1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.64.1 | The Communication Network Of The LDAP Domain Server Is Abnormal |
ldapServerNetworkAbnormal1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.64.2 | Recover: The Communication Network Of The LDAP Domain Server Is Abnormal |
nisServerNetworkAbnormal1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.68.1 | The Communication Network Of The NIS Domain Server Is Abnormal |
nisServerNetworkAbnormal1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.68.2 | Recover: The Communication Network Of The NIS Domain Server Is Abnormal |
domainDNSServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.73.1 | The Communication Network With The DNS Server Is Abnormal |
domainDNSServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.73.2 | Recover: The Communication Network With The DNS Server Is Abnormal |
ldapServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.74.1 | The Communication Network With The LDAP Domain Server Is Abnormal |
ldapServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.74.2 | Recover: The Communication Network With The LDAP Domain Server Is Abnormal |
nisServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.75.1 | The Communication Network With The NIS Domain Server Is Abnormal |
nisServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.75.2 | Recover: The Communication Network With The NIS Domain Server Is Abnormal |
adDomainServerNetworkAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.76.1 | The Communication Network With The AD Domain Server Is Abnormal |
adDomainServerNetworkAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.76.2 | Recover: The Communication Network With The AD Domain Server Is Abnormal |
theNumberOfOpenedSMB2SharesHasReachedTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.77.1 | The Number Of Opened SMB2 Shares Has Reached The Upper Limit |
theNumberOfOpenedSMB2SharesHasReachedTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.77.2 | Recover: The Number Of Opened SMB2 Shares Has Reached The Upper Limit |
smb2ShareNumReachUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.8.1 | The Number Of Share Connections For The SMB2 Protocol Reaches The Upper Limit |
smb2ShareNumReachUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.8.2 | Recover: The Number Of Share Connections For The SMB2 Protocol Reaches The Upper Limit |
theDNSServiceIsAbnormal1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.82.1 | The DNS Service Is Abnormal |
theDNSServiceIsAbnormal1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.82.2 | Recover: The DNS Service Is Abnormal |
clientConcurrencyReachUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.84.1 | The Number Of Concurrent NAS Clients On The Controller Reaches The Upper Limit |
clientConcurrencyReachUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.84.2 | Recover: The Number Of Concurrent NAS Clients On The Controller Reaches The Upper Limit |
smbHardCryptFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.95.1 | SMB Hard Encryption And Decryption Fault |
smbHardCryptFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.95.2 | Recover: SMB Hard Encryption And Decryption Fault |
adDomainServiceAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.96.1 | The AD Domain Service Is Abnormal |
adDomainServiceAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.96.2 | Recover: The AD Domain Service Is Abnormal |
theDNSServiceIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.97.1 | The DNS Service Is Abnormal |
theDNSServiceIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16386.97.2 | Recover: The DNS Service Is Abnormal |
vstoreQuotaNotEnough-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16442.1.1 | The VStore Quota Capacity Has Reached The Threshold |
vstoreQuotaNotEnough-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16442.1.2 | Recover: The VStore Quota Capacity Has Reached The Threshold |
theNumberOfClientRelatedResourcesHasReachedTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16452.29.1 | The Number Of Client Related Resources Has Reached The Upper Limit |
theNumberOfClientRelatedResourcesHasReachedTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16452.29.2 | Recover: The Number Of Client Related Resources Has Reached The Upper Limit |
resourcesUsedByTheClientAreAboutToExceedTheSpecification-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16453.46.1 | Resources Used By The Client Are About To Exceed The Specification |
resourcesUsedByTheClientAreAboutToExceedTheSpecification-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16453.46.2 | Recover: Resources Used By The Client Are About To Exceed The Specification |
quotaNumIsExceed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.16.1 | The Number Of Configured File System Quotas Exceeds 85% Of The Threshold |
quotaNumIsExceed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.16.2 | Recover: The Number Of Configured File System Quotas Exceeds 85% Of The Threshold |
usedResourceOfAFileSystemDirQuotaExceedsTheSoftQuota-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19969.1 | Used Resource Of A File System Quota Exceeds The Soft Quota |
usedResourceOfAFileSystemDirQuotaExceedsTheSoftQuota-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19969.2 | Recover: Used Resource Of A File System Quota Exceeds The Soft Quota |
usedResourceOfAFileSystemGrpUsrQuotaExceedsTheSoftQuota-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19970.1 | Used Resource Of A File System Quota Exceeds The Soft Quota |
usedResourceOfAFileSystemGrpUsrQuotaExceedsTheSoftQuota-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19970.2 | Recover: Used Resource Of A File System Quota Exceeds The Soft Quota |
usedResourceOfAFileSystemDirQuotaReachesTheHardQuota-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19971.1 | Used Resource Of A File System Quota Reaches The Hard Quota |
usedResourceOfAFileSystemDirQuotaReachesTheHardQuota-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19971.2 | Recover: Used Resource Of A File System Quota Reaches The Hard Quota |
usedResourceOfAFileSystemGrpUsrQuotaReachesTheHardQuota-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19972.1 | Used Resource Of A File System Quota Reaches The Hard Quota |
usedResourceOfAFileSystemGrpUsrQuotaReachesTheHardQuota-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.19972.2 | Recover: Used Resource Of A File System Quota Reaches The Hard Quota |
fsQuotaSoftCapAlarmDirType-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.21.1 | Used Resource Of A File System Quota Exceeds The Soft Quota |
fsQuotaSoftCapAlarmDirType-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.21.2 | Recover: Used Resource Of A File System Quota Exceeds The Soft Quota |
fsQuotaSoftCapAlarmGrpUsrType-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.22.1 | Used Resource Of A File System Quota Exceeds The Soft Quota |
fsQuotaSoftCapAlarmGrpUsrType-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.22.2 | Recover: Used Resource Of A File System Quota Exceeds The Soft Quota |
fsQuotaHardCapAlarmDirType-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.23.1 | Used Resource Of A File System Quota Reaches The Hard Quota |
fsQuotaHardCapAlarmDirType-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.23.2 | Recover: Used Resource Of A File System Quota Reaches The Hard Quota |
fsQuotaHardCapAlarmUsrGrpType-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.25.1 | Used Resource Of A File System Quota Reaches The Hard Quota |
fsQuotaHardCapAlarmUsrGrpType-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.25.2 | Recover: Used Resource Of A File System Quota Reaches The Hard Quota |
fsQuotaCapAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.27.1 | The Number Of Configured File System Quotas Exceeds The Threshold |
fsQuotaCapAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16458.27.2 | Recover: The Number Of Configured File System Quotas Exceeds The Threshold |
akskIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.1.1 | Object Service Access Key Is About To Expire |
akskIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.1.2 | Recover: Object Service Access Key Is About To Expire |
akskHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.2.1 | Object Service Access Key Has Expired |
akskHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.2.2 | Recover: Object Service Access Key Has Expired |
setUpHTTPSConnFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.3.1 | HTTPS Connections Failed To Be Established For The Object Service |
setUpHTTPSConnFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.3.2 | Recover: HTTPS Connections Failed To Be Established For The Object Service |
obsHTTPSConnReachUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.4.1 | Number Of HTTPS Connections Of The Object Service On The Controller Is About To Reach The Upper Limit |
obsHTTPSConnReachUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.16459.4.2 | Recover: Number Of HTTPS Connections Of The Object Service On The Controller Is About To Reach The Upper Limit |
internalDatabaseServiceOfAStorageNodeIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.1.1 | Internal Database Service Of A Storage Node Is Abnormal |
internalDatabaseServiceOfAStorageNodeIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.1.2 | Recover: Internal Database Service Of A Storage Node Is Abnormal |
internalComponentsOfTheSystemHaveRisks-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.157.1 | Internal Components Of The System Have Risks |
internalComponentsOfTheSystemHaveRisks-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.157.2 | Recover: Internal Components Of The System Have Risks |
theNumberOfWrittenLogsReachesTheLogQuota-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.2.1 | The Number Of Written Logs Reaches The Log Quota |
theNumberOfWrittenLogsReachesTheLogQuota-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.2.2 | Recover: The Number Of Written Logs Reaches The Log Quota |
controllerWriteCacheIsDisabled-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.21.1 | Controller Write Cache Is Disabled |
controllerWriteCacheIsDisabled-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.21.2 | Recover: Controller Write Cache Is Disabled |
systemWriteCacheDisabled-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.22.1 | Write Cache Of A System Was Disabled |
systemWriteCacheDisabled-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.22.2 | Recover: Write Cache Of A System Was Disabled |
ipaddrConflict-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.317.1 | IP Address Conflict |
ipaddrConflict-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.317.2 | Recover: IP Address Conflict |
componentsInTheSystemAreAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.336.1 | Components In The System Are Abnormal |
componentsInTheSystemAreAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.336.2 | Recover: Components In The System Are Abnormal |
componentsInTheSystemAreAbnormalAndHaveBeenRepairedAutomatically-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.337.1 | Components In The System Are Abnormal And Have Been Repaired Automatically |
componentsInTheSystemAreAbnormalAndHaveBeenRepairedAutomatically-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.337.2 | Recover: Components In The System Are Abnormal And Have Been Repaired Automatically |
dnsIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.340.1 | Management DNS Server Is Unavailable |
dnsIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.340.2 | Recover: Management DNS Server Is Unavailable |
theProcessOfDaemonIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.341.1 | The Process Of Daemon Is Faulty |
theProcessOfDaemonIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.341.2 | Recover: The Process Of Daemon Is Faulty |
componentsInTheSystemOfTheControllerAreAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.343.1 | Components In The System Of The Controller Are Abnormal |
componentsInTheSystemOfTheControllerAreAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.343.2 | Recover: Components In The System Of The Controller Are Abnormal |
theControllerWillEnterTheWriteProtectionMode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.345.1 | The Controller Will Enter The Write Protection Mode |
theControllerWillEnterTheWriteProtectionMode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.345.2 | Recover: The Controller Will Enter The Write Protection Mode |
theEffectiveCapacityInTheLicenseExceedsTheSystemSpecification-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.346.1 | The Effective Capacity In The License Exceeds The System Specification |
theEffectiveCapacityInTheLicenseExceedsTheSystemSpecification-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.346.2 | Recover: The Effective Capacity In The License Exceeds The System Specification |
theControllerWillEnterTheWriteProtectionMode1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.347.1 | The Controller Will Enter The Write Protection Mode |
theControllerWillEnterTheWriteProtectionMode1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.347.2 | Recover: The Controller Will Enter The Write Protection Mode |
aComponentInTheSystemIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.348.1 | A Component In The System Is Abnormal |
aComponentInTheSystemIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.348.2 | Recover: A Component In The System Is Abnormal |
failedToSynchronizeDNSZoneConfigurationsToTheSecondaryVStoreOfTheVStorePair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.349.1 | Failed To Synchronize DNS Zone Configurations To The Secondary VStore Of The VStore Pair |
failedToSynchronizeDNSZoneConfigurationsToTheSecondaryVStoreOfTheVStorePair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.349.2 | Recover: Failed To Synchronize DNS Zone Configurations To The Secondary VStore Of The VStore Pair |
risksIdentifiedThroughSystemSelfcheck-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.351.1 | Risks Identified Through System Selfcheck |
risksIdentifiedThroughSystemSelfcheck-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.351.2 | Recover: Risks Identified Through System Selfcheck |
componentsOfTheControllerAreAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.353.1 | Components Of The Controller Are Abnormal |
componentsOfTheControllerAreAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.353.2 | Recover: Components Of The Controller Are Abnormal |
aComponentInTheExpansionModuleIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.356.1 | A Component In The Expansion Module Is Abnormal |
aComponentInTheExpansionModuleIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.356.2 | Recover: A Component In The Expansion Module Is Abnormal |
theSystemIsAboutToEnterTheWriteProtectionMode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.358.1 | The System Is About To Enter The Write Protection Mode |
theSystemIsAboutToEnterTheWriteProtectionMode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.358.2 | Recover: The System Is About To Enter The Write Protection Mode |
containerIPAddressesConflict-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.360.1 | Container IP Addresses Conflict |
containerIPAddressesConflict-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.360.2 | Recover: Container IP Addresses Conflict |
theControllerIsAboutToEnterTheWriteThroughMode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.361.1 | The Controller Is About To Enter The WriteThrough Mode |
theControllerIsAboutToEnterTheWriteThroughMode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.361.2 | Recover: The Controller Is About To Enter The WriteThrough Mode |
controllerIsFaultyWithErrorCode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.365.1 | A Component In The System Is Abnormal |
controllerIsFaultyWithErrorCode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.365.2 | Recover: A Component In The System Is Abnormal |
systemEnterSafeMode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.6.1 | The System Has Entered Safe Mode |
systemEnterSafeMode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.201.6.2 | Recover: The System Has Entered Safe Mode |
thePasswordHasNotBeenInitialized-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.1.1 | The Password Has Not Been Initialized |
thePasswordHasNotBeenInitialized-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.1.2 | Recover: The Password Has Not Been Initialized |
passwdOfUserIsAboutToExpire1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.14.1 | The Password Of The User Is About To Expire |
passwdOfUserIsAboutToExpire1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.14.2 | Recover: The Password Of The User Is About To Expire |
passwdOfUserHasExpired1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.15.1 | The Password Of The User Has Expired |
passwdOfUserHasExpired1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.15.2 | Recover: The Password Of The User Has Expired |
passwdOfUserIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.16.1 | The Password Is About To Expire |
passwdOfUserIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.16.2 | Recover: The Password Is About To Expire |
passwdOfUserHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.17.1 | The Password Has Expired |
passwdOfUserHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.17.2 | Recover: The Password Has Expired |
theSuperAdministratorNeedsToReviewUserAccountInformation-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.27.1 | The Super Administrator Needs To Review User Account Information |
theSuperAdministratorNeedsToReviewUserAccountInformation-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.27.2 | Recover: The Super Administrator Needs To Review User Account Information |
testingTheAlarmFunction-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.65532.1 | Testing The Alarm Function |
testingTheAlarmFunction-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.202.65532.2 | Recover: Testing The Alarm Function |
certificateExpiredWithDeadline-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.1.1 | A Certificate Has Expired |
certificateExpiredWithDeadline-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.1.2 | Recover: A Certificate Has Expired |
tenantCRLHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.10.1 | A Certificate Revocation List Has Expired |
tenantCRLHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.10.2 | Recover: A Certificate Revocation List Has Expired |
theCACertificateIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.13.1 | A CA Certificate Is About To Expire |
theCACertificateIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.13.2 | Recover: A CA Certificate Is About To Expire |
theCACertificateHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.14.1 | A CA Certificate Has Expired |
theCACertificateHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.14.2 | Recover: A CA Certificate Has Expired |
theCACertificateOfAVstoreIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.19.1 | The CA Certificate Of A Vstore Is About To Expire |
theCACertificateOfAVstoreIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.19.2 | Recover: The CA Certificate Of A Vstore Is About To Expire |
certificateWillExpireWithTime-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.2.1 | A Certificate Is About To Expire |
certificateWillExpireWithTime-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.2.2 | Recover: A Certificate Is About To Expire |
tenantCertificateHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.3.1 | A Certificate Has Expired |
tenantCertificateHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.3.2 | Recover: A Certificate Has Expired |
theCACertificateOfAVstoreHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.35.1 | The CA Certificate Of A Vstore Has Expired |
theCACertificateOfAVstoreHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.35.2 | Recover: The CA Certificate Of A Vstore Has Expired |
thereIsNoCACertificateForDiskAuthenticationOnTheArray-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.351.1 | There Is No CA Certificate For Disk Authentication On The Array |
thereIsNoCACertificateForDiskAuthenticationOnTheArray-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.351.2 | Recover: There Is No CA Certificate For Disk Authentication On The Array |
certificateExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.36.1 | A Certificate Has Expired |
certificateExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.36.2 | Recover: A Certificate Has Expired |
certificateWillExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.37.1 | A Certificate Is About To Expire |
certificateWillExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.37.2 | Recover: A Certificate Is About To Expire |
tenantCertificateWillExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.4.1 | A Certificate Is About To Expire |
tenantCertificateWillExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.4.2 | Recover: A Certificate Is About To Expire |
crlExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.6.1 | A Certificate Revocation List Has Expired |
crlExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.20480.6.2 | Recover: A Certificate Revocation List Has Expired |
failedToMonitorADiskEnclosure-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.1.1 | Failed To Monitor A Disk Enclosure |
failedToMonitorADiskEnclosure-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.1.2 | Recover: Failed To Monitor A Disk Enclosure |
diskEnclTempIsFarBeyondUpLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.10.1 | Disk Enclosure Temperature Is Far Beyond The Upper Limit |
diskEnclTempIsFarBeyondUpLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.10.2 | Recover: Disk Enclosure Temperature Is Far Beyond The Upper Limit |
anUnsupportedExpEnclConnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.15.1 | Controller Is Connected To An Unsupported Disk Enclosure |
anUnsupportedExpEnclConnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.15.2 | Recover: Controller Is Connected To An Unsupported Disk Enclosure |
diskEnclosureQuantityExceeds-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.2.1 | Disk Enclosure Quantity Exceeds The System Limit |
diskEnclosureQuantityExceeds-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.2.2 | Recover: Disk Enclosure Quantity Exceeds The System Limit |
numOfEnclOnExpPortExceedsLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.23.1 | The Number Of Disk Enclosures Connected To An Expansion Port Exceeds The System Specification |
numOfEnclOnExpPortExceedsLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.23.2 | Recover: The Number Of Disk Enclosures Connected To An Expansion Port Exceeds The System Specification |
diskEnclosureIsSingleLink-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.42.1 | Disk Enclosure Is Working In Single Link State |
diskEnclosureIsSingleLink-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.42.2 | Recover: Disk Enclosure Is Working In Single Link State |
highDensityAreMixConnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.43.1 | From An Expansion Port, Disk Enclosures And HighDensity Disk Enclosures Are MixConnected |
highDensityAreMixConnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.43.2 | Recover: From An Expansion Port, Disk Enclosures And HighDensity Disk Enclosures Are MixConnected |
failedToMonitorTheRearPanel-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.46.1 | The System Failed To Monitor The Rear Panel Of The Enclosure |
failedToMonitorTheRearPanel-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.46.2 | Recover: The System Failed To Monitor The Rear Panel Of The Enclosure |
enclosureIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.49.1 | Faults Occurred On An Enclosure |
enclosureIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.49.2 | Recover: Faults Occurred On An Enclosure |
diskEnclTempExceedsUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.5.1 | Disk Enclosure Temperature Exceeds The Upper Limit |
diskEnclTempExceedsUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.5.2 | Recover: Disk Enclosure Temperature Exceeds The Upper Limit |
enclosureIsUnrecognizable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.50.1 | Failed To Identify A Controller Enclosure Or Disk Enclosure |
enclosureIsUnrecognizable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.50.2 | Recover: Failed To Identify A Controller Enclosure Or Disk Enclosure |
enclSpeedSmallerThanLoopSpeed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.52.1 | The Disk Enclosure Speed Does Not Reach The Maximum Loop Speed |
enclSpeedSmallerThanLoopSpeed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.52.2 | Recover: The Disk Enclosure Speed Does Not Reach The Maximum Loop Speed |
failedToMatchTheEnclosureType-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.59.1 | The Enclosure Type Is Mismatched |
failedToMatchTheEnclosureType-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.59.2 | Recover: The Enclosure Type Is Mismatched |
powerSupplyNotCompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.6.1 | Power Supplies In The Enclosure Are Inconsistent |
powerSupplyNotCompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.6.2 | Recover: Power Supplies In The Enclosure Are Inconsistent |
diskEnclTempIsBelowLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.7.1 | Engine Or Disk Enclosure Temperature Is Below The Lower Limit |
diskEnclTempIsBelowLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.7.2 | Recover: Engine Or Disk Enclosure Temperature Is Below The Lower Limit |
theNumberOfDiskEnclosuresConnectedToAnExpansionPortExceedsTheSystemSpecification-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.70.1 | The Number Of Disk Enclosures Connected To An Expansion Port Exceeds The System Specification |
theNumberOfDiskEnclosuresConnectedToAnExpansionPortExceedsTheSystemSpecification-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.70.2 | Recover: The Number Of Disk Enclosures Connected To An Expansion Port Exceeds The System Specification |
anUnsupportedDiskEnclosureIsConnectedToTheSystem-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.71.1 | An Unsupported Disk Enclosure Is Connected To The System |
anUnsupportedDiskEnclosureIsConnectedToTheSystem-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.71.2 | Recover: An Unsupported Disk Enclosure Is Connected To The System |
modelOfAnExpansionModuleInTheDiskEnclosureIsNotSupportedByTheSystem-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.72.1 | Model Of An Expansion Module In The Disk Enclosure Is Not Supported By The System |
modelOfAnExpansionModuleInTheDiskEnclosureIsNotSupportedByTheSystem-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.72.2 | Recover: Model Of An Expansion Module In The Disk Enclosure Is Not Supported By The System |
ctrlEnclTempExceedsUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.8.1 | Controller Enclosure Temperature Exceeds The Upper Limit |
ctrlEnclTempExceedsUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.8.2 | Recover: Controller Enclosure Temperature Exceeds The Upper Limit |
ctrlEnclTempIsFarBeyondUpLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.9.1 | Controller Enclosure Temperature Is Far Beyond The Upper Limit |
ctrlEnclTempIsFarBeyondUpLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.206.9.2 | Recover: Controller Enclosure Temperature Is Far Beyond The Upper Limit |
sshServiceIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.1.1 | The SSH Service Is Abnormal |
sshServiceIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.1.2 | Recover: The SSH Service Is Abnormal |
controllerNetStackIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.10.1 | The Network Protocol Stack Of A Controller Is Abnormal |
controllerNetStackIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.10.2 | Recover: The Network Protocol Stack Of A Controller Is Abnormal |
processCpuUsageIsTooHigh-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.11.1 | The Process CPU Utilization Is Too High |
processCpuUsageIsTooHigh-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.11.2 | Recover: The Process CPU Utilization Is Too High |
theControllerIsBeingRepaired1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.112.1 | The Controller Is Being Repaired |
theControllerIsBeingRepaired1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.112.2 | Recover: The Controller Is Being Repaired |
controllerTypesAreDifferent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.114.1 | Types Of Controllers In The Enclosure Are Different |
controllerTypesAreDifferent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.114.2 | Recover: Types Of Controllers In The Enclosure Are Different |
theControllerFailsToBePoweredOn-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.115.1 | The Controller Fails To Be Powered On |
theControllerFailsToBePoweredOn-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.115.2 | Recover: The Controller Fails To Be Powered On |
controllerRunningStatusIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.116.1 | Controller Running Status Is Abnormal |
controllerRunningStatusIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.116.2 | Recover: Controller Running Status Is Abnormal |
theControllerIsBeingRepaired3-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.118.1 | The Controller Is Being Repaired |
theControllerIsBeingRepaired3-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.118.2 | Recover: The Controller Is Being Repaired |
failedToMonitorTheController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.119.1 | Failed To Monitor The Controller |
failedToMonitorTheController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.119.2 | Recover: Failed To Monitor The Controller |
processMemoryUsageIsTooHigh-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.12.1 | The Process Memory Usage Is Too High |
processMemoryUsageIsTooHigh-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.12.2 | Recover: The Process Memory Usage Is Too High |
ctlI2cCommuError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.120.1 | The Monitoring Link Between The Controller And Enclosure Is Faulty |
ctlI2cCommuError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.120.2 | Recover: The Monitoring Link Between The Controller And Enclosure Is Faulty |
controllerProtectWrite2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.121.1 | Write Protection Is Enabled On A Controller |
controllerProtectWrite2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.121.2 | Recover: Write Protection Is Enabled On A Controller |
controllerProtectWrite1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.122.1 | Write Protection Is Enabled On A Controller |
controllerProtectWrite1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.122.2 | Recover: Write Protection Is Enabled On A Controller |
controllerSoltIDIsIncorrect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.124.1 | The Slot ID Of The Controller Module Is Incorrect |
controllerSoltIDIsIncorrect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.124.2 | Recover: The Slot ID Of The Controller Module Is Incorrect |
theControllerIsBeingRepaired2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.125.1 | The Controller Is Being Repaired |
theControllerIsBeingRepaired2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.125.2 | Recover: The Controller Is Being Repaired |
theControllerIsBeingRepaired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.126.1 | The Controller Is Being Repaired |
theControllerIsBeingRepaired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.126.2 | Recover: The Controller Is Being Repaired |
theControllerPoweronTimesOut-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.128.1 | The Controller Poweron Times Out |
theControllerPoweronTimesOut-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.128.2 | Recover: The Controller Poweron Times Out |
cpuUsageTooHigh-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.13.1 | CPU Utilization Is Too High |
cpuUsageTooHigh-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.13.2 | Recover: CPU Utilization Is Too High |
theControllerFailedToBePoweredOn-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.131.1 | The Controller Failed To Be Powered On |
theControllerFailedToBePoweredOn-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.131.2 | Recover: The Controller Failed To Be Powered On |
ctrlHeatRemovalSysFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.134.1 | Heat Dissipation System Of The Controller Is Faulty |
ctrlHeatRemovalSysFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.134.2 | Recover: Heat Dissipation System Of The Controller Is Faulty |
connOfControllerExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.135.1 | The Number Of ISCSI Initiator Connections On A Controller Exceeds The Upper Limit |
connOfControllerExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.135.2 | Recover: The Number Of ISCSI Initiator Connections On A Controller Exceeds The Upper Limit |
cmdOfControllerExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.136.1 | The Number Of ISCSI Commands On A Controller Exceeds The Upper Limit |
cmdOfControllerExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.136.2 | Recover: The Number Of ISCSI Commands On A Controller Exceeds The Upper Limit |
failedToEnableTheAICacheAlgorithm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.137.1 | Failed To Enable The AI Cache Algorithm |
failedToEnableTheAICacheAlgorithm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.137.2 | Recover: Failed To Enable The AI Cache Algorithm |
controllerProtectWrite-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.138.1 | Write Protection Is Enabled On A Controller |
controllerProtectWrite-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.138.2 | Recover: Write Protection Is Enabled On A Controller |
memoryUsageTooHigh-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.14.1 | Memory Utilization Is Too High |
memoryUsageTooHigh-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.14.2 | Recover: Memory Utilization Is Too High |
aMemoryErrorOccurred-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.141.1 | A Memory Error Occurred |
aMemoryErrorOccurred-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.141.2 | Recover: A Memory Error Occurred |
theControllerIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.142.1 | The Controller Is Faulty |
theControllerIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.142.2 | Recover: The Controller Is Faulty |
anUncorrectableErrorOccursOnTheMemoryModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.147.1 | An Uncorrectable Error Occurs On The Memory Module |
anUncorrectableErrorOccursOnTheMemoryModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.147.2 | Recover: An Uncorrectable Error Occurs On The Memory Module |
theNumberOfMemoryModulesOnTheControllerDoesNotMatch-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.148.1 | The Number Of Memory Modules On The Controller Does Not Match |
theNumberOfMemoryModulesOnTheControllerDoesNotMatch-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.148.2 | Recover: The Number Of Memory Modules On The Controller Does Not Match |
aMemoryErrorOccurs-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.149.1 | A Memory Error Occurs |
aMemoryErrorOccurs-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.149.2 | Recover: A Memory Error Occurs |
theClusterServiceIsSubhealthy-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.150.1 | The Cluster Service Is Subhealthy |
theClusterServiceIsSubhealthy-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.150.2 | Recover: The Cluster Service Is Subhealthy |
memoryErrorOccurs-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.152.1 | A Memory Error Occurs |
memoryErrorOccurs-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.152.2 | Recover: A Memory Error Occurs |
memoryOccursUncorrectableError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.153.1 | An Uncorrectable Error Occurs On The Memory |
memoryOccursUncorrectableError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.153.2 | Recover: An Uncorrectable Error Occurs On The Memory |
ctrlAndMgtCommunicateLinkFault1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.154.1 | Communication Link Fault Among The Controller And Management Modules |
ctrlAndMgtCommunicateLinkFault1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.154.2 | Recover: Communication Link Fault Among The Controller And Management Modules |
theControllerMemoryManagementPolicyDoesNotTakeEffect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.157.1 | The Controller Memory Management Policy Does Not Take Effect |
theControllerMemoryManagementPolicyDoesNotTakeEffect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.157.2 | Recover: The Controller Memory Management Policy Does Not Take Effect |
theCommunicationBetweenTheControllerAndComputeNodeIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.158.1 | The Communication Between The Controller And Compute Node Is Abnormal |
theCommunicationBetweenTheControllerAndComputeNodeIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.158.2 | Recover: The Communication Between The Controller And Compute Node Is Abnormal |
theControllerEntersTheWriteThroughMode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.159.1 | The Controller Enters The WriteThrough Mode |
theControllerEntersTheWriteThroughMode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.159.2 | Recover: The Controller Enters The WriteThrough Mode |
theCcdbServiceIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.16.1 | The CCDB Service Is Abnormal |
theCcdbServiceIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.16.2 | Recover: The CCDB Service Is Abnormal |
ctrlAndMgtCommunicateLinkFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.162.1 | The Communication Link Between The Controller And Management Module Is Faulty |
ctrlAndMgtCommunicateLinkFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.162.2 | Recover: The Communication Link Between The Controller And Management Module Is Faulty |
directoryIsOversized-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.163.1 | A Directory Is Oversized |
directoryIsOversized-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.163.2 | Recover: A Directory Is Oversized |
cpuIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.164.1 | CPU Module Fault |
cpuIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.164.2 | Recover: CPU Module Fault |
cpuPeripheralIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.165.1 | CPU Peripheral Module Fault |
cpuPeripheralIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.165.2 | Recover: CPU Peripheral Module Fault |
clusterPowerOnTimeOut-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.166.1 | HyperScale Cluster Poweron Timed Out |
clusterPowerOnTimeOut-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.166.2 | Recover: HyperScale Cluster Poweron Timed Out |
clusterNodeStatusAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.167.1 | HyperScale Cluster Node Status Is Abnormal |
clusterNodeStatusAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.167.2 | Recover: HyperScale Cluster Node Status Is Abnormal |
theCcdbServiceDegradation-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.17.1 | The CCDB Service Is Degraded |
theCcdbServiceDegradation-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.17.2 | Recover: The CCDB Service Is Degraded |
ftpServiceIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.2.1 | The FTP Service Is Abnormal |
ftpServiceIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.2.2 | Recover: The FTP Service Is Abnormal |
monitorControllersFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.21.1 | Failed To Monitor Controllers Enclosure |
monitorControllersFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.21.2 | Recover: Failed To Monitor Controllers Enclosure |
contorllersMemorySizeDiffer-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.47.1 | Inconsistent Memory Capacities Between Controllers |
contorllersMemorySizeDiffer-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.47.2 | Recover: Inconsistent Memory Capacities Between Controllers |
abnormalCommunicateBetweenCtrls-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.5.1 | Abnormal Communication Between Controllers |
abnormalCommunicateBetweenCtrls-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.5.2 | Recover: Abnormal Communication Between Controllers |
controllerServicesAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.54.1 | Controller Services Are Abnormal |
controllerServicesAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.54.2 | Recover: Controller Services Are Abnormal |
controllerIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.6.1 | Controller Is Removed |
controllerIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.6.2 | Recover: Controller Is Removed |
directoryIsOversized1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.7.1 | A Directory Is Oversized |
directoryIsOversized1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.7.2 | Recover: A Directory Is Oversized |
excessiveFilesExistInADirectory-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.8.1 | Excessive Files Exist In A Directory |
excessiveFilesExistInADirectory-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.8.2 | Recover: Excessive Files Exist In A Directory |
ntpSynchronizationIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.9.1 | NTP Time Synchronization Is Abnormal |
ntpSynchronizationIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.9.2 | Recover: NTP Time Synchronization Is Abnormal |
cpuUsageIsTooHigh-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.93.1 | CPU Utilization Is Too High |
cpuUsageIsTooHigh-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.93.2 | Recover: CPU Utilization Is Too High |
remainAvailableMemoryTooLow-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.94.1 | Remaining Available Memory Is Too Low |
remainAvailableMemoryTooLow-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.94.2 | Recover: Remaining Available Memory Is Too Low |
controllerIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.95.1 | The Controller Is Faulty |
controllerIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.95.2 | Recover: The Controller Is Faulty |
memoryCapacityIsNotSupported-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.96.1 | Incorrect Controller Memory Capacity |
memoryCapacityIsNotSupported-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.96.2 | Recover: Incorrect Controller Memory Capacity |
ctrlAndMgtCommunicateLinkFault2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.97.1 | Communication Link Fault Among The Controller And Management Modules |
ctrlAndMgtCommunicateLinkFault2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.207.97.2 | Recover: Communication Link Fault Among The Controller And Management Modules |
expansionModuleIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.1.1 | Expansion Module Is Removed |
expansionModuleIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.1.2 | Recover: Expansion Module Is Removed |
expI2cCommuError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.119.1 | The Monitor Link Between The Expansion Module And The Enclosure Is Faulty |
expI2cCommuError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.119.2 | Recover: The Monitor Link Between The Expansion Module And The Enclosure Is Faulty |
abnormalCommBetweenExpModules-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.20.1 | Abnormal Communication Between Expansion Modules |
abnormalCommBetweenExpModules-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.20.2 | Recover: Abnormal Communication Between Expansion Modules |
syncExpansionFirmwareFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.23.1 | Failed To Synchronize The Firmware Version Of An Expansion Module |
syncExpansionFirmwareFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.23.2 | Recover: Failed To Synchronize The Firmware Version Of An Expansion Module |
expansionModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.24.1 | Expansion Module Is Faulty |
expansionModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.24.2 | Recover: Expansion Module Is Faulty |
expansionModuleSpeedNotSupport-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.29.1 | The Expansion Module Speed Does Not Meet Specifications |
expansionModuleSpeedNotSupport-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.29.2 | Recover: The Expansion Module Speed Does Not Meet Specifications |
expandFrameTypeInvalid-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.32.1 | The Expansion Module Cannot Identify The Enclosure Type |
expandFrameTypeInvalid-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.32.2 | Recover: The Expansion Module Cannot Identify The Enclosure Type |
expansionModuleIsBeingRepaired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.33.1 | Expansion Module Is Being Repaired |
expansionModuleIsBeingRepaired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.33.2 | Recover: Expansion Module Is Being Repaired |
expansionModuleRepairTimesOut-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.34.1 | Expansion Module Repair Times Out |
expansionModuleRepairTimesOut-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.34.2 | Recover: Expansion Module Repair Times Out |
failedToRepairAnExpansionModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.35.1 | Failed To Repair An Expansion Module |
failedToRepairAnExpansionModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.35.2 | Recover: Failed To Repair An Expansion Module |
expHeatRemovalSysFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.40.1 | Heat Dissipation System Of The Expansion Module Is Faulty |
expHeatRemovalSysFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.40.2 | Recover: Heat Dissipation System Of The Expansion Module Is Faulty |
expansionModuleIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.41.1 | Expansion Module Firmware Is Incompatible With Storage Array Software |
expansionModuleIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.41.2 | Recover: Expansion Module Firmware Is Incompatible With Storage Array Software |
typesOfExpansionModulesInTheDiskEnclosureAreDifferent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.42.1 | Types Of Expansion Modules In The Disk Enclosure Are Different |
typesOfExpansionModulesInTheDiskEnclosureAreDifferent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.42.2 | Recover: Types Of Expansion Modules In The Disk Enclosure Are Different |
memCapOfExpIsIncorrect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.43.1 | Memory Capacity Of Expansion Module Is Incorrect |
memCapOfExpIsIncorrect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.43.2 | Recover: Memory Capacity Of Expansion Module Is Incorrect |
theSystemCannotMonitorAExpansionModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.45.1 | The System Cannot Monitor A Expansion Module |
theSystemCannotMonitorAExpansionModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.45.2 | Recover: The System Cannot Monitor A Expansion Module |
sasExpansionModuleIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.57.1 | The Shared SAS Expansion Module Firmware Is Incompatible With Storage Array Software |
sasExpansionModuleIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.208.57.2 | Recover: The Shared SAS Expansion Module Firmware Is Incompatible With Storage Array Software |
managementModuleIsRemoved1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.1.1 | Management Module Is Removed |
managementModuleIsRemoved1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.1.2 | Recover: Management Module Is Removed |
interfaceModuleIsFaultyWithOpn-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.106.1 | Interface Module Is Faulty |
interfaceModuleIsFaultyWithOpn-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.106.2 | Recover: Interface Module Is Faulty |
interfaceNotRedundancy-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.13.1 | Port Redundancy Requirements Not Met |
interfaceNotRedundancy-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.13.2 | Recover: Port Redundancy Requirements Not Met |
cmdOfCardExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.3.1 | Number Of Commands On A Module Exceeds The System Limit |
cmdOfCardExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.3.2 | Recover: Number Of Commands On A Module Exceeds The System Limit |
monitorInterfaceModuleFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.30.1 | Interface Module Cannot Be Monitored |
monitorInterfaceModuleFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.30.2 | Recover: Interface Module Cannot Be Monitored |
theMCUFirmwareVersionIsIncompatibleWithStorageArraySoftware-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.4.1 | The MCU Firmware Version Is Incompatible With Storage Array Software |
theMCUFirmwareVersionIsIncompatibleWithStorageArraySoftware-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.4.2 | Recover: The MCU Firmware Version Is Incompatible With Storage Array Software |
interfaceModuleIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.40.1 | Interface Module Firmware Version Is Incompatible With Storage Array Software |
interfaceModuleIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.40.2 | Recover: Interface Module Firmware Version Is Incompatible With Storage Array Software |
abnormalCommunicateBetweenManageModules-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.46.1 | The Communication Between Management Modules Is Abnormal |
abnormalCommunicateBetweenManageModules-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.46.2 | Recover: The Communication Between Management Modules Is Abnormal |
interfaceModuleIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.5.1 | Interface Module Is Removed |
interfaceModuleIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.5.2 | Recover: Interface Module Is Removed |
managementModuleIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.50.1 | The Management Module Firmware Is Incompatible With Storage Array Software |
managementModuleIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.50.2 | Recover: The Management Module Firmware Is Incompatible With Storage Array Software |
pcieChannelIsFaulty1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.56.1 | PCIe Channel Between An Interface Module And A Controller Is Abnormal |
pcieChannelIsFaulty1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.56.2 | Recover: PCIe Channel Between An Interface Module And A Controller Is Abnormal |
linkIntfCtrlAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.57.1 | The Link Between An Interface Module And A Controller Is Abnormal |
linkIntfCtrlAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.57.2 | Recover: The Link Between An Interface Module And A Controller Is Abnormal |
managementModuleIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.59.1 | Management Module Is Removed |
managementModuleIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.59.2 | Recover: Management Module Is Removed |
managementModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.60.1 | The Management Module Is Faulty |
managementModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.60.2 | Recover: The Management Module Is Faulty |
interfaceModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.61.1 | Interface Module Is Faulty |
interfaceModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.61.2 | Recover: Interface Module Is Faulty |
interfaceSfpSpeedUnmatch-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.63.1 | Speeds Of The Port And Optical Module In The Port Are Not The Same On An Interface Module |
interfaceSfpSpeedUnmatch-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.63.2 | Recover: Speeds Of The Port And Optical Module In The Port Are Not The Same On An Interface Module |
fruNotSupport-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.68.1 | Interface Module Not Supported |
fruNotSupport-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.68.2 | Recover: Interface Module Not Supported |
intfNotMatchCorrectSlot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.69.1 | Interface Module Inserted Into An Incorrect Slot |
intfNotMatchCorrectSlot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.69.2 | Recover: Interface Module Inserted Into An Incorrect Slot |
mgtAndCtrlCommunicateLinkFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.72.1 | Communication Link Fault Between The Management Module And Controller |
mgtAndCtrlCommunicateLinkFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.72.2 | Recover: Communication Link Fault Between The Management Module And Controller |
intfNotMatchSuggestSlot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.75.1 | An Interface Module Is Not Inserted Into The Recommended Slot |
intfNotMatchSuggestSlot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.75.2 | Recover: An Interface Module Is Not Inserted Into The Recommended Slot |
aSpareInterfaceModuleIsInsertedIntoAnIncorrectSlot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.76.1 | A Spare Interface Module Is Inserted Into An Incorrect Slot |
aSpareInterfaceModuleIsInsertedIntoAnIncorrectSlot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.76.2 | Recover: A Spare Interface Module Is Inserted Into An Incorrect Slot |
connOfCardExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.77.1 | The Number Of ISCSI Initiator Connections On An Interface Module Exceeds The Upper Limit |
connOfCardExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.77.2 | Recover: The Number Of ISCSI Initiator Connections On An Interface Module Exceeds The Upper Limit |
incorrectWorkingModeOfAnInterfaceModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.78.1 | Incorrect Working Mode Of An Interface Module |
incorrectWorkingModeOfAnInterfaceModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.78.2 | Recover: Incorrect Working Mode Of An Interface Module |
interfaceModuleIsUnrecognizable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.8.1 | Interface Module Is Unrecognizable |
interfaceModuleIsUnrecognizable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.8.2 | Recover: Interface Module Is Unrecognizable |
managementModuleNotSupport-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.81.1 | Management Module Not Supported |
managementModuleNotSupport-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.81.2 | Recover: Management Module Not Supported |
theCommunicationLinkBetweenTheManagementModuleAndControllerIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.82.1 | The Communication Link Between The Management Module And Controller Is Faulty |
theCommunicationLinkBetweenTheManagementModuleAndControllerIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.82.2 | Recover: The Communication Link Between The Management Module And Controller Is Faulty |
pcieChannelIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.83.1 | The PCIe Channel Between An Interface Module And A Controller Is Abnormal |
pcieChannelIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.83.2 | Recover: The PCIe Channel Between An Interface Module And A Controller Is Abnormal |
anUnsupportedSpareInterfaceModuleIsInsertedIntoTheSlot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.87.1 | An Unsupported Spare Interface Module Is Inserted Into The Slot |
anUnsupportedSpareInterfaceModuleIsInsertedIntoTheSlot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.87.2 | Recover: An Unsupported Spare Interface Module Is Inserted Into The Slot |
theInterfaceModuleIsIncompatibleWithTheOceanStorOSKernelVersion-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.89.1 | The Interface Module Is Incompatible With The OceanStor OS Kernel Version |
theInterfaceModuleIsIncompatibleWithTheOceanStorOSKernelVersion-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.89.2 | Recover: The Interface Module Is Incompatible With The OceanStor OS Kernel Version |
interfaceModuleTempExceedsLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.9.1 | Interface Module Temperature Exceeds The Upper Limit |
interfaceModuleTempExceedsLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.9.2 | Recover: Interface Module Temperature Exceeds The Upper Limit |
theInterfaceModuleIsInAbnormalStatus-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.91.1 | The Interface Module Is In Abnormal Status |
theInterfaceModuleIsInAbnormalStatus-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.91.2 | Recover: The Interface Module Is In Abnormal Status |
riserCardChipFaults-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.94.1 | Riser Card Chip Faults |
riserCardChipFaults-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.209.94.2 | Recover: Riser Card Chip Faults |
noRedundantConnectionToHost-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.25.1 | Host Is Not Redundantly Connected To Storage Arrays |
noRedundantConnectionToHost-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.25.2 | Recover: Host Is Not Redundantly Connected To Storage Arrays |
aLinkToHostIsDown-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.26.1 | Link Between A Host And Storage Array Is Down |
aLinkToHostIsDown-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.26.2 | Recover: Link Between A Host And Storage Array Is Down |
ultrapathIncompatibleWithStorage-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.29.1 | Ultrapath Incompatible With Storage Array Software |
ultrapathIncompatibleWithStorage-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.29.2 | Recover: Ultrapath Incompatible With Storage Array Software |
theOperatingSystemTypeOfTheArrayHostIsInconsistentWithThatOfTheAssociatedPhysicalHost-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.30.1 | The Operating System Type Of The Array Host Is Inconsistent With That Of The Associated Physical Host |
theOperatingSystemTypeOfTheArrayHostIsInconsistentWithThatOfTheAssociatedPhysicalHost-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.30.2 | Recover: The Operating System Type Of The Array Host Is Inconsistent With That Of The Associated Physical Host |
theUniversalMultipathingSoftwareAndUltraPathJointlyTakeOverTheLUNs-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.35.1 | The Universal Multipathing Software And UltraPath Jointly Take Over The LUNs |
theUniversalMultipathingSoftwareAndUltraPathJointlyTakeOverTheLUNs-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.35.2 | Recover: The Universal Multipathing Software And UltraPath Jointly Take Over The LUNs |
ultraPathIncompatibleWithOperatingSystemKernel-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.37.1 | UltraPath Incompatible With Operating System Kernel |
ultraPathIncompatibleWithOperatingSystemKernel-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.37.2 | Recover: UltraPath Incompatible With Operating System Kernel |
lUNsMappedToTheHostHaveNoRedundantLinksToTheStorageArray-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.39.1 | LUNs Mapped To The Host Have No Redundant Links To The Storage Array |
lUNsMappedToTheHostHaveNoRedundantLinksToTheStorageArray-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.39.2 | Recover: LUNs Mapped To The Host Have No Redundant Links To The Storage Array |
pathsBetweenTheHostAndStorageArrayDoNotMeetRedundancyRequirements-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.4.1 | Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
pathsBetweenTheHostAndStorageArrayDoNotMeetRedundancyRequirements-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.4.2 | Recover: Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
lUNsMappedToTheHostHaveNoRedundantLinksToControllers-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.40.1 | LUNs Mapped To The Host Have No Redundant Links To Controllers |
lUNsMappedToTheHostHaveNoRedundantLinksToControllers-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.40.2 | Recover: LUNs Mapped To The Host Have No Redundant Links To Controllers |
theHostLUNIDOfALUNMappedToTheHostIs0-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.54.1 | The Host LUN ID Of A LUN Mapped To The Host Is 0 |
theHostLUNIDOfALUNMappedToTheHostIs0-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.54.2 | Recover: The Host LUN ID Of A LUN Mapped To The Host Is 0 |
hyperMetroLUNsAreNotSupportedDueToNVMeUsedByTheHost-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.55.1 | HyperMetro LUNs Are Not Supported Due To NVMe Used By The Host |
hyperMetroLUNsAreNotSupportedDueToNVMeUsedByTheHost-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.55.2 | Recover: HyperMetro LUNs Are Not Supported Due To NVMe Used By The Host |
theInBandManagementCertificateOfTheHostIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.56.1 | The InBand Management Certificate Of The Host Is About To Expire |
theInBandManagementCertificateOfTheHostIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.56.2 | Recover: The InBand Management Certificate Of The Host Is About To Expire |
theInBandManagementCertificateOfTheHostHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.57.1 | The InBand Management Certificate Of The Host Has Expired |
theInBandManagementCertificateOfTheHostHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.21.57.2 | Recover: The InBand Management Certificate Of The Host Has Expired |
failedToMonitorABBUModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.20.1 | BBU Module Cannot Be Monitored |
failedToMonitorABBUModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.20.2 | Recover: BBU Module Cannot Be Monitored |
bbuModuleTypeDoesNotComply-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.25.1 | The BBU Type Does Not Comply With The System Specification |
bbuModuleTypeDoesNotComply-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.25.2 | Recover: The BBU Type Does Not Comply With The System Specification |
bbuModuleTempIsBelowLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.27.1 | BBU Module Temperature Is Below The Lower Limit |
bbuModuleTempIsBelowLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.27.2 | Recover: BBU Module Temperature Is Below The Lower Limit |
bbuModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.28.1 | BBU Module Is Faulty |
bbuModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.28.2 | Recover: BBU Module Is Faulty |
bbuModuleLifeIsOvertime-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.29.1 | BBU Module Reaches Its Expiration Date Or Is Aging |
bbuModuleLifeIsOvertime-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.29.2 | Recover: BBU Module Reaches Its Expiration Date Or Is Aging |
bbuModuleIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.30.1 | BBU Module Is About To Expire |
bbuModuleIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.30.2 | Recover: BBU Module Is About To Expire |
potentialPowerBackupRisks-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.37.1 | Potential Risks Of System Backup Power |
potentialPowerBackupRisks-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.37.2 | Recover: Potential Risks Of System Backup Power |
bbuFirmwareIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.39.1 | BBU Firmware Is Incompatible With Storage Array Software |
bbuFirmwareIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.39.2 | Recover: BBU Firmware Is Incompatible With Storage Array Software |
bbuModuleIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.4.1 | BBU Module Is Removed |
bbuModuleIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.4.2 | Recover: BBU Module Is Removed |
bbuModuleTempExceedsLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.5.1 | BBU Module Temperature Exceeds The Upper Limit |
bbuModuleTempExceedsLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.210.5.2 | Recover: BBU Module Temperature Exceeds The Upper Limit |
failedToMonitorAFanModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.20.1 | Fan Module Cannot Be Monitored |
failedToMonitorAFanModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.20.2 | Recover: Fan Module Cannot Be Monitored |
fanModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.21.1 | Fan Module Is Faulty |
fanModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.21.2 | Recover: Fan Module Is Faulty |
ctrlFanFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.23.1 | Faulty Fan Module |
ctrlFanFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.23.2 | Recover: Faulty Fan Module |
expFanFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.24.1 | Faulty Fan Module |
expFanFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.24.2 | Recover: Faulty Fan Module |
fanCtlBoardFanFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.25.1 | The Fan Module Is Faulty |
fanCtlBoardFanFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.25.2 | Recover: The Fan Module Is Faulty |
fanModuleIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.3.1 | Fan Module Removed |
fanModuleIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.211.3.2 | Recover: Fan Module Removed |
storagePoolIsDegraded-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.1.1 | Storage Pool Is Degraded |
storagePoolIsDegraded-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.1.2 | Recover: Storage Pool Is Degraded |
currentUsageOfTheBackupStoragePoolExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.10.1 | Current Usage Of The Backup Storage Pool Exceeds The Threshold |
currentUsageOfTheBackupStoragePoolExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.10.2 | Recover: Current Usage Of The Backup Storage Pool Exceeds The Threshold |
storagePoolIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.2.1 | Storage Pool Is Faulty |
storagePoolIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.2.2 | Recover: Storage Pool Is Faulty |
aStoragePoolIsOffline-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.21.1 | A Storage Pool Is Offline |
aStoragePoolIsOffline-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.21.2 | Recover: A Storage Pool Is Offline |
storagePoolCapacityNotEnough1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.281.1 | Storage Pool Remaining Capacity Is Insufficient |
storagePoolCapacityNotEnough1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.281.2 | Recover: Storage Pool Remaining Capacity Is Insufficient |
storagePoolCapacityIsUsedUp1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.285.1 | Storage Pool Capacity Is Used Up |
storagePoolCapacityIsUsedUp1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.285.2 | Recover: Storage Pool Capacity Is Used Up |
storagePoolCapacityShouldUseUp-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.288.1 | Storage Pool Capacity Is About To Be Used Up |
storagePoolCapacityShouldUseUp-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.288.2 | Recover: Storage Pool Capacity Is About To Be Used Up |
theEffectiveCapacityOfTheSystemIsInsufficient-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.322.1 | The Effective Capacity Of The System Is Insufficient |
theEffectiveCapacityOfTheSystemIsInsufficient-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.322.2 | Recover: The Effective Capacity Of The System Is Insufficient |
theEffectiveCapacityOfTheSystemIsAboutToBeUsedUp-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.323.1 | The Effective Capacity Of The System Is About To Be Used Up |
theEffectiveCapacityOfTheSystemIsAboutToBeUsedUp-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.323.2 | Recover: The Effective Capacity Of The System Is About To Be Used Up |
theEffectiveCapacityOfTheSystemIsUsedUp-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.324.1 | The Effective Capacity Of The System Is Used Up |
theEffectiveCapacityOfTheSystemIsUsedUp-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.324.2 | Recover: The Effective Capacity Of The System Is Used Up |
theUsedEffectiveCapacityIsNotAsExpected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.328.1 | The Used Effective Capacity Is Not As Expected |
theUsedEffectiveCapacityIsNotAsExpected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.328.2 | Recover: The Used Effective Capacity Is Not As Expected |
storagePoolCapacityIsUsedUp-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.337.1 | Storage Pool Capacity Is Used Up |
storagePoolCapacityIsUsedUp-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.337.2 | Recover: Storage Pool Capacity Is Used Up |
storagePoolCapacityNotEnough-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.345.1 | Storage Pool Remaining Capacity Is Insufficient |
storagePoolCapacityNotEnough-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.345.2 | Recover: Storage Pool Remaining Capacity Is Insufficient |
storagePoolCapacityShouldUseUp2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.346.1 | The Storage Pool Capacity Is About To Be Used Up |
storagePoolCapacityShouldUseUp2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.346.2 | Recover: The Storage Pool Capacity Is About To Be Used Up |
storagePoolCapacityShouldUseUp1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.358.1 | The Storage Pool Capacity Is About To Be Used Up |
storagePoolCapacityShouldUseUp1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.216.358.2 | Recover: The Storage Pool Capacity Is About To Be Used Up |
theSmartCachePoolPrecopyFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.10.1 | The Smart Cache Pool Precopy Failed |
theSmartCachePoolPrecopyFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.10.2 | Recover: The Smart Cache Pool Precopy Failed |
differentDiskType-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.3.1 | Inconsistent Smart Cache Disk Types |
differentDiskType-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.3.2 | Recover: Inconsistent Smart Cache Disk Types |
inconsistentEncryptionTypesBeforeAndAfterDiskReplacement-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.4.1 | Inconsistent Encryption Types Before And After Disk Replacement |
inconsistentEncryptionTypesBeforeAndAfterDiskReplacement-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.4.2 | Recover: Inconsistent Encryption Types Before And After Disk Replacement |
diskIsRemovedFromSmartCachePool-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.5.1 | A Disk Is Removed From A Smart Cache Pool |
diskIsRemovedFromSmartCachePool-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.5.2 | Recover: A Disk Is Removed From A Smart Cache Pool |
newDiskCapacityInsufficieny-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.6.1 | A New Disk Fails To Be Added To The Smart Cache Pool |
newDiskCapacityInsufficieny-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.6.2 | Recover: A New Disk Fails To Be Added To The Smart Cache Pool |
theModelOfTheNewDiskIsDifferentFromTheReplacedOneAndCannotBeAddedToTheSmartCachePool-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.7.1 | The Model Of The New Disk Is Different From The Replaced One And Cannot Be Added To The Smart Cache Pool |
theModelOfTheNewDiskIsDifferentFromTheReplacedOneAndCannotBeAddedToTheSmartCachePool-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.7.2 | Recover: The Model Of The New Disk Is Different From The Replaced One And Cannot Be Added To The Smart Cache Pool |
theNewDiskFailedToBeAddedToTheSmartCachePool-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.8.1 | The New Disk Failed To Be Added To The Smart Cache Pool |
theNewDiskFailedToBeAddedToTheSmartCachePool-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.8.2 | Recover: The New Disk Failed To Be Added To The Smart Cache Pool |
theSmartCachePoolReconstructionFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.9.1 | The Smart Cache Pool Reconstruction Failed |
theSmartCachePoolReconstructionFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.218.9.2 | Recover: The Smart Cache Pool Reconstruction Failed |
remoteReplicationCGIsInterrupted1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.1.1 | Remote Replication Consistency Group Is Disconnected |
remoteReplicationCGIsInterrupted1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.1.2 | Recover: Remote Replication Consistency Group Is Disconnected |
hyperMetroCGAutoDisconnect1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.12.1 | A HyperMetro Consistency Group Is Automatically Disconnected And The Local LUNs Cannot Provide Services |
hyperMetroCGAutoDisconnect1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.12.2 | Recover: A HyperMetro Consistency Group Is Automatically Disconnected And The Local LUNs Cannot Provide Services |
hyperMetroCGAutoDisconnect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.13.1 | A HyperMetro Consistency Group Is Automatically Disconnected And The Local LUNs Continue To Provide Services |
hyperMetroCGAutoDisconnect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.13.2 | Recover: A HyperMetro Consistency Group Is Automatically Disconnected And The Local LUNs Continue To Provide Services |
autoStartSynRemoteRepCGFails-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.14.1 | Remote Replication Consistency Group Failed To Synchronize Data Automatically |
autoStartSynRemoteRepCGFails-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.14.2 | Recover: Remote Replication Consistency Group Failed To Synchronize Data Automatically |
rmConsistencyRecoveredNew-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.15.1 | The Remote Replication Consistency Group Enters The ToBeRecovered State And Data On The Primary End Cannot Be Synchronized To The Remote End |
rmConsistencyRecoveredNew-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.15.2 | Recover: The Remote Replication Consistency Group Enters The ToBeRecovered State And Data On The Primary End Cannot Be Synchronized To The Remote End |
remoteReplicationCGIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.2.1 | Remote Replication Consistency Group Is Unavailable |
remoteReplicationCGIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.2.2 | Recover: Remote Replication Consistency Group Is Unavailable |
remoteReplicationCGAutoSplit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.4.1 | Remote Replication Consistency Group Is Automatically Split |
remoteReplicationCGAutoSplit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.4.2 | Recover: Remote Replication Consistency Group Is Automatically Split |
remoteReplicationCGIsInterrupted-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.9.1 | Remote Replication Consistency Group Is Disconnected |
remoteReplicationCGIsInterrupted-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.221.9.2 | Recover: Remote Replication Consistency Group Is Disconnected |
succeededInReconnectingTheRemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.112.1 | Succeeded In Reconnecting The Remote Device |
succeededInReconnectingTheRemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.112.2 | Recover: Succeeded In Reconnecting The Remote Device |
failedToReconnectTheRemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.113.1 | Failed To Reconnect The Remote Device |
failedToReconnectTheRemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.113.2 | Recover: Failed To Reconnect The Remote Device |
replicationLinkIsIsolatedBecauseItIsSubhealthy-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.119.1 | Replication Link Is Isolated Because It Is Subhealthy |
replicationLinkIsIsolatedBecauseItIsSubhealthy-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.119.2 | Recover: Replication Link Is Isolated Because It Is Subhealthy |
theWDMDeviceIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.120.1 | The WDM Device Is Disconnected |
theWDMDeviceIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.120.2 | Recover: The WDM Device Is Disconnected |
remoteDevPortNumInsuff-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.121.1 | Controller Links Of The Remote Device Are Insufficient |
remoteDevPortNumInsuff-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.121.2 | Recover: Controller Links Of The Remote Device Are Insufficient |
remoteDeviceIsSetToBeUnableToRecoverAutomatically-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.14.1 | Remote Device Is Set To Be Unable To Recover Automatically |
remoteDeviceIsSetToBeUnableToRecoverAutomatically-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.14.2 | Recover: Remote Device Is Set To Be Unable To Recover Automatically |
theLinkFromTheLocalStorageToTheExternalStorageDoesNotMeetTheRedundancyRequirements-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.302.1 | The Link From The Local Storage To The External Storage Does Not Meet The Redundancy Requirements |
theLinkFromTheLocalStorageToTheExternalStorageDoesNotMeetTheRedundancyRequirements-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.302.2 | Recover: The Link From The Local Storage To The External Storage Does Not Meet The Redundancy Requirements |
noRedundantLinkExistsBetweenTheLocalArrayAndRemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.67.1 | No Redundant Link Exists Between The Local Array And Remote Device |
noRedundantLinkExistsBetweenTheLocalArrayAndRemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.67.2 | Recover: No Redundant Link Exists Between The Local Array And Remote Device |
receptionOfMessagesFromTheWDMDeviceIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.68.1 | Reception Of Messages From The WDM Device Is Abnormal |
receptionOfMessagesFromTheWDMDeviceIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.68.2 | Recover: Reception Of Messages From The WDM Device Is Abnormal |
remoteDeviceIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.69.1 | Remote Device Is Faulty |
remoteDeviceIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.69.2 | Recover: Remote Device Is Faulty |
theLinkAuthenticationBetweenStorageDevicesFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.71.1 | The Link Authentication Between Storage Devices Failed |
theLinkAuthenticationBetweenStorageDevicesFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.71.2 | Recover: The Link Authentication Between Storage Devices Failed |
theReplicationLinkBetweenTheStorageArrayAndTheInterfaceModuleOfTheRemoteDeviceDoesNotMeetTheRedundancyRequirements-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.73.1 | The Replication Link Between The Storage Array And The Interface Module Of The Remote Device Does Not Meet The Redundancy Requirements |
theReplicationLinkBetweenTheStorageArrayAndTheInterfaceModuleOfTheRemoteDeviceDoesNotMeetTheRedundancyRequirements-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.73.2 | Recover: The Replication Link Between The Storage Array And The Interface Module Of The Remote Device Does Not Meet The Redundancy Requirements |
externalARRAYToOnlyOneController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.74.1 | The External Storage Is Connected To Only One Controller |
externalARRAYToOnlyOneController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.74.2 | Recover: The External Storage Is Connected To Only One Controller |
externalARRAYOffline-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.75.1 | The External Storage Is Offline |
externalARRAYOffline-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.75.2 | Recover: The External Storage Is Offline |
theRemoteDeviceIsOffline-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.80.1 | The Remote Device Is Offline |
theRemoteDeviceIsOffline-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.80.2 | Recover: The Remote Device Is Offline |
theProtocolLinkOfTheRemoteDeviceIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.81.1 | The Protocol Link Of The Remote Device Is Disconnected |
theProtocolLinkOfTheRemoteDeviceIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.81.2 | Recover: The Protocol Link Of The Remote Device Is Disconnected |
protocolConnectionOfTheRemoteDeviceIsNotRedundant-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.82.1 | Protocol Connection Of The Remote Device Is Not Redundant |
protocolConnectionOfTheRemoteDeviceIsNotRedundant-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.82.2 | Recover: Protocol Connection Of The Remote Device Is Not Redundant |
createRmtdSuccess-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.83.1 | Succeeded In Creating A Remote Device |
createRmtdSuccess-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.83.2 | Recover: Succeeded In Creating A Remote Device |
createRmtdFail-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.84.1 | Failed To Create A Remote Device |
createRmtdFail-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.84.2 | Recover: Failed To Create A Remote Device |
succeededInDeletingARemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.85.1 | Succeeded In Deleting A Remote Device |
succeededInDeletingARemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.85.2 | Recover: Succeeded In Deleting A Remote Device |
failedToDeleteARemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.86.1 | Failed To Delete A Remote Device |
failedToDeleteARemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.86.2 | Recover: Failed To Delete A Remote Device |
succeededInModifyingARemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.87.1 | Succeeded In Modifying A Remote Device |
succeededInModifyingARemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.87.2 | Recover: Succeeded In Modifying A Remote Device |
failedToModifyARemoteDevice-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.88.1 | Failed To Modify A Remote Device |
failedToModifyARemoteDevice-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.88.2 | Recover: Failed To Modify A Remote Device |
succeededInCreatingAnIPGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.89.1 | Succeeded In Creating An IP Group |
succeededInCreatingAnIPGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.89.2 | Recover: Succeeded In Creating An IP Group |
failedToCreateAnIPGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.90.1 | Failed To Create An IP Group |
failedToCreateAnIPGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.90.2 | Recover: Failed To Create An IP Group |
succeededInDeletingAnIPGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.91.1 | Succeeded In Deleting An IP Group |
succeededInDeletingAnIPGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.91.2 | Recover: Succeeded In Deleting An IP Group |
failedToDeleteAnIPGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.92.1 | Failed To Delete An IP Group |
failedToDeleteAnIPGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.92.2 | Recover: Failed To Delete An IP Group |
succeededInDeletingAnIPAddressFromTheIPGroup-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.95.1 | Succeeded In Deleting An IP Address From The IP Group |
succeededInDeletingAnIPAddressFromTheIPGroup-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.224.95.2 | Recover: Succeeded In Deleting An IP Address From The IP Group |
powerModuleIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.2.1 | Power Module Is Removed |
powerModuleIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.2.2 | Recover: Power Module Is Removed |
powerModuleHasNoInput1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.20.1 | Power Module Has No Input |
powerModuleHasNoInput1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.20.2 | Recover: Power Module Has No Input |
powerModulesTypesDifferent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.21.1 | Power Modules Of Different Types Are Used In A Disk Enclosure |
powerModulesTypesDifferent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.21.2 | Recover: Power Modules Of Different Types Are Used In A Disk Enclosure |
failedToMonitorAPowerModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.23.1 | The System Failed To Monitor A Power Module |
failedToMonitorAPowerModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.23.2 | Recover: The System Failed To Monitor A Power Module |
powerModuleIsIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.24.1 | Power Module Type Is Mismatched |
powerModuleIsIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.24.2 | Recover: Power Module Type Is Mismatched |
powerModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.25.1 | Power Module Is Faulty |
powerModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.25.2 | Recover: Power Module Is Faulty |
powerIsIncompatWithController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.26.1 | The Power Module Is Incompatible With The Controller |
powerIsIncompatWithController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.26.2 | Recover: The Power Module Is Incompatible With The Controller |
powerModuleInputIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.33.1 | Power Module Input Is Abnormal |
powerModuleInputIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.33.2 | Recover: Power Module Input Is Abnormal |
powerModuleHasNoInput-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.34.1 | Power Module Has No Input |
powerModuleHasNoInput-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.34.2 | Recover: Power Module Has No Input |
unbalancedPowerSupplyCurrentAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.36.1 | Uneven Power Output |
unbalancedPowerSupplyCurrentAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.36.2 | Recover: Uneven Power Output |
powerIsIncompatWithExpModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.38.1 | The Power Module Is Incompatible With The Expansion Module |
powerIsIncompatWithExpModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.38.2 | Recover: The Power Module Is Incompatible With The Expansion Module |
powerModuleTempExceedsLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.4.1 | Power Module Temperature Exceeds The Upper Limit |
powerModuleTempExceedsLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.4.2 | Recover: Power Module Temperature Exceeds The Upper Limit |
powerModuleInputIsAbnormal1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.5.1 | Power Module Input Is Abnormal |
powerModuleInputIsAbnormal1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.23.5.2 | Recover: Power Module Input Is Abnormal |
portLinkIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.20.1 | Abnormal Port Link |
portLinkIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.20.2 | Recover: Abnormal Port Link |
failedToMonitorAnOpticalModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.21.1 | Optical Module Cannot Be Monitored |
failedToMonitorAnOpticalModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.21.2 | Recover: Optical Module Cannot Be Monitored |
opticalModuleTempIsBelowLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.22.1 | Optical Module Temperature Is Below The Lower Limit |
opticalModuleTempIsBelowLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.22.2 | Recover: Optical Module Temperature Is Below The Lower Limit |
opticalModuleTempExceedsLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.23.1 | Optical Module Temperature Exceeds The Upper Limit |
opticalModuleTempExceedsLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.23.2 | Recover: Optical Module Temperature Exceeds The Upper Limit |
failedToMonitorOpOrEleModule-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.24.1 | The System Failed To Monitor An Optical Or Electrical Module |
failedToMonitorOpOrEleModule-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.24.2 | Recover: The System Failed To Monitor An Optical Or Electrical Module |
electricalModuleRateIsInconsistentWithThatOfItsPort-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.27.1 | Electrical Module Rate Is Inconsistent With That Of Its Port |
electricalModuleRateIsInconsistentWithThatOfItsPort-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.27.2 | Recover: Electrical Module Rate Is Inconsistent With That Of Its Port |
theOpticalElectricalModuleIsNotSupportedByThePort-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.29.1 | The OpticalElectrical Module Is Not Supported By The Port |
theOpticalElectricalModuleIsNotSupportedByThePort-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.29.2 | Recover: The OpticalElectrical Module Is Not Supported By The Port |
portOpticalModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.3.1 | Port Optical Module Is Faulty |
portOpticalModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.3.2 | Recover: Port Optical Module Is Faulty |
opticalModuleTypeIsIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.4.1 | Port Unavailable Due To Incompatible Optical Module Type |
opticalModuleTypeIsIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.4.2 | Recover: Port Unavailable Due To Incompatible Optical Module Type |
opticalModuleRateIsInconsistent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.5.1 | Optical Module Rate Is Inconsistent With That Of Its Port |
opticalModuleRateIsInconsistent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.234.5.2 | Recover: Optical Module Rate Is Inconsistent With That Of Its Port |
theMemoryIsFaulty2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.12.1 | The Memory Is Faulty |
theMemoryIsFaulty2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.12.2 | Recover: The Memory Is Faulty |
theMemoryIsFaulty3-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.13.1 | The Memory Is Faulty |
theMemoryIsFaulty3-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.13.2 | Recover: The Memory Is Faulty |
memoryAuthenticationFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.14.1 | Memory Authentication Failed |
memoryAuthenticationFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.14.2 | Recover: Memory Authentication Failed |
theMemorySlotIsIncorrect-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.15.1 | The Memory Slot Is Incorrect |
theMemorySlotIsIncorrect-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.15.2 | Recover: The Memory Slot Is Incorrect |
aCorrectableErrorOccurredOnTheMemory1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.16.1 | A Correctable Error Occurred On The Memory |
aCorrectableErrorOccurredOnTheMemory1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.16.2 | Recover: A Correctable Error Occurred On The Memory |
theMemoryIsFaulty1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.17.1 | The Memory Is Faulty |
theMemoryIsFaulty1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.17.2 | Recover: The Memory Is Faulty |
theMemoryIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.18.1 | The Memory Is Faulty |
theMemoryIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.18.2 | Recover: The Memory Is Faulty |
aCorrectableErrorOccurredOnTheMemory-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.19.1 | A Correctable Error Occurred On The Memory |
aCorrectableErrorOccurredOnTheMemory-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.237.19.2 | Recover: A Correctable Error Occurred On The Memory |
licenseIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.244.1.1 | The License Is About To Expire |
licenseIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.244.1.2 | Recover: The License Is About To Expire |
licenseHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.244.2.1 | The License Has Expired |
licenseHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.244.2.2 | Recover: The License Has Expired |
licenseIsInvalidWithStartDate-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.244.6.1 | The License Is Invalid |
licenseIsInvalidWithStartDate-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.244.6.2 | Recover: The License Is Invalid |
remoteLunExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.250.1.1 | The Number Of External LUNs Reaches The Upper Limit |
remoteLunExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.250.1.2 | Recover: The Number Of External LUNs Reaches The Upper Limit |
heterogeneousLinkConnectionFailures-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.250.3.1 | Heterogeneous Link Connection Failures |
heterogeneousLinkConnectionFailures-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.250.3.2 | Recover: Heterogeneous Link Connection Failures |
remoteLunPathExceedUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.250.76.1 | The Number Of Paths Of External LUNs Reaches The Upper Limit |
remoteLunPathExceedUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.250.76.2 | Recover: The Number Of Paths Of External LUNs Reaches The Upper Limit |
almSmartMigrationErr-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.253.8.1 | LUN Migration Is Faulty |
almSmartMigrationErr-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.253.8.2 | Recover: LUN Migration Is Faulty |
theHostPathDoesNotMeetTheRedundancySpecifications-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.255.36.1 | Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
theHostPathDoesNotMeetTheRedundancySpecifications-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.255.36.2 | Recover: Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
theHostPathDoesNotMeetTheRedundancySpecification-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.255.37.1 | Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
theHostPathDoesNotMeetTheRedundancySpecification-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.255.37.2 | Recover: Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
hostPathDoesNotMeetTheRedundancySpecifications-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.255.38.1 | Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
hostPathDoesNotMeetTheRedundancySpecifications-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.255.38.2 | Recover: Paths Between The Host And Storage Array Do Not Meet Redundancy Requirements |
addRemoteReplicationToCGFails-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.21.1 | Failed To Add Remote Replication To A Consistent Group |
addRemoteReplicationToCGFails-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.21.2 | Recover: Failed To Add Remote Replication To A Consistent Group |
failedRecoverRmReplication-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.22.1 | Failed To Recover The LUN Remote Replication Service At The Array End |
failedRecoverRmReplication-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.22.2 | Recover: Failed To Recover The LUN Remote Replication Service At The Array End |
fsRmPairRecovered-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.27.1 | File Remote Replication Enters The ToBeRecovered Status And Data At The Primary End Cannot Be Synchronized To The Remote End |
fsRmPairRecovered-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.27.2 | Recover: File Remote Replication Enters The ToBeRecovered Status And Data At The Primary End Cannot Be Synchronized To The Remote End |
fsRemoteReplicationPairInvalid-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.274.1 | A Remote Replication Is Unavailable |
fsRemoteReplicationPairInvalid-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.274.2 | Recover: A Remote Replication Is Unavailable |
fsRemoteReplicationPairFault1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.275.1 | A Remote Replication Pair Is Interrupted Unexpectedly |
fsRemoteReplicationPairFault1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.275.2 | Recover: A Remote Replication Pair Is Interrupted Unexpectedly |
fsRemoteReplicationAutoSyncFail-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.304.1 | A Remote Replication Pair Fails To Synchronize Data Automatically |
fsRemoteReplicationAutoSyncFail-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.304.2 | Recover: A Remote Replication Pair Fails To Synchronize Data Automatically |
remoteReplicationAutomaticSplit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.311.1 | Remote Replication Is Automatically Split |
remoteReplicationAutomaticSplit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.311.2 | Recover: Remote Replication Is Automatically Split |
fsRemoteReplicationPairFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.36.1 | A Remote Replication Is Interrupted Unexpectedly |
fsRemoteReplicationPairFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.36.2 | Recover: A Remote Replication Is Interrupted Unexpectedly |
rmPairRecoveredNew-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.38.1 | The Remote Replication Pair Enters The ToBeRecovered State Data On The Primary End Cannot Be Synchronized To The Remote End |
rmPairRecoveredNew-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.38.2 | Recover: The Remote Replication Pair Enters The ToBeRecovered State Data On The Primary End Cannot Be Synchronized To The Remote End |
remoteReplicationIsInterrupted-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.56.1 | Remote Replication Is Interrupted |
remoteReplicationIsInterrupted-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.56.2 | Recover: Remote Replication Is Interrupted |
remoteReplicationIsInvalid-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.57.1 | Remote Replication Is Unavailable |
remoteReplicationIsInvalid-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.57.2 | Recover: Remote Replication Is Unavailable |
autoStartSynRemoteRepFails-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.58.1 | Remote Replication Failed To Synchronize Data Automatically |
autoStartSynRemoteRepFails-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.263.58.2 | Recover: Remote Replication Failed To Synchronize Data Automatically |
eULANotSigned-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.264.1.1 | EULA Not Signed |
eULANotSigned-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.264.1.2 | Recover: EULA Not Signed |
diskDomainDegradation-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.1.1 | Disk Domain Is Degraded |
diskDomainDegradation-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.1.2 | Recover: Disk Domain Is Degraded |
hotSpareCapacityInsufficient1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.104.1 | The Hot Spare Space Of The Disk Domain Is Insufficient |
hotSpareCapacityInsufficient1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.104.2 | Recover: The Hot Spare Space Of The Disk Domain Is Insufficient |
theNewDiskFailedToBeAddedToTheDiskDomain-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.108.1 | The New Disk Failed To Be Added To The Disk Domain |
theNewDiskFailedToBeAddedToTheDiskDomain-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.108.2 | Recover: The New Disk Failed To Be Added To The Disk Domain |
inconsistentEncryptionTypesBeforeAndAfterDiskReplacement1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.109.1 | Inconsistent Encryption Types Before And After Disk Replacement |
inconsistentEncryptionTypesBeforeAndAfterDiskReplacement1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.109.2 | Recover: Inconsistent Encryption Types Before And After Disk Replacement |
diskDomainReconstructionFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.11.1 | Disk Domain Reconstruction Failed |
diskDomainReconstructionFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.11.2 | Recover: Disk Domain Reconstruction Failed |
diskDomainLosesEnclosurelevelRedundancyCapability-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.110.1 | Disk Domain Loses Enclosurelevel Redundancy Capability |
diskDomainLosesEnclosurelevelRedundancyCapability-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.110.2 | Recover: Disk Domain Loses Enclosurelevel Redundancy Capability |
theDiskDomainCannotProvideEnclosureLevelRedundancyDueToDiskLocationChange-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.112.1 | The Disk Domain Cannot Provide EnclosureLevel Redundancy Due To Disk Location Change |
theDiskDomainCannotProvideEnclosureLevelRedundancyDueToDiskLocationChange-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.112.2 | Recover: The Disk Domain Cannot Provide EnclosureLevel Redundancy Due To Disk Location Change |
theBackgroundInspectionTaskOfTheDiskDomainIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.116.1 | The Background Inspection Task Of The Disk Domain Is Abnormal |
theBackgroundInspectionTaskOfTheDiskDomainIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.116.2 | Recover: The Background Inspection Task Of The Disk Domain Is Abnormal |
hotSpareCapacityInsufficient-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.121.1 | The SSD Space In The Disk Domain Is Insufficient |
hotSpareCapacityInsufficient-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.121.2 | Recover: The SSD Space In The Disk Domain Is Insufficient |
aComponentInTheDiskDomainIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.122.1 | A Component In The Disk Domain Is Abnormal |
aComponentInTheDiskDomainIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.122.2 | Recover: A Component In The Disk Domain Is Abnormal |
thePerformanceLayerQuotaOfTheStoragePoolIsInsufficient-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.124.1 | The Performance Layer Quota Of The Storage Pool Is Insufficient |
thePerformanceLayerQuotaOfTheStoragePoolIsInsufficient-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.124.2 | Recover: The Performance Layer Quota Of The Storage Pool Is Insufficient |
theHotSpareSpaceAtThePerformanceLayerIsInsufficient-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.125.1 | The Hot Spare Space At The Performance Layer Is Insufficient |
theHotSpareSpaceAtThePerformanceLayerIsInsufficient-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.125.2 | Recover: The Hot Spare Space At The Performance Layer Is Insufficient |
aDiskIsRemovedFromThePerformanceLayer-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.126.1 | A Disk Is Removed From The Performance Layer |
aDiskIsRemovedFromThePerformanceLayer-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.126.2 | Recover: A Disk Is Removed From The Performance Layer |
theNewDiskIsNotAddedToThePerformanceLayer-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.127.1 | The New Disk Is Not Added To The Performance Layer |
theNewDiskIsNotAddedToThePerformanceLayer-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.127.2 | Recover: The New Disk Is Not Added To The Performance Layer |
theMemberDiskTypesAreInconsistent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.128.1 | The Member Disk Types Are Inconsistent |
theMemberDiskTypesAreInconsistent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.128.2 | Recover: The Member Disk Types Are Inconsistent |
theMemberDiskEncryptionTypesAreInconsistent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.129.1 | The Member Disk Encryption Types Are Inconsistent |
theMemberDiskEncryptionTypesAreInconsistent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.129.2 | Recover: The Member Disk Encryption Types Are Inconsistent |
failedToAddTheNewDiskToThePerformanceLayer-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.130.1 | Failed To Add The New Disk To The Performance Layer |
failedToAddTheNewDiskToThePerformanceLayer-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.130.2 | Recover: Failed To Add The New Disk To The Performance Layer |
theNewDiskIsNotAddedToThePerformanceLayerDueToAnInconsistentModel-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.131.1 | The New Disk Is Not Added To The Performance Layer Due To An Inconsistent Model |
theNewDiskIsNotAddedToThePerformanceLayerDueToAnInconsistentModel-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.131.2 | Recover: The New Disk Is Not Added To The Performance Layer Due To An Inconsistent Model |
diskDomainSelfCheck-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.134.1 | Disk Domain SelfCheck |
diskDomainSelfCheck-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.134.2 | Recover: Disk Domain SelfCheck |
newDiskInconsistentHardwareModel-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.136.1 | The New Disk Is Not Added To The Disk Domain |
newDiskInconsistentHardwareModel-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.136.2 | Recover: The New Disk Is Not Added To The Disk Domain |
theDiskDomainScaleInTaskIsAboutToBeRolledBack1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.137.1 | The Disk Domain ScaleIn Task Is About To Be Rolled Back |
theDiskDomainScaleInTaskIsAboutToBeRolledBack1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.137.2 | Recover: The Disk Domain ScaleIn Task Is About To Be Rolled Back |
theDiskDomainScaleInTaskIsAboutToBeRolledBack-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.138.1 | The Disk Domain ScaleIn Task Is About To Be Rolled Back |
theDiskDomainScaleInTaskIsAboutToBeRolledBack-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.138.2 | Recover: The Disk Domain ScaleIn Task Is About To Be Rolled Back |
diskDomainPreCopyFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.14.1 | Disk Domain PreCopy Failed |
diskDomainPreCopyFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.14.2 | Recover: Disk Domain PreCopy Failed |
diskDomainAssociatedWithThePerformanceLayerLosesEnclosurelevelRedundancyCapabilityDueToDiskLocationChange-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.140.1 | Disk Domain Associated With The Performance Layer Loses Enclosurelevel Redundancy Capability Due To Disk Location Change |
diskDomainAssociatedWithThePerformanceLayerLosesEnclosurelevelRedundancyCapabilityDueToDiskLocationChange-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.140.2 | Recover: Disk Domain Associated With The Performance Layer Loses Enclosurelevel Redundancy Capability Due To Disk Location Change |
diskDomainLosesEnclosurelevelRedundancyCapability1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.141.1 | Disk Domain Loses Enclosurelevel Redundancy Capability |
diskDomainLosesEnclosurelevelRedundancyCapability1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.141.2 | Recover: Disk Domain Loses Enclosurelevel Redundancy Capability |
theNewDiskCannotBeAddedToThePerformanceLayer-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.142.1 | The New Disk Cannot Be Added To The Performance Layer |
theNewDiskCannotBeAddedToThePerformanceLayer-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.142.2 | Recover: The New Disk Cannot Be Added To The Performance Layer |
diskDomainCapNotAvailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.143.1 | Some Capacity Of The Disk Domain May Be Unavailable |
diskDomainCapNotAvailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.143.2 | Recover: Some Capacity Of The Disk Domain May Be Unavailable |
lossEnclosureLevelAbilityAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.144.1 | Disk Domain Loses Distributed EC Redundancy Capability |
lossEnclosureLevelAbilityAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.144.2 | Recover: Disk Domain Loses Distributed EC Redundancy Capability |
diskRoamingAlarmBetweenController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.145.1 | Disk Domain Associated With The Performance Layer Loses Distributed EC Redundancy Capability Due To Disk Location Change |
diskRoamingAlarmBetweenController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.145.2 | Recover: Disk Domain Associated With The Performance Layer Loses Distributed EC Redundancy Capability Due To Disk Location Change |
capCheckPointAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.148.1 | The Disk Domain Capacity Is Found To Be Abnormal In A Check |
capCheckPointAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.148.2 | Recover: The Disk Domain Capacity Is Found To Be Abnormal In A Check |
diskDomainFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.2.1 | Disk Domain Is Faulty |
diskDomainFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.2.2 | Recover: Disk Domain Is Faulty |
theModelOfTheNewDiskIsDifferentFromTheReplacedOneAndCannotBeAddedToTheDiskDomain-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.293.1 | The Model Of The New Disk Is Different From The Replaced One And Cannot Be Added To The Disk Domain |
theModelOfTheNewDiskIsDifferentFromTheReplacedOneAndCannotBeAddedToTheDiskDomain-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.293.2 | Recover: The Model Of The New Disk Is Different From The Replaced One And Cannot Be Added To The Disk Domain |
diskDomainIsOffline-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.3.1 | Disk Domain Is Offline |
diskDomainIsOffline-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.3.2 | Recover: Disk Domain Is Offline |
newDiskCapacityInsufficieny1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.32.1 | A New Disk Fails To Be Added To The Disk Domain |
newDiskCapacityInsufficieny1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.32.2 | Recover: A New Disk Fails To Be Added To The Disk Domain |
differentDiskType1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.6.1 | Inconsistent Disk Types |
differentDiskType1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.6.2 | Recover: Inconsistent Disk Types |
diskIsRemovedFromDiskDomain-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.8.1 | A Disk Is Removed From A Disk Domain |
diskIsRemovedFromDiskDomain-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.8.2 | Recover: A Disk Is Removed From A Disk Domain |
diskDomainHasAMediumError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.85.1 | A Disk Domain Has A Medium Error |
diskDomainHasAMediumError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.85.2 | Recover: A Disk Domain Has A Medium Error |
internalResourceOfTheDiskDomainIsNotEnough-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.87.1 | Internal Resource Of The Disk Domain Is Not Enough |
internalResourceOfTheDiskDomainIsNotEnough-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.87.2 | Recover: Internal Resource Of The Disk Domain Is Not Enough |
theSelfEncryptingDiskKeyInADiskDomainHasExpired-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.95.1 | The SelfEncrypting Disk Key In A Disk Domain Has Expired |
theSelfEncryptingDiskKeyInADiskDomainHasExpired-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.95.2 | Recover: The SelfEncrypting Disk Key In A Disk Domain Has Expired |
theSelfEncryptingDiskKeyInADiskDomainIsAboutToExpire-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.96.1 | The SelfEncrypting Disk Key In A Disk Domain Is About To Expire |
theSelfEncryptingDiskKeyInADiskDomainIsAboutToExpire-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.266.96.2 | Recover: The SelfEncrypting Disk Key In A Disk Domain Is About To Expire |
theAmountOfWrittenDataReachesTheSpecificationOfEffectiveCapacity-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.267.5.1 | The Amount Of Written Data Reaches The Specification Of Effective Capacity |
theAmountOfWrittenDataReachesTheSpecificationOfEffectiveCapacity-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.267.5.2 | Recover: The Amount Of Written Data Reaches The Specification Of Effective Capacity |
theAmountOfWrittenDataExceedsTheSpecificationOfEffectiveCapacity-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.267.6.1 | The Amount Of Written Data Exceeds The Specification Of Effective Capacity |
theAmountOfWrittenDataExceedsTheSpecificationOfEffectiveCapacity-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.267.6.2 | Recover: The Amount Of Written Data Exceeds The Specification Of Effective Capacity |
smartQoSExceedThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.269.53.1 | Service Performance Continuously Exceeds The Alarm Threshold Of The SmartQoS Upper Limit Policy |
smartQoSExceedThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.269.53.2 | Recover: Service Performance Continuously Exceeds The Alarm Threshold Of The SmartQoS Upper Limit Policy |
performanceOfTheSmartQoSPolicyFailedToReachTheSpecifiedControlObjective-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.269.57.1 | Performance Of The SmartQoS Policy Failed To Reach The Specified Control Objective |
performanceOfTheSmartQoSPolicyFailedToReachTheSpecifiedControlObjective-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.269.57.2 | Recover: Performance Of The SmartQoS Policy Failed To Reach The Specified Control Objective |
controllerIsOverload-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.269.99.1 | The Controller Is Overloaded |
controllerIsOverload-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.269.99.2 | Recover: The Controller Is Overloaded |
faultsOccurDuringTheRollbackOfASnapshot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.27.5.1 | Faults Occur During The Rollback Of A Snapshot |
faultsOccurDuringTheRollbackOfASnapshot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.27.5.2 | Recover: Faults Occur During The Rollback Of A Snapshot |
hyperCDPSchedulesOfTheVStoreFailedToBeSynchronized-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.27.7.1 | HyperCDP Schedules Of The VStore Failed To Be Synchronized |
hyperCDPSchedulesOfTheVStoreFailedToBeSynchronized-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.27.7.2 | Recover: HyperCDP Schedules Of The VStore Failed To Be Synchronized |
exceptionsOccurContinuouslyWhenFileSystemSnapshotsAreDeletedInTheBackground-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.27.8.1 | Exceptions Occur Continuously When File System Snapshots Are Deleted In The Background |
exceptionsOccurContinuouslyWhenFileSystemSnapshotsAreDeletedInTheBackground-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.27.8.2 | Recover: Exceptions Occur Continuously When File System Snapshots Are Deleted In The Background |
failedToSynchronizeLogicalPortConfigurationsToTheSecondaryVStoreOfTheVStorePair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.279.1.1 | Failed To Synchronize Logical Port Configurations To The Secondary VStore Of The VStore Pair |
failedToSynchronizeLogicalPortConfigurationsToTheSecondaryVStoreOfTheVStorePair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.279.1.2 | Recover: Failed To Synchronize Logical Port Configurations To The Secondary VStore Of The VStore Pair |
theFirewallConfigurationsOfTheVStorePairAtThePrimaryAndSecondarySitesAreInconsistent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.279.2.1 | The Firewall Configurations Of The VStore Pair At The Primary And Secondary Sites Are Inconsistent |
theFirewallConfigurationsOfTheVStorePairAtThePrimaryAndSecondarySitesAreInconsistent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.279.2.2 | Recover: The Firewall Configurations Of The VStore Pair At The Primary And Secondary Sites Are Inconsistent |
theDNSLoadBalancingSwitchesOnThePrimaryAndSecondarySitesOfTheVStorePairAreInDifferentStates-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.279.3.1 | The DNS Load Balancing Switches On The Primary And Secondary Sites Of The VStore Pair Are In Different States |
theDNSLoadBalancingSwitchesOnThePrimaryAndSecondarySitesOfTheVStorePairAreInDifferentStates-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.279.3.2 | Recover: The DNS Load Balancing Switches On The Primary And Secondary Sites Of The VStore Pair Are In Different States |
antivirusServerIsFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.285.68.1 | The Antivirus Server Is Faulty |
antivirusServerIsFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.285.68.2 | Recover: The Antivirus Server Is Faulty |
noAntivirusServerIsAvailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.285.72.1 | No Antivirus Server Is Available |
noAntivirusServerIsAvailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.285.72.2 | Recover: No Antivirus Server Is Available |
theAntivirusServerIsOverloaded-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.285.74.1 | The Antivirus Server Is Overloaded |
theAntivirusServerIsOverloaded-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.285.74.2 | Recover: The Antivirus Server Is Overloaded |
memberPortsOfTheFailoverGroupDoNotMeetRedundancyRequirements1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.289.1.1 | Member Ports Of The Failover Group Do Not Meet Redundancy Requirements |
memberPortsOfTheFailoverGroupDoNotMeetRedundancyRequirements1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.289.1.2 | Recover: Member Ports Of The Failover Group Do Not Meet Redundancy Requirements |
memberPortsOfTheFailoverGroupDoNotMeetRedundancyRequirements-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.289.2.1 | Member Ports Of The Failover Group Do Not Meet Redundancy Requirements |
memberPortsOfTheFailoverGroupDoNotMeetRedundancyRequirements-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.289.2.2 | Recover: Member Ports Of The Failover Group Do Not Meet Redundancy Requirements |
failoverNoRedundancy-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.289.4.1 | Member Ports Of The Failover Group Do Not Meet Redundancy Requirements |
failoverNoRedundancy-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.289.4.2 | Recover: Member Ports Of The Failover Group Do Not Meet Redundancy Requirements |
assistantCoolingUnitRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.2.1 | Assistant Cooling Module Removed |
assistantCoolingUnitRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.2.2 | Recover: Assistant Cooling Module Removed |
assistCoolingUnitMonitorFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.4.1 | The System Failed To Monitor Assistant Cooling Unit |
assistCoolingUnitMonitorFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.4.2 | Recover: The System Failed To Monitor Assistant Cooling Unit |
coolingUnitIsUnrecognizable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.5.1 | Assistant Cooling Unit Is Unrecognizable |
coolingUnitIsUnrecognizable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.5.2 | Recover: Assistant Cooling Unit Is Unrecognizable |
coolingUnitIsIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.6.1 | The Auxiliary Heat Dissipation Module Is Incompatible With The Controller Module |
coolingUnitIsIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.6.2 | Recover: The Auxiliary Heat Dissipation Module Is Incompatible With The Controller Module |
assistantCoolingUnitIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.68.1 | Assistant Cooling Unit Is Faulty |
assistantCoolingUnitIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.306.68.2 | Recover: Assistant Cooling Unit Is Faulty |
metadataMediaErrorsExistInVariablelengthDeduplication-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.350.2.1 | Metadata Media Errors Exist In Variablelength Deduplication |
metadataMediaErrorsExistInVariablelengthDeduplication-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.350.2.2 | Recover: Metadata Media Errors Exist In Variablelength Deduplication |
reductionSpeedIsLow-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.350.6.1 | Low Data Reduction Speed |
reductionSpeedIsLow-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.350.6.2 | Recover: Low Data Reduction Speed |
writeProtectionIsEnabledForFS-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.117.1 | File System Under Write Protection |
writeProtectionIsEnabledForFS-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.117.2 | Recover: File System Under Write Protection |
theRatioOfTheTotalCapacityOfAllFileSystemsAndLUNsToTheCapacityOfTheStoragePoolExceedsTheOverprovisioningThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.2.1 | The Ratio Of The Total Capacity Of All File Systems And LUNs To The Capacity Of The Storage Pool Exceeds The Overprovisioning Threshold |
theRatioOfTheTotalCapacityOfAllFileSystemsAndLUNsToTheCapacityOfTheStoragePoolExceedsTheOverprovisioningThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.2.2 | Recover: The Ratio Of The Total Capacity Of All File Systems And LUNs To The Capacity Of The Storage Pool Exceeds The Overprovisioning Threshold |
theSpaceOfTheFileSystemIsUsedUp-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.294.1 | The Space Of The File System Is Used Up |
theSpaceOfTheFileSystemIsUsedUp-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.294.2 | Recover: The Space Of The File System Is Used Up |
filesystemCapacityIsFull-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.296.1 | Expand The Capacity In A Timely Manner Because The File System Capacity Reaches The Alarm Threshold |
filesystemCapacityIsFull-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.296.2 | Recover: Expand The Capacity In A Timely Manner Because The File System Capacity Reaches The Alarm Threshold |
fileOrDirExistMediumError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.300.1 | A Metadata Medium Error Occurred To The File Or Directory |
fileOrDirExistMediumError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.300.2 | Recover: A Metadata Medium Error Occurred To The File Or Directory |
fileDataExistMediumError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.301.1 | A Medium Error Occurred To The File Data |
fileDataExistMediumError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.301.2 | Recover: A Medium Error Occurred To The File Data |
theRemainingCapacityOfTheAuditLogFileSystemIsInsufficient-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.303.1 | The Remaining Capacity Of The Audit Log File System Is Insufficient |
theRemainingCapacityOfTheAuditLogFileSystemIsInsufficient-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.303.2 | Recover: The Remaining Capacity Of The Audit Log File System Is Insufficient |
theSpaceOfTheAuditLogFileSystemIsUsedUp-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.304.1 | The Space Of The Audit Log File System Is Used Up |
theSpaceOfTheAuditLogFileSystemIsUsedUp-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.304.2 | Recover: The Space Of The Audit Log File System Is Used Up |
theClusterWriteCacheIsDegraded-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.306.1 | The Cluster Write Cache Is Degraded |
theClusterWriteCacheIsDegraded-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.306.2 | Recover: The Cluster Write Cache Is Degraded |
failedToCollectAuditLogFileSystemLogs-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.308.1 | Failed To Collect Audit Log File System Logs |
failedToCollectAuditLogFileSystemLogs-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.308.2 | Recover: Failed To Collect Audit Log File System Logs |
failedToUpdateTheAuditLogFileSystemTiming-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.309.1 | Failed To Update The Audit Log File System Timing |
failedToUpdateTheAuditLogFileSystemTiming-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.309.2 | Recover: Failed To Update The Audit Log File System Timing |
theFileSystemTransactionPlaybackFailedContinuouslyOrHasBeenRunningForALongTime-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.310.1 | The File System Transaction Playback Failed Continuously Or Has Been Running For A Long Time |
theFileSystemTransactionPlaybackFailedContinuouslyOrHasBeenRunningForALongTime-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.310.2 | Recover: The File System Transaction Playback Failed Continuously Or Has Been Running For A Long Time |
tooMuchSpaceOfTheReservedVolumeOfTheFileSystemIsOccupied-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.311.1 | Too Much Space Of The Reserved Volume Of The File System Is Occupied |
tooMuchSpaceOfTheReservedVolumeOfTheFileSystemIsOccupied-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.311.2 | Recover: Too Much Space Of The Reserved Volume Of The File System Is Occupied |
theFileSystemFailedToReclaimTransactionLogsContinuouslyOrTheOperationTakesALongTime1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.312.1 | The File System Failed To Reclaim Transaction Logs Continuously Or The Operation Takes A Long Time |
theFileSystemFailedToReclaimTransactionLogsContinuouslyOrTheOperationTakesALongTime1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.312.2 | Recover: The File System Failed To Reclaim Transaction Logs Continuously Or The Operation Takes A Long Time |
numberOfAllocatedObjectIDsInTheFileSystemExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.313.1 | Number Of Allocated Object IDs In The File System Exceeds The Threshold |
numberOfAllocatedObjectIDsInTheFileSystemExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.313.2 | Recover: Number Of Allocated Object IDs In The File System Exceeds The Threshold |
singleVnodeCapacityIsTooHigh-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.316.1 | Used Capacity Of A Single Vnode In The File System Is Too High |
singleVnodeCapacityIsTooHigh-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.316.2 | Recover: Used Capacity Of A Single Vnode In The File System Is Too High |
smartMobilityRemoteDeviceFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.317.1 | SmartMobility Remote Device Fault |
smartMobilityRemoteDeviceFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.317.2 | Recover: SmartMobility Remote Device Fault |
failedToRecallDataDueToInsufficientRemainingSpaceOfTheFileSystem-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.318.1 | Failed To Recall Data Due To Insufficient Remaining Space Of The File System |
failedToRecallDataDueToInsufficientRemainingSpaceOfTheFileSystem-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.318.2 | Recover: Failed To Recall Data Due To Insufficient Remaining Space Of The File System |
insufficientCapacityReservedForFileSystemDataProtection-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.323.1 | Insufficient Capacity Reserved For File System Data Protection |
insufficientCapacityReservedForFileSystemDataProtection-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.323.2 | Recover: Insufficient Capacity Reserved For File System Data Protection |
theFileSystemFailedToReclaimTransactionLogsContinuouslyOrTheOperationTakesALongTime-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.325.1 | The File System Failed To Reclaim Transaction Logs Continuously Or The Operation Takes A Long Time |
theFileSystemFailedToReclaimTransactionLogsContinuouslyOrTheOperationTakesALongTime-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.325.2 | Recover: The File System Failed To Reclaim Transaction Logs Continuously Or The Operation Takes A Long Time |
auditServerFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.327.1 | The Syslog Server For Audit Logs Cannot Be Connected |
auditServerFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.327.2 | Recover: The Syslog Server For Audit Logs Cannot Be Connected |
engineHighCapacityAndUneven-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.329.1 | Excessively High Capacity Usage Of Some Controller Enclosures |
engineHighCapacityAndUneven-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.329.2 | Recover: Excessively High Capacity Usage Of Some Controller Enclosures |
directorySizeIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.4.1 | The Directory Contains Too Many Files And Subdirectories |
directorySizeIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.4.2 | Recover: The Directory Contains Too Many Files And Subdirectories |
nasHyperMetroFileSystemIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.47.1 | File System Data Is Incomplete |
nasHyperMetroFileSystemIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.47.2 | Recover: File System Data Is Incomplete |
fileSystemIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.69.1 | File System Is Faulty |
fileSystemIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.40.69.2 | Recover: File System Is Faulty |
systemComponentAnomaly-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.447.2.1 | A Component In The System Is Abnormal |
systemComponentAnomaly-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.447.2.2 | Recover: A Component In The System Is Abnormal |
writeProtectionIsEnabledForSomeFileSystemsLUNsOrSpaceThatStoresHistoricalPerformanceData-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.447.301.1 | Write Protection Is Enabled For Some File Systems, LUNs, Or Space That Stores Historical Performance Data |
writeProtectionIsEnabledForSomeFileSystemsLUNsOrSpaceThatStoresHistoricalPerformanceData-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.447.301.2 | Recover: Write Protection Is Enabled For Some File Systems, LUNs, Or Space That Stores Historical Performance Data |
cPUQuotaExceeded-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.49.18.1 | CPU Quota Exceeded |
cPUQuotaExceeded-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.49.18.2 | Recover: CPU Quota Exceeded |
eventAmountReachUpLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.49.4.1 | The Space That Stores Event Logs Is To Be Used Up |
eventAmountReachUpLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.49.4.2 | Recover: The Space That Stores Event Logs Is To Be Used Up |
trapTestAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.49.65534.1 | Trap Test Alarm |
trapTestAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.49.65534.2 | Recover: Trap Test Alarm |
storageUnitIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50000.1.1 | A Storage Unit Is Disconnected |
storageUnitIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50000.1.2 | Recover: A Storage Unit Is Disconnected |
storageUnitInaccessible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50000.2.1 | Failed To Access The Storage Unit |
storageUnitInaccessible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50000.2.2 | Recover: Failed To Access The Storage Unit |
theCapacityOfAStorageUnitInAStoragePoolIsInsufficient-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50000.3.1 | The Capacity Of A Storage Unit In A Storage Pool Is Insufficient |
theCapacityOfAStorageUnitInAStoragePoolIsInsufficient-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50000.3.2 | Recover: The Capacity Of A Storage Unit In A Storage Pool Is Insufficient |
insufficientRepositorySpace-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50001.1.1 | Insufficient Repository Space |
insufficientRepositorySpace-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50001.1.2 | Recover: Insufficient Repository Space |
repositoryUsageExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50001.2.1 | Repository Usage Exceeds The Threshold |
repositoryUsageExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50001.2.2 | Recover: Repository Usage Exceeds The Threshold |
theNumberOfTasksReachesTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50011.1.1 | The Number Of Tasks Reaches The Threshold |
theNumberOfTasksReachesTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50011.1.2 | Recover: The Number Of Tasks Reaches The Threshold |
theNumberOfTasksReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50011.2.1 | The Number Of Tasks Reaches The Upper Limit |
theNumberOfTasksReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50011.2.2 | Recover: The Number Of Tasks Reaches The Upper Limit |
theNumberOfBackupImagesIsAboutToReachTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50012.5.1 | The Number Of Backup Images Is About To Reach The Upper Limit Supported By The System |
theNumberOfBackupImagesIsAboutToReachTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50012.5.2 | Recover: The Number Of Backup Images Is About To Reach The Upper Limit Supported By The System |
nTPFailedToSynchronizeTime-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50029.1.1 | NTP Failed To Synchronize Time |
nTPFailedToSynchronizeTime-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.50029.1.2 | Recover: NTP Failed To Synchronize Time |
incompatibleHardwareOfTheSpareController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.558.17.1 | Incompatible Hardware Of The Spare Controller |
incompatibleHardwareOfTheSpareController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.558.17.2 | Recover: Incompatible Hardware Of The Spare Controller |
ctrlenclFirmwareIncompatible-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.558.7.1 | The Hardware Version Of The Controller Enclosure Or Smart Disk Enclosure Is Incompatible With Storage System Software |
ctrlenclFirmwareIncompatible-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.558.7.2 | Recover: The Hardware Version Of The Controller Enclosure Or Smart Disk Enclosure Is Incompatible With Storage System Software |
dMEIQFailedToConnectToTheRemoteServer-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57435.4.1 | DME IQ Failed To Connect To The Remote Server |
dMEIQFailedToConnectToTheRemoteServer-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57435.4.2 | Recover: DME IQ Failed To Connect To The Remote Server |
drStarIsInvalid-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57508.2.1 | DR Star Is Invalid |
drStarIsInvalid-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57508.2.2 | Recover: DR Star Is Invalid |
aFileSystemMigrationTaskIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.5.1 | A File System Migration Task Is Faulty |
aFileSystemMigrationTaskIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.5.2 | Recover: A File System Migration Task Is Faulty |
theNumberOfSynchronizationTimesOfTheFileSystemMigrationTaskHasReachedTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.6.1 | The Number Of Synchronization Times Of The File System Migration Task Has Reached The Upper Limit |
theNumberOfSynchronizationTimesOfTheFileSystemMigrationTaskHasReachedTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.6.2 | Recover: The Number Of Synchronization Times Of The File System Migration Task Has Reached The Upper Limit |
theNASMigrationLinkIsDisconnectedProactively-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.7.1 | The NAS Migration Link Is Disconnected Proactively |
theNASMigrationLinkIsDisconnectedProactively-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.7.2 | Recover: The NAS Migration Link Is Disconnected Proactively |
thereIsNoFreeSpaceInTheLogFileSystem-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.8.1 | There Is No Free Space In The Log File System |
thereIsNoFreeSpaceInTheLogFileSystem-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57802.8.2 | Recover: There Is No Free Space In The Log File System |
failedToStartTheContainerServiceOnTheController-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57884.6.1 | Failed To Start The Container Service On The Controller |
failedToStartTheContainerServiceOnTheController-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57884.6.2 | Recover: Failed To Start The Container Service On The Controller |
containerRootDirectoryIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57884.8.1 | Container Root Directory Is Faulty |
containerRootDirectoryIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57884.8.2 | Recover: Container Root Directory Is Faulty |
theContainerServiceProcessOnTheControllerIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57884.9.1 | The Container Service Process On The Controller Is Abnormal |
theContainerServiceProcessOnTheControllerIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57884.9.2 | Recover: The Container Service Process On The Controller Is Abnormal |
failedToActivateTheComponent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57885.1.1 | Failed To Activate The Component |
failedToActivateTheComponent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57885.1.2 | Recover: Failed To Activate The Component |
failedToUninstallTheComponent-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57885.2.1 | Failed To Uninstall The Component |
failedToUninstallTheComponent-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57885.2.2 | Recover: Failed To Uninstall The Component |
podIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57886.1.1 | Pod Is Abnormal |
podIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57886.1.2 | Recover: Pod Is Abnormal |
theContainerPodDirectoryIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57886.5.1 | The Container Pod Directory Is Faulty |
theContainerPodDirectoryIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.57886.5.2 | Recover: The Container Pod Directory Is Faulty |
theLinkEstablishmentBetweenTheHostAndArrayIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.17.1 | The Link Establishment Between The Host And Array Is Abnormal |
theLinkEstablishmentBetweenTheHostAndArrayIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.17.2 | Recover: The Link Establishment Between The Host And Array Is Abnormal |
initiatorExceedLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.20.1 | Number Of Initiators Connected To A Port Exceeds The Upper Limit |
initiatorExceedLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.20.2 | Recover: Number Of Initiators Connected To A Port Exceeds The Upper Limit |
linkIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4103.1 | The Link Between A Host And The Storage Array Is Disconnected |
linkIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4103.2 | Recover: The Link Between A Host And The Storage Array Is Disconnected |
failedToEstablishALinkBetweenTheHostAndDiskArray-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4104.1 | Failed To Establish A Link Between The Host And Disk Array |
failedToEstablishALinkBetweenTheHostAndDiskArray-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4104.2 | Recover: Failed To Establish A Link Between The Host And Disk Array |
initiatorsAssociatedWithMultipleHostsRepeat-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4106.1 | Initiators With The Same NVMe Host ID Exist On Different Hosts |
initiatorsAssociatedWithMultipleHostsRepeat-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4106.2 | Recover: Initiators With The Same NVMe Host ID Exist On Different Hosts |
hostHasInitiatorsWithDifferentNvmeHostIds-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4107.1 | Initiators With Different NVMe Host IDs Exist On The Same Host |
hostHasInitiatorsWithDifferentNvmeHostIds-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.4107.2 | Recover: Initiators With Different NVMe Host IDs Exist On The Same Host |
numberOfInitiatorConnectionsOnAPortExceedsTheSystemLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.48.1 | Number Of Initiator Connections On A Port Exceeds The System Limit |
numberOfInitiatorConnectionsOnAPortExceedsTheSystemLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.48.2 | Recover: Number Of Initiator Connections On A Port Exceeds The System Limit |
theNumberOfIntermittentDisconnectionsOfTheLinkWhereTheInitiatorResidesExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.6.1 | The Number Of Intermittent Disconnections Of The Link Where The Initiator Resides Exceeds The Threshold |
theNumberOfIntermittentDisconnectionsOfTheLinkWhereTheInitiatorResidesExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.580.6.2 | Recover: The Number Of Intermittent Disconnections Of The Link Where The Initiator Resides Exceeds The Threshold |
theNumberOfIntermittentDisconnectionsOfTheLinkWhereThePortIsLocatedExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.100.1 | The Number Of Intermittent Disconnections Of The Link Where The Port Is Located Exceeds The Threshold |
theNumberOfIntermittentDisconnectionsOfTheLinkWhereThePortIsLocatedExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.100.2 | Recover: The Number Of Intermittent Disconnections Of The Link Where The Port Is Located Exceeds The Threshold |
expansionPortIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.12.1 | Expansion Port Is Faulty |
expansionPortIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.12.2 | Recover: Expansion Port Is Faulty |
expansionPortIsolated-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.16.1 | The Expansion Port Is Isolated |
expansionPortIsolated-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.16.2 | Recover: The Expansion Port Is Isolated |
portIsWorkingInHalfDuplexMode-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.17.1 | Network Port Is Working In HalfDuplex Mode |
portIsWorkingInHalfDuplexMode-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.17.2 | Recover: Network Port Is Working In HalfDuplex Mode |
linkIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.171.1 | The RDMA Link Between Nodes Is Abnormal |
linkIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.171.2 | Recover: The RDMA Link Between Nodes Is Abnormal |
expansionPortIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.2.1 | Expansion Port Link Down |
expansionPortIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.2.2 | Recover: Expansion Port Link Down |
portHasTooManyBitErrors-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.21.1 | Port Has Too Many Bit Errors |
portHasTooManyBitErrors-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.21.2 | Recover: Port Has Too Many Bit Errors |
rateIsSmallerThanAllowedMaximum-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.29.1 | Port Negotiated Rate Is Smaller Than The Allowed Maximum |
rateIsSmallerThanAllowedMaximum-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.29.2 | Recover: Port Negotiated Rate Is Smaller Than The Allowed Maximum |
portIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.4.1 | A Port Is Disconnected |
portIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.4.2 | Recover: A Port Is Disconnected |
manageNetworkPortIsDisconnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.49.1 | Management Network Port Is Disconnected |
manageNetworkPortIsDisconnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.49.2 | Recover: Management Network Port Is Disconnected |
theCableIsIncorrectlyConnectedToAPort-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.57.1 | The Cable Is Incorrectly Connected To A Port |
theCableIsIncorrectlyConnectedToAPort-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.57.2 | Recover: The Cable Is Incorrectly Connected To A Port |
theCableBetweenTwoPortsIsIncorrectlyConnected1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.58.1 | The Cable Between Two Ports Is Incorrectly Connected |
theCableBetweenTwoPortsIsIncorrectlyConnected1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.58.2 | Recover: The Cable Between Two Ports Is Incorrectly Connected |
theCableBetweenTwoPortsIsNotConnectedAccordingToTheStandardNetwork1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.59.1 | The Cable Between Two Ports Is Not Connected According To The Standard Network |
theCableBetweenTwoPortsIsNotConnectedAccordingToTheStandardNetwork1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.59.2 | Recover: The Cable Between Two Ports Is Not Connected According To The Standard Network |
expansionPortPartiallyDamaged-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.6.1 | Expansion Port Partially Damaged |
expansionPortPartiallyDamaged-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.6.2 | Recover: Expansion Port Partially Damaged |
theCableIsNotConnectedToAPort-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.60.1 | The Cable Is Not Connected To A Port |
theCableIsNotConnectedToAPort-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.60.2 | Recover: The Cable Is Not Connected To A Port |
theCableBetweenTwoPortsIsNotConnected1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.61.1 | The Cable Between Two Ports Is Not Connected |
theCableBetweenTwoPortsIsNotConnected1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.61.2 | Recover: The Cable Between Two Ports Is Not Connected |
cableLengthError-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.62.1 | Cable Length Does Not Meet Specifications |
cableLengthError-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.62.2 | Recover: Cable Length Does Not Meet Specifications |
theRDMALinksBetweenNodesAreAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.66.1 | The RDMA Links Between Nodes Are Abnormal |
theRDMALinksBetweenNodesAreAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.66.2 | Recover: The RDMA Links Between Nodes Are Abnormal |
manageNetworkPortIsDisconnected1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.73.1 | Management Network Port Is Disconnected |
manageNetworkPortIsDisconnected1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.73.2 | Recover: Management Network Port Is Disconnected |
theCableBetweenTwoPortsIsIncorrectlyConnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.74.1 | The Cable Between Two Ports Is Incorrectly Connected |
theCableBetweenTwoPortsIsIncorrectlyConnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.74.2 | Recover: The Cable Between Two Ports Is Incorrectly Connected |
theCableBetweenTwoPortsIsNotConnectedAccordingToTheStandardNetwork-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.75.1 | The Cable Between Two Ports Is Not Connected According To The Standard Network |
theCableBetweenTwoPortsIsNotConnectedAccordingToTheStandardNetwork-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.75.2 | Recover: The Cable Between Two Ports Is Not Connected According To The Standard Network |
theCableBetweenTwoPortsIsNotConnected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.76.1 | The Cable Between Two Ports Is Not Connected |
theCableBetweenTwoPortsIsNotConnected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.76.2 | Recover: The Cable Between Two Ports Is Not Connected |
theHeartbeatLinksBetweenControllersInTheControllerEnclosureAreAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.77.1 | The Heartbeat Links Between Controllers In The Controller Enclosure Are Abnormal |
theHeartbeatLinksBetweenControllersInTheControllerEnclosureAreAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.77.2 | Recover: The Heartbeat Links Between Controllers In The Controller Enclosure Are Abnormal |
theNetworkingOfTheDiskEnclosureDoesNotMeetTheRequirementsOfTheEnclosureLevelRedundancyPolicy-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.78.1 | The Networking Of The Disk Enclosure Does Not Meet The Requirements Of The EnclosureLevel Redundancy Policy |
theNetworkingOfTheDiskEnclosureDoesNotMeetTheRequirementsOfTheEnclosureLevelRedundancyPolicy-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.78.2 | Recover: The Networking Of The Disk Enclosure Does Not Meet The Requirements Of The EnclosureLevel Redundancy Policy |
failedToSynchronizeThePortRouteConfigurationToTheSecondaryVStoreOfTheVStorePair-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.85.1 | Failed To Synchronize The Port Route Configuration To The Secondary VStore Of The VStore Pair |
failedToSynchronizeThePortRouteConfigurationToTheSecondaryVStoreOfTheVStorePair-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.85.2 | Recover: Failed To Synchronize The Port Route Configuration To The Secondary VStore Of The VStore Pair |
theManagementNetworkIsNotRedundant-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.92.1 | The Management Network Is Not Redundant |
theManagementNetworkIsNotRedundant-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6.92.2 | Recover: The Management Network Is Not Redundant |
cCDBClusterBackupFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.60002.13335.1 | CCDB Cluster Backup Failed |
cCDBClusterBackupFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.60002.13335.2 | Recover: CCDB Cluster Backup Failed |
ccdbBackupFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.60002.13341.1 | CCDB Database Backup Failed In The HyperScale Cluster |
ccdbBackupFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.60002.13341.2 | Recover: CCDB Database Backup Failed In The HyperScale Cluster |
updateArbtrationFail-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.60002.37.1 | Failed To Update CCDB Arbitration Information |
updateArbtrationFail-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.60002.37.2 | Recover: Failed To Update CCDB Arbitration Information |
smartDedupeAndSmartCompressionAccelerationModuleIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6004.22.1 | Failed To Connect The Data Reduction Acceleration Module |
smartDedupeAndSmartCompressionAccelerationModuleIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.6004.22.2 | Recover: Failed To Connect The Data Reduction Acceleration Module |
smartMoveDomainIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.1.1 | SmartMove Domain Is Faulty |
smartMoveDomainIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.1.2 | Recover: SmartMove Domain Is Faulty |
smartMovePairInvalid-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.10.1 | SmartMove Pair Invalid |
smartMovePairInvalid-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.10.2 | Recover: SmartMove Pair Invalid |
smartMoveFileSystemPairIsDisconnectedUnexpectedly-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.11.1 | SmartMove File System Pair Is Disconnected Unexpectedly |
smartMoveFileSystemPairIsDisconnectedUnexpectedly-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.11.2 | Recover: SmartMove File System Pair Is Disconnected Unexpectedly |
smartMoveFileSystemPairConfigurationsAreDisconnectedUnexpectedly-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.12.1 | SmartMove File System Pair Configurations Are Disconnected Unexpectedly |
smartMoveFileSystemPairConfigurationsAreDisconnectedUnexpectedly-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.12.2 | Recover: SmartMove File System Pair Configurations Are Disconnected Unexpectedly |
smartMoveDomainIsRecovery-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.14.1 | SmartMove Domain Is In The Recovering State For A Long Time |
smartMoveDomainIsRecovery-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.14.2 | Recover: SmartMove Domain Is In The Recovering State For A Long Time |
smartMoveDomainIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.2.1 | SmartMove Domain Is Unavailable |
smartMoveDomainIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.2.2 | Recover: SmartMove Domain Is Unavailable |
smartMoveVStorePairConfigurationsAreDisconnectedUnexpectedly-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.3.1 | SmartMove VStore Pair Configurations Are Disconnected Unexpectedly |
smartMoveVStorePairConfigurationsAreDisconnectedUnexpectedly-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.3.2 | Recover: SmartMove VStore Pair Configurations Are Disconnected Unexpectedly |
smartMoveVStorePairIsInvalid-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.4.1 | SmartMove VStore Pair Is Invalid |
smartMoveVStorePairIsInvalid-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.4.2 | Recover: SmartMove VStore Pair Is Invalid |
smartMoveFileSystemPairIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.6.1 | SmartMove File System Pair Is Unavailable |
smartMoveFileSystemPairIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.6.2 | Recover: SmartMove File System Pair Is Unavailable |
smartMovePairFault-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.9.1 | SmartMove Pair Fault |
smartMovePairFault-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.633.9.2 | Recover: SmartMove Pair Fault |
cloudVxLANNetworkConfigurationsDoNotMeetRedundancyRequirements-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.678.1.1 | CloudVxLAN Network Configurations Do Not Meet Redundancy Requirements |
cloudVxLANNetworkConfigurationsDoNotMeetRedundancyRequirements-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.678.1.2 | Recover: CloudVxLAN Network Configurations Do Not Meet Redundancy Requirements |
boxCpldComponentIsFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.1.1 | A CPLD Module In The Box Is Faulty |
boxCpldComponentIsFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.1.2 | Recover: A CPLD Module In The Box Is Faulty |
riserCardTypeIsIllegal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.90.1 | Invalid Box Type |
riserCardTypeIsIllegal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.90.2 | Recover: Invalid Box Type |
riserCardIsRemoved-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.91.1 | The Box Is Removed |
riserCardIsRemoved-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.91.2 | Recover: The Box Is Removed |
riserCardTypeIsUnrecognizable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.92.1 | The Box Type Cannot Be Identified |
riserCardTypeIsUnrecognizable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.756.92.2 | Recover: The Box Type Cannot Be Identified |
smartmobilityExclusionWithAntiRansomware-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8001.14.1 | The SmartMobility Feature Is Exclusive With The Ransomware Protection Feature And Is Enabled For The File System |
smartmobilityExclusionWithAntiRansomware-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8001.14.2 | Recover: The SmartMobility Feature Is Exclusive With The Ransomware Protection Feature And Is Enabled For The File System |
failedToPerformRollbackUsingTheFileSystemSnapshot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.10.1 | Failed To Perform Rollback Using The File System Snapshot |
failedToPerformRollbackUsingTheFileSystemSnapshot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.10.2 | Recover: Failed To Perform Rollback Using The File System Snapshot |
resourceIsInfected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.15.1 | Copy Infected By Ransomware |
resourceIsInfected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.15.2 | Recover: Copy Infected By Ransomware |
failedToCancelApplyingTheFileNameExtensionFilteringRuleAssociatedWithTheVStore-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.16.1 | Failed To Cancel Applying The File Name Extension Filtering Rule Associated With The VStore |
failedToCancelApplyingTheFileNameExtensionFilteringRuleAssociatedWithTheVStore-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.16.2 | Recover: Failed To Cancel Applying The File Name Extension Filtering Rule Associated With The VStore |
failedToApplyTheFileNameExtensionFilteringRuleAssociatedWithTheVStore-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.17.1 | Failed To Apply The File Name Extension Filtering Rule Associated With The VStore |
failedToApplyTheFileNameExtensionFilteringRuleAssociatedWithTheVStore-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.17.2 | Recover: Failed To Apply The File Name Extension Filtering Rule Associated With The VStore |
nasInfected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.18.1 | File System Of A VStore Infected By Ransomware |
nasInfected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.18.2 | Recover: File System Of A VStore Infected By Ransomware |
intelligentDetectionAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.19.1 | An Exception Occurred During Intelligent Ransomware Detection |
intelligentDetectionAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.19.2 | Recover: An Exception Occurred During Intelligent Ransomware Detection |
failedToDeleteAFileSystemShare-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.2.1 | Failed To Delete A File System Share |
failedToDeleteAFileSystemShare-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.2.2 | Recover: Failed To Delete A File System Share |
theNumberOfIndexJobsReachesTheUpperLimit-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.20.1 | The Number Of Index Jobs Reaches The Upper Limit |
theNumberOfIndexJobsReachesTheUpperLimit-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.20.2 | Recover: The Number Of Index Jobs Reaches The Upper Limit |
failedToCreateACopyIndex-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.21.1 | Failed To Create A Copy Index |
failedToCreateACopyIndex-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.21.2 | Recover: Failed To Create A Copy Index |
fileNameExtensionFilteringRulesCannotBeConfiguredForTheSecondaryFileSystemOfTheVStore-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.30.1 | File Name Extension Filtering Rules Cannot Be Configured For The Secondary File System Of The VStore |
fileNameExtensionFilteringRulesCannotBeConfiguredForTheSecondaryFileSystemOfTheVStore-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.30.2 | Recover: File Name Extension Filtering Rules Cannot Be Configured For The Secondary File System Of The VStore |
failedToDeployHoneyfiles-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.38.1 | Failed To Deploy Honeyfiles |
failedToDeployHoneyfiles-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.38.2 | Recover: Failed To Deploy Honeyfiles |
fileSystemShareConfigurationIsAbnormal-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.39.1 | File System Share Configuration Is Abnormal |
fileSystemShareConfigurationIsAbnormal-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.39.2 | Recover: File System Share Configuration Is Abnormal |
antiRansomwareDetectFailedDueToSnapshotNotExists-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.40.1 | An Exception Occurred During Intelligent Ransomware Detection Because The Snapshot Does Not Exist |
antiRansomwareDetectFailedDueToSnapshotNotExists-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.40.2 | Recover: An Exception Occurred During Intelligent Ransomware Detection Because The Snapshot Does Not Exist |
lunInfected-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.43.1 | Ransomware Infection Is Detected In A LUN Of The VStore |
lunInfected-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.43.2 | Recover: Ransomware Infection Is Detected In A LUN Of The VStore |
enableRansomwareFileInterceptionFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.49.1 | An Exception Occurred When Ransomware File Interception Was Being Enabled For The VStore |
enableRansomwareFileInterceptionFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.49.2 | Recover: An Exception Occurred When Ransomware File Interception Was Being Enabled For The VStore |
disableRansomwareFileInterceptionFaulty-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.50.1 | An Exception Occurred When Ransomware File Interception Was Being Disabled For The VStore |
disableRansomwareFileInterceptionFaulty-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.50.2 | Recover: An Exception Occurred When Ransomware File Interception Was Being Disabled For The VStore |
failedToDeleteTheFileSystemSnapshot-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.8.1 | Failed To Delete The File System Snapshot |
failedToDeleteTheFileSystemSnapshot-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.8.2 | Recover: Failed To Delete The File System Snapshot |
failedToDeleteAFileSystem-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.9.1 | Failed To Delete A File System |
failedToDeleteAFileSystem-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8002.9.2 | Recover: Failed To Delete A File System |
jobFailed-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8003.13.1 | Job Failed |
jobFailed-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8003.13.2 | Recover: Job Failed |
memoryUsageExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.10.1 | Memory Usage Exceeds The Threshold |
memoryUsageExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.10.2 | Recover: Memory Usage Exceeds The Threshold |
containerRunsAbnormally-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.11.1 | The Container Runs Abnormally |
containerRunsAbnormally-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.11.2 | Recover: The Container Runs Abnormally |
cpuUsageExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.12.1 | The CPU Usage Exceeds The Threshold |
cpuUsageExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.12.2 | Recover: The CPU Usage Exceeds The Threshold |
builtinPersistentVolumeCapacityUsageExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.13.1 | Builtin Persistent Volume Capacity Usage Exceeds The Threshold |
builtinPersistentVolumeCapacityUsageExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.13.2 | Recover: Builtin Persistent Volume Capacity Usage Exceeds The Threshold |
abnormalLogLevel-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.9.1 | Abnormal Log Level |
abnormalLogLevel-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.8005.9.2 | Recover: Abnormal Log Level |
warnAvgCpuUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.1.1 | Average CPU Utilization Exceeded The Threshold |
warnAvgCpuUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.1.2 | Recover: Average CPU Utilization Exceeded The Threshold |
criticalAvgIORespThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.11.1 | Average IO Response Time Exceeded The Threshold |
criticalAvgIORespThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.11.2 | Recover: Average IO Response Time Exceeded The Threshold |
criticalTimeSinceSyncThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.14.1 | Time Since Last Synchronization Exceeded The Threshold |
criticalTimeSinceSyncThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.14.2 | Recover: Time Since Last Synchronization Exceeded The Threshold |
majorAvgCpuUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.15.1 | Average CPU Utilization Exceeded The Threshold |
majorAvgCpuUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.15.2 | Recover: Average CPU Utilization Exceeded The Threshold |
majorUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.16.1 | Utilization Exceeded The Threshold |
majorUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.16.2 | Recover: Utilization Exceeded The Threshold |
majorAvgIORespTimeThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.18.1 | Average IO Response Time Exceeded The Threshold |
majorAvgIORespTimeThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.18.2 | Recover: Average IO Response Time Exceeded The Threshold |
warnUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.2.1 | Utilization Exceeded The Threshold |
warnUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.2.2 | Recover: Utilization Exceeded The Threshold |
majorTimeSinceSyncThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.21.1 | Time Since Last Synchronization Exceeded The Threshold |
majorTimeSinceSyncThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.21.2 | Recover: Time Since Last Synchronization Exceeded The Threshold |
exceedThresholdWarning-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.308.1 | The Performance Indicator Exceeded The Threshold |
exceedThresholdWarning-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.308.2 | Recover: The Performance Indicator Exceeded The Threshold |
exceedThresholdMajor-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.309.1 | The Performance Indicator Exceeded The Threshold |
exceedThresholdMajor-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.309.2 | Recover: The Performance Indicator Exceeded The Threshold |
exceedThresholdCritical-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.310.1 | The Performance Indicator Exceeded The Threshold |
exceedThresholdCritical-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.310.2 | Recover: The Performance Indicator Exceeded The Threshold |
warnMemberdiskUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.37.1 | The Average Usage Of Member Disks Exceeds The Threshold |
warnMemberdiskUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.37.2 | Recover: The Average Usage Of Member Disks Exceeds The Threshold |
majorMemberdiskUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.38.1 | The Average Usage Of Member Disks Exceeds The Threshold |
majorMemberdiskUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.38.2 | Recover: The Average Usage Of Member Disks Exceeds The Threshold |
criticalUsageThreshAlarm1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.39.1 | The Average Usage Of Member Disks Exceeds The Threshold |
criticalUsageThreshAlarm1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.39.2 | Recover: The Average Usage Of Member Disks Exceeds The Threshold |
warnAvgIORespTimeThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.4.1 | Average IO Response Time Exceeded The Threshold |
warnAvgIORespTimeThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.4.2 | Recover: Average IO Response Time Exceeded The Threshold |
theUnmapCommandBandwidthForWritingDataToDisksExceedsTheThreshold2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.40.1 | The Unmap Command Bandwidth For Writing Data To Disks Exceeds The Threshold |
theUnmapCommandBandwidthForWritingDataToDisksExceedsTheThreshold2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.40.2 | Recover: The Unmap Command Bandwidth For Writing Data To Disks Exceeds The Threshold |
theFullCopyCommandBandwidthOfWritingDataToDisksExceedsTheThreshold1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.41.1 | The Full Copy Command Bandwidth Of Writing Data To Disks Exceeds The Threshold |
theFullCopyCommandBandwidthOfWritingDataToDisksExceedsTheThreshold1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.41.2 | Recover: The Full Copy Command Bandwidth Of Writing Data To Disks Exceeds The Threshold |
theOdxCommandWriteBandwidthExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.42.1 | The Odx Command Write Bandwidth Exceeds The Threshold |
theOdxCommandWriteBandwidthExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.42.2 | Recover: The Odx Command Write Bandwidth Exceeds The Threshold |
theUnmapCommandBandwidthForWritingDataToDisksExceedsTheThreshold1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.43.1 | The Unmap Command Bandwidth For Writing Data To Disks Exceeds The Threshold |
theUnmapCommandBandwidthForWritingDataToDisksExceedsTheThreshold1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.43.2 | Recover: The Unmap Command Bandwidth For Writing Data To Disks Exceeds The Threshold |
theUnmapCommandBandwidthForWritingDataToDisksExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.44.1 | The Unmap Command Bandwidth For Writing Data To Disks Exceeds The Threshold |
theUnmapCommandBandwidthForWritingDataToDisksExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.44.2 | Recover: The Unmap Command Bandwidth For Writing Data To Disks Exceeds The Threshold |
theFullCopyCommandBandwidthOfWritingDataToDisksExceedsTheThreshold-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.45.1 | The Full Copy Command Bandwidth Of Writing Data To Disks Exceeds The Threshold |
theFullCopyCommandBandwidthOfWritingDataToDisksExceedsTheThreshold-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.45.2 | Recover: The Full Copy Command Bandwidth Of Writing Data To Disks Exceeds The Threshold |
theFullCopyCommandBandwidthOfWritingDataToDisksExceedsTheThreshold2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.46.1 | The Full Copy Command Bandwidth Of Writing Data To Disks Exceeds The Threshold |
theFullCopyCommandBandwidthOfWritingDataToDisksExceedsTheThreshold2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.46.2 | Recover: The Full Copy Command Bandwidth Of Writing Data To Disks Exceeds The Threshold |
theOdxCommandWriteBandwidthExceedsTheThreshold1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.47.1 | The Odx Command Write Bandwidth Exceeds The Threshold |
theOdxCommandWriteBandwidthExceedsTheThreshold1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.47.2 | Recover: The Odx Command Write Bandwidth Exceeds The Threshold |
theOdxCommandWriteBandwidthExceedsTheThreshold2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.48.1 | The Odx Command Write Bandwidth Exceeds The Threshold |
theOdxCommandWriteBandwidthExceedsTheThreshold2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.48.2 | Recover: The Odx Command Write Bandwidth Exceeds The Threshold |
dataOnTheSecondaryEndIsEarlierThanThatOnThePrimaryEnd2-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.49.1 | Data On The Secondary End Is Earlier Than That On The Primary End |
dataOnTheSecondaryEndIsEarlierThanThatOnThePrimaryEnd2-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.49.2 | Recover: Data On The Secondary End Is Earlier Than That On The Primary End |
dataOnTheSecondaryEndIsEarlierThanThatOnThePrimaryEnd1-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.50.1 | Data On The Secondary End Is Earlier Than That On The Primary End |
dataOnTheSecondaryEndIsEarlierThanThatOnThePrimaryEnd1-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.50.2 | Recover: Data On The Secondary End Is Earlier Than That On The Primary End |
dataOnTheSecondaryEndIsEarlierThanThatOnThePrimaryEnd-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.51.1 | Data On The Secondary End Is Earlier Than That On The Primary End |
dataOnTheSecondaryEndIsEarlierThanThatOnThePrimaryEnd-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.51.2 | Recover: Data On The Secondary End Is Earlier Than That On The Primary End |
fluctuationDetectionAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.52.1 | Fluctuation Detection Alarm |
fluctuationDetectionAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.52.2 | Recover: Fluctuation Detection Alarm |
warnTimeSinceLastSyncThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.7.1 | Time Since Last Synchronization Exceeded The Threshold |
warnTimeSinceLastSyncThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.7.2 | Recover: Time Since Last Synchronization Exceeded The Threshold |
criticalAvgCpuUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.8.1 | Average CPU Utilization Exceeded The Threshold |
criticalAvgCpuUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.8.2 | Recover: Average CPU Utilization Exceeded The Threshold |
criticalUsageThreshAlarm-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.9.1 | Utilization Exceeded The Threshold |
criticalUsageThreshAlarm-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.822.9.2 | Recover: Utilization Exceeded The Threshold |
theCAServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.1.1 | The CA Server Is Unavailable |
theCAServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.1.2 | Recover: The CA Server Is Unavailable |
sSOServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.10.1 | SSO Server Is Unavailable |
sSOServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.10.2 | Recover: SSO Server Is Unavailable |
theRADIUSServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.11.1 | The RADIUS Server Is Unavailable |
theRADIUSServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.11.2 | Recover: The RADIUS Server Is Unavailable |
serverLinkIsDown-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.12.1 | Server Link Is Down |
serverLinkIsDown-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.12.2 | Recover: Server Link Is Down |
serverIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.2.1 | Server Is Unavailable |
serverIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.2.2 | Recover: Server Is Unavailable |
theSMTPServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.3.1 | The SMTP Server Is Unavailable |
theSMTPServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.3.2 | Recover: The SMTP Server Is Unavailable |
syslogServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.4.1 | Syslog Server Is Unavailable |
syslogServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.4.2 | Recover: Syslog Server Is Unavailable |
alarmDumpServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.5.1 | Alarm Dump Server Is Unavailable |
alarmDumpServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.5.2 | Recover: Alarm Dump Server Is Unavailable |
performanceDumpServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.6.1 | Performance Dump Server Is Unavailable |
performanceDumpServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.6.2 | Recover: Performance Dump Server Is Unavailable |
lDAPServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.7.1 | LDAP Server Is Unavailable |
lDAPServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.7.2 | Recover: LDAP Server Is Unavailable |
keyFileBackupServerIsUnavailable-Fault
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.8.1 | Key File Backup Server Is Unavailable |
keyFileBackupServerIsUnavailable-Resume
| .1.3.6.1.4.1.2011.2.251.20.1.2.2.15.823.8.2 | Recover: Key File Backup Server Is Unavailable |
huawei 