Hitachi Tuning Manager Release Notes

Transcription

1 Hitachi Release Notes Contents Contents... 1 About this document... 1 Intended audience... 1 Getting help... 2 About this release... 2 Product package contents... 2 New features and important enhancements... 3 System requirements... 5 Resolved problems... 5 Known problems... 9 Installation precautions Upgrade precautions Removal precautions Usage precautions Documentation Copyrights and licenses About this document This document (RN-00HS262-77, November 2016) provides late-breaking information about the Hitachi 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 the Hitachi Hitachi, Ltd. All rights reserved. 1

2 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 is a major release that adds new features and resolves multiple known problems. Product package contents Medium Components Revision Release Type Software Hitachi Full Package Prerequisite version of Service Pack - Hitachi - Agent for Server System Hitachi - Agent for Oracle Hitachi - Agent for RAID Hitachi - Agent for Network Attached Storage Hitachi - Agent for SAN Switch Hitachi - Agent for Microsoft(R) SQL Server Hitachi - Agent for IBM DB Full Package Full Package Full Package Full Package Full Package Full Package Full Package Documents Hitachi Command Suite Tuning Manager Installation Guide Hitachi Command Suite Tuning Manager Server Administration Guide Hitachi Command Suite Tuning Manager Agent Administration Guide Hitachi Command Suite Tuning MK-96HC MK-92HC MK-92HC MK-95HC Hitachi, Ltd. All rights reserved. 2

3 Manager Application Reports Reference Hitachi Command Suite Tuning Manager User Guide Hitachi Command Suite Tuning Manager Hardware Reports Reference Hitachi Command Suite Tuning Manager Operating System Reports Reference Hitachi Command Suite Tuning Manager Messages Hitachi Command Suite Tuning Manager CLI Reference Guide Hitachi Command Suite Tuning Manager Getting Started Guide Hitachi Command Suite Tuning Manager API Reference Guide MK-92HC MK-95HC MK-95HC MK-95HC MK-96HC MK-96HC MK-92HC New features and important enhancements For # New Features and Enhancements Applied products Applied 1 The following Operating System is now supported: - Red Hat Enterprise The following Operating System is now supported: - Red Hat Enterprise The following Operating System is now supported: - Oracle The following Operating System is now supported: - SUSE Enterprise Server 12 SP1 5 The following Operating System is now supported: - Operation in a VMware Fault Tolerance environment is now supported. Agent for RAID Agent for SAN Switch Agent for NAS Agent for SAN Switch Agent for RAID Agent for NAS Agent for Server System Agent for SAN Switch Agent for NAS Agent for Oracle agents Windows 2016 Hitachi, Ltd. All rights reserved. 3

4 6 The following NAS systems are now supported as monitoring targets: - Hitachi File Services Manager v5.4.0, 6.1.0, The following storage systems are now supported as monitoring targets: - VSP G200 (Firmware version: X) - VSP G400 (Firmware version: X) - VSP G600 (Firmware version: X) - VSP G800 (Firmware version: X) - VSP G1000 (Firmware version: X) - VSP G1500 (Firmware version: X)(*) - VSP F400 (Firmware version: X) - VSP F600 (Firmware version: X) - VSP F800 (Firmware version: X) - VSP F1500 (Firmware version: X)(*) (*) VSP G1500 or VSP F1500 is now displayed as the model name of the storage unit. 8 Viewing of the window is now supported in an environment installed Adobe Flash Player 23. Agent for NAS Agent for RAID Agent for Server System Windows All 1 All 1 9 The following NAS Platforms are now supported as monitoring targets: - HNAS4100 (Firmware version: 12.7, 13.0) - HNAS4080 (Firmware version: 12.7, 13.0) - HNAS4060 (Firmware version: 12.7, 13.0) - HNAS4040 (Firmware version: 12.7, 13.0) - HNAS3090 (Firmware version: 12.7, 13.0) - HNAS3080 (Firmware version: 12.7, 13.0) 10 The Unified NAS modules of the following storage systems are now supported as monitoring targets: - VSP G400 (Firmware version: X) - VSP G600 (Firmware version: X) - VSP G800 (Firmware version: X) - VSP F400 (Firmware version: X) - VSP F600 (Firmware version: X) - VSP F800 (Firmware version: X) 11 In the following records, you can now obtain settings and amount of the data reduced when the dedupe and compression is used. - Pool Configuration (PD_PLC) Settings of the dedupe and compression for pools Amount of the data reduced when the dedupe and compression is used for pools Agent for NAS All 1 Agent for NAS All 1 Agent for RAID All 1 - Virtual Volume Configuration(PD_VVC) Settings of the dedupe and compression for a volume 12 For VSP Gx00 models and VSP Fx00 models, Tuning Agent for RAID All Hitachi, Ltd. All rights reserved. 4

