HP Systems Insight Manager 4.2 Installation and User Guide€¦ · HP Systems Insight Manager can be extended to provide system management with plug-ins for HP clients, storage, power,

HP Systems Insight Manager 4.2Installation and User Guide

Manufacturing Part Number: 5991-0710

November 2004, Edition 1.3

©Copyright 2004 Hewlett-Packard

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 errors containedherein or direct, indirect, special, incidental, or consequential damages in connection with the furnishing, performance, oruse 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-2004 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 NoticesAdobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

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.

Intel® and Itanium® are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United Statesand other countries.

Linux® is a U.S. registered trademark of Linux Torvalds.

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

Microsoft®, Windows®, and Windows NT® are U.S. registered trademarks of Microsoft Corporation.

UNIX® is a registered trademark of The Open Group.

Red Hat® is a registered trademark of Red Hat, Inc. in the United States and other countries.

SuSE® is a registered trademark of SuSE Linux AG.

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

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

Typographic ConventionsWe use the following typographical conventions.

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

Features ................................................................................................................ 7What's New ........................................................................................................ 10Product Architecture .............................................................................................. 11Authorizations ...................................................................................................... 13

Default Toolboxes ......................................................................................... 14User Privileges .............................................................................................. 14

Tools ................................................................................................................... 15Information Storage .............................................................................................. 15

HP Systems Insight Manager Audit Log ............................................................ 15Database ..................................................................................................... 16

Database Software ................................................................................ 16Secure Access ...................................................................................................... 16

Command Line Interface ................................................................................ 16Graphical User Interface ................................................................................ 17

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

2. Installation Overview and Requirements ...................................................................... 21Process Overview ................................................................................................. 21System Requirements ............................................................................................. 22

CMS Requirements ........................................................................................ 22HP-UX Central Management Server ......................................................... 22Linux Central Management Server ........................................................... 23Windows Central Management Server .................................................... 24

Managed System Requirements and Recommendations ..................................... 25Network Client Requirements and Recommendations ......................................... 27

SSH Requirements ................................................................................................. 283. Installing on Windows .............................................................................................. 30

Preparing the System ............................................................................................. 30Installing and Configuring the Software ................................................................... 31Next Steps ........................................................................................................... 40Windows Installation Options ................................................................................ 41

4. Installing on HP-UX ................................................................................................... 42Optimizing the Operating Environment (Kernel Tuning) ............................................. 42Preparing the System ............................................................................................. 43Installing and Configuring the Software ................................................................... 44Next Steps ........................................................................................................... 46

5. Installing on Linux ..................................................................................................... 47Preparing the System ............................................................................................. 47Installing and Configuring the Software ................................................................... 50

Manually Installing HP Systems Insight Manager ............................................... 50Automatically Installing HP Systems Insight Manager ........................................ 51After Installing HP Systems Insight Manager ..................................................... 52

Next Steps ........................................................................................................... 536. Upgrading from Compaq Insight Manager 7 Service Pack 2.3 to HP Systems InsightManager 4.2 ............................................................................................................... 54

Types of Migration ................................................................................................ 55

4

Performing an In-Place Migration ............................................................................ 55Performing a Remote Migration .............................................................................. 57

7. Upgrading HP Systems Insight Manager 4.0, 4.0.1 and 4.1 to HP Systems Insight Manager4.2 ............................................................................................................................. 60

Serviceguard Manager scenarios ........................................................................... 60Upgrading HP Systems Insight Manager 4.0 or 4.1 to HP Systems Insight Manager 4.2on Windows ........................................................................................................ 62Upgrading HP Systems Insight Manager 4.0. or 4.1 to HP Systems Insight Manager4.2 on HP-UX ....................................................................................................... 71Upgrading HP Systems Insight Manager 4.0.1 or 4.1 to HP Systems Insight Manager4.2 on Linux ........................................................................................................ 72

8. Upgrading from HP Servicecontrol Manager to HP Systems Insight Manager ................... 73Upgrading from SCM 3.0 to HP Systems Insight Manager 4.2 ................................... 74Upgrading Existing Managed Systems .................................................................... 78

9. Uninstalling HP Systems Insight Manager ..................................................................... 80Uninstalling HP Systems Insight Manager from a Windows System ............................. 80Uninstalling HP Systems Insight Manager from an HP-UX System ................................. 80Uninstalling HP Systems Insight Manager from a Linux System .................................... 82

10. Using the Graphical User Interface ........................................................................... 83Accessing the GUI ................................................................................................ 83

Required Java Plug-in .................................................................................... 83Graphical User Interface Features ........................................................................... 84Default Home Page Features .................................................................................. 85Customizing the GUI ............................................................................................. 86

Customizing the Home Page .......................................................................... 86Customizing the Banner ................................................................................. 86

11. Using the Command Line Interface ............................................................................ 88Logging into the CLI .............................................................................................. 88

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

HP Systems Insight Manager Commands ................................................................. 8912. Initial Setup ........................................................................................................... 92

Introduction .......................................................................................................... 92Setting Up Managed Systems ................................................................................. 92

Setting Up HP-UX Managed Systems ............................................................... 92Setting Up Linux Managed Systems ................................................................. 94Setting Up Windows Managed Systems .......................................................... 96

Configuring Protocol Settings ............................................................................... 101Configuring and Executing Discovery .................................................................... 102

Configuring and Executing Automatic Discovery ............................................. 102Configuring and Executing Manual Discovery ................................................ 104

Adding Users ..................................................................................................... 105Configuring Email Settings ................................................................................... 106Configuring Paging Settings ................................................................................. 107Setting Up Automatic Event Handling .................................................................... 107Adding Toolboxes .............................................................................................. 109Adding Authorizations ........................................................................................ 110

13. Migrating Version Control to the System Management Homepage .............................. 111System Management Homepage Migration Overview ............................................. 111

Migrating the Version Control Agent and the Version Control Repository Managerfrom Management HTTP Server to System Management Homepage to useOperating System Authentication .................................................................. 112

14. Configuration Options .......................................................................................... 115CPU Utilization During Data Collection .................................................................. 115

5

HP Systems Insight Manager 4.2 Installation and User Guide

Overview ................................................................................................... 115Implementation ........................................................................................... 116

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

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

Lifetimes for Entries on the Task Results Page .......................................................... 118Overview ................................................................................................... 118Implementation ........................................................................................... 119

15. Reference ............................................................................................................ 120Open Source Components Used in HP Systems Insight Manager .............................. 120

Glossary ................................................................................................................... 122Index ........................................................................................................................ 138

6

HP Systems Insight Manager 4.2 Installation and User Guide

Chapter 1. Product Overview HP 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 value-addedsoftware required to deliver complete lifecycle management for your hardware assets.

FeaturesHP Systems Insight Manager provides the following features:

● Easy and rapid installation. Installs on your server platform of choice running HP-UX,Windows, or Linux, or on a Windows desktop or workstation.

● Automatic discovery and identification. Automatically discovers and identifies systemsattached to the network. Use discovery filters to prevent discovery of unwanted system types.Discovery filters enable you to limit discovery to specific network segments or IP address ranges.

● Fault management and event handling. Provides proactive notification of actualor impending component failure alerts. Automatic event handling enables you to configureactions to notify appropriate users of failures through e-mail, pager, or Short Message Service(SMS) gateway, and enables automatic execution of scripts or event forwarding to enterpriseplatforms such as HP OpenView Network Node Manager or HP OpenView Operations.

Note:

Pager support is only for Windows based central management server (CMS).

● Consistent multi-system management. Initiates a task on multiple systems or nodesfrom a single command on the CMS. This functionality eliminates the need for tedious,one-at-a-time operations on each system.

● Secure remote management. Leverages operating system security for user authentication,and 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.

7

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

● 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. Snapshotcomparisons can also be used to save a picture of standard configuration for comparisons toother systems.

● Version control. Automatically downloads the latest BIOS, driver, and agent updates forHP ProLiant servers running Windows and Linux, identifies systems running out-of-date systemsoftware, and enables system software updates across groups of servers. For HP-UX systems,Software Distributor is integrated into HP Systems Insight Manager.

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

● Data Migration Tool and Upgrade. HP Systems Insight Manager provides a DataMigration Tool to extract data from Insight Manager 7 Service Pack 2.3 and PerformanceManagement Pack data to HP Systems Insight Manager on a Windows system. The DataMigration Tool exports user-defined data from Insight Manager 7 by extracting it and storingthe information in a portable format. The Data Migration Tool then imports that user-definedInsight Manager 7 data into HP Systems Insight Manager. Also available is upgrading fromHP Servicecontrol Manager 3.0 to HP Systems Insight Manager 4.2 on HP-UX systems.

● Install SSH tool. Runs from the central management server (CMS) and installs the OpenSSHservice onto target Windows systems and then runs the mxagentconfig command to completethe configuration.

● Initial ProLiant Support Pack Install now installs OpenSSH. HP Systems InsightManager enables you to install OpenSSH through the Initial ProLiant Support Pack Install processby selecting Install and initialize OpenSSH (Secure Shell) on the Initial ProLiant SupportPack Install page.

● Desktop blade support (BC1000). HP Systems Insight Manager now includes a pictureview of the half-height BC1000 Desktop Blades.

● Support for HP-UX Serviceguard clusters. HP Systems Insight Manager recognizesHP-UX Serviceguard clusters and displays them in the UI. HP Serviceguard Manager is openedby clicking a Serviceguard cluster in a search list, and provides information on the clusters.

● Context launch of portal. The HP Systems Insight Manager portal URL supports beinglaunched with a context. A context consists of two URL parameters: a list of systems and a tool.For example,http://hostname:280/mxportal/MxContextLaunch.jsp?systems=ovwpc012,ovwpc013&tool=Ping.This capability enables an environment such as HP OpenView to launch the HP Systems InsightManager portal in a more integrated fashion than bringing up the Home page in the browser.You are still required to log into the portal, after which the portal automatically selects the givensystems and automatically launches the given tool.

8

Product Overview

● WBEM Indications from HP-UX. HP Systems Insight Manager enables you to subscribeand unsubscribe to WBEM indications through the graphical user interface (GUI). You can alsosubscribe or unsubscribe to WBEM indications from the command line interface (CLI).

● WBEM Property pages for HP-UX and Linux. WBEM Property Page links for CPUand Memory have been added in the status and configuration pages for the HP-UX platform.A full compliment of WBEM Property Pages have been added for the RedHat Linux IPF platform.

● Alternate ping using TCP. Select Use the TCP protocol for system reachable (ping)check. port number 80 on the Global Protocol Settings page if your company has disabledICMP on the corporate network or the corporate policy mandates system firewall software tofilter out ICMP requests. For example, Windows XP has this feature built in and can result insystems not being automatically discovered. This option enables you to run HP Systems InsightManager and ping all available systems.

● System Management Homepage. The System Management Homepage is a Web-basedapplication that provides a consolidated interface for single system management. By aggregatingthe data from HP web-based agents and management utilities, the System ManagementHomepage provides a common, easy to use interface for displaying hardware fault and statusmonitoring, performance data, system thresholds, diagnostics and software version control foran individual server.

● Performance Management Pack (PMP) access. A software solution that detects,analyzes, and explains hardware bottlenecks on HP ProLiant servers. PMP tools available inHP Systems Insight Manager consist of Online Analysis, Offline Analysis, CSV File GeneratorReport, System Summary Report, Static Analysis Report, Configuration, Licensing, and ManualLog Purge. For HP-UX users, PMP and GlancePlus are integrated into HP Systems Insight Managerfor monitoring system performance.

● HP ProLiant Essentials Vulnerability and Patch Management Pack (VPM)access. The Vulnerability and Pack Management Pack identifies and provides advice toresolve security vulnerabilities and delivers advanced patch management through automatedacquisition, optimized deployment, and continuous enforcement of security patches.

● HP ProLiant Essentials Virtual Machine Management Pack (VMM) access. TheVirtual Machine Management Pack extends HP Systems Insight Manager with the ability todeploy, clone, monitor, and control VMWare and Microsoft Virtual Server virtual machines. Toaccess VMM, select Tools->Virtual Machine Management Pack. You then have options toDeploy Windows Agent and Licensing.

● HP BladeSystem Integrated Management. HP Systems Insight Manager delivers anew blade management environment designed to centralize access to blade deployment,configuration, and monitoring tools. To access the HP BladeSystem Integrated Managementenvironment in HP Systems Insight Manager, select Tools->Integrated Consoles->HPBladeSystem. Go to http://www.hp.com/go/hpsim/ to view the BladeSystem IntegratedManagement Guide.

● HP Configure or Repair Agents. A new plug-in feature that enables you to repaircredentials for SNMP settings, System Management Homepage, or Management HTTP Servertrust relationships on Windows systems supported by HP Systems Insight Manager on local orremote systems. Go to http://www.hp.com/go/hpsim/ to view the HP Configure or RepairAgents guide.

9

Product Overview

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


What's NewHP Systems Insight Manager delivers new capabilities for customers who currently use HPServicecontrol Manager (SCM) to manage their HP 9000 and Integrity systems running HP-UX andLinux and those who use Insight Manager 7 to manage their ProLiant servers running Windows,Linux, and NetWare. New features differ depending on whether you use SCM 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 servers and Integrity servers running HP-UX, Linux, and Windows

● 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 on 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, Serviceguard Manager, and HP-UX system administration (for example, kernelconfiguration and user and replicate agent settings)

● 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

New Features for Servicecontrol Manager3.0 Users

HP Systems Insight Manager provides the following added functionality over SCM 3.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

10

Product Overview

● 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 replicate agent settings), 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 (CMS), managed systems, and network clients.)

The CMS and the managed systems together are called the HP Systems Insight Managermanagement domain.

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 a

11

Product Overview

separate system. Typically, servers for the multiple-system aware (MSA) applications also resideon the CMS. These applications are not required to reside on the CMS. They can reside anywhereon the network.

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 IPX address associated with them. A managed system can be managed bymore than one CMS if desired.

Systems to be managed need to have one or more management agents installed. There are a widevariety of agents such as the ProLiant management agents based on SNMP, WMI found on Windowssystems, or WBEM providers such as the System Fault Management providers. Those agents providemanagement information and alerts (indications). The SSH agent and servers will then allow theability of the HP Systems Insight Manager CMS to log into the managed system to executemanagement commands.

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 arbitrary collections 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 step.

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 a Secure Shell (SSH) client application to securelyaccess the command line interface (CLI).

12

Product Overview

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. Aftera user is added to HP Systems Insight Manager, he or she can be authorized to use a toolbox onone or more systems in the management domain.

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 might enable users with non-privileged access (forexample, non-root users or users that are not members of the Windows Administratorsgroup) to run tools as root/administrator or as another specified user. Be carefulwhen granting users permission to run tools as root or administrator. Consider allthe capabilities given by a tool, above and beyond the capabilities it is designedfor, before you associate it with a toolbox.

13

Product Overview

Default ToolboxesThe All Tools toolbox is a default toolbox installed with HP Systems Insight Manager. The AllTools toolbox provides complete access to all tools for the authorized system or system group.When a tool is added to HP Systems Insight Manager, the tool is automatically added to thistoolbox. Tools cannot be removed from the All Tools toolbox, and the All Tools toolbox cannotbe deleted from HP Systems Insight Manager. If you do not want a user to have access to allavailable tools for a specific system or system group, they should not be authorized for the AllTools toolbox on that system or system group.

Caution:

Users assigned the All Tools toolbox on the CMS can execute commands as anyuser. Therefore, these users could grant the full configuration rights user privilege tothemselves.

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.

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 an 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 permission can later be revoked. This user is automatically authorized for the All Tools toolboxon all systems, including the CMS. The full configuration rights user privilege can be given to oneor more users, and HP Systems Insight Manager requires that at least one user is a full configurationrights user.

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.

14

Product Overview

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. Three types of tools are supported in the HP Systems Insight Managerenvironment: 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 amanaged system. HP Systems Insight Managerlaunches the URL from a CLI or GUI. When aWeb tool is launched from the command line,HP Systems Insight Manager opens a browser todisplay the tool. When a Web tool is launchedfrom the HP Systems Insight Manager GUI, itopens in the workspace or in a separate browserwindow.

Web tools

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 CLI or GUI, HP Systems Insight Managerinvokes the X Window application using thecommand line and passes the location of the Xserver by requesting the device for display fromthe user.

X Window tools

Command line tools include applications,commands, and scripts. They can reside on theCMS or another managed system. They can belaunched directly from the CLI or GUI.

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

15

Product Overview

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 andother commands is configurable. In addition, other aspects of the audit log, such as maximum filesize, is also configurable. Information about configuring the audit log is available in Chapter 14. Configuration Options and in the "Administering the Software" section of the HPSystems Insight Manager online 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● 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 2000,which provides more advanced enterprise features.

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

Command Line InterfaceWhen you access HP Systems Insight Manager from the CLI, your operating system login is usedto identify you to HP Systems Insight Manager. You have access to use the HP Systems InsightManager commands based on your authorizations. If you access HP Systems Insight Manager fromany system other than the CMS, be sure you use an SSH client. Programs like telnet, rlogin, andftp do not provide encrypted access. When you use one of these applications to access HP SystemsInsight Manager, your data including your password is transmitted across the network unencrypted.In addition, these protocols are not spoof-protected. If you have a Windows CMS, then onlyadministrators have command line access to HP Systems Insight Manager. A remote desktopconnection to the CMS can be used to access the command line.

16

Product Overview

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 can bereplaced by a certificate that is signed by a trusted certificate authority. Your Web browser shouldimport this certificate to trust the CMS.

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, Web-Based EnterpriseManagement (WBEM), Secure HTTP (HTTPS), Desktop Management Interface (DMI), and SimpleNetwork Management Protocol (SNMP). Tools are not limited to these protocols, and they canprovide a custom management protocol. SSH is the only protocol that must be installed on everymanaged system. Tools require specific protocols, and they can only be run on a managed systemif the protocol they require is installed and configured correctly.

17

Product Overview

SSH . SSH is a program that enables you to log into another system over a network and executecommands on that system. It also enables you to move files from one system to another, and itprovides authentication and secure communications over insecure channels. SSH uses apublic/private key pair to provide a secure mechanism to authenticate and encrypt communication.SSH keys are used to identify the execute-as user on the managed system. Typically, the execute-asuser is either root or administrator, but other users can be configured, depending on the tool thatwill be executed on the managed system. The private key is kept secure on the CMS, while thepublic key is installed on each managed system.

The SSH-2 protocol is used by the Distributed Task Facility (DTF) to communicate with managedsystems. The DTF improves operator efficiency by replicating operations across the systems orsystem groups within the management domain using a single command. This functionality reducesthe load on administrators in multi-system environments. X Window and CLI tools use the DTF toexecute and support the following:

● 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 must be performed on the system. The SSH server then performs thetasks and returns the results to the DTF. The DTF consolidates the feedback it receives from all themanaged systems.

WBEM. WBEM is an industry standard that simplifies system management. It is based on aset of management and Internet standard technologies developed to unify the management ofenterprise computing environments. It provides access to both software data and hardware datathat 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 CLI or GUI. For moreinformation, refer to the "Administering the Software" section in the HP Systems Insight Manageronline 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 WindowsManagement Instrumentation, a WMI Mapper running on a Windows system converts the HTTPSWBEM requests into WMI requests, which use Distributed Component Object Model and NTsecurity.

HTTPS. HTTPS is simply HTTP over SSL, a protocol that supports sending data securely overthe Web. HTTPS is used to access WBEM data as explained in the previous section, and it is usedto access ProLiant agent information. Digital certificates are used instead of user names andpasswords to establish trust between the agent and the CMS. The certificate of the CMS should beloaded 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 Desktop Management Taskforce. DMI provides anefficient means of reporting client system problems. DMI compliant computers can send statusinformation to a CMS 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 from

18

Product Overview

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

