® 3PAR InForm OS 2.3.1 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.3.1 3PAR InForm OS Concepts Guide Table of Contents 1 Introduction 1.1 Audience 1.1 1.2 User Interfaces 1.2 1.3 Units of Measure 1.2 1.4 Related Documentation 1.3 1.5 Organization 1.4 1.6 Typographical Conventions 1.5 1.7 Advisories 1.6 2 Overview 2.1 3PAR Storage Concepts and Terminology 2.2 2.1.1 Physical Disks 2.4 2.1.2 Chunklets 2.4 2.1.3 Logical Disks 2.4 2.1.4 Common Provisioning Groups 2.4 2.1.5 Virtual Volumes 2.5 2.2 3PAR InForm Software 2.7 2.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 3 InServ Storage Server Users 3.1 Overview 3.1 3.2 Local Users 3.2 3.3 Domain Users 3.3 3.4 LDAP Users 3.4 4 LDAP 4.1 Overview 4.1 4.1.1 Active Directory 4.2 4.1.2 OpenLDAP 4.3 4.2 LDAP Users 4.3 4.3 LDAP Server Data Organization 4.4 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 Virtual Domains 4.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 6.2.2 iSCSI Ports 6.3 6.2.3 Gigabit Ethernet Ports 6.3 6.3 Port Location Formats 6.3 6.4 Port Target, Initiator, and Peer Modes 6.4 6.5 Active and Inactive Hosts 6.4 6.6 Adding and Removing Hosts 6.5 6.7 Host Personas 6.5 6.7.1 Legacy Host Personas 6.8 The Host Explorer Agent 6.7 6.8 7 Chunklets 7.1 Overview 7.1 7.2 Physical Disk Chunklets 7.2 7.3 Spare Chunklets 7.2 8 Logical Disks 8.1 Overview 8.1 8.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 9.2.1 Growth Increments, Warnings, and Limits 9.3 9.2.2 Growth Increment 9.4 9.2.3 Growth Warning 9.5 9.2.4 Growth Limit 9.5 9.3 System Guidelines for Creating CPGs 9.6 9.4 Volume Types Associated with CPGs 9.7 10 Virtual Volumes 10.1 Overview 10.1 10.2 Virtual Volume Types 10.2 10.2.1 Administrative Volumes 10.3 10.2.2 Fully-Provisioned Virtual Volumes 10.3 10.2.3 Thinly-Provisioned Virtual Volumes 10.4 10.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 12.3 Dynamic Optimization 12.3 12.4 System Tuner 12.4 12.5 Thin Conversion 12.5 12.5.1 Assessment 12.6 12.5.2 Data Preparation 12.6 12.5.3 Zeroing Unused Space 12.6 12.5.4 Creating a Physical Copy 12.6 12.6 Thin Persistence 12.7 12.7 Thin Copy Reclamation 12.8 12.8 Virtual Lock 12.8 13 3PAR InServ Storage Server Hardware 13.1 Overview 13.1 13.2 Identifying Storage Server Components 13.2 13.3 Physical Disks 13.4 13.3.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 14.4.1 Standard Compliance 14.3 14.4.2 Supported MIBs 14.3 15 The 3PAR InForm CIM API 15.1 Overview 15.2 15.2 About SMI-S 15.2 15.3 About the WBEM Initiative 15.3 15.4 3PAR InForm CIM Support 15.4 15.4.1 Standard Compliance 15.4 15.4.2 SMI-S Profiles 15.4 15.4.3 Supported Extensions 15.4 15.4.4 CIM Indications 15.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 1 Introduction In this chapter 1.1 Audience 1.1 1.2 User Interfaces 1.2 1.3 Units of Measure 1.2 1.4 Related Documentation 1.3 1.5 Organization 1.4 1.6 Typographical Conventions 1.5 1.7 Advisories 1.6 1.1 Audience This conceptual guide is for all levels of system and storage administrators. Anyone who plans storage policies, configures storage resources, or monitors the storage usage of 3PAR InServ Storage Servers should read this guide.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 1.2 User Interfaces Two user interfaces are available for the administration of 3PAR InServ Storage Servers: the 3PAR InForm Command Line Interface (CLI) and the 3PAR InForm Management Console. Unless otherwise stated, all tasks can be performed with both the CLI and the Management Console.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 1.4 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.3.1 1.5 Organization This guide is organized as follows: ■ Chapter 1, Introduction (this chapter), provides an overview of this guide, including information on audience, related documentation, and typographical conventions. ■ Chapter 2, Overview, explains basic 3PAR concepts and terminology. ■ Chapter 3, InServ Storage Server Users, describes the different user types and their associated privileges within the InServ storage system.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 1.6 Typographical Conventions This guide employs the following typographical conventions: Table 1-2. Typographical Conventions Typeface Meaning Example ABCDabcd Used for dialog When prompted, click Finish to elements such as complete the installation. titles, button labels, and other screen elements. ABCDabcd Used for paths, Open the file filenames, and \console\windows\setup.exe screen output.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 1.7 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.
InForm OS Version 2.3.1 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.4 2.1.2 Chunklets 2.4 2.1.3 Logical Disks 2.4 2.1.4 Common Provisioning Groups 2.4 2.1.5 Virtual Volumes 2.5 2.2 3PAR InForm Software 2.7 2.2.1 InForm Software Suite 2.7 2.2.2 Optional Software Features 2.8 2.2.3 Host-Based Software 2.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 2.1 3PAR Storage Concepts and Terminology 3PAR InServ Storage Servers include both the hardware components that physically store your data, and the software applications that manage your data. For more information about InServ Storage Server hardware platforms, see 3PAR InServ Storage Server Hardware. For more information about InServ Storage Server software applications and features, see 3PAR InForm Software.
InForm OS Version 2.3.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 2.1.1 Physical Disks A physical disk is a hard drive mounted on a drive magazine located in a 3PAR InServ Storage Server drive cage. For more information about physical disks and the 3PAR InServ Storage Server hardware platforms, see Chapter 13, 3PAR InServ Storage Server Hardware. 2.1.2 Chunklets Physical disks are divided into chunklets. Each chunklet occupies 256 MB of contiguous space on a physical disk.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 2.1.5 Virtual Volumes Virtual 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 the hosts. You can create physical copies or virtual copy snapshots of virtual volumes that remain available if the original base volume becomes unavailable.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 2.1.5.3 Physical Copies A physical copy duplicates all the data from a base volume to a destination volume. The base volume is the original volume that is copied to the destination volume. The physical copy on the destination volume becomes available if the original base volume becomes unavailable. Unlike a virtual copy or snapshot, a physical copy maintains the performance of the base virtual volume.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 2.1.5.4.1 Exporting Virtual Volumes For a host to see a virtual volume, the volume must be exported as a Logical Unit Number (LUN). Volumes are exported by creating Virtual Volume-LUN pairings (VLUNs) on the InServ Storage Server. When you create VLUNs the system produces both VLUN templates that establish export rules, and active VLUNs that the host sees as a LUN or attached disk device.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 volumes from the volume set are autonomically provisioned to the new host without any administrative intervention. If you add a new volume or a new domain to a set, the volume or domain inherits all the privileges of the set. ■ 3PAR Persistent Cache, allows InServ Storage Servers to maintain a high level of performance and availability during node failure conditions, and during hardware and software upgrades.
InForm OS Version 2.3.1 ■ 3PAR InForm OS Concepts Guide 3PAR Thin Conversion converts a fully-provisioned volume to a Thinly-Provisioned Virtual Volume (TPVV). Virtual volumes with large amounts of allocated but unused space are converted to TPVVs that are much smaller than the original volume. To use the Thin Conversion feature you must have an InServ F-Class or T-Class Storage Server, a 3PAR Thin Provisioning license, and a 3PAR Thin Conversion license.
3PAR InForm OS Concepts Guide ■ InForm OS Version 2.3.1 3PAR System Tuner improves performance by identifying over-used physical disks, and performing load balancing on those disks without interrupting access. To learn more about the 3PAR System Tuner, see Chapter 12, Enhanced Storage Applications. ■ 3PAR Virtual Lock enforces the retention period of any volume or copy of a volume. To learn more about Virtual Lock, see Chapter 12, Enhanced Storage Applications. 2.2.
InForm OS Version 2.3.1 ■ 3PAR InForm OS Concepts Guide 3PAR Recovery Manager for Oracle on Solaris and Red Hat Linux is a separately purchased and licensed application that provides a simple, efficient and highly scalable solution for backup and recovery of Oracle databases. 3PAR Recovery Manager intelligently creates, manages, and presents time-consistent snapshot images of Oracle databases for non-disruptive backup, rapid application recovery, and data sharing.
3PAR InForm OS Concepts Guide 2.12 3PAR InForm Software InForm OS Version 2.3.
InForm OS Version 2.3.1 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.3 3.4 LDAP Users 3.4 The purpose of this chapter is to provide an overview of different types of InServ Storage Server users. 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.3.1 Creating local users and assigning system accessibility can be performed with both the 3PAR InForm Command Line Interface (CLI) and the 3PAR InForm Management Console. Refer to the 3PAR InForm OS CLI Administrator’s Manual and the 3PAR InForm Management Console Online Help for instructions on how to perform these tasks. 3.2 Local Users Local users are users created on the system and access the system using the InForm CLI or InForm Management Console.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 3.3 Domain Users NOTE: 3PAR Virtual Domains requires a 3PAR Virtual Domains license. For additional information about the license, see 3PAR InForm Software on page 2.7. Local users belonging to a system using 3PAR Virtual Domains are domain users. In addition to being assigned a user class, domain users’ activities are also limited to the domain(s) to which they have privileges.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 3.4 LDAP Users Whereas local users are authenticated and authorized directly on the InServ Storage Server, LDAP users are authenticated and authorized using information from an LDAP server. If multiple InServ Storage Servers are configured to use the same LDAP server in the same way, a user that can access one of the InServ servers can access all of them with the same privileges.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 4 LDAP In this chapter 4.1 Overview 4.1 4.2 LDAP Users 4.3 4.3 LDAP Server Data Organization 4.4 4.4 LDAP and Domains 4.4 4.5 LDAP Authentication and Authorization 4.5 The purpose of this chapter is to provide information about using LDAP with InServ Storage Servers. 4.1 Overview The Lightweight Directory Access Protocol (LDAP) is a standard protocol for communication between LDAP clients and LDAP directory servers.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 there are multiple InServ servers configured to use the same LDAP server in the same way, a single user with access to one InServ server can access all of the environment’s InServ servers with the same privileges. Accessing objects on InServ servers configured to use 3PAR Virtual 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.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 4.1.2 OpenLDAP OpenLDAP is an open source implementation of LDAP directory services developed by the OpenLDAP Project. OpenLDAP includes a server, client library, and tools that are available for a wide variety of operating systems. Different schemas can be used for user and group information with OpenLDAP. For example, the Posix schema is typically used for user and group information in Linux/Unix systems. 4.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 4.3 LDAP Server Data Organization LDAP server data consists of user information, which includes the user’s group associations. Data can be previously existing data used for user account information, or can be data created for specific use with InServ Storage Servers. Data on the LDAP server can be organized in two different ways: ■ As a list of groups associated with each user. ■ As a list of users associated with each group.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide NOTE: 3PAR Virtual Domains requires a 3PAR Virtual Domains license. For additional information about the license, see Optional Software Features on page 2.8. 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.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 4.5.1.2 SASL Binding In addition to simple binding, the InForm OS LDAP client also supports the PLAIN, DIGEST-MD5, and GSSAPI SASL binding mechanisms. Generally, DIGEST-MD5 and GSSAPI are more secure methods of authentication as user passwords are not sent to the LDAP server. NOTE: The SASL mechanism you can use is dependent on your LDAP server configuration.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 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 level privileges for the system. With this process, a user can be authenticated, but not authorized if no group membership exists. In this case, the user is subsequently denied access to the system. 4.5.
3PAR InForm OS Concepts Guide 4.8 LDAP Authentication and Authorization InForm OS Version 2.3.
InForm OS Version 2.3.1 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.4 5.4 Object and Domain Association Rules 5.5 5.5 The Default and Current Domains 5.5 The purpose of this chapter is to explain the relationship between users and 3PAR Virtual Domains. 5.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 NOTE: 3PAR Virtual Domains require a 3PAR Virtual Domains license. For additional information about the license, see 3PAR InForm Software on page 2.7. 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).
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Virtual domains can be grouped into autonomic groups that can be managed as one domain. If you have a group of domains that require the same administrative procedures, it is easier to group those domains into an autonomic group and mange them together. NOTE: Remote Copy requires a 3PAR Remote Copy license. For additional information about the license, see 3PAR InForm Software on page 2.7. 5.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 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.3.1 3PAR InForm OS Concepts Guide 5.4 Object and Domain Association Rules Domains contain basic objects such as CPGs, hosts, and Remote Copy groups, and derived objects such as VVs, LDs, and VLUNs. Objects and their associations with domains must adhere to the following rules: ■ Objects derived from a CPG inherit the domain of that CPG. ■ VVs can only be exported to hosts belonging to the VVs’ domain.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 If you are using the InForm Management Console, the user selects which domain to connect to and there is no default domain, and no domain session. To change domains, InForm Management Console users simply select a new domain from a menu of available domains. 5.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 6 Ports and Hosts In this chapter 6.1 Overview 6.2 6.2 About Ports 6.2 6.3 Port Location Formats 6.3 6.4 Port Target, Initiator, and Peer Modes 6.4 6.5 Active and Inactive Hosts 6.4 6.6 Adding and Removing Hosts 6.5 6.7 Host Personas 6.5 6.8 The Host Explorer Agent 6.8 The purpose of this chapter is to explain the interaction between ports, hosts, and host personas. Ports and Hosts 6.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 6.1 Overview The InServ Storage Server 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 InServ Storage Server are automatically detected. The Fibre Channel port WWNs and iSCSI port iSCSI Names are displayed by the user interfaces. You can also add new WWNs or iSCSI Names for unestablished host paths and assign them to a host before they are physically connected.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 6.2.1 Fibre Channel Ports InServ Storage Servers use Fibre Channel ports to connect controller nodes to hosts and drive cages. For information about controller nodes and drive cages, see Chapter 13, 3PAR InServ Storage Server Hardware. 6.2.2 iSCSI Ports InServ Storage Servers use iSCSI ports to connect controller nodes to hosts. For information about controller nodes, see Chapter 13, 3PAR InServ Storage Server Hardware.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 6.4 Port Target, Initiator, and Peer Modes The InServ Storage Server controller node ports operate in different modes. Depending on the type of port, the port may operate in target, initiator, or peer mode. Fibre Channel ports use the following firmware mode settings: ■ Target mode for ports that connect to hosts and receive commands from those hosts.
InForm OS Version 2.3.1 2 3PAR InForm OS Concepts Guide The InForm OS remembers all volumes exported to the host before it became inactive. It will not unexport the volumes on the port with the missing host. 3 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. 6.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Different host personas have different functions and support different host operating systems. The specific host persona is designated by the host persona number. Depending on the selected host persona number, the following additional capabilities are supported: ■ UARepLun - Sends an unit attention when the LUN list changes due to adding or removing VLUNs.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Table 6-1. Host Personas (continued) Persona Persona Host Operating Additional Number Name System Capabilities 7 HPUX- HP-UX VolSetAddr Legacy 8 AIX-Legacy AIX NACA 9 Egenera Egenera, NetApp SoftInq 10 NetApp Data ONTAP SoftInq ONTAP NOTE: Only the Generic, Generic-ALUA, and Generic-Legacy personas are supported for iSCSI connections. NOTE: The NetApp host operating system requires unique WWNs for hosts in an FC fabric.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 6.8 The Host Explorer Agent The 3PAR Host Explorer agent is a program that runs on a host connected to an InServ Storage Server. The Host Explorer agent runs as a service on Windows and as a daemon on Linux and Solaris operating systems. No license is required to use the 3PAR Host Explorer agent.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 7 Chunklets In this chapter 7.1 Overview 7.1 7.2 Physical Disk Chunklets 7.2 7.3 Spare Chunklets 7.2 The purpose of this chapter is to provide an overview of chunklets. 7.1 Overview Physical disks are divided into chunklets. When a physical disk is admitted to the storage server it is divided into chunklets that become available to the system.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 7.2 Physical Disk Chunklets Physical disks are divided into chunklets, where each chunklet occupies 256 MB of contiguous space. Space on a physical disk is allocated as follows: ■ 256MB of data is reserved for the table of contents (TOC), which contains the internal description of the system. The TOCs on all physical disks in the system contain the same information.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide automatically. Free chunklets are any chunklets that are not already allocated for use by logical disks. ■ 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.
3PAR InForm OS Concepts Guide 7.4 Spare Chunklets InForm OS Version 2.3.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 8 Logical Disks In this chapter 8.1 Overview 8.1 8.2 Logical Disks and Common Provisioning Groups 8.2 8.3 Logical Disk Types 8.2 8.4 RAID Types 8.3 8.5 Logical Disk Size and RAID Types 8.8 8.6 Logical Disk Size and Virtual Volumes 8.9 8.7 Logical Disk Size and Common Provisioning Groups 8.9 The purpose of this chapter is to explain the relationship between logical discs, RAID types, and other InServ Storage Server data layers. 8.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 allocation, growth increments and other logical disk parameters can be set when you create a CPG or modified after creating a CPG. For information about CPGs, see Chapter 9, Common Provisioning Groups. 8.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.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide system during the initial installation and setup of the storage server. Each controller node in the system has a 20 GB logging LD. ■ preserved data logical disks are RAID 10 logical disks used to hold preserved data. Preserved data logical disks are created by the system during the initial installation and setup of the storage system. The size of the preserved data LD is based on the amount of data cache in the system.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 8.4.1 RAID 0 On a RAID 0 logical disk, data is striped across rows of chunklets on different physical disks. The number of chunklets in a RAID 0 set is known as the set size, which is always 1 for a RAID 0 logical disk. The number of sets in a row is known as the row size.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Figure 8-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 8-2. Data Striped Across RAID 1 Sets on a RAID 10 Logical Disk 8.4.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Figure 8-3 shows a RAID 50 logical disk with a set size of 3, and 2 sets in 1 row: Row size Set size* Step size A p (E,F) B E p (A,B) F C p (G,H) D G p (C,D) H I p (I,J) J K p (K,L) L = Chunklet RAID 50 Logical Disk *Parity set p = Parity step Figure 8-3. Data Striped Across RAID 5 Sets on a RAID 50 Logical Disk 8.4.4 RAID Multi-Parity On a RAID Multi-Parity (MP) or RAID 6 logical disk, data is striped across rows of RAID MP sets.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide The following example shows 2 RAID MP sets in one row, the second set is shown below the first set. In the first RAID MP set in the following example, p0 is the parity step for data steps F, L, M, Q, T, V, and X. Figure 8-4 shows a RAID MP logical disk with a set size of 8, and 2 sets in 1 row: Set 1 Row 1 A B D E G H J K M N P Q S T V W C p0 F p1 I p2 L p3 O p4 R p5 U p6 X p7... R2 ...
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 8.5 Logical Disk Size and RAID Types A logical disk is a collection of physical disk chunklets, each 256 MB, that have been arranged as rows of RAID sets. For this reason, the total size of a logical disk is a multiple of the user space within a single logical disk RAID set. For RAID 0 and RAID 1 logical disks, the user space within each RAID set is equal to one chunklet, or 256 MB.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 8.6 Logical Disk Size and Virtual Volumes Rounding up of logical disk size by the system may occur when creating virtual volumes. When you create a virtual volume, the system automatically creates the necessary underlying logical disks to support that volume. When the specified virtual volume size is less than the sum of the logical disks created to support that volume, those logical disks will have some unused space.
3PAR InForm OS Concepts Guide 8.10 Logical Disk Size and Common Provisioning Groups InForm OS Version 2.3.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 9 Common Provisioning Groups In this chapter 9.1 Overview 9.2 9.2 Precautions and Planning 9.3 9.2.1 Growth Increments, Warnings, and Limits 9.3 9.2.2 Growth Increment 9.4 9.2.3 Growth Warning 9.5 9.2.4 Growth Limit 9.5 9.3 System Guidelines for Creating CPGs 9.6 9.4 Volume Types Associated with CPGs 9.7 The purpose of this chapter is to provide planning considerations for Common Provisioning Groups. Common Provisioning Groups 9.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 9.1 Overview A Common Provisioning Group (CPG) creates a virtual pool of logical disks that allows up to 4,095 virtual volumes to share the CPG's resources and allocates space on demand. You can create fully-provisioned virtual volumes and Thinly-Provisioned Virtual Volumes (TPVVs) that draw space from the CPG's logical disk pool. CPGs enable fine-grained, shared access to pooled logical capacity.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 9.2 Precautions and Planning A Common Provisioning Group (CPG) creates a virtual pool of logical disks that allows up to 4,095 volumes to share the CPG's resources and allocate space on demand. However, CPGs still require careful planning and monitoring to prevent them from becoming so large that they set off the system's built-in safety mechanisms.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 9.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 9-1). Table 9-1.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 9.2.3 Growth Warning When the size of the volumes that draw from a CPG reach the CPG’s growth warning, the system generates an alert to notify you of the CPG's increasing size. This safety mechanism provides the opportunity to take early action that may prevent snapshot volumes associated with the CPG from experiencing failures, causing host or application write failures, and exhausting all free space on the system.
3PAR InForm OS Concepts Guide ■ InForm OS Version 2.3.1 For base volumes with a stale snapshots virtual copy policy, new writes will cause snapshot volumes to become invalid (stale). ■ If the volumes that draw from a CPG reach the CPG’s growth limit, the system generates additional alerts to notify you that all logical capacity for the CPG has been consumed. 9.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 9.4 Volume Types Associated with CPGs Depending on the products and features licensed for use on the system, after creating a CPG you can create two types of base volumes that draw from the CPG's logical disk pool: ThinlyProvisioned Virtual Volumes (TPVVs) and fully-provisioned virtual volumes. These two volume types draw from the pool in different ways. For information about TPVVs, see ThinlyProvisioned Virtual Volumes on page 10.4.
3PAR InForm OS Concepts Guide 9.8 Volume Types Associated with CPGs InForm OS Version 2.3.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 10 Virtual Volumes In this chapter 10.1 Overview 10.1 10.2 Virtual Volume Types 10.2 10.2.1 Administrative Volumes 10.3 10.2.2 Fully-Provisioned Virtual Volumes 10.3 10.2.3 Thinly-Provisioned Virtual Volumes 10.4 10.3 Physical Copies 10.6 10.4 Virtual Copy Snapshots 10.7 10.5 Exporting Virtual Volumes 10.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 visible to hosts. You can create physical copies or virtual copy snapshots of virtual volumes for use if the original base volume becomes unavailable. Before creating virtual volumes, you must first create CPGs to allocate space to the virtual volumes. Volumes can be grouped into autonomic groups that can be managed as one volume.
InForm OS Version 2.3.1 ■ 3PAR InForm OS Concepts Guide Administration space, also known as admin space, is the area of the volume that corresponds to logical disk regions in the CPG that track changes to the volume since the previous snapshot was created. The administration space contains pointers to copies of user data in the snapshot space. Administration space is managed by the system, not with the tools you use to manage user and snapshot space.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 10.2.3 Thinly-Provisioned Virtual Volumes With a 3PAR Thin Provisioning license, you can also create Thinly-Provisioned Virtual Volumes (TPVVs). A TPVV uses logical disks that belong to a logical disk pool known as a Common Provisioning Group (CPG). TPVVs associated with the same CPG draw user space from that pool as needed, allocating space on demand in small increments beginning with 256 MB per controller node.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 10.2.3.1 TPVV Warnings and Limits The TPVV volume size limit is 16 TB. When creating a TPVV, you have the option to set an allocation warning threshold and an allocation limit threshold. ■ allocation warning threshold: For volumes capable of allocating space on demand, the user-defined threshold at which the system generates an alert. This threshold is a percentage of the volume's virtual size, the size that the volume presents to the host.
3PAR InForm OS Concepts Guide ◆ InForm OS Version 2.3.1 for a TPVV with read-only snapshots, or when that TPVV is a physical copy or used for Remote Copy, n=2. 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: Allocation warning = percentage 1— 2 • 1 GB per day • 30 days • 100 = 94 % 1024 GB 10.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 10.4 Virtual Copy Snapshots A virtual copy is a snapshot of another virtual volume. You can make virtual copies of base volumes, physical copies, or other virtual copies. Virtual copies are created using copy-on-write techniques available only with the 3PAR Virtual Copy license. Unlike a physical copy which duplicates the entire base volume, a virtual copy only records the changes to the original volume.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 only create read-only copies of a base volume. See Figure 10-1 for an example of alternating read-only and read/write virtual copy relationships. BASE VOLUME (RW) RW=read/write RO=read-only RO RW RO RO RO RO RW RW RW RW RO RO RO RO Figure 10-1. Alternating Read-only and Read/Write Virtual Copies See Figure 10-2 for a more complex example of the possible relationships between a parent base volume and its virtual copies.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 10.4.1.1 Copy-on-Write Function When a virtual volume or snapshot’s source volume is written to, the copy-on-write function preserves the data that is to be overwritten. The data is copied to the snapshot space associated with the original virtual volume before the write operation is completed, and a pointer in the administration space points to the copied data. See Figure 10-3 for an example of a sequence of snapshots.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Each copy of a copy has an additional level added to its name: in this example, the first copy of S1 is S1_0, and a copy of S1_0 is S1_0_0. Unlike the automatic snapshots created for physical copies, these snapshots are not assigned names by the system. NOTE: The naming convention used in the example above is recommended, but it is not enforced by the system. You can name each virtual volume and virtual copy at the time of creation.
InForm OS Version 2.3.1 ■ 3PAR InForm OS Concepts Guide Understanding which virtual copies become stale if the administration space is full and the copy-on-write data cannot be written. A stale snapshot is one that cannot be completely recreated because the most recent changes will not be included. The current snapshot and all its children become stale when a write fails.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 host or hosts. Those volume exports, which are seen as LUNs by the host or hosts, are active VLUNs. A VLUN template can be one of the following types: ■ Host sees allows only a specific host to see a volume. ■ Host set allows any host that is a member of the host set to see a volume. ■ Port presents allows any host on a specific port to see the volume. ■ Matched set allows only a specific host on a specific port to see the volume. 10.5.2.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 10.5.2.4 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. Exporting Virtual Volumes 10.
3PAR InForm OS Concepts Guide 10.14 Exporting Virtual Volumes InForm OS Version 2.3.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 11 Reclaiming Unused Space In this chapter 11.1 Overview 11.1 11.2 Reclaiming Unmapped Logical Disk Space from CPGs 11.2 11.3 Reclaiming Unmapped Logical Disk Space from Volumes 11.3 11.4 Automatically Reclaiming Unused Snapshot Space from Volumes 11.3 11.5 Manually Reclaiming Unused Snapshot Space from Volumes 11.4 11.6 Deleted Volume’s Snapshot Space 11.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Mapping is the correspondence of Logical Disk (LD) regions to the virtual volume regions. Virtual volumes are made up of multiple logical disks, and each logical disk contains regions that are mapped to the virtual volume. All types of volumes are created by mapping data from one or more logical disks to the virtual volume. Figure 11-1 shows how data mapped in regions from logical disks onto a base volume.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide pool may have only a small portion of their regions mapped to existing virtual volumes. However, the logical disk’s unused regions are not available for use by the volumes mapped to the CPG. Compacting the logical disk regions mapped to these volumes may recover and free logical disk space. Compacting a CPG allows you to reclaim space from a CPG that has become less efficient in space usage from creating, deleting, and relocating volumes.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 11.5 Manually Reclaiming Unused Snapshot Space from Volumes You cannot manually remove snapshot and administration space from a Thinly-Provisioned Virtual Volume because the InForm OS automatically removes any unused space.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 12 Enhanced Storage Applications In this chapter 12.1 Overview 12.2 12.2 mySnapshot 12.2 12.3 Dynamic Optimization 12.3 12.4 System Tuner 12.4 12.5 Thin Conversion 12.5 12.6 Thin Persistence 12.7 12.7 Thin Copy Reclamation 12.8 12.8 Virtual Lock 12.8 The purpose of this chapter is to provide an overview of specialized InServ Storage Server features. Enhanced Storage Applications 12.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 12.1 Overview 3PAR 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 3PAR InForm Command Line Interface (CLI) and the 3PAR InForm Management Console to view the licenses currently enabled on your InServ Storage Servers. For a list of default 3PAR InForm Software Suite features and optional features, see 3PAR InForm Software.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 12.3 Dynamic Optimization 3PAR Dynamic Optimization is an optional feature that allows you to improve the performance of virtual volumes without interrupting access. Use this feature to avoid over provisioning for peak system usage by optimizing the layout of your virtual volumes. With 3PAR Dynamic Optimization you can change the virtual volume’s parameters, RAID levels, set sizes, and disk filters by associating the virtual volume with a new CPG.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 the failure of a drive cage because its RAID sets use chunklets from different drive cages. A volume with a magazine-level availability can tolerate the failure of a drive magazine because its RAID sets use chunklets from different magazines. As applications and business requirements change, it may be desirable to non-disruptively alter the availability characteristics of existing virtual volumes. ■ Volume service level changes.
InForm OS Version 2.3.1 ■ 3PAR InForm OS Concepts Guide The physical disk is a bad disk. A bad disk typically has unusually high maximum service times when compared to other disks. 3PAR System Tuner allows you to: ■ Perform physical disk performance tuning on an entire InServ Storage Server or on a specified subset of disks. ■ Set performance thresholds for physical disk tuning. ■ Identify and relocate under-performing chunklets.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 12.5.1 Assessment Before converting your volumes you must determine the benefits of the conversion process. The potential benefits of zeroing free space prior to copying or migrating the data to a TPVV depends on the amount of allocated but unused space. If there is relatively little unused space in the allocated physical space then there is little benefit to zeroing the free space to recapture this relatively small amount of space.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide NOTE: Converting fully-provisioned volumes to Thinly-Provisioned Virtual Volumes (TPVVs) with the Thin Conversion feature requires an InServ F-Class or TClass Storage Server, a 3PAR Thin Provisioning license, and a 3PAR Thin Conversion license. Contact your 3PAR representative for more information. 12.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 12.7 Thin Copy Reclamation Thin Copy Reclamation is an optional feature that reclaims space when snapshots are deleted from an InServ Storage Server. As snapshots are deleted, the snapshot space is reclaimed from a Thinly-Provisioned Virtual Volume (TPVV) or fully-provisioned virtual volume and returned to the CPG for reuse by other volumes. Deleted snapshot space can be reclaimed from virtual copies, physical copies, or remote copies.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 13 3PAR InServ Storage Server Hardware In this chapter 13.1 Overview 13.1 13.2 Identifying Storage Server Components 13.2 13.3 Physical Disks 13.4 13.4 Drive Cage Models 13.6 13.5 Controller Node Overview 13.10 The purpose of this chapter is to provide an overview of InServ Storage Server hardware platforms and components. 13.1 Overview 3PAR InServ® Storage Servers are available in a variety of hardware configurations.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 WARNING: The servicing of 3PAR hardware is to be performed by qualified technicians who are authorized by 3PAR to install InServ Storage Servers and their hardware components. Authorized technicians include 3PAR field engineers, Value Added Resellers (VARs), certified self-maintaining customers, and, in some cases, authorized third-party field technicians.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Front Fascia Drive Magazines Drive Chassis Bezel Drive Cage FC-AL Modules Controller Nodes Storage Server Backplane with Controller Nodes Battery Tray Service Processor Main Power Cords Leveling Foot 0582_L_R2 Figure 13-1. Front view of an InServ T-Class Storage Server Identifying Storage Server Components 13.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Rear Door Drive Cage Power Supplies Lock Controller Node Power Supplies Hinge Battery Backup Units (BBUs) Power Distribution Units (PDUs) 0212_L_R1 Figure 13-2. Rear View of an InServ T-Class Storage Server 13.3 Physical Disks A physical disk is a hard drive. Each physical disk is mounted on a drive magazine or in a drive module. The drive magazines and modules are located in drive cages in 3PAR InServ Storage Servers.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide In a DC3 drive cage, each plug-in drive module holds a single disk numbered 0 through 15. The DC3 drive cage contains 16 drive bays and accepts up to 16 drive magazine modules for a maximum of 16 physical disks in each drive cage. See Figure 13-4. To learn more about drive cages, see Chapter 13, 3PAR InServ Storage Server Hardware. Front 3 2 1 0 Rear 0600_L_R1 Figure 13-3. DC2 and DC4 Drive Magazine with Physical Disks 0366_L_R1 Figure 13-4.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 13.3.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. When replacing the physical disk, the chunklets from all of the disks in the drive magazine must be managed during the replacement procedure.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0230_L_R1 Figure 13-5. DC2 Drive Cage Drive Magazines 1 2 3 4 5 6 7 8 9 Ports A1 B1 Ports B0 A0 0 0588_L_R2 Figure 13-6. DC4 Drive Cage Drive Cage Models 13.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 13.4.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.3.1 3PAR InForm OS Concepts Guide 13.4.3 DC3 Drive Cage The DC3 drive cage contains 16 drive bays at the front, each accommodating the appropriate plug-in drive magazine module. The 16 drive bays are arranged in four rows of four drives. Figure 13-8 shows the front view of a DC3 drive cage. 0148_L_R2 Figure 13-8. DC3 Drive Cage (Front View) 13.4.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 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 13-10): Node Fibre Channel Adapter Port Drive Chassis Drive Cage Port (Cxx.x) Nx:Sx:Px <–> (Cxx.x) Dx:Px Cabinet and Bay (Node Chassis Cabinet) Cabinet and Bay (Drive Chassis Cabinet) Figure 13-10.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Table 13-1. Storage Server and Controller Node Model Compatibility Storage Server Model Controller Node Model InServ S400 and S800 S-Class InServ T400 and T800 T-Class InServ E200 E-Class InServ F200 and F400 F-Class The number of controller nodes each storage server model can accommodate is summarized in Table 13-2. Table 13-2.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Table 13-3. Storage Server Models and Number of Ports Storage Server Model Number of FC Ports Number of iSCSI Ports InServ E200 and F200 0-8 0-4 InServ F400 0-16 0-8 13.5.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 0 1 2 3 4 5 6 7 0586_L_R1 Figure 13-11. 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. Controller Node Overview 13.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 13.5.3 E-Class and F-Class Controller Node Numbering InServ E-Class and F-Class Storage Servers have a different number of controller nodes depending on the storage server model. ■ 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.
InForm OS Version 2.3.1 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.3 The purpose of this chapter is to provide information about using the 3PAR SNMP agent and the SNMP interface. 14.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 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.3.1 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.3.1 This is the authoritative identification of the notification currently being sent. This variable occurs as the second varbind in every SNMPv2 trap. ■ 3PAR MIB This is the 3PAR proprietary MIB. 14.4.2.1 MIB-II MIB-II defines several groups of standard information to be provided by the agent. The 3PAR SNMP agent supports only the system group objects. Table 14-1 on page 14.4 summarizes the MIB-II information provided by the 3PAR SNMP agent.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 14.4.2.2 Exposed Objects The 3AR SNMP agent supports MIB-II system group objects. This section describes each of those objects in detail. 14.4.2.2.1 System Description Access: Read-only MIB definition: sysDescr Data type: Display string (max. 255 characters) Default value: 3PAR InServ Description: Identifies InServ Storage Server model, system ID, serial number and InForm OS version of the master node.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 14.4.2.2.4 System Contact Information Access: Read/write MIB definition: sysContact Data type: Display string (max. 255 characters) 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 InServ storage system. This value can be changed via the manager at any time. 14.4.2.2.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Table 14-2. Contents of the alertNotify trap Object Descriptor Description Access component Tells you which system hardware, software, or logical Read-only component caused the alert or alert state change. details Detailed description of the alert or alert state Read-only change, displayed as an alert string (for example: PR table is corrupt).
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 Table 14-2. Contents of the alertNotify trap (continued) Object Descriptor Description Access messageCode Code that identifies the specific type of alert or alert Read-only state change. For example, the message code for the alert state change is 1245186. For alerts, use the message code in referring to the InForm OS Messages and Operator’s Guide for instructions on prescribed operator actions.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide NOTE: If you receive a trap with messageCode == 1245186, this is to notify you that an alert has changed state. In order to find out which alert has changed state, you must extract the alert ID from the id trap field. An alert status change event is not an alert. It notifies you that an alert has changed status (e.g., from New to Resolved by System).
3PAR InForm OS Concepts Guide 14.10 The 3PAR SNMP Agent InForm OS Version 2.3.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 15 The 3PAR InForm CIM API In this chapter 15.1 Overview 15.2 15.2 About SMI-S 15.2 15.3 About the WBEM Initiative 15.3 15.4 3PAR InForm CIM Support 15.4 15.4.1 Standard Compliance 15.4 15.4.2 SMI-S Profiles 15.4 15.4.3 Supported Extensions 15.4 15.4.4 CIM Indications 15.4 The purpose of this chapter is to provide an overview of the 3PAR InForm CIM application programming interface (API). The 3PAR InForm CIM API 15.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 15.1 Overview This chapter describes the 3PAR InForm CIM Application Programming Interface (API), 3PAR’s industry-standard API based on SNIA’s Storage Management Initiative Specification (SMI-S). For detailed information about the 3PAR InForm CIM API, refer to the 3PAR CIM API Programming Reference. 15.2 About SMI-S SMI-S enables management of storage area networks (SANs) in a heterogeneous multi-vendor environment.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide 15.3 About the WBEM Initiative SMI-S is based on the Web-Based Enterprise Management (WBEM) Initiative, which is defined by the Distributed Management Task Force (DMTF). WBEM is a set of management and Internet standard technologies developed to unify the management of distributed computing environments.
3PAR InForm OS Concepts Guide InForm OS Version 2.3.1 15.4 3PAR InForm CIM Support The following sections provide information about the 3PAR InForm CIM API provided with InForm OS Version 2.3.1. 15.4.1 Standard Compliance ■ The 3PAR InForm CIM Server supports SMI-S version 1.1.0. ■ The 3PAR InForm CIM API passes SNIA-CTP conformance. For additional information, see http://www.snia.org. 15.4.2 SMI-S Profiles SMI-S defines a number of profiles that are used to manage elements of a SAN.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Glossary 3PAR Virtual 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 and SQL Server backups and restores. 3PAR software component that provides volume security at logical and physical levels.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide alert Volumes (TPVVs) and fully-provisioned virtual An alert is a system event that requires the volumes. immediate attention of the user, and may also require user intervention. See also event. battery backup unit (BBU) A unit containing two batteries.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide not ready). The chunklet is placed in logging control cache mode, where data that is supposed to be written Memory modules that support the to the chunklet is instead written to a log. If the microprocessors located in a controller node. chunklet becomes available again, the system places the chunklet in playback mode, where the data is read from the log and written to the appropriate chunklet.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide CPG template DC2 drive cage Common provisioning group template.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide drive cage FCAL module event An interface module, located in a drive chassis, A normal system occurrence. connecting a drive cage to a controller node or to another drive cage. drive chassis Enclosure that takes up 4U of an EIA-standard rack, used for housing the drive cage(s). drive chassis cabinet In a multi-cabinet storage server, any cabinet that is connected to a node cabinet but does not contain controller nodes.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide transferring data via the network. See also 3PAR host definition Remote Copy. The name of the host plus a list of the WWNs grow To expand a base volume manually by increasing the user space, snapshot administration space, or snapshot data space. growth increment that make up the host. A host can have a host definition even though it is not physically connected to a storage server. host port See target port.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide L logical disk pool LD See Common Provisioning Group. See logical disk. logical unit number LD template See LUN. Logical disk template.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide message code O A keycode that identifies a system alert. original parent base volume midplane The original base volume from which a series of See storage server backplane. virtual and/or physical copies has been created.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide physical copy resynch data. The logical capacity of the preserved data See resynchronize. logical disks is equal to the sum of all data cache physical disk A dual-ported Fibre Channel disk mounted onto memory of the system. primary path a drive magazine. Connection between a controller node initiator physical parent port and a physical disk that is used by default. The source volume for a physical copy.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide rack unit (U) region The standard unit of height for an EIA-standard A subdivision of a logical disk or virtual volume. rack or components housed in an EIA-standard The size of a region is always a multiple of 32 rack: equivalent to 1.75 in. (4.45 cm). MB. RAID registered state change notification (RSCN) Stands for redundant array of independent disks.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide safety breaker SFP The device used to power on and power off the See small form-factor pluggable transceiver. power distribution unit. The safety breaker also prevents power surges in the AC line from damaging a storage server. second virtual volume backup node The controller node that takes over for the virtual volume backup node if the virtual volume node fails. snapshot A virtual or physical copy of a virtual volume.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Snapshots virtual copy policy halts writing data the InForm Management Console and InForm to the base volume so as to prevent loss of sync CLI. between the volume and any snapshots. See also virtual copy policy and no stale snapshots.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide TOC V See table of contents. virtual copy TPVV A snapshot created using the copy-on-write See Thinly-Provisioned Virtual Volume. technique. See also 3PAR Virtual Copy. TSIH virtual copy policy See Target Session Identifying Handle. Determines the course of action should a volume's snapshot administration space or U snapshot data space become depleted. See also U stale snapshots and no stale snapshots. See rack unit.
InForm OS Version 2.3.1 VLUN Stands for virtual-LUN. A VLUN is a virtual 3PAR InForm OS Concepts Guide WWN See World-Wide Name. volume-LUN pairing expressed as either an active VLUN or as a VLUN template. See also active Z VLUN, VLUN template. zero fill To fill unused storage space with the VLUN template representation of the character denoting “0”. A rule that sets up the association between the port, or LUN-host-port combination.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Index 3PAR Domains 4.5, 5.2 C 3PAR LDAP client 4.1 cautions, about 1.6 chapter overviews 1.4 A Active Directory chunklets 2.4 free, defined 7.3 Kerberos server 4.2 Active Directory LDAP 4.2 Active Directory LDAP server 4.2 CLI (command line interface) privilege levels 3.2 conventions admin volume 10.3 advisories, conventions 1.6 alerts advisories 1.6 conventions, typographical 1.5 copy-on-write when spare and free chunklets are used up 7.
3PAR InForm OS Concepts Guide chunklets 2.4 documentation, related 1.3 domain InForm OS Version 2.3.1 L LDAP Active Directory 4.2 default domain 5.5 authentication 4.5 derived objects 5.2 authorization 4.5, 4.6 no domain 5.3 binding SASL 4.2 specified domain 5.3 types 5.3 data organization 4.4 types and user class 5.3 group-to-privilege mapping 4.6 user class types 5.3 ldapsearch command 4.4 users 3.3 ldp.exe 4.4 users and their privileges 5.4 OpenLDAP 4.2, 4.3 with LDAP 4.2 overview 4.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide overview 11.2 stale definition 10.11 mapping parameters 4.6 tree view of 10.9 N naming conventions, virtual volumes 10.10 notes, about 1.6 SNMP (Simple Network Management Protocol) 14.1 T typographical conventions 1.5 O OpenLDAP 4.2, 4.3 overviews of chapters 1.4 U user accounts, setting up 3.1 P user interfaces 1.2 performance consequences of virtual volumes 10.10 user privileges in domains 5.4 physical disks 2.4, 13.4 chunklets 2.
3PAR InForm OS Concepts Guide IX.4 Index InForm OS Version 2.3.
InForm OS Version 2.3.1 3PAR InForm OS Concepts Guide Revision History Release Level Revision Summary 320-200112 Rev A First release of this document to support the release of InForm OS October 2009 Version 2.3.1. 320-200112 Rev B Second release of this document to support the release of InForm OS February 2010 Version 2.3.1 MU1. Revision History RH.
3PAR InForm OS Concepts Guide RH.2 InForm OS Version 2.3.
