Error message

  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Notice: Trying to access array offset on value of type int in element_children() (line 6489 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).
  • Deprecated function: implode(): Passing glue string after array is deprecated. Swap the parameters in drupal_get_feeds() (line 394 of /home1/dezafrac/public_html/ninethreefox/includes/common.inc).

7

3par inserv physical reference manual

LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF

File Name:3par inserv physical reference manual.pdf
Size: 4035 KB
Type: PDF, ePub, eBook

Category: Book
Uploaded: 22 May 2019, 14:33 PM
Rating: 4.6/5 from 570 votes.

Status: AVAILABLE

Last checked: 10 Minutes ago!

In order to read or download 3par inserv physical reference manual ebook, you need to create a FREE account.

Download Now!

eBook includes PDF, ePub and Kindle version

✔ Register a free 1 month Trial Account.

✔ Download as many books as you like (Personal use)

✔ Cancel the membership at any time if not satisfied.

✔ Join Over 80000 Happy Readers

3par inserv physical reference manualFor example, the configured used and free space information for the storage system. You can obtain performance and storage utilization statistics on the following storage objects: Controller Nodes Common Provisioning Groups(CPGs) Disk Cages and applicable interfaces, power supplies, and fans Physical Disks Logical Disks Ports Virtual Volumes The probe configuration is available only through the Admin Console. Contents Revision History This section describes the history of the revisions for this probe.: Support case(s) may not be viewable to all customers. Support case numbers 816725, 716511 GA August 2017 Fixed Defect: When a volume listed in the system is renamed, the probe displayed both the renamed as well as the original volume. Support case number 610470 GA July 2017 Fixed Defects: The probe intermittently generated incorrect alarms. Support case number 460996 Improved the probe performance. Support case number 433600 The probe did not validate the port number when connecting to the storage system. Support case number 229882 GA November 2016 GA April 2016 The probe configuration is available ONLY through Admin Console GUI and NOT through the Infrastructure Manager (IM) GUI. The probe includes the standard static alarm threshold parameters. - June 2015 You must start the CIM server on your system to enable communication between the probe and the HP 3PAR storage system. Update the NAS Probe Alarms are classified by their subsystem ID, identifying which part of the system the alarm relates to. These subsystem IDs are kept in a table maintained by the NAS probe. If you are working with CA UIM 8.2, you must add the following subsystem IDs manually using the NAS Raw Configuration menu. However, if you have upgraded to CA UIM 8.31 or later, then you do not have to manually add the following subsystem IDs: Click Subsystems. Add the new key name and value. Repeat this process for all of the required subsystem IDs.http://foundrygate.com/userfiles/4-star-40-manual.xml

    Tags:
  • 3par inserv physical reference manual, 3par inserv physical reference manual pdf, 3par inserv physical reference manual download, 3par inserv physical reference manual free, 3par inserv physical reference manual online.

