3par文档 - 360文档中心

3par存储配置文档

3par存储配置文档
HP 3PAR 管理地址：192.168.100.2
用户名：3paradm
密码：3pardata
1 HP 3par 存储配置内容
存储ipsan网络地址100.100.100.101-104
2 多路径软件配置内容
3 HP 3par 存储配置流程
笔记本端安装3par管理软件HP 3PAR Management Console,
IP:使用OOTB中设置的IP.
用户名和密码：3paradm/3pardata.
进入Management Console有以下几个步骤：
共五个步骤：
1：配置FC端口
2：创建CPG
3：创建HOST
4：创建VV
5：把VV指定给HOST
1：配置FC端口，选择PORT端口，设置Connection Node为Host设置Type为Point(现在系统默认已配置好，此步骤可以省略，检查一下即可)
2：进入IMC在3PAR中创建CPG：(如果使用系统自带的CPG，可省略此步骤)
3：创建VV: （一个VV最大不能超过16T）
想建几个磁盘就重复几次上面的操作，注意磁盘空间即可。

4：创建HOST主机：
5：把磁盘指定给HOST主机：。

3PAR主打胶片V2.1-2017-5

20850 / 20840
外部全闪存阵列性价比第1名 $0.23/IOPS
第 1名
第1个进入性价比前10的全闪存阵列
领先
545,164 IOPS
中端存储的最高性能
Confidential 保密
>62GB/s
18
最完整的闪存阵列产品线
3M
最具扩展性的全闪存阵列
3PAR 20850 3PAR 20840
3PAR在线换代
10
3PAR存储联邦技术
增强数据的流动性
应用加速性能型 SLA
高达 60PB 10M IOPS 一键平衡阵列间的负载
生产阵列经济型 SLA 生产阵列性能型 SLA
开发和测试
Confidential 保密
11
满足闪存优化数据中心的需求
存储联邦: 数据可以在线的在存储之间自由流动
可以在存储联邦中的不同类型3PAR（全闪存、高端和中端）间在线迁移容量和平衡IO负载
为关键业务设计，为闪存优化，企业级的功能和性能
Confidential 保密
5
3PAR存储不断创新的历程
2013
6月 3PAR进入全闪存市场 12月 SSD的容量超过20%
自动、智能地提供服务
应用加速便捷运维降低风险投资回报
简便的提供数据中心存储能力
统一的用户使用体验和可编程的REST APIs接口
+
HPE OneView HPE 3PAR SSMC
+
HPE RMC
+
HPE StoreFront Remote
3PAR自动化管理
自动优化的架构
Confidential 保密

HP-3PAR存储日常管理手册

HP-3PAR存储日常管理手册————————————————————————————————作者：————————————————————————————————日期：2a d m i n技术支持服务热线800-810-3860/400-810-3860V e r s i o n1.0目录一，3PAR存储介绍 (3)1.3PAR InSpire架构 (3)2.3PAR InForm软件 (4)3.3PAR主要构件 (7)4.3PAR组件编号系统 (9)5.3PAR LED状态指示灯 (10)二，日常配置 (11)1.添加主机Host (11)2.创建CPG (12)3.创建VV虚拟磁盘 (13)4.分配VV虚拟磁盘 (15)三，日常维护 (17)1.存储开机步骤 (17)2.存储关机步骤 (17)3.存储日志Insplore收集 (17)4.管理机SP日志SPLOR收集 (19)5.特定信息CLI命令行收集 (21)四，HP支持服务模式 (22)1.主动式响应--SP Call-Home (22)2.被动式响应—HP服务热线 (22)3.被动式响应—邮寄存储日志 (23)May.2012Version 1.0admin一，3PAR存储介绍3PAR 系列存储平台具有超高的灵活性和高效性，突破了公共基础设施中传统存储阵列的局限性。

作为精简配置、绿色存储以及存储虚拟化技术的先行者，3PAR能帮助用户降低能耗、实履行环保义务，还可削减最高达50%的存储总拥有成本1.3PAR InSpire架构紧密集群化、多客户端的3PAR InSpire 构架设计，消除了传统整体式和模块化阵列价格高昂和扩展十分复杂的弊端。

用户可以一开始只购买较小的系统，之后，随着业务量的增加再进行扩展，即经济且连续地添加新的应用和工作负载，所有这些都将在一个单一、自动化的分层阵列中进行。

内置Thin Built In™的 Gen3 /Gen4 ASIC内置Thin Built In™的3PAR Gen3 ASIC 提供一种高效、基于硬件的零检测机制。

HP 3PAR存储解决方案模板v2

贵单位HP- 3PAR存储解决方案目录贵单位 (1)第1章． ......................................................................... 前言5第2章． ......................................................................... 简介52.1用户现状 (5)2.2用户需求 (6)第3章． ................................................................... 需求分析73.1容量分析 (7)3.2性能分析 (7)3.3维护分析 (10)3.3.1存储部署 (10)3.3.2存储配置调整 (11)3.3.3存储扩容 (12)3.3.4性能优化 (14)3.4高可用性需求 (15)3.5容灾需求 (16)第4章． ................................................................... 解决方案164.1方案概述 (16)4.2方案配置 (18)4.3方案基本优势 (19)4.3.1全网状控制器集群架构 (19)4.3.2独特的双分类处理单元 (19)4.3.3全新的磁盘划分方式 (20)4.3.4高性能存储系统 (22)4.3.4存储的高可用性 (23)4.3.5业务连续性 (24)4.3.6存储数据精简 (25)4.3.7动态的存储优化 (27)4.3.8数据分层以与热点数据迁移 (28)4.3.9虚拟资源调配 (29)4.3.10智能的管理界面 (31)4.4VM WARE环境解决方案 (31)4.4.1提高VMware vSphere投资回报 (32)4.4.2提高虚拟化环境的整合力度 (33)4.4.3简化虚拟化环境的管理 (37)4.5O RACLE环境解决方案 (40)4.5.1 Oracle环境面临的挑战 (40)4.5.2 HP-3PAR Thin与Oracle ASM环境的完美结合.. 414.5.3 Oracle环境的更高磁盘利用率 (45)4.5.3 智能和主动的分层存储技术 (46)4.5.5 总结 (48)第1章．前言承蒙贵单位对HP-3PAR的信任和厚爱，提供我们参与其系统建设的机会，我们不胜感激与深表荣幸。

