Hitachi NAS Platform F1000 Series Release Notes

Transcription

1 Hitachi NAS Platform F1000 Series Release Notes Copyright 2012, 2016, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED Notice: 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 Data Systems Corporation (hereinafter referred to as "Hitachi Data Systems"). Hitachi Data Systems reserves the right to make changes to this document at any time without notice and assumes no responsibility for its use. Hitachi Data Systems products and services can only be ordered under the terms and conditions of Hitachi Data Systems' applicable agreements. All of the features described in this document may not be currently available. Refer to the most recent product announcement or contact your local Hitachi Data Systems sales office for information on feature and product availability. This document contains the most current information available at the time of publication. When new and/or revised information becomes available, this entire document will be updated and distributed to all registered users. 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. RN-92NAS

2 Table of Contents About This Document... 3 Intended Audience... 3 Getting Help... 3 About This Release... 3 How to obtain a copy... 3 New Features and Important Enhancements... 3 Manual Corrections... 4 Restrictions... 4 Requirement for use Management Console for Single Node Configuration... 7 Fixed Problems Known Problems Usage Precautions for "CIFS bypass traverse checking" function Usage Precautions when integrating HCP Usage Precautions for CIFS Access Log Usage Precautions for Negotiation Mode ( or later) Usage precaution for Internet Explorer 11.0 as Management console Usage precaution for the chunk size of the differential data device ( and later) Usage precaution for "subfolder monitoring" function Caution ACL for the shared directory Caution when deny setting of ACL is prioritized Caution for NFS share creation Caution when outputting system operation information Caution when creating keytab file for Kerberos authentication Caution when editing or releasing link trunking Caution for Read Write Content Sharing Caution for update installation Caution for /etc/hosts file Prerequisite program needed to use a particular function Documentation Port numbers Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 2

3 About This Document This document provides late-breaking information about Hitachi NAS Platform F. 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 authorized service partners who license and use the Hitachi NAS Platform F. 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: 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 These release notes cover version of the Hitachi NAS Platform F. How to obtain a copy This firmware can be downloaded or ordered from The Download Center (TDC) in the Technical Information Service Center (TISC). New Features and Important Enhancements Table 1 New Features and Important Enhancements No Items Contents 1 Enhancements A function to set policies related to Virtual Server performance is added. Version Enhancements A function to output SNMP trap when a network loop is detected or an overlapping IPv6 address is detected at ifadd is added. Version Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 3

4 3 Enhancements A function to collect CIFS service performance statistics is added. Version Enhancements A function to periodically monitor PCI failures in NIC and to perform failover (or port switch) when a PCI failure occurs is added. Version Enhancements CPU to allocate to Virtual Server is optimized and the Virtual Server processing performance is improved. The optimization takes place automatically at update installation from a version earlier than Version Enhancements A function to display hard quota allocated to namespace as disk capacity displayed on NFS client when limiting capacity based on hard quota of namespace while linking with HCP is supported. Version Enhancements Auto mode is added to autocommit function for WORM file system. Version Enhancements The initial value of Default Retention Period for WORM file system is changed from 30 years to 10 days. Also, resetting of the default retention period is enabled. Version Enhancements A confirmation message is output when enabling autocommit function by running fscreate command and fsedit command. Version Manual Corrections Table 2 The corrections of "Hitachi NAS Platform F1000 Series API References" No Location to be corrected Corrections 1 I/O formats for requests and responses Before F- node:9090/mapi/static/mapi-5_3_3.xsd After F- node:9090/mapi/static/mapi-6_0_3.xsd Restrictions While a file path that is a data import target contains special characters, if a file or directory being imported is migrated from HNAS F to HCP, a message KAQM37094-E may be output. If "Invalid XML in custom metadata" is reported as detailed information of the above message, the migration can succeed by disabling the setting of "Check on ingestion that XML in custom meta data file is well-formed" in HCP name space. Ask the HCP administrator to disable the above setting until the data import is complete. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 4