SNMP. SNMP is a set of protocols for managing complex networks. SNMP works by sendingmessages, called protocol data units (PDUs), to different parts of a network. SNMP-compliantdevices, called agents, store data about themselves in Management Information Bases (MIBs) andreturn this data to the SNMP requesters. There are multiple versions of SNMP. SNMP Version 1,used by HP Systems Insight Manager, is not a secure protocol. Therefore, anyone with access toyour network will be able to intercept and view 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 CLI or GUI. For moreinformation, refer to the "Administering the Software" section in the HP Systems Insight Manageronline 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 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 the clientor browser, known as spoofing. To prevent the possibility of spoofing, use a certificate signed bya trusted Certificate Authority (CA) or securely export the certificate by browsing locally to the CMSand then securely importing it into your browser. You can also obtain the server certificate bybrowsing remotely and saving it in the browser the first time you access HP Systems Insight Manager,but this option is less secure and still susceptible to a possible "man-in-the-middle" attack. Informationabout importing CA-signed certificates is available in the "Administering the Software" section ofthe HP Systems Insight Manager online 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, HTTPS, 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

19

Product Overview

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

20

Product Overview


Chapter 2. Installation Overviewand Requirements

This chapter provides an overview of the HP Systems Insight Manager installation process, and itidentifies the system requirements for a CMS, a managed system, 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. Install and configure the CMS. The procedure to complete this step is in the installation chaptersof this guide. Follow the appropriate chapter based on the operating system of your CMS.Refer to Chapter 4. Installing on HP-UX , Chapter 5. Installing on Linux , or Chapter 3. Installing on Windows for details.

2. Install and configure the required management agents on the systems that will be managedby the CMS. This step is covered in the first section of Chapter 12. Initial Setup .

21

3. Configure HP Systems Insight Manager for your environment. The remaining sections in Chapter 12. 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 CMS, managedsystem, and network client.

CMS RequirementsThis section contains the requirements for the CMS. These requirements are sorted by operatingsystem. Please review the section of requirements that applies to your CMS. Refer to:

● "HP-UX Central Management Server" ● "Linux Central Management Server" ● "Windows Central Management Server"

HP-UX Central Management Server● Operating System

❍ HP-UX 11i v1❍ HP-UX 11i v2❍ HP-UX 11i v2 update 2

Note: The required patches must be installed for each of these operating systems. Refer to theHP Systems 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: rp3410 or higher with 1 GB RAM

❍ Any HP Intel Itanium-based system with 2 GB RAM

● Software

❍ PostgreSQL 7.3.1 for HP-UX 11i v1❍ PostgreSQL 7.4.2 for HP-UX 11i v2❍ PostgreSQL 7.4.2 for HP-UX 11i v2 update 2❍ OpenSSH❍ WBEM providers installed and active for HP-UX 11i or greater

● Free Disk Space

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

● Swap Space

22

Installation Overview and Requirements

❍ 2 GB minimum total swap space for PA-RISC systems❍ 3 GB minimum total swap space for Intel® Itanium®-based systems

● Networking

❍ Static or dynamic host name resolution

Linux Central Management Server● Operating System

❍ Red Hat Enterprise AS Linux 2.1, Update 4❍ Red Hat Enterprise ES Linux 2.1, Update 4❍ Red Hat Enterprise AS Linux 3, Update 3❍ Red Hat Enterprise ES Linux 3, Update 3❍ SuSE Linux Enterprise Server 8.0 , Service Pack 3❍ SuSE Linux Server 9.0

● 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

● Software

❍ OpenSSH❍ ProLiant Support Pack for Linux 7.00 or later❍ For Red Hat 2.1 AS/ES Update 4

❑ PostgreSQL 7.4-0.3

❍ For Red Hat Enterprise Linux 3.0 AS/ES Update 3

❑ PostgreSQL 7.4.1

❍ For SuSE Enterprise server 8, Service Pack 3

❑ PostgreSQL 7.4.0

❍ For SuSE Enterprise server 9

❑ PostgreSQL 7.4.2-36.3

● Free Disk Space

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

23


● Swap Space

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

● Networking


Windows Central Management Server● Operating System

❍ Microsoft® Windows 2000 Server, Service Pack 4❍ Microsoft® Windows 2000 Advanced Server, Service Pack 4❍ Microsoft® Windows 2000 and 2003 International Server-French, German, Italian, Japanese

and Spanish

❍ Microsoft® Windows 2003 Server Standard Edition❍ Microsoft® Windows 2003 Server Enterprise Edition❍ Microsoft® Windows XP Professional, Service Pack 1❍ Microsoft® Windows XP Professional, Service Pack 2

Note: Japanese fully localized.

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

Note: The Windows server must have at least one partition formatted for the NT File System(NTFS) on which the HP Systems Insight Manager server software is to be installed. NTFSprovides the ability to restrict file access based on user accounts and groups. Without NTFS,the CMS cannot be adequately secured against unauthorized access, and potentially sensitiveoperations and data could be made available to unauthorized users.

● 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 CMS, only as managed systems.

● Software

❍ MSDE 2000 with Service Pack 3 (bundled with HP Systems Insight Manager), or you canuse one of the following:

❑ Microsoft SQL 2000, Standard Edition with Service Pack 3 (for "Standard Server"operating system)

❑ Microsoft SQL 2000, Enterprise Edition with Service Pack 3 (for "Advanced Server"operating system)

24


Note: Windows XP Professional is not supported with a local installation SQL 2000, onlyMSDE 2000. SQL 2000 can be used as a remote database for a CMS on Windows XPProfessional.

❍ ProLiant Support Pack for Windows 6.30 or later❍ WMI Mapper 2.0❍ Microsoft Internet Explorer 6.0

● Free Disk Space

❍ 500 MB recommended

● Networking

❍ Static or dynamic host name resolution❍ TCP/IP

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

❍ SNMP (recommended)

Managed System Requirements andRecommendations

This section contains requirements and recommendations for managed systems.

● Required Operating Systems

❍ HP-UX 11i v1❍ HP-UX 11i v2❍ HP-UX 11i v2 update 2❍ 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

25


❍ SCO UnixWare 7❍ SuSE Linux 7.0❍ SuSE Linux 7.2❍ SuSE Enterprise Server 8❍ SuSE Linux Server 9 Enterprise Edition for x 86❍ SuSE Linux Server 9 Enterprise Edition for AMD64 and Intel EM64T❍ Tru64 UNIX

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

● 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

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

❍ For HP-UX:

❑ SSH❑ WBEM

❍ For Linux:

❑ SSH❑ ProLiant Support Pack for Linux 7.0 or later❑ SNMP (recommended as an alternative to WBEM)❑ 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

26



Network Client Requirements and RecommendationsThis section contains requirements and recommendations for managed systems used as clientsaccessing the CMS.

● Required Web Browsers

❍ For HP-UX:

❑ Mozilla 1.4 or later supplied by HP with Java™ Runtime Environment (JRE) browserplug-in 1.4.1_05 or later

Refer to the following note about the required security options.

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

❍ For Linux:

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

Refer to the following notes about the required security options and the Java plug-inregistration.

Note:

The default Mozilla 1.6 profile uses a cookie policy that doesnot work with HP Systems Insight Manager's Java applets. Youneed to configure Mozilla to accept cookies, by selectingEdit->Preferences, expand Privacy &Security->Cookies->Enable all cookies. Click OK to save thechanges.

Note: If you do not want to enable all cookies, you can selectEnable cookies for the originating website only instead.

Note:

SUSE 9 has different method than other Linux distributions, foradding JRE Plugin. For SUSE 9, in order to add the JRE pluginto Mozilla 1.6, after the plugin has been downloaded, you needto do the following: change to the Mozilla bin directory cd/opt/mozilla/bin execute the following script, which willlocate and add the plugin ./plugins.sh

❍ For Windows:

❑ Microsoft Internet Explorer 6.0 or later with Java JRE browser plug-in 1.4.2.03 or later

27


http://software.hp.com

Refer to the following note 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:

❑ 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 website 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 by executing thefollowing command:

mv libjavaplugin_oji.so libjavaplugin_oji.so.bak

Change the Java version that exists in the /usr/java path by executing the followingcommand:

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, HP recommends 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 CMS. Additionalsteps to complete the configuration on the CMS may be provided in the HP Systems Insight ManagerREADME. Custom commands on the Tools menu require SSH on the CMS to run properly. Thesecommands run on the CMS with environment variables set to the context of specific events ordevices. SSH on the CMS is also used by the Initial ProLiant Support Pack Install on theDeploy->Deploy Drivers, Firmware and Agents menu.

You can optionally install and configure SSH on each of the managed systems and have HP SystemsInsight Manager exchange keys with the managed systems (through the mxagentconfig commandor for Windows, through the Install SSH task). If you do this, then the Command Line Tools option

28


on the Tools menu works for these managed systems. If you choose not to configure it to workwith remote SSH clients, then these commands fail. There is no other loss of functionality withoutSSH.

29


Chapter 3. Installing on Windows Preparing 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 supports upgrading from Compaq InsightManager 7 Service Pack 2.3. Refer to Chapter 6. Upgrading from CompaqInsight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2 for details.

Note:

The Windows installer will fail if Internet Explorer 6.0 or later is not present. If InternetExplorer 5.x or earlier is installed, it must be upgraded to Internet Explorer 6.0 orlater for the HP Systems Insight Manager install to complete successfully.

Important:

On Windows 2003, install HP Systems Insight Manager using a local administratorlevel account and not a domain account. If you want to use domain accounts toaccess HP Systems Insight Manager, you can add them after the install is complete.This requires adding users to HP Systems Insight Manager and configuring SSH forthose users. Please refer to the HP Systems Insight Manager 4.2 README foradditional steps to complete the configuration.

To verify and prepare your system:

1. Verify your system meets the minimum requirements. Refer to the HP Systems Insight ManagerRelease Notes for details.

2. Install the required Windows and SQL/MSDE Service Packs if necessary.

3. Verify your system has at least one partition formatted for the NTFS file system, on which theHP Systems Insight Manager server software is to be installed.

If this requirement is not yet met, create or format an NTFS partition for use by HP SystemsInsight Manager.

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

30

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

Installing and Configuring the Software1. Run setup.exe to launch the HP Systems Insight Manager Installer. The HP Systems

Insight Manager Welcome screen appears. The Welcome screen displays links to the followingdocumentation:

● Readme (readme.txt)

● Release Notes (hpsim-releaseNote.pdf)

● User Guide (hpsim-userGuide.pdf)

2. Click Install to launch the install process. The HP Systems Insight Manager setup window isdisplayed with three stages which would read as mentioned below:

● Pre-installation. Examines this system for previous versions of Insight Manager 7and runs data export tools as needed.

● Installation. Installs HP Systems Insight Manager and other HP management softwareproducts.

● Post-installation. Runs data import tools as needed to migrate customer data fromprior local installations of Insight Manager 7.

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

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

4. (Optional) If Microsoft SQL is not detected locally, you will be prompted to either install MSDE2000 Service Pack 3A or continue and point to a remote SQL installation later.

Note: For a list of supported databases, refer to the HP Systems Insight Manager ReleaseNotes for details.

Note: If choosing to use a remote Microsoft SQL Server, verify that Microsoft Access DataComponents (MDAC) 2.7 Service Pack 1 or higher is installed on the CMS. To verify whetherthis is installed, navigate to C:\Program Files\Common Files\System\Ado, andright-click on the icon for the msado15.dll file. In the pop-up menu, select Properties, andclick the Version tab to display the version number. If the file is not found in this path, use theWindows search engine to find the file. If you must download MDAC, go tohttp://www.microsoft.com/downloads/, and search for MDAC Service Pack.

a. Click Install MSDE to launch the install.

b. After MSDE installation is complete, you have to reboot your system and then repeat theprevious step to launch the installer. You will not see the option to install MSDE again.

Note: When you reboot, the HP Systems Insight Manager Installer will not automaticallybe launched. You must manually execute setup.exe to launch the installer.

31

Installing on Windows

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

Refer to Windows Installation Options to view the options available during an installation ofHP Systems Insight Manager.

5. Click Typical to install the components listed under the Available Components for Installwith minimal user interaction or click Custom to select the components you want to install.

Note: The differences between the Typical and Custom installs for this version of HP SystemsInsight Manager is that the Custom option enables you to deselect components in addition toallowing you to change one or more of the following settings for the components:

● Drive● Install directory● Program group

Refer to Windows Installation Options to determine which components listed in the AvailableComponents for Install are mandatory in the Typical install or optional in the Custom install.

6. On the Typical Install - Account Authentication screen, enter the Account Credentialsfor the database server. If your database is local, then the Database Server name field ispre-populated, if your database is not local then you must supply the Database Server name.

Note: In case of a reboot, if you just installed MSDE, the administrative credentials are thoseyou used to log in before installing MSDE. Windows authentication is required to connect tothe SQL server (whether locally or remotely). In addition, these credentials will also be yourHP Systems Insight Manager administrative user login credentials. Any account that is a memberof the administrator group will have administrator rights to MSDE

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

Each component will be installed sequentially, Custom Install will launch them interactively.You may skip to #13.

For the Custom install, you choose the components to install, starting with #8.

8. Installing HP System Management Homepage for an In-Place custom install:

Note:

For more information regarding where the System Management Homepagedefault settings are stored during a Typical installation and how to changethem, refer to the System Management Homepage Installation Guide at:http://h18013.www1.hp.com/products/servers/management/agents/documentation.html

Note:

The HP Version Control Agent and HP Version Control Repository Managerlogin to the management web server by way of the System ManagementHomepage. The System Management Homepage is security software thatmust be configured in order to allow the Version Control Agent to connectto the Version Control Repository Manager using operating systemauthentication. For more information regarding migrating version control

32


http://h18013.www1.hp.com/products/servers/management/agents/documentation.html

to the System Management Homepage Refer to Migrating Version Controlto the System Management Homepage for details.

a. Click Next. The OS Groups dialog box appears. Click Cancel to cancel the installationprocess. If you click Cancel, a message appears, giving you the option to continueinstallation or to exit the installation.

b. Select Administrator, Operator, or User from the Operating Systems Group Namefield.

Note: It is necessary to assign an account to an operating system user group withadministrator privileges to access the Version Control Repository Manager from the VersionControl Agent. Do not use the Administrator account to connect from the Version ControlAgent to the Version Control Repository Manager as it could potentially lock theAdministrator account out. Using the Administrator account, add another account withadministrator privileges to be used for Version Control Repository Manager access.

c. Enter the group name of an operating systems group in the Group Name field.

d. Click Add. The group name is added. A maximum of five entries can be added for eachgroup level.

Note: To delete a group name, select the group name and click Delete.

e. Click Next to continue or Back to return to the previous page. The User Access dialogbox appears.

The User Access dialog box enables you to configure the System ManagementHomepage from the following access types:

● Select Anonymous Access to enable anonymous access to unsecured pages.

● Select Local Access Anonymous or Local Access Administrator to set up theSystem Management Homepage to automatically grant local IP addresses at theselected access level.

Caution: Selecting Local Access with Administrator privileges provides any userswith access to the local console full access without prompting them for a user nameor password.

f. Click Next. The Trust Mode dialog box appears.

g. Select the level of security you want to provide from one of the following trust modes:

● Trust By Certificate

i. Click Next. The Trusted Certificates dialog box appears. The TrustedCertificates dialog box allows trusted certificate files to be added to the TrustedCertificate List.

ii. Click Add File to browse and select any certificates to be included in the TrustedCertificate List. The Add File dialog box appears. If an invalid file name isentered in the file name field, an error message appears, indicating the file does

33


not exist. Click OK to select another file, or click Cancel to close the dialog box.The Trusted Certificate List appears.

Note: If you click Next without adding any certificates to the list, and nocertificates exist from a previous installation, a message appears indicating thatif you do not specify any trusted certificates, HP Systems Insight Manager cannotaccess the HP Insight Management Agentss on this system. Click OK if you donot want HP Systems Insight Manager to access the Insight Management Agentson this system, or click Cancel to close the dialog box and add the trustedcertificates to the list.

Note: The Trust By Certificates option enables the System ManagementHomepage system and the HP Systems Insight Manager system to establish a trustrelationship by means of certificates. This mode is the strongest method of securitybecause it requires certificate data and verifies the digital signature beforeenabling access.

iii. Click Next. The IP Binding dialog box appears.

or

i. Click Import. The Import Server Certificate dialog box appears.

ii. Enter the name or IP address of the server whose certificate you want to import.

iii. Click Get Cert. The certificate information appears.

iv. Verify the certificate information. If you want to add this certificate to the TrustedCertificate List, click Accept and the certificate is added to the TrustedCertificate List, or click Cancel if you do not want to add it to the TrustedCertificate List. The Trusted Certificate List appears.

Note: You can add an unlimited number of trusted certificates.

v. Click Next. The IP Binding dialog box appears. Click Back to return to theTrust Mode dialog box.

Note: To delete a certificate, select the certificate and click Delete. The selectedcertificate is removed.

● Trust By Name

i. Select Trust By Name.

ii. Click Next. The Trusted Server dialog box appears.

Note: Although the Trust By Name mode is a slightly stronger method of securitythan the Trust All mode, it still leaves your system vulnerable to security attacks.The Trust By Name mode sets up the System Management Homepage to onlyaccept certain requests from servers with the HP Systems Insight Manager namesdesignated in the Trust By Name field. The Trust By Name option is easy toconfigure and can prevent non-malicious access. For example, you might wantto use the Trust By Name option if you have a secure network, but your networkhas two groups of administrators in two separate divisions. The Trust By Nameoption would prevent one group from installing software to the wrong system.

34


This option does not verify anything other than the HP Systems Insight Managerserver name submitted.

iii. Enter the names of the servers you want to trust.

Note: The server name cannot contain the following characters:

❍ ~

❍ !