3PAR 基础功能-尚道计划实验手册v1

Rev. 15.33
i
HP Storage TME, Houston
ii
Rev. 15.33
HP 3PAR Basic Provisioning
实验 1 HP 3PAR 基础供应实验 Lab 1 实验 1
Objectives 目标
After completing this lab, you should be able to: 完成这个实验，您将可以:
Contents 目录
Lab 1—HP 3PAR Basic Provisioning 实验 1—HP 3PAR 基础供应实验
Objectives 目标..................................................................................................... 1 Requirements 需求 ............................................................................................... 2 Exercise 1—Installing the SSMC ........................................................................... 4 练习 1—安装 SSMC .............................................................................................. 4 Exercise 2—Configuring the SSMC ..................................................................... 10 练习 2—配置 SSMC ............................................................................................ 10 Exercise 3—Creating a CPG ............................................................................... 19 练习 3—创建一个 CPG ........................................................................................ 19 Exercise 4—Creating a VV .................................................................................. 24 练习 4—创建一个 VV ........................................................................................... 24 Exercise 5—Installing Host Explorer .................................................................... 27 练习 5—安装 Host Explorer ................................................................................. 27 Exercise 6—Exporting a VV to a host .................................................................. 32 练习 6—挂载一个 VV 到一台主机 ........................................................................ 32 Exercise 7—Installing and configuring MPIO ....................................................... 39 练习 7—安装并配置 MPIO ................................................................................... 39 Exercise 8—Making a volume available to Windows ........................................... 46 练习 8—让卷可用于 Windows .............................................................................. 46

3PAR_Power OFF ON Procedures

3PAR InServ Power off/on ProcedurePOWER OFF PROCEDUREThe following procedure describes how to safely remove power from the storage server and the service processor.1. To Shutdown the Inserv storage server:From a CLI prompt, enter ‘shutdownsys halt’.Wait until the system has completed shutdown by observing that all controller nodes in the system have the Hot-Plug LED solid green and the Node Status LED blinking fast-green (a rate of three blinks per second)Unlock and open the rear door of the storage server.Turn all power supply rocker switches to the OFF position.2. To shutdown the Service Processor :SSH to the service processor or physically connect a maintenance PC to the Serial Connection (See Physical reference manual in the rear door for settings).Enter your login name and password(Pls contact 3PAR support if you do not know the login name/ password )In the service processor window, issue the spmaint command, if necessary.Result: The 3PAR Service Processor Menu appears.1 SP Main3PAR Service Processor MenuTransfer media: ethernet Transfer status: OkEnter Control-C at any time to abort this process1 ==> SP Control/Status2 ==> Network Configuration3 ==> InServ Configuration Management4 ==> InServ Product Maintenance5 ==> Local Notification Configuration6 ==> Site Authentication Key Manipulation7 ==> Interactive CLI for an InServ8 ==> Execute a command on a nodeX ExitSelect option 1: SP Control/StatusResult: The SP Control/Status menu appears.1 SP CONTROL3PAR Service Processor MenuTransfer media: ethernet Transfer status: OkSP Control FunctionsEnter Control-C at any time to abort this process1 ==> Display SP Version2 ==> Reboot SP3 ==> Halt SP4 ==> Stop InServ related Processes5 ==> Start InServ related Processes6 ==> File Transfer Monitor7 ==> SP File Transfer Trigger8 ==> Reset Quiesce state in Transfer process9 ==> Mount a CDROM10 ==> Unmount a CDROM11 ==> SP Date/Time maintenance12 ==> Manage NTP configuration13 ==> Display SP status14 ==> SP User Access Control15 ==> SP Process Control Parameters16 ==> Maintain SP Software17 ==> SP File maintenance18 ==> De-install SP ( Back-in-the-box )X Return to previous menuSelect option 3, Halt SP.Result: The SP SHUTDOWN window appears.1.3.1 SP SHUTDOWN3PAR Service Processor MenuConfirmationEnter Control-C at any time to abort this processHalt will power off the SP! Are you certainyou want to halt the SP now?(y or n)Type y and press Enter.Result: The following output is displayed:.Broadcast message from root (ttyS0) Fri Oct 7 12:51:33 2006...The system is going down for system halt NOW !!Verify that the blue LED on the front of the service processor is no longer illuminated.3 Remove AC to the storage server by turning off the PDU circuit breakers of ALL fourPDUs in the cabinetPOWER ON PROCEDURETurn on AC power to the cabinet(s) by turning on all the PDU circuit breakers of ALL four PDUs. Then turn on all the power switches of all the disk enclosures, controller nodes, batteries and the service processor.To verify that the system is operational, observe that all drive chassis LEDs that are illuminated SHOULD be solid green and all controller node status LEDs are blinking green once per second. (It may help best to remove all bezels to assist in visual inspections) Verify that the blue LED on the front of the service processor is illuminated.NOTESThe system takes approximately five minutes to become fully operational, providing it was gracefully shut down. If the system was powered off abruptly, powering on could take considerably longer.Gracefully means you issued shutdownsys halt and then switched the PDUs off when the nodes were halted.Abruptly means that power was simply turned off to the system, causing battery backup of the cache data to the IDE disks.Extremely abruptly means an uncontrolled shutdown, or powering off a drive chassis cabinet (causing logical disks to become degraded/failed), and then powering off the node cabinet.Considerably longer means the time varies depending on how many logical disks exist and must go through ldchk.。

3PAR Remote Connectivity

