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 Installation precautions Usage precautions Documentation Copyrights and licenses About this document This document (RN-00HS262-71, February 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. This release is a major release that adds new features. 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 MK-96HC MK-92HC MK-92HC Hitachi, Ltd. All rights reserved. 2

3 Hitachi Command Suite Tuning 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-95HC 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 as an operating environment. - Red Hat Enterprise The following Operating System is now supported as an operating environment. - Oracle The following Operating Systems are now supported as monitoring targets: - Red Hat Enterprise Oracle SUSE Enterprise Server 12 SP1 Agent for Oracle Agent for DB2 Agent for Oracle All 1 4 The following NAS system is now supported as a monitoring target: - Hitachi File Services Manager v5.3 5 The following HNAS are supported as management targets: - HNAS4100 (Firmware version: 12.5) - HNAS4080 (Firmware version: 12.5) - HNAS4060 (Firmware version: 12.5) - HNAS4040 (Firmware version: 12.5) Agent for NAS All 1 Agent for NAS All Hitachi, Ltd. All rights reserved. 3

4 - HNAS3090 (Firmware version: 12.5) - HNAS3080 (Firmware version: 12.5) 6 The following storage systems are now supported as monitoring targets: - VSP G1000 (Firmware version: v04) - VSP G800 (Firmware version: v03) - VSP G600 (Firmware version: v03) - VSP G400 (Firmware version: v03) - VSP G200 (Firmware version: v03) - VSP F800 (Firmware version: v03) (*1) - VSP F600 (Firmware version: v03) (*1) - VSP F400 (Firmware version: v03) (*1) (*1) VSP F400 F600, VSP F800, or VSP Fx00 is now displayed as the model name of the storage unit. Agent for Server System Agent for RAID All 1 7 In the following records, you can now obtain both the pre- and post- compression data capacity of pools composed of FMCs. - Operation information (PD_PLC) of DP pool Basic Capacity Total Basic Capacity Used Basic Capacity Free Basic Capacity Usage % Pool Capacity Expansion % FMC Capacity Saving FMC Capacity Saving % Agent for RAID All 1 - Operation information (PD_PLTC) for each tier type of DP pools performing tier management Basic Capacity Total Basic Capacity Used Basic Capacity Free Basic Capacity Usage % FMC Capacity Total FMC Capacity Used FMC Capacity Free FMC Capacity Usage % FMC Capacity Saving FMC Capacity Saving % FMC Capacity Expansion % 8 In operation monitoring that uses the alert functionality, detailed information on storage systems can now be obtained via LAN. - Performance data showing detailed information (PD_PDX) on the storage system DKC Name DKC Serial Number Vendor ID Agent for RAID Windows, 2016 Hitachi, Ltd. All rights reserved. 4

5 9 The following database is now supported. - Microsoft SQL Server 2014 SP1 10 Viewing of the window is now supported in an environment installed Adobe Flash Player GUI can now check the user's last login time. 12 In Oracle 7, 7.1, and 7.2, the following database is now supported. - Oracle Database 11g Release 2 Agent for SQL Server Agent for Oracle Windows Windows All 1Yoshitsug u Ono 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 In the HP-UX or AIX environment, on the host of Agent for RAID using API, command execution errors might occur, the following symptoms occur: Agent for RAID HP-UX, AIX Symptom 1) The following error message is output in the installation log, and the upgrade installation for Agent for RAID fails. AIX: /opt/jp1pc/htnm/bin/htmrestctrl on: Failed. (error code=255) HP-UX: Installation of - Agent Common Component failed. <component=rest API, rc=43, detail=1> output destination of the install log: /var/opt/hicommand/tuningmanager/logs/htm_inst_log _AGTD_*.log Symptom 2) The following error message is output in the installation log, and the overwrite installation for Agent for RAID fails. /opt/jp1pc/htnm/bin/htmrestctrl on: Failed.(error 2016 Hitachi, Ltd. All rights reserved. 5

6 code=255) output destination of the install log: /var/opt/hicommand/tuningmanager/logs/htm_inst_log _AGTD_*.log Symptom 3) When uninstallation is executed, Uninstallation finishes normally, but the - Agent REST Web Service does not stop and process remains. Symptom 4) The htmrestctrl on command fails with KATR10026-E.*1 message(*1): KATR10026-E An unexpected error occurred during command execution. (detailed information = Failed to start service : webservice) Output Destinations : Standard output Symptom 5) When any of the following commands is executed, the command finishes normally, but the - Agent REST Web Service does not stop. -htmrestctrl off -htmsrv stop -all -htmsrv stop -webservice Symptom 6) When either of the following commands is executed, the command finishes normally, but the - Agent REST Web Service status is displayed as "The specified service is stopped.", even though it is active: -htmsrv status -all -htmsrv status -webservice Symptom 7) When any of the following commands is executed, the command finishes abnormally, and the - Agent REST Web Service does not start. -htmsrv start -all -htmsrv start -webservice This problem occurs when all of the following conditions are met: Symptom 1) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) Agent for RAID is upgraded Hitachi, Ltd. All rights reserved. 6

