Hitachi Configuration Manager Release Notes

Transcription

1 Hitachi Configuration Manager Release Notes Contents Contents... 1 About this document... 2 Intended audience... 2 Getting help... 2 About this release... 2 Product package contents... 2 New features and important enhancements... 2 System requirements... 3 Known problems... 3 Resolved problems Installation precautions Usage precautions Documentation Documentation errata Copyrights and licenses Hitachi, Ltd. All rights reserved. 1

2 About this document This document (RN-92HC239, December 2016) provides late-breaking information about Hitachi Configuration Manager v 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: 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 resolves multiple known problems and adds new features. Product package contents Item Contents Revision Release type Software Hitachi Configuration Manager Full Package Documents Hitachi Command Suite Configuration Manager REST API Reference Guide MK-92HC New features and important enhancements For Features and enhancements Affected operating systems 2017 Hitachi, Ltd. All rights reserved. 2

3 Features and enhancements For VSP G1000, G1500, VSP F1500, VSP Gx00, and VSP Fx00, the Configuration Manager REST API now supports the following features: Affected operating systems -Forced deletion for dedupe and compression volumes -Native flash capacity display -Thin Image pairs tree deletion For VSP G1000, G1500, VSP F1500, VSP Gx00, and VSP Fx00, the Configuration Manager REST API now supports the following features: -SNMP settings -Cascade for Thin Image copy pairs For VSP G1000, G1500, VSP F1500, VSP Gx00, VSP Fx00, VSP, and HUS VM, the Configuration Manager REST API now supports the following features: -License display -License settings (VSP Gx00, VSP Fx00 only) For VSP G1000, G1500, VSP F1500, VSP Gx00, VSP Fx00, VSP, and HUS VM, the Configuration Manager REST API raises the upper limit for the number of LDEVs that can be retrieved, from 1000 to The Configuration Manager REST API now supports Windows Server The Configuration Manager REST API now supports Red Hat Enterprise Linux 7.3. The Configuration Manager REST API now supports SUSE Linux Enterprise Server 12 SP2. The Configuration Manager REST API now supports Oracle Linux 7.3. The Configuration Manager REST API now supports VMware ESXi 6.5. Note: See Hitachi Command Suite System Requirements for details. *: Applies to all supported operating systems in Configuration Manager. System requirements System requirements can be found in Hitachi Command Suite System Requirements (MK-92HC209-23).The requirements are presented in the form of requirements for each type of server, rather than as requirements for individual Hitachi Command Suite components. Known problems Storage systems supported by Hitachi Command Suite In Hitachi Command Suite , storage systems with the following firmware versions are supported. VSP Gx00 models, VSP Fx00 models ( XX/XX or earlier) VSP G1000, VSP G1500, VSP F1500 ( XX/XX or earlier) 2017 Hitachi, Ltd. All rights reserved. 3

4 Note: This condition does not apply to other storage system models About status codes returned during a request to upload a file During a request to upload a file, you may receive HTTP status code 502 (Proxy Error). In this case, verify that the specified file matches the file described in the "Configuration Manager REST API Reference Guide", and try again. The latest information about storage system resources is not updated in the Configuration Manager REST API when certain modifications are made to the storage system When the following modifications are made to storage system configurations, the latest information about the corresponding storage system resources is not updated in the REST API server database. - Deleting a pool Information about the volume may not be updated. - Shrinking a pool Information about the volume is not updated. - Deleting a parity group Information about the volume is not updated. - Modifying an iscsi name Information about the iscsi name is not updated. - Modifying a nickname of an iscsi Information about the nickname of the iscsi is not updated. If you execute one of these operations, refresh the storage system configuration information by using the Configuration Manager REST API. Error KART00003-E is displayed when the Configuration Manager REST API functions are executed for VSP Gx00 or VSP Fx00 storage systems that are SSL enabled. When you execute an API function to obtain information or change existing information of VSP Gx00 or Fx00 storage system that is enabled for secure communication (SSL), the KART00003-E error ("An internal error is occurred in REST API server") is displayed, which in turn results in abnormal termination of API. When this error occurs, a problem might exist with the SSL communication settings between the REST API server and the storage system. Refer to the REST API Reference Guide for how to check the SSL communication settings between the REST API server and the storage system, and then reconfigure the settings if needed. Problems related to the synchronization of the date and time between the NTP server and the storage system in Configuration Manager REST API A difference of several hours between the storage system's date and time and the NTP server's date and time occurs if all of the following conditions are met: 1. A time zone for which daylight saving time is supported is set. 2. Automatic adjustment of daylight saving time is enabled Hitachi, Ltd. All rights reserved. 4

