SIM Install

HP Systems Insight ManagerInstallation and User Guide

Manufacturing Part Number: 5990-7221

February 2004, Edition 1.1

United States

©Copyright 2004 Hewlett-Packard Development Company, L.P

Legal NoticesThe information in this document is subject to change without notice.

Hewlett-Packard makes no warranty of any kind with regard to this manual, including, but not limited to, the impliedwarranties of merchantability and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errorscontained herein or direct, indirect, special, incidental, or consequential damages in connection with the furnishing,performance, or use of this material.

WarrantyA copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtainedfrom your local Sales and Service Office.

U.S. Government LicenseProprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for CommercialItems are licensed to the U.S. Government under vendor's standard commercial license.

Copyright Notices©Copyright 1983-2003 Hewlett-Packard Development Company, L.P. All rights reserved. Reproduction, adaptation, ortranslation of this document without prior written permission is prohibited, except as allowed under copyright laws.

Trademark NoticesIntel® and Itanium® are registered trademarks of Intel Corporation in the US and other countries and are used underlicense.

MS-DOS®, Microsoft®, and Windows® are registered trademarks of Microsoft Corporation in the United States of Americaand in other countries.

UNIX® is a registered trademark of The Open Group.

HP-UX Release 10.20 and later and HP-UX Release 11.00 and later (in both 32 and 64-bit configurations) on all HP 9000computers are Open Group UNIX 95 branded products.

Java� is a US trademark of Sun Microsystems, Inc.

Publication HistoryThe manual publication date and part number indicate its current edition. The publication date will change when a newedition is released. The manual part number will change when extensive changes are made.

To ensure that you receive the latest edition, you should subscribe to the appropriate product support service. See your HPsales representative for details.

Please direct comments regarding this guide to:

Hewlett-Packard CompanyHP-UX Learning Products3404 East Harmony RoadFort Collins, Colorado 80528-9599

Or, use this web form to send us feedback:

http://docs.hp.com/assistance/feedback.html

Typographic ConventionsWe use the following typographical conventions.

http://docs.hp.com/assistance/feedback.html

audit(5) HP-UX manpage. audit is the name and 5 is the section in the HP-UX Reference. On the web and on theInstant Information DVD, it may be a hot link to the manpage itself. From the HP-UX command line, youcan enter “man audit” or “man 5 audit” to view the manpage. See man(1).

Book Title Title of a book. On the web and on the Instant Information DVD, it may be a hot link to the book itself.

Command Command name or qualified command phrase.

ComputerOut Text displayed by the computer.

Emphasis Text that is emphasized.

Emphasis Text that is strongly emphasized.

KeyCap Name of a keyboard key. Note that Return and Enter both refer to the same key.

Term Defined use of an important word or phrase.

UserInput Commands and other text that you type.

Variable Name of a variable that you may replace in a command or function or information in a display thatrepresents several possible values.

[ ] Contents are optional in formats and command descriptions. If the contents are a list separated by |,you must choose one of the items.

{ } Contents are required in formats and command descriptions. If the contents are a list separated by |,you must choose one of the items.

... Preceding element may be repeated an arbitrary number of times.

| Separates items in a list of choices.

Table of Contents1. Product Overview ....................................................................................................... 1

Introduction ............................................................................................................ 1What's New .......................................................................................................... 2

New Features for Insight Manager 7 Users ........................................................ 2New Features for Servicecontrol Manager 3.0 Users ........................................... 3

Product Architecture ................................................................................................ 3Central Management Server ............................................................................. 4Managed Systems .......................................................................................... 4

System Lists ........................................................................................... 5System Groups ...................................................................................... 5

Network Clients .............................................................................................. 5Authorizations ........................................................................................................ 5

Default Toolboxes ........................................................................................... 6User Privileges ................................................................................................ 7

Tools ..................................................................................................................... 7Information Storage ................................................................................................ 8

HP Systems Insight Manager Audit Log .............................................................. 8Database ....................................................................................................... 8

Database Software .................................................................................. 9Secure Access ........................................................................................................ 9

Command Line Interface .................................................................................. 9Graphical User Interface .................................................................................. 9

Secure Data Transmission ...................................................................................... 10Management Protocols .................................................................................. 10Web Server Security .................................................................................... 12Self-Signed Certificates ................................................................................. 12X Application Security ................................................................................... 12Managing Servers Behind a Firewall .............................................................. 12

2. Install Overview and Requirements ............................................................................. 13Process Overview ................................................................................................. 13System Requirements ............................................................................................. 14

Central Management Server Requirements ....................................................... 14HP-UX Central Management Server ......................................................... 14Linux Central Management Server ........................................................... 15Windows Central Management Server .................................................... 15

Managed System Requirements and Recommendations ..................................... 16Network Client Requirements and Recommendations ......................................... 18

SSH Requirements ................................................................................................. 193. Install on HP-UX ........................................................................................................ 20

Optimize the Operating Environment (Kernel Tuning) ................................................ 20Prepare the System ............................................................................................... 21Install and Configure the Software .......................................................................... 21Next Steps ........................................................................................................... 23Remove the Software ............................................................................................. 23

4. Install on Linux ......................................................................................................... 25Prepare the System ............................................................................................... 25Install and Configure the Software .......................................................................... 28Next Steps ........................................................................................................... 30Remove the Software ............................................................................................. 31

5. Install on Windows ................................................................................................... 33Prepare the System ............................................................................................... 33

iv

Install and Configure the Software .......................................................................... 33Next Steps ........................................................................................................... 35Removing the Software .......................................................................................... 35

6. Use the Graphical User Interface ................................................................................ 36Access the GUI ..................................................................................................... 36

Required Java Plug-in .................................................................................... 36Graphical User Interface Features ........................................................................... 37Default Home Page Features .................................................................................. 38Customize the GUI ................................................................................................ 39

Customize Home .......................................................................................... 39Customize the Banner .................................................................................... 39

7. Use the Command Line Interface ................................................................................ 41Log in to the CLI ................................................................................................... 41

Directly on the CMS ...................................................................................... 41Remotely Using an SSH Client ........................................................................ 41

HP Systems Insight Manager Commands ................................................................. 428. Initial Setup ............................................................................................................. 45

Introduction to the Initial Setup ............................................................................... 45Set Up Managed Systems ...................................................................................... 45

Set Up HP-UX Managed Systems .................................................................... 45Set Up Linux Managed Systems ...................................................................... 47Set Up Windows Managed Systems ................................................................ 48

Configure Protocol Settings .................................................................................... 50Configure and Execute Discovery: Automatic or Manual ............................................ 51

Configure and Execute Automatic Discovery .................................................... 51Configure and Execute Manual Discovery ........................................................ 53

Add Users ........................................................................................................... 53Configure Email Settings ........................................................................................ 55Configure Paging Settings ...................................................................................... 55Set Up Automatic Event Handling ........................................................................... 55Add Toolboxes ..................................................................................................... 57Add Authorizations ............................................................................................... 58

9. Configuration Options .............................................................................................. 59CPU Utilization During Data Collection .................................................................... 59

Overview ..................................................................................................... 59Implementation ............................................................................................. 60

GUI Time-Out Policy .............................................................................................. 60Overview ..................................................................................................... 60Implementation ............................................................................................. 60

HP Systems Insight Manager Audit Log Configuration ............................................... 61Overview ..................................................................................................... 61Implementation ............................................................................................. 61

Lifetimes for Entries on the Task Results Page ............................................................ 63Overview ..................................................................................................... 63Implementation ............................................................................................. 64

Glossary ..................................................................................................................... 65Index .......................................................................................................................... 80

v

HP Systems Insight ManagerInstallation and User Guide

Chapter 1. Product OverviewHP Systems Insight Manager combines the strengths of Insight Manager 7, HP Toptools, and HPServicecontrol Manager to deliver a single tool for managing HP ProLiant, Integrity, and HP 9000systems running Microsoft® Windows®, Linux®, and HP-UX. The core HP Systems Insight Managersoftware delivers the essential capabilities required to manage all HP server platforms.

HP Systems Insight Manager can be extended to provide system management with plug-ins for HPclients, storage, power, and printer products. Plug-in applications for rapid deployment, performancemanagement, partition management, and workload management enable you to pick the valueadded software required to deliver complete lifecycle management for your hardware assets.

IntroductionHP Systems Insight Manager provides the following features:

● Easy and rapid installation. Installs on your server platform of choice running HP-UXor Windows.

● Automatic discovery and identification. Automatically discovers and identifies systemsattached to the network. Use Discovery Filters to prevent discovery of unwanted system types.Manual discovery options are also available.

● Fault management and event handling. Provides proactive notification of actualor impending component failure alerts. Automatic Event Handling enables users to configurepolicies to notify appropriate users of failures through e-mail, pager, or short message service(SMS) gateway. It also enables automatic execution of scripts or event forwarding to enterpriseplatforms such as HP OpenView Network Node Manager or HP OpenView Operations.

● Consistent multi-system management. Initiates a task on multiple systems or nodesfrom a single command on the central management server (CMS). This functionality eliminatesthe need for tedious, one-at-a-time operations on each system. The integration of single-systemaware tools lets the CMS use them in a multiple-system aware manner, allowing them to executesimultaneously on multiple nodes.

● Secure remote management. Leverages operating system security for user authenticationand Secure Sockets Layer (SSL) and Secure Shell (SSH) to encrypt management communications.

● Role-based security. Enables effective delegation of management responsibilities bygiving systems administrators granular control over which users can perform which managementoperations on which systems.

● Tool definitions. Defines tools using simple XML documents that enable you to integrateoff-the-shelf or custom tools. These tools can be command line tools, Web-based applications,or scripts. Access to these integrated tools is governed by role-based security.

● Data collection and inventory reports. Performs comprehensive system data collectionand enables you to quickly produce detailed inventory reports for managed systems. Reportscan be saved in HTML format or exported to CSV format for easy incorporation into popularreporting packages.

1

● Snapshot comparisons. Enables you to compare configuration snapshots of up to fourdifferent servers or configuration snapshots of a single server over time. This functionally assistsIT staff in pinpointing configuration issues that can contribute to system instability.

● Version control. Automatically downloads the latest BIOS, driver, and agent updates forProLiant servers running Windows and Linux. This feature identifies systems running out-of-datesystems software and enables system software updates across groups of servers.

● Two user interfaces. Provides a Web browser graphical user interface (GUI) andcommand line interface (CLI) to help incorporate HP Systems Insight Manager into your existingmanagement processes.

What's NewHP Systems Insight Manager delivers new capabilities for customers who currently use ServicecontrolManager to manage their HP 9000 and Integrity systems running HP-UX and Linux and those whouse Insight Manager 7 to manage their ProLiant servers running Windows, Linux, and NetWare.New features differ depending on whether you use Servicecontrol Manager or Insight Manager7.

New Features for Insight Manager 7 UsersHP Systems Insight Manager provides the following added functionality over Insight Manager 7:

● Ability to install the central management server (CMS) on HP-UX and Linux

● Management of HP 9000 and Integrity servers running HP-UX

● Support for the Mozilla Web browser on Linux and HP-UX

● Role-based security that provides granular control over which users can select which actions toperform on which systems and enables effective delegation of management responsibility withoutallowing unauthorized access to managed systems

● Ability to execute initial deployment of ProLiant Support Packs to Windows systems without theHP Version Control Agent and support for Version Control Agent of Linux systems

● Improved breadth of management through integration with the HP Client Manager, HP WebJetAdmin, HP CommandView for SDM, EVA, XP, and ESL storage, and the HP Power Manager

● Improved lifecycle management through integration with the ProLiant Essential Rapid DeploymentPack, ProLiant Essentials Performance Management Pack, Remote Insight Lights-Out Edition(RILOE), Integrated Lights-Out (iLO), Ignite UX, Software Distributor-UX, Process ResourceManager, Partition Manager, HP-UX Workload Management, GlancePlus, Security Patch Check,Bastille, Service Guard Manager, and HP-UX system administration (for example, kernelconfiguration and user/group configuration)

● Command line interface (CLI)and the ability to easily integrate off-the-shelf or custom commandline and browser-based applications through Tool Definition Files

● Ability to securely run tools on managed systems.

2

Product Overview

New Features for Servicecontrol Manager 3.0 UsersHP Systems Insight Manager provides the following added functionality over Servicecontrol Manager3.0:

● Ability to install the CMS on Windows

● Management of ProLiant servers running Windows, Linux, and NetWare and AlphaServersrunning Tru64 UNIX® and OpenVMS

● Automatic discovery and identification

● System polling

● Integrated inventory and snapshot comparison using integrated HP Systems Insight Managerfunctionality

● Improved breadth of management through integration with HP Client Manager, HP WebJetAdmin, HP CommandView for SDM, EVA, XP, and ESL storage, and HP Power Manager

● Improved lifecycle management through integration with Ignite-UX, Software Distributor-UX,Process Resource Manager, Partition Manager, HP-UX Workload Management, GlancePlus,Security Patch Check, Bastille, ServiceGuard Manager, HP-UX system administration (for example,kernel configuration and user/group configuration), the ProLiant Essentials Rapid DeploymentPack, ProLiant Essentials Performance Management Pack, RILOE, and iLO

Product ArchitectureHP Systems Insight Manager leverages a distributed architecture that can be broken into threetypes of systems:

● Central Management Server● Managed Systems● Network Clients

The central management server (CMS) and the managed systems together are called the HP SystemsInsight Manager management domain.

3

Product Overview

Management Domain

Windows

Linux

Windows

Windows

LinuxHP-UX

HP-UX

ManagedSystem

ManagedSystem

ManagedSystem

ManagedSystem

System Group

ManagedSystem Managed

System ManagedSystem

CentralManagement

Server

Central Management ServerEach management domain has a single CMS. The CMS is the system in the management domainthat executes the HP Systems Insight Manager software and initiates all central operations withinthe domain. In addition to the HP Systems Insight Manager software, the CMS maintains a databasefor storage of persistent objects. If you are using a Windows CMS, this database can reside on aseparate system. Typically, servers for the multiple-system aware applications also reside on theCMS. These applications are not required to reside on the CMS; they can reside anywhere on thenetwork.

Because the CMS is a system within the management domain, it manages itself as part of thedomain. You can add the CMS as a managed system within another management domain if youwant to manage it using a separate CMS.

Managed SystemsSystems that make up a management domain are called managed systems. A system can be anydevice on the network that can communicate with HP Systems Insight Manager, which includesservers, desktops, laptops, printers, workstations, hubs, and routers. In most cases, these deviceshave an IP address or a Macintosh address associated with them. A managed system can bemanaged by more than one CMS if desired.

Each system must be running a management agent. Managed systems can have a variety ofmanagement agents installed. These agents perform tasks, monitor software, and monitor hardwareon the managed systems.

4

Product Overview

System ListsSystem lists provide a way to search the HP Systems Insight Manager database for systems thatshare common attributes, such as operating system type or hardware type. System lists can alsobe an arbitrary collection of systems. Systems can belong to one or more system lists. Many standardsystem lists are provided, and users can create their own public and private lists. Working withsystem lists increases your efficiency because you can perform a task on each system in a systemlist with a single task.

System GroupsSystem groups can be used to divide and organize your management domain into manageableunits for authorizations. Working with system groups increases your efficiency because you canset authorizations for each system in a system group in a single step. Systems can belong to oneor more system groups.

Network ClientsHP Systems Insight Manager can be accessed from any network client. The network client can bepart of the management domain. The network clients must be running a compatible browser toaccess the graphical user interface (GUI) or an SSH client application to securely access thecommand line interface (CLI).

Note

Access to the Web server on the CMS can be restricted to specific IP address rangesfor specific users.

System GroupNetwork Client

Central Management Server

TomcatWeb Server

ManagedSystem

Remote Login

Command Shell

SSHClient

WebBrowser

HP SystemsInsight

Manager

ManagedSystems

ManagedSystem

AuthorizationsAn HP Systems Insight Manager user must have a valid operating system login on the CMS. Oncea user is added to HP Systems Insight Manager, then he or she can be authorized to use a toolboxon one or more systems in the management domain.

5

Product Overview

Each toolbox is associated with a set of tools that a user might need for a particular task, such asdatabase administration or software management. Authorizing a user for a toolbox on a systemor system group enables the user to run the associated set of tools on that system or systems thatare members of the system group.

AUTHORIZATIONS =

++User Toolbox System orSystem Group

Important

Authorization for a toolbox may enable users with non-privileged users (i.e. non-rootusers or users that are not a member of the Windows Administrators group) to runtools as root/Administrator or as another specified user. Be careful when grantingusers permission to run tools as root or Administrator. Take into consideration allthe capabilities given by a tool, above and beyond the capabilities it is designedfor, before you associate it with a toolbox.

