® 3PAR InForm OS 2.2.4 Concepts Guide 3PAR, Inc. 4209 Technology Drive Fremont, CA 94538 USA Part No.
Revision Notices This is the second release of this manual. A complete revision history of this document is provided at the end of this document. Changes The material in this document is for information only and is subject to change without notice. While reasonable efforts have been made in the preparation of this document to assure its accuracy, 3PAR Inc. assumes no liability resulting from errors or omissions in this document or from the use of the information contained herein.
5. Products derived from this software may not be called "Apache", nor may "Apache" appear in their name, without prior written permission of the Apache Software Foundation. THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
2 Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3 All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the NetBSD Foundation, Inc. and its contributors.
A copy of the GNU Lesser General Public License is available on the CD-ROM provided by 3PAR and may additionally be obtained at http://www.fsf.org/licenses/lgpl.html. A copy of the source code for such software may be obtained from 3PAR or from http://www.debian.org OpenSSL License Materials The InForm OS uses the unmodified libssl OpenSSL library. This library is licensed under dual licenses, the OpenSSL License and the SSLeay License. Copyright (c) 1998-1999 The OpenSSL Project. All rights reserved.
lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used.
Other Licensed Materials The snmpagent within the InServ contains copyright materials from AdventNet, Inc. http://www.adventnet.com. All rights to such copyright material rest with AdventNet. Trademarks 3PAR, InServ, InForm, InSpire and Serving Information are registered trademarks of 3PAR Inc. Intel and Pentium are registered trademarks of Intel Corporation. Linux is a registered trademark of Linus Torvalds.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Table of Contents 1 Introduction 1.1 Audience 1.1 1.2 User Interfaces 1.2 1.3 Supported Operating Systems 1.2 1.4 Units of Measure 1.2 1.5 Related Documentation 1.3 1.6 Organization 1.4 1.7 Typographical Conventions 1.6 1.8 Advisories 1.7 2 Overview 2.1 3PAR Storage Concepts and Terminology 2.2 2.1.1 Physical Disks 2.2 2.1.2 Logical Disks 2.3 2.1.3 Virtual Volumes 2.7 2.1.4 LUNs and VLUNs 2.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 3 InServ Storage Server Users 3.1 Overview 3.1 3.2 Local Users 3.2 3.3 Domain Users 3.2 3.4 LDAP Users 3.3 4 LDAP 4.1 Overview 4.1 4.1.1 Active Directory 4.2 4.1.2 OpenLDAP 4.2 4.2 LDAP Users 4.2 4.3 LDAP Server Data Organization 4.3 4.4 LDAP and Domains 4.4 4.5 LDAP Authentication and Authorization 4.5 4.5.1 Authentication 4.5 4.5.2 Authorization 4.6 4.5.3 Authorization on Systems Using 3PAR Domains 4.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 6.3.1 Fibre Channel Adapters 6.3 6.3.2 iSCSI Adapters 6.3 6.3.3 Gigabit Ethernet Adapters 6.3 6.4 Target, Initiator, and Peer Mode 6.3 6.5 Exporting Volumes 6.4 6.6 Port Location Formats 6.5 6.7 The Port Persona 6.5 6.8 The Port Parameters 6.8 7 Logical Disks 7.1 Logical Disks and Virtual Volumes 7.1 7.2 Logical Disks and Common Provisioning Groups 7.2 7.3 Logical Disk Types 7.2 7.4 Logical Disk Size and RAID Type 7.3 7.4.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 8.7.5 TPVV Warnings and Limits 8.13 8.7.6 Commonly Provisioned Virtual Volumes 8.15 9 Virtual Volumes Exports 9.1 Active and Template VLUNs 9.1 9.2 VLUN Template Types 9.2 9.2.1 Host Sees 9.2 9.2.2 Port Presents 9.2 9.2.3 Matched Set 9.3 10 Common Provisioning Groups 10.1 Overview 10.2 10.2 Precautions and Planning 10.2 10.2.1 Growth Increments, Warnings, and Limits 10.3 10.2.2 Growth Increment 10.4 10.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 14 SNMP 14.1 Overview 14.1 14.2 About SNMP 14.2 14.3 SNMP Managers 14.2 14.4 The 3PAR SNMP Agent 14.3 14.4.1 Standard Compliance 14.3 14.4.2 Supported MIBs 14.4 15 Space Management 15.1 Overview 15.1 15.2 Reclaiming Space 15.1 15.2.1 Reclaiming Volume Space 15.3 15.2.2 Reclaiming CPG Space 15.3 16 mySnapshot 17 The 3PAR InForm CIM API 17.1 Overview 17.1 17.2 About SMI-S 17.2 17.3 About the WBEM Initiative 17.2 17.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 19 Dynamic Optimization 20 System Tuner A Sparing A.1 Overview A.1 A.2 Viewing Spare Chunklets A.2 A.3 Creating Spare Chunklets A.4 A.4 Removing Spare Chunklets A.4 B Servicing Hardware and Moving Hosts B.1 Disk Replacement B.2 B.2 Using the servicemag Command B.2 B.2.1 xiv Considerations for Using servicemag B.3 Preserved Data B.4 B.4 Active and Inactive Hosts B.4 B.5 Moving Hosts B.5 B.6 Disconnecting a Host B.6 B.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 1 Introduction In this chapter 1.1 Audience 1.1 1.2 User Interfaces 1.2 1.3 Supported Operating Systems 1.2 1.4 Units of Measure 1.2 1.5 Related Documentation 1.3 1.6 Organization 1.4 1.7 Typographical Conventions 1.6 1.8 Advisories 1.7 1.1 Audience This concepts manual is for system and storage administrators who monitor and direct system configurations and resource allocation for 3PAR InServ Storage Servers. Introduction 1.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 1.2 User Interfaces Two user interfaces are offered as part of the 3PAR InForm® Operating System for administration of the InServ Storage Server: the 3PAR InForm Command Line Interface (CLI) and the 3PAR InForm Management Console. 1.
InForm OS Version 2.2.4 ■ 3PAR InForm OS Concepts Guide All units of performance (speed) are calculated base 10 (x1000). Therefore: ◆ 1 KB = 1000 bytes ◆ 1 MB = 1020 bytes = 1,000,000 bytes ◆ 1 GB = 1030 bytes = 1000 MB = 1,000,000,000 bytes ◆ 1 TB = 1040 bytes = 1000 GB = 1,000,000,000,000 bytes 1.5 Related Documentation The following documents also provide information related to InServ Storage Servers and the InForm Operating System: Table 1-1.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Table 1-1. Related Documentation (continued) For information about… Read the… Identifying storage server 3PAR InForm OS Messages and components and detailed alert Operator’s Guide information Using 3PAR Remote Copy 3PAR Remote Copy User’s Guide Using 3PAR CIM 3PAR CIM API Programming Reference 1.
InForm OS Version 2.2.4 ■ 3PAR InForm OS Concepts Guide Chapter 10, Common Provisioning Groups, discusses how logical disks can be pooled into groups used to provision space in virtual volumes. ■ Chapter 11, Physical Disks, provides detailed information about storage server physical disks. ■ Chapter 12, Drive Cages, provides detailed information about storage server drive cages and loops.
3PAR InForm OS Concepts Guide ■ InForm OS Version 2.2.4 Appendix B, Servicing Hardware and Moving Hosts, describes some service procedures from an informational perspective. Included in this appendix is a discussion of the servicemag and servicehost InForm CLI commands. This guide also contains a glossary, an index, and a revision history for your reference. 1.7 Typographical Conventions This guide employs the following typographical conventions: Table 1-2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 1.8 Advisories To avoid injury to people or damage to data and equipment, be sure to observe the cautions and warnings in this guide. Always be careful when handling any electrical equipment. NOTE: Notes are reminders, tips, or suggestions that supplement the procedures included in this guide. CAUTION: Cautions alert you to actions that can cause damage to equipment, software, or data.
3PAR InForm OS Concepts Guide 1.8 Advisories InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 2 Overview In this chapter 2.1 3PAR Storage Concepts and Terminology 2.2 2.1.1 Physical Disks 2.2 2.1.2 Logical Disks 2.3 2.1.3 Virtual Volumes 2.7 2.1.4 LUNs and VLUNs 2.10 2.2 3PAR Products, Features, and Licenses 2.10 2.2.1 InForm Software Suite 2.11 2.2.2 Optional System Features 2.11 2.2.3 Related Software Products 2.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 2.1 3PAR Storage Concepts and Terminology The 3PAR storage system is comprised of the following layers: ■ Physical disks ■ Logical disks ■ Virtual volumes ■ LUNs and VLUNs 2.1.1 Physical Disks A physical disk is a Fibre Channel or Near Line disk mounted onto a drive magazine in a storage server drive cage. There are three models of drive cages: DC2, DC3, and DC4.
InForm OS Version 2.2.4 ■ 3PAR InForm OS Concepts Guide One or more chunklets are allocated as spares. These spare chunklets are used to hold data during disk failures and maintenance procedures that require data relocation. Any chunklet can be reserved as a spare, but the system setup script selects those chunklets as close to the end of the disk logical-block space as possible. Appendix A, Sparing contains additional information about working with spare chunklets.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Figure 2-1 shows a RAID 0 logical disk with a set size of 1 and a row size of 3: Row size Set size Step size B E C F .. . ... ... A D n-2 n-1 n =Chunklet RAID 0 logical disk Figure 2-1. Data is Striped Across Chunklets on a RAID 0 Logical Disk 2.1.2.1.2 RAID 1 and 10 On a RAID 10 logical disk, data is striped across RAID 1 (or mirrored) sets. A RAID 1 set is made up of two or more chunklets that contain the same data.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Figure 2-2 shows a RAID 10 logical disk with a set size of 2 and a row size of 3 in two rows: Row size Set size* Step size A D A‘ D‘ B E B‘ E‘ C F C‘ F‘ n-3 n-3‘ n-2 n-2‘ n-1 n-1‘ n n+3 n‘ n+3‘ n+1 n+4 n+1‘ n+4‘ n+2 n+5 n+2‘ n+5‘ Row 1 Row 2 = Chunklet RAID 10 logical disk *Mirror depth Figure 2-2. Data is Striped Across RAID 1 Sets on a RAID 10 Logical Disk 2.1.2.1.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Figure 2-3 shows a RAID 50 logical disk with a set size of 3 and a row size of 2 in one row: Row size Set size* Step size A P (E,F) B E = Chunklet P (A,B) F C P (G,H) D G P (C,D) H RAID 50 logical disk *Parity set Figure 2-3. Data is Striped Across RAID 5 Sets on a RAID 50 Logical Disk 2.1.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide NOTE: Snapshot administration space is explained in a following section. CPGs are explained further in Chapter 10, Common Provisioning Groups. 2.1.3 Virtual Volumes Virtual volumes can either be base volumes or snapshots (copies of other volumes). Copies of other volumes are called snapshots because they are point-in-time copies. These snapshots can either be virtual copies or physical copies.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 A base volume is the original volume from which a series of point-in-time copies (snapshots), either physical or virtual, can be created. Base volumes differ from other types of virtual volumes in that base volumes are the only type of volumes that have physical storage space to hold data rather than pointers to other volumes.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide destination volume must also be a base volume, have a user space size at least as large as the user space of the base volume being copied, and must not be exported. NOTE: With a 3PAR Remote Copy license, physical copies can be copied from one InServ Storage Server to another using 3PAR Remote Copy. For additional information, see the 3PAR Remote Copy User’s Guide. See Chapter 8, Virtual Volumes for additional information on physical copies. 2.1.3.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 NOTE: With a 3PAR Remote Copy license, virtual copies can be copied from one InServ Storage Server to another using 3PAR Remote Copy. For additional information, see the 3PAR Remote Copy User’s Guide. 2.1.3.4 The Admin Volume As part of installation and setup, a base volume called the admin volume (or administrative volume), is created on the system.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 2.2.1 InForm Software Suite 3PAR InServ Storage Servers come with the InForm software suite. 3PAR InForm Suite is the core set of storage management software. 3PAR InForm Suite includes: ■ 3PAR InForm Operating System. Independent instances of the operating system run on each controller node. ■ Access Guard, to provide volume security at logical and physical levels by enabling you to secure hosts and ports to specific virtual volumes.
3PAR InForm OS Concepts Guide ■ InForm OS Version 2.2.4 3PAR Recovery Manager for Oracle, Exchange Server, and SQL Server is an optional feature that intelligently creates, manages, and presents time-consistent snapshot images of Oracle®, Microsoft® Exchange, and Microsoft SQL Server databases for nondisruptive backup, rapid application recovery, and data sharing. ■ 3PAR Domains is an optional system feature that is used for access control.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 3 InServ Storage Server Users In this chapter 3.1 Overview 3.1 3.2 Local Users 3.2 3.3 Domain Users 3.2 3.4 LDAP Users 3.3 3.1 Overview A user account is required to access an InServ Storage Server. The first user account must be set up on the node itself.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 3.2 Local Users Local users are users created on the system and access the system using the InForm CLI or InForm Management Console. Each user is assigned one of four user classes during creation, which allow varying levels of accessibility in the system. These classes are described in Table 3-1. Table 3-1. User Classes User Class Accessibility Browse Allows read-only accessibility.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide have privileges. Thus, a domain user’s assigned user class is applicable only within the domain to which the user has privileges. Table 3-2. User Class Privileges by Domain Type User Class Privileges in Domain “All” Browse ■ Browse all objects in the system. ■ Review the system event log. ■ Review system alerts. Privileges in Domain “Specified” ■ Browse all physical system objects.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 is a significant difference from local users in that privileges are associated with a group rather than an individual. Group privileges are identical to local user’s user classes as described in Local Users on page 3.2. For detailed information about LDAP users and LDAP, see Chapter 4, LDAP. For instructions on setting up an LDAP connection, see Chapter 4, Managing User Accounts and Connections, in the InForm OS CLI Administrator’s Manual. 3.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 4 LDAP In this chapter 4.1 Overview 4.1 4.2 LDAP Users 4.2 4.3 LDAP Server Data Organization 4.3 4.4 LDAP and Domains 4.4 4.5 LDAP Authentication and Authorization 4.5 4.1 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.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Accessing objects on InServ servers configured to use 3PAR Domains requires privileges in the domain in which those objects reside. The configuration of domains may differ from one InServ system installation to the next. This results in differing levels of privileges over objects based on mapping between the LDAP configuration and the individual InServ server’s domain configuration.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide During authentication, if a user name is not recognized as a local user, that user’s name and password are checked on the LDAP server. Users existing as both a local user and LDAP use who share the same user name, are authenticated by the InServ Storage Server. That is, the local user’s authentication data takes precedence over the user’s LDAP authentication data. User names not associated with local user names are authenticated using LDAP data.
3PAR InForm OS Concepts Guide ■ As a list of groups associated with each user. ■ As a list of users associated with each group. InForm OS Version 2.2.4 The form in which data is organized is dependent on the type of LDAP server used and the tools used to maintain the data. Programs such as ldp.exe, which is a downloadable Windows Support Tool available from Microsoft, and ldapsearch, which is available for many Unix and Linux systems, can be used to view data entries in the LDAP server.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 4.5 LDAP Authentication and Authorization As stated earlier, the user’s user name is first checked against the authentication data stored on the local InServ Storage Server. 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.
3PAR InForm OS Concepts Guide ■ InForm OS Version 2.2.4 The PLAIN mechanism is similar to simple binding where the user’s user name and password are sent directly to the LDAP server for authentication. As with simple binding, the PLAIN mechanism should only be used if there is a secure connection (SSL or TLS) to the LDAP server. ■ The GSSAPI mechanism obtains a ticket from the Kerberos server which validates the user’s identity. That ticket is then sent to the LDAP server for authentication.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide further where the user’s groups are mapped to system domains. Therefore, the user’s privilege level within a specific group is carried over to the domain(s) mapped to that group. For instructions on authorizing LDAP users on systems using Domains, see Chapter 4, Managing User Accounts and Connections in the InForm OS CLI Administrator’s Manual.
3PAR InForm OS Concepts Guide 4.8 LDAP Authentication and Authorization InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 5 3PAR Virtual Domains In this chapter 5.1 Overview 5.1 5.2 Domain Types and User Classes 5.3 5.3 Users and Domain Privileges 5.5 5.4 Object and Domain Association Rules 5.5 5.5 The Default and Current Domains 5.5 5.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 In addition to the inherent security provided by this hierarchical user structure, finer grain access control of the InServ system can optionally be achieved through the implementation of 3PAR Virtual Domains (domains). Domains allows an administrator to create up to 1024 domains, or spaces, within an InServ Storage Server, where each domain is dedicated to a specific application.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 5.2 Domain Types and User Classes When using domains for access control, accessibility to basic objects and derived objects is limited by a user’s class (privilege level) and domain assignment. 5.2.1 Domain Type The first tier of access control is the domain to which a subset of an InServ system’s objects belong. The objects can be assigned to a specific domain, or have no domain association.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Table 5-1. User Class Privileges by Domain Type User Class Privileges in Domain “All” Browse ■ Browse all objects in the system. ■ Review the system event log. ■ Review system alerts. Privileges in Domain “Specified” ■ Browse all physical system objects. ■ Browse basic and derived domain objects in the user’s specified domain. Edit ■ All Browse user class privileges. ■ All Browse user class privileges. ■ Create hosts.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 5.3 Users and Domain Privileges By default, users belonging to the Super user class have privileges over the entire system. Only these users and users belonging to the Edit user class in the all domain can create and edit CPGs, hosts, Remote Copy groups and assign CPGs and hosts to specified domains. Additionally, these users have access to all domains and their objects.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 that a specific domain will receive the majority of attention from a user, 3PAR Domains provides the ability for administrators to set a default domain for that user. Domain A User belonging to edit user class Domain B ALL assigned domains’ objects viewable and operable. Figure 5-2. No Assigned Default or Current Domains A user’s default domain is the domain that user will access upon the start of each working CLI session.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Session 1 User belonging to edit user class default domain: set for ALL sessions (Domain A) Session 2 Domain A Session 3 Domain A current domain: set for a SINGLE session (Domain B) Domain B SINGLE assigned domain’s (either default or current) objects viewable and operable. Figure 5-3. Assigned Default and Current Domains The Default and Current Domains 5.
3PAR InForm OS Concepts Guide 5.8 The Default and Current Domains InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 6 Hosts, Ports, and Connections In this chapter 6.1 Overview 6.2 6.2 Creating, Editing, and Removing Hosts 6.2 6.3 About Ports 6.3 6.4 Target, Initiator, and Peer Mode 6.3 6.5 Exporting Volumes 6.4 6.6 Port Location Formats 6.5 6.7 The Port Persona 6.5 6.8 The Port Parameters 6.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 6.1 Overview InServ Storage Servers automatically detect new physically connected host paths and display their WWNs (World Wide Names) (for Fibre Channel ports) or iSCSI Names (for iSCSI ports) in the InForm CLI and the InForm Management Console. However, you can also add new WWNs or iSCSI Names for unestablished host paths and assign them to a host before they are physically connected.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 6.3 About Ports The storage server controller nodes use Fibre Channel, iSCSI, and Gigabit Ethernet adapters to connect the system's physical disks to host computers and to other storage servers. The InForm CLI and Management Console enables you to view port information and settings for all of these ports. 6.3.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 iSCSI ports use the following firmware mode settings: ■ Target mode is for ports that connect to hosts and receive commands from those hosts. Gigabit Ethernet ports use the following firmware mode setting: ■ Peer mode is for Ethernet ports, used for Remote Copy over IP (RCIP).
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 6.6 Port Location Formats The InForm user interfaces can express controller node Fibre Channel, iSCSI, and Gigabit Ethernet adapter port locations in the following formats: ■ 0:0:0 (default) - as expressed in the InForm CLI and Management Console (::) Node: (0,1,2,3,4,5,6 or 7) depends on the number of nodes and the storage server model. Slot: (0-5 for each node) numbered consecutively from left to right.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 NOTE: Persona setting 0 is for initiator ports that connect to drive cages within the same InServ Storage Server. See also Target, Initiator, and Peer Mode on page 6.3. NOTE: Persona settings 16 and 17 are for Remote Copy connections. See the 3PAR Remote Copy User’s Guide for more information. 6.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Table 6-1.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Table 6-1. Port Persona Settings (continued) Persona number Vendor Adapter type OS Level Connection 18 Generic Generic Data 0 Direct connect (DC) 0 Fabric attached (FA) ONTAP® 19 Generic Generic Data ONTAP® NOTE: This list of persona numbers may be expanded in the future. To see all the personas currently available, use the controlport -h command to display the help for this command. 6.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide controlport rate auto followed by the port location in node:slot:port (N:S:P) format to allow the system to determine the data rate automatically. The default value for this option is auto. ■ Set the port’s Class 2 service support level with the cl2 sub-command followed by ack0, ack1, or disable and then by the port location in node:slot:port (N:S:P) format.
3PAR InForm OS Concepts Guide 6.10 The Port Parameters InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 7 Logical Disks In this chapter 7.1 Logical Disks and Virtual Volumes 7.1 7.2 Logical Disks and Common Provisioning Groups 7.2 7.3 Logical Disk Types 7.2 7.4 Logical Disk Size and RAID Type 7.3 7.5 Logical Disks and Physical Disks 7.4 7.1 Logical Disks and Virtual Volumes Virtual volumes are built on logical disks, which are built on physical disks.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 7.2 Logical Disks and Common Provisioning Groups Creating a Common Provisioning Group (CPG) establishes a virtual pool of logical disks that can grow on demand. Volumes associated with a CPG draw logical disk space from that pool as needed, allocating space on demand. As the volumes that draw from a CPG require additional storage, the system automatically creates additional logical disks and adds them to the pool.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Group (CPG). These administration LDs are separate from the admin volume, a single base volume created on each system during installation and set up to store system administrative data such as the system event log. 7.4 Logical Disk Size and RAID Type A logical disk is a collection of physical disk chunklets, each 256 MB, that have been arranged as rows of RAID sets.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 7.4.2 For Common Provisioning Groups When creating a common provisioning group, the system may also round up to determine the initial allocation as well as the growth increment that determines the size of subsequent allocations that occur as the CPG grows over time.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 8 Virtual Volumes In this chapter 8.1 Logical Disks and Virtual Volumes 8.2 8.2 Standard Base Volumes 8.2 8.3 Thinly Provisioned Virtual Volumes 8.2 8.4 About the Admin Volume 8.3 8.5 System Guidelines for Volume Creation 8.3 8.6 Virtual Volume Exports (VLUNs) 8.4 8.7 Virtual Volume Types and Variations 8.5 8.7.1 Base Volumes 8.5 8.7.2 Physical Copies 8.6 8.7.3 Virtual Copies 8.7 8.7.4 Thinly Provisioned Virtual Volumes 8.11 8.7.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 NOTE: 3PAR Thin Provisioning and snapshot functionality are optional system features which must be licensed separately from other 3PAR software products and features. 8.1 Logical Disks and Virtual Volumes Virtual volumes are the only logical storage component visible to hosts. Virtual volumes are built on logical disks, which are built on physical disks.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide the CPG require additional storage, the system automatically creates additional logical disks and adds them to the pool until the CPG reaches the user-defined growth limit that restricts the CPG’s maximum size. Before creating a TPVV, you must first create a CPG. For instructions on creating CPGs and TPVVs, see the InForm OS CLI Administrator’s Manual or the InForm OS Management Console Online Help. 8.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 NOTE: The system may round up when creating logical disks to support virtual volumes and Common Provisioning Groups (CPGs), resulting in a discrepancy between the user-specified size or growth increment and the actual space allocated to logical disks created by the system. For a detailed discussion of this issue, see Logical Disk Size and RAID Type on page 7.3.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 8.7 Virtual Volume Types and Variations There are three distinct types of virtual volumes: ■ Base volumes ■ Physical copies ■ Virtual copies In addition, base volumes have two variations for allocating space on demand: ■ Thinly provisioned virtual volumes (TPVVs) ■ Commonly provisioned virtual volumes (CPVVs) 8.7.1 Base Volumes Base volumes form the root of all virtual and physical copy operations.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 The snapshot data and snapshot administration spaces for a given base volume are used for all the virtual copies created from that parent volume (when applicable). If either of these spaces becomes full, a copy-on-write operation fails. The size of these spaces is fixed when the base volume is created, but can be changed later by growing, or increasing the size of, the volume.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 8.7.3 Virtual Copies A virtual copy is a snapshot of another virtual volume (a base volume or another virtual copy) created using copy-on-write techniques available only with a 3PAR Virtual Copy license. Unlike a physical copy, which is a duplicate of the entire base volume, a virtual copy only records the changes to the original volume (that original volume need not be a base volume).
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Read-only and read/write copies must alternate. You can only make a read-only copy of a read/ write volume and a read/write copy of a read-only volume. Because base volumes are always read/write, you can only create read-only copies of a base volume (Figure 8-1): BASE VOLUME (RW) RO RO RO RO RW=read/write RO=read-only Figure 8-1.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Figure 8-3 illustrates one example of the possible relationships between a parent base volume and its virtual copies, where the virtual copies are used to create additional virtual copies: BASE VOLUME (RW) RO RO RO RO RO... RW RW RW RW RW RO RO RO RO... RO RO RO RO... RO RO RO RO... RO RO RO RO... RO RO RO RO... RW RW RW RW RW RW RW RW RW RW RW RW RW RW RW RW RW RW RW RW RO RO RO RO . . . RO RO RO RO . . . RO RO RO RO . . .
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Copy of Copy of S0 (RO) Parent Parent Copy of Parent Parent Copy of baseVV (RW) Parent Copy of Copy of S1 (RO) S1_0_0 (RO) S2 (RO) S1_0 (RW) Parent S1_0_1 (RO) S0 is the first virtual copy made of baseVV; S2 is the most recent virtual copy. 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. Figure 8-4.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Notice that the creation of snapshots follows certain rules, enforced by the system: ■ The tree grows in alternating layers of read-write and read-only snapshots. ■ There can only be one copy of a read-only virtual volume, but multiple copies of a readwrite virtual volume. (That is, each read-write copy starts a new branch of the tree; each read-only copy continues an existing branch.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 additional logical disks and adds them to the pool until the CPG reaches a user-defined growth limit that restricts its maximum size. TPVVs are capable of responding to host write requests by allocating space on demand in small increments, beginning with 256 MB per controller node supporting the TPVV. These allocations are adaptive since subsequent allocations are based on the rate of consumption for previously allocated space.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide CAUTION: Do not allow the volumes that draw from a CPG to exceed the CPG’s growth limit (see TPVV Warnings and Limits, below). Doing so can invalidate snapshot volumes. Refer to Common Provisioning Groups on page 10.1 for additional cautions and instructions. To learn about CPGs, see Chapter 10, Common Provisioning Groups.
3PAR InForm OS Concepts Guide ` InForm OS Version 2.2.4 Set the allocation warning and limit thresholds based on the growth rate and how much advance warning you require before the volume reaches its limit and writes fail.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 8.7.6 Commonly Provisioned Virtual Volumes Another variation on the standard base volume, Commonly Provisioned Virtual Volumes (CPVVs) can also draw resources from a Common Provisioning Group (CPG). CPVVs have a set amount of user space that is allocated up front for user data, and only allocate snapshot data space and snapshot administration space on demand.
3PAR InForm OS Concepts Guide 8.16 Virtual Volume Types and Variations InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 9 Virtual Volumes Exports In this chapter 9.1 Active and Template VLUNs 9.1 9.2 VLUN Template Types 9.2 9.2.1 Host Sees 9.2 9.2.2 Port Presents 9.2 9.2.3 Matched Set 9.3 9.1 Active and Template VLUNs A virtual-LUN, or VLUN, is a pairing between a virtual volume and a logical unit number (LUN), expressed as either a VLUN template or an active VLUN.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Once a VLUN template is applied to create one or more active VLUNs, hosts continue to be able to access volumes based on the export rule established by that template. Removing VLUNs associated with a volume halts host access to that volume. Removing all VLUNs for a host stops the host from accessing all volumes. 9.2 VLUN Template Types A VLUN template can be one of the following types: ■ Host sees allows only a specific host to see a volume.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 9.2.3 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. For any single LUN, there can only be one matched set VLUN template with the same host-port combination. VLUN Template Types 9.
3PAR InForm OS Concepts Guide 9.4 VLUN Template Types InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 10 Common Provisioning Groups In this chapter 10.1 Overview 10.2 10.2 Precautions and Planning 10.2 10.2.1 Growth Increments, Warnings, and Limits 10.3 10.2.2 Growth Increment 10.4 10.2.3 Growth Warning 10.5 10.2.4 Growth Limit 10.6 10.3 Volume Types Associated with CPGs 10.7 NOTE: Creating virtual volumes capable of sharing pooled resources and allocating space on demand requires additional licenses.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 10.1 Overview A Common Provisioning Group (CPG) creates a "virtual pool" of logical disks that allows up to 64 volumes to share the CPG's resources and allocate space on demand. Depending on the products and features licensed for use on a system, you can use CPGs to create virtual volumes that draw from the CPG's logical disk pool, such as Thinly Provisioned Virtual Volumes (TPVVs). CPGs enable fine-grained, shared access to pooled logical capacity.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 10.2.1 Growth Increments, Warnings, and Limits When creating a CPG, set a growth increment and an optional growth warning and growth limit to restrict the CPG's growth and maximum size. Depending on the products and features licensed for use on a system, you can then create several types of volumes that draw space from the CPG's logical disk pool as needed.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 10.2.2 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 growth increment is fixed at 32 GB, but the minimum growth increment varies according to the number of controller nodes in the system and ranges from 8 GB for a two-node system to 32 GB for a four-node system (Table 10-1). Table 10-1.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide NOTE: The system may round up when creating logical disks to support virtual volumes and common provisioning groups (CPGs), resulting in a discrepancy between the user-specified size or growth increment and the actual space allocated to logical disks created by the system. For a detailed discussion of this issue, see Logical Disk Size and RAID Type on page 7.3. 10.2.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 There are several courses of action you can take, such as adding physical disks to the system or limiting the future growth of volumes that draw from the CPG. Your response will vary depending on several factors including but not limited to the following: ■ Total available space on your system. ■ Nature of the data running on the system. ■ Number of CPGs in the system. ■ Number of volumes associated with those CPGs.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide CAUTION: Use caution in planning CPGs. The system does not prevent you from setting CPG growth warnings or growth limits that exceed the amount of currently available storage on a system. When volumes associated with a CPG use all space available to that CPG, any new writes to TPVVs associated with the CPG will fail and/or snapshot volumes associated with the CPG may become invalid (stale).
3PAR InForm OS Concepts Guide 10.8 Volume Types Associated with CPGs InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 11 Physical Disks In this chapter 11.1 Physical Disk Chunklets 11.1 11.2 Physical Disk Locations 11.2 NOTE: See Appendix B, Servicing Hardware and Moving Hosts, for information on servicing physical disks. 11.1 Physical Disk Chunklets Physical disks are divided into chunklets, where each chunklet occupies 256 MB of contiguous space.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 during installation and setup. Any chunklet can be reserved as a spare, but the system setup script selects those chunklets as close to the end of the disk logical-block space as possible. If your system is comprised of a mixture of FC and NL disks, no chunklets are allocated. ■ The remainder of the disk can be used for logical disks. 11.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 0366_L_R1 Figure 11-2. DC3 Drive Magazine Module with Physical Disk Physical Disk Locations 11.
3PAR InForm OS Concepts Guide 11.4 Physical Disk Locations InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 12 Drive Cages In this chapter 12.1 Drive Cage Models 12.1 12.1.1 DC2 and DC4 Drive Cages 12.2 12.1.2 DC2 and DC4 Ports and Cabling 12.4 12.1.3 DC3 Drive Cage 12.5 12.1.4 DC3 Ports and Cabling 12.5 NOTE: See Appendix B, Servicing Hardware and Moving Hosts, for information on servicing physical disks. 12.1 Drive Cage Models There are three models of drive cages: DC2, DC3, and DC4.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 12.1.1 DC2 and DC4 Drive Cages The DC2 and DC4 drive cages house ten drive bays numbered 0 through 9. Each drive bay accommodates a single drive magazine that holds four disks. Figure 12-1 and Figure 12-2 show a DC2 and DC4 drive cage. Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0230_L_R1 Figure 12-1. DC2 Drive Cage 12.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0588_L_R2 Figure 12-2. DC4 Drive Cage Drive Cage Models 12.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 12.1.2 DC2 and DC4 Ports and Cabling The DC2 and DC4 drive cages contain two FCAL modules for connecting the drive cage to the controller nodes. The left-hand FCAL module has two ports: A0 and B0, and the right-hand FCAL module has two ports: A1, and B1. NOTE: Daisy chaining is not supported for the DC2 or DC4 drive cages. Fibre Channel cables connect the Fibre Channel ports in the drive cage to the ports on the controller nodes.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 12.1.3 DC3 Drive Cage The DC3 drive cage contains 16 drive bays at the front, each accommodating the appropriate plug-in drive carrier module. The 16 drive bays are arranged in four rows of four drives. Figure 12-4 shows a DC3 drive cage. 0148_L_R2 Figure 12-4. DC3 Drive Cage 12.1.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Controller nodes connect to Fibre Channel ports in the drive cage FCAL modules via Fibre Channel cables. Each cable has a label to indicate the ports it uses (Figure 12-6): Node Fibre Channel Adapter Port Drive Chassis Drive Cage Port (Cxx.x) Nx:Sx:Px <–> (Cxx.x) Dx:Px Cabinet and Bay (Node Cabinet) Cabinet and Bay (Drive Chassis Cabinet) 0234_L_R1 Figure 12-6.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 13 Controller Nodes In this chapter 13.1 Controller Node Overview 13.1 13.1.1 E-Class and F-Class Controller Node Numbering 13.4 13.1 Controller Node Overview InServ controller nodes can use Fibre Channel, Gigabit Ethernet, and iSCSI ports to connect the storage sever to your network, host computers, storage sever components, and to other storage servers.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Different InServ Storage Servers use different models of controller nodes. The compatible storage severs and controller nodes are listed in Table 13-2. Table 13-1.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide The number of host ports each storage server model can accommodate is summarized in Table 13-3. Table 13-3.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 0 1 2 3 4 5 6 7 0586_L_R1 Figure 13-1. T800 Controller Node Numbering NOTE: If an InServ T800 backplane contains only two controller nodes, the controller nodes occupy the bottom 2 bays of the backplane enclosure and are numbered controller node 6 and controller node 7. 13.1.1 E-Class and F-Class Controller Node Numbering InServ E-Class and F-Class Storage Servers have one or two controller nodes depending on the storage server model. 13.
InForm OS Version 2.2.4 ■ 3PAR InForm OS Concepts Guide InServ E-Class Storage Servers always contain two controller nodes. The top controller node is number 0 and the bottom controller node is number 1. ■ InServ F-Class Storage Servers contain two or four controller nodes. The controller nodes are numbered 0-3 from top to bottom. See Figure 13-2 for an example of controller node numbering in an InServ F400 Storage Server with four controller nodes. 0 1 2 3 0757_L_R1 Figure 13-2.
3PAR InForm OS Concepts Guide 13.6 Controller Node Overview InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 14 SNMP In this chapter 14.1 Overview 14.1 14.2 About SNMP 14.2 14.3 SNMP Managers 14.2 14.4 The 3PAR SNMP Agent 14.3 14.4.1 Standard Compliance 14.3 14.4.2 Supported MIBs 14.4 14.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 14.2 About SNMP Simple Network Management Protocol (SNMP) is a standard management interface used by many software frameworks to manage hardware devices. Use of SNMP requires two components, an agent and a manager. The manager is the management process that sends requests to the agent. The host that the manager runs on is called the management station. 14.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 14.4 The 3PAR SNMP Agent The 3PAR SNMP agent runs on the InServ Storage Server and provides a management interface to enable other software products to manage 3PAR hardware using SNMP. The 3PAR SNMP agent responds to GET, SET, GETNEXT, and GETBULK SNMP requests and also generates notification messages (traps) for critical events (alerts) and alert state changes.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 14.4.2 Supported MIBs The 3PAR SNMP agent supports the following MIBs: ■ SNMPv2-MIB ◆ Management Information Block-II (MIB-II), system group. For discovery and basic information, the 3PAR SNMP agent supports the MIB-II system group. ◆ snmpTrap group, snmpTrapOID only. This is the authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2 trap.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Table 14-1. MIB-II Objects Supported by the 3PAR SNMP Agent (continued) Object Descriptor Description Access sysContact User-defined name of the person or group Read-write responsible for maintaining the storage server. sysName Name of the InServ storage system. This helps to Read-only identify the storage system. This name cannot be set via SNMP. sysLocation User-defined system location.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 14.4.2.2.2 System Object ID Access: Read-only MIB definition: sysObjectID Data type: integer Default value: 12925.1 Description: Identifies the unique product ID for the 3PAR InServ Storage Server. The first part of this ID is the unique enterprise ID assigned to 3PAR Inc. by ICANN (12925). The second part of this ID is the product ID assigned to the InServ Storage Server (1).
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 14.4.2.2.6 System Location Access: Read-write MIB definition: sysLocation Data type: Display string (max. 255 characters) Default value: Please provide location description where the device resides such as building, room, and rack number Description: Contains the user-defined location of the system. This helps to indicate where the storage system is located. For example, the location may be indicated as follows: Building 1, room 4, rack 3.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 Table 14-2. Contents of the alertNotify Trap (continued) Object Descriptor Description Access severity Severity level of the alert or alert state change, which Read-only is an integer from 0 to 5. See the 3PAR MIB for definitions for each integer. timeOccurred Time the alert or alert state change occurred, in Read-only DDD mmm dd hh:mm:ss ZZZ yyyy format (for example: Mon, Jan 01 12:30:34 PST 2005). Alert ID.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide The following example shows an alertNotify trap translated from an alert: sysUpTime.0:0 hours, 28 minutes, 1 seconds. snmpTrapOID.0:.iso.org.dod.internet.private.enterprises.threepar.inserv.alertNotif y component.1:comp_hw_node details.1:Node 7 is offline nodeID.1:0 severity.1:major(2) timeOccurred.1:Wed Dec 15 16:58:20 PST 2004 id.1:647 messageCode.1:1703938 state.1:new(1) For this and for all alerts, use the message code provided (e.g.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 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 an InServ Storage Server. 14.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 15 Space Management In this chapter 15.1 Overview 15.1 15.2 Reclaiming Space 15.1 15.2.1 Reclaiming Volume Space 15.3 15.2.2 Reclaiming CPG Space 15.3 15.1 Overview The InForm OS space management commands allow you to change the way that virtual volumes are mapped to logical disks in order to move virtual volume regions from one logical disk to another.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 All types of volumes are created by mapping data from one or more logical disks to the virtual volume. Mapping is the correspondence of logical disk regions to virtual volume regions. Figure 15-1 shows data mapped in regions from logical disks onto a base volume.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 15.2.1 Reclaiming Volume Space 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. If several of the members of that volume group are later deleted, the underlying logical disks may become less efficient in terms of space.
3PAR InForm OS Concepts Guide 15.4 Reclaiming Space InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 16 mySnapshot 3PAR mySnapshot enables safe and easy copy and provisioning access to non-storage professionals such as DBAs, software developers, and test engineers working with InServ Storage Servers. Users can safely and easily restore their own copies of test data in seconds without relying on the storage administrator. mySnapshot uses an access control list to associate a user with certain administrative permissions and specified storage resources.
3PAR InForm OS Concepts Guide 16.2 InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 17 The 3PAR InForm CIM API In this chapter 17.1 Overview 17.1 17.2 About SMI-S 17.2 17.3 About the WBEM Initiative 17.2 17.4 3PAR InForm CIM Support 17.3 17.4.1 Standard Compliance 17.3 17.4.2 SMI-S Profiles 17.3 17.4.3 Supported Extensions 17.4 17.4.4 CIM Indications 17.4 17.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 17.2 About SMI-S SMI-S enables management of Storage Area Networks (SANs) in a heterogeneous multi-vendor environment. SMI-S uses an object-oriented model based on the Common Information Model (CIM) to define objects and services which comprise a SAN. By leveraging vendor and technology independent standards, SMI-S allows management application vendors to create applications that work across products from multiple vendors.
InForm OS Version 2.2.4 ■ 3PAR InForm OS Concepts Guide CIM-XML CIM-XML is a method of exchanging CIM management data. CIM-XML uses an xmlCIM payload and HTTP(s) as the transport mechanism. 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).
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 17.4.3 Supported Extensions The 3PAR InForm CIM Server supports additional classes that provide management for InServ Storage Server specific features not covered by SMI-S. Refer to the 3PAR CIM API Programming Reference for complete information. 17.4.4 CIM Indications SMI-S provides for asynchronous notification of events that indicate changes in the CIM server or the managed elements controlled by the CIM server.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 18 Task Management In this chapter 18.1 Overview 18.1 18.2 About Tasks 18.2 18.3 Task Types 18.4 18.1 Overview A set of InForm CLI task management commands enable you to display status for and manage certain long-running system operations on the InServ Storage Server. This chapter provides an overview of task management.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 18.2 About Tasks Tasks are a mechanism by which users can track selected long-running system operations on the InServ storage system. Tasks are created in one of two ways: By a user (or script) issuing certain InForm CLI commands, such as the tunealdvv ■ command. By the system initiating certain automated or scheduled processes, such as the periodic ■ resynchronization of remote copy volumes groups. Table 18-2 on page 18.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 18.2.2 Task Management Commands Table 18-1 summarizes the InForm CLI task management commands. NOTE: A task can be started by actions performed via the InForm CLI or the InForm Management Console (for example, creating a physical copy), but the task management features available via the commands listed in Table 18-1 are not currently supported by the InForm Management Console. Table 18-1.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 18.3 Task Types There are a number of tasks that can be used to track long-running system operations. Table 18-2 lists the commands associated with each operation. Table 18-2. Task Types by Operation and Command Operation (Feature or Product) Physical Copy Command createvvcopy Description Copies a virtual volume. Moving LD regions movereg (3PAR InForm OS) Virtual copy promote Moves data between logical disks.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Table 18-2. Task Types by Operation and Command (continued) Operation (Feature or Product) Command Description Restart tuning virtual tunealdvv Restarts a tunealdvv volumes -restart** operation that was (3PAR System Tuner) previously interrupted. Rollback tuning virtual tunealdvv volumes -rollback** (3PAR System Tuner) Rolls back a tunealdvv operation that was previously interrupted.
3PAR InForm OS Concepts Guide 18.6 Task Types InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 19 Dynamic Optimization The 3PAR Dynamic Optimization is an optional InForm OS feature that enables you to dynamically tune volumes by changing volume parameters (for example, RAID levels, set sizes, and disk filters). 3PAR Dynamic Optimization requires the use of the InForm CLI and also requires a 3PAR Dynamic Optimization license. Dynamic optimization enables you to non-disruptively re-layout virtual volumes.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 of this natural expansion, a system with TPVVs reduces the need for Dynamic Optimization to re-layout volumes after adding disks. Note that capacity dedicated to TPVVs and CPGs prior to adding new node pairs to a system is not "tunable" into the capacity associated with the subsequently added node pairs. If, in rare circumstances, this becomes necessary, contact your 3PAR Technical Account Manager (TAM). ■ Volume RAID level change.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide 20 System Tuner The 3PAR System Tuner is an optional InForm OS feature that allows you to identify overutilized physical disks as candidates for load balancing and to then perform load balancing on those disks. 3PAR System Tuner requires the use of the InForm CLI and also requires a 3PAR System Tuner license. As discussed in Chapter 2, Overview, virtual volumes are made up of multiple logical disks, where each logical disk contains several chunklets.
3PAR InForm OS Concepts Guide 20.2 InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide A Sparing In this appendix A.1 Overview A.1 A.2 Viewing Spare Chunklets A.2 A.3 Creating Spare Chunklets A.4 A.4 Removing Spare Chunklets A.4 A.1 Overview Some chunklets are identified as spares when the storage server is first set up at installation.
3PAR InForm OS Concepts Guide ■ InForm OS Version 2.2.4 If the time limit for logging is reached, or if the logging logical disk becomes full, relocation of chunklets on the physical disk to other chunklets (free chunklets or allocated spares) starts automatically. Free chunklets are chunklets that are not used by the system. Spare chunklets are physically allocated using the createspare command. ■ For automatic relocations, the system uses up a maximum of one disk worth of chunklets per system node.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide The fields in this output provide the following information: ■ PdId. The physical disk on which the chunklets reside. ■ Chnk. The position on the physical disk of the spare chunklets. ■ LdName. The name of the logical disk that is using the spare chunklet. ■ LdCh. The position of the chunklet on the logical disk. ■ State. The state of the chunklet as identified by the kernel.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 A.3 Creating Spare Chunklets Use the createspare command to allocate chunklets that can be used in the event of a system failure. To identify the chunklets, first identify the physical disk that contains them, either by ID or by position, and then give the position of the chunklet you want to add to the list of spares. To mark all the chunklets on a physical disk as spare, use the letter a (for “all”) instead of a chunklet number.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide The -f option forces the removal, even if the chunklet is in use. The -p command allows partial completion of the command, that is, spare chunklets not in use will be removed even if some of the chunklets listed on the command line are in use and therefore cannot be removed from the list. The following example shows a sample removespare command: removespare -p 1:3 1:4 This command removes chunklets 3 and 4 on physical disk 1.
3PAR InForm OS Concepts Guide A.6 Removing Spare Chunklets InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide B Servicing Hardware and Moving Hosts In this appendix B.1 Disk Replacement B.2 B.2 Using the servicemag Command B.2 B.2.1 Considerations for Using servicemag B.3 B.3 Preserved Data B.4 B.4 Active and Inactive Hosts B.4 B.5 Moving Hosts B.5 B.6 Disconnecting a Host B.6 B.7 Using the servicehost command B.6 CAUTION: This appendix describes procedures from an informational, rather than operational, perspective.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 B.1 Disk Replacement When a physical disk failure occurs, the disk is no longer usable by the InServ system, and must be replaced. As a physical disk fails, the InServ system automatically relocates the chunklets in this disk to other disks in the system. For additional information on how chunklets are relocated, see Appendix A, Sparing.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide chunklets back to their original positions on the drive magazine and to reconstruct the chunklets on the new disk. cli% servicemag resume 1 0.2 ... Once servicemag resume is issued, chunklets in the logging state enter the playback state as their data is played back. Once all data is played back, the chunklets return to the normal state. Any chunklets in the normal,smg state return directly to the normal state.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 B.3 Preserved Data When the InServ storage system is holding data in cache but is not able to write that data to the destination disk for any reason, it saves the data to the preserved data logical disk. As described in Logical Disk Types on page 2.6, this logical disk is automatically created at the time that the storage system is installed and initially configured.
InForm OS Version 2.2.4 3 3PAR InForm OS Concepts Guide If and when the host reappears on the same port, the InForm OS will change the state of the host to active again. At that time, the host will have access to all previously exported volumes as before. B.5 Moving Hosts Prior to moving the host to another server port, check the new port configuration and verify that the persona of the new port is the same as the source port.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 B.6 Disconnecting a Host When disconnecting a host permanently from a port, it is recommended that you use servicehost remove to remove the inactive host from the port. Prior to connecting a node to a port where the inactive host was formerly connected, manually reset the port to initiator mode using: controlport rst -m initiator B.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Glossary 3PAR Domains A A 3PAR feature that is used to create distinct Access Guard domains with domain-specific users and objects in an InServ Storage Server. 3PAR Recovery Manager A 3PAR data protection solution that has been enhanced to provide fast and efficient Oracle® backups and restores. 3PAR Remote Copy 3PAR software component that provides volume security at logical and physical levels. Access Guard is part of the InForm Software Suite.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide alert volumes are the only type of volume that have An alert is a system event that requires the snapshot data space and snapshot immediate attention of the user, and may also administration space used by snapshots to track require user intervention. See also event. alert pane The alert pane, located at the bottom of the changes to the base volume.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide child volume common provisioning group (CPG) A virtual volume (virtual or physical copy) made A set of logical disks from which you can create from a parent volume. virtual volumes and virtual copies that are capable of allocating storage on demand. chunklet A 256-MB block of contiguous space on a component indicator physical disk.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide copy data D Data that occupies the snapshot data space on a daisy chaining virtual volume. See also snapshot data space. Cabling configuration where components such as BBUs or drive cages are connected in copy size succession. The size of the snapshot data space in a virtual data cache volume, which is the amount of logical disk The dual in-line memory modules (DIMMs) that space reserved for snapshots.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide disk port drive magazine filler panel See initiator port. A panel used to seal off an empty drive bay. All slots in a drive cage must be sealed for EMI and disk scrub airflow considerations. An action by the system that periodically reads and writes to the system IDE disk to ensure that drive mount the disk is working properly. A metal bracket used to secure a physical disk to dmag a drive magazine. Each disk requires two drive mounts.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Fibre Channel adapter growth limit A Fibre Channel PCI host bus adapter (HBA) User-defined threshold that can be set for located in a controller node. The Fibre Channel common provisioning groups (CPGs) to cap their adapter connects a controller node to a host or potential size. See also growth warning. to a drive chassis.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide independent electrical circuit logging LD An electrical circuit that does not share a circuit Logging logical disk. A RAID 10 logical disk breaker with another electrical circuit. created during initial system setup and used to initiator, initiator port A port that is connected to a drive cage. Also temporarily store data during physical disk failures and replacement procedures. Each controller node has a 20 GB logging logical disk.
InForm OS Version 2.2.4 a particular host on a particular port. See also export, VLUN, and VLUN template. 3PAR InForm OS Concepts Guide N navigation tree magazine, mag The navigation tree appears in a pane that See drive magazine. occupies the left side of the InForm Management maintenance PC Console main window. Each system and system object appears as an icon in the navigation tree.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide P port-presents VLUN template parent volume A VLUN template that allows any host connected A virtual volume from which a virtual or physical to a particular port to see a virtual volume as a copy is made. See also original parent base specified LUN. See also VLUN template. volume.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide privilege levels RAID 50 (RAID 5) set Four user privilege levels (Super, Edit, Service, A group of parity-protected chunklets. Also and Browse) allow varying degrees of access to known as a parity set. storage system administrative functions. RAID set promote A grouping of mirrored or parity-protected For physical copies: to break the association chunklets.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide resynch, resynchronize primary path is inaccessible (a failure condition). To copy changes from one volume in a physical The primary and secondary paths are not user copy pair to the other because that volume was configurable and are determined by drive modified at some point after the physical copy magazine placement. operation took place. See also physical copy. selecting rollback In the InForm Management Console, Selecting See promote.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide snapshot administration space administration and/or snapshot data space to The space on a virtual volume that is used to record new changes to that base volume. track changes to the data since a snapshot of a virtual volume was created. stale snapshot A snapshot that does not track the most recent snapshot data changes to its base volume.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide storage server backplane Target Session Identifying Handle An electronic circuit board that contains sockets An identifier, assigned by the iSCSI target, for a into which power supplies and controller nodes session with a specific named initiator. are plugged. thin provisioning system box Feature on the InForm Management Console main window toolbar that enables you to move quickly between systems. See 3PAR Thin Provisioning.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide user privilege levels whatever value is assigned to the user space. See Four privilege levels (Super, Edit, Service, and also user space. Browse) allow varying degrees of access to storage system administrative functions. virtual volume A virtual storage unit created by mapping data user size from one or more logical disks. See also logical The amount of user space in a virtual volume, or disk, mapping.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide VV template Virtual volume template. The template contains a set of virtual volume parameters that can be applied again and again to create volumes with the same characteristics using the InForm Management Console. W World-Wide Name (WWN) A unique 64-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.
InForm OS Version 2.2.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Index 3PAR Domains 4.4, 5.2 C 3PAR LDAP client 4.1 cautions, about 1.7 chapter overviews 1.4 to 1.6 A Active Directory Kerberos server 4.2 Active Directory LDAP 4.2 Active Directory LDAP server 4.2 chunklet management B.2 chunklets 2.2 free, defined A.2 spare creating A.4 admin volume 2.10, 8.3 defined A.2 administration volume (admin volume) 2.10 removing A.4 advisories, conventions 1.7 viewing A.2 to A.
3PAR InForm OS Concepts Guide current domain 5.6 InForm OS Version 2.2.4 F Fibre Channel D adapter ports data rate for ports, setting 6.8 default domain 5.6 setting parameters 6.8 free chunklets, defined A.2 degraded performance 20.1 DIGEST-MD5 binding 4.6 disks logical 2.3 to 2.6, 7.1 RAID sets 2.3 physical 2.2, 11.1 chunklets 2.2 documentation, related 1.3 domain basic objects 5.5 G group-to-domain mapping 4.7 group-to-privilege mapping 4.6 GSSAPI binding 4.6 I interfaces, user 1.
InForm OS Version 2.2.4 users 3.3, 4.2 3PAR InForm OS Concepts Guide persona number of port 6.5 LDAP and Domains 4.4 physical disks 2.2 authorization 4.6 chunklets 2.2 group-to-domain mapping 4.7 repairing A.5 LDAP authentication 4.5 PLAIN binding 4.6 LDAP users vs. local users 4.3 port personas 6.5 local users 4.2 ports data rate, setting 6.8 logging logical disk persona number of (host profile) 6.5 allocated at set up A.1 service support level, setting 6.9 logical disks 2.3 to 2.6, 7.
3PAR InForm OS Concepts Guide InForm OS Version 2.2.4 simple binding 4.5 user interfaces 1.2 snapshots user privileges creation rules 8.11 stale in domains 5.5 using the servicemag command B.2 definition 8.11 types of supported 8.9 SNMP (Simple Network Management Protocol) 14.1 Solaris 8, 9 SPARC, supported 1.2 V virtual copies rules 2.9 stale definition 8.11 Solaris operating system supported 1.2 space management 15.1 to 15.3 spare chunklets virtual volumes 2.7 to 2.8, 8.2, 15.
InForm OS Version 2.2.4 3PAR InForm OS Concepts Guide Revision History Release level Revision summary 320-200085 Rev A First release of this document under part number 320-200085 Rev. A May 2008 to support initial release of InForm OS Version 2.2.4. This document was previously published under part number 320-200044. This update contains the addition of the new T-Class information. 320-200085 Rev B Added information about the InServ F-Class Storage Servers. March 2009 Revision History RH.
3PAR InForm OS Concepts Guide RH.2 InForm OS Version 2.2.