5 3. You synchronize the storage system with the NTP server during the transition period from standard time to daylight saving time or the transition period from daylight saving time to standard time. To recover from this problem, synchronize with the NTP server again after the transition period from standard time to daylight saving time or the transition period from daylight saving time to standard time. Problems related to automatic adjustments for daylight saving time in the date and time of the storage system in Configuration Manager REST API The symptoms of this problem occur if all of the following conditions are met: 1. A time zone for which daylight saving time is supported is set. 2. Automatic adjustment of daylight saving time is enabled. Symptom 1: 1. An NTP server synchronization time that was set during standard time incorrectly changes to one hour earlier than the actual time when daylight saving time begins. 2. An NTP server synchronization time that was set during daylight saving time incorrectly changes to one hour later than the actual time when daylight saving time ends. To resolve this problem, reset the NTP server synchronization time by reexecuting the API function to change the date and time of the storage system after daylight saving time begins or ends. Symptom 2: 1. When the date and time of the REST server is in daylight saving time and the date and time of the storage system is in standard time, a time one hour earlier than the time you request as the time of synchronization with the NTP server is set as the synchronization time for the storage system. 2. When the date and time of the REST server is in standard time and the date and time of the storage system is in daylight saving time, a time one hour later than the time you request as the time of synchronization with the NTP server is set as the synchronization time for the storage system. To resolve this problem, set the same date and time for the REST server and the NTP server, and then re-set the NTP server synchronization time by re-executing the API function to change the date and time of the storage system. Registering the same storage system into multiple Configuration Manager REST API servers The KART30003 error occurs and storage system configuration information is not updated when the same user account is used to register a specific storage system into multiple REST API servers. To register the same storage system into multiple REST API servers, use different user accounts Hitachi, Ltd. All rights reserved. 5

6 Display of attributes related to the compression and deduplication functions when the Configuration Manager REST API is used to get pool information The attributes listed below should be displayed only when the Configuration Manager REST API is used to get HDP pool information. However, they are also displayed when the Configuration Manager REST API is used to get information about pools other than HDP pools. If you use the Configuration Manager REST API to get information about pools other than HDP pools, ignore the following attributes for non-hdp pools. duplicationnumber datareductionacceleratecompcapacity datareductioncapacity datareductionbeforecapacity datareductionacceleratecomprate duplicationrate compressionrate datareductionrate Display of the pair concordance rate and the processing progress rate in the Thin Image pair information If all of the following conditions are met, the progressrate attribute, which indicates the progress of processing, is displayed: - The isclone attribute of the pair is set to "false". - The cancascade attribute of the pair is set to "false". - The pair status is COPY, RCPY, SMPP, or PSUP. In the above case, the value displayed for the progressrate attribute is actually the value of the concordancerate attribute. Using the Configuration Manager REST API to get configuration information when a syslog server has been set for VSP Gx00 If a syslog server has been set as the server to which the monitoring logs of a VSP Gx00 storage system are to be sent, if you change the configuration of the storage system, the information in the database of the REST API server might not be updated. (If you search for information about that storage system, you might get configuration information that is out of date.) If this problem occurs, re-set the syslog server to which the monitoring logs of the VSP Gx00 storage system are to be sent. The user account which has been used for VSP G1000, G1500 or VSP F1500 storage systems registration by the Configuration Manager REST API server Do not use the user account which has been used for VSP G1000, G1500 or VSP F1500 storage systems registration by the REST API server, to create the REST API session or to operate the storage system by Hitachi Device Manager - Storage Navigator. If the user account is used, refreshing the storage system configuration information may fail Hitachi, Ltd. All rights reserved. 6