❍ `

❍ @

❍ #

❍ $

❍ %

❍ ^

❍ &

❍ *

❍ (

❍ )

❍ +

❍ =

❍ "

❍ :

❍ '

❍ <

❍ >

❍ ?

❍ ,

❍ |

❍ ;

iv. Click Add to add the name of a server you want to trust.

v. Click Next. The IP Binding dialog box appears.

35


Note: If you click Next without adding any server names to the list, an errormessage appears, indicating that if you do not specify any trusted server names,HP Systems Insight Manager cannot access the Insight Management Agents onthis system. Click OK to proceed without trusting any systems, or click Cancel toclose the dialog box and add server names to the list.


● Trust All

i. Select Trust All.

ii. Click Next. The IP Binding dialog box appears.

Note: The Trust All option leaves your system vulnerable to security attacks andsets up the System Management Homepage to accept certain requests from anyserver. For example, you might want to use Trust All if you have a secure network,and everyone in the network is trusted.

h. Select IP Binding to enable the Subnet IP Address and NetMask.

The IP Binding dialog box enables you to bind to specific IP addresses that match aspecific Subnet IP Address or NetMask. It restricts the subnet you want to manage.

i. Enter the Subnet IP Address in the designated field.

ii. Enter the NetMask in the designated field.

iii. Click Add to add the Subnet IP Address/NetMask into the dialog box. Select aSubnet IP Address/NetMask, and click Delete to remove it from the dialog box

Note: You can add up to five Subnet IP Address/NetMask pairs.

Note: If you click IP Binding but do not specify the IP Address/NetMask then youmay not be able to connect to the System Management Homepage.

i. Click Next. The IP Restricted Logins dialog box appears. The IP Restricted Loginsdialog box enables you to select specific IP addresses or IP address ranges to include orexclude from gaining login access. Although optional, the System Management Homepagecan restrict login access based on the IP addresses of the machine attempting to gainaccess.

j. Select IP Restricted Logins, and click Next. The IP Address to Include dialog boxappears. This dialog box enables you to specify the IP address or IP address ranges togrant login access permission. If there are IP addresses in the Inclusion list, then onlythose IP addresses are enabled for login privileges. If there are no IP addresses in theInclusion list, then login privileges are permitted to all IP addresses that are not in theExclusion list.

Note: A single address and ranges of addresses can be accepted in the IP RestrictionLogins dialog box. Enter the single address in the first box.

36


i. In the Include field, enter a beginning IP address to which you want to grant loginaccess.

ii. In the To field, enter an ending IP address to which you want to grant login access.All IP address that fall between the beginning and ending IP addresses are grantedlogin access.

iii. Click Add. The IP address or IP address range is added to the Exclusion list. Selectan IP address or IP address range, and click Delete to remove it from the Exclusionlist.

Note: If you entered an invalid IP address or IP address range, an error messageappears indicating the IP address is invalid. Click OK. Enter a valid IP address or IPaddress range, and click Add again.

k. Click Next. The IP Address to Exclude dialog box appears.

i. In the Exclude field, enter a beginning IP address to which you want to deny loginaccess.

ii. In theTo field, enter an ending IP address to which you want to deny login access.All IP addresses that fall between the beginning and ending IP addresses are deniedlogin access.

iii. Click Add. The IP address or IP address range is added to the Inclusion list. Selectan IP address or IP address range, and click Delete to remove it from the Inclusionlist

Note: If you entered an invalid IP address or IP address range, an error messageappears, indicating the IP address is invalid. Click OK. Enter a valid IP address orIP address range, and click Add again.

Note: If Next is selected without adding any IP addresses to either theInclude orExclude lists, a warning message appears stating, IP Restricted Logincheckbox will be marked as disabled. Do you want to proceedwithout adding any IP Address restrictions? If you select OK, the IPRestricted Login option on the IP Restricted Login dialog box is deselected, andthe Install Preview dialog box appears.

l. Click Next. The Install Preview Panel appears. The Install Preview Panel lists thelocation where the System Management Homepage is installed, the amount of space theinstallation requires, and the summary of the options that you specified during theinstallation.

m. Click Next. The installation process is started.

Note: During the installation of the System Management Homepage, Cancel is disabled.If you click the X in the upper-right corner of the box, an error message appears, statingthe current operation cannot be canceled.

n. Click Finish to complete the installation.

Note: If this is an upgrade, HP recommends that you configure System ManagementHomepage to use operating system authentication for HP Version Control Agent access

37


to HP Version Control Repository Manager, and then re-configure the servers running HPVersion Control Agent to point to the new account. If these actions are not taken, pre-7.20HP Version Control Agent will access your upgraded HP Version Control RepositoryManager via legacy HTTP Server account access. For more information, refer to VersionControl Installation Guide athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html/.If this is a new install, an operating system account must be created and configured inthe System Management Homepage on this computer and each of the HP Version ControlAgent must be configured to use the new account. For more information, refer to VersionControl Installation Guide athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html/.

Note: If HP Systems Insight Manager is installed after System Management Homepageis installed, the System Management Homepage 2048-bit key pair will be replaced withthe HP Systems Insight Manager1024-bit key pair.

9. Installing OpenSSH for a custom install:

a. Click Next to install.

b. Select the destination location using the Browse button.

c. Click OK.

d. Click Next. The Ready to Install screen appears.

e. Click Install to continue with the installation, or click Back to make changes.

f. After installing OpenSSH, click No, I will restart the computer later.

g. Click Finish.

IMPORTANT: On Windows 2003 after installing HP Systems Insight Manager 4.2 the SSHkey might not be configured automatically which does not allow the domain user to run customcommands. Please refer to the HP Systems Insight Manager 4.2 README for additional stepsto complete the configuration.

10. Installing HP Systems Insight Manager for a custom install:

a. Click Next on the HP Systems Insight Manager welcome screen.

b. Read the information screen. Click Next. The Database Configuration screen appears.

c. Enter the password and database server name. If your database is local, then the DatabaseServer name field is pre-populated, if your database is not local you must supply the nameof the Database Server.

Note: HP Systems Insight Manager creates a database name with the format“Insight_V42_0_(timestamp).” For example, “Insight_V42_0_123456.” It then updatesdatabase.props and the DSN with this value. The database.props file can be found inC:\Program Files\HP\Systems InsightManager\Config

d. Click Next. The Destination Location screen appears.

e. Select the destination location by clicking the Browse button.

38


http://h18013.www1.hp.com/products/servers/management/agents/documentation.html/




f. Click OK.

g. Click Next. The Select Start menu folder appears.

h. Select or enter a different folder name.

i. Click Next. The ready to install screen appears.

j. Click Install to install HP Systems Insight Manager, The Install Progress Screen appearsor click Back to make any changes.

k. Click Finish when the installation is complete to close the HP Systems Insight ManagerInstaller window.

11. Installing WMI Mapper for a custom install:


b. The End-User License Agreement screen appears. Click I accept the agreement.

c. Choose Setup Type screen appears. Chose the setup type.

d. Select the destination location using the Browse button.

e. Click OK.

f. Click Next. The Ready to install screen appears.

g. Click Install to continue with the installation, or click Back to make changes.

h. Click Finish.

12. Installing the ProLiant Essentials Performance Management Pack (PMP)for a custom install:

Note: The PMP requires HP Systems Insight Manager 4.1 or later to be installed on yoursystem before installing the PMP.

Note: During the installation of the PMP, the warning is displayed: As part of HPPerformance Management Pack installation the HP Systems InsightManager service must be stopped and restarted. Click OK to stop the serviceand continue with the PMP installation, or click Cancel to abort the installation.

a. Click Next. The Database configuration screen appears.

b. Enter your account password.

c. Click Next. Installation begins.

d. Click Finish to exit PMP setup.

13. Installing HP Version Control Repository Manager for a custom install:

a. Click Install to install HP Version Control Repository Manager. The HP Version ControlRepository Manager setup screen appears.

39


b. Click Install.

c. Click the Browse button to select the directory from which HP Version Control RepositoryManager will retrieve support pack information. This directory must be manually createdlater if it does not exist.

d. Click OK.

e. Click Next.

f. Select the Enable Automatic Update checkbox to enable automatic downloading ofProLiant Support Packs and components at a specified interval and time.

g. Click Finish. Installation of HP Version Control Repository Manager proceeds andcompletes.

14. Installing HP ProLiant Essentials Virtual Machine Management Pack for a custom install:

Note: During the installation of the HP ProLiant Essentials Virtual Machine Management Pack,the warning is displayed: "As part of . HP ProLiant Essentials Virtual Machine ManagementPack installation the HP Systems Insight Manager service must be stopped and restarted."Click OK to stop the service and continue with the HP ProLiant Essentials Virtual MachineManagement Pack installation, or click Cancel to abort the installation. If you clicked OK theHP ProLiant Essentials Virtual Machine Management Pack Welcome screen appears.




d. Click Finish to exit HP ProLiant Essentials Virtual Machine Management Pack setup.

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

Note: During the Custom Install process, do not select the reboot now option if a componentrequests this. Reboot only after all components have been installed.

16. Click Finish to complete the component installation that you selected.

Note: Click Finish in the Initial Setup HP Systems Insight Manager window, to complete theinstallation.

Next StepsInstall and configure the required management agents on the systems that will be managed by theCMS. Refer to Chapter 12. Initial Setup for details.

Next, complete the initial setup of HP Systems Insight Manager. Initial setup involves addingmanaged systems, adding users, setting up authorizations, and configuring event handling. Referto Chapter 12. Initial Setup for details.

40


Windows Installation Options● Typical installation of HP Systems Insight Manager installs all components listed in the table.

● Custom installation of HP Systems Insight Manager enables you to chose the components to beinstalled.

Note: If you chose not to install a component during the initial installation of HP Systems InsightManager, you can re-run setup.exe and at that time select the components that are to be installed.

HPProLiantEssentialsVirtualMachineManagementPack

HPVersionControlRepositoryManager

HPPerformanceManagementPack

WMIMapper

HPSystemsInsightManager

SSHServer

HPSystemManagementHomepage

InstallationTypes

not IncludedXXXXXXTypical

OptionalOptionalOptionalOptionalXOptionalXCustom

Note: If a component is not listed as being available for installation on the CMS, then the HPSystems Insight Manager install shell has determined one of the following:

● The installation prerequisites for the component have not been met.

● The component is currently installed.

If the component that is present on the CMS is an older version than what is bundled with the HPSystems Insight Manager install shell and it supports an in-place upgrade, it appears in thecomponent list.

41


Chapter 4. Installing on HP-UX Optimizing the Operating Environment(Kernel Tuning)

Note:

This release of HP Systems Insight Manager supports upgrading from Service ControlManager 3.0 Refer to Upgrading from HP Servicecontrol Manager to HP SystemsInsight Manager for details.

Note:

The "\" at the end of each command line represents that the rest of the commandis on the next line.

1. Install the latest recommended HP-UX patches.

For a list of recommended patches refer to the HP Systems Insight Manager Release Notes fordetails.

2. Tune the kernel using the JavaOOB (Java-out-of-box) fileset. For information on this, go tohttp://www.hp.com/products1/unix/java/java2/outofbox/index.html. This product may beavailable for you to install with HP Systems Insight Manager, either as part of the downloaddepot file containing HP Systems Insight Manager 4.2. or from the Application Release media.The kernel parameter values it adjusts are listed in the table below.

Note:

Java Out-of-Box is a stand-alone bundle that upon installation will rebootthe system.

Java Out-of-Box Settings

=3000max_thread_proc

=2063835136maxdsize

=2048maxfiles

=2048maxfiles_lim

=512maxusers

42

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

=6000ncallout

=4097nfile

=6000nkthread

=2048nproc

=2048tcp_conn_request_max

Note:

The maxusers parameter is obsolete in HP-UX 11i v2 (B.11.23).

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

a. The JOOB file will only set the nfile parameter to 4097. Increase the nfile parameterto at least 12000. This value might need to be increased to 30000 depending on yourenvironment. If you get an error that you cannot open a file, increase this value.

b. 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 physical memory thatequals 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%.

Note: For HP-UX 11i v2 (B.11.23) these parameters are dynamic and when you modifythe parameters a reboot of the system is not necessary.

Preparing the System

Note:




1. Verify your system meets the minimum requirements. Refer to "System Requirements" fordetails.

43

Installing on HP-UX

2. Verify that a previous version of HP Servicecontrol Manager or HP Systems Insight Manageris not installed and configured for use, using the following commands:

swlist -l bundle B8337BA B8339BA B8338BA T2414BA

swlist -l product ServControlMgr AgentConfig SysMgmtServerSysMgmtAgent

If SysMgmtServer is installed, but has never been configured, then uninstall it. If it has beenconfigured, you have the option of uninstalling it or upgrading it.

If you choose to uninstall Servicecontrol Manager to prepare for a fresh install of HP SystemsInsight Manager, use the following commands:

swremove ID

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

swremove -x enforce_dependencies=false B8339BA

If SysMgmtServer has been configured and you wish to perform an upgrade, then use theupgrade steps in Upgrading HP Systems Insight Manager 4.0, 4.0.1 and 4.1 to HP SystemsInsight Manager 4.2.

Note:

Not all of SysMgmtServer and SysMgmtAgent Filesets can be removed dueto dependencies. HP Systems Insight Manager 4.2updates those filesetswhen installed.

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


Installing and Configuring 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:

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

44

Installing on HP-UX


2. Install HP Systems Insight Manager:

swinstall -s /directory/depot T2414BA


swinstall -s /tmp/HPSIM_download.depot T2414BA

3. Test the prerequisites:

/opt/mx/bin/mxinitconfig -l

4. Remove extraneous conflicting files from any unconfigured Servicecontrol Manager system:

rm -fr /var/opt/mx/setup

rm -f /var/opt/mx/config/nodesecurity.xml

5. Initialize HP Systems Insight Manager:

/opt/mx/bin/mxinitconfig -a

Note: This step could take several minutes. After it completes, view the file/var/opt/mx/logs/initconfig.log to verify the initialization completed.

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

7. (Optional) Configure the CMS to send SNMP traps to itself.

a. Add the name of the CMS as a trapdest in the file /etc/SnmpAgent.d/snmpd.conftrap-dest: <cms_full_hostname_or_ip_address>

b. Stop the SNMP Master agent and all subagents with the command:

/sbin/init.d/SnmpMaster stop

c. Restart the SNMP Master agent and all subagents with the command:

/usr/sbin/snmpd

Note:

Once installation is complete you must logout of the operating system andthen log back in to set all the correct file permissions and systemenvironmentals.

45

Installing on HP-UX

Installing and initializing HP Systems Insight Manager is complete on the central managementserver. You may start the HP Systems Insight Manager user interface and explore HP SystemsInsight Manager refer to Chapter 10. Using the Graphical User Interface

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, complete the initial setup of HP Systems Insight Manager. Initial setup involves addingmanaged systems, adding users, setting up authorizations, and configuring event handling. Referto Chapter 12. Initial Setup for details.

46

Installing on HP-UX

Chapter 5. Installing on Linux Preparing the System


Note:



1. Verify your system meets the minimum requirements. Refer to "System Requirements" fordetails.

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 mxagent mxrepository

3. Verify that earlier versions of PostgreSQL are not installed:

rpm -qa | grep postgresql

If PostgreSQL is not installed, proceed to the next step. If installed, refer to "Linux CentralManagement Server" portion of the “System Requirements” section for supported versions.

IMPORTANT: No matter what version of PostgreSQL you have installed, even a supportedversion, you must backup the database file and remove the postgresql-server.

To remove postgresql-server:

cp –rp /var/lib/pgsql /var/lib/pgsql.old

The p retains the permission, time, and date of all files and folders

Note: If you must backup the database, you must take the backup first and then remove thepackage after executing this command.

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

47

Note: If you have PostgreSQL installed, even if it is a supported version, you must remove itand let the HP Systems Insight Manager installer install a supported version unless you areinstalling over a previous version of HP Systems Insight Manager (4.0.1).

4. Download the software or locate a copy on a depot server. To download the software, go tohttp://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

or

chmod +x T2416BA_4.02.0.0_Linux.bin

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, install it from your Linux operating system CD before continuingwith the installation.

b. Verify that SNMP is installed:

rpm -qa | grep snmp

If it is not installed, install it from your Linux operating system CD before continuing withthe installation.

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

rpm -qa | grep compat

If they are not installed, install them from your Linux operating system CD before continuingwith the installation.

d. Verify that the GLIBC library is installed. If you plan to install Mozilla on your CMS, thelibrary 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 library must be installedfirst.

rpm -qa | grep gdk-pixbuf


48

Installing on Linux


7. (Optional) If you are planning to run the Mozilla browser on the CMS, verify that Mozilla 1.6or later is installed. To verify which version is installed, open the Mozilla browser and selectHelp->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 Mozilla 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:

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 remainder 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 must 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->Cookies->Enable all cookies. Click OK to save the changes.

Note: If you do not want to enable all cookies, you can select Enable cookies for theoriginating website only instead.

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

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. Accept all the defaults to install.

b. Register the plug-in. Navigate to the /usr/local/mozilla/plugins directory andtype:

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

49

Installing on Linux

http://www.mozilla.org/download

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

Note: Use the Tab key to help type in this long command accurately. Pressing the Tabkey after typing the first letter or so of each directory name automatically fills in the restof the name.

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, specify the path to the mozilla directory in place of the final period.

Note: The directory j2re1.4.2_03 changes if you are installing a later version of theJRE.

Note: In Mozilla, select the "About Plug-ins" from the Help menu to verify the plug-in wascorrectly registered.

Installing and Configuring the SoftwareInstallation of HP Systems Insight Manager includes the PostgreSQL software dependency.

Manually Installing HP Systems Insight Manager1. Extract the rpm files from the bin file. Be sure you set the permissions to include the right to

execute the bin for the following step.

./T2416BA_4.02.00_Linux.bin \ --keep --confirm

Note: Refer to Step 5 in the "Installing on Linux - Preparing the System" section for informationon setting permissions.

2. Respond negatively to the prompt to run scripts for an automatic install. The extracted files areplaced in an mxserver subdirectory.

3. Enter cd mxserver.

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

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

● For Red Hat Enterprise Linux AS/ES 3 U1(this command is entered with no carriage returns).

rpm -U postgresql-libs-7.4.1-1PGDG.i386.rpm \postgresql-7.4.1-1PGDG.i386.rpm \postgresql-server.7.4.1-1PGDG.i386.rpm

● For Red Hat Enterprise Linux AS/ES 2.1 U3 (this command is entered with no carriagereturns).

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

● For SuSE Enterprise Server 8 (this command is entered with no carriage returns).

50

Installing on Linux

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

● For SuSE Enterprise Server 9 (this command is entered with no carriage returns).

rpm -U postgresql-libs-7.4.2-36.3.i586.rpm \postgresql-7.4.2-36.3.i586.rpm\postgresql-server-7.4.2-36.3.i586.rpm

5. 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 and SuSE Enterprise Server 9:

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:

chkconfig postgresql 345

6. Install HP Systems Insight Manager using the rpm files by executing the following command:

rpm -ivh hpsim-C.4.02.0.0 -1.i386.rpm \ hpsim-pgsql-config-C.4.02.0.0-1.i386.rpm

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

Note: To install HP Systems Insight Manager on a system without OpenSSH or a purchasedversion of SSH, use the --nodeps option on rpm.

For example rpm --nodeps -ivh...

Automatically Installing HP Systems Insight ManagerExtract the rpm files from the bin folder. Be sure you set the permissions to include the right toexecute in the following section.

51

Installing on Linux

chmod +x *.bin T2416BA_4.02.0.0_Linux.bin --keep --confirm

Note: Refer to Step 5 for information on setting the permission.

Enter y to install automatically.

Note:

Once installation is complete you must logout of the operating system and then logback in to set all the correct file permissions and system environmentals.

After Installing HP Systems Insight Manager1. 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: HP recommends removing any warnings before continuing with the setup process.

2. Initialize and configure HP Systems Insight Manager:

/opt/mx/bin/mxinitconfig -a

Note: This step could take several minutes. After it completes, view the file/var/opt/mx/logs/initconfig.log to verify the initialization completed logs.


ps -ef | grep mx


/opt/mx/bin/mxstart

4. Configure the system to send SNMP traps.

Note: These steps might vary slightly, depending on your version of Linux. Refer to your Linuxprovider for details if these file paths and file names do not exist on your system.

a. Verify that SNMP is installed:

rpm -qa | grep snmp

If it is not installed, refer to your Linux provider for information on installing SNMP.

b. If you have not installed the HP Server Management Drivers and Agents from the ProLiantSupport Pack for Linux, omit this step. Otherwise, stop the HP Server and ManagementDrivers and Agents daemons on the platform where you are installing HP Systems InsightManager using the following command:

52

Installing on Linux

/etc/init.d/hpasm stop

Note: If the HP Server Management Drivers and Agents daemon is not installed, omitthis step and step F.

c. Stop the SNMP daemon:

/etc/init.d/snmpd stop

d. Edit the snmpd.conf file using any text editor.

For Red Hat Linux run the following command for opening this file in the vi editor: vi/etc/snmp/snmpd.conf

For SuSE SLES 8 run the following command for opening this file in the vi editor: vi/usr/share/snmp/snmpd.conf

i. Remove the comment symbol (#) from the trapsink line, and add the IP address ofthe CMS:

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. To save and close this file using the vi editor, press theEsc key, enter :wq!, and press the Enter key.

e. Start the SNMP daemon:

/etc/init.d/snmpd start

f. Start the HP Server Management Drivers and Agents daemon if it is installed on yoursystem:

/etc/init.d/hpasm start


Next complete the initial setup of HP Systems Insight Manager. Initial setup involves adding managedsystems, adding users, setting up authorizations and configuring event handling. Refer to Chapter 12. Initial Setup for details.

53

Installing on Linux

Chapter 6. Upgrading fromCompaq Insight Manager 7 ServicePack 2.3 to HP Systems InsightManager 4.2

The HP Systems Insight Manager Data Migration Tool is used to migrate Insight Manager 7 datato HP Systems Insight Manager. The Data Migration Tool exports user-defined data from InsightManager 7 by extracting it and storing the information in a portable format. The Data MigrationTool then imports that user-defined Insight Manager 7 data into HP Systems Insight Manager. Themigration process transfers custom data, which includes:

● User accounts and privileges

● User access control settings

● User-defined folders, tasks and queries

● Discovered devices

● User-defined reports

● Device Type Manager rules

● Server certificate (for an in-place migration only)

● User-defined MIB and notice data (this needs to be manually recompiled)

In addition, the following data is archived:

● Received events/notices

Note:

You must be running Compaq Insight Manager 7 Service Pack 2.3 to upgrade toHP Systems Insight Manager 4.2. If you are running a version of Insight Manager7 earlier than Insight Manager 7 Service Pack 2.3, upgrade to Insight Manager 7Service Pack 2.3 before upgrading to HP Systems Insight Manager 4.2. If you haveInsight Manager 7 Service Pack 2, 2.1, or 2.2 installed, the migration process offersan automatic upgrade to Insight Manager 7 Service Pack 2.3. If you have a versionearlier than Service Pack 2, you are directed to the HP website to download theSoftpaq that will enable you to upgrade to Insight Manager 7 Service Pack 2.3.Refer to the Compaq Insight Manager 7 User's Guide for information on upgradingfrom Insight Manager 7 to Insight Manager 7 Service Pack 2.3. Refer to theTransitioning from Insight Manager 7 to HP Systems Insight Manager whitepaperfor more in-depth detail on this process.

54

Your system must also meet the operating system and SQL/MSDE requirements listedin Chapter 2. Installation Overview and Requirements .

Note:

The Data Migration Tool must be run by a user with full Windows administrativerights.

Note:

The HP Performance Management Pack was part of the Insight Manager 7 ServicePack 2.3 installation. If it is detected on your system, a migration utility for transferringdata specific to it will also be launched.

Types of MigrationThere are two types of migration:

● In-Place

● Remote

In-place migration. This type of migration enables you to install HP Systems Insight Manager,and optionally, the HP Performance Management Pack on the same server that previously ranInsight Manager 7. As part of the In-place migration process, Insight Manager 7 is disabled andcan only be re-enabled by uninstalling HP Systems Insight Manager and manually re-enablingInsight Manager 7. In-place migration preserves user-defined data including the Insight Manager7 server certificate.

Remote migration. This type of migration enables you to install HP Systems Insight Manageron a different server than Insight Manager 7. The remote migration process leaves Insight Manager7 running after data has been exported and requires you to import the Insight Manager 7 andPerformance Management Pack migration data files to your new HP Systems Insight Managerserver. Remote migration preserves user-defined data except the Insight Manager 7 Server certificate.

Performing an In-Place Migration1. Export Performance Management Pack and Insight Manager 7 data:

a. Upgrade from Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2via the HP 7.2 Management CD or by downloading the HP Systems Insight Manager 4.2software. To download the software, go to http://www.hp.com/go/hpsim, and selectDownload.

b. Begin the migration process by launching setup.exe from the download package orfrom the Management CD, select Products->HP Systems Insight Manager ->Install

55

Upgrading from Compaq Insight Manager 7 Service Pack 2.3 to HP Systems InsightManager 4.2


on the Insight Manager 7 server. The HP Systems Insight Manager Welcome screenappears. The Welcome screen displays links to the following documentation:




A background setup screen will be displayed showing that Pre-Installation is “In Progress”.If the Performance Management Pack that was installed with Insight Manager 7 is detectedon your system, the Performance Management Pack Migration Utility for data export islaunched. Follow the screen prompts to completion before continuing with the InsightManager 7 data export.

c. On completion of the data export for the Performance Management Pack, setup detectsthat you are running Insight Manager 7 Service Pack 2.3, or later and automaticallylaunches the HP Systems Insight Manager Data Migration Tool. The Data Migration Tooldialog screen appears. Click Next to continue.

d. Click Next to confirm data export to the following directory and file: C:\ProgramFiles\HP\Systems Insight Manager Data MigrationTool\user-data.dmt. Export of data begins.

e. When the export of data successfully completes, click Next.

f. Click the In-place migration (disable Insight Manager 7) radio button.

g. Click Next. The HP Systems Insight Manager Data Migration Tool export success screenappears and indicates that Insight Manager 7 has been disabled.

h. Click Finish to continue with the installation of the HP Systems Insight Managercomponents. Refer to the Chapter 3. Installing on Windows for details. The backgroundsetup screen will show that Pre-Installation is “Done” and the Installation is now “InProgress”

2. After installing HP Systems Insight Manager and its related components on the Insight Manager7 server and clicking Finish , the background setup screen will show that Installation is “Done”and the Post-Installation is now “In Progress”. Import of Insight Manager 7 and PerformanceManagement Pack data has automatically begun:

a. After all the HP Systems Insight Manager components have been installed, the InsightManager 7 Data Migration Tool dialog screen automatically appears. Click Next. A dataimport screen appears showing that the data will be imported from the following directoryand file: C:\Program Files\HP\Systems Insight Manager Data MigrationTool\user-data.dmt.

b. Click Next to start the Data Import. The process might take more than an hour dependingon the amount of user-defined data and the configuration of the HP Systems InsightManager. A status window shows the progress.

c. When data import completes, click Next. A pop-up message appears stating that the usermust log into HP Systems Insight Manager to complete the migration process by verifyinguser accounts, assigning authorizations, and enabling tasks and Automatic Event Handlingrules.

56


d. Click OK.

e. At the data import success screen, click Finish.

3. If the Performance Management Pack was upgraded, then the Performance Management PackMigration Utility for data import is automatically launched. Follow the screens to completion.The background setup screen will show the Post-Installation is “Done”.

4. Click Finish on the background setup screen and reboot the system at this time if any HPSystems Insight Manager components indicated the need for this.

Note:

For an in-place migration the Compaq DMI Indication handler service shouldbe disabled on the CMS.

Performing a Remote Migration1. Export Performance Management Pack and Insight Manager 7 data:

a. Acquire HP Systems Insight Manager 4.2 by either downloading the HP Systems InsightManager software from http://www.hp.com/go/hpsim, and select Download or fromthe HP 7.20 Management CD.

b. Start the migration process by launching setup.exe from the download package orfrom the Management CD, select Products->HP Systems Insight Manager->Install.

The HP Systems Insight Manager Welcome screen appears. The Welcome screen displayslinks to the following documentation:




c. A background setup screen appears showing that Pre-Installation is “In Progress”. If thePerformance Management Pack that was installed with Insight Manager 7 is detected onyour system, the Performance Management Pack Migration Utility for data export islaunched. Follow the screen prompts to completion before continuing with the InsightManager 7 data export

d. On completion of the data export for the Performance Management Pack, setup detectsthat you are running Insight Manager 7 Service Pack 2.3, or later and automaticallylaunches the HP Systems Insight Manager Data Migration Tool. The Data Migration Tooldialog screen appears

57



Note:

If Insight Manager 7 Service Pack 2, 2.1 or 2.2 is detected, theHP Systems Insight Manager Data Migration Tool displays an optionto upgrade to Insight Manager 7 Service Pack 2.3. Select thisoption and follow the screen prompts to install the Softpaq. Whencomplete, launch setup.exe again from the download packageor from the Management CD, select Products->HP SystemsInsight Manager->Install again to start the export of InsightManager 7 data.

e. Click Next to continue.

f. Click Next to confirm data export to the following file: C:\ProgramFiles\HP\Systems Insight Manager Data MigrationTool\user-data.dmt. Export of data begins.

g. When the export of data successfully completes, click Next.

h. Click the Remote migration (do not disable Insight Manager 7) radio button.

i. Click Next. HP Systems Insight Manager Data Migration Tool export success screenappears and instructs the user to copy the export file to the server where HP SystemsInsight Manager will be installed.

j. Click Finish to exit the Data Migration Tool.The background process will showPre-Installation is “Done” and Installation is “In Progress”

k. Cancel out of the Welcome screen for the HP Systems Insight Manager install. Thebackground setup will show that both Installation and Post-Installation are “Not Done”

l. Click Finish on the background setup screen to close it out.

m. Copy the file C:\Program Files\HP\Systems Insight Manager DataMigration Tool\user-data.dmt to a location where it can be accessed from thenew HP Systems Insight Manager 4.2 server.

n. Copy the file PMP DMT installation directory\data\pmp.jar to a locationwhere it can be accessed from the new HP Systems Insight Manager 4.2 server. ThePerformance Management Pack Data Migration Tool installation directory is usuallyc:\Program Files\HP\Performance Management Pack Data MigrationTool.

o. Go to the server to be used for the new HP Systems Insight Manager, and launchsetup.exe from the download package or from the Management CD, selectProducts->HP Systems Insight Manager->Install to start the HP Systems InsightManager components installation. The background setup screen will show Pre-Installationis “Not Done” and Installation is now “In Progress:”

p. Click Install on the HP Systems Insight Manager welcome screen to begin the installationof HP Systems Insight Manager components. Refer to Chapter 3. Installing on Windows for details.

58


q. Click Finish when the installation is complete to close the HP Systems Insight ManagerInstaller window. The background setup screen will show Installation is “Done” andPost-Installation is “Not Done”.

r. Click Finish on the background setup screen to close it out.

2. Import Insight Manager 7 and Performance Management Pack data:

a. After HP Systems Insight Manager 4.2 and all its components have been installed, launchdmtshell.exe from the download package or from the Management CD on HP SystemsInsight Manager 4.2 server. The background setup screen will NOT display. The InsightManager 7 Data Migration Tool dialog screen automatically appears.

b. Click Next.

c. Specify the location of the user-data.dmt file as noted during the export process whenprompted.

d. Click OK to dismiss the prompt.

e. Click Open when the export file is located.

f. Click Next. Insight Manager 7 Data Import starts. The process might take more than anhour depending upon the amount of user-defined data and the configuration of the HPSystems Insight Manager. A status bar shows the progress.

g. Click OK.

h. Click Finish.

3. If a migration file for the Performance Management Pack was created, launch pmpdmt.exeto import the Performance Management Pack data. Follow the screens to completion, pointingto the location of the pmp.jar file as noted during the export process.

4. If the Performance Management Pack 2.1 server licenses/logged data is migrated and afterHP Performance Management Pack 3.0 is installed, launch pmpshell.exe to importPerformance Management Pack 2.1 server licenses/logged data. Follow the screens tocompletion, pointing to the PMP data file (pmp.jar) as noted during the export process.

5. Reboot the system at this time if any HP Systems Insight Manager components indicated theneed for this.

59


Chapter 7. Upgrading HP SystemsInsight Manager 4.0, 4.0.1 and 4.1to HP Systems Insight Manager 4.2

This chapter provides the steps to upgrade HP Systems Insight Manager 4.0 and 4.1 on Windowsand HP-UX and HP Systems Insight Manager 4.0.1 and 4.1 on Linux systems to HP Systems InsightManager 4.2.

Note:


Serviceguard Manager scenarios

Note:

If you currently have Serviceguard Manager installed on an HP Systems InsightManager 4.0.1 system or HP Servicecontrol Manager (SCM) and upgrade to HPSystems Insight Manager 4.2, some of the Serviceguard Manager files areoverwritten, which disables Serviceguard Manager. Therefore, HP recommendsrenaming or copying the following files and directories before upgrading the CMSand renaming or copying them back to their original locations after the upgrade iscomplete.

● Rename or copy the directory named sgmgr, which can be located at/opt/hpwebadmin/webapps on HP-UX and Linux or at \ProgramFiles\HP\Systems Insight Manager\hpwebadmin\ webapps on aWindows CMS.

● Rename or copy any files that start with sgmgrLauncher.properties, whichcan be located at /opt/hpwebadmin/lib on HP-UX and Linux or at \ProgramFiles\HP\Systems Insight Manager\hpwebadmin\lib on a WindowsCMS.

The following scenarios might appear when installing Serviceguard Manager. When you clickLaunch Serviceguard Manager, you are asked to download a jnlp file.

● Scenario 1: Java Web start not installed.

Solution: Download and Install Java Web start.

● Scenario 2: Java Web start is installed, but you are still being asked to download the .jnlp file.

60

Windows 2003 Internet Explorer Browser Solution

1. Download the .jnlp file.

2. Right-click the .jnlp file.

3. Select Open with...Choose Program.

4. Click Browse.

5. Navigate to C:\Program Files\Java Web Start\javaws.exe, and open it.

6. Select Always use this program to open these files.

7. Click OK.

Linux Mozilla Browser Solution

1. Click Launch Serviceguard Manager.

2. Select Open with.

3. Click Choose.

4. Navigate to /user/java/j2re1.4.2/javaws/javaws

5. Select Always perform this action.

6. Click OK.

HP-UX Mozilla Browser Solution

1. Click Launch Serviceguard Manager.

2. Select Open with.

3. Click Choose.

4. Navigate to/opt/java1.4/jre/javaws/javaws.

Note:

If this path is not present install the T1456AA with Java Web start.

5. Select Always perform this action.

6. Click OK.

61

Upgrading HP Systems Insight Manager 4.0, 4.0.1 and 4.1 to HP Systems Insight Manager4.2

Note:

Upgrading HP Systems Insight Manager 4.0or 4.1 to HP Systems Insight Manager 4.2on Windows

1. Verify that HP Systems Insight Manager 4.0 or 4.1 is running on the system.

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


3. Run setup.exe to launch the HP Systems Insight Manager Installer. The HP SystemsInsight Manager Welcome screen appears. The Welcome screen displays links to the followingdocumentation:




4. Click Install to launch the install process. The HP Systems Insight Manager setup window isdisplayed with three stages which would read as mentioned below:

● Pre-installation. Examines this system for previous versions of Insight Manager 7and runs data export tools as needed.

● Installation. Installs HP Systems Insight Manager and other HP management softwareproducts.

● Post-installation. Runs data import tools as needed to migrate customer data fromprior local installations of Insight Manager 7.

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

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

Refer to Windows Installation Options to view the options available during an upgrade of HPSystems Insight Manager.

62



Note: SSH Server and Version Control Repository Manager components will not be listed ifthey were installed in version 4.0.

Note: If you choose not to install or upgrade a component during the upgrade of HP SystemsInsight Manager, you can re-run the setup.exe and at that time select the components that areto be installed or upgraded.

6. Click Typical to install the components listed under the Available Components for Installwith minimal user interaction or click Custom to select the components you want to install.

Note: The differences between the Typical and Custom installs for this version of HP SystemsInsight Manager is that the Custom option enables you to deselect components in addition toallowing you to change one or more of the following settings for the components:

● Drive● Install directory● Program group

Refer to the preceding table to determine which components listed in the AvailableComponents for Install are mandatory in the Typical install or optional in the Custom install.

7. On the Typical Install - Account Authentication screen, enter the Account Credentialsfor the database server. If your database is local, then the Database Server name field ispre-populated, if your database is not local then you must supply the Database Server name.

Note: In case of a reboot, if you just installed MSDE, the administrative credentials are thoseyou used to log in before installing MSDE. Windows authentication is required to connect tothe SQL server (whether locally or remotely). In addition, these credentials will also be yourHP Systems Insight Manager administrative user login credentials. Any account that is a memberof the administrator group will have administrator rights to MSDE

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

Each component will be installed sequentially, Custom Install will launch them interactively.You may skip to #16.

For the Custom install, you choose the components to install, starting with #8.

9. Installing HP System Management Homepage for an In-Place custom install:

Note:

For more information regarding where the System Management Homepagedefault settings are stored during a Typical installation and how to changethem, refer to the System Management Homepage Installation Guide at:http://h18013.www1.hp.com/products/servers/management/agents/documentation.html

63


http://h18013.www1.hp.com/products/servers/management/agents/documentation.html

Note:

The HP Version Control Agent and HP Version Control Repository Managerlogin to the management web server by way of the System ManagementHomepage. The System Management Homepage is security software thatmust be configured in order to allow the Version Control Agent to connectto the Version Control Repository Manager using operating systemauthentication. For more information regarding migrating version controlto the System Management Homepage Refer to Migrating Version Controlto the System Management Homepage for details.

a. Click Next. The OS Groups dialog box appears. Click Cancel to cancel the installationprocess. If you click Cancel, a message appears, giving you the option to continueinstallation or to exit the installation.

b. Select Administrator, Operator, or User from the Operating Systems Group Namefield.

Note: It is necessary to assign an account to an operating system user group withadministrator privileges to access the Version Control Repository Manager from the VersionControl Agent. Do not use the Administrator account to connect from the Version ControlAgent to the Version Control Repository Manager as it could potentially lock theAdministrator account out. Using the Administrator account, add another account withadministrator privileges to be used for Version Control Repository Manager access.

c. Enter the group name of an operating systems group in the Group Name field.

d. Click Add. The group name is added. A maximum of five entries can be added for eachgroup level.

Note: To delete a group name, select the group name and click Delete.

e. Click Next to continue or Back to return to the previous page. The User Access dialogbox appears.

The User Access dialog box enables you to configure the System ManagementHomepage from the following access types:

● Select Anonymous Access to enable anonymous access to unsecured pages.

● Select Local Access Anonymous or Local Access Administrator to set up theSystem Management Homepage to automatically grant local IP addresses at theselected access level.

Caution: Selecting Local Access with Administrator privileges provides any userswith access to the local console full access without prompting them for a user nameor password.

f. Click Next. The Trust Mode dialog box appears.

g. Select the level of security you want to provide from one of the following trust modes:

● Trust By Certificate

64


i. Click Next. The Trusted Certificates dialog box appears. The TrustedCertificates dialog box allows trusted certificate files to be added to the TrustedCertificate List.

ii. Click Add File to browse and select any certificates to be included in the TrustedCertificate List. The Add File dialog box appears. If an invalid file name isentered in the file name field, an error message appears, indicating the file doesnot exist. Click OK to select another file, or click Cancel to close the dialog box.The Trusted Certificate List appears.

Note: If you click Next without adding any certificates to the list, and nocertificates exist from a previous installation, a message appears indicating thatif you do not specify any trusted certificates, HP Systems Insight Manager cannotaccess the HP Insight Management Agentss on this system. Click OK if you donot want HP Systems Insight Manager to access the Insight Management Agentson this system, or click Cancel to close the dialog box and add the trustedcertificates to the list.

Note: The Trust By Certificates option enables the System ManagementHomepage system and the HP Systems Insight Manager system to establish a trustrelationship by means of certificates. This mode is the strongest method of securitybecause it requires certificate data and verifies the digital signature beforeenabling access.

iii. Click Next. The IP Binding dialog box appears.

or

i. Click Import. The Import Server Certificate dialog box appears.

ii. Enter the name or IP address of the server whose certificate you want to import.

iii. Click Get Cert. The certificate information appears.

iv. Verify the certificate information. If you want to add this certificate to the TrustedCertificate List, click Accept and the certificate is added to the TrustedCertificate List, or click Cancel if you do not want to add it to the TrustedCertificate List. The Trusted Certificate List appears.

Note: You can add an unlimited number of trusted certificates.

v. Click Next. The IP Binding dialog box appears. Click Back to return to theTrust Mode dialog box.


● Trust By Name

i. Select Trust By Name.

ii. Click Next. The Trusted Server dialog box appears.

Note: Although the Trust By Name mode is a slightly stronger method of securitythan the Trust All mode, it still leaves your system vulnerable to security attacks.

65


The Trust By Name mode sets up the System Management Homepage to onlyaccept certain requests from servers with the HP Systems Insight Manager namesdesignated in the Trust By Name field. The Trust By Name option is easy toconfigure and can prevent non-malicious access. For example, you might wantto use the Trust By Name option if you have a secure network, but your networkhas two groups of administrators in two separate divisions. The Trust By Nameoption would prevent one group from installing software to the wrong system.This option does not verify anything other than the HP Systems Insight Managerserver name submitted.

iii. Enter the names of the servers you want to trust.

Note: The server name cannot contain the following characters:

❍ ~

❍ !

❍ `

