| SVAPAR-136256 |
All |
HIPER
|
Each ethernet port can only have a single management IP address. Attempting to add a second management IP to the same port may cause multiple node warmstarts and a loss of access to data.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
None |
| Trigger |
Attempting to add a second management IP address to a port |
| Workaround |
Do not attempt to add a second management IP address to a port |
|
8.7.1.0 |
Reliability Availability Serviceability |
| SVAPAR-140080 |
All |
HIPER
|
Tier 2 warmstarts ending with nodes in service state while processing a long list of expired snapshots.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Systems running code level 8.6.1.x, 8.6.2.x, 8.6.3.x and 8.7.0.0 that use either SGC or volume group snapshots. |
| Trigger |
It is very unlikely that this can be triggered only by user activity (e.g. by running 'rmsnapshot' on a large number of snapshots). The most likely trigger is if the system is already affected by SVAPAR-140079, and the client runs 'rmsnapshot' on one or more snapshots. This will unblock the scheduler and prompt it to process (rmsnapshot) all the snapshots that expired since it became blocked. |
| Workaround |
If the system is already affected by SVAPAR-140079, avoid running 'rmsnapshot' commands. The risk can be temporarily mitigated by suspending snapshot policies at a system level. ('chsystem -snapshotpolicysuspended yes') |
|
8.7.1.0 |
FlashCopy, Safeguarded Copy & Safeguarded Snapshots |
| SVAPAR-135022 |
All |
Critical
|
When using Policy Based High Availability, a storage partition can become suspended due to a disagreement in the internal quorum race state between two systems, causing a loss of access to data.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Any systems with Policy Based High Availability configured |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-137485 |
FS5000 |
Critical
|
Reseating a FlashSystem 50xx node canister at 8.7.0.0 may cause the partner node to reboot, causing temporary loss of access to data.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
FS50xx running 8.7.0.0 |
| Trigger |
Reseating a canister |
| Workaround |
None |
|
8.7.1.0 |
Reliability Availability Serviceability |
| SVAPAR-141112 |
All |
Critical
|
When using policy-based high availability and volume group snapshots, it is possible for an I/O timeout condition to trigger node warmstarts. This can happen if a system is disconnected for an extended period, and is then brought back online after a large amount of host I/O to the HA volumes.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems using policy-based high availability and volume-group snapshots (including safeguarded copy) |
| Trigger |
Policy-based high availability systems being disconnected for an extended period |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-142040 |
All |
Critical
|
A timing window related to logging of capacity warnings may cause multiple node warmstarts on a system with low free physical capacity on an FCM array.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Systems with FCM drives |
| Trigger |
Timing window combined with low physical free capacity |
| Workaround |
Avoid allowing an FCM array to come close to running out of physical capacity |
|
8.7.1.0 |
Reliability Availability Serviceability |
| SVAPAR-142045 |
All |
Critical
|
A system which was previously running pre-8.6.0 software, and is now using policy-based high availability, may experience multiple node warmstarts when a PBHA failover is requested by the user.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Systems using PBHA after upgrade from pre-8.6.0 software. |
| Trigger |
User-requested PBHA failover |
| Workaround |
Do not initiate a PBHA failover until the software has been upgraded |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-143480 |
All |
Critical
|
When using asynchronous policy based replication on low bandwidth links with snapshot clone/restore, an undetected data corruption may occur. This issue only affects 8.7.0.0.
(show details)
| Symptom |
Data Integrity Loss |
| Environment |
8.7.0.0 systems using policy based replication with snapshot clone/restore |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-147978 |
All |
Critical
|
A system running 8.7.0 and using policy-based replication may experience additional warmstarts during the recovery from a single node warmstart
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Systems using policy-based replication on 8.7.0 |
| Trigger |
Warmstart of a node |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-111173 |
All |
High Importance
|
Loss of access when two drives experience slowness at the same time
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Can occur on any SAS based system, including SAS expansion enclosures. |
| Trigger |
Heavily loaded SAS spinning drives |
| Workaround |
Try and reduce the work load |
|
8.7.1.0 |
RAID |
| SVAPAR-136427 |
All |
High Importance
|
When deleting multiple older snapshots versions, whilst simultaneously creating new snapshots, the system can run out of bitmap space resulting in a bad snapshot map, repeated asserts, and a loss of access.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
This can affect any system configured with FlashCopy |
| Trigger |
Deletion of multiple mid-age snapshots and creating new snapshots. |
| Workaround |
Avoid deleting multiple older snapshots versions, whilst simultaneously creating new snapshots |
|
8.7.1.0 |
FlashCopy |
| SVAPAR-138214 |
All |
High Importance
|
When a volume group is assigned to an ownership group, creating a snapshot and populating a new volume group from the snapshot will cause a warmstart of the configuration node when 'lsvolumepopulation' is run.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Using a combination of volume groups, volume group snapshot policies and ownership groups. Veeam 12.1 with Spectrum Virtualize 8.5.1 and higher. |
| Trigger |
Creating a snapshot of a volume that has ownership. Populating a new volume group from the snapshot as an ownership group user. Running 'lsvolumepopulation' as an ownership group user. |
| Workaround |
Either use superuser credentials to perform the tasks, or remove the ownership group and associated user group for objects that will have these actions performed on them. |
|
8.7.1.0 |
FlashCopy |
| SVAPAR-140926 |
All |
High Importance
|
When a cluster partnership is removed, a timing window can result in an I/O timeout and a node warmstart.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
All platforms running policy-based replication. |
| Trigger |
Use of the 'rmpartnership' command |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-141684 |
All |
High Importance
|
Prevent drive firmware upgrade with both '-force' and '-all' parameters, to avoid multiple drives going offline due to lack of redundancy.
(show details)
| Symptom |
Data Integrity Loss |
| Environment |
All |
| Trigger |
Upgrading drive firmware with '-force' and all at the same time |
| Workaround |
If the force flag is required to upgrade drive firmware, each drive must be upgraded individually. |
|
8.7.1.0 |
Drives |
| SVAPAR-142081 |
All |
High Importance
|
If an error occurs during creation of a replication policy, multiple node warmstarts may occur, causing a temporary loss of access to data.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
System versions that support Policy-based replication. |
| Trigger |
An unexpected error during creation of a replication policy. |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-145355 |
All |
High Importance
|
On FS5045 with policy-based high availability or replication, an out-of-memory issue may cause frequent 4110 events.
(show details)
| Symptom |
Configuration |
| Environment |
FS5045 with policy-based high availability or replication |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Policy-based High availability, Policy-based Replication |
| SVAPAR-152902 |
All |
High Importance
|
If a system is using asynchronous policy-based replication, certain unusual host I/O workloads can cause an I/O timeout to be incorrectly detected, triggering node warmstarts at the recovery site.
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Systems using policy-based replication
|
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-153246 |
All |
High Importance
|
A hung condition in Remote Receive IOs (RRI) for volume groups can lead to warmstarts on multiple nodes.
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Any system that uses Policy-based Replication |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-89331 |
All |
High Importance
|
Systems running 8.5.2 or higher using IP replication with compression may have low replication bandwidth and high latency due to an issue with the way the data is compressed.
(show details)
| Symptom |
Performance |
| Environment |
Systems using IP replication compression |
| Trigger |
None |
| Workaround |
Disable compression on IP partnership |
|
8.7.1.0 |
IP Replication |
| SVAPAR-130984 |
All |
Suggested
|
Configuring Policy-based replication in the GUI fails if the system authentication service type is unused.
(show details)
| Symptom |
Configuration |
| Environment |
Systems that previously upgraded from 8.3.0 or lower and used TIP (Tivoli Integrated Portal) authentication. |
| Trigger |
Attempting to link pools or create a replication policy in the GUI |
| Workaround |
Change authentication service type to LDAP using: 'svctask chauthservice -type ldap' |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-135742 |
All |
Suggested
|
A temporary network issue may cause unexpected 1585 DNS connection errors after upgrading to 8.6.0.4, 8.6.3.0 or 8.7.0.0. This is due to a shorter DNS request timeout in these PTFs.
(show details)
| Symptom |
Configuration |
| Environment |
Systems with a DNS server configured. |
| Trigger |
Temporary network issue causing a DNS request timeout. |
| Workaround |
Check the network for any issues that may cause packet loss, which could lead to a timeout on DNS requests. 'traceroute' command from the cluster to the DNS server can help determine if there are routes that are slower than others. |
|
8.7.1.0 |
Reliability Availability Serviceability |
| SVAPAR-138418 |
All |
Suggested
|
Snap collections triggered by Storage Insights over cloud callhome time out before they have completed
(show details)
| Symptom |
None |
| Environment |
Systems using Cloud Callhome |
| Trigger |
Remotely collecting a snap via callhome |
| Workaround |
Collect the snap locally and upload to IBM |
|
8.7.1.0 |
Reliability Availability Serviceability |
| SVAPAR-139118 |
All |
Suggested
|
When logged into GUI as a user that is a member of the FlashCopy Administrator group, the GUI does not allow flashcopies to be created and options are greyed out.
(show details)
| Symptom |
Configuration |
| Environment |
GUI |
| Trigger |
None |
| Workaround |
Run the command via the CLI. |
|
8.7.1.0 |
Graphical User Interface |
| SVAPAR-139205 |
All |
Suggested
|
A node warmstart may occur due to a race condition between Fibre Channel adapter I/O processing and a link reset.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems with Fibre Channel adapters. |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Fibre Channel |
| SVAPAR-140994 |
All |
Suggested
|
Expanding a volume via the GUI fails with CMMVC7019E because the volume size is not a multiple of 512 bytes.
(show details)
| Symptom |
Configuration |
| Environment |
None |
| Trigger |
Attempting to expand a volume by a value that is not a multiple of 512 bytes |
| Workaround |
Expand the volume via the CLI using the 'expandvdisksize' command, ensuring that you increase by 512 byte multiples |
|
8.7.1.0 |
Reliability Availability Serviceability |
| SVAPAR-141019 |
All |
Suggested
|
The GUI crashed when a user group with roles 3SiteAdmin and remote users exist
(show details)
| Symptom |
Configuration |
| Environment |
Systems configured for 3Ssite replication |
| Trigger |
Environments that have a user group with role 3SiteAdmin and a remote user exists |
| Workaround |
Either remove the remote user, or if no 3 site replication is in use, remove the user group with role 3SiteAdmin |
|
8.7.1.0 |
3-Site using HyperSwap or Metro Mirror, Graphical User Interface |
| SVAPAR-141467 |
All |
Suggested
|
SNMPv3 traps may not be processed properly by the SNMP server configured in the system.
(show details)
| Symptom |
Configuration |
| Environment |
Systems running SNMPv3 |
| Trigger |
None |
| Workaround |
Recreate the SNMP definition of the storage system at the SNMP server, this will make the process to work again. |
|
8.7.1.0 |
System Monitoring |
| SVAPAR-141559 |
All |
Suggested
|
GUI shows: 'error occurred loading table data.' in the volume view after the first login attempt to the GUI. Volumes will be visible inside the 'Volumes by Pool'. This is evoked if we create volumes with either a number between dashes, or numbers after dashes, or other characters after numbers
(show details)
| Symptom |
Configuration |
| Environment |
None |
| Trigger |
Creating a volume name that contains numbers between dashes (for example, 'Volume-8-Data'), or contains numbers after the dashes, but with other characters (such as underscores) after these numbers (for example, Volume-8_Data) |
| Workaround |
Do not use dashes or another characters between numbers |
|
8.7.1.0 |
Graphical User Interface |
| SVAPAR-141937 |
All |
Suggested
|
In a Policy-based high availability configuration, when a SCSI Compare and Write command is sent to the non-Active Management System, and communication is lost between the systems while it is being processed, a node warmstart may occur.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Policy-based high availability |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Policy-based Replication |
| SVAPAR-142093 |
All |
Suggested
|
The 'Upload support package' option is missing from the Support Package GUI
(show details)
| Symptom |
None |
| Environment |
None |
| Trigger |
None |
| Workaround |
Download the support package to the desktop, and upload manually to IBM support |
|
8.7.1.0 |
Graphical User Interface |
| SVAPAR-142190 |
All |
Suggested
|
The user role descriptions in the GUI are wrong for the CopyOperator.
(show details)
| Symptom |
None |
| Environment |
None |
| Trigger |
None |
| Workaround |
None |
|
8.7.1.0 |
Graphical User Interface |
| SVAPAR-142193 |
All |
Suggested
|
If an IP Replication partnership only has link2 configured, then the GUI Partnership shows type Fibre Channel for the IPV4 connection.
(show details)
| Symptom |
None |
| Environment |
IP Replication Partnership with remote cluster using IPV4 type connection |
| Trigger |
Configuring IP Replication partnership with only link2, and link1 not configured |
| Workaround |
Via the CLI, reconfigure the IP Replication partnership to use link1 |
|
8.7.1.0 |
IP Replication |
| SVAPAR-142194 |
All |
Suggested
|
GUI volume creation does not honour the preferred node that was selected.
(show details)
| Symptom |
Configuration |
| Environment |
This only effects volumes created via the GUI. |
| Trigger |
None |
| Workaround |
Use the CLI, or change the preferred node to desired node after volume creation |
|
8.7.1.0 |
Graphical User Interface |
| SVAPAR-148643 |
All |
Suggested
|
Changing the management IP address on 8.7.0 software does not update the console_IP field in lspartnership and lssystem output. This can cause the management GUI and Storage Insights to display the wrong IP address.
(show details)
| Symptom |
Configuration |
| Environment |
Systems running 8.7.0 software |
| Trigger |
Changing the management IP address |
| Workaround |
None |
|
8.7.1.0 |
Graphical User Interface |