HP 3Par Setup and Configuration SP & VSP There are two options available to manage a new HP 3Par StoreServ, the physical Service Processor and the Virtual Service Processor. In this guide, I will cover the initial setup for both, and review how to setup the StoreServ after the Service Processor is configured. A vulnerability was found in HPE 3PAR Service Processor up to 3.5.0.0 and classified as critical. This issue affects some unknown processing. The manipulation with an unknown input leads to a privilege escalation vulnerability. Using CWE to declare the problem leads to CWE-269.
HPE Peer Persistence software enables storage systems located at metropolitan distances to act as peers to each other, presenting a nearly continuous storage system to hosts and servers connected to them. This capability allows you to configure a high-availability solution between two sites or data centers where failover and failback remains completely transparent to the hosts and applications running on those hosts. Compared to the traditional failover models where upon failover, the hosts must be restarted, the Peer Persistence software allows hosts to remain online serving their business applications even when they switch from their original site to the disaster-recovery (DR) site, resulting in a much improved recovery time. The Peer Persistence software achieves this key enhancement by taking advantage of the Asymmetric Logical Unit Access (ALUA) capability that allows paths to a SCSI device to be marked as having different characteristics
HPE Peer Persistence is available with HPE 3PAR and HPE Primera systems, it leverages the robust high-availability solutions already available on these systems, and extends it even further by enabling a peer relationship between two storage systems located at geographically separated sites. The software is built in to the HPE 3PAR and HPE Primera systems, customers with remote replication setup can deploy Peer Persistence without any appliance or additional hardware.
HPE Peer Persistence Quorum Witness (QW) software facilitates automatic transparent failover within a Peer Persistence environment. It is run on a separate server environment) and must not be part of the host cluster(s). It is configured and connected to both arrays using network interfaces that are independent from the remote copy network used for replication data traffic.
What’s New with Version 3.0.014:
Note: Starting with version 3.0.014 , Quorum Witness (QW) will be distributed as a RPM package. The earlier versions of Quorum Witness were distributed as a Virtual Appliance ISO image that included the Quorum Witness software binaries and a Linux OS runtime image. The QW 3.0.014 RPM package will contain only the Quorum Witness 3.0.014 software and other required binaries (there is no Linux OS runtime image include in the RPM). Consequently installation of QW 3.0.014 is different than earlier versions; so please refer to the installation guide below for more details.
- QW version 3.0.014 is released as a self-contained application, installed as an RPM package on a CentOS 7.4 (or later 7.x versions) OS or Red Hat Enterprise Linux 7.6 (or later 7x versions). Therefore customers have more flexibility in the configuration of theirown CentOS or Red Hat Enterprise Linux host installation, and can apply OS security and feature updates from vendors directly, on their own schedule.
- This version of QW (3.0.014) replaces previous versions of QW running with Peer Persistence software on 3PAR 3.2.2 and 3.3.1.
- The QW RPM package can be installed on any physical machine or virtual machine running CentOS 7.4 (or later within 7.x) or Red Hat Enterprise Linux 7.6 (or later 7x versions) Operating Systems.
- This version of QW server is no longer restricted to ESX or Hyper-V virtual machines. It can be installed on virtual machine of any Hypervisor that support CentOS 7.4 (or later within 7.x) or Red Hat Enterprise Linux 7.6 (or later 7x versions) Operating Systems.
- Mixed Peer Persistence setup using HPE Primera and HPE 3PAR arrays must be configured using Quorum Witness version 3.0.014
- Please review the instructions regarding installation and upgrading of this version of Quorum Witness.
Customers can continue to use older versions of QW but are advised to move to the latest version for upgrades and new installations if supported with their configuration. Please refer to the 3PAR support matrix (listed below) for compatibility.
Product Documentation:
HPE Peer Persistence Quorum Witness information can be found in the HPE 3PAR Remote Copy Software Users Guide:
www.hpe.com/info/storage/docs
The HPE 3PAR Quorum Witness Installation and Update Guide can be found:
www.hpe.com/info/storage/docs
Up to date Quorum Witness software compatibility information can be found in the “HPE 3PAR Support Matrix 3.3.1” document on the SPOCK page:http://www.hpe.com/storage/spock, under“HPE 3PAR”on the left side box menu “Other Hardware”.
The HPE 3PAR Quorum Witness 3.0.x Release Notes can be found:
www.hpe.com/info/storage/docs
Up to date HPE Peer Persistence interoperability with host OS version for HPE 3PAR can be found in the “3PAR Peer Persistence Host OS Support Matrix” document on the SPOCK page:http://www.hpe.com/storage/spock, under“Array SW: 3PAR”on the left side box menu “Software”.
Product Support:
For support, please follow the standard support processes for your HPE Storage arrays or visit https://www.hpe.com/us/en/support.html
Print|Rate this content |
Connecting to a Virtual Service Processor (VSP)Use this procedure only if a physical SP is not installed on the storage system. Requirements:
Procedure: To import the VSP (VM) OVF file:
Obtaining the temporary SP IP addressAfter the verification for connection to the VSP, obtain the temporary SP IP address that will be used in setting up the Service Processor. To obtain the SP IP:
Installing the physical service processor in the storage systemNOTE: The SP ID is the HPE 10-digit serial number located on the top front of the server and in a pull-out placard in the front of the server. This serial number has the prefix SP. Use these procedures when installing a HPE 3PAR Service Processor to an existing rack. Before begin, end user will need to verify the SPS-Processor 1U mounting kit (683811-001). The service processor rail kit supports a variety of products in round, square, or threaded-hole racks.
The following components are included in the kit:
In addition to the supplied items, end user may also need the following:
WARNING: To avoid risk of injury or damage to the equipment, do not stack anything on top of rail-mounted equipment or use it as a work surface when extended from the rack. CAUTION: Always plan the rack layout before installing the equipment. HPE recommends installing the heaviest component first at the bottom and continuing to populate the rack from bottom to top. To install the Service Processor:
Assigning the permanent service processor IP address to the physical SPConnecting a laptop to the SP:
End user can now connect to the storage system. Click here to view the Installing Storage System Software page for HPE 3PAR StoreServ 7000 Storage . Configuring the laptop LAN settings:
Link to product related documentsClick here to view the list of product related documents . DisclaimerNOTE: One or more of the links above will take you outside the Hewlett-Packard Enterprise web site, HPE does not control and is not responsible for information outside of the HPE web site. |
Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.
3par Service Processor Download
Provide feedback |
Please rate the information on this page to help us improve our content. Thank you! |
- Was the information on this page helpful?