5 Manager now supports environments in which a single SVP manages multiple DKCs. 13 The following Brocade switch is now supported as a monitoring target: - Network Advisor 14.0.x 14 For instance setup performed by using the jpcinssetup command, the default value of the following items was changed from N to Y: - Unassigned Open Volume Monitoring (Y/N) - Mainframe Volume Monitoring (Y/N) Agent for Switch All 1 Agent for RAID All 1 Note1: Applies to all supported operating systems System requirements The system requirements for can be found in Hitachi Command Suite System Requirements (MK-92HC209). Resolved problems For # Resolved problems Applied products Applied 1 Overwrite installations or upgrade installations might fail in Agent for RAID or Agent for NAS. This problem might occur if overwrite installations or upgrade installations are performed when all of the following conditions are met: (1) Hybrid Store is used. (2) There are many monitoring storage resources on the same host. (3) The value set for Collection Interval is too small. 2 If an attempt to start - Agent REST Web Service failed, information indicating the failure is not output to the log. Agent for RAID Agent for NAS Agent for RAID Agent for NAS Windows( x64), (x6 4), AIX, HP- UX This problem occurs if execution of the htmsrv command fails. 3 When the stops, the stop script of the REST service is not executed. Agent for RAID Agent for NAS, AIX The following problem occurs. In RHEL 6.x: The stop script is not executed, because the processing to deploy the service name file is not 2016 Hitachi, Ltd. All rights reserved. 5

6 implemented in /var/lock/subsys/. In AIX: The stop script is not executed, because the processing to execute the stop script is not included in /etc/rc.shutdown. 4 The htmsrv command might not be able to start Agent REST Application Service normally. This problem occurs if all of the following conditions are met: (1) Either of the following is installed: - Agent for RAID or later - Agent for NAS or later (2) Agent REST Service (Tuning Agent) is stopped. (3) The htmsrv start -webservice command is executed. 5 When polling starts in an environment in which the time zone is set to GMT+xx:yy or GMT-xx:yy (where YY is not zero), no processor is displayed in the Tuning Manager Main Console. Agent for RAID Agent for NAS Agent for RAID Windows,, AIX, HP- UX Windows( x64), (x6 4) This problem occurs if all of the following conditions are met: (1) Hybrid Store is used. (2) The time zone is set to GMT+xx:yy or GMTxx:yy (where YY is not zero) in one of the following environments: In Windows: - Caracas (GMT-04:30) - Newfoundland (GMT-03:30) - Tehran (GMT+03:30) - Kabul (GMT+04:30) - Sri Jayawardenepura (GMT+05:30) - Chennai, Kolkata, Mumbai, New Delhi (GMT+05:30) - Kathmandu (GMT+05:45) - Yangon (Rangoon) (GMT+06:30) - Pyongyang (GMT+08:30) - Adelaide (GMT+09:30) - Darwin (GMT+09:30) In : - Pacific/Marquesas (GMT-0930) - America/Caracas (GMT-0430) - America/St_Johns (GMT-0230) - Asia/Kabul (GMT+0430) - Asia/Tehran (GMT+0430) - Asia/Colombo (GMT+0530) 2016 Hitachi, Ltd. All rights reserved. 6

7 - Asia/Kolkata (GMT+0530) - Asia/Kathmandu (GMT+0545) - Asia/Rangoon (GMT+0630) - Indian/Cocos (GMT+0630) - Australia/Eucla (GMT+0845) - Australia/Adelaide (GMT+0930) - Australia/Broken_Hill (GMT+0930) - Australia/Darwin (GMT+0930) - Australia/Lord_Howe (GMT+1030)(*) - Pacific/Norfolk (GMT+1130) - Pacific/Chatham (GMT+1245) (*) Except during daylight saving time. (3) Polling is performed at the appropriate time, as shown below. If the time zone is set to GMT+XX:YY: Polling is performed from XX:00 to XX:YY local time. Example: The time zone is set to GTM+XX and the polling time period is for an hour beginning at 0:00. 0:00 to (0: minutes) = From 0:00 to 0:45 If the time zone is set to GMT-XX:YY: Polling is performed during the period from XX:00 to (XX + 1:00 - YY minutes). Example: The time zone is set to GMT-3:15, and the polling time period is for an hour beginning at 0:00. 0:00 to (1:00-15 minutes) = From 0:00 to 0:45 6 Symptom 1 or 2 shown below occurs when storage system information is displayed in the Main Console. Symptom 1: Processor information cannot be displayed. - In the summary area, "0" is displayed for the number of processors. - The processor list in the information area displays "No object". - Processors cannot be displayed in a tree in the navigation area. Windows( x64), (x6 4) Symptom 2: The association between LDEVs and processors cannot be displayed. - The LDEV list displays "no data" for related processors. - The list of LDEVs related to processors displays "No object" Hitachi, Ltd. All rights reserved. 7

8 Condition of occurrence for symptom 1: Problem A occurs if the PI_PRCS record (in hours) cannot be acquired from Agent for RAID during polling on the. Conditions of occurrence for symptom 2 Problem B occurs if all of the following conditions are met: (1) The type of the device being monitored by Agent for RAID is VSP, VSP G1000, HUS VM, a VSP Gx00 model, or a VSP Fx00 model. (2) During polling on the, the PI_PRCS record (in hours) cannot be acquired from the instance of Agent for RAID that is monitoring the device in (1). (3) During polling on the performed after (2), the PI_PRCS record (in hours) is acquired from the instance of Agent for RAID in (2). 7 Hitachi Command Suite products are vulnerable to a denial of service (DoS) attack related to Apache Commons FileUpload (CVE ). Windows, This problem might occur if a Hitachi Command Suite product receives an invalid request from a malicious third party. 8 When the Server Priority Manager (SPM) group settings are valid in a storage system, Agent for RAID cannot collect performance data by using a TCP/IP connection. Agent for RAID Windows( x64), (x6 4) This problem occurs if all of the following conditions are met: (1) Acquisition of performance data via TCP/IP is set to ON. (For jpcinssetup, TCP/IP or "both" is specified.) (2) The storage system contains a Server Priority Manager (SPM) group. (3) The PI_HBAS record is collected. 9 When the Copy-on-Write Snapshot secondary volume and Thin Image secondary volume are displayed in the Main Console, POOL is displayed by mistake in the Volume Attribute column. Windows, This problem occurs if all of the following conditions are met: (1) A storage system that contains the secondary volume (V-VOL) of Copy-on-Write Snapshot or Thin Image is being monitored. (2) Polling for the storage system in (1) is performed in the Main Console. (3) The Copy-on-Write Snapshot or Thin Image secondary volume (V-VOL) in the storage system for which polling was performed in (2) is displayed in the Main Console window or by using the 2016 Hitachi, Ltd. All rights reserved. 8