❍ @

❍ #

❍ $

❍ %

❍ ^

❍ &

❍ *

❍ (

❍ )

❍ +

❍ =

❍ "

❍ :

❍ '

❍ <

❍ >

❍ ?

❍ ,

❍ |

66


❍ ;

iv. Click Add to add the name of a server you want to trust.

v. Click Next. The IP Binding dialog box appears.

Note: If you click Next without adding any server names to the list, an errormessage appears, indicating that if you do not specify any trusted server names,HP Systems Insight Manager cannot access the Insight Management Agents onthis system. Click OK to proceed without trusting any systems, or click Cancel toclose the dialog box and add server names to the list.


● Trust All

i. Select Trust All.

ii. Click Next. The IP Binding dialog box appears.

Note: The Trust All option leaves your system vulnerable to security attacks andsets up the System Management Homepage to accept certain requests from anyserver. For example, you might want to use Trust All if you have a secure network,and everyone in the network is trusted.

h. Select IP Binding to enable the Subnet IP Address and NetMask.

The IP Binding dialog box enables you to bind to specific IP addresses that match aspecific Subnet IP Address or NetMask. It restricts the subnet you want to manage.

i. Enter the Subnet IP Address in the designated field.

ii. Enter the NetMask in the designated field.

iii. Click Add to add the Subnet IP Address/NetMask into the dialog box. Select aSubnet IP Address/NetMask, and click Delete to remove it from the dialog box