7 Installing the Configuration Manager REST API in the environment where Command Control Interface (CCI) is installed In the environment where CCI is already installed, install the Configuration Manager REST API in the drive with the same letter as assigned to the drive for CCI. If it cannot be installed in a drive with the same letter as assigned to the drive for CCI, install it in a different drive with a letter later in alphabetical order. When the Configuration Manager REST API is installed in a drive with a letter earlier than assigned to the drive for CCI, the absolute path to the CCI executable file will have to be specified by the user when executing CCI commands. When the model of the storage system is upgraded after registering a storage system into the Configuration Manager REST API When the model of the storage system is upgraded after registering a storage system into the Configuration Manager REST API, old model name might be displayed in the model attribute when the Configuration Manager REST API is used to get information about the storage system. To display the model name correctly in the Configuration Manager REST API, delete information about the storage system and then register again. When SSL communication is enabled between Configuration Manager REST API server and the storage system For a VSP G1000, VSP G1500 and VSP F1500 storage system for which SSL communication is enabled and for which the microcode version is earlier than X-XX/XX, the KART40098-E error might occur during an attempt to perform any of the following operations related to volumes and pools, and the operation might fail. - Creating a volume - Deleting a volume - Formatting a volume - Creating a pool - Deleting a pool - Expanding a pool - Shrinking a pool However, even under the circumstance described above, these operations might succeed. To check whether an operation succeeded, obtain the information for the target resource. Error message ID "KART E" displayed in Configuration Manager REST API To resolve this error, verify the following and then retry the API operation: - The status of REST API server which that is running on the remote storage system. - The network configuration of storage system registered by the remote REST API server. - The network status between storage systems registered by the local and remote REST API servers. - The status of both storage systems registered by the local and remote REST API servers Hitachi, Ltd. All rights reserved. 7

8 Registration of VSP G1000, G1500 or VSP F1500 storage system by multiple Configuration Manager REST API servers disabled when SSL communication is enabled between REST API server and storage system A VSP G1000, VSP G1500, or VSP F1500 storage system for which the microcode version is earlier than X-XX/XX and for which SSL communication between the REST API server and the storage system is enabled cannot be registered to multiple REST API servers at the same time. When changing SSL communication settings between Configuration Manager REST API server and VSP G1000, G1500 or VSP F1500 If you change the SSL communication settings between REST API server and VSP G1000, G1500 or VSP F1500 storage system, the REST API server must be restarted. If the information of a remote storage system is registered in the REST API server, delete this information and register it again. Resource group lock not supported when SSL communication is enabled between VSP G1000, G1500 or VSP F1500 and Configuration Manager REST API server Inability to lock a resource group containing a VSP G1000, G1500, or VSP F1500 storage system for which the microcode version is earlier than X-XX/XX and for which SSL communication is enabled between the storage system and the REST API server: [Cause]:A resource group of the storage system is locked by other users, or by another storage management software. Error message with error code SSB1=2E11, SSB2=2205 is displayed. [Solution]:Retry the operation later. [Cause]:Configuration change is requested to the storage system at the same time from other users, or other storage management software. [Solution]:Confirm the current configuration and retry the operation. Error messages displayed when storage systems are modified by using the particular Configuration Manager REST API If an error occurs in the processing to modify a VSP G1000, G1500, or VSP F1500 storage system for which SSL communication is enabled and for which the microcode version is earlier than X-XX/XX, "null" appears in the error message. This problem occurs when one of the following operations fails: - Creating a host group with the host mode specified - Creating a host group with the host mode option specified - Creating a pool for Hitachi Dynamic Tiering - Modifying pool information - Modifying volume information Error messages displayed when storage systems are modified by using the Configuration Manager REST API If an error occurs in the processing to modify a VSP G1000, G1500, or VSP F1500 storage system for which SSL communication is enabled and for which the 2017 Hitachi, Ltd. All rights reserved. 8

