Hitachi Device Manager 8.2.1-00 Release Notes · Hitachi Data Systems Community is a global online community for HDS customers, partners, independent software vendors, employees,

© 2015 Hitachi, Ltd. All rights reserved. 1

RN-00HS266-93 (November 2015)

Hitachi Device Manager

8.2.1-00 Release Notes

Contents

About this document.................................................................................... 1

Intended audience ....................................................................................... 1

Getting help ............................................................................................... 1

About this release ....................................................................................... 2

Product package contents............................................................................. 2

New features and important enhancements .................................................... 2

System requirements................................................................................... 8

Resolved problems ...................................................................................... 8

Known problems ......................................................................................... 9

Installation precautions .............................................................................. 15

Usage precautions ..................................................................................... 16

Documentation ......................................................................................... 20

Copyrights and licenses ............................................................................. 20

About this document

This document (RN-00HS266-93, November 2015) provides late-breaking

information about Hitachi Device Manager v8.2.1-00.It includes information that

was not available at the time the technical documentation for this product was

published, as well as a list of known problems and solutions.

Intended audience

This document is intended for customers and Hitachi Data Systems partners who

license and use Hitachi Device Manager.

Getting help

Hitachi Data Systems Support Connect is the destination for technical support of

products and solutions sold by Hitachi Data Systems. To contact technical

support, log on to Hitachi Data Systems Support Connect for contact information:

https://support.hds.com/en_us/contact-us.html.

https://support.hds.com/en_us/contact-us.html




Hitachi Data Systems Community is a global online community for HDS

customers, partners, independent software vendors, employees, and prospects.

It is the destination to get answers, discover insights, and make connections.

Join the conversation today! Go to community.hds.com, register, and

complete your profile.

About this release

This release is a major release that adds new features.

Product package contents

Item Contents Revision Release type

Software Device Manager Server 8.2.1-00 Full Package

Documents Hitachi Command Suite User Guide MK-90HC172-22

Hitachi Command Suite CLI Reference Guide

MK-90HC176-22

Hitachi Command Suite Tiered Storage Manager CLI Reference Guide

MK-90HC177-19

Hitachi Command Suite Messages MK-90HC178-22

Hitachi Command Suite Audit Log Reference Guide

MK-92HC213-08

Hitachi Command Suite Installation and Configuration Guide

MK-90HC173-22

Hitachi Command Suite Administrator Guide

MK-90HC175-22

New features and important enhancements

For 8.2.1-00

Features and enhancements Affected components

Affected operating systems

- Device Manager agent now supports the following operating systems:

-

- Red Hat Enterprise Linux 6.7

- Oracle Linux 6.7 UEK R2


- SUSE Linux Enterprise Server 11 SP4

Device Manager Agent

All*

http://community.hds.com/

http://community.hds.com/



Device Manager agent now supports the following cluster software:

- Oracle Solaris Cluster

- HA Monitor(for HP-UX)

- HA Monitor(for Linux)


All*

Device Manager agent now supports the following file systems:

- AIX JFS2

- Solaris ZFS


All*

Device Manager agent now supports the following path management software:

- AIX Multiple Path I/O (MPIO)

- Linux Device-Mapper Multipath


All*

Host Data Collector now supports the following operating systems as a target host:

- RedHat Enterprise Linux 6.7




Host Data Collector

All*

Host Data Collector now supports the following operating systems as a server:

- RedHat Enterprise Linux 6.7


Host Data Collector

All*

Target hosts that are managed by the Host Data Collector now support the following file systems:

- AIX JFS2

- Solaris ZFS

Host Data Collector

All*

Target hosts that are managed by Host Data Collector now support the following cluster software:

- Oracle Solaris Cluster

- HA Monitor(for HP-UX)

- HA Monitor(for Linux)

Host Data Collector

All*

- Target hosts that are managed by Host Data Collector now support the following path management software:

-

- AIX Multiple Path I/O (MPIO)

- Linux Device-Mapper Multipath

Host Data Collector

All*

In Device Manager, for Hitachi Virtual Storage Platform G200, G400, G600, G800, tasks from the following dialog boxes and products can now be performed for a

Device Manager Server

Device Manager

All*



DP volume of up to 256 TB:

Dialog boxes:

- Create Volumes

- Allocate Volumes (standard or global-active device)

- Allocate Like Volumes (standard or global-active device)

- Change to Global-Active Device Volumes

- Expand DP Volumes

- Create File Systems

Products:

- global-active device

- Universal Replicator

- TrueCopy

- Thin Image

ShadowImage

GUI

Device Manager CLI