Default ToolboxesThe All Tools toolbox is a default toolbox installed with HP Systems Insight Manager. The All Toolstoolbox provides complete access to all tools for the authorized system or system group. When atool is added to HP Systems Insight Manager, the tool is automatically added to this toolbox. Toolscannot be removed from the All Tools toolbox, and the All Tool toolbox cannot be deleted fromHP Systems Insight Manager. If you don't want a user to have access to all available tools for aspecific system or system group, they should not be authorized for the All Tools toolbox on thatsystem or system group.

Caution

A user assigned the All Tools toolbox on the CMS can execute commands as anyuser. Therefore, this user could grant the full configuration rights user privilege tohimself.

Another default toolbox is the Monitor Tools toolbox. This toolbox contains tools that display thestate of managed systems, but not tools that change the state of managed systems.

HP Systems Insight Manager can have up to 32 defined toolboxes including the default toolboxes.All toolboxes other than All Tools and Monitor Tools can be enabled, disabled, or deleted.

6

Product Overview

User PrivilegesFull configuration rights user. Full configuration rights users have been given specialprivileges to administer the HP Systems Insight Manager software. Full-rights users manage:

● authorizations● systems● system groups● users● toolboxes● tools

In addition, full-rights users maintain and backup the database and monitor the HP Systems InsightManager audit log.

By default, root on a HP-UX or Linux CMS or the administrative account used to install HP SystemsInsight Manager on a Windows CMS is assigned the full configuration rights user privilege, butthis can later be revoked. This user is also automatically authorized for the All Tools toolbox on allsystems including the CMS. The full configuration rights user privilege can be given to one or moreusers, and HP Systems Insight Manager requires that at least one user is a full configuration rightsuser.

Limited configuration rights user. Limited configuration rights users have limited capabilityto configure the CMS. They have permission to create, modify, and delete all reports and theirown tools.

No configuration rights user. No configuration rights users cannot configure the CMS.Their ability to manage systems are based on their authorizations.

ToolsTools are applications, commands, or scripts that are launched from within HP Systems InsightManager. You can add custom tools into HP Systems Insight Manager and execute them acrossmultiple systems simultaneously. There are three types of tools supported in the HP Systems InsightManager environment: Web tools, X Window tools, and command line tools.

Web tools must reside on a Web server. TheWeb server can be running on the CMS or ona managed system. HP Systems Insight Managerlaunches the URL from a command line or fromthe graphical user interface. When a Web toolis launched from the command line, HP SystemsInsight Manager opens a browser to display thetool. When a Web tool is launched from the HPSystems Insight Manager graphical userinterface, it is opened in the workspace or in aseparate browser window.

Web tools

7

Product Overview

X Window tools require that an X server isrunning. These tools can reside on the CMS oron a managed system. When accessing HPSystems Insight Manager from a network client,you must have X server software running on thenetwork client to execute an X Window tool.From the command line or the graphical userinterface, HP Systems Insight Manager invokesthe X Window application using the commandline and passes the location of the X server byrequesting the device for display from the user.

X Window tools

Command line tools include applications,commands, and scripts. They can reside on theCMS or on another managed system. They canbe launched directly from the command line orfrom the graphical user interface.

Command line tools

Information StorageHP Systems Insight Manager uses an audit log and a database to track activity and store yourmanagement domain information.

HP Systems Insight Manager Audit LogHP Systems Insight Manager logs all tasks performed by all HP Systems Insight Manager users onall systems. The information is stored in the audit log on the CMS. HP Systems Insight Managerlogs all tasks with the following information:

● time stamp● user name● systems● event● tool result

For command tools, the verbose level of stdout and stderr is frequently large and time sensitive,so it is only logged by default for the ps command. The option to log this output for the ps andfor other commands is configurable. In addition, other aspects of the audit log, such as maximumfile size, is also configurable. Information about configuring the audit log is available in Chapter 9,Configuration Options and in the Administering the Software section of the HP Systems InsightManager on-line help.

DatabaseHP Systems Insight Manager uses a database to store vital management domain information. Thedatabase contains information about:

● authorizations● systems● system lists● system group definitions● users● passwords

8

Product Overview

● toolbox definitions● tool definitions● events● inventory data

Database SoftwareHP Systems Insight Manager supports the use of several databases:

● An HP-UX or Linux CMS uses PostgreSQL.

● A Windows CMS uses Microsoft SQL Server Desktop Engine (MSDE) or Microsoft SQL 2000.HP Systems Insight Manager ships with MSDE, but you can choose to use Microsoft SQL 2000which provides more advanced enterprise features.

Secure AccessHP Systems Insight Manager utilizes several technologies to provide secure access. You can accessHP Systems Insight Manager via the command line or a Web browser. Both of these user interfacescan be accessed from anywhere on your network.

Command Line InterfaceWhen you access HP Systems Insight Manager from the command line interface, your operatingsystem login is used to identify you to HP Systems Insight Manager. You have access to use the HPSystems Insight Manager commands based on your authorizations. If you access HP Systems InsightManager from any system other than the CMS, make sure you use an SSH client. Programs liketelnet, rlogin, and ftp do not provide encrypted access. When you use one of these applicationsto access HP Systems Insight Manager, your data including your password is transmitted acrossthe network unencrypted. In addition, these protocols are not spoof-protected. If you have a WindowsCMS, then only administrators have command line access to HP Systems Insight Manager. A RemoteDesktop Connection to the CMS may be used to access the command line.

Graphical User InterfaceWhen you access the HP Systems Insight Manager from a Web browser, you log on using thesecure HTML login page. The user name and password for the login page are the same as yourCMS operating system user name and password. A Windows CMS also requires a domain name.Your information is securely transmitted using the SSL protocol. SSL provides data encryption andserver authentication by using a public and private key technology. The Web server on the CMSuses a certificate for server authentication. By default, this certificate is self-signed, but it may bereplaced by a certificate that is signed by a trusted certificate authority. Your web browser shouldimport this certificate to trust the CMS.

9

Product Overview

Network Client Central Management Server

SSH

TomcatWeb Server

HTTPSWeb Browser

SSH Client

SSH

DMI

SNMP

WBEM

HP-UXManaged System

SSH

SNMP

WBEM

LINUXManaged System

SSH

ProLiant Support Pack

SNMP

WMI

WindowsManaged System

HP SystemsInsight

Manager

SSH

DMI

SNMP

WBEM

SSH

SNM

P

WBE

M

HTT

PS

ProLiant Support Pack

Secure Data TransmissionThe security of the transaction depends on your networking environment and on the managementprotocol that each tool is using.

Management ProtocolsThe basic supported management protocols and applications are SSH, WBEM, HTTPS, DMI, andSNMP. Tools are not limited to these protocols, and they can provide a custom managementprotocol. SSH is the only protocol that must be installed on every managed system. Tools requirespecific protocols, and they can only be run on a managed node if the protocol they require isinstalled and configured correctly.

Secure Shell (SSH) . SSH is a program that enables you to log into another system over anetwork and execute commands on that system. It also enables you to move files from one systemto another, and it provides authentication and secure communications over insecure channels. SSHuses a public/private key pair to provide a secure mechanism to authenticate and encryptcommunication. SSH keys are used to identify the execute-as user on the managed system. Typicallythe execute-as user is either root or Administrator, but other users may be configured dependingon the tool that will be executed on the managed system. The private key is kept secure on theCMS, while the public key is installed on each managed node.

The SSH-2 protocol is used by the Distributed Task Facility (DTF) to communicate with managednodes. The DTF improves operator efficiency by replicating operations across the systems or systemgroups within the management domain using a single command. This reduces the load on

10

Product Overview

administrators in multi-system environments. X Window tools and command line tools use the DTFto execute. The DTF supports:

● Executing scripts, commands, and applications remotely on managed systems● Copying files to managed systems

The DTF connects the CMS to the SSH server software running on each managed system. The DTFtells the SSH server what tasks need to be performed on the system. The SSH server then performsthe tasks and returns the results to the DTF. The DTF consolidates the feedback it receives from allthe managed systems.

Web Based Enterprise Management (WBEM). WBEM is an industry standard thatsimplifies system management. It is based on a set of management and Internet standard technologiesdeveloped to unify the management of enterprise computing environments. It provides access toboth software data and hardware data that is readable by WBEM compliant applications.

HP Systems Insight Manager keeps a database of passwords for managed systems running WBEM.The database contains the user names and passwords for each managed system, which are requiredto provide user authentication for tools using this protocol. These accounts do not need to haveother access capabilities, such as log on rights. They are only used for WBEM access by HP SystemsInsight Manager. The WBEM username and password can be set from the command line or thegraphical user interface. For more information, see the Administering the Software section in theHP Systems Insight Manager on-line help.

HP Systems Insight Manager uses HTTPS to access WBEM data, providing a secure path for systemmanagement data. For access to Windows management data instrumented in WMI, a WMI Mapperrunning on a Windows system converts the HTTPS WBEM requests into WMI requests, which useDCOM and NT security.

Secure HTTP (HTTPS). HTTPS is simply HTTP over SSL, a protocol that supports sending datasecurely over the Web. HTTPS is used to access WBEM data as explained in the previous section,and it is used to access ProLiant agent information. Digital certificates are used instead of usernames and passwords to establish trust between the agent and the CMS. The certificate of the CMSshould be loaded into each agent to be managed by that CMS.

Desktop Management Interface (DMI). DMI is an industry standard protocol, primarilyused in client management, established by the DMTF. DMI provides an efficient means of reportingclient system problems. DMI compliant computers can send status information to a centralmanagement system over a network. DMI is supported for system inventory collection where theinformation is not available from WBEM and SNMP. A Windows CMS uses DMI to gatherinformation from third party servers. An HP-UX CMS uses DMI to gather system information fromother HP-UX systems. DMI is not supported on a Linux CMS. DMI is not a secure protocol. Therefore,anyone with access to your network will be able to intercept and view DMI transactions.

Simple Network Management Protocol (SNMP). SNMP is a set of protocols formanaging complex networks. SNMP works by sending messages, called protocol data units (PDUs),to different parts of a network. SNMP-compliant devices, called agents, store data about themselvesin Management Information Bases (MIBs) and return this data to the SNMP requesters. There aremultiple versions of SNMP. SNMP Versions 1 and 2, used by HP Systems Insight Manager, arenot secure protocols. Therefore, anyone with access to your network will be able to intercept andview SNMP transactions.

HP Systems Insight Manager keeps a database of read and write community names for managedsystems running SNMP. The community name must match those configured on the managementsystem. The SNMP community names and passwords can be set from the command line or the

11

Product Overview

graphical user interface. For more information, see the Administering the Software section in theHP Systems Insight Manager on-line help.

HP Systems Insight Manager does not use SNMP SetRequests. By default, the supported operatingsystem platforms have SNMP SetRequests disabled. For improved security, do not enable SNMPSetRequests on the CMS or on the managed systems. Even SNMP GetRequest responses can bespoofed, so all information from SNMP should be regarded as insecure.

Web Server SecurityHP Systems Insight Manager uses the Tomcat Web server on the CMS. Tomcat features that arenot required by HP Systems Insight Manager are turned off by default. This includes Server SideIncludes and Common Gateway Interface scripts.

Self-Signed CertificatesThe self-signed certificates used for WBEM and Web server authentication make it possible foranother system to impersonate the CMS if the valid certificate is not securely imported into theclient or browser. This is called spoofing. To prevent the possibility of spoofing, use a certificatesigned by a trusted CA (Certificate Authority) or securely export the certificate by browsing locallyto the CMS and then securely importing it into your browser. You can also obtain the servercertificate by browsing remotely and saving it in the browser the first time you access HP SystemsInsight Manager, but this option is less secure and still susceptible to a possible "man-in-the-middle"attack. Information about importing CA-signed certificates is available in the Administering theSoftware section of the HP Systems Insight Manager on-line help.

X Application SecurityThe data exchanged between an X client (or application) running on a managed system and anX server on the network client is transmitted in clear text over the network. X clients are notrecommended in environments where security is a concern.

Managing Servers Behind a FirewallHP Systems Insight Manager supports managing servers that are located behind a firewall whenusing the SSH, HTTP, and WBEM protocols. The SNMP and DMI protocols are not recommendedbecause they are not secure protocols. The firewall must be configured to allow this traffic throughthe firewall. The following ports are used:

● WBEM uses HTTPS over port 5989● Web agents use HTTPS over port 2381● DTF uses SSH-2 over port 22

For a complete list of ports used by HP Systems Insight Manager, see the Understanding HP SystemsInsight Manager Security white paper. This white paper is available athttp://www.hp.com/go/hpsim/.

12

Product Overview

http://www.hp.com/go/hpsim/

Chapter 2. Install Overview andRequirements

This chapter provides an overview of the HP Systems Insight Manager installation process, and itidentifies the system requirements for a CMS, a managed node, and a network client.

Process OverviewThe installation process for HP Systems Insight Manager involves several steps. The following flowdiagram represents the process.

Install and configure the

Central Management Server

Perform initialsetup

Install agents and configure protocols

on a managed system

Setup another managedsystem?

yes

no

Configure and customize HP System

Insight Manager including: discovery,

event handling, users, toolboxes, and authorizations

1. First you need to install and configure the CMS. The procedure to complete this step is in theinstallation chapters of this guide. Follow the appropriate chapter based on the operatingsystem of your CMS. See Chapter 3, Install on HP-UX, Chapter 4, Install on Linux, orChapter 5, Install on Windows for details.

13

2. The second step involves installing and configuring the required management agents on thesystems that will be managed by the CMS. This step is covered in the first section of Chapter 8,Initial Setup.

3. The final step involves configuring HP Systems Insight Manager for your environment. Theremaining sections in Chapter 8, Initial Setup cover these recommended tasks.

System RequirementsThis section identifies the hardware and software requirements and recommendations for HP SystemsInsight Manager. These requirements are broken into sections by system type for the centralmanagement server, managed node, and network client.

Central Management Server RequirementsThis section contains the requirements for the central management server. These requirements aresorted by operating system. Please review the section of requirements that applies to your centralmanagement server.

● the section called “HP-UX Central Management Server”● the section called “Linux Central Management Server”● the section called “Windows Central Management Server”

HP-UX Central Management Server● Operating System

❍ HP-UX 11i v1 (B.11.11), 64-bit installation only

Note: The required patches must be installed for each of these operating systems. See the HPSystems Insight Manager Release Notes for details.

● Hardware

❍ Any HP system with a PA-RISC 2.0 processor

❑ Minimum: A-class system with 1 GB RAM❑ Recommended: rp7410 or higher with 1 GB RAM

● Software

❍ PostgreSQL 7.3.1 or later from HP Internet Express Group❍ OpenSSH❍ WBEM

● Free Disk Space

❍ 256 MB for the CMS and DTF agent (/opt)❍ 500 MB minimum recommended for data (/var/opt)

● Swap Space

14

Install Overview and Requirements

2 GB minimum total swap space for PA-RISC Systems❍

❍ 3 GB minimum total swap space for Itanium-based Systems

● Networking

❍ static or dynamic hostname resolution

Linux Central Management Server● Operating System

❍ Red Hat Enterprise Linux AS 2.1, Update 3❍ Red Hat Enterprise Linux ES 2.1, Update 3❍ Red Hat Enterprise Linux AS 3, Update 1❍ Red Hat Enterprise Linux ES 3, Update 1❍ SuSE Enterprise Server 8

● Hardware

❍ Any HP IA-32 system with:

❑ Minimum: 1.5 GHz processor and 512 MB RAM❑ Recommended: 2.4 GHz processor and 1 GB RAM

Note: HP Netservers are not supported as central management servers, only as managedsystems.

● Software

❍ PostgreSQL 7.3.4 or later❍ OpenSSH

● Free Disk Space

❍ 256 MB for the CMS and DTF agent (/opt)❍ 500 MB minimum recommended for data (/var/opt)

● Swap Space

❍ 3 GB minimum total swap space for Itanium-based Systems

● Networking


Windows Central Management Server● Operating System

15


Microsoft Windows 2000 Server, Service Pack 4❍

❍ Microsoft Windows 2000 Advanced Server, Service Pack 4❍ Microsoft Windows Server 2003, Service Pack 1❍ Microsoft Windows Server 2003 Enterprise Edition, Service Pack 1❍ Microsoft Windows XP Professional

Note: The required Windows Service Packs must be installed for each of these operatingsystems. See the HP Systems Insight Manager Release Notes for details.

● Hardware

❍ Any HP ProLiant IA-32 system with:

