HP 3PAR StoreServ Storage Concepts Guide HP 3PAR OS 3.1.3 Abstract This guide is for all levels of system and storage administrators who plan storage policies, configure storage resources, or monitor the storage usage of HP 3PAR storage systems.
© Copyright 2007, 2014 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Overview..................................................................................................7 HP 3PAR Storage Concepts and Terminology...............................................................................7 Physical Disks......................................................................................................................8 Chunklets............................................................................................................................
The Host Explorer Software Agent.............................................................................................32 6 Chunklets................................................................................................34 Overview..............................................................................................................................34 Physical Disk Chunklets............................................................................................................
11 Enhanced Storage Applications................................................................54 Overview..............................................................................................................................54 HP 3PAR mySnapshot Software................................................................................................54 HP 3PAR Dynamic Optimization Software .................................................................................
System Name..........................................................................................................78 System Location........................................................................................................78 The HP 3PAR MIB..........................................................................................................78 alertNotify Traps......................................................................................................79 14 The HP 3PAR CIM API.
1 Overview HP 3PAR Storage Concepts and Terminology HP 3PAR storage systems include the hardware components that physically store your data and the software applications that manage your data. For more information about hardware platforms, see “HP 3PAR Storage System Hardware” (page 64). For more information about system software applications and features, see “HP 3PAR Software” (page 10).
Physical Disks A physical disk is a hard drive mounted on a drive magazine located in an HP 3PAR storage system drive cage. For more information about physical disks and the HP 3PAR storage system hardware platforms, see “HP 3PAR Storage System Hardware” (page 64). Chunklets Physical disks are divided into chunklets. Each chunklet occupies contiguous space on a physical disk. On F-Class and T-Class systems, all chunklets are 256 MB. On 10000 and 7000 systems, all chunklets are 1 GB.
Thinly-provisioned Virtual Volumes A TPVV is a volume that uses LDs that belong to a CPG. TPVVs associated with the same CPG draw space from the LD pool as needed, allocating space on demand in 16 KB increments. As the volumes that draw space from the CPG require additional storage, the HP 3PAR OS automatically creates additional LDs and adds them to the pool until the CPG reaches the user-defined growth limit which restricts the CPG maximum size. The TPVV volume size limit is 16 TB.
HP 3PAR Software In addition to HP 3PAR OS software, HP offers separately licensed software suites, optional software features, and a set of host-based software applications. You can use the HP 3PAR Command Line Interface (CLI) Software and the HP 3PAR Management Console Software to view the licenses currently enabled on your system. IMPORTANT: Optional HP 3PAR software features may not currently be enabled on your system because they require additional licenses and may require separate installations.
• HP 3PAR Thin Provisioning Software: allows you to allocate virtual volumes to application servers yet provision only a fraction of the physical storage behind these volumes. By enabling a true capacity-on-demand model, a storage administrator can use HP 3PAR Thin Provisioning to create TPVVs that maximize asset use. To learn more about TPVVs, see “Virtual Volumes” (page 44). • HP 3PAR Thin Conversion Software: converts an FPVV to a TPPV.
• HP 3PAR Policy Server Software: provides flexibility and control to allow or deny outbound communications or remote service connections to and from HP 3PAR storage systems at the customer site and HP 3PAR Central. • HP 3PAR ODM 3.1 Software for IBM MPIO and Veritas VxDMP: standalone software that delivers a highly available, robust, and trouble-free multipathing solution for IBM AIX deployments.
• HP 3PAR GeoCluster Software: simplifies and automates disaster recovery, reducing administration time and improving recovery time objectives (RTOs) in Windows-based environments. • HP 3PAR Virtual Domains Software: is used for access control. Virtual domains allow you to limit the access of users to subsets of volumes and hosts in an HP storage system, and ensure that virtual volumes associated with a specific domain are not exported to hosts outside of that domain.
HP 3PAR Software Licensing Requirements The following table provides licensing information for all HP 3PAR software products and features.
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software License Required? Licensing Supported Hardware Platforms HP 3PAR EVA to Y 3PAR Online Import Software Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR StoreServ 10000 Storage OS Software Suite; also available standalone HP 3PAR StoreServ 7000 Storage, HP 3PAR StoreServ 10000 Storage HP 3PAR Management Console Software N Part of the HP 3PAR OS HP 3PAR F-Class, HP 3
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software 16 License Required? Licensing Supported Hardware Platforms HP 3PAR Dynamic Optimization Software Y Licensed as part of the HP 3PAR StoreServ 7000 Storage Data Optimization Suite v2, the HP 3PAR StoreServ 10000 Storage Data Optimization Suite v2, and the HP 3PAR Optimization Suite; also available standalone HP 3PAR Adaptive Optimization Software Y Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software License Required? Licensing Supported Hardware Platforms VMware; also available standalone for other hardware platforms HP 3PAR VASA Provider Software Y Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ VMware and the HP 3PAR StoreServ 7000 Storage 10000 Application Suite for VMware; also available standa
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software 18 License Required? Licensing Supported Hardware Platforms HP 3PAR NULL INF N for SCSI Enclosure Device Available standalone HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR Data Encryption Licensed as part of the HP 3PAR StoreServ 7000 OS, the HP 3PAR StoreServ 7450 OS, and the HP 3PAR StoreServ 10000 OS HP 3PAR StoreServ 7000, HP 3PAR StoreServ
2 HP 3PAR Storage System Users User Accounts To access an HP 3PAR storage system, you must have a user account. Each HP 3PAR OS user is assigned a role, and each role is assigned a set of rights. The roles and rights assigned to the user determine which tasks the user can perform with a system. Assign roles to users based on the tasks you intend the users to perform. Eight roles are defined in the HP 3PAR OS. See Table 2 (page 19) for a description of each role.
Table 2 HP 3PAR OS User Roles (continued) User Roles Rights Assigned to Roles 3PAR AO Rights are limited to internal use by HP for Adaptive Optimization operations. 3PAR RM Rights are limited to internal use by HP for Recovery Manager operations. Local User Authentication and Authorization Users accessing the HP 3PAR storage system with the HP 3PAR CLI client or Secure Shell (SSH) connections are authenticated and authorized directly on the system. These users are referred to as local users.
3 Lightweight Directory Access Protocol Overview The LDAP is a standard protocol for communication between LDAP clients and LDAP directory servers. Data is stored as a directory hierarchy by the server, and clients add, modify, search, or remove the data. The data can be organized by using standard schemas understood by clients and servers from different vendors or by using an application-specific schema that is used only by a particular vendor or application.
see “HP 3PAR Storage System Users” (page 19). LDAP users can access the system using the same methods as local users, although some user account creation and modification operations are unavailable. Do not create local and LDAP users with the same user name. If local and LDAP users have the same user name, it can cause confusion about where access is controlled. For instructions on using LDAP with the storage system, see the HP 3PAR Command Line Interface Administrator’s Manual.
• If virtual domains are in use, the user’s group is mapped to a domain. • The user is assigned a system user role and a domain, if domains are in use. LDAP Authentication Users are authenticated with the LDAP server by using a bind operation. The bind operation authenticates the HP 3PAR OS LDAP client to the LDAP server. This authentication process is required for all systems that use LDAP, including systems using domains. Several binding mechanisms are supported by the HP 3PAR OS LDAP client.
is made for group A with the super-map parameter, a user who belongs to group A is authorized with Super rights to the system. With this process, a user can be authenticated, but that user is not authorized if no group membership exists. In this case, the user is subsequently denied access to the system. Authorization on Systems Using Virtual Domains As discussed in “LDAP Authorization” (page 23), a user’s group association determines that user’s role within the system.
4 HP 3PAR Virtual Domains Overview To set up the HP 3PAR storage system, the system administrator creates and assigns user roles and rights in the system. You can create, modify, and remove a user’s access to HP 3PAR Virtual Domains Software in the system with both the HP 3PAR CLI and the HP 3PAR Management Console. See the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on performing these tasks.
Domain Type The first tier of access control is the domain to which a subset of a system’s objects belong. The objects can be assigned to a specific domain, or have no domain association. • The no domain contains objects that do not belong to any specified domains. For example, objects in an existing system that did not previously use domains do not belong to any domain. • specified domains are created by the domain administrator and contain objects specific to that domain.
An HP 3PAR CLI user’s default domain is the domain that the user accesses at the start of each CLI session. For example, if you have Edit rights to domains A and B, and your default domain has been set to domain A, each time you start a new CLI session, you view and work with only objects in domain A. The user’s default domain can be set or reset at any time by the administrator. If you are using the HP 3PAR Management Console, the user selects which domain to access.
5 Ports and Hosts Overview The HP 3PAR storage system sees a host as a set of initiator port World Wide Names (WWNs) or iSCSI names. Hosts that are physically connected to ports on the system are automatically detected. The FC port WWNs and iSCSI port iSCSI names are displayed by the user interfaces. You can also add new WWNs or iSCSI names for unestablished host paths and assign them to a host before they are physically connected.
• Gigabit Ethernet ports Systems use Gigabit Ethernet ports to enable the Remote Copy over Internet Protocol (RCIP) solution and to connect the primary and secondary systems in the Remote Copy pair. For information about Remote Copy, see the HP 3PAR Remote Copy Software User Guide. • SAS ports Systems use SAS ports to connect controller nodes to drive enclosures. SAS ports are supported only on HP 3PAR StoreServ 7000 Storage systems.
◦ StoreServ 10000 ports are numbered from bottom to top in a node in the lower chassis. In the upper chassis, ports are numbered from top to bottom. ◦ StoreServ 7000 ports are numbered 1–4 from left to right in a node in the lower node enclosure. In the upper node enclosure, slots are numbered 1–4 from right to left. For information about controller nodes, see “HP 3PAR Storage System Hardware” (page 64).
create separate hosts on the system and assign each WWN or iSCSI name to its own host. Use the HP 3PAR CLI or the HP 3PAR Management Console to create, modify, and remove hosts. Hosts can be grouped into autonomic groups that can be managed as a single host. If you have a group of hosts that require the same administrative procedures, it is easier to group those hosts into an autonomic group and mange them together.
Table 3 Host Personas (continued) Persona Number Persona Name Host Operating System Additional Capabilities 8 AIX-Legacy AIX NACA 9 Egenera Egenera, NetApp SoftInq 10 NetApp ONTAP Data ONTAP SoftInq 11 VMware Linux and Windows SubLun, ALUA 12 OpenVMS OpenVMS UARepLun, RTPG, SESLun, LunoSCC 13 HPUX HP-UX UARepLun, VolSetAddr, SESLun, ALUA, LunoSCC 15 WindowsServer Windows UARepLun, SESLun, ALUA, WSC NOTE: Only the Generic, Generic-ALUA, and Generic-Legacy personas are supporte
You can install the Host Explorer agent from the HP 3PAR Host Explorer CD. For instructions on installing and using the Host Explorer agent, see the HP 3PAR Host Explorer User’s Guide. For a list of supported host operating systems, go to the SPOCK website: http://www.hp.
6 Chunklets Overview Physical disks are divided into chunklets. When a physical disk is admitted to the system, it is divided into chunklets that become available to the system. Some chunklets are used by LDs, and other chunklets are designated as spares to hold relocated data during a disk failure or during maintenance procedures. Creating, moving, and removing chunklets and spares can only be performed with the HP 3PAR CLI.
NOTE: Local chunklets are chunklets on disks whose primary path is connected to a node that owns the LD that contains the chunklets being relocated. • If the system uses up its free or spare chunklets for relocation, an alert is generated. • When the spare and free chunklets are used up, automatic relocation no longer occurs. In most cases, some data redundancy is lost. The system also generates an alert.
7 LDs Overview An LD is a collection of physical disk chunklets arranged as rows of RAID sets. Each RAID set is made up of chunklets from different physical disks. LDs are pooled together in CPGs, which allocate space to virtual volumes. Creating CPGs maps out the data layout parameters for creating LDs. LDs are created automatically by the system when virtual volumes are created from CPGs.
failures. When the destination LDs become available again, the system automatically writes the preserved data from the preserved data LDs to the destination LDs. • Administration volume LDs provide storage space for the admin volume, a single volume created on each system during installation. The admin volume is used to store system administrative data such as the system event log.
Figure 6 Data Striped Across RAID 1 Sets on a RAID 10 LD RAID 5 and RAID 50 On a RAID 50 LD, data is striped across rows of RAID 5 sets. A RAID 5 set, or parity set, must contain at least three chunklets. A RAID 5 set with three chunklets has a total of two chunklets of space for data and one chunklet of space for parity. RAID 5 set sizes with between 3 and 9 chunklets are supported. The data and parity steps are striped across each chunklet in the set.
Figure 7 Data Striped Across RAID 5 Sets on a RAID 50 LD RAID MP or RAID 6 On a RAID MP or RAID 6 LD, data is striped across rows of RAID MP sets. A RAID MP set, or double-parity set, must contain at least 8 chunklets. A RAID MP set with eight chunklets has a total of six chunklets of space for data and two chunklets of space for parity. RAID MP set sizes of eight and 16 chunklets are supported. The data and parity steps are striped across each chunklet in the set.
Figure 8 Data Striped Across RAID MP Sets on a RAID MP LD LD Size and RAID Types On F-Class and T-Class systems all chunklets are 256 MB. On StoreServ 10000 and StoreServ 7000 systems all chunklets are 1 GB. All systems round up so that the LD size is divisible by the size of one chunklet, either 1 GB or 256 MB. The total size of the LD is determined by the number of data chunklets in the RAID set. • A RAID 0 or RAID 1 LD must contain at least one chunklet.
8 Common Provisioning Groups Overview A CPG creates a virtual pool of LDs that allows virtual volumes to share the CPG's resources and allocates space on demand. You can create FPVVs and TPVVs that draw space from the CPG's LD pool. CPGs enable fine-grained, shared access to pooled logical capacity. Instead of dedicating LDs to volumes, the CPG allows multiple volumes to share the buffer pool of LDs.
Table 4 Default and Minimum Growth Increments Number of nodes Default Minimum 2 32 GB 8 GB 4 64 GB 16 GB 6 96 GB 24 GB 8 128 GB 32 GB A larger growth increment is sometimes desirable; however, a smaller growth increment can prevent the CPG from automatically allocating too much space. The optimal growth increment depends on several factors: • Total available space on your system. • Nature of the data running on the system. • Number of CPGs in the system.
controller node 0, when the virtual volumes that draw from a CPG have filled up all space available to that CPG based on its LD parameters, the following will happen: • New writes to any TPVVs that are mapped to that CPG will return write failures. • Snapshot volumes mapped to the CPG may become invalid (stale), subject to the virtual copy policy associated with the base volume. For base volumes with a no stale snapshots virtual copy policy, new writes to the base volume will result in write failures.
9 Virtual Volumes Overview Volumes draw their resources from CPGs, and volumes are exported as LUNs to hosts. Virtual volumes are the only data layer visible to hosts. You can create physical copies or virtual copy snapshots of virtual volumes for use if the original base volume becomes unavailable. Before creating virtual volumes, you must first create CPGs to allocate space to the virtual volumes. For information about CPGs, see “Common Provisioning Groups” (page 41).
on different CPGs, the user space remains available to the host if the CPG containing the snapshot space becomes full. To save time, you can create many identical virtual volumes at one time. If your system is accessible from an OpenStack cloud, you may see volumes with prefixes indicating that the volumes were created through the OpenStack cloud. Volumes created through the OpenStack cloud use the OpenStack Volume (OSV) and OpenStack Snapshot (OSS) prefixes.
TPVV Warnings and Limits The TPVV volume size limit is 16 TB. When you create a TPVV, you can set an allocation warning threshold and an allocation limit threshold. • Allocation warning threshold: For volumes capable of allocating space on demand, the user-defined threshold at which the system generates an alert. This threshold is a percentage of the volume's virtual size, the size that the volume presents to the host.
allow for continued growth of the volume. When a TPVV reaches approximately 80% of capacity, the incremental benefit of capacity savings versus accelerating performance is weighted towards performance. In addition, converting volumes from thinly-provisioned to fully-provisioned can free up thinly-provisioned capacity for other TPVVs. Similarly, if an FPVV storage space is largely unused, you might choose to convert it to a TPVV to save storage space.
http://www.hp.com/storage/spock Virtual copies can be created and managed in groups to reduce the number of management tasks. You can create a consistent group of virtual copies from a list of virtual volumes, and group virtual copies into autonomic groups that are managed as a single virtual copy. NOTE: Virtual copies are consistent at the virtual volume level, but not at the host file system or application level.
Copy-on-Write Function When a virtual volume or snapshot’s source volume is written to, the copy-on-write function preserves the data that is to be overwritten. The data is copied to the snapshot space associated with the original virtual volume before the write operation is completed, and a pointer in the administration space points to the copied data. See Figure 11 (page 49) for an example of a sequence of snapshots.
• A maximum of 500 virtual copies can be made from one base volume. • A virtual volume cannot be deleted if a child copy of it exists. For example, S1 cannot be removed unless S1_0, S1_0_0, and S1_0_1 are deleted first. Copy-of and Parent Relationships In the example in Figure 11 (page 49), there are two different tree structures: the solid arrows show the copy-of relationships, and the dashed arrows show the parent relationship. For example, S0 is a read-only copy of BaseVV, and S1 is the parent of S0.
exported. A VLUN template enables the export of a virtual volume as a VLUN to hosts. Those volume exports, which are seen as LUNs by the hosts, are active VLUNs. A VLUN template can be one of the following types: Host sees allows only a specific host to see a volume. Host set allows any host that is a member of the host set to see a volume. Port presents allows any host on a specific port to see the volume. Matched set allows only a specific host on a specific port to see the volume.
10 Reclaiming Unused Space Overview The HP 3PAR OS space consolidation features allow you to change the way that virtual volumes are mapped to LDs in a CPG. Moving virtual volume regions from one LD to another enables you to compact LDs, and free up disk space so that it can be reclaimed for use by the system. For more information about virtual volumes, see “Virtual Volumes” (page 44). Mapping is the relationship of LD regions to the virtual volume regions.
Reclaiming Unmapped LD Space from Volumes When multiple identical virtual volumes are created as a result of a single volume creation operation, the underlying LDs that support those volumes are shared by the volume group. If several of the members of that volume group are later deleted, the underlying LDs may become less efficient in the usage of space. One or more LDs shared by the volume group may have only a small portion of their regions mapped to existing virtual volumes.
11 Enhanced Storage Applications Overview HP offers several enhanced storage features for managing data and improving system performance. Optional features require you to purchase a separate license. You can use the HP 3PAR CLI and the HP 3PAR Management Console to view the licenses that are currently enabled on your systems. For a list of default HP 3PAR OS Software Suite features and optional features, see “HP 3PAR Software” (page 10).
capability of TPVVs reduces the need for Dynamic Optimization to change the layout of TPVVs after adding disks. • Volume RAID level changes. Since different RAID levels have varying capacity requirements and offer different degrees of performance, you may want to convert volumes from one RAID type to another when system requirements change. • Volume fault-tolerance changes.
System Tuner allows you to: • Perform physical disk performance tuning on an entire system or on a specified subset of disks. • Set performance thresholds for physical disk tuning. • Identify and relocate under-performing chunklets. System Tuner tasks can only be performed with the HP 3PAR CLI. See the HP 3PAR Command Line Interface Administrator’s Manual for instructions on performing these tasks.
7000 Storage systems automatically detect the zeros and do not allocate space for them in the physical copy. The result is a TPVV that is much smaller than the original volume. Thin conversion tasks can be performed with the HP 3PAR CLI and the HP 3PAR Management Console. See the HP 3PAR Command Line Interface Administrator's Manual and the HP 3PAR Management Console Online Help for instructions on how to perform these tasks.
moving frequently accessed data to the higher-performance tier—for example, RAID 1 using solid state disks, or SSDs—while infrequently accessed data is moved to the lower-cost tier—for example, RAID 6 on near line (NL) disks. Active use of AO requires an HP Adaptive Optimization license. Contact your HP representative for information. AO uses HP System Reporter statistics gathered from logical disks and physical disks to relocate customer data on physical volumes in an optimal way.
HP 3PAR Peer Motion Software HP 3PAR Peer Motion Software controls the migration of a host and its data from a source system to a destination system with as little disruption to the host as possible. With peer motion, you can copy the virtual volumes and system configuration information to a new system with no changes to host configurations, no loss of access by a host to its data in an online migration, and only a minimal outage during migration.
takes about 30 seconds, and booting takes an additional 5 seconds. Rekeying under a light load takes about 15 seconds. CAUTION: Keep the encryption key file and password safe. If you lose the encryption key and the HP 3PAR StoreServ system is still functioning, you can always perform another backup of the encryption key file.
random, and transactional, among others), with different I/O packet sizes on a single HP 3PAR storage system. The use of QoS rules stabilizes performance in a multi-tenant environment. Virtual Volume Sets QoS rules operate on sets of VVs called VVsets. A VVset is an autonomic group object that is a collection of virtual volumes. VVsets help to simplify administration of volumes and reduce human error. An operation such as exporting a VVset to a host will export all member volumes of the VVset.
If the current limit for IOPS or bandwidth for a particular VVset has been reached, HP 3PAR Priority Optimization delays SCSI I/O request responses for the volumes contained in that VVset. These delayed I/O requests are pushed onto an outstanding I/O queue for the VV(s) in the VVset experiencing the limit breach. Every QoS rule maintains its own queue for delayed I/Os. These queues are constructed inside each HP 3PAR StoreServ controller node that receives an I/O request that needs to be delayed.
Overlapping QoS Rules A VV can be a member of multiple VVsets, each of which can have a QoS rule defined. In such a case, the I/O to and from volumes in the VVset is governed by multiple, possibly overlapping rules. All active rules for a particular VVset are combined using wired-OR logic: the QoS limit that is reached first takes precedence. A QoS rule can be created on a VVset that has none, or not all, of its VVs exported to a host.
12 HP 3PAR Storage System Hardware Overview HP 3PAR storage systems are available in a variety of hardware configurations. Different models address different levels of storage capacity and anticipated growth requirements. All models use the HP 3PAR OS. Hardware monitoring and configuration tasks can be performed with both the HP 3PAR CLI and the HP 3PAR Management Console.
Table 5 HP 3PAR StoreServ 10000 Front View System Components Item Description 1 HP 3PAR StoreServ 10000 Storage system (V400 model) 2 HP 3PAR StoreServ 10000 Storage system (V800 model) 3 Drive cage FC-AL modules 4 Cooling fans 5 Battery backup units 6 Service processor 7 Drive chassis 8 Leveling foot Figure 14 HP 3PAR StoreServ 10000 Storage System Rear View Table 6 HP 3PAR StoreServ 10000 Storage System Rear View System Components Item Description 1 Drive chassis power supply 2 Pow
Physical Disks A physical disk is a hard drive mounted on a drive magazine or module located in drive cages in HP 3PAR storage systems. There are three types of physical disks: FC, NL, and SSD. In DC4 drive cages, each drive magazine holds four disks numbered 0 through 3 from the rear to the front of the magazine. The DC4 drive cages contain a maximum of ten drive magazines for a maximum of 40 physical disks in each drive cage. See Figure 15 (page 66). Figure 15 DC4 Drive Magazine with Physical Disks 1. 2.
Drive Cage/Enclosure Models • StoreServ 7000 Storage systems contain either the M6710 (2U24) drive enclosure or the M6720 (4U24) drive enclosure. • T-Class and StoreServ 10000 Storage systems contain DC4 drive cages. The DC4 is a 40 disk, 4 Gbps drive cage. • F-Class systems contain only DC3 drive cages. The DC3 is a 16 disk, 4 Gbps drive cage. HP M6710 Drive Enclosure The HP M6710 Drive Enclosure (2U24) holds up to 24, 2.
FC cables connect the ports in the drive cage to the ports on the controller nodes. Each cable is labeled to indicate the ports it uses. NOTE: Daisy chaining is not supported for the DC4 drive cages.
In the DC3 drive cage, two FC-ALs, each providing four small form-factor pluggable modules to service the drive cage. Figure 21 (page 69) shows the rear view of a DC3 drive cage. • FC-AL B has four ports, labeled Port B0 through Port B3, from bottom to top. • FC-AL A has four ports, labeled Port A0 through Port A3, from top to bottom. FC cables connect the ports in the drive cage to the ports on the controller nodes. Each cable is labeled to indicate the ports it uses.
Table 9 System Models and Number of Controller Nodes Storage System Model Number of Controller Nodes StoreServ 7000 2 or 4 StoreServ 10000 2, 4, 6, or 8 T400 2 or 4 T800 2, 4, 6, or 8 F200 2 F400 4 Port Numbering The number of host ports each storage system model can accommodate is summarized in Table 10 (page 70).
Figure 22 HP 3PAR StoreServ 7200 Storage System Figure 23 HP 3PAR StoreServ 7400 Storage System (4 Nodes) HP 3PAR StoreServ 10000 Controller Node Numbering The HP 3PAR StoreServ 10000 system may contain two, four, six or eight controller nodes per system configuration. The controller node chassis is located at the rear of the storage cabinet. From the rear of the storage cabinet, component numbering starts with zero (0) at the bottom-left corner and advances right and upward.
Figure 24 HP 3PAR StoreServ 10000 Controller Node Numbering T-Class Controller Node Numbering T-Class systems contain two, four, six, or eight controller nodes per system and only use T-Class controller nodes. Controller nodes are loaded into the system backplane enclosure from bottom to top. For a T800 storage system with only two controller nodes installed, those controller nodes occupy the lowest 4U of the backplane and are numbered node 6 and node 7.
Figure 25 T-Class Controller Node Numbering F-Class Controller Node Numbering The F-Class systems contains two or four nodes per system. Controller nodes are numbered from top to bottom node 0 and node 1 for a two node system, and node 0–3 for a four node system. See Figure 26 (page 74) for an example of controller node numbering in an F-Class system.
Figure 26 F-Class Controller Node Numbering 74 HP 3PAR Storage System Hardware
13 HP 3PAR SNMP Infrastructure Overview In addition to managing the system with the HP 3PAR Management Console and the HP 3PAR CLI, the HP 3PAR OS includes a Simple Network Management Protocol (SNMP) agent that allows you to perform some basic management functions by running network management software on a management station. These SNMP management functions require that you have SNMP management software not provided by HP.
Standard Compliance The HP 3PAR SNMP agent supports the following standards: • SNMPv2c This version refers to a widely-used administrative framework for SNMPv2, also known as “community-based SNMPv2.” Although this version includes SNMPv2 enhancements, such as notification and GETBULK requests, it relies on the SNMPv1 community concept for security. • Structure of Management Interface-v2 (SMIv2) This standard specifies the format of the MIB. The HP 3PAR MIB definition uses SMIv2 conventions.
Table 11 MIB-II Objects Supported by the SNMP Agent (continued) Object Descriptor Description Access sysName Name of the system. This helps to Read-only identify the storage system. This name cannot be set by using SNMP. sysLocation User-defined system location. For example: Building 1, room 4, rack 3. Read/write Exposed Objects The 3PAR SNMP agent supports MIB-II system group objects. This section describes each of those objects in detail.
Default value: Please provide contact information such as name, phone number, and e-mail address Description: Specifies the name of a person or group responsible for maintaining the storage. This value can be changed by the manager at any time. System Name Access: Read-only MIB definition: sysName Data type: Display string (max. 255 characters) Default value: None Description: Indicates the system name, which is set during initialization and setup of the system.
Table 12 Contents of the alertNotify trap (continued) Object Descriptor Description Access messageCode Code that identifies the specific type of alert or alert state change. For Read-only example, the message code for the alert state change is 1245186. For information about system alerts, go to http://www.hp.com/support/hpgt/ 3par and select your server platform. state Current alert state, which is an integer between 0 and 5. See the HP 3PAR MIB for definitions for each integer.
The following information describes these alert status change events: Message Code 1245186 Severity Info Type Change in alert state Alert String Alert changed from state to Operator Action The alert has changed state. This can be used to track the state of the existing alerts in a system.
14 The HP 3PAR CIM API Overview This chapter describes the HP 3PAR Common Information Model Application Programming Interface (CIM API), the HP industry-standard API based on the SNIA Storage Management Initiative Specification (SMI-S). For detailed information about the HP 3PAR CIM API, see the HP 3PAR CIM API Programming Reference. About SMI-S SMI-S enables management of SANs in a heterogeneous multi-vendor environment.
For more information regarding WBEM and CIM, see the DMTF web site: http://www.dmtf.org HP 3PAR CIM Support The following sections provide information about the HP 3PAR CIM API provided with HP 3PAR OS Version 3.1.3. Standard Compliance • The HP 3PAR CIM Server supports SMI-S version 1.1.0. • The HP 3PAR CIM API passes SNIA-CTP conformance. For additional information, see http:// www.snia.org. SMI-S Profiles SMI-S defines profiles that are used to manage the elements of a SAN.
15 Comparing HP 3PAR to EVA Terms This comparison of EVA and HP 3PAR terms is intended to be a general guide to similar concepts. These terms do not necessarily represent exactly the same entities with all the same properties in both product lines. For detailed descriptions of each term, see the EVA or HP 3PAR glossary.
16 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.
For information about: See: Migrating data from one HP 3PAR storage system to another HP 3PAR-to-3PAR Storage Peer Motion Guide Configuring the Secure Service Custodian server in order to monitor and control HP 3PAR storage systems HP 3PAR Secure Service Custodian Configuration Utility Reference Using the CLI to configure and manage HP 3PAR Remote Copy HP 3PAR Remote Copy Software User’s Guide Updating HP 3PAR operating systems HP 3PAR Upgrade Pre-Planning Guide Identifying storage system components
For information about: See: Planning for HP 3PAR storage system setup Hardware specifications, installation considerations, power requirements, networking options, and cabling information for HP 3PAR storage systems HP 3PAR 7200, 7400, and 7450 storage systems HP 3PAR StoreServ 7000 Storage Site Planning Manual HP 3PAR StoreServ 7450 Storage Site Planning Manual HP 3PAR 10000 storage systems HP 3PAR StoreServ 10000 Storage Physical Planning Manual HP 3PAR StoreServ 10000 Storage Third-Party Rack Physic
Typographic conventions Table 14 Document conventions Convention Element Bold text • Keys that you press • Text you typed into a GUI element, such as a text box • GUI elements that you click or select, such as menu items, buttons, and so on Monospace text • File and directory names • System output • Code • Commands, their arguments, and argument values • Code variables • Command variables Bold monospace text • Commands you enter into a command line interface • Syste
17 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
Glossary Access Guard A software component that provides volume security at logical and physical levels. Access Guard is part of the HP 3PAR OS Software Suite. active host A host that is connected to a system port and recognized by the HP 3PAR OS. active VLUN The pairing of a virtual volume and a LUN so the host can access its virtual volume and I/O writes can be saved to the virtual volume. The VLUN parameters determine whether a virtual volume is expressed as an active VLUN.
CMP Cache Memory Page. A 16 KB block of control cache memory where I/O requests are stored. component indicator HP 3PAR Management Console alert pane icon that represents a logical or physical system component. control cache Memory modules that support the microprocessors located in a controller node. control cache DIMM A single control cache memory module.
drive enclosure A component used for housing drive cages in the front of the enclosure and nodes and I/O modules in the rear of the enclosure. drive magazine An electronic circuit board mounted on a mechanical structure that is inserted into a drive bay in a drive cage. A drive magazine holds up to four physical disks. drive magazine filler panel The panel used to seal off an empty drive bay. All drive bays in a drive cage must be sealed for EMI and airflow considerations.
HP 3PAR System Tuner Software The utility that enables the system to reallocate space usage in order to take advantage of additional resources, such as added hardware or updated CPGs. The System Tuner identifies underused chunklets and overused volumes, and balances the usage. HP 3PAR Thin Provisioning Software Software that enables you to create a virtual volume that allocates resources from the CPG on demand and in small increments.
no stale snapshots Virtual copy policy that prevents changes being written to a base volume when it does not have enough snapshot data or administration space to prevent virtual copies from becoming invalid, or stale, as a result. node cabinet A cabinet that houses the system backplane and controller nodes. original parent base volume The original base volume from which a series of virtual or physical copies has been created.
RAID set A grouping of mirrored or parity-protected chunklets. RAID type RAID 0, RAID 10 (1), RAID 50 (5), and RAID MP (6) are all supported RAID types; however, not all RAID types may be available on your system. RCFC Remote Copy over Fibre Channel. The use of Remote Copy with two systems that are connected via Fibre Channel ports. RCIP Remote Copy over IP. The use of Remote Copy with two systems that are connected via Ethernet ports. region A subdivision of a logical disk or virtual volume.
SPOCC Service Processor Onsite Customer Care. A suite of service tools applications with a web-based graphical user interface that is used to support the HP 3PAR storage system and its Service Processor. SPOCK Single Point of Connectivity Knowledge website. SPOCK is the primary portal used to obtain detailed information about supported HP storage product configurations.
virtual volume A virtual storage unit created by mapping data from one or more logical disks. virtual volume backup nodes The controller nodes that take over for the virtual volume master node if the virtual volume master node fails. virtual volume master node The controller node that is responsible for a virtual volume from its creation to its deletion. When the system builds a virtual volume, the system begins with the logical disk connected to the master node.
Index A Active Directory Kerberos server, 21 Active Directory LDAP, 21 Active Directory LDAP server, 21 adaptive optimization, 57 admin volume, 45 alertNotify, 79 alerts when spare and free chunklets are used up, 34 allocation limit, 46 allocation warning, 46 authentication, 20, 21 LDAP, 23 authorization LDAP, 23 B base volumes retrieval time affected by distance from, 50 virtual copy tree relationships, 49 C chunklets, 34 free, defined, 34 physical disk, 34 CIM, 81 CIM API, 81 commands setrcopy switchove
H hardware HP 3PAR storage system, 64 host personas, 31 host sees VLUN template, 51 host set VLUN template, 51 hosts active, 30 adding and removing, 30 inactive, 30 HP 3PAR Access Guard Software, 10 HP 3PAR Adaptive Optimization Software, 12 HP 3PAR Autonomic Groups Software, 11 HP 3PAR Autonomic Rebalance Software, 10 HP 3PAR Command Line Interface Software, 11 HP 3PAR Data Encryption Software, 59 HP 3PAR Dynamic Optimization Software, 12, 54 HP 3PAR EVA to 3PAR Online Import Software, 11 HP 3PAR Full Copy
M management information base see MIB mapping overview, 52 mapping parameters, 23 matched set VLUN template, 51 MIB HP, 78 supported, 76 modes system controller, 30 N naming conventions, virtual volumes, 49 O objects MIB-II, 77 OpenLDAP, 21 optimization adaptive , 57 priority, 60 P peer motion, 59 performance consequences of virtual volumes, 50 permissions (roles), 19 persona, 31 legacy host, 32 physical copy, 47 creating, 56 definition, 9 physical disk, 66 PLAIN binding, 23 PLAIN, 23 port location forma
mapping, definition, 52 naming conventions, 49 parent relationships, 50 performance consequences, 50 performance consequences of, 50 VLUN template, 50 volume types CPG, 43 W warnings CPG, 41 WBEM, 81 Web-Based Enterprise Management see WBEM World Wide Names see WWN WWNs, 28 100 Index
