HP 3PAR StoreServ Storage Concepts Guide HP 3PAR OS 3.1.2 MU2 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, 2013 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.............................................................................................31 6 Chunklets................................................................................................32 Overview..............................................................................................................................32 Physical Disk Chunklets............................................................................................................
11 Enhanced Storage Applications................................................................53 Overview..............................................................................................................................53 HP 3PAR mySnapshot Software................................................................................................53 HP 3PAR Dynamic Optimization Software .................................................................................
About the WBEM Initiative.......................................................................................................78 HP 3PAR CIM Support............................................................................................................79 Standard Compliance.........................................................................................................79 SMI-S Profiles..............................................................................................................
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 61). For more information about system software applications and features, see “HP 3PAR Software” (page 9).
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 61). 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.
TPVV volume size limit is 16 TB. For more information about TPVVs, see “Thinly-Provisioned Virtual Volumes” (page 43). NOTE: Creating TPVVs requires the HP 3PAR Thin Provisioning Software license. For more information, see “HP 3PAR Software” (page 9). Physical Copies A physical copy is a full copy of a volume. The data in a physical copy is static; it is not updated with subsequent changes to the parent volume. The parent volume is the original volume that is copied to the destination volume.
IMPORTANT: Optional HP 3PAR software features may not currently be enabled on your system because they require additional licenses and may require separate installations. When features are not available on your system because they are not licensed for use, screens and functionality relating to those features may appear grayed-out or be otherwise inaccessible in the HP 3PAR Management Console and HP 3PAR CLI.
3PAR StoreServ 10000, or HP 3PAR StoreServ 7000 storage system, an HP 3PAR Thin Provisioning license, and an HP 3PAR Thin Conversion license. To learn more about HP 3PAR thin conversion, see “Enhanced Storage Applications” (page 53). • HP 3PAR Thin Persistence Software: keeps TPVVs and read/write snapshots of TPVVs small by detecting pages of zeros during data transfers and not allocating space for the zeros.
• HP 3PAR ODM Software for Veritas VxVM: an application for customers using Veritas VxVM/DMP with HP 3PAR storage devices. It provides HP 3PAR device definitions and a message catalog. • HP 3PAR NULL INF for SCSI Enclosure Device: HP 3PAR NULL driver for Windows Server 2003 is used to add WHQL signature for Windows Server 2003 environments so that the storage system can be recognized without triggering an “unknown device” message.
• HP 3PAR System Reporter Software: allows you to monitor performance, create charge back reports, and plan storage resources for systems using either a standard Web browser or the HP 3PAR System Reporter Excel client. • HP 3PARInfo Software: a command line utility that provides useful information on the volume mapping between the host and the array. • HP 3PAR Management Plug-in for VMware: a Web application that is deployed as a VI Client plug-in.
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms HP 3PAR Software 14 License Required? Licensing Supported Hardware Platforms HP 3PAR Access Guard Software Y Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR Full Copy Software Y Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR Rapid Provisioning Sof
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software License Required? Licensing Supported Hardware Platforms StoreServ 10000 Storage OS Software Suite; also available standalone HP 3PAR Management Console Software N Part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR Host Explorer Software N Licensed as part of the HP 3PAR StoreServ 7000 Storage OS Software Suite and the HP 3PAR
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software License Required? Licensing Supported Hardware Platforms and the HP 3PAR Optimization Suite; also available standalone 16 HP 3PAR Peer Motion Software Y Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR StoreServ 7000 Data Optimization StoreServ 10000 Storage, HP 3PAR StoreServ Suite v2 and the HP 3PAR StoreServ 7000 Storage 10000 Data Optimization Suite v2; also available standalo
Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) HP 3PAR Software HP 3PAR Host Explorer for VMware vSphere License Required? Licensing Supported Hardware Platforms 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 Exchange; also available standalone for other hardware platforms HP 3PAR Recovery
2 HP 3PAR Storage System Users User Accounts In order 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 18) 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 Lightweight Directory Access Protocol (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 using standard schemas understood by clients and servers from different vendors or by an application-specific schema used only by a particular vendor or application.
over the user’s LDAP authentication data. User names not associated with local user names are authenticated using LDAP data. Additionally for local users, during authentication, the password supplied by the user must match the password assigned when that user was initially created or modified. The rights assigned to the user during authorization are the same rights associated with the user role assigned when that user was initially created or modified.
LDAP Authentication and Authorization As stated earlier, the user’s user name is first checked against the authentication data stored on the local system. If the user’s name is not found, the LDAP authentication and authorization process proceeds as follows: • The user’s user name and password are used to authenticate with the LDAP server. • The user’s group memberships are determined with the data on the LDAP server.
Each group to which a user is a member is compared against the mapping parameters. Mapping occurs sequentially with a group first compared to the super-map parameter. If no match is made, the group is then compared with the service-map parameter, and so on. For example, if a match is made for group A with the super-map parameter, the user belonging to group A is authorized with Super rights to the system. With this process, a user can be authenticated, but not authorized if no group membership exists.
4 HP 3PAR Virtual Domains Overview When initially setting up the HP 3PAR storage system, the system administrator creates and assigns users with 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 Command Line Interface (CLI) and the HP 3PAR Management Console.
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 domains. • 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 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 will view and work with only objects in Domain A. The user’s default domain can be set and reset at any time by the administrator.
5 Ports and Hosts Overview The HP 3PAR storage system sees a host as a set of initiator port WWNs (World Wide Names) or iSCSI Names. Hosts that are physically connected to ports on the system are automatically detected. The Fibre Channel 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 IP (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’s Guide. • Serial Attached SCSI (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.
For information about controller nodes, see “HP 3PAR Storage System Hardware” (page 61). For more information about physical port and HBA locations, see the Physical Planning Manual for your system model. Port Target, Initiator, and Peer Modes The system controller node ports operate in different modes. Depending on the type of port, the port may operate in target, initiator, or peer mode.
removing hosts, see the HP 3PAR Command Line Interface Administrator’s Manual and HP 3PAR Management Console Online Help. Managing Host Personas Host personas are a set of behaviors that permit hosts connected to FC or iSCSI ports on the system to deviate from the default host behavior. By assigning a persona to a host, multiple host types that require distinct customized responses can share a single system port.
Table 3 Host Personas (continued) Persona Number Persona Name Host Operating System Additional Capabilities 10 NetApp ONTAP Data ONTAP SoftInq 11 VMware Linux and Windows SubLun, ALUA NOTE: • Only the Generic, Generic-ALUA, and Generic-Legacy personas are supported for iSCSI connections. • The NetApp host operating system requires unique WWNs for hosts in an FC fabric. • A host device must use either iSCSI or Fibre Channel connections. Mixed ports on a single device is not supported.
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 logical disks 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 Command Line Interface (CLI).
• For automatic relocations, the system uses up a maximum of one disk worth of chunklets per system node. • When selecting a target chunklet for relocation, the system attempts to identify a local spare chunklet, a local free chunklet, a remote spare chunklet, and then finally a remote free chunklet. NOTE: Local chunklets are chunklets on disks whose primary path is connected to a node that owns the logical disk containing the chunklets being relocated.
7 Logical Disks Overview A Logical Disk (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. Logical disks are pooled together in Common Provisioning Groups (CPGs) which allocate space to virtual volumes. Creating CPGs maps out the data layout parameters for the creating logical disks. Logical disks are created automatically by the system when virtual volumes are created from CPGs.
failures. When the destination logical disks become available again, the system automatically writes the preserved data from the preserved data logical disks to the destination logical disks. • Administration volume logical disks 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 4 Data Striped Across RAID 1 Sets on a RAID 10 Logical Disk RAID 5 and 50 On a RAID 50 logical disk, 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 5 Data Striped Across RAID 5 Sets on a RAID 50 Logical Disk RAID Multi-Parity On a RAID Multi-Parity (MP) or RAID 6 logical disk, 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 8 chunklets has a total of 6 chunklets of space for data and 2 chunklets of space for parity. RAID MP set sizes of 8 and 16 chunklets are supported. The data and parity steps are striped across each chunklet in the set.
Figure 6 Data Striped Across RAID MP Sets on a RAID MP Logical Disk Logical Disk Size and RAID Types A logical disk is a collection of physical disk chunklets arranged as rows of RAID sets. 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 logical disk size is divisible by the size of one chunklet, either 1 GB or 256 KB.
8 Common Provisioning Groups Overview A common provisioning group (CPG) creates a virtual pool of logical disks that allows virtual volumes to share the CPG's resources and allocates space on demand. You can create fully-provisioned virtual volumes and thinly-provisioned virtual volumes (TPVVs) that draw space from the CPG's logical disk pool. CPGs enable fine-grained, shared access to pooled logical capacity.
Growth Increment As volumes that draw from a CPG require additional storage, the system automatically creates additional logical disks according to the CPG's growth increment. The default and minimum growth increments vary according to the number of controller nodes in the system. 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 In some it may be desirable to use a larger growth increment.
In addition, volumes that draw from a CPG can only use the space available to that CPG based on the CPG's logical disk parameters. For example, if you create a CPG that only uses logical disks that belong to controller node 0, when the virtual volumes that draw from a CPG have filled up all space available to that CPG based on it's logical disk parameters, the following will happen: • New writes to any TPVVs mapped to that CPG will return write failures.
9 Virtual Volumes Overview Volumes draw their resources from Common Provisioning Groups (CPGs), and volumes are exported as Logical Unit Numbers (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 greater administrative flexibility, you can provision the virtual volume’s user space and snapshot space from the same or different CPGs. If the virtual volume’s user space and snapshot space are on different CPGs, the user space remains available to the host if the CPG containing the snapshot space becomes full. To save time by not repeating tasks, you can create many identical virtual volumes at one time.
allocation limit, the system allows allocation of an additional 128 MB per node beyond these limits in order to ensure that the exported TPVV address space is usable. CAUTION: Use of allocation limits is recommended to prevent consumption of physical raw capacity beyond a tolerable limit. However, you should exercise caution when setting the value of the allocation limit. Upon reaching the allocation limit, any new writes to TPVVs will fail and/or snapshot volumes associated with the CPG may become invalid.
For example, if a 1 TB TPVV with read-only snapshots has a maximum write rate of 1 GB per day and you would like 30 days warning prior to that TPVV reaching the allocation limit, use the following calculation for the allocation warning percentage: Virtual Volume Online Conversion You can convert existing fully provisioned virtual volumes to Thinly Provisioned Virtual Volumes and you can convert Thinly Provisioned Virtual Volumes to fully provisioned virtual volumes on the array without disrupting normal st
For the maximum number of physical copies that can be created with your specific system configuration, go to the Single Point of Connectivity Knowledge (SPOCK) website http:// www.hp.com/storage/spock. NOTE: If the base volume and destination volume are both Thinly Provisioned Virtual Volumes (TPVVs), only the space that is actually used is copied. See “Overview” (page 7) for additional information on TPVVs. Virtual Copy Snapshots A virtual copy is a snapshot of another virtual volume.
See Figure 8 (page 47) for a more complex example of the possible relationships between a parent base volume and its virtual copies. Figure 8 Base Volume and Virtual Copy Relationships 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.
• Each copy tracks changes made to BaseVV from its own creation date until the next snapshot is made. • S1_0 can be created at any time after S1 is created. The relationships between the virtual copies derived from a base volume can be represented as a tree. In the example in Figure 9 (page 47), the base volume BaseVV is the starting point. In this example, each new virtual copy of the original has its name incremented by 1.
Exporting virtual volumes can be performed with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform this task. VLUN Templates and Active VLUNs A VLUN template sets up an association between a virtual volume and a LUN-host, LUN-port, or LUN-host-port combination by establishing the export rule.
active VLUNs are created when the port is attached to additional hosts. However, there can only be one port presents VLUN template per port LUN combination. The same virtual volume can be exported as different LUNs on the same or different ports. Matched Set A matched set VLUN template is a combination of the host sees and port presents template types. A matched set VLUN allows a particular host on a specified port to see a virtual 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 logical disks in a Common Provisioning Group (CPG). Moving virtual volume regions from one logical disk to another enables you to compact logical disks, 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 42).
with both the HP 3PAR Command Line Interface (CLI) and the HP 3PAR Management Console. Refer to the HP 3PAR Command Line Interface Administrator’s Manual and the HP 3PAR Management Console Online Help for instructions on how to perform this task. Reclaiming Unmapped Logical Disk Space from Volumes When multiple identical virtual volumes are created as a result of a single volume creation operation, the underlying logical disks that support those volumes are shared by the volume group.
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 Command Line Interface (CLI) and the HP 3PAR Management Console to view the licenses currently enabled on your systems. For a list of default HP 3PAR OS Software Suite features and optional features, see “HP 3PAR Software” (page 9).
There are several ways Dynamic Optimization may improve system performance: • Volume layout changes after hardware upgrades. Existing virtual volumes only take advantage of resources that were present at the time of volume creation. When a system is upgraded by adding nodes, cages, or disks, the original volume and logical disk layouts may no longer be optimal. Changing the layout of a virtual volume enables volumes to take full advantage of new system resources.
If the performance of one or more physical disks degrades, the throughput of the logical disks is reduced and the entire system performance may decline. There are two general reasons why a physical disk may have degraded performance: • The physical disk has reached its maximum throughput due to an unbalanced load. A disk in this state typically has unusually high average service times when compared to other disks. • The physical disk is a bad disk.
Zeroing Unused Space Use a host application to write zeros to the allocated but unused volume space. F-Class, T-Class, StoreServ 10000, and StoreServ 7000 Storage systems detect and discard the zeros during the volume copy operation. Creating a Physical Copy After writing zeros to the allocated but unused space, the source volume is ready for the final phase of conversion. You create a TPVV physical copy of the source volume to convert the source volume to a TPVV.
HP 3PAR Virtual Lock Software HP 3PAR Virtual Lock software is an optional feature that enforces the retention period of any volume or copy of a volume. You must purchase the HP 3PAR Virtual Lock license to use this feature. Locking a volume prevents the volume from being deleted intentionally or unintentionally before the retention period elapses. You can use HP 3PAR Virtual Lock to specify the retention period for each volume or copy of a volume.
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 a minimally disruptive 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.
ATF automatically redirects host I/O from a failed source system to the replicant target system in a manner that is transparent to the host and causes minimal disruption to service. ATF uses the HP 3PAR Quorum Witness to monitor for HP 3PAR StoreServ array failure and to automatically determine whether a failover of host service is required. The HP 3PAR Quorum Witness and related technology provide the automation to trigger the transparent failover technology to execute the migration of the I/O path.
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 Operating System (OS). Hardware monitoring and configuration tasks can be performed with both the HP 3PAR Command Line Interface (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 12 HP 3PAR StoreServ 10000 Storage System Rear View Table 6 HP 3PAR StoreServ 10000 Storage System Rear View System Components 62 Item Description 1 Drive Chassis Power Supply 2
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: Fibre Channel (FC), Near Line (NL) and Solid State Drives (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 13 (page 63).
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 only contain 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.
Fibre Channel 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 (SFP) modules to service the drive cage. Figure 19 (page 66) 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. Fibre Channel 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 67).
Figure 20 HP 3PAR StoreServ 7200 Storage System Figure 21 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 22 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 would occupy the lowest 4U of the backplane and would be numbered node 6 and node 7.
Figure 23 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 24 (page 71) for an example of controller node numbering in an F-Class system.
Figure 24 F-Class Controller Node Numbering Controller Nodes 71
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 an SNMP agent that allows you to perform some basic management functions via network management software running 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 like notification and GETBULK requests, it still relies on the SNMPv1 community concept for security. • Standard 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 via 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 via 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 CIM Application Programming Interface (API), HP’s industry-standard API based on SNIA’s Storage Management Initiative Specification (SMI-S). For detailed information about the HP 3PAR CIM API, refer to the HP 3PAR CIM API Programming Reference. About SMI-S SMI-S enables management of storage area networks (SANs) in a heterogeneous multi-vendor environment.
This protocol is defined by the following specifications: • Specification for the Representation of CIM in XML Defines a standard for the representation of CIM elements and messages in XML, written in Document Type Definition (DTD). • CIM Operations over HTTP Defines a mapping of CIM Messages onto HTTP that allows implementations of CIM to interoperate in an open, standardized manner. It uses the CIM XML DTD that defines the XML Schema for CIM objects and messages.
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 82 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 compo
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 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. VLUNs that are not active will not communicate with the HP 3PAR StoreServ Storage system.
control cache Memory modules that support the microprocessors located in a controller node. control cache DIMM A single control cache memory module. controller node An individual device that works with other controller nodes to cache and manage data in a system and to provide hosts with a coherent, virtualized view of the storage system. controller node chassis An enclosure that houses all the controller nodes of a system.
drive mount A metal bracket used to secure a physical disk to a drive magazine. Each disk must be secured by two drive mounts. encryption key A cryptographic key that is not exposed outside of the drive itself. The encryption key is used to encrypt and decrypt all data stored on a drive. ESI Enclosure Services Interface.
IMP Initiator Mode Prohibited. A system setting that, when enabled, prevents a port from being set to initiator mode. independent electrical circuit An electrical circuit that does not share a circuit breaker with another electrical circuit. initiator mode The firmware setting for a Fibre Channel port that is connected to a drive cage. initiator port A port that is connected to and relays commands to physical disks within a drive cage. Also known as a disk port.
physical disk A dual-ported Fibre Channel disk mounted onto a drive magazine. physical parent The source volume for a physical copy. physical size The total actual raw storage allocated to a logical disk, as determined by its size and RAID type. port-presents VLUN template A VLUN template that allows any host connected to a particular port to see a virtual volume as a specified LUN. power bank A group of four connected AC outlets within the power distribution unit (PDU).
safety breaker The device used to power on and power off the power distribution unit. The safety breaker also prevents power surges in the AC line from damaging a system. second virtual volume backup node The controller node that takes over for the virtual volume backup node if the virtual volume node fails. secondary path Connection between a controller node initiator port and a physical disk that is used when the primary path is inaccessible (a failure condition).
system backplane An electronic circuit board that contains sockets into which power supplies and controller nodes are plugged. system box Feature on the HP 3PAR Management Console main window toolbar that enables you to move quickly between systems. system manager Software component that negotiates between the system and the user interfaces such as the HP 3PAR Management Console and HP 3PAR OS CLI.
WWN World-Wide Name. A unique 64-bit or 128-bit value used to identify Fibre Channel devices on an arbitrated loop. The WWN consists of a prefix issued by the IEEE to uniquely identify the company and a suffix that is issued by the company. zero fill To fill unused storage space with the representation of the character denoting “0”. zone A unit of physical disk space reserved by a controller node for snapshot or snapshot administration data. A single zone may occupy space on more than one disk.
Index A G Active Directory Kerberos server, 20 Active Directory LDAP, 20 Active Directory LDAP server, 20 adaptive optimization, 57 admin volume, 43 alerts when spare and free chunklets are used up, 32 allocation limit, 44 allocation warning, 44 authentication, 20 group-to-domain mapping, 23 group-to-role mapping, 22 growth increment considerations, 40 GSSAPI binding, 22 GSSAPI, 22 B base volumes retrieval time affected by distance from, 48 virtual copy tree relationships, 48 C hardware HP 3PAR storag
O OpenLDAP, 20 optimization adaptive , 57 priority, 59 P peer motion, 58 performance consequences of virtual volumes, 48 PLAIN binding, 22 PLAIN, 22 priority optimization, 59 S schemas, 20 self-encrypting drives, 58 simple binding, 22 snapshots creation rules, 48 stale definition, 48 tree view of, 47 SNMP (Simple Network Management Protocol), 72 symbols in text, 84 T text symbols, 84 U user rights in domains, 25 V virtual columes naming conventions, 48 virtual copies stale definition, 48 virtual volume