9 microcode version is earlier than X-XX/XX, the error information is displayed as shown in the following example. The "message", "cause", and "solution" attributes are displayed as part of the message content, instead of as JSON attributes. Example error information: "error" : { "errorsource" : "<URL-of-the-API-command-for-which-the-error-occurred>", "message" : "An error occurred by the storage system. ( details: message ID = <message-id>, message = <error-message>, cause = <cause-of-the-error>, solution = <solution-for-the-error>, storage device ID = <storage-device-id>)", } "solution" : <solution-for-the-error>, "messageid" : <message-id> Details about information related to MUs (mirror units) when information about a specific journal is collected by using the Configuration Manager REST API of Hitachi Command Suite When one journal ID is specified to collect information about a journal used in a 3DC configuration, if multiple MUs are specified for the journal, information about only one MU is displayed. To see information about all of the MUs, set basic, timer, or detail for the query parameter for collecting journal information (journalinfo). After the list containing journal information appears, check the list for the information about the corresponding journal ID. Using the Configuration Manager REST API to get job information and session information For VSP G1000, G1500, VSP Gx00, VSP F1500 and VSP Fx00 storage systems, a failure results when getting job information or session information by using the Configuration Manager REST API if all of the following conditions are met: 1. A storage system is registered with the REST API server. 2. Changed the user password or deleted the user account on the storage system described in (1) by using different management tool, such as Storage Navigator. 3. The REST API server was restarted after (2). The following symptoms occur. Symptom 1: The API function to get job information for the storage system described in condition (1) fails with the applicable error described below Hitachi, Ltd. All rights reserved. 9

10 Symptom 2: The API function to get a list of sessions for the storage system described in condition (1) fails with the applicable error described below. Errors: - VSP G1000, G1500 or VSP F1500 KART30085-E User authentication failed. - VSP Gx00 models or VSP Fx00 models KART30002-E All or part of the processing cannot be performed by the storage system. To recover from this problem, use the Configuration Manager REST API to reconfigure correct user information as described in procedure (2) for the storage system described in procedure (1). About the KART00000-E error when getting storage system information or changing the storage system configuration using the Configuration Manager REST API When getting storage system information or changing the storage system configuration by using the Configuration Manager REST API, the operation might fail with the KART00000-E error. In most cases, a communication problem that exists between the REST API server and the storage system might be the cause of the error. Check the communication path between the REST API server and the storage system, including ports and encryption related settings, and then reconfigure the settings if needed. Authorization information for the Configuration Manager REST API To specify authorization information for a VSP G1000, G1500, or VSP F1500 storage system for which SSL communication is enabled and for which the microcode version is earlier than X-XX/XX, specify the information in the Remote-Authorization header by using the following format: Basic authentication-information If you specify the token of the session as the authorization information, the authentication attempt fails. Known problems when an IPv6 address is specified in the request body for a storage system that is registered on a server in a Windows Server 2008 R2 environment, and for which the IP addresses for different segments are applied to multiple NICs The following are the known problems: 2017 Hitachi, Ltd. All rights reserved. 10

11 - When you attempt to perform operations for a remote copy, an error occurs in which "EX_ENORMT" appears in "errorcode". - When you register a storage system for which the value for the "isnotifiable" parameter is "true", the KART40166-E error occurs. - When you register a storage system without specifying a value for the "isnotifiable" parameter, the REST API server cannot be automatically registered in the destinations for sending notifications about changes to storage system configurations. When any of the above problems occur, perform the following procedure: 1. Delete the storage system's information. 2. For the "restipforsvpconnection" attribute, specify an address that can be used to communicate with the SVP IP address specified for the "svpip" attribute, and then register the storage system again. Executing an asynchronous processing API function to the REST API server When a user executes an asynchronous processing API function job that takes two hours or more to process, the KART30031-E error occurs and the job fails. This problem occurs if the user executes an API function command to perform one of the following tasks and the job takes two hours or more to complete. - Deleting a journal - Formatting a volume - Shredding a volume - Formatting a parity group - Deleting a parity group - Initializing the capacity-saving function for a pool - Shrinking a pool - Restoring a pool - Relocating a pool Even though the KART30031-E error occurs, the request might have succeeded. Confirm the status of the resources. Registering destinations for sending notifications about changes to storage system configurations on the REST API server If you use the following procedure to register destinations for sending notifications, any attempt to delete information about the storage system fails, and the "KART40170-E" error message is output Hitachi, Ltd. All rights reserved. 11

