Service Processor - Specifications / Datasheet

[viflores]

Hello,

We need to provide our customer power/energy/physical requirements for this Service Processor. I have been looking into HP web site, without success.

I wonder if any of you has this specifications about Service Processor.

Thanks in advance.

Best Regards,
Victor Flores

[Cleanur]

~317 Watts
~1.44 Amps @ 220V
~1,082 BTU's
Rest of the specs should be as per the DL320e Gen8 http://www8.hp.com/h20195/v2/GetDocumen ... =c04123220

[Josh26]

You may prefer to use the virtual service processor - then - the power and space requirements are 'nil'.

[viflores]

~317 Watts
~1.44 Amps @ 220V
~1,082 BTU's
Rest of the specs should be as per the DL320e Gen8 http://www8.hp.com/h20195/v2/GetDocumen ... =c04123220

Hi Cleanur,

Thanks for the info !

Regards

[viflores]

You may prefer to use the virtual service processor - then - the power and space requirements are 'nil'.

Hi Josh26,

Our customer does not have a server with required specifications for virtual service processor.

Regards

[JustinH]

Sorry to hijack this thread but we recently installed the 3par with the blade enclosure and my question is should the VSP be on the same VLAN range as the current server environment?
What is the best practice for assigning a static IP to the VSP and storage?
Also should the Storage be on its own VLAN?
Can the Blade Servers be on the same range as my current servers ?

Thanks

PS : This is what HP requires

[Josh26]

Sorry to hijack this thread but we recently installed the 3par with the blade enclosure and my question is should the VSP be on the same VLAN range as the current server environment?
What is the best practice for assigning a static IP to the VSP and storage?
Also should the Storage be on its own VLAN?
Can the Blade Servers be on the same range as my current servers ?

Thanks

PS : This is what HP requires

Ideally storage will sit on a dedicated VLAN so you can isolate it. It's one thing to try and secure individual servers, but anything that impacts your 3PAR can leave the whole environment down. Consider when Heartbleed came out. It's one thing to patch every server over the next few days. Getting firmware updates for a 3PAR is a much bigger deal. You do however need the VSP and the 3PAR itself on the same subnet.

As for the static IP, well, you pick one. I'm not sure how much more of a best practice there could be?

Finally, as for blade servers coexisting with other servers, there's nothing magical about blades and there's no reason to treat servers on blades any differently to existing servers.