7 Symptom 2) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) Agent for RAID is overwrite. Symptom 3) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) Agent for RAID is uninstalled. Symptom 4) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) The htmrestctrl on command is executed. Symptom 5) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) Any of the following commands are executed: -htmrestctrl off -htmsrv stop -all -htmsrv stop -webservice Symptom 6) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) Any of the following commands are executed: -htmsrv status -all -htmsrv status -webservice Symptom 7) 1) On the host of Agent for RAID using API. 2) The Agent REST API component service is running for 24 hours or more. 3) Any of the following commands are executed: -htmsrv start -all -htmsrv start -webservice 2 In a environment, the collection of performance data with Agent for RAID by using a TCP/IP connection might fail with OutOfMemoryError. As a result, the following problem occurs: Agent for RAID - The performance data at the time that the collection fails cannot be stored in the database of Agent for RAID. Therefore, the data at the time of the failure is missing, which results in an incorrect display and output of the history report. When the error occurs, the following message is output to 2016 Hitachi, Ltd. All rights reserved. 7

8 the log. message: KATR14203-E An unexpected error occurred. java.lang.outofmemoryerror: Java heap space output destination of the log message: /opt/jp1pc/agtd/agent/instancename/log/pmmccollectormessagen.log This problem occur when both of the following conditions are met: 1) In the environment settings of an instance of Agent for RAID, either of the following is selected as the connection method for performance data collection. - using TCP/IP connections - using TCP/IP connections and command device 2) There are about 1,000 or more LDEVs in the storage system monitored by the instance in 1). (*1) (*1) The above number of LDEVs is a rough guide. If more storage system resources are used including those of LDEVs, this problem is more likely to occur. 3 If the alert definition synchronization API function is executed in Agent for RAID, the following problem occurs: - The synchronization alert definition before synchronization that must be deleted might be continuously evaluated. Agent for RAID Windows, This problem may occur when all of the following conditions are met: 1) An Agent instance meets both of the following conditions: - One or more alert definitions are set for the Agent instance. - An alert definition has not been synchronized. 2) The alert definition synchronization API function is executed when there is no alert definition to be synchronized for the Agent instance in 1). 4 When the htmhsconvert command is executed, either of the following symptoms occurs: Symptom 1) The htmhsconvert command fails with the KATR10078-E message. KATR10078-E Failed to inherit the configuration information. (servicekey = service-key-of-the-agent, instance name = Agent-instance-name, host name = host-name, detailed information = 255) Agent for RAID Agent for NAS Symptom 2) The htmhsconvert command fails with the KATR00124-E message Hitachi, Ltd. All rights reserved. 8

9 KATR00124-E An unexpected error occurred during command execution. (detailed information = 255) The message is output to the following location: installation-directory/htnm/logs/htmhsconverttrace#.log #: Log file number This problem may occur when all of the following conditions are met: Symptom 1) 1) The target product is installed in a 64-bit environment. 2) The htmhsconvert command is executed without the - deletestore option specified. Symptom 2) 1) The target product is installed in a 64-bit environment. 2) The htmhsconvert command with the -deletestore option specified is executed. 5 In monitoring storage systems by Agent for RAID, information about the virtual storage machines becomes invalid. The following problems occur. When performance data is collected by Agent for RAID or later, the following information about virtual storage machines becomes invalid. Record name LDEV Summary - Extended(PI_LDE) LDEV Summary 1 - Extended(PI_LDE1) LDEV Summary 2 - Extended(PI_LDE2) LDEV Summary 3 - Extended(PI_LDE3) Logical Device Configuration(PD_LDC) Logical Device Summary(PI_LDS) Logical Device Summary 1(PI_LDS1) Logical Device Summary 2(PI_LDS2) Logical Device Summary 3(PI_LDS3) Agent for RAID Windows,, HP- UX, AIX Field name Virtual DKC Name(VIRTUAL_DKC_NAME) Virtual LDEV Number(VIRTUAL_LDEV_NUMBER) Virtual Serial Number(VIRTUAL_SERIAL_NUMBER) This problem occurs when all of the following conditions are met: 1) The target storage system (VSP G200, G400, G600, G800, VSP G1000, VSP) is monitored by Agent for RAID or later Hitachi, Ltd. All rights reserved. 9

