| SNO |
Notification/OID |
Description |
Action |
| 1 |
unknownDomainAlert/1.3.6.1.4.1.19746.2.0.5000 |
During the upgrade procedure, the system could not determine the domain it joined: NT4, Windows 2000, or a newer Active Directory. |
If the system is joined to an NT4 domain, Data Domain recommends moving (joining) the system to a Windows 2000 or newer Active Directory domain, because NT4 domain support is being deprecated. If the system is already joined to a Windows 2000 or newer domain, contact Data Domain Support at https://mydatadomain.com to switch the authentication mode. |
| 2 |
nT4DomainAlert/1.3.6.1.4.1.19746.2.0.5001 |
During the upgrade procedure, the system determined that it joined an NT4 domain. |
If the system is joined to an NT4 domain, Data Domain recommends moving (joining) the system to a Windows 2000 or newer Active Directory domain because NT4 domain support is being deprecated. |
| 3 |
controllerUnreachableAlert/1.3.6.1.4.1.19746.2.0.5002 |
This event is specific to Global Deduplication Arrays (GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master. |
This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected.This event is specific to Global Deduplication Arrays
(GDAs) and is generated by the master controller when it fails to reach the worker controller for more than five minutes. If a worker controller becomes unreachable,the implication is that none of the worker controller interfaces can be ping-ed by the master.
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected. |
| 4 |
controllerIfaceUnreachableAlert/1.3.6.1.4.1.19746.2.0.5003 |
This event is specific to Global Deduplication Arrays (GDAs) and is generated by the master controller when it fails to reach the worker controller interface for more than five minutes. If an interface becomes unreachable, the implication is it cannot be ping-ed by the master controller or equivalent interface. |
1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected1. Check the network interface status on both controllers.
2. Check network connectivity between the master and worker controllers.
3. Make sure all cables are securely connected |
| 5 |
correctableECCLimitReached/1.3.6.1.4.1.19746.2.0.5004 |
The ECC limit has been reached for single-bit errors. |
Replace the failed DIMMs. For assistance,contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 6 |
uncorrectableECCerror/1.3.6.1.4.1.19746.2.0.5005 |
A multi-bit error that cannot be corrected by ECC has been detected on the system. |
Replace the failed DIMMs. For assistance,contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 7 |
legacyChassisTempWarning/1.3.6.1.4.1.19746.2.0.5006 |
The current temperature sensor reading exceeds the warning threshold. |
Monitor temperature readings. If the alert persists, check the ambient room temperature, and make sure the air flow is not blocked. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 8 |
legacyChassisTempCritical/1.3.6.1.4.1.19746.2.0.5007 |
The current temperature sensor reading exceeds critical threshold. |
Check the ambient room temperature, and make sure the air flow is not blocked. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 9 |
legacyPowerSupplyWarning/1.3.6.1.4.1.19746.2.0.5008 |
A power supply has failed, is unplugged, or is absent. |
Check the power supply cables and LED. If necessary, replace the power supply. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 10 |
legacyFanWarning/1.3.6.1.4.1.19746.2.0.5009 |
A fan has failed. |
Check all fans to determine if one is missing or has failed, and then replace that fan. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 11 |
powerSupplyWarning/1.3.6.1.4.1.19746.2.0.5010 |
A power supply has failed, is unplugged, or is absent. |
Check the power supply cables and LED. If necessary, replace the power supply. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 12 |
fanWarning/1.3.6.1.4.1.19746.2.0.5011 |
A fan has failed or is missing. |
Check all fans to determine if one is missing or has failed, and then replace that fan. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 13 |
voltageWarning/1.3.6.1.4.1.19746.2.0.5012 |
A voltage sensor reading exceeds the warning threshold. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 14 |
powerWarning/1.3.6.1.4.1.19746.2.0.5013 |
The current power consumption reading exceeds the warning threshold. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 15 |
correctECCWarning/1.3.6.1.4.1.19746.2.0.5014 |
ECC (error-correcting code) correctable memory errors exceed the warning threshold. |
These memory errors should be automatically corrected by the system. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 16 |
nonThreshWarning/1.3.6.1.4.1.19746.2.0.5015 |
The current non-threshold type sensor reading exceeds the warning threshold. |
Check the specific alert message for the recommended action. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 17 |
processorWarning/1.3.6.1.4.1.19746.2.0.5016 |
An alert has been generated by the processor thermal sensor. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 18 |
powerUnitWarning/1.3.6.1.4.1.19746.2.0.5017 |
This event is expected after power off, power cycle, or an AC power loss event. |
If this alert was unexpected, check the power cords and AC power. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 19 |
unCorrectECCWarning/1.3.6.1.4.1.19746.2.0.5018 |
ECC (error-correcting code) uncorrectable memory errors exceed the warning threshold. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 20 |
chassisSensorWarning/1.3.6.1.4.1.19746.2.0.5019 |
There is an other chassis sensor alert. |
Check the specific alert message for the recommended action. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 21 |
chassisSensorCritical/1.3.6.1.4.1.19746.2.0.5020 |
The current sensor reading or state exceeds the critical condition. |
1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check the specific alert message for information.
2. Monitor temperature readings.
3. Check ambient room temperature and make sure air flow is not blocked.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 22 |
chassisTempWarning/1.3.6.1.4.1.19746.2.0.5021 |
The current temperature sensor reading exceeds the warning threshold. |
Monitor temperature readings. If the alert persists, check the ambient room temperature and for blocked air flow. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 23 |
chassisTempCritical/1.3.6.1.4.1.19746.2.0.5022 |
The current temperature sensor reading exceeds the critical threshold. |
Check the ambient room temperature and for blocked air flow. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 24 |
cPUFailureWarning/1.3.6.1.4.1.19746.2.0.5023 |
The Data Domain OS has detected a CPU fault. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 25 |
legacyBMCHangCritical/1.3.6.1.4.1.19746.2.0.5024 |
While BMC is unresponsive, environmental monitoring and remote access via IPMI is not operational. This could mask serious problems such as overheating. |
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC. Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 26 |
bMCHangCritical/1.3.6.1.4.1.19746.2.0.5025 |
While BMC is unresponsive, environmental monitoring and remote access via IPMI is not operational. This could mask serious problems such as overheating. |
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Use the CLI or Enterprise Manager to check fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC.Wait until all LEDs are off. Reinsert the power cables and then power the system up. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
|
| 27 |
abnormalShutdown/1.3.6.1.4.1.19746.2.0.5026 |
The system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdownThe system was shut down improperly. The system must be shut down by one of the following methods:
1. IPMI chassis control command
2. power button
3. OS shutdown |
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
This alert is expected after the loss of AC (main power). If this alert was unexpected, and/or this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
|
| 28 |
tooManyRelaunches/1.3.6.1.4.1.19746.2.0.5027 |
The file system process has failed to restart multiple times. Backup and restore services are unavailable. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 29 |
filesystemProblem/1.3.6.1.4.1.19746.2.0.5028 |
A problem is preventing the file system from running. This typically involves unavailable storage. |
Check the disk shelf cabling. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 30 |
dDGCFailedInShutdown/1.3.6.1.4.1.19746.2.0.5029 |
A Data Domain Global Compression (DDGC) process failed during shutdown. |
None required. |
| 31 |
dDFSFailedInShutdown/1.3.6.1.4.1.19746.2.0.5030 |
The file system failed to shut down cleanly. This can leave data in NVRAM that would normally be flushed to disk. An unclean shutdown state prevents some actions from being performed, such as an upgrade. |
Re-enable the file system, and try shutting it down in proper sequence. The condition is cleared if the second shutdown completes cleanly. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 32 |
dDFSNotCleanlyShutdown/1.3.6.1.4.1.19746.2.0.5031 |
The Data Domain file system did not shut down cleanly because of Data Domain Global Compression (DDGC). |
None required. |
| 33 |
dDGCFailed1/1.3.6.1.4.1.19746.2.0.5032 |
A Data Domain Global Compression (DDGC) process failed. The Data Domain file system is being restarted. |
None required. |
| 34 |
dDGCFailed2/1.3.6.1.4.1.19746.2.0.5033 |
A Data Domain Global Compression (DDGC) process failed. The system is being disabled. |
None required. |
| 35 |
dDFSNoHeartbeat/1.3.6.1.4.1.19746.2.0.5034 |
The file system hung and failed to respond to heartbeats, so it was restarted. |
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
file system restarts successfully.
|
| 36 |
dDGCFailed3/1.3.6.1.4.1.19746.2.0.5035 |
A Data Domain Global Compression (DDGC) process failed during shutdown. The Data Domain file system is being restarted. |
None required. |
| 37 |
dDFSDiedAfterReboot/1.3.6.1.4.1.19746.2.0.5036 |
The file system failed to start immediately after system reboot. |
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully. |
| 38 |
dDFSDied/1.3.6.1.4.1.19746.2.0.5037 |
The file system process failed and is restarting. |
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
Contact your support provider or Data Domain Support at https://mydatadomain.com for diagnosis of the cause of failure. No further action is required if
the file system restarts successfully.
|
| 39 |
dDFSRebooted/1.3.6.1.4.1.19746.2.0.5038 |
Notification alert that system was rebooted. |
None required. |
| 40 |
dDFSRebootedDisabled/1.3.6.1.4.1.19746.2.0.5039 |
Notification alert sent during system startup after system reboot. The system is rebooted with the file system in disabled state. |
None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details.None required unless you are enabling the file system. In that case, run the filesys enable command option. See the DD OS Command Reference Guide for
details. |
| 41 |
indexRebuildComplete/1.3.6.1.4.1.19746.2.0.5040 |
Informational alert indicating the index rebuild is complete. |
None required. |
| 42 |
historicalDatabaseRecoverError/1.3.6.1.4.1.19746.2.0.5041 |
The system successfully created a new historical database but the historical database recovery failed.All historical data has been lost. Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head swap processing if recovery from creating the new head primary historical database from the shelf database files fails. |
Contact your support provider or Data Domain Support at https://mydatadomain.comto debug this problem and recover lost data. |
| 43 |
historicalDatabaseBackupError/1.3.6.1.4.1.19746.2.0.5042 |
Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning.Historical database backup failed. If the primary historical database fails without a recent backup present, some or all of the historical data may be lost
when the primary historical database is restored from its backup and log files. Data in the historical database is used for some system reports, but is not
required for proper system functioning. |
If this alert is issued two consecutive days,contact your support provider or Data Domain Support at https://mydatadomain.comto debug the database. |
| 44 |
historicalDatabaseUpgradeError/1.3.6.1.4.1.19746.2.0.5043 |
Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system.Historical database upgrade failed during software upgrade. New historical data fields are not saved. Some user interface reports may be unavailable or
missing data. Otherwise, this failure should not affect the system. |
Contact your support provider or Data Domain Support at https://mydatadomain.com to debug the database. |
| 45 |
historicalDatabasePruneError/1.3.6.1.4.1.19746.2.0.5044 |
Historical database pruning failed. Pruning ensures the database does not consume more than the allocated disk space. |
If this alert is issued two consecutive days, contact your support provider or Data Domain Support at https://mydatadomain.comto debug the problem. |
| 46 |
noHistoricalDatabaseError/1.3.6.1.4.1.19746.2.0.5045 |
Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails.Historical database recovery failed. The system is running without historical database after failing to create a new one. All historical data has been lost.
Data in the historical database is used for some system reports, but is not required for proper system functioning. This failure may occur during the head
swap processing if recovery from creating the new head primary historical database from the shelf database files fails. |
To debug this problem and recover lost data, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 47 |
hDTFileTransferFailed/1.3.6.1.4.1.19746.2.0.5046 |
The system was unable to send a historical data update file to DDMS. |
Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check network connection and permissions between the DDMS and the Data Domain system. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com. |
| 48 |
hDTSystemError/1.3.6.1.4.1.19746.2.0.5047 |
A system error occurred while sending historical data to DDMS. |
Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check configuration and system status and message logs for an indication of the problem. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com. |
| 49 |
dIMMFailureAlert/1.3.6.1.4.1.19746.2.0.5048 |
A DIMM failure was detected. The Data Domain file system cannot be enabled. |
Replace the failed DIMM(s). |
| 50 |
memoryAlert/1.3.6.1.4.1.19746.2.0.5049 |
The current memory is less than configured. The Data Domain file system cannot be enabled. |
Check the DIMMs in the Data Domain system. Add new DIMMs and/or replace failed DIMMs, as required. |
| 51 |
portPathDisabled/1.3.6.1.4.1.19746.2.0.5050 |
Path not enabled, which may cause problems during a failover. |
Enable path. |
| 52 |
diskPathRedundancy/1.3.6.1.4.1.19746.2.0.5051 |
Only one path is recognized on a multipath configuration and only one HBA is connected. |
Verify storage cabling is connected correctly and HBA controllers are functional. |
| 53 |
missingPortConnection/1.3.6.1.4.1.19746.2.0.5052 |
A port and the attached storage have disappeared. |
Verify the connections to the port and external storage are intact. |
| 54 |
missingLunPath/1.3.6.1.4.1.19746.2.0.5053 |
The number of active paths to a LUN changed. |
If due to reconfiguration, verify the topology,and then disable and re-enable multipath monitoring to reset the monitoring. If not due to reconfiguration,verify the storage cabling is intact and that all pathsare connected. |
| 55 |
missingDiskPath/1.3.6.1.4.1.19746.2.0.5054 |
The number of active paths to a disk changed. |
If due to reconfiguration, verify the topology,and then disable and re-enable multipath monitoring to reset the monitoring. If not due to reconfiguration, verify the storage cabling is intact and that all paths are connected. |
| 56 |
missingEnclosurePath/1.3.6.1.4.1.19746.2.0.5055 |
The number of active paths to an enclosure changed. |
If due to reconfiguration, verify the topology,and then disable and re-enable multipath monitoring to reset the monitoring. If not due to reconfiguration,verify the storage cabling is intact and that all paths are connected. |
| 57 |
linkLoss/1.3.6.1.4.1.19746.2.0.5056 |
Link loss detected. |
Check network connectivity. |
| 58 |
linkOscillations/1.3.6.1.4.1.19746.2.0.5057 |
Link oscillations detected. |
Check network connectivity. |
| 59 |
linkConfiguration/1.3.6.1.4.1.19746.2.0.5058 |
Link configuration problem detected. |
Check network configuration. |
| 60 |
nvramWarning/1.3.6.1.4.1.19746.2.0.5059 |
The NVRAM battery is at low charge, so the Data Domain file system cannot be enabled. The battery is being charged, but may take up to three hours. When the battery is full, this alert will be cleared. |
Wait for the NVRAM alert to be cleared. If this issue persists, contact your support provider. |
| 61 |
nvramBatteryAlert/1.3.6.1.4.1.19746.2.0.5060 |
A battery on the NVRAM card is in discharged state and is not charging. |
Replace NVRAM card. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 62 |
nvramErrorAlert/1.3.6.1.4.1.19746.2.0.5061 |
NVRAM card has too many PCI or memory ECC errors. |
Replace NVRAM card. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 63 |
phyalert/1.3.6.1.4.1.19746.2.0.5062 |
Enclosure slot has been disabled. |
Replace the drive and enable the slot using the DD OS CLI. See the DD OS Command Reference Guide for details. |
| 64 |
replProgressThreshholdReached/1.3.6.1.4.1.19746.2.0.5063 |
Replication has not made recent progress. |
1. Check the network.
2. Check the replica file system.
3. Check the replication status to identify errors. Use the CLI or Enterprise Manager (GUI).
4. Check the messages file for more specific1. Check the network.
2. Check the replica file system.
3. Check the replication status to identify errors. Use the CLI or Enterprise Manager (GUI).
4. Check the messages file for more specific1. Check the network.
2. Check the replica file system.
3. Check the replication status to identify errors. Use the CLI or Enterprise Manager (GUI).
4. Check the messages file for more specific1. Check the network.
2. Check the replica file system.
3. Check the replication status to identify errors. Use the CLI or Enterprise Manager (GUI).
4. Check the messages file for more specific1. Check the network.
2. Check the replica file system.
3. Check the replication status to identify errors. Use the CLI or Enterprise Manager (GUI).
4. Check the messages file for more specific1. Check the network.
2. Check the replica file system.
3. Check the replication status to identify errors. Use the CLI or Enterprise Manager (GUI).
4. Check the messages file for more specific |
| 65 |
replNeedResync/1.3.6.1.4.1.19746.2.0.5064 |
Replication requires a resync. The context is disabled due to an NVRAM loss. |
Break replication on source and destination. Reconfigure source and destination, and run command option replication resync. |
| 66 |
replLogFull/1.3.6.1.4.1.19746.2.0.5065 |
Number of free replication log entries is below threshold. Disabling write access. |
1. Allow configured contexts to make progress. If a context is disabled, re-enable it and then allow progress.
2. Break disabled contexts no longer required by using the replication break command option.1. Allow configured contexts to make progress. If a context is disabled, re-enable it and then allow progress.
2. Break disabled contexts no longer required by using the replication break command option.1. Allow configured contexts to make progress. If a context is disabled, re-enable it and then allow progress.
2. Break disabled contexts no longer required by using the replication break command option.1. Allow configured contexts to make progress. If a context is disabled, re-enable it and then allow progress.
2. Break disabled contexts no longer required by using the replication break command option.1. Allow configured contexts to make progress. If a context is disabled, re-enable it and then allow progress.
2. Break disabled contexts no longer required by using the replication break command option.1. Allow configured contexts to make progress. If a context is disabled, re-enable it and then allow progress.
2. Break disabled contexts no longer required by using the replication break command option. |
| 67 |
replIncompatibleWorm/1.3.6.1.4.1.19746.2.0.5066 |
Incompatible retention-locked files detected during resync. |
Replace the drive and enable the slot using DD OS command options. See the DD OS Command Reference Guide for details. |
| 68 |
replDestNotConfigured/1.3.6.1.4.1.19746.2.0.5067 |
Destination is not configured and cannot initialize. |
Configure the context on the destination. |
| 69 |
replLagThreshholdReached/1.3.6.1.4.1.19746.2.0.5068 |
The replication lag threshold has been reached. |
Check the replication history to verify that replication is working properly. |
| 70 |
sASEnclosureCheck/1.3.6.1.4.1.19746.2.0.5069 |
A port has exceeded the maximum limit of supported SAS enclosures. This may cause problems because the configuration is now unsupported. |
Inspect the port and reduce the number of externally connected SAS enclosures. See the SAS documentation for details. |
| 71 |
sASTopologyCheck/1.3.6.1.4.1.19746.2.0.5070 |
Detected SAS topology error. |
Verify connectivity of SAS enclosures. See the SAS documentation. |
| 72 |
sASPortDisabled/1.3.6.1.4.1.19746.2.0.5071 |
Detected an HBA port is disabled. May be due to shelf controller failures or faulty cables. |
Contact Data Domain Support at https://mydatadomain.comto diagnose a connectivity problem. |
| 73 |
sSLCertificateCorrupted/1.3.6.1.4.1.19746.2.0.5072 |
SSL certificate used to establish mutual trust between Data Domain systems is broken. |
Contact Data Domain Support at https://mydatadomain.com. |
| 74 |
missingSysadminRegistryEntry/1.3.6.1.4.1.19746.2.0.5073 |
Required entry for determining role of sysadmin user is missing from the registry. Without this entry, the sysadmin user lacks privileges to perform critical and important operations. This may cause the system to become unusable. Because of the irrevocable consequences this condition may cause, DDSH auto-corrects the issue by adding the missing entry to the registry so the sysadmin user can function. However, doing so may cause problems if other registry entries are also missing. |
Contact your support provider or Data Domain Support at https://mydatadomain.comto determine why the registry entry was missing, and to discover if other registry entries are missing and how to resolve the issue. |
| 75 |
smsRestartFullQ/1.3.6.1.4.1.19746.2.0.5074 |
System management service, SMS restarted because all service tasks are hung and not making any progress. |
If the problem persist, Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 76 |
snapshotOver90Percent/1.3.6.1.4.1.19746.2.0.5075 |
The current number of an MTree’s snapshots is 90% or more of the maximum allowed. |
Expire the MTree’s snapshots or adjust the retention periods in the snapshot schedule. |
| 77 |
snapshotLimitReached/1.3.6.1.4.1.19746.2.0.5076 |
The Data Domain system limits the number of snapshots retained for a single Mtree. After the limit is reached, snapshots of the Mtree cannot be created. |
Expire snapshots of that Mtree to make room for newer ones. |
| 78 |
sNTZMultipleIterations/1.3.6.1.4.1.19746.2.0.5077 |
Indicates sanitization will run in multiple iterations. In an extreme case this process may take 15-20 days for 280 TBs. The system will not run at full speed during the process and GC will not run to reclaim space. However, sanitization will reclaim space during the process but it may not be as efficient as GC. |
Make sure you have enough space and that you can wait out the duration of an extreme case. You must have at least 20% of physical space available. Another option is to stop sanitization, delete unneccesary files, and retry the process. You can run this process iteratively until the alert is no longer generated. |
| 79 |
coredumpWarning/1.3.6.1.4.1.19746.2.0.5078 |
The directory /ddvar may soon run out of space for saving core dumps. Lack of space can result in missing core dumps, which hampers debug operations. |
Remove unwanted files from /ddvar to create space. |
| 80 |
coredumpDisabled/1.3.6.1.4.1.19746.2.0.5079 |
Space in the /ddvar directory is insufficient for saving core dumps. Lack of space can result in missing core dumps, which hampers debug operations. |
Remove unwanted files from /ddvar to create space. |
| 81 |
spaceOver80Percent/1.3.6.1.4.1.19746.2.0.5080 |
Space usage has exceeded 80% of the total capacity.Lack of space may result in missing important logs. |
If space is in root or /ddvar, or in an active tier,remove unwanted files to create space. If space is in an archive tier, add archive units to the file system. |
| 82 |
spaceOver90Percent/1.3.6.1.4.1.19746.2.0.5081 |
Space usage has exceeded 90% of the total capacity.Lack of space may result in missing important logs. |
If space is in root or /ddvar, or in an active tier,remove unwanted files to create space. If space is in an archive tier, add archive units to the file system. |
| 83 |
diskAccessError/1.3.6.1.4.1.19746.2.0.5082 |
Data Domain system cannot identify the state of the disk. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 84 |
diskFailure/1.3.6.1.4.1.19746.2.0.5083 |
The disk is in one of the following states: absent,failed, foreign. |
Make sure the disk is securely connected. If required, replace disk. |
| 85 |
diskTemperatureWarning/1.3.6.1.4.1.19746.2.0.5084 |
The disk temperature sensor reading has exceeded the warning threshold. If the temperature is high due to increased activity for a short period, temperature will return to normal. |
If temperature does not return to normal:
1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.If temperature does not return to normal:
1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.If temperature does not return to normal:
1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.If temperature does not return to normal:
1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.If temperature does not return to normal:
1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value. |
| 86 |
diskTemperatureShutdown/1.3.6.1.4.1.19746.2.0.5085 |
The disk temperature sensor reading has exceeded the critical threshold. The system will shut down. |
1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value.1. Check for fan failure.
2. Check if environment temperature is too high or low.
3. Check if the sensor is reporting inaccurate value. |
| 87 |
unsupportedHardwareSpareSize/1.3.6.1.4.1.19746.2.0.5086 |
Disk capacity is too small to be of use in system. |
Replace with a larger capacity disk. |
| 88 |
missingDiskGroup/1.3.6.1.4.1.19746.2.0.5087 |
One or more critical disks or LUNs are unavailable. |
1. Make sure storage is securely connected.
2. Review alert history for path failures.
3. Check core files. A critical layer may be unavailable.
4. Verify all storage is working and recognized correctly.1. Make sure storage is securely connected.
2. Review alert history for path failures.
3. Check core files. A critical layer may be unavailable.
4. Verify all storage is working and recognized correctly.1. Make sure storage is securely connected.
2. Review alert history for path failures.
3. Check core files. A critical layer may be unavailable.
4. Verify all storage is working and recognized correctly.1. Make sure storage is securely connected.
2. Review alert history for path failures.
3. Check core files. A critical layer may be unavailable.
4. Verify all storage is working and recognized correctly.1. Make sure storage is securely connected.
2. Review alert history for path failures.
3. Check core files. A critical layer may be unavailable.
4. Verify all storage is working and recognized correctly. |
| 89 |
diskGroupReconstructionNoProgress/1.3.6.1.4.1.19746.2.0.5088 |
One or more disks failed and RAID reconstruction is not running. |
Verify there is one or more spare disks in the system. |
| 90 |
diskGroupReconstruction/1.3.6.1.4.1.19746.2.0.5089 |
Two or more disks failed and RAID protection is in critical state. Additional disk failure will cause permanent data loss. System shuts down if problem is not fixed immediately. |
Verify there is one or more spare disks in the system. |
| 91 |
diskGroupReconstructionShutdown/1.3.6.1.4.1.19746.2.0.5090 |
Two or more disks failed and RAID protection is in critical state for a lengthy duration. Additional disk failure will cause permanent data loss. System will shut down. |
Restart the system. Verify there is one or more spare disks in the system. |
| 92 |
diskGroupReconstructionCritical/1.3.6.1.4.1.19746.2.0.5091 |
Two or more disks failed and RAID protection is in critical state for a lengthy duration. Additional disk failure will cause permanent data loss. |
Verify there is one or more spare disks in the system. |
| 93 |
diskUnknown/1.3.6.1.4.1.19746.2.0.5092 |
Disk is unknown. |
Add disk to the system. |
| 94 |
enclUnknown/1.3.6.1.4.1.19746.2.0.5093 |
All disks in enclosure are unknown. |
Add enclosure to the system. |
| 95 |
lowSpares/1.3.6.1.4.1.19746.2.0.5094 |
Tier is low on spares. |
Replace failed or absent disks. |
| 96 |
unsupportedConfigurationROL/1.3.6.1.4.1.19746.2.0.5095 |
RAID on LUN from 4.8 is no longer supported. Follow instructions below to increase usable space in file system. See the DD OS Command Reference Guide or Administration Guide for details. |
1. Migrate data away.
2. Perform a file system destroy.
3. Add LUN.
4. Migrate data back.1. Migrate data away.
2. Perform a file system destroy.
3. Add LUN.
4. Migrate data back.1. Migrate data away.
2. Perform a file system destroy.
3. Add LUN.
4. Migrate data back.1. Migrate data away.
2. Perform a file system destroy.
3. Add LUN.
4. Migrate data back. |
| 97 |
syslogAlert/1.3.6.1.4.1.19746.2.0.5096 |
A message of high severity has been logged. |
Review logs to see if there is a problem requiring attention. |
| 98 |
vTLFCLinkOnline/1.3.6.1.4.1.19746.2.0.5097 |
The VTL (Virtual Tape Library) FC (Fibre Channel) link is online: port %s. |
No action is required. |
| 99 |
cpismissing/1.3.6.1.4.1.19746.2.0.5500 |
An archive unit is missing, which could result in a failure to access files in that unit. |
1. Check the power connection of each shelf.
2. Check the data cables of each shelf.
3. If a hardware problem is found and fixed, restart the file system and verify that the archive unit is online.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com1. Check the power connection of each shelf.
2. Check the data cables of each shelf.
3. If a hardware problem is found and fixed, restart the file system and verify that the archive unit is online.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com1. Check the power connection of each shelf.
2. Check the data cables of each shelf.
3. If a hardware problem is found and fixed, restart the file system and verify that the archive unit is online.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com1. Check the power connection of each shelf.
2. Check the data cables of each shelf.
3. If a hardware problem is found and fixed, restart the file system and verify that the archive unit is online.
4. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com |
| 100 |
containerMarkedInvalid/1.3.6.1.4.1.19746.2.0.5501 |
The restorer file system has detected a data integrity check failure caused by a hardware or software problem. There is potential for data loss or corruption,so this requires immediate attention. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 101 |
smiMrc/1.3.6.1.4.1.19746.2.0.5502 |
There has been a BIOS SMI MRC interrupt. |
Check to see if the system memory size has been decreased because a DIMM has been disabled,and if so, replace the bad DIMM. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Check to see if the system memory size has been decreased because a DIMM has been disabled,and if so, replace the bad DIMM. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Check to see if the system memory size has been decreased because a DIMM has been disabled,and if so, replace the bad DIMM. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
Check to see if the system memory size has been decreased because a DIMM has been disabled,and if so, replace the bad DIMM. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.
|
| 102 |
nvramBoardTempAlert/1.3.6.1.4.1.19746.2.0.5503 |
The current NVRAM board temperature sensor reading exceeds the warning threshold temperature. |
1. Check to see if there is a system fan alert. If yes,replace the old fan with a new one.
2. Check the ambient room temperature.
3. Check for blocked air flow.
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check to see if there is a system fan alert. If yes,replace the old fan with a new one.
2. Check the ambient room temperature.
3. Check for blocked air flow.
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check to see if there is a system fan alert. If yes,replace the old fan with a new one.
2. Check the ambient room temperature.
3. Check for blocked air flow.
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Check to see if there is a system fan alert. If yes,replace the old fan with a new one.
2. Check the ambient room temperature.
3. Check for blocked air flow.
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 103 |
nvramBoardVoltageAlert/1.3.6.1.4.1.19746.2.0.5504 |
The DD OS detected an NVRAM board voltage sensor reading that exceeds the warning threshold voltage. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 104 |
nvramBatteryTempAlert/1.3.6.1.4.1.19746.2.0.5505 |
The DD OS detected an NVRAM battery temperature sensor reading that exceeds the warning threshold.
Probable cause(s):
1. Insufficient air inflow, or
2. High system ambient temperature, or
3. Degraded batteriesThe DD OS detected an NVRAM battery temperature sensor reading that exceeds the warning threshold.
Probable cause(s):
1. Insufficient air inflow, or
2. High system ambient temperature, or
3. Degraded batteriesThe DD OS detected an NVRAM battery temperature sensor reading that exceeds the warning threshold.
Probable cause(s):
1. Insufficient air inflow, or
2. High system ambient temperature, or
3. Degraded batteriesThe DD OS detected an NVRAM battery temperature sensor reading that exceeds the warning threshold.
Probable cause(s):
1. Insufficient air inflow, or
2. High system ambient temperature, or
3. Degraded batteries |
Check to see if there is a system fan alert. If yes, replace the old fan with a new one. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check to see if there is a system fan alert. If yes, replace the old fan with a new one. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check to see if there is a system fan alert. If yes, replace the old fan with a new one. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com.Check to see if there is a system fan alert. If yes, replace the old fan with a new one. If this issue persists, contact your support provider or
Data Domain Support at https://mydatadomain.com. |
| 105 |
nvramBatteryVoltageAlert/1.3.6.1.4.1.19746.2.0.5506 |
The DD OS detected an NVRAM battery voltage sensor reading that exceeds the warning threshold. Probable cause: The NVRAM battery unit is faulty. |
The NVRAM card battery unit may need to be replaced. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 106 |
nvramBatteryChargeAlert/1.3.6.1.4.1.19746.2.0.5507 |
The DD OS detected an NVRAM card battery unit hardware fault. Probable cause: One or more batteries is not charging. |
Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com. |
| 107 |
nvramBatteryLowChargeAlert/1.3.6.1.4.1.19746.2.0.5508 |
The NVRAM battery charge is lower than 80%. |
This alert will be cleared when the battery charge is greater than or equal to 80%. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 108 |
nvramBatteryGaugeAlert/1.3.6.1.4.1.19746.2.0.5509 |
The DD OS detected an NVRAM card battery unit hardware fault.Probable cause: The battery unit hardware is not accessible. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 109 |
nvramBatteryDetectAlert/1.3.6.1.4.1.19746.2.0.5510 |
The DD OS detected an NVRAM card battery unit hardware fault.Probable cause: One or more batteries is missing. |
Contact your support provider or Data Domain Support at https://mydatadomain.com.
Contact your support provider or Data Domain Support at https://mydatadomain.com.
Contact your support provider or Data Domain Support at https://mydatadomain.com.
Contact your support provider or Data Domain Support at https://mydatadomain.com.
|
| 110 |
nvramBatteryChargeDisableAlert/1.3.6.1.4.1.19746.2.0.5511 |
The DD OS detected an NVRAM card Battery Unit hardware fault. Probable cause: One or more batteries is not charging. |
Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.
Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.
Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.
Run the command, system show nvram, to check the battery status. If this issue persists, contact your support provider or Data Domain Support at
https://mydatadomain.com.
|
| 111 |
nvramCorrectMemAlert/1.3.6.1.4.1.19746.2.0.5512 |
The DD OS detected an NVRAM card fault. Probable cause: NVRAM card correctable memory errors exceed the warning threshold number. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 112 |
nvramUncorrectMemAlert/1.3.6.1.4.1.19746.2.0.5513 |
The DD OS detected an NVRAM card fault. Probable cause: The NVRAM card has uncorrectable memory errors. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 113 |
nvramPCIeAlert/1.3.6.1.4.1.19746.2.0.5514 |
The DD OS detected an NVRAM card fault. Probable cause: The NVRAM card has PCIe errors. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 114 |
nvramCPUAlert/1.3.6.1.4.1.19746.2.0.5515 |
The DD OS detected an NVRAM card fault.Probable cause: The NVRAM card has CPU errors. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 115 |
nvramBatteryPowerDisableAlert/1.3.6.1.4.1.19746.2.0.5516 |
The DD OS detected that NVRAM battery power is disabled. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 116 |
nvramReadOnlyAlert/1.3.6.1.4.1.19746.2.0.5517 |
The DD OS detected an NVRAM card Battery Unit hardware fault. Probable cause: An NVRAM card initialization error. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 117 |
nvramCardDetectAlert/1.3.6.1.4.1.19746.2.0.5518 |
The DD OS could not detect any NVRAM card(s) in the system. Probable causes:
1. the NVRAM card(s) may be absent, or
2. the NVRAM card(s) may not be seated properlyThe DD OS could not detect any NVRAM card(s) in the system. Probable causes:
1. the NVRAM card(s) may be absent, or
2. the NVRAM card(s) may not be seated properlyThe DD OS could not detect any NVRAM card(s) in the system. Probable causes:
1. the NVRAM card(s) may be absent, or
2. the NVRAM card(s) may not be seated properly |
1. Check that the NVRAM card(s) is (are) properly seated.
2. To get a new NVRAM card, contact your support provider or Data Domain Support at https://mydatadomain.com.
1. Check that the NVRAM card(s) is (are) properly seated.
2. To get a new NVRAM card, contact your support provider or Data Domain Support at https://mydatadomain.com.
1. Check that the NVRAM card(s) is (are) properly seated.
2. To get a new NVRAM card, contact your support provider or Data Domain Support at https://mydatadomain.com.
|
| 118 |
nvramWrongModelAlert/1.3.6.1.4.1.19746.2.0.5519 |
The DD OS detected an incompatible NVRAM card configuration. Probable cause: The NVRAM card in the system is not supported by your current DD OS version. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 119 |
nvramMemSizeAlert/1.3.6.1.4.1.19746.2.0.5520 |
The DD OS detected an incompatible NVRAM card configuration. Probable cause: The NVRAM card is incompatible with this system. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 120 |
nvramLinkSpeedAlert/1.3.6.1.4.1.19746.2.0.5521 |
The DD OS detected an incompatible NVRAM card configuration. Probable cause: The NVRAM card is incompatible with this system. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 121 |
nvramLinkWidthAlert/1.3.6.1.4.1.19746.2.0.5522 |
The DD OS detected an incompatible NVRAM card configuration. Probable cause: The NVRAM card is incompatible with this system. |
The NVRAM card may need to be replaced.Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 122 |
nvramGetInfoAlert/1.3.6.1.4.1.19746.2.0.5523 |
The DD OS detected an NVRAM card battery unit hardware fault. Probable cause: The battery unit hardware is not accessible. |
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 123 |
nvramTargetLinkSpeedAlert/1.3.6.1.4.1.19746.2.0.5524 |
The DD OS detected an incompatible NVRAM card configuration.Probable cause: The NVRAM card is incompatible with this system. |
The NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 124 |
nvramWrongCountAlert/1.3.6.1.4.1.19746.2.0.5525 |
The DD OS detected an incompatible NVRAM card configuration. Probable cause: The number of NVRAM cards in the system is different from what DD OS expects. |
VRAM card(s) may need to be removed or added. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 125 |
nvramMIxAlert/1.3.6.1.4.1.19746.2.0.5526 |
The DD OS detected an incompatible NVRAM card configuration. Probable cause: Two generations of NVRAM cards are in the system. |
An NVRAM card may need to be replaced. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 126 |
ext3NvlogDisabled/1.3.6.1.4.1.19746.2.0.5527 |
NVRAM battery status is not okay to enable nvlog in this disk group. When the battery status is okay, nvlog will be enabled, and this alert will be cleared. |
Wait for the NVRAM alert to be cleared. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 127 |
enclosureMixType/1.3.6.1.4.1.19746.2.0.5528 |
An unsupported mix of enclosure models has been detected, for example, a mixture of ES30s and ES20s. |
Refer to the configuration guide for valid cabling configurations. |
| 128 |
vTLFCLinkOffline/1.3.6.1.4.1.19746.2.0.5529 |
No connection is detected on the Fibre Channel (FC) port. |
If this port is not in use, disable it. If it is in use, restore FC port connectivity. The alert will be cleared when the port is disabled or online. |
| 129 |
vTLFCLinkOscillations/1.3.6.1.4.1.19746.2.0.5530 |
The system has detected that a Fibre Channel port has been transitioning between online and offline too frequently. This may cause backup issues. |
Ensure stable port connectivity. Disable the port if it is not in use. |
| 130 |
replPathTooLong/1.3.6.1.4.1.19746.2.0.5531 |
The replication path is too long. |
Shorten the path. |
| 131 |
compromisedEncryptionKeys/1.3.6.1.4.1.19746.2.0.6001 |
Data on the disk may be at risk of disclosure. Data encrypted with the compromised keys should be reencrypted before shipping the disks. Run the command,
filesys encryption keys show, to see the list of compromised keys.Data on the disk may be at risk of disclosure. Data encrypted with the compromised keys should be reencrypted before shipping the disks. Run the command,
filesys encryption keys show, to see the list of compromised keys. |
Run the command, filesys clean start, to start the re-encryption process. Note that this command may take a long time to complete. |
| 132 |
newEncryptionKey/1.3.6.1.4.1.19746.2.0.6002 |
Run the command, filesys encryption keys show, to see the newly added key. The old key is still used for encrypting new data. To begin encrypting the data with the new key, restart the file system. |
Run the command, filesys restart, to restart the file system. |
| 133 |
encryptionKeyTableFull/1.3.6.1.4.1.19746.2.0.6003 |
The encryption key table is full. The old key is still being used for encrypting new data. |
To free up key table space, run the command, filesys encryption keys delete. To add the new key, run the command, filesys encryption keys sync. |
| 134 |
uncertifiedFirmware/1.3.6.1.4.1.19746.2.0.6004 |
The firmware version is not compatible with this version of DD OS and may cause unexpected behavior. |
The firmware must be updated as soon as possible. Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 135 |
filesystemNVRAMDataLoss/1.3.6.1.4.1.19746.2.0.6005 |
The file system cannot be enabled because of an NVRAM mismatch. This can happen because of an improper headswap or NVRAM card replacement operation. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 136 |
filesystemUpgradeFailure/1.3.6.1.4.1.19746.2.0.6006 |
During the upgrade process, there was an error upgrading the file system. The file system cannot be enabled. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 137 |
mtreeQuotaSoftLimit/1.3.6.1.4.1.19746.2.0.6007 |
The soft limit quota for this MTree has been reached. This will not affect the operation of the system and is only a warning. If a hard limit quota is set for this MTree, you are approaching that limit, and operations writing data to this MTree may fail if the hard limit is reached. |
To clear this alert, either raise the quota limits or reduce the data in the MTree by deleting files.
To clear this alert, either raise the quota limits or reduce the data in the MTree by deleting files.
|
| 138 |
mtreeQuotaHardLimit/1.3.6.1.4.1.19746.2.0.6008 |
The hard limit quota for this MTree has been reached. No more data will be written to this MTree. If a backup operation was running, it probably failed and must be restarted after clearing this condition. |
To clear this alert, either raise the hard limit quota for this MTree or reduce the data in the MTree by deleting files. |
| 139 |
interfaceConnectivityDown/1.3.6.1.4.1.19746.2.0.6009 |
The network connectivity on this interface is down. This interface is not ping-able and cannot be used to send or receive any data. All data transfers using this interface will fail. |
View the Hardware->Network GUI page, or use the commands, net show settings and net show config, to check the current configuration. Make sure
the cable is securely connected to both endpoints and the interfaces on both ends are properly configured. Otherwise, the cable or network hardware could be faulty and may need to be replaced. If the network is configured properly, and the problem still persists, contact your support provider or Data
Domain Support at https://mydatadomain.com.View the Hardware->Network GUI page, or use the commands, net show settings and net show config, to check the current configuration. Make sure
the cable is securely connected to both endpoints and the interfaces on both ends are properly configured. Otherwise, the cable or network hardware could be faulty and may need to be replaced. If the network is configured properly, and the problem still persists, contact your support provider or Data
Domain Support at https://mydatadomain.com. |
| 140 |
interfaceConnectivityIntermittent/1.3.6.1.4.1.19746.2.0.6010 |
Network connectivity on this interface is intermittent.Data may not be sent or received successfully. Data transfers using this interface may experience performance degradation or intermittent failures. |
View the Hardware->Network GUI page, or use the commands, net show settings and net show config, to check the current configuration. Make sure the cable is securely connected to both endpoints and the interfaces on both ends are properly configured. Otherwise, the cable or network hardware could be faulty and may need to be replaced. If the network is configured properly and this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 141 |
interfaceMisconfiguration/1.3.6.1.4.1.19746.2.0.6011 |
A network interface configuration problem has been detected. This may be a result of changing the NIC (network interface controller) hardware without
reconfiguring the interface. This could indicate an unsupported configuration, network environment, or hardware problem. A misconfigured interface can
potentially cause connectivity problems on subsequent reboots.A network interface configuration problem has been detected. This may be a result of changing the NIC (network interface controller) hardware without
reconfiguring the interface. This could indicate an unsupported configuration, network environment, or hardware problem. A misconfigured interface can
potentially cause connectivity problems on subsequent reboots. |
View the Hardware->Network GUI page, or use the commands, net show settings, net config, and net show hardware, to check the network configuration.Try to fix the problem by reconfiguring the interface with the command, net config. |
| 142 |
unreachableKeyManager/1.3.6.1.4.1.19746.2.0.6012 |
There has been a communication failure.
Probable causes:
1. network connectivity
2. RKM (RSA Key Manager) server being down
3invalid certificatesThere has been a communication failure.
Probable causes:
1. network connectivity
2. RKM (RSA Key Manager) server being down
3invalid certificates |
1. Verify/check all issues on the Data Domain system.
2. Verify/check that the RKM is online.
3. If the certificates have expired, import new certificates.
4. Run the command, filesys encryption key-manager show, to view the status.
5. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com.1. Verify/check all issues on the Data Domain system.
2. Verify/check that the RKM is online.
3. If the certificates have expired, import new certificates.
4. Run the command, filesys encryption key-manager show, to view the status.
5. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 143 |
recoverFromNVRAMFailed/1.3.6.1.4.1.19746.2.0.6013 |
Due to NVRAM issues, the file system has been disabled in order to maintain data integrity. No backups will run until this problem is resolved. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 144 |
cleaningError/1.3.6.1.4.1.19746.2.0.6014 |
The system is unable to reclaim unused space, which may impact the ability to perform backups. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 145 |
bMCPartialHang/1.3.6.1.4.1.19746.2.0.6015 |
The BMC firmware is not responsive. |
Use the CLI or Enterprise Manager to check the fan, voltage, and power supply readings. If the system fails to fetch the readings, gracefully shut down the system and pull out all power cables to reset BMC. Wait until all LEDs are off. Reinsert the power cables, and then power the system up.
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 146 |
fileMigrationError/1.3.6.1.4.1.19746.2.0.6016 |
File migration has been suspended until a problem is resolved. |
Contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 147 |
unusableHostCertificate/1.3.6.1.4.1.19746.2.0.6017 |
The Enterprise Manager will not start up using the imported certificate. However, it will start up using the default self-signed certificate.
Probable causes:
1. the file system is locked
2. the system passphrase is missing
3. the imported certificate is corrupted |
1. Unlock the file system if it is locked.
2. Enter the system passphrase if it is missing.
3. Delete and re-import the current host certificate if it is corrupted.
4.? In all cases, the Enterprise Manager must be restarted.
If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 148 |
missingHostCertificate/1.3.6.1.4.1.19746.2.0.6018 |
The imported certificate is missing, However, the Enterprise Manager will start up using the default selfsigned certificate. |
If you want to use your own certificate, import it again. |
| 149 |
foreignEnclosure/1.3.6.1.4.1.19746.2.0.6019 |
The enclosure is unusable by the file system. |
If this is intentional as part of a chassis swap or chassis upgrade, proceed with the headswap operation to make the foreign file system available. Otherwise, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 150 |
interfaceConnectivityUpAndRunning/1.3.6.1.4.1.19746.2.0.6020 |
The network interface has been up and running for a period of time, after experiencing instability. |
No action needed. |
| 151 |
tcpZeroWindowAlert/1.3.6.1.4.1.19746.2.0.6101 |
The TCP connection is active, but data is not being transferred. This may cause other communication failures. |
1. Check the remote application that uses this TCP connection.
2. Check the network path between the local and remote systems.
3. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 152 |
mailserverError/1.3.6.1.4.1.19746.2.0.6511 |
There is a problem communicating with the configured mail server. The system will not be able to send out any email notifications that include alerts, autosupports, and daily summary emails. |
Make sure that the mail server is configured correctly. Verify the configured mail server by sending out a test email from the system. If this issue persists, contact your support provider or Data Domain Support at https://mydatadomain.com. |
| 153 |
systemReset/1.3.6.1.4.1.19746.2.0.6529 |
A critical failure caused the system to unexpectedly shut down. The system was able to boot successfully because either the fault was corrected, the fault was transient, or the system was able to boot without the component causing the fault. |
Review the system for earlier alerts to determine the cause of the unexpected shutdown. Check the system inventory to verify that all components are configured as expected. If this alert is issued again, contact your support provider or Data Domain Support at https://mydatadomain.com. |