Regarding the VVol functions provided in VMware vSphere version 6.0 and later, Device Manager now supports storage container tasks that are necessary for the usage of the Storage Policy Based Management function in the Hitachi NAS Platform environment.


Device Manager GUI

All*

Device Manager now supports volume allocations that use an iSCSI port on Hitachi Virtual Platform G1000.


Device Manager GUI

Device Manager CLI

All*

Device Manager now supports the viewing and setting of the ALUA Application States and Asymmetric Access States (ALUA path priority) that are used for global-active devices in cross path configurations on Hitachi Virtual Storage Platform G1000.


Device Manager GUI

Device Manager CLI

All*

Device Manager now supports the viewing of the Data

Direct Mapping attribute for external parity groups, HDP pools, and HDP volumes on Hitachi Virtual Storage Platform G200, G400, G600, G800, and G1000.


Device Manager GUI

Device Manager CLI

All*

Device Manager GUI now supports functionality for notifying users of task completion by email.

Device Manager GUI

All*

Device Manager now supports the host mode option Proprietary ANCHOR command support for Hitachi Virtual Storage Platform G200, G400, G600, G800, and G1000.


Device Manager GUI

Device Manager CLI

All*

Device Manager now supports file system expansion up Device Manager All*



to a maximum of 1 PB. Server

Device Manager GUI

In a configuration where virtualization servers are connected to Hitachi Virtual Storage Platform G200, G400, G600, or G800 by Fibre Channel or iSCSI, Device Manager now supports the following VVol functions that are provided in VMware vSphere version 6.0 and later:

- The completion of various VVol-related

operations on storage systems based on requests from the VASA provider

- Management of the storage container that is required for using the Storage Policy Based Management function

- Display of protocol endpoints (ALUs) and VVols (SLUs)

- Performance analysis of VVols in the Analytics tab


Device Manager GUI

Device Manager CLI

All*

Regarding the VVol functions provided in VMware

vSphere version 6.0 and later, the following enhancements were made to Device Manager:

Values that can be specified in the capability profile by using the following capabilities were changed.

Performance IOPS - Class

Performance Latency - Class

Availability - Class

Snapshot Backup Importance - Class

Initial values are no longer set in the Define Capability Profile dialog box.

In the Create/Edit Storage Container dialog

box, the content specified for the capability profile is now displayed in a pop-up message box.


Device Manager GUI

All*

Device Manager agent now supports guest operating systems running on the following virtualization server products.

VMware vSphere ESXi 6.0 update 1



All*

Host Data Collector now supports the following

virtualization server products, and guest operating systems running on these virtualization server products as target hosts.



Host Data Collector

All*

Host Data Collector now supports guest operating systems running on the following virtualization server products as a server.

Host Data Collector

All*





The Device Manager server, GUI, and CLI now support Red Hat Enterprise Linux 6.7.


Device Manager GUI

Device Manager CLI

Linux

The Device Manager server, GUI, and CLI now support the virtualization server product VMware vSphere ESXi 5.5 Update 3.

For more information about guest operating systems, see the Hitachi Command Suite System Requirements.


-

The Device Manager server, GUI, and CLI now support

the virtualization server product VMware vSphere ESXi 6.0 Update 1.

For more information about guest operating systems, see the Hitachi Command Suite System Requirements.


-

The Device Manager GUI now supports Internet Explorer 11 in Microsoft Windows 10.

Device Manager GUI

Windows

The Device Manager GUI now supports Adobe Flash Player 19.

Device Manager GUI

Windows

For HUS100 (microcode version: x8D1/A or later), the Device Manager CLI now supports setting hostmode2 to one of the following three parameters in the AddHostStorageDomain and ModifyPort commands:

WriteSame Rejection Mode

FullProvisioning Reply Mode

UNMAP Rejection Mode


Device Manager GUI

Device Manager CLI

All*

For HUS100 (microcode version: x981/A or later) and

Hitachi AMS 2000 (microcode version: x8D1/A or later), the Device Manager CLI now supports displaying and specifying the iSCSI Delayed Ack setting in the ModifyPort command.


Device Manager CLI

All*

The Device Manager server, GUI, and CLI now support SUSE Linux Enterprise Server 11 SP4.


Device Manager GUI

Device Manager CLI

Linux

The JDK version that is bundled with the Device Manager server is now version 1.8.0.

Because of the introduction of the upgraded version,

JDK 1.7.0 is no longer supported for use by the Device Manager server.


All*

Device Manager now supports Hitachi NAS Platform 12.5.


Device Manager GUI

All*



Note: See Hitachi Command Suite System Requirements for details.

*: Applies to all supported operating systems in Device Manager.

