In the first blog post we covered an overview of the StoreServ 7000 hardware the next stage is looking at ‘what we do next’.
Setup A StoreServ VSP
The Virtual Service Processor comes as an Virtual Appliance in the OVF format, this can only be installed on ESXi 4.1, 5 or 5.1. From a design perspective it’s not a good idea to have the VSP on the StoreServ. Why’s this you ask?
Well, the VSP is responsible for reporting back any issues to 3PAR Central that the StoreServ has. If the VSP is on the Virtual Volumes provided by the StoreServ then how can it report back ? The answer is it can’t. Recommended practice is to place the VSP on a RAID protected local HDD of an ESXi host.
I’m not able to walk through deploying the OVF VSP as it doesn’t appear to have been released for download and therefore it’s likely to only come with a DVD media kit when ordering the product. From the installation guide, the only thing to note is that it’s recommended to use Thin Provisioning.
After launching the OVF you need to login to the VSP, my understanding this will be via SSH like the F400’s.
U: root
P: hp3par
Once logged in, the VSP would have obtained an IP Address from DHCP, run the command
ifconfig -a
Which will return the IP Address to enable the HP SmartStart software to connect to allow configuration of the VSP.
SmartStart
SmartStart requires Windows Server 2008. It is the software used to configure your StoreServ 7000.
A couple of items to note:
- You require Administrator access on the Windows Server 2008.
- VSP and the StoreServ 7000 much be on the same subnet as the Windows Server 2008 running are running SmartStart on.
The screen shots below are taking from the HP training, hopefully the process makes sense without me actually having an actual StoreServ to configure!
Initial SmartStart Welcome Screen
Prepare to Configure
This is the part where you now want to ‘click’ on Setup Service Processor and enter the IP Address you received from running the ifconfig -a command and login using root hp3par
The SP Setup Wizard will then launch on a Web Page.
Next you will enter some basic networking details which are:
- Service Processor ID, I believe this is obtained from HP
- Service Processor Hostname e.g. StoreServ-VSP001
- IP Address
- Subnet Mask
- Default Gateway
- Domain Name
- DNS Server(s)
Next you need to configure the support package. You have three choices:
- Active – this allows HP to remotely perform maintenance tasks on the Virtual Service Processor and StoreServ. Log files are automatically sent to HP.
- Passive – this sends log files only
- No Support – you need to send log files manually
Next enter your Time Zone and enter a NTP server. My recommendation is to use an internal DC as your NTP server to avoid time skew.
Lastly, you confirm your settings and apply them. Naturally, your IP address will change so remember that you will need to reconnect to this to make any further changes.
Setup StoreServ 7000
Back to the SmartStart and the next thing we want to do is select ‘Set up the Storage System’.
This takes you back to the Virtual Service Processor, so you need to login with U: root P: hp3par
Click next a couple of times and then at this point you will need to enter the ‘assembly serial number’ which is on the StoreServ or your HP 3PAR System Assurance Document. To be clear this is the serial number for the complete StoreServ not an individual component.
The StoreServ is then verified with the model, 3PAR OS version and the number of Nodes, hits next.
Enter networking information for:
- Hostname e.g. StoreServ-001
- IP Address
- Subnet Mask
- Default Gateway
Next we configure the time, it is recommended to get the time from the Virtual Service Processor
Lastly, click Next and verify the installation.
Great write up Craig,
HP have updated their documentation. It looks like the 3PAR vSP is now also supported on ESX4.1.
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c03653513
Thanks for letting me know Gareth, I have updated the article.
Great article.
The manual states it required 320GB of storage for the VSP, is this correct? seems excessive. Thanks.
It is quite alot, but with all things we need to follow HP guidance to make sure you are supported. Don’t forget to install the VSP on some local server hard drives.
I knew you might say that 🙂
Many thanks Craig.