9 htm-logicaldisks command. 10 When the htmsrv start -all command is executed, Agent REST Web Service and Agent REST Application Service do not start, performance data cannot be summarized, and access via the API is disabled. Agent for RAID Agent for NAS Windows,, AIX, HP- UX This problem occurs if all of the following conditions are met: (1) Either or both of the following products are installed: - Agent for RAID or later - Agent for NAS or later (2) Either or both of the following conditions are met: - Hybrid Store is used as the storage location for the Performance database (in Windows and only). - The API is used. (3) Either or both of the following services are stopped: - Agent REST Web Service - Agent REST Application Service (4) Because of an error in the Agent instance settings or environment, some Agent instances successfully start services, but other Agent instances fail to start services on the same host. (5) The htmsrv start -all command is executed. 11 When an alarm is imported, no confirmation message for overwriting the alarm appears. This problem occurs when all of the following conditions are met. - LANG is not EUC. - The alarm name to be imported by the jpctool alarm import command contains multibyte characters. - The alarm already exists. - The jpcalarm import command is executed. Known problems # Known Problems Applied products Applied 1 When obtaining performance data by using Tuning Manager API, you cannot obtain the corresponding performance data in the case of sending the request message that includes "+" in the query-string. For example, you cannot obtain the corresponding performance data in the case of specifying "RAID_TYPE=RAID5(3D+1P)" in the query-string. All Hitachi, Ltd. All rights reserved. 9

10 2 When you use Hybrid Store as a performance database and change time zone, the following problems will happen: - It takes a long time (several tens of minutes to several hours. It depends on the number of resources on monitoring systems) to start Agent REST API component. - Latest values of performance data that was aggregated are incorrect. 3 When using Hybrid Store on, the service fails to start and the message indicating incorrect property value is not output to the log. Agent for RAID Agent for NAS Agent for RAID Agent for NAS Windows, The following property files are affected: - <installationdirectory>/htnm/agent/config/dbdataglobalconfig.ini - <installation-directory>/agtx#/store/<instancename>/dbconfig.ini #: x is replaced with the Agent product ID. If the service fails to start, review the value set for the property, and then start the service again. 4 When you upgrade Agent for RAID or Agent for NAS in an environment where an agent of a cluster configuration exists, if you select Hybrid Store in upgrading process while the shared disk (that is, the environment directory of the logical host) cannot be connected, the process will be failed. Agent for RAID Agent for NAS Windows, Always execute the following procedure when an agent of a cluster configuration exists in the target installation environment: (a) In Windows (a-1) If all data is inherited: 1. Stop the services from the clustering software. 2. Make sure that the execution host can connect to the shared disk. 3. Start the upgrade in the execution host. 4. Select [Hybrid Store (recommended)] when you select the Performance database. 5. Select [Transfer all performance data] and finish installation. 6. Make sure the standby host can connect to the shared disk. 7. Start the upgrade in the standby host. 8. Select [Hybrid Store (recommended)] when you select the Performance database. 9. Select [Do not transfer any performance data] and finish installation. 10. Stop the Agent REST API Component services Hitachi, Ltd. All rights reserved. 10

11 Execute the command "htmsrv stop - webservice". (* If there are multiple standby hosts, execute steps 6-10 for all standby hosts) 11. Start the services from the clustering software, and start operation. (a-2) If data is not inherited: 1. Stop the services from the clustering software. 2. Make sure that the host that executes the upgrade can connect to the shared disk. 3. Start the upgrade. 4. Select [Hybrid Store (recommended)] when you select the Performance database. 5. Select [Do not transfer any performance data] and finish installation. 6. Stop the Agent REST API Component services. Execute the command "htmsrv stop - webservice". (Execute steps 2-6 for all hosts.) 7. Start the services from the clustering software, and start operation. (a-3) If data is inherited after installation: 1. Stop the services from the clustering software. 2. Make sure that the host that executes the upgrade can connect to the shared disk. 3. Start the upgrade. 4. Select [Hybrid Store (recommended)] when you select the Performance database. 5. Select [Transfer performance data after installation] and finish installation. (Execute steps 2-5 for all hosts.) 6. Change the Performance databases of all hosts to Hybrid Store. For details, see "Migrating the Store database to the Hybrid Store" in the manual Hitachi Command Suite Agent Administration Guide. 7. Start the services from the clustering software, and start operation. (b) In (b-1) If all data is inherited: 1. Stop the service from the clustering software. 2. Remove the script registered in the clustering software. 3. Make sure that the execution host can connect to the shared disk. 4. Start the upgrade in the execution host. 5. Select [Hybrid Store (recommended)] when you 2016 Hitachi, Ltd. All rights reserved. 11