Device Manager now supports the following functions for Hitachi Virtual Storage Platform G200, G400, G600, G800 (microcode version: 83-02-0X-XX/XX or later):

In the GUI and CLI, the T10 PI of a volume and the T10 PI mode of a port are now displayed.

Applicable GUI functionality

Dialog boxes:

Allocate Volumes (both standard and global-active device)

Allocate Like Volumes (both standard and global-active device)

Change to Global-Active Device Volumes

LUN path editing

Identify Performance Problems in Analytics tab

Health Check Report in Analytics tab

Applicable CLI functionality

Port instance

LDEV instance


Device Manager GUI

Device Manager CLI

All*

The Analytics tab now supports selecting whether to output a company logo in the exported PDF file.

Device Manager GUI

All*

The Replication tab now supports configuration and management tasks for replication environments that are prepared for disaster recovery.

In addition, the procedures for managing replication environments have been simplified.

Device Manager GUI

All*

Device Manager now supports Hitachi Virtual Storage Platform F400, F600, and F800.


Device Manager GUI

Device Manager CLI


Host Data Collector

CIM,

Replication Manager

Tuning Manager

All*

The following change was made: During an upgrade using the All-in-One Installer, only products that are already installed are selected by default in the Select Products window.


Windows



System requirements

System requirements can be found in Hitachi Command Suite System

Requirements (MK-92HC209-20).The requirements are presented in the form of

requirements for each type of server, rather than as requirements for individual

Hitachi Command Suite components.

When upgrading Hitachi Command Suite products from v7.6.1 or earlier, if the

following components are installed, upgrade them to v8.0.0 or later:

Device Manager

Tiered Storage Manager

Replication Manager

Tuning Manager

Compute Systems Manager

Global Link Manager

Resolved problems

From 8.2.0-03 to 8.2.1-00

Problem description Affected products

Affected operating systems

In the Expand DP Volume dialog box, you cannot perform DP volume expansion when specifying a capacity that uses a decimal point.

Device Manager GUI

All*

When allocating volumes for a global-active device pair

in the Allocate Volumes or Allocate Like Volumes dialog box that are launched by the following methods, any of the following symptoms occur in the dialog box.

Launch the dialog box from the General Tasks menu.

Launch the Allocate Volumes dialog box from the Actions menu.

Launch the dialog box by selecting a host from

an operating system listed in the Hosts tree in the Resources tab.

Launch the dialog box by selecting a host in the Hosts tab that opens when selecting a logical group of hosts listed in the Logical Groups tree in the Resources tab.

Symptom 1: Some of the storage systems which already

have been configured by the Setup Global-Active Device dialog box might not appear in the Storage Systems list in the Primary Site tab of the dialog box.

Symptom 2: The KAIC16141-E error appears in the dialog box, and the allocation cannot be completed.

Device Manager GUI

All*

When a host is selected in the Allocate Volumes dialog box, duplicated errors might appear.

Device Manager GUI

All*



In HCS for VVol, when the Delete Storage Container task

is being processed, launching the Task Details dialog box while the task is running or after the task is finished, fails with the KAIC15021-E error.

Device Manager GUI

All*

When a host is selected in the Allocate Volumes dialog box, duplicated errors might appear.

Device Manager GUI

All*

On a virtual machine that uses VVol functionality provided by VMware vSphere 6.0 or later, other storage systems volume information might be deleted from the Hitachi Device Manager database, and operations using those volumes failed sometimes.

Device Manager Sever

All*

When performing a new installation in a cluster environment, if the name of the installation-destination folder contains the character ")", the following symptoms occur and setting up a cluster environment fails.

Symptom 1:

The KAIB10222-E or KAIB64121-E message might appear.

Symptom 2:

The hcmds64clustersrvstate and

hcmds64clustersrvupdate commands terminate without a message.

Installer Windows

Device Manager contain vulnerability that allows unauthorized disclosure of arbitrary files.

Device Manager GUI

All*

When the CLI ModifyPort command is run by specifying the vlanid parameter for a VSP G200, G400, G600 or G800 port, the command might fail with KAIC90083-E (error code=6503).

Device Manager Sever

All*

Known problems

Managing file storage VVols

Because the storage container tasks cannot be performed in the file storage

VVols environment, do not add a VASA provider (file storage) in HCS for VVol.

Performing operations on mainframe volumes

When you open the following dialog boxes by selecting mainframe volumes, error

messages indicating that the operation is not supported should be displayed;

however, the incorrect error messages below are displayed instead:

Dialog boxes:

Allocate Like Volumes

Shred Volumes

Create Pool

Expand Pool

Error messages:

