Fix Readme
Abstract
Welcome to IBM Storage Fusion 2.6.1 release. This release note contains information about IBM Storage Fusion HCI and IBM Storage Fusion deployments.
Content
What is new
For more information on the new features and improvements for IBM Storage Fusion 2.6.1 release, see What is new.
Planning and prerequisites
The planning and prerequisites section provides important information to review before the installation of this release version.
For more information on planning and prerequisites for IBM Storage Fusion HCI 2.6.1 release, see Planning and prerequisites for IBM Storage Fusion HCI.
For more information on planning and prerequisites for IBM Storage Fusion 2.6.1 release, see Planning and prerequisites for IBM Storage Fusion.
Installation instructions
The install instructions section provides the instructions to install the product.
IBM Documentation
The IBM Documentation provides an entry point to the product documentation. You can view, browse, and search for online information related to the product.
Known issues and troubleshooting
The troubleshooting section provides information about known issues, tips and tricks to troubleshoot the product.
Supporting component versions
- Red Hat OpenShift Container Platform
- 4.13 for IBM Storage Fusion
- 4.12 for IBM Storage Fusion HCI
For more information, see Red Hat OpenShift Container Platform documentation.
Note: The OpenShift Container Platform 4.13 supports only Data Foundation service, Data Cataloging service, and Backup & Restore service. It does not support Global Data Platform service and Backup & Restore (Legacy) service.
- IBM Spectrum Scale 5.1.7 efix
- IBM Data Cataloging service 2.1.2
- IBM Data Foundation service 4.13
- Backup and restore (legacy) service 10.1.12.450
- Backup and Restore service 2.6.1
- For supported IBM Cloud Paks versions, see IBM Cloud Paks support for IBM Storage Fusion.
Field fixes
| Ticket No. | Description | Severity |
| 23956 | Firmware upgrade failed at 30% with error code - BMYUP2106. The issue is due to the conflict in the pod name that belongs to the job. There was an existing completed job with the related pod name containing the same substring. While getting the current job status, it queried the completed job/pod status instead of the current job resulting in the error code. | Major |
| 23247 | Install Scale Pods did not start during Stage3 Install due to mismatch in Storage VLAN values after a non-default value was entered during Stage 1 Install. Changes made to configure the Storage VLAN on switch if previously configured VLAN does not match the input VLAN. | Major |
| 22680 | A non-call home event is now generated when a switch fan fails. | Normal |
| 24562 | When the BMC of a node is getting reinitialized, the node becomes inaccessible and its monitoring fails. This is an expected hardware behavior and the connectivity loss is only temporary. If you find a false Call Home event created due to this process, increase the event threshold to a higher value for the event ID BMYCO0003. This configurable value is available since the IBM Storage Fusion 2.3 release. The suggested value is 50-55 on IBM Storage Fusion 2.5.2. In IBM Storage Fusion 2.6.1, the default threshold of 10 cannot be reached within 5 minutes time of BMC unreachable state, and a false Call Home gets raised. | Major |
| 24163 | When the BMC of the node is being reinitialized the node is inaccessible and node monitoring fails. This is expected hardware behavior and the connectivity loss is only temporary. To prevent unnecessary call home notifications during this time, the interval at which the test connection is checked has been increased. In addition, the threshold value for event ID BMYCO0003 can be manually increased starting in 2.6.1. | Major |
| 25593 | IBM Storage Fusion operator does not report status "Succeeded" or goes from "Succeeded" to "Installing > Pending > InstallReady" status. This behavior was observed on Red Hat OpenShift Platform version (OCP) 4.12.25 or higher only. This issue has been addressed in 2.6.1; starting at this release version, no manual intervention is needed. | Normal |
| 25819 | Intermittent Storage Fusion restore failures due to datamover messages being missed by the underlying agent. This issue has been addressed in 2.6.1. | Normal |
| 24839 | If an application restore was initiated without choosing to restore the resources as well, the restore process would fail. The issue has been addressed and the restore process allows user to specify type of resources to restore. For example, restore only persistent volumes or only application resources or both. | Normal |
Notifications
MyNotifications enables you to adopt a proactive approach towards preventing problems. Sign up to stay informed of critical IBM software support updates and receive immediate notifications of Security Bulletins and Flashes that are tailored to your needs and delivered directly to you. For more information, see MyNotifications.
[{"Type":"MASTER","Line of Business":{"code":"LOB26","label":"Storage"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSFETU","label":"IBM Storage Fusion"},"ARM Category":[{"code":"a8m3p0000000rXCAAY","label":"SW"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"2.6.0"}]
Was this topic helpful?
Document Information
Modified date:
30 August 2023
UID
ibm17028202