Hitachi File Services Manager 6.4.2-00 Release Notes

About this document

This document (RN-90HDI013-55, March 2018) provides late-breaking information about Hitachi File Services Manager 6.4.2-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 Vantara partners who license and use Hitachi File Services Manager.

Accessing product downloads

Product software, drivers, and firmware downloads are available on Hitachi Vantara Support Connect: https://support.hitachivantara.com/.

Log in and select Product Downloads to access the most current downloads, including important updates that may have been made after the release of the product.

About this release

This release is a major release that adds new features and resolves multiple known problems.

Product Package Contents

Table 1. Product Package Contents

Documentation

In addition to the help system, Hitachi File Services Manager ships with the following:

         Hitachi Data Ingestor Installation and Configuration Guide

         Hitachi Data Ingestor Cluster Administrator's Guide

         Hitachi Data Ingestor CLI Administrator's Guide

         Hitachi Data Ingestor Error Codes

         Hitachi Data Ingestor Cluster Troubleshooting Guide

         Hitachi Data Ingestor Cluster Getting Started Guide

New Features and Enhancements

Table 2. New Features and Enhancements

Restrictions

         On the page of Task Management dialog, some keyboard operations may not be available. For example, choosing items from pull-down menu cannot be done from keyboard.

         In case user set the migration interval for 4 weeks with either of arcmigset or arcmigedit command, the operation you have done through [Task Edit] in migration task window will not be reflected to the settings.

         User cannot specify a character which consists of 4 bytes code in UTF-8 to following field.

o    [Task Comment] field in [Add Task] and [Edit Task]

o    [File name] field and [Directory path] field in policy information

o    Arguments of arcmigset and arcmigedit commands

         When combining with HCP, do not use symbols (other than alphabets and numbers) for a user name or password of HCP tenant administrator.

         By using HFSM 6.1.1 or later, you cannot manage HDI 5.4.1 and update from HDI 5.4.1 to any version. Please use HFSM 5.4.1 for updating to and managing HDI 5.4.1. In case you want to manage HDI nodes with HFSM 6.1.1 or later, please update to HDI 6.1.1 or later and do not update to HDI 5.4.1.

         When updating the node software from HFSM using Firefox, the screen may be frozen during the update. In this case, click [Refresh Tree] to update the information on the window, and then verify that the system version of both nodes is installed software version.

         When an HFSM is newly installed, if the path name of installation location contains a parenthesis and does not contain a space, an error with KAQM30012-E occurs and the installation fails. Install it to a folder that does not meet the above conditions.

Operating System Requirements

Table 3. Supported platforms for Hitachi File Services Manager management server

Table 4. Supported platforms for Hitachi File Services Manager management console

#1: OS that does not support TLS1.1 and TLS1.2.

Required Web browser

Table 5. Supported Web browser for Hitachi File Services Manager management console

Required Programs for Processing Node

Hitachi Data Ingestor is required on the network node controllers.

Memory and Disk Space Requirements

The following table lists memory and disk space requirements for Hitachi File Services Manager:

Table 6. Hitachi File Services Manager Requirements

Fixed Problems

• Following defect has been fixed by Hitachi File Services Manager 6.4.2-00

• Following defect has been fixed by Hitachi File Services Manager 6.4.2-00

• Following defect has been fixed by Hitachi File Services Manager 6.4.2-00

• Following defect has been fixed by Hitachi File Services Manager 6.4.2-00

Precautions

• Hitachi File Services Manager version 6.4.2-00 and later cannot manage nodes with the software earlier than 6.4.2-00 installed. For the procedure to upgrade the node software, refer to "Updating software" in Hitachi Data Ingestor Cluster Administrator's Guide.
   
• When installing the following programs into the same computer as Hitachi File Services Manager, upgrading is required to the following version:
  • Hitachi Device Manager 8.5.2 or later.
  • Hitachi Compute Systems Manager 7.5.1-00 or later.
  • JP1/Automatic Operation 10-10 or later.
  • SVP software for VSP Gx00 series which can coexist with HFSM is version 83-03-01-XX/XX or later
     
• The Automatic LU creation function allows easy creation of LUs without RAID group consideration (it cannot choose a RAID group and disk drives to create an LU). Therefore, notice the following implications before using the function:
  • Do not share the storage subsystem with another HDI instance or SAN.
  • A RAID group might be automatically created on a disk drive.
  • An LU might be automatically created in a RAID group.
     
• For better control on performance optimization and workload, use Storage Navigator Modular 2 to create RAID groups and LUs.
   
• When upgrading File Services Manager that is integrated with the Device Manager GUI, the upgrade will release the integration. Re-authenticate File Services Manager to Device Manager after the upgrade.
   
• The management method of HCP has changed to improve the tenant management operations. When migrating data to HCP, you need to take one of the following actions:
  • Register the tenant administrator account in HCP with the same name and password as the data access account.
  • Configure the tenant administrator account through the HCP Settings of Configuration Wizard.
     