KAIC15017-E

KAIC16993-E



Creating replication configurations with local copy by using the Replication tab:

When using the Create Copy Topology wizard or Expand Copy Topology wizard in

the Replication tab, creation of local copy pairs might fail with the KAIC05960-E

(Detail:RPM-03327) message.

Conditions:

This problem occurs when all of the following conditions are met.

1. Create multi-target configurations of local copy.

2. The multi-target configurations described in 1. are created with multiple

copy groups by a single operation of the Create Copy Topology wizard or

Expand Copy Topology wizard.

3. The copy types of the copy groups to be created in 2. are a combination of

ShadowImage and Thin Image.

4. When configuring the copy groups described in 3., AUTO is selected for

the MU Number of each copy group configuration.

Workaround:

Apply either of the following operations for creating multi-target configurations of

local copy.

1. Create copy groups of ShadowImage first, and then create copy groups of

Thin Image.

2. Select a specific number for MU Number from the applicable numbers for

ShadowImage and Thin Image, instead of selecting AUTO.

Allocating volumes by using the Replication tab:

When allocating a volume by using the Replication tab and if all of the following

conditions met, the allocation might fail with the KAIC05960-E message (details

= RPM-01004) or KAIC70033-E message (details = KAVN02854-E+RPM-01004).

Conditions:

1. In the Resource Group window on the Administration tab, resources that

meet either of the following conditions have been registered to a resource

group:

Unassigned volume LDEV ID

Unassigned host group number

2. Create a volume or new host group using any of the following functions:

Select Volumes in the Create Copy Topology wizard

Select Volumes in the Expand Copy Topology wizard

Allocate Command Device in the Set up for Replication window

Workaround:

In the Resource Group window on the Administration tab, do not register the

following resources to any resource group:

Unassigned volume LDEV ID

Unassigned host group number

If you want to register the volumes or host groups created by the task to a

resource group, do so after the task finishes.



Using a system account to log in to Device Manager, and then operating VSP G200,

G400, G600, G800

If you use a system account to log in to Device Manager, the functions that you

can perform from the maintenance utility might be unintentionally restricted.

To use the functions, log in to Device Manager as a user who belongs to a user

group that has the Admin role.

Limit on the VASA Provider (file storage) that HCS for VVols can manage:

In the file storage VVols environment managed by VASA Provider (file storage),

both of the following conditions must be met:

The maximum number of file systems is 10 or fewer.

The maximum number of storage containers is 5 or fewer.

Command device candidate display in the preparation for the replication

configuration:

If you are using a VSP G1000, VSP G200, G400, G600, G800 storage system, a

Virtual Storage Platform, or HUS VM storage system, and the resources in the

storage system are managed by dividing them into multiple resource groups, you

can use the following LDEV IDs for the command device on the Allocate

Command Device dialog box of the Replication tab.

If you are using Virtual Storage Platform or HUS VM storage system:

LDEV IDs registered in resource group 0

If you are using VSP G1000, VSP G200, G400, G600, or G800 storage

system:

LDEV IDs registered in a resource pool on the default virtual storage

machine

However, the following LDEV IDs that cannot be used as the command device are

also displayed as candidates on the Allocate Command Device dialog box.

If you are using Virtual Storage Platform or HUS VM storage system:

LDEV IDs other than those registered in resource group 0

IF you are using VSP G1000, VSP G200, G400, G600, or G800 storage

system:

LDEV IDs registered in a resource pool that is not on the default virtual

storage machine

If you use one of the LDEV IDs described above as the command device, the

following problems might occur.

A task for creating or expanding a copy topology fails with the message

KAIC05956-E.

A task for shrinking a copy topology fails with the message KAIC05957-E.

During an operation related to a copy topology, the Replication Manager

task registered by the launched Change Pair Status wizard does not

succeed.

Check for an unused LDEV ID registered in resource group 0 or a resource pool

on the default virtual storage machine in advance, and use that LDEV ID for the

command device.



Incorrect error message displayed in the Configure Remote Paths panel of the Set up

for Replication dialog box

An incorrect error message (KAIC70022-E (details = RPM-05004)) might be

displayed in the Configure Remote Paths panel in the Set up for Replication.

Device Manager message

Error code: KAIC70022-E

Error message: Data could not be collected from Replication Manager.

(details = <detailed-information>) See the message given in the details,

resolve the problem, and then try again.

Replication Manager message in <detailed-information>

Error code: RPM-05004

Error message: A parameter is invalid. (parameter = <parameter>, value

= <value>)

This problem occurs when either of the following conditions are met:

1. The following operations are performed while the Set up for Replication

dialog box is displayed.

