Atto Thunderlink Enables Vmware Esxi(tm For Mac

Posted on  by admin

Abstract The document titled Supported Hardware List, Device Driver, Firmware and Recommended Software Levels for the IBM Storwize V7000 provides the operating systems, Host adapters, SAN fabric elements, RAID controllers and selected other hardware that have been tested or qualified by IBM. 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 and/or 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 Centre may be directed to upgrade a component to a recommended level. IBM Storwize V7000 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. HP 9000 Series Servers (PA-RISC 64bit) & HP Itanium ServersThe following patches should be applied to the base OS: BUNDLE11i(B.3) HWEnable11i(B.064) FEATURE11i(B.063) QPK1123(B.064) Set PV (Physical Volume) timeout to 60 seconds when using PV Links.

Enables

This is to avoid I/O timeouts during fabric maintenance and IBM Storwize V7000 CCLs (Concurrent code loads) BUNDLE11i B.3 Required Patch Bundle for HP-UX 11i v2 (B.11.23), FEATURE11i B.070a Feature Enablement Patches for HP-UX 11i v2, HWEnable11i B.070 Hardware Enablement Patches for HP-UX 11i v2, OnlineDiag B.11.23.10.05 HPUX 11.23 Support Tools Bundle, QPKAPPS B.072 Applications Patches for HP-UX 11i v2, QPKBASE B.072 Base Quality Pack Bundle for HP-UX 11i v2, HPUX11i-OE-MC B. HP-UX Mission Critical Operating Environment Component. LUN numbering: When mapping vdisks to hosts, only LUNs in the range 0 to 254 can be used Expanding Volumes on the IBM Storwize V7000 is supported (upon volume expansion, the disk label still shows original size however the disk needs to be re labelled and AdvFS file system extended) Shrinking IBM Storwize V7000 Volumes is not supported IBM Storwize V7000 Copy Services Configuration / LUN Synthesis: With AdvFS, it is possible to map a FC target to the same machine as a FC source. In order to use the same domain name, manual link to the new disk (ln -s /dev/disk/dskNc) has to be created in the /etc/fdmns/domainname directory.

IBM Storwize V7000 supports Server Blades that meet all of the following criteria; 1. The Server blade contains Qlogic and Emulex generic chip sets running the IBM or equivalent supported Drivers; and 2. These generic chip sets and drivers are present in the IBM Storwize V7000 support matrix for HBAs used in non Blade servers; and 3. The Server blade is running an OS that is present in the IBM Storwize V7000 support matrix; and 4. Either a Fibre Channel pass through module is used in the Blade server chassis to connect the Blades to an external FC network; or The Fibre Channel switch module used in the Blade server chassis is equivalent (in the sense it runs the same microcode on the same switch hardware base) to a discrete Fibre Channel switch that is already listed in the IBM Storwize V7000 support matrix. Examples of specific BladeCentre configurations that IBM includes in IBM Storwize V7000 interoperability testing currently include: HS & LS Intel & AMD Models.

Microsoft Windows 2008 Supported without multipathing Yes Supported with multipathing Yes: Native multipathing (MPIO) SAN Boot No iSCSI Host Attachment Restrictions. Maximum of 64 iSCSI hosts per I/O group, maximum of 256 iSCSI hosts per cluster. ISCSI Host Attachment Recommendations These configuration recommendations are not mandatory for a supported configuration. For best performance:. iSCSI host and IBM Storwize V7000 Ethernet ports should be directly connected to the same switch. Ethernet switches should be used in preference to hubs.

Atto Thunderlink Enables Vmware Esxi(tm For Mac

iSCSI host and IBM Storwize V7000 node Ethernet ports should be running at the same link speed. For best results, all links used for iSCSI traffic should operate at 1Gb/s full duplex. If you are using IBM Tivoli Storage Productivity Center (TPC) or equivalent application to monitor the performance of your IBM Storwize V7000 cluster, it is recommended to separate this management traffic from iSCSI host I/O traffic, such as using node port 1 for management IPs and node port 2 for iSCSI IPs. Controllers Please refer to the Configuration Guide which details the recommended customer configurable settings that should be applied for each storage controller type. Dynamic expansion of controller LUNs is not supported Please refer the for the latest recommended DS4000 client software and RDAC levels Please refer the for specific configuration guidelines, cabling requirements & restrictions when attaching EXP810 to DS4300 & DS4500 DS4000 copy services (FlashCopy, VolumeCopy, MetroMirror) can be used with Storwize V7000 RAID-5 Array size must be 4+1 or larger. RAID-6 Array size must be 4+1+1 or larger. DS4000 range maximum LUNs per partition is currently 256, limiting the number of LUNs from a single DS4000 to a single Storwize V7000 cluster to 256.

Atto Thunderline Enables Vmware Esxi(tm For Mac

Please see the following DS4K flashe s If you have 07.36.08.xx code, you MUST contact DS4000 support prior to upgrading to your DS4000 firmware. The 07.36.08.xx release is no longer supported. Dynamic expansion of controller LUNs is not supported Please refer the for the latest recommended DS5000 client software, RDAC levels, specific configuration guidelines, cabling requirements & restrictions when attaching EXP5000 and EXP810 DS5000 copy services (FlashCopy, VolumeCopy, MetroMirror) can be used with Storwize V7000. DS5000 range maximum LUNs per partition is currently 256, limiting the number of LUNs from a single DS5000 to a Storwize V7000 cluster to 256.

RAID-5 Array size must be 4+1 or larger RAID-6 Array size must be 4+1+1 or larger. 07.36.12.xx is no longer available,.

Compellent storage is not supported in NPIV mode with Storwize V7000 Compellent Advanced Functions are not supported with Storwize V7000 Switches IBM Storwize V7000 supports NPIV products in the SAN with the restriction that these products can only be used for host attachment. An example of an NPIV product is the Brocade Access Gateway module for the BladeCenter.

FCIP technology listed on the IBM SAN Support pages can be used in IBM Storwize V7000 configurations for the following uses: 1) iSCSI host attachment. Please refer to the iSCSI Host Attachment section for more information. 2) Links between two IBM Storwize V7000 clusters in a Metro Mirror or Global Mirror configuration. Please refer to the Configuration Guide for details. V6.6.0.15 V6.8.0.03 Other Hardwar e & Software Technologies for extending the distance between two IBM Storwize V7000 clusters can be broadly divided into the following two categories. Inter Cluster Fibre Channel Extenders Fibre channel extenders simply extend a fibre channel link by transmitting fibre channel packets across long links without changing the contents of those packets. IBM has tested a number of such fibre channel extender technologies with IBM Storwize V7000 and will support fibre channel extenders of all types provided that they are planned, installed and operated as described in the Configuration Guide document.

Inter Cluster SAN Routers SAN routers extend the scope of a SAN by providing 'virtual nPorts' on two or more SANs. The router arranges that traffic at one virtual nPort is propagated to the other virtual nPort but the two fibre channel fabrics are independent of one another. Thus nPorts on each of the fabrics cannot directly log into each other. There are distance restrictions imposed due to latency. The amount of latency which can be tolerated depends on the type of copy services being used (Metro Mirror or Global Mirror). Details of the maximum latencies supported can be found in the Software Installation and Configuration Guide: Due to the more complex interactions involved, IBM explicitly tests products of this class for interoperability with IBM Storwize V7000.

The following SAN Routers are supported for use with IBM Storwize V7000 when planned, installed and operated as described in the Configuration Guide document.