12 1. You register a storage system, and disable notifications. 2. You execute an API command to register destinations for sending notifications about storage system configurations. To remove the storage system information, perform the following procedure. 1. Delete any destinations for sending notifications about changes to storage system configurations. 2. Remove the storage system. Performing operations for ShadowImage pairs in the same copy group by executing management API functions in parallel When you execute ShadowImage operations in parallel, the results of some of the operations are not reflected in the server. This problem occurs if you attempt to create, delete or change resources while any of the following operations are being executed for resources associated with the same copy group: - Obtaining information about all ShadowImage pairs in the specified copy group - Obtaining information about a single ShadowImage pair - Creating a ShadowImage pair - Splitting all ShadowImage pairs in the copy group - Splitting a single ShadowImage pair - Resynchronizing all ShadowImage pairs in the copy group - Resynchronizing a single ShadowImage pair - Restoring all ShadowImage pairs in the copy group - Restoring a single ShadowImage pair - Deleting a copy group - Deleting a ShadowImage pair When this problem occurs, only the result of the first job that was executed is applied to the server. The results of any other jobs are not applied. Because of this, the server returns incorrect information. The following is an example of a situation in which this problem occurs. Example: 1. The user creates a ShadowImage pair Hitachi, Ltd. All rights reserved. 12

13 2. The user creates another ShadowImage pair in the same copy group while the previous job is still being executed. 3. When the user attempts to obtain information about the ShadowImage pairs in the copy group, an error occurs in which "EX_ENORMT" appears in "errorcode". When you perform operations for ShadowImage pairs in the same copy group, confirm that the current job has ended before executing the next job. Do not execute these jobs in parallel. If this problem occurs, perform the following procedure: - Restart the REST API server. - Add a new ShadowImage pair to the copy group. Known problems when an IPv6 address is specified for the "svpip" attribute for a VSP G1000, VSP G1500, or VSP F1500 storage system that is registered on the REST API server If an IPv6 address is specified for the "svpip" attribute when a VSP G1000, VSP G1500, or VSP F1500 storage system is registered on the REST API server, any API functions that a user attempts to execute for the registered storage system fails, and the KART00003-E error occurs. To resolve this problem, when you register a VSP G1000, VSP G1500, or VSP F1500 storage system on the REST API server, specify an IPv4 address for the "svpip" attribute in the storage system registration. Configuration Manager displays an invalid string in the error messages Error messages may be displayed incorrectly similar to that shown in the following example, when you execute REST API with Accept-Language header. Example: { "errorsource" : "/ConfigurationManager/v1/objects/storages/ /sessions", } "message" : "a? a??a?ea?e?a?a?a?a??a?a??a??", "cause" : "Authorizationa??a??a??a??a-a?a??a?aR?a?a??a? a??a??a??a?a??", "solution" : "Authorizationa??a??a??a?RaaR1a?coea?a?a? a??a??a?a??a??", "messageid" : "KART40002-E" 2017 Hitachi, Ltd. All rights reserved. 13

14 To display error messages correctly, please input the following header when you execute REST API. "Accept-Language:en" Invalid host group name displayed when you get volume information, or get information about a specific volume When API is used to get volume information, or get information about a specific volume, host group name can display up to 16 characters. To get host group name correctly, use the API of getting host group information, or getting information about a specific host group. Known problems that occur if you change the host name (the computer name in windows) of the REST API server that Configuration Manager including virtual appliance is installed If you change the host name of the REST API server that Configuration Manager is installed, the following problems occur. - When you register a storage system for which the value for the "isnotifiable" parameter is "true", the KART40166-E error occurs. - When you register a storage system without specifying a value for the "isnotifiable" parameter, the REST API server cannot be automatically registered in the destinations for sending notifications about changes to storage system configurations. - When there are the storage systems that are already registered, the resource information of the storage systems used for the search function might not be kept up to date, because the REST API database used for the search function cannot be automatically updated. When any of the above problems occurs, perform the following procedure. In Windows: 1. Open the <Configuration-Manager-installationdestination>\oss\rabbitmq\etc\rabbitmq\rabbitmq-env-conf.bat file and delete the following line. set RABBITMQ_NODENAME=rabbit 2. Run <Configuration-Manager-installation-destination>\sbin\install.bat. 3. Run <Configuration-Manager-installation-destination>\start.bat Hitachi, Ltd. All rights reserved. 14