❑ Minimum: 1.5 GHz processor with 512 MB RAM❑ Recommended: 2.4 GHz processor with 1 GB RAM

Note: HP Netservers are not supported as central management servers, only as managedsystems.

● Software

❍ MSDE 2000 with SP3 (bundled with HP Systems Insight Manager), or you can use one ofthe following:

❑ Microsoft SQL 2000, Standard Edition with SP3 (for "Standard Server" OS)

❑ Microsoft SQL 2000, Enterprise Edition with SP3 (for "Advanced Server" OS)

Note: Windows XP Pro is not supported with SQL 2000, only MSDE 2000. SQL 2000can be used as a remote database for a CMS on Windows XP Pro.

❍ OpenSSH 3.7.1❍ ProLiant Support Pack 6.30 or later❍ Version Control Repository Manager 2.0.1.30❍ WMI Mapper 1.2

● Free Disk Space

❍ 500 MB recommended

● Networking

❍ static or dynamic hostname resolution❍ TCP/IP

Note: Operating systems with only IPX enabled will not be identified by an HP-UX or Linuxcentral management server.

❍ SNMP (recommended)

Managed System Requirements andRecommendations

This section contains requirements and recommendations for managed systems.

16


● Required Operating Systems

❍ HP-UX 11.0❍ HP-UX 11i v1 (B.11.11)❍ HP-UX 11i v2 (B.11.23)❍ IntraNetWare 4.x❍ IntraNetWare for Small Business❍ Microsoft BackOffice Small Business Server❍ Microsoft Small Business Server 2000❍ Microsoft Windows 2000 Server❍ Microsoft Windows 2000 Advanced Server❍ Microsoft Windows 2000 Professional❍ Microsoft Windows NT Server 4.0❍ Microsoft Windows Server 2003❍ Microsoft Windows Server 2003 Enterprise Edition❍ Microsoft Windows XP Professional❍ Novell NetWare 4❍ Novell NetWare 5.x❍ Novell NetWare 6❍ Novell NetWare Small Business Suite❍ OpenVMS❍ Red Hat Linux 7.3❍ Red Hat Linux 8❍ Red Hat Enterprise Linux AS 2.1 (IA-32 and Itanium-based systems)❍ Red Hat Enterprise Linux AS 3 (IA-32 and Itanium-based systems)❍ SCO OpenServer 5.0x❍ SCO UnixWare 7❍ SuSE Linux 7.0❍ SuSE Linux 7.2❍ SuSE Enterprise Server 8❍ Tru64

Note: Operating systems with only IPX enabled with not be identified by an HP-UX or Linuxcentral management server.

● Required Hardware

❍ For HP-UX:

❑ Any HP PA-RISC system❑ Any HP Itanium-based system

❍ For Linux:

❑ Any HP IA-32 system❑ Any HP Itanium-based system

❍ For Windows:

❑ Any HP IA-32 system

● Recommended Software

17


Note:This software is not required, but if you want improved management capabilities, it isrecommended that you install these components.

❍ For HP-UX:

❑ SSH❑ WBEM

❍ For Linux:

❑ SSH❑ Linux ProLiant Support Pack❑ SNMP (recommended as an alternative to WBEM)

❍ For Windows:

❑ OpenSSH 3.7.1❑ ProLiant Support Pack 6.30 or later❑ WBEM/WMI❑ SNMP (recommended as an alternative to WBEM)

● Required Networking


Network Client Requirements and RecommendationsThis section contains requirements and recommendations for managed systems.

● Required Web Browsers

❍ For HP-UX:

❑ Mozilla 1.4 or later supplied by HP with Java JRE browser plug-in 1.4.0 or later

See the note below about the required security options.

To download, go to http://software.hp.com.

❍ For Linux:

❑ Mozilla 1.5 or later with Java JRE browser plug-in 1.4.2_03 or later

See the notes below about the required security options and the Java plug-in registration.

❍ For Windows:

❑ Internet Explorer 6.0 or later with Java JRE browser plug-in 1.4.1_04 or later

See the note below about the required security options.

Note: For all browsers, you must have the following browser security options enabled forHP Systems Insight Manager to work properly:

18


http://software.hp.com

❑ SSL 3.0 or TLS 1.0❑ Allow cookies

● For Internet Explorer, first party cookies must be accepted● For Mozilla, enable all cookies or enable cookies for the originating web site only

❑ Run ActiveX controls and plug-ins (Internet Explorer only)❑ Script ActiveX controls marked safe for scripting (Internet Explorer only)❑ Active scripting (Internet Explorer only)

Note: To use Mozilla on Linux, you must register the Java plug-in. At a command prompt,execute the following commands:

cd /usr/local/mozilla/plugins

If the libjavaplugin_oji.so file already exists in this directory, rename it:

mv libjavaplugin_oji.so libjavaplugin_oji.so.bak

Change the Java version which exists in the /usr/java path:

ln -s/usr/java/j2re1.4.2_03/plugin/i386/ns610-gcc32/libjavaplugin_oji.so

● Recommended Software

Note:This software is not required, but if you want improved HP Systems Insight Managercapabilities, it is recommended that you install these components which can be purchased ordownloaded from many software suppliers.These components are included with HP-UX.

❍ SSH Client❍ X Window Server

SSH RequirementsSSH is configured during HP Systems Insight Manager installation locally on the central managementserver (CMS). Additional steps to complete the configuration on the CMS may be provided in theHP Systems Insight Manager README. Custom Commands on the Tools menu require SSH onthe CMS in order to run properly. These commands run on the CMS with environment variablesset to the context of specific events or devices. SSH on the CMS is also used by the Initial ProLiantSupport Pack Install on the Deploy->Deploy Drivers, Firmware and Agents menu.

You may optionally install and configure SSH on each of the managed systems and have HPSystems Insight Manager exchange keys with the managed systems (via the mxagentconfigcommand). If you do this, then the Command Line Tools on the Tools menu will work for thesemanaged systems. If you choose not to configure it to work with remote SSH clients, then thesecommands will fail. There is no other loss of functionality without SSH.

19


Chapter 3. Install on HP-UXOptimize the Operating Environment (KernelTuning)

This section provides steps to optimize your HP-UX system prior to installing HP Systems InsightManager.

1. Install the latest recommended HP-UX patches.

Download the HP Systems Insight Manager Release Notes for the latest list of recommendedpatches. To download the Release Notes, go to: http://www.hp.com/go/hpsim

2. Tune the kernel using the Java Out-of-Box file set. For information on this, go to:http://www.hp.com/products1/unix/java/java2/outofbox/index.html. The kernel parametervalues it adjusts are listed in the table below.

Java Out-of-Box Settings

=3000max_thread_proc

=2063835136maxdsize

=2048maxfiles

=2048maxfiles_lim

=512maxusers

=6000ncallout

=4097nfile

=6000nkthread

=2048nproc

=2048tcp_conn_request_max

3. Using HP SAM or the HP-UX Kernel Configuration tool (kcweb), complete the following manualparameter adjustments.

a. Manually set the parameters listed in the table above if you did not use the Java Out-of-Boxfile set to set the parameters.

Note: The tcp_conn_request_max parameter can only be set using the networktuning command, ndd.

b. Increase the nfile parameter to at least 12000. This value may need to be increasedup to 30000 depending on your environment. If you get an error that you can't open afile, you need to increase this value.

c. Set the dbc_max_pct kernel parameter. This is the percentage of physical memory thatcan be dynamically allocated for the Data Buffer Cache. It defaults to 50%, which isusually too high. Set this variable to the percentage of your system's physical memory

20

http://www.hp.com/go/hpsim

http://www.hp.com/products1/unix/java/java2/outofbox/index.html

that equals approximately 200 MB. For example, a server with 1 GB of RAM should havethis value set at 20%.

Note: This value cannot be less than dbc_min_pct, which cannot be less than 1%.

Prepare the SystemThis procedure verifies that your system meets the minimum requirements and prepares your systemfor installation.

Note

This release of HP Systems Insight Manager does not support upgrading from HPServicecontrol Manager. Therefore, it is recommended to install this software on asystem that is not your HP Servicecontrol Manager central management server or towait for the next version of HP Systems Insight Manager, which will provide amigration tool.

To verify and prepare your system:

1. Verify your system meets the minimum requirements. See the section called “SystemRequirements” for details.

2. Verify that HP Servicecontrol Manager is not installed:

swlist -l bundle B8337BA B8339BA B8338BA T1863AA T2414BA

swlist -l product ServControlMgr AgentConfig SysMgmtServerSysMgmtAgent

If any of these are installed, remove them:

swremove ID

where ID is the product or bundle id. For example:

swremove B8339BA

3. Download the software or locate a copy of the software on a depot server.

To download the software, go to http://www.hp.com/go/hpsim, and select Download.

Install and Configure the SoftwareWhen you install HP Systems Insight Manager, you also install the following software dependencies:Java, PostgreSQL, SSH and WBEM. If you downloaded your software from the Web, thesedependency packages are included in the depot file. This procedure also involves configuring SSH,WBEM, SNMP, and DMI to communicate with HP Systems Insight Manager.

To install HP Systems Insight Manager:

21

Install on HP-UX


1. Install Java, PostgreSQL, SSH, and WBEM:

swinstall -s /directory/depot T1458AA ixPostgreSQL T1471AA B8465BA

where directory is the path to the depot file and depot is the name of the depot file. Forexample:

swinstall -s /tmp/HPSIM_download.depot T1458AA ixPostgreSQL T1471AAB8465BA

2. Install HP Systems Insight Manager:

swinstall -s /directory/depot T2414BA

where directory is the path to the depot file and depot is the name of the depot file. Forexample:

swinstall -s /tmp/HPSIM_download.depot T2414BA

3. Test the prerequisites:

/opt/mx/bin/mxinitconfig -l

Note: It is recommended to resolve any warnings before continuing with the setup process.

4. Initialize HP Systems Insight Manager:

/opt/mx/bin/mxinitconfig -a

5. Verify that the mxagent, mxdomainmgr, and mxdtf daemons are running:

ps -ef | grep mx

If they are not running, start them:

/opt/mx/bin/mxstart

6. Configure the managed system to send SNMP traps.

a. Stop the SNMP daemon on the managed system:

/sbin/init.d/SnmpMaster stop

b. Edit /etc/SnmpAgent.d/snmpd.conf by removing the comment symbol and addingthe IP address of the CMS:

trap-dest address

where address is the IP address for the CMS.

c. Start the SNMP daemon:

/sbin/init.d/SnmpMaster start

7. Log into the HP Systems Insight Manager GUI. For assistance with this, refer to Chapter 6,Use the Graphical User Interface

22

Install on HP-UX

8. Using the GUI, add the default WBEM user name and password to the Global ProtocolSettings page.

Note: An account for at least one of the WBEM user name and password combinations mustexist on the CMS.

a. Select Options->Protocol Settings->Global Protocol Settings.

b. In the Default WBEM settings section, ensure that the Enable WBEM checkbox isselected and add the default WBEM user name and password.

c. Click OK.

Next StepsNext you need to complete the initial setup of HP Systems Insight Manager. Initial setup involvesadding managed systems, adding users, setting up authorizations and configuring event handling.See Chapter 8, Initial Setup for details.

Remove the SoftwareIf you need to remove HP Systems Insight Manager, complete the following steps.

Caution

Removing HP Systems Insight Manager will permanently delete the information inthe database unless you back it up prior to removing the software.

1. Stop the HP Systems Insight Manager daemons:

mxstop

2. Verify that the daemons are no longer running:

ps -ef | grep mx

If any of the HP Systems Insight Manager daemons are running, kill them:

kill daemon

where daemon is the name of the daemon. For example,

kill mxinventory

3. Optional: Back up the HP Systems Insight Manager database:

mxrepositorysave -f filename

where filename is the name of the backup file.

23

Install on HP-UX

4. Remove the HP Systems Insight Manager software:

swremove T2414BA

5. Optional: If other applications are not using the following dependencies, you can removethem. If you want to manage this system using another HP Systems Insight Manager centralmanagement server, you may want to leave SSH and WBEM installed on this system.

a. Remove Java:

swremove T1458AA

b. Remove PostgreSQL:

swremove ixPostgreSQL

c. Remove SSH:

swremove T1471AA

d. Remove WBEM:

swremove B8465BA

24

Install on HP-UX

Chapter 4. Install on LinuxPrepare the System

This procedure verifies that your system meets the minimum requirements and prepares your systemfor installation.

Note

This release of HP Systems Insight Manager does not support upgrading from HPServicecontrol Manager. Therefore, it is recommended to install this software on asystem that is not your HP Servicecontrol Manager central management server or towait for the next version of HP Systems Insight Manager, which will support migration.



2. Verify that HP Servicecontrol Manager is not installed:

rpm -qa | grep mx

If mxcms, mxagent, or mxrepository are installed, remove them:

rpm -e mxcms-B.03.00.00-1 mxagent-B.03.00.00-1mxrepository-B.03.00.00-1

3. Verify that PostgreSQL version 7.3.4 or later is installed:

rpm -qa | grep postgresql

If you have an earlier version installed, remove the postgresql-server and backup the databasefile:

rpm -qa | qrep postgresql | xarqs rpm -e

mv /var/lib/pgsql /var/lib/pgsql.old

Note: This database file is not compatible with the newer version of PostgreSQL that is installedwith HP Systems Insight Manager. If you ever need to access the data in this file, you will needto use a system that has the older version of PostgreSQL installed.

4. Download the T2416BA_4.00.01_Linux_20040415.bin file or locate a copy on thenetwork. To download a copy, go to http://www.hp.com/go/hpsim, and select Download.

5. In the directory where you downloaded or copied the files, give all users permission to executethe bin file:

chmod +x *.bin

Note: This will change the permissions for all bin files in the directory.

25


6. Verify that the required software dependencies are available on your system and install anythat are not already installed.

a. Verify that SSH is installed:

rpm -qa | grep ssh

If SSH is not installed, you need to install it from your Linux operating system CD beforecontinuing with the installation.

b. Verify that SNMP is installed:

rpm -qa | grep snmp

If it is not installed, you need to install it from your Linux operating system CD beforecontinuing with the installation.

c. Verify that standard C++ libraries (compat-libstdc++-7.3) are installed:

rpm -qa | grep compat


d. Verify that the the GLIBC library is installed. If you plan to install Mozilla on your CMS,this must be installed first.

rpm -qa | grep glib


e. For Red Hat Enterprise Linux ES 3, verify that the GDK Library (gdk-pixbuf-0.22.0-3.0or later) is installed. If you plan to install Mozilla on your CMS, this must be installed first.

rpm -qa | grep gdk-pixbuf


7. Optional: If you are planning to run the Mozilla browser on the CMS, verify that Mozillaversion 1.5 or later is installed. To verify which version is installed, open the Mozilla browserand select Help->About Mozilla.

Note: Mozilla is not required on the CMS. It can be used to access HP Systems InsightManager from any network client. Most Linux distributions install version 1.0 as part of thebase operating system.

To upgrade your version of Mozilla:

a. Download the latest version for Linux at http://www.mozilla.org/download. Create atemporary directory called mozillatemp, and place the downloaded GZIP file in thatdirectory.

b. Navigate into the mozillatemp directory and decompress the archive:

26

Install on Linux

http://www.mozilla.org/download

cd path/mozillatemp

tar -zxvf moz*.tar.gz

where path is the location of the temporary directory you created in the previous step.

c. Navigate into the mozilla-installer subdirectory that was created in the previousstep and run the installer:

cd mozilla-installer

./mozilla-installer

Follow the Mozilla install wizard to walk you through the rest of the process.

d. Verify that Mozilla installed correctly by running the browser:

/usr/local/mozilla/mozilla

The path usr/local/mozilla is the default install directory. If you changed the installdirectory during the installation, this command will need to reference your path instead.

Note: If you are running GNOME or another desktop, you can edit the properties of theMozilla icon to point to the version that you just installed.

e. Configure Mozilla to accept cookies. Select Edit->Preferences, expand Privacy &Security and Cookies, then select the Enable All Cookies option. Click OK to savethe changes.

Note: If you don't want to enable all cookies, you can select Enable cookies for theoriginating web site only instead.

8. Optional: If you are planning to run the Mozilla browser on the CMS, install and register theJava JRE browser plug-in version 1.4.2_03 or later.

To install and register the JRE browser plug-in:

a. Download the JRE browser plug-in at http://java.sun.com/j2se/1.4.2/download.html.

Note: You are prompted to install this plug-in the first time you navigate to the HP SystemsInsight Manager login page if it is not already installed.

b. Register the plug-in:

ln -s/usr/java/j2re1.4.2_03/plugin/i386/ns610-gcc32/libjavaplugin_oji.so.

Note: There is a space before the final period in the command. This command assumesthat you are located in the /usr/local/mozilla/plugins directory. If you are in adifferent directory, you must specify the path to the mozilla directory in place of thefinal period.

Note: The directory j2re1.4.2_03 will change if you are installing a later version ofthe JRE.

27

Install on Linux

http://java.sun.com/j2se/1.4.2/download.html

Install and Configure the SoftwareInstallation of HP Systems Insight Manager includes the PostgreSQL software dependency.

To install HP Systems Insight Manager on Linux:

1. Extract the rpm files from the bin file. Make sure you set the permissions to include the rightto execute in the previous section.

T2416BA_4.00.01_Linux_20040415.bin --keep --confirm

2. Respond negatively to the prompt to run scripts. The extracted files will be placed in anmxserver subdirectory.

3. Install the PostgreSQL database using the appropriate rpm files in the order listed below.

Note: The rpm -U command will update older versions of PostgreSQL or install the packageif it is not already installed on your system.

● For Red Hat Enterprise Linux AS 2.1:

rpm -U postgresql-libs-7.4-0.3PGDG.i386.rpm

rpm -U postgresql-7.4-0.3PGDG.i386.rpm

rpm -U postgresql-server-7.4-0.3PGDG.i386.rpm

● For Red Hat Enterprise Linux ES 2.1:

rpm -U postgresql-libs-7.4-0.3PGDG.i386.rpm

rpm -U postgresql-7.4-0.3PGDG.i386.rpm

rpm -U postgresql-server-7.4-0.3PGDG.i386.rpm

● For Red Hat Enterprise Linux AS 3:

rpm -U postgresql-libs-7.4-1-1PGDG.i386.rpm

rpm -U postgresql-7.4-1-1PGDG.i386.rpm

rpm -U postgresql-server-7.4-1-1PGDG.i386.rpm

● For Red Hat Enterprise Linux ES 3:

rpm -U postgresql-libs-7.4-1-1PGDG.i386.rpm

rpm -U postgresql-7.4-1-1PGDG.i386.rpm

rpm -U postgresql-server-7.4-1-1PGDG.i386.rpm

● For SuSE Enterprise Server 8

rpm -U postgresql-libs-7.4-0.i586.rpm

rpm -U postgresql-7.4-0.i586.rpm

28

Install on Linux

rpm -U postgresql-server-7.4-0.i586.rpm

4. Verify that the PostgreSQL status reads running.

● For Red Hat Enterprise Linux (all versions):

a. Execute the serviceconf command.

b. Using the GUI, scroll down to the postgresql entry.

c. Select the checkbox, save the changes, and start the service.

d. Verify that the PostgreSQL daemon status is running:

/etc/rc.d/init.d/postgresql status

● For SuSE Enterprise Server 8:

a. View the status:

/etc/init.d/postgresql status

b. If the status is unused, start the daemon:

/etc/init.d/postgresql start

c. To configure postgresql to run during startup:

chkcongfig postgresql 345

5. Install HP Systems Insight Manager using the rpm files:

rpm -ivh hpsim-C.04.00.01-1.i386.rpmhpsim-pgsql-config-C.04.00.01-1.i386.rpm

Note: Both files must be installed concurrently with a single command.

6. Test the prerequisites:

/opt/mx/bin/mxinitconfig -l

This utility should report that all server components are Acceptable and that it completedall tasks successfully.

Note: It is recommended to resolve any warnings before continuing with the setup process.

7. Initialize and configure HP Systems Insight Manager:

/opt/mx/bin/mxinitconfig -a

8. Verify that the mxagent, mxdomainmgr, and mxdtf daemons are running:

ps -ef | grep mx

29

Install on Linux

If they are not running, start them:

/opt/mx/bin/mxstart


Note: These steps may vary slightly depending on your version of Linux. Refer to your Linuxprovider for details if these file paths and file names.

a. Verify that SNMP is installed on the managed system:

ps -ef | grep snmpd

If it isn't installed, refer to your Linux provider for information on installing SNMP.

b. Stop the HP Server Management Drivers and Agents daemon on the managed system:

/etc/init.d/hpasm stop

c. Stop the SNMP daemon on the managed system:

/etc/init.d/snmpd stop

d. Edit /etc/snmp/snmpd.conf file.

i. Remove the comment symbol from the trapsink line and add the IP address of theCMS:

trapsink IPaddress

where IPaddress is the IP address of the CMS.

ii. Add the CMS to the read only community by adding the line:

rocommunity CommunityName IPaddress

where CommunityName is the SNMP community string used by the CMS andIPaddress is the IP address of the CMS.

iii. Save the changes to the file.

e. Start the SNMP daemon:

/etc/init.d/snmpd start

f. Start the HP Server Management Drivers and Agents daemon:

/etc/init.d/hpasm start


30

Install on Linux

Remove the SoftwareIf you need to remove HP Systems Insight Manager, complete the following steps.

Caution

Removing HP Systems Insight Manager will permanently delete the information inthe database unless you back it up prior to removing the software.

1. Stop the HP Systems Insight Manager daemons:

/opt/mx/bin/mxstop

2. Verify that the daemons are no longer running:

ps -ef | grep mx

If any of the HP Systems Insight Manager daemons are running, record the process ID (pid)and kill the process:

kill -9 pid

where pid is the process ID of the daemon. For example,

kill -9 3456

Note: Process IDs can contain up to 5 digits.

3. Optional: Back up the HP Systems Insight Manager database:

mxrepositorysave -f directory/filename

where directory is a unique location for the file outside of the HP Systems Insight Managerdirectory structure and filename is the name of the backup file.

Note: If you plan to remove the HP Systems Insight Manager directories later in the process,you need to save this backup in a location outside of the default product directories.

4. Remove the HP Systems Insight Manager software:

a. Identify the package names:

rpm -qa | grep hpsim

b. Remove the packages:

rpm -e hpsim*

where hpsim* are the names of the packages.

5. Optional: Remove the HP Systems Insight Manager directories:

31

Install on Linux

CAUTION: Removing these directories will delete your database backup if you did not selecta location for that file outside the default product directories.

rm -rf /opt/mx /var/opt/mx /etc/opt/mx

6. Optional: If other applications are not using PostgreSQL, you can remove it :

a. Identify the package names:

rpm -qa | grep postgresql

b. Remove the packages:

rpm -e postgresql*

where postgresql* are the names of the packages.

32

Install on Linux

Chapter 5. Install on WindowsPrepare the System

This procedure verifies that your system meets the minimum requirements and prepares your systemfor installation.

Note

This release of HP Systems Insight Manager does not support upgrading from HPInsight Manager 7 or Toptools. Therefore, only install HP Systems Insight Manageron a system where neither of these applications have been previously installed.



2. Install the required Windows Service Pack if necessary.

Download the HP Systems Insight Manager Release Notes for the latest Service Packrequirements. To download the Release Notes, go to: http://www.hp.com/go/hpsim

3. Download the software or locate a copy of the HP Management CD.

To download the software, go to http://www.hp.com/go/hpsim, and select Download.

Note

If your system has a C:\HP directory, you need to delete it or rename it prior toinstalling HP Systems Insight Manager. The WMI Mapper that is installed with HPSystems Insight Manager requires a C:\hp directory for certificate storage, and itwill not find the certificates if the directory is not lower case.

Install and Configure the SoftwareTo install HP Systems Insight Manager:

1. Run inshell.exe to launch the HP Systems Insight Manager Installer.

Note: If you are using the Management CD, place the CD in the CD-ROM drive. The CD hasan autorun feature which launches a license agreement. Accept the license agreement, andnavigate to the Products tab. Click Install on the HP Systems Insight Manager page. Thenselect Install beside the HP Systems Insight Manager (Windows) listing to launch the Installer.

2. From the HP Systems Insight Manager Installer window, click Install to launch the installprocess.

33



3. (Optional) If Microsoft SQL is not detected locally, you will be prompted to either installMicrosoft SQL Server Desktop Engine (MSDE) 2000 SP3A or continue and point to a remoteSQL installation later.

Note: For a list of supported databases, see the section called “System Requirements” fordetails.

Note: If choosing to use a remote Microsoft SQL Server, verify that Microsoft Access DataComponents (MDAC) version 2.7 Service Pack 1 or higher is installed on the centralmanagement server. To verify whether this is installed or not, navigate to C:\ProgramFiles\Common Files\System\Ado, and right click on the icon for the msado15.dllfile. In the pop-up menu, choose Properties, and select the Version tab to display the versionnumber. If the file is not found in this path, use the Windows search engine to find the file. Ifyou need to download MDAC, go to http://www.microsoft.com/downloads/, and searchfor MDAC Service Pack.

a. Click Install MSDE to launch the install.

b. After MSDE installation is complete:

● If you are prompted to reboot, reboot your system and repeat the previous step tolaunch the installer after you reboot. You will not see the option to install MSDE again.

● If you are not prompted to reboot, return to the Installer window.

Note: If you reboot, the HP Systems Insight Manager Installer window will notautomatically be open. You will need to execute inshell.exe to launch the installer.

4. Click Typical to install all the components of HP Systems Insight Manager.

Note: The only differences between the Typical and Custom installs for this version of HPSystems Insight Manager is that the Custom option allows you to change one or more of thefollowing settings for the components:

● drive● install directory● program group

The Available Components for Install listed in the table will be installed as part of theTypical install. This list should include HP Systems Insight Manager, WMI Mapper, OpenSSH,and Version Control Repository Manager.

5. On the Typical Install - Account Authentication screen, enter the Account Credentialsfor the database server. If your database is local, enter the CMS name as the Database Server.

Note: If you just installed MSDE, the administrative credentials are those you used to log inprior to installing MSDE. It is required to use Windows Authentication to connect to the SQLserver (whether locally or remotely). In addition, these credentials will also be your HP SystemsInsight Manager administrative user login credentials.

6. On the Typical Install - Summary screen, select Install to initiate the installation process.This process installs all the products listed in the Selected Components table.

7. Click Finished when the installation is complete to close the HP Systems Insight ManagerInstaller window.

34

Install on Windows

http://www.microsoft.com/downloads/

8. If any of the components indicated that a reboot is necessary, reboot your system.


Removing the SoftwareUsing the Add/Remove Programs feature in Windows, complete the following steps to removeHP Systems Insight Manager and its dependencies:

1. Remove HP Systems Insight Manager.

2. Optional: If other applications are not using the following dependencies, you can removethem. If you want to manage this system using another HP Systems Insight Manager centralmanagement server, you may want to leave SSH installed on this system.

a. Remove Microsoft SQL Server Desktop Engine if you installed the default version bundledwith HP Systems Insight Manager.

Note: Removing MSDE leaves a database directory at C:\Program Files\MicrosoftSQL Server. If you plan to reinstall MSDE or another Microsoft SQL database product,you need to rename or remove this folder.

b. Remove the WMI Mapper.

c. Remove the OpenSSH Services for HP Systems Insight Manager.

d. Remove the Version Control Repository Manager.

3. Reboot the system.

35

Install on Windows

Chapter 6. Use the Graphical UserInterface

HP Systems Insight Manager provides a browser-based graphical user interface (GUI).

Access the GUIThe GUI can be accessed from any network client that is running a supported Web browser. Seethe section called “Network Client Requirements and Recommendations” for a list of supportedbrowsers.

Required Java Plug-inWhen you navigate to the HP Systems Insight Manager GUI, it checks to make sure you have thecorrect version of the Java Runtime Environment (JRE) installed. If you don't, it prompts you to installthe correct version. When installing the JRE, it is recommended to select the Custom install optionand to deselect the options for this to be the default Java runtime for Microsoft Internet Explorerand Netscape. Failure to do this may cause issues with other Web applications.

Note

To use Mozilla on Linux, you must register the Java® plug-in. At a command prompt,enter the following commands:

cd /usr/local/mozilla/plugins

mv libjavaplugin_oji.so libjavaplugin_oji.so.bak

ln -s/usr/java/j2re1.4.2_01/plugin/i386/ns610-gcc32/libjavaplugin_oji.so

To log in to the GUI:

1. Open a supported Web browser on any network client, and enter the address for the loginpage by navigating to http://hostname:280/ where hostname is the hostname of thecentral management server (CMS).

Note: If you are logging in directly on a Windows CMS, you can use the HP SystemsInsight Manager desktop icon to access the login page, or you can selectStart->Programs->HP Systems Insight Manager->HP Systems Insight Manager.

2. Enter your User name, Password and Domain if requested.

3. Click Secure Login.

36

Graphical User Interface FeaturesThis section describes the graphical user interface (GUI) features. The following is a sample screenshot of the GUI.

1

2

3

4

5

There are five regions in the GUI:

1. Banner with summary views. The banner provides a link to the Home page and alink to log out. It also provides system status information and an alarm to notify you of certainevents. The banner can be customized for your environment.

2. Search. The search feature enables you to search for matches by system name andcommon system attributes. You can also perform an advanced search for matches based onselected criteria.

3. System and event lists. System and event lists enable you to view all known systemsand events or a specific subset. Lists can be private, visible only to its creator, or public, visibleby all users. HP Systems Insight Manager ships with default public lists only. For informationabout customizing and creating new lists, refer to the HP Systems Insight Manager on-linehelp.

4. Menus. The HP Systems Insight Manager menus provide access to tools, logs, softwareoptions, and on-line help. The Options menu is primarily targeted for users who administerthe HP Systems Insight Manager software. If you lack authorization to use these tools, youmight not be able to access this menu.

5. Workspace. The workspace displays the results of your latest request. It can contain alist, tool, or a report. Some tools launch a separate browser window or X Window terminalinstead of displaying in the workspace. This area contains the Home page when you log into HP Systems Insight Manager. By default, the introductory page is displayed as the Homepage.

37

Use the Graphical User Interface

Default Home Page FeaturesThe HP Systems Insight Manager introductory page is the default Home page for the GUI. Theintroductory page provides information and tips about HP Systems Insight Manager and links tofrequently used features. You can customize HP Systems Insight Manager to display a differentpage as the Home page. The following is a sample screen shot of the introductory page.

1

2 3

4

There are four default sections on the introductory page:

1. DO THIS NOW to finish the install. This section is only visible to users with fullconfiguration rights and only appears if the following conditions are met:

● The user has full configuration rights.● The user has not disabled this section from the Home Page Settings page.

2. Monitor. The Monitor section provides links to common monitoring tasks, including locatingand tracking systems, clusters, and events. All monitoring tasks can be performed using thefeatures and tools provided in the system and event list area.

3. Manage. The Manage section provides links to frequently used tools and features availablefrom the menus above the workspace. These links provide access to inventory reports, softwareand firmware deployment, discovery, event handling, and authorizations.

4. Did You Know You Can...? This section provides useful tips and shortcuts. Learn moreabout HP products, service offerings, and software.

38


Customize the GUICustomize Home

Customize the HP Systems Insight Manager Home page to select which page displays when HPSystems Insight Manager is first started and to disable sections in the default introductory page.

To customize the Home page:

1. Click Home in the banner to display the Home page in the workspace.

2. Click Customize in the upper right corner of the introductory page.

Note: If the Home page has been set to something other than the default introductory page,you can access the Home Page Settings page by clicking Options->Home Page Settings.

3. Specify which page you want to use as Home page:

● Introductory page (default)● Status Overview page● Any specific system, cluster, or event list page

Note: The default introductory page is only available when it is set as the Home page. If youwant to view this page when it is not set as your home page, reselect it as the Home page.

4. (Optional) If the introductory page is selected as your Home page, customize the content onthe page by selecting or clearing the:

● Did You Know You Can...? section● Do this now to finish the install section

Customize the BannerCustomize the HP Systems Insight Manager banner to configure summary views, to configure thevisible alarm, and to display the icon legend.

To customize the banner:

1. Click Customize in the upper right corner of the banner area. The Customize Banner pagedisplays.

2. Select Show summary of and select uncleared event status, hardware status, or both.

a. Select the system list All Systems, or select a system list from the drop-down list.

Note: An error message is displayed if a folder is selected instead of a list.

b. Edit the Label if desired.

3. Select to Show an alarm when any system meets the condition.

a. Select the Condition.

39


b. Select the system list All Systems, or select a system list from the drop-down list.

c. Edit the Label if desired.

4. Select or clear the Show legend of status icons in lower left area of screen.

5. Select OK to save changes.

Note: Restore Defaults returns the customization screen to its default condition. Only theuncleared event status appears in the banner. Hardware status and the alarm are turned off.The legend is turned on. All personalized information is removed.

40


Chapter 7. Use the Command LineInterface