5 The capacity of the differential-data storage device that can be used for file snapshot creation has been limited to 99% of the total capacity. If the differential-data storage device is used more than 99%, creating the file snapshot is stopped. When performing HFRR copy, KAQR25621-E message is output and the operation may fail by the restriction. If KAQR25621-E message is output, take one of the following actions to increase free capacity so that the used capacity of the differential-data storage device on the secondary site falls below the warning threshold. - Expand the capacity of the differential-data storage device - Delete unnecessary differential-data snapshot If the overflow prevention action is set to the differential-data storage device, the above actions are not necessary. After that, verify the free capacity of the differential-data storage device on the secondary site, and then retry the HFRR copy. If the file path accessed by a CIFS client contains special characters, real-time scanning may not be complete normally. For such files that the real-time scanning is not complete normally, change the file path so as not to contain any special characters and then retry the scanning where necessary. If the specified chunk size is less than the default size of it when the differentialdata storage device is set, the access to file systems suspend temporarily and the user I/O request may fall in the timeout. So, if you want to specify the chunk size less than the default size of it, you should set the differential-data storage device in time except the user service time of the file system. If the notify_delay_time setting is changed by running cifsoptset command, the setting of a CIFS client being connected may not be reflected. To apply the setting, log off with the CIFS client and then log back in. Some part of the graph might not be displayed, if the file system was unmounted during the time period where the request result or the cache hit ratio is displayed in the Monitor tab on the file-system-name window in a single node GUI. A tenant administrator password must be equal to or shorter than 64 characters and contains at least 2 types of characters from 1-byte alphabet, number, and symbol. If you go back to edit screen without finishing Service Configuration Wizard because an error occurs, you might not be able to change password even if [Change password] of tenant administrator is checked on HCP settings. If you want to change password, uncheck the checkbox of [Change password] and then check it again. If you use filter function of sub window on Shares tab for cluster system, the filtering for the attribute: Capacity Management Directory, might not work properly. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 5

