IBM Storwize V7000 yeni firmware çıktı.
Yeni Sürüm 7.1.0.1. Yenilikler ise
IBM Storwize V7000
++++++++++++++++++++++++++++++++++++++++
CONTENTS
1. Introduction
2. Available Education
3. Pre-Requisites
4. System Upgrade Information
5. Software Levels
6. Problems Resolved and New Features
7. Further Documentation
8. Known Issues and Restrictions in this Level
9. Maximum Configurations
10. Supported Hardware
-------------------------------------------------------------------------------
1. Introduction
This document describes how to install version 7.1.0.1 of the IBM Storwize V7000.
This release of software is a service release and delivers fixes to resolve the APARs detailed in section 6.
Please refer to the Recommended Software List and Supported Hardware List on the support website:
http://www.ibm.com/storage/support/storwize/V7000
-------------------------------------------------------------------------------
2. Available Education
A course on Storwize V7000 Planning and Implementation is available. For further information or enrolment, contact your local IBM representative.
Visit the support website for online learning materials and tutorials, IBM Redbooks and training information.
-------------------------------------------------------------------------------
3. Pre-Requisites
Before installing this software level please check the following pre-requisites are met. Also please note the concurrent upgrade (upgrade with I/O running) restrictions.
Performance of the system will be degraded during the software upgrade process while node canisters are taken offline to perform the upgrade and the write cache is flushed when each node is restarted. IBM recommends you perform the upgrade at a time of lower overall I/O activity and when you do not expect significant spikes in the system workload.
If you are performing a concurrent software upgrade, you must first ensure that all host paths are available and operating correctly.
Check there are no unfixed errors in the event log or in the service GUI. Use normal service procedures to resolve any errors before proceeding.
Before upgrading, IBM recommends using the software upgrade test utility "upgradetest". Refer to the following URL for further information:
http://www.ibm.com/support/docview.wss?uid=ssg1S4000585
If you are running a version of Storwize V7000 software older than 6.1.0.0 then you will have to perform multiple upgrades to install the 7.1.0.1 software on your system.
Please see the following web page for the full upgrade compatibility matrix.
http://www.ibm.com/support/docview.wss?uid=ssg1S1003705
Note: Once an upgrade has completed, it is not possible to downgrade the software to an earlier level without deleting and manually rebuilding the system in its entirety, including restoring all volume data from an external backup.
-------------------------------------------------------------------------------
4. System Upgrade Information
Direct upgrades to V7.1 from V6.1 are supported only for systems that do not have iSCSI configured. For these upgrade paths it is mandatory that the SAN Volume Controller and Storwize V7000 Software Upgrade Test Utility is run prior to the upgrade. This will ensure that the system configuration does not include iSCSI, permitting the upgrade to V6.4.x to be applied.
http://www.ibm.com/support/docview.wss?uid=ssg1S4000585
When upgrading an existing system running V6.3 or earlier to V6.4, an alert will be logged for each node installed with 10Gb Ethernet hardware, indicating that the FCoE functionality has not yet been enabled.
The alert is:
- Node error : 841 (as seen on node front panel or service assistant)
- Cluster error: 1199 (as seen using system management GUI/CLI)
- Description : Detected hardware needs activation
These alerts are expected and do not indicate an actual error. Any 10Gb iSCSI functions previously in use continue to operate as normal.
Once the system software upgrade has completed, the FCoE functionality can be enabled on each node by following the fix procedures for these events using the management GUI.
Note that the FCoE activation procedure involves a node reboot and it is therefore recommended to allow time for host multipathing to recover between activation of different nodes in the same I/O group.
Refer to the following Flash for further information:
http://www.ibm.com/support/docview.wss?uid=ssg1S1004195
It is not possible to activate the FCoE function if the system has a remote copy partnership with another system which is running a software release earlier than 6.4.0.0
-------------------------------------------------------------------------------
5. Software Levels
2076 Software:
2076 Release Level 7.1.0.1 (79.6.1306101000)
-------------------------------------------------------------------------------
6. Problems Resolved and New Features
New features in 7.1.0
Ability to configure FC ports for specific traffic types
This release contains all fixes included in the 6.4.1.4 release.
APARs resolved in this release (7.1.0.1):
Critical Fixes
IC93087 Loss of access to data due to internal bus error
IC83684 Hardware fault in one node canister causes reboot of both node canisters
IC86864 Node canister shutdown during battery firmware upgrade
IC88865 Loss of access to data when system is logging a very large number of errors about backend storage
IC90295 Node warmstarts during migrations caused by persistent reservations on image mode managed disks
IC90476 Loss of access to data when an LDAP server 0 is not configured
IC90637 Node warmstarts caused by RNID frames sent to FCoE ports from SAN management tool
IC90872 Multiple node warmstarts caused by slow I/O from backend storage
IC91255 Using two or more FlashCopy maps with the same target volume may result in inconsistent data on the target volume
High Importance Fixes
IC83241 Single node warmstart due to delays processing Global Mirror IOs
IC86399 Single node warmstart when significantly increasing the size of a volume
IC86591 Slow response time when host fails to send data after system sends XFER_RDY
IC86971 Global Mirror slowdown when host fails to send data after system sends XFER_RDY
IC87048 Single node warmstart due to inter-cluster communication issues
IC88869 iSCSI Performance issues
IC90060 Single node warmstart caused by timing window in EasyTier
IC90442 Single node warmstart caused by unexpected settings in FCP frame
IC90821 Single node warmstart caused by frequent GUI logins
IC92028 Cache not sending enough IOs to compression
IC92138 Single node assert when force deleting a volume involved in FlashCopy maps
IC92386 Single node warmstart during software upgarde commit due to slow IO response times for Thin Provisioned volumes
IC92803 Single node assert caused by SCSI Compare and Write command
Suggested Fixes
IC93080 Additional enclosure is seen after cluster recovery procedure
IC93081 Enclosure becomes temporarily degraded
IC93083 Flash Copy exceeds configured background copy rate
IC93088 1625 errors when removing unmanaged mdisk
IC84694 Incorrect Fix Procedure for 1840 event
IC79537 Invalid 1048 event logged when canister is offline
IC82729 1692 Fix Procedure not marking event as fixed
IC86279 Incorrect title for Edit Port panel in iSCSI GUI
IC86505 Fibre Channel ports will not function if connected to a switch port with a Domain ID ending in 'FF'
IC87229 GUI shows empty tables when CPU utilisation is high
IC87339 GUI dialog hangs at Synchronizing memory cache after changing enclosure ID
IC88220 Slow boot time and possible node warmstart during the detection of ethernet ports
IC89258 Array members constantly exchanging after changing enclosure ID
IC89378 DS3000, DS4000 and DS5000 managed disks not using preferred controller
IC89661 Unable to create snap package if too many files exist
IC90771 Drive replacement fix procedure does not remove old drive
IC91142 Temporarily unable to create FlashCopy of Global Mirror Change Volume Secondary volume after stopping the Global Mirror
IC91336 Intel FCoE software initiator fails to detect LUNS
IC91993 GUI shows wrong Metro/Global Mirror direction when stopped
IC92075 Single node assert due to resource leak in FCoE driver
-------------------------------------------------------------------------------
7. Further Documentation
The latest version of all Storwize V7000 documentation can be downloaded in PDF format from the support website:
http://www.ibm.com/storage/support/storwize/V7000
-------------------------------------------------------------------------------
8. Known Issues and Restrictions in this Level
Moving Volumes to Another I/O Group Without Stopping Host Activity is Not Supported for All Operating Systems
http://www.ibm.com/support/docview.wss?uid=ssg1S1004125
Intra-Cluster Global Mirror Not Supported With V6.x
Refer to the following flash for more information on this restriction:
http://www.ibm.com/support/docview.wss?uid=ssg1S1003725
SAN Volume Controller Inter-cluster Metro Mirror and Global Mirror Compatibility Cross Reference
Refer to the following flash for more information on this restriction:
http://www.ibm.com/support/docview.wss?uid=ssg1S1003646
Use of a standards-compliant browser, such as Firefox, is recommended for using the SVC Management GUI. Use of Internet Explorer is supported but may result in slower performance of the GUI.
If using Firefox to access the 5.1.0 SVC Console (GUI) to perform a software upgrade from 5.1.0 to 6.4, please ensure that third-party cookies are enabled. This can be achieved via the following steps in Firefox:
1) Tools > Options
2) Click the Privacy tab
3) Make sure that both the "Accept cookies from sites" and the "Accept third-party cookies" checkboxes are checked.
If a SAN Volume Controller or Storwize V7000 Code Upgrade Stalls or Fails then Contact IBM Support for Further Assistance
http://www.ibm.com/support/docview.wss?uid=ssg1S1002894
-------------------------------------------------------------------------------
9. Maximum Configurations
The maximum configurations for 7.1.0.1 are documented in the SVC 7.1 Configuration Limits and Restrictions document which is available from:
http://www-01.ibm.com/support/docvie...d=ssg1S1004378
-------------------------------------------------------------------------------
10. Supported Hardware
This release of Storwize V7000 software is supported on the following node hardware types:
Control enclosures:
* 2076-112
* 2076-124
* 2076-312
* 2076-324
Expansion enclosures:
* 2076-212
* 2076-224
-----------------------