HP Systems Insight Manager provides a command line interface (CLI) in addition to the GUI. Allfunctionality available in the GUI is available via the CLI.

Log in to the CLIAccess the HP Systems Insight Manager CLI directly on the CMS or from any network client usingSSH client software.

Note

Only administrators have command line access to HP Systems Insight Manager ona Windows CMS.

Directly on the CMSTo log in to the CLI directly on the CMS:

1. Log in to the CMS using a valid user name and password.

HP Systems Insight Manager grants authorizations based on your operating system user login.

2. Open a terminal window or a command prompt window to execute HP Systems Insight Managercommands.

Remotely Using an SSH Client

Note

The preferred way to log in remotely is using an SSH client. Telnet or Rlogin works,but they do not provide a secure connection.

To log in to the CLI remotely using an SSH client:

1. Open an SSH client application on any network client.

2. Log in to the CMS through the SSH client software, using a valid user name and password.

HP Systems Insight Manager grants authorizations based on your operating system user login.

41

HP Systems Insight Manager CommandsHP Systems Insight Manager commands are installed in the following locations on the CMS.

● For HP-UX and Linux:

/opt/mx/bin/

● For Windows:

C:\Program Files\HP\Systems Insight Manager\bin\

Note

The Windows path will vary if HP Systems Insight Manager was not installed in thedefault location.

To view the man pages from the command line on an HP-UX or Linux system, use the followingman page sections.

● For HP-UX:

❍ Administrative command man pages are section 1M.❍ Special file man pages are section 4.

● For Linux:

❍ Administrative command man pages are section 8.❍ Special file man pages are section 4.

For command help on a Windows central management server, use the HTML version of the manpages available in the following table.

The following table provides a complete list of HP Systems Insight Manager commands. For adetailed explanation of these commands, view the associated man pages from a command promptor see the HP Systems Insight Manager on-line help.

Available Man PagesFunctionalityCommandcommandCompiles an SNMP MIB file into

an intermediate format (.cfg) filefor importing into HP SystemsInsight Manager using themxmib command.

mcompile

commandConfigures the agent to workwith a central managementserver (CMS).

mxagentconfig

command and fileAdds or removes atoolbox-based authorization.

mxauth

42

Use the Command Line Interface

Available Man PagesFunctionalityCommandcommandContains the object managers

that interact with the databaseand the Distributed Task Facility(DTF).

mxdomainmgr

commandContains the DTF that is used toremotely execute commands onmanaged nodes that areequipped with Secure Shell(SSH).

mxdtf

commandExecutes tools and verifies thestatus of running tools.

mxexec

command and filePerforms initial configuration fora DTF agent or the CMS.

mxinitconfig

commandAdds, deletes, and processes alist of MIBs for HP SystemsInsight Manager. Also listsregistered MIBs and lists trapsfor a specific registered MIB.

mxmib

command and fileAdds, modifies, or removessystem groups from HP SystemsInsight Manager.

mxngroup

command and fileAdds, modifies, or removessystems from the HP SystemsInsight Manager managementdomain.

mxnode

commandAdds, modifies, or removessecurity credentials for SNMPand WBEM protocols.

mxnodesecurity

commandAdds, lists, modifies, or removespasswords stored in HP SystemsInsight Manager.

mxpassword

command and fileAdds, lists, modifies, or removeslists in HP Systems InsightManager.

mxquery

commandRestores the HP Systems InsightManager database from apreviously created backup.

mxrepositoryrestore

commandBacks up the HP Systems InsightManager database.

mxrepositorysave

command and fileAdds, modifies, and removesHP Systems Insight Managerroles.

mxrole

commandStarts and stops the embeddedWeb-server on the CMS.

mxserver

commandStarts daemons or processesused by the CMS.

mxstart

43


Available Man PagesFunctionalityCommandcommandAdds, removes, and lists System

Type Manager rules.mxstm

commandStops daemons or processesused by the CMS.

mxstop

command and fileLists, executes, removes, creates,and changes ownership for theHP Systems Insight Managerscheduled tasks.

mxtask

command and fileAdds, modifies, and removestools.

mxtool

command and fileAdds, modifies, or removestoolboxes from the HP SystemsInsight Manager system.

mxtoolbox

command and fileAdds, modifies, or removesusers from HP Systems InsightManager.

mxuser

44


Chapter 8. Initial SetupIntroduction to the Initial Setup

The intial setup involves steps like setting up managed systems, configuring discovery, configuringevent handling, adding users, and defining authorizations. It assumes that you just completed theinstallation of your central management server (CMS).

The procedures in this process are common tasks that HP Systems Insight Manager administratorsperform on a regular basis. If you are a new administrator of an existing management domain, itmay be useful for you to familiarize yourself with these procedures even though your CMS hasalready been through the initial setup.

Note

All the information in this section is also available in the online help.

Set Up Managed SystemsSetting up managed systems involves installing the required management agents and configuringthe supported protocols to communicate with the HP Systems Insight Manager software. Follow theappropriate procedure below based on the managed system's operating system.

● Set Up HP-UX Managed Systems● Set Up Linux Managed Systems● Set Up Windows Managed Systems

Set Up HP-UX Managed SystemsTo set up an HP-UX managed system:

1. Install and configure SSH.

a. Install the SSH software on the managed system:

swinstall -s /directory/depot T1471AA

where directory is the path to the depot file and depot is the name of the depot file.For example:

swinstall -s /tmp/HPSIM_download.depot T1471AA

b. On the CMS, copy the SSH generated public key from the CMS to the managed systemand place it in the authorized keys file of the execute-as user (root or administrator).

i. Launch the Manage SSH Keys dialog box from the CMS command prompt:

45

mxagentconfig -g

ii. Enter the managed system's Hostname.

iii. Enter root or administrator for the Username and the associated Password.

iv. Click Connect.

2. Configure DMI on the managed system by adding the DNS host name of the CMS.

a. Stop the DMI daemon on the managed system:

/sbin/init.d/Dmisp stop

b. Edit /var/dmi/dmiMachines by adding the host name of the CMS to the end of thisfile. Save the file.

c. Start the DMI daemon:

/sbin/init.d/Dmisp start


a. Stop the SNMP daemon on the managed system:

/sbin/init.d/SnmpMaster stop

b. Edit /etc/SnmpAgent.d/snmpd.conf by removing the comment symbol and addingthe IP address of the CMS:

trap-dest address

where address is the IP address for the CMS.

c. Start the SNMP daemon:

/sbin/init.d/SnmpMaster start



Note: An account for at least one of the WBEM user name and password combinations mustexist on each managed system.

Note: This step can be performed once for all the managed systems you are setting up.


b. In the Default WBEM settings section, ensure that the Enable WBEM checkbox isselected and add the default WBEM user name, password, and confirmation password.

46

Initial Setup

c. Click OK.

Set Up Linux Managed SystemsTo set up a Linux managed system:


a. Verify that SSH is installed on the managed system:

ps -ef | grep ssh

If it isn't installed, refer to your Linux provider for information on installing SSH.

b. On the CMS, copy the SSH generated public key from the CMS to the managed systemand place it in the authorized keys file of the execute-as user (root or administrator).


mxagentconfig -g



iv. Click Connect.


Note: These steps may vary slightly depending on your version of Linux. Refer to your Linuxprovider for details if these file paths and file names.

a. Verify that SNMP is installed on the managed system:

ps -ef | grep snmpd

If it isn't installed, refer to your Linux provider for information on installing SNMP.

b. Stop the HP Server Management Drivers and Agents daemon on the managed system:

/etc/init.d/hpasm stop

c. Stop the SNMP daemon on the managed system:

/etc/init.d/snmpd stop

d. Edit /etc/snmp/snmpd.conf file.

i. Remove the comment symbol from the trapsink line and add the IP address of theCMS:

trapsink IPaddress

where IPaddress is the IP address of the CMS.

47

Initial Setup

ii. Add the CMS to the read only community by adding the line:

rocommunity CommunityName IPaddress

where CommunityName is the SNMP community string used by the CMS andIPaddress is the IP address of the CMS.

iii. Save the changes to the file.

e. Start the SNMP daemon:

/etc/init.d/snmpd start

f. Start the HP Server Management Drivers and Agents daemon:

/etc/init.d/hpasm start

3. Install the Linux ProLiant Support Pack. To download this software and access installationinformation, go to http://www.hp.com/support/files.


5. Add the default WBEM user name and password to the Global Protocol Settings page inthe HP Systems Insight Manager GUI.





c. Click OK.

Set Up Windows Managed SystemsTo set up a Windows managed system:


a. Install SSH on the managed system. Using the HP Management CD or the installation filesthat you downloaded for the CMS installation, navigate to the openssh folder andexecute OpenSSH_3.7.1p1-1.exe. Accept all the default prompts.

b. Configure SSH on the managed system.

i. Open a Command Prompt window and navigate to the following directory:

cd C:\Program Files\OpenSSH\etc

48

Initial Setup

http://www.hp.com/support/files

This command assumes OpenSSH was installed in the default location.

ii. Execute the following command to see which users are registered with OpenSSH:

type passwd

If the execute-as user for your CMS (root or administrator) is not listed, you need toadd them. Otherwise, you can skip to the next step of copying the SSH generatedpublic key.

iii. Navigate to the bin directory:

cd C:\Program Files\OpenSSH\bin

iv. Add the user.

● For a domain account:

mkpasswd -d -u login domain >> C:\ProgramFiles\OpenSSH\etc\passwd

where login is the login name of the execute-as user and domain is the userdomain.

● For a local account:

mkpasswd -l -u login >> C:\Program Files\OpenSSH\etc\passwd

where login is the login name of the execute-as user.

c. On the CMS, copy the SSH generated public key from the CMS to the managed systemand place it in the authorized keys file of the execute-as user (root or administrator).


mxagentconfig -g



iv. Click Connect.


a. Select Start->Programs->Administrative Tools->Services.

On Windows 2003 and Windows XP, the Programs submenu is All Programs.

b. Scroll down the list and right-click SNMP Service.

c. Select Properties from the pop-up menu.

49

Initial Setup

d. On the Security tab, either click Add to add a new community string or click Edit tomodify an existing one.

e. Enter the information for the CMS and click Apply to save the changes.

f. On the Traps tab, enter a Community Name and click Add to List.

g. Click Add to add the Trap Destination.

h. Enter the IP Address of the CMS and Click Add and click Apply to save the changes andOK to close the dialog box.


4. Using the GUI, install the ProLiant Support Pack on the managed system. Click Deploy->DeployDrivers, Firmware and Agents->Initial ProLiant Support Pack Install, and refer to theUse Default Tools section of the on-line help for more information.

Note: This step can be performed once for all the Windows managed systems you are settingup.




a. Click Options->Protocol Settings->Global Protocol Settings.


Note: The user name must include the domain. For example: domain\user

c. Click OK.

Configure Protocol SettingsConfiguring the protocol settings defines what systems are added to HP Systems Insight Managerusing discovery in the next step.

To configure the protocol settings:

1. Click Options->Protocol Settings->Global Protocol Settings. The Global Protocol Settingspage is displayed.

2. In the Default ping (ICMP) settings section, set the Default timeout and the Default retries.If some systems are managed over a WAN or satellite link, use a larger timeout (for example,5 seconds) with at least one retry. For a LAN, a shorter timeout may be used.

50

Initial Setup

3. In the Default WBEM settings section, select the Enable WBEM box. Then enter as manydefault user names and passwords as needed. The identification process attempts each ofthese user name and password pairs until a successful response is obtained. Future WBEMrequests to that system use the user name and password that succeeded. For Windows basedsystems, the user name should include the domain name, for example, domainname\username.

Note: Order the name\password pairs such that root and administrator passwords are listedfirst and user and guest passwords are listed secondarily, to help minimize the search time.

4. In the Default HTTP settings section, select the Enable HTTP and HTTPS if necessary toallow for Web-based agents and other HTTP port scans to be identified.

5. In the Default SNMP settings section, select the Enable SNMP box and set the Defaulttimeout and Default retries. If some systems are managed over a WAN or satellite link, usea larger timeout (for example, 5 seconds) with at least one retry. For a LAN, a shorter timeoutmay be used.

6. Enter the Default write community string. Only a few tools need this option set.

7. Enter the Read community string. Enter as many as needed. The identification processattempts communication to the system using each of these communities until a successfulresponse is obtained. Future SNMP requests then use the community string that provided asuccessful response.

8. In the Default DMI settings section, select the Enable DMI box to enable DMI identificationto run on systems.

Note: DMI is not currently supported on Linux systems.

9. Click OK to accept the settings.

Configure and Execute Discovery: Automaticor Manual

Discovery is the process that HP Systems Insight Manager uses to find and identify the systems onyour network and populate the database with that information. A system must first be discoveredin order to collect data and track system status. There are two basic ways to discover new systems:

● Automatic discovery searches the network for systems running specific protocols. It runsautomatically every 24 hours, but the process can be manually executed at other times.

● Manual discovery is used to add a single system or a group of systems using a Hosts file.

Configure and Execute Automatic DiscoveryTo configure and execute automatic discovery:

1. Click Options->Discovery->Automatic Discovery. The Automatic Discovery - GeneralSettings page is displayed.

2. In the Schedule section, select Automatically execute discovery every:, and enter thenumber of months, weeks, hours, days or a combination between each discovery. You canalso specify the start time for daily, weekly, or monthly schedules. The default is once a day.

51

Initial Setup

3. Five options are available in the Discovery configuration section:

● Use discovery filters. This option allows you to eliminate undesired system types frombeing discovered and managed, click discovery filters to change the settings. DiscoveryFilters can also be enabled or disabled from this page. However, you must click Save orSave and Run.

● IP range pinging

● IPX SAP (Windows only)

● Automatically discover a system when an event is received from it. This optionallows systems to be discovered when a trap or some other supported event is receivedby HP Systems Insight Manager. It uses the discovery filters and IP address exclusion rangesfor additional filtering of these events.

● Configure global protocol settings

a. If you select Configure global protocol settings, the Global Protocol Settings pageis displayed. Set the Default ping (ICMP) settings and select to Enable WBEM,Enable HTTP and HTTPS, Enable SNMP, and Enable DMI.

Note: You need SNMP enabled with correct security settings on HP Systems InsightManager and running on the target systems to discover clusters correctly.

Note: DMI is not available on Linux systems.

b. Click OK to save changes and then click Automatic Discovery to return to theAutomatic Discovery - General Settings page.

4. In the IP address ranges section of the Automatic Discovery - General Settings page,specify the IP addresses to include or exclude for pinging. Be sure to specify the ExclusionRanges for any of the Automatic Discovery processes. This applies to both range IP pingingand event based auto-discovery.

You can click templates to create Discovery Templates or click hosts files to create Hostsfiles.

After creating a Discovery Template, you can reference it by using @template_name inthe Ping inclusion ranges or Exclusion ranges fields.

Note

A single Discovery Template cannot include both Included and Excludedranges. You must create a separate template for use in each field ofAutomatic Discovery. Template files cannot be nested, that is, a templatefile cannot contain another template file name via the @template_namereference.

5. Click Save to save the current configuration, click Save and Run to save the currentconfiguration and run Discovery now.

52

Initial Setup

Important

The new configuration is not saved until you click Save to save your settingsor click Save and Run to begin the discovery process immediately. If youclick Save and Run, this button changes to Stop Automatic Discovery.While Automatic Discovery is running, you can click this button to stop itfrom running.

Configure and Execute Manual DiscoveryTo configure and execute manual discovery:

1. Click Options->Discovery->Manual Discovery.

2. On the Manual Discovery - Add System page, in the System Information section, select theSystem name radio button and enter the system name.

or

select the IP address radio button and enter the IP address.

3. Click Add System to add the system to the database, or click More Settings to enter thefollowing optional information:

● Specify additional system properties to use only if Identification fails on this system.Includes System type, System subtype, and Product model.

● WBEM Settings. Includes User name and Password

● SNMP Settings. Includes Timeout, Retries, Read-only community string, and Writecommunity string

4. If you clicked More Settings, you can click Add System to add the system immediately, orclick Fewer Settings to return to the previous brief display. If you click Fewer Settings, clickAdd System to add the system to the database.

Add UsersAny user with a valid network login can be added to HP Systems Insight Manager.

To add users:

1. Click Options->Security->Users and Authorizations->Users->[New]. The New User sectionis displayed.

2. In the Login name field, enter the operating system login account name to be used to login toHP Systems Insight Manager. This is a required field.

Note: The user cannot log in to HP Systems Insight Manager if the account is not a validlogin, and the account is not validated until the user tries to log in to HP Systems InsightManager the first time.

