HP 3PAR Service Processor Software 4.1.x Release Notes (QR482-96666)

2 Service Processor Software 4.1.0 Release
The following release notes are for the HP 3PAR Service Processor (SP) Software 4.1 release.
What’s New in the Service Processor
HP 3PAR Service Processor functions as the communication interface between the customer’s IP
network and HP 3PAR Central by managing all service-related communications in both directions.
The Service Processor leverages the industry-standard HTTP over Secure Socket Layer (HTTPS)
protocol to secure and encrypt data communication.
The key enhancements in this release are the following new features:
• Introduced the ability to deploy the Service Processor as a virtual machine for managing all
service-related tasks for the HP 3PAR StoreServ 7000 Storage system.
• Implemented a web-based user interface for installing and configuring the Service Processor
and the HP 3PAR StoreServ 7000 Storage system.
• Menu trees have been reorganized.
• Support for HP 3PAR Policy Server is added.
NOTE: Modem support is dropped in the HP 3PAR Service Processor 4.1.0 release. Customers
planning to upgrade to HP 3PAR OS 3.1.2 (which requires SP 4.1.0) will need to move to a
supported connectivity model.
Modifications to the Service Processor
The following issues have been addressed in this release.
DescriptionItemIssue ID
If you are using the GM scripts to replace a DC-2 FC-AL on an S-class InServ,
note that you must transfer and reuse the old SFPs from the failed FC-AL to
the new FC-AL.
GM: FC-AL replacement
for S-class InServs with
DC-2 cages
63798
This modification addresses the issue where an upgrade can fail due to too
many SD DeFrag activities during the upgrade. The space defragmentation
Turn off space
defragmentation during
70926
feature is turned off during an online upgrade to 3.1.1.MU1 and turned
back on once all nodes in the cluster have successfully upgraded.
online upgrade to
3.1.1.MU1
This modification should be used only for online upgrades to 3.1.1.MU1.
If you try to log into SPOCC as setupusr, after the Moment of Birth, you will
be redirected to a page informing you it is not a valid ID for use after initial
SPOCC SETUPUSR
available after MOB
80282
configuration. In some cases, you will be presented with a blank screen. In
all cases, you must close your browser and log back in with the appropriate
ID, such as 3parcust.
If there is an error or failure when adding a InServ to an SP, the "Username:"
prompt may be displayed along with the returned error condition info.
Adding Inserv to SP:
username could appear
in error info
80873
If the storage system upgrade fails or is aborted mid-way, the SP's
configuration persistence file related to the storage system has a version
Check defrag failure after
upgrading from
80974
number that does not match that of the storage system, depending on whether
the storage system rebooted with the newer version or the older version.
3.1.1.342 (MU1) to
3.1.1.410 (MU2)
In case the storage system upgrade fails for some reason, the user has to
remove and re-add the storage system from the SP, and this will cause the
SP configuration persistence file that is related to the storage system to
synchronize the version number with the one that is actually running on the
storage system.
What’s New in the Service Processor 7