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

SP4.1 with HP 3PAR OS-3.1.2 in SPMAINT (not SPOCC) still attempts to configure
SP legacy node rescue (Issue 79693)
Workaround: Attempt node to node rescue. For more information, see the HP 3PAR StoreServ
7000 Storage Service Guide.
You must set up alert emails manually (Issue 79635)
The HP 3PAR storage system does not automatically email you alerts as issues occur (e.g., a CPG
becomes low on space, a disk drive fails, and so on).
Workaround: Use SPOCC's Setup module to set up Local Notification.
After installing a patch (311 MU1 P16), CLI connection is broken (Issue 80530)
Workaround:
1. Exit the SPMAINT session.
2. Log in to SPMAINT again, and then enter 7 for Interactive CLI.
3. Run the showpatch command.
ProLiant DL360e SPMAINT: mount cdrom fails with “mount special device /dev/cdrom
does not exist” (Issue 72636)
The physical DVD must be connected from the physical machine to the virtual machine using a
menu command on the Virtual Machine Manager. For VMware, the steps to do this are as follows:
1. Insert the CD with the contents in ISO format.
2. In the vSphere client, find the CDROM tool icon on the toolbar near the far right (select
"View->Toolbar" if the toolbar is not already present).
3. Select "CD/DVD drive1", and then select the drive letter corresponding to the physical DVD
drive in the physical machine.
4. Run SPMAINT.
If the storage system name is changed in SPMAINT 3.3.2, option 8 (command on
node) will no longer work (Issue 81536)
The SPMAINT option to change the InServ cluster name on the SP cluster configuration file is not
supported. HP recommends that you do not use this option because it causes issues with
communicating with InServ storage.
SPMAINT InSplore USAGE: callnode displays (Issue 81700)
The option to change the configured InServ name is not supported. HP recommends that you do
not initiate the InServ name from the SP after it is configured, because doing so causes issues
communicating with InServ storage.
Workaround: If the InServ name needs to be changed, use the CLI to change the InServ name,
and then remove and re-add the InServ to the SP.
SP 4.1 cannot start an InSplore (Issue 81672)
The InSplore process may not complete immediately after a StoreServ upgrade.
Workaround: Kill the InSplore by using SPOCC. To do this, launch an InSplore by using SPOCC.
If SPOCC indicates that an InSplore process is already running, monitor the InSplore window for
new output. If no new output shows up for 20 minutes, the InSplore is likely to be hung. In this
case, press Kill This InSplore. After the kill succeeds, wait two minutes, and then launch another
InSplore from SPOCC. If it fails again, reboot the SP. Rebooting the SP will automatically generate
a new InSplore.
10 Service Processor Software 4.1.0 Release