53

Initial Setup

3. In the Domain field, enter the Windows domain name for the login name if running a Windowsoperating system.

4. In the Full name field, enter the user's full name.

5. In the Phone field, enter the user's phone number.

6. In the E-mail address field, enter the user's e-mail address.

7. In the Copy all authorizations of this user or template field, select a template or login thatalready has the pre-defined authorizations that you want to assign to the login account youare creating.

8. In the Central management server configuration rights section, select the level of authorityto assign to the new user from the following options:

● Full configuration rights. Allows the user total control of the database. Users can runDiscovery of systems and Data Collection; define users and authorizations; set ClusterMonitor configuration; configure licensing and protocol settings; and create, modify, delete,and run reports, snapshot comparisons, tools, custom commands, events, automation tasks,and so on.

● Limited configuration rights. Allows the user to create new reports, edit any reports,and delete any reports (including the pre-defined reports). Users can also create newsingle-system aware (SSA) tools and Web-launch aware (WLA) tools. These tools remainowned by that user, which means they have restricted authorizations. As owner of the tool,they can edit or delete the tool, and the tool can only be a member of the All Tools toolbox.

● No configuration rights. A user with no configuration rights cannot execute any actionsto affect the system database. This allows a user to view and run pre-defined reports onsystems they have been authorized to view only.

9. Under the Login IP Address Restrictions section, in the Inclusion ranges field, enter theIP addresses of the systems that you want this user to be able to use as a client browsing intothis CMS. If you list multiple IP addresses, separate them with a semi-colon (;). Each range isa single IP address or two IP addresses separated by a dash (-). The IP addresses must beentered in the standard dotted form, for example 15.1.54.133. Any spaces surrounding thesemi-colons or dashes are ignored. Spaces are not allowed within a single IP address in dottedform. Enter 0.0.0.0 to prevent a user from logging in through a remote system.

10. In the Exclusion ranges field, enter the IP address of the systems that should be excluded fromthis user as clients browsing into this CMS. Use the same format in the previous step for Inclusionranges.

Note: Be sure to verify that your inclusion and exclusion ranges do not overlap.

11. Note: The following five steps are for Windows systems only.

Under the Pager Information section, in the Phone Number field, enter the pager phone numberof the user associated with this user account if you are using a Windows operating system. IfPhone Number field is left blank, the paging information is not saved.

12. In the PIN number field, enter the PIN number associated with the pager phone number.

54

Initial Setup

13. In the Message length field, select how many characters can be accepted in the pagingmessage from the drop-down list.

14. In the Baud rate field, select the appropriate baud rate for the pager from the drop-down list.

15. In the Data format field, select the appropriate data format for the pager from the drop-downlist.

16. Click OK to save and close the New User section. Click Apply to save and keep the NewUser section open. Click Cancel to cancel the creation of this user.

The new user account is created.

Configure Email SettingsConfiguring email settings will enable users to receive email notification of certain events.

To configure email settings:

1. Click Options->Events->Automatic Event Handling->E-mail Settings. The E-mail Settingspage is displayed.

2. Specify the SMTP host in the SMTP Host box.

3. Specify the e-mail address that the management server will use when sending e-mail notificationsin the Sender box.

4. Click OK to save changes.

Configure Paging SettingsConfiguring paging settings will enable users to receive pages to notify them of certain events.

To configure paging settings:

1. Click Options->Events->Automatic Event Handling->Modem Settings. The Modem Settingspage is displayed.

2. Click the down arrow in the COM port drop-down box and select the appropriate COM port.Refer to your modem documentation for details.

3. Click OK to save the setting.

Set Up Automatic Event HandlingAutomatic event handling enables you to define an action that HP Systems Insight Manager willperform when an event is received. Automatic event handling can be set up to use the email andpaging settings that you specified in the previous sections.

To set up automatic event handling:

1. Click Options->Events->Automatic Event Handling->New Task. The Automatic EventHandling - New Task page is displayed.

55

Initial Setup

2. There are six steps to complete to define a new task. Step 1, Select name, is highlighted.Enter a name for the task in the Task name box.

3. Click Next.

4. In the Select events section, select the event search criteria for defining the rule:

● List criteria

● Comparison option

● Value for the criteria or comparison options selected

If you would like to add additional search criteria, click Add.

5. After you have entered the information, click Next to continue with the next step or Prev toreturn to the previous step.

6. Select the system criteria for defining the task. Select the following from the drop-down menus:

● List criteria

● Comparison option

● Value for the criteria or comparison options selected

7. If you would like to add additional criteria, click Add.

8. After you have entered the information, click Next to continue with the next step, Prev toreturn to the previous step, or Cancel to cancel all changes.

9. Select actions for this task. Select from the following:

● Send page (Windows only)

Add users to be paged from the drop-down list of users by clicking >>. Click << to removeusers from the list of users to be paged. The pager number for an HP Systems InsightManager user is set on the Users and Authorizations page. If a user name in the Users listis inactive, the pager information for the user has not been configured. You can add theuser to the list of users to be paged, but pager messages will not be sent to this user untilthe pager information is provided on the Users and Authorizations page.

● Send e-mail

In the To field, enter the list of e-mail addresses that should receive the notification.

In the CC field, enter any e-mail address that should receive a copy of the e-mail.

In the Subject field, enter a note describing the subject of the e-mail.

In the Message format field, select the format:

❍ Standard. A text e-mail message is sent to the recipients. This is the default messageformat.

56

Initial Setup

❍ Pager/SMS. An e-mail message formatted with the same information and format as apager message is sent to the recipients.

❍ HTML. An e-mail message that looks like the HTML Event Details page will be sent tothe recipients.

● Run custom tool

Select a custom command from the drop-down list. Custom Command tools are createdunder Tools->Custom Commands option.

● Assign

Type in the name of the person to assign the task to. The event is assigned to this userwhen received.

● Forward as SNMP trap

Enter a system name or IP address in the Name or IP text field and click >> to add it tothe Trap recipients box.

Click Delete if you want to delete a recipient after first highlighting the name in the TrapRecipient box. Use the up and down arrows to scroll to the recipient to delete.

● Write to system log

● Clear event

10. After you have made your selections, click Next to continue with the next step or Prev to returnto the previous step.

11. Select Use time filter if you want to use time filters and select an option from the drop-downlist.

Click Manage Filters if you want to set user defined filters.

Click View Filter, and the Time Filter Popup window is displayed, showing the times selected.

12. After you have entered the information, click Next to continue with the next step or Prev toreturn to the previous step

13. After clicking Next, the Review summary page is displayed. If a paging or e-mail optionwas selected, the modem and e-mail settings are displayed, along with buttons to change thesettings. Click Edit Modem Settings to edit the modem settings, or click Edit SMTP Settingsto edit the SMTP settings.

14. Click Finish to create the new task or click Prev to go back to the previous step.

Add ToolboxesCreate a toolbox to configure a group of tools that a user has access to.

To add a toolbox:

57

Initial Setup

1. Click Options->Security->Users and Authorizations->Toolboxes->[New]. The New Toolboxsection is displayed.

2. In the Name field, enter a name for the new toolbox. This is a required field.

3. In the Description field, enter a description for the toolbox.

4. Select to enable or disable the toolbox and all authorizations created with this toolbox.

5. In the Show tools in category field, select the category to display a list of tools in the availabletools list. Select the tools to be assigned to this toolbox in the available tools list and click >>.

The selected tools appear in the Toolbox contents list. You can select a tool displayed inthe Toolbox contents list and click << to remove it from the assigned tools list.

6. Click OK to save the new toolbox and close the Add Toolbox section. Click Apply to savethe settings without closing the New Toolbox section, or click Cancel to cancel the saveoperation.

Add AuthorizationsAuthorize your users for a toolbox on a system or group of systems.

To add authorizations:

1. Click Options->Security->Users and Authorizations->Authorizations->[New]. The NewAuthorizations section is displayed.

2. In the Select User(s) drop-down box, select the user logins to which you want to addauthorizations. You can select multiple users by holding the Ctrl key down while selectingusers, or by selecting one user and holding the Shift key down to select a group of users. Thisis a required field.

3. In the Enter authorizations for the selected users(s) section, select one of the following:

● Copy all authorizations of this user or [template]:. Select a user or template from thedrop-down list

● Manually assign toolbox and system/system group authorizations

a. In the Select Toolbox(es) drop-down box, select the toolboxes in which to includethe users.

b. From the Select drop-down box, select whether you want to allow the user to manageSystem Group(s) or System(s) and then select the group or individual system fromthe drop-down box.

4. Click OK to save the new authorization and close the New Authorizations section. You canclick Apply to save the new authorization without closing the New Authorizations section.You can click Cancel to cancel the creation process.

58

Initial Setup

Chapter 9. Configuration OptionsThere are several configurable parameters in HP Systems Insight Manager that are not availablefrom the GUI. These parameters can only be configured by editing a configuration file on the CMS.

Note

All HP Systems Insight Manager parameters have been set to predefined values thatare appropriate for most situations. These parameters should only be changed ifyou are experiencing issues with the default values.

There are two main default locations where configuration files are stored.

For HP-UX and Linux:

● /etc/opt/mx/config● /opt/hpwebadmin/lib

For Windows:

● C:\Program Files\HP\Systems Insight Manager\config\● C:\Program Files\HP\Systems Insight Manager\hpwebadmin\lib

The Windows directory paths will vary if HP Systems Insight Manager is not installed in the defaultlocation.

These files follow the format of a Java properties file. Therefore, the keys in these files arecase-sensitive. In addition, the backslash (\) must be represented by a double-backslash (\\). Formore information about the Java property file format, see http://java.sun.com/.

This chapter provides information on the following configuration options:

● the section called “CPU Utilization During Data Collection”● the section called “GUI Time-Out Policy”● the section called “HP Systems Insight Manager Audit Log Configuration”● the section called “Lifetimes for Entries on the Task Results Page”

CPU Utilization During Data CollectionOverview

The data collection task runs a number of threads in parallel to overlap computing and databaseoperations with the wait for managed nodes to respond. On slower systems, this could potentiallysaturate the CPU for some period of time, depending on the processor speed of the CMS systemand the number of systems being collected. Therefore, HP Systems Insight Manager provides somestrategies to lessen the CPU usage.

59

http://java.sun.com/

ImplementationTo lessen the CPU usage during data collection on the CMS:

● Limit the number of systems which are being collected at one time. For example, create separatedata collection tasks for different groups of systems and schedule them to run at different times.

● Configure the CMS to use a remote database on a system other than the CMS. A substantialportion of the CPU load is consumed by the database during data collection. This option is onlysupported with a Windows CMS.

● Lower the DataCollectionThreadCount parameter in the globalsettings.props file.This parameter defaults to 3. Lowering it to 2 or 1 will reduce the CPU demand of data collectiontasks, but it will increase the time required to complete the tasks.

GUI Time-Out PolicyOverview

HP Systems Insight Manager provides two alternative time-out policies. The first time-out policy isfor environments where HP Systems Insight Manager is used to monitor system status. This is calledthe monitor time-out policy, and it is similar to the policy used by Insight Manager 7. The secondtime-out policy is more strict and will time-out inactive users. This is called the active time-out policyand it is similar to the policy used by Servicecontrol Manager.

Monitor time-out policy. The monitor time-out policy keeps sessions alive provided the userhas a Web browser window open displaying the HP Systems Insight Manager GUI. Closing thebrowser or navigating to another Web page will start the timer for the time-out period. The defaulttime-out period is 20 minutes. Users must use some other means to protect an unattended sessionfrom illegal use, such as password-protected screen savers.

Active time-out policy. The active time-out policy will only keep sessions alive if the user isactively using the GUI, such as clicking on links and buttons. Display and refresh of the bannerwill not be sufficient to keep the session alive. The user will be timed-out either by inactivity, byclosing the browser, or by navigating to another site. The default time-out period is 20 minutes.

Implementation● To configure the time-out policy, edit the globalsettings.props file. You can switch

between these modes or change the time-out period. The default time-out policy is the monitorpolicy. The monitor policy is enabled when:

EnableSessionKeepAlive=true

To enable the active time-out policy, change this value to false.

EnableSessionKeepAlive=false

● To change the default time-out period, edit the web.xml file. The default location for this fileis:

❍ For HP-UX or Linux:

60

Configuration Options

/opt/hpwebadmin/webapps/MxSessionTimeout/WEB-INF/web.xml❍ For Windows:

C:\Program Files\HP\Systems InsightManager\hpwebadmin\webapps\MxSessionTimeout\WEB-INF\web.xml

Locate the session-timeout element and set it to a new value in minutes.

<session-timeout>20</session-timeout>

HP Systems Insight Manager Audit LogConfigurationOverview

Several features of the HP Systems Insight Manager Audit Log are configurable. For example, youcan specify which tools log data and the maximum Audit Log file size. The HP Systems InsightManager Audit Log is configured through the log.properties file and tool logging is enabledor disabled through the XML tool definition files.

Tool behaviors. The XML tool definition file provides an option to disable logging ofsingle-system aware (SSA) and multiple-system aware (MSA) command tools. The log attribute forthe command element specifies whether the results of the command will be output to the HP SystemsInsight Manager log file. Command output is logged by default.

Audit Log parameters. In the log.properties file, you can configure the following AuditLog parameters:

● the file name● the file extension● the maximum file size in megabytes● the file extension of the roll-over name● the amount of memory allocated for queuing items to be written to the Audit Log

Audit Log location. The location of the Audit Log can be configured using thepath.properties file.

ImplementationFive variables can be defined in the log.properties file:

● MX_LOG_FILENAME for the file name. The default is:

MX_LOG_FILENAME = mx

● MX_LOG_FILEEXT for the file extension. The default is:

MX_LOG_FILEEXT = log

● MX_LOG_FILESIZE for the maximum file size in megabytes. The default is:

MX_LOG_FILESIZE = 20

61


● MX_LOG_ROLLFILEEXT for the file extension of the roll-over name. The default is:

MX_LOG_ROLLFILEEXT = old

● MX_LOG_QUEUESIZE for the amount of memory allocated for queuing items to be written tothe Audit Log. The default is:

MX_LOG_QUEUESIZE = 300

Changes made to the log.properties file will not take effect until the log manager daemon orservice is restarted. For Linux and HP-UX, restart the HP Systems Insight Manager daemons. Usemxstop and mxstart. For Windows, restart the HP Systems Insight Manager service.

Caution

The queue size should be changed only with extreme care. If the queue is set toohigh, the log manager will consume too much system memory.

Note

When the Audit Log file reaches the maximum file size, the log is renamed withMX_LOGROLLFILEEXT extension and a new file is started. If a previous version ofthe file has already been renamed with the MX_LOG_ROLLFILEEXT extension, itwill be an automatic roll over of an audit log file. A roll over will not occur until atask running is completed. However, after one hour of exceeding the maximum filesize, if the task is not finished, then the audit log file will roll over to another file.

To configure the location of the Audit Log:

1. Create the path.properties file if it doesn't exist.

● For Windows, place the file in 'C:\Program Files\HP\Systems InsightManager\config'.

● For Linux and HP-UX, place the file in '/etc/opt/mx/config'.

2. Define the LOG parameter in the path.properties file:

For Windows:

LOG=C:\\Auditlog\\Logs

For HP-UX or Linxu:

LOG=/Auditlog/Logs

where C:\\Auditlog\\Logs and /Auditlog/Logs is the new path to the Audit Log. Thisis a user specific path, and it will vary based on your requirements.

62


Note: When representing a backslash (\) in a Java properties file, you must use adouble-backslash (\\) as shown in the example above.

Note: By default, for Linux and HP-UX, the path for the log file is set to /var/opt/mx/logs.For Windows the default location is the "logs" subdirectory of the directory where the productwas installed.

3. For Linux and HP-UX, restart the HP Systems Insight Manager daemons. Use mxstop andmxstart. For Windows, restart the HP Systems Insight Manager service. After restarting theservice a new log file named mx.log will reside in the directory specified in thepath.properties file.

Lifetimes for Entries on the Task Results PageOverview

HP Systems Insight Manager enables you to set how long entries remain on the Task ResultsPage after a task completes its results.

Short and long task lifetimes. Some task results are kept for a short period of time, whileother task results are kept for a longer period of time. Tasks fall into one or the other categorybased on the type of tool associated with them. Tasks for the following tools have a short lifetime:

● Web-Launch tools● Tools that run from the mxexec command line using the -O or -o options to save the command

output● Tools that run X-Window commands● Tools that specify in their tool definition the "job-log" flag as disabled including:

