Admin Console alerts in Analytics Platform System
Alerts for Analytics Platform System appear in the Admin Console appliance and in System Center Operations Manager. Use the list in this article to identify which alerts require investigation.
For information about connecting to the Admin Console by using Internet Explorer, see Monitor the appliance by using the Admin Console (Analytics Platform System). For information about Operations Manager, see Monitor the appliance by using System Center Operations Manager (Analytics Platform System).
For information about obtaining alert information by using Transact-SQL, see Monitor the appliance by using system views (Analytics Platform System).
Types of alerts
Alert names that indicate a NORMAL status don't usually require investigation. Alert names that contain NON-CRITICAL sometimes require action. Investigation is required for all other types of alerts.
Alert list
The following table lists alerts alphabetically by name. The list doesn't include all possible alerts. The wording of some alerts varies slightly for different vendors.
| Alert name | Action required? | State | Severity | Description | More information |
|---|---|---|---|---|---|
| Ambari Agent has CRITICAL status. | Yes | Failed | Error | This Ambari Agent resource has failed (status: 4) or is offline (status: 3). Or an offline state is pending (status: 130). Status is reported in the component's hadoop_service_status property. |
Review the cluster resource on the head and data nodes. |
| Ambari Agent has NON-CRITICAL status. | Yes | Degraded | Warning | This Ambari Agent resource is in a non-critical state for one of the following reasons: - The resource is in an inherited state (status: 0).- The resource is in a pending state (status: 128).- The resource is in an online pending state (status: 129).- The resource is performing initialization (status: 1).Status is reported in the component's hadoop_service_status property. |
Review the cluster resource on the head and data nodes. |
| Ambari Agent has NORMAL status. | No | Operational | Informational | The Ambari Agent is running normally (status: Running). Status is reported in the component's hadoop_service_status property. |
|
| Ambari Agent has UNKNOWN status. | Yes | Degraded | Warning | Status of this Ambari Agent resource couldn't be determined (status: -1). Status is reported in the component's hadoop_service_status property. |
Review the cluster resource on the head and data nodes. |
| Application Heartbeat has NORMAL status. | No | Operational | Informational | Establishment of communication with the application was successful. | The component previously reported a different status but has since returned to normal. |
| Application Heartbeat is throwing CRITICAL alert. | Yes | Non-operational | Error | Communication with the application was unsuccessful. The application might be in the process of restarting. | The application heartbeat is in an unexpected state. Troubleshooting is required. Review the node's Windows event log for details. |
| Cluster Failover event has occurred. | Yes | Operational | Error | The primary clustered node is no longer active, so the passive node has taken over as the primary node. Review the failed node's Windows event log for details, and review Failover Cluster Manager on the HST01 VM. | Failover has occurred. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM and the node's system event log. |
| Cluster resource group has CRITICAL status. | Yes | Failed | Error | This cluster resource group has failed and might be in the process of attempting a restart or is offline. | The resource group status has failed and requires troubleshooting. Review Failover Cluster Manager on the HST01 VM. |
| Cluster resource group has NON-CRITICAL status. | Yes | Degraded | Warning | This cluster resource group is online but in a non-critical state for one of the following reasons: - The resource group is partially online. - The resource group is in a pending state. |
The resource group isn't completely in the expected state. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Cluster resource group has NORMAL status. | No | Operational | Informational | This cluster resource group is online. | The component previously reported a different status but has since returned to normal. |
| Cluster resource group has UNKNOWN status. | Yes | Degraded | Warning | This cluster resource group is in an unknown state. | The system couldn't retrieve the health status of the cluster resource group. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Cluster resource has CRITICAL status. | Yes | Failed | Error | This clustered resource has failed and might be attempting a restart, or is in an offline state. | The cluster resource isn't in the expected state. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Cluster resource has NON-CRITICAL status. | Yes | Degraded | Warning | This clustered resource is in a non-critical state for one of the following reasons: - The resource is in an inherited state. - The resource is in a pending state. - The resource is in an online pending state. - The resource is in an offline pending state. - The resource is performing initialization. |
The cluster resource isn't in the expected state. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Cluster resource has NORMAL status. | No | Operational | Informational | This clustered resource is online. | The component previously reported a different status but has since returned to normal. |
| Cluster resource has UNKNOWN status. | Yes | Degraded | Warning | Status of this clustered resource couldn't be determined. | The system couldn't retrieve the health state of the cluster resource. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Cluster Shared Volume has CRITICAL status. | Yes | Failed | Error | This clustered shared volume resource has failed (status: 4) or is offline (status: 3). Or an offline state is pending (status: 130). Status is reported in the component's csv_state property. |
Review Failover Cluster Manager on the HST01 VM. |
| Cluster Shared Volume has NON-CRITICAL status. | Yes | Degraded | Warning | This clustered shared volume resource is in a non-critical state for one of the following reasons: - The resource is in an inherited state (status: 0). - The resource is in a pending state (status: 128). - The resource is in an online pending state (status: 129). - The resource is performing initialization (status: 1). Status is reported in the component's csv_state property. |
Review Failover Cluster Manager on the HST01 VM. |
| Cluster Shared Volume has a NORMAL status. | No | Operational | Informational | This clustered shared volume resource is online (status: 2). Status is reported in the component's csv_state property. |
|
| Cluster Shared Volume has an UNKNOWN status. | Yes | Degraded | Warning | Status of this clustered shared volume resource couldn't be determined (status: -1). Status is reported in the component's csv_state property. |
Review Failover Cluster Manager on the HST01 VM. |
| Cluster Status Normal | No | Operational | Informational | The cluster has a normal status. | The component previously reported a different status but has since returned to normal. |
| Controller has a CRITICAL status. | Yes | Failed | Error | The PERC disk is indicating there's a critical error, or the controller has been powered off. | The local RAID controller has a critical error and might need to be replaced. Troubleshooting is required. Review the node's Windows event log for details. |
| Controller has a NON-CRITICAL status. | Yes, if the problem persists for more than 7 hours or reoccurs multiple times on the same node and isn't tied to expected reboots | Degraded | Warning | The PERC disk reported a non-critical problem, probably related to a cable malfunction. | This event most commonly indicates a battery recharging cycle on the PowerEdge RAID Controller's battery-backed cache module. This cycle might be the scheduled test cycle (duration up to 7 hours). It also might be reported after reboots or power cycles when the battery must recharge. This event also usually indicates that the controller's policy temporarily has changed from write-through to write-back until the charging is complete. This change has performance implications on the local storage ( tempdb). Review the node's Windows event log for details. |
| Controller has a NON-RECOVERABLE status. | Yes | Failed | Error | The PERC disk status is non-recoverable. | The local RAID controller isn't functional. It has entered a non-recoverable state and might need to be replaced. Troubleshooting is required. Review the node's Windows event log for details. |
| Controller has a NORMAL status. | No | Operational | Informational | The PERC disk is running normally. | The component previously reported a different status but has since returned to normal. |
| Controller has an UNKNOWN status. | Yes | Degraded | Warning | The status of the PERC disk couldn't be determined. | The system couldn't retrieve the health state of the local RAID controller. Troubleshooting is required. Review the node's Windows event log for details. |
| Cooling device has a CRITICAL status. | Yes | Failed | Warning | The cooling device has reached a critical upper or lower threshold. | The cooling device might require replacement. Troubleshooting is required. Review the node's Windows event log for details. |
| Cooling device has a NON-CRITICAL status. | Yes | Degraded | Warning | The cooling device has reached a non-critical upper or lower threshold. | The cooling device hasn't reached critical levels but is outside the expected upper or lower range. Review the node's Windows event log for details. |
| Cooling device has a NON-RECOVERABLE status. | Yes | Failed | Warning | The cooling device has reached a non-recoverable upper or lower threshold. | The cooling device might require replacement. Troubleshooting is required. Review the node's Windows event log for details. |
| Cooling device has a NORMAL status. | No | Operational | Informational | The cooling device is running normally. | The component previously reported a different status but has since returned to normal. |
| Cooling device has an UNKNOWN status. | Yes | Degraded | Warning | The status of the cooling device couldn't be determined. | The system couldn't retrieve the status of the cooling device. Troubleshooting is required. Review the node's Windows event log for details. |
| Disk array has a CRITICAL overall status. | Yes | Failed | Error | The disk array's overall status is critical. | This event might indicate that the disk array is no longer active because of failed drives or a similar problem. Troubleshooting is required. Review the node's Windows event log for details. |
| Disk array has a NON-CRITICAL overall status. | Yes | Degraded | Warning | The disk array's overall status is indicating there's a non-critical warning but the system is still operational. | The disk array is still functional, but this event might indicate a disk failure or a similar problem. Troubleshooting is required. Review the node's Windows event log for details. |
| Disk array has a NON-RECOVERABLE overall status. | Yes | Failed | Error | The disk array's overall status is non-recoverable. | The disk array is no longer functional. Troubleshooting is required. Review the node's Windows event log for details. |
| Disk array has a NORMAL overall status. | No | Operational | Informational | The disk array's overall status is normal. | The component previously reported a different status but has since returned to normal. |
| Disk array has an UNKNOWN overall status. | Yes | Degraded | Warning | Overall status of the disk array couldn't be determined. | The system can't retrieve the health state of the local disk array. Troubleshooting is required. Review the node's Windows event log for details. |
| External Storage Array has CRITICAL status. | Yes | Failed | Error | The external storage array is indicating there's a failure (vendor operational status: 6, 16). Vendor status is reported in the component's storage_global_status property. Values: 6-Error, 16-Supporting Entity Error. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| External Storage Array has a NON-CRITICAL status. | Yes | Degraded | Warning | The external storage array reported a non-critical warning (vendor operational status: 3, 4, 5, 11, 14, 15, 17). Vendor status is reported in the component's storage_global_status property. Values: 3-Degraded, 4-Stressed, 5-Predictive Failure, 11-In Service, 14-Aborted, 15-Dormant, 17-Completed Operation. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| External Storage Array has a NON-RECOVERABLE status. | Yes | Failed | Error | The external storage array is indicating that it's down and non-recoverable (vendor operational status: 7). Vendor status is reported in the component's storage_global_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| External Storage Array has a NORMAL status. | No | Operational | Informational | The external storage array is working normally (vendor status: ok). Vendor status is reported in the component's storage_global_status property. |
|
| External Storage Array has an UNKNOWN status. | Yes | Degraded | Warning | The status of the external storage array couldn't be determined based on the vendor status (vendor operational status: 0, 1, 18). Vendor status is reported in the component's storage_global_status property. Values: 0-Unkown, 1-Other, 18-Power Mode. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| External Storage Array has an UNREACHABLE status. | Yes | Failed | Error | The external storage array is indicating that it's unreachable (vendor operational status: 8, 9, 10, 12, 13). Vendor status is reported in the component's storage_global_status property. Values: 8-Starting, 9-Stopping, 10-Stopped, 12-No Contact, 13-Lost Communication. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| External Storage has a CRITICAL status. | Yes | Failed | Error | The external storage is indicating there's a failure. | Troubleshooting is required. Review the Windows event log and the storage device's event log for details. |
| External Storage has a DEGRADED status. | Yes | Degraded | Warning | The storage system is degraded. You need to check the temperature status or power supply status of this storage system. Additionally, if the side panel for the storage system is removed, the air flow changes might result in improper cooling of the drives and affect the temperature status. Vendor status is reported in the component's storage_global_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| External Storage has a NON-CRITICAL status. | Yes, if the problem persists for more than 7 hours or reoccurs frequently on the same device more than every 90 days | Degraded | Warning | The external storage reported a non-critical warning. | This event typically indicates one of two issues: disk failures/transition events or battery recharging cycles on the RAID controller's battery-backed cache module. The charging cycles are usually scheduled every 90 days and can take up to 7 hours. During this time, it's likely that the controller's write-cache policy has temporarily changed from write-through to write-back. This change can affect performance. Review the Windows event log and the storage device's event log for details. |
| External Storage has a NORMAL status. | No | Operational | Informational | The external storage is working normally. | The component previously reported a different status but has since returned to normal. |
| External Storage has an UNKNOWN status. | Yes | Degraded | Warning | The status of the external storage couldn't be determined. | The system couldn't retrieve the health state of the server's external storage. Troubleshooting is required. Review the node's Windows event log and the storage device's event log for details. |
| Fan device has a CRITICAL status. | Yes | Failed | Warning | The fan device has reached a critical upper or lower threshold (vendor status: CriticalUpper or CriticalLower). Vendor status is reported in the component's device_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Fan device has a NON-CRITICAL status. | Yes | Degraded | Warning | The fan device has reached a non-critical upper or lower threshold (vendor status: nonCriticalUpper or nonCriticalLower). Vendor status is reported in the component's device_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Fan device has a NON-RECOVERABLE status. | Yes | Failed | Warning | The fan device has reached a non-recoverable upper or lower threshold (vendor status: failed, nonRecoverableUpper, or nonRecoverableLower). Vendor status is reported in the component's device_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Fan device has a NORMAL status. | No | Operational | Informational | The fan device is running normally (vendor status: ok). Vendor status is reported in the component's device_status property. |
|
| Fan device has an UNKNOWN status. | Yes | Degraded | Warning | The status of the fan device couldn't be determined (vendor status: other or unknown). Vendor status is reported in the component's device_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Fibre Channel host controller has a CRITICAL status. | Yes | Failed | Warning | The Fibre Channel host controller component detects one of the following conditions: - The host controller has failed and should be replaced (vendor status: failed). - The host controller has been shut down (vendor status: shutdown). - The Fibre Channel connection has failed (vendor status: loopFailed). Vendor status is reported in the component's FC_device_rollup_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. If the controller status is failed, replace the controller. |
| Fibre Channel host controller has a NON-CRITICAL status. | Yes | Degraded | Warning | The Fibre Channel host controller is reporting one of the following conditions: - The Fibre Channel connection is degraded (vendor status: loopDegraded). - The Fibre Channel port isn't connected, or the device to which it's connected is powered down (vendor status: notConnected). Vendor status is reported in the component's FC_device_rollup_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Fibre Channel host controller has a NORMAL status. | No | Operational | Informational | The Fibre Channel host controller is operating normally (vendor status: ok). Vendor status is reported in the component's FC_device_rollup_status property. |
|
| Fibre Channel host controller has an UNKNOWN status. | Yes | Degraded | Warning | Fibre Channel host controller status couldn't be determined, or the controller isn't present (vendor status: other). Vendor status is reported in the component's FC_device_rollup_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Hadoop Service has a CRITICAL status. | Yes | Non-operational | Error | This service is in a critical state and has stopped working (status: Installed or Stopped) or is in a transitional state to be stopped (status: Stopping). Status is reported in the component's hadoop_service_status property. |
Review the node's Windows and PDW component event logs for details. |
| Hadoop Service has a NON-CRITICAL status. | Yes | Degraded | Warning | This service is in a non-critical state for one of the following reasons: - The service is starting (status: Starting). - The service is upgrading (status: Upgrading). Status is reported in the component's hadoop_service_status property. |
Review the node's Windows and PDW component event log for details. |
| Hadoop Service has an UNKNOWN status. | Yes | Degraded | Warning | This service is reporting that it's in an unknown state. Status is reported in the component's hadoop_service_status property. |
Review the node's Hadoop logs, plus the Windows and PDW component event log, for details. |
| Memory device has a CRITICAL status. | Yes | Failed | Warning | The memory is reporting a critical problem. | A DIMM might need to be replaced. Troubleshooting is required. A server might still be active with some failed RAM, but performance might be affected. Review the node's Windows event log for details. |
| Memory device has a NON-CRITICAL status. | Yes | Degraded | Warning | The memory is reporting a non-critical situation. | This event might point to imminent DIMM failure. Generally, this situation means the DIMM has seen errors, but it's not yet past the threshold to make it a critical/failed status. A server might still be active with some failed RAM, but performance might be affected. You must clear the hardware log to clear the error. Review the node's Windows event log for details. |
| Memory device has a NON-RECOVERABLE status. | Yes | Failed | Warning | The memory reported a non-recoverable problem. | A DIMM might need to be replaced. Troubleshooting is required. A server might still be active with some failed RAM, but performance might be affected. Review the node's Windows event log for details |
| Memory device has a NORMAL status. | No | Operational | Informational | The memory is working normally. | The component previously reported a different status but has since returned to normal. |
| Memory device has an UNKNOWN status. | Yes | Degraded | Warning | Status of the memory couldn't be determined. | The system can't retrieve the health state of the system memory. A DIMM might need to be replaced. Troubleshooting is required. A server might still be active with some failed RAM, but performance might be affected. Review the node's Windows event log for details. |
| Network adapter has a CRITICAL status. | Yes | Degraded | Warning | The network adapter is raising a critical alert for one of the following reasons: - The adapter is offline. - The adapter has been powered off. - The adapter is in an off-duty status. |
The network adapter is in a failed state and might need replacement (which could mean motherboard replacement). Troubleshooting is required. Review the node's Windows event log for details. |
| Network adapter has a NON-CRITICAL status. | Yes | Degraded | Warning | The network adapter is indicating there's a non-critical warning but is still operational. Performance is potentially degraded. | The network adapter has some errors but isn't in a critical state. Because this state might affect performance, troubleshooting is required. Review the node's Windows event log for details. |
| Network adapter has a NON-RECOVERABLE status. | Yes | Failed | Warning | The network adapter is in a non-recoverable status because it was potentially installed in error. | The network adapter is in a failed state and might need replacement (which could mean motherboard replacement). Troubleshooting is required. Review the node's Windows event log for details. |
| Network adapter has a NORMAL status. | No | Operational | Informational | The network adapter is online and running normally. | The component previously reported a different status but has since returned to normal. |
| Network adapter has an UNKNOWN status. | Yes | Degraded | Warning | The status of the network adapter couldn't be determined for one of the following reasons: - The network adapter is in Power Save mode: standby, low power, warning, unknown, or power cycle. - The network adapter hasn't been installed. - The network adapter device reported an unknown status. - The network adapter is in a testing state. |
The system couldn't retrieve the health state of the network adapter. Troubleshooting is required. Review the node's Windows event log for details. |
| Network connection has a CRITICAL status. | Yes | Degraded | Warning | The network connectivity is raising a critical alert for one of the following reasons: - The network is disconnected. - Hardware isn't present. - Hardware has been disabled. - Media is disconnected. - Authentication has failed. - An invalid address was used. - A credential is required but wasn't supplied. |
The network adapter is in a critical state. Review the node's Windows event log for details. |
| Network connection has a NON-CRITICAL status. | Yes | Degraded | Warning | The network is reporting a non-critical state. This status might happen for one of the following reasons: - The network is in a connecting state. - The network is in a disconnecting state. - Network authentication is in process. |
The network adapter is in an unexpected state. If this problem persists or happens multiple times, troubleshooting is required. Review the node's Windows event log for details. |
| Network connection has a NORMAL status. | No | Operational | Informational | The network is connected and working correctly. | The component previously reported a different status but has since returned to normal. |
| Network connection profile is on an expected profile. | No | Operational | Informational | The network is connected and working as an expected profile. The profile is reported in the component's profile_category property. Domain profile is 2, and private profile is 1. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. The loss of a single disk might affect the health of the mirror, so another alert might have occurred for the disk itself. |
| Network connection profile is showing to be on the Public profile. | Yes | Degraded | Warning | The network is reporting that it's on the public profile. The profile is reported in the component's profile_category property. Public profile is reported as 0. This situation might cause communication issues for this node. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Node in a cluster has a CRITICAL status. | Yes | Failed | Error | The clustered node is down. | A server in the cluster is down. Review Failover Cluster Manager on the HST01 VM. |
| Node in a cluster has a NON-CRITICAL status. | Yes | Degraded | Warning | The clustered node is throwing a non-critical alert. One of the following situations might have occurred: the node is in paused state, or the node is in the process of joining the cluster. | The node is in an unexpected state. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Node in a cluster has a NORMAL status. | No | Operational | Informational | The clustered node is up and running. | The component previously reported a different status but has since returned to normal. |
| Node in a cluster has an UNKNOWN status. | Yes | Degraded | Warning | The clustered node is in an unknown state. | The system couldn't retrieve the health state of the node. Troubleshooting is required. Review Failover Cluster Manager on the HST01 VM. |
| Physical Disk has a CRITICAL status. | Yes | Failed | Error | The disk status is critical (vendor status: 2-Unhealthy). The status is reported in the component's phys_disk_status property. The operational status, shown in property phys_disk_oper_status, might provide more information about the problem. Operational status values: 0-The operational status of the physical disk is unknown. 2-OK 3-Degraded 4-Stressed 5-Predictive Failure 6-Error 7-Non-Recoverable Error 8-Starting 9-Stopping 10-Stopped 11-In Service 12-No Contact 13-Lost Communication 15-Dormant 18-Power Mode 0x8004-Failed Media 0x8005-Split 0x8006-Stale Metadata 0x8007-IO Error 0x8008-Corrupt Metadata |
|
| Physical Disk has a NON-CRITICAL status. | Yes | Degraded | Warning | The disk status is indicating there's a non-critical warning but the system is still operational. The status is reported in the component's phys_disk_status property. The operational status, shown in property phys_disk_oper_status, might provide more information about the problem. Operational status values: 0-The operational status of the physical disk is unknown. 2-OK 3-Degraded 4-Stressed 5-Predictive Failure 6-Error 7-Non-Recoverable Error 8-Starting 9-Stopping 10-Stopped 11-In Service 12-No Contact 13-Lost Communication 15-Dormant 18-Power Mode 0x8004-Failed Media 0x8005-Split 0x8006-Stale Metadata 0x8007-IO Error 0x8008-Corrupt Metadata |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. The loss of a single disk might affect the health of the mirror, so another alert might have occurred for the disk itself. |
| Physical Disk has a NORMAL status. | No | Operational | Informational | The disk status is normal. The status is reported in the component's phys_disk_status property. |
|
| Physical Disk has an UNKNOWN status. | Yes | Degraded | Warning | The disk status couldn't be determined (status: 5-Unknown). The status is reported in the component's phys_disk_status property. The operational status, shown in property phys_disk_oper_status, might provide more information about the problem. Operational status values: 0-The operational status of the physical disk is unknown. 2-OK 3-Degraded 4-Stressed 5-Predictive Failure 6-Error 7-Non-Recoverable Error 8-Starting 9-Stopping 10-Stopped 11-In Service 12-No Contact 13-Lost Communication 15-Dormant 18-Power Mode 0x8004-Failed Media 0x8005-Split 0x8006-Stale Metadata 0x8007-IO Error 0x8008-Corrupt Metadata |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. |
| Power Supply has a CRITICAL status. | Yes | Failed | Warning | The power supply is indicating there's a critical error. | The power supply might require replacement. Troubleshooting is required. Power supplies are redundant, so the server might still be active. Review the node's Windows event log for details. |
| Power Supply has a NON-CRITICAL status. | Yes | Operational | Warning | The power supply reported a non-critical problem. | The power supply has reported a problem but isn't in a failed state. This alert might indicate imminent failure. Power supplies are redundant, so a failure might not create a server outage. A hardware error probably needs to be cleared to clear the admin console error. Review the node's Windows event log for details. |
| Power supply has a NON-RECOVERABLE status. | Yes | Failed | Warning | The power supply is in a non-recoverable status. | The power supply might require replacement. Troubleshooting is required. Power supplies are redundant, so the server might still be active. Review the node's Windows event log for details. |
| Power Supply has a NORMAL status. | No | Operational | Informational | The power supply is running normally. | The component previously reported a different status but has since returned to normal. |
| Power supply has an UNKNOWN status. | Yes | Degraded | Warning | The status of the power supply couldn't be determined. | The system couldn't retrieve the health state of the power supply. Power supplies are redundant, so the server might still be active. Troubleshooting is required. Review the node's Windows event log for details. |
| Processor device has a CRITICAL status. | Yes | Failed | Warning | The CPU is reporting a critical problem. | The CPU might need to be replaced. Troubleshooting is required. Review the node's Windows event log for details. |
| Processor device has a NON-CRITICAL status. | Yes | Degraded | Warning | The CPU is reporting a non-critical situation. | The CPU encountered an error but isn't yet in a failed state. This alert might indicate an imminent failure. Review the node's Windows event log for details. |
| Processor device has a NON-RECOVERABLE status. | Yes | Failed | Warning | The CPU reported a non-recoverable problem. | Similar to critical status, the CPU might need to be replaced. Troubleshooting is required. Review the node's Windows event log for details. |
| Processor device has a NORMAL status. | No | Operational | Informational | The CPU is working normally. | The component previously reported a different status but has since returned to normal. |
| Processor device has an UNKNOWN status. | Yes | Degraded | Warning | Status of the CPU couldn't be determined. | The system can't retrieve the health state of a CPU, and further investigation is required. Review the node's Windows event log for details. |
| SAS Host Bus Adapter has a DEGRADED condition. | Yes | Degraded | Warning | The SAS host bus adapter is reporting that the overall condition of the HBA and all of the physical drives that it controls is degraded (vendor status: degraded). Vendor status is reported in the component's hba_device_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| SAS Host Bus Adapter has a FAILED condition. | Yes | Failed | Warning | The SAS host bus adapter is reporting that the overall condition of the HBA is in a failed state, including all of the physical drives that it controls. This condition requires a component to be replaced (vendor status: failed). Vendor status is reported in the component's hba_device_rollup_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| SAS Host Bus Adapter has a NORMAL status. | No | Operational | Informational | The SAS host bus adapter is operating normally (vendor status: ok). Vendor status is reported in the component's hba_device_rollup_status property. |
|
| SAS Host Bus Adapter has an UNKNOWN status. | Yes | Degraded | Warning | The SAS host bus adapter status couldn't be determined (vendor status: other). Vendor status is reported in the component's hba_device_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| SQL Server has a CRITICAL status. | Yes | Non-operational | Error | This service is in a critical state and has stopped working (status: Stopped) or is in a transitional state to be stopped (status: StopPending). Status is reported in the component's sql_server_service_status property. |
Review the node's Windows event log for details. |
| SQL Server has a NORMAL status. | No | Operational | Informational | This service is running normally (status: Running). Status is reported in the component's sql_server_service_status property. |
|
| Storage Enclosure Fan has a DEGRADED status. | Yes | Degraded | Warning | The storage enclosure fan is reporting that it's degraded (vendor status: 10, 15). Vendor status is reported in the component's storage_fan_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Fan has a FAILED status. | Yes | Failed | Warning | The storage enclosure fan is reporting that it's in a failed state. This status requires a component to be replaced (vendor status: 20, 25). Vendor status is reported in the component's storage_fan_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Fan has a NON-RECOVERABLE status. | Yes | Failed | Warning | The storage enclosure fan is reporting that it's in a non-recoverable state. This alert requires a component to be replaced (vendor status: 30). Vendor status is reported in the component's storage_fan_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Fan has an UNKOWN status. | Yes | Degraded | Error | The status of the storage enclosure fan couldn't be determined (vendor status: 0-Unknown). Vendor status is reported in the component's storage_fan_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Fan has a NORMAL status. | No | Operational | Informational | The storage enclosure fan is operating normally (vendor status: 5). Vendor status is reported in the component's storage_fan_status property. |
|
| Storage Enclosure Power Supply has a DEGRADED status. | Yes | Degraded | Warning | The storage enclosure power supply is reporting that it's degraded (vendor status: 10, 15). Vendor status is reported in the component's storage_power_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Power Supply has a FAILED status. | Yes | Failed | Error | The storage enclosure power supply is reporting that it's in a failed state. This state requires a component to be replaced or power to be restored to the device (vendor status: 20, 25). Vendor status is reported in the component's storage_power_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Power Supply has a NON-RECOVERABLE status. | Yes | Failed | Error | The storage enclosure power supply is reporting that it's in a non-recoverable state. This situation requires a component to be replaced (vendor status: 30). Vendor status is reported in the component's storage_power_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Power Supply has an UNKNOWN status. | Yes | Degraded | Warning | The status of the storage enclosure power supply couldn't be determined (vendor status: 0). Vendor status is reported in the component's storage_power_status property. |
Review the node's Windows event log for details, or contact the device manufacturer. |
| Storage Enclosure Power Supply has a NORMAL status. | No | Operational | Informational | The storage enclosure power supply is operating normally (vendor status: 5). Vendor status is reported in the component's storage_power_status property. |
|
| Storage Pool has a CRITICAL status. | Yes | Failed | The storage pool status is critical (vendor status: 2-Unhealthy). The status is reported in the component's storage_pool_status property. The operational status, shown in property storage_pool_oper_status, might provide more information about the problem. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. The loss of a single disk might affect the health of the mirror, so another alert might have occurred for the disk itself. | |
| Storage Pool has a NON-CRITICAL status. | Yes | Degraded | The storage pool status is indicating there's a non-critical warning but the system is still operational (status: 1-Warning). The status is reported in the component's storage_pool_status property. The operational status, shown in property storage_pool_oper_status, might provide more information about the problem. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. The loss of a single disk might affect the health of the mirror, so another alert might have occurred for the disk itself. | |
| Storage Pool has a NORMAL status. | No | Operational | The storage pool status is normal (status: 0-Healthy). The status is reported in the component's storage_pool_status property. |
||
| Storage Pool has an UNKNOWN status. | Optional | Operational | The storage pool status is in an unknown state on this node (status: 5-Unknown). The status is reported in the component's storage_pool_status property. The operational status, shown in property storage_pool_oper_status, might provide more information about the problem. This problem commonly happens when the node querying the storage pool state isn't the owner of the storage pool. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. | |
| Temperature status is CRITICAL. | Yes | Failed | Error | The temperature has reached a critical upper or lower threshold. | The temperature is too high or too low. Continuing at this state might damage or drastically shorten the life of the hardware. Troubleshooting is required. Review the node's Windows event log for details. |
| Temperature status is NON-CRITICAL. | Optional | Degraded | Warning | The temperature has reached a non-critical upper or lower threshold. | The temperature that the server has reported is at a level higher or lower than normal, but it hasn't reached the threshold for critical status. Temperatures outside threshold shorten hardware life. Things that might affect temperature are workload, datacenter temperature/airflow, and cabling restricting server exhaust. Review the node's Windows event log for details. |
| Temperature status is NON-RECOVERABLE. | Yes | Failed | Warning | The temperature is in a non-recoverable status. | The temperature sensor has detected an error from which it can't recover. This issue might be a problem with the temperature or with the temperature module itself. Review the node's Windows event log for details. |
| Temperature status is NORMAL. | No | Operational | Informational | The temperature is normal. | The component previously reported a different status but has since returned to normal. |
| Temperature status is UNKNOWN. | Yes | Degraded | Warning | The status of the temperature couldn't be determined. | The system couldn't retrieve the server temperature. Troubleshooting is required. Review the node's Windows event log for details. |
| Virtual Disk has a CRITICAL status. | Yes | Failed | Error | The Storage Spaces virtual disk status is critical (vendor status: 2-Unhealthy). The status is reported in the component's virtual_disk_status property. The operational status, shown in property virtual_disk_oper_status, might provide more information about the problem. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. The loss of a single disk might affect the health of the mirror, so another alert might have occurred for the disk itself. |
| Virtual Disk has a NON-CRITICAL status. | Yes | Degraded | Warning | The Storage Spaces virtual disk status is indicating there's a non-critical warning but the system is still operational (status: 1-Warning). The status is reported in the component's virtual_disk_status property. The operational status, shown in property virtual_disk_oper_status, might provide more information about the problem. If the virtual disk has moved to another node, review the state of the cluster shared volume's components and move the disks back to the expected owner. The number after the N in the name indicates the expected owner. For example, N01D01 belongs on HSA01. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. The loss of a single disk might affect the health of the mirror, so another alert might have occurred for the disk itself. |
| Virtual Disk has a NORMAL status. | No | Operational | Informational | The Storage Spaces virtual disk status is normal (status: 0-Healthy). The status is reported in the component's virtual_disk_status property. |
|
| Virtual Disk has an UNKNOWN status. | Yes | Operational | Warning | The Storage Spaces virtual disk status couldn't be determined (status: 5-Unknown). The status is reported in the component's virtual_disk_status property. The operational status, shown in property virtual_disk_oper_status, might provide more information about the problem. If the virtual disk has moved to another node, review the state of the cluster shared volume's components and move the disks back to the expected owner. The number after the N in the name indicates the expected owner. For example, N01D01 belongs on HSA01. |
Review the node's events in log Application and service logs\Microsoft\Windows\StorageSpaces-Driver\Operational for further details. |
| Volume free space status is CRITICAL. | Yes | Degraded | Error | Volume free space is critically low. The current volume's used disk space is beyond 90% of total capacity. Clean up unnecessary files/data to ensure normal appliance operation. | The Admin Console reports allocated space and not necessarily used space. You can use DBCC PDW_SHOWSPACEUSED to investigate used versus allocated space. You can also use DBCC SHRINKLOG. There are also DMVs to provide more customizable queries for table size. For more information, see Table size queries. |
| Volume free space status is NON-CRITICAL. | Optional | Operational | Warning | The current volume's used disk space is between 70% and 90% full. Review disk space used on this volume and clean up unnecessary files/data to ensure normal appliance operation. | The Admin Console reports allocated space and not necessarily used space. You can use DBCC PDW_SHOWSPACEUSED to investigate used versus allocated space. You can also use DBCC SHRINKLOG. There are also DMVs to provide more customizable queries for table size. For more information, see Table size queries. |
| Volume free space status is NORMAL. | No | Operational | Informational | There's enough free disk space on this volume. The current volume's used disk space is below 70%. | The component previously reported a different status but has since returned to normal. To identify space and rows that a table consumes, see Table size queries. |
Next steps
Feedback
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see: https://aka.ms/ContentUserFeedback.
Submit and view feedback for