HPE Storage Users Group

Hi All,

I'm new to 3Par arrays world, and recently got 3PAR8450 as a PoC project under my disposal.

I'm now looking for "Virtual Service Processor" (I read it's VMWare based VM) for this array, mainly because I need "call home" (aka "autosupport") feature enabled.

Does anyone know where to get it from? I have a basic support contract for this appliance.

Cheers!

You should be able to download it via your Software Entitlement agreement that comes with the product.

Use your HPE passport account to access it. You will need the Support Agreement ID number.

And here is the Download Link:
https://h20575.www2.hpe.com/tsusbportal/index.do

Thank you guys!

I indeed lacked the "SAID" thingy, but HP support provided me with a ISO file per my request.

On a separate note: I'm quite surprised that 3Par needs a SP (VPS) per storage appliance, I hope HPE is going to amend it soon.

@sl0n
We discused it many times, but there are some Questions open:
- How many 3PAR should one SP monitor? (1, 2, 16, ... 100)
- What if 3PAR are in different Places?
- How to handle if one of the 3PAR does not match the SP

@cali IMO, ideally I'd like to run my storage infra with no extra bits and pieces, just storage appliances + SAN fabircs. The 3Par's SP is currently SPOF (single point of failure) and a hard dependency really. So, my answer to your questions - I want to have "0 SPs" =)

I understand that currently the SP has got more than one functionality, and right now I'm after "call home" feature. I'd rather see an appliance being capable to send callhome messages back to vendor on its own, and not depend on another infrastructure piece.

It is not a SPOF, because the Storage still run fine without the SP.
And it is only a VM.

If the SP is included in the Storage, who will notify if the Storage have no Power?
I like this SP-VM.
I can Stage a lot of Software there, have Rebuild Files and so on.
Much more flexible as an dumy On-Board Solution.

I told HPE that I prefer to have one VM that Services the SPOCC (may be for 2 or more 3PAR) and also the SSMC.

If the ask me: Should we include SP and SSMC on the Controller?
I will answer, NO, hold the Software Stack on the Controller as smal as possible.

If the VSP fails you have disruptions on your workflows, eg callhome is not going to work. And from this perspective it is SPOF, i.e. you need to restore the VSP, if you want its functionality.

I agree, the VSP runs important functions, however I know some storage vendors, that have a small SP, embedded into storage controller, with just absolutely necessary monitoring / watchdog functionality implemented. And it works pretty well. I also think that 'callhome' is one of those essentials things.

HPE have had similar functionality in the past with on board management and call home, the issue is it lacks flexibility and scalability. The SP/VSP provides much more than basic call home features and more will be added in the future. Although a neat and low cost solution if you're reliant on relatively lightweight embedded hardware then that adds a barrier to features and adoption between hardware models and generations. Embedding the device or service can also has an affect on serviceability.

BTW if it doesn't call home it will trigger an overdue alert at HPE and they'll let you know.

Hi Sir,

Could you please explain on these 3 points..

Kindly provide me download link if available.

Regards,
KK