Ensure that you enter the key names as-is including the period (.) in the end for correct mapping. The term “Broadcom” refers to Broadcom Inc. For each asset type acquired by Cloud Insights, the most common terminology used for this asset is shown. When viewing or troubleshooting this data collector, keep the following terminology in mind: The default is 40 minutes. The default is 300 seconds. Provider initialization failed. Try changing the array name. When communication from the SP to the node If the process takes longer than twenty minutes, problems When complete, the node reboots. This is designed to be a quick reference of the commands available for use. Notify me of new posts by email. Learn how your comment data is processed. Showing recent items. You interact with it in exactly the same way you would a physical 3Par i.e. via the HP 3PAR Management Console or remote CLI. Most of the major features including AO, DO, snapshots, exporting virtual volumes and even remote replication (if you have 2 instances of the simulator) are supported. I have covered the high level steps to install the simulator to give you a feel for the process below, for detailed step by step instructions refer to the release notes that come with the simulator. The first NIC will be the IP you use to manage the device when using the management console or CLI. The second you will not need unless you are using RCIP. The third will be connected to a local private network allowing the 3 VM’s to talk to each other The default choices are:Was wondering about updating the InServ. It is not currently possible to run an upgrade on the simulator. You cannot create a LAN segment network. Creating a private network (with no host connection and manually configured 192.168.101.0 network) didn?t work. The problem is that after step 1 “Simulator Cluster Node configuration” on both nodes after reboot the network is not working and step 2 fails with an error (cluster is not formed).http://www.tsjikatilo.be/UserFiles/4-steps-of-manual-handling.xml What did you do to fix this. I have set it up as per the reference guide. I’ve tried it on two different PCs now and it just doesn’t work for me. VMware workstation is supported, just try following the instructions carefully I’ve got v1.2 but you have to change the system date to pre feb 2014 on the host which is a pain. I am running V2.0 I see you stated to contact Ivan on twitter. DM’s aren’t possible if Ivan isn’t following me. With that being the case, is it okay to ask him via tweet. Just want to make sure that I won’t cause any problems by asking him that way. I followed the steps in the pdf. When I’m at the Out of the box steps, it takes a couple minutes and it gives a message saying Cannot create admin volume. If you choose more than 48 disks it will not work. Try choosing one of the default cage options form the enclosure VM eg 1. 1 cage, 24 HDDs 1 DCN1 cage with 24 FC drives I redid about 3 times, always the same things, and it worked.Really practical to play with it since I don’t have a 3par anymore. The ESD seems to have come up and now I have done the simulator step where I choose the node number and assign it a serial number. The nodes reboot and they give my the following error message: Suggest giving it another go I am going to take an exam next week from 3PAR. So I would like to learn some hads-on. Thank you in advance, Flaszkan Ella Please read the article again, the instructions are in thereyou need to follow Ivan on twitter and request. Good luck with the Exam! I hope he will answer. Flaszkan Not just asking you to trust it on first use? I am getting the same error. Access is via connecting on Twitter, read the article again and you will see all the info Can you please paste the here to download it. The Simulator is accessed via Twitter, please read through the above post for details Is it possible to expose iSCSI? These are only used for the fake hosts to connect to.http://www.drupalitalia.org/node/67607 If you are struggling with an error suggest, deleting the VM’s and carefully following the instructions again from the start again. I configured an ipadresse for esd and can login via putty. But can’t login trought the cli or management console? I forgot to ran the OOTB setup ?? I ran it, now I can connect en start to play. Thnx I’ve also tried to find it on the HPE website but only yhe P6000 EVA Simulator shows up. It is currently just available to partners. I will update the post if this changes again. Thank you for the update. Please contact your local HPE representative. However, I am getting this error “Trying to build up link to node 0” and after that, no positive results. Please guide how to resolve this. If this does not work I would suggest starting again following each step carefully.Please let me know what might have gone wrong. Learn how your comment data is processed. To browse Academia.edu and the wider internet faster and more securely, please take a few seconds to upgrade your browser. You can download the paper by clicking the button above. Related Papers HPE 3PAR StoreServ Architecture By Gabriel Martinez Technical white paper HP 3PAR StoreServ Architecture Table of contents By arbnor mehana READ PAPER Download pdf. Fixed issue when there are more then 150 physical disks. Is works on the commandline but not in the Nagios check.There are failed VVs. There are degraded VVs. There are failed LDs. There are degraded LDs.I tried with root and nagios but always the same problem. Not perfect, but it does the job.Very easy to implement using installation guide provided. All other servicemarks and trademarks are the property of their respective owner. The files and information on this site are the property of their respective owner(s). Nagios Enterprises makes no claims or warranties as to the fitness of any file or information on this website, for any purpose whatsoever. In fact, we officially disclaim all liability.https://asidicelabiblia.com/images/3pj-manual.pdf We do, however, think these community contributions are pretty damn cool. All rights reserved. Most of the time you will never require this but on occasion during a power outage or planned Datacenter shutdown the need could arise to turn on and off your 3PAR storage system. Enjoy the process after the jump. Using improper tools can result in damage to the storage system. Attach the grounding strap clip directly to an unpainted surface of the rack. If the system was powered off abruptly, powering on could take considerably longer. This can seriously impact host access to data. Thin provisioning allows the array to allocate storage only when it is used. A space saving in excess of 50 is quite common. The rest of the storage does not need to be installed until it is going to be used; on some systems the space is never completely used, and the extra storage never needs to be purchased at all. This in turn can cut energy consumption and the production of greenhouse gasses while saving on capacity and energy costs. Also, when existing data is erased correctly, space can be reclaimed and will be reused in preference to requesting additional storage space. No disk is overworked in comparison to another, so no maintenance “hot spots”. This is particularly good for virtualised server infrastructures such as VMWare. You can reject cookies by changing your browser settings. Begin Installation Step 12. Synchronize Backups and Tape Libraries Step 11. Finish Working with Wizard Migrating Configuration Database Backup About Backup How Backup Works Backup Architecture Backup Chain Backup Methods Forever Forward Incremental Backup Forward Incremental Backup Reverse Incremental Backup Switching Between Backup Methods Active Full Backup Synthetic Full Backup How Synthetic Full Backup Works Backup Chain Transformation Short-Term Retention Policy Forever Forward Incremental Backup Retention Policy Forward Incremental Backup Retention Policy Reverse Incremental Backup Retention Policy Retention Policy for Deleted Items Removal of Restore Points Long-Term Retention Policy (GFS) Assignment of GFS Flags Removal of GFS Flags Per-VM Backup Files Retention for Per-VM Backup Files Changed Block Tracking Data Compression and Deduplication Data Exclusion VMs and VM Disks Deleted File Blocks (BitLooker) Swap Files VM Guest OS Files VMware Tools Quiescence Combined Approach Guest Processing Runtime Coordination Process Application-Aware Processing Pre-Freeze and Post-Thaw Scripts Transaction Log Truncation Copy-Only Backup VM Guest OS File Indexing Veeam Backup Catalog How VM Guest OS File Indexing Works Persistent VSS Snapshots Microsoft SQL Server Log Backup Transaction Log Backup Jobs How Microsoft SQL Server Log Backup Works Retention for Transaction Log Backups Log Shipping Servers Transaction Log Backup Statistics Support for AlwaysOn Availability Groups Oracle Log Backup Archived Log Backup Jobs How Oracle Archived Log Backup Works Retention for Archived Log Backup Log Shipping Servers Archived Log Backup Statistics Backup Job Scheduling Automatic Startup Schedule Job Retry Backup Window Manual Start of Backup Jobs Manual Stop of Backup Jobs Health Check for Backup Files Compact of Full Backup File Resume on Disconnect Snapshot Hunter How Snapshot Hunter Works Creating Backup Jobs Before You Begin Step 1. Launch New Backup Job Wizard Step 2. Specify Job Name and Description Step 3. Select VMs to Back Up Step 4. Exclude Objects from Backup Job Step 5. Define VM Backup Order Step 6. Specify Backup Storage Settings Step 7. Specify GFS Retention Policy Step 8. Specify Advanced Backup Settings Backup Settings Maintenance Settings Storage Settings Notification Settings vSphere Settings Integration Settings Script Settings Step 9. Specify Secondary Target Step 10. Specify Guest Processing Settings Application-Aware Processing Microsoft SQL Server Transaction Log Settings Oracle Archived Log Settings VM Guest OS File Exclusion Pre-Freeze and Post-Thaw Scripts VM Guest OS File Indexing Step 11. Define Job Schedule Step 12. Finish Working with Wizard Performing Active Full Backup Quick Backup Retention Policy for Quick Backups Performing Quick Backup Importing Backups Manually Importing Encrypted Backups Importing Transaction Logs Importing Backup Files from Scale-Out Backup Repositories Exporting Backups Performing Export Step 1. Launch New Export Wizard Step 2. Select Restore Points to Export Step 3. Specify Export Reason Step 4. Finish Working with Wizard Viewing Session Statistics Managing Backups Viewing Properties Removing from Configuration Deleting Backups from Disk Deleting Backups from Object Storage Removing Missing Restore Points Managing Jobs Editing Job Settings Cloning Jobs Disabling and Removing Jobs Starting and Stopping Jobs Starting and Stopping Transaction Log Backup Jobs Reconfiguring Jobs with Microsoft SQL Server VMs Reporting Viewing Real-Time Statistics Viewing Job Session Results Viewing Job and Job Session Reports Replication About Replication How Replication Works Replication Architecture Replication Scenarios Replication Chain Changed Block Tracking Advanced Replication Technologies Replica from Backup How Replica from Backup Works Replica Seeding Replica Mapping Network Mapping and Re-IP Creating Replication Jobs Before You Begin Step 1. Launch New Replication Job Wizard Step 2. Specify Job Name and Description Step 3. Select VMs to Replicate Step 4. Specify Data Source Step 5. Exclude Objects from Replication Job Step 6. Define VM Replication Order Step 7. Specify Replica Destination Step 8. Create Network Map Table Step 9. Configure Re-IP Rules Step 10. Specify Replication Job Settings Step 11. Specify Advanced Replica Settings Traffic Settings Notification Settings vSphere Settings Integration Settings Script Settings Step 12. Specify Data Transfer Settings Step 13. Define Seeding and Mapping Settings Step 14. Specify Guest Processing Settings Application-Aware Processing Transaction Log Settings: Microsoft SQL Server Transaction Log Settings: Oracle VM Guest OS File Exclusion Pre-Freeze and Post-Thaw Scripts Step 15. Define Job Schedule Step 16. Finish Working with Wizard Managing Replicas Viewing Replica Properties Rescanning Replicas Removing from Configuration Deleting from Disk Replica Failover and Failback Replica Failover Performing Failover Before You Begin Step 1. Launch Failover Wizard Step 2. Select VMs Step 3. Select Restore Point Step 4. Specify Failover Reason Step 5. Review Summary and Finish Working with Wizard Permanent Failover Performing Permanent Failover Failover Plan Creating Failover Plans Before You Begin Step 1. Launch New Failover Plan Wizard Step 2. Specify Failover Plan Name and Description Step 3. Select VMs Step 4. Define VM Failover Order Step 5. Set Time Delay Step 6. Review Summary and Finish Working with Wizard Running Failover Plans Undoing Failover by Failover Plans Planned Failover Performing Planned Failover Before You Begin Step 1. Launch Planned Failover Wizard Step 2. Select VMs Step 3. Specify Failover Reason Step 4. Review Summary and Finish Working with Wizard Undo Failover Undoing Failover Replica Failback Failback on VSAN Quick Rollback Performing Failback Before You Begin Step 1. Launch Failback Wizard Step 2. Select VM Replicas to Fail Back Step 3. Select Failback Destination Step 4. Select Target Host Step 5. Select Target Resource Pool Step 6. Select Target Datastore Step 7. Select Target Folder Step 8. Select Target Network Step 9. Map VM Replica to Restored VM Step 10. Review Summary and Finish Working with Wizard Commit Failback Committing Failback Undo Failback Undoing Failback VeeamZIP Creating VeeamZIP Backups Backup Copy About Backup Copy How Backup Copy Works Backup Copy Architecture Backup Copy Modes Backup Copy Intervals Restore Point Selection Transformation Processes Backup Copy Window Retention Policy for Backup Copy Jobs Simple Retention Policy GFS Retention Policy Methods for Archive Backups Creation Retention Policy for Active Full Archive Backups Switching Between Synthetic and Active Full Modes GFS Cycles Regular Backup Cycle Weekly Backup Cycle Synthetic Weekly Full Backups Active Weekly Full Backups Restore Point Selection for Weekly Backup (Synthetic Method) Monthly, Quarterly and Yearly Backup Cycles Archive Full Backups per GFS Cycle Deleted Items Retention Health Check for Backup Files Compact of Full Backup File Backup Copy Job Mapping Creating Seed for Backup Copy Job Active Full Backup Copies Automatic Job Retries Creating Backup Copy Jobs for VMs and Physical Machines Before You Begin Step 1. Launch New Backup Copy Job Wizard Step 2. Specify Job Name and Copy Mode Step 3. Select Workloads to Process Step 4. Exclude Objects from Backup Copy Job Step 5. Select Source Backup Repositories Step 6. Define Processing Order Step 7. Define Backup Copy Target Step 8. Map Backup File Step 9. Specify Advanced Settings Maintenance Settings Storage Settings RPO Monitor Settings Notification Settings Scripts Settings Step 10. Specify Data Path Settings Step 11. Define Backup Copy Window Step 12. Apply Parameters Connecting to Existing Virtual Lab Editing and Deleting Virtual Labs SureBackup Job SureBackup Job Processing Creating SureBackup Job Before You Begin Step 1. Launch New Sure Backup Job Wizard Step 2. Specify Job Name and Description Step 3. Select Virtual Lab Step 4. Select Application Group Step 5. Link Backup or Replication Job Step 6. Specify Recovery Verification Options and Tests Step 7. Specify Additional Job Settings Step 8. Specify Job Schedule Step 9. Review Job Summary and Finish Working with Wizard Starting and Stopping SureBackup Job Viewing Recovery Verification Job Statistics Creating SureBackup Session Reports XML Files with VM Roles Description Manual Recovery Verification SureReplica How SureReplica Works Replica Recovery Verification Tests Application Group Virtual Lab Configuration Basic Single-Host Virtual Labs Advanced Single-Host Virtual Labs Limitations of Single-Host Virtual Labs Advanced Multi-Host Virtual Labs Isolated Networks on DVS Port Groups and VLAN IDs SureBackup Job for VM Replicas SureBackup Job for VM Replicas Processing On-Demand Sandbox On-Demand Sandbox for Storage Snapshots Mixed Scenarios Configuring On-Demand Sandbox Data Recovery Instant VM Recovery Performing Instant VM Recovery of Workloads to VMware vSphere VMs Before You Begin Step 1. Launch Instant VM Recovery Wizard Step 2. Select Workloads Step 3. Select Restore Point Step 4. Select Restore Mode Step 5. Specify Destination for Restored VMs Specifying Destination for One VM Specifying Destination for Multiple VMs Step 6. Select Destination for Virtual Disk Updates Step 7. Configure Helper Appliance Step 8. Specify Secure Restore Settings Step 9. Specify Restore Reason Step 10. Verify Instant VM Recovery Settings Step 11. Finalize Instant VM Recovery Instant VM Disk Recovery Performing Instant VM Disk Recovery Before You Begin Step 1. Launch VM Disk Recovery Wizard Step 2. Select Source VM Step 3. Select Restore Point Step 4. Select Virtual Disk to Restore Step 5. Specify Secure Restore Settings Step 6. Specify Restore Reason Step 7. Verify Recovery Settings Step 8. Finalize Instant VM Disk Recovery Entire VM Restore Quick Rollback Restoring Entire VM Before You Begin Step 1. Launch Full VM Restore Wizard Step 2. Select VMs Step 3. Select Restore Point Step 4. Select Restore Mode Step 5. Select Target Host Step 6. Select Target Resource Pool Step 7. Select Target Datastore Step 8. Select Target Folder and Change VM Settings Step 9. Specify Network Mapping Step 10. Specify Secure Restore Settings Step 11. Specify Staged Restore Settings Step 12. Specify Restore Reason Step 13. Start Restore Process Secure Restore How Secure Restore Works Antivirus XML Configuration File Viewing Malware Scan Results Staged Restore vCloud Director Support Viewing vCloud Director VMs Backup and Restore of vApps Backup of vCloud Director VMs Data to Back Up vCD Backup Jobs Performing Backup of vCloud Director VMs Creating VeeamZIP Files for vCloud Director VMs Restore of vCloud Director VMs Restoring Regular and Standalone VMs to vCloud Director Restoring Linked Clone VMs to vCloud Director Performing Instant VM Recovery for VMs Restoring VMs with Instant VM Recovery into vCloud vApp Before You Begin Step 1. Launch vCloud Instant VM Recovery Wizard Step 2. Select Restore Point Step 3. Select Restore Mode Step 4. Select Destination for Restored VM Step 5. Select Destination for Virtual Disk Updates Step 6. Select Destination Network Step 7. Specify Secure Restore Settings Step 8. Specify Restore Reason Step 9. Verify Instant VM Recovery Settings Step 10. Finalize Instant VM Recovery Restoring VMs with Instant VM Recovery into vSphere infrastructure Restoring vCloud vApps Step 1. Launch Full vApp Restore Wizard Step 2. Select vApp to Restore Step 3. Select Restore Point Step 4. Select Restore Mode Step 5. Select vApp Location Step 6. Select Destination Network Step 7. Select Template to Link Step 8. Select Storage Policy and Datastores Step 9. Specify Secure Restore Settings Step 10. Specify Restore Reason Step 11. Verify Recovery Settings and Finish Working with Wizard Restoring VMs into vCloud vApp Before You Begin Step 1. Launch vCloud Full VM Restore Wizard Step 2. Select VMs to Restore Step 3. Select Restore Point Step 4. Select Restore Mode Step 5. Select VM Location Step 6. Select Destination Network Step 7. Select Template to Link Step 8. Select Storage Policy and Datastores Step 9. Specify Secure Restore Settings Step 10. Specify Restore Reason Step 11.Then use the New HPE Primera (3PAR) wizard to add the storage system. Launch the New HPE 3PAR StoreServ Storage wizard Specify the HPE 3PAR Web Services API address Specify credentials Specify access options Apply settings Finish working with the wizard. Use this document in conjunction with the HP 3PAR Systems Assurance and Pre-Installation Site Planning Guide that details specific system configuration and installation information for your storage system and operating site. The information in this manual is intended for use by HP customers, in conjunction with the advice and assistance of an HP Sales Representative or Systems Engineer, for the purpose of planning an HP 3PAR Storage system installation. The installation of HP 3PAR Storage systems and hardware components is to be completed by qualified technicians who are authorized by HP. Authorized technicians include HP Field Engineers, Value Added Resellers (VARs), and authorized third-party field technicians. HP Part Number: QL Published: March 2014 2 Copyright 2011, 2014 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein. Acknowledgments Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Adobe and Acrobat are trademarks of Adobe Systems Incorporated. All other trademarks and registered trademarks are owned by their respective owners. Warranty WARRANTY STATEMENT: To obtain a copy of the warranty for this product, see the warranty information website: Federal Communications Commission Radio Frequency Interference Statement WARNING: Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the user s authority to operate the equipment. This device complies with Part 15 of FCC Rules. Operation is subjected to the following two conditions (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense. Canadian Compliance Statement This ClassA digital apparatus meets all requirements of the Canadian Interference-Causing Equipment Regulations. They are intelligent, compact, extremely dense storage units where each is capable of holding a large number of disk drives in a small rack space (EIA-standard rack units). The HP 3PAR StoreServ Storage is housed in 2 meter (2M) cabinets and is comprised of the following components: Controller nodes are high-performance, data movement engines that provide the caching capabilities and manage the flow of data in a storage system. The Storage system can accomodate two or four controller nodes while the can accommodate two, four, six or eight nodes. The 3PAR Storage backplane works in conjunction with the controller nodes to route data. This passive, full-mesh backplane enables high-bandwidth and low-latency internal pathing that supersedes bus-, switch-, and even InfiniBand-based architectures. The Drive Chassis houses the drive cages that, in turn, contain the drive bays. Each drive bay contains one magazine that can hold four hard disk drives. Fibre Channel adapters and FC-AL modules provide high speed routing of data and enable granular and potentially massive connectivity to hosts and to the drive chassis. The Service Processor provides the remote error detection and reporting capabilities that support diagnostic and maintenance activities for storage systems. In general, one Service Processor (SP) s required per storage system. HP 3PAR Storage System Components 5 6 Figure 3 (page 8), Figure 1 (page 6), and Figure 2 (page 7) show the front views of a fully populated 2M (40U) HP 3PAR StoreServ Storage cabinet with the various components installed. Figure 1 Front View of the HP 3PAR StoreServ Storage, Single Phase HP PDU 6 System Components and Specifications 7 Figure 2 Front View of the HP 3PAR StoreServ Storage, 3 Phase PDU HP 3PAR Storage System Components 7 8 Figure 3 Front View of the HP 3PAR StoreServ Storage with 3PAR PDUs 8 System Components and Specifications 9 Figure 4 Rear View of the HP 3PAR StoreServ (left) and (right) Storage systems, 3PAR PDU HP 3PAR Storage System Components 9 10 For Figure 1 (page 6) and Figure 2 (page 7), use the following table: Item Description Cable management tray Drive chassis Cooling fans Battery modules Service processor PDUs Leveling feet StoreServ Storage Security Feature The Data Encryption feature allows you to encrypt all specifically formatted hard drives on the storage system with an authentication key and the use of Self Encrypting Drives (SEDs). Enhancing Security with Data Encryption When a Data Encryption license is registered, you must manually enable the encryption feature on the system. When the encryption feature is enabled successfully, all the drives in the system become automatically set in an encrypted state. You can review the encryption status of individual hard disk drives within the system Summary tab of the HP 3PAR Management Console. This feature allows you to perform the following encryption-related tasks: Check encryption status Enable encryption Back up an authentication key Restore an authentication key Generate a new key Recover a key For more information about enabling the feature, see the HP 3PAR Management Console User s Guide. CAUTION: HP recommends retaining all acquired software product licenses for reference and maintenance purposes. The maximum number of supported drive chassis varies according to the number of controller nodes utilized by the system. The physical and capacity specifications are shown here. The efficiency value is based on a host-maximized configuration using 600GB drives. NOTE: SSDs have a limited number of writes that can occur before reaching the SSD's write endurance limit. This limit is generally high enough so wear out will not occur during the expected service life of an HP 3PAR StoreServ under the great majority of configurations, IO patterns, and workloads. HP 3PAR StoreServ tracks all writes to SSDs and can report the percent of the total write endurance limit that has been used. This allows any SSD approaching the write endurance limit to be proactively replaced before they are automatically spared out. An SSD has reached the maximum usage limit once it exceeds its write endurance limit. Following the warranty period of the SSDs, the SSDs that have exceeded the maximum usage limit will not be repaired or replaced under HP support contracts.