HP P9000 Tiered Storage Manager Software 7.4.0-00 Release Notes (TB585-96028, December 2012)

A tier created from the Device Manager GUI is not displayed in Tiered Storage Manager
When a tier created from the Device Manager GUI meets any of the following conditions, the tier is
not displayed in the storage tiers of Tiered Storage Manager:
The tier was created by directly specifying 101 or more volumes.
The tier was created by selecting either of the following attributes in the advanced search criteria
and by specifying 101 or more values for the attribute:
ID/Number/Name is specified for the category, and the Parity group on a controller that
hosts can access is specified for the attribute.
ID/Number/Name is specified for the category, and the Parity group on a controller that
contains drives is specified for the attribute.
Editing a storage tier created by the CLI in the Edit Tier dialog box
If a storage tier including the capacity conditions created by the CLI is selected and the Edit Tier dialog
box is launched, the GUI malfunctions.
In this case, use the CLI ModifyStorageTier command to edit the storage tier. Then close the GUI
browser and log in again.
Message about refreshing the storage domain
Substitute messages directing to Refresh the storage domain or Refresh Tiered Storage
Manager with Refresh the storage system.
Determine the name of the storage system corresponding to the storage domain using one of the
following methods:
Using the GUI:
In the <storage-domain-name> subwindow, on the Detailed Information tab, refer to the first
value of Domain Ctrl.
In Domain Ctrl, the display format of the storage system is
<storage-system-name>:<model-name>:<serial-number>.
Using the CLI:
Refer to the controllerName value in the output of the GetStorageDomains -d command.
Mozilla 1.7.13 (HP-UX 11i v3) support
If the Tiered Storage Manager GUI uses Mozilla 1.7.13 in HP-UX 11i v3 for PA-RISC, the IPv6 protocol
cannot be used to communicate with the Tiered Storage Manager server.
Monitoring schedule templates
If a monitoring schedule template created in a version earlier than 7.2.0-00 is executed, stop-monitoring
tasks and start-relocation tasks might not complete.
Also, if an old version monitoring schedule template is registered with a monitoring start time that is
the same as the monitoring end time of another monitoring, the start-monitoring tasks might generate
the KAIC06400-E error.
After upgrading to version 7.2.0-00 or later, open the old version of the monitoring schedule template
to edit and close it by clicking the OK button.
This open-close operation upgrades the monitoring schedule template.
6 Important considerations