12 select the Performance database. 6. Select [Transfer all performance data] and finish installation. 7. Make sure the standby host can connect to the shared disk. 8. Start the upgrade in the standby host. 9. Select [Hybrid Store (recommended)] when you select the Performance database. 10. Select [Do not transfer any performance data] and finish installation. 11. Stop the Agent REST API Component services. Execute the command "htmsrv stop - webservice". (* If there are multiple standby hosts, execute steps 7-11 for all standby hosts) 12. Stop the service from the clustering software. 13. In the clustering software, register the script that registers the agents service. 14. Start the service from the clustering software, and start operation. (b-2) If data is not inherited: 1. Stop the service from the clustering software. 2. Remove the script registered in the clustering software. 3. Make sure that the host that executes the upgrade can connect to the shared disk. 4. Start the upgrade. 5. Select [Hybrid Store (recommended)] when you select the Performance database. 6. Select [Do not transfer any performance data] and finish installation. 7. Stop the Agent REST API Component services. Execute the command "htmsrv stop - webservice". (Execute steps 3-7 for all hosts.) 8. Stop the service from the clustering software. 9. In the clustering software, register the script that registers the agents service. 10. Start the service from the clustering software, and start operation. (b-3) If data is inherited after installation: 1. Stop the service from the clustering software. 2. Remove the script registered in the clustering software. 3. Make sure that the host that executes the upgrade can connect to the shared disk. 4. Start the upgrade. 5. Select [Hybrid Store (recommended)] when you 2016 Hitachi, Ltd. All rights reserved. 12

13 select the Performance database. 6. Select [Transfer performance data after installation] and finish installation. (Execute steps 3-6 for all hosts.) 7. Change the Performance databases of all hosts to Hybrid Store. For details, see "Migrating the Store database to the Hybrid Store" in the manual Hitachi Command Suite Agent Administration Guide. 8. Stop the service from the clustering software. 9. In the clustering software, register the script that registers the agents service. 10. Start the service from the clustering software, and start operation. 5 When you execute the following commands in an environment where an agent of a cluster configuration exists, if the commands are executed while the shared disk (that is, the environment directory of the logical host) cannot be connected, the conversion process of the performance database of the agent on a logical host fails with the KATR00124-E message. Make sure that the shared disk can be connected when you perform the following operations: - Executing the htmhsmigrate command - Executing the htmhsconvert command Agent for RAID Agent for NAS Windows, Also, when changing the Performance database by using the htmhsmigrate command, do not start the Agent for RAID or Agent for NAS service until migration of all the physical hosts to Hybrid Store has finished. Note1: Applies to all supported operating systems Resolved known problems For # Resolved known problems Applied products Applied 1 In the following environments, if you install the Tuning Manager or the agents on an XFS file system whose size exceeds 1 TB, the installation might fail or startup of the service after the installation might fail. agents - Red Hat Enterprise 7 - Oracle 7 - SUSE Enterprise Server 12 You can use one of the following methods to prevent this problem: (a) Use another file system such as ext Hitachi, Ltd. All rights reserved. 13

14 (b) If you do use XFS, use one of the following methods: 1. Split the partition so that the size of the file system is less than 1 TB. 2. Mount the XFS file system by specifying the option -o inode32. 2 If agents are used with Hybrid Store and the disk space for the installation directory or the Hybrid Store output directory is insufficient, the Agent REST API component might not start normally. To avoid this, make sure that you estimate the necessary disk space before performing operations. Agent for RAID Agent for NAS Windows, Installation precautions and agents # Installation Precautions Applied products Applied 1 Do not install and agents in the host on which the following products are installed: - Analytics probe of Hitachi Infrastructure Analytics Advisor Note1: Applies to all supported operating systems Tuning Manager Tuning Manager agents All 1 # Installation Precautions Applied products Applied 1 After installing the 8.5.0, if the database of the which had been exported on version to was imported, the Tuning Manager might take approximately 1 hour to start at the first time after the import. 2 After an installation or removal, shortcut folder named "programs" might be incorrectly created under the Windows Start menu. This symptom is temporary, and this shortcut folder will no longer appear after you log off and log on to Windows. 3 If the following message is recorded in the Common Component installation log file, the installation file is registered to be updated as a pending file for next start up. Restart the machine, and then start the installer again. Log file location: <system drive> File name: hcmdsist.log [hh:mm:ss] Installation result: [hh:mm:ss] Tuning Manager Tuning Manager Tuning Manager All 1 Windows Windows 2016 Hitachi, Ltd. All rights reserved. 14

15 4 The following library was added as a prerequisite library for Red Hat Enterprise 6.5. Apply this patch if you use Red Hat Enterprise upstart el6_5.3.x86_64 or later 5 Port numbers in the range from to were added for use in to enhance security. Therefore, confirmation is required that the port numbers from to are not used by other programs. If these port numbers are used by other programs, change any of the port numbers used by other programs, or temporarily suspend the other programs and change the port number used by the product from the default value after installation. For details on changing port numbers, see "Managing ports used by Common Component" in the Hitachi Command Suite Server Administration Guide 6 If the version of the you use is or later, the version of Device Manager in the system must also be or later. Note1: Applies to all supported operating systems Tuning Manager Tuning Manager Tuning Manager All 1 All 1 agents # Installation Precautions Applied products Applied 1 If you install the agent version or earlier in an environment that already contains a Tuning Manager agent product of version or later, the following items are displayed in the Start menu:(*) - Administrator Console - Administrator Console - HTnM Tuning Manager agents Windows (*)Coexistence of these menu items does not affect program operations. Use either of them to start Administrator Console. 2 When installing Agent for RAID or Agent for NAS, the path which can be specified for the destination of Hybrid Store output is as follows. However, in, the path which include spaces cannot be specified for the destination of Hybrid Store output. a. Specify an existing path. The path must be from 1 to 80 bytes long. b. Specify an absolute path. Do not use the following: - Symbolic link - Network folder - Network drive c. Use single-byte alphanumeric characters, symbols, and spaces. Do not use the following characters: ;, *? ' " < > 3 If the version of you use is or later, the versions of the and Agent for RAID Agent for NAS Tuning Manager agents Windows, All Hitachi, Ltd. All rights reserved. 15