15 In Linux: 1. Run <Configuration-Manager-installation-destination>/sbin/install.bat. 2. Run <Configuration-Manager-installation-destination>/start.bat. In Windows and Linux: When there are the storage systems that are already registered, register destinations for sending notifications about changes to storage system configurations again. See the REST API Reference Guide, delete destinations for sending notifications about changes to storage system configurations and register the destinations. Fail to register a storage system Even though the microcode version of the storage system is correct, registering a storage system might fail with "KART40128-E" or "KART40167-E" message. Confirm IP address of SVP that manages the storage system, and then try again. Resolved problems From to Problem description For ceratin requests for remote copy pair operations, REST API server may not send a response. On a REST API server that is installed on a server for which the IP addresses for different segments are applied to multiple NICs, an attempt to perform remote copy operations or to send notifications about changes to storage system configurations might fail. An attempt to obtain volume information results in an incorrect value returned for the attribute "quorumstoragetypeid". When a user executes an asynchronous processing API, the result of the job is not displayed correctly. If you change the configuration of a port or change the configuration of the resources that belong to a port for which "x" in the port name "CLx-y" is a value other than a numeric value, the processing to refresh the configuration information of the storage system fails. When REST API server receives change notification of external parity groups, REST API server fails to update configuration information. Affected products Configuration Manager Configuration Manager Configuration Manager Configuration Manager Configuration Manager Configuration Manager Affected operating systems Visual C Redistributable Packages 32-bit version Configuration Windows 2017 Hitachi, Ltd. All rights reserved. 15

16 Problem description will be removed unexpectedly during the installation of HCS products to earlier than This symptom is due to the Microsoft KB Affected products Manager Affected operating systems *: Applies to all supported operating systems in Device Manager. Installation precautions None Usage precautions The latest storage system configuration information are not obtained immediately after starting Configuration Manager REST API services After startup it takes a while for the REST API server to refresh automatically with the latest storage system configuration information. For an immediate refresh of the system configuration information, see the procedure in the Configuration Manager REST API Reference Guide. Conditions when the concordance rate for Thin Image pairs is displayed. Relevant locations in the Hitachi Command Suite Configuration Manager REST API Reference Guide: - Getting information about Thin Image pairs in units of snapshot groups - Getting information about Thin Image pairs in a specified snapshot group - Getting information about a Thin Image pair - Getting information about a specific Thin Image pair The concordancerate attribute is displayed if both of the following conditions are met: - The value for the isclone attribute is false. - The value for the cancascade attribute is false. The concordancerate attribute is also displayed if both of the following conditions are met: - The value for either the isclone attribute or the cancascade attribute, or for both, is true. - The pair status is something other than COPY, RCPY, SMPP, or PSUP. Configuration Manager REST API commands that can be run only by root users and the reason for such restrictions in Linux For the reasons described below, only the root user can run the following REST API commands: 2017 Hitachi, Ltd. All rights reserved. 16

17 1. The following commands require files to be created or deleted in certain OS directories (such as the "/etc" directory) for which only root users have the necessary write permissions: <mount directory of the installation media>/confmanager/install.sh <REST API installation directory>/confmanager/inst/uninstall.sh 2. The following commands run shell scripts that can only be run by root users in the REST API installation directory: <REST API installation directory>/confmanager/supporttools/collecttool/restti.sh <REST API installation directory>/confmanager/bin/changejdk.sh <REST API installation directory>/confmanager/bin/changermport.sh <REST API installation directory>/confmanager/bin/configurecluster.sh <REST API installation directory>/confmanager/bin/setcertificatefile.sh <REST API installation directory>/confmanager/bin/setchangenotificationport.sh <REST API installation directory>/confmanager/bin/setchangenotificationsecret.sh <REST API installation directory>/confmanager/bin/setciphersuite.sh <REST API installation directory>/confmanager/bin/deltask.sh <REST API installation directory>/confmanager/start.sh <REST API installation directory>/confmanager/status.sh <REST API installation directory>/confmanager/stop.sh Command descriptions: RestTI.sh - Collects REST API logs changejdk.sh - Switches to a customer-provided JDK changermport.sh - Changes the range of port numbers to be used by CCI configurecluster.sh - Configures the REST API service to recognize that it is in a cluster with HCS setcertificatefile.sh - Specifies a certificate file for SSL communication setchangenotificationport.sh - Changes the range of port numbers to be used by the REST API when sending notifications about changes made to storage system configurations setchangenotificationsecret.sh - Registers the character string to be used in notifications about changes made to storage system configurations setciphersuite.sh - Specifies a cipher suite for SSL communication deltask.sh - Deletes the REST API service information from the operating system start.sh - Starts the REST API service status.sh - Gets the status of the REST API service 2017 Hitachi, Ltd. All rights reserved. 17