• When using the HCP Settings in Configuration Wizard, the namespace named system-backup-data is automatically allocated for backing up the system configuration information.
   
• When upgrading from the Hitachi Data Ingestor version earlier than 4.0.0-00, a tenant will become available for use by several systems. If you had migrated data to HCP before the update, confirm with your HCP administrator that the namespace system-backup-data is already created in HCP.
   
• Clicking an anchor or a button may result in opening additional blank window. If this happens, close the unnecessary window. If this problem persists, create a new Windows user account and then operate the browser with the new user.
   
• In a Windows Server 2012 R2, Windows 8.1, or Windows 10 environment, the management console might show display anomalies such as a line the tab in under some windows. These lines do not affect the operations or the function of the console.
   
• Using a long password (65 character or more) for a private key for public key certificate (--key-passwd), access from a browser is disabled after the update installation. To prevent this, run the certctl command with the　--reset option specified to initialize the certificate before update to a version 6.1.1-00 or later.
   
• During the course of an update installation, the following anomalies will occur in the HDI single node and cluster models if the certificate is NOT initialized.
  • Node restart fails after completing the node0 update;
  • HFSM access to the nodes becomes unavailable;
  • and the message KAQM20046-E is displayed on the HFSM screen.
    
    Perform the following recovery procedure:

1. Login to the node1 via ssh and execute following steps.

a)     Confirm the cluster node and resource group status as below by clstatus command.

                                                              i.        Node status: node 0 is "INNACTIVE", node1 is "UP"

                                                             ii.        Resource Group status: Resource groups of both nodes are running on the node1 and show status "Online"

b)    Confirm the HDI version is NOT updated, by versionlist command.

c)     Initialize certificate by certctl command with reset option (--reset).

2. 2) Login to node0 via ssh and execute following steps.

a)     Confirm the HDI version is updated, by versionlist command.

b)    Initialize certificate by certctl command with reset option (--reset).

c)     Start node0 by ndstart command.

d)    Confirm node0 status is "UP" by clstatus command.

2. Log in to HFSM to perform the following steps:

a)     Execute "Refresh Processing Node" to check connection error doesn't occur.

b)    Failover both resource groups to node0 from "Cluster Management" screen.

c)     Execute "Refresh Processing Node" to refresh the HFSM information.

d)    Execute "Update Software" from "System Software" pane to update node1.

e)     After the completion of update install, confirm HDI version of both nodes are up to date

f)      Both resource groups are running on node0. Failback one of the resource group whose default host node is node1.
 

• On the security setting in the Advanced tab on WWW browser connected to HDI or management server, clear check boxes for Use SSL2.0 and Use SSL3.0.
• Default TLS version for the communication between the management server and the HDI is TLSv1.2 from HFSM 6.2.0. Therefore HFSM cannot communicate with a HDI 6.1.0 or earlier by default.
  
  To perform software update on a HDI node whose version is 6.1.0 or earlier, first set the TLS version for the communication between the management server and the node in accordance with the procedure below. When the update installation for all nodes is complete, turn the TLS setting back to the previous one.

1.  1)If user.conf exists in the folder: Hitachi-Command-Suite-Common-Component-installation-folder\conf on the management server, add a row. If it does not exist, newly create it with the content below.
   
   ssl.protocol=TLSv1
   
   
    
2. Select Start - HFSM from File Services Manager of Hitachi Command Suite in the Start menu of the management server to start HFSM.2)  
    
3. Select Stop - HFSM from File Services Manager of Hitachi Command Suite in the Start menu of the management server to stop HFSM.
    
4. Click Refresh Processing Node of HFSM to refresh the node.
    
5. Perform software update on node with HFSM. For the procedure to update the software, refer to the Updating software section (page on 14-3) in Hitachi Data Ingestor Cluster Administrator's Guide.
    
6. When the software update is complete, turn back Hitachi-Command-Suite-Common-Component-installation-folder\conf\user.conf of the management server as it was before step 1. (If a row is added, delete the row. If a file is newly created, delete the file).
    
7. Select Stop - HFSM from File Services Manager of Hitachi Command Suite in the Start menu of the management server to stop HFSM. If other Hitachi Command Suite products are installed, stop all HCS products.
    
8. Select Start - HFSM from File Services Manager of Hitachi Command Suite in the Start menu of the management server to start HFSM. If other Hitachi Command Suite products are installed, start all HCS products.
    
9. Click Refresh Processing Node of HFSM to refresh the node.
    
10. Caution for creating a file system when On (Read/Write) is selected for Content sharing

If you did not select Yes for Create Namespace in the Basic tab, names of the namespace for the migration destination HCP system are displayed in pull-down menu. Namespace name other than On (Read/Write) for Content sharing can also be chosen from pull-down menu. Create a file system after confirming the connection to the HCP system by clicking the Test Connection button.