SUSE Linux Enterprise Server 1. SP4. Storage Administration Guide. Copyright (C) 1. 98. UpdateStar is compatible with Windows platforms. UpdateStar has been tested to meet all of the technical requirements to be compatible with Windows 10, 8.1, Windows 8.Free Software Foundation, Inc. Temple Place - Suite 3. Boston, MA 0. 21. USA Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software- -to ensure that the software is free for all its users. This guide provides information about how to manage storage devices on a SUSE Linux Enterprise Server 11 Support Pack 4 (SP4) server. This guide is intended. 2.1 What's New in Enterprise Manager Cloud Control 12c Release 5 (12.1.0.5) Oracle Cloud Management (Hybrid Cloud) Oracle Cloud Management (Hybrid Cloud). Verint solutions capture, distill, and analyze complex and underused information sources (such as voice, video, and unstructured text) to help organizations make. Nexus 7700 10-Slot Switch: Access product specifications, documents, downloads, Visio stencils, product images, and community content. This General Public License applies to most of the Free Software Foundation’s software and to any other program whose authors commit to using it. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to ensure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things. To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it. For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must ensure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software. Also, for each author’s protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors’ reputations. Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone’s free use or not licensed at all. The precise terms and conditions for copying, distribution and modification follow. GNU GENERAL PUBLIC LICENSE TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The “Program”, below, refers to any such program or work, and a “work based on the Program” means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does. You may copy and distribute verbatim copies of the Program’s source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program. You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a). You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a). Accompany it with the complete corresponding machine- readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b). Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine- readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, c). Accompany it with the information you received as to the offer to distribute corresponding source code. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable. If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. VMware Compatibility Guide - Storage/SAN Search. VMware ESX software has been tested and deployed in a variety of storage network environments. This guide describes the storage devices currently tested by VMware and its storage partners. ESX, ESXi Embedded and ESXi Installable are equivalent products from a storage compatibility perspective. In this guide we only explicitly list ESX compatibility information. If a product is listed as supported for ESX, the product is also supported for ESXi Embedded and ESXi Installable corresponding versions. Note: Boot from SAN (Fibre Channel, Fibre Channel over Ethernet, SAS, or i. SCSI) is not supported with ESXi version 4. If you are having a technical issue with 3rd party HW/SW and it is not found on this list, please refer to our 3rd Party HW/SW support policy at http: //www. Third. Party. html. VMware works closely with each of its OEMs to drive towards mutual support of ESX at the time of announcement. Due to different product release cycles, levels of testing, and OEM agreements, not all OEM devices will be supported at the general availability date of a new version of ESX. We recommend contacting the OEM vendor for the best information on when their device is planned to be certified with Virtual Infrastructure. For further details about array firmware, storage product configurations and best practices, please contact the storage vendor. NOTE: The use of an external enclosure, or JBOD connected to a supported SAS/SCSI controller in a supported server is supported, as long as there is no disk sharing among multiple servers or SAS/SCSI cards. This SAN HCL lists storage devices starting with ESX 3. It does not include older ESX 2. Please contact your storage vendors if you do not find devices certified in the SAN HCL list. Microsoft Windows Failover Cluster with ESX Windows Clustering refers Cluster Services in Windows operating systems in a shared disk configuration between two virtual machines or a virtual machine and a physical system. Such clustering is certified only with a subset of arrays listed in this guide. Previously Failover Clustering was called MSCS. Before installing VMware ESX software with your storage array, please examine the lists on the following pages to find out whether your array and configuration are supported. Please refer to your storage vendor for more information and configuration details. Windows Failover Cluster support with ESX 3. Below table shows the supported list of Windows OS, FC HBA speed and drivers. Windows Failover Cluster support with ESX 3. MSCS/Failover cluster is supported with ESX 3. VMs running - Windows 2. SP4 and - Windows 2. SP2. Only 4. Gb Emulex and Qlogic FC HBAs are supported. Windows Failover Cluster support with ESX 4. With native multipathing (NMP), clustering is not supported when the path policy is set to round robin. Please see 'Setup for Failover Clustering and Microsoft Cluster Services' for limitations on MSCS support with PSA. Virtual SCSI adapter and Windows OS supported- LSI Logic Parallel for Windows Server 2. SP4- LSI Logic Parallel for Windows Server 2. RTM (x. 86 and x. SP2- LSI Logic SAS for Windows Server 2. SP1. 2. Only 4. Gb Qlogic and Emulex Fibre Channel HBAs are supported. The driver versions supported are as follows: qla. PSA Plug- ins with ESX 4. ESX 5. x. Array operating modes and path selection behavior are supported through the Pluggable Storage Architecture (PSA) framework. Storage partners may (1) provide their own Multi- Pathing Plug- ins (MPP), (2) use Storage Array Type Plug- ins (SATP) and Path Selection Plug- ins (PSP) offered by VMware 's Native Multi- pathing (NMP) or (3) provide their own SATP and PSP. The plug- ins supported with a storage array are noted in the 'Mode' and 'Path Policy' columns of the 'Model/Release Details' page. The path policy of VMW. If desired, contact the storage array manufacture for recommendation and instruction to set VMW. Please see 'Setup for Failover Clustering and Microsoft Cluster Services' for limitations on MSCS support with PSA. Note that VMware does not currently support unloading of third- party PSA plug- ins on a running ESX/ESXi host. Installation, upgrade or removal of third- party PSA plug- ins may require a reboot of the ESX/ESXi host. This configuration does not allow for multipathing or any type of failover.* Multipathing - The ability of ESX hosts to handle multiple paths to the same storage device.* HBA Failover - In this configuration, the ESX host is equipped with multiple HBAs connecting to one or more SAN switches. The server is robust to HBA and switch failure only.* Storage Port Failover - In this configuration, the ESX host is attached to multiple storage ports and is robust to storage port failures.* Boot from SAN - In this configuration, the ESX host boots from a LUN stored on the SAN rather than a local disk.* Direct Connect - In this configuration, the ESX host is directly connected to the array. There is no switch between HBA and the array and each HBA port must be connect directly to a storage port on the array. Multiple storage ports also known as FC target port on single Fiber Channel- Arbitrated Loop are not supported; therefore, daisy- chaining of storage ports within a storage controller, across storage controller, or across multiple arrays is not supported. Windows Failover Clustering is not supported in this configuration. NOTE: Windows Failover Clustering (MSCS) support applies to Windows 2. SP4, Windows 2. 00. RTM, SP 1, R2 and SP 2. For ESX version requirements for these operating systems in cluster environment, please refer to http: //kb. Windows Failover Clustering is supported only with a limited set of HBAs; please refer to the I/O Compatibility Guide (http: //www. NOTE: MSCS is not supported for Direct Connect. NOTE: Only footnoted storage arrays are supported with Brocade 4. HBAs. NOTE: Unless otherwise footnoted, all fibre channel arrays are supported with both 2. Gb and 4. Gb FC HBAs on ESXNOTE: For ESX 3. U2 onwards unless otherwise footnoted, all fibre channel arrays are supported with 2. Gb, 4. Gb and 8. Gb FC HBAs on ESX. NOTE: For devices with external SAN storage support, please refer to Storage Virtualization Device (SVD). NOTE: Unless otherwise noted, all fibre channel storage products are supported in a boot from SAN configuration. NOTE: End- to- end connectivity at 8. Gbps FC speed is supported with 8. G FC arrays only if the product details has prefix of '8. G FC' or is footnoted. Otherwise support for 8. G FC arrays is limited to up to 4. Gbps speed only. Storage Virtualization Device (SVD)VMware supports Storage Virtualization Devices (SVD) with ESX 3. ESX/ESXi 4. x and ESXi 5. Back- end array and the SVD are both required to be certified with the same ESX release.* Do not share the same LUN of the backend storage array between SVD and any other host.* Only devices that are listed with Array Type SVD are allowed to connect to external Fibre Channel SAN storages. Storage Arrays supported with FCo. E CNAs. VMware supports Fibre Channel (FC) Arrays connected to Fibre Channel Over Ethernet (FCo. E) Converged Network Adapters (CNAs) with ESX 3. U4 and newer releases. It allows the host to connect to the i. SCSI storage device through standard network adapters. The software i. SCSI adapter handles i. SCSI processing while communicating with the network adapter. With the software i. SCSI adapter, you can use i. SCSI technology without purchasing specialized hardware. Hardware i. SCSI Adapter. A hardware i. SCSI adapter is a third- party adapter that offloads i. SCSI and network processing from your host. Hardware i. SCSI adapters are divided into categories. Dependent Hardware i. SCSI Adapter: Depends on VMware networking, and i. SCSI configuration and management interfaces provided by VMware. This type of adapter can be a card that presents a standard network adapter and i. SCSI offload functionality for the same port. The i. SCSI offload functionality depends on the host's network configuration to obtain the IP, MAC, and other parameters used for i. SCSI sessions. An example of a dependent adapter is the i. SCSI licensed Broadcom 5. NIC. Independent Hardware i. SCSI Adapter: Implements its own networking and i. SCSI configuration and management interfaces. An example of an independent hardware i. SCSI adapter is a card that either presents only i. SCSI offload functionality or i. SCSI offload functionality and standard NIC functionality. The i. SCSI offload functionality has independent configuration management that assigns the IP, MAC, and other parameters used for the i. SCSI sessions. An example of a independent adapter is the QLogic QLA4. Hardware i. SCSI adapters might need to be licensed. Otherwise, they will not appear in the v. Sphere Client or v. Sphere CLI. Contact the adapter's vendor for licensing information. Please refer to the I/O Compatibility Guide for a list of hardware i. SCSI adapters and NIC that can be used with ESX. For i. SCSI storage with the Software and Dependent Hardware i. SCSI Adapter, if listed, VMware supports the following configuration, unless footnoted otherwise: * i. SCSI Base Connectivity - The ability of an ESX host to recognize the target and interoperate with it.* SP failover - In this configuration the ESX host is attached to multiple ports and is robust to storage port failover* Boot from i. SCSI - In this configuration, ESX hosts boot from the target i. SCSI array rather than from a local disk. This is only supported on ESXi starting with ESXi 4. NIC to support i. SCSI Boot Firmware Table (i. BFT).* NIC failover for software initiator - If the Ethernet adapters are teamed and one fails, the other one takes over. Both adapters must be connected to the same physical switch and be on the same subnet (both NICs and i. SCSI storage ports).* i. SCSI initiator failover - The ESX host is equipped with multiple software and/or dependent hardware i. SCSI adapters and is robust to i. SCSI adapter failover. This is supported is starting with ESX 4.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
September 2017
Categories |