18 stop.sh - Stops the REST API service When using Hitachi Command Suite Configuration Manager REST API to specify a replication type to change the configuration of a remote copy pair When using Hitachi Command Suite Configuration Manager REST API to change the configuration of a remote copy pair, even if specifying replication types that are different from that of the remote copy pair, the change will be applied if specified parameters are valid. Changing configuration of remote copy pairs After creating, splitting, resyncing, or deleting a remote copy pair, if the job progress takes more than five minutes to complete, the job might appear as Failed regardless of the actual status. Additionally, the following message appears: KART40097-E An error occurred on the REST API server managing the remote storage system. (details: message ID = KART40047-E, message = The specified token is invalid., cause = An invalid token was specified, or the session might be disabled., solution = Revise the token info. If the problem persists, recreate the session.) See the details of the message, and remove the cause of the error on the REST API server managing the remote storage system. In this case, check the applicable resources for the actual status. When upgrading the microcode of a storage system managed by Configuration Manager from specific microcode versions If all of the following conditions are met, restart the Configuration Manager service after upgrading the microcode of the storage system. -The storage system is one of the following models: VSP G1000, VSP G1500, or VSP F SSL communication is enabled. -You plan to upgrade the existing microcode version to X-XX/XX or a later version. Storage system that has SSL communication enabled and the microcode version REST API requests for a VSP G1000, VSP G1500, or VSP F1500 storage system that has SSL communication enabled and the microcode version is earlier than X-XX/XX fails with the 503 status code (Service unavailable) due to multiple too many instances of Configuration Manager managing the same storage system. Review the configuration, and delete information about the storage system from duplicate or unwanted instances of Configuration Manager Hitachi, Ltd. All rights reserved. 18

19 Installation of Configuration Manager on Windows Server 2008 R2 SP1 If the root certification of the Windows Server 2008 R2 SP1 is old, the installation of the Configuration Manager might fail. Update the root certification and install the Configuration Manager again. Documentation Available documents Document name Document number Issue date Hitachi Configuration Manager REST API Reference Guide MK-92HC Feb, 2017 Documentation errata For Manual Name: Hitachi Configuration Manager REST API Reference Guide # Section Existing Content Changes 1. Getting volume information p Setting the system date and time of a storage system P Getting SNMP settings P Specifying the SNMP error notification destination s P None PUT /base- URL/v1/objects/storages/storagedevice-ID/date-times/instance sendingtrapsetting snmpv1v2csetting snmpv3setting requestauthenticationsetting snmpv1v2csetting snmpv3setting sendingtrapsetting snmpv1v2csetting snmpv3setting user name requestauthenticationsetting snmpv1v2csetting snmpv3setting Attribute: drivetype Type: string Description: Code indicating the drive type of the drive belonging to the LDEV PUT base- URL/v1/objects/storages/storagedevice-ID/date-times/instance sendingtrapsetting snmpv1v2csettings snmpv3settings requestauthenticationsetting snmpv1v2csettings snmpv3settings sendingtrapsetting snmpv1v2csettings snmpv3settings username requestauthenticationsetting snmpv1v2csettings snmpv3settings 2017 Hitachi, Ltd. All rights reserved. 19

20 Copyrights and licenses 2017 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 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, DS6000, DS8000, Enterprise Storage Server, ESCON, FICON, FlashCopy, IBM, Lotus, MVS, OS/390, RS/6000, S/390, System z9, System z10, Tivoli, VM/ESA, z/os, z9, z10, zseries, z/vm, and 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, Ltd. All rights reserved. 20