2 overview, Customer responsibilities, Service processor connectivity overview – HP 3PAR Service Processors User Manual
The Service Processor is available in both physical and virtual versions for the SP 4.2.0 release.
The SP is designed to provide remote error detection and reporting and to support diagnostic and
maintenance activities involving the storage systems. The SP is composed of a Linux operating
system and the SP software, and it exists as a single undivided entity.
The physical SP is a hardware device mounted in the system’s rack. If the customer chooses a
physical SP, each storage system installed at the operating site includes a physical SP installed in
the same cabinet as the system’s controller nodes. A physical SP uses two physical network
connections; one (eth0) requires a connection from the customer network in order to communicate
with the storage system. The other (eth1) is for maintenance purposes only and is not connected
to the customer network.
The virtual SP (VSP) is provided in an Open Virtual Format (OVF) format. The VSP is tested and
supported on the VMware vSphere hypervisor (based on the ESXi 4.0 server and supported on
VMware ESX and ESXi 4.1 and later clients). It is also tested and supported on the Microsoft
Hyper-V Server 2008 R2 and later hypervisor. The VSP has no physical connections. It runs on a
customer-owned and customer-defined server and communicates with an HP 3PAR storage system
over its own Ethernet connections.
For information about how to use the VSP, see
. The VSP is
supported only for the HP 3PAR StoreServ 7000 Storage system.
The customer must provide any hardware required to host the remote support software when
deploying a Virtual Service Processor. For scheduled service calls, the customer shall make the
Virtual Service Processor available to HP for remedial activities at the agreed-upon time. The
customer is responsible for maintaining the appropriate HP 3PAR Remote Support Technology with
a secure connection to HP and any passwords required to access the local network and Virtual
Service Processor. The customer is responsible for providing all necessary resources in accordance
with the HP 3PAR Service Processor Release Notes in order to enable the delivery of the service
and options. Please contact a local HP representative for further details on requirements,
specifications, and exclusions.
Service Processor Connectivity Overview
The data collected by the SP is used to maintain, troubleshoot, and upgrade the SP and the HP
3PAR StoreServ Storage system. (Only one storage system can be attached to an SP.) Depending
on the SP’s connection mode, the SP communicates either with an HP 3PAR Connection Portal or
with the HP 3PAR Collector Server.
During system setup, the SP can be set up in either Secure Network mode (recommended) or SP
mode. In Secure Network mode, the SP communicates with the HP 3PAR Collector Server by using
HP 3PAR Secure Service Agent software. In SP mode, the SP communicates with the HP 3PAR
Connection Portal server via Secure Shell (SSH) and SSH File Transfer Protocol (SFTP).
The connection between the SP and the connection portal can be made using your network and
the Internet or, for versions that are earlier than SP 4.1.0, a point-to-point connection with a modem.
Connections that use your network pass through your firewall, while connections that use a modem
bypass the firewall.
Modem support was discontinued in the HP 3PAR Service Processor 4.1.0 release.
Customers planning to upgrade to HP 3PAR OS 3.1.2 or 3.1.3 (which require SP 4.1.0 or later)
will need to move to a supported connectivity model.