NetIQ AppManager for Hardware Readme
 

AppManager for Hardware

Version 8.0.209.0

Readme

Date Published: April 2013
 

 

What's New?

System Requirements

Contents of the Download Package

Installing This Module

Known Issues

Third-Party Software

Contact Information

Legal Notice

 

 

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. 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.

You can post feedback in the AppManager forum on Qmunity, our community Web site that also includes product notifications, blogs, and product user groups.

For more information about this release and for the latest management guide, see the AppManager Documentation page. To download this module and view the latest release notes, see the AppManager Module Upgrades & Trials page.

What's New?

This initial release of AppManager for Hardware includes 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 includes 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.

Return to Top

System Requirements

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:

For more information, see the AppManager for Hardware Management Guide, included in the download package.

Return to Top

Contents of the Download Package

AppManager for Hardware includes a managed object, qHardwareMOa.dll, and Knowledge Scripts to discover and monitor Hardware resources. The download package includes this Readme, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

  • AM70-Hardware-8.0.209.0.msi, the module installer.
  • AM70-Hardware-8.0.209.0.ini, a configuration file used with the AppManager setup program.
  • AM70-Hardware-8.0.209.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.0.209.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.

Return to Top

Installing This Module

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 and the case-sensitive QDB name.

Install Knowledge Scripts only once per QDB. The module installer installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder.

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.

Return to Top

Known Issues

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.

  • 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; 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 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)

Return to Top

Third-Party Software

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.

Return to Top

Contact Information

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 page.

For general corporate and product information, see the NetIQ Corporate Web site.

For interactive conversations with your peers and NetIQ Corporation experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.

Return to Top

Legal Notice

THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.

For purposes of clarity, any module, adapter or other similar material ("Module") is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.

This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.

This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.

U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.

© 2013 NetIQ Corporation and its affiliates. All Rights Reserved.

For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.

Return to Top