HU00982 |
SVC |
High Importance
|
Single node warmstart when software update is attempted on some DH8 nodes
(show details)
Symptom |
Single Node Warmstart |
Environment |
DH8 nodes containing a particular boot drive |
Trigger |
Software upgrade on a cluster containing DH8 nodes with model AL13SEB300 boot drive. Note that not all drives of this model exhibit this issue |
Workaround |
Use the manual software upgrade procedure, documented in the Knowledge Center, to upgrade to a fixed software version |
|
7.4.0.11 |
System Update |
HU01258 |
SVC |
Suggested
|
A compressed volume copy will result in an unexpected 1862 message when site/node fails over in a stretched cluster configuration
(show details)
Symptom |
None |
Environment |
SVC systems running v7.4 or later in a stretched cluster configuration |
Trigger |
Site/node failover |
Workaround |
None |
|
7.4.0.11 |
Compression |
HU00726 |
SVC, V7000, V5000 |
High Importance
|
Single node warmstart due to stuck I/O following offline MDisk group condition
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems running v7.3 or later that are virtualising external storage controllers |
Trigger |
Offline MDisk group (when MDisks are from an external storage controller) |
Workaround |
Prevent external conditions that can take an MDisk group offline |
|
7.4.0.10 |
Storage Virtualisation |
IT14917 |
All |
High Importance
|
Node warmstarts due to a timing window in the cache component. For more details refer to this Flash
(show details)
Symptom |
Multiple Node Warmstarts |
Environment |
Systems running v7.4 or later |
Trigger |
None |
Workaround |
None |
|
7.4.0.10 |
Cache |
HU00831 (reverted) |
All |
Suggested
|
This APAR has been reverted in light of issues with the fix. This APAR will be re-applied in a future PTF
|
7.4.0.10 |
Cache |
HU01024 |
V7000, V5000, V3700, V3500 |
Suggested
|
A single node warmstart may occur when the SAS firmwares ECC checking detects a single bit error. The warmstart clears the error condition in the SAS chip
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems running v7.4 or later |
Trigger |
None |
Workaround |
None |
|
7.4.0.10 |
|
HU01097 |
V5000, V3700, V3500 |
Suggested
|
For a small number of node warmstarts the SAS register values are retaining incorrect values rendering the debug information invalid
(show details)
Symptom |
None |
Environment |
Systems running v7.4 or later |
Trigger |
None |
Workaround |
None |
|
7.4.0.10 |
Support Data Collection |
HU00831 (reverted in 7.4.0.10) |
All |
Suggested
|
Single node warmstart due to hung I/O caused by cache deadlock
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems running v7.2 or later |
Trigger |
Hosts sending many large block IOs that use many credits per I/O |
Workaround |
None |
|
7.4.0.9 |
Cache |
HU00936 |
All |
Suggested
|
During the volume repair process the compression engine restores a larger amount of data than required leading to the volume being offline
(show details)
Symptom |
Offline Volumes |
Environment |
Systems running v7.3 or later that are using compressed volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.9 |
Compression |
HU01029 |
SVC |
Suggested
|
Where a boot drive has been replaced with a new unformatted one, on a DH8 node, the node may warmstart when the user logs in as superuser to the CLI via its service IP or they login to the node via the service GUI. Additionally where the node is the config node this may happen when the user logs in as superuser to the cluster via CLI or management GUI
(show details)
Symptom |
Single Node Warmstart |
Environment |
DH8 clusters running v7.3 or later |
Trigger |
Replace boot drive with new, uninitialised drive. Attempt to login to service assistant as "superuser" |
Workaround |
Send necessary service commands to the node from another node in the cluster. Put node into service and resync the drive |
|
7.4.0.9 |
|
HU00819 |
All |
HIPER
|
Large increase in response time of Global Mirror primary volumes due to intermittent connectivity issues
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems running v7.4 or later using Global Mirror |
Trigger |
Connectivity issues between the primary and secondary cluster |
Workaround |
Use a lower link tolerance setting to prevent host impact on the primary |
|
7.4.0.8 |
Global Mirror |
HU00990 |
All |
HIPER
|
A node warmstart on a cluster with Global Mirror secondary volumes can also result in a delayed response to hosts performing I/O to the Global Mirror primary volumes
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems running v7.4 or later using Global Mirror |
Trigger |
Node warmstart on the secondary cluster |
Workaround |
Use GMCV |
|
7.4.0.8 |
Global Mirror |
HU01051 |
All |
HIPER
|
Large increase in response time of Global Mirror primary volumes when replicating large amounts of data concurrently to secondary cluster
(show details)
Symptom |
Performance |
Environment |
Systems running v7.4 or later using a large number of Global Mirror relationships |
Trigger |
None |
Workaround |
None |
|
7.4.0.8 |
Global Mirror |
HU00830 |
All |
High Importance
|
When a node running iSCSI encounters a PDU with AHS it will warmstart
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems with iSCSI connected hosts |
Trigger |
Connect an iSCSI host with AHS enabled |
Workaround |
Disable host AHS on iSCSI |
|
7.4.0.8 |
iSCSI |
HU00891 |
All |
High Importance
|
The extent database defragmentation process can create duplicates whilst copying extent allocations resulting in a node warmstart to recover the database
(show details)
Symptom |
Multiple Node Warmstarts |
Environment |
Systems running v7.3 or later using Thin Provisioning |
Trigger |
None |
Workaround |
None |
|
7.4.0.8 |
Thin Provisioning |
HU00346 |
All |
Suggested
|
Running GMCV relationships are not consistently displayed in GUI
(show details)
Symptom |
None |
Environment |
Systems using Global Mirror with Change Volumes |
Trigger |
None |
Workaround |
Create and start an additional GMCV relationship to trigger all relationships to be shown |
|
7.4.0.8 |
Graphical User Interface, Global Mirror with Change Volumes |
HU00890 |
V7000 |
Suggested
|
Technician port inittool redirects to SAT GUI
(show details)
Symptom |
Configuration |
Environment |
OEM V7000 Gen 2 systems |
Trigger |
Initialise cluster via the technician port |
Workaround |
Use SAT GUI or USB stick to initialise the cluster |
|
7.4.0.8 |
Graphical User Interface |
HU00836 |
All |
Critical
|
Wrong volume copy may be taken offline in a timing window when metadata corruption is detected on a Thin Provisioned Volume and a node warmstart happens at the same time
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems using Thin Provisioned Volumes |
Trigger |
Metadata corruption (e.g. due to actual backend data corruption) is detected on a Thin Provisioned volume and a node warmstarts at exactly the same time |
Workaround |
Take measures to prevent backend data corruption |
|
7.4.0.7 |
Thin Provisioning |
HU00980 |
SVC, V7000 |
Critical
|
Enhanced recovery procedure for compressed volumes affected by APAR HU00898. For more details refer to this Flash
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems running v7.3 or later that are using compressed volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.7 |
Compression |
HU00740 |
All |
High Importance
|
Read/write performance latencies due to high CPU utilisation from EasyTier 3 processes on the configuration node
(show details)
Symptom |
Performance |
Environment |
Systems running v7.3 or later with EasyTier enabled that have many extents (>1 million) |
Trigger |
High volume workloads |
Workaround |
Disable EasyTier |
|
7.4.0.7 |
EasyTier |
HU00898 |
SVC, V7000 |
HIPER
|
Potential data loss scenario when using compressed volumes on SVC and Storwize V7000 running software versions v7.3, v7.4 or v7.5. For more details refer to this Flash
(show details)
Symptom |
None |
Environment |
Systems running v7.3 or later that are using compressed volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.6 |
Compression |
HU00904 |
SVC, V7000, V5000, V3700 |
Critical
|
Multiple node warmstarts leading to loss of access to data when the link used for IP Replication experiences packet loss and the data transfer rate occasionally drops to zero
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems running v7.4.0.5 or v7.5.0.2 that are using IP Replication |
Trigger |
When the IP link used for replication experiences packet loss and the data transfer rate occasionally drops to zero |
Workaround |
None |
|
7.4.0.6 |
IP Replication |
HU00922 |
All |
Critical
|
Loss of access to data when moving volumes to another I/O group using the GUI
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems with multiple I/O groups |
Trigger |
Moving volumes between I/O groups using the GUI |
Workaround |
Use the CLI to move volumes between I/O groups |
|
7.4.0.6 |
Graphical User Interface |
HU00832 |
V3700 |
High Importance
|
Automatic licensed feature activation fails for 6099 machine type
(show details)
Symptom |
Configuration |
Environment |
V3700 systems with 6099 machine type |
Trigger |
Automatic feature activation using the GUI |
Workaround |
Use manual license activation (via GUI or CLI) |
|
7.4.0.6 |
Graphical User Interface |
HU00845 |
V3700 |
High Importance
|
Trial licenses for licensed feature activation are not available
(show details)
Symptom |
Configuration |
Environment |
V3700 systems that were created on v7.4 or v7.5 |
Trigger |
None |
Workaround |
None |
|
7.4.0.6 |
|
HU00913 |
SVC, V7000, V5000, V3700 |
High Importance
|
Multiple node warmstarts when using a Metro Mirror or Global Mirror volume that is greater than 128TB
(show details)
Symptom |
Multiple Node Warmstarts |
Environment |
Systems using Metro Mirror, Global Mirror or Global Mirror with Change Volumes |
Trigger |
I/O to a global mirror volume that is larger than 128TB |
Workaround |
Keep volume size to less than 128TB when using replication services |
|
7.4.0.6 |
Global Mirror, Global Mirror with Change Volumes, Metro Mirror |
HU00923 |
SVC, V7000, V5000 |
High Importance
|
Single node warmstart when receiving frame errors on 16GB Fibre Channel adapters
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems using 16GB FC adapters |
Trigger |
When error conditions are present in the fibre channel network |
Workaround |
None |
|
7.4.0.6 |
Reliability Availability Serviceability |
II14778 |
All |
High Importance
|
Reduced performance for volumes which have the configuration node as their preferred node due to GUI processing the update of volume attributes where there is a large number of changes required
(show details)
Symptom |
Performance |
Environment |
Systems that have a large number of volumes (1000+) |
Trigger |
Using the GUI when a large number of volumes have regularly changing attributes |
Workaround |
Disable GUI |
|
7.4.0.6 |
Performance |
HU00756 |
SVC, V7000 |
Suggested
|
Performance statistics BBCZ counter values reported incorrectly
(show details)
Symptom |
None |
Environment |
Systems using 16GB FC adapters |
Trigger |
None |
Workaround |
None |
|
7.4.0.6 |
System Monitoring |
HU00905 |
All |
Suggested
|
The serial number value displayed in the GUI node properties dialog is incorrect
(show details)
Symptom |
None |
Environment |
All |
Trigger |
None |
Workaround |
The correct Node serial number value can be displayed using cli command 'svcinfo lsnodevpd' |
|
7.4.0.6 |
Graphical User Interface |
HU00924 |
SVC, V7000 |
Suggested
|
The Volumes by Pool display in the GUI shows incorrect EasyTier status
(show details)
Symptom |
None |
Environment |
All |
Trigger |
None |
Workaround |
Use the lsmdiskgrp or lsvdisk CLI commands to confirm EasyTier status |
|
7.4.0.6 |
Graphical User Interface |
HU00725 |
SVC, V7000, V5000, V3700 |
HIPER
|
Loss of access to data when adding a Global Mirror Change Volume relationship to a consistency group on the primary site, when the secondary site does not have a secondary volume defined
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems using Global Mirror with Change Volumes |
Trigger |
Adding a GMCV relationship to a consistency group on the primary site |
Workaround |
Create a volume on the secondary cluster and associate the volume with the relationship before adding the relationship on the primary cluster |
|
7.4.0.5 |
Global Mirror with Change Volumes |
HU00671 |
V7000, V5000, V3700, V3500 |
Critical
|
1691 error on arrays when using multiple FlashCopies of the same source. For more details refer to this Flash
(show details)
Symptom |
None |
Environment |
Systems running v7.3 or later using FlashCopy |
Trigger |
Start and stop of FlashCopy mappings when there are multiple FlashCopies of the same source volume |
Workaround |
None |
|
7.4.0.5 |
Backend Storage, FlashCopy |
HU00811 |
SVC, V7000, V5000 |
Critical
|
Loss of access to data when SAN connectivity problems leads to backend controller being detected as incorrect type
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems virtualising external storage controllers |
Trigger |
SAN connectivity problems |
Workaround |
None |
|
7.4.0.5 |
Backend Storage |
HU00820 |
V7000, V5000, V3700, V3500 |
Critical
|
Data integrity issue when using encrypted arrays. For more details refer to this Flash
(show details)
Symptom |
None |
Environment |
Systems running v7.4 or later which are using Encryption |
Trigger |
Internal SAS network recovery actions |
Workaround |
None |
|
7.4.0.5 |
Backend Storage, Encryption |
HU00659 |
SVC, V7000, V5000, V3700 |
High Importance
|
Global Mirror with Change Volumes freeze time reported incorrectly
(show details)
Symptom |
None |
Environment |
Systems running v7.4 or later that are using Global Mirror with Change Volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.5 |
Global Mirror with Change Volumes |
HU00673 |
V7000, V5000, V3700, V3500 |
High Importance
|
Drive slot is not recognised following drive auto manage procedure
(show details)
Symptom |
Configuration |
Environment |
Systems running v7.4 or later |
Trigger |
Disk drive recovery action using 'drive auto manage' procedure |
Workaround |
None |
|
7.4.0.5 |
System Monitoring |
HU00731 |
All |
High Importance
|
Single node warmstart due to invalid volume memory allocation pointer
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems running v7.4 or later |
Trigger |
None |
Workaround |
None |
|
7.4.0.5 |
Hosts |
HU00745 |
SVC, V7000, V5000, V3700 |
High Importance
|
IP Replication does not return to using full throughput following packet loss on IP link used for replication
(show details)
Symptom |
Performance |
Environment |
Systems using IP Replication |
Trigger |
Packet loss on IP link |
Workaround |
After the IP link is stabilised: Stop the IP partnership Start the IP partnership Stop all remote copy relationships Start all relationships |
|
7.4.0.5 |
IP Replication |
HU00825 |
V7000, V5000, V3700, V3500 |
High Importance
|
Java exception error when using the Service Assistant GUI to complete an enclosure replacement procedure
(show details)
Symptom |
Configuration |
Environment |
All |
Trigger |
When replacing an enclosure |
Workaround |
Use the Service Assistant cli to complete enclosure replacement procedure |
|
7.4.0.5 |
Graphical User Interface |
HU00711 |
All |
Suggested
|
GUI response slow when filtering a large number of volumes
(show details)
Symptom |
None |
Environment |
All |
Trigger |
None |
Workaround |
Use CLI to list or perform actions on volumes |
|
7.4.0.5 |
Graphical User Interface |
HU00759 |
All |
Suggested
|
catxmlspec cli command (used by external monitoring applications such as Spectrum Control Base) not working
(show details)
Symptom |
None |
Environment |
Systems running v7.4.0.3 & v7.4.0.4 |
Trigger |
None |
Workaround |
None |
|
7.4.0.5 |
System Monitoring |
HU00829 |
V7000, V5000, V3700, V3500 |
Suggested
|
1125 (or 1066 on V7000 Generation 2) events incorrectly logged for all PSUs/Fan trays when there is a single PSU/fan tray fault
(show details)
Symptom |
None |
Environment |
Systems running v7.4 or later (does not apply to V7000 Generation 1 systems) |
Trigger |
PSU failure |
Workaround |
None |
|
7.4.0.5 |
Reliability, Availability and Serviceability |
HU00680 |
V7000 |
HIPER
|
Compressed volumes go offline due to false detection event. Applies to V7000 Generation 2 systems only running v7.3.0.9 or v7.4.0.3
(show details)
Symptom |
Offline Volumes |
Environment |
V7000 Gen2 systems with compressed volumes |
Trigger |
Following update to v7.3.0.9 or v7.4.0.3 |
Workaround |
None |
|
7.4.0.4 |
Compression |
HU00676 |
SVC, V7000 |
High Importance
|
Node warmstart due to compression engine restart
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems with compressed volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.4 |
Compression |
HU00630 |
SVC, V7000, V5000, V3700 |
HIPER
|
Temporary loss of paths for FCoE hosts after 497 days uptime due to FCoE driver timer problem
(show details)
Symptom |
Loss of Redundancy |
Environment |
Systems using FCoE |
Trigger |
Systems using FCoE attached hosts that have been up and running for 497 days |
Workaround |
None |
|
7.4.0.3 |
Hosts |
HU00654 |
SVC, V7000 |
HIPER
|
Loss of access to data when FlashCopy stuck during a Global Mirror Change Volumes cycle
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems using Global Mirror with Change Volumes |
Trigger |
Start of Global Mirror change volume cycle |
Workaround |
None |
|
7.4.0.3 |
Global Mirror with Change Volumes |
HU00655 |
V7000, V5000, V3700, V3500 |
Critical
|
Loss of access to data if a PSU in two different enclosures suffers an output failure simultaneously (whilst AC input is good)
(show details)
Symptom |
Loss of Access to Data |
Environment |
Storwize systems |
Trigger |
PSU DC output failure in two separate enclosures simultaneously |
Workaround |
None |
|
7.4.0.3 |
Reliability Availability Serviceability |
HU00669 |
All |
Critical
|
Node warmstart and VMware host I/O timeouts if a node is removed from the cluster during upgrade from a pre v7.4.0 version to v7.4.0 whilst there are active VAAI CAW commands
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems running v7.3 or later with VMware hosts using VAAI CAW feature |
Trigger |
If a node is removed from the cluster during upgrade from pre v7.4.0 level to v7.4.0 |
Workaround |
When upgrading from pre v7.40 to v7.4.0 do not remove last downlevel node from the cluster during the upgrade process. Alternately disabling VAAI CAW commands during upgrade will prevent this problem. |
|
7.4.0.3 |
Hosts |
HU00516 |
SVC, V7000 |
High Importance
|
Node warmstart due to software thread deadlock
(show details)
Symptom |
Single Node Warmstart |
Environment |
SVC DH8 or V7000 Generation 2 systems running v7.3 or later with VMware hosts using VAAI CAW feature |
Trigger |
VAAI CAW commands |
Workaround |
None |
|
7.4.0.3 |
Hosts |
HU00629 |
SVC, V7000 |
High Importance
|
Performance degradation triggered by specific I/O pattern when using compressed volumes due to optimisation issue
(show details)
Symptom |
Performance |
Environment |
Systems with compressed volumes |
Trigger |
Specific I/O pattern when using compressed volumes |
Workaround |
None |
|
7.4.0.3 |
Compression |
HU00636 |
V3700, V3500 |
High Importance
|
Livedump prepare fails on V3500 & V3700 systems with 4GB memory when cache partition fullness is less than 35%
(show details)
Symptom |
None |
Environment |
V3500 & V3700 systems with 4GB memory in each node canister |
Trigger |
When running 'preplivedump' command or collecting Snap option 4 |
Workaround |
None |
|
7.4.0.3 |
Support Data Collection |
HU00637 |
SVC, V7000, V5000 |
High Importance
|
HP MSA P2000 G3 controllers running a firmware version later than TS240P003 may not be recognised by SVC/Storwize
(show details)
Symptom |
Configuration |
Environment |
Systems virtualising HP MSA P2000 G3 controllers |
Trigger |
When initialising MDisks for an HP MSA P2000 G3 controller |
Workaround |
None |
|
7.4.0.3 |
Storage Virtualisation |
HU00646 |
SVC, V7000, V5000, V3700 |
High Importance
|
Easy tier throughput reduced due to Easy tier only moving 6 extents per 5 minutes regardless of extent size
(show details)
Symptom |
Performance |
Environment |
Systems running v7.3 or later with EasyTier enabled |
Trigger |
None |
Workaround |
None |
|
7.4.0.3 |
EasyTier |
HU00665 |
All |
High Importance
|
Node warmstart due to software thread deadlock condition during execution of internal MDisk/discovery process
(show details)
Symptom |
Single Node Warmstart |
Environment |
All |
Trigger |
When internal discovery/detectmdisk process runs |
Workaround |
None |
|
7.4.0.3 |
|
HU00666 |
SVC, V7000, V5000, V3700 |
High Importance
|
Upgrade from v7.2.0 stalls due to dependent volumes
(show details)
Symptom |
None |
Environment |
Systems using Global Mirror |
Trigger |
Upgrading from v7.2.0 whilst Global Mirror relationships are active |
Workaround |
Stop Global Mirror relationships or consistency groups before performing upgrade |
|
7.4.0.3 |
Global Mirror |
HU00672 |
SVC, V7000 |
High Importance
|
Node warmstart due to compression stream condition
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems with compressed volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.3 |
Compression |
HU00677 |
All |
High Importance
|
Node warmstart or loss of access to GUI/CLI due to defunct SSH processes
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems running v7.4.0 |
Trigger |
Many SSH sessions to the cluster, most often triggered by monitoring tools |
Workaround |
Stop SSH connections to cluster |
|
7.4.0.3 |
System Monitoring |
II14771 |
SVC, V7000 |
High Importance
|
Node warmstart due to compression/index re-writing timing condition
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems with compressed volumes |
Trigger |
None |
Workaround |
None |
|
7.4.0.3 |
Compression |
HU00389 |
SVC, V7000, V5000 |
Suggested
|
When a Storwize system is configured as a backend storage subsystem for an SVC or another Storwize system, the port statistics count the traffic between these two systems as remote cluster traffic instead of host to storage traffic (e.g. in TPC Port to Remote Node Send Data Rate instead of Port to Controller Send Data Rate)
(show details)
Symptom |
None |
Environment |
SVC or Storwize systems with another Storwize system virtualised as a backend controller |
Trigger |
None |
Workaround |
None |
|
7.4.0.3 |
System Monitoring |
HU00653 |
V7000, V5000, V3700, V3500 |
Suggested
|
1691 RAID inconsistencies falsely reported due to RAID incomplete locking issue
(show details)
Symptom |
None |
Environment |
All |
Trigger |
None |
Workaround |
None |
|
7.4.0.3 |
Backend Storage |
HU00678 |
All |
Suggested
|
iSCSI hosts incorrectly show an offline status following update to V6.4 from a pre V6.4 release
(show details)
Symptom |
None |
Environment |
Systems with iSCSI hosts |
Trigger |
Systems running pre V6.4.0 release with iSCSI hosts defined that then update to V6.4 |
Workaround |
A restart of the non-config node will correct the reported host status |
|
7.4.0.3 |
iSCSI |
HU00645 |
SVC, V7000 |
Critical
|
Loss of access to data when using compressed volumes on 7.4.0.1 can occur when there is a large number of consecutive and highly compressible writes to a compressed volume
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems with compressed volumes running 7.4.0.1 |
Trigger |
Very large number of consecutive and highly compressible writes to a compressed volume (for example writing sequential zeros to a disk) |
Workaround |
Avoid workloads which create a large number of consecutive and highly compressible writes to a compressed volume |
|
7.4.0.2 |
Compression |
HU00660 |
SVC, V7000 |
High Importance
|
Reduced performance on compressed volumes when running parallel workloads with large block size
(show details)
Symptom |
Performance |
Environment |
Systems with compressed volumes |
Trigger |
Host workloads with large block size combined with high host queue depth |
Workaround |
Lower maximum host I/O size and queue depth (field cases have shown that setting host MAX XFER SIZE to 128 KB and lowering the queue depth help improve performance) |
|
7.4.0.1 |
Compression |
HU00546 |
All |
HIPER
|
Multiple Node warmstarts when attempting to access data beyond the end of the volume
(show details)
Symptom |
Loss of Access to Data |
Environment |
Systems using thin provisioning |
Trigger |
Reads or writes which attempt to access data beyond the end of the volume capacity |
Workaround |
None |
|
7.4.0.0 |
Thin Provisioning |
HU00658 |
SVC, V7000, V5000, V3700 |
HIPER
|
Global Mirror source data may be incompletely replicated to target volumes. For more details refer to this Flash
(show details)
Symptom |
Data Integrity Loss |
Environment |
Systems using Global Mirror |
Trigger |
Environments in which the secondary SVC cluster or Storwize system is running or has previously been running a v7.2.0 or v7.3.0 release earlier than v7.2.0.11 or v7.3.0.9 |
Workaround |
None |
|
7.4.0.0 |
Global Mirror |
IC80230 |
V7000, V5000, V3700, V3500 |
HIPER
|
Both nodes warmstart due to Ethernet storm
(show details)
Symptom |
Multiple Node Warmstarts |
Environment |
All |
Trigger |
Ethernet Storm |
Workaround |
Take measures to prevent ethernet storm occurring |
|
7.4.0.0 |
|
HU00505 |
SVC, V7000, V5000, V3700 |
Critical
|
Multiple node warmstarts caused by timing window when using inter-system replication
(show details)
Symptom |
Multiple Node Warmstarts |
Environment |
Systems using Global Mirror or Metro Mirror replication |
Trigger |
Timing window |
Workaround |
None |
|
7.4.0.0 |
Global Mirror, Metro Mirror |
HU00518 |
All |
Critical
|
Multiple Node warmstarts due to invalid SCSI commands generated by network probes
(show details)
Symptom |
Loss of Access to Data |
Environment |
iSCSI Configuration |
Trigger |
Using Ethernet Network Probing software |
Workaround |
Avoid using Network probing software on systems which are running production workloads |
|
7.4.0.0 |
iSCSI |
HU00544 |
All |
Critical
|
Storage pool offline when upgrading firmware on storage subsystems listed in APAR Environment
(show details)
Symptom |
Offline Volumes |
Environment |
Systems virtualising IBM DS3000 DS4000 DS5000 storage subsystems |
Trigger |
Storage subsystem firmware upgrade |
Workaround |
Update NVSRAM before updating firmware |
|
7.4.0.0 |
|
HU00545 |
V7000, V5000, V3700, V3500 |
Critical
|
Loss of Access to data after control chassis or midplane enclosure replacement
(show details)
Symptom |
Loss of Access to Data |
Environment |
Storwize platform |
Trigger |
Control enclosure chassis or midplane replacement |
Workaround |
None |
|
7.4.0.0 |
|
HU00484 |
SVC, V7000, V5000, V3700, V3500 |
High Importance
|
Loss of access to data when the lsdependentvdisks command is run with no parameters
(show details)
Symptom |
Loss of Access to Data |
Environment |
All |
Trigger |
Running the 'lsdependentvdisks' command with no parameters |
Workaround |
Do not issue the 'lsdependentvdisks' command with no parameters |
|
7.4.0.0 |
|
HU00490 |
SVC, V7000, V5000, V3700 |
High Importance
|
Node warmstart when using Metro Mirror or Global Mirror
(show details)
Symptom |
Single Node Warmstart |
Environment |
Environments using Metro Mirror or Global Mirror |
Trigger |
Metro Mirror or Global Mirror |
Workaround |
None |
|
7.4.0.0 |
Global Mirror, Metro Mirror |
HU00494 |
All |
High Importance
|
Node warmstart caused by timing window when handling XCOPY commands
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems with VMware hosts |
Trigger |
None |
Workaround |
Disable VAAI where possible |
|
7.4.0.0 |
Hosts |
HU00495 |
SVC, V7000, V5000, V3700 |
High Importance
|
Node warmstart caused by a single active write holding up the GM disconnect
(show details)
Symptom |
Single Node Warmstart |
Environment |
Systems using Global Mirror |
Trigger |
Using Global Mirror |
Workaround |
None |
|
7.4.0.0 |
Global Mirror |
HU00520 |
All |
High Importance
|
Node warmstart caused by iSCSI command being aborted immediately after the command is issued
(show details)
Symptom |
Single Node Warmstart |
Environment |
iSCSI Configuration using 10GB/s Ethernet Adapter |
Trigger |
SCSI command is aborted immediately after the command is received |
Workaround |
None |
|
7.4.0.0 |
iSCSI |
HU00528 |
V7000, V5000, V3700, V3500 |
High Importance
|
Single PSU DC output turned off when there is no PSU hardware fault present
(show details)
Symptom |
Loss of Redundancy |
Environment |
Storwize systems |
Trigger |
None |
Workaround |
None |
|
7.4.0.0 |
Reliability Availability Serviceability |
HU00538 |
All |
High Importance
|
Node warmstart when removing host port (via GUI or CLI) when there is outstanding I/O to host
(show details)
Symptom |
Single Node Warmstart |
Environment |
Any |
Trigger |
Removing host port when there is active I/O to the host |
Workaround |
Unzone or unplug HBA before running rmhostport command |
|
7.4.0.0 |
Hosts |
HU00543 |
All |
High Importance
|
Elongated I/O pause when starting or stopping remote copy relationships when there are a large number of remote copy relationships
(show details)
Symptom |
Performance |
Environment |
Systems using Global Mirror or Metro Mirror replication |
Trigger |
Start or Stop Remote Copy relationships or consistency groups when there are a large number of remote copy relationships in the same stream. |
Workaround |
None |
|
7.4.0.0 |
Global Mirror, Metro Mirror |
HU00547 |
SVC |
High Importance
|
I/O delay during site failure using enhanced stretched cluster
(show details)
Symptom |
Performance |
Environment |
Enhanced stretched cluster configuration |
Trigger |
Site failure |
Workaround |
None |
|
7.4.0.0 |
Performance |
HU00130 |
V5000, V3700, V3500 |
Suggested
|
Node warmstart due to IPC queue state
(show details)
Symptom |
Single Node Warmstart |
Environment |
Any |
Trigger |
Collecting statesaves whilst one node is starting up |
Workaround |
None |
|
7.4.0.0 |
|
HU00251 |
All |
Suggested
|
Unable to migrate volume mirror copies to alternate storage pool using GUI
(show details)
Symptom |
None |
Environment |
Environments with volume mirroring |
Trigger |
Migrating volume mirror copies via GUI |
Workaround |
Use the CLI to migrate volume copies |
|
7.4.0.0 |
GUI |
HU00300 |
All |
Suggested
|
Volume mirroring synchronisation exceeds the maximum copy rate
(show details)
Symptom |
Performance |
Environment |
Systems using Volume Mirroring of volumes that have a copy rate of 100 and are larger than 1 TB |
Trigger |
Adding a volume copy with a sync rate of 100 |
Workaround |
Use lower copy rate for volume mirroring on large volumes |
|
7.4.0.0 |
Performance, Volume Mirroring |
HU00305 |
SVC, V7000, V5000 |
Suggested
|
System unable to detect and use newly added ports on EMC VMAX
(show details)
Symptom |
Performance |
Environment |
Systems virtualising EMC VMAX |
Trigger |
Add new paths from system to EMC VMAX |
Workaround |
None |
|
7.4.0.0 |
Backend Storage |
HU00467 |
SVC, V7000, V5000, V3700 |
Suggested
|
Global Mirror Change Volumes Freeze time not reported correctly if cycle takes longer than the cycle period to complete
(show details)
Symptom |
None |
Environment |
Systems using Global Mirror with Change Volumes |
Trigger |
Global Mirror Change Volumes cycle taking longer than the cycle period to complete |
Workaround |
None |
|
7.4.0.0 |
Global Mirror with Change Volumes |
HU00487 |
V7000, V5000, V3700, V3500 |
Suggested
|
Rebuild process stalls or unable to create MDisk due to unexpected RAID scrub state
(show details)
Symptom |
None |
Environment |
All |
Trigger |
Background RAID scrub process |
Workaround |
None |
|
7.4.0.0 |
Backend Storage |
HU00540 |
All |
Suggested
|
Configuration Backup fails due to invalid volume names
(show details)
Symptom |
None |
Environment |
All |
Trigger |
Configuration Backup when volumes names start with non-alphabetical characters |
Workaround |
Rename volumes as required |
|
7.4.0.0 |
Support Data Collection |
HU00541 |
V7000, V5000, V3700, V3500 |
Suggested
|
Fix Procedure fails to complete successfully when servicing PSU
(show details)
Symptom |
None |
Environment |
System with PSU failure |
Trigger |
Running the Fix Procedure |
Workaround |
None |
|
7.4.0.0 |
Fix Procedures |
HU00548 |
SVC, V7000, V5000, V3700 |
Suggested
|
Unable to create IP partnership that had previously been deleted
(show details)
Symptom |
None |
Environment |
IP Replication configuration |
Trigger |
Trying to recreate a partnership that had previously been deleted |
Workaround |
None |
|
7.4.0.0 |
IP Replication |