a. The selected storage system is removed in another Device Manager

window.

b. Click Refresh Display in the dialog box.

2. The following operations are performed while the Select Storage

Systems and Copy Type dialog box of the Set up for Replication

dialog box is displayed.

a. The selected storage system is deleted in another Device Manager

window.

b. Click OK in the Selected Storage Systems and Copy Type

dialog box.

If the error message appeared, select a different storage system in the Selected

Storage Systems and Copy Type dialog box.



Allocate Like Volumes dialog box

When you open the Allocate Like Volumes dialog box and select a volume, if a

port that is being used in the LUN path of that volume is being used by multiple

virtual storage machines, the automatically selected LUN path might differ from

the LUN path of the volume that you selected when you opened the dialog box.

In this case, manually edit the LUN path.

Changing the IP address of the SVP for storage systems in the VSP G200, G400,

G600, and G800 series:

When the IP address of an SVP for a VSP G200, G400, G600, or G800 storage

system is changed, either Edit Storage Systems from the GUI or the Device

Manager CLI command AddStorageArray must be run, but then might fail with

one of the following errors:

Edit Storage Systems

KAIC05602-E Communication with the RMI server failed. Make sure the

specified IP address or port number are correct, and then check the network

connection. (IP address = <IP address>, Port number = <Port number>)

Device Manager CLI command AddStorageArray

KAIC90083-E Communication with the RMI server failed. Make sure the

specified IP address or port number are correct, and then check the network

connection. (IP address = <IP address>, Port number = <Port number>)

In this case, do the following:

1. Stop all Hitachi Command Suite (HCS) products.

2. Open the following properties file in a text editor.

File name: dispatcher.properties

File location:

In Windows

<HCS-installation-

folder>\DeviceManager\HiCommandServer\config\dispatcher.prope

rties

In Linux

<HCS-installation-

directory>/HiCommandServer/config/dispatcher.properties

3. Write down the values of the following properties in the properties file

described in (2):

server.dispatcher.daemon.pollingPeriod

server.dispatcher.daemon.configUpdate.detection.interval

4. Change the values of the properties as follows:

server.dispatcher.daemon.pollingPeriod=0

server.dispatcher.daemon.configUpdate.detection.interval=0

5. Save the changes, and then close the text editor.

6. Open the following properties file in a text editor:

File name: base.properties

File location:

In Windows

<HCS-installation-folder>\ReplicationManager\conf\base.properties

In Linux



<HCS-installation-

directory>/ReplicationManager/conf/base.properties

7. Write down the value of the following property in the properties file

described in (6).

base.operationmode.forcemaintenancemode

Note: The value for the above property might not exist. In this case, the

configured value is false.

8. Change the value of the property as follows:

base.operationmode.forcemaintenancemode=true

9. Save the changes, and then close the text editor.

10. Restart the HCS products.

11. Run the following command to stop Tiered Storage Manager:

In Windows

<HCS-installation-folder>\TieredStorageManager\bin\htsmserver

forcestop

In Linux

<HCS-installation-

directory>/TieredStorageManager/bin/htsmserver forcestop

12. Run the Edit Storage Systems task on the storage system for which the

IP address of the SVP was changed.

Note: If the task fails with the error KAIC05602-E, run the task again.

13. Stop all HCS products.

14. Following the same procedure as in steps (2) through (5), use a text

editor to change the values of the properties described in (3) back to their

original values (the values you wrote down), and then save the changes.

15. Following the same procedure as in steps (6) through (9), use a text

editor to change the value of the property described in (7) back to its

original value (the value you wrote down), and then save the changes.

Note: If the property did not exist in the properties file in (7), delete the

line that was added in (8) or set the value of the property to false.

16. Start the HCS products.



Device Manager GUI event notification

The following event does not support email notification.

Data collection tasks

Installing Device Manager agent on a host running Solaris 11.1 or later:

The following error message is output during installation if you overwrite or

upgrade the installation of Device Manager agent on a host running Solaris 11.1

or later.

pkgadd: ERROR: The package <HDVMAgent> is currently installed on the system

in the global zone. To install the new instance of this package in the global zone

only, you must specify the -G option. To install the new instance of this package

in all zones you must first remove the existing instance of this package from the

global zone first (via pkgrm) and then install the new instance of this package in

all zones.

pkgadd: ERROR: package <HDVMAgent> cannot be installed on this system/zone

In this case, the Device Manager agent version is not updated after the

installation. You can verify the version by using the following command.

# /opt/HDVM/HBaseAgent/bin/hbsa_modinfo

module name: hdvm

description: Device Manager Agent

version : 8.1.4-00

