HP 3PAR StoreServ 7200 2-node Manual
  1. Manuals
  2. Brands
  3. HP Manuals
  4. Storage
  5. 3PAR StoreServ 7200 2-node
  6. Manual

HP 3PAR StoreServ 7200 2-node Manual

Hp 3par storeserv storage concepts guide (os 3.1.2 mu2) (qr482-96384, june 2013)
Hide thumbs Also See for 3PAR StoreServ 7200 2-node:
Table of Contents

Advertisement

Quick Links

See also: Administrator's Manual , Manual
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.
HP Part Number: QR482-96384
Published: June 2013

Advertisement

Table of Contents
loading

Related Manuals for HP 3PAR StoreServ 7200 2-node

Summary of Contents for HP 3PAR StoreServ 7200 2-node

  • Page 1 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. HP Part Number: QR482-96384 Published: June 2013...
  • Page 2 © 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.21 1 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.

  • Page 3: Table Of Contents

    Contents 1 Overview....................7 HP 3PAR Storage Concepts and Terminology................7 Physical Disks........................8 Chunklets..........................8 Logical Disks........................8 Common Provisioning Groups....................8 Virtual Volumes........................8 Fully-provisioned Virtual Volumes..................8 Thinly-provisioned Virtual Volumes..................8 Physical Copies.......................9 Virtual Copy Snapshots....................9 Exporting Virtual Volumes....................9 HP 3PAR Software........................9 HP 3PAR Software Products and Features................10 HP 3PAR Software Licensing Requirements................13 2 HP 3PAR Storage System Users..............18 User Accounts........................18...
  • Page 4 The Host Explorer Software Agent.....................31 6 Chunklets....................32 Overview..........................32 Physical Disk Chunklets......................32 Spare Chunklets........................32 7 Logical Disks....................34 Overview..........................34 Logical Disks and Common Provisioning Groups.................34 Logical Disk Types........................34 RAID Types..........................35 RAID 0..........................35 RAID 1 and 10........................35 RAID 5 and 50........................36 RAID Multi-Parity........................37 Logical Disk Size and RAID Types.....................38 8 Common Provisioning Groups..............39 Overview..........................39...
  • Page 5 1 1 Enhanced Storage Applications..............53 Overview..........................53 HP 3PAR mySnapshot Software....................53 HP 3PAR Dynamic Optimization Software .................53 HP 3PAR System Tuner Software....................54 HP 3PAR Thin Conversion Software...................55 Assessment........................55 Data Preparation.......................55 Zeroing Unused Space.......................56 Creating a Physical Copy....................56 HP 3PAR Thin Persistence Software....................56 HP 3PAR Thin Copy Reclamation Software.................56 HP 3PAR Virtual Lock Software....................57 HP 3PAR Adaptive Optimization Software..................57...
  • Page 6 About the WBEM Initiative.......................78 HP 3PAR CIM Support......................79 Standard Compliance......................79 SMI-S Profiles........................79 Supported Extensions......................79 CIM Indications.........................79 15 Comparing HP 3PAR to EVA Terms............80 16 Support and Other Resources..............81 Contacting HP........................81 HP 3PAR documentation......................81 Typographic conventions......................84 HP 3PAR branding information....................84 17 Documentation feedback.................85 Glossary....................86 Index......................94 Contents...

  • Page 7: Overview

    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, “HP 3PAR Storage System Hardware” (page 61).

  • Page 8: Physical Disks

    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).

  • Page 9: Physical Copies

    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 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.

  • Page 10: Hp 3Par Software Products And Features

    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.
  • Page 11 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.
  • Page 12 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”...

  • Page 13: Hp 3Par Software Licensing Requirements

    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.
  • Page 14 Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms License HP 3PAR Software Required? Licensing Supported Hardware Platforms HP 3PAR Access Licensed as part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR Guard Software StoreServ 10000 Storage, HP 3PAR StoreServ 7000 Storage HP 3PAR Full Copy...
  • Page 15 Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) License HP 3PAR Software Required? Licensing Supported Hardware Platforms StoreServ 10000 Storage OS Software Suite; also available standalone HP 3PAR Part of the HP 3PAR OS HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR Management StoreServ 10000 Storage, HP 3PAR StoreServ Console Software...
  • Page 16 Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) License HP 3PAR Software Required? Licensing Supported Hardware Platforms and the HP 3PAR Optimization Suite; also available standalone HP 3PAR Peer Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR Motion Software StoreServ 7000 Data Optimization StoreServ 10000 Storage, HP 3PAR StoreServ...
  • Page 17 Table 1 HP 3PAR Software Licensing and Supported Hardware Platforms (continued) License HP 3PAR Software Required? Licensing Supported Hardware Platforms HP 3PAR Host Licensed as part of the HP 3PAR HP 3PAR F-Class, HP 3PAR T-Class, HP 3PAR Explorer for StoreServ 7000 Application Suite for StoreServ 10000 Storage, HP 3PAR StoreServ VMware vSphere...

  • Page 18: Hp 3Par Storage System Users

    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.

  • Page 19: Local User Authentication And Authorization

    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.

  • Page 20: Lightweight Directory Access Protocol

    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.

  • Page 21: Ldap Server Data Organization

    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.

  • Page 22: Ldap Authentication And Authorization

    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.

  • Page 23: Authorization On Systems Using Virtual Domains

    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.

  • Page 24: Hp 3Par Virtual Domains

    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.

  • Page 25: Domain Type

    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.
  • Page 26 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.

  • Page 27: Ports And Hosts

    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.

  • Page 28: Port Location Formats

    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.

  • Page 29: Port Target, Initiator, And Peer Modes

    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.

  • Page 30: Managing Host Personas

    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.

  • Page 31: Legacy Host Personas

    Table 3 Host Personas (continued) Persona Number Persona Name Host Operating System Additional Capabilities NetApp ONTAP Data ONTAP SoftInq 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.

  • Page 32: Chunklets

    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.
  • Page 33 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.

  • Page 34: Logical Disks

    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.

  • Page 35: Raid Types

    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.

  • Page 36: Raid 5 And 50

    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.

  • Page 37: Raid Multi-Parity

    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.

  • Page 38: Logical Disk Size And Raid Types

    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.

  • Page 39: Common Provisioning Groups

    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.

  • Page 40: Growth Increment

    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...

  • Page 41: System Guidelines For Creating Cpgs

    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.

  • Page 42: Virtual Volumes

    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.

  • Page 43: Administrative 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.

  • Page 44: Tpvv Warnings And Limits

    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.

  • Page 45: Virtual Volume Online Conversion

    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...

  • Page 46: Virtual Copy Snapshots

    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.

  • Page 47: Copy-On-Write Function

    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.

  • Page 48: Copy-Of And Parent Relationships

    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.

  • Page 49: Vlun Templates And Active Vluns

    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.

  • Page 50: Matched Set

    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.

  • Page 51: 10 Reclaiming Unused Space

    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.

  • Page 52: Reclaiming Unmapped Logical Disk Space From Volumes

    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.

  • Page 53: 1 Enhanced Storage Applications

    1 1 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.

  • Page 54: Hp 3Par System Tuner Software

    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.

  • Page 55: Hp 3Par Thin Conversion Software

    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.

  • Page 56: Zeroing Unused Space

    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.

  • Page 57: Hp 3Par Virtual Lock Software

    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.

  • Page 58: Hp 3Par Peer Motion Software

    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.

  • Page 59: Priority Optimization

    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.
  • Page 60 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.

  • Page 61: 12 Hp 3Par Storage System Hardware

    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.
  • Page 62 Table 5 HP 3PAR StoreServ 10000 Front View System Components Item Description HP 3PAR StoreServ 10000 Storage system (V400 model) HP 3PAR StoreServ 10000 Storage system (V800 model) Drive Cage FC-AL Modules Cooling Fans Battery Backup Units Service Processor Drive Chassis Leveling Foot Figure 12 HP 3PAR StoreServ 10000 Storage System Rear View Table 6 HP 3PAR StoreServ 10000 Storage System Rear View System Components...

  • Page 63: Physical Disks

    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.

  • Page 64: Drive Cage/Enclosure Models

    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.

  • Page 65: Dc3 Drive Cage And Ports And Cabling

    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. Figure 17 DC4 Drive Cage Table 7 DC4 Drive Cage Components Item Description...

  • Page 66: Controller Nodes

    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.

  • Page 67: Port Numbering

    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 F400 Port Numbering The number of host ports each storage system model can accommodate is summarized in Table 10...

  • Page 68: Hp 3Par Storeserv 10000 Controller Node Numbering

    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.

  • Page 69: T-Class Controller Node Numbering

    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.

  • Page 70: F-Class Controller Node Numbering

    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. Figure 24 (page 71) for an example of controller node numbering in an F-Class system.
  • Page 71 Figure 24 F-Class Controller Node Numbering Controller Nodes...

  • Page 72: 13 Hp 3Par Snmp Infrastructure

    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.

  • Page 73: Standard Compliance

    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.

  • Page 74: Exposed Objects

    Table 1 1 MIB-II Objects Supported by the SNMP Agent (continued) Object Descriptor Description Access Name of the system. This helps to Read-only sysName identify the storage system. This name cannot be set via SNMP. User-defined system location. For Read/write sysLocation example: Building 1, room 4, rack 3.

  • Page 75: System Name

    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.

  • Page 76: Alertnotify Traps

    Table 12 Contents of the alertNotify trap (continued) Object Descriptor Description Access Code that identifies the specific type of alert or alert state change. For Read-only messageCode 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.
  • Page 77 The following information describes these alert status change events: Message Code 1245186 Severity Info Type Change in alert state Alert String Alert <alert_id> changed from state <old_state> to <new_state> Operator Action The alert has changed state. This can be used to track the state of the existing alerts in a system. The HP 3PAR SNMP Agent...

  • Page 78: 14 The Hp 3Par Cim Api

    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.

  • Page 79: Hp 3Par Cim Support

    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.

  • Page 80: 15 Comparing Hp 3Par To Eva Terms

    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.

  • Page 81: 16 Support And Other Resources

    16 Support and Other Resources Contacting HP For worldwide technical support information, see the HP support website: http://www.hp.com/support Before contacting HP, collect the following information: Product model names and numbers Technical support registration number (if applicable) Product serial numbers Error messages Operating system type and revision level Detailed questions Specify the type of support you are requesting:...
  • Page 82 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 HP 3PAR Secure Service Custodian Configuration Utility monitor and control HP 3PAR storage systems Reference Using the CLI to configure and manage HP 3PAR Remote HP 3PAR Remote Copy Software User’s Guide...
  • Page 83 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...

  • Page 84: Typographic Conventions

    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...

  • Page 85: 17 Documentation Feedback

    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.

  • Page 86: Glossary

    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.
  • Page 87 control cache Memory modules that support the microprocessors located in a controller node. control cache A single control cache memory module. DIMM 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.
  • Page 88 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.
  • Page 89 Initiator Mode Prohibited. A system setting that, when enabled, prevents a port from being set to initiator mode. independent An electrical circuit that does not share a circuit breaker with another electrical circuit. 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.
  • Page 90 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 A VLUN template that allows any host connected to a particular port to see a virtual volume as VLUN template...
  • Page 91 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 The controller node that takes over for the virtual volume backup node if the virtual volume node volume backup fails.
  • Page 92 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.
  • Page 93 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”.

  • Page 94: Index

    Index Active Directory group-to-domain mapping, Kerberos server, group-to-role mapping, Active Directory LDAP, growth increment Active Directory LDAP server, considerations, adaptive optimization, GSSAPI binding, admin volume, GSSAPI, alerts when spare and free chunklets are used up, allocation limit, hardware allocation warning, HP 3PAR storage system, authentication, HP 3PAR peer persistence,...
  • Page 95 OpenLDAP, optimization adaptive , priority, peer motion, performance consequences of virtual volumes, PLAIN binding, PLAIN, priority optimization, schemas, self-encrypting drives, simple binding, snapshots creation rules, stale definition, tree view of, SNMP (Simple Network Management Protocol), symbols in text, text symbols, user rights in domains, virtual columes...

This manual is also suitable for:

3par storeserv 7400 2-node3par storeserv 7400 4-node3par storeserv 7450 2-node3par storeserv 100003par t4003par t800 ... Show all

Table of Contents