Storwize V7000实验手册3_存储管理
IBM Flex System V7000 Storage Node 产品指南说明书
IBM Flex System V7000 Storage NodeProduct Guide (withdrawn product)IBM® Flex System™ V7000 Storage Node complements the next generation of integrated systems and is built on the industry-leading storage virtualization and efficiency capabilities of IBM Storwize® V7000 while being physically integrated into IBM PureFlex™ System or IBM Flex System solutions. It plays the pivotal role of storage in IBM PureSystems™ solutions.IBM Flex System V7000 Storage Node is derived from the same base technology as the successful IBM Storwize V7000. It inherits unmatched performance and flexibility through internal virtualization and built-in flash memory optimization technologies. It enables external virtualization, consolidation, and tiering, and improves application availability and resource usage for organizations of all sizes.Figure 1 shows the chassis with the IBM Flex System V7000 Storage Node occupying 4x compute bays. It is partially inserted into the IBM Flex System Enterprise Chassis for identification.Figure 1. Front view of IBM Enterprise Flex System Chassis with IBM Flex System V7000 Storage NodeDid you know?Real-time compression has been used in wide area network (WAN) transmissions ever since IBM developed the Houston Aerospace Spooling Protocol (HASP) for NASA back in 1973. IBM has offered real-time compression on tape cartridges since 1986 with the 3480 IDRC (Improved Data Recording Capability).After nearly 40 years of network usage, highly efficient real-time compression is available for file-based and block-based disk systems with the IBM Storwize family of systems, including IBM Flex System V7000 Storage Node.Figure 2. Role of Flex System V7000 in PureSystemsFigure 3. Flex System V7000 control and expansion enclosuresFigure 4. IBM Flex System V7000 Storage Node in IBM Flex System Enterprise ChassisFor a complete and updated list of IBM Flex System V7000 Storage Node configuration limits and restrictions, see the following link:/support/docview.wss?uid=ssg1S1004369Product specificationsTable 2 is a brief overview of the IBM Flex System V7000 Storage Node specifications.Table 2. Control and expansion enclosure specificationsFigure 5. Control enclosure with connection ports and indicatorsTable 3 shows the physical dimensions of the control and expansion enclosures and their weight when they are fully populated with disks.Table 3. Physical dimensions and weight of enclosuresEnclosure Height mm (in.)Width mm (in.)Depth Max weight24 drive-slot controlenclosures 4939-X49110 (4.4)432 (17)505 (19.9)27.1 kg (61 lb)24 drive-slot expansionenclosures 4939-X29110 (4.4)432 (17)505 (19.9)25.1 kg (55.4 lb)Table 4 shows the different environmental requirements.Table 4. Temperature requirementsEnvironment Ambienttemperature Altitude Relative humidity Maximum wet bulbtemperature200 W operating5°C to 40°C(41°F to 104°F)0 to 2133 m(0 to 7000 ft)8% to 80% non-condensing23°C (73°F)5°C to 35°C (41°F to 95°F)2134 to 3048 m (7001 to 10000 ft)400 W operating5°C to 35°C(41°F to 95°F)0 to 2133 m(0 to 7000 ft)8% to 80% non-condensing23°C (73°F)5°C to 30°C (41°F to 86°F)2134 to 3048 m (7001 to 10000 ft)Non-operating1°C to 50°C(34°F to 122°F)-305 to 12192m(-1000 to 40000 ft)8% to 80% non-condensing29°C (84°F)Storage1°C to 60°C(34°F to 140°F)5% to 80% non-condensingShipping-40°C to 60°C(-40°F to 140°F)5% to 100% condensing, but not precipitatingOptions and feature codesBoth the control and expansion enclosures connect to the Flex System Enterprise chassis through the midplane interconnect, which provides power and internal control connections. The expansion enclosure uses the Serial Attached SCSI (SAS2) 6 Gbps chain connection on the front of the control and expansion canisters, as shown in Figure 3.The IBM Flex System V7000 Storage Node uses new smaller SAS2 cable connectors. These connectors are based on the high density (HD) mini SAS connectors.There is an adapter on the external IBM Storwize V7000 expansion that changes the HD mini SAS to the mini SAS connection. Figure 6 shows the cabling scheme and the differences in the cable connections of the two expansions.Figure 6. Node cabling - internal SAS and externalFor the connections between the IBM Flex System V7000 Control Enclosure and the IBM Flex System V7000 Expansion Enclosure in the chassis, the short cables that are shown in Figure 6 are used and can be ordered. The expansion enclosure cables that are shown in Table 5 are offered with the Flex System V7000.Table 5. Expansion enclosure cablesFeature Part number DescriptionADA100Y4600 A 0.328 meter SAS cable that is used for the attachment of Flex SystemV7000 expansion enclosures.ADA690Y7682 A 6 meter SAS cable that is used for the attachment of Storwize V7000expansion enclosures.Supported disk drivesFigure 7. Logical layout of Storage Node to I/O module switch interconnectsFigure 8. Example of FC connectivity using FC canister adapters and I/O module switchesPowerTable 8 shows the operating environment for power consumption and heat dissipation.Table 8. Flex System V7000 power consumption and heat dissipationEnclosure Watts (AC)Btu per hour3761283Flex System V7000controller node188641Flex System V7000expansion nodePower connectivity and supply are managed through the IBM Flex System Enterprise Chassis. For more information, consult the Power Configurator for exact configuration support for the IBM Flex System V7000 Storage Node on the IBM Flex System Enterprise Chassis. See the following link:/systems/bladecenter/resources/powerconfig.htmlOther feature highlights/support/customercare/sas/f/comprestimator/home.htmlThere are compression performance enhancements that are included in IBM Flex System V7000 Storage Node V7.1.x or later, which result in improvements on performance and cache destage latency usage. The most notable improvement is when the compression software detects a block that is unlikely to achieve reasonable compression ratio, and writes the block to the back-end storage without compressing it to avoid unnecessary processing impact.External Storage VirtualizationWith this feature, an external storage subsystem can be attached through Fibre Channel or FCoE to the IBM Flex System V7000 Storage Node (these devices cannot be presented through an iSCSI connection). The devices that are presented are treated as Mdisks and can be mapped to storage pools for volume creation and management. After the storage from the external system is integrated into the IBM Flex System V7000 Storage Node and added to a storage pool, it is available to be virtualized and used by any of the features and functions of the IBM Flex System V7000 Storage Node.Note: External Storage Virtualization is supported only on FC and FCoE but not iSCSI.Host attachment interoperabilitymust license IBM Flex System V7000 Storage Node External Virtualization Software. You must license the number of storage enclosures that are attached externally to the IBM Flex System V7000 Storage Node. IBM Flex System V7000 Control Enclosures and IBM Flex System V7000 Expansion Enclosures, which are clustered, do not need to be included in this External Virtualization license. However, any IBM Flex SystemV7000 Control Enclosures or Expansion Enclosures that are SAN-attached and virtualized are included in this license.A storage enclosure that is externally managed by IBM Flex System V7000 Storage Node is defined as an independently powered, channel-attached device that stores data on magnetic disks or SSDs, such as disk controllers and their respective expansion units, each constituting separate enclosures. Therefore, an enclosure can be either the main controller that houses disk (or SSD) drives or the expansion chassis that houses additional heard disk drives (or SSDs) to expand the total capacity of the storage system. If there is any confusion for an external storage enclosure that does not conform to this definition, consult your IBM sales representative for an equivalent measure that is based on a disk drive count.For example, if you add a DS5020 consisting of three enclosures to IBM Flex System V7000 Storage Node consisting of one control enclosure and one expansion enclosure, then you need one license with three enclosure authorization feature codes (one for each of the DS5020 enclosures) of the IBM Flex System V7000 External Virtualization software.Remote Copy (Advanced Copy Services: Metro Mirror / Global Mirror)To authorize the usage of Remote Copy capabilities of IBM Flex System V7000 Storage Node where the primary and secondary systems have the same number of enclosures at each site, you must purchase a license for IBM Flex System V7000 Remote Mirroring Software with a quantity of licenses that matches the number of licensed enclosures that are managed by IBM Flex System V7000 Storage Node, including each internal enclosure that is licensed with the IBM Flex System V7000 Base Software, each attached Storwize V7000 expansion enclosure with the Storwize V7000 Base Software, and each external enclosure that is licensed with the IBM Flex System V7000 External Virtualization Software.For example, suppose that your primary system has a DS5020 consisting of three enclosures that are managed by an IBM Flex System V7000 Storage Node consisting of one control enclosure and one expansion enclosure, and you have the same number of enclosures at the secondary system. Then, to authorize remote mirroring for the primary system, you must license the IBM Flex System V7000 Remote Mirroring Software for five enclosures. Assuming that the matching secondary system is also an IBM Flex System V7000 Storage Node, you need five additional enclosure licenses for the secondary system, for a total of 10 enclosure licenses.For primary and secondary systems with a different number of enclosures that are using Remote Mirroring, the number of licenses that are needed for each system is the number of enclosures on the smaller of the two systems (see scenarios 1 and 2 below).When multiple production systems replicate to a single disaster recovery system, the number of licenses at the disaster recover system must equal the sum of the licenses at the production systems (see scenario 3 below). Here are examples about how to license Remote Mirroring software under these licensing rules:Scenario 1: The primary system is a three-enclosure IBM Flex System V7000 Storage Node with nothing externally virtualized, so it has three base enclosure licenses (IBM Storwize Family Software for Flex SystemV7000). The secondary system is a two-enclosure IBM Flex System V7000 Storage Node with nothing externally virtualized, so it has two base enclosure licenses (IBM Storwize Family Software for Flex System V7000). The Flex System V7000 Remote Mirroring licensing is two licenses for the primary system plus two licenses for the secondary system, for a total of four licenses.Scenario 2: The primary system is a one-enclosure IBM Flex System V7000 Storage Node managing a DS5020 that consists of three enclosures, so it has one base system license (IBM Storwize Family Software for Flex System V7000) plus three licenses for IBM Flex System V7000 External Virtualization Software. The secondary system is a three-enclosure Flex System V7000 with nothing externally virtualized, so it has three base system licenses (IBM Storwize Family Software for Flex System V7000). The Flex System V7000 Remote Mirroring licensing is three licenses for the primary system plus three licenses for the secondary system, for a total of sixLicense requirements for migrationWith External Virtualization, the IBM Flex System V7000 Storage Node allows customers to bring a system in to their storage environment and quickly and easily migrate data from existing storage systems to IBM Flex System V7000 Storage Node.To facilitate this migration, IBM allows customers 45 days from the date of purchase of the IBM Flex SystemV7000 Storage Node to use the External Virtualization function to migrate data from an existing storage system to IBM Flex System V7000 Storage Node. Any usage thereafter, and ongoing usage of the external virtualization function of IBM Flex System V7000 Storage Node, requires the purchase of a Flex System V7000 External Virtualization license at a quantity equal to the capacity that is managed under the IBM Flex System V7000 Storage Node.Migrations that are performed at later points in time that replace other storage systems with IBM Flex SystemV7000 Storage Node, and thus requiring temporary virtualization of that external storage system to perform that replacement activity, are granted a 45-day period for usage of External Virtualization without having to purchase a license to complete such a migration effort.You must make your IBM sales representative aware of your intention and when you will start this migration so that an end date can be tracked. It is your responsibility to ensure that your systems are properly licensed for all external storage that is managed by IBM Flex System V7000 Storage Node after those 45 days.All license feature codes are listed in Table 11.TrademarksLenovo and the Lenovo logo are trademarks or registered trademarks of Lenovo in the United States, other countries, or both. A current list of Lenovo trademarks is available on the Web athttps:///us/en/legal/copytrade/.The following terms are trademarks of Lenovo in the United States, other countries, or both:Lenovo®Flex SystemServerProven®The following terms are trademarks of other companies:Intel® is a trademark of Intel Corporation or its subsidiaries.Linux® is the trademark of Linus Torvalds in the U.S. and other countries.Microsoft®, Windows Server®, and Windows® are trademarks of Microsoft Corporation in the United States, other countries, or both.Other company, product, or service names may be trademarks or service marks of others.。
IBM Storwize V7000 信息中心勘误表说明书
IBM System Storage SAN Volume ControllerIBM Storwize V7000Information Center ErrataVersion 6.3.0April 27, 20121Contents Introduction (4)Who should use this guide (4)Last Update (4)Change History (4)iSCSI Limits (5)iSCSI Limits with Multiple I/O Groups (5)Definition of terms (5)Limits that take effect when using iSCSI (6)Single I/O Group Configurations (6)iSCSI host connectivity only (6)Mixed iSCSI and Fibre Channel host connectivity (6)Multiple I/O Group Config (7)Symptoms of exceeding the limits (7)Configuring the HP 3PAR F-Class and T-Class Storage Systems (8)Minimum Supported STORWIZE V7000 Version (8)Configuring the HP 3PAR Storage System (8)Supported models of HP 3PAR Storage Systems (8)Support firmware levels of HP 3PAR storage arrays (8)Concurrent maintenance on HP 3PAR storage arrays (8)HP 3PAR user interfaces (8)HP 3PAR Management Console (9)HP 3PAR Command Line Interface (CLI) (9)Logical units and target ports on HP 3PAR storage arrays (9)LUNs (9)LUN IDs (9)LUN creation and deletion (10)LUN Presentation (10)Special LUNs (10)LU access model (11)LU grouping (11)LU preferred access port (11)Detecting Ownership (11)Switch zoning limitations for HP 3PAR storage arrays (11)Fabric zoning (11)Target port sharing (11)Controller splitting (12)Configuration settings for HP 3PAR storage array (12)Logical unit options and settings for HP 3PAR storage array (12)Creation of CPG (12)Set up of Ports (13)Setup of Host (14)LUN creation (15)Host options and settings for HP 3PAR storage array (16)2Quorum disks on HP 3PAR storage arrays (16)Clearing SCSI reservations and registrations (17)Copy functions for HP 3PAR storage array (17)Thin Provisioning for HP 3PAR storage array (17)Recommended Settings for Linux Hosts (18)Multipath settings for specific Linux distributions and Releases (19)Udev Rules SCSI Command Timeout Changes (21)Editing the udev rules file (22)3IntroductionThis guide provides errata information that pertains to release 6.3.0 of the IBM System Storage SAN Volume Controller Information Center and the IBM Storwize V7000 Information Center.Who should use this guideThis errata should be used by anyone using iSCSI as a method to connect hosts, Connecting Linux hosts using Fibre Channel or when connecting HP 3PAR Storage to IBM System Storage SAN Volume Controller or IBM Storwize V7000 .Last UpdateThis document was last updated: April 27, 2012.Change HistoryThe following revisions have been made to this document:Revision Date Sections ModifiedNov 18, 2011 New publicationApr 27 2012 Linux Host SettingsTable 1: Change History4iSCSI LimitsiSCSI Limits with Multiple I/O GroupsThe information is in addition to, and a simplification of, the information provided in the Session Limits pages at the following links:/infocenter/StorwizeV7000/ic/index.jsp?topic=/com.ibm.storage.Storwize V7000.console.doc/StorwizeV7000_iscsisessionlimits.html/infocenter/storwize/ic/topic/com.ibm.storwize.v7000.doc/S torwize V7000_iscsisessionlimits.htmlDefinition of termsFor the purposes of this document the following definitions are used:IQN:an iSCSI qualified name – each iSCSI target or initiator has an IQN. The IQN should be unique within the network. Recommended values are of the formiqn.<date>.<reverse domain name>:<hostname>.<unique id> e.g. iqn.03-.ibm.hursley:host1.1initiator: an IQN that is used by a host to connect to an iSCSI targettarget: an IQN on an STORWIZE V7000 or V7000 node that is the target for an iSCSI logintarget portal: an IP address that can be used to access a target IQN. This can be either an IPv4 or an IPv6 address.5Limits that take effect when using iSCSISingle I/O Group ConfigurationsiSCSI host connectivity only1 target IQN per node2 iSCSI target portals (1xIPv4 and 1xIPv6) per network interface on a node4 sessions per initiator for each target IQN256 defined iSCSI host object IQNs512 host iSCSI sessions per I/O group **256 host iSCSI sessions per node (this is to allow the hosts to reconnect in the event of a failover)** e.g. if a single initiator logs in 3 times to a single target count this as 3. If a singleinitiator logs in to 2 targets via 3 target portals each count this as 6.Only the 256 defined iSCSI IQN limit is enforced by the GUI or CLI commands. Mixed iSCSI and Fibre Channel host connectivity512 total sessions per I/O group where:1 defined FC host object port (WWPN) = 1 session1 defined iSCSI host object IQN = 1 session1 additional iSCSI session to a target = 1 sessionIf the total number of defined FC ports & iSCSI sessions in an I/O group exceeds 512, some of the hosts may not be able to reconnect to the STORWIZE V7000/V7000 targets in the event of a node IP failover. See above section for help on calculating the number of iSCSI sessions.6Multiple I/O Group ConfigIf a host object is defined in more than one I/O group then each of its host object port definitions is counted against the session limits for every I/O group it is a member of. This is true for both FC and iSCSI host objects. By default a host object created using the graphical user interface is created in all available I/O groups.Symptoms of exceeding the limits.The following list is not comprehensive. It is given to illustrate some of the common symptoms seen if the limits defined above are exceeded.. These symptoms could also indicate other types of problem with the iSCSI network.•The host reports a time out during the iSCSI login process•The host reports a time out when reconnecting to the target after a STORWIZE V7000/V7000 node IP failover has occurred.In both of the above cases no errors will be logged by the STORWIZE V7000/V7000 system.7Configuring the HP 3PAR F-Class and T-Class Storage SystemsMinimum Supported STORWIZE V7000 Version6.2.0.4Configuring the HP 3PAR Storage SystemThis portion of the document covers the necessary configuration for using an HP 3PAR Storage System with an IBM Storwize V7000 cluster.Supported models of HP 3PAR Storage SystemsThe HP 3PAR F-Class (Models 200 and 400) the HP 3PAR T-Class (Models 400 and 800) are supported for use with the IBM STORWIZE V7000. These systems will be referred to as HP 3PAR storage arrays. For the latest supported models please visit /support/docview.wss?uid=ssg1S1003907Support firmware levels of HP 3PAR storage arraysFirmware revision HP InForm Operating System 2.3.1 (MU4 or later maintenance level) is the supported level of firmware for use with IBM STORWIZE V7000. For support on later versions, consult /support/docview.wss?uid=ssg1S1003907 Concurrent maintenance on HP 3PAR storage arraysConcurrent Firmware upgrades (“online upgrades”) are supported as per HP procedures. HP 3PAR user interfacesUsers may configure an HP 3PAR storage array with the 3PAR Management Console or HP 3PAR Command Line Interface (CLI).8HP 3PAR Management ConsoleThe management console accesses the array via the IP address of the HP 3PAR storage array. All configuration and monitoring steps are intuitively available through this interface.HP 3PAR Command Line Interface (CLI)The CLI may be installed locally on a Windows or Linux host. The CLI is also available through SSH.Logical units and target ports on HP 3PAR storage arraysFor clarification, partitions in the HP 3PAR storage array are exported as Virtual Volumes with a Virtual Logical Unit Number (VLUN) either manually or automatically assigned to the partition.LUNsHP 3PAR storage arrays have highly developed thin provisioning capabilities. The HP 3PAR storage array has a maximum Virtual Volume size of 16TB. A partition Virtual Volume is referenced by the ID of the VLUN.HP 3PAR storage arrays can export up to 4096 LUNs to the STORWIZE V7000 Controller (STORWIZE V7000’s maximum limit). The largest Logical Unit size supported by STORWIZE V7000 under PTF 6.2.0.4 is 2TB, STORWIZE V7000 will not display or exceeded this capacity.LUN IDsHP 3PAR storage arrays will identify exported Logical Units throughSCSI Identification Descriptor type 3.The 64-bit IEEE Registered Identifier (NAA=5) for the Logical Unit is in the form;5-OUI-VSID .The 3PAR IEEE Company ID of 0020ACh, the rest is a vendor specific ID.9Example 50002AC000020C3A.LUN creation and deletionVirtual Volumes (VVs) and their corresponding Logical Units (VLUNs) are created, modified, or deleted through the provisioning option in the Management Console or through the CLI commands. VVs are formatted to all zeros upon creation.To create a VLUN, highlight the Provisioning Menu and select the Create Virtual Volume option. To modify, resize, or destroy a VLUN, select the appropriate Virtual Volume from the window, right click when the specific VLUN is highlighted.*** Note: Delete the mdisk on the STORWIZE V7000 Cluster before deleting the LUN on the HP 3PAR storage array.LUN PresentationVLUNs are exported through the HP 3PAR storage array’s available FC ports by the export options on Virtual Volumes. The Ports are designated at setup and configured separately as either Host or Target (Storage connection). Ports being identified by a node : slot : port representation.There are no constraints on which ports or hosts a logical unit may be addressable.To apply Export to a logical unit, highlight the specific Virtual Volume associated with the Logical Unit in the GUI and right click and select Export.Special LUNsThere are no special considerations to a Logical Unit numbering. LUN 0 may be exported where necessary.Target PortsA HP 3PAR storage array may contain dual and/or quad ported FC cards. Each WWPN is identified with the pattern 2N:SP:00:20:AC:MM:MM:MM where N is the node, S is the slot and P is the port number on the controller and N is the controller’s address. The MMMMMM represents the systems serial number.Port 2 in slot 1 of controller 0 would have the WWPN of 20:12:00:02:AC:00:0C:3A The last 4 digits of serial number 1303130 in hex (3130=0x0C3A).This system has a WWNN for all ports of 2F:F7:00:02:AC:00:0C:3A.10LU access modelAll controllers are Active/Active. In all conditions, it is recommended to multipath across FC controller cards to avoid an outage from controller failure. All HP 3PAR controllers are equal in priority so there is no benefit to using an exclusive set for a specific LU.LU groupingLU grouping does not apply to HP 3PAR storage arrays.LU preferred access portThere are no preferred access ports on the HP 3PAR storage arrays as all ports are Active/Active across all controllers.Detecting OwnershipDetecting Ownership does not apply to HP 3PAR storage arrays.Switch zoning limitations for HP 3PAR storage arraysThere are no zoning limitations for HP 3PAR storage arrays.Fabric zoningWhen zoning an HP 3PAR storage array to the STORWIZE V7000 backend ports, be sure there are multiple zones or multiple HP 3PAR storage array and STORWIZE V7000 ports per zone to enable multipathing.Target port sharingThe HP 3PAR storage array may support LUN masking to enable multiple servers to access separate LUNs through a common controller port. There are no issues with mixing workloads or server types in this setup.Host splitting11There are no issues with host splitting on an HP 3PAR storage array.Controller splittingHP 3PAR storage array LUNs that are mapped to the Storwize V7000 cluster cannot be mapped to other hosts. LUNs that are not presented to STORWIZE V7000 may be mapped to other hosts.Configuration settings for HP 3PAR storage arrayThe management console enables the intuitive setup of the HP 3PAR storage array LUNs and export to the Storwize V7000 cluster.Logical unit options and settings for HP 3PAR storage array From the HP 3PAR storage array Management Console the following dialog of options are involved in setting up of Logical Units.Creation of CPGThe set up of Common Provisioning Groups (CPGs). If Tiering is to be utilised, it should be noted it is not good practice to mix different performance LUNs in the same STORWIZE V7000 mdiskgrp.Action->Provisioning->Create CPG (Common Actions)12Set up of PortsShown is on a completed 8 node STORWIZE V7000 cluster.Each designated Host ports should be set to Mode; point.Connection Mode: HostConnection Type: PointSystem->Configure FC Port (Common Actions)13Setup of HostHost Persona should be: 6 – Generic Legacy.All STORWIZE V7000 ports need to be included. Actions->Hosts->Create Host (Common Actions)14LUN creationSize limitations: 256 MiB minimum2TB maximum (STORWIZE V7000 limit)Provisioning: Fully Provision from CPGThinly ProvisionedCPG: Choose provisioning group for new LUN, usually R1,R5,R6 or drive specific. Allocation Warning: Level at which warning is given, optional [%]Allocation Limit: Level at which TP allocation is stopped, optional [%] Grouping: For creating multiple sequential LUNs in a set [integer values, 1-999] Actions->Provisioning->Create Virtual Volumes (Common Actions)15Exporting LUNs to STORWIZE V7000Host selection: choose host definition created for STORWIZE V7000Actions->Provisioning->Virtual Volumes->Unexported (Select VV and right click)Host options and settings for HP 3PAR storage arrayThe host options required to present the HP 3PAR storage array to Storwize V7000 clusters is, “6 legacy controller”.Quorum disks on HP 3PAR storage arraysThe Storwize V7000 cluster selects disks that are presented by the HP 3PAR storage array as quorum disks. To maintain availability with the cluster, ideally each quorum disk should reside on a separate disk subsystem.16Clearing SCSI reservations and registrationsYou must not use the HP 3PAR storage array to clear SCSI reservations and registrations on volumes that are managed by Storwize V7000. The option is not available on the GUI.Note; the following CLI command should only be used under qualified supervision,“setvv –clrsv”.Copy functions for HP 3PAR storage arrayThe HP 3PARs copy/replicate/snapshot features are not supported under STORWIZEV7000.Thin Provisioning for HP 3PAR storage arrayThe HP 3PAR storage array provides extensive thin provisioning features. The use of these thin provisioned LUNs is supported by STORWIZE V7000.The user should take notice of any warning limits from the Array system, to maintain the integrity of the STORWIZE V7000 mdisks and mdiskgrps. An mdisk will go offline and take its mdiskgroup offline if the ultimate limits are exceeded. Restoration will involve provisioning the 3PAR Array LUN, then including the mdisk and restoring any slandered paths.17Recommended Settings for Linux HostsThe following details the recommended multipath ( DMMP ) settings and udev rules for the attachment of Linux hosts to SAN Volume Controller and Storwize V7000. The settings are recommended to ensure path recovery in failover scenarios and are valid for x-series, all Intel/AMD based servers and Power platforms.A host reboot is required after completing the following two stepsEditing the multipath settings in etc/multipath.confEditing the udev rules for SCSI command timeoutFor each Linux distribution and releases within a distribution please reference the default settings under [/usr/share/doc/device-mapper-multipath.*] for Red Hat and[/usr/share/doc/packages/multipath-tools] for Novell SuSE. Ensure that the entries added to multipath.conf match the format and syntax for the required Linux distribution. Only use the multipath.conf from your related distribution and release. Do not copy the multipath.conf file from one distribution or release to another.Note for some OS levels the "polling_interval" needs to be located under defaults instead of under device settings.If "polling_interval" is present in the device section, comment out "polling_interval" using a # keyExamplesUnder Device Section# polling_interval 30,Under Defaults Sectiondefaults {user_friendly_names yespolling_interval 30}18Multipath settings for specific Linux distributions and ReleasesEdit /etc/multipath.conf with the following parameters and confirm the changes using “multipathd -k"show config".RHEL61device {vendor "IBM"product "2145"path_grouping_policy group_by_priogetuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"features "1 queue_if_no_path"prio aluapath_checker turfailback immediateno_path_retry "5"rr_min_io 1# polling_interval 30dev_loss_tmo 120}RHEL56device {vendor "IBM"product "2145"path_grouping_policy group_by_prioprio_callout "/sbin/mpath_prio_alua /dev/%n"path_checker turfailback immediateno_path_retry 5rr_min_io 1# polling_interval 30dev_loss_tmo 120}19RHEL57device {vendor "IBM"product "2145"path_grouping_policy group_by_prioprio_callout "/sbin/mpath_prio_alua /dev/%n" path_checker turfailback immediateno_path_retry 5rr_min_io 1dev_loss_tmo 120}SLES10SP4device {vendor "IBM"product "2145"path_grouping_policy "group_by_prio"features "1 queue_if_no_path"path_checker "tur"prio "alua"failback "immediate"no_path_retry "5"rr_min_io "1"# polling_interval 30dev_loss_tmo 120}SLES11SP1device {vendor "IBM"product "2145"path_grouping_policy group_by_prioprio aluafeatures "0"no_path_retry 5path_checker turrr_min_io 1failback immediate# polling_interval 30dev_loss_tmo 12020}SLES11SP2device {vendor "IBM"product "2145"path_grouping_policy "group_by_prio"prio "alua"path_checker "tur"failback "immediate"no_path_retry "5"rr_min_io 1dev_loss_tmo 120}Udev Rules SCSI Command Timeout ChangesSet the udev rules for SCSI command timeoutSet SCSI command timeout to 120sOS Level Default Required SettingRHEL61 30 120RHEL62 30 120RHEL56 60 120RHEL57 60 120SLES10SP4 60 120SLES11SP1 60 120SLES11SP2 30 12021Creating a udev rules fileCreate the following udev rule that increases the SCSI command timeout for SVC and V7000 block devicesudev rules filecat /etc/udev/rules.d/99-ibm-2145.rules# Set SCSI command timeout to 120s (default == 30 or 60) for IBM 2145 devices SUBSYSTEM=="block", ACTION=="add", ENV{ID_VENDOR}=="IBM",ENV{ID_MODEL}=="2145", RUN+="/bin/sh -c 'echo 120 >/sys/block/%k/device/timeout'"Reconfirm the settings following the system reboot.22。
Linux系统下管理V7000存储的盘.docx
Linux系统下管理V7000存储的盘Linux系统用device-mapper multipathing driver管理V7000存储的盘1、查看主机上光纤卡的WWN[root@test1 host2]# pwd/sys/class/fc_host/host2[root@test1 host2]# cat port_name0x5001438006342f802、在V7000存储上进行mapping在存储上查看是否能看到该HBA卡的WWN，mapping后可重新扫描设备[root@oawas2 host2]# cd /sys/class/scsi_host/host2[root@oawas2 host2]# echo "- - -" >./scan可以看到认到盘了fdisk -l3、V7000使用Linux device-mapper multipathing driver作为多路径软件启用步骤：step1. service multipathd stopstep2.修改/etc/multipah.conf备份该文件cp /etc/multipath.conf /etc/bak.multipath.confblacklist {# 黑名单，就是禁止哪些设备使用multipathing driver# 默认情况下所以的设备都在multipath的黑名单中，所以即使启动了multip athd服务并加在了内核模块，multipath也不会对链路进行聚合，必须进行修改# 可以按照wwid逐一加入，也可以使用devnode的方式按照规律批量加入wwid 1HITACHI_D60055750023wwid 1HITACHI_D60055750028devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"devnode "^hd[a-z]"}defaults {# 默认情况下multipath生成dm设备之后，会同时在/dev/mapper/下生成以磁盘wwid为名的符号链接指向对应的dm设备。
HP_3PAR_StoreServ_7000_管理维护手册
保修时候确定以下信息
NOTE:
• Node IP : 192.168.XX.XX /3paradm/3pardata (默认，参考安装密码) • SP &VSP IP : 192.168.XX.XX /3parcust/3parInServ(默认) • 3par p7000 sn: SGHXXXXXX/xXXXXXXX • HP24 小时服务热线: 800-810-3860 / 400-810-3860
(2 nodes, 4 FC ports, 24 SFF slots)
4-port 8Gb/s FC HBA
HP M6710 2.5in 2U SAS
SFF SAS HDDs/SSDs HP G3 Rack Physical SP (Optional)
HP 3PAR StoreServ 7400
(2-node, 4 FC ports, 24 SFF slots)
1
2 0
3 1
4
2 2
1 0
0
1
1
Console port 2x cluster expansion ports 2x 6 Gb SAS 4-wide for optional 4-way configuration expansion ports 2x 8 Gb Fibre Channel host ports
• An Alert will be reported
HP AR StoreServ 7000 管理
© 2009 HP Confidential
管理工具介绍
• • • • • • IMC连接到3par CLI连接到3par 管理界面 System 查看存储信息 Performance&Reports查看 Event&Alerts
IBM_V7000配置实施文档(图文并茂)
2011/5/5
一、 设备
序号
1 2 3
设备名称
IBM Power 720 IBM Storwize V7000 IBM B24
数量
2 1 1
访问 IP
用户名/密码
二、IBM Storwize V7000 相关术语
1) Mdisk（被管理的磁盘） ：Storwize V7000 管理到的磁盘单元 2) StoragePool(池):由一个或多个 Mdisk 组成存储空间 3) Volumes(卷)：由存储池中创建的存储空间，提供给主机使用（lun）
2 / 33
4) 设置完成后，按下图的提示进行操作
5) 在浏览器中输入管理 IP 地址，如：https://172.16.0.235，输入用户名、密 码，用户名和密码在 USB Key 中有提示：superuser、passw0rd(‘0’为零)：
3 / 33
6) 按提示接受许可协议，并且进行其他的配置操作,以下配置中有些内容可 以自己研究下：
将该卷再映射到第二台主机 chustar2，2 台主机共享一个 lun：
19 / 33
配置完成后：
20 / 33
四、其他功能
拷贝服务： FlashCopy 一致性组 FlashCopy 映射 远程拷贝 伙伴关系
21 / 33
用户管理 用户 审计日志
配置 网络 时间通知 高级
22 / 33
选择某个 mdisk，可针对该 mdisk 进行相关“删除”等操作：
12 / 33
点击“物理存储器池新建池“，选择对应的 Mdisk，创建新池：
选择” 卷所有卷/按池划分的卷/按主机划分的卷新建卷”，创建新的卷：
V7000存储相关配置
完成此安装之后，需要设置一个 SDD 路径选择策略算法，该算法可以帮助您提高多路径配置的和受支持的存储设备的性能，并且可以让路径故障对应用程序透明。
以下路径选择策略受到支持：∙仅故障转移 (fo)由于 I/O 错误，在路径发生故障之前，应将所有 I/O 操作发送至相同（首选）路径。
然后为后续的 I/O 操作选择一个备用路径。
∙负载平衡 (lb)通过评估适配器上每个路径连接的负载来选择用于 I/O 操作的路径。
负载是同时进行的 I/O 操作数量的函数。
如果多个路径具有相同的负载，则会从这些路径中随机选择一条路径。
负载平衡模式还会并入故障转移保护。
负载平衡策略也称为优化策略。
∙负载平衡顺序 (lbs)该策略与用于顺序 I/O 优化的负载平衡策略相同。
此负载平衡顺序策略也称为优化顺序策略。
这是默认设置。
∙轮循 (rr)从没有用于最后一个 I/O 操作的路径中随机选择用于每个 I/O 操作的路径。
如果设备只有两个路径，那么 SDD 会交替使用这两个路径。
∙轮循顺序 (rrs)该策略与针对顺序 I/O 进行优化的轮循 (round-robin) 策略相同。
您需要为您的环境选择最适当的 SDD 路径选择策略，并使用以下方法应用该策略。
注意：在更改算法之前，您需要将磁盘保留策略更改为 no_reserve。
# chdev -l hdiskX -a reserve_policy=no_reserve用于设置不同的 SDD 路径选择策略算法的命令的示例# chdev -l hdiskX -a algorithm=load_balance_port# chdev -l hdiskX -a algorithm=round_robin您可以使用 pcmpath query device 命令查看磁盘策略。
图 2. 轮循算法您也可以使用 nmon 工具查看 FCS 适配器使用情况。
该工具可帮助您了解正在使用哪些 FCS 适配器。
IBMStorwizeV7000全资料解析
IBMStorwizeV7000全资料解析IBM Storwize V7000最全资料解析存储效率五项技术集于一身，IBM Storwize V7000中端存储新品解析最近IBM 新一代中端虚拟存储产品Storwize V7000在业内反响挺大，Storwize V7000是一款被IBM寄予厚望的产品，在发布这款新品之前，IBM特意为其制作了具有强烈神秘感的广告，并宣称这将是“改变存储游戏规则”的产品，确实，作为IBM全新的中端磁盘存储系统，围绕在Storwize V7000身上的谜题确实是太多了。
因此我特意整理了一些资料分享给大家，打造史上最全的V7000汇总贴。
IBM Storwize V7000有三个第一，1.第一个IBM自主研发的中端存储2.0产品，架构上突破传统，吸收了DS和IBM 横向扩展架构XIV 的精华；2.第一次集“EasyTier自动分层”“虚拟化”“精简调配”三大存储效率于一身的磁盘列阵，使IBM Storwize V7000当之无愧的成为更加看重存储效率的中端存储市场上的杀手级产品；3. 第一次把DS8000的RAID技术和自动分层，SVC虚拟化架构以及XIV的赏心悦目的管理界面等高端存储上的技术用在中端存储上，拥有企业级阵列的功能和使人眼前一亮的GUIIBM Storwize V7000技术参数IBM Storwize V7000目前是一个双控制器存储阵列（将来计划括充至8个控制器，与IBM SVC类似），每个控制器都利用了一个四核Jasper Forest（Nehalem）处理器来驱动虚拟化的三级后端存储，采用了SAS连接。
该系统采用了SVC（SANVolume Controller）代码堆栈，以及储存资源随需分配、虚拟化和数据保护等功能。
并添加了IBM 高端存储XIV的用户图形界面以及DS8000 RAID以及EasyTier功能。
可以说是集大成于一身。
V7000的主机接口是8Gbit/s的Fibre Channel，可选加四个1Gbit/E的iSCSI，iSCSI为原生支持。
IBM V7000配置实施文档
IBM Storwize V7000 配置实施文档
2011/5/5
一、设备
二、IBM Storwize V7000相关术语
1)Mdisk（被管理的磁盘）：Storwize V7000管理到的磁盘单元
2)StoragePool(池):由一个或多个Mdisk组成存储空间
3)Volumes(卷)：由存储池中创建的存储空间，提供给主机使用（lun）
三、实施步骤
1)安装上架、连线、加电正常
2)V7000的配置中有一个USB Key，该Key是用来管理V7000存储所需的，
将USB Key插入工程师的PC笔记本上，对其设置管理IP，设置完成后，
会在该Key中生存一个配置文件，再将该Key拔出，插入V7000控制器
上对应的管理以太网口上面的USB口，待V7000配置稳定后，即可通过
设置的IP地址对存储进行管理；
3)打开.exe执行程序，按提示进行IP的设置
4)设置完成后，按下图的提示进行操作
码，用户名和密码在USB Key中有提示：superuser、passw0rd(‘0’为零)：
以自己研究下：。
V7000存储高可用解决方案
V7000存储高可用解决方案(XXX容灾方案建议)容灾参考方案目录第1章 XXXX容灾方案参考 ..................................................................... .. (1)1.1 系统现状 ..................................................................... .. (1)1.2 容灾需求分析 ..................................................................... (1)1.3 容灾参考方案 ..................................................................... (2)1.3.1 总体架构规划 ..................................................................... ............................................... 2 1.3.2 V7000 外部存储虚拟化功能说明...................................................................... ............... 3 1.3.3 V7000 VDM(虚拟磁盘镜像)功能说明 ......................................................................31.3.4 后期存储扩展建议 ..................................................................... ....................................... 4 1.4 系统配置参考 ..................................................................... (4)第2章 V7000存储设备介绍 ..................................................................... .. (6)2.1 IBM V7000存储系统概述 ..................................................................... ..................................... 6 2.2 通过IBM SYSTEM STORAGE EASY TIER增强访问能力 (6)2.3 通过精简调配来优化效率...................................................................... ..................................... 7 2.4 动态迁移避免系统中断运行...................................................................... ................................. 7 2.5 通过复制服务来保护数据...................................................................... ..................................... 8 2.6 管理工具与IBM SYSTEMS DIRECTOR相集成 ..................................................................... .. (10)2.7 高性能SSD支持 ..................................................................... .................................................. 10 2.8 外部存储系统虚拟化 ..................................................................... . (10)第3章存储高可用技术建议 ..................................................................... (12)3.1 存储高可用性的内容 ..................................................................... ........................................... 12 3.2 存储高可用性方案的主要实现方式 ..................................................................... .................... 14 3.2.1 方式一:磁盘设备间数据镜像( 如LVMMirror ) (15)3.2.2 方式二:磁盘设备间数据复制(如PPRC或ERM) (19)3.2.3 方式三:采用SVC或V7000或V7000实现逻辑卷镜像 (21)3.2.4 三种HA方式的比较 ..................................................................... . (23)目录容灾参考方案第1章 XXXX容灾方案参考1.1 系统现状XXXX现有IT系统的现状大致如下图所示。
V7000存储相关配置
完成此安装之后，需要设置一个 SDD 路径选择策略算法，该算法可以帮助您提高多路径配置的和受支持的存储设备的性能，并且可以让路径故障对应用程序透明。
以下路径选择策略受到支持：∙仅故障转移 (fo)由于 I/O 错误，在路径发生故障之前，应将所有 I/O 操作发送至相同（首选）路径。
然后为后续的 I/O 操作选择一个备用路径。
∙负载平衡 (lb)通过评估适配器上每个路径连接的负载来选择用于 I/O 操作的路径。
负载是同时进行的 I/O 操作数量的函数。
如果多个路径具有相同的负载，则会从这些路径中随机选择一条路径。
负载平衡模式还会并入故障转移保护。
负载平衡策略也称为优化策略。
∙负载平衡顺序 (lbs)该策略与用于顺序 I/O 优化的负载平衡策略相同。
此负载平衡顺序策略也称为优化顺序策略。
这是默认设置。
∙轮循 (rr)从没有用于最后一个 I/O 操作的路径中随机选择用于每个 I/O 操作的路径。
如果设备只有两个路径，那么 SDD 会交替使用这两个路径。
∙轮循顺序 (rrs)该策略与针对顺序 I/O 进行优化的轮循 (round-robin) 策略相同。
您需要为您的环境选择最适当的 SDD 路径选择策略，并使用以下方法应用该策略。
注意：在更改算法之前，您需要将磁盘保留策略更改为 no_reserve。
# chdev -l hdiskX -a reserve_policy=no_reserve用于设置不同的 SDD 路径选择策略算法的命令的示例# chdev -l hdiskX -a algorithm=load_balance_port# chdev -l hdiskX -a algorithm=round_robin您可以使用 pcmpath query device 命令查看磁盘策略。
图 2. 轮循算法您也可以使用 nmon 工具查看 FCS 适配器使用情况。
该工具可帮助您了解正在使用哪些 FCS 适配器。
V7000_存储 安装配置
Storwize V7000初始化安装 – InitTool.exe
配置系统的管理IP地址
22 22
© 2010 IBM Corporation
Advanced Technical Skills, IBM China
Storwize V7000初始化安装 – 初次登录
请安装火狐浏览器对V7000进行管理 输入V7000的管理IP 例如：http://9.171.158.11
Advanced Technical Skills, IBM China
Storwize V7000初始化安装 – InitTool.exe
运行USB KEY里面的 InitTool.exe工具
21 21
© 2010 IBM Corporation
Advanced Technical Skills, IBM China
Storwize V7000 安装前准备-查看安排机柜位置
|
© 2010 IBM Corporation
Advanced Technical Skills, IBM China
Storwize V7000 硬件安装
|
© 2010 IBM Corporation
Advanced Technical Skills, IBM China
Storwize V7000 安装前准备-识别组件
|
© 2010 IBM Corporation
Advanced Technical Skills, IBM China
Storwize V7000 安装前准备-环境要求
|
© 2010 IBM Corporation
Advanced Technical Skills, IBM China
IBM Storwize V7000虚拟中端磁盘系统产品说明
IBM Storwize V7000虚拟中端磁盘系统存储市场中功能最强大、最易于使用的创新中端磁盘系统在当前的存储管理环境中，要想打破常规，控制日渐加剧的复杂性及爆炸性的数据增长，将是一项极为艰巨的任务。
以往用于购买和管理存储系统的做法现今已经失效。
由于资源短缺—物理存储资源和人力资源—因此，IT 部门必须快速优化并且简化他们的基础架构。
如果不能合理控制复杂性与增长，这个问题将会愈演愈烈。
中小企业还可能面临一系列的其他问题：• 服务器之间无法共享存储资源• 孤立的存储方法会降低生产力并且增加成本• 难以部署层级式存储系统• 迁移会造成系统的故障停机• 无法使用虚拟化存储产品来优化开销、资源和能力为了克服这些挑战，以便企业能够响应快速变化的市场动态，IBM Storwize ® V7000提供中级磁盘系统中前所未见的无与伦比的性能、可用性、高级功能和高级扩容能力。
IBM Storwize V7000是功能强大的中级磁盘系统，支持轻松使用和快速部署，无需添加资源。
Storwize V7000提供固有的IBM 存储资源虚拟化、SSD 优化和“精简调配”技术，能够提高存储资源利用率，并且允许您重新配置系统来快速轻松地满足不断变化的需求。
此外，Storwize V7000的高级功能还允许您在不中断系统运行的情况下将数据迁出现有存储器，从而简化实施流程并且最大限度地避免用户服务中断。
IBM Storwize V7000还允许您虚拟化和复用现有磁盘系统，从而进一步提高投资回报率(ROI)。
摘要• 易于中型企业使用的高级的企业级虚拟存储功能，即可使用自身存储空间，亦可控制外接异构存储• 集成了IBM System Storage ® Easy Tier ™ 功能，可自动迁移到高性能的固态驱动器(SSD)，从而最多可实现300%的性能改进• 精简调配允许您只购买所需的磁盘容量• 动态迁移功能在关键数据迁移期间确保应用的持续可用性• 通过IBM FlashCopy ®功能为在线备份、测试或数据挖掘提供速度更快、效率更高的数据拷贝支持• IBM Systems Director 提供灵活的服务器和存储器管理功能管理信息基础架构为了提高存储效率，许多IT机构都通过整合、虚拟化及自动层级等方法来降低前期购置与后期运营成本。
IBM Storwize V7000实施手册
IBM Storwize V7000实施手册（含图）
一、V7000界面
1.1V7000架构：
1.2V7000菜单：
二、V7000管理配置
2.1 创建RAID (MDisk）
V7000机头和扩展柜的硬盘为：内部盘。
通过V7000机头挂载的外部阵列为：外部盘（DS5000、EMC等）。
只有内部盘需要定制RAID，外部盘连进来就是MDisk。
2.1.1 操作：物理存储器→内部→配置存储器→选择其他配置
2.1.2 驱动器与RAID
选择硬盘类型及RAID级别，V7000现在支持RAID0、5、6、10。
2.1.3 如果钩选自动配置备件会为RAID添加一块热备盘。
optionize for performance 优化性能创建要符合相关条件如RAID5 最少要8块。
optionize for capaity 优化容量
可以使用已有的池或新建
三、池管理
3.1 新建池
3.2 输入池名
四、卷管理
4.1 创建卷
4.2 选择卷类型和池
4.3 输入卷名及大小（可以同时创建多个卷）
3.4 详细信息可以显示创建命令及过程。
3.5 如果已经创建过主机，可以继续做卷的MAP。
五、主机管理
5.1 新建主机
5.2 选择主机类型，现在支持光纤和iSCSI。
4.3 输入主机名和光纤通道WWN号或iSCSI端口
如图：
4.4 映射主机
六网络端口管理。
IBM Storwize V7000 技术白皮书
IBM Storwize V7000 中端磁盘系统要点•为所有规模的企业提供先进的企业级存储功能•在控制成本的同时，支持您不断增长的业务需求•凭借到高性能固态驱动器的自动迁移将性能提高多达200%1•在单个系统中整合块级和文件级存储，以实现简单性和更高的效率•通过动态迁移实现近乎持续的应用程序可用性•支持更快速、更高效的数据拷贝以用于在线备份、测试或数据挖掘•提供灵活的服务器与存储管理•易于使用的数据管理采用图形用户界面和点击式系统管理功能•城域镜像和全球镜像在系统之间同步或异步地复制数据以提高备份效率•固态驱动器适用于要求高速度和快速数据访问的应用程序•RAID 0、1、5、6 和10在如今的存储管理环境下，打破复杂性升高和数据爆炸式增长的循环可能是一大挑战。
购买和管理存储的老办法已变得不那么有效。
由于资源的限制，无论物理存储资源还是人力资源，IT 组织必须迅速采取行动以优化和简化其基础架构。
不受控制的复杂性和增长随着时间的推移只会变成更大的问题。
中小型组织可能还面临着一系列的挑战：登录社区，观看相关视频（http://goo.gl/kPjjc）•有中断的迁移•难以部署分层存储•不能在服务器之间共享存储•孤立的服务器和存储管理工具导致生产效率降低、成本升高•不能像使用虚拟务器一样，将虚拟化存储用作工具来优化开支、资源和能力为了克服这些挑战并使企业能够应对瞬息万变的市场，IBM® Storwize® V7000 Unified 提供了与虚拟化服务器环境互为补充的虚拟化存储系统，具有无与伦比的性能、可用性、先进的功能和高度可扩展的容量，这在中端磁盘系统中是前所未有的。
Storwize V7000 Unified 是一个强大的中端磁盘系统，经过精心打造，不仅易于使用还可实现快速部署，而无需额外的资源。
Storwize V7000 Unified 将块级和文件级工作负载整合到单个存储系统中，以简化管理并降低成本。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
Lab 3. Storwize V7000存储管理及主机连接
目标：
通过GUI练习V7K存储管理，包括创建Raid，创建存储池，创建Volume，HostMapping，多路径软件安装。
步骤：
创建Raid和Pool:
点击Physical Storage->Internal
选择SAS盘并点击Configure Storage
可以自动创建也可以手动创建，请选择Select a different configutation。
点击下拉菜单选择Raid级别，建议选择Raid5。
指定使用16块硬盘，并且以性能为导向的方式创建Raid5，不指定Spare盘，点击下一步。
选择创建一个新的Pool并输入Pool的名字Team1_Pool1，点击finish。
Raid、Pool创建过程开始
点击Physical storage->Pools，查看已创建的pool。
创建Volume:
点击Volume->All Vomumes。
点击New Volume。
选择Vomume的类型，通常情况下我们选择Generic。
选择Volume将来自于那有个pool，请选择刚才创建好的TeamX-PoolX pool。
给Volume命名并知道卷的容量。
Volume开始创建过程，点击close。
查看已经创建好的Volume。
点击Hosts->All Hosts。
点击New Host。
选择主机的接口类型，请选择FC Host。
给主机命名。
从下拉菜单中选择WWN或者手工输入WWN，并添加到主机下，点击Create Host。
开始创建主机过程。
完成后，查看已经定义好的主机。
右键点击主机，选择Modify Mapping。
选择主机和要Mapping给主机的volume，点击向右的箭头，点击apply，进行mapping。
查看定义好的主机，我们发现Host Mapping属性已经变成Yes，并且有相应的图标表示。
在Windows主机上配置多路径软件
下载并安装V7K多路径软件SDDDSM
在Windows主机上识别V7K映射过来的Volume。
SDDDSM提供的管理命令。