module name: hrpm

description: Replication Manager Agent

version : 8.1.4-00

If this problem occurs, uninstall Device Manager agent, and then reinstall again.

Installation precautions

When you install Hitachi Command Suite, some components require that you

take some precautions. The following table lists the components and the location

of the precaution information:

Component Reference

Device Manager See “Installing” in the Hitachi Command Suite Installation and



Server Configuration Guide.

GUI

See the online help.

CLI See “Requirements for CLI Operations” in the Hitachi Command Suite CLI Reference Guide.

Device Manager

Agent

See Installing the Device Manager Agent in Windows and

Installing the Device Manager Agent in Linux in the Hitachi Command Suite Installation and Configuration Guide.

Usage precautions

Deleting copy pairs by using the Replication tab and refreshing storage systems at the same time

When all of the following conditions are met, deleting copy pairs by using the

Replication tab might fail with the KAIC05961-E message (details = RPM-01004).

Conditions:

1. For the Shrink Copy Topology or Remove Local Copy Groups tasks on the

Replication tab, one of the following check boxes is selected:

When removing the specified remote copy pairs, also delete the

secondary volumes.

When removing the specified local copy pairs, also delete the

secondary volumes.

2. Some volumes of the copy pairs to be deleted belong to storage systems

that are being managed by one or more instances of Device Manager at

remote sites.

3. The storage systems in 2. are being refreshed by Device Manager at the

remote sites.

Solution:

Do the Unallocate Volumes and Delete Volumes tasks by using the following

procedure in the order listed:

1. Refresh the storage systems described in Conditions 3.

2. After the storage systems described in 1. have been refreshed, unallocate

volumes.

3. Delete the volumes.

The directories created by the prerequisite checker will remain(Linux).

The prerequisite checker creates the following directories when checking the

prerequisites:

<Installation directory>/TuningManager

/var/<Installation directory>/TuningManager

Directory for saving the database



After checking the prerequisites, if the installation is continued with the same

settings as when the checking was performed, a directory created by the

prerequisite checker is used for the installation directory.

If the same settings used for checking the prerequisites are not used for the

installation, the directories created by the prerequisite checker will remain.

Delete them, if necessary.

Using Device Manager to manage Hitachi Virtual Storage Platform F400, F600, and F800:

1. When using Device Manager to manage Hitachi Virtual Storage Platform

F400, F600, and F800:

Register the storage system type as "VSP Gx00."

When registration is complete, the storage system model is displayed as

VSP G400, G600, or G800.

The storage system name might also be displayed as VSP G400, G600, or

G800.

It is recommended that you change the storage system name to

distinguish VSP F400, F600, and F800 from VSP G400, G600, and G800.

2. Text in Help and in the manual:

Help and the manual do not mention VSP F400, F600, or F800. Substitute

the following terms listed in Before with the terms listed in After when

reading Help and the manual:

Before:

VSP G400

VSP G600

VSP G800

After:

VSP G400 or VSP F400



Conditions for the status of required resource settings to become "Complete" in the Set up for Replication dialog box

Even if the status displayed in the upper left of each resource panel is "Complete"

in the Set up for Replication dialog box, an attempt to create a copy topology

might fail.

Verify the resource status is normal before attempting to create a copy topology,

even if the setting status is "Complete." In addition, verify the system

requirements are met for the command device to be connected to the pair

management server.

Displaying information about file storage VVols takes time:

In HCS for VVols on Windows, displaying information about file storage VVols

might take more than 5 seconds.

In this case, edit the "hosts" file in Windows to add an entry for the host name

and IP address of the VASA Provider (file storage).

If the host name of the VASA Provider (file storage) can be resolved to an IP

address, the display time might improve.



Installation of the Device Manager server and Hitachi File Services Manager (HFSM) on the same server and importing an HFSM databases

If you import an HFSM database by executing the hcmdsdbtrans command on a

server where the Device Manager server and HFSM are both installed, the

command fails with the KAPM05915-E message.

If this problem occurs, perform the following recovery procedure:

Step 1: Set the management server of the HFSM user account to a primary

server.

<HFSM-installation-path>\Base\bin\hcmdsprmset /host 127.0.0.1 /port non-SSL-

port-number

Step 2: Execute the following command to import the HFSM database.

<HFSM-installation-path>\Base\bin\hcmdsdbtrans /import

/type FileServicesManager /workpath XXX /file YYY /auto

XXX: Working directory (must be empty).

YYY: Archive file of the HFSM database.

Step 3: Set the management server of the HFSM user account to a secondary

server.

To perform this step, see the latest manual of Hitachi File Service Manager