16 agents running on the same host must also be or later. However, for agents running on remote hosts on which a of version or later is running, you do not need to upgrade the version to Note1: Applies to all supported operating systems Upgrade precautions # Upgrade Precautions Applied products Applied 1 If you upgraded the from version to to version 8.5.0, the might take approximately 1 hour to start at the first time after upgrade. 2 If following products are installed, upgrade them to or later. - Device Manager - Tiered Storage Manager - Replication Manager - - Compute Systems Manager - Global Link Manager 3 If you upgrade Hitachi Command Suite products from or earlier to or later, confirm the following services are running in the Services window in Windows. If both or one of them is not running, start them. - HiRDB/EmbeddedEdition _HD0 - HiRDB/EmbeddedEdition _HD1 All 1 All 1 Windows Upgrade Installation fails message with KATN00231-E if both or one of them is not running. KATN00231-E An attempt to start the HiRDB database has failed. Processing will be stopped. 4 About the lapse of time for upgrade installation. When upgrading the version from or earlier to or later, the upgrade installation may take a long time to move the place of database from 32 bit to 64 bit. The estimate time for the upgrade installation depends on the size of the database. The following shows criterion of a configuration with which might take more than three hours for the installation of Hitachi Command Suite products. All 1 An environment of installation CPU: vcpu * 2 (4GHz) 2016 Hitachi, Ltd. All rights reserved. 16

17 HDD: SATA drive 7200rpm 1TB The estimate time for installation (upgrade from V7.6.1 to V8.0.0) The estimate time for products first installation (1)The estimate time for the installation is the total time of the Backup-time (*1) of every Hitachi Command Suite products that had already been installed which shown in Table 1 or Table 2, and the Import-time of the installing product, and etc. in the tables. *1: The first upgrade installation takes longer time because backup of every installed Hitachi Command Suite products have to take place. (2)The estimate time for the products installation after (1) The estimate time for the installation is the total time of the Import-time of the products shown in Table1 and Table2, and etc. in the tables. Table1 estimating time for installation (Windows) units: minutes # Product name Comp osition Backu p Import etc. 1 -Device Manager, -Tiered Storage Manager, - Replication Manager 2 -Tuning Manager 3 -Global Link Manager 4 -Compute Systems - Volum es: 128, Paths: 512, Hosts: 1,000 - Paths/ hosts: 1,000 - Hosts: 60 - Pathst atuslo g: 4GB (total capaci ty) - Chassi Hitachi, Ltd. All rights reserved. 17

18 Manager s: Blades : 1,000 - Hosts: 1,000 Table2 estimating time for installation () units: minutes # Product name Comp osition Backu p Import etc. 1 -Device Manager, -Tiered Storage Manager, - Replication Manager 2 -Tuning Manager - Volum es: 128, Paths: 512, Hosts: 1, If you upgrade the version of the to or later, you must also upgrade the version of Device Manager to or later. 6 When you upgrade the of a version earlier than to or later, note the following: In versions earlier than 8.5.0, the most recent association between LDEVs and processors might not be displayed due to invalid data in the database caused by a defect in the. If this problem occurs and the database data at a past time also has a problem, it might be possible to display the association by specifying the past time in the report window. However, after a certain time, the association cannot be displayed. To avoid this problem, when upgrading from a version earlier than to or later, restore data in the database so that the most recent association between LDEVs and processors can be displayed correctly. Available modification methods are the automatic data restoration described below as a corrective action, as well as manually recovering before the upgrade. Each method has associated restrictions or side effects, as shown below. Therefore, perform one of the two options, (1) automatic restoration of data in the database during the upgrade or (2) manual recovery of data in the database before the upgrade. Agent for RAID All 1 Windows (1) Automatic restoration of data in the database during the upgrade (i) Task details Perform an upgrade installation of the 2016 Hitachi, Ltd. All rights reserved. 18