3PAR InServ ConnectivityThe intent of this document is to present an overview of the remote connectivity options offeredon the InServ product line. Additionally it will outline the benefits our customers receive when they choose remote connectivity, along with the limitations if remote connectivity is not available. Enabling remote connectivity allows HP-3PAR support to deliver rapid, proactive response with complete 24x7 remote monitoring and analysis to identify issues and proactively communicate them to customers. Allowing remote connectivity with remote operations enables “lights out” online remote software updates and service actions that eliminate scheduling and onsite visit delays.If customers do not allow any form of remote connectivity, HP-3PAR’s ability to quickly identifythe root cause of an issue can be severely impacted. InServ issues may take longer to determine root cause, which would result in extending the time required to resolve the reported issue. Depending on the type of issue encountered, the delay in problem resolution can be significantly longer than if remote connectivity was available.All of the connectivity options described in this document are enabled via the Service Processor. The Service Processor (SP) is a HP-3PAR provided server that is housed within the basecabinet of each InServ Storage Server. The SP serves as the communication interface withinthe customer’s IP network for all service-related communication to and from the InServ Storage Server. It gathers diagnostic information from the InServ and periodically transmits it over a secure network to HP-3PAR Central, if allowed. All customer-authorized remote service connections to a given InServ leverage the Service Processor as the conduit for executingservice actions on the InServ.The connectivity options available to our customers are listed below, each one will be explained and where appropriate the customer requirements will be documented.∙Secure Network Mode∙SP mode∙Local notification and RAP Forwarding∙Weekly File TransferIn all cases the customer can control how and when communications takes place and if Remote Operations is allowed. This concept will be explored in the following detailed explanation ofeach transfer mode.Secure Network ModeThis is the preferred method of transfer as it is secure, easy for customers to implement in their firewall, and offers customers the most access control options.Secure Network Mode utilizes the HP-3PAR Secure Service Architecture. The HP-3PAR Secure Service architecture provides secure service communication between the HP-3PAR InServ Storage Servers at a customer’s site and HP-3PAR Central, enabling secure diagnostic data transmission and remote service connections. Diagnostic data can be transferred frequently and maintained centrally on a historical basis. As a result, manual intervention in the support process is minimized and pro-active fault detection and analysis is enhanced. Further, with remote operations connectivity for troubleshooting, HP-3PAR Customer Service and Engineering can deliver the fastest, most reliable response and quickest resolution time.The Secure Service Architecture leverages the industry-standard HTTP over Secure Socket Layer (HTTPS) protocol for all external communication, ensuring that the communication is secure and any data transmission is encrypted. The Secure Service Architecture is also firewall-friendly. HP-3PAR only requires that HTTPS Port 443 be enabled on the customer’s external firewall, and all communication with HP-3PAR Support is initiated in an outbound manner.Secure Network Mode is enabled as part of the Service Processor “Moment of Birth” which occurs at installation time. All of the information required to set up Secure Network Mode is captured in the SA Document.The customer requirements for Secure Network Mode are as follows:Port 443 open (industry standard HTTPS port) for file transfer and Remote OperationsThis can also be enabled anytime after the install by scheduling the change with the HP-3PAR Service Planning Specialist (SPS) team. The HP-3PAR SPS team will engage the HP-3PAR National Technical Support Specialist (NTSS) or 3PAR Deployment Center (3DC) team to plan and support the activity. The SPS team will also schedule the activity with the customer.Please note that the inbound connection is only needed for remote operations and it does not need to remain on constantly. Both the inbound and outbound access is controlled by the customer via Customer Controlled Access (CCA) setting on the Service Processor. This setting can be modified by the customer at any time.SP ModeSP mode is the HP-3PAR legacy method of file transfer and also provides secure file transfer between the InServ on the Customer site and HP-3PAR Central in Fremont, CA. This optionwill be retired in the near future.The protocol for the connection between the Service Processor and HP-3PAR Central is SSH. The following firewall ports at the customer site must be opened to allow the file transfer to take place.For outbound connectivity (file transfer to HP-3PAR Central)Outbound access from the Service Processor to (66.126.187.144) ORIGINATES from ports 1024 – 65535 TO port 22 on andrequires all related session traffic to be allowed.For inbound connectivity (remote operations to the InServ)Inbound (remote operations) access from to the ServiceProcessor ORIGINATES from ports 1024-65535 TO port 22 on the Service Processorand requires all related session traffic be allowed.Please note that the inbound connection is only needed for remote operations and it does not need to remain on constantly. Both the inbound and outbound access is controlled by the customer via Customer Controlled Access (CCA) setting on the Service Processor. This setting can be modified by the customer at any time.Local Notification and Rap ForwardingFor customers that will not allow remote connectivity, while they will not receive the full benefitof the proactive support that HP-3PAR offers, there are options which will provide limited notification of alerts.Local Notification utilizes customer email to send events to customer defined individuals and/or group-ids. The Service Processor is configured during the “Moment of Birth” with information supplied by the SA Doc to send events to the defined email addresses. The limitation of only using Local Notification is that it places ALL responsibility for problem reporting on the customer. HP-3PAR are not made aware of any problems with the InServ unless the customer reports them first.Additionally RAP (Real-time Alert Processing) forwarding can be enabled, if no outbound connection is possible, to email these events to HP-3PAR Central in a format that is acceptedby the Service Tools Platform. These events will be catalogued and appropriate notifications to HP-3PAR support will be generated. While this does not provide detailed information it doesprovide notifications of problems and system warnings, and it does allow HP-3PAR to be proactively notified of system alerts.The following customer specific information is required to set up Local Notification at the Service Processor:Mail Host IP AddressMail Host Domain NameCompany or Site NameSite NumberTime ZoneMail to NamesMail AddressesWeekly File TransferThis option is also for customers that will not allow remote connectivity, while they will not receive the full benefit of the proactive support that HP-3PAR offers, there are options which will provide limited notification of alerts.The Service Processor gathers logs and automatically creates a zipped file called“3PAR_WEEKLY...” every Sunday (~ 4 AM, PT). This file contains much of the pertinent system information that would have been transferred during the week if transfers were allowed, such as alerts, failure information, information regarding temperature, voltage and battery conditions, and various hardware and software states.The customer can download this file from the Service Processor on Monday morning and send it to HP-3PAR for analysis via email or ftp. This provides a delayed view of the events that have occurred during the previous week, but does allow the HP-3PAR Support Team to identify problems or potential issues.Policy Manager (optional software)Policy Manager is an optional feature, purchased separately, and designed to work in tandem with Secure Network Mode. Policy Manager is software that is loaded onto a customer server and is completely customer controlled. Policy Manager allows the customer to set policies around Remote Operations as well as capturing an audit log of all activity. The Policy Manager is defined in a separate document but is mentioned here to make the reader aware of it.Policy Manager allows customers to define and implement the following key policies for remote operations:File Upload – Defines whether file uploads of diagnostic data to HP-3PAR Central are allowed or disallowed.File Download – Defines whether file downloads from HP-3PAR Central are allowed or disallowed.Remote Session – Defines whether or not remote sessions for remote serviceability can be established with HP-3PAR Central. These sessions are only available to customers where HP- 3PAR is the primary support provider.Each of the above policies can be configured with one of the following values:Always Allow – All remote connection requests are allowedAlways Deny – All remote connection requests are denied.Ask – The Service Processor seeks approval via email within a configured timeout window from the configured customer administrator for any remote connection requests. If approved, the remote connection request is allowed. If denied or the configured timeout window elapses, the remote connection is denied.。