(HFSM) or Storage Navigator Modular 2 (SNM2).

When a copy pair operation using the CLI fails with the error code "7783," "7756," or "7757."

If a copy pair operation is performed from the CLI, the operation might time out

and the following error codes might be displayed:

KAIC90083-E (error code: 7783)

KAIC90083-E (error code: 7756) An error occurred during the processing

of the service by the host agent. The host agent error message is

"Processing will now stop because the status of the Thin Image pair was

changed and is now invalid. (". The command error message is "raidcom:

[EX_EWSTOT] Timeout waiting for specified status".

KAIC90083-E (error code: 7757) An error was detected in the host agent.

Details: "A timeout occurred when the RAID Manager command was

executed.(ErrorCode=6126)"

The copy pair operation will continue to run in the storage system even if the

operation ends in an error. To check the status of the copy pair operation, refresh

the storage system, and then execute one of the following commands to check

the pair status:

GetStorageArray (subtarget=ReplicationInfo)

GetStorageArray (subtarget=SnapshotGroup

snapshotgrpsubinfo=ReplicationInfo) (#)

#: This command can only be used for Thin Image pairs.

If you execute the ModifyReplication command, you can check the status and the

splitTime of the pair by executing one of the following commands:



1. ModifyReplication (operation=split) or (operation=resync)

If the pair status is not Split, the pair operation is being performed. Wait a

while, refresh the storage system, and then verify the following:

The pair status is Split.

The value of splitTime is later than the time when the operation

was executed.

2. ModifyReplication (operation=restore)

If the pair status is Reverse-Copying, the pair is being restored. Wait a

while, refresh the storage system, and then check that the pair status is

Split.

In cases where operation=resync or operation=restore, if the pair status is Pair

after the storage system has been refreshed, you need to split the pair manually.

Perform ModifyReplication (operation=split) on the target pair.

Displaying the capacity for file storage VVols:

If you expand the capacity of file systems by using SMU, the capacity of the file

systems and associated storage containers is not refreshed to the expanded

value in HCS for VVols.

To reference the latest capacity, use SMU or HCS.

Editing or deleting storage containers for file storage VVols:

In a file storage VVol environment, you can edit or delete related storage

containers by using HCS for VVols, even when virtual machines are operating on

the datastore.

When editing or deleting a storage container, first confirm with the VM

administrator whether the VVol environment is operating.

Creating or editing the storage container for file storage VVols:

If multiple users create or edit storage containers at the same time by using HCS

for VVols, a file system might be added to the wrong storage container.

Displaying the Enterprise Virtual Server (EVS) of a file system on file storage VVols:

In HCS for VVols, an incorrect value is displayed as the EVS of a file system.

To check the correct EVS, use SMU or HCS.

Displaying the Enterprise Virtual Server (EVS) and status of a file system on file storage VVols:

In HCS for VVols, the EVS value and status of a file system might not be

displayed.

To check the correct EVS and status, use SMU or HCS.



Documentation

Available documents

Document name Document number

Issue date

Hitachi Command Suite User Guide MK-90HC172-22 November 2015

Hitachi Command Suite CLI Reference Guide MK-90HC176-22 November 2015

Hitachi Command Suite Tiered Storage Manager CLI Reference Guide

MK-90HC177-19 November 2015

Hitachi Command Suite Messages MK-90HC178-22 November 2015

Hitachi Command Suite Audit Log Reference Guide MK-92HC213-08 November 2015

Hitachi Command Suite Installation and Configuration Guide MK-90HC173-22 November 2015

Hitachi Command Suite Administrator Guide MK-90HC175-22 November 2015

Copyrights and licenses

© 2015 Hitachi, Ltd. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording, or stored in a database or retrieval system for any purpose without the express written permission of Hitachi, Ltd.

Hitachi, Ltd reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. This document contains the most current information available at the time of publication. When new or revised information becomes available, this entire document will be updated and distributed to all registered users.

Some of the features described in this document might not be currently available. Refer to the most recent product announcement for information about feature and product availability, or contact Hitachi, Ltd., at https://support.hds.com/en_us/contact-us.html.

Notice: Hitachi, Ltd., products and services can be ordered only under the terms and conditions of the applicable Hitachi Data Systems Corporation agreements. The use of Hitachi, Ltd., products is governed by the terms of your agreements with Hitachi Data Systems Corporation.

By using this software, you agree that you are responsible for:

1) Acquiring the relevant consents as may be required under local privacy laws or otherwise from employees and other individuals to access relevant data; and

2) Verifying that data continues to be held, retrieved, deleted, or otherwise processed in accordance with relevant laws.

