| SVAPAR-117738 |
All |
HIPER
|
The configuration node may go offline with node error 565, due to a full /tmp partition on the boot drive.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Systems running 8.6.2 |
| Trigger |
None |
| Workaround |
Reboot the node to bring it online. |
|
8.6.2.1 |
Reliability Availability Serviceability |
| SVAPAR-105861 |
SVC |
HIPER
|
A cluster recovery may occur when an attempt is made to create a mirrored snapshot with insufficient volume mirroring bitmap space in the IO group
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Systems using mirrored snapshots, including safeguarded snapshots |
| Trigger |
Attempting to create a mirrored snapshot without sufficient volume mirroring bitmap space |
| Workaround |
Adjust snapshot policy configuration to ensure that the maximum bitmap space is sufficient |
|
8.6.2.0 |
FlashCopy, Safeguarded Copy, Volume Mirroring |
| SVAPAR-104533 |
All |
Critical
|
Systems that encounter multiple node asserts, followed by a system T3 recovery, may experience errors repairing Data Reduction Pools
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Systems using Data Reduction Pools |
| Trigger |
Multiple node asserts followed by a system T3 recovery |
| Workaround |
None |
|
8.6.2.0 |
Data Reduction Pools |
| SVAPAR-105430 |
All |
Critical
|
When hardware compression is suspended mid IO to a DRP compressed volume, it may cause the IO to hang until an internal timeout is hit and a node warmstarts.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
GEN3 or later hardware with DRP compressed volumes. |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Compression, Data Reduction Pools |
| SVAPAR-107270 |
All |
Critical
|
If an upgrade from a level below 8.6.x, to 8.6.0 or 8.6.1 commits, whilst FlashCopy is preparing to start a map, a bad state is introduced that prevents the FlashCopy maps from starting.
(show details)
| Symptom |
Loss of Redundancy |
| Environment |
Systems using Global Mirror with Change Volumes or Policy-based Replication |
| Trigger |
Upgrade commit |
| Workaround |
Stop replication, or the partnership before starting the upgrade |
|
8.6.2.0 |
Global Mirror with Change Volumes, Policy-based Replication |
| SVAPAR-107547 |
All |
Critical
|
If there are more than 64 logins to a single Fibre Channel port, and a switch zoning change is made, a single node warmstart may occur.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems with Fibre Channel adapters |
| Trigger |
Switch zoning change with more than 64 logins to a single storage system port. |
| Workaround |
Reduce the number of logins to a single storage system port |
|
8.6.2.0 |
Reliability Availability Serviceability |
| SVAPAR-107734 |
All |
Critical
|
When issuing IO to an incremental fcmap volume that is in a stopped state, but has recently been expanded, and it also has a partner fcmap, may cause the nodes to go into a restart.
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Systems configured with Incremental flashcopy and reverse fcmap |
| Trigger |
Resizing volumes in an incremental partnered fcmaps |
| Workaround |
Ensure that both incremental partnered fcmaps are deleted, and then re-create a new pair if you need to resize the volumes. |
|
8.6.2.0 |
FlashCopy |
| SVAPAR-110735 |
All |
Critical
|
Additional policing has been introduced to ensure that FlashCopy target volumes are not used with policy-based replication. Commands 'chvolumegroup -replicationpolicy' will fail if any volume in the group is the target of a FlashCopy map. 'chvdisk -volumegroup' will fail if the volume is the target of a FlashCopy map, and the volume group has a replication policy.
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
None |
| Trigger |
Running either the 'chvolumegroup -replicationpolicy' or 'chvdisk -volumegroup' commands. |
| Workaround |
None |
|
8.6.2.0 |
FlashCopy, Policy-based Replication |
| SVAPAR-111257 |
All |
Critical
|
If many drive firmware upgrades are performed in quick succession, multiple nodes may go offline with node error 565 due to a full boot drive.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
Systems running 8.5.5, 8.6.0 or 8.6.1 software, with SAS drives. NVMe drives are not affected by this issue. |
| Trigger |
Performing many individual drive firmware upgrades in quick succession. This issue does not occur if a drive firmware upgrade is applied to all drives at once. |
| Workaround |
Upgrade all drives at once, instead of upgrading individual drives one at a time. |
|
8.6.2.0 |
Drives |
| SVAPAR-111705 |
All |
Critical
|
If a Volume Group Snapshot fails and the system has 'snapshotpreserveparent' set to 'yes', this may trigger multiple node warmstarts.
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Systems using Volume Group Snapshot and have 'snapshotpreserveparent' set to 'yes'. |
| Trigger |
An addsnapshot failure. |
| Workaround |
None |
|
8.6.2.0 |
FlashCopy |
| SVAPAR-111994 |
All |
Critical
|
Certain writes to deduplicated and compressed DRP vdisks may return a mismatch, leading to a DRP pool going offline.
(show details)
| Symptom |
Loss of redundancy |
| Environment |
DRP with deduplification and compression. |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Compression, Data Reduction Pools, Deduplication |
| SVAPAR-112007 |
All |
Critical
|
Running the 'chsystemlimits' command with no parameters can cause multiple node warmstarts.
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
None |
| Trigger |
Running the 'chsystemlimits' command without any parameters |
| Workaround |
Avoid running the 'chsystemlimits' command without any parameters. |
|
8.6.2.0 |
Command Line Interface |
| SVAPAR-112107 |
FS9500, SVC |
Critical
|
There is an issue that affects PSU firmware upgrades in FS9500 and SV3 systems that can cause an outage. This happens when one PSU fails to download the firmware and another PSU starts to download the firmware. It is a very rare timing window that can be triggered if two PSUs are reseated close in time during the firmware upgrade process.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
FS9500 or SV3 |
| Trigger |
Two PSUs are reseated close in time during the firmware upgrade process |
| Workaround |
None |
|
8.6.2.0 |
System Update |
| SVAPAR-93709 |
FS9500 |
Critical
|
A problem with NVMe drives may impact node to node communication over the PCIe bus. This may lead to a temporary array offline.
(show details)
| Symptom |
Loss of Access to Data |
| Environment |
None |
| Trigger |
Failing NVMe drive |
| Workaround |
None |
|
8.6.2.0 |
Drives, RAID |
| SVAPAR-104159 |
All |
High Importance
|
Nodes configured with 32GB or less of RAM, and specific 25Gb ethernet adapters, under some circumstances may run out of memory. This can cause a single node warmstart.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Nodes running 8.6.0.0 with 32GB or less of RAM, and specific 25Gb ethernet adapters |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Reliability Availability Serviceability |
| SVAPAR-104250 |
All |
High Importance
|
There is an issue whereby NVMe CaW (Compare and Write) commands can incorrectly go into an invalid state, thereby causing the node to assert to clear the bad condition
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Any host running NVMe |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Hosts, NVMe |
| SVAPAR-105727 |
All |
High Importance
|
An upgrade within the 8.5.0 release stream from 8.5.0.5 or below, to 8.5.0.6 or above, can cause an assert of down-level nodes during the upgrade, if volume mirroring is heavily utilised
(show details)
| Symptom |
Multiple Node Warmstarts |
| Environment |
Any system running volume mirroring with either a large number of volumes or high syncrate |
| Trigger |
Upgrading from 8.5.0.5 or below to 8.5.0.6 or above with heavy volume mirroring workload |
| Workaround |
Disable mirroring, or reduce syncrate to a low value during the upgrade process |
|
8.6.2.0 |
Volume Mirroring |
| SVAPAR-106874 |
FS5200, FS7200, FS7300, FS9100, FS9200, FS9500, SVC |
High Importance
|
A timing window may cause a single node warmstart, while recording debug information about a replicated host write. This can only happen on a system using Policy Based Replication.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems running PBR and code 8.6.0.0 or 8.6.0.1 |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Policy-based Replication |
| SVAPAR-107815 |
All |
High Importance
|
There is an issue between 3-Site, whilst adding snapshots on the auxfar site, that causes the node to warmstart
(show details)
| Symptom |
Multiple node warmstarts |
| Environment |
Any system that is running 8.6.0.0 with 3-Site configured |
| Trigger |
adding snapshots on the auxfar site when 3-Site is configured |
| Workaround |
None |
|
8.6.2.0 |
3-Site |
| SVAPAR-108715 |
All |
High Importance
|
The Service Assistant GUI on 8.5.0.0 and above incorrectly performs actions on the local node instead of the node selected in the GUI.
(show details)
| Symptom |
Configuration |
| Environment |
None |
| Trigger |
None |
| Workaround |
The work around is to perform Service Assistant GUI actions using the Service Assistant CLI instead. Alternatively, In the Service Assistant GUI, select a node that you are not on to perform a Service Assistant action, then when you submit the command, the action will be performed on the local node instead. |
|
8.6.2.0 |
GUI, Graphical User Interface |
| SVAPAR-108831 |
FS9500, SVC |
High Importance
|
FS9500 and SV3 nodes may not boot with the minimum configuration consisting of at least 2 DIMMS.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
FS9500 or SV3 nodes with 2 DIMMS in the node. |
| Trigger |
FS9500 or SV3 nodes that are configure with 2 DIMMS. |
| Workaround |
Ensure that the node has a minimum of 8 DIMMS installed |
|
8.6.2.0 |
Reliability Availability Serviceability |
| SVAPAR-110059 |
All |
Suggested
|
When using Storage Insights without a data collector, an attempt to collect a snap using Storage Insights may fail.
(show details)
| Symptom |
None |
| Environment |
Storage Virtualize system running 8.5.4 or higher and using Storage Insights without a data collector |
| Trigger |
Initiating a Support Package collection using Storage Insights |
| Workaround |
Disable then re-enble the Cloud Callhome service using the 'svctask chcloudcallhome -disable' and 'svctask chcloudcallhome -enable'. This will function until the next time the configuration node fails over |
|
8.6.2.0 |
Support Data Collection |
| SVAPAR-110426 |
All |
High Importance
|
When a security admin other than superuser runs security patch related commands 'lspatch' and 'lssystempatches' this can cause a node to warmstart
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
None |
| Trigger |
Any user that is not Superuser running a security patch command |
| Workaround |
Use superuser for security patching commands. |
|
8.6.2.0 |
Security |
| SVAPAR-110742 |
All |
High Importance
|
A System is unable to send email to email server because the password contains a hash '#' character.
(show details)
| Symptom |
None |
| Environment |
Configured email server requires username and password for authentication. |
| Trigger |
Password contains hash characters |
| Workaround |
Update the user password to remove any hash characters. |
|
8.6.2.0 |
|
| SVAPAR-110743 |
All |
High Importance
|
Email becoming stuck in the mail queue caused a delay in the 'upgrade commit was finished' message being sent, therefore causing 3 out of 4 nodes to warmstart, and then rejoin the cluster automatically within less than three minutes.
(show details)
| Symptom |
Single node warmstart |
| Environment |
None |
| Trigger |
Email stuck in the mail queue causing a delay in the 'upgrade commit was finished' message being sent. |
| Workaround |
None |
|
8.6.2.0 |
System Update |
| SVAPAR-110819 & SVAPAR-113122 |
All |
High Importance
|
A single-node warmstart may occur when a Fibre Channel port is disconnected from one fabric, and added to another. This is caused by a timing window in the FDMI discovery process.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
There are more than one fc switches connected to same Flash system cluster |
| Trigger |
Disconnected a Fibre Channel port from one switch, and connecting it to another switch. |
| Workaround |
None |
|
8.6.2.0 |
Fibre Channel |
| SVAPAR-110765 |
All |
High Importance
|
In a 3-Site configuration, the Config node can be lost if the 'stopfcmap or 'stopfcconsistgrp ' commands are run with the '-force' parameter
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Any cluster with 3-Site configuration |
| Trigger |
Running 'stopfcmap' or 'stopfcconsistgrp' with '-force' on the flash copy maps with vdisk in 3-site configuration. |
| Workaround |
Do not use the '-force' parameter when running either the 'stopfcmap' or 'stopfcconsistgrp' commands. |
|
8.6.2.0 |
3-Site |
| SVAPAR-111996 |
FS9500, SVC |
High Importance
|
After upgrading to a level which contains new battery firmware, the battery may be offline after the upgrade.
(show details)
| Symptom |
Loss of Redundancy |
| Environment |
FS9500 or SV3 only |
| Trigger |
Upgrading to 8.5.0.8+ or 8.6.0.0+ |
| Workaround |
We have a utility to allow us to fix this in the field. |
|
8.6.2.0 |
Reliability Availability Serviceability, System Update |
| SVAPAR-112119 |
All |
High Importance
|
Volumes can go offline due to out of space issues. This can cause the node to warmstart.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
None |
| Trigger |
Out of space condition |
| Workaround |
None |
|
8.6.2.0 |
|
| SVAPAR-112203 |
All |
High Importance
|
A node warmstart may occur when removing a volume from a volume group which uses policy-based Replication.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems with policy-based Replication |
| Trigger |
Removing a volume from a volume group which uses policy-based Replication. |
| Workaround |
None |
|
8.6.2.0 |
Policy-based Replication |
| SVAPAR-112525 |
All |
High Importance
|
A node assert can occur due to a resource allocation issue in a small timing window when using Remote Copy
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems using Hyperswap, Metro Mirror, Global Mirror, or Global Mirror with Change Volumes |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Global Mirror, Global Mirror with Change Volumes, HyperSwap, Metro Mirror |
| SVAPAR-99175 |
All |
High Importance
|
A node may warmstart due to an invalid queuing mechanism in cache. This can cause IO in cache to be in the same processing queue more than once.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Any cluster on code below 8.6.1 |
| Trigger |
Can happen when IO in cache is being processed |
| Workaround |
None |
|
8.6.2.0 |
Cache |
| SVAPAR-99354 |
All |
High Importance
|
Missing policing in the 'startfcconsistgrp' command for volumes using volume group snapshots, resulting in node warmstarts when creating a new volume group snapshot
(show details)
| Symptom |
Multiple Node Warmstart |
| Environment |
Any system configured with Volume Group Snapshot and FlashCopy |
| Trigger |
Adding a Volume Group Snapshot when a downstream legacy FlashCopy map exists. |
| Workaround |
Only create a Volume Group Snapshot if a downstream legacy FlashCopy map does not exist |
|
8.6.2.0 |
FlashCopy |
| SVAPAR-100924 |
FS9500, SVC |
Suggested
|
After the battery firmware is updated, either using the utility or by upgrading to a version with newer firmware, the battery LED may be falsely illuminated.
(show details)
| Symptom |
None |
| Environment |
SV3 or FS9500 systems |
| Trigger |
Battery firmware update |
| Workaround |
Manually toggle the battery LED with the following commands. 'satask chnodeled -on -battery <ID>' and 'satask chnodeled -off -battery <ID>' |
|
8.6.2.0 |
|
| SVAPAR-102382 |
All |
Suggested
|
Fibre Channel Read Diagnostic Parameters (RDP) indicates that a short wave SFP is installed when infact an long wave SFP is installed.
(show details)
| Symptom |
Configuration |
| Environment |
Systems with long wave SFPs running 8.5.2.0 or higher. |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
System Monitoring |
| SVAPAR-106693 |
FS9500 |
Suggested
|
Remote Support Assistance (RSA) cannot be enabled on FS9500 systems with MTM 4983-AH8
(show details)
| Symptom |
Configuration |
| Environment |
FS9500 systems with MTM 4983-AH8 |
| Trigger |
Trying to enable RSA on MTM 4983-AH8 |
| Workaround |
None |
|
8.6.2.0 |
RSA, Support Remote Assist |
| SVAPAR-107558 |
All |
Suggested
|
A Volume Group Snapshot (VGS) trigger may collide with a GMCV or Policy based Replication cycle causing the VGS trigger to fail.
(show details)
| Symptom |
Configuration |
| Environment |
Volume Group Snapshots with GMCV or Policy Based Replication |
| Trigger |
Trigger a Volume Group Snapshot |
| Workaround |
None |
|
8.6.2.0 |
FlashCopy, Global Mirror with Change Volumes, Policy-based Replication |
| SVAPAR-107733 |
All |
Suggested
|
The 'mksnmpserver' command fails with 'CMMVC5711E [####] is not valid data' if auth passphrase contains special characters, such as '!'
(show details)
| Symptom |
Configuration |
| Environment |
Any system running on or after v8.3.1.9, v8.4.0.10, or v8.5.0.7 |
| Trigger |
Using an auth passphrase containing special characters to execute the 'mksnmpserver' command |
| Workaround |
Do not include special characters in the auth passphrase |
|
8.6.2.0 |
|
| SVAPAR-107852 |
All |
Suggested
|
A Policy-Based High Availability node may warmstart during IP quorum disconnect and reconnect operations.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems using Policy-Based High Availability and IP quorum |
| Trigger |
IP quorum disconnecting and reconnecting |
| Workaround |
None |
|
8.6.2.0 |
IP Quorum |
| SVAPAR-108469 |
All |
Suggested
|
A single node warmstart may occur on nodes configure to use a secured IP partnership
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems with a secured IP partnership |
| Trigger |
Service Association goes down |
| Workaround |
None |
|
8.6.2.0 |
IP Replication |
| SVAPAR-108476 |
All |
Suggested
|
Remote users with public SSH keys configured cannot failback to password authentication.
(show details)
| Symptom |
Configuration |
| Environment |
Systems that have remote users configured that use public SSH keys |
| Trigger |
Remote users configured with public SSH keys |
| Workaround |
None |
|
8.6.2.0 |
Security |
| SVAPAR-108551 |
All |
Suggested
|
An expired token in the GUI file upload process can cause the upgrade to not start automatically after the file is successfully uploaded.
(show details)
| Symptom |
Configuration |
| Environment |
None |
| Trigger |
Start a code upgrade via GUI |
| Workaround |
Upgrade via the CLI. The other option is to log out from the GUI, then log back in to re-authenticate, then go back to the Update System view. On the Test and Update modal, select the test utility and update image files that are already on the system from the previous upload (without selecting to upload them again) |
|
8.6.2.0 |
System Update |
| SVAPAR-109289 |
All |
Suggested
|
Buffer overflow may occur when handling the maximum length of 55 characters for either Multi-Factor Authentication (MFA) or Single Sign On (SSO) client secrets
(show details)
| Symptom |
Configuration |
| Environment |
Systems that use MFA or SSO |
| Trigger |
Using a client secret with > 55 characters |
| Workaround |
Use less then 55 characters for the client secret |
|
8.6.2.0 |
Backend Storage |
| SVAPAR-110745 |
All |
Suggested
|
Policy-based Replication (PBR) snapshots and Change Volumes are factored into the preferred node assignment. This can lead to a perceived imbalance of the distribution of preferred node assignments.
(show details)
| Symptom |
Configuration |
| Environment |
Any system running policy-based Replication |
| Trigger |
Policy-based Replication enabled |
| Workaround |
None |
|
8.6.2.0 |
Policy-based Replication |
| SVAPAR-110749 |
All |
Suggested
|
There is an issue when configuring volumes using the wizard, the underlying command that is called is the 'mkvolume' command rather than the previous 'mkvdisk' command. With 'mkvdisk' it was possible to format the volumes, whereas with 'mkvolume' it is not possible
(show details)
| Symptom |
Configuration |
| Environment |
Definition of multiple volumes |
| Trigger |
Defining volumes via management GUI. |
| Workaround |
Run the 'mkvdisk' command manually. |
|
8.6.2.0 |
|
| SVAPAR-111021 |
All |
Suggested
|
Unable to load resource page in GUI if the IO group ID:0 does not have any nodes.
(show details)
| Symptom |
None |
| Environment |
Any systems that have no nodes in IO group ID:0. |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
System Monitoring |
| SVAPAR-111187 |
All |
Suggested
|
There is an issue if the browser language is set to French, that can cause the SNMP server creation wizard not to be displayed.
(show details)
| Symptom |
None |
| Environment |
Any system where the browser language is set to French |
| Trigger |
None |
| Workaround |
Switching the browser language to English, or use the CLI to configure SNMP |
|
8.6.2.0 |
System Monitoring |
| SVAPAR-111239 |
All |
Suggested
|
In rare situations it is possible for a node running Global Mirror with Change Volumes (GMCV) to assert
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Systems running GMCV |
| Trigger |
Any system running GMCV |
| Workaround |
None |
|
8.6.2.0 |
Global Mirror with Change Volumes |
| SVAPAR-111989 |
All |
Suggested
|
Downloading software with a Fix ID longer than 64 characters fails with an error
(show details)
| Symptom |
None |
| Environment |
None |
| Trigger |
Downloading a software package from Fix Central that has a Fix ID greater than 64 characters long |
| Workaround |
None |
|
8.6.2.0 |
Support Remote Assist |
| SVAPAR-111991 |
All |
Suggested
|
Attempting to create a truststore fails with a CMMVC5711E error if the certificate file does not end with a newline character
(show details)
| Symptom |
Configuration |
| Environment |
Systems using policy-based Replication, secured IP partnerships or VASA. |
| Trigger |
Attempting to create a truststore |
| Workaround |
Ensure the certificate file ends with a newline character |
|
8.6.2.0 |
IP Replication, Policy-based Replication, vVols |
| SVAPAR-111992 |
All |
Suggested
|
Unable to configure policy-based Replication using the GUI, if truststore contains blank lines or CRLF line endings
(show details)
| Symptom |
Configuration |
| Environment |
Systems configured with policy-based Replication |
| Trigger |
Attempting to configure policy-based Replication |
| Workaround |
Ensure the certificate file used to create the truststore contains no blank lines and uses LF line endings instead of CRLF line endings. |
|
8.6.2.0 |
GUI, Policy-based Replication |
| SVAPAR-112243 |
All |
Suggested
|
Prior to 8.4.0 NTP was used. After 8.4.0 this was changed to 'chronyd'. When upgrading from a lower level to 8.4 or higher, systems may experience compatibility issues.
(show details)
| Symptom |
Configuration |
| Environment |
Systems that have upgrade to 8.4 or higher |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
|
| SVAPAR-112711 |
All |
Suggested
|
IBM Storage Virtualize user interface code will not respond to a malformed HTTP POST with expected HTTP 401 message.
(show details)
| Symptom |
None |
| Environment |
IBM Storage Virtualize GUI |
| Trigger |
Malformed HTTP POST |
| Workaround |
None |
|
8.6.2.0 |
GUI |
| SVAPAR-114081 |
All |
Suggested
|
The lsfabric command may show FC port logins which no longer exist. In large environments with many devices attached to the SAN, this may result in an incorrect 1800 error being reported, indicating that a node has too many logins.
(show details)
| Symptom |
Configuration |
| Environment |
None |
| Trigger |
None |
| Workaround |
Warmstart each node in turn, to remove the invalid entries from lsfabric. |
|
8.6.2.0 |
Reliability Availability Serviceability |
| SVAPAR-96952 |
All |
Suggested
|
A single node warmstart may occur when updating the login counts associated with a backend controller.
(show details)
| Symptom |
Single Node Warmstart |
| Environment |
Any system with backend external controllers. |
| Trigger |
None |
| Workaround |
None |
|
8.6.2.0 |
Backend Storage |