19 from a version earlier than to or later rather than performing the procedure described in (2) Manual recovery of data in the database before the upgrade, described later. (ii) Restrictions or side effects - Associations can no longer be displayed even for past times that were displayed correctly. The past time for which associations can no longer be displayed depends on the LDEV. If the LDEV configuration has been changed, associations for the last time that the configuration changed can no longer be displayed, but those for earlier times can be displayed. - If polling is performed in a normal environment before a maximum of one hour has passed since the upgrade, the association between LDEVs and processors might not be displayed. In this case, you can display the association between LDEVs and processors by performing polling after a maximum of one hour has passed since the upgrade. (iii) Details and restrictions, and conditions for the occurrence of side effects The information here applies if storage devices monitored by the have LDEVs for which the most recent associated processors cannot be displayed, and manual recovery of data in the database before the upgrade, the procedure described in (2) below, has not been performed. (2) Manual recovery of data in the database before the upgrade (a) Task details (i) Temporarily remove the affected storage from the monitoring targets of Main Console, and then add it again as a monitoring target (the details are described later). (ii) Perform an upgrade installation of the Tuning Manager. (iii) Perform polling. For details about step (i), see <Step (i) details> described later. If you upgrade the of a version earlier than to or later after performing this recovery procedure, the side effects described in (1) do not occur, because automatic restoration of data in the database in (1) has not been performed. (b) Restrictions or side effects After the recovery procedure is performed, the Main Console handles the monitored storage as different storage compared to before the recovery. This causes the following side effects: Problem with custom charts: Charts defined for a storage system before a 2016 Hitachi, Ltd. All rights reserved. 19

20 recovery is performed are no longer displayed after the recovery of the storage system. If the charts are necessary, re-define them after recovery. Problem with performance information charts: Performance charts for time periods before a recovery are not displayed in the report window. Performance charts for time periods after a recovery can be displayed in Main Console on the Tuning Manager. To view performance information collected before recovery, use Performance Reporter on the. Problem with capacity information charts: For the storage capacity charts displayed in Main Console on the, continuity of data collected before and after recovery will be lost. That is, if a time range that includes the time at which a recovery was performed is specified, the report window can display only data collected after the time at which recovery was performed. To display a chart of data collected before recovery in the report window, set a time period before the time at which recovery was performed. Recovery procedure: Follow the recovery procedure below to delete, from the monitoring targets of the, the storage systems for which symptoms have occurred and then add those storage systems back to the monitoring targets. 1) Clear the automatic-polling settings. Note: - Before you clear the automatic-polling settings, make sure that you record them. You will need to restore these settings after the recovery in step 6). - For details about automatic-polling settings, see the following manual: [Manual] Software Server Administration Guide Specifying settings for data acquisition from Agents and DeviceManager Configuring the polling settings 2) Stop the Agent for RAID instance. a) Log in (as a member of the Administrators group in Windows or as the root user in ) to the host that the Agent for RAID instance is running on. b) Stop the Agent for RAID instance that symptoms have occurred by executing the following commands Hitachi, Ltd. All rights reserved. 20

21 In Windows: cd Agent-installation-folder\tools jpcstop agtd inst= Agent-for-RAID-instancename In : cd /opt/jp1pc/tools./jpcstop agtd inst=agent-for-raid-instancename c) Confirm that the service of the Agent for RAID instance that symptoms have occurred is in the Inactive status by executing the following command: In Windows: jpcctrl list "D*" In :./jpcctrl list "D*" 3) Remove the monitored Agent for RAID instance from the 's monitoring targets. a) Log in (as a member of the Administrators group in Windows or as the root user in ) to the host that the is running on. b) Delete the service that corresponds to the Agent for RAID instance that symptoms have occurred from Collection Manager by executing the following commands: In Windows: cd Agent-installation-folder\tools jpcctrl delete service-id host=host-name In : cd /opt/jp1pc/tools./jpcctrl delete service-id host=host-name c) Restart the on the host which was running the. In Windows: cd <Common-Component-installationfolder>\bin hcmds64srv /stop / TuningManager hcmds64srv /start / TuningManager In : 2016 Hitachi, Ltd. All rights reserved. 21

22 cd <Common-Component-installationdirectory>/bin./hcmds64srv -stop - TuningManager./hcmds64srv -start - TuningManager d) Log in to the, and then perform refresh processing. i. From the Administration menu, display the Polling Settings screen. ii. In the application bar area, click the Refresh button. e) Confirm that the Agent for RAID instance that symptoms have occurred is not displayed as a related agent in the agent list of the Polling Settings screen. 4) Start the Agent for RAID instance. Start the Agent for RAID instance that symptoms have occurred on the host that was running the instance. In Windows: jpcstart agtd inst=agent-for-raid-instance-name In :./jpcstart agtd inst=agent-for-raid-instancename 5) Start the Agent for RAID instance. a) On the, perform polling between from xx:15 and xx: From the Administration menu, display the Polling Settings screen. 2. In the agent list, select the objects to be monitored. 3. In the report area, click the Start Polling button. b) Confirm that the Agent for RAID instance that symptoms have occurred is displayed as a related agent in the agent list of the Polling Settings screen. c) Check whether symptoms have occurred in the Agent for RAID instance. If a symptom has occurred, re-perform the steps from step 2). If the Agent for RAID instance has recovered from the symptoms, go to step 6). 6) Restore the automatic-polling settings that you cleared Hitachi, Ltd. All rights reserved. 22