Hitachi is a registered trademark of Hitachi, Ltd., in the United States and other countries. Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., in the United States and other countries.

Archivas, BlueArc, Essential NAS Platform, HiCommand, Hi-Track, ShadowImage, Tagmaserve, Tagmasoft, Tagmasolve, Tagmastore, TrueCopy, Universal Star Network, and Universal Storage Platform are registered trademarks of Hitachi Data Systems Corporation.




AIX, AS/400, DB2, Domino, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, OS/390, RS6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/OS, z9, zSeries, z/VM, z/VSE are registered trademarks and DS6000, MVS, and z10 are trademarks of International Business Machines Corporation.

All other trademarks, service marks, and company names in this document or website are properties of their respective owners.

Microsoft product screen shots are reprinted with permission from Microsoft Corporation.

Notice on Export Controls. The technical data and technology inherent in this Document may be subject to U.S. export control laws, including the U.S. Export Administration Act and its associated regulations, and may be subject to export or import regulations in other countries. Reader agrees to comply strictly with all such regulations and acknowledges that Reader has the responsibility to obtain licenses to export, re-export, or import the Document and any Compliant Products.

Hitachi Data Systems is a registered trademark and service mark of Hitachi, Ltd., and the Hitachi Data Systems design mark is a trademark and service mark of Hitachi, Ltd. All other brand or product names are or may be trademarks or service marks of and are used to identify products or services of their respective owners.

Adobe and Flash Player are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States and/or other countries.

IBM, AIX are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries.

Brocade is a trademark or a registered trademark of Brocade Communications Systems, Inc. in the United States and/or in other countries.

BSAFE is either a registered trademark or a trademark of EMC Corporation in the United States and/or other countries.

EMC and CLARiiON are registered trademarks of EMC Corporation.

IBM, ESCON are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

HP is a trademark of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.

HP Tru64 UNIX is a trademark of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.

HP-UX is a product name of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.

HP and StorageWorks are trademarks of Hewlett-Packard Development Company, L.P. in the U.S. and other countries.

IBM is trademark of International Business Machines Corporation, registered in many jurisdictions worldwide.

IBM, OS/390 are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

IBM, z/OS are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide.

Oracle and Java are registered trademarks of Oracle and/or its affiliates.

Linux® is the registered trademark of Linus Torvalds in the U.S. and other countries.

Microsoft is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Microsoft .NET is software for connecting people, information, systems, and devices.

Microsoft and Internet Explorer are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.



Mozilla is a trademark of the Mozilla Foundation in the U.S and other countries.

NetWare is a registered trademark of Novell, Inc.

RC2 is either a registered trademark or a trademark of EMC Corporation in the United States and/or other countries.

RC4 is either a registered trademark or a trademark of EMC Corporation in the United States and/or other countries.

Red Hat is a trademark or a registered trademark of Red Hat Inc. in the United States and other countries.

RSA is either a registered trademark or a trademark of EMC Corporation in the United States and/or other countries.

Hitachi Device Manager includes RSA BSAFE(R) Cryptographic software from EMC Corporation.

All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc., in the United States and other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc.

VERITAS is a trademark or registered trademark of Symantec Corporation in the U.S. and other countries.

VMware and VMware vSphere ESX are registered trademarks or trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows NT is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries.

Windows Server is either a registered trademark or a trademark of Microsoft Corporation in the United

States and/or other countries.

Windows XP, Windows Vista, and Windows 7 are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

This product includes software developed by Ben Laurie for use in the Apache-SSL HTTP server project.

This product includes software developed by Borland Software Corp.

This product includes software developed by Ralf S. Engelschall [email protected] for use in the mod_ssl project (http://www.modssl.org/).

Hitachi Device Manager and Hitachi Tiered Storage Manager include some parts whose copyrights are reserved by Oracle and/or its affiliates.

Hitachi Device Manager Software includes some parts whose copyrights are reserved by Unix System Laboratories, Inc.

SUSE is a registered trademark or a trademark of SUSE LLC in the United States and other countries.

Kerberos is a name of network authentication protocol created by Massachusetts Institute of Technology.

This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/).

This product includes software developed by the Java Apache Project for use in the Apache JServ servlet engine project (http://java.apache.org/).

This product includes software developed by Andy Clark.

Other company and product names mentioned in this document may be the trademarks of their respective owners. Throughout this document Hitachi has attempted to distinguish trademarks from descriptive terms by writing the name with the capitalization used by the manufacturer, or by writing



the name with initial capital letters. Hitachi cannot attest to the accuracy of this information. Use of a trademark in this document should not be regarded as affecting the validity of the trademark.