Note: You can add up to five Subnet IP Address/NetMask pairs.

Note: If you click IP Binding but do not specify the IP Address/NetMask then youmay not be able to connect to the System Management Homepage.

i. Click Next. The IP Restricted Logins dialog box appears. The IP Restricted Loginsdialog box enables you to select specific IP addresses or IP address ranges to include orexclude from gaining login access. Although optional, the System Management Homepagecan restrict login access based on the IP addresses of the machine attempting to gainaccess.

j. Select IP Restricted Logins, and click Next. The IP Address to Include dialog boxappears. This dialog box enables you to specify the IP address or IP address ranges togrant login access permission. If there are IP addresses in the Inclusion list, then only

67


those IP addresses are enabled for login privileges. If there are no IP addresses in theInclusion list, then login privileges are permitted to all IP addresses that are not in theExclusion list.

Note: A single address and ranges of addresses can be accepted in the IP RestrictionLogins dialog box. Enter the single address in the first box.

i. In the Include field, enter a beginning IP address to which you want to grant loginaccess.

ii. In the To field, enter an ending IP address to which you want to grant login access.All IP address that fall between the beginning and ending IP addresses are grantedlogin access.

iii. Click Add. The IP address or IP address range is added to the Exclusion list. Selectan IP address or IP address range, and click Delete to remove it from the Exclusionlist.

Note: If you entered an invalid IP address or IP address range, an error messageappears indicating the IP address is invalid. Click OK. Enter a valid IP address or IPaddress range, and click Add again.

k. Click Next. The IP Address to Exclude dialog box appears.

i. In the Exclude field, enter a beginning IP address to which you want to deny loginaccess.

ii. In theTo field, enter an ending IP address to which you want to deny login access.All IP addresses that fall between the beginning and ending IP addresses are deniedlogin access.

iii. Click Add. The IP address or IP address range is added to the Inclusion list. Selectan IP address or IP address range, and click Delete to remove it from the Inclusionlist

Note: If you entered an invalid IP address or IP address range, an error messageappears, indicating the IP address is invalid. Click OK. Enter a valid IP address orIP address range, and click Add again.

Note: If Next is selected without adding any IP addresses to either theInclude orExclude lists, a warning message appears stating, IP Restricted Logincheckbox will be marked as disabled. Do you want to proceedwithout adding any IP Address restrictions? If you select OK, the IPRestricted Login option on the IP Restricted Login dialog box is deselected, andthe Install Preview dialog box appears.

l. Click Next. The Install Preview Panel appears. The Install Preview Panel lists thelocation where the System Management Homepage is installed, the amount of space theinstallation requires, and the summary of the options that you specified during theinstallation.

m. Click Next. The installation process is started.

68


Note: During the installation of the System Management Homepage, Cancel is disabled.If you click the X in the upper-right corner of the box, an error message appears, statingthe current operation cannot be canceled.

n. Click Finish to complete the installation.

Note: If this is an upgrade, HP recommends that you configure System ManagementHomepage to use operating system authentication for HP Version Control Agent accessto HP Version Control Repository Manager, and then re-configure the servers running HPVersion Control Agent to point to the new account. If these actions are not taken, pre-7.20HP Version Control Agent will access your upgraded HP Version Control RepositoryManager via legacy HTTP Server account access. For more information, refer to VersionControl Installation Guide athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html/.If this is a new install, an operating system account must be created and configured inthe System Management Homepage on this computer and each of the HP Version ControlAgent must be configured to use the new account. For more information, refer to VersionControl Installation Guide athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html/.

Note:If HP Systems Insight Manager is installed after System Management Homepageis installed, the System Management Homepage 2048-bit key pair will be replaced withthe HP Systems Insight Manager1024-bit key pair.

10. Installing OpenSSH for a custom install:


b. Select the destination location using the Browse button.

c. Click OK.

d. Click Next. The Ready to Install screen appears.

e. Click Install to continue with the installation, or click Back to make changes.

f. After installing OpenSSH, click No, I will restart the computer later.

g. Click Finish.

11. Installing HP Systems Insight Manager for a custom install:

a. Click Next on the HP Systems Insight Manager welcome screen.

b. Read the information screen. Click Next. The Database Configuration screen appears.

c. Enter the password and database server name. If your database is local, then the DatabaseServer name field is pre-populated, if your database is not local you must supply the nameof the Database Server.

Note: HP Systems Insight Manager creates a database name with the format“Insight_V42_0_(timestamp).” For example, “Insight_V42_0_123456.” It then updatesdatabase.props and the DSN with this value. The database.props file can be found inC:\Program Files\HP\Systems InsightManager\Config

69






d. Click Next. The Destination Location screen appears.

e. Select the destination location by clicking the Browse button.

f. Click OK.

g. Click Next. The Select Start menu folder appears.

h. Select or enter a different folder name.

i. Click Next. The ready to install screen appears.

j. Click Install to install HP Systems Insight Manager, The Install Progress Screen appearsor click Back to make any changes.

k. Click Finish when the installation is complete to close the HP Systems Insight ManagerInstaller window.

12. Installing WMI Mapper for a custom install:


b. The End-User License Agreement screen appears. Click I accept the agreement.

c. Choose Setup Type screen appears. Chose the setup type.

d. Select the destination location using the Browse button.

e. Click OK.

f. Click Next. The Ready to install screen appears.

g. Click Install to continue with the installation, or click Back to make changes.

h. Click Finish.

13. Installing the HP Performance Management Pack for a custom install:

Note:The HP Performance Management Pack requires HP Systems Insight Manager 4.1 beinstalled on your system before installing the HP Performance Management Pack.

Note:During the installation of the HP Performance Management Pack, the warning isdisplayed: "As part of HP Performance Management Pack installation the HP Systems InsightManager service must be stopped and restarted." Click OK to stop the service and continuewith the HP Performance Management Pack installation, or click Cancel to abort the installation.




d. Click Finish to exit Performance Management Pack setup.

14. Installing HP Version Control Repository Manager for a custom install:

70


a. Click Install to install HP Version Control Repository Manager. The HP Version ControlRepository Manager setup screen appears.

b. Click Install.

c. Click the Browse button to select the directory from which HP Version Control RepositoryManager will retrieve support pack information. This directory must be manually createdlater if it does not exist.

d. Click OK.

e. Click Next.

f. Select the Enable Automatic Update checkbox to enable automatic downloading ofProLiant Support Packs and components at a specified interval and time.

g. Click Finish. Installation of HP Version Control Repository Manager proceeds andcompletes.

15. Installing HP ProLiant Essentials Virtual Machine Management Pack for a custom install:

Note: During the installation of the HP ProLiant Essentials Virtual Machine Management Pack,the warning is displayed: "As part of . HP ProLiant Essentials Virtual Machine ManagementPack installation the HP Systems Insight Manager service must be stopped and restarted."Click OK to stop the service and continue with the HP ProLiant Essentials Virtual MachineManagement Pack installation, or click Cancel to abort the installation. If you clicked OK theHP ProLiant Essentials Virtual Machine Management Pack Welcome screen appears.




d. Click Finish to exit HP ProLiant Essentials Virtual Machine Management Pack setup.

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

Note: During the Custom Install process, do not select the reboot now option if a componentrequests this. Reboot only after all components have been installed.

17. Click Finish to complete the component installation that you selected.

Note: Click Finish in the Initial Setup HP Systems Insight Manager window, to complete theinstallation.

Upgrading HP Systems Insight Manager 4.0.or 4.1 to HP Systems Insight Manager 4.2on HP-UX

• Install HP Systems Insight Manager:

71





Note: After the last step completes, view the file /var/opt/mx/logs/initconfig.log toverify that the initialization completed. This step could take several minutes. You can also typetail –f /var/opt/mx/logs/initconfig.log to verify that the initialization completed.

Upgrading HP Systems Insight Manager4.0.1 or 4.1 to HP Systems Insight Manager4.2 on Linux

1. Extract the rpm files from the bin file. Be sure you set the permissions to include the right toexecute the bin for the following step.

./T2416BA_4.02.00_Linux.bin \ --keep --confirm

Note: Refer to Step 5 in the "Installing on Linux - Preparing the System" section for informationon setting permissions.

2. Respond negatively to the prompt to run scripts for an automatic install. The extracted files areplaced in an mxserver subdirectory.

3. Enter cd mxserver.

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

rpm -U hpsim-C.4.02.0.0-1.i386.rpmhpsim-pgsql-config-C.4.02.0.0-1.i386.rpm

Note: Both files must be installed concurrently with a single command (no carriage return).

Note: This step can be completed successfully in less time. The initialization of the upgradeis done in the background, which takes several minutes. To verify if the upgrade is complete,view the file by executing:

cat/var/opt/mx/logs/initconfig.log

72


Chapter 8. Upgrading from HPServicecontrol Manager to HPSystems Insight Manager

The HP Systems Insight Manager upgrade installs the HP Systems Insight Manager 4.2 files andmigrates your HP Servicecontrol Manager (SCM) data to be compatible with HP Systems InsightManager 4.2. The upgrade installation migrates all custom data including:

● Users

● Systems

● System groups

● Tools

● Toolboxes

● Authorizations

HP Servicecontrol Manager and HP Systems Insight Manager cannot coexist on the same system.

Note:

Migration from HP Servicecontrol Manager 3.0 to HP Systems Insight Manager 4.2on a Linux CMS is not supported.

Note:

You must be running SCM 3.0 to upgrade to HP Systems Insight Manager 4.2. Ifyou are running a version of SCM earlier than 3.0, you must upgrade to 3.0 beforeupgrading to HP Systems Insight Manager 4.2. Refer to the HP ServicecontrolManager 3.0 User Guide for information on upgrading from SCM 2.5 to SCM 3.0.

Note:

Before upgrading SCM 3.0 to HP Systems Insight Manager 4.2, managed systemsshould be upgraded and have SSH installed.

73

Note:


Note:

If you currently have ServiceGuard Manager installed on an SCM 3.0 system andupgrade to HP Systems Insight Manager 4.2, you must reinstall ServiceGuardManager; integration with HP Systems Insight Manager (ability to launchServiceGuard Manager), requires HP Systems Insight Manager to be installed first.

$ swlist -l bundle B8325BA B8325BA A.04.00 ServiceGuardManager

Upgrading from SCM 3.0 to HP SystemsInsight Manager 4.2

Note:

During an upgrade of SCM 3.0 to HP Systems Insight Manager, the existing databaseis migrated and the password is preserved in the backup directory.

Note:

When upgrading SCM 3.0 to HP Systems Insight Manager, new RMI keys and akeystore are created. The keystore is moved to a backup directory.

Steps 7 through 9 are optional:

1. To upgrade SCM 3.0 to HP Systems Insight Manager, first verify that SCM is running byentering the following:

ps -ef | grep mx

Wait some time, and if they are not running, start the service:

/opt/mx/bin/mxstart

74

Upgrading from HP Servicecontrol Manager to HP Systems Insight Manager

2. Tune the kernel using the JavaOOB (Java-out-of-box) fileset. For information on this, go tohttp://www.hp.com/products1/unix/java/java2/outofbox/index.html. This product may beavailable for you to install with HP Systems Insight Manager, either as part of the downloaddepot file containing HP Systems Insight Manager 4.2. or from the Application Release media.The kernel parameter values it adjusts are listed in the table below.

Note:

Java Out-of-Box is a stand-alone bundle that upon installation will rebootthe system.

Java Out-of-Box Settings

=3000max_thread_proc

=2063835136maxdsize

=2048maxfiles

=2048maxfiles_lim

=512maxusers

=6000ncallout

=4097nfile

=6000nkthread

=2048nproc

=2048tcp_conn_request_max

Note:

The maxusers parameter is obsolete in HP-UX 11i v2 (B.11.23).

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

a. The JOOB file will only set the nfile parameter to 4097. Increase the nfile parameterto at least 12000. This value might need to be increased to 30000 depending on yourenvironment. If you get an error that you cannot open a file, increase this value.

b. 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 physical memory thatequals 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%.

75


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

Note: For HP-UX 11i v2 (B.11.23) these parameters are dynamic and when you modifythe parameters a reboot of the system is not necessary.

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

swinstall -s /directory/depot T1458AA ixPostgreSQL T1471AA B8465BA


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

5. Install HP Systems Insight Manager:





ps -ef | grep mx


/opt/mx/bin/mxstart

7. Configure SNMP to send traps to the CMS:

a. Add the full hostname or IP address of the CMS as a trapdest in the file/etc/SnmpAgent.d/snmpd.conf

trap-dest: hostname_or_ip_address




/usr/sbin/snmpd

8. Log into the HP Systems Insight Manager GUI. For assistance with this, refer to Chapter 10. Using the Graphical User Interface

9. If after logging into HP Systems Insight Manager, you find that some items (toolboxes, users,tools, systems, system groups, or authorizations) did not upgrade correctly, perform thefollowing. Otherwise, skip to step 10.

IMPORTANT: These steps must be performed in the order specified. You can, however, skipto the first step that applies to you. For example, if node groups and authorizations failed tomigrate, but everything else migrated properly, start with step e.

76


a. Migrate toolboxes (roles) by running the following command from the command line onthe CMS.

mxtoolbox -af /var/opt/mx/bak/3.0/zzz_mxrole.3_0.xml

If the message A toolbox named <toolbox> already exists in the systemis displayed, log into HP Systems Insight Manager and delete all toolboxes except for AllTools and Monitor Tools, and repeat this step.

b. Migrate users by running the following command from the command line on the CMS.

mxuser -af /var/opt/mx/bak/3.0/zzz_mxuser.3_0.xml

If the message A user named <user> already exists in the system isdisplayed, log into HP Systems Insight Manager and delete all users except for the userused to log in, and repeat this step.

c. Migrate tools by running the following command from the command line on the CMS:

mxtool -af /var/opt/mx/bak/3.0/zzz_mxtool.3_0.xml

This can display many Cannot add <tool> because it already exists inthe system messages, but these can be safely ignored.

d. Migrate updated definition of tools and ensure all the tools are displayed correctly withinthe HP Systems Insight Manager tool menu by running the following command from thecommand line: sh fixmenu.sh scmtdefs.data /var/opt/mx/bak/3.0/tools/var/opt/mx/tools

e. Migrate systems (nodes) by running the following command from the command line onthe Central Management Server.

mxnode -af /var/opt/mx/bak/3.0/zzz_mxnode.3_0.xml

If mxnode encounters any duplicate systems (nodes), it will continue properly withoutdisplaying any messages.

If mxnode encounters a hostname that cannot be resolved, the following error messageis displayed. Unknown host: <node_name>. Node ignored. The remaining nodeswill continue to be processed. However, the missing node might affect the success ofmigrating node groups.

IMPORTAINT: When the command returns, log into HP Systems Insight Manager, displaythe All Systems list, and wait for all of the expected nodes to appear in the list beforeproceeding to the next step. The amount of time varies based on system performance andthe number of nodes being added.

f. Migrate system groups (node groups) by running the following command from thecommand line on the CMS.

mxngroup -af /var/opt/mx/bak/3.0/zzz_mxngroup.3_0.xml

If the message A node group named <group> already exists in thissystem is displayed, log into HP Systems Insight Manager and delete all node groupsexcept for All Managed Systems and CMS, and repeat this step.

77


If the message The name <node_name> does not represent a node in thissystem is displayed, then a node in the node group is missing, and processing on thefile stops. Add the node using mxnode -a <node_name> or log into HP Systems InsightManager and add the node through Manual Discovery, then repeat this step.

g. Migrate authorizations by running the following command from the command line on theCMS.

mxauth -af /var/opt/mx/bak/3.0/zzz_mxauth.3_0.xml

If this command encounters any duplicate authorizations, it continues properly withoutdisplaying any messages.

Note: If the names contain characters such as underscore, space, and symbols, theymight not be migrated because these characters are not supported.

h. If after taking the above steps, items such as menus are still missing or out of place, runthe following command:

sh /opt/mx/bin/fixmenu.sh scmtdefs.data /var/opt/mx/bak/3.0/tools/var/opt/mx/tools


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


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.

Note: After upgrading to HP Systems Insight Manager, you must run identification for all networkdevices, racks, and enclosures to be displayed on the System Overview page.

Upgrading Existing Managed Systems1. Install SSH on the managed systems:

On HP-UX:

a. Set up a depot that includes the SSH product.

b. Run the Install Software command on all HP-UX DTF managed systems.

mxexec -t "Install Software" -n <hpux_nodes>

This tool is multiple-system aware (MSA) and requires a DISPLAY to run a GUI.

2. Upgrade the CMS. Refer to "Upgrading from SCM 3.0 to HP Systems Insight Manager 4.2" .

78


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

Important: If the CMS is not an HP-UX system: On a non-English CMS, ensure that anadministrator account (spelled exactly as follows, administrator) exists on the CMS, and thatmxagentconfig has been run on the CMS for the created administrator account.

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

mxagentconfig -g

b. Enter the Hostname of the managed system.

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

Note: If the password for the mxagentconfig command contains a special characterlike & or $, it fails unless the password is contained by single quotation marks.

d. Click Connect.

Alternatively you can configure SSH via the command line version of mxagentconfig. On theCMS, type "mxagentconfig -?" for usage.

Note:

Using the -p option will make the passwd available in "ps" output, so useof the -f option (with a file only readable by root) is highly recommendedwhen using mxagentconfig -a. If the –p using option is used, enclose thepassword in single quotes if the password has any special characters like& or $

79


Chapter 9. Uninstalling HPSystems Insight Manager Uninstalling HP Systems Insight Managerfrom a Windows System

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

1. Remove the HP Performance Management Pack.

Note: Removing HP Performance Management Pack does not remove its database files. Ifyou plan to reinstall HP Performance Management Pack rename or remove the old database.

2. Remove HP Systems Insight Manager.

Note: Removing HP Systems Insight Manager does not remove its database files. If you planto reinstall HP Systems Insight Manager rename or remove the old database.