3par配置说明书

3PAR创建主机、划盘划盘的具体步骤:
1. 登陆3par管理界面HP 3PAR Management Console 4.3
IP:
User Name: 3paradm
Password:3pardata
2. 新建和查看HOST信息
➢登陆界面→HOST→Common Actions→create host
➢进入创建界面→不用勾选→next
➢填写主机名称、选择操作系统类型→next
➢从左选框选择该主机HBA卡WWN点至右选框；若该主机HBA卡WWN在左选框未列出来，则手动下下方输出框输入WWN添加至右选框→next
➢完成创建，点击左菜单栏host即可查看已建主机列表。

3. 创建CPG
➢点击左下菜单Provisioning→create CPG
➢进入创建界面→不用勾选→next
➢填写CPG名称、选择CPG raid级别和类型→next
➢创建成功→左上菜单点击CPGs可查看已建CPG信息
4. 创建VV
➢选择左下菜单Provisioning→create virtual volume
➢进入创建界面：填写VV name、VV size；选择VV类型、选择所在CPG名称→finish
➢完成创建，点击左菜单栏Virtual Volumes即可查看已建VV列表。

5. 分配VV到主机
➢点击左下菜单Export Volumes
➢进入分配VV界面不用勾选→next
➢在左选框选择需要分配的VV，右选框选择VV需要分配至的主机，LUN勾选Auto （可选择多个VV至一台主机或者选择一个VV至多台主机）→next
➢完成分配VV，点击左上菜单Virtual Volume即可查看VV与HOST对应关系。

3PAR产品介绍

• 提高性能 • 扩容性能更好
500 400
Chunklets
300
200 100
0 1 20 39 58 77 96 Physical Disks
After Dynamic Optimization
600
Free Used
500 400
Chunklets
300
200 100
0 1 20 39 58 Physical Disks 77 96
传统阵列
InServ
15
©2010 3PAR Inc. All rights reserved. | 3PAR Confidential
虚拟资源调配 Thin-Provisioning
传统阵列
- 按照预留的空间进行分配 Exported Volumes Exported Volumes Exported Volumes Exported Volumes
Autonomic Tiering and Data Movement
Save ~30% on $/IOPS and $/GB vs. Fibre Channel
3PAR Company Confidential
©2010 3PAR Inc. All rights reserved. | 3PAR Confidential
Month/Day/Year, Presentation Title
存储体系架构的发展
多控制器冗余架构双控制器架构投入单控制器
服务级别/性能
4
©2010 3PAR Inc. All rights reserved. | 3PAR Confidential
磁盘阵列的架构演变
传统阵列

3par 存储架构