❍ Hardware Status Polling❍ Data Collection❍ Identify Systems❍ Software Status Polling❍ Delete Events❍ System Protocol Settings❍ Automatic Discovery❍ Hardware Status Polling

Tools in this category have no task output, have task output that is saved outside of HP SystemsInsight Manager, or have task results that are unlikely to be of long-term interest. Tasks for all othertools have the long lifetime.

Frequently scheduled tasks. Task results may also be removed from the Task ResultsPage if a certain number of task results for a scheduled task accumulate. This setting defaults to10 instances of a single task. If more than 10 accumulate on the results page, then the oldest taskresult for this scheduled task is removed.

Last result tasks. Finally, a task result is kept indefinitely if it is the last result for a scheduledtask. For example, if a scheduled task is disabled, its final task result will be kept indefinitely, oruntil the task is enabled and more task results accumulate.

63


ImplementationTo configure the short and long task lifetimes, edit the mx.properties file.

● The short lifetime defaults to 30 minutes. To change that time, edit:

MX_JOB_CACHE_TIME_COMPLETED_JOBS=30

● The long lifetime defaults to 30 days. To change that time, edit:

MX_JOB_MAX_COMPLETED_JOB_AGE=30

● Task results for frequently scheduled tasks start to drop off after 10 instances. To change thisvalue, edit:

MX_JOB_MAX_COMPLETED_JOBS_PER_TASK=10

Note

The limit of 10 task results applies to scheduled tasks with the "job-log" flagenabled in the tool definition. Scheduled tasks for the tools with the "job-log"flag disabled have a limit of 1. This value is not configurable.

● By default, the last task results for a scheduled task will be kept indefinitely. If you want to keepmore than 1 job, edit:

MX_JOB_MIN_COMPLETED_JOBS_PER_TASK=1

Note

This many job instances per task will be kept regardless of theMX_JOB_MAX_COMPLETED_JOB_AGE setting.

64


Glossaryagent A program that regularly gathers information or performs some

other service without the user's immediate presence. HP SystemsInsight Manager agents provide in-depth hardware and softwareinformation and subsystem status to HP Systems Insight Managerand numerous third-party management applications.See Also management agent.

aggregate CPU data This aggregate data display shows utilization data for all CPUsin a cluster. The display aggregates data for all nodes of thecluster onto one page, allowing you to see a cluster-level summaryof data even though CPUs are monitored by a node-level ClusterMonitor Resource.

aggregate data links A link in the Aggregate Data area to see data for all objects inthe cluster on a single page.

aggregate Disk data This aggregate display shows utilization data for all Disks in acluster. The display aggregates data for all nodes of the clusteronto one page, allowing you to see a cluster-level summary ofdata even though Disks are monitored by a node-level ClusterMonitor Resource.

alarm User configurable notification displayed in the banner of HPSystems Insight Manager when certain events happen. Forinstance, if a monitored item changes, an alarm notifies the userthat a change has occurred.See Also trap, event.

all events Systems where any event types have occurred.

All Tools toolbox A default toolbox that provides complete access to all tools forthe authorized system or system group.

attribute A single characteristic of a manageable product or component,as in an attribute of a Management Information Format (MIF) file.A set of related attributes constitutes a group. For example, theclock speed of a processor chip is an attribute of a group thatdescribes that chip.See Also Management Information Format.

authorizations A mapping of a relationship between a user, a toolbox, and asystem or system group.

automatic discovery The process that HP Systems Insight Manager uses to find andidentify the systems on your network and populate the databasewith that information. A system must first be discovered in orderto collect data and track system status.

banner The section of the graphical user interface at the top of the screenthat shows status information and provides access to HP SystemsInsight Manager home page and logout functions.

65

blade server A server that is located in a rack or enclosure.

blade server visual locator This feature is designed to provide visual representation of ProLiantBL e-class and p-class servers within their respective enclosuresand racks.

categories The method for grouping system or event searches.

caution A note to indicate that failure to follow directions could result indamage to equipment or loss of information.

central management server(CMS)

A system in the management domain that executes the HP SystemsInsight Manager software. All central operations within HPSystems Insight Manager are initiated from this system.

central processing unit pollingrate

The rate for how often the Cluster Monitor CPU Resource checksCPU utilization as reported by HP Insight Manager Agents onmonitored nodes.

certificate An electronic document that contains a subject's public key andidentifying information about the subject. The certificate is signedby a Certification Authority (CA) to bind the key and subjectidentification together.

certificate authority (CA) A trusted third-party organization or company that issues digitalcertificates used to create digital signatures and public-privatekey pairs. The role of the CA in this process is to guarantee thatthe individual who has been granted the unique certificate is theindividual they claim to be.

cleared status Systems with cleared status.

clearing events Removing events from the event list. You can remove all eventsexcept discovered system events.

clients HP desktop, portable, and workstation systems.

cluster A cluster is a parallel or distributed computing system made upof a number of discrete systems that form a single, unifiedcomputing resource. Clusters vary in their features, complexity,and the purposes for which they are best suited.

cluster system identification Information about cluster systems. This information is stored inthe database.

cluster information area A display area that shows the control data for a specific cluster.Control data is location, IP address, operator name, phone, email,and pager.

cluster information fields Information fields referencing the cluster.

cluster IP address The IP address of the cluster.

cluster monitor A core component of HP Systems Insight Manager. ClusterMonitor adds the ability to monitor and manage multi-node

66

Glossary

clusters. Cluster Monitor also manages multiple cluster platformsin a heterogeneous environment.

cluster monitor resource A program that provides a monitoring or management functionfor clustered nodes in a cluster.

cluster settings page The page used to enter problem reporting and administrativeinformation for the clusters you manage. This information isdisplayed:

● in the Cluster Monitor Data Viewer when you select the clusterfrom the hierarchy tree

● in notices generated about the cluster

cluster tree view Also known as tree topology. A window that is displayed at thetop left of the Cluster Monitor page. This page displays a treelist of all clustered or managed nodes that the administrator isresponsible for. Each tree item is color coded to reflect status.

command line interface (CLI) The set of commands that can be executed directly from theoperating system's command shell.

common information model(CIM)

An object-oriented schema defined by the Desktop ManagementTask Force (DMTF). CIM is an information model guide thatdescribes and shares management information enterprise-wide.CIM is designed for extending each management environmentin which it is used.

communications protocol See management protocol.

configuration history report The Survey Utility that contains reports that show configurationdetails for server and compares configuration history files fordifferences.

control tasks Sequences of instructions that are associated with a search and/orevent, such as Delete Events, Remove Disk Thresholds, Set DiskThreshold, and Set Device Access community strings.

critical status A state generated when HP Systems Insight Manager can nolonger communicate to a managed system.

custom commands Task to launch an application on the server that is running HPSystems Insight Manager.

data collection reports HP Systems Insight Manager supports Overwrite existing data set(for detailed analysis) formally known as Single Instance DataCollection task Insight Manager 7 and Append new data set (forhistorical trend analysis) formally known as Historical DataCollection task Insight Manager 7. With Overwrite existing dataset (for detailed analysis), data is collected from a system at asingle instance. With Append new data set (for historical trendanalysis), data detailing the system's history is collected.

67

Glossary

data collection tasks Involves gathering information from a group of managed systemsand storing that information in the database. HP Systems InsightManager uses Device Polling and Data Collection Tasks toimplement collection.

database All collected data is stored in the SQL Server. The database canbe local or remote.

Desktop ManagementInterface (DMI)

An industry standard protocol, primarily used in clientmanagement, established by the DMTF. DMI provides an efficientmeans of reporting client system problems. DMI-compliantcomputers can send status information to a central managementsystem over a network.

Desktop ManagementTaskforce (DMTF)

An industry standard body that defines DMI and WBEM standardsfor the industry. HP is an active sponsor and participant in theDMTF body.

digital signatures A technology used to validate a transaction ’s sender. Thistechnology uses private-keys to digitally sign the data, andpublic-keys to verify the sender.

discovery Feature within a management application that finds and identifiesnetwork objects. In HP’s management applications, discoveryfinds and identifies all the HP systems within a specified networkrange.

discovery filters Used to provide users with full configuration rights with amechanism to prevent (or allow) certain system types from everbeing added to the database.

Distributed Component ObjectModel (DCOM)

An extension of the Component Object Model (COM) that allowsCOM components to communicate between clients and serverson the same network.

distributed task facility (DTF) A management application that manages the remote executionof tasks on managed systems.

DMI See Desktop Management Interface.

document type definition(DTD)

A file that identifies the elements and attributes that can be usedto create the content of an XML document. It identifies where eachelement is allowed and which elements can appear within otherelements.

Domain Name Service (DNS) A service that translates domain names into IP addresses.

edit list The modifying of existing lists to add or remove search criteria.

email notification One of the notification tasks in HP Systems Insight Manager. Usethis type of task to send notifications through email. If two usersare adding, editing, or deleting a task simultaneously, the taskreflects the changes from the last user who saves the task.

enclosure A physical container for a set of Blades. It consists of a backplane that routes power and communication signals, and

68

Glossary

additional hardware for cabling and thermal issues. It also hoststhe CPU's or server's power supplies.

encryption The process in which data is converted into a form, which isapparently random and meaningless, usually involving a secretkey. The data is nearly impossible to recover without the correctkey.

event Information sent to certain users that something in the managedenvironment has changed. Events are generated from SNMPTraps. The traps are pre-configured in this release. HP SystemsInsight Manager receives a trap when an important event occurs.Events are defined as:

● Informational—Events of this type require no attention. Theyare provided as useful information.

● Normal—Events of this type indicate that this event is not aproblem.

● Minor— Events of this type indicate a warning condition thatcan escalate into a more serious problem.

● Major—Events of this type indicate an impending failure.● Critical—Events of this type indicate a failure and signal the

need for immediate attention.

event overview A Chart that summarizes the uncleared events by product type.

extensible markup language(XML)

A simplified subset of Standard Generalized Markup Language(SGML) that offers extensible data modeling capabilities.

external sites Third-party application URLs

full configuration rights user A user who is automatically authorized for the All Tools toolboxon all systems including the CMS. This type of user has beengiven special privileges to administer the HP Systems InsightManager software.

graphical user interface (GUI) A program interface that takes advantage of the computer'sgraphics capabilities to make the program easier to use. HPSystems Insight Manager's GUI is Web-enabled and displays ina Web browser.

group See node group.

ProLiant Essentials License Key A license is the contractual permissions granted by HP to thecustomer that is embodied by a license agreement. A license isa legal contract. A license key is the coded embodiment of alicense that represents a specific instance of a license. A singlelicense may be represented by a single key or by a collection ofkeys.

hosts files All critical system information from the HP Systems InsightManager database, such as IP addresses.

HyperText Transfer Protocol(HTTP)

The underlying protocol used by the World Wide Web.

69

Glossary

identification An aspect of the discovery process that identifies the managementprotocol and type of system.

initial configuration wizard Step-by-step, on-line guidance for performing the initialconfiguration of HP Systems Insight Manager.

Internet Server ApplicationProgram Interface (ISAPI)

An application-programming interface, created by ProcessSoftware and Microsoft, tailored to Internet servers. ISAPI usesthe dynamic link libraries (DLLs) in Microsoft Windows to makeprocesses run faster than under regular APIs.

IP range Systems with an IP address that falls in the specified range.

IPSec An infrastructure to allow secure communications (authentication,integrity, confidentiality) between systems and devices thatimplement the IPSec family of protocol standards.

ISAPI See Internet Server Application Program Interface.

Java database connectivity(JDBC)

Similar to ODBC, this set of APIs provides a standard mechanismto allow Java applets access to a database.

Java Remote MethodInvocation (RMI)

A set of protocols that enable Java objects to communicateremotely with other Java objects.

key A value used either alone or with an encryption decoder(corresponding Public or Private Key) for cryptography. Intraditional Private Key cryptography, the communicators wouldshare a key or cipher so that each could encrypt and decryptmessages. The risk in this system is that if any party loses the key,the system will be broken. In Public Key cryptography, the PrivateKey is associated with a Public Key, so each person in the systemhas a personal Private Key that is never shared.

keystore A database that maintains a list of keys. The keystore can containa subject's own Private Key. A keystore can also contain a list ofPublic Keys, as published in certificates.See Also key.

limited configuration rightsuser

A user who has limited capability to configure the CMS. Limitedconfiguration rights users have permission to create, modify, anddelete all reports and their own tools.

major status Aggregate status information collected from the system indicatesthat one or more of the monitored subsystems are not operatingproperly and that this is impacting the system. Action should betaken immediately.

managed systems Any system managed by HP Systems Insight Manager, such asservers, desktops, and RIB.

managed node Also known as a cluster node. A configured cluster system wherethe HP Systems Insight Manager Cluster Monitor is monitoringactivities.

70

Glossary

Management InformationBase (MIB)

The data specification for passing information using the SNMPprotocol. A MIB is also a database of managed objects accessedby network management protocols.

Management InformationFormat (MIF)

An ASCII text file in the DMI architecture that describes a product'smanageable features and attributes. The DMI maintains thisinformation in a MIF database and makes it available to operatingsystems and management applications. The DMTF has specifiedMIF formats for a variety of system types and peripheral systems.

management agent A daemon or process running on a managed system. It receivesand executes requests from the CMS on the managed system.

management domain A collection of resources called managed systems that have beenplaced under the control of the HP Systems Insight Manager. Eachcentral management server is responsible for a managementdomain. The managed systems can belong to more than onemanagement domain.

management instrumentation Agents running on systems that provide management informationfor HTTP, DMI, or SNMP protocols.

management LAN A LAN dedicated to the communications necessary for managingsystems. It is typically a moderate bandwidth (10/100 baseT)and secured through limited access.

management protocol A set of protocols such as WBEM, HTTP, SNMP or DMI toestablish communication with discovered systems.

management scope A set of systems within the set of all discovered systems that HPSystems Insight Manager is responsible for managing.

management services Provider of a core set of capabilities such as auto-discovery, datacollection, a central repository for system and event information,event management, basic notification, and secure access. Theseare used by add-ins from HP, a Management Solutions Partner,and/or HP Systems Insight Manager end-users.

management tasks Procedures you set up to search systems or events.

manual discovery techniques Manual discovery lets you bypass a full discovery for the followingtasks:

● add a single system● edit the system● create or import a HP Systems Insight Manager database

hosts file● create or import generic hosts name files

master role A default role that has access to all tools. All tools areautomatically associated with the master role, and the master rolecannot be deleted from HP Systems Insight Manager.

Microsoft Clustering Servicestatus page

A page that summarizes cluster status as defined by MicrosoftCluster Server and lists the status and values of MSCS-defined

71

Glossary

cluster attributes. The Cluster Monitor uses color to display statusbased on MSCS condition values (OK, Degraded, Major, Critical,or Unknown).

Monitor Tools toolbox A default toolbox that contains tools that display the state ofmanaged systems, but not tools that change the state of managedsystems.

minor status Aggregate status information collected from the system indicatesthat one or more of the monitored subsystems are not operatingproperly and that this is impacting the system. Action should betaken as soon as possible to prevent further failure.

multiple-system aware (MSA) A run type that supports multi-system operations. Tools with thisrun type operate on the target nodes using their own internalmechanisms instead of using the distributed task facility. The MSArun type uses the distributed task facility to launch the tool on asingle node prior to the tool interacting with the other managednodes.

no configuration rights user A user who cannot configure the CMS. No configuration rightsusers' ability to manage systems are based on their authorizations.

node Any system on the network that can communicate with HP SystemsInsight Manager including servers, printers, workstations, hubs,and routers. Nodes must be added to an HP Systems InsightManager management domain, and they can be assigned to oneor more node groups by a trusted user.

node group A group of nodes defined by a trusted user to divide a networkinto manageable units. Nodes in a node group usually havesomething in common like OS type, backup schedule, applicationtype, or hardware type.

racks Set of components cabled together to communicate betweenthemselves. A rack is a container for an enclosure.

remote wakeup Sometimes referred to as Wake-On-LAN (WOL). The remotepowering up of a system through its resident Wake-On-LAN(WOL) network card, provided that the system has been ENABLEDto be so “awaken” via its ROM or F10 Setup.

This is a capability HP Systems Insight Manager relies on to turnon the systems for scheduled Software Updates or Replicate AgentSettings.

remove all Disk thresholds A control task provided by HP Systems Insight Manager. Toremove Disk thresholds for systems in an associated list. This taskonly removes Disk thresholds that were set by HP Systems InsightManager or by browsing directly to the Web agent. Anythresholds set by HP Systems Insight Manager for Windows 32,including Disk thresholds, are not removed by this task.

Replicate Agent Settings A tool that can be used to copy Web-based agent settings to agroup of systems.

