HP XP7 Command View Advanced Edition 8.0.0-01 Release Notes

Changing the IP address of a host added by a Device Manager agent
When the Device Manager agent is installed, and either the IP address of the host was changed or
the server.http.socket.agent Address property in the server.properties file for the host
was changed, the IP address was not reflected for the Device Manager Server, even though the Device
Manager agent service or deamon was restarted.
In this case, remove the host from the Device Manager server, then restart the Device Manager server
agent or deamon.
The server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh
property
Even if true is specified for the
server.dispatcher.daemon.autoSynchro.logicalGroup.doRefresh property in the
dispatcher.properties file, information on logical groups is not updated automatically when
any CLI commands are executed.
Smart Tier for Mainframe
If Device Manager is managing XP P9500, Smart Tiers for Mainframe pools are displayed as Thin
Provisioning for Mainframe pools. As a result, all attributes specific to Smart Tiers for Mainframe (for
example, tier information) cannot be viewed in Device Manager. Use Element Manager to view the
attributes specific to Smart Tiers for Mainframe.
Meter-based Term License
When only the Meter-based Term license is registered, an Emergency license cannot be input.
Changing the hostname
If one or more letters in the target host name is changed, after host information is refreshed, the HiScan
command is executed or the Device Manager agent service is restarted on a host, pair information
may not be managed by the host.
To change the host name, perform the following:
1. Stop the Device Manager agent service and automatic execution of the HiScan command on
the host.
2. Check whether the target host is registered in any resource groups.
3. Change the target host name.
4. From the Device Manager GUI or CLI, change the host name to a completely different name.
Example:
Before: ABCD
After: EFGH
5. Start the Device Manager agent service and automatic execution of the HiScan command on
the host.
6. From the Device Manager GUI or CLI, delete the host name in the Device Manager server.
7. If the target host had been registered in any resource groups (as described in step 2), register the
host again.
8. Refresh the storage systems to which the LUNs recognized by the target host belong.
The parity group list dialog box
The parity group number might not be displayed correctly. In this case, please refer to the parity group
summary information to confirm the correct number. In addition, the format type cannot be chosen
when the create volume dialog is opened from the parity group list. Open the dialog from another
screen.
Important considerations 25