All alerts in this section apply to the block subsystem.
Code | Name | Description | Severity | Repair flow | SNMP Code | SCG symptom ID |
---|---|---|---|---|---|---|
20300001 | LICENSE_EXPIRED | The system license has expired! you can no longer make configuration changes, please install a valid license to resume system operations. | CRITICAL | you can no longer make configuration changes, please install a valid license to resume system operations. | System.License.License_Expired | SIO01.02.0000001 |
20300003 | TRIAL_LICENSE_USED | PowerFlex is using a trial license | MINOR | Purchase a license and install it. | System.License.Trial_License_Used | SIO01.02.0000003 |
20300004 | OBJECT_HAS_OSCILLATING_FAILURES | Oscillating failures reported | MINOR | Check oscillating failures of the component and take action accordingly. If the oscillating failure does not indicate a problem, change the settings of the oscillating failure window to suppress this alert | System.Oscillating_Failures.Object_has_oscillating_failures | SIO01.03.0000001 |
20300005 | OBJECT_HAS_OSCILLATING_NETWORK_FAILURES | There are oscillating network failures. Download network counters for detailed information. | MINOR | Check the oscillating failure report that can be accessed from one of the management interfaces. Check whether there is a problem with the network links, fix, and restart the counters. | System.Oscillating_Failures.OBJECT_HAS_OSCILLATING_NETWORK_FAILURES | SIO01.03.0000002 |
20300006 | GW_CONFIGURATION_INVALID_MDM_CREDENTIALS | No valid MDM credentials are configured in PowerFlex Gateway. | CRITICAL | Configure the MDM credentials in the PowerFlex Gateway using the FOSGWTool. | System.Credentials.GW_CONFIGURATION_INVALID_MDM_CREDENTIALS | SIO01.04.0000001 |
20300007 | GW_REQUIRES_MDM_USER_PW_CHANGE | The MDM user configured in PowerFlex Gateway requires a password change. | CRITICAL | Configure MDM credentials on the PowerFlex Gateway using the FOSGWTool | System.Credentials.GW_REQUIRES_MDM_USER_PW_CHANGE | SIO01.04.0000004 |
20300008 | GW_TOO_OLD | PowerFlex Gateway version is too old. | CRITICAL | Upgrade the PowerFlex Gateway to the same version as the rest of your system. | System.Upgrade.GW_TOO_OLD | SIO01.05.0000002 |
20300009 | MDM_NOT_CLUSTERED | The MDM is not operating in clustered mode. | CRITICAL | MDM cluster was manually set to SINGLE mode. Confirm that this is an expected operation. Working in SINGLE mode is not recommended. Prepare the cluster modules (if needed), and return to CLUSTER mode. | MDM.MDM_Cluster.MDM_Not_Clustered | SIO02.01.0000001 |
2030000a | MDM_FAILS_OVER_FREQUENTLY | MDM fails over frequently. | MINOR | The MDMs frequently swap ownership. No action required. | ||
2030000f | CLUSTER_DEGRADED | The MDM cluster is degraded, and data is not protected. | MAJOR | Check that all MDM cluster nodes are functioning correctly, and fix and replace faulty nodes, if necessary, to return to full protection. | COMPONENTS | |
20300010 | PD_INACTIVE | Inactive Protection Domain. | MINOR | Protection Domain was inactivated by a user command. Confirm that this is an expected operation. This is usually done for maintenance. When maintenance is complete, reactivate the Protection Domain. | MDM.Protection_Domain.Protection_Inactive | SIO02.02.0000001 |
20300011 | STORAGE_POOL_HAS_FAILED_CAPACITY | Storage Pool has failed capacity. | CRITICAL | For the given Storage Pool, for some blocks, both primary and secondary copies are inaccessible. Check and fix the state of all devices in the Storage Pool and all the server's holding devices in the Storage Pool. | MDM.Storage_Pool.Storage_Pool_has_Failed_Capacity | SIO02.04.0000001 |
20300012 | STORAGE_POOL_HAS_DEGRADED_CAPACITY | Storage Pool has degraded capacity | MAJOR | For the given Storage Pool, for some blocks, one of the two copies is inaccessible. Check if a server is offline or if there is another server hardware-related issue. Check if a storage device is down. | MDM.Storage_Pool.Storage_Pool_has_Degraded_Capacity | SIO02.04.0000002 |
20300015 | FAILURE_RECOVERY_CAPACITY_BELOW_THRESHOLD | Failure recovery capacity is below the threshold | MAJOR | The capacity available for recovery in a degraded storage event is lower than the predefined threshold. Replace failed hardware or add more physical storage. | MDM.Storage_Pool.Failure_Recovery_Capacity_Below_Threshold | SIO02.04.0000005 |
20300016 | BACKGROUND_SCANNER_COMPARE_ERROR | Background device scanning has found data conflicts | CRITICAL | Primary and secondary data copies do not match. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | MDM.Storage_Pool.Background_Scanner_Compare_Error | SIO02.04.0000007 |
20300017 | CONFIGURED_SPARE_CAPACITY_SMALLER_THAN_LARGEST_FAULT_UNIT | Configured spare capacity is smaller than the size of the largest Fault Set | CRITICAL | Increase the "spare percentage", configured in the Storage Pool and reserved for failure recovery, so that it is larger than the largest Fault Set in the Storage Pool. | MDM.Storage_Pool.Configured_Spare_Capacity_Smaller_Than_Largest_Fault_Unit | SIO02.04.0000008 |
20300018 | STORAGE_POOL_UNBALANCED | The Storage Pool relies too heavily (over 50%) on capacity from a single SDS or Fault Set. Balance capacity over other SDSs or Fault Sets. | MAJOR | Move some physical disks from the large SDS to the others, or add disks to the smaller SDS in order to approximate the capacity of the large SDS as much as possible. | MDM.Storage_Pool.STORAGE_POOL_UNBALANCED | SIO02.04.0000009 |
20300019 | NOT_ENOUGH_FAULT_UNITS_IN_SP | Storage Pool does not meet the minimum requirement of 3 fault units | MAJOR | Add more SDSs to the Storage Pool to meet the minimum requirement of 3 hosts. | MDM.Storage_Pool.Not_Enough_Fault_Units | SIO02.04.0000010 |
2030001a | UNTRUSTED_CERTIFICATE | There are cluster certificates pending approval. Further details can be found in the MDM view. | MAJOR | Pending for approval certificates can be viewed and approved in the MDM view. | MDM.CERTIFICATE.UNTRUSTED_CERTIFICATE | SIO02.05.0000001 |
2030001b | CERTIFICATE_ABOUT_TO_EXPIRE | Primary MDM Certificate is about to expire | CRITICAL | Install a valid SSL certificate on the MDM before the old one expires | MDM.CERTIFICATE.CERTIFICATE_ABOUT_TO_EXPIRE | SIO02.05.0000002 |
2030001c | MDM_CERTIFICATE_EXPIRED | Primary MDM Certificate has expired | CRITICAL | Install a valid SSL certificate on the host | MDM.CERTIFICATE.MDM_CERTIFICATE_EXPIRED | SIO02.05.0000003 |
2030001d | MDM_SECURE_CONNECTION_DISABLED | Secure connection disabled on MDM | CRITICAL | Enable secure connections on the MDM in order to protect your login information | MDM.CERTIFICATE.MDM_SECURE_CONNECTION_DISABLED | SIO02.05.0000004 |
2030001e | MDM_SELF_SIGNED_CERTIFICATE_NOT_TRUSTED | The self-signed certificate presented by the Primary MDM is not trusted | CRITICAL | Check the certificate, and trust it if you see fit to do so | MDM.CERTIFICATE.MDM_SELF_SIGNED_CERTIFICATE_NOT_TRUSTED | SIO02.05.0000005 |
2030001f | MDM_SECURE_CONNECTION_NOT_SUPPORTED | MDM does not support secure connections | CRITICAL | Check MDM cluster nodes | MDM.CERTIFICATE.MDM_SECURE_CONNECTION_NOT_SUPPORTED | SIO02.05.0000006 |
20300020 | MDM_CERTIFICATE_NOT_YET_VALID | The validity period of the certificate presented by the Primary MDM starts in the future | CRITICAL | The time and date on the computer where the certificate was created is not consistent with the time and date set in the PowerFlex system. Replace the certificate or fix the system time. | MDM.CERTIFICATE.MDM_CERTIFICATE_NOT_YET_VALID | SIO02.05.0000007 |
20300021 | MDM_CA_SIGNED_CERTIFICATE_CA_NOT_TRUSTED | The Certificate Authority that signed the Primary MDM's certificate is not trusted | CRITICAL | Trust the CA certificate if you see fit | MDM.CERTIFICATE.MDM_CA_SIGNED_CERTIFICATE_CA_NOT_TRUSTED | SIO02.05.0000008 |
20300022 | SDS_DISCONNECTED | SDS is disconnected | MAJOR | The SDS service may be down or unreachable over the network. Verify that the SDS service is up and running and that the network is properly connected. | SDS.SDS.SDS_Disconnected | SIO03.01.0000001 |
20300023 | SDS_DISCONNECTS_FREQUENTLY | SDS disconnects frequently | MINOR | The SDS connection is fluctuating due to an unstable network connection. Check the SDS data network connection for Packet Drops, and try to disconnect one of the ports to see if the SDS disconnection issue is resolved by using only one port. If this does not resolve the issue, switch to the other port. If there is still an issue, it may be due to a Faulty NIC, Faulty Switch ports, or a faulty switch. If there is no issue with another switch, the issue was switch-related. Otherwise, the issue may be due to a faulty NIC, which requires NIC replacement. | 1.3x | |
20300024 | SDS_RMCACHE_MEMORY_ALLOCATION_FAILED | Memory allocation for RAM Read Cache failed on SDS | MINOR | The system failed to allocate memory to the SDS RAM Read-Cache. For 32 GB RAM or less, up to 50% of the memory can be allocated for caching. From 32 GB or more, up to 75% of the memory can be allocated for caching. Reduce the configured RAM Read-Cache memory to match the allocation conditions. | SDS.SDS.SDS_Rmcache_Memory_allocation_Failed | SIO03.01.0000003 |
20300025 | DRL_MODE_NON_VOLATILE | DRL mode: Hardened | MINOR | DRL Mode is configured to "Hardened" instead of "Volatile". Both modes are configurable. | SDS.SDS.DRL_MODE_NON_VOLATILE | SIO03.01.0000004 |
2030002e | SDS_IN_MAINTENANCE | SDS is in Maintenance Mode | MINOR | The SDS is currently in Maintenance Mode. Exit Maintenance Mode once maintenance is complete. If an NDU is in progress, ignore this warning. | SDS.SDS.SDS_IN_MAINTENANCE | SIO03.01.0000014 |
2030002f | DEVICE_FAILED | Device failed | MAJOR | The SDS device could not be opened, read from or written to. Validate the device state. Check the cause of the error, and determine if it is a human error or a system malfunction. Check hardware if needed. | SDS.Device.Device_Failed | SIO03.02.0000001 |
20300030 | DEVICE_PENDING_ACTIVATION | Device test is done and device is pending activation | MINOR | The SDS device has been added and tested. Activate the SDS device. | SDS.Device.Device_Pending_Activation | SIO03.02.0000002 |
20300033 | DEVICE_ERROR_ERROR | Device failed: All IO to the device will be stopped, and data will be relocated to another device. | CRITICAL | Check the device, and if necessary, replace it | SDS.Device.Device_ErrorError | SIO03.02.0000005 |
20300034 | DEVICE_ERROR_WARNING | Device failed: All IO to the device will be stopped, and data will be relocated to another device. | MAJOR | Check the device, and if necessary, replace it | SDS.Device.Device_ErrorWarning | SIO03.02.0000006 |
20300035 | DEVICE_ERROR_NOTICE | Device malfunction has been detected. | MINOR | Check the device, and if necessary, replace it | SDS.Device.Device_ErrorNotice | SIO03.02.0000007 |
20300036 | DEVICE_ERROR_INFO | Minor failures have been detected in device performance. | MINOR | Check the device, and if necessary, replace it | SDS.Device.Device_ErrorInfo | SIO03.02.0000008 |
20300037 | SMART_TEMPERATURE_STATE_FAILED_NOW | Disk temperature is above the configured threshold, and may fail soon if no action is taken. | MAJOR | Check the temperature in the server and at the data center. Check if a fan alert is raised in the node. | SDS.Device.SMART_Temperature_State_failed.Now | SIO03.02.0000009 |
20300038 | SMART_TEMPERATURE_STATE_FAILED_IN_PAST | Disk temperature exceeded the configured threshold at some time in the past, indicating a potential issue that may cause problems in the future. | INFORMATION | Disk temperature exceeded the configured threshold at some time in the past, indicating a potential issue that may cause problems in the future. | SDS.Device.SMART_Temperature_State_failed.In.Past | SIO03.02.0000010 |
20300039 | SMART_END_OF_LIFE_STATE_FAILED_NOW | The disk is near the end of its working life, and should be replaced. | MAJOR | Replace the disk. | SDS.Device.SMART_End_Of_Life_State_Failed_Now | SIO03.02.0000011 |
2030003a | SMART_END_OF_LIFE_STATE_FAILED_IN_PAST | The disk generated an end of life status message at some time in the past, indicating a potential issue or that it is no longer working. | INFORMATION | The disk generated an end of life status message at some time in the past, indicating a potential issue or that it is no longer working. | SDS.Device.SMART_End_Of_Life_State_Failed_In_Past | SIO03.02.0000012 |
2030003b | SMART_AGGREGATED_STATE_FAILED_NOW | The disk may be about to fail, or may be operating with reduced performance. | MAJOR | Consider replacing the disk. | SDS.Device.SMART_Aggregated_State_Failed_Now | SIO03.02.0000013 |
2030003c | SMART_AGGREGATED_STATE_FAILED_IN_PAST | The disk generated a failed state message at some time in the past, indicating a potential issue or that it is no longer working. | INFORMATION | The disk generated a failed state message at some time in the past, indicating a potential issue or that it is no longer working. | SDS.Device.SMART_Aggregated_State_Failed_In_Past | SIO03.02.0000014 |
2030003d | SDC_DISCONNECTED | The SDC is either down or unreachable over the network | MAJOR | Verify that the SDC service is up and running, and that the network is properly configured and connected. Note: MDM proxy functionality is running as short term mitigation. | SDC.SDC.SDC_DISCONNECTED | SIO04.01.0000001 |
2030003e | SDC_MAX_COUNT | No more SDCs can be defined on this system; the maximum has been reached | MAJOR | The maximum number of SDCs in the system has been reached (1024^2). | SDC.SDC.SDC_Max_Count | SIO04.01.0000002 |
20300044 | ACCELERATION_MISCONFIGURATION | This Storage Pool contains devices that are not being accelerated | MINOR | This Storage Pool contains devices that are not being accelerated. It is recommended to configure the devices with the same acceleration settings as the Storage Pool's settings. | System.Accleration.MisConfiguration | SIO12.01.0000001 |
20300045 | DEVICE_MEDIA_TYPE_MISMATCH | Device media type mismatch: device {{device}} is an {{actual_type}} device, but its media type has been configured as an {{configured_type}} device | MINOR | Verify the device media type and re-set accordingly. | Device.MediaType.Mismatch | SIO12.01.0000002 |
2030004a | AUTOMATIC_LOGS_COLLECT_NOT_ENOUGH_DISK_SPACE | There is not enough disk space to run automatic log collection | CRITICAL | Delete some files from your disk | System.Automatic_Collect_Logs.NOT_ENOUGH_DISK_SPACE | SIO12.01.0000004 |
2030004b | AUTOMATIC_LOGS_COLLECT_MISSING_ESX_CREDENTIALS | Auto Collect logs started working, while cluster contains 1 or more ESX ips, with no credentials configured | MINOR | Configure ESX credentials in lockbox, or by using the IM option. | System.Automatic_Collect_Logs.MISSING_ESX_CREDENTIALS | SIO12.01.0000005 |
2030004c | DEVICE_ERROR_ACCELERATION | Acceleration device associated with this storage device failed: All I/O to the device will be stopped, and data will be relocated to another device. | CRITICAL | Check the associated acceleration device, and if necessary, replace it. | SDS.Device.Device_ErrorAcceleration | SIO03.02.0000015 |
2030004d | ONE_SDC_DISCONNECTED_FROM_ONE_SDS | One SDC is disconnected from one SDS | CRITICAL | Check the network links between the affected SDS and SDC | System.SDC.One_Sdc_Disconnected_From_One_Sds | SIO01.07.0000001 |
2030004e | ONE_SDC_DISCONNECTED_FROM_ONE_SDS_IP | One SDC is disconnected from one SDS IP address | MINOR | Check the network links between the affected SDC and SDS IP addresses. | System.SDC.One_Sdc_Disconnected_From_One_Sds_Ip | SIO01.07.0000002 |
2030004f | ONE_SDC_DISCONNECTED_FROM_ALL_SDS | One SDC is disconnected from all SDSs | CRITICAL | Check the network links between the affected SDC and all SDSs. | System.SDC.One_Sdc_Disconnected_From_All_Sds | SIO01.07.0000003 |
20300050 | ALL_SDC_DISCONNECTED_FROM_ONE_SDS | All SDCs are disconnected from one SDS | CRITICAL | Check the network links between all SDCs and the affected SDS. | System.SDC.All_Sdc_Disconnected_From_One_Sds | SIO01.07.0000004 |
20300051 | ALL_SDC_DISCONNECTED_FROM_ONE_SDS_IP | All SDCs are disconnected from one SDS IP address | MINOR | Check the network links between all SDCs and the affected SDS IP address. | System.SDC.All_Sdc_Disconnected_From_One_Sds_Ip | SIO01.07.0000005 |
20300052 | ALL_SDC_DISCONNECTED_FROM_ALL_SDS | All SDCs are disconnected from all SDSs | CRITICAL | Check the network links between all SDCs and SDSs. | System.SDC.All_Sdc_Disconnected_From_All_Sds | SIO01.07.0000006 |
20300053 | SDC_MULTIPLE_DISCONNECTIONS_FROM_SDS | Disconnected network links between SDCs and SDSs. | CRITICAL | Check the network links between all SDCs and SDSs. | System.SDC.Sdc_Multiple_Disconnections_From_Sds | SIO01.07.0000007 |
20300054 | ONE_SDC_DISCONNECTED_FROM_ONE_SDR | One SDC is disconnected from one SDR | MINOR | Check the network links between the affected SDR and SDC | System.SDC.One_Sdc_Disconnected_From_One_Sdr | SIO01.07.0000001 |
20300055 | ONE_SDC_DISCONNECTED_FROM_ONE_SDR_IP | One SDC is disconnected from one SDR IP address | MINOR | Check the network links between the affected SDC and SDR IP addresses. | System.SDC.One_Sdc_Disconnected_From_One_Sdr_Ip | SIO01.07.0000002 |
20300056 | ONE_SDC_DISCONNECTED_FROM_ALL_SDR | One SDC is disconnected from all SDRs | MINOR | Check the network links between the affected SDC and all SDRs. | System.SDC.One_Sdc_Disconnected_From_All_Sdr | SIO01.07.0000003 |
20300057 | ALL_SDC_DISCONNECTED_FROM_ONE_SDR | All SDCs are disconnected from one SDR | MINOR | Check the network links between all SDCs and the affected SDR. | System.SDC.All_Sdc_Disconnected_From_One_Sdr | SIO01.07.0000004 |
20300058 | ALL_SDC_DISCONNECTED_FROM_ONE_SDR_IP | All SDCs are disconnected from one SDR IP address | MINOR | Check the network links between all SDCs and the affected SDR IP address. | System.SDC.All_Sdc_Disconnected_From_One_Sdr_Ip | SIO01.07.0000005 |
20300059 | ALL_SDC_DISCONNECTED_FROM_ALL_SDR | All SDCs are disconnected from all SDRs | MINOR | Check the network links between all SDCs and SDRs. | System.SDC.All_Sdc_Disconnected_From_All_Sdr | SIO01.07.0000006 |
2030005a | SDC_MULTIPLE_DISCONNECTIONS_FROM_SDR | Disconnected network links between SDCs and SDRs. | MINOR | Check the network links between all SDCs and SDRs. | System.SDC.Sdc_Multiple_Disconnections_From_Sdr | SIO01.07.0000007 |
2030005b | ONE_SDR_DISCONNECTED_FROM_ONE_SDS | One SDR is disconnected from one SDS | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.One_Sdr_Disconnected_From_One_Sds | SIO01.07.0000001 |
2030005c | ONE_SDR_DISCONNECTED_FROM_ONE_SDS_IP | One SDR is disconnected from one SDS IP address | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.One_Sdr_Disconnected_From_One_Sds_Ip | SIO01.07.0000002 |
2030005d | ONE_SDR_DISCONNECTED_FROM_ALL_SDS | One SDR is disconnected from all SDSs | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.One_Sdr_Disconnected_From_All_Sds | SIO01.07.0000003 |
2030005e | ALL_SDR_DISCONNECTED_FROM_ONE_SDS | All SDRs are disconnected from one SDS | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.All_Sdr_Disconnected_From_One_Sds | SIO01.07.0000004 |
2030005f | ALL_SDR_DISCONNECTED_FROM_ONE_SDS_IP | All SDRs are disconnected from one SDS IP address | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.All_Sdr_Disconnected_From_One_Sds_Ip | SIO01.07.0000005 |
20300060 | ALL_SDR_DISCONNECTED_FROM_ALL_SDS | All SDRs are disconnected from all SDSs | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.All_Sdr_Disconnected_From_All_Sds | SIO01.07.0000006 |
20300061 | SDR_MULTIPLE_DISCONNECTIONS_FROM_SDS | Disconnected network links between SDRs and SDSs. | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.SDR.Sdr_Multiple_Disconnections_From_Sds | SIO01.07.0000007 |
20300062 | ONE_SDR_DISCONNECTED_FROM_ONE_SDR | One SDR is disconnected from one SDR | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.One_Sdr_Disconnected_From_One_Sdr | SIO01.17.0000001 |
20300063 | ONE_SDR_DISCONNECTED_FROM_ONE_SDR_IP | One SDR is disconnected from one SDR IP address | MINOR | CCheck the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.One_Sdr_Disconnected_From_One_Sdr_Ip | SIO01.17.0000002 |
20300064 | ONE_SDR_DISCONNECTED_FROM_ALL_SDR | One SDR is disconnected from all SDRs | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.One_Sdr_Disconnected_From_All_Sdr | SIO01.17.0000003 |
20300065 | ALL_SDR_DISCONNECTED_FROM_ONE_SDR | All SDRs are disconnected from one SDR | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.All_Sdr_Disconnected_From_One_Sdr | SIO01.17.0000004 |
20300066 | ALL_SDR_DISCONNECTED_FROM_ONE_SDR_IP | All SDRs are disconnected from one SDR IP address | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.All_Sdr_Disconnected_From_One_Sdr_Ip | SIO01.17.0000005 |
20300067 | ALL_SDR_DISCONNECTED_FROM_ALL_SDR | All SDRs are disconnected from all SDRs | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.All_Sdr_Disconnected_From_All_Sdr | SIO01.17.0000006 |
20300068 | SDR_MULTIPLE_DISCONNECTIONS_FROM_SDR | Disconnected network links between SDRs and SDRs. | MINOR | Check the wire connectivity, IP addresses and access between the SDR IP addresses at both source and target | System.Peer_MDM.Sdr_Multiple_Disconnections_From_Sdr | SIO01.17.0000007 |
20300069 | SDC_NOT_APPROVED | This SDC has not been approved | MINOR | Add the IP address for this SDC to the list of approved IP addresses. | System.SDC.Sdc_Not_Approved | SIO01.07.0000008 |
2030006a | SDC_DOES_NOT_HAVE_APPROVED_IPS | This SDC does not have an approved IP address | MINOR | Update the list of approved IP addresses for this SDC. | System.SDC.Sdc_Does_Not_Have_Approved_Ips | SIO01.07.0000009 |
2030006b | SNAPSHOT_POLICY_PAUSED | Policy has been paused | MINOR | Policy has been paused. You can resume policy. | SnapshotPolicy.Snapshot_Policy_Paused | SIO13.01.0000001 |
2030006c | SNAPSHOT_POLICY_LAST_AUTO_SNAPSHOT_FAILURE_IN_FIRST_LEVEL | Auto snapshot creation failed | MINOR | Snapshotpolicy.lastAutoSnapshotFailureInFirstLevel | SIO13.01.0000002 | |
20300072 | VTREES_PAUSED_MIGRATION_ERROR | Multiple V-Tree migrations are paused due to internal error | MAJOR | MDM.Storage_Pool.VTrees_Paused_Migration_Error | SIO02.04.0000015 | |
20300073 | VTREES_PAUSED_INACTIVE_PROTECTION_DOMAIN | Multiple V-Tree migrations are paused as either the source or destination Protection Domain is inactive | MINOR | Activate the Protection Domain to resume the migration | MDM.Protection_Domain.VTrees_Paused_Inactive_Protection_Domain | SIO02.02.0000002 |
20300074 | VTREES_PAUSED_DEGRADED_CAPACITY_IN_PROTECTION_DOMAIN | Multiple V-Tree migrations are paused as the Protection Domain has degraded capacity | MAJOR | Resolve the issue causing the degraded capacity to resume the migration | MDM.Protection_Domain.VTrees_Paused_Degraded_Capacity_In_Protection_Domain | SIO02.02.0000003 |
20300075 | VTREES_PAUSED_NO_SPACE_IN_DESTINATION_STORAGE_POOL | Multiple V-Tree migrations are paused as there is not enough space in this destination Storage Pool | MAJOR | Add capacity or remove volume to resume the migration | MDM.Storage_Pool.VTrees_Paused_No_Space_In_Destination_Storage_Pool | SIO02.04.0000016 |
20300076 | VTREES_PAUSED_UNAVAILABLE_CAPACITY_IN_SOURCE_STORAGE_POOL | Multiple V-Tree migrations are paused as there is unavailable capacity in the this source Storage Pool | MAJOR | Resolve the issue causing the unavailable capacity to resume the migration | MDM.Storage_Pool.VTrees_Paused_Unavailable_Capacity_In_Source_Storage_Pool | SIO02.04.0000017 |
20300077 | NET_CAPACITY_HIGH_USAGE | The Storage Pool has reached a high threshold for device capacity utilization | MAJOR | Remove unneeded volumes and snapshots, if possible, or add devices to the Storage Pool | MDM.Storage_Pool.Net_Capacity_High_Usage | SIO02.04.0000018 |
20300078 | NET_CAPACITY_CRITICAL_USAGE | The Storage Pool has reached a critical threshold for device capacity utilization | CRITICAL | Remove unneeded volumes and snapshots, if possible, or add devices to the Storage Pool | MDM.Storage_Pool.Net_Capacity_Critical_Usage | SIO02.04.0000019 |
20300079 | NET_CAPACITY_FULL_USAGE | The Storage Pool physical capacity is full and cannot serve new write requests | CRITICAL | Remove unneeded volumes and snapshots, if possible, or add devices to the Storage Pool | MDM.Storage_Pool.Net_Capacity_Full_Usage | SIO02.04.0000020 |
2030007a | USER_DATA_HIGH_USAGE | The Storage Pool has reached a high threshold for user data capacity utilization | MAJOR | Remove unneeded volumes and snapshots, if possible, or add devices to the Storage Pool | MDM.Storage_Pool.User_Data_High_Usage | SIO02.04.0000021 |
2030007b | USER_DATA_CRITICAL_USAGE | The Storage Pool has reached a critical threshold for user data capacity utilization | CRITICAL | Remove unneeded volumes and snapshots, if possible, or add devices to the Storage Pool | MDM.Storage_Pool.User_Data_Critical_Usage | SIO02.04.0000022 |
2030007c | USER_DATA_FULL_USAGE | The Storage Pool user data capacity is full and cannot serve new write requests | CRITICAL | Remove unneeded volumes and snapshots, if possible, or add devices to the Storage Pool | MDM.Storage_Pool.User_Data_Full_Usage | SIO02.04.0000023 |
2030007d | VTAS_CRITICAL_USAGE_CAPACITY_LIMIT | The VTree address space allocated for this Storage Pool is almost full. You may not be able to create new volumes in this Storage Pool | MINOR | Consider adding capacity to the Storage Pool or removing some vtrees from the Storage Pool | MDM.Storage_Pool.VTAS_Critical_Usage_Capacity_Limit | SIO02.04.0000025 |
2030007e | VTAS_FULL_USAGE_CAPACITY_LIMIT | The VTree address space allocated for this Storage Pool is full. You cannot create new volumes, or enlarge volumes capacity in this Storage Pool | MINOR | Consider adding capacity to the Storage Pool or removing some vtrees from the Storage Pool | MDM.Storage_Pool.VTAS_Full_Usage_Capacity_Limit | SIO02.04.0000026 |
2030007f | VTAS_CRITICAL_USAGE_STORAGE_POOL_LIMIT | The VTree address space allocated for this Storage Pool is almost full. You may not be able to create new volumes in this Storage Pool | MINOR | Consider removing some vtrees from the Storage Pool | MDM.Storage_Pool.VTAS_Critical_Usage_Storage_Pool_Limit | SIO02.04.0000027 |
20300080 | VTAS_FULL_USAGE_STORAGE_POOL_LIMIT | The VTree address space allocated for this Storage Pool is full. You cannot create new volumes, or enlarge volumes capacity in this Storage Pool | MINOR | Consider removing some vtrees from the Storage Pool | MDM.Storage_Pool.VTAS_Full_Usage_Storage_Pool_Limit | SIO02.04.0000028 |
20300081 | SYSTEM_VTAS_CRITICAL_USAGE | The VTree address space allocated in the system is almost full. You may not be able to create new volumes in the system | MINOR | Consider removing some vtrees from the system | System.VTAS.System_VTAS_Critical_Usage | SIO01.07.0000001 |
20300082 | SYSTEM_VTAS_FULL_USAGE | The VTree address space allocated for the system is full. You cannot create new volumes, or enlarge volumes capacity in the system | MAJOR | Consider removing some vtrees from the system | System.VTAS.System_VTAS_Full_Usage | SIO01.07.0000002 |
20300083 | SP_DEVICE_MEDIA_TYPE_MISMATCH | The Storage Pool contains one or more devices with unexpected media types | MINOR | Please update the Storage Pool media type or replace the mismatched devices. | MDM.Storage_Pool.Device_Media_Type_Mismatch | SIO02.04.0000029 |
20300086 | PROTECTION_DOMAIN_HAS_UNBALANCED_DATA_IPS | The Protection Domain has unbalanced data path support. | MINOR | Verify consistent Data Path configurations for all Host SDSs that support this Protection Domain | MDM.Protection_Domain.Protection_Unbalanced | SIO02.02.0000004 |
20300088 | DEVICE_ERROR_UNRECOVERABLE | An unrecoverable state has been reported on the device: All I/O to the device will be stopped, and the data will be relocated to another device. The SDS does not recognize the internal signature on the device. | CRITICAL | An unrecoverable state has been reported on the device: All I/O to the device will be stopped, and the data will be relocated to another device. The SDS does not recognize the internal signature on the device. | SDS.Device.Device_ErrorUNRecoverable | SIO03.02.0000016 |
20300089 | VTREE_PAUSED_SDS_IN_MAINTENANCE_IN_PROTECTION_DOMAIN | The V-Tree Migration is paused because either the source or destination Protection Domain has at least one SDS in Maintenance Mode | MINOR | Exit the relevant SDSs from Maintenance Mode | Storage_Pool.Volume.VTree_Paused_Sds_In_Maintenance_In_Protection_Domain | SIO14.01.0000006 |
2030008a | VTREES_PAUSED_SDS_IN_MAINTENANCE_IN_PROTECTION_DOMAIN | Multiple V-Tree migrations are paused because either the source or destination Protection Domain has at least one SDS in Maintenance Mode | MINOR | Exit the relevant SDSs from Maintenance Mode | MDM.Protection_Domain.VTrees_Paused_Sds_In_Maintenance_In_Protection_Domain | SIO02.02.0000005 |
2030008d | DEVICE_ERROR_MISMATCH | Media type mismatch: HDD media type is not supported in storage pools with fine granularity data layout | CRITICAL | Media type mismatch: HDD media type is not supported in storage pools with fine granularity data layout | SDS.Device.Device_ErrorTypeMismatch | SIO03.02.0000017 |
2030008e | NVDIM_OVERBOOKING | Your system has insufficient NVDIMM capacity on {{sds_name}} to support future version upgrades. Required NVDIMM capacity for the upgrade is {{required_capacity}} MB. Contact your account manager for more information. | MAJOR | Increase the NVDIMM capacity or reduce the SDS FG capacity before you upgrade | SDS.Device.NVDIM_OVERBOOKING | SIO03.02.0000015 |
2030008f | JOURNAL_CAPACITY_ABOVE_CRITICAL_THRESHOLD | Journal Capacity above critical threshold | CRITICAL | Check the link status, the RCG freeze apply state, and check if either system had been upgraded to a non-compatible version. Consider increasing journal size. Consider increasing the WAN bandwidth. | System.ProtectionDomain.JOURNAL_CAPACITY_ABOVE_CRITICAL_THRESHOLD | SIO16.01.0000001 |
20300090 | JOURNAL_CAPACITY_ABOVE_VERY_HIGH_THRESHOLD | Journal Capacity above very high threshold | MAJOR | Check the link status, the RCG freeze apply state, and check if either system had been upgraded to a non-compatible version. Consider increasing journal size. Consider increasing the WAN bandwidth. | System.ProtectionDomain.JOURNAL_CAPACITY_ABOVE_VERY_HIGH_THRESHOLD | SIO16.01.0000002 |
20300091 | JOURNAL_CAPACITY_ABOVE_HIGH_THRESHOLD | Journal Capacity above high threshold | MINOR | Check the link status, the RCG freeze apply state, and check if either system had been upgraded to a non-compatible version. Consider increasing journal size. Consider increasing the WAN bandwidth. | System.ProtectionDomain.JOURNAL_CAPACITY_ABOVE_HIGH_THRESHOLD | SIO16.01.0000003 |
20300092 | JOURNAL_CAPACITY_ABOVE_WARNING_THRESHOLD | Journal Capacity above warning threshold | MINOR | Check the link status, the RCG freeze apply state, and check if either system had been upgraded to a non-compatible version. Consider increasing journal size. Consider increasing the WAN bandwidth. | System.ProtectionDomain.JOURNAL_CAPACITY_ABOVE_WARNING_THRESHOLD | SIO16.01.0000004 |
20300093 | RCG_REMOTE_CONSISTENCY_GROUP_IS_INCONSISTENT | The replication is in inconsistent mode | MINOR | Check that the lag between source and target is small and change the Remote Consistency Group to consistent mode | System.RCG.RCG_REMOTE_CONSISTENCY_GROUP_IS_INCONSISTENT | SIO16.01.0000005 |
20300094 | RCG_RPO_EXCEEDED | Remote Consistency Group RPO Exceeded | MINOR | Check Journal capacity, link status and RCG state | System.RCG.RCG_RPO_EXCEEDED | SIO16.01.0000006 |
20300095 | PEER_SYSTEM_DISCONNECTED | Peer system MDM disconnected | MINOR | Check the connectivity between the local MDM And peer MDM. Check whether either system had been upgraded to a non-compatible version. | System.PEER_SYSTEM_DISCONNECTED | SIO16.01.0000007 |
20300096 | PEER_SYSTEM_INCOMPATIBLE_VERSION | A replication peer system version is incompatible with the local system version. Impacted RCGs will be paused. | MAJOR | Perform an upgrade to bring the systems to compatible versions. If upgrade is not possible, consider removing the relevant RCGs. | System.PEER_SYSTEM_INCOMPATIBLE_VERSION | SIO16.01.0000008 |
20300097 | DEVICE_AT_FAULT | Device at fault | MAJOR | The SDS device has experienced a persistent fault, and is undergoing a managed re-deployment. When re-deployment is complete, verify that the device is operating normally. If problems persist, check the cause of the error, and determine if it is a human error or a system malfunction. Check hardware if needed. | SDS.DEVICE.DEVICE_AT_FAULT | SIO03.03.0000001 |
20300098 | FIRST_UNLICENSED_ALERT_THRESHOLD | The system is using a license which will expire in {{days}} days, please install a valid license soon. | MAJOR | In order to maintain system operational, please install a valid license | System.Licence.FIRST_UNLICENSED_ALERT_THRESHOLD | SIO02.03.0000001 |
20300099 | SECOND_UNLICENSED_ALERT_THRESHOLD | The system is using a license which is about to expire in 1 day, please install a valid license. | CRITICAL | In order to maintain system operational, please install a valid license | System.Licence.SECOND_UNLICENSED_ALERT_THRESHOLD | SIO02.03.0000002 |
2030009a | THIRD_UNLICENSED_ALERT_THRESHOLD | The system license has expired! you will not be able to make configuration changes, please install a valid license. | CRITICAL | In order to maintain system operational, please install a valid license | System.Licence.THIRD_UNLICENSED_ALERT_THRESHOLD | SIO02.03.0000003 |
2030009d | REPLICATION_FAILED | The Protection Domain has failed replication volumes | CRITICAL | Identify the reason for the replication failure before re-creating the replication. | System.REPLICATION_FAILED | SIO16.01.0000010 |
2030009e | SDR_NOT_OPERATIONAL | The SDR is not operational. Reason: {{reason}} | MAJOR | Check for device and server error in the protection domain which may lead to journal volume availability issues. | System.SDR.SDR_NOT_OPERATIONAL | SIO16.01.0000009 |
2030009f | JOURNAL_ALLOCATION_EXCEEDS_RATIO | The Journal allocation in Storage Pool exceeds the Journal capacity ratio | MAJOR | Consider increasing the journal ratio in this or another pool | System.StoragePool.JOURNAL_ALLOCATION_EXCEEDS_RATIO | SIO16.01.0000011 |
203000a0 | SDR_IN_MAINTENANCE | The SDR is in Maintenance Mode | MINOR | The SDR is currently in Maintenance Mode. Exit Maintenance Mode once maintenance is complete. If an NDU is in progress, ignore this warning. | SDR.SDR.SDR_IN_MAINTENANCE | |
203000a1 | SDR_UPDATED_BEFORE_SDS | An SDR was updated before updates of all SDSes had completed | MAJOR | Finish the update of all SDSes in order to allow the updated SDR to join the cluster | SDR.SDR.SDR_UPDATED_BEFORE_SDS | SIO01.17.0000008 |
203000a2 | DEVICE_READ_ERROR_MINOR | Background read from the SDS device failed. Data may be corrected from the other copy. No action is required. | MINOR | Read from the SDS device failed. Data was corrected from the other copy. No action is required, but note that the device might be faulty. | SDS.Device.READ_ERROR_MINOR | SIO15.03.0000001 |
203000a3 | DEVICE_READ_ERROR_MAJOR | Background read from the SDS device failed. Data may be corrected from the other copy. No action is required. | MAJOR | Read from the SDS device failed. Data was corrected from the other copy. No action is required, but note that the device might be faulty. | SDS.Device.READ_ERROR_MAJOR | SIO15.03.0000002 |
203000a4 | DEVICE_READ_ERROR_CRITICAL | Background read from the SDS device failed. Data may be corrected from the other copy. There are too many device failures, please replace it. | CRITICAL | SDS device suffered more than FG/MG_DEVICE_ERROR_CRITICAL read failures. Replace the physical device. | SDS.Device.READ_ERROR_CRITICAL | SIO15.03.0000003 |
203000a5 | COMPARE_ERROR_MINOR | Background RAID scanning has found data conflicts. Data may be recovered automatically. No action required. | MINOR | RAID errors were found and corrected. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.COMPARE_ERROR_MINOR | SIO15.03.0000004 |
203000a6 | COMPARE_ERROR_MAJOR | Background RAID scanning has found data conflicts. Data may be recovered automatically. No action required. | MAJOR | RAID errors were found and corrected. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.COMPARE_ERROR_MAJOR | SIO15.03.0000005 |
203000a7 | COMPARE_ERROR_CRITICAL | Background RAID scanning has found data conflicts. Data may be recovered automatically. No action required. | CRITICAL | More than COMPARE_ERROR_CRITICAL RAID errors were encountered. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.COMPARE_ERROR_CRITICAL | SIO15.03.0000006 |
203000a8 | UNFIXED_READ_ERROR_MAJOR | There are failed SDS device reads pending a fix. No action is required. | MAJOR | There are several unfixed device read errors. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.UNFIXED_READ_ERROR_MAJOR | SIO15.03.0000007 |
203000a9 | UNFIXED_READ_ERROR_CRITICAL | There are failed SDS device reads pending a fix. No action is required. | CRITICAL | There is a large number of unfixed device read errors. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.UNFIXED_READ_ERROR_CRITICAL | SIO15.03.0000008 |
203000aa | UNFIXED_COMPARE_ERROR_MAJOR | There are RAID data conflicts pending a fix. No action required. | MAJOR | There are several unresolved RAID errors. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.UNFIXED_COMPARE_ERROR_MAJOR | SIO15.03.0000009 |
203000ab | UNFIXED_COMPARE_ERROR_CRITICAL | There are RAID data conflicts pending a fix.No action required. | CRITICAL | There is a large number of unresolved RAID errors. Check the volumes running on the Storage Pool for any consistency issues. Contact Customer Support for assistance. | SDS.Device.UNFIXED_COMPARE_ERROR_CRITICAL | SIO15.03.0000010 |
203000ac | MAINTENANCE_ABORTED_BY_SYSTEM | Enter PMM action on the SDS was aborted by the System. the SDS maintenance state is 'Auto aborted by the system' | MAJOR | PMM was aborted in order to avoid out of capacity condition. Please exit or enter PMM to clear the alert. | SDS.SDS.MAINTENANCE_ABORTED_BY_SYSTEM | SIO01.17.0000009 |
203000ad | ONE_PORT_FLAPPING | The path between {{first_ip}} and {{second_ip}} is disqualified | MINOR | Please refer to the cli port flapping report for more information | System.ONE_PORT_FLAPPING | SIO01.18.0000001 |
203000ae | FEW_PORTS_FLAPPING | The paths between {{ip}} are disqualified | MAJOR | Please refer to the cli port flapping report for more information | System.FEW_PORTS_FLAPPING | SIO01.18.0000003 |
203000af | TOO_MANY_PORTS_FLAPPING | Multiple paths between many components are disqualified. For instance: {{ip}}, etc. | MAJOR | Please refer to the cli port flapping report for more information | System.TOO_MANY_PORTS_FLAPPING | SIO01.18.0000005 |
203000b0 | RCG_CONSISTENT_IMAGE_TOO_LARGE | The RCG consistent image is too large to be consumed by the destination in one piece. | MAJOR | PMM was aborted in order to avoid out of capacity condition. Please exit or enter PMM to clear the alert. | System.RCG.RCG_CONSISTENT_IMAGE_TOO_LARGE | SIO01.19.0000001 |
203000b1 | REPLICATION_CONSISTENT_IMAGES_TOO_LARGE | Multiple RCGs of the PD have consistent images that are too large to be consumed by the destination in one piece. | CRITICAL | Check RCGs of the PD. For affected RCGs use Inconsistent Apply to authorize handling of the consistent image in pieces. Consider using a snapshot to save the existing destination image before authorizing Inconsistent Apply. Check the reason for the too large image. This may be multiple SDR failures or a long connectivity outage between the source or destination. Another option is IO load higher than the replication is able to consume. | System.ProtectionDomain.REPLICATION_CONSISTENT_IMAGES_TOO_LARGE | SIO01.19.0000003 |
203000b2 | SDC_CANNOT_CONNECT_TO_SOME_SDSS | The SDC cannot connect to some SDSs. It may still work as expected using SDS proxies. Verify the cause of the SDC disconnections, and fix them. | MINOR | The SDC cannot connect to some SDSs. This usually indicates a network error. It is not critical since the SDC may continue working using SDS proxies, but it is advisable to check connection status using the query_disconnections command. | System.SDC.Sdc_Cannot_Connect_to_Some_Sdss | SIO01.07.0000010 |