Menu
![](/uploads/1/2/5/5/125559944/188142988.jpg)
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. Setup A StoreServ VSPThe Virtual Service Processor comes as an Virtual. It's likely to only come with a DVD media kit when ordering the product. The HP SmartStart software to connect to allow configuration of the VSP.
Print|Rate this content |
Connecting to a Virtual Service ProcessorPrerequisites for Using a VSP:
WARNING: Do not install the VSP on the same StoreServ 7450 array because it may lead tothe inability of properly managing the array when connectivity to the storage is unavailable.Provision the VSP on a VMware server and ensure the VSP boots from the local disk of the assignedVMware server and not from the StoreServ 7450 LUNs. CAUTION: VMware vMotion is not a supported application. Do not use vMotion to migrate theVSP from one physical server to another. Using vMotion may cause communication failure andinterrupt system service. Deploying the VSP OVF File: NOTE: The virtual service processor supports VMware ESXi versions 4.1 and later. For morespecific VMware environment support, see the VMware compatibility matrix on the VMwarewebsite. The following set of instructions may vary depending on the version of VMware ESXi youare using.
The VSP is now ready to set up. Establishing the Virtual Service Processor IP Address: After verifying the connection to the Virtual Service Processor, you must perform one of the followingoptions:
Option A: DHCP Network Environment To determine a temporary IP address for the VSP:
Option B: Non-DHCP Environment To set the IP address of the VSP:
Connecting to a Physical Service ProcessorConfiguring the Physical Service Processor IP Address: The following example uses Microsoft Windows 7 to configure the SP IP address and theprocedures may vary depending on the type of OS being used.
Link to the list of available documentsClick here to view the list of available documents for HP 3PAR StoreServ 7450 Storage . |
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.
Provide feedback |
Please rate the information on this page to help us improve our content. Thank you! |
- Was the information on this page helpful?
Please wait while we process your request.
![Hp 3par Virtual Service Processor Software Dvd Hp 3par Virtual Service Processor Software Dvd](http://www.bitcon.be/wp-content/uploads/2014/07/VSPupdate1.jpg)
HP 3PAR has created a bit of a 'damned of you do...' situation with regard to its Service Processor (which is available as a physical and/or Virtual Appliacne for VMware).
In directly conflicting documentation, HP states that the Service Processor should be placed on the local disks of an ESXi host, and that vSphere HA should be leveraged when possible. We all know that HA won't work with local disks, so where to go from here?
![3par 3par](/uploads/1/2/5/5/125559944/810327058.jpg)
Of course, in the event we were lucky to have more than one, completely independent 3PAR SAN's, we could put the Service Processor for one on the other and vice-versa. Unfortunately, many installations will only have one 3PAR (the situation I face now) - and that may be the only viable form of block-level storage.
My thoughts are this:
- HP can't possibly expect users to revert to the 'old fashioned' disk-based installs of ESX 3.X days, just to accommodate the needs of the 3PAR Service Processor.
- The 3PAR has complete device redundancy, therefore it should be one of the least likely points of failure in an environment.
- The Service Processor is not absolutely required for the presentation of block storage.
- The value of vSphere HA (and potentially FT as well, because the Service Processor is a 1 vCPU RHEL VM) far outweighs the need to run the Service Processor on local storage.
- One could, potentially, keep a copy of the Service Processor on portable storage and bring it up using VMware Workstation in an emergency.
I would love to get the opinions of other 3PAR users!
Thanks-
-J
![](/uploads/1/2/5/5/125559944/188142988.jpg)