IBM V7. 7. x Supported Hardware List, Device Driver, Firmware and Recommended Software Levels for SAN Volume Controller. The documents titled Supported Hardware List and Recommended Software Levels provide the operating systems, Host adapters, SAN fabric elements, RAID controllers and selected other hardware that have been tested or qualified by IBM. Note If you are upgrading from a previous version of BizFlow, before continuing please contact BizFlow technical support for installation instructions. SiteAssets/TEC546668_Embeded/546668h.gif' alt='Hpux Get Driver Version' title='Hpux Get Driver Version' />This page combines the previously separate Software and Hardware support matrices. For operating systems, we show the latest tested release levels and service packs. Only the listed operating systems are supported. For host adapters, SAN fabric elements and RAID controllers, we list our currently recommended firmware andor BIOS levels and formally support only the hardware listed. While these levels are not mandatory levels for a customer to be supported by IBM, they are the recommended levels. There may be known operational issues with older firmware and BIOS levels and, in these cases, a customer working with the IBM Support center may be directed to upgrade a component to a recommended level. SVC will support all OS applications at any level that run to the standard block level OS interface. This includes such applications as Oracle, HP Virtual Connect, etc. Note The levels shown in italic text indicate previously recommended levels. The level shown in bold text indicates the latest recommended level. EOL End of Life Where interoperability items have gone end of life out of support and are no longer supported by the vendor either generally or by extended service contact IBM will continue to support the environment on a best can do basis. Where issues occur which are deemed by IBM support to be directly related to items which are no longer generally supported by the vendor IBM may direct customers to upgrade a component to a recommended level. Whilst IBM recommends these levels based upon the most recent testing, the following levels were tested against previous versions of SVC and IBM will support the use of these levels with SVC V7. If you have Interoperability requirements which are not listed in this document please contact your IBM Account Representative 1. Gbps Fibre Channel Node Connection. Please see SSIC for supported 1. Gbps Fibre Channel configurations supported with 1. Gbps node hardware. A Sysadmins Unixersal Translator ROSETTA STONE OR What do they call that in this world Contributions and corrections gratefully accepted. Please help us fill. Note 1. 6Gbps Node hardware is supported when connected to Brocade and Cisco 8. Gbps or 1. 6Gbps fabrics only. Direct connections to 2. Release+Review+Official+Name+Release+Identifier+Architecture.jpg' alt='Hpux Get Driver Version' title='Hpux Get Driver Version' />Gbps or 4. Gbps SAN or direct host attachment to 2. Gbps or 4. Gbps ports is not supported. Other configured switches which are not directly connected to the. Gbps Node hardware can be any supported fabric switch as currently listed in SSIC. Previously Supported Levels. SVC Version. Previous Support Levels. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V7. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V7. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V7. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V7. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V7. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V7. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V6. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V6. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V6. SAN Volume Controller Supported Hardware List, Device Driver, Firmware and Recommended Software Levels V6. Supported Hardware List, Device Driver and Firmware Levels for SAN Volume Controller. Recommended Software Levels for SAN Volume Controller. Supported Hardware List, Device Driver and Firmware Levels for SAN Volume Controller. Recommended Software Levels for SAN Volume Controller. Supported Hardware List, Device Driver and Firmware Levels for SAN Volume Controller. Recommended Software Levels for SAN Volume Controller. Supported Hardware List, Device Driver and Firmware Levels for SAN Volume Controller. Recommended Software Levels for SAN Volume Controller. Supported Hardware List, Device Driver and Firmware Levels for SAN Volume Controller. Recommended Software Levels for SAN Volume Controller. Supported Hardware List, Device Driver and Firmware Levels for SAN Volume Controller. Recommended Software Levels for SAN Volume Controller SAN Volume Controller Supported Drive Types. SVC Easy Tier Function Supported Configurations. Tier 0 Storage. Tier 1 Storage. Tier 2 Storage. Notes. Internal or externally virtualized flash storage. Internal or externally virtualized enterprise HDDs 1. Internal or externally virtualized nearline HDDs. Easy Tier is not supported in any configuration where flash storage is not exclusively being used as the Tier 0 storage. Hpux Get Driver Version' title='Hpux Get Driver Version' />News November 25, 2017. Mesa 17. 2. 6 is released. This is a bugfix release. November 10, 2017. Mesa 17. 2. 5 is released. This is a bugfix release. Download Software Install Rslogix 5000 Support For This Firmware. October 30, 2017. If there are no enterprise HDDs in the pool Internal or externally virtualized nearline HDDs. Split Cluster Configuration Documentation. SAN Volume Controller Code Compatibility. SAN Volume Controller Non Disruptive Volume Move. The following Fibre Channel attached host types are supported for non disruptively moving a volume between IO groups control enclosures. OS Version. NPIV or v. SCSIMultipathing. Clustering. Notes. AIX7. 1 TL1 with VIOS 2. FP2. 5 SP0. 2NPIVSDDPCM 2. SDDPCM 2. 6. 5. 1. SDDPCM 2. 6. 6. 0. SDDPCM 2. 6. 7. 0. SDDPCM 2. 6. 8. 0. Non Disruptive Volume Move may leave the same Volume mapped to different hosts in the same host cluster using different SCSI IDs. If the host cluster cannot tolerate this configuration then non disruptive move cannot be used. For Host Clusters which cannot tolerate this condition users should quiesce their hosts, perform the NVDM steps to move the volumes to another IO group, reassign the SCSI IDs manually, then reconfigure and restart the hosts. In SDDPCM 2. 6. 4. Preferred paths are not detected after moving a volume to a new IO group. SDDPCM 2. 6. 3. 2. SAN Boot is supported. NPIV is supported. AIX7. 1 TL2 with VIOS 2. SCSISDDPCM 2. 6. 4. SDDPCM 2. 6. 5. 1. SDDPCM 2. 6. 6. 0. SDDPCM 2. 6. 7. 0. SDDPCM 2. 6. 8. 0. SAN Boot is supported. SCSI only. NPIV is not supported in this configuration. AIX7. 1 TL2 with VIOS 2. NPIVSDDPCM 2. 6. 4. SDDPCM 2. 6. 5. 1. SDDPCM 2. 6. 6. 0. SDDPCM 2. 6. 7. 0. SDDPCM 2. 6. 8. 0. NPIV is supported. SAN Boot Supported, boot path should be updated after NDVMIn NPIV configuration when RAW IO is running over a disk, some enabled paths of that disk may get failedinvalid during NDVM. The failedinvalid paths will be recovered automatically by AIX path health check hence application IO will not be impacted. Disks used by filesystem do not have such issue. SDDPCM 2. 6. 4. 0. SDDPCM 2. 6. 5. 1. SDDPCM 2. 6. 6. 0. SDDPCM 2. 6. 7. 0. SDDPCM 2. 6. 8. 0v. SCSI only. NPIV is not supported in this configuration. AIX6. 1 TL3 with VIOS 2. FP 2. 4 SP 0. 2v. SCSIAIX7. 1 with VIOS 2. SCSIPower. HA 7. 1 Supported. In NPIV configuration when RAW IO is running over a disk, some enabled paths of that disk may get failedinvalid during NDVM. The failedinvalid paths will be recovered automatically by AIX path health check hence application IO will not be impacted. Disks used by filesystem do not have such issue. SVC host type should be changed to TPGSAIX7.