IBM Storwize V7000, Introduction And Implementation Manual

Page: 615 / 670

Chapter 13. Maintenance and troubleshooting
595
13.6.2 Upgrading the system software using IBM Flex System V7000 Storage
Node management GUI
Upgrading the software automatically
During the automatic upgrade process, each node in a system is upgraded one at a time, and
the new code is staged on the nodes. While each node restarts, there might be some
degradation in the maximum I/O rate that can be sustained by the system. After all the nodes
in the system are successfully restarted with the new code level, the new level is
automatically committed.
During an automatic code upgrade, each node of a working pair is upgraded sequentially. The
node that is being upgraded is temporarily unavailable and all I/O operations to that node
fails. As a result, the I/O error counts increase and the failed I/O operations are directed to the
partner node of the working pair. Applications do not see any I/O failures. When new nodes
are added to the system, the upgrade package is automatically downloaded to the new nodes
from IBM Flex System V7000 Storage Node.
The upgrade can normally be performed concurrently with normal user I/O operations.
However, there is a possibility that performance could be impacted. If any restrictions apply to
the operations that can be performed during the upgrade, these restrictions are documented
on the IBM Flex System V7000 Storage Node website that you use to download the upgrade
packages. During the upgrade procedure, the majority of configuration commands are not
available.
This automatic procedure provides a unified mechanism to upgrade the entire system in a
coordinated process with no user intervention. Excluding drives, when a node is rebooted as
part of the clustered system upgrade, the system checks that it is at the correct level. When
the system detects that the hardware is not running at the expected level, the system applies
the correct firmware.
Attention:
򐂰
If you experience failover issues with multipathing driver support, resolve these issues
before you start normal operations.
򐂰 Ensure that you have no unfixed errors in the log and that the system date and time are
correctly set. Start the Fix Procedures, and ensure that you fix any outstanding errors
before you attempt to concurrently upgrade the code.
򐂰 If you want to upgrade without host I/O, shut down all hosts before you start the
upgrade.
򐂰 Some code levels support upgrades only from specific previous levels, or the code can
be installed only on certain hardware types. If you upgrade to more than one level
above your current level, you might be required to install an intermediate level. For
example, if you are upgrading from level 1 to level 3, you might need to install level 2
before you can install level 3. For information about the prerequisites for each code
level, see the IBM Support website.
Tip: Use the Software Upgrade Test Utility to help you find potential upgrade-related
problems. See the following link for more information about this Software Upgrade Test
Utility and directions to download the utility:
http://www-01.ibm.com/support/docview.wss?uid=ssg1S4000585