3. (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 CMS, youmight 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.

b. Remove the WMI Mapper.

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

d. Remove the Version Control Repository Manager.

4. Reboot the system if any of the uninstall processes require this action.

Uninstalling HP Systems Insight Managerfrom an HP-UX System

Caution:

Removing HP Systems Insight Manager permanently deletes the information in thedatabase unless you back it up before removing the software.

1. Stop the HP Systems Insight Manager daemons:

mxstop

80

2. Verify that the daemons are no longer running:

ps -ef | grep mx

If any of the HP Systems Insight Manager daemons are running, note their process IDs (PIDs)in the ps -ef output, and kill them:

kill -9 PID

where PID is the process ID of the daemon. For example, if the ps -ef | grep mx commanddisplays a line that looks like

root 18582 1 0 Jan 12 ? 00:13:18 /opt/mx/mxagent, then the command to killthis daemon is

kill -9 18582

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

mxrepositorysave -f filename

where filename is the name of the backup file.

4. Remove the HP Systems Insight Manager software:

swremove –x enforce_dependencies=false 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 CMS, youmight want to leave SSH and WBEM installed on this system.

a. Remove Java:

swremove T1458AA

b. Remove PostgreSQL:

swremove –x enforce_dependencies=false ixPostgreSQL

c. Remove SSH:

swremove –x enforce_dependencies=false T1471AA

d. Remove WBEM:

swremove –x enforce_dependencies=false B8465BA

81

Uninstalling HP Systems Insight Manager

Uninstalling HP Systems Insight Managerfrom a Linux System

Caution:

Removing HP Systems Insight Manager permanently deletes the information in thedatabase unless you back it up before 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 PID and kill theprocess:

kill -9 pid

where pid is the PID of the daemon. For example,

kill -9 3456

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,save this backup in a location outside of the default product directories.

4. Remove the HP Systems Insight Manager software:

rpm -qa | grep hpsim | xargs rpm -e

5. (Optional) If other applications are not using PostgreSQL, you can remove it:

rpm -qa | grep postgresql | xargs rpm -e

82

Uninstalling HP Systems Insight Manager

Chapter 10. Using the GraphicalUser Interface

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

Accessing the GUIThe GUI can be accessed from any network client that is running a supported Web browser. Referto "Network Client Requirements and Recommendations" for a list of supported browsers.

Required Java Plug-inWhen you navigate to the HP Systems Insight Manager GUI, it ensures you have the correct versionof the Java Runtime Environment (JRE) installed. If you do not, it prompts you to install the correctversion. When installing the JRE, HP recommends that you select the Custom install option anddeselect the options for this to be the default Java runtime for Internet Explorer and Netscape.Failure to follow this configuration can cause issues with other Web applications.

Note:

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

cd /usr/local/mozilla/pluginsmv libjavaplugin_oji.so libjavaplugin_oji.so.bakln -s /usr/java/j2re1.4.2_03/plugin/i386/ns610-gcc32/ libjavaplugin_oji.so

To log into 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.

83

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

The five regions in the GUI include:

1. Banner with summary views. The banner provides a link to the Home page and alink to Logout. 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 of 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 online 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 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 intoHP Systems Insight Manager. By default, the introductory page is displayed as the Homepage.

1

2

3

4

5

84

Using 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. Refer to "Customizing the Home Page" for information on selectinga different introductory page. The following figure is a sample screen shot of the introductory page.

The four default sections on the introductory page include:

1. DO THIS NOW to finish the install. This section only appears if the following conditionsare met:

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

2. Monitor. This section provides links to common monitoring tasks, including locating andtracking systems, clusters, and events. All monitoring tasks can be performed using the featuresand tools provided in the system and event list area.

3. Manage. This section provides links to frequently used tools and features available fromthe menus above the workspace. These links provide access to inventory reports, software andfirmware 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.

1

2 3

4

85


Customizing the GUICustomizing the Home Page

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 selecting Options->Home Page Settings.

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

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

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 deselecting:

● Show "Do this now to finish the install" frame. If selected, this section is displayed onthe Home page.

● Show the "Did You Know?" image. If selected, the image in the bottom right corner ofthe Home page is displayed.

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

To customize the banner:

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

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

86


a. Select the Condition.

b. Select the system list All Systems, or select a system list from the dropdown list.

c. Edit the Label if desired.

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

5. Click 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 disabled.The legend is enabled. All personalized information is removed.

87


Chapter 11. Using the CommandLine Interface

HP Systems Insight Manager provides a command line interface (CLI) in addition to the GUI. Manyfunctions available in the GUI are also available through the CLI.

Logging into 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. For security reasons, administrators should not modify the accesscontrol settings put in place by the installer.

Directly on the CMSTo log into the CLI directly on the CMS:

1. Log into 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 neither provides a secure connection.

To log into the CLI remotely using an SSH client:

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

2. Log into 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.

88

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 manpages from the command line on an HP-UX, Linux, or Windows system use thefollowing manpage sections:

● For HP-UX:

❍ Administrative command manpages are section 1M.❍ Special file manpages are section 4.

● For Linux:

❍ Administrative command manpages are section 8.❍ Special file manpages are section 4.

● For Windows:

❍ HP\Systems InsightManager\hpwebadmin\webapps\mxhelp\mxportal\en\manpages

The following table provides a complete list of HP Systems Insight Manager commands. For adetailed explanation of these commands, view the associated manpages from a command promptor see the HP Systems Insight Manager online help.

Available manpagesFunctionalityCommandmcompile(1M)Compiles an Simple Network

Management Protocol (SNMP)Management Information Base(MIB) file into an intermediateformat (.CFG) file for importinginto HP Systems InsightManager using the mxmibcommand

mcompile

89

Using the Command Line Interface

Available manpagesFunctionalityCommandmxagentconfig(1M)Configures the agent to work

with a central managementserver (CMS)

mxagentconfig

mxauth(1M) and mxauth(4)Adds, removes, or lists atoolbox-based authorization

mxauth

mxdomainmgr(1M)Contains the object managersthat interact with the databaseand the Distributed Task Facility(DTF)

mxdomainmgr

mxdtf(1M)Contains the DTF that is used toremotely execute commands onmanaged systems that areequipped with Secure Shell(SSH)

mxdtf

mxexec(1M)Executes HP Systems InsightManager tools, with associatedarguments, on specific HPSystems Insight Managermanaged nodes and nodegroups as well as verifies thestatus of running tools andenables a full configurationrights user to kill or cancel arunning task

mxexec

mxinitconfig(1M) andmxinitconfig(4)

Performs initial configuration forthe CMS

mxinitconfig

mxmib(1M)Adds, deletes, and processes alist of MIBs for HP SystemsInsight Manager and listsregistered MIBs and traps for aspecific registered MIB

mxmib

mxngroup(1M) and mxngroup(4)Adds, modifies, removes, or listssystem groups from HP SystemsInsight Manager

mxngroup

mxnode(1M) and mxnode(4)Add, modify, identify, removeor lists nodes in the HP SystemsInsight Manager managementdomain

mxnode

mxnodesecurity(1M)Adds, modifies, or removessecurity credentials for SNMPand Web-Based EnterpriseManagement (WBEM) protocols

mxnodesecurity

mxpassword(1M)Adds, lists, modifies, or removespasswords stored in HP SystemsInsight Manager

mxpassword

mxquery(1M) and mxquery(4)Adds, lists, modifies, or removeslists in HP Systems InsightManager

mxquery

90


Available manpagesFunctionalityCommandmxrepositoryrestore(1M)Restores the HP Systems Insight

Manager database from apreviously created backup

mxrepositoryrestore(HP-UX and Linux only)

mxrepositorysave(1M)Backs up the HP Systems InsightManager database

mxrepositorysave (HP-UXand Linux only)

mxserver(1M)Starts, stops, and changes theSSL port number for theembedded Web server on theCMS

mxserver

mxstart(1M)Starts daemons or processesused by the CMS

mxstart

mxstm(1M)Adds, removes, and lists SystemType Manager rules

mxstm

mxstop(1M)Stops daemons or processesused by the CMS

mxstop

mxtask(1M) and mxtask(4)Lists, executes, removes,creates, and changes ownershipfor the HP Systems InsightManager scheduled tasks

mxtask

mxtool(1M) and mxtool(4)Adds, modifies, and removestools from HP Systems InsightManager

mxtool

mxtoolbox(1M) and mxtoolbox(4)Adds, modifies, or removestoolboxes from the HP SystemsInsight Manager system

mxtoolbox

mxuser(1M) and mxuser(4)Adds, modifies, removes, or listsusers in HP Systems InsightManager

mxuser

mxwbemsub(1M)Performs WBEM indicationsubscription functions on a setof systems, such as adding,deleting, listing or movingsubscriptions on each of thesystems passed in as arguments

mxwbemsub

91


Chapter 12. Initial Setup Introduction

The initial 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, itmight 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.

Setting 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 based on the managed systems operating system.

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

Setting Up HP-UX Managed SystemsTo set up an HP-UX managed system, these steps must be done:

1. Install and configure SSH (bundle T1471AA)

2. Install and configure WBEM (bundle B8465BA)

3. (Optional) Configure SNMP to send traps to the CMS

4. (Optional) Configure DMI on HPUX 11.11 systems (this step is not needed if WBEM installed)

SSH and WBEM are installed on HPUX 11.23 systems by default. For 11.11 systems, checkif installed with this command:

swlist B8465BA T1471AA

1. Install SSH on the managed system if not previously installed.

swinstall -s /directory/depot T1471AA

92


swinstall -s /tmp/HPSIM_download.depot T1471AA

2. Install WBEM on the managed system if not previously installed.

swinstall -s /directory/depot 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 B8465BA

3. Configure SNMP to send traps to the CMS:

a. Add the full hostname or IP address of the CMS as a trapdest in the file/etc/SnmpAgent.d/snmpd.conf

trap-dest: hostname_or_ip_address




/usr/sbin/snmpd

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

Note:

DMI only needs to be configured for HP-UX 11.11 and only if WBEM isnot installed.

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

5. Log into the HP Systems Insight Manager GUI. For assistance with this, refer to . Chapter 10. Using the Graphical User Interface Using the GUI, add the default WBEMuser name and password to the Global Protocol Settings page.

93

Initial Setup

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.

c. Click OK.

Note:

An account for at least one of the WBEM user name and passwordcombinations must exist on each managed system. If the user in the GlobalProtocol Settings does not exist on the managed node you can set per-systemWBEM user names and passwords from the System Protocol Settingspage.

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

1. Install and configure SSH.

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

rpm -qa | grep ssh

If it is not 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).

Important: On a non-English CMS, ensure that an administrator account (spelled exactlyas follows, administrator) exists on the CMS, and that mxagentconfig has been runon the CMS for the created administrator account.

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

mxagentconfig

ii. Enter the Hostname of the managed system.

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

Note: If the password for the mxagentconfig command contains a specialcharacter like & or $, it fails unless the password is contained by single quotationmarks.

iv. Click Connect.

94

Initial Setup

2. Configure the system to send SNMP traps.

Note: These steps might vary slightly, depending on your version of Linux. Refer to your Linuxprovider for details if these file paths and file names do not exist on your system.

a. Verify that SNMP is installed:

rpm -qa | grep snmp

If it is not installed, refer to your Linux provider for information on installing SNMP.

b. If you have not installed the HP Server Management Drivers and Agents from the ProLiantSupport Pack for Linux, omit this step. Otherwise, stop the HP Server and ManagementDrivers and Agents daemons on the platform where you are installing HP Systems InsightManager using the following command:

/etc/init.d/hpasm stop

Note: If the HP Server Management Drivers and Agents daemon is not installed, omitthis step and step F.

c. Stop the SNMP daemon:

/etc/init.d/snmpd stop

d. Edit the snmpd.conf file using any text editor.

For Red Hat Linux run the following command for opening this file in the vi editor: vi/etc/snmp/snmpd.conf

For SuSE SLES 8 run the following command for opening this file in the vi editor: vi/usr/share/snmp/snmpd.conf