6 When a namespace-access account is created on the Add Share dialog or the Edit Share dialog on single node GUI for a file system that meets the following conditions, the created account name is displayed as it is not set (--) in the list of shares and the setting cannot be confirmed. - The namespace type of target file system is [Subtree]. - The files system name contains an underscore (_). To verify whether the account information is set or not for the file system that meets the above conditions, ask an HCP administrator. To create a namespace for access account, ask an HCP administrator and perform the operation on HCP side. When you are using Roaming Home Directory feature enabled file system, and CIFS retry feature enabled, please stop the file access from CIFS clients before restarting CIFS services. When you restart CIFS service in a state that CIFS users still access to the CIFS share, below message will be displayed in HNAS F GUI and CLI, and there may be a case that HNAS F out puts the core file. In such an occasion, please make sure there is no CIFS user access, restart the CIFS service once again, obtain the core file, and contact the maintenance personnel. KAQG62001-W: smbd ended abnormally, and the core file was generated. When Virtual Servers are used in environment where IPv4 and IPv6 networks coexist, if the interface information of one protocol is added, edited, or deleted, communication with a Virtual Server to which an interface of protocol that is not the operation target is assigned as a virtual IP address is disabled. To recover from the above condition, take one of the following operations. - Release the virtual IP address of operation target Virtual Server, and then assign it again. - Reboot the Virtual Server. When a group name containing "at sign" (@) is specified in umapidget command, the following message is output and the operation turns to error. KAQM16110-E Name resolution failed because an account not registered in the authentication server was specified or communication with the authentication server was not possible. When accessing a file system on a Virtual Server from an NFS client using Ipv6 and UDP, the OS may reboot. To use Virtual Server with NFS service, use IPv4 or TCP for communication protocol. When a directory name below is specified in fsctl and fsiusedlist commands, the commands fail. - The directory name contains accent grave (`), asterisk (*), apostrophe ('), ampersand (&), semicolon (;), vertical bar ( ), back slash (\), dollar sign($), opening parenthesis ((), closing parenthesis ()), left angle bracket (<), right angle bracket (>), exclamation mark (!), question mark (?), quotation mark ("), or space, and is enclosed in quotation marks. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 6

7 When importing data from NFS share in a different file server, if the number of directory hierarchies that are import targets exceeds 128, the import processing ends abnormally, and the data cannot be imported. Make sure to have 128 or less import target directory hierarchies. In Resource Settings page on Service Configuration Wizard of Single node, the following phenomenon would occur when you edit a WORM File System with Auto Commit enabled. When you do not open [File system settings] in Create File System dialog box and click OK button, the Create File System dialog box would not close. If this phenomenon occurred, open [File system settings] and click OK button. When you create or edit the WORM file system by using the PUT or POST method of FileSystem resource, and if you set isautocommitenabled property to "true", then it is mandatory to set commitmodesetting property. When editing an unmounted file system on the Edit File System dialog, "No" is displayed for Renaming of Empty Directories, but this setting value is not set actually and the previous setting value is kept. When editing a WORM file system that is mounted while writing is not allowed on the Edit File System window of single node GUI, "Infinite" may be displayed for Default Retention Period on the confirmation window, but this value is not set actually and the setting value for Default Retention Period before the edit is kept. Requirement for use Management Console for Single Node Configuration Operating system requirement for management console Table 3 Supported platforms for management console Operating Systems Windows 7, no service pack or Service Pack 1 Windows 7 Professional Windows 7 Ultimate Windows 7 Enterprise Windows 7 x64 Editions, no service pack or Service Pack 1 Windows 7 Professional Windows 7 Ultimate Windows 7 Enterprise Windows 8 Windows 8 Enterprise Windows 8 Pro Windows 8 x64 Editions Windows 8 Enterprise Windows 8 Pro Windows 8.1 Windows 8.1 Enterprise Windows 8.1 Pro Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 7

8 Operating Systems Windows 8.1 x64 Editions Windows 8.1 Enterprise Windows 8.1 Pro Windows Vista, Service Pack 1 or Service Pack 2 Windows Vista Ultimate Windows Vista Business Windows Vista Enterprise Windows Vista x64 Editions, Service Pack 1 or Service Pack 2 Windows Vista Ultimate Windows Vista Business Windows Vista Enterprise Windows Server 2003, Service Pack 1 or Service Pack 2 Windows Server 2003, Standard Edition Windows Server 2003, Enterprise Edition Windows Server 2003, Datacenter Edition Windows Server 2003 x64 Editions, Service Pack 1 or Service Pack 2 Windows Server 2003, Standard x64 Edition Windows Server 2003, Enterprise x64 Edition Windows Server 2003, Datacenter x64 Edition Windows Server 2003 R2, no service pack or Service Pack 2 Windows Server 2003 R2, Standard Edition Windows Server 2003 R2, Enterprise Edition Windows Server 2003 R2, Datacenter Edition Windows Server 2003 R2, x64 Editions, no service pack or Service Pack 2 Windows Server 2003 R2, Standard x64 Edition Windows Server 2003 R2, Enterprise x64 Edition Windows Server 2003 R2, Datacenter x64 Edition Windows Server 2008 x64 Editions, Service Pack 1 or Service Pack 2 Windows Server 2008, Standard x64 Edition Windows Server 2008, Enterprise x64 Edition Windows Server 2008, Datacenter x64 Edition Windows Server 2008, Service Pack 1 or Service Pack 2 Windows Server 2008, Standard Edition Windows Server 2008, Enterprise Edition Windows Server 2008, Datacenter Edition Windows Server 2008 R2, no service pack or Service Pack 1 Windows Server 2008 R2, Standard Edition Windows Server 2008 R2, Enterprise Edition Windows Server 2008 R2, Datacenter Edition Windows Server 2012 Windows Server 2012, Standard Edition Windows Server 2012, Datacenter Edition Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 8

9 Operating Systems Windows Server 2012 R2 Windows Server 2012 R2, Standard Edition Windows Server 2012 R2, Datacenter Edition Windows 10 Windows 10 Home Windows 10 Enterprise Windows 10 Pro Windows 10 Education Windows 10 x64 Edition Windows 10 Home Windows 10 Enterprise Windows 10 Pro Windows 10 Education Red Hat Enterprise Linux 5.6 Red Hat Enterprise Linux 5.6 Advanced Platform Red Hat Enterprise Linux 6.4 Required Web browser for management console Table 4 Supported Web browsers for management console Web browser Remark Internet Explorer 7.0 Internet Explorer 8.0 Internet Explorer 9.0 Internet Explorer 10.0 Internet Explorer 11.0 #3 Mozilla Firefox 3.6.x #1#2 Mozilla Firefox ESR 10.0.x #1#2 Mozilla Firefox ESR 17.0.x #1#2 Mozilla Firefox ESR 24.1.x #1#2 Mozilla Firefox ESR 31.0.x #1#2 Mozilla Firefox ESR 38.0.x #1#2 32-bit version 32-bit version 32-bit version 32-bit version 32-bit version x86 version x86 version x86 version x86 version x86 version x86 version #1 : x means that it does not depend on the version x. #2 : Supported platforms for Hitachi File Services Manager management console is only Red Hat Enterprise Linux. #3 : If an operation to open a different window or tab is performed, an unnecessary window may be opened concurrently. For the case, see the usage precaution. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 9

10 Required programs for management console Table 5 Required programs for management console Adobe Flash Player 10.1 or later Required Programs When "Manage Migration Task" is executed during HNAS F maintenance, the KAQM23810-E message might be displayed. The error might be caused by the resource group had been stopped at that time. Please retry the operation after confirming resource group status is Online. If problem persists, acquire all log data and contact maintenance personnel. Fixed Problems (1) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When importing data from a different file server, the import processing status becomes inconsistent. The condition: It may occur when one of the following conditions is met. (a) Import processing and migration to HCP concurrently take place. (b) An internal error occurs during import processing. (2) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When importing data from a different server, the import processing ends abnormally. The condition: It occurs when the conditions below are all combined. (a) All-data import is performed. (b) The number of import target directory hierarchies exceeds 95. The evasion plan: Make sure to have 95 or less import target directory hierarchies. (3) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: At the fixed time system setting information storing, the system setting information file output to a home directory of an account for SSH is deleted. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 10

11 The condition: It occurs when the conditions below are all combined. (a) A Virtual Server or single node is used. (b) The starting time of fixed time storing is set within the time slot where daylight saving time is switched. (c) For a location to store the setting information file, a home directory of an account for SSH is specified. The evasion plan: Set the starting time of fixed time storing outside the time slot where daylight saving time is switched. The recovery plan: The setting information file is stored to the home directory of the account for SSH when the fixed time storing works next time. Or store the system setting information file on the [Browse Settings Backup Status] page or by running syslusave command. (4) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When adding or changing interface or changing link trunking setting for a data port, message KAQM05133-E or KAQM05134-E is displayed and the operation may end abnormally. The condition: It occurs when the conditions below are all combined. (a) Only IPv4 is set to the operation target data port or the port with link trunking of data port. (b) The network configuration is in invalid status. (c) One of the following operations is performed. (c-1) Cluster configuration (c-1-1) A virtual IP address of active resource group or Virtual Server is added or changed. (c-1-2) While a virtual IP address is set to an active resource group or Virtual Server, a fixed IP address, netmask, or MTU is changed. (c-1-3) While link trunking is set and a virtual IP address is set to an active resource group or Virtual Server, the link trunking setting is changed. (c-2) Single node configuration (c-2-1) An interface is added or changed. (c-2-2) While link trunking is set and an IP address is set, link trunking setting is changed. The evasion plan: Set the configuration of network to which the data port is connected to be in normal status. The recovery plan: Verify the configuration of network that the data port is connected to. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 11

12 (5) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: The following error messages are reported wrongly. KAQM37021-E KAQM37133-E KAQM37216-E KAQM37390-E KAQS11094-E The condition: It may occur on a failover source node when the recovery operation of KAQG72026-E is performed. The recovery plan: None because error messages are just reported. (6) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When the OS is forcibly stopped or is reset, the Virtual Server or resource group becomes in Partial online status at the next activation. The condition: It may occur when the conditions below are all combined. (a) Virtual Server or single node configuration (b) One of the following operations is performed. (b-1) File system creation, mounting, unmounting, expansion, or deletion (b-2) NFS share creation, edit, or deletion (b-3) Differential-data snapshot mounting or unmounting (c) During or immediately after (b), the OS is forcibly stopped or is reset. The recovery plan: (a) In single node configuration, restore the system setting information. (b) In Virtual Server configuration, restore the system setting information on Virtual Server OS LU. (7) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: If differential-data snapshot mounting or unmounting is suspended, unmounting is disabled after that. The condition: It may occur when the conditions below are all combined. (a) A differential-data snapshot is mounted or unmounted by a user operation or scheduled automatic-operation. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 12

13 (b) The operation of (a) is suspended by one of the following events. (b-1) OS reboot or stop on node (b-2) Node reset (b-3) Virtual Server stop or restart, or change of active node of Virtual Server (b-4) OS stop due to a factor other than (b-1) to (b-3), such as unexpected power outage (c) The differential-data snapshot whose mounting or unmounting is suspended by syncumount command is unmounted. (8) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: In HNAS F internal processing, newly created asynchronous processing thread is wrongly terminated. If it causes the thread of mount processing to be terminated wrongly, the file system information collection by fslist command fails and response wait occurs. The condition: None. The recovery plan: Take actions in accordance with the output error message. Or, run nncreset command to reset and perform failover. (9) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: In synchronization processing between nodes on cluster management daemon, if the cluster daemon ends abnormally due to invalid area referring, cluster operations, such as failover, are disabled. The condition: It may occur when stopping, starting, or resetting node is performed in cluster environment. The recovery plan: Run emergencyshutdown command on both nodes to immediately stop nodes, and then start them again. (10) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: At the first activation of cluster after installation, a reset occurs on a node and starting the other node where failover is performed fails. The condition: It may occur when the conditions below are all combined. (a) One of the following operations is performed. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 13

14 (a-1) New installation or update installation of both nodes (a-2) Update installation from a version earlier than while the cluster stops (b) The cluster is started. (c) Both resource groups are started. The evasion plan: Do not perform cluster start (clstart) of occurrence condition (b), but start the nodes (ndstart) one by one. The recovery plan: Take the steps below. (a) Verify that the status of the reset node is UP. (b) Forcibly stop the resource group that cannot be started. (c) Start the resource group that is stopped in (b). (11) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: Virtual Server startup and failover take time wrongly. The condition: It occurs when one of the following operations is performed. (a) Virtual Server failover (b) Virtual Server startup (c) Virtual Server restart (12) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When SNMPv3 is used, SNMP trap for those other than coldstart or nsnotifyshutdown may not be reported. The condition: It may occur when the conditions below are all combined. (a) SNMPv3 is used and the setting to authenticate the security level of rouser or rwuser is specified (auth or priv). (b) A trap of coldstart or nsnotifyshutdown is received. (c) A trap of other than coldstart or nsnotifyshutdown is received. The evasion plan: Take one of the following actions. (a) Use SNMPv2. (b) Specify the setting (noauth) not to authenticate SNMPv3 rouser or rwuser security level. (13) Following defect has been fixed by Hitachi NAS Platform F Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 14

15 The phenomenon: During communication, a node may reboot. The condition: It may occur at data sending or receiving on CIFS due to a problem in OS. (14) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When the function to import data from a different file server is used, the OS may reboot. The condition: It may occur when the conditions below are all combined. (a) An NFS share is specified as a migration source by running datamigrateconfadd command. (b) Data import is started by running datamigratestart. (15) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When the node OS is stopped, the OS does not stop but may reboot. The condition: It may occur due to a problem in OS when the node OS is stopped or rebooted by a command or GUI. (16) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: The following MIB objects become invalid values. (a) hfrrpairlastcopycompletiondate (b) hfrrpairbaselinesnapshotcreatedate (c) hfrrpaircopyingsnapshotcreatedate The condition: It may occur when one of the following conditions is met. (a) Data copy by HFRR is running. (b) "Error status" of HFRR pair is not "no error". The evasion plan: Refer to the processing result for ruspairlist command that is run with -v option specified, instead of MIB objects. (a) hfrrpairlastcopycompletiondate The information of Last in the ruspairlist processing result Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 15

16 (b) hfrrpairbaselinesnapshotcreatedate The information of Baseline in the ruspairlist -v processing result (c) hfrrpaircopyingsnapshotcreatedate The information of Copying in the ruspairlist -v processing result (17) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: The setting of share level ACL cannot be restored even when all-system LU recovery is performed by running syslurestore command. The condition: It occurs when syslurestore command is run on a physical node in cluster configuration. (18) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: Incorrect accesses to files and directories outside the share are enabled in CIFS share. This problem is reported with the following Common Vulnerabilities and Exposures. CVE The condition: It occurs when the conditions below are all combined. (a) At the secondary site in Hitachi File Remote Replicator (HFRR) environment, the latest differential-data snapshot is made visible. (b) The front portion of the absolute path of CIFS share directory for making the latest differential-data snapshot visible and that of the absolute path of a different CIFS share directory at secondary site are the same, like the example below. Example for (b): Under the following conditions, the front portion of "/mnt/fs01/cifs_ssnap" is the same as that of "/mnt/fs01/cifs_ssnap_test". - The absolute path of CIFS share directory for making the latest differential-data snapshot visible: /mnt/fs01/cifs_ssnap - The absolute path of CIFS share directory that is different from the one for making the latest differential-data snapshot visible: /mnt/fs01/cifs_ssnap_test Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 16

17 (c) Using NFS service, a symbolic link for the file or directory on the CIFS share directory whose front portion of absolute path is the same as that of the CIFS share directory for making the latest differential-data snapshot visible is created on the CIFS share for making the latest differential-data snapshot visible. The evasion plan: Stop making the latest differential-data snapshot visible. (19) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: When a character string containing a left square bracket is specified at import definition setting information, operations with data import and HCP combined are disabled. The condition: (a) Data import using CIFS protocol It occurs when an import definition is added with a character string containing a left square bracket specified to one of the following setting items and then the setting is edited. (a-1) Import definition name (a-2) Directory path (a-3) Mapping file name (b) Data import using NFS protocol It occurs when an import definition is added with a character string containing a left square bracket specified to one of the following setting items and then verification or import is started. (b-1) Import definition name (b-2) Directory path The evasion plan: Do not use a left square bracket for setting items listed in occurrence condition. (20) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: Even though there is free capacity in a file system, if multiple files/directories are created at a time, an error of insufficient capacity occurs and the files/directories may not be created. The condition: It occurs when multiple files/directories are created at the same time. The problem is likely to occur when the file system size is 256GB or less. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 17

18 (21) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: File access from an NFS client hangs up, or file access from a CIFS client turns to time-out. The condition: It may occur when the conditions below are all combined. (a) Mounting is performed while the quota function is enabled. (b) A file on a file system is accessed. (c) One of the following events occurs on the file system during (b). (c-1) The capacity of a device to store differential-data is not enough. (c-2) Virtual LU pool depletion (c-3) Failure of storage system or internal hard disk drive The recovery plan: Take the steps below. (a) Run nncreset command to start the OS of the node where the problem occurs. (b) Refer to the "Recovering from file system errors" section in "Cluster Troubleshooting Guide" or "Single Node Troubleshooting Guide" and perform recovery operation for occurrence condition (c). (22) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: File access from an NFS client hangs up, or file access from a CIFS client turns to time-out. The condition: It may occur when the conditions below are all combined. (a) A file on a file system is accessed. (b) One of the following events occurs on the file system during (a). (b-1) The capacity of a device to store differential-data is not enough. (b-2) Virtual LU pool depletion (b-3) Failure of storage system or internal hard disk drive The recovery plan: Take the steps below. (a) Run nncreset command to start the OS of the node where the problem occurs. (b) Refer to the "Recovering from file system errors" section in "Cluster Troubleshooting Guide" or "Single Node Troubleshooting Guide" and perform recovery operation for occurrence condition (b). (23) Following defect has been fixed by Hitachi NAS Platform F Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 18

19 The phenomenon: The OS may reboot. The condition: It may occur when the conditions below are all combined. (a) A file is accessed while specifying a path name containing an upper directory. (b) The upper directory specified in (a) is deleted. (24) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When an invalid SMB request is sent from an attacker to a CIFS share, the CIFS service may stop due to incorrect memory access. This problem is reported with the following Common Vulnerabilities and Exposures. CVE The condition: It occurs when a user-authenticated attacker sends an SMB request with character code flag falsified to a CIFS share. (25) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: Starting and stopping resource group, starting, stopping and rebooting OS, and starting, stopping and failing over Virtual Server take time. The condition: It may occur when the conditions below are all combined in Virtual Server or single node configuration. (a) NFS service is used with TCP connection. (b) Write is performed form an NFS client to an NFS share file. (c) One of the following operations is performed. (c-1) Virtual Server configuration (c-1-1) Virtual Server failover (c-1-2) Virtual Server start (c-1-3) Virtual Server stop (c-1-4) Virtual Server reboot (c-2) Single node configuration (c-2-1) OS start (c-2-2) OS shutdown (c-2-3) OS reboot Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 19

20 (c-2-4) Resource group start (c-2-5) Resource group stop (26) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: An object under a renamed directory cannot be migrated. The condition: It may occur when the conditions below are all combined. (a) HCP is combined. (b) During pre-processing of the migration, a directory is renamed. The recovery plan: Run arccorrection command to rebuild the management information of file system. (27) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: An object whose migration fails is excluded from the migration target after that. The condition: It may occur when the conditions below are all combined. (a) HCP is combined. (b) An error occurs in the post-processing of migration. (c) In the migration performed after (a), transfer of some files or directories fails. The recovery plan: Run arccorrection command to rebuild the management information of the file system. (28) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: Restoration of a file or directory fails. The condition: It may occur when the conditions below are all combined in a file system that is combined with HCP. (a) Advanced ACL is specified for ACL type. (b) 348 or more ACEs with inheritance attribute are set to a directory. (c) One of the following operations is performed. (c-1) Data restoring (c-2) Resynchronizing data of a different HNAS F via HCP (c-3) Referring past version directory Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 20

21 In the case of a different file system where the data is imported from another file server, it may occur when the conditions below are all combined. (a) Advanced ACL is specified for ACL type. (b) 348 or more ACEs with inheritance attribute are set to an import source or import target directory. (c) The data is imported. The evasion plan: Reduce the number of ACEs set to the directory to be 347 or less. (29) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: When sysinfoget command is run or HNAS F is highly loaded, the OS may reboot. The condition: It may occur when one of the following conditions is met. (a) sysinfoget command is run and the operating information of system is collected. (b) HNAS F is highly loaded. (The status where the number of ongoing tasks or executable tasks is five times as many as the number of tasks that the CPU can process continues for a minute or longer.) (30) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: A code can be run with root authority. The problem is reported with the following Common Vulnerabilities and Exposures. CVE , CVE , CVE , CVE , CVE , CVE , CVE , CVE The condition: It may occur when those other than authorized users log in. The evasion plan: Make sure to control so that those other than authorized users cannot log in. (31) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: Update installation fails with error message KAQM E and KAQG61018-W, or collecting all-log data information may fail with error message KAQM09039-E. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 21

22 The condition: After importing data from a different file server using NFS protocol, update installation or all-log data information collection may fail. The recovery plan: Take the following operations in the listed order. (a) Perform system LU maintenance. (b) Install OS. (c) Restore the system LU using the data stored in (a). (32) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: At OS update installation using the HFSM system software installation wizard, the update installation of node is complete but the OS cannot start, and the operation is interrupted with KAQM20046-E error. The condition: It may occur when OS update installation is performed using the HFSM system software installation wizard. The recovery plan: Take the recovery operations in the listed order. (a) Power on the node where the error occurs. (b) Perform [Refresh Processing Node] from HFSM. (c) Verify that the version of node where the error occurs is updated. (d) Start the node where the error occurs. (e) Fail back the resource group. (f) If the error occurs on node0 and the node is restored, perform update installation on node1. If the error occurs on node1, take the above steps (a) to (e). (33) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: After [OK] is clicked on the Create File System dialog or Edit File System dialog, an error message may be displayed at an inadequate location near the [OK] button. The condition: It may occur when the following operations are performed in the listed order. (a) The Create File System dialog or Edit File system dialog is opened. (b) An invalid value is entered for Time Until Committed or Default Retention Period. (c) File system setting and/or Auto commit is closed. (d) [OK] is clicked. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 22

23 The recovery plan: Open File system setting and Auto commit, enter a valid value, and then click [OK]. (34) Following defect has been fixed by Hitachi NAS Platform F Affected version: The phenomenon: When free capacity is insufficient in a file system combined with HCP, operations such as migration and stubbing are affected and may fail. The condition: It occurs when the conditions below are all combined. (a) A file system is created in cluster configuration. (b) The file system setting is as follows. (b-1) HCP is combined per share. (b-2) Single instance is enabled. The recovery plan: Perform the following operations in the listed order. (a) Organize unnecessary files, and reserve the reserved space for file system by taking a measure such as data backup to outside. (b) Run arcresvse command to set the reserved space. (35) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: At file system setting change, KAQM37021-E message is wrongly output in HSM Core log. The condition: It may occur when the conditions below are all combined. (a) One of the following file system setting changes is performed. (a-1) Enabling the single instance (a-2) Enabling autocommit for WORM file system (b) The target file system is mounted while it is in readable and writable status. The recovery plan: None as the error message is just output in HSM Core log. (36) Following defect has been fixed by Hitachi NAS Platform F The phenomenon: When WormSetting property is specified for API FileSystem resource and then POST method is run, the invalid setting may not turn to error. The condition: It occurs when one of the following auto commit-related properties is specified for WormSetting property of FileSystem resource and then POST method is run. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 23

24 (a) "false" that is not valid as isautocommitenabled property is specified. (b) A property that is not valid as autocommitperiod property is specified. Known Problems N/A Usage Precautions for "CIFS bypass traverse checking" function The default setting of "CIFS bypass traverse checking" when creating a file system has been changed as Table 6 in or later. Table 6 The default operation of creating a file system No Function before or later 1 CIFS bypass traverse checking function Disable (Not supported) Enable CIFS bypass traverse checking function has been setup as disable if the update installation from a version former than is performed. Please change the setting when you use CIFS bypass traverse checking function Usage Precautions when integrating HCP When a file of 200MB or larger is migrated with the HTTP compression enabled while other than "0" is set to the period for monitoring the transfer speed and the lowest transfer speed to the HCP system, the average speed of transfer may be lower than the limit and the migration may fail with time-out. Set "0" to the period for monitoring the transfer speed and the lowest transfer speed, so that a time-out does not occur until the time set to time-out of communication to HCP has passed even when the transfer speed to HCP is low. When the priority of file stubbing is changed by arcconfedit command, if the priority of stubbing is high, the processing time of data reading/writing from a client and migration/recall may get longer. Do not keep the stubbing priority high but change it in the case that an increase in data writing from clients is expected. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 24

25 When a failure occurs in the network between HNAS F and HCP or in HCP, a wait for a response from HCP continues, which may affect the performance of accesses from file share clients to HNAS F. In order to mitigate the effect on the access performance, set the wait time until reconnecting to HCP by arcconfedit command to be larger than --low-speed-time option. However, if a temporary communication errors frequently occur, such as a case where HNAS F is combined with HCP via network, as the wait status can be solved by the temporary communication error, set 60 or lower value. When an operation with communication to HCP, such as migration and recall, is performed under the condition that the communication error is detected but the wait time has not yet passed, a communication error is returned instead of connecting to HCP. If the wait time has passed, connecting to HCP is tried. Note that access to HCP is disabled until the wait time passes even when the error has been solved. Therefore, set the wait time to "0" and see if accesses to HCP are enabled. If the user can successfully access, restore the setting to the previous. When a file system linked to the HCP is deleted and then a file system with the same name is created, both policies of before deletion and after creation may be displayed on the [Task Management] dialog box. In this case, Present Status of policies after creation and before deletion are [Scheduled] and [Standby] respectively. As the policy of after deletion is not scheduled, it does not affect the behavior. By the default setting, 5% (upper limit 40GB) of total capacity of the file system are secured as the reserved space that a system uses when creating a file system in or later which links to HCP. This reserved space prevents that migration process and stubbing process are affected when the file system lacked the capacity. Because user cannot use reserved space, design total capacity of file system as total of user capacity and reserved space. If the update installation from a version former than is performed, reserved space is set as 0% to existing file systems. If necessary, set reserved space using arcresvset command. When the reserved space is set in or later, update management information process starts at 0:07 a.m. for stubbing process. This updating process takes up to an hour. While this process is running, the load of the system increases. Usage Precautions for CIFS Access Log If the update installation from a version former than is performed, "Rename items" (renaming files or folders) event of CIFS access log is not set in the Setting Events Logged to the CIFS Access Log page in GUI. If necessary, set the CIFS access log setting. Usage Precautions for Negotiation Mode ( or later) With the negotiation mode having been added in , when the update installation from a version former than that is performed, the following negotiation mode name is changed. However, no action is required because the setting is not changed. Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 25

26 Before the change (1) 1000Base Full Duplex After the change (1) 1000Base Full Duplex(Auto Negotiation) In addition, when the update installation from a version former than is performed, the following negotiation mode names are changed. However, no action is required because the settings are not changed. Before the change (1) 100Base Full Duplex (2) 100Base Half Duplex After the change (1) 100Base Full Duplex(Auto Negotiation) (2) 100Base Half Duplex(Auto Negotiation) Usage precaution for Internet Explorer 11.0 as Management console An operation to open different window or tab by a click of anchor or button on the window may cause an unnecessary window (such as blank or in transition window) to be opened concurrently. In this case, close the unnecessary window. If this problem persists, create a new Windows user account and then operate the browser with the new user. Usage precaution for the chunk size of the differential data device ( and later) In order to improve file system access performance and to reduce the amount of differential data when you enable the snapshot capability, default chunk size has been changed in case following two conditions are both satisfied. 1) Max number of reserved generations is no more than 124 2) File system capacity is no more than 32TB <Old value> File system capacity Default chunk size Max reserved Max reserved generations = generations = Max reserved generations = 496 Max reserved generations = 992 No more than 32TB 4MB 8MB 16MB 32MB <New value> File system capacity Default chunk size Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 26

27 Max reserved generations = 124 Max reserved generations = 248 Max reserved generations = 496 Max reserved generations = 992 No more than 32TB 1MB 8MB 16MB 32MB Notices on the change (1) After update installation to this version, new default chunk size is applied when you reset the differential data device or you set the new differential data device. When you want to reset the old chunk size, please specify 4MB chunk size when you reset the existing differential data device. (2) When you set the chunk size to 1MB, you can expand the file system up to 256TB. Note that in case you have a plan to expand the file system up to 1PB, you need to specify more than 4MB chunk size when you set differential data device. (3) Time taken by background process when you create/delete differential snapshot gets longer than the older versions. When background process time gets longer than the minimal interval of the snapshot schedule, please consider either of following options. When you have enough time for the minimal snapshots scheduling, you don't need to care following options. 1. Revisit snapshot scheduling to extend to longer interval 2. Set chunk size to 4MB when you set the differential data device Usage precaution for "subfolder monitoring" function When the setting of subfolder monitoring function (a function to report any change in response to a request for "monitoring all files and folders under the specified folder" from a CIFS client) is changed from "Disable" to "Enable", if many CIFS clients are connected, HNAS F may be highly loaded. In this case, setting the subfolder monitoring function to "disable" can solve the high load status. Caution ACL for the shared directory All of the information regarding ACL for the shared directory are stored in share_info.tdb. Maximum size of share_info.tdb is 64 Mbyte. CIFS service failure may be caused due to the disk space shortage if the size is more than 64 Mbyte. Size of share_info.tdb depends on "the number of CIFS share" and "total of the number of ACE for the shared directory of each share". For this reason, set "the number of CIFS share" and "total of the number of ACE for the shared directory of each share" so that the size of share_info.tdb does not exceed 64 Mbyte. The following is the example of setting. # the number of CIFS share total of the number of ACE for the shared directory of each share Size of share_info.tdb Copyright 2012, 2015, Hitachi, Ltd., Hitachi Data Systems Corporation, ALL RIGHTS RESERVED 27