Logical Disks are bound to, serviced All LDs are by bound and load balanced together transparently Each Physical Drive across all Nodes Drive Magazines have Drive Chassis are Nodes are added in pairs RAID Sets are bound to form a into single is divided “Chunklets” 4 of the same drives point-to-point connected for cache redundancy. together to form RAID sets ( in 3+1 R5 volume. And presented each 256 MB size. FC 15, SATA, SSD to controllers nodes in An with 4 etc. or all more logical disks for example will L to InServ the host across D Drive magazines can the T Series InServs to nodes also supports stripe the 4 members ports and all nodes. Each VV “ is automatically be mixed inside the” provide cage level “ Cache Persistence ” of the RAID set into Enabling a TRUE widely striped across same drive chassis. availability. Which enables separate chassis. active/active chunklets onto all disk and The ability withstand maintenance windows Massively striping configuration on a PER spindles of the same type the loss of an Entire upgrades without data and enabling LUN basis. Not SATA, by (Fiber channel, drive enclosure without performance penalties. chassis level Active/passive a default etc. to on losing access your availability. per LUN abasis as other Creating massively parallel data. (default) architectures. system

3par 安装指南

3par安装指南
第一章磁阵安装
1．连接console口
对于SS7000系列，将串口线连接node后端mfg口，如下图中console口。

连接线为DB9 female to RJ45 serial adapter assembly (P/N 180–0055)。

串口设置如下：
2．3PAR 阵列初始化
Login：console
Password： cmp43pd (如3par OS 为3.2.2 or later，需要致电响应中心获取)
选择第一项
设定日期时间
设定系统名
检查硬件状态
是否做压力测试
设置热备空间
检查license状态
是否打开API功能
设置网络参数
完成初始化
3.2 3PAR 管理机初始化Login：root
SP初始化完成后会自动重启
将3par磁阵加入SP进行管理，选择第二项
输入磁阵的IP地址
加入磁阵成功
2.日常维护
SP登录的用户名/密码：3parcust/3parInServ 收集磁阵日志
收集SP日志。

HP 3par安装配置文档

3par存储操作手册1 、 VSP-3par存储报警和日志收集平台，安装在B7-5的虚拟机上。

该虚拟机IP 10.17.200.225访问方式：Https：10.17.200.225用户名 spvar口令HP3parvarAction 下面的InSplore 在有问题的情况下，并且VSP断开外网连接，手动收集日志作分析。

如果想检查系统健康状态，点击Health Check 进行检查，如下图：2、3par管理软件安装在B7-5上的管理客户端HP 3PAR Management Console 用来对3par存储进行管理（1）IP address 选择 3par控制器心跳地址10.17.200.226Username :3paradmPassword :3pardata进入看到如下界面(2)新建HOST主机：点击后，点击“creat host”新建主机，点击“Export volume”将划出的虚拟盘挂到主机上。

新建主机：只需填写name和选择host os接下去选择对应主机的wwn号注：一般服务器的wwn号能在HBA卡边上的标签上查到。

HP刀片服务器的WWN号需要登录刀箱管理地址进行查看：老10.17.200.233，新10.17.200.224https://10.17.200.233/ admin、admin点击，(WWN号)选择完WWN号之后直接点击finish(2)点击provisioning，Create Virtual Volume，新建虚拟盘，主需要填写：name，选择fully provisioned，在size中填写大小，选择的单位大小，选择raid级别，一般选择raid5，之后点击finish（3）挂盘：将虚拟盘挂接到新建的主机上。

，点击“export volume”，然后分别：选中“左边的虚拟盘”和“右边的主机”，（可多选），之后点击finish，这样就将虚拟盘挂到了需要的主机上了。

HP 3PAR 命令行界面管理手册

HP 3PAR 命令行界面管理手册HP3PAR OS3.1.3摘要本手册适用于所有级别的系统和存储管理员。

本指南提供了关于安装 HP 3PAR CLI 以及使用该 CLI 配置和管理 HP 3PARStorage System 的说明。

拥有、使用或复制本软件须获得 HP 颁发的有效许可证。

依据 FAR 12.211 和 12.212，商业计算机软件、计算机软件文档以及商业物品的技术数据根据供应商的标准商业许可证授权于美国政府。

此处包含的信息如有更改，恕不另行通知。

惠普产品与服务仅有的担保已在这类产品与服务附带的明确担保声明中阐明。

此处任何信息均不构成额外的保修条款。

对于本文包含的技术或编辑上的错误或遗漏，惠普概不负责。

声明Microsoft® 和 Windows® 是 Microsoft Corporation 在美国的注册商标。

Java、Oracle 和 Oracle Solaris 是 Oracle 和/或其子公司的注册商标。

UNIX® 是 The Open Group 的注册商标。

担保担保声明：要获取此产品的担保副本，请访问担保信息网站：/go/storagewarranty目录1 安装 HP 3PAR 命令行界面 (12)关于 HP 3PAR 命令行界面 (12)受支持平台 (12)系统要求 (12)磁盘空间要求 (12)安装说明 (13)安装之前 (13)在Windows 上进行图形化安装 (14)在 UNIX 和 Linux 上进行命令行安装 (14)在Windows 上进行无提示安装 (15)在 UNIX 和 Linux 上进行无提示安装 (15)在 UNIX 和 Linux 上设置 CLI 的路径 (16)排除安装故障 (16)删除 HP 3PAR CLI (16)在 Windows 上进行 GUI 卸载 (17)在 UNIX 和 Linux 上进行命令行卸载 (17)在Windows 上进行无提示卸载 (17)在 UNIX 和 Linux 上进行无提示卸载 (17)脚本注意事项 (17)2 SSL 证书 (18)3 管理用户帐户和连接 (19)了解用户帐户 (19)默认用户帐户 (20)对 CLI 用户进行身份验证和授权 (20)查看用户角色和权限 (21)创建用户 (21)查看用户 (22)删除用户 (22)向域中添加用户 (22)从域中删除用户 (22)设置用户默认域 (22)删除用户的默认域 (23)设置用户的当前域 (23)删除用户的当前域 (23)查看用户连接 (23)删除用户连接 (23)配置 LDAP 连接 (23)采用 SASL 绑定的 Active Directory LDAP 配置 (24)配置连接参数 (24)配置绑定参数 (25)配置帐户位置参数 (26)配置“组到角色”映射参数 (27)采用 SSL 上简单绑定的 Active Directory LDAP 配置 (29)配置连接参数 (29)配置绑定参数 (30)配置 CA 证书 (30)配置帐户位置参数 (31)配置“组到角色”映射参数 (32)采用 SSL 上简单绑定的 OpenLDAP 配置 (34)配置连接参数 (34)目录3配置绑定参数 (34)配置组位置参数 (35)配置“组到角色”映射参数 (35)在使用域的系统上配置 LDAP 连接 (37)4 运行 HP 3PAR 命令行界面 (40)全局选项和环境变量 (40)常规控制和帮助命令 (42)具有列帮助的命令 (42)使用 SSL (43)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDSOCKSSL 环境变量 (43)设置 Windows 中的 TPDSOCKSSL 环境变量 (43)使用 -sockssl 选项 (43)设置 TPDSYSNAME 环境变量 (43)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDSYSNAME 环境变量 (44)设置 Windows 中的 TPDSYSNAME 环境变量 (44)使用 -sys 选项 (44)使用系统名称 (44)设置用户名称和密码 (44)使用setpassword 命令 (45)设置 TPDPWFILE 环境变量 (45)使用 –pwf 选项 (45)使用-password 选项 (45)为多个 HP 3PAR 存储阵列设置密码 (45)验证 CLI 服务器证书 (46)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDCERTFILE 环境变量 (48)设置 Windows 中的 TPDCERTFILE 环境变量 (46)使用-certfile 选项 (47)将证书文件保存到某个目录 (47)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDCERTDIR 环境变量 (48)设置 Windows 中的 TPDCERTDIR 环境变量 (48)使用 -certdir 选项 (49)检查主机名以验证证书 (47)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDCERTHOSTCHECK 环境变量 (48)设置 Windows 中的 TPDCERTHOSTCHECK 环境变量 (48)使用 -certhostcheck 选项 (49)隐藏证书验证提示 (48)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDNOCERTPROMPT 环境变量 (48)设置 Windows 中的 TPDNOCERTPROMPT 环境变量 (48)使用 -nocertprompt 选项 (49)缓存客户端字节码 (49)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDCACHEDIR 环境变量 (49)设置 Windows 中的 TPDCACHEDIR 环境变量 (49)启动文件 (49)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDSTARTFILE 环境变量 (49)设置 Windows 中的 TPDSTARTFILE 环境变量 (49)逗号分隔值 (50)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDCSVTABLE 环境变量 (50)设置 Windows 中的 TPDCSVTABLE 环境变量 (50)使用-csvtable 选项 (50)列出域 (50)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDLISTDOM 环境变量 (51)设置 Windows 中的 TPDLISTDOM 环境变量 (51)使用 -listdom 选项 (51)表标题和总计数 (51)4目录设置 Solaris、Linux、HP-UX 和 AIX 中的环境变量 (52)设置 Windows 中的环境变量 (52)使用 -nohdtot 选项 (52)使用 -hafter 选项 (52)强制执行命令 (52)设置 Solaris、Linux、HP-UX 和 AIX 中的 TPDFORCE 环境变量 (53)设置 Windows 中的 TPDFORCE 环境变量 (53)独立命令 (53)SSH (53)使用 SSH 的优势 (54)使用 SSH 时的 CLI 用户名限制 (54)新用户 (54)现有用户 (54)使用 SSH 访问 CLI (55)使用 SSH 编写 CLI 脚本 (55)5 管理 HP 3PAR 虚拟域 (58)概述 (58)默认域 (58)创建域 (58)查看域 (58)修改域 (59)更改域名 (59)向域添加注解 (59)删除域 (59)管理域对象 (59)将域对象移至其他域 (59)从域对象删除域关联 (60)管理虚拟域自治组 (60)创建虚拟域集 (60)将虚拟域添加至虚拟域集 (60)修改虚拟域集 (60)删除虚拟域集 (61)查看虚拟域集 (61)6 管理端口和主机 (62)概述 (62)修改端口参数 (62)FC 端口设置 (63)iSCSI 端口设置 (63)端口目标方、发起方和对等模式 (64)活动或非活动主机 (64)管理主机 (64)主机管理 CLI 命令 (65)创建主机 (65)创建具有光纤通道路径的主机 (65)创建具有iSCSI 路径的主机 (65)创建主机但不分配路径 (66)修改主机 (66)更改主机名称 (66)添加光纤通道路径WWN (66)添加 iSCSI 路径 iSCSI 名称 (66)删除光纤通道路径WWN (67)删除 iSCSI 路径 iSCSI 名称 (67)配置 iSCSI CHAP 身份验证信息 (67)删除 iSCSI CHAP 身份验证信息 (67)目录5移动、删除主机和断开主机的连接 (67)删除主机路径 (68)管理主机自治组 (68)创建主机集 (69)向主机集中添加主机 (69)修改主机集 (69)删除主机集 (69)管理主机角色 (69)Host Explorer 软件代理 (71)主机和虚拟域 (71)创建域特有的主机 (71)修改域特有的主机 (71)更改主机域 (72)使用持久端口进行非破坏性在线软件升级 (72)7 管理 CPG 和虚拟卷 (76)概述 (76)通用配置组 (76)通用配置组容量递增注意事项 (76)创建通用配置组的系统指南 (77)通用配置组 CLI 命令 (77)创建通用配置组 (77)修改通用配置组 (78)设置快照空间使用警告 (78)设置通用配置组的自动增长量 (78)整合通用配置组空间 (78)删除通用配置组 (78)虚拟卷类型 (79)完全配置虚拟卷 (79)精简配置虚拟卷 (79)虚拟卷 CLI 命令 (79)创建虚拟卷 (80)创建完全配置虚拟卷 (80)创建精简配置虚拟卷 (80)修改虚拟卷 (81)增大虚拟卷 (81)联机转换虚拟卷 (81)将完全配置虚拟卷转换为精简配置虚拟卷 (82)将精简配置虚拟卷转换为完全配置虚拟卷 (82)使用 HP 3PAR Thin Conversion 软件减小卷的大小 (82)手动将完全配置虚拟卷转换为精简配置虚拟卷 (82)使用 HP 3PAR Thin Persistence 软件减小卷的大小 (83)管理虚拟卷自治组 (83)创建虚拟卷集 (83)向虚拟卷集中添加虚拟卷 (83)修改虚拟卷集 (84)删除虚拟卷集 (84)释放虚拟卷快照空间 (84)设置虚拟卷的到期时间 (84)设置虚拟卷的保留时间 (85)删除虚拟卷 (85)验证和修复虚拟卷 (86)导出虚拟卷 (86)创建 VLUN 模板 (86)创建主机可见或主机集类型的 VLUN 模板 (86)6目录创建端口呈现类型的 VLUN 模板 (86)创建匹配集类型的 VLUN 模板 (87)取消导出虚拟卷 (87)删除主机可见或主机集类型的VLUN 模板 (87)删除端口呈现类型的VLUN 模板 (87)删除匹配集类型的 VLUN 模板 (88)虚拟域、CPG 和虚拟卷 (88)在域中创建通用配置组 (88)在虚拟域中创建虚拟卷 (88)修改域中的虚拟卷 (89)增长域中的虚拟卷 (89)释放域中的虚拟卷快照空间 (89)导出域中的虚拟卷 (89)在 All 域中创建 VLUN 模板 (89)在 Specific 域中创建 VLUN 模板 (89)将通用配置组移至域 (90)8 管理虚拟卷复制 (91)虚拟副本 (91)创建虚拟副本 (91)升级虚拟副本 (92)修改虚拟副本 (92)删除虚拟副本 (92)创建虚拟副本组 (92)联机创建虚拟副本 (93)物理副本 (93)创建脱机物理副本 (93)创建联机物理副本 (94)创建物理副本组 (94)重新同步物理副本 (95)重新同步一组物理副本 (95)升级物理副本 (95)创建联机副本 (95)快照和域 (95)移动快照 (96)9 创建和应用模板 (97)概述 (97)创建模板 (97)应用模板 (97)使用模板创建虚拟卷和逻辑磁盘 (97)使用模板创建通用配置组 (97)修改模板 (98)查看模板参数 (98)添加和替换模板参数 (98)删除模板参数 (98)删除模板 (98)10 监控系统和物理磁盘容量 (99)概述 (99)系统容量 (99)确定系统总容量 (99)按照物理磁盘类型确定系统容量 (100)物理磁盘容量 (100)确定物理磁盘总容量 (100)按照磁盘类型确定物理磁盘容量 (101)目录7确定特定物理磁盘的容量 (101)备用存储块 (101)查看备用存储块 (101)逻辑磁盘和存储块初始化 (102)恢复失败的 RAID 集 (102)查看硬件清单 (103)11 数据加密 (104)支持的配置 (105)数据加密许可证 (105)使用自加密磁盘 (105)获得所有权 (105)使用 controlencryption 命令 (106)启用加密 (106)备份身份验证密钥文件 (106)还原密钥文件 (106)重新生成身份验证密钥 (107)显示数据加密状态 (107)更换故障的磁盘驱动器 (107)使用新固件升级 SED (108)解除一个现存的 SED (108)数据加密命令 (108)12 管理事件和警报 (109)概述 (109)检查系统的状态 (109)监控和管理警报 (109)查看警报 (109)设置警报状态 (109)删除警报 (109)设置系统警报 (109)设置原始空间阈值警报 (110)监控和管理事件日志 (110)查看事件日志 (110)停止的逻辑磁盘和缺失的物理磁盘 (110)保留的数据 (111)13 查看统计数据和直方图 (112)概述 (112)查看统计数据 (112)查看物理磁盘的统计数据 (112)查看端口统计数据 (112)查看 VLUN 统计数据 (113)查看虚拟卷统计数据 (113)查看数据高速缓存的统计信息 (113)查看 CPU 使用情况的统计信息 (113)使用节点上系统报告查看统计报告 (113)查看区域 I/O 密度的统计报告 (114)查看已使用容量的统计报告（空间报告） (114)查看性能的统计报告 (114)查看性能的统计报告直方图 (114)查看直方图 (114)查看存储块的直方图 (115)查看逻辑磁盘的直方图 (115)查看物理磁盘的直方图 (115)查看端口的直方图 (115)8目录查看 VLUN 的直方图 (116)查看虚拟卷的直方图 (116)14 管理任务 (117)概述 (117)任务管理器 (117)任务 ID (117)任务管理器命令 (117)启动任务 (118)显示任务信息 (118)设置运行的任务的优先级 (119)等待任务 (119)删除任务 (120)取消任务 (120)任务类型 (121)background_command (122)compact_cpg (122)compact_lds (122)promote_sv (122)remote_copy_sync (122)scheduled_task (123)snapspace_accounting (123)startao (123)system_task (123)tune_vv (124)tune_vv_restart (124)tunevv_rollback (125)tune_sys (125)tune_sd (126)vv_copy (126)系统计划程序 (126)系统计划程序命令 (127)显示计划任务 (127)计划任务 (128)修改计划任务。

ESG 白皮书-3PAR：优化IO服务级别

简介 (3)企业级存储性能优化 (4)3PAR的Adaptive Optimization（自适应优化）和SSD（固态盘） (5)市场和用户的关联性 (5)重要事实 (8)所有商标名称都是其各自公司的财产。

本出版物中包含的信息是从Enterprise Strategy Group（ESG）认为可靠的来源获得的，但ESG不提供担保。

本出版物可能包含ESG的观点，这些观点可能随时间变化。

本出版物版权归Enterprise Strategy Group公司所有。

未经Enterprise Strategy Group公司明确同意，对本出版物的整体或部分以硬拷贝格式、电子形式或其他方式进行任何再现或重新分发给未经授权的人都会触犯美国版权法并且可能会被提起民事诉讼，或者如果适用，将被提起刑事诉讼。

如有任何问题，请联系ESG客户关系，电话：（508）482.0188。

存储的价值链常言道，一根链条的强度取决于它的最薄弱环节。

由此可以推论，向一条弱链添加一个表面上坚固的环节并不能增强其张力。

然而，一些宣传和炒作使人们误以为固态存储（SSD ）本身能够巩固每一个薄弱的存储链（无论它用于何处以及如何使用）。

向薄弱链添加基于规范的坚固环节的做法将很快成为现实，无论它是一支拔河队还是一个存储系统。

可取的做法是使用SSD 在存储环境能带来的价值来强化存储环境中现有组件。

为了获得优化结果，就要求用户切实了解并能动态将现有系统以及系统所需要的数据进行整合。

换言之，实现固态可用是第一步，从IT 和业务层面实现高价值的可用性，决定固态技术是否真正有价值。

上述几个方面的整合决定着固态技术是否能实现企业级性能优化。

其难度、怎样实现和为什么实现涉及的广度，远不止单纯添加SSD 那么简单。

本白皮书中有一部分讨论了3PAR 已经向其InServ 存储服务器添加了固态盘驱动器这一事实（本白皮书中最明显的‘事实’部分）。

然而，这不是本文的主要所在；3PAR 还利用自适应优化（本白皮书中次要明显的管理部分）增强了其系统现有的数据组织结构和布局功能。

3Par存储技术介绍

Written Data
Written Data
Written Data
Written Data
传统卷的部署需要占用较大存储资源
3PAR 自动精简按照业务需要分配资源
Purchased Physical Capacity
8 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
Exporte d
Volumes
Written Data
Written Data
Written Data
Written Data
Written Data
Written Data
Purchased Physical Capacity
Purchased Physical Capacity
9 © Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.
整体提升存储空间利用率和存储本身运行的性能
Thin Built in Zero Detect
Fast RAID 10, 50 & 60 Rapid RAID Rebuild Integrated XOR Engine
Mixed Workload
Independent Metadata and Data Processing
RAID 0, RAID 10, RAID 50 (1:2-8),

3PAR StoreServ存储产品介绍与日常管理手册

惠普3PAR StoreServ7000产品介绍及日常管理手册目录3PAR StoreServ7000产品介绍 (3)StoreServ7000体系结构 (3)功能介绍 (3)新增功能 (3)沿任何方向自由扩展 (3)提供大型企业级的功能和恢复能力 (4)易于安装、易于拥有、易于升级 (4)技术规格 (4)软件特性 (5)硬件概述 (6)StoreServ7000控制器节点（7000 node chassis） (6)M6710 2U24 SFF盘笼 (8)M6720 4U24 LFF盘笼 (8)硬盘驱动器 (9)IFC SAS端口 (9)PCM电源模块 (9)PCM电池 (10)管理服务器（Service Processor） (10)日常管理与维护 (12)StoreServ7000硬件编号 (12)节点端口位置与编号 (12)日常配置 (12)添加主机Host (12)创建CPG (13)创建VV虚拟磁盘 (14)分配VV虚拟磁盘 (16)日常维护 (19)节点LED状态指示灯 (19)SmartStart和设置向导 (19)存储开机步骤 (24)存储关机步骤 (24)存储日志Insplore收集 (24)管理机SP日志SPLOR收集 (26)特定信息CLI命令行收集 (27)常用命令CLI (28)维护向导（Guided Maintenance） (28)HP支持服务模式 (33)主动式响应--SP Call-Home (33)被动式响应—HP服务热线 (33)被动式响应—Mail存储日志 (33)知识与技术资料资源获取 (35)售后服务热线 (35)网站支持 (35)培训课程推荐 (35)《管理3Par磁盘阵列》，课程编号：HK902S (35)《3Par磁盘阵列高级管理》，课程编号：HK904S (35)3PAR StoreServ7000产品介绍StoreServ7000体系结构3PAR StoreServ7000系列存储服务是惠普公司推出的一款中端存储设备。

3PAR_Power OFF ON Procedures

3PAR InServ Power off/on ProcedurePOWER OFF PROCEDUREThe following procedure describes how to safely remove power from the storage server and the service processor.1. To Shutdown the Inserv storage server:From a CLI prompt, enter ‘shutdownsys halt’.Wait until the system has completed shutdown by observing that all controller nodes in the system have the Hot-Plug LED solid green and the Node Status LED blinking fast-green (a rate of three blinks per second)Unlock and open the rear door of the storage server.Turn all power supply rocker switches to the OFF position.2. To shutdown the Service Processor :SSH to the service processor or physically connect a maintenance PC to the Serial Connection (See Physical reference manual in the rear door for settings).Enter your login name and password(Pls contact 3PAR support if you do not know the login name/ password )In the service processor window, issue the spmaint command, if necessary.Result: The 3PAR Service Processor Menu appears.1 SP Main3PAR Service Processor MenuTransfer media: ethernet Transfer status: OkEnter Control-C at any time to abort this process1 ==> SP Control/Status2 ==> Network Configuration3 ==> InServ Configuration Management4 ==> InServ Product Maintenance5 ==> Local Notification Configuration6 ==> Site Authentication Key Manipulation7 ==> Interactive CLI for an InServ8 ==> Execute a command on a nodeX ExitSelect option 1: SP Control/StatusResult: The SP Control/Status menu appears.1 SP CONTROL3PAR Service Processor MenuTransfer media: ethernet Transfer status: OkSP Control FunctionsEnter Control-C at any time to abort this process1 ==> Display SP Version2 ==> Reboot SP3 ==> Halt SP4 ==> Stop InServ related Processes5 ==> Start InServ related Processes6 ==> File Transfer Monitor7 ==> SP File Transfer Trigger8 ==> Reset Quiesce state in Transfer process9 ==> Mount a CDROM10 ==> Unmount a CDROM11 ==> SP Date/Time maintenance12 ==> Manage NTP configuration13 ==> Display SP status14 ==> SP User Access Control15 ==> SP Process Control Parameters16 ==> Maintain SP Software17 ==> SP File maintenance18 ==> De-install SP ( Back-in-the-box )X Return to previous menuSelect option 3, Halt SP.Result: The SP SHUTDOWN window appears.1.3.1 SP SHUTDOWN3PAR Service Processor MenuConfirmationEnter Control-C at any time to abort this processHalt will power off the SP! Are you certainyou want to halt the SP now?(y or n)Type y and press Enter.Result: The following output is displayed:.Broadcast message from root (ttyS0) Fri Oct 7 12:51:33 2006...The system is going down for system halt NOW !!Verify that the blue LED on the front of the service processor is no longer illuminated.3 Remove AC to the storage server by turning off the PDU circuit breakers of ALL fourPDUs in the cabinetPOWER ON PROCEDURETurn on AC power to the cabinet(s) by turning on all the PDU circuit breakers of ALL four PDUs. Then turn on all the power switches of all the disk enclosures, controller nodes, batteries and the service processor.To verify that the system is operational, observe that all drive chassis LEDs that are illuminated SHOULD be solid green and all controller node status LEDs are blinking green once per second. (It may help best to remove all bezels to assist in visual inspections) Verify that the blue LED on the front of the service processor is illuminated.NOTESThe system takes approximately five minutes to become fully operational, providing it was gracefully shut down. If the system was powered off abruptly, powering on could take considerably longer.Gracefully means you issued shutdownsys halt and then switched the PDUs off when the nodes were halted.Abruptly means that power was simply turned off to the system, causing battery backup of the cache data to the IDE disks.Extremely abruptly means an uncontrolled shutdown, or powering off a drive chassis cabinet (causing logical disks to become degraded/failed), and then powering off the node cabinet.Considerably longer means the time varies depending on how many logical disks exist and must go through ldchk.。