23 Note1: Applies to all supported operating systems agents # Upgrade Precautions Applied products Applied 1 To upgrade the version of to or later, you must also upgrade the and agents running on the same host to version or later. 2 For Agent for SAN Switch or later, a 64-bit edition of the JDK is now required (rather than a 32-bit edition). Therefore, in an environment where the Oracle JDK is used to monitor Agent for SAN Switch, if Agent for SAN Switch is upgraded to version or later, the Oracle JDK is automatically switched to the default JDK. If you want to use the Oracle JDK, change the settings again after the version has been upgraded. 3 In Windows or, after Agent for Oracle is upgraded from a version earlier than to or a later version, the instance information must be updated. If you start an Agent for Oracle service without updating the instance information, the service abnormally stops with the following messages: agents Agent for SAN Switch Agent for Oracle All 1 All 1 Windows Window s Error messages KAVF12020-E While executing functionname function called-function-name failed. KAVF12023-E Agent Collector is going to stop because the error has occurred. KAVF12004-E Agent Collector stopped abnormally. KAVF12011-E Initialization of interprocess communication failed. KAVF12021-E Error occurred by function functionname. (en=error- code,arg1=argument-1,arg2=argument- 2,arg3=argument-3) KAVF12023-E Agent Collector is going to stop because the error has occurred. KAVF12004-E Agent Collector stopped abnormally. For the sections where the instance information must be updated, see Precautions for collecting the record with Agent for Oracle. If you upgrade Agent for Oracle from a version earlier than to or a later version, the 32-bit edition of Oracle Client will become unnecessary. You can uninstall Oracle 2016 Hitachi, Ltd. All rights reserved. 23

24 Client if it is used with Agent for Oracle only. Note1: Applies to all supported operating systems Removal precautions None. agents # Upgrade Precautions Applied products Applied 1 The menu item Administrator Console - HTnM is not removed from the Start menu if both of the following conditions are met: (1) The agent is not installed on the host on which the is installed. (2) The version of the last uninstalled agent is or earlier. agents Windows Preventive measures: Uninstall the agent first. Action to be taken if the problem has occurred: After the agent has been uninstalled from all hosts, manually remove Administrator Console - HTnM if it remains in the Start menu. 2 A agent whose version is or earlier and a agent whose version is or later might be installed in the same environment. In such a case, if you want to uninstall both agents, uninstall agent or earlier first. agents Windows Usage precautions Notes on using in the built-in Administrator account when using Internet Explorer When you click a button or anchor on the screen to open a new tab or new window, an extra blank window or transitional window might be displayed at the same time. In such a case, please close the unnecessary window. Windows 2016 Hitachi, Ltd. All rights reserved. 24

25 If this problem occurs, create a new Windows user account, and then use the new user account to operate the browser. Notes on the use of Performance Reporter when using Internet Explorer 9 or later on Windows Server 2008: 1 If you move the Message dialog box in the browser, an image of the Message dialog box might remain displayed in the pre-move location. If this displayed image remains, close the Message dialog box by clicking the [OK] or [Cancel] button in the Message dialog box. Windows Notes on the use of Performance Reporter when using Internet Explorer 11.0: 1 When you select any record in [All Fields] in the [New Report > Field] window of the Report Wizard, the text box for the description may appear with its lower edge cut off. If this happens, adjust the display width of the frame information by adjusting the window size or position dividers. Windows Precautions for displaying a list of installed programs 1 When the Add or Remove Programs dialog box is opened, the displayed icon of this product might switch from an icon displayed initially to the other icon (*1). *1: Any of the icons registered in Windows Windows Even if this symptom occurs, the is operational normally. agents None Hitachi, Ltd. All rights reserved. 25

26 Precautions for monitoring Brocade SAN switches None. agents 1 If Brocade(R) SMI Agent v x (x is "a" or later) or v is used for monitoring a fabric consisting of only Brocade switches whose firmware versions are v5.2.0 or later, a blank might appear for Model Name and Vendor Name for these switches. Brocade has corrected this problem in Brocade SMI Agent v To monitor Brocade switches, use Brocade SMI Agent v or later. 2 If Brocade SMI Agent v or v is used for monitoring a fabric including Brocade switches whose firmware versions are v5.2.x, Agent for SAN Switch might fail to collect the data necessary to create a record. Upgrade the firmware version of all switches in the same fabric to v5.3.x or later. Agent for SAN Switch Agent for SAN Switch Applies to all supported operating systems Applies to all supported operating systems Notes for trouble on an operation of Agent for SAN Switch None. agents 1 When Agent for SAN Switch causes a trouble while monitoring CISCO switches, we might ask to gather material for investigation with the packet capture tool etc. Agent for SAN Switch Applies to all supported operating systems Precautions for displaying a correlation reports 1 Even if a system failover is performed by High Availability Manager functionality for the Universal Storage Platform V/VM series, Virtual Storage Platform, Applies to all supported 2016 Hitachi, Ltd. All rights reserved. 26

27 Virtual Storage Platform G1000 or Virtual Storage Platform Gx00 series, the continues to display the active volume, not the standby volume, as related to the relevant device file. operating systems agents None. Precautions for monitoring a storage system 1 If LDEVs are being configured by combining various LDEVs in multiple parity groups in a LUSE configuration, the [Write Hit Ratio] of the parity groups might temporarily exceed 100% depending on the level of measurement error used by the storage system. (In such a case, treat the value that exceeds 100% as 100%.) This problem might occur while the Thunder 9200 series, the Thunder 9500V series, or the Hitachi AMS/WMS series is being monitored. Applies to all supported operating systems agents None. Precautions for monitoring again a Storage System or a Server which had been monitored in the past 1 If users accidentally delete a storage device or host from the list of targets to be monitored by, or if users accidentally change the storage configuration, the might not properly display information even if the status of the storage device or host is restored. Table-1 describes the relationship between the devices monitored by the and the information that cannot be properly displayed. Table-1 Devices monitored by the and related error Item Devices monitored by the Tuning Error Manager Applies to all supported operating systems Storage Host Virtualiz ation Oracle 2016 Hitachi, Ltd. All rights reserved. 27

