ibm storwize v7000图解配置文档
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。
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，创建新池：
选择” 卷所有卷/按池划分的卷/按主机划分的卷新建卷”，创建新的卷：
IBMv7000存储服务器双活配置流程
IBMv7000存储服务器双活配置流程
V7000做双活调试步骤
⼀：连接光纤交换机管理⼝，默认ip为：10.77.77.77，将本机ip设为通⽹段，web登陆10.77.77.77，⽤户名：admin，密码：password
登陆后界⾯如下，选择zone admin选项
点击zone选项，选择new zone，新建⼀个区域，v7000_a,点击ok
在name下拉框中选择原来的v7000_sva
在右侧zone members对话框中，将需要移除存储wwn码选中，点击remove member
点击name下拉框，选择新建的v7000_a，将刚才移出的存储wwn码加⼊到这⾥，选中需要加⼊的wwn，点击add member
点击上⽅zone config 选项框，选中v7000_a，点击add member，完成后依次点击save config
，enable config
出现上图成功字样（commt succeeded）后，表⽰操作完成，退出。
使⽤远程桌⾯连接到部服务器，⽜雪飞已经在服务器上做好putty连接。
点击需要进⼊的存储，选择open打开字符界⾯，⽤户名为admin
登陆后输⼊命令：lssystem
查看layer replication这条命令，表⽰存储不在storage层，使⽤命令将层级修改为storage层。
IBM_存储_V7000更换硬盘详细步骤_V7000鬼盘_消除_详细步骤
图 2.
若硬盘仍然在Volumes中或并非Offline状态，请参见V7000快速维护手册中的处理方法。 将待更换硬盘标记为Unused并进行更换
与DS4000/5000不同，V7000硬盘处于Failed状态后不能直接拔出更换新盘，这回导致Mdisk路径出现问题，需要CLI手工修 复。
后者是将正在使用的热备盘替换原来的磁盘划入Array 中，新盘需要手工设置为Spare 。
点击继续后，流程会很快结束，报错事件消失（但硬 盘仍处于Failed状态未改变）。
硬盘更换流程
找到损坏待更换的硬盘位置。 选择Pool——Internal Storage，即可查看所有硬盘槽位。找到报错的硬盘，如图1。 硬盘Item的右键菜单中有Indentify选项点亮指示灯。列表中的DriveID编号并非物理Slot号，请注意对应关系，查看“属性”找到
继续确 定
登录成 功
SSH到v7000的管理IP，然后分别执行下面命令即可消除鬼 盘
svctask chdrive -use failed 74 svctask chdrive -use unused 74
鬼盘 消除 机器运行状态正常
Байду номын сангаас
图5
图 6
将硬盘标记为Spare状态 在硬盘处于candidate的状态时，可将硬盘状态改为Spare，作为热备盘使用。
如图7、图8
图7
图 8
硬盘更换完毕 磁盘状态为Online，Spare。
图 9
V7000 鬼盘 删除 方法
运行 SSH
输入用户名 ：superuser PASSWORD: passw0rd
正确的盘位。 *需要注意的是，如果硬盘已经处于Failed状态，那么它的Status会变为Offline，此时硬盘物理指示灯的状态是全灭的。
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’为零)：
以自己研究下：。
IBM Storwize V7000介绍
十一长假的最后一天，IBM在美国纽约宣布了一系列存储新品。
起初，它们看上去在磁盘阵列的前端取得了一些成功，不过也有一部分消息可能会引起一些困惑。
首先让我们回顾一下。
IBM最近收购了Storwize，一家专攻主存储中实时数据压缩的公司。
蓝色巨人将该公司的产品去掉了Storwize的名称，现在成为了IBM实时压缩（Real-time Compression）产品线，大体上归于针对NAS的实时压缩设备，然而IBM看上去保留了原有的系列型号名称，例如：STN 6500（最多16个千兆以太网连接）和STN 6800（最多8个万兆以太网连接）。
不过，本次发布的重磅产品是IBM Storwize V7000阵列，至少在目前，它没有显示出在技术上和来自以前Storwize公司的产品有任何关联。
IBM Storwize V7000我想我们忽略了一些东西，于是我与StorageIO的Greg Schulz先生进行了确认，他也不清楚IBM对Storwize这个名字的重新定位。
下面是Greg所说的：“如果IBM试图发布一批存储产品，在将数据缩减（dfr）公司——以前大家知道的Storwize 重新命名为Real-time Compression方面，他们也许已经成功地制造了一层迷雾。
”“那个也许是易懂的，但难以理解或者模糊的是，使用或者再利用Storwize的品牌名称。
从那个已经发展并到处知晓的针对主存储的实时压缩，到命名一款基于SVC的存储虚拟化系统。
他们试图去说使用V7000是明智的存储选择，或者聪明的？他们试图指出（Storwize V7000）与SVC，或者是虚拟化存储的不同之处了吗？或者谈论关于Storwize品牌名称更多的信息？”就像所说的那样，难以理解的部分是Storwize V7000并没有Storwize的实时压缩技术，至少现在还没有。
IBM Storwize V7000是一款吸收了SAN Volume Controller（SVC）元素的中端存储系统，同时包含Easy Tier自动分层存储技术和XIV的用户界面。
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 将块级和文件级工作负载整合到单个存储系统中，以简化管理并降低成本。
V7000配置要点
一. Power750做HA的相关配置：解答：(1) 双以太网卡：推荐使用双卡，以实现网卡的冗余。
双网卡并不是HACMP的最小配置，但是使用双网卡可以在某个网卡失败的时候只做本机的网卡切换，而不必做主机切换。
推荐连接双以太网交换机，避免网络的单点故障；(2) 双HBA卡，避免HBA卡的单点故障；(3) 双SAN 交换机，避免交换机的单点故障；(4) 串口卡和心跳线，用于建立第二网络，传递心跳信息，避免在IP网络失败的情况形成主机孤岛；(5) 每台机器配置1套PowerHA软件。
二. Power720硬盘背板介绍：解答：Power720有两种类型的硬盘背板，fc#5618和fc#5630。
具体介绍如下：fc#5618，支持6块SFF 的SAS硬盘（HDDs/SDDs），一个SATA DVD光驱，一个半高的磁带机或者USB的移动硬盘。
该硬盘背板支持背板的分离，需要配置fc#5631来实现背板分离，每个SAS通道支持3块硬盘，其中，由fc#5631管理的三块硬盘支持RAID10。
该硬盘背板不支持RAID5，6，不支持对外的SAS端口。
fc#5630，支持8块SFF的SAS硬盘（HDDs/SDDs），一个SATA DVD光驱，一个半高的磁带机或者USB的移动硬盘。
支持RAID功能，175MB的写缓存，支持RAID5，6，一个对外的SAS端口。
但是该硬盘背板不支持背板的分离。
三. 如何在Power740上配置3个以上分区：解答：在Power 740中,内置硬盘能实现2个分区,要实现3个及以上分区,需要通过IO扩展实现。
1.前两个分区,需要配置支持分离的硬盘背板的编号为：fc#5618，同时还需要配置fc#5631的分离背板的选件，该选件为第二个分区提供了SAS Controller，且不占用PCI槽位，可以支持背板的分离，实现两个分区。
每个分区支持3块SFF的SAS硬盘。
其中，由fc#5631管理的分区支持RAID10。
- 1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
- 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
- 3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。
一、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 映射主机
六网络端口管理。