10 2) An LDEV is registered in a virtual storage machine of the storage system in (1). 3) The following records are collected: - PD_LDC - PI_LDS/PI_LDS1/PI_LDS2/PI_LDS3 - PI_LDE/PI_LDE1/PI_LDE2/PI_LDE3 6 In monitoring storage systems by Agent for RAID, information about the virtual storage machines becomes invalid. The following problems occur. When performance data is collected by Agent for RAID or later in an AIX environment, the following information about virtual storage machines becomes invalid. Record name LDEV Summary -Extended(PI_LDE) LDEV Summary 1 - Extended(PI_LDE1) LDEV Summary 2 - Extended(PI_LDE2) LDEV Summary 3 - Extended(PI_LDE3) Logical Device Configuration(PD_LDC) Logical Device Summary(PI_LDS) Logical Device Summary 1(PI_LDS1) Logical Device Summary 2(PI_LDS2) Logical Device Summary 3(PI_LDS3) Agent for RAID AIX Field name Virtual DKC Name(VIRTUAL_DKC_NAME) This problem occurs when all of the following conditions are met: 1) The target storage system (VSP G200, G400, G600, G800, VSP G1000, VSP) is monitored by the Agent for RAID or later in an AIX environment. 2) An LDEV is registered in a virtual storage machine of the storage system in (1). 3) The following records are collected: - PD_LDC - PI_LDS/PI_LDS1/PI_LDS2/PI_LDS3 - PI_LDE/PI_LDE1/PI_LDE2/PI_LDE3 7 The values of performance data collected by using Tuning Manager API are invalid. The following problems occur. Agent for RAID Windows,, AIX, HP- UX The values of performance data collected by using Tuning Manager API are invalid. Example: (float-type), (double-type) The followings are the records and fields. Record name 2016 Hitachi, Ltd. All rights reserved. 10

11 Port Summary(PI_PTS) Field name Initiator Max I/O /sec(initiator_max_io_rate) Initiator Min I/O /sec(initiator_min_io_rate) Initiator Avg I/O /sec(initiator_avg_io_rate) Initiator Max Xfer /sec(initiator_max_xfer_rate) Initiator Min Xfer /sec(initiator_min_xfer_rate) Initiator Avg Xfer /sec(initiator_avg_xfer_rate) Port Role(PORT_ROLE) Record name Virtual Volume Configuration(PD_VVC) Field name Attribute(ATTRIBUTE) Reserved Capacity(RESERVED_CAPACITY) Record name Pool Configuration(PD_PLC) Field name Reserved Capacity(RESERVED_CAPACITY) Record name Storage Summary(PI) Field name CHA Cache Path Usage %(CHA_CACHE_PATH_USAGE_RATE) DKA Cache Path Usage %(DKA_CACHE_PATH_USAGE_RATE) This problem occurs when all of the following conditions are met: 1) The version of Agent for RAID was updated to or later from a version earlier than ) The updated version of Agent for RAID in 1) is used with the Store database, and use of the API is enabled. 3) There is an operation performance information file when all the following conditions are met: - The file contains records to which a float-type or doubletype field was added as a result of the version update. - The file was generated before the version update, and the data retention period is enabled. 4) After the version update, the API is used to obtain the performance data in 3). 8 The values of performance data collected by using Tuning Manager API are invalid. The following problems occur. Agent for RAID Windows,, AIX, HP- UX 2016 Hitachi, Ltd. All rights reserved. 11