72

Glossary

repository The database that stores vital information about the managedcluster including: users, nodes, node groups, roles, tools, andauthorizations.

role A definition of responsibilities related to an operation or process.Each HP Systems Insight Manager role is associated with a setof tools.

role-based management A system that uses roles to limit the tools users can access.

rule set Conditions or policies or criteria applied to system informationto determine what it is.

search criteria A set of variables (information) used to define a requested subsetof information from the set of all information. The information setthat can be filtered includes action information, some of thesystem's information, and so on. A filter is composed of aninclusion filter followed by an exclusion filter. The result of thesetwo filtering operations is called a group. An example of a filteris a SQL statement that creates viewable information or causesmanagement operations to be performed.

Secure HTTP (HTTPS) An extension to the HTTP protocol that supports sending datasecurely over the Web.

Secure Shell (SSH) A program to log into another system over a network and executecommands on that system. It also enables you to move files fromone system to another, and it provides authentication and securecommunications over insecure channels.

Secure Sockets Layer (SSL) A standard protocol layer that lies between HTTP and TCP andprovides privacy and message integrity between a client andserver. A common usage of SSL is to provide authentication ofthe server, so the client can be assured he is talking to whom theserver claims to be. It is application protocol independent.

Secure Task Execution (STE) Secure execution of a task from a managed device. This featureof HP Systems Insight Manager ensures that the user requestingthe task has the appropriate rights to perform the task, and willencrypt the request to protect data from snooping.

security roles A feature that enables administrators to restrict system access andmanage access on a per-user or per-group basis. This capabilityallows systems administrators to delegate tasks to junior staffwithout providing access to advanced or dangerous features. Italso allows systems administrators to delegate management ofsystems to specific organizations or customers without providingaccess to systems owned by other organizations or customers.

self-signed certificate A certificate that is its own Certificate Authority (CA), such as thesubject and the CA are the same.See Also certificate, certificate authority.

73

Glossary

set Disk thresholds A control task provided by HP Systems Insight Manager to set aDisk threshold for systems in an associated list. This threshold isset on all Disk volumes on the target system.

short message service (SMS) SMS is a convenient way to send brief text messages directoryto a wireless phone. There is a maximum message length of 140characters.

Simple Network ManagementProtocol (SNMP)

One of the management protocols supported by HP SystemsInsight Manager. Traditional management protocol usedextensively by networking systems and most servers. MIB-2 is thestandard information available consistently across all vendors.

single login Permission granted to an authenticated user browsing to HPSystems Insight Manager to browse to any of the managedsystems from within HP Systems Insight Manager withoutre-authenticating to the managed system. HP Systems InsightManager is the initial point of authentication and browsing toanother managed system must be from within HP Systems InsightManager.

single-system aware (SSA) A run type that does not support multi-node operations. Tools withthis run type are only aware of the node they are running on.

SNMP communication setting Default SNMP community string used when communicating withsystems supporting SNMP communications.

SNMP trap Asynchronous event generated by SNMP agent at the systemused to communicate a fault.

software update A task to remotely update software and firmware.

spoofing A Web site posing as another site to gather confidential orsensitive information, alter data transactions, or present false ormisleading data.

standard output (stdout) The default place to which a program writes its output. The defaultis the terminal display.

standard error (stderr) The default place where the system writes error messages. Thedefault is the terminal display.

status messages Listed in order of descending priority (critical, warning, major,unknown, advisory) and decreasing age (oldest, longestoutstanding alerts first; most recent alerts last). So, the oldestcritical message appears first followed by more recent criticalmessages, then the oldest warning message followed by morerecent warnings, then the oldest unknown status message followedby more recent unknown status messages.

Each status message is a link to a display of relevant information.Click on a message to display this information in the Data Viewerarea.

status message list Found in the bottom-left area of the Cluster Monitor page. ClusterManagement Resources add entries, called status messages, to

74

Glossary

this list to bring your attention to cluster attributes that are in anabnormal state.

status message summaryheader

The list header summary of the total number of status messagesin the list and, in parentheses, the number of status messages thathave not been examined.

status type Systems of specified status type (Critical, Major, Minor, Normal,and Unknown).

survey utility An agent (or online service tool) that gathers and delivershardware and operating system configuration information. Thisinformation is gathered while the server is online.

symmetric key This is a common key that both the server and receiver of amessage share and use to encrypt and decrypt a message.

system Nodes on the network that communicate via TCP/IP or IPX. Tomanage a system, some type of management protocol—SNMP,DMI, WBEM—must be present on the system. Examples of systemsinclude servers, workstations, desktops, portables, routers,switches, hubs, and gateways.

system default searches Requests for data about aggregate system status, proactivesubsystem status, and detailed component information on servers,workstations, desktops and portables, irrespective of managementprotocol.

system identification Identifying information about systems. This information is storedin the database. The following information is identified:

● type of management protocol on the system (HTTP, SNMP,DMI)

● type of HP system (server, client, switch, router, and so on)● network name of system

system information Information that is provided on the System Page under theIdentity tab. The system information includes:

● network address● network name● description● contact● location● system links

system information using DMI Agents that conform to the DMI V2 standard and have passedtesting. The list of compliant DMI V2 agents can be found onhttp://www.dmtf.org.

system information usingSNMP

Agents that conform to SNMP MIB-2 standards.

75

Glossary

system links A summary information page for a specific system that has amanagement agent.

system overview report A report indicating the state of systems that is available at thetime that HP Systems Insight Manager is first opened. A systemsearch result contains the number of systems that are registeredwith the HP Systems Insight Manager databases. Systems aregrouped by their status condition. Each underlined number in acolumn is a hyperlink to a more detailed list of systems, whichdisplays the systems that correspond to the number in theoverview.

system search Logical grouping of systems into a collection based on informationin the HP Systems Insight Manager database. After a search isdefined, you can display the results from the system view pageor associate it with a management task.

system search results The result of a search.

system status The operating state of SNMP-based devices. A system's status isdetermined by polling SNMP information from the system. Thisis the same as hardware status. Status is defined as:

● Critical-HP Systems Insight Manager can no longercommunicate with the system. The system was previouslydiscovered, but cannot be pinged. The system may be down,powered off, or no longer accessible on the network due tonetwork problems.

● Major-a problem exists● Minor-functioning but with errors● Normal-functioning correctly● Unknown

system type One of 12 supplied types. You can add your own based on oneof these types. Use Server type to create MyServer type. It is stilla server and is reported on in the same way, but it has yourdesignation.

System Type Manager (STM) A utility that enables you to modify the default behavior ofdiscovery and identification so objects classified as Unknown oras another category of systems are discovered and identifiedprecisely as you require. HP Systems Insight Manager discoversand identifies the system and applies the new information whenan Unknown system matches a rule set that you specify as theprimary rule set. Furthermore, creating the new system typeprovides a System Link page for viewing the information returnedfrom the system agent or from the communication protocol ofSNMP or DMI.

task An executed instance an HP Systems Insight Manager tool, onone or more systems or systems groups, with a specific set ofarguments.

76

Glossary

task scheduling A master scheduling tool for the scheduling of Polling, Control,and Notification Tasks.

threshold A present limit that produces an event when the limit is reachedor exceeded.

Timed Event An action that schedules necessary events. Examples of eventsinclude backups, Disk storage cleanup, and so on. The userdefines the tools in this category.

Tomcat An open source implementation of Java Servlet and JavaServerPages technologies that is used by HP Systems Insight Manageras a Web server.

tool An application, command, or script that can be executed by HPSystems Insight Manager on one or more systems to perform atask.

tool category An organizational structure for grouping tools. A tool must belongto one and only one category. Tool categories can only containtools; they cannot contain other tool categories.

toolbox A defined set of tools that a user might need for a particular task,such as database administration or software management.

trap An unsolicited message generated by a management agent thatindicates that an event has occurred. For example, a monitoreditem has exceeded a set threshold or changed status. Previouslycalled alarm.See Also event.

trap categories Event list systems found by event type. SNMP traps categorizedby HP Systems Insight Manager into logical groups according totheir function.

trap forwarding address The IP address of a machine that has been specified to receivetrap notifications forwarded by the HP Systems Insight Managersystems.

trusted user A privilege given to one or more users. Trusted users administerthe HP Systems Insight Manager software to enable other usersto manage network resources.

type Systems identified with the standard system types. The systemtypes are client, cluster, portable, printer, remote access device,repeater, router, server, switch, unknown, workstation, and other.

unknown status HP Systems Insight Manager is not able to obtain managementinformation about the system using SNMP or DMI. Although nomanagement instrumentation information is available, the systemcan be pinged. It may have an invalid community string or securitysetting.

uncleared event status Events that have a critical, major, minor, or normal severity.

77

Glossary

Critical—HP Systems Insight Manager can no longercommunicate with the system. The system was previously

●

discovered, but cannot be pinged. The system may be down,powered off, or no longer accessible on the network due tonetwork problems.

● Major—a problem exists● Minor—functioning but with errors● Normal—functioning correctly

user A network user with a valid login on the CMS that has beenadded to HP Systems Insight Manager.

user accounts Accounts used to login to HP Systems Insight Manager. Theseaccounts associate a local Windows user account or a domainaccount with privilege levels and paging attributes inside HPSystems Insight Manager.

user configuration page A page in HP Systems Insight Manager that provides the abilityto create and define users that have access to the managementapplication and associate rights.

version control A feature that checks the versions of HP operating system drivers,HP Systems Insight Manager Agents, HP utilities, and firmwareon the user's system. It compares them with the Version ControlDatabase (VCDB) of current software and firmware versions.Version Control then indicates that the software is up-to-date orthat an upgrade is available, and provides reasons for upgrading.

Version information appears as a system link for a system.

Version Control Agent (VCA) The Version Control Agent is an agent that is installed on a serverto allow the customer to see the HP software installed on thatserver. The Version Control Agent can be configured to point toa Version Control Repository Manager agent, allowing easyversion comparison and software update from the repository.

Version Control RepositoryManager (VCRM)

An HP agent that allows a customer to manage HP providedsoftware stored in a user-defined directory/repository.

WBEM Services HP WBEM Services for HP-UX - A Hewlett-Packard product thatuses WBEM and DMTF standards to manage HP-UX systemresources.

Web-Based EnterpriseManagement (WBEM)

An initiative based on a set of management and Internet standardtechnologies developed to unify the management of enterprisecomputing environments.

Web-launch aware (WLA) A run type for tools that are launched in a Web browser usinga Web server. WLA tools can be designed to deal with multiplesystems.

Windows ManagementInstrumentation (WMI)

An API in the Windows operating system that enables devicesand systems in a network, typically enterprise networks, to bemanaged and controlled.

78

Glossary

workspace The section of the graphical user interface where tools display.

X client An application or tool that displays on an X server. X clients canalso called X applications.

X server A local application that accepts X client requests and acts uponthem.

X Window System A cross-platform windowing system that uses the client/servermodel to distribute services across a network. It enablesapplications or tools to run on a remote computer.

XML See extensible markup language.

XML document A collection of data represented in XML.

79

Glossary

IndexAaccess the graphical user interface, 36active time-out, 60add authorizations, 58add toolboxes, 57add users, 53All Tools toolbox, 6audit log, 8

configure, 61authorizations, 5

add, 58automatic discovery, 51automatic event handling, 55

Bbanner

customize, 39

Ccentral management server

HP-UX kernel tuning, 20HP-UX system preparation, 21install HP Systems Insight Manager on HP-UX, 21install HP Systems Insight Manager on Linux, 28install HP Systems Insight Manager on Windows, 33Linux system preparation, 25overview, 1remove HP Systems Insight Manager on HP-UX, 23remove HP Systems Insight Manager on Linux, 31remove HP Systems Insight Manager on Windows, 35requirements, 14Windows system preparation, 33

certificate authority, 12CMS (see central management server)command line interface

log in, 41security, 9

commands, 41comments, 2communication protocols (see management protocols)configuration

add authorizations, 58add toolboxes, 57add users, 53audit log, 61automatic event handling, 55data collection CPU utilization, 59

discovery, 51email settings, 55lifetimes for Task Result entries, 63managed system, 45paging settings, 55protocol settings, 50time-out policy, 60

configuration options, 59configuration rights

full, 7limited, 7no, 7

configure email settings, 55configure paging settings, 55contact information, 2conventions, typographic, 2CPU utilization, 59customization options, 59customize the graphical user interface, 39

Ddatabase, 8

remote for improved performance, 59data collection

performance, 59default time-out period, 60default toolboxes, 6Desktop Management Interface, 11discovery, 51Distributed Task Facility, 10DMI, 10–11DTF, 10

Eemail

configure, 55event handling, 55

Ffeatures, 1feedback form, 2firewalls, 12firewalls ports, 12first setup (see initial setup)frequently scheduled task lifetimes, 63full configuration rights user, 7

Ggetting started, 45graphical user interface

customize, 39log in, 36

80

security, 9

HHome page

customize, 39HP Systems Insight Manager

commands, 41features, 1

HP Systems Insight Manager database, 8HP-UX CMS

installation and configuration, 21kernel tuning, 20remove HP Systems Insight Manager, 23system preparation, 21

HP-UX managed systemsetup, 45

HTTPS, 10–11

Iinitial setup, 45

add authorizations, 58add toolboxes, 57add users, 53automatic discovery, 51automatic event handling, 55configure email settings, 55configure paging settings, 55discovery, 51managed systems, 45manual discovery, 53protocol settings, 50

Insight Manager 7 comparison, 1install

central management server requirements, 14managed system requirements, 16network client requirements, 18process overview, 13

install HP Systems Insight ManagerHP-UX CMS, 21Linux CMS, 28Windows CMS, 33

Llast result task lifetimes, 63lifetimes for Task Result entries, 63limited configuration rights user, 7Linux CMS

installation and configuration, 28remove HP Systems Insight Manager, 31system preparation, 25

Linux managed systemsetup, 47

log in

command line interface, 41graphical user interface, 36

Mmanaged node (see managed system)managed system

discovery of, 51overview, 1protocol settings on the CMS, 50requirements, 16setup, 45

management domainoverview, 1

management protocols, 10DMI, 11HTTPS, 11SNMP, 11SSH, 10WBEM, 11

manpages, 41manual discovery, 53monitor time-out, 60Monitor Tools toolbox, 6

Nnetwork client

overview, 1requirements, 18supported Web browsers, 18

new features, 1no configuration rights user, 7node (see managed system)node group (see system group)

Ppaging

configure, 55parameter

DataCollectionThreadCount, 59EnableSessionKeepAlive, 60LOG, 61MX_JOB_CACHE_TIME_COMPLETED_JOBS, 63MX_JOB_MAX_COMPLETED_JOB_AGE, 63MX_JOB_MAX_COMPLETED_JOBS_PER_TASK, 63MX_JOB_MIN_COMPLETED_JOBS_PER_TASK, 63MX_LOG_FILEEXT, 61MX_LOG_FILENAME, 61MX_LOG_FILESIZE, 61MX_LOG_QUEUESIZE, 61MX_LOG_ROLLFILEEXT, 61session-timeout, 60

ports, 12protocols, 10

81

Index

protocol settings, 50

Rremove HP Systems Insight Manager

HP-UX CMS, 23Linux CMS, 31Windows CMS, 35

repository (see database)requirements

central management server, 14managed system, 16network client, 18

SSecure HTTP, 11Secure Shell , 10security

access, 9certificate authority, 12command line interface, 9firewalls, 12graphical user interface, 9ports, 12self-signed certificates, 12Web server, 12X applications, 12

self-signed certificates, 12Servicecontrol Manager 3.0 comparison, 1setup

add authorizations, 58add toolboxes, 57add users, 53automatic event handling, 55configure email settings, 55configure paging settings, 55discovery, 51HP-UX managed systems, 45initial, 45Linux managed systems, 47managed systems, 45protocol settings, 50Windows managed systems, 48

short and long task lifetimes, 63Simple Network Management Protocol, 11SNMP, 10–11spoofing, 12SSH, 10system group

overview (see )

TTask Results Page

entry lifetime configuration, 63

time-out policyconfiguration, 60

toolboxes, 5add, 57

tools, 7command line, 7Web, 7X Window, 7

types of tools, 7typographic conventions, 2

UU.S. Government License, 2users

add, 53add authorizations, 58

Wwarranty, 2WBEM, 10–11Web Based Enterprise Management, 11Web browser

requirements, 18Web server security, 12Windows CMS

installation and configuration, 33remove HP Systems Insight Manager, 35system preparation, 33

Windows managed systemsetup, 48

XX application security, 12

82

Index

SIM Install

Documents

Transcript of SIM Install