i. Remove the comment symbol (#) from the trapsink line, and add the IP address ofthe CMS:

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. To save and close this file using the vi editor, press theEsc key, enter :wq!, and press the Enter key.

e. Start the SNMP daemon:

/etc/init.d/snmpd start

f. Start the HP Server Management Drivers and Agents daemon if it is installed on yoursystem:

95

Initial Setup

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






c. Click OK.

Note:


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





c. Click OK.

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

96

Initial Setup

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

Note:

With HP Systems Insight Manager 4.1, SSH on Windows can be setup along withinstalling the Initial PSP, which is in step 4.

1. Install and configure SSH.

a. Select Deploy->Deploy Drivers, Firmware and Agents->Initial ProLiant SupportPack Install. The Initial ProLiant Support Pack Install page is displayed.

b. Select the target systems.

c. Click Next.

d. From the Enter Windows login credentials page:

i. In the User name field, enter the Windows administrator user name.

ii. In the Password field, enter the administrator password for the Windows user nameentered above.

iii. In the Password (Verify) field, reenter the Windows administrator password exactlyas it was entered in the Password field.

iv. In the Domain field, enter the Windows domain.

e. Click Next. The Select a Windows Support Pack page is displayed.

f. Under Select a Version Control Repository, select a source repository system fromwhich to retrieve the catalog.

The following fields are displayed:

● Name. This field displays the name of the system.

● Status. This field displays the status of the system.

● Product Name. This field displays the name of the product.

● Trusted?. This field indicates whether the system trust relationship has been configured.To configure a trust relationship, click configure.

Note: This section displays systems that are authorized by the current user name. If thecurrent user is not authorized to view the systems, a message is displayed, indicating thatthe user does not have authorization rights on the system.

g. Under Select a Support Pack to Install, select a support pack to install. Click the icon to drill down and view the contents of the Version Control Repository that you selected.

97

Initial Setup

Note: To expand the System Software Baseline to display all contents, click the icon located in the upper right corner of the Select a Support Pack to Install section.Click the icon to collapse the listings.

h. Select Install and initialize SSH (Secure Shell) if you want to install OpenSSH on thetarget systems. This option is disabled by default.

i. Optional. Select Force downgrade if necessary if you are installing a ProLiant SupportPack that is older than the version currently installed. This option is disabled by default.

j. By default, Reboot systems if necessary after successful install is selected. You candeselect this option if you do not want to reboot after the installation. However, the systemmust be rebooted for the new ProLiant Support Pack to be available.

k. Click Next. The Configure Support Pack page is displayed.

● If you selected a ProLiant Support Pack 7.10 or earlier, Configure a Support Packis displayed.

To configure the support pack:

a. Click Configure Support Pack to set up the HP Version Control Agent in theselected Support Pack. The Version Control Agent Setup page is displayed.

Note: If the Version Control Agent has already been configured, you can skipthis step.

b. In the Computer Name field, enter the name of the system where the VersionControl Repository Manager is installed.

c. In the Login Account field, enter the login name used to connect to the VersionControl Repository Manager on the system specified.

d. In the Login Password field, enter the password associated with the login namespecified.

e. Click Save to save your settings. Click Cancel to discard your settings and closethe Version Control Agent Setup page.

f. Click Next.

● If you selected a ProLiant Support Pack 7.20 or later, the following options aredisplayed.

❍ Click Configure System Management Homepage to setup the Support Pack toestablish a trust relationship with System Management Homepage when it isinstalled on target systems.

Note: If the Support Pack has already been configured, you can skip this step.

Note: After the trust relationship is established, click Last Update to update thestatus to trusted.

To configure the System Management Homepage:

98

Initial Setup

a. In the Computer Name field, enter the name of the system on which the HPVersion Control Repository Manager is installed.

b. In the Administrator Password field, enter the password associated withthe system you entered.

c. Click System Management Homepage Setup. In the Password field, enterthe administrator password.

d. Click HP Systems Insight Manager Trust on the left. Set up the trustinformation as necessary.

e. Click Save. A message box is displayed, indicating whether the updates weresaved.

f. Click Close.

g. Click Next.

● Click Configure Version Control Agent to set up the HP Version Control Agent inthe selected Support Pack.

Note: If the Version Control Agent has already been configured, you can skip thisstep.

To configure the Version Control Agent:

a. In the Computer Name field, enter the name of the system where the VersionControl Repository Manager is installed.

b. In the Login Account field, enter the login name used to connect to the VersionControl Repository Manager on the system specified.

c. In the Login Password field, enter the password associated with the login namespecified.

d. Click Save to save your settings. Click Cancel to discard your settings and closethe Version Control Agent Setup page.

e. Click Next.

l. Back in HP Systems Insight Manager, click Next to start the ProLiant Support Packdownload

2. Configure the managed system to send SNMP traps.

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.

99

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.

i. Click Apply to save the changes, and click OK to close the dialog box.






c. Click OK.

Note:


4. Using the GUI, install the ProLiant Support Pack on the managed system. Select Deploy->DeployDrivers, Firmware and Agents->Initial ProLiant Support Pack Install->Install Softwareand Firmware, and refer to the Use Default Tools section of the on-line help for moreinformation.

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




100

Initial Setup



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

c. Click OK.

Configuring Protocol SettingsConfiguring the protocol settings defines what systems are added to HP Systems Insight Managerusing discovery.

To configure the protocol settings:

1. Select Options->Protocol Settings->Global Protocol Settings. The Global ProtocolSettings page is displayed.

2. In the Default ping settings section, select either Use the ICMP protocol for systemreachability (ping) check or Use the TCP protocol for system reachability (ping) checkport number 80. The Use the ICMP protocol for system reachability (ping) check checkis the default and recommended setting.

Select Use the TCP protocol for system reachable (ping) check. port number 80 if yourcompany has disabled ICMP on the corporate network or the corporate policy mandatessystem firewall software to filter out ICMP requests. For example, Windows XP has this featurebuilt in and can result in systems not being automatically discovered. This option enables youto run HP Systems Insight Manager and ping all available systems.

Note: This option only applies to IP-based systems and is available for global, system-widesettings that are used when managing all systems in HP Systems Insight Manager. It is usedby automatic discovery, hardware status polling, the ping tool, and any other tool that mustverify system availability. This option is not available on a single-system basis.

Note: If you select Use the TCP protocol for system reachable (ping) check. port number80, even though HP Systems Insight Manager attempts a connection request to the currentsystem, that system does not need any additional software running on it for this option to work.For example, HP does not require that a Web server be running on port 80. Some networkingdevices might not respond to the TCP request, which is typically seen in low end networkingequipment. Manual addition can be made if it is necessary. However, this system displays asCritical if hardware status polling is run.

3. Also in the Default ping (ICMP) settings section, set the Default timeout and the Defaultretries. If some systems are managed over a wide area network (WAN) or satellite link, usea larger timeout (for example, 5 seconds) with at least one retry. For a local area network(LAN), a shorter timeout can be used. This can be configured on a single-system basis.

4. In the Default WBEM settings section, select the Enable WBEM checkbox to allow WBEMrequests to be sent. Enabled is the default setting. Enter as many default user names andpasswords as needed. The identification process attempts each of these user name andpassword pairs until a successful response is obtained. Future WBEM requests to that systemuse the user name and password that succeeded. For Windows-based systems, the user nameshould include the domain name, for example, domainname\username.

101

Initial Setup

Note: Order the name and password pairs such that root and administrator passwords arelisted first and user and guest passwords are listed second. This order minimizes the searchtime.

5. In the Default HTTP settings section, select the Enable HTTP and HTTPS if it is necessaryto allow Web-based agents and other HTTP port scans to be identified. HP recommends leavingthis option enabled for proper management and discovery of systems.

6. In the Default SNMP settings section, select the Enable SNMP checkbox, which is the systemdefault, and set the Default timeout and Default retries. If some systems are managed overa WAN or satellite link, use a larger timeout (for example, 5 seconds) with at least one retry.For a LAN, a shorter timeout can be used. These settings can also be configured on asingle-system basis.

7. Enter the Default write community string. This value is case-sensitive. Only a few tools needthis option set. Community strings are case-sensitive.

8. Enter the Read community string. This value is case sensitive. Enter as many as needed.The identification process attempts communication to the system, using each of thesecommunities in succession until a successful response is obtained. Future SNMP requests thenuse the community string that provided a successful response.

9. In the Default DMI settings section, select the Enable DMI checkbox, which is the defaultsetting, to enable DMI identification to run on systems. DMI is used to manage some olderdesktops, HP-UX servers, and some third-party servers. If you do not need to manage thesekinds of systems, DMI can be disabled to improve discovery performance.

Note: DMI is not currently supported on Linux systems and is not shown in the user interface.

Note: If DMI is disabled and some systems no longer have a correct system type or productname, re-enable DMI.

10. Click OK to accept the settings.

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

● Automatic discovery. The process that HP Systems Insight Manager uses to find andidentify the systems on your network to populate the database with that information. A systemmust first be discovered to collect data and track system status.

● Manual discovery. The process that enables you to bypass a full automatic discoveryand add single and multiple systems to the database, create or import the HP Systems InsightManager database Hosts file, and create or import a generic Hosts file.

Configuring and Executing Automatic Discovery1. Select Options->Discovery->Automatic Discovery. The Automatic Discovery - General

Settings page is displayed.

102

Initial Setup

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

3. Select any of the five options available in the Discovery configuration section:

● Use discovery filters. This option enables 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 at the bottom of the page.

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

● Automatically discover a server blade when its Integrated Lights Out managementprocessor is identified. This option adds servers that were indirectly discovered throughits managmeent processor. When these servers are discovered, they are listed with aDisabled state on the system list page and the only information displayed is the systemserial number and the association to the iLO and the enclosure.

● Configure global protocol settings

a. If you click Configure global protocol settings, the Global Protocol Settingspage is displayed. Set the Default ping settings, and verify your settings to EnableWBEM, Enable HTTP and HTTPS, Enable SNMP, and Enable DMI.

Note: You need Simple Network Management Protocol (SNMP) enabled with correctsecurity settings on HP Systems Insight Manager and running on the target systems todiscover clusters correctly.

Note: Desktop Management Interface (DMI) is not available on Linux systems.

b. Click OK to save changes, and then click the Automatic Discovery link at the topof the page to return to the Automatic 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, which applies to both range 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 in thePing inclusion ranges or Exclusion ranges fields.

103

Initial Setup

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 through the@template_name reference.

5. Click Save to save the current configuration, or click Save and Run to save the currentconfiguration and run discovery immediately.

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.

Configuring and Executing Manual Discovery1. Select Options->Discovery->Manual Discovery.

2. On the Manual Discovery - Add System page, in the System Information section, selectthe System 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

❍ Product model

● WBEM Settings. Includes:

❍ User name

❍ Password

● SNMP Settings. Includes:

104

Initial Setup

Timeout (in seconds)❍

❍ Retries

❍ Read-only community string

❍ Write community string

4. If you clicked More Settings, click Add System to add the system immediately or click FewerSettings to return to the previous brief display. If you clicked Fewer Settings, click AddSystem to add the system to the database.

Adding UsersCreate a new user account to provide an existing valid login on the central management server(CMS) to log into HP Systems Insight Manager. The login must be authenticated by the CMS. Youmust know the CMS user account name of the user you are adding, but you do not need to knowthe password.

To create a new user:

1. Select Options->Security->Users and Authorizations->Users, and click New. The NewUser section is displayed.

2. In the Login name (on central management server) field, enter the operating system loginaccount name to be used to log into HP Systems Insight Manager. This field is required.

Note: The user cannot log into HP Systems Insight Manager if the account is not a valid login,and the account is not validated until the user tries to log into HP Systems Insight Manager thefirst time.

3. In the Domain (Windows domain for login name) field, enter the Windows domain namefor the login name if running a Windows operating system.

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

5. In the Phone number 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 loginthat already has the predefined authorizations that you want to assign to the login accountyou are 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, allowed to modify all central management server settings. Allows theuser total control of the database. Users can run discovery of systems and data collectiondefine users and authorizations; set Cluster Monitor configuration; configure licensing andprotocol settings; and create, modify, delete, and run reports, snapshot comparisons, tools,custom commands, events, automation tasks, and so on.

105

Initial Setup

● limited, allowed to create/modify/delete all reports and their own tools.Allows the user to create new reports, edit any reports, and delete any reports (includingthe predefined reports).

● none, no configuration of central management server allowed. Allows theuser to view and run predefined reports on the CMS and all managed systems. However,the user has no configuration rights on the CMS or on the managed systems.

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 semicolon (;). 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 thesemicolons 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 excludedfrom this user as clients browsing into this CMS. Use the same format in the previous step forInclusion ranges.

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

11. Note: Steps 11 though 15 are for Windows systems only.

Under the Pager Information section, in the Phone number field, enter the pager phonenumber of the user associated with this user account if you are using a Windows operatingsystem. If the Phone 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.

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

14. In the Baud rate field, select the appropriate baud rate for the pager from the dropdown list.

15. In the Data format field, select the appropriate data format for the pager from the dropdownlist.

16. Click OK to save and close the New User section. You can click Apply to save and keep theNew User section open, or click Cancel to cancel the creation of this user.

The new user account is created.

Configuring Email SettingsConfiguring e-mail settings enables users to receive e-mail notification of certain events.

To configure e-mail settings:

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

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

106

Initial Setup

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.

Configuring Paging SettingsConfiguring paging settings enables users to receive pages to notify them of certain events.

To configure paging settings:

1. Select Options->Events->Automatic Event Handling->Modem Settings. The ModemSettings page is displayed.

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

3. Click OK to save the setting.

Setting Up Automatic Event HandlingAutomatic event handling enables you to define an action that HP Systems Insight Manager performswhen an event is received. Automatic event handling can be set up to use the e-mail and pagingsettings that you specified in the previous sections.

To set up automatic event handling:

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

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. The Select events window is displayed.

4. Select the event search criteria for defining the task:

● List criteria

● Comparison option

● Value for the criteria or comparison options selected

To add additional search criteria, click Add.

5. When 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 dropdown menus:

● List criteria

● Comparison option

● Value for the criteria or comparison options selected

107

Initial Setup

7. To add additional criteria, click Add.

8. When 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 dropdown 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 Userslist is inactive, the pager information for the user has not been configured. You can addthe user to the list of users to be paged, but pager messages are not 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 from the following formats based on the encodingpreference of the recipient:

❍ Standard. A default message format that sends a text e-mail message to the recipients

❍ 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 is sent to therecipients

In the Encoding field, select from the following formats:

❍ Western European (ISO-8859-1)

❍ Unicode (UTF-8)

❍ Japanese (ISO-2022-JP)

❍ Japanese (Shift_JIS)

❍ Japanese (EUC-JP)

● Run custom command

Select a custom command from the Name dropdown list. Custom Command tools arecreated under the Tools->Custom Commands option.

● Assign

108

Initial Setup

Enter the name of the person to whom to assign the task. 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 Traprecipients box. Use the up and down arrows to scroll to the recipient to delete.

● Write to system log

On Windows NT and Windows XP systems, the event details are written to the ApplicationLog, and the Source column of the Event Log is listed as HP Systems Insight Managerfor the logged event. On Linux and HP-UX systems, the event details are logged to thesystem log, which is usually located in the file /var/log/messages on Linux and in/var/adm/sysLog/syslog.log on HP-UX.

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

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

Click View Filter. The Time Filter popup window is displayed, showing the times selected.

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

Adding ToolboxesCreate a toolbox to configure a group of tools to which a user has access.

To add a toolbox:

1. Select Options->Security->Users and Authorizations->Toolboxes, and then click New.The New Toolbox section is displayed.

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

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

109

Initial Setup

4. Select Toolbox is enabled to enable the toolbox and all authorizations created with thistoolbox.

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 New Toolbox section. Click Apply to savethe settings without closing the New Toolbox section, or click Cancel to cancel the newtoolbox creation and return to the Toolboxes section.

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

To add authorizations:

1. Select Options->Security->Users and Authorizations->Authorizations, and then clickNew. The New Authorizations section is displayed.

2. In the Select User(s) dropdown 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. Thisfield is a required.

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

● Copy all authorizations of this user or [template]:

Select a user or template from the dropdown list.

● Manually assign toolbox and system/system group authorizations

a. In the Select Toolbox(es) section, select the toolboxes in which to include the users.

b. From the Select dropdown box, select whether you want to enable the SystemGroup(s) or System(s), and then select the group or individual system from theselection section.

4. Click OK to save the new authorization and close the New Authorizations section. ClickApply to save the new authorization without closing the New Authorizations section, or clickCancel to cancel the creation process.

110

Initial Setup

Chapter 13. Migrating VersionControl to the System ManagementHomepage

This chapter provides information regarding migrating version control to the System ManagementHomepage.

System Management Homepage MigrationOverview

The HP Version Control Agent and HP Version Control Repository Manager login to the managementweb server by way of the System Management Homepage. The System Management Homepageis security software that must be configured in order to allow the Version Control Agent to connectto the Version Control Repository Manager using operating system authentication.

Previous versions of the System Management Homepage, known as Management HTTP Server,provided three levels of account access, including administrator, operator and user. Theseaccounts had passwords that were defined locally at the System Management Homepage andwere assigned a privilege level that corresponded to the account name. When the SystemManagement Homepage is installed, the Management HTTP Server credentials are used if anyWeb Agents are installed on a system. The concept of an administrator or operator level still existsand is accomplished by associating an operating system user group with that privilege level in theSystem Management Homepage security settings, and finally by adding the user accounts to thegroups that provide the level or privilege desired.

The Version Control Agent communicates with a Version Control Repository Manager acting asan HTTP client, just as an interactive user communicates. Therefore, Version Control Agent settingsrequire the name of a system where the Version Control Repository Manager is installed, and thelogin account and password required to access the System Management Homepage on that system.The security changes that resulted from the upgrade of the Management HTTP Server to the SystemManagement Homepage, cause the account and password that are configured at the VersionControl Agent to be migrated to System Management Homepage. Migrating the ManagementHTTP Server credentials allows the Version Control Agent to communicate with the Version ControlRepository Manager to calculate software status and allow software downloads.

Note: If you are using HP Systems Insight Manager or Insight Manager 7, the Software Statuscolumn on the Home page displays Unknown for any Version Control Agent that cannot connect.

Operating system accounts that are in user groups that have been assigned the System ManagementHomepage administrator or operator level privileges, have full access to all Version Control Agentor Version Control Repository Manager features. Operating system accounts that are in user groupsthat have been assigned anonymous or user access have read-only access to page data.

111

Migrating the Version Control Agent and the VersionControl Repository Manager from Management HTTPServer to System Management Homepage to useOperating System Authentication

Although Version Control will continue to report accurately after upgrading Management HTTPServer to System Management Homepage, HP recommends that you configure System ManagementHomepage to use operating system authentication for Version Control Agent access, and re-configurethe systems running Version Control Agent to point to the new account for added security.

Use the following steps as a guideline to reconfigure version control to use operating systemauthentication:

1. Identify the versions of the Version Control Agents that are installed that are being reconfiguredto use operating system authentication.

2. Determine whether you intend to update all of the systems with Version Control Agents installedwith ProLiant Support Pack 7.20 or Integrity Support Pack 3.20.

3. From the system where the Version Control Repository Manager is installed, create a localuser account and user group specifically for version control use. If the installed Version ControlAgents are 2.0.7.10 or later, any account name can be used, for example, vcadmin. If earlierversions of the Version Control Agent are installed and you are not planning to upgrade theVersion Control Agent, you must use an account name that matches one of the non-administratoraccounts the earlier versions of the System Management Homepage defined, for example,operator or user.

By default, the Version Control Agent is unable to login with an account named administratorusing operating system authentication, to prevent an accidental lockout of the local administratoraccount.

To add operating system accounts:

1. Select Start->Settings->Control Panel.

2. Double-click Users and Passwords. The Users and Passwords dialog box is displayed.

3. From the Users tab, click Add. The Add New User dialog box is displayed.

4. In the User name field, enter a user name for this account.

5. In the Full name field, enter a full name for this account.

6. In the Description field, enter a brief description of this account.

7. Click Next. The Add New User dialog box is displayed.

8. In the Password field, enter a password for this account.

9. In the Confirm Password field, re-enter the password exactly as you entered it in thePassword field.

112

Migrating Version Control to the System Management Homepage

10. Click Next. The Add New User dialog box is displayed asking you to indicate what levelof access you want to grant this user.

11. Select the appropriate access level for this user:

● Standard User. Users can modify the computer and install programs, but cannotread files that belong to other users.

● Restricted User. Users can operate the computer and save documents, but cannotinstall programs or make potentially damaging changes to the system files and settings.

● Other. This option enables you to specify a custom level.

❍ Administrators. Administrators have complete and unrestricted access to thecomputer/domain. This level is required to connect from the Version Control Agentto the Version Control Repository Manager.

❍ Backup Operators. Backup Operators can override security restrictions forthe sole purpose of backing up or restoring files.

❍ Guests. Guests have the same access as members of the Users group bydefault, except for the Guest account which is further restricted.

❍ Power Users. Power Users possess most administrative powers with somerestrictions.

❍ Users. Users are prevented from making accidental or intentional system-widechanges.

12. Click Finish. The account is created and appears in the Users for this computer list.

13. Click OK to close the Users and Passwords dialog box.

4. Create a user group that includes the System Management Homepage's Administrator orOperator list, for example, VCOperators. Add the account that you created to that group.

5. If you used one of the legacy account names, and you have not upgraded to SystemManagement Homepage yet, change the existing operator or user account's password tomatch the identically named operating system account.

6. If you intend to upgrade, add the created user group to the Administrator or Operator grouplist in the System Management Homepage-Operating System Groups page during installation.If you have already upgraded to System Management Homepage, add the the created usergroup to System Management Homepage through the System Management HomepageSettings page. For more information regarding assigning accounts in System ManagementHomepage, refer to the System Management Homepage online help.

The user group must be added to the Administrator or Operator lists in the SystemManagement Homepage for the Version Control Agent to have the ability to download andinstall software using the Version Control Repository Manager on this system.

Login to the System Management Homepage using the newly created account and passwordto verify that it logs in successfully.

113


7. Change the configuration of the Version Control Agents that are already installed. There areseveral ways to change the configuration, including:

a. HP Systems Insight Manager users should use Replicate Agent Settings to configureone Version Control Agent to the account and password previously created in step 3,and then deploy that configuration to all installed Version Control Agents.

Note: This is the lowest impact solution, and it does not cause a reboot or restart of theaffected systems.

b. Pre-configure a Version Control Agent component using the Version Control RepositoryManager, and use HP Systems Insight Manager or Insight Manager 7 to create a softwaredeployment task to deploy this component.

If you choose to deploy the Version Control Agent from the 7.20 ProLiant Support Pack,you must deploy the System Management Homepage component first before the VersionControl Agent can install.

Note: This method causes a reboot of the systems where the Version Control Agent isupgraded, since it is being used to upgrade itself.

c. Use the ProLiant Remote Deployment Utility to pre-configure a Version Control Agentfor Windows component. If you choose the Version Control Agent from the 7.20 ProLiantSupport Pack, you must deploy the System Management Homepage component firstbefore the Version Control Agent can install.

8. Verify that the settings are correct and functioning by browsing to one of the systems wherean updated Version Control Agent is installed, and confirming the software status is accurate.If you are an HP Systems Insight Manager or Insight Manager 7 user, run the Software StatusPolling task to display updated status.

114


Chapter 14. ConfigurationOptions

There 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 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, refer to http://java.sun.com/.

This chapter provides information on the following configuration options:

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

CPU Utilization During Data CollectionOverview

The data collection task runs many threads in parallel to overlap computing and database operationswith the wait for managed nodes to respond. On slower systems, this could potentially saturatethe CPU for some time, depending on the processor speed of the CMS system and the number ofsystems being collected. Therefore, HP Systems Insight Manager provides some strategies to lessenthe CPU usage.

115

http://java.sun.com/

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

● Limit the number of systems that 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 reduces the CPU demand of data collectiontasks, but it increases 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 in which HP Systems Insight Manager is used to monitor system status, which iscalled the monitor time-out policy, and it is similar to the policy used by Insight Manager 7. Thesecond time-out policy is more strict and will time-out inactive users. This is called the active time-outpolicy and 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 starts 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 only keeps sessions alive if the user isactively using the GUI, such as clicking on links and buttons. Display and refresh of the banner isnot sufficient to keep the session alive. The user is timed-out either by inactivity, closing the browser,or 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 monitor policy.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:

116

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 are 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:

● File name● File extension● Maximum file size in megabytes● File extension of the roll-over name● 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.

ImplementationChanges made to the log.properties file do not take effect until the log manager daemon orservice is restarted. For Linux and HP-UX, restart the HP Systems Insight Manager daemons usingmxstop 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 consumes too much system memory.

117


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. For Windows, create a file named path.properties under C:\ProgramFiles\HP\Systems Insight Manager\config.

For Linux and HP-UX, create a file named path.properties under /etc/opt/mx/config.

2. Add the following entry in the path.properties file: LOG=C:\\Auditlog\\Logs orLOG=C:/Auditlog/Logs .

Note: C:\\Auditlog\\Log is listed here as an example. This path is user-specific, andcould vary based on your requirements.

3. For Linux and HP-UX, restart the HP Systems Insight Manager daemons (mxstop and mxstart).For Windows, restart the HP Systems Insight Manager service. After restarting the service, anew log file named mx.log resides in the directory specified in path.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 time, while other taskresults are kept for a longer time. Tasks fall into one or the other category based on the type oftool 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

118


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. A task result is kept indefinitely if it is the last result for a scheduled task.For example, if a scheduled task is disabled, its final task result is kept indefinitely, or until the taskis enabled and more task results accumulate.

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 is kept indefinitely. If you want to keep morethan 1 job, edit:

MX_JOB_MIN_COMPLETED_JOBS_PER_TASK=1

Note:

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

119


Chapter 15. Reference Open Source Components Used in HPSystems Insight Manager

There are several open source components used in HP Systems Insight Manager that might affectother applications. They are:

● JavaOOB. The Java Out of Box optimizes the operating system to run Java but should haveno adverse affect on the rest of the system.

● JRE. The JRE is used for browser installs. The provided JRE can be used if needed. However,you can acquire the JRE you explicitly want to use.

● Xerces XML parser. The parser used with HP Systems Insight Manager can be used forother applications. However, HP recommends you install your own separate copy in a differentdirectory structure so that HP Systems Insight Manager is not affected. HP is unaware of anyinteraction with other applications.

● Tomcat. HP Systems Insight Manager uses an embedded version of Tomcat. You can useanother installation of Tomcat with no worry of collision as long as it is not in the HP SystemsInsight Manager directory structure.

● Java. The Java SDK is embedded in HP Systems Insight Manager. There should be nocollision with another standard installation. This installation can be utilized for other purposes.If you choose to apply a patch that is not recommended by HP and have problems, this willnot be supported.

● OpenSSH. Using the OpenSSH provided with HP Systems Insight Manager for use outsideof HP Systems Insight Manager is permitted. However, installing Cygwin is not supported.

● ixPostgresql. This causes problems with HP Systems Insight Manager if used by otherapplications. HP Systems Insight Manager uses a standard installation of PostgreSQL, and youmight be able to use the database for other uses, but HP does not recommend this. If there areproblems with using the database for other purposes, it will not be supported by HP.

● namazu. Afull-text search system intended for easy use.

HP is unaware of any interaction with other applications for the following open source componentsused by HP Systems Insight Manager:

● Inno Setup

● Apache software components

● OpenSSL

● SSLeay

● JuggleMaster 1.60

● JuggleMaster X 0.42

120

● JuggleMaster Java 1.03

● JDOM

121

Reference

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 An aggregate data display that shows utilization data for allCPUs in a cluster. The display aggregates data for all nodes ofthe cluster onto one page, enabling you to see a cluster-levelsummary of data even though CPUs are monitored by a node-levelCluster Monitor 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 An aggregate data display that shows utilization data for all disksin a cluster. The display aggregates data for all nodes of thecluster onto one page, enabling you to see a cluster-level summaryof data even though disks are monitored by a node-level ClusterMonitor Resource.

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

authentication The process of identifying an individual, based on a usernameand password. Authentication is distinct from authorizations, andmerely ensures that the individual is who they claim to be.

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 to collectdata and track system status.

122

available software A listing of the software components available in the repositorythat the Version Control Agent has been configured to point to.When browsing directly into a Version Control Agent, theseadditional components can be selected for installation.

banner The section of the graphical user interface (GUI) at the top of thescreen that shows status information and provides access to HPSystems Insight Manager Home page and logout functions.

blade server A server that is located in a rack or enclosure.See Also enclosure, racks.

blade server visual locator A feature designed to provide visual representation of ProLiantBL e-Class and p-Class servers within their respective enclosuresand racks.See Also enclosure, 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 () 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 Management Agent 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.See Also certificate authority.

certificate authority () 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 A status condition that indicates a system is cleared.

clearing events Changing the event status from uncleared to cleared.

clients HP desktop, portable, and workstation systems.

cluster A parallel or distributed computing system made up of manydiscrete systems that form a single, unified computing resource.Clusters vary in their features, complexity, and the purposes forwhich they are best suited.

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

123

Glossary

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. Cluster Monitoradds the ability to monitor and manage multi-node clusters. ClusterMonitor also manages multiple cluster platforms in aheterogeneous 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

● Notices generated about the cluster

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

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 for which the administratoris responsible. Each tree item is color coded to reflect status.

command line interface () The command line is where commands can be executed directlyfrom the command shell of the operating system command shell.

common information model () 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.

component A component is a single, self-describing, installable (interactiveor silent) binary file containing a single piece of software, suchas firmware image, driver, agent, or utility, that is supported bythe management and update tools.

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, event,or both, 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.

124

Glossary

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

data collection reports Data collection reports include information about discoveredsystems in a single instance or a historical trend analysis report.HP Systems Insight Manager supports Overwrite existing dataset (for detailed analysis) formerly known as Single InstanceData Collection task in Insight Manager 7 and Append newdata set (for historical trend analysis) formerly known asHistorical Data Collection task Insight Manager 7. WithOverwrite existing data set (for detailed analysis), data iscollected from a system at a single instance. With Append newdata set (for historical trend analysis), data detailing thesystem history is collected.

data collection tasks Procedure that involves gathering information from a group ofmanaged systems and storing that information in the database.HP Systems Insight Manager uses Hardware Status Polling andData Collection Tasks to implement collection.

Desktop ManagementInterface ()

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 ()

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 the sender of a transaction. Thistechnology uses private keys to digitally sign the data and publickeys to verify the sender.

discovery A feature within a management application that finds andidentifies network objects. In HP management applications,discovery finds and identifies all the HP systems within a specifiednetwork range.

discovery filters Enables users with full configuration rights to prevent or allowcertain system types from ever being added to the database.

discovery template Files that can be used by automatic discovery in lieu of typingthe addresses directly in to the Ping inclusion ranges orExclusion ranges fields on the Automatic Discovery - GeneralSettings page, and are designed to be used as a quick way tochange the scope of automatic discovery.

Distributed Component ObjectModel ()

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

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

125

Glossary

DMI See Desktop Management Interface.

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

e-mail notification One of the notification tasks in HP Systems Insight Manager thatsends notifications through e-mail. If two users are adding, editing,or deleting a task simultaneously, the task reflects the changesfrom the last user who saves the task.

edit list To modify existing lists to add or remove search criteria.

enclosure A physical container for a set of blades servers. It consists of abackplane that routes power and communication signals andadditional hardware for cabling and thermal issues. It also hoststhe CPU or server power supplies.

event Information sent to certain users that something in the managedenvironment has changed. Events are generated from SNMP trapsand are preconfigured in this release. HP Systems Insight Managerreceives a trap when an important event occurs. Events aredefined as:

● Informational. Events of this type require no attentionand are provided as useful information.

● Normal. Events of this type indicate that this event is nota problem.

● Minor. Events of this type indicate a warning conditionthat can 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.

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 () A program interface that takes advantage of the graphicscapabilities of the computer to make the program easier to use.The HP Systems Insight Manager GUI is Web-enabled anddisplays in a Web browser.

group See node group.

hosts files A file that includes all critical system information from the HPSystems Insight Manager database, such as IP addresses.

HP Insight Management Agent A program that regularly gathers information or performs someother service without the user's immediate presence.

126

Glossary

HP ProLiant Essentials VirtualMachine Management Pack()

Provides central management and control of Virtual Machines onMicrosoft Virtual server, Vmware’s GSX and ESX. Integrated withHP Systems Insight Manager, VMM provides unified managementof HP ProLiant host servers and Virtual Machines.

HP Systems Insight Managerdatabase ()

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

HyperText Transfer Protocol () The underlying protocol used by the World Wide Web.

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

installed version A particular HP software component that is installed on the serverthe Version Control Agent is installed on.

Internet Protocol () Specifies the format of datagrams (packets) and the addressingscheme on a network. Most networks combine IP with TransmissionControl Protocol (TCP), which establishes a virtual connectionbetween a destination and a source.

Internetwork Packet Exchange()

A networking protocol used by the Novell NetWare operatingsystems, and is a datagram (packet) protocol used forconnectionless communications.

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

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

Java Remote MethodInvocation ()

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 share akey or cipher so that each can encrypt and decrypt messages.The risk in this system is that if any party loses the key, the systemis broken. In public key cryptography, the private key isassociated with a public key, so each person in the system hasa 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 thatindicates one or more of the monitored subsystems are notoperating properly which is impacting the system. Action shouldbe taken immediately.

127

Glossary

managed node Also known as a cluster node. A configured cluster system forwhich the HP Systems Insight Manager Cluster Monitor ismonitoring activities.

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

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 InformationBase ()

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

Management InformationFormat ()

An ASCII text file in the DMI architecture that describes themanageable features and attributes of a product. The DMImaintains this information in a MIF database and makes itavailable to operating systems and management applications.The DMTF has specified MIF formats for a variety of system typesand peripheral systems.

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

management services The provider of a core set of capabilities such as auto-discovery,data collection, a central repository for system and eventinformation, event management, basic notification, and secureaccess. These functions are used by add-ins from HP, aManagement Solutions Partner, and/or HP Systems InsightManager end users.

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

manual discovery techniques Processes that enable you to bypass a full discovery for thefollowing tasks:

● Adding a single system● Editing the system● Creating or importing an HP Systems Insight Manager

database hosts file

128

Glossary

● Creating or importing generic hosts files

Microsoft Clustering Servicestatus page

A page that summarizes cluster status as defined by MicrosoftCluster Server and lists the status and values of MSCS-definedcluster attributes. The Cluster Monitor uses color to display statusbased on MSCS condition values (Normal, Degraded, Failed,and Other).

Minor status Aggregate status information collected from the system thatindicates one or more of the monitored subsystems are notoperating properly which is impacting the system. Action shouldbe taken as soon as possible to prevent further failure.

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

multiple-system aware () 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 before the tool interacting with the other managednodes.

no configuration rights user A user who cannot configure the CMS. However, the user canview and run predefined reports on the CMS and all managedsystems.

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 operating system type, backupschedule, application type, or hardware type.

overall software status This section indicates whether the software on the server that theVersion Control Agent is installed on has any updates availablewithin the repository in which it has been configured to monitor.

Performance ManagementPack ()

A software solution that detects, analyzes, and explains hardwarebottlenecks on HP ProLiant servers. PMP tools consist of OnlineAnalysis, Offline Analysis, CSV File Generator Report, SystemSummary Report, Status Analysis Report, Configuration, Licensing,and Manual Log Purge.

ProLiant Essentials license key The contractual permissions granted by HP to the customer in theform of a coded embodiment of a license that represents a specificinstance of a license. A single license may be represented by asingle key or by a collection of keys.

129

Glossary

ProLiant Support Pack A set of HP software components that have been bundled togetherby HP, and verified to work with a particular operating system.A ProLiant Support Pack contains driver components, agentcomponents, and application and utility components. All of theseare verified to install together.

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

Red Hat Package Manager () The Red Hat Package Manager is a powerful package managerthat can be used to build, install, query, verify, update, anduninstall individual software packages. A package consists of anarchive of files and package information, including name, version,and description.

Reference Support Pack A baseline bundle of HP software components that the VersionControl Agent can be configured to point to in the repository.This setting enables users to indicate that they want to keep allof their software up to a certain Support Pack level.

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

This is a capability on which HP Systems Insight Manager reliesto turn on the systems for scheduled Software Updates or ReplicateAgent Settings.

remove all disk thresholds A task provided by HP Systems Insight Manager to remove diskthresholds for systems in an associated list. This task only removesdisk thresholds that were set by HP Systems Insight Manager orby browsing directly to the Web agent. Any thresholds set by HPSystems Insight Manager for Windows 32, including diskthresholds, 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.

repository A directory containing ProLiant Support Pack or Integrity SupportPacks and Smart Components.

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

rule set Conditions, policies, or criteria applied to system information todetermine 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 the systeminformation, and so on. A filter is composed of an inclusion filterfollowed by an exclusion filter. The result of these two filteringoperations is called a group. An example of a filter is an SQL

130

Glossary

statement that creates viewable information or causesmanagement operations to be performed.

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

Secure Shell () 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 () 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 clients can be assured they are communicating withthe server it claims to be. It is application protocol independent.

Secure Task Execution () A feature of HP Systems Insight Manager that securely executesa task from a managed system. STE ensures that the userrequesting the task has the appropriate rights to perform the task,and encrypts 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 capabilityenables systems administrators to delegate tasks to junior staffwithout providing access to advanced or dangerous features. Italso enables 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 thatthe subject and the CA are the same.See Also certificate, certificate authority.

Service Advertising Protocol()

A NetWare protocol used to identify the services and addressesof servers attached to the network.

set disk thresholds A task provided by HP Systems Insight Manager to set a diskthreshold for systems in an associated list. This threshold is set onall disk volumes on the target system.

Short Message Service () A convenient way to send brief text messages directly to a wirelessphone. There is a maximum message length of 140 characters.

Simple Network ManagementProtocol ()

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 to

131

Glossary

another managed system must be from within HP Systems InsightManager.

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

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

SNMP trap Asynchronous event generated by an SNMP agent that the systemuses to communicate a fault.

software inventory A listing of the HP software installed on the system where theVersion Control Agent is installed.

software update A task to remotely update software and firmware.

spoofing The act of a website posing as another site to gather confidentialor sensitive information, alter data transactions, or present falseor misleading data.

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

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

status message list A list created by Cluster Management Resources to collect entriesfound in the bottom left area of the Cluster Monitor page tobring your attention to cluster attributes that are in an abnormalstate.

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 messages Messages about system status, listed in order of descendingpriority (Critical, Major, Minor, Normal, and Unknown) anddecreasing age (oldest, longest outstanding status messages first;most recent status messages last). So, the oldest critical messageappears first followed by most recent critical messages, then theoldest warning message followed by more recent warnings, thenthe oldest unknown status message followed by most recentunknown status messages.

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

status type The classification of status messages (Critical, Major, Minor,Normal, and Unknown).

subnet On TCP/IP networks, subnets are all systems whose IP addresseshave the same prefix. For example, all systems with IP addressesthat start with 10.10.10. would be part of the same subnet.

132

Glossary

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 A common key that both the server and receiver of a messageshare and use to encrypt and decrypt a message.

system Nodes on the network that communicate through TCP/IP or IPX.To manage a system, some type of management protocol (forexample, SNMP, DMI, or WBEM) must be present on the system.Examples of systems include 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 (SNMP, DMI,WBEM, HTTP, and SSH)

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

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

System ManagementHomepage

An integrated piece of software used by the HP suite of HPWeb-enabled System Management Software to communicateover HTTP and HTTPS. It provides a uniform set of functionalityand security to HP Web-enabled System Management Software.

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 registered

133

Glossary

http://www.dmtf.org

with the HP Systems Insight Manager databases. Systems aregrouped by their status conditions. 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 system search.

system status The operating state of SNMP-based systems. A system 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 might be down,powered off, or no longer accessible on the network becauseof network problems.

● Major. A problem exists.● Minor. The system is functioning but with errors.● Normal. The system is functioning correctly.● Unknown. HP Systems Insight Manager is not able to

obtain management information about the system.

● Disabled. The system is disabled from monitoring, butnot necessarily turned off.

system type One of 12 supplied types. You can add your own based on oneof these types, for example, use Server type to create MyServertype. It is still a server and is reported on in the same way, but ithas your designation.

System Type Manager () A utility that enables you to modify the default behavior ofdiscovery and identification of 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 informationreturned from the system agent or from the communicationprotocol of SNMP or DMI.

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

task scheduling A master scheduling tool for the scheduling of polling, control,and notification tasks.

134

Glossary

threshold A preset 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 functions.

trap forwarding address The IP address of a system that has been specified to receive trapnotifications forwarded by the HP Systems Insight Managersystems.

type The classification of a system, which identifies it as a standardsystem type. The system types are client, cluster, portable, printer,remote access device, repeater, router, server, switch, unknown,workstation, and other.

uncleared event status Events that have a Critical, Major, Minor, Normal, orInformational severity.

● Critical. A failure has occurred, and immediate attentionis required.

● Major. A failure is impending.● Minor. A warning condition exists that can escalate into

a more serious problem.● Normal. These events are not a problem.● Informational. No attention require. This status is

provided as useful information

unknown status HP Systems Insight Manager is not able to obtain managementinformation about the system using SNMP or DMI. Although no

135

Glossary

management instrumentation information is available, the systemcan be pinged. It might have an invalid community string orsecurity setting.

user A network user with a valid login on the CMS that has beenadded to HP Systems Insight Manager.

user accounts Accounts used to log into 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 associated rights.

version control A feature that verifies 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 current or thatan upgrade is available and provides reasons for upgrading.

Version information appears as a system link for a system.

Version Control Agent () An agent that is installed on a server to enable you to see the HPsoftware installed on that server. The Version Control Agent canbe configured to point to a Version Control Repository Manageragent, enabling easy version comparison and software updatefrom the repository.

Version Control Agent log A listing of all the software maintenance tasks completed by theVersion Control Agent and reports resulting from those tasks.

Version Control RepositoryManager ()

An HP agent that enables a customer to manage HP providedsoftware stored in a user-defined repository.

WBEM Services HP WBEM Services for HP-UX is an HP product that uses WBEMand DMTF standards to manage HP-UX system resources.

Web-Based EnterpriseManagement ()

An initiative based on a set of management and Internet standardtechnologies developed to unify the management of enterprisecomputing environments.

Web-launch aware () 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 ()

An API in the Windows operating system that enables systems ina network, typically enterprise networks, to be managed andcontrolled.

workspace The section of the GUI where tools are displayed.

X client An application or tool that appears on an X server. X clients canalso be called X applications.

136

Glossary

X server A local application that accepts X client requests and acts onthem.

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 document A collection of data represented in XML.

137

Glossary

IndexAaccess the graphical user interface, 83active time-out, 116add authorizations, 110add toolboxes, 109add users, 105All Tools toolbox, 14audit log, 15

configure, 117authorizations, 13

add, 110automatic discovery, 102automatic event handling, 107

Bbanner

customize, 86overview, 84

Ccentral management server

HP-UX kernel tuning, 42HP-UX system preparation, 43install HP Systems Insight Manager on HP-UX, 44install HP Systems Insight Manager on Linux, 50install HP Systems Insight Manager on Windows,31Linux system preparation, 47overview, 7remove HP Systems Insight Manager on HP-UX, 80remove HP Systems Insight Manager on Linux, 82remove HP Systems Insight Manager on Windows,80requirements, 22Windows system preparation, 30

certificate authority, 19CMS (see central management server)command line interface

log in, 88security, 16

commands, 88communication protocols (see management protocols)configuration

add authorizations, 110add toolboxes, 109add users, 105audit log, 117automatic event handling, 107data collection CPU utilization, 115

discovery, 102email settings, 106lifetimes for Task Result entries, 118managed system, 92paging settings, 107protocol settings, 101time-out policy, 116

configuration options, 115configuration rights

full, 14limited, 14no, 14

configure email settings, 106configure paging settings, 107conventions, typographic, 3CPU utilization, 115customization options, 115customize the graphical user interface, 86

Ddata collection

performance, 115database, 15–16

remote for improved performance, 115default time-out period, 116default toolboxes, 14Desktop Management Interface, 18discovery, 102Distributed Task Facility, 18DMI, 17–18DTF, 18

Eemail

configure, 106event handling, 107

Ffeatures, 7firewalls, 19firewalls ports, 19first setup (see initial setup)frequently scheduled task lifetimes, 118full configuration rights user, 14

Ggetting started, 92graphical user interface

customize, 86log in, 83overview, 84security, 17

138

GUI (see graphical user interface)

HHome page

customize, 86overview, 84

HP Systems Insight Managercommands, 88features, 7

HP Systems Insight Manager database, 16HP-UX CMS

installation and configuration, 44kernel tuning, 42remove HP Systems Insight Manager, 80system preparation, 43

HP-UX managed systemsetup, 92

HTTPS, 17–18

Iinitial setup, 92

add authorizations, 110add toolboxes, 109add users, 105automatic discovery, 102automatic event handling, 107configure e-mail settings, 106configure paging settings, 107discovery, 102managed systems, 92manual discovery, 104protocol settings, 101

Insight Manager 7 comparison, 7install

central management server requirements, 22managed system requirements, 25network client requirements, 27process overview, 21

install HP Systems Insight ManagerHP-UX CMS, 44Linux CMS, 50Windows CMS, 31

Llast result task lifetimes, 118lifetimes for Task Result entries, 118limited configuration rights user, 14Linux CMS

installation and configuration, 50remove HP Systems Insight Manager, 82system preparation, 47

Linux managed systemsetup, 94

log incommand line interface, 88graphical user interface, 83

Mmanaged node (see managed system)managed system

discovery of, 102overview, 7protocol settings on the CMS, 101requirements, 25setup, 92

management domainoverview, 7

management protocols, 17DMI, 18HTTPS, 18SNMP, 19SSH, 18WBEM, 18

manpages, 88manual discovery, 104monitor time-out, 116Monitor Tools toolbox, 14

Nnetwork client

overview, 7requirements, 27supported Web browsers, 27

new features, 7no configuration rights user, 14node (see managed system)node group (see system group)

Ooverview

System Management Homepage, 111

Ppaging

configure, 107parameter

DataCollectionThreadCount, 115EnableSessionKeepAlive, 116LOG, 117MX_JOB_CACHE_TIME_COMPLETED_JOBS, 118MX_JOB_MAX_COMPLETED_JOB_AGE, 118MX_JOB_MAX_COMPLETED_JOBS_PER_TASK,118MX_JOB_MIN_COMPLETED_JOBS_PER_TASK, 118MX_LOG_FILEEXT, 117

139

Index

MX_LOG_FILENAME, 117MX_LOG_FILESIZE, 117MX_LOG_QUEUESIZE, 117MX_LOG_ROLLFILEEXT, 117session-timeout, 116

ports, 19protocol settings, 101protocols, 17

Rremove HP Systems Insight Manager

HP-UX CMS, 80Linux CMS, 82Windows CMS, 80

repository (see database)requirements

central management server, 22managed system, 25network client, 27

SSecure HTTP, 18Secure Shell , 18security

access, 16certificate authority, 19command line interface, 16firewalls, 19graphical user interface, 17ports, 19self-signed certificates, 19Web server, 19X applications, 19

self-signed certificates, 19Servicecontrol Manager 3.0 comparison, 7setup

add authorizations, 110add toolboxes, 109add users, 105automatic event handling, 107configure email settings, 106configure paging settings, 107discovery, 102HP-UX managed systems, 92initial, 92Linux managed systems, 94managed systems, 92protocol settings, 101Windows managed systems, 96

short and long task lifetimes, 118Simple Network Management Protocol, 19SNMP, 17, 19spoofing, 19

SSH, 17–18system group

overview (see )System Management Homepage

integration, 111migration, 111

TTask Results Page

entry lifetime configuration, 118time-out policy

configuration, 116toolboxes, 13

add, 109tools, 15

command line, 15Web, 15X Window, 15

types of tools, 15typographic conventions, 3

Uusers

add, 105add authorizations, 110

WWBEM, 17–18Web Based Enterprise Management, 18Web browser

requirements, 27Web server security, 19Windows CMS

installation and configuration, 31remove HP Systems Insight Manager, 80system preparation, 30

Windows managed systemsetup, 96

XX application security, 19

140

Index

Documents

HP Systems Insight Manager 4.2 Installation and User Guide€¦ · HP Systems Insight Manager can be extended to provide system management with plug-ins for HP clients, storage, power,