12 The values of performance data collected by using Tuning Manager API are invalid. The followings are the records and fields. Record name LDEV Summary 1 - Extended(PI_LDS1) LDEV Summary 2 - Extended(PI_LDS2) LDEV Summary 3 - Extended(PI_LDS1) Field name Write Response Rate(WRITE_TOTAL_RESPONSE) Write Total Response(WRITE_RESPONSE_RATE) This problem occurs when all of the following conditions are met: 1) The target storage system (VSP G1000 or VSP) is monitored by Agent for RAID or later. 2) A logical device (LDEV) that has an LDEV number of 00:40:00 or higher exists in the monitored storage system. 3) Agent for RAID is used with the Store database, and use of the API is enabled. 4) The API is used to obtain performance data. 9 Main Console is used to display storage information, the following symptoms occur: Symptom 1) Processor information is not displayed correctly on Main Console, and the following problems occur: - The number of processors in the summary area is displayed as "0". - The processor list in the information area is displayed as "No object". - No processor is displayed in the tree of the navigation area. Tuning Manager Agent for RAID Windows, Symptom 2) The relationships between the LDEVs and processors cannot be displayed. - "no data" is displayed for the related processors in the LDEV list. - "No object" is displayed for the list of LDEVs associated with processors. Symptom 1) This symptom occurs when both of the following conditions are met: 1) Agent for RAID is operated on Hybrid Store. 2) Either of the following conditions is met: a) The polling offset is 15 minutes or less, or the offset is not specified. b) Perform manual polling between xx:00 and xx: Hitachi, Ltd. All rights reserved. 12

13 Symptom 2) This symptom occurs when all of the following conditions are met: 1) Agent for RAID is operated on Hybrid Store. 2) Either of the following conditions is met: a) The polling offset is 15 minutes or less, or the offset is not specified. b) Perform manual polling between xx:00 and xx:15. 3) Instances that monitor the following storage systems exist: - HUS VM - VSP - VSP G200, 400, 600, VSP G1000 Note: xx indicates any hour of day. 10 Agent for RAID failed to collect performance data by using a TCP/IP connection. For details about the records that can be collected by using a TCP/IP connection, see the following manual: Agent for RAID Windows Hitachi Command Suite Installation Guide Performance data collected using a TCP/IP connection (Agent for RAID) This problem occurs when all of the following conditions are met: 1) In setting up an Agent instance, "2:TCP/IP" or "3: Both" is specified for "Method for collecting". 2) The Agent installation path includes spaces. For example, the following path includes spaces: "C:\Program Files (x86)\hicommand\tuningmanager\jp1pc" 3) The string up to the first space in the path in 2) is the same as the name of an existing file. For example, the string up to the first space in the path in 2) is as follows: "C:\Program" 11 When executing the "jpctdchkinst" command, the following message is not output in [Check Result]: KAVF18850-I No error was found during verification of the agent instance setting. Agent for RAID Windows, This problem occurs when both of the following conditions are met: 1) The monitored storage system is Hitachi HUS100/AMS2000/AMS/WMS/SMS series. 2) Execute the jpctdchkinst command Hitachi, Ltd. All rights reserved. 13

14 12 When using Hybrid Store as performance database, the Agent REST API component services may terminate abnormally. This problem occurs when both of the following conditions are met: - Hybrid Store is used as performance database. - The total number of instances of Agent for RAID and Agent for NAS is two or more. Agent for RAID Agent for NAS Windows, 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. Note1: Applies to all supported operating systems All 1 agents # Known Problems Applied products Applied 1 To delete an instance that is operated by using Hybrid Store, execute the htmsrv stop -webservice command to stop the Agent REST API component before deleting the instance. If you attempt to delete an instance while an Agent REST API component is running, the deletion of the instance might fail with the KAVE05052-E message. 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 Agent for RAID Agent for NAS Windows, Windows, 2016 Hitachi, Ltd. All rights reserved. 14

15 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. 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 2016 Hitachi, Ltd. All rights reserved. 15

16 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 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" Hitachi, Ltd. All rights reserved. 16

