All alerts in this section apply to the block subsystem.
Code | Name | Description | Severity | System impact | Repair flow | SNMP code | SCG symptom ID |
---|---|---|---|---|---|---|---|
20010100 | HOST_CONNECTIVITY_DOES_NOT_MATCH_GOAL | Host connectivity does not match goal | MINOR | The host connectivity may not provide resiliency or load balancing. | Verify the networking between the host and the system and ensure that the host can reach all the SDTs in the relevant PDs. If the network is healthy and configured correctly, perform re-discovery on the host. | nvme-hosts.connectivity-below-goal | |
20010101 | HOST_LOW_POTENTIAL_PATH_RESILIENCE_IN_A_PROTECTION_DOMAIN | The host path resiliency requirements cannot be satisfied in a protection domain from which the host has a mapped volume | MINOR | The host configured requirement for #paths cannot be satisfied in a protection domain. | Add SDTs to the relevant PD to increase the connectivity options. | nvme-hosts.low-resilience | PFX00019.0000101 |
20010102 | HOST_CONNECTIVITY_NOT_RESILIENT | Host connectivity is not resilient | MAJOR | A host has a non-resilient connectivity. A subsequent failure can result in the host experiencing data unavailability. | Verify the networking between the host and the system and ensure that the host can reach all the SDTs in the relevant PDs. Verify the health of the SDTs | nvme-hosts.connectivity-not-resilient | PFX00019.0000102 |
20010103 | HOST_DISCONNECTED | Host is disconnected | MAJOR | A host is disconnected from the system. | Verify the networking between the host and the system and ensure that the host can reach all the SDTs in the relevant PDs. Verify the health of the SDTs | nvme-hosts.disconnected | PFX00019.0000103 |
20010150 | SDT_LOAD_UNBALANCED | SDT load is unbalanced | MINOR | The system IO performance may be limited by the overloaded SDTs. | Consider requesting the system to recalculate the hosts connectivity goals. This is only required if a performance issue potentially caused by the overloaded SDT was identified. After new connectivity goals are calculated requesting re-discovery on the hosts is required for it to become effective. | protection-domains.sdt-load-unbalanced | PFX00016.0000150 |
20010200 | ONE_SDT_DISCONNECTED_FROM_ONE_STORAGE_BACKEND_COMPONENT | One SDT internal link to an SDS or SDR is disconnected | MINOR | The hosts connected to the SDTs will not be able to use their paths to those SDTs. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target. | mdms.sdt-disconnection-one-to-one | |
20010201 | ONE_SDT_DISCONNECTED_FROM_ALL_STORAGE_BACKEND_COMPONENTS | One SDT's internal link to all SDSs and SDRs is disconnected | MINOR | The hosts connected to the SDTs will not be able to use their paths to those SDTs. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target. | mdms.sdt-disconnection-one-to-all | PFX00002.0000201 |
20010202 | ALL_SDTS_DISCONNECTED_FROM_ONE_STORAGE_BACKEND_COMPONENT | All SDTs' internal link to an SDS or SDR is disconnected | MAJOR | The hosts connected to the SDTs will not be able to use their paths to those SDTs. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target. | mdms.sdt-disconnection-all-to-one | PFX00002.0000202 |
20010203 | ALL_SDTS_DISCONNECTED_FROM_ALL_STORAGE_BACKEND_COMPONENTS | All SDTs' internal link to all SDSs and SDRs is disconnected | CRITICAL | The hosts connected to the SDTs will not be able to use their paths to those SDTs. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target. | mdms.sdt-disconnection-all-to-all | PFX00002.0000203 |
20010204 | SDT_MULTIPLE_DISCONNECTIONS_FROM_STORAGE_BACKEND_COMPONENTS | Multiple SDTs' internal link to multiple SDSs and/or multiple SDRs is disconnected | MAJOR | The hosts connected to the SDTs will not be able to use their paths to those SDTs. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target. | mdms.sdt-disconnection-multiple | PFX00002.0000204 |
20010205 | CONNECTIVITY_IS_FLAPPING | Connectivity is flapping | MINOR | IOs directed through that server may experience performance issues. | Check the network | mdms.port-flap | PFX00002.0000205 |
20010300 | SDT_PORT_HEALTH_ERROR | The SDT identified a port health issue | MINOR | Hosts connected through the failed port will lose the relevant paths. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target | sdts.port-health-error | |
20010301 | SDT_NOT_CONNECTED_TO_HOST | The SDT has no host connections even though it is included in a connectivity goal | MINOR | The SDT may have connectivity issues preventing hosts from connecting. | Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target | sdts.no-host-connection | PFX00007.0000301 |
20010302 | SDT_DECOUPLED_FROM_SYSTEM | The SDT is permanently disconnected from all NVMe/TCP connections. | MINOR | All NVMe/TCP paths through that SDT are lost. | Option1: Check the wire connectivity, IP addresses and access between the SDT IP addresses at both source and target. Option2: the local NVMe initiator used by the Data Mobility feature is not responding, to recover a graceful reboot cycle is required, refer to PowerFlex Monitor guide to check if applicable and perform a graceful reboot cycle. | sdts.decoupled | PFX00007.0000302 |
20010303 | SDT_IN_MAINTENANCE_MODE | The SDT is in Maintenance Mode | MINOR | All hosts paths through that SDT are disconnected for the term of the maintenance. | The SDT is currently in Maintenance Mode. Exit Maintenance Mode once maintenance is complete. If an NDU is in progress, ignore this warning. | sdts.maintenance-mode | |
20010309 | SDS_EXCEEDED_IMM_TIMEOUT | {{sds_title}} (ID {{sds_id}}) is running with Instant Maintenance Mode (IMM) for more than {{threshold}} minutes, this places the system at risk for a 2nd failure of another node and might lead to Data Unavailability. Refer to PowerFlex guidelines for remediation recommendation | CRITICAL | System has a node in Instant Maintenace Mode over the allowed time - High risk of Data Unavailability in case of 2nd failure. | Admin should exit instant maintenance mode gracefully to force a rebuild, if you can't exit IMM, contact support for guidance. | sdses.sds-exceeded-imm-timeout | PFX00003.0000309 |
20010450 | SYSTEM_REACHED_MAXIMAL_PERSISTENT_DISCOVERY_CONTROLLERS | The System has reached maximal number of persistent discovery controllers | MINOR | No more persistent discovery controllers can be connected to system. | Disconnect the unused persistent discovery controllers from the system | mdms.max-persistent-discovery-controllers | |
20010451 | SDT_REACHED_MAXIMAL_PERSISTENT_DISCOVERY_CONTROLLERS | The SDT has reached maximal number of persistent discovery controllers | MINOR | No more persistent discovery controllers can be connected to SDT. | Disconnect the unused persistent discovery controllers from the SDT | sdts.max-persistent-discovery-controllers | |
20010452 | SNAPSHOT_COPY_TASK_FAILED | Data mobility snapshot copy task failed | MAJOR | Copy task cannot proceed. | Troubleshoot why the task failed, fix the issue, restart it. | sdts.snapshot-copy-task-failed | PFX00007.0000452 |
20010453 | SNAPSHOT_COPY_TASK_STUCK | Data mobility snapshot copy task is stuck | MAJOR | Copy task cannot proceed. | Troubleshoot why the task failed, fix the issue, restart it. | sdts.snapshot-copy-task-stuck | PFX00007.0000453 |
20010454 | MDM_MNO_CERTIFICATE_DUE_TO_EXPIRE | Renew the MDM M&O certificate by running the appropriate command, see user manual for details | mdm-cluster-config.mdm-mno-certificate-about-to-expire | PFX00015.0000454 | |||
20010455 | SDT_INITIATOR_UNRESPONSIVE_FATAL_ERROR | The SDT is unable to participate in data mobility copy because its NVMe initiator is unresponsive or had a fatal error | CRITICAL | SDT OS is stuck. | Rebooting the SDT's server will restart the NVMe initiator. After resolving the issue, an Admin should clear the alert manually using the procedure desribed in the REST manual | sdts.sdt-unresponsive-fatal-error | PFX00007.0000455 |