AppManager for Hardware allows you to use a single set of Knowledge Scripts to monitor the hardware resources on VMware ESX or ESXi servers running on Cisco UCS, Dell, HP, or IBM systems. Also includes a set of Knowledge Scripts to monitor the storage environments of NetApp EMC, HP, and Dell.
AppManager for Hardware enables you to monitor server availability. In addition to providing support and optimizing performance, the module ensures availability of hardware resources through automated event detection and collects data for analysis.
This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials web site.
This release provides the following enhancements:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Hardware provides support for TLS 1.2.
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the Upgrading Knowledge Script Jobs
section in the management guide.
This release of AppManager for Hardware replaces all Previous Releases.
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Hardware has the following system requirements:
|
Software |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computer, on all proxy agent computers, and on all console computers |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later One of the following AppManager agents are required:
|
|
Microsoft Windows operating system on the proxy agent computers |
One of the following:
|
|
AppManager for Microsoft Windows module installed on the repository, proxy agent, and console computers |
Support for Windows Server 2008 R2 on AppManager 7.x requires the AppManager for Windows module, version 7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials page. |
|
VMware hypervisor and the software required for monitoring the hardware resources on the hypervisor |
One of the following:
|
|
SMI-S Providers for EMC, NetApp, HP (MSA and 3PAR), and Dell (MDI) storages |
EMC SMI-S Provider version 4.6 and later. NetApp Data ONTAP SMI-S Agent 5.1 and later. HP 3PAR SMI-S Provider version 2.9 HP MSA SNIA SMI-S Provider version 1.5.0 Dell SMI-S Provider version 10.30 |
|
Microsoft Visual C++ Redistributable Package installed on all computers where you plan to install the module |
Microsoft Visual C++ 2008 Service Pack 1 (32-bit) NOTE:The module installer automatically installs the package. |
|
CIMOM(CIM Server) |
Ensure that the CIM Server is running on the ESX or ESXi server. By default, the CIM Server is configured to run on port 5989. |
|
CIMOM(CIM Servers in SAN/NAS environments) |
Ensure that the CIM Server is running where it is hosted. By default, the CIM Server is configured to run on ports 5988 (unsecured connection) and 5989 (secured connection) for EMC, NetApp, HP (MSA and 3PAR), and Dell (MDI). |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
For more information, see the AppManager for Hardware Management Guide, included in the download package.
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for Hardware includes a managed object, qHardwareMOa.dll, and Knowledge Scripts to discover and monitor Hardware resources. The download package includes this Release Notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-Hardware-8.2.52.0.msi, the module installer.
AM70-Hardware-8.2.52.0.ini, a configuration file used with the AppManager setup program.
AM70-Hardware-8.2.52.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-Hardware-8.2.52.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
DefaultRule_Hardware.xml, a configuration file used for deploying the module with Control Center.
ckHardware.exe, the pre-installation check used with the AppManager setup program.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On all proxy agent computers to install the agent components
On all console computers to install the Help and console extensions
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install these components into local or remote QDBs. When installing to the primary QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
IMPORTANT:If you use Control Center 7.x, run the module installer for each QDB attached to Control Center. If you use Control Center 8.x or later, run the module installer only for the primary QDB, and Control Center will automatically replicate this module to secondary QDBs.
Install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
Run the module installer for each QDB attached to Control Center.
For more information about installing this module, see the AppManager for Hardware Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
ReadMisses and WriteMisses values are negative for few HP MSA storage arrays. If you run the LogicalDiskIO Knowledge Script on HP MSA storage, the values of ReadMisses and WriteMisses appear in negative in the graph data for few HP MSA storage arrays. (ENG341664)
Data legend gets truncated if its length exceeds 128 characters. In the AppManager console, the data legend of a data source gets truncated if the string length exceeds 128 characters. But the Analysis Center reporting console displays the data legends properly irrespective of string length. (ENG342029)
Discovering hardware resources on certain ESXi 5.x IBM systems discovers some of the memory devices more than once. If you run the Discovery_Hardware Knowledge Script on certain ESXi 5.x IBM systems, such as ESXi 5.x IBM x3850 M2, some of the memory devices might get discovered more than once. Consequently, the TreeView pane of the Operator Console or the View pane of the Control Center console displays the same memory device multiple times. However, this does not affect the event generation or data collection jobs, because the MemoryHealth Knowledge Script runs only on the actual instance of the discovered memory device and ignores all the duplicated instances of the same memory device. (ENG317033 and DOC320666)
NOTE:Running the Discovery_Hardware Knowledge Script on certain ESXi 5.x IBM systems, such as ESXi 5.x IBM x3850 M2, that do not have voltage devices raises a warning event that the discovery is incomplete. Ignore this event.
Discovering hardware resources on a IBM HS23 blade server running on ESXi 5.5 generates a partial discovery event. If you run the Discovery_Hardware Knowledge Script on IBM HS23 blade server running on ESXi 5, a partial discovery event is generated for fan and temperature objects because the CIM classes are not available for these resources. (DOC338341)
Discovering hardware resources on a Cisco UCS B-Series Blade server generates a partial or incomplete discovery event. If you run the Discovery_Hardware Knowledge Script on a Cisco UCS B-Series Blade server, a partial or incomplete discovery event is generated even though all the existing hardware resources on the server are discovered. This is because the discovery process attempts to discover fans that are not available on the Cisco UCS B-Series Blade server. (DOC327584)
Discovering hardware resources on a ESXi 4.1 HP system discovers the storage box devices more than once. If you run the Discovery_Hardware Knowledge Script on a ESXi 4.1 HP system, the storage devices might get discovered more than once. Consequently, the TreeView pane of the Operator Console or the View pane of the Control Center console displays the same storage box device multiple times. However, this does not affect the event generation or data collection jobs, because the StorageBoxHealth Knowledge Script runs only on the actual instance of the discovered storage box device and ignores all the duplicated instances of the same storage box device. (DOC323920)
Running the VoltageHealth Knowledge Script on a ESXi 4.1 IBM system might generate a not available event. When you run the VoltageHealth Knowledge Script on a ESXi 4.1 IBM system, such as ESXi 4.1 IBM x3650, a not available event might get generated during the first iteration of the job if the status of the device is not yet available. However, appropriate events get generated in the subsequent iterations of the job. (DOC323726)
Running theTemperatureHealth Knowledge Script on a Dell, IBM, or Cisco UCS server displays incorrect values for the temperature sensor. When you run the TemperatureHealth Knowledge Script on a Dell, IBM, or Cisco UCS server, the temperature sensor values displayed in the Control Center console do not match the values displayed in the server administrator tool. (ENG305726)
This release of AppManager for Hardware provided the following enhancements:
Support for VMware vSphere Hypervisor (ESXi) 6.0. This release supports VMware vSphere Hypervisor (ESXi) 6.0.
Support for HP 3PAR and HP MSA storages. This release supports HP 3PAR and HP MSA storages.
Support for Dell MDI storage. This release supports Dell MDI storage.
Support for Microsoft Windows Server 2012 R2. This release supports Windows Server 2012 R2.
This release of AppManager for Hardware provided the following Knowledge Scripts for monitoring storages in NetApp and EMC environments:
LogicalDiskDataTransfer: Monitors the array logical disk or Flex volumes for total, read, and write transfers per second. This script raises an event if this job fails to fetch metrics for monitored logical disks or Flex volumes and if the threshold exceeds for read, write, or total data transfer.
LogicalDiskIO: Monitors the array logical disk or Flex volumes for total diskIO, read/write count, read/write hits if read/write hit operations succeed to perform on the logical disk cache, and read/write misses if read/write miss operations fail to perform on the logical disk cache. This script raises an event if this job fails to fetch IO metrics for monitored logical disks and if the threshold exceeds for any of the metrics.
LogicalDiskResponseTime: Monitors the array logical disks or Flex volumes for response time, wait time, IO rate, and queue depth. This script raises an event if this job fails to get the metrics on response time. This script also raises an event if the threshold exceeds for response rate, IO rate, wait time, or queue depth.
LogicalDiskUtilization: Monitors the space utilization of Flex volumes and LUNs in NAS environments. This script raise events for conditions such as when the job cannot get the logical disk capacity metrics or when the used space per disk exceeds the threshold you set.
PhysicalDiskDataTransfer: Monitors the array physical disks for total transfer, read, and write transfers per second. This script raises an event if this job fails to fetch metrics for monitored physical disks and if the threshold exceeds for read, write, or total data transfer.
PhysicalDiskIO: Monitors the array physical disks for total disk IO and read/write count. This script raises an event if this job fails to fetch IO metrics for monitored physical disks and if the threshold exceeds for any of the metrics.
PhysicalDiskResponseTime: Monitors the array physical disks for response time, IO rate, wait time, and queue depth. This script raises an event if this job fails to get the metrics on response time. This script also raises an event if the threshold exceeds for response rate, IO rate, wait time, or the queue depth.
StorageArrayUtilization: Monitors the space utilization of physical disks in an array. This script raise event for conditions such as when the job cannot get the physical disk array capacity metrics of when the used space in an array exceeds the threshold you set.
This release also resolved the following issue:
Discovery_Hardware Knowledge Script takes longer time to discover resources. If you run the Discovery_Hardware Knowledge Script on an ESXi host, the script took a longer time to discover the resources and the job run time increased if additional hosts are included. With this release, a thread specific process is introduced that improves the job run time considerably. (ENG328930)
This initial release of AppManager for Hardware included the following features and benefits:
Monitors hardware resources from multiple vendors using a single set of Knowledge Scripts.
Monitors multiple servers with a single set of credentials.
Allows you to choose the hardware resources to monitor on specific servers to simplify monitoring.
Remotely monitors hardware resources through proxy agents, and monitors multiple servers with different versions of the hardware monitoring agent for that vendor.
Automatically determines the hardware vendor during the discovery process.
This release included the following Knowledge Scripts:
Discovery_Hardware: Discovers hardware resources.
BatteryHealth: Monitors the operational status of system batteries.
FanHealth: Monitors the operational status of system fans.
LogicalDriveHealth: Monitors the operational status of system logical drives in an array.
MemoryHealth: Monitors the operational status of system memory
NICHealth: Monitors the operational status of system network interface controllers (NICs).
PhysicalDriveHealth: Monitors the operational status of system physical drives in an array.
PowerSupplyHealth: Monitors the operational status of system power supplies.
ProcessorHealth: Monitors the operational status of system CPUs.
SmartArrayControllerHealth: Monitors the operational status of Smart Array controllers.
StorageBoxHealth: Monitors the operational status of storage boxes.
TemperatureHealth: Monitors the operational status of system temperature.
VoltageHealth: Monitors voltage levels on the system board.
NetIQ AppManager for Hardware software, as well as any and all Adapters, modules, updates, modifications thereto ("Software"), is distributed with certain Third Party Software and Open Source Software (as defined in the License Agreement provided with the Software).
The following Third Party and Open Source Software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable EULA. No further licenses are granted.
XMLCC Copyright © 2012 NetIQ Corporation
Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
OpenPegasus
Licensed to The Open Group (TOG) under one or more contributor license agreements. Refer to the OpenPegasusNOTICE.txt file distributed with this work for additional information regarding copyright ownership {See Copyright Notice Below}.
Each contributor licenses this file to you under the OpenPegasus Open Source License; you may not use this file except in compliance with the License.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"),to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
{Copyright Notice}
Pegasus is subject to one or more of the following copyrights:
Copyright (c) 2000, 2004 BMC Software.
Copyright (c) 2003, 2008 EMC Corporation.
Copyright (c) 2000-2009 Hewlett-Packard Development Company, L.P.
Copyright (c) 2000, 2008 IBM Corp.
Copyright (c) 2005, 2008 Inova Development Inc.
Copyright (c) 2000, 2003 Michael Day.
Copyright (c) 2008 Novell.
Copyright (c) 2006, 2007 Symantec Corporation.
Copyright (c) 2000-2008 The Open Group.
Copyright (c) 2000, 2002 Tivoli Systems.
Copyright (c) 2004, 2005 VERITAS Software Corporation.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
© 2018 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.