17 (* 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 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 Hitachi, Ltd. All rights reserved. 17

18 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. 6 The Pool Configuration (PD_PLC) record of Agent for RAID may have incorrect values for the fields regarding Dynamic Provisioning pool capacity because it disregards the reserved capacity of a pool. The relevant fields of the Pool Configuration (PD_PLC) record are as follows: Agent for RAID Windows,, HP-UX, AIX - Physical Capacity Used - Physical Capacity Free - Physical Capacity Usage % This problem occurs when both of the following conditions are met: (1) The monitored storage system is VSP G1000, VSP G200/G400/G600/G800 or VSP F400/F600/F800. (2) The monitored Dynamic Provisioning pool is configured to have the reserved capacity. Resolved known problems For None Hitachi, Ltd. All rights reserved. 18

19 Installation precautions # Installation Precautions Applied products Applied 1 After installing the 8.2.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] 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 Note1: Applies to all supported operating systems Tuning Manager Tuning Manager Tuning Manager Tuning Manager All 1 Windows Windows 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 Agent for RAID Agent for NAS Windows, 2016 Hitachi, Ltd. All rights reserved. 19

20 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: ;, *? ' " < > 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. If this problem occurs, create a new Windows user account, and then use the new user account to operate the browser. Windows 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 2016 Hitachi, Ltd. All rights reserved. 20

21 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. 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 2016 Hitachi, Ltd. All rights reserved. 21

22 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, 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. Applies to all supported 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 2016 Hitachi, Ltd. All rights reserved. 22

23 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 (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 2016 Hitachi, Ltd. All rights reserved. 23

24 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 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) Hitachi, Ltd. All rights reserved. 24

25 (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 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 Hitachi, Ltd. All rights reserved. 25

26 (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).#1 (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 Hitachi, Ltd. All rights reserved. 26

27 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 [How to display a report] (a) Select the Resources - Applications in the Explorer area. (b) Select the Oracle in the Navigation area. (c) Select the Oracle Instances tab in the Information area (Correlation View). If you want to display a report for the host related to an Oracle instance, select the host from the resource tree. agents None. Precautions for collecting the record with Agent for Oracle None. agents 1 When all of the following conditions are met, store the Agent for Oracle, 2016 Hitachi, Ltd. All rights reserved. 27

28 listener.ora file of Oracle Database under the ORACLE_HOME/network/admin directory of Oracle Client 32bit, and restart Agent for Oracle service. (1) Oracle Database 11gR2 or Oracle Database 12cR1 for Solaris, AIX or (x64) is monitored. (2) The listener is monitored with the SQL*Net Listener (PD_PDNL) record or SQL*Net Listeners (PD_PDLS) record. (3) The monitored listener is not a default listener, and the name of listener or port number has been changed. 2 To monitor Oracle Database on Oracle 7.0, you must apply the patch glibc el7.i686.rpm. After applying glibc el7.i686.rpm, you must install Oracle Client 32-bit. If you do not install Oracle Client 32-bit after applying glibc el7.i686.rpm, a segmentation fault might occur when you start sqlplus in Oracle Client 32- bit or Agent for Oracle. 3 When monitoring Oracle Database from RHEL 7.0 or later, please use Oracle Client (32-bit) for Oracle Database 11g Release 2. Please note that Oracle Client (32-bit) for Oracle Database 12c Release 1 is not supported. When Oracle Client (32-bit) for Oracle Database 12c Release 1 is used, an attempt to activate Agent for Oracle might fail. Agent for Oracle Agent for Oracle AIX, Solaris Precautions for starting or stopping a service automatically on SUSE Enterprise Server 11 and agents 1 When registering or deleting an automatic start/stop script file for by using the chkconfig command on SUSE Enterprise Server 11, a warning message might be output. The following shows an example of an warning message: insserv: warning: script 'jp1_pc' missing LSB tags and overrides insserv: Default-Start undefined, assuming default start runlevel(s) for script 'jp1_pc' There is no problem by this warning message, and disregard it. For procedure about starting a service automatically, refer the following section in the manual Hitachi Command Suite Agent Administration Guide: - "Managing Collection Manager and Agent services" - "Starting and stopping Collection Manager and Agent services" + "Starting a service automatically", agents SUSE Enterprise Server Hitachi, Ltd. All rights reserved. 28

29 Precautions for changing a command device name in an AIX environment None. agents 1 In an environment where AIX v6.1 or AIX v7.1 is installed, if the command device name specified to the "Command Device File Name" item is changed to other than the following format, the performance information cannot be collected from Storage System. Therefore, specify the name according to the following format to the rendev command as the command device name after change. [Format of the command device name] "hdisk" + (Arbitrary half-width alphanumeric characters) agents AIX Notes applying when Load Reduction for Changing Configuration Mode is enabled in a Hitachi AMS2000 series or Hitachi SMS series storage system and agents 1 When the is monitoring a Hitachi AMS2000 series or Hitachi SMS series storage system with "Load Reduction for Changing Configuration Mode" enabled, the following problems might occur if the configuration of the system is changed: (1) Collection of performance data fails. (2) Polling fails. To prevent these problems from occurring, before you change the storage system configuration, stop the services of the and the Agent for RAID instance that is monitoring the storage system, and restart these services after the configuration has been changed. Note1: Applies to all supported operating systems, Agent for RAID All Hitachi, Ltd. All rights reserved. 29

30 Precautions for displaying a vendor name of the switch and agents 1 When all of the following conditions are met, Unknown might be displayed for the switch's vendor name on the tree. (1)In Agent for SAN Switch, Vendor Name field of PD record for some instance is empty string. (2)The combination of the version of the prerequisite program, such as SMI Agent for F/E and DCFM, and the firmware version of the switch is not supported., Agent for SAN Switch All 1 The recovery procedure is as follows: a) Stop the instance of Agent for SAN Switch for which Vendor Name field of PD record includes empty string. b) Confirm the version of the following prerequisite program for the switch which is monitored by the Agent for SAN Switch in a). - SMI Agent for F/E or DCFM (For the Brocade switch only) - firmware version of the switch For details about the supported version of the prerequisite programs for Agent for SAN Switch., see the Hitachi Command Suite System Requirements (MK- 92HC209). c) Start the service of. d) Execute the following command on the Tuning Manager host to delete the instance of the Agent for SAN Switch from the monitoring target. jpcctrl delete "<service ID of the Agent for SAN Switch instance in a)>" e) Click Refresh button on the screen of Administration - Data Polling. f) Start the service of Agent for SAN Switch which is stopped in a). g) Click Start Polling button on the screen of Administration - Data Polling. h) Confirm the Navigation area of the Fabrics and make sure that the switch which is monitored by the Agent for SAN Switch of a) is displayed under the vendor name other than Unknown. Note1: Applies to all supported operating systems 2016 Hitachi, Ltd. All rights reserved. 30

31 Precautions when rebooting and agents 1 When the available IPv6 address has been set in windows system, the symptom such as the following might occur, because the service has been started abnormally after rebooting the. - The report might not be displayed by using Performance Reporter., agents Windows If the above symptom has occurred, perform the following actions after rebooting. - Stop the services by executing the hcmds64srv /stop command and the jpcstop command. - Restart services by the hcmds64srv /start command and the jpcstart command. If the services have failed to stop, stop all services manually whose names are started with "PFM -" from Service Control Manager. To start Service Control Manager, from the Windows Start menu, select Administrative Tools, and then select Services. Precautions for installation folder and agents 1 Do not put files or folders other than provided by Tuning Manager under the following folder. <Tuning-Manager-installation-folder>\jp1pc\tools If you put files or folders other than provided by Tuning Manager to the above folder, executing of commands or starting of the Tuning Manager services might fail., agents Windows Notes on InPrivate Browsing of Internet Explorer During InPrivate Browsing Mode, the browsing history might remain in the browser. Windows 2016 Hitachi, Ltd. All rights reserved. 31

32 Notes on enabling SSL(*1) between the and management clients when using Firefox 1 To enable SSL between the and management clients by using Firefox, perform the following operations: (1) Disable SSL between the and management clients. (2) register the license files (3) Enable SSL between the and management clients. Note1: For details about enabling SSL, see "Security settings for Common Component (communication with the GUI)" in the Hitachi Command Suite Administrator Guide. Notes of using Firefox ESR 17, Firefox ESR 24, Firefox ESR 31 or Firefox ESR 38 1 When using Firefox ESR 17, Firefox ESR 24, Firefox ESR 31 or Firefox ESR 38 to browse GUI, the following Flash Player is required. - Flash Player 10.3 to earlier than 11 - Flash Player 11.2 Notes of the Server Core option of Windows Server 2008 and Windows Server Server Core mode is not supported., agents Windows Notes of the Minimal Server Interface of Windows Server Minimal Server Interface is not supported., Windows 2016 Hitachi, Ltd. All rights reserved. 32