| SVAPAR-136256 |
All |
Critical
|
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-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-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-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-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-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-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 |