28 (a) * Relevant information between storage components is not properly displayed. (b) * * Relevant information between storage devices and hosts is not properly displayed. (c) * * Relevant information between storage devices and virtualization s is not properly displayed. (d) * * Relevant information between hosts and Oracle is not properly displayed. Legend: *: Monitored devices for which the error occurs Blank: Monitored devices for which the error does not occur The conditions that cause the error and the recovery procedure are as follows: 1. Conditions This error might occur if either of the following operations is performed: (a) Operation 1: (i) Add the devices indicated by * in Table-1 (b), (c), or (d) to the list of targets to be monitored by the Tuning Manager. Then, refresh the list of Agents on the. (ii) From the, perform automatic or manual polling on the monitoring targets that were added in step (i). (iii) After polling, delete the storage devices or hosts from the list of targets to be monitored by the Tuning Manager by using one of the following operations: [For storage devices] - Delete Agent for RAID from the list of targets to be monitored by the. - Remove the storage devices from Device Manager. [For hosts] - Delete Agent for Server System from the list of targets 2016 Hitachi, Ltd. All rights reserved. 28

29 to be monitored by the (if the host is monitored in Agent mode). - Remove the host from Device Manager (if the host is monitored in agentless mode). (iv) Refresh the list of Agents on the. (v) Add the monitoring targets that were deleted in step (iii) and whose configurations have not been changed since step (iii) to the list of targets to be monitored by the again by using one of the following operations: [For storage devices] - Add Agent for RAID to the list of targets to be monitored by the. - Add the storage devices to Device Manager. [For hosts] - Add Agent for Server System to the list of targets to be monitored by the (if the host is monitored in Agent mode). - Add the host to Device Manager (if the host is monitored in agentless mode). (vi) Refresh the list of Agents on the. (vii) From the, perform automatic or manual polling again on the monitoring targets on which polling was performed in step (ii). (b) Operation 2: (i) Add the devices indicated by * in Table-1 (a), (b), or (c) to the list of targets to be monitored by the Tuning Manager. Then, refresh the list of Agents on the. (ii) From the, perform automatic or manual polling on the monitoring targets that were added in step (i). (iii) For the monitored storage devices, one of the following operation is performed: - Remove the hardware (port or disk) - Delete the SLPR or CLPR - Change SLPR that belongs to the command device. (iv) From the, perform automatic or manual polling again on the monitoring targets on which polling was performed in step (ii). (v) For the monitored storage devices indicated in step (iii), restore them to their status before step (iii). (vi) From the, perform automatic or manual polling again on the monitoring targets on which polling was performed in step (ii). Table-2 lists the information that is not properly displayed after Operation 1 or Operation 2 is performed. Table-2 Operations that cause this error and the 2016 Hitachi, Ltd. All rights reserved. 29

30 information that is not properly displayed # Operation Information that is not properly displayed 1 Operation 1 Table-1 (b), (c), and (d) 2 Operation 2 Table-1 (a), (b), and (c) 2. Recovery procedure Perform one of the procedures below (from 1 to 3) indicated in Table-3 depending on the monitored device on which the error occurred. Table-3 Procedures for recovering from the error # Condition Recovery procedure 1 The error occurs on a host that is being monitored in agentless mode. 2 The error occurs on a virtualization. Procedure 1 Procedure 2 3 In cases other than 1 and 2. Procedure 3 (a) Procedure 1: (i) Remove from Device Manager the storage device that contains volumes that are connected to the host. (ii) Use Device Manager to refresh the host indicated in step (i). (iii) From the, perform manual polling on Device Manager.#1 (iv) Add the storage device that was removed from Device Manager in step (i) to Device Manager again. (v) Use Device Manager to refresh the host indicated in step (i) again. (vi) From the, perform manual polling on Device Manager.#1 #1: Be sure to wait at least one hour after the last polling was performed before you perform manual polling. (b) Procedure 2: (i) Delete the storage device that contains volumes being used as a datastore of the virtualization from the list of targets to be monitored by the by using one of the following operations: - Delete Agent for RAID from the list of targets to be monitored by the. - Remove the storage devices from Device Manager. (ii) From the, perform manual polling on the Device Manager that manages the virtualization indicated in step (i).# Hitachi, Ltd. All rights reserved. 30

31 (iii) Add the storage device that was removed from the list of targets to be monitored by the in step (i) to the list of monitoring targets again. - Add Agent for RAID to the list of targets to be monitored by the. - Add the storage devices to Device Manager. (iv) From the, perform manual polling on Device Manager.#1 #1: Be sure to wait at least one hour after the last polling was performed before you perform manual polling. (c) Procedure 3: (i) Delete the monitoring targets whose information is not properly displayed from the list of targets to be monitored by the. (ii) Add the monitoring targets that were removed in step (i) to the list of targets to be monitored by the again. (iii) From the, perform manual polling on the Agents that monitor the added targets.#1 #1: Be sure to wait at least one hour after the last polling was performed before you perform manual polling. agents None. Precautions for displaying a report with the 1 When all of the following conditions are met, the hyperlink for a related host is not displayed on a report displayed by procedures described in the [How to display a report]. [Conditions] (1) Connect the Agent for Oracle to the. (2) Monitor the host in which the Agent for Oracle has been installed by the Agent for Server System. (3) The hostname mentioned in (2) contains a lowercase letter. Applies to all supported operating systems 2016 Hitachi, Ltd. All rights reserved. 31