HP Systems Insight Manager Installation and Configuration Guide

7/18/2019 HP Systems Insight Manager Installation and Configuration Guide

http://slidepdf.com/reader/full/hp-systems-insight-manager-installation-and-configuration-guide 1/149

HP Systems Insight Manager 5.1 Installation

and Configuration Guide for Microsoft®

Windows

*418812-002*Printed in the USHP Part Number: 418812-002Published: January 2007Edition: 5.1



© Copyright 2003-2007 Hewlett-Packard Development Company, L.P.

Legal Notices

The 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 implied warranties of merchantability

and fitness for a particular purpose. Hewlett-Packard shall not be held liable for errors contained herein or direct, indirect, special, incidental, or

consequential damages in connection with the furnishing, performance, or use of this material.

Warranty

A copy of the specific warranty terms applicable to your Hewlett-Packard product and replacement parts can be obtained from your local Salesand Service Office.

U.S. Government License

Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial

Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under

vendor's standard commercial license.

Copyright Notices

©Copyright 1983-2007 Hewlett-Packard Development Company, L.P. All rights reserved. Reproduction, adaptation, or translation of this document

without prior written permission is prohibited, except as allowed under copyright laws.

Trademark Notices

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

Java™ is a U.S. trademark of Sun Microsystems, Inc.

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

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

Oracle is a registered U.S. trademark of Oracle Corporation, Redwood City, California.

Publication History

The manual publication date and part number indicate its current edition. The publication date will change when a new edition 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 HP sales representative for

details.

Please direct comments regarding this guide to:Hewlett-Packard Company

HP Systems Insight Manager Learning Products

20555 Tomball Parkway

Houston, Texas 77070

Or, use this web form to send us feedback:

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

Typographic Conventions

We 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 the Instant Information

DVD, it might be a hot link to the manpage itself. From the HP-UX command line, you can 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 might 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 can replace in a command or function or information in a display that represents 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 can be repeated an arbitrary number of times.

| Separates items in a list of choices.



Table of Contents

1 Product overview........................................................................................7Features.................................................................................................................................................7

HP SIM management.........................................................................................................................7Security............................................................................................................................................7Installation........................................................................................................................................8

Discovery..........................................................................................................................................8Custom tools.....................................................................................................................................8Reporting..........................................................................................................................................8Partner applications...........................................................................................................................8

What's new.........................................................................................................................................11Collections......................................................................................................................................11Events............................................................................................................................................11Task Wizard...................................................................................................................................11Directory services.............................................................................................................................11Security..........................................................................................................................................11Command Line Interface...................................................................................................................12Discovery........................................................................................................................................12

Protocols.........................................................................................................................................12Reporting........................................................................................................................................12 Additional new features....................................................................................................................12Partner applications.........................................................................................................................12

Product architecture...............................................................................................................................13Central management server...............................................................................................................13Managed systems............................................................................................................................13 Web-browser clients.........................................................................................................................13

Authorizations......................................................................................................................................13Default toolboxes.............................................................................................................................14User privileges.................................................................................................................................14

Tools...................................................................................................................................................14Information storage...............................................................................................................................15

HP SIM audit log.............................................................................................................................15Database........................................................................................................................................15

Database software......................................................................................................................16Secure access.......................................................................................................................................16

Command line interface...................................................................................................................16Graphical user interface...................................................................................................................16

Secure data transmission........................................................................................................................17Management protocols.....................................................................................................................17 Web server security ........................................................................................................................18Self-signed certificates .....................................................................................................................18X application security.......................................................................................................................19Managing servers behind a firewall ..................................................................................................19

2 Installation overview and requirements........................................................20First time install process overview............................................................................................................20Upgrade overview................................................................................................................................20System requirements..............................................................................................................................20 Windows Central Management Server....................................................................................................20Managed system requirements and recommendations................................................................................21SSH requirements..................................................................................................................................23

3 Installing HP SIM on the Central Management Server (CMS) for the first time...25Preparing the system..............................................................................................................................25Typical install........................................................................................................................................28Custom install.......................................................................................................................................28

Silent install..........................................................................................................................................34

Table of Contents 4



Next steps............................................................................................................................................36

4 Configuring HP SIM using the First Time Wizard...........................................37First Time Wizard..................................................................................................................................37Entering WBEM settings.........................................................................................................................38Entering SNMP settings..........................................................................................................................38Enabling system automatic discovery.......................................................................................................39 Adding users to the Central Management Server.......................................................................................39Configuring e-mail settings.....................................................................................................................40

Configuring automatic event handling......................................................................................................41First Time Wizard summary ...................................................................................................................41

5 Configuring HP SIM using the Options menu................................................42Configuring protocol settings..................................................................................................................42Users and authorizations........................................................................................................................44

Adding users...................................................................................................................................44 Adding user groups....................................................................................................................45

Adding toolboxes............................................................................................................................46 Adding authorizations......................................................................................................................46Configuring email settings.................................................................................................................48Configuring paging settings..............................................................................................................48Setting up automatic event handling...................................................................................................49

Configuring and executing discovery.............................................................................................51Configuring and executing automatic discovery.........................................................................51Configuring and executing manual discovery............................................................................52

6 Setting up managed systems......................................................................56Setting up managed systems from a Windows CMS..................................................................................56

Installing the HP ProLiant Support Pack on Windows systems for the first time...........................................56Configuring the managed system software using the Configure or Repair Agents feature from the CMS.......67

Setting up managed storage systems.......................................................................................................65Installing SMI-S providers..................................................................................................................66 Verifying SSL...................................................................................................................................66Configuring SMI-S providers..............................................................................................................66Configuring HP SIM to discover storage systems...................................................................................66

7 Configuring managed systems...................................................................67Configuring the managed system software using the Configure or Repair Agents feature from the CMS............67

8 Initializing the Remote Support Software Manager on the Central ManagementServer (CMS) .............................................................................................70

Understanding the Remote Support Software Manager..............................................................................70SWM device and access requirements................................................................................................70HP Remote Support Software Manager Configuration Options...............................................................71

Initializing the HP Remote Support Software Manager Software Manager....................................................72 About the Initialization Process..........................................................................................................72Running the Remote Support Software Initialization Process...................................................................72Using the HP Remote Support Software Manager.................................................................................77

Modifying HP Remote Support Software Manager Settings..............................................................77Form or Action Submission Windows.......................................................................................77

Automation Levels and Scheduling in the Software Manager............................................................77Understanding Automation Levels in the Remote Support Software Manager.................................78Modifying Automation Levels in the Software Manager..............................................................80

Understanding and Modifying Scheduling in Software Manager......................................................81Modifying the Global Update Window....................................................................................82Modifying Package Update Scheduling....................................................................................82

Managing Software Downloads and Installations............................................................................83Understanding and Configuring HP Reports ..................................................................................84Understanding and Configuring Customer Notifications and Reports ................................................85Modifying Proxy Settings.............................................................................................................86

Modifying Bandwidth Settings......................................................................................................86

Table of Contents 5



Understanding and Using the Actions Option.................................................................................87Removing or Reinstalling the Remote Support Software Manager...........................................................87

Reinstalling the Remote Support Software Manager.........................................................................88

9 Installing and configuring the Service Essentials Remote Support Pack on HP SIM5.1............................................................................................................89

Prerequisites.........................................................................................................................................89Remote Support Pack setup.....................................................................................................................89

10 Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager4.2..........................................................................................................101Types of migration...............................................................................................................................101Performing an in-place migration...........................................................................................................102Performing a remote migration..............................................................................................................103

11 Upgrading HP Systems Insight Manager from 4.x or later .........................105Upgrading from HP SIM 4.x or later......................................................................................................105Typical upgrade..................................................................................................................................106Custom upgrade.................................................................................................................................107Silent upgrade....................................................................................................................................112Next steps..........................................................................................................................................114

12 Uninstalling HP Systems Insight Manager.................................................115Uninstalling HP Systems Insight Manager from a Windows system.............................................................115

13 Using the graphical user interface..........................................................116 Accessing the GUI..............................................................................................................................116Using Internet Explorer 7......................................................................................................................116Graphical user interface features...........................................................................................................116Customizing the GUI...........................................................................................................................118

Customizing the Home Page............................................................................................................118Customizing the System Status Panel.................................................................................................119

14 Using the command line interface...........................................................120Logging in to the CLI...........................................................................................................................120

Logging in directly on the CMS........................................................................................................120Using an SSH client remotely...........................................................................................................120manpages..........................................................................................................................................120

15 Configuration options...........................................................................121CPU utilization during data collection....................................................................................................121

Overview......................................................................................................................................121Implementation..............................................................................................................................121

GUI time-out policy.............................................................................................................................121Overview......................................................................................................................................121Implementation..............................................................................................................................122

HP SIM audit log configuration.............................................................................................................122Overview......................................................................................................................................122

Implementation..............................................................................................................................123Lifetimes for entries on the Task Results Page...........................................................................................123Overview......................................................................................................................................123Implementation..............................................................................................................................124

16 Troubleshooting....................................................................................125Installation issues................................................................................................................................125

Sign in.........................................................................................................................................125Upgrade issues...................................................................................................................................130Password issues..................................................................................................................................131

glossary...................................................................................................132Index.......................................................................................................146

6 Table of Contents



1 Product overviewHP Systems Insight Manager (HP SIM) is the foundation for HP's unified server-storage management strategy.It is a multiple operating system, hardware level management product that supports HP ProLiant, Integrityand HP 9000 servers, HP StorageWorks MSA, EVA, XP arrays, and third-party arrays. Through a singlemanagement view of Microsoft® Windows®, HP-UX 11iv1, HP-UX 11iv2, HP-UX 11iv3, and Red Hat, SuSELinux, HP SIM provides the basic management features of system discovery and identification, single event

view, inventory data collection, and reporting. The core HP SIM software uses Web Based EnterpriseManagement (WBEM) to deliver the essential capabilities required to manage all HP server platforms.

HP SIM can be extended to provide system management with plug-ins for HP clients, storage, power, andprinter products. Plug-in applications for workload management, capacity management, virtual machinemanagement, and partition management through the HP Integrity Essentials enable you to pick the value-addedsoftware required to deliver complete lifecycle management for your hardware assets.

FeaturesHP SIM provides the following features:

HP SIM management

• Fault management and event handling HP SIM provides proactive notification of actual or impendingcomponent failure alerts. Automatic Event Handling enables you to configure actions to notify appropriateusers of failures through e-mail, pager, or Short Message Service (SMS) gateway and enables automaticexecution of scripts or event forwarding to enterprise platforms, such as HP OpenView Network NodeManager or HP OpenView Operations.

• Consistent multisystem management HP SIM initiates a task on multiple systems or nodes from asingle command on the CMS. This functionality eliminates the need for tedious, one-at-a-time operationson each system.

• Two user interfaces HP SIM provides a web browser GUI and a command line interface (CLI) tomake it easy to incorporate HP SIM into your existing management processes.

• Web Based Enterprise Management (WBEM) indications for HP-UX, Linux, and Storage ManagementInitiative Specification (SMI-S) devices HP SIM enables you to subscribe and unsubscribe to WBEMindications through the GUI. You can also subscribe or unsubscribe to WBEM indications through theCLI.

Security

• Role-based security HP SIM enables effective delegation of management responsibilities by givingsystem administrators granular control over which users can perform which management operationson which systems.

• Manage SSH keys The SSH Keys feature enables you to view and manage the public SSH keys,stored in the known_hosts file, from the CMS. SSH keys enable the CMS and a managed system to

authenticate a secure connection.• Secure remote management HP SIM leverages operating system security for user authentication and

uses Secure Sockets Layer (SSL) and Secure Shell (SSH) to encrypt management communications.

• The Configure or Repair Agents feature enables you to repair credentials for SNMP settings, SystemManagement Homepage, or Management HTTP Server trust relationships on Windows, Linux, andHP-UX systems supported by HP SIM.

Features 7



Installation

• Easy and rapid installation. HP SIM installs on your server platform of choice running HP-UX 11i v1,HP-UX 11i v2 or HP-UX 11i v3 on PA-RISC/Integrity or ProLiant platforms running Windows or Linux.

• First Time Wizard HP SIM provides you with step-by-step, online guidance for performing the initialconfiguration of HP SIM. The wizard helps you configure HP SIM settings on the Central ManagementServer (CMS).

Discovery▲ HP SIM can automatically discover and identify systems attached to the network. Discovery filters enable

you to limit discovery to specific network segments or IP address ranges. Use discovery filters to preventdiscovery of unwanted system types.

Custom tools

▲ HP SIM defines tools using simple XML documents that enable you to integrate off-the-shelf or customtools. These tools can be command line tools, web-based applications, or scripts. Access to theseintegrated tools is governed by role-based security.

Reporting

• Data collection and inventory reports HP SIM performs comprehensive system data collection andenables you to quickly produce detailed inventory reports for managed systems. Reports can be generatedin HTML, XML, or CSV format. Data collection and reporting has been added for Superdome systemsand other cellular complexes. Data that can be collected includes information on enclosures, cabinets,cells, memory, Integrity virtual machines, non-Integrity virtual machines, virtual partitions (vPars), andhard partitions (nPars). The data collected depends on which filters are selected,

• Snapshot comparisons HP SIM enables you to compare configuration snapshots of up to four differentservers or configuration snapshots of a single server over time. This functionality assists IT staff inpinpointing configuration issues that can contribute to system instability. Snapshot comparisons canalso be used to save a picture of a standard configuration for comparisons to other systems.

Partner applications• HP Version Control HP SIM automatically downloads the latest BIOS, driver, and agent updates for

HP ProLiant servers running Windows and Linux, identifies systems running outdated system software,and enables system software updates across groups of servers. For HP-UX systems, Software Distributoris integrated into HP SIM.

• Service Essentials Remote Support Pack HP SIM now includes a new Service Essentials RemoteSupport Pack plug-in. This plug-in leverages elements of HP’s Instant Support Enterprise Edition (ISEE)technology and provides integrated HP SIM and Remote Support Pack capability. This capability isdeployed on your Windows-based Central Management Server (CMS) and includes the following:

• Remote event monitoring to supplement the local monitoring of HP SIM.

• Real-time hardware event monitoring and secure event submission to HP Support to help identifyand prevent potentially critical problems on hardware.

• Faster restoration of your supported systems and devices to operational status.

• Less disruption to your company’s revenue-generating activities and business productivity.

• HP SIM's single view of your data center is enhanced by adding serviceability attributes.

Contract and warranty details for your systems.•

• Service event view, including remote support details such as HP case ID and service casestatus.

• CMS heartbeat polling, monitored by HP, allowing early notification to your IT team that eventsubmission to HP is not working.

8 Product overview



• Web-Based Enterprise Services, and Open Service Event Manager HP Services has deployed leadingedge analysis tools that notify you when a significant system event will occur or has already occurred. Web-Based Enterprise Services (WEBES) System Event Analyzer (SEA) and Open Service Event Manager(OSEM), are used as part of the Remote Support Pack remote service offering and as standalone toolsto HP Services customers. WEBES and OSEM generate service notifications to HP SIM through a specificSNMP trap type if analysis has determined there are serviceable events. If the Remote Support Pack isinstalled, the service notification provided by WEBES and OSEM also provides status about the remotesupport incident.

• System Management Homepage The System Management Homepage is a web-based applicationthat provides a consolidated interface for single system management. By aggregating the data fromHP web-based agents and management utilities, the System Management Homepage provides acommon, easy-to-use interface for displaying hardware fault and status monitoring, performance data,system thresholds, diagnostics, and software version control for an individual server.

• HP ProLiant Essentials Performance Management Pack HP SIM provides a software solution thatdetects, analyzes, and explains hardware bottlenecks on HP ProLiant servers and HP StorageWorksModular Smart Array (MSA) shared storage. HP ProLiant Essentials Performance Management Pack(PMP) tools available in HP SIM consist of Online Analysis, Offline Analysis, CSV File Generator Report,System Summary Report, Static Analysis Report, Configuration, Licensing, and Manual Log Purge. PMPis automatically installed with HP SIM and operates in conjunction with HP SIM. No software installationon the monitored servers is required, other than the Insight Management Agents. PMP 4.3 includes the

following features:• Support for HP SIM 5.x (This version of PMP does not support HP SIM 4.x.)

• Support for Oracle® database (local or remote)

The following hardware is supported:

• ProLiant BL465c G1 servers

• ProLiant BL68c G1 servers

• ProLiant BL25p G2 servers

• ProLiant BL45p G2 VR1 servers

• ProLiant DL320 G5 Servers


• ProLiant DL365 Servers


• ProLiant ML310 G4 Servers

• Integrity rx7620 Servers




• Integrity Superdome Servers

Note: The Integrity Superdome includes support for Montecito, M9M, and MX2 processors.

• Ultra 160 SCSI Adapter

• HP NC370i NIC

• rx8620 Gigabit LoM (5701) NIC

• rx8640 Gigabit LoM (5703) NIC

• LAN/SCSI Combo Card (Castor, AB290A)

The following new operating systems are supported:

• VMware ESX 2.5.2


Features 9




• VMware ESX 3.0

Go to http://h18013.www1.hp.com/products/servers/proliantessentials/valuepack/pmp/index.htmlfor more information.

• HP ProLiant Essentials Vulnerability and Patch Management Pack HP ProLiant Essentials Vulnerabilityand Patch Management Pack identifies and provides advice to resolve security vulnerabilities anddelivers advanced patch management through automated acquisition, optimized deployment, and

continuous enforcement of security patches. The HP ProLiant Essentials Vulnerability and PatchManagement Pack must be manually installed from the Management CD and requires one license foreach target system being managed. Five fully functional non-expiring licenses, for use on servers ordesktops, are provided with the HP ProLiant Essentials Vulnerability and Patch Management Pack forevaluation purposes. For more information about installation and setup, see the HP ProLiant Essentials Vulnerability and Patch Management Pack Quick Setup Poster and the HP ProLiant Essentials Vulnerability and Patch Management Pack User Guide , on the Management CD. For more information on the HPProLiant Essentials Vulnerability and Patch Management Pack, go to HP ProLiant Essentials Vulnerabilityand Patch Management Pack at http://www.hp.com/servers/proliantessentials/vpm.

• HP ProLiant Essentials Virtualization Management Software Virtual machine management capabilitiesintegrated into HP SIM extend its capabilities to deliver unified management of an IT infrastructureconsisting of both physical and virtual server resources and to simplify and consolidate the provisioning,

management, and migration of all server resources from one central interface.The virtual machine management capabilities in HP SIM are provided by integrating the HP ProLiantEssentials Virtual Machine Management Pack and the HP ProLiant Essentials Server Migration Pack.Both these components are installed together as one component, but they are licensed separately.

• HP ProLiant Essentials Virtual Machine Management Pack The Virtual Machine ManagementPack provides central management and control for Microsoft's Virtual Server and VMware's GSXServer or ESX Server virtual machines. Using the Virtual Machine Management Pack, all virtualmachines and virtual machine (VM) hosts can be managed from the HP SIM console. The Virtual

Machine Management Pack displays a tree view of the virtual machine hosts and virtual machineguests in the left pane of the HP SIM console. After selecting a system in the left pane tree,information for the system selected appears in the right pane. You can deploy, register, unregister,and upgrade. The Virtual Machine Management Pack is now integrated into HP SIM. See http://www.hp.com/go/vmmanage for documentation and more information on the Virtual MachineManagement Pack.

• HP ProLiant Essentials Server Migration Pack The Server Migration Pack extends the functionalityof the Virtual Machine Management Pack to provide integrated physical-to-virtual (P2V),virtual-to-virtual (V2V), and virtual-to -physical (V2P) migrations. The Server Migration Pack enablesyou to simplify the server consolidation process, thereby freeing you to focus on other priorities.The Server Migration Pack now offers a new Server Migration Pack license type that allowsunlimited migrations for one year after the first migration is initiated. To purchase additionallicenses, see http://www.hp.com/go/vmmanage.

• HP BladeSystem Integrated Manager in HP Systems Insight Manager HP SIM delivers a bladeenvironment designed to consolidate access to blade deployment, configuration, and monitoring tools.Picture views are available of racks and enclosures. HP BladeSystem Integrated Manager is automaticallyinstalled with HP SIM. No license key is required. To access HP BladeSystem Integrated Manager,select Tools→Integrated Consoles→HP BladeSystem. See http://h18004.www1.hp.com/products/servers/Integrity-bl/p-class/60p/index.html for more information.

• HP ProLiant Essentials Rapid Deployment Pack - Windows Edition The HP ProLiant Essentials RapidDeployment Pack (RDP) is a multiserver deployment tool that enables IT administrators to easily deploylarge volumes of servers in an unattended, automated fashion. The RDP is installed separately from HPSIM and requires a license for each server being managed. You must register your RDP productregistration number to purchase licenses or obtain a 10-node 30-day license prior to installing RDP (a10-node 7-day evaluation license is built into the software). The RDP is installed from its own DVD. Seehttp://www.hp.com/servers/rdp for information about RDP including a link to obtain evaluation licenses

10 Product overview

http://h18013.www1.hp.com/products/servers/proliantessentials/valuepack/pmp/index.html

http://www.hp.com/servers/proliantessentials/vpm

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



http://h18004.www1.hp.com/products/servers/Integrity-bl/p-class/60p/index.html


http://www.hp.com/servers/rdp

http://www.hp.com/servers/rdp






http://www.hp.com/servers/proliantessentials/vpm

http://h18013.www1.hp.com/products/servers/proliantessentials/valuepack/pmp/index.html



or register your product. Refer to the RDP documentation for network environment setup, prerequisitesfor the deployment server, and installation instructions.

• HP Storage Essentials HP is changing the economics of managing the data center. HP StorageEssentials is the first open, standards-based suite of storage products designed to integrate into HP SIM.For more information on HP Storage Essentials, see http://h18006.www1.hp.com/products/storage/software/esuite/index.html.

• HP Insight Power Manager HP Insight Power Manager (IPM) is an integrated power monitoring andmanagement application that provides centralized control of server power consumption and thermaloutput at the datacenter level. It extends the capacity of datacenters by enabling the user to control theamount of power and cooling required for ProLiant servers. Built on ProLiant Power Regulator Technology,it extends new server energy instrumentation levers into HP SIM for greater Unified InfrastructureManagement.

• Support for HP-UX Serviceguard clusters HP SIM recognizes HP-UX Serviceguard clusters and displaysthem in the GUI. HP Serviceguard Manager opens when you click a Serviceguard cluster in a searchlist and provides information on the clusters.

What's new

Collections

▲ You can combine system and event collections for added power and flexibility. You can easily viewevents associated with system collections and vice versa. Improved versatility for moving and copyingcollections.

Events

• Automatic event handling utilizes both event and system collections.

• Event management (clearing, deleting, and so on) is possible for users with limited configuration rightsprivileges. Users do not have to be full configuration rights users.

• Increased control over HP SIM generated e-mail format

• For All HP Services Events, additional case information is now available.

• New event types in the HP Service Events categories provide advance notification when a managedsystem warranty or contract is about to expire.

Task Wizard

• You can configure the task wizard to skip the target verification.

• On the target verification page, you can filter the task by selecting system or event filters.

Directory services

• Added a new tool to read ActiveDirectory group membership for systems and place the membershipin the database. This can be used for searches and authorizations.

• Support for determining membership in Windows domains, Organizational Units (OU), and staticgroups, as defined in Windows Active Directory by using LDAP 3 to communicate with the ActiveDirectory server.

Security

• More refined control over Trusted System Certificates: Always Accept, First Time, and Require.

• New SSL certificate management support makes using the stringent Require trusted certificates optioneasy to set up with an optional automatic import of certificates upon first receipt.

• A separate WBEM certificate for WBEM connections is used as a client credential.

• Authorizations can track your dynamic system environment automatically

What's new 11

http://h18006.www1.hp.com/products/storage/software/esuite/index.html






Command Line Interface

• Tighter integration with HP NonStop Kernel servers.

• The command mxquery can provide output in XML format.

Discovery

• Discovery of HP virtual machine systems is now available.

•

HP SIM discovers external LUs (a feature of External Storage XP) on XP arrays that are managed byCommand View XP Advanced Edition.

Protocols

• When setting protocol settings, the Write community string is only required for firmware updates on aGbE switch.

• WBEM communications now support certificate-based authorization as well as user and password-basedauthentication where support is available. The Configure or Repair Agents have also been extendedto configure WBEM certificates on target systems.

Reporting

• HP SIM can now generate reports containing event information, as well as nPars and tape libraries.• Improvements to inventory reports for non stop systems and power supplies.

• Presentation improvements for snapshot reports.

Additional new features

• New quick search available.

• Easier to use interface for creating custom tools.

• You can enlarge the System Status panel to display a separate, large window that can be resizedand viewed from across a room without sitting at the HP SIM terminal.

• The HP SIM Configure and Repair Agents tool enables you to configure Windows managed systemsfrom a HP-UX or Linux CMS

• An improved license management user interface.

• Error messages have been rewritten to include a root cause and a corrective action.

• New default task to delete events older than 90 days.

• Can manage c-Class blade systems.

• Really Simple Syndication (RSS) feed information displays Critical, Major, and Minor systems and theevents associated with the system, including totals.

• Product registration enables you to receive notification of software updates, support alerts, andnewsletters.

Partner applications• HP SIM includes a new Service Essentials Remote Support Pack plug-in. This plug-in leverages elements

of HP’s Service Essentials Remote Support Pack technology and provides integrated HP SIM and RemoteSupport Pack capability.

• When the Remote Support Pack and HP SIM are installed together on a Windows CMS, you canmonitor and view contract and warranty data in the HP SIM user interface. An HP support contract isnot required for monitoring warranty data.

• HP SIM includes HP Insight Power Manager which provides new insight into ProLiant server energyconsumption to include centralized graphical reporting and analysis of power and cooling costs for

12 Product overview



groups of servers, policy-based power management based on the time of day, and instantaneous andhistorical views of thermal output and power consumed.

• HP SIM supports the launch of HBAnyware from the system page of storage hosts with Emulex HBAs.

Product architectureHP Systems Insight Manager (HP SIM) leverages a distributed architecture that is broken into three types ofsystems: Central Management Server (CMS), managed systems , and web browser clients.

The CMS and the managed systems together are called the HP SIM management domain .

Central management serverEach management domain has a single CMS. The CMS is the system in the management domain thatexecutes the HP SIM software and initiates all central operations within the domain. In addition to the HPSIM software, the CMS maintains a database for storage of persistent objects that can reside locally or ona separate system. Typically, applications for the multiple-system aware (MSA) tools also reside on the CMS.However, these applications are not required to reside on the CMS. They can reside anywhere on thenetwork.

Because the CMS is a system within the management environment, it manages itself as part of the domain.You can add the CMS as a managed system within another management domain if you want to managethe domain using a separate CMS.

Managed systemsSystems that make up a management domain are called managed systems. A system can be any device onthe network that can communicate with HP SIM, including servers, desktops, laptops, printers, workstations,hubs, storage systems , storage area networks (SANs), and routers. In most cases, these devices have an IPaddress associated with them. A managed system can be managed by more than one CMS, if desired.

Systems to be managed must have one or more management agents installed. There is wide variety ofagents, such as the ProLiant management agents based on SNMP , Windows Management Instrumentation (WMI) found on Windows systems, or such as Web-Based Enterprise Management (WBEM) providers, andSystem Fault Management providers for HP-UX. These agents provide management information and alerts(indications) to the CMS. The SSH agent (service) then enables the HP SIM CMS to log in to the managedsystem to execute commands through scripts.

Web-browser clientsHP SIM can be accessed from any browser client. The network client can be part of the management domain.The network clients must be running a compatible browser to access the GUI or an SSH client applicationto securely access the CLI . Access to the web server on the CMS can be restricted to specific IP addressranges for specific users.

Authorizations An HP SIM user must have a valid operating system login on the CMS. After a user is added to HP SIM, heor she can be authorized to use a toolbox on one 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 as databaseadministration or software management. Authorizing a user for a toolbox on a system or system group enables the user to run the associated set of tools on that system or systems that are members of the systemgroup.

IMPORTANT: Authorization for a toolbox can enable users with non-privileged access (for example, non-rootusers or users that are not members of the Windows Administrators group) to run tools as root/administratoror as another specified user. Be careful when granting users permission to run tools as root or administrator.

Product architecture 13



Consider all the capabilities given by a tool, beyond the capabilities it is designed for, before you associateit with a toolbox.

Default toolboxesThe All Tools toolbox is a default toolbox installed with HP SIM. The All Tools toolbox provides completeaccess to all tools for the authorized system or system group. When a tool is added to HP SIM, the tool isautomatically added to this toolbox. Tools cannot be removed from the All Tools toolbox, and the All Tools

toolbox cannot be deleted from HP SIM. If you do not want a user to have access to all available tools for

a specific system or system group, they should not be authorized for the All Tools toolbox on that systemor system group.

CAUTION: Users assigned to the All Tools toolbox on the Central Management Server (cms2;) can executecommands as any user. 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 the state ofmanaged systems but not tools that change the state of managed systems.

HP SIM 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 special privileges to administerthe HP SIM software. Full rights users manage the following components:

• Authorizations

• Systems

• System groups

• Users

• Toolboxes

• Tools

In addition, full rights users maintain and back up the database and monitor the HP SIM audit log.

By default, the administrative account used to install HP SIM on a Windows CMS is assigned the fullconfiguration rights user privilege, but this permission can later be revoked. This user is automaticallyauthorized for the All Tools toolbox on all systems, including the CMS. The full configuration rights user privilege can be given to one or more users, and HP SIM requires that at least one user is a full configurationrights user.

Limited configuration rights user Limited configuration rights user s have limited capability to configurethe CMS. They have permission to create, modify, and delete all reports and their own tools.

No configuration rights user No configuration rights user s cannot configure the CMS. Their ability tomanage systems are based on their authorizations.

ToolsTools are applications, commands, or scripts that are launched from within HP SIM. You can add customtools into HP SIM and execute them across multiple systems simultaneously. Three types of tools are supportedin the HP SIM environment: web tools, X Window tools, and command line tools.

Web tools must reside on a web server. The web server can berunning on the CMS or a managed system. HP SIM launches the

web tools

URL from a CLI or GUI. When a web tool is launched from thecommand line, HP SIM opens a browser to display the tool. Whena web tool is launched from the HP SIM GUI, it opens in theworkspace or in a separate browser window.

X Window tools require that an X server is running. These toolscan reside on the CMS or on a managed system. When accessing

X Window tools

HP SIM from a network client, you must have X server softwarerunning on the network client to execute an X Window tool. From

14 Product overview



the CLI or GUI, HP SIM invokes the X Window application usingthe command line and passes the location of the X server byrequesting the device for display from the user.

Command line tools include applications, commands, and scripts.They can reside on the CMS or another managed system. Theycan be launched directly from the CLI or GUI.

Command line tools

Custom tools are tools that can be created by the user to run on the Central Management Server or on targetsystems. For example:

• Remote tool A tool that runs on selected target systems. It might copy files to the target systems orrun specific X-Window applications on the target systems. This tool can be scheduled.

• CMS tool A tool that runs on the Central Management Server. It is usually a script or batch file andcan pass in environment variables. Using Automatic Event Handling, this tool can optionally be configuredto run when events are received. This tool can be scheduled.

• Web page tool A tool that launches a web URL. The URL is launched in a separate browser windowon the Central Management Server. This tool cannot be scheduled.

Information storageHP SIM uses an audit log and a database to track activity and store your management domain information.

HP SIM audit logHP SIM logs all tasks performed by all HP SIM users on all systems. The information is stored in the auditlog on the CMS. HP SIM logs all tasks with the following information:

• Time stamp

• User name

• Systems

• Event

• Tool result

For command tools, the verbose level of stdout and stderr is frequently large and time-sensitive, so it isonly logged by default for the ps command. You can configure the option to log this output for the ps andother commands, as well as other aspects of the audit log, such as maximum file size. Information aboutconfiguring the audit log is available in Chapter 15 “Configuration options”.

DatabaseHP SIM uses a database to store vital management domain information. The database contains the followinginformation:

• Authorizations

• Systems

• System lists

• System group definitions• Users

• Passwords

• Toolbox definitions

• Tool definitions

• Events

• Inventory data

You can use the HP Systems Insight Manager Sizer, located athttp://h71019.www7.hp.com/activeanswers/Secure/274366-0-0-0-121.html to get a recommended serverconfiguration based on projected management workloads, installed management applications, and number

of console users.

Information storage 15

http://h71019.www7.hp.com/activeanswers/Secure/274366-0-0-0-121.html

http://h71019.www7.hp.com/activeanswers/Secure/274366-0-0-0-121.html



Database software

HP SIM supports the use of several databases:

• Microsoft SQL Server Desktop Engine (MSDE) or Microsoft SQL Server 2000 is supported on a WindowsCMS. HP SIM ships with MSDE, but you can choose to use Microsoft SQL Server 2000, which providesmore advanced enterprise features. SQL Server 2005 running on Windows Server 2003 is supported.SQL Server 2005 Express Edition is NOT supported.

• Oracle 10g and Oracle 9i Release 2 are supported on all platforms.

NOTE: You must create the Oracle database using Unicode (AL32UTF8) as the character set beforeinstalling HP SIM. You must also specify the thin client .jar file location. HP SIM requires Oracle databaseand Transparent Network Substrate (TNS) listener services to be up and running when system is restarted.Oracle by itself does not start the Oracle database and TNS listener automatically. An Oracle databaseadministrator (DBA) must set these services to be restarted when the server is reset. See the Oracledocumentation for details on how to auto start these services athttp://download-east.oracle.com/docs/html/A96167_01/post-inst.htm#sthref548. Access to this linkrequires registration, which is free. The Oracle DBA who manages the Oracle installation must performthis task.

NOTE: You must install the Oracle JDBC driver, version 10.1.0.2.0. You can download this driverfrom the Oracle website at

http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html.

Secure accessHP SIM utilizes several technologies to provide secure access. You can access HP SIM through the commandline or a web browser. Both of these user interfaces can be accessed from anywhere on your network.

Command line interface When you access HP SIM from the CLI, your operating system login is used to identify you to HP SIM. Youhave access to use the HP SIM commands based on your authorizations. If you access HP SIM from anysystem other than the CMS, be sure you use an SSH client. Programs like telnet, rlogin, and FTP do notprovide encrypted access. When you use one of these applications to access HP SIM, your data, including

your password, is transmitted across the network unencrypted. In addition, these protocols are notspoof-protected. If you have a Windows CMS, then only administrators have command line access to HPSIM. A remote desktop connection to the CMS can be used to access the command line.

Graphical user interface When you access the HP SIM from a web browser, you log in using the secure HTML login page. The username and password for the login page are the same as your CMS operating system user name and password. A Windows CMS also requires a domain name. Your information is securely transmitted using the SSLprotocol. SSL provides data encryption and server authentication by using a public and private key technology.The web server on the CMS uses a certificate for server authentication. By default, this certificate is self-signed,but it can be replaced by a certificate that is signed by a trusted certificate authority. Your web browsershould import this certificate to trust the CMS.

16 Product overview

http://download-east.oracle.com/docs/html/A96167_01/post-inst.htm#sthref548l

http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html


http://download-east.oracle.com/docs/html/A96167_01/post-inst.htm#sthref548l



Secure data transmissionThe security of the transaction depends on your networking environment and the management protocol thateach tool is using.

Management protocols

The basic supported management protocols and applications are SSH , Web-Based Enterprise Management (WBEM) , Secure HTTP (HTTPS) , Desktop Management Interface (DMI) , and SNMP . Tools are not limited tothese protocols, and they can provide a custom management protocol. SSH is the only protocol that mustbe installed on every managed system. Tools require specific protocols, and they can only be run on amanaged system if the protocol they require is installed and configured correctly.

SSH SSH is a program that enables you to log in to another system over a network and execute commandson that system. It also enables you to move files from one system to another, and it provides authenticationand secure communications over insecure channels. SSH uses a public/private key pair to provide a securemechanism to authenticate and encrypt communication. SSH keys are used to identify the execute-as useron the managed system. Typically, the execute-as user is either root or administrator, but other users can beconfigured, depending on the tool that will be executed on the managed system. The private key is keptsecure on the CMS, while the public key is installed on each managed system.

The SSH-2 protocol is used by the Distributed Task Facility (DTF) to communicate with managed systems.The DTF improves operator efficiency by replicating operations across the systems or system groups withinthe management domain using a single command. This functionality reduces the load on administrators inmultisystem environments. X Window and CLI tools use the DTF to execute and support the following tasks:

• 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 DTF tells theSSH server what tasks must be performed on the system. The SSH server then performs the tasks and returnsthe results to the DTF. The DTF consolidates the feedback it receives from all the managed systems.

WBEM WBEM is an industry standard that simplifies system management. It is based on a set ofmanagement and Internet standard technologies developed to unify the management of enterprise computing

Secure data transmission 17



environments. It provides access to both software data and hardware data that is readable by WBEM-compliant applications.

HP SIM keeps a database of passwords for managed systems running WBEM. The database contains theuser names and passwords for each managed system, which are required to provide user authentication fortools using this protocol. These accounts do not need to have other access capabilities, such as login rights.They are only used for WBEM access by HP SIM. The WBEM user name and password can be set from theCLI or GUI. For more information, see the "Administering systems and events" section in the HP SIM User Guide at http://docs.hp.com/en/index.html.

HP SIM uses HTTPS to access WBEM data, providing a secure path for system management data. For accessto Windows management data instrumented in Windows Management Instrumentation (WMI), a WMIMapper running on a Windows system converts the HTTPS WBEM requests into WMI requests, which useDistributed Component Object Model and NT security.

A new SSL certificate is created during CMS initialization that is used as a client credential in WBEM requestsinstead of the CMS certificate. Select Use certificate instead in the WBEM settings section of the System

Protocol Settings page to authenticate using the WBEM certificate.

NOTE: The WBEM client certificate authentication feature is only supported on HP-UX systems which have WBEM Services 2.5 installed for HP SIM.

HTTPS HTTPS is simply HTTP over SSL, a protocol that supports sending data securely over the Web.

HTTPS is used to access WBEM data as explained in the previous section, and it is used to access ProLiantagent information. Digital certificates are used instead of user names and passwords to establish trust betweenthe agent and the CMS. The certificate of the CMS should be loaded into each agent to be managed bythat CMS.

Desktop Management Interface DMI is an industry-standard protocol, primarily used in client management,established by the Desktop Management Task Force . DMI provides an efficient means of reporting clientsystem problems. DMI-compliant computers can send status information to a CMS over a network. DMI issupported for system inventory collection where the information is not available from WBEM and SNMP. A Windows CMS uses DMI to gather information from third-party servers. DMI is not a secure protocol.Therefore, anyone with access to your network can intercept and view DMI transactions.

SNMP SNMP is a set of protocols for managing complex networks. SNMP works by sending messages,called protocol data units (PDUs), to different parts of a network. SNMP-compliant devices, called agents,

store data about themselves in Management Information Bases (MIBs) and return this data to the SNMPrequesters. SNMP is available in several versions. SNMP Version 1, used by HP SIM, is not a secure protocol.Therefore, anyone with access to your network can intercept and view SNMP transactions.

HP SIM keeps a database of read and write community names for managed systems running SNMP. Thecommunity name must match those configured on the management system. The SNMP community namesand passwords can be set from the CLI or GUI. For more information, see the "Administering systems andevents" section in the HP SIM User Guide at http://docs.hp.com/en/index.html.

HP SIM does not use SNMP SetRequests. By default, the supported operating system platforms have SNMPSetRequests disabled. For improved security, do not enable SNMP SetRequests on the CMS or the managedsystems. Even SNMP GetRequest responses can be spoofed, so all information from SNMP should be regardedas insecure.

Web server securityHP SIM uses the Tomcat web server on the CMS. Tomcat features that are not required by HP SIM are turnedoff by default. These features include Server Side Includes and Common Gateway Interface scripts.

Self-signed certificatesThe self-signed certificates used for WBEM and web server authentication make it possible for another systemto impersonate the CMS if the valid certificate is not securely imported into the client or browser, which isknown as spoofing . To prevent the possibility of spoofing, use a certificate signed by a trusted Certificate Authority (CA) or securely export the certificate by browsing locally to the CMS and then securely importingit into your browser. You can also obtain the server certificate by browsing remotely and saving it in thebrowser the first time you access HP SIM, but this option is less secure and still susceptible to a possible

18 Product overview

http://docs.hp.com/en/index.html






"man-in-the-middle" attack. Information about importing CA-signed certificates is available in the "Administeringsystems and events" section of the HP SIM User Guide at http://docs.hp.com/en/index.html.

X application securityThe data exchanged between an X client (or application) running on a managed system and an X serveron the network client is transmitted in clear text over the network. HP does not recommend X clients inenvironments in which security is a concern.

Managing servers behind a firewallHP SIM supports managing servers that are located behind a firewall when using the SSH, HTTPS, and WBEM protocols. HP does not recommend the SNMP and DMI protocols because they are not secureprotocols. The firewall must be configured to allow this traffic through the firewall. The following ports areused:

• WBEM uses HTTPS over port 5989

• Web Agents use HTTPS over port 2381

• DTF uses SSH-2 over port 22

For a complete list of ports used by HP SIM, see the Understanding HP SIM Security white paper. This whitepaper is available at http://www.hp.com/go/hpsim/.

Secure data transmission 19


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

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




2 Installation overview and requirementsThis chapter provides an overview of the HP SIM installation process, and it identifies the system requirementsfor a Windows CMS, a managed system, and a network client.

First time install process overviewPerform these steps for a first time install of HP SIM on your CMS:

1. Install and configure the CMS. The procedure to complete this step is in the installation chapter of thisguide. See Chapter 3 “Installing HP SIM on the Central Management Server (CMS) for the first time”for details.

2. Configure HP SIM for your environment. See Chapter 4 “Configuring HP SIM using the First Time Wizard” or Chapter 5 “Configuring HP SIM using the Options menu” for the recommended tasks.

3. Install and configure the required Management Agents on the systems that will be managed by theCMS. This step is covered in the first section of Chapter 6 “Setting up managed systems”.

4. Configure the remaining protocols for the managed systems. See Chapter 7 “Configuring managedsystems” for details.

Upgrade overviewIf HP SIM has previously been installed on your CMS proceed to the upgrade instructions inChapter 10 “Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2”" orChapter 11 “Upgrading HP Systems Insight Manager from 4.x or later ” for details.

System requirementsThis section identifies the hardware and software requirements and recommendations for HP Systems InsightManager. These requirements are broken into sections for the CMS, managed system, and network client.

Windows Central Management ServerThis section contains the minimum requirements for the Windows operating system that is used for the CMS.

NetworkingSoftwareHardwareOperating system

MSDE 2000 with Service Pack3a (bundled with HP Systems

Any HP ProLiant x86 systemwith the following configuration:

• Static or dynamic host nameresolution

• Microsoft WindowsServer(TM) 2003 R2

Insight Manager) or one of thefollowing:

• Minimum: 1.5-GHzprocessor with 1 GB RAM

• •Microsoft Windows 2003,Standard or Enterprise

TCP/IP

• SNMP• Microsoft SQL Server 2000,

Standard Edition withEdition, for x86 with ServicePack 1 (running on x86 orx64/AMD64 platforms)

• 500 MB free disk spacerecommended

Service Pack 3 or ServicePack 4 (for Standard Serveroperating system)

• Recommended: 2.4-GHzprocessor with 1.5 GB RAM

Note: If Microsoft SQLServer is installed on the

• Microsoft Windows 2003SMB, with Service Pack 1

• Microsoft SQL Server 2000,Enterprise Edition with• Microsoft Windows 2003

for x64 CMS, an additional 500 MBof RAM should be installed.

Service Pack 3 or ServicePack 4 (for "AdvancedServer" operating system)

• Microsoft Windows 2000Server with Service Pack 4for x86 Note: HP Netserverplatforms can be used for • Microsoft SQL Server 2005

running on Windows Server2003

Note: SQL Server 2005Express Edition is notsupported.

the CMS as long as theInstant Toptools software isnot installed and all otherrequirements are met.

• Microsoft Windows 2000 Advanced Server withService Pack 4 for x86

• Microsoft Windows XPProfessional with ServicePack 2 for x86

• Microsoft SQL Server 2005Service Pack 1The CMS supports Microsoft

Windows 2000 and 2003• Oracle 9i Release 2International Server - French,

German, Italian, Spanish, and • Oracle 10g Japanese (latest service packavailable for each language). • ProLiant Support Pack for

Windows 6.30 or later

• Microsoft Internet Explorer7.0

First time install process overview 20



NetworkingSoftwareHardwareOperating system

• Microsoft Internet Explorer6.0 with Service Pack 1

• Firefox 1.5

NOTE: HP SIM 5.1 can run on a Windows Virtual Machine (VM) provided the following requirements aremet. The VM must be hosted on an ESX 3.0.1 or later server and the VM configuration must meet HP SIM

hardware requirements and the CPU and Memory resources allocated to this VM must be always availableto this VM (by reserving CPU and Memory resources).

The required Windows service packs must be installed for each of these operating systems.

Important: The Windows server must have at least one partition formatted for the NT File System (NTFS) onwhich the HP SIM server software is to be installed. NTFS provides the ability to restrict file access basedon user accounts and groups. Without NTFS, the CMS cannot be adequately secured against unauthorizedaccess, and potentially sensitive operations and data could be made available to unauthorized users.

Note: HP SIM on Windows XP Professional only supports a local MSDE2000 installation for the database.

Note: Service Essentials Remote Support Pack (Remote Support Pack) is not supported on Windows XPProfessional. If you install HP SIM on Windows XP Professional, you will not be able to use Remote SupportPack.

Note: SQL Server 2005 is only supported if HP SIM is running on Windows Server 2003.

Note: You cannot run Internet Explorer 6.0 and Internet Explorer 7.0 simultaneously. However, if you uninstallInternet Explorer 7.0, Internet Explorer 6.0 will be restored.

Managed system requirements and recommendationsThis section contains requirements and recommendations for managed systems.

Operating systems

Windows managed systems

• Microsoft Windows 2003 Standard for x86

• Microsoft Windows 2003 Standard with Service Pack 1 for x86• Microsoft Windows 2003 Enterprise for x86

• Microsoft Windows 2003 Enterprise for x64

• Microsoft Windows 2003 Enterprise Service Pack 1 for x86

• Microsoft Windows 2003 Enterprise for Itanium-based Systems

• Microsoft Windows 2003 Enterprise with Service Pack 1 for Itanium-based Systems

• Microsoft Windows 2003 Extended Systems for x64 and AMD64

• Microsoft Windows 2003 Web Edition for x86

• Microsoft Windows 2003 Data Center

• Microsoft Windows 2003 Small-Medium Business for x86

• Microsoft Windows Professional for x86

• Microsoft Windows Data Center for x86

• Microsoft Windows 2000 Server with Service Pack 4 for x86

• Microsoft Windows 2000 Advanced Server with Service Pack 4 for x86

• Microsoft Windows 2000 Server for x86

• Microsoft Windows 2000 Advanced Server for x86

• Microsoft Windows 2000 with Service Pack 1 or later for x86

• Microsoft Windows XP with Service Pack 2

Managed system requirements and recommendations 21



• Microsoft Windows XP with Service Pack 1

• Microsoft Windows XP

• Windows NT4 Service Pack 6

• Microsoft Windows Virtual Server

• Windows Vista Client

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

HP-UX managed systems• HP-UX 11.0 as a managed node running the DMI agents on that platform

• HP-UX 11i

• HP-UX 11i v2 (September 2004 or later)

• HP-UX 11iv3

• HP Tru64 UNIX

• HP NSK

Linux managed systems

• Red Hat Linux 9

• Red Hat Linux 8• Red Hat Linux 7.3 Workstation

• Red Hat Linux 7.2

• Red Hat Enterprise Linux 4 for x86

• Red Hat Enterprise Linux 4 for AMD64 and EM64T

• Red Hat Enterprise Linux 3 for x86

• Red Hat Enterprise Linux 3 for AMD64 and EM64T

• Red Hat Enterprise Linux 3 Itanium-based systems

• Red Hat Enterprise Linux 2.1 for x86

• Red Hat Enterprise Linux 2.1 for Itanium-based systems

• SUSE Linux Enterprise Server 10

• SUSE Linux Enterprise Server 10, 64 bit

• SUSE Linux Enterprise Server 9 with service pack 3 for x86

• SUSE Linux Enterprise Server 9 for Itanium-based systems

• SUSE Linux Enterprise Server 9 for x86

• SUSE Linux Enterprise Server 9 for AMD64 and Intel EM64T

• SUSE Linux Enterprise Server 8 for Itanium-base systems

• SUSE Linux Enterprise Server 8

• SUSE Linux Enterprise Server 8/United Linux 1.0

• SUSE Linux 7.2

• SUSE Linux 7.0

• VMware ESX

• VMware GSX

Hardware

For HP-UX:

• Any HP PA-RISC system

• Any HP Itanium®-based system

22 Installation overview and requirements



For Windows:

• Any HP x86 system


For Linux:



•

Any HP Itanium-based systemSoftware

This software is not required, but if you want improved management capabilities, HP recommends that youinstall these components.

For Windows:

• OpenSSH Services 4.3p2

• ProLiant Support Pack 6.30 or later

• WBEM/WMI

• SNMP (recommended as an alternative to WBEM)

• WBEM (for Integrity systems only)

This software is not required, but if you want improved HP SIM capabilities, HP recommends that you installthese components, which can be purchased or downloaded from many software suppliers:

• SSH Client

• X Window Server

Required web browsers

For Windows:

• Microsoft Internet Explorer 6 with Service Pack 1 or later

• Firefox 1.5 or later

Note: For optimum performance, the minimum resolution for the browser should be 1024 x 768.

For HP-UX:

▲ Firefox 1.5 or later

For Linux:

▲ Firefox 1.5 or later

Note: For all Internet Explorer browsers, you must have the SSL 3.0 or TLS 1.0 browser security optionsenabled for HP SIM to work properly.

Managed storage system

To view the latest information regarding HP SIM support for a particular storage system, including FibreChannel disk arrays, switches, tape libraries, or hosts (with Fibre Channel host bus adapters), see the HPSIM SMI-S Provider web page at http://www.hp.com/go/hpsim/providers.

This webpage also offers information on obtaining and installing SMI-S providers.

SSH requirementsSSH is locally configured during HP SIM local installation on the CMS.

Custom tools on the Tools menu require SSH on the CMS to run properly. These commands run on theCMS with environment variables set to the context of specific events or devices. SSH on the CMS is alsoused by the Initial ProLiant Support Pack Install on the Deploy→Deploy Drivers, Firmware and Agents

menu.

You can install and configure SSH on each of the managed systems and have HP SIM exchange keys withthe managed systems (through the mxagentconfig command or for Windows, through the Install OpenSSH

task). If you do this, then the Command Line Tools option on the Tools menu works for these managed

SSH requirements 23

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




systems. If you choose not to configure it to work with remote SSH clients, then these commands fail. If SSHis not configured on the client, then command line tools, any HP SIM plugins that require SSH, and configureor repair agents will not work properly.

24 Installation overview and requirements



3 Installing HP SIM on the Central Management Server(CMS) for the first time

Preparing the systemThese steps are for a clean installation of HP SIM on your Windows system. If a previous version of HP SIMor Insight Manager 7 Service Pack 2.3 is installed on your system and you want to upgrade your data, see

Chapter 10 “Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2” orChapter 11 “Upgrading HP Systems Insight Manager from 4.x or later ” for more information on upgrade.

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

1. Install and configure the CMS. The procedure to complete this step is in the this chapter.2. Configure HP SIM for your environment. See Chapter 4 “Configuring HP SIM using the First Time

Wizard” or Chapter 5 “Configuring HP SIM using the Options menu” for the recommended tasks.

3. Install and configure the required Management Agents on the systems that will be managed by theCMS. This step is covered in the first section of Chapter 6 “Setting up managed systems”.


NOTE: If installing HP SIM with a local MSDE or SQL database on a Windows XP SP2 machine that isnot a member of a domain, Simple File Sharing is automatically disabled. The Simple File Sharing settingon Windows XP Professional changes the way local users are authenticated.

Enabled = Guest only. Local users authenticate as Guest.

Disabled = Classic. Local users authenticate as themselves.

This setting is located in the Local Security Policy Editor under Start>Control Panel>Administrative

Tools>Local Security Policy. Select Security Settings>Local Policies>Security Options>Network

access: Sharing and security model for local accounts. This change is necessary for the databaseinstall.

To verify and prepare your system, perform the following procedure:

1. Verify your system meets the minimum requirements. See “System requirements” for details.

2. Install the required Windows and Microsoft SQL Server 2000 Server or MSDE Service Packs.

Note: The Silent install for HP SIM does not support an Oracle database.

Note: If you are using an external SQL database, leave the default as "Master" to insure that all necessarydatabases are created with correct permissions.

3. Verify your system has at least one partition formatted for the NTFS file system, on which the HP SIMserver software is to be installed.

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

4. If you have HP Instant Support Enterprise Edition (ISEE) Windows Client software A.03.95 or older,installed on your CMS AND you wish to install HP Service Essentials Remote Support Pack along with

HP SIM 5.x, then you must remove the ISEE client software first. To remove ISEE complete the followingsteps:

a. Select Start>Settings>Control Panel> Add/Remove Programs.

b. Select HP Instant Support Enterprise Edition Client from the list of installed programs, thenclick [Change/Remove].

5. Verify that Microsoft Access Data Components (MDAC) 2.7 Service Pack 1 or higher is installed.Navigate to C: \Program Files\Common Files\System\Ado, and right-click the icon for themsado15.dll file. Select Properties, and click the Version tab to display the version number. If the fileis not found in this path, use the Windows search engine to find the file. If you must download MDAC,see http://www.microsoft.com/downloads/, and search for MDAC Service Pack.

6. Before you proceed with the install, if you are going to perform a custom install HP ProLiant Essentials

Performance Management Pack , HP ProLiant Essentials Virtual Machine Management Pack , or the

Preparing the system 25

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

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



System Management Homepage see the following documents for specific user name requirements forthe product administrator, service account, and database administrator:

• HP ProLiant Essentials Performance Management Pack documentation athttp://www.hp.com/products/pmp

• HP ProLiant Essentials Virtualization Management Software User Guide at http://www.hp.com/servers/proliantessentials/vmm

• System Management Homepage Installation Guide at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html

HP SIM can be installed three ways:

• Typical install - Requires minimal user interaction. See Typical install for more information.

• Custom install - Enables you to select the components you want to install. See Custom install formore information.

• Silent install - Requires no user interaction. Administrators can install HP SIM to target systems usingcommand line options. See Silent install for more information.

7. Download the software, or install it from the HP Management CD or the Insight Control ManagementDVD.

To download the software, see http://www.hp.com/go/hpsim, and on the upper-left of the page underHP Systems Insight Manager, click Download. The HP SIM Download Page appears. Under Download

HP Systems Insight Manager , select HP SIM-Windows. Select the latest version for a full productinstall.

To install the software from the Management CD, place the CD in the CD-ROM drive. The CD has anautorun feature that launches a license agreement. Agree to the license agreement, and click theProducts tab. Click Install under HP SIM to launch the Installer. Or click the Products tab, clickExplore CD, and then run setup.exe located at \HPSIM\win_ia32\ to launch the Installer.

To install the software from the Insight Control Management DVD, place the DVD in the DVD-ROM drive.The DVD has an autorun feature that launches a license agreement. Agree to the license agreement,and click the Products tab. On the sidebar under Foundation Management Products, select HP

Systems Insight Manager , then click Install under HP SIM to launch the Installer. Or click the Products

tab, click Explore DVD, and then run setup.exe located at \HPSIM\win_ia32\ to launch the Installer.

Note: The installing account and the HP SIM service account, both included in the local admins group,are the initial login account.

The Welcome to the HP Systems Insight Manager Installer window appears. HP SIM examinesthis system for supported versions of MSDE, SQL Server, and Oracle. If no local database is found, theoption to install MSDE is presented.

Note: Click the drop-down selection box in the upper-right corner of any dialog box to view the HP SIMInstallation and Configuration Guide , ReadMe or Release Notes.

8. Click Next. The System Inspection window appears. The system is inspected for a previous versionof HP SIM and a local database. When the Database Configuration window appears, if the localdatabase found is MSDE, click Use SQL/MSDE if you want to use an existing instance. If no localdatabase is found, click Install and Use MSDE to start the MSDE install process. You are given theoption to Install and Use MSDE if your local MSDE has less than four instances installed.

Note: If you are installing onto a Windows 2003 Small Business Server, do not select to install to thedefault MSDE instance: MSSQLSERVER. Instead, select a different available instance name or installand use a new MSDE instance. MSDE uses MSSQLSERVER, so using it again will cause a conflict.

For SQL Server or MSDE:

Enter the Account Credentials for the database server. The installing user account is prepopulated inthe Username field and can be edited. The Host field prepopulated with the local host name and canonly be edited if doing a fresh install. Provide the password for the installing user, and click Next toproceed.

26 Installing HP SIM on the Central Management Server (CMS) for the first time

http://www.hp.com/products/pmp/

http://www.hp.com/servers/proliantessentials/vmm


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


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






http://www.hp.com/products/pmp/



Note: HP SIM does not support the following in a user name and password:

• A blank password

• A space followed by a double-quote

• A backslash (\)

If you use these characters in your user name or password, the HP SIM database initializationfails.

For Oracle:

The Oracle database with Unicode (AL32UTF8) as the character set must be created before installingHP SIM. An Oracle user with DatabaseAdministrator (DBA) privileges must be created in this databasefor the exclusive use by HP Systems Insight Manager. HP SIM must be installed in an empty Oracledatabase schema. The thin client .jar file must be copied on to the system, and its location must bespecified during installation. Provide valid values for the following:

• User name: This Oracle user name must be assigned DBA role.

NOTE: An Oracle user name cannot contain a backslash (\) or a forward slash (/).

• Your password

• Host: The name of the remote or local server where Oracle is installed. An IP address may alsobe used.

• Database: The name of the database created on Oracle for the use of HP SIM.

• Port: The default is 1521.

• JarFile: The full path that points to the .jar file, must be accessible through the file system on theCMS. Installation copies the file to the correct location.

9. When the Select Installation Type window appears, select Typical to install the included componentswith minimal user interaction listed under the Available Components for Install or select Custom toselect the individual components under the Available Components for Install and configure themduring installation.

Custom installationTypical installation Available components for installIncludedIncludedSystem Management Homepage

OptionalIncludedOpenSSH Services 4.3p2

OptionalIncluded WMI Mapper

IncludedIncludedHP Systems Insight Manager

OptionalIncludedService Essentials Remote Support Pack

OptionalIncludedHP ProLiant Essentials Performance Management Pack

OptionalIncludedHP Version Control Repository Manager

OptionalIncludedHP ProLiant Essentials Virtualization Management Software

Note: If a component is not listed as being available for installation on the CMS, then the HP SIM installshell has determined one of the following:

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

• A newer version of the component is currently installed.

If the component that is present on the CMS is an older version than what is bundled with the HP SIMinstall shell and it supports an in-place upgrade, it appears in the component list.

Note: HP ProLiant Essentials Performance Management Pack and HP ProLiant Essentials VirtualizationManagement Software cannot be installed in a Typical install against an Oracle database. A Custominstall must be performed.

See "Typical install", "Custom install" or "Silent install" more information.

Preparing the system 27



Typical install1. Click Next, the Service Account Credentials window appears. The Domain and User name fields

default to the installing account credentials and these fields can be edited.

Note: This user account is used to run the HP SIM service.

2. Enter the password for this account. Click Next, the Summary window appears with the componentsthat are to be installed.

3. Click Install to initiate the installation process. This process installs all the products listed in the Selected

Components table. The Status window appears. As each component is being installed, it states "InProgress" beside the component's name. After the component has installed, it states "InstalledSuccessfully."

4. After all the components are installed, click Next. The Registration window appears. Register HP SIMor click the Register Later button.

Note: If you do not have Internet access, click the Register Later button.

5. After registering or clicking the Register Later button, the Installation complete window appears.For a fresh install, the following message appears For this new install, an operatingsystem account must be created and configured in the System ManagementHomepage on this computer and each HP Version Control Agent must beconfigured to use the new account. For more information, refer to the Version Control Installation Guide athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html.

6. The reboot option is presented on this screen. The Yes, reboot the system now option is selected bydefault. Click Finish to allow the system to reboot. This completes the typical installation process See"Next steps" for more information.

Note: For more information regarding where the System Management Homepage default settings arestored during a Typical installation and how to change them, see the System Management Homepage Installation Guide at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html.

Custom install1. Click Next, the Software Selection window appears. This window displays the complete list of the

available components with a checkbox next to each one. If the checkbox is selected and disabled, thecomponent is deemed a mandatory component and cannot be cleared. The amount of required diskspace is also listed for each component. Select the components you wish to install.

2. Click Next to verify that enough disk space exists for the selected components. If enough space exists,the Service Account Credentials window appears. The Domain and User name fields default to theinstalling account credentials and can only be edited if doing a fresh install. Enter the password for thisaccount.

Note: This user account is used to run the HP Systems Insight Manager service.

3. Click Next. The Summary window appears.

4. Click Install to initiate the installation process. This process installs all the products listed in the Selected

Components table. The Status window appears. As you install each component, it states "In Progress"

beside the component's name. After the component has installed, it states "Installed Successfully."5. Install the System Management Homepage:

a. The System Management Homepage Setup window appears. The InstallShield Wizard guidesyou through the install of System Management Homepage. Click Next. The Operating Systems

Groups window appears.

Note: If at any time during the install of System Management Homepage you click Cancel, theinstallation and setup of the System Management Homepage ends.

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

c. Enter the group name of an operating systems group in the Group Name field. Click Add. Thegroup name is added. A maximum of five entries can be added for each group level. Click Next

to continue.

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










d. From the User Access window, configure the System Management Homepage for the followingaccess types:

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

• Select Local Access Anonymous or Local Access Administrator to set up the SystemManagement Homepage to automatically grant local IP addresses at the selected accesslevel.

Caution: Selecting Local Access with Administrator privileges provides any users with accessto the local console full access without prompting them for a user name or password.

e. Click Next. The Trust Mode window appears.

f. Select the level of security you want to provide from one of the three trust modes:

• Trust By Certificate

Select Trust By Certificate, and click Next. The Trusted Certificates window appears.The Trusted Certificates window allows trusted certificate files to be added to theTrusted Certificate List.

i.

ii. Click Add File to browse and select any certificates to be included in the Trusted

Certificate List. The Select File window appears. If an invalid file name is entered inthe file name field, an error message appears, indicating the file does not exist. ClickOK to select another file, or click Open to add the file to the Trusted Certificate List.The Trusted Certificate List appears. Click Next.

Note: If you click Next without adding any certificates to the list, and no certificates existfrom a previous installation, a message appears, indicating that if you do not specifyany trusted certificates, HP SIM cannot access the HP Insight Management Agent on thissystem. Click OK if you do not want HP SIM to access the Insight Management Agenton this system, or click Cancel to close the window and add the trusted certificates tothe list.

Note: The Trust By Certificates option enables the System Management Homepagesystem and the HP SIM system to establish a trust relationship by means of certificates.This mode is the strongest method of security because it requires certificate data andverifies the digital signature before enabling access.

or

i. Click Import. The Import Server Certificate window 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 Trusted

Certificate List, click Accept and the certificate is added to the Trusted Certificate

List, or click Cancel if you do not want to add it to the Trusted Certificate List. TheTrusted Certificate List appears. Click Next.

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

Note: To delete a certificate, select the certificate, and click Delete. The selected certificateis removed.

v. From the IP Binding window, select the IP Binding checkbox if you would like to bindto IP addresses that match a specific subnet and mask. Click Next.

vi. From the IP Restricted Logins window, select the Enable IP Restricted Logins

checkbox if you would like to include or exclude specific IP addresses or IP addressranges. Click Next, and the Summary Panel appears.

• Trust By Name

Select Trust By Name. Click Next. The Trusted Server window appears. Enter thenames of the servers you want to trust.

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

i.

By Name mode sets up the System Management Homepage to only accept certainrequests from servers with the HP SIM names designated in the Trust By Name field.The Trust By Name option is easy to configure and can prevent non-malicious access.

Custom install 29



For example, you might want to use the Trust By Name option if you have a securenetwork, but your network has two groups of administrators in two separate divisions.The Trust By Name option would prevent one group from installing software to thewrong system. This option does not verify anything other than the HP SIM server namesubmitted.

Note: The server name cannot contain the following characters:

~ ! ` @ # $ % ^ & * ( ) + = " : ' < > ? , | ;

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

Note: If you click Next without adding any server names to the list, an error messageappears, indicating that if you do not specify any trusted server names, HP SIM cannotaccess the Insight Management Agent on this system. Click OK to proceed withouttrusting any systems, or click Cancel to close the window and add server names to thelist.

Note: To delete a certificate, select the certificate and click Delete. The selected certificateis removed.

iii. From the IP Binding window, select the IP Binding checkbox if you would like to bindto IP addresses that match a specific subnet and mask. Click Next.

iv. From the IP Restricted Logins window, select the Enable IP Restricted Logins

checkbox if you would like to include or exclude specific IP addresses or IP address

ranges. Click Next, and the Summary Panel appears.

• Trust All

Select Trust All. Click Next. The IP Binding window appears.i.ii. Select the IP Binding checkbox if you would like to bind to IP addresses that match a

specific subnet and mask. Click Next.

Note: The Trust All option leaves your system vulnerable to security attacks and sets upthe System Management Homepage to accept certain requests from any server. Forexample, you might want to use Trust All if you have a secure network, and everyonein the network is trusted.

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 you mightnot be able to connect to the System Management Homepage.

The IP Restricted Logins window appears. The IP Restricted Logins window enablesyou to select specific IP addresses or IP address ranges to include or exclude from gaininglogin access. Although optional, the System Management Homepage can restrict loginaccess based on the IP addresses of the machine attempting to gain access.

iii. Select Enable IP Restricted Logins, and click Next. The IP Addresses to Include

window appears. This window enables you to specify the IP address or IP address rangesto grant 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 RestrictedLogins window. Enter the single address in the first box.

iv. In the Include field, enter a beginning IP address to which you want to grant loginaccess. In the To field, enter an ending IP address to which you want to grant loginaccess. All IP addresses that fall between the beginning and ending IP addresses aregranted login access. Click Add. The IP address or IP address range is added to theExclusion list. If necessary, select an IP address or IP address range, and click Delete

to remove it from the Exclusion list. Click Next.

Note: If you entered an invalid IP address or IP address range, an error message appearsindicating the IP address is invalid. Click OK. Enter a valid IP address or IP addressrange, and click Add again. The IP Addresses to Exclude window appears.




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

v. In theTo field, enter an ending IP address to which you want to deny login access. AllIP addresses that fall between the beginning and ending IP addresses are denied loginaccess.

vi. Click Add. The IP address or IP address range is added to the Inclusion list. If necessary,select an IP address or IP address range, and click Delete to remove it from the Inclusion

list. Click Next.

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

Note: If you select Next without adding any IP addresses to the Include or Exclude

lists, a warning message appears, stating, IP Restricted Login checkbox willbe marked as disabled. Do you want to proceed without addingany IP Address restrictions? If you click OK, the IP Restricted Login optionon the IP Restricted Login window is cleared.

The Summary Panel appears. The Summary Panel lists the location where the SystemManagement Homepage is installed, the amount of space the installation requires, and the summaryof the options that you specified during the installation.

g. Click Next. The installation process is started. Click Finish to exit the wizard.Note: If HP SIM is installed after System Management Homepage is installed, the SystemManagement Homepage 2048-bit key pair is replaced with the HP SIM1024-bit key pair.

6. Install OpenSSH:

a. On the Welcome to the OpenSSH Services Setup Wizard, click Next. The Select Destination

Location window appears. Setup installs OpenSSH into the following folder C:\ProgramFiles\OpenSSH. To change the location, use the Browse button. Click Next. The OpenSSH

Service Log On As User window appears.

b. Enter your account password. The User name and Domain fields are prepopulated. Although thesefields are prepopulated, you can change these values to specify any user you choose. However,the account credentials you do choose must have local administrator rights (be a member of the

local "Administrators" group.) Click Next. The Ready to Install window appears.Note: The OpenSSH Service Log On As User window appears only if installing on a WindowsXP or Windows 2003 system. If you are installing on a Windows 2000 system, the OpenSSHService runs as "localsystem" and does not ask for credentials.

c. Click Install to continue with the installation.

d. After installing OpenSSH, if prompted, click No, I will restart the computer later .

e. Click Finish.

Note: The local security policy is modified to give you the following rights: log on as a service,create a token object, and replace a process level token. See the HP SIM Readme at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more details.

7. Install the WMI Mapper:a. On the Welcome to the Pegasus WMI Mapper Setup Wizard, click Next. The End-User

License Agreement window appears.

b. After reading the license agreement, click I accept the terms in the License Agreement. ClickNext. The Choose Setup Type window appears.

c. Select the setup type. (The basic requirement for HP SIM is Typical installation. If you select Typical,omit step d.)

d. Select the default location C:\Program Files\The Open Group\WMI Mapper or changethe destination location using Browse. Click OK. Click Next. The Ready to Install windowappears.

Custom install 31

http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html






e. Click Install to continue with the installation.

f. Click Finish.

Note: For Windows XP SP2 or Windows 2003 SP1 or later, COM security is updated to allowremote access and activation by everyone and anonymous users. See the HP SIM Readme at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more details.

8. Install HP Systems Insight Manager:

a. When the Welcome to the HP Systems Insight Manager Setup Wizard appears, click Next.The Select Destination window appears.

b. Select or enter a different folder name using Browse. Click OK>Next.The Select Start Menu

Folder appears.

c. Select or enter a different folder name using Browse. Click OK>Next. The Ready to Install windowappears.

d. Click Install. The Install Progress window appears.

e. Click Finish when the installation is complete to close the HP Systems Insight Manager Installer

window.

f. Once the HP SIM installation is complete, the Service Essentials Remote Support Pack windowappears. The configuration of the ISEE_CMS_SWMAGENT completes automatically. This processprovides the files needed so that you can access the Service Essentials Remote Support Packapplication and run the installation. The Service Essentials Remote Support Pack is not active until

it is customized to your enterprise. See the HP Remote Support Software Manager Initialization & Usage Guide located at http://docs.hp.com/en/5991-7446/5991-7446.pdf for configurationinstructions.

9. Install the HP ProLiant Essentials Performance Management Pack:

Note: PMP does not support a remote MSDE database. For PMP to connect to a local or remote Oracledatabase, install the Oracle client application on the server on which PMP is installed.

Note: HP BladeSystem Integrated Manager in HP Systems Insight Manager supports PMP only on Windows CMS's running SQL Server.

▲ Optional, if you plan to use an Oracle database. Install the Oracle client. If not, proceed to theHP ProLiant Essentials Performance Management Pack install step a.

a. Insert the Oracle 9i Release 2 CD in the CD-ROM drive of the server on which PMP is installed.

b. At the autorun, click Install/Deinstall Products.c. At the Welcome screen, click Next.

d. Enter the source and destination path for support files, and click Next.

e. Select Oracle 9 Client 9.2.0.1.0, and click Next.

f. Select Custom, and click Next.

g. In the Available Product Components, select the following options:

• Oracle Network Utilities 9.2.0.1.0

• Oracle Database Utilities 9.2.0.1.0

• SQL *Plus 9.2.0.1.0

• Oracle Windows Interfaces 9.2.0.1.0

• Oracle Call Interfaces 9.2.0.1.0

Click Next.

h. Specify the destination location of the JRE 1.1.8.16.0 or select the default location, and click Next.

i. Specify the Port number or select the default Port, and click Next.

j. Verify the installation summary, and click Install.

k. When prompted, insert the next Oracle CD in the CD-ROM drive, and click OK.

l. When prompted, insert the next Oracle CD in the CD-ROM drive, and click OK.

m. At the Oracle Net Configuration Assistant screen, click Cancel.

n. When prompted to cancel the Oracle Net Configuration Assistant, click Yes.

o. Click OK when the error message appears.

p. At the Configuration Tools window, click Next.




http://docs.hp.com/en/5991-7446/5991-7446.pdf






q. At the End of Installation screen, click Exit.

r. Click Yes to confirm.

Note: During the installation of the HP ProLiant Essentials Performance Management Pack, the followingwarning appears: "Warning: As part of PMP installation the HP SIM service mustbe stopped and restarted." Click OK to stop the service and continue PMP installation or clickCancel to abort the installation.

The Welcome to the HP ProLiant Essentials Performance Management Pack Setup Wizard appears.Click Next. The Service Account Credentials window appears.

a. Enter your account password. Click Next.b. If you are using an Oracle database, the Database Configuration screen appears. Enter your

valid user name, password and database name, and click Next.

c. The HP ProLiant Essentials Performance Management Pack Installing window appears andinstallation begins.

d. Click Finish to exit the HP ProLiant Essentials Performance Management Pack setup.

10. Install the HP Version Control Repository Manager:

a. When the HP Version Control Repository Manager Setup window appears, click Install. TheHP Version Control Repository Manager Setup Repository Directory window appears.

b. Select the directory from which HP Version Control Repository Manager will retrieve support packinformation using the Browse button. This directory must be manually created later if it does not

exist. Click OK. Click Next. The HP Version Control Repository Manager Automatic Updatewindow appears.

c. Select the Enable Automatic Update checkbox to enable automatic downloading of HP ProLiantSupport Packs and components at a specified interval and time.

d. Click Finish. Installation of HP Version Control Repository Manager proceeds and completes.

Note: If the HP Version Control Agent is configured to use the HP Version Control RepositoryManager, warning appears: "At least one HP Version Control Agent must beconfigured to use the HP Version Control Repository Manager." If noneare configured, verify the HP Version Control Agent settings to ensureproper operation of the automatic update feature. Click OK.

e. Click Close.

11. Install the HP ProLiant Essentials Virtualization Management Software:Note: During the installation of the HP ProLiant Essentials Virtualization Management Software, thefollowing warning appears: "Warning: The Virtualization Management Softwareinstallation requires HP SIM and database services to be running. Duringinstallation, the HP SIM service will be restarted." Click OK to start the HP SIMstatus check.

a. On the Welcome to the HP ProLiant Essentials Virtualization Management Software Setup

Wizard, click Next to continue with the installation. The Available Components window appearswith the following components to be installed:

• Virtual Machine Management Pack

• Server Migration Pack

b. Click Next to continue.

c. The Service Account Credentials window appears.

d. Enter your account password, and Click Next. Installation begins. The VMware VirtualCenter

Settings appears. Select one of the following:

• Configure VMware VirtualCenter Setting later

• Configure VMware VirtualCenter Setting now

Custom install 33



e. If you select to configure VMware VirtualCenter Setting now, enter your password and click Next.If you decide to configure at a later time, select Options>Virtualization

Management>Security>VMware VirtualCenter Settings from the HP SIM menu.

The Completing the HP Virtualization Management Software Setup Wizard window appears.

f. Click Finish to exit setup.

Note: For Oracle, if you are installing the HP ProLiant Essentials Virtualization Management Softwareand want to connect to a local or remote Oracle database, enter your password and .jar file locationon the Database Configuration screen. The HP ProLiant Essentials Virtualization Management Software

must be installed in an empty Oracle database schema. If Oracle is used as your primary HP SIMdatabase, an Oracle database must be created manually with the name VMMV21 before continuingwith the migration. HP ProLiant Essentials Virtualization Management Software database installationmay be omitted if the HP ProLiant Essentials Virtualization Management Software database alreadyexists in the specified schema. Click Yes to bypass HP ProLiant Essentials Virtualization ManagementSoftware database installation and use the current database. Click No to specify a different databasename. For more detailed information, see the HP ProLiant Essentials Virtualization Management Software User Guide at http://www.hp.com/servers/proliantessentials/vmm.

12. The Status window appears again, after all components have been installed, they will have an installedstatus. Click Next.

13. The Registration window appears. Register HP SIM or click the Register Later button.

Note: If you do not have Internet access, click the Register Later button.14. After registering or clicking the Register Later button, the Installation complete window appears.

15. Click Finish to complete the installation. If any of the components indicated that a reboot is necessary,your system automatically reboots after you click Finish.

Note: When installing HP SIM, a CMS host name that exceeds 15 characters is truncated, and the truncatedname must be used to complete the installation. After the install, two administrator accounts are created.One account includes the original host name\administrator and the other account includes the truncatedhost name\administrator. To log in, use the original host name in the Domain field on the Sign in page.

Silent installNote: Silent install of HP SIM does not support an Oracle database.

Installing HP SIM from the command line with an .xml file.The option to perform a Silent install is available through a command line installation. A silent install occurswhen “setup.exe” is launched with the command line options for a Silent install.

Execute:

setup.exe –s “<path to silent file>” –svcpw “<service password>” –dbpw

“<database password>”

A silent.xml file resides in the same directory as setup.exe. This text file can be edited with any text editor.If installing HP SIM from the CD, copy the silent .xml to a location where the file can be edited. If installingHP SIM from the Web, then after extracting the installation program, edit the silent.xml file and launchthe setup in Silent mode.

All errors, warnings or information messages are logged in the HP SIM.log. The installation status of HP SIMand installed components appear in the silentstatus.xml file. These files are created in the root of thesystem drive.

The silent.xml file contains the parameters below for the installation process.

Database information: Set <installMSDE>

as 'true' if you want to install and configure HP SIM to a locally running MSDE instance.

Note: MSDE can only be installed on the local server.

<dbUserName>

Provide a valid user account which is a member of the local admins group on the database server.

<dbDomain>

Provide the domain for the user account.






<dbHost>

This can be the local server or a remote system runnning SQL server or MSDE. Provide the host name or IPaddress of the database server.

<dbInstance>

Provide a valid existing instance name already running on the database server or specify a new instancename if you want to install MSDE on the local server.

<dbName>

use the default 'master'.<dbPort>

Use default 1433 or provide a valid port. HP SIM service Information:

<svcuserName>

Provide a valid local or domain user account which is a member of the local admins group.

<svcDomain>

Provide the domain for the user account.

Installation Location:

<baseInstallLocation>

and

<hpsimInstallLocation>

define the installation location of HP SIM and the partner components. The base installation location is themain directory that HP SIM and the partner components are installed to. OpenSSH, HP ProLiant EssentialsPerformance Management Pack and HP ProLiant Essentials Virtualization Management Software are installedin the

<baseInstallLcation>

specified in silent.xml. HP SIM will be installed in


specified in silent.xml. If the silent install finds a previous HP SIM installation on the target system, that locationwill be used instead System Management Homepage at %system root drive%\hp\hpsmh.WMI Mapper at

%system root drive%\program Files\The open group\WMI Mapper.<allowReboot>

Set this to true or false as desired. A server reboot is recommended after installing HP SIM and partnercomponents. The silent.xml lists all the components with their product IDs for install. Set the

<install>

value to true to install.

Note: HP SIM and System Management Homepage are always installed even if their

<install>

is set to false.

IMPORTANT: For a Silent install, the service or database user name and/or domain name containingspecial characters, such as: &, <, >, ', " must be escaped appropriately as below in the silent.xml file:

& &

< <

> >

' '

" "

For example, for a user name such as user&1 , the entry in silent.xml would be user&1.

For a silent install embedded quote ( " ) character in service or database password is not supported.

Silent install 35



Next stepsHP SIM is now installed and initialized on the CMS. To browse to HP SIM, use the icon that appears onyour desktop after installation is complete, or start the HP SIM GUI using Internet Explorer or Firefox athttp://localhost:280/.

You will need to configure HP SIM using the First Time Wizard. See Chapter 4 “Configuring HP SIM usingthe First Time Wizard” for details.

See Chapter 13 “Using the graphical user interface” for details.See Chapter 6 “Setting up managed systems” for details about installing and configuring the requiredManagement Agents on the systems that will be managed by the CMS. Next, complete the initial setup ofHP SIM. Initial setup involves adding managed systems , adding users , setting up authorizations , andconfiguring event handling.

See the Service Essentials Remote Support Pack documentation for details about configuring Remote SupportPack.

NOTE: If HP SIM hasn't already been registered, the HP Systems Insight Manager Registration windowand First Time Wizard appear when a user with full configuration rights logs in to HP SIM for the first time.Follow the onscreen instructions to register HP SIM or click the Register Later button to register at anothertime.

NOTE: The First Time Wizard configures only the basic settings of an initial setup for HP SIM. Additionalconfiguration options are available in the HP SIM graphical user interface. See Chapter 5 “ConfiguringHP SIM using the Options menu” or the HP SIM User Guide at http://docs.hp.com/en/index.html for moreinformation.






4 Configuring HP SIM using the First Time Wizard At this point, step 1 below is complete. Perform step 2 to configure HP SIM for your environment by usingFirst Time Wizard or proceed to Chapter 5 “Configuring HP SIM using the Options menu”.

1. Install and configure the CMS. The procedure to complete this step is in Chapter 3 “Installing HP SIMon the Central Management Server (CMS) for the first time”.

2. Configure HP SIM for your environment. The procedure to complete the First Time Wizard is in this

chapter or Chapter 5 “Configuring HP SIM using the Options menu”.3. Install and configure the required management software on the systems that will be managed by the

CMS. For more information on this step, see Chapter 6 “Setting up managed systems” for details.


The initial setup of HP SIM uses the First Time Wizard to provide step-by-step instructions for performing theinitial configuration of HP SIM Central Management Server as well as steps for setting up managed systems ,configuring discovery , configuring event handling, adding users , and defining authorizations . To performthe initial setup, you must complete the installation of your Central Management Server (CMS) as describedin an earlier chapter.

NOTE: All the information in this section is also available in the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html.

First Time WizardThe First Time Wizard starts the first time a full configuration rights user signs in to HP Systems Insight Manager(HP SIM). The administrative account used to install HP SIM is the initial full configuration rights account. Ifthe wizard is canceled before completion, it restarts each time a user with full configuration rights signs in.You can cancel and disable the wizard from starting automatically by selecting the Do not automatically

show this wizard again checkbox and clicking Cancel. The wizard can be started manually by selectingOptions→First Time Wizard.

The First Time Wizard provides step-by-step instructions for performing the initial configuration of HP SIM. Additional configuration options are available in the HP SIM graphical user interface (GUI).

The First Time Wizard helps you configure the following settings on the Central Management Server (CMS). After configuring a setting, click Next to continue the First Time Wizard setup procedure.

NOTE: The default settings in Firefox block the First Time Wizard. You must disable the pop up blocker inFirefox to see the First Time Wizard.

NOTE: The selections you make in the First Time Wizard are not applied until you click Finish on thesummary page.

NOTE: For more detailed information on each item below, see the detailed information later in the chapter.

1. Web-Based Enterprise Management (WBEM) . Enter the default WBEM user names and passwords.This information is used to discover systems that use the WBEM management protocol .

2. SNMP . Enter the read community strings to use for all newly discovered systems. Community stringsset up the authentication that enables communication between HP SIM and a managed system. Thisinformation is used to discover systems that use the SNMP management protocol.

See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more information about WBEM and SNMP.

3. Automatic discovery. Use the wizard to enable discovery, set up the discovery schedule, and enter theIP address ranges that include the systems you want to discover. Discovery is the process HP SIM usesto find and identify the systems on your network and populate the database with information. A systemmust be discovered to collect data and track system health status .

4. User settings. Add the operating system user accounts that will be used to sign in to HP SIM. Theseaccounts associate a user account with privilege levels in HP SIM.

First Time Wizard 37









5. E-mail settings. Enter the e-mail settings the CMS will use to send e-mail notifications. You can set up Automatic Event Handling tasks that cause HP SIM to send e-mails when the CMS receives a specificevent.

6. Automatic Event Handling. Define a task that will cause the CMS to send e-mail notifications based onthe selected event criteria or event collection.

NOTE: The First Time Wizard configures only the basic settings of HP SIM.

Entering WBEM settingsHP Systems Insight Manager (HP SIM) uses the Web-Based Enterprise Management (WBEM) protocol tocommunicate with managed systems . You can enter WBEM settings in the First Time Wizard or in the HPSIM menu bar. (GUI) To disable WBEM communication or enter settings in the GUI, select Options→Protocol

Settings→Global Protocol Settings.

If you do not have WBEM systems in your network, you do not need to enter information here. If you have WBEM systems and you do not enter the user names and passwords for these systems, HP SIM will notdiscover them.

NOTE: See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more information on fine tuning protocol settings for asingle system or a group of similar systems.

1. In the User Name, Password, and Confirm Password fields, enter as many default user names andpasswords as needed. These defaults apply to all newly discovered systems.

Note: HP recommends limiting the WBEM user name and password pairs to 10 to reduce the overalldiscovery run time. To add more than 10 WBEM user name and password pairs, run mxnodesecurity-a -p wbem -c username :password for each additional set. You can also create an XML file thatdefines your system authorizations prior to running discovery.

If your network includes storage systems , enter the user name and password of each SMI CIMOM inthis section. For example, if you have an HP HBA (Emulex OEM) for Windows, enter the user namecimadmin and password pwd580. See your storage system's SMI-S provider documentation forinformation about the SMI CIMOM username and password.

The system identification process attempts each user name and password pair until a successful responseis obtained. Future WBEM requests to a system use the user name and password that succeeded. For Windows-based systems, the user name must include the domain name, for example,domainname\username .

Note: Enter the name and password pairs such that root and administrator passwords are listed firstand user and guest passwords are listed second. This order minimizes the search time.

2. Click Next to go to the next First Time Wizard step.

Note: The users used for WBEM access do not need to be configured to sign in.

Entering SNMP settingsHP Systems Insight Manager (HP SIM) uses the SNMP to communicate with managed systems . Community

strings set up the authentication that enables communication between HP SIM and a managed system. Youcan enter read community strings in the First Time Wizard, or in the HP SIM menu bar. (GUI). To disableSNMP communication, enter community strings, or control other SNMP settings not available in the wizard,select Options→Protocol Settings→Global Protocol Settings.

If you do not have SNMP systems in your network, you do not need to enter information here. If you haveSNMP systems and you do not enter read community strings that match these systems, HP SIM will notdiscover them.

38 Configuring HP SIM using the First Time Wizard







NOTE: See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for information on fine tuning protocol settings for a singlesystem or a group of similar systems.

1. In the Read community string fields, enter up to four read community strings. Community strings arecase-sensitive and apply to all newly discovered systems.

The identification process attempts communication to a system, using each read community in successionuntil a successful response is obtained. Future SNMP requests use the community string that provideda successful response.


Enabling system automatic discoveryHP Systems Insight Manager (HP SIM) uses automatic discovery to find and identify systems on the network.The System Automatic Discovery task is the default discovery task and is disabled by default. You can enableand configure the System Automatic Discovery task in the First Time Wizard, or by selectingOptions→Discovery.

If the System Automatic Discovery task is enabled, it will run immediately at the conclusion of this wizard toinitially populate the HP SIM database.

You can create additional automatic discovery tasks by selecting Options→

Discovery and entering thedetails, and you can run manual discovery to discover single systems.

1. To enable the System Automatic Discovery task, select the Automatically execute discovery every

checkbox. If you do not enable the System Automatic Discovery task at this time, discovery will not takeplace until you select Options→Discovery, and enable a discovery task or select a task and click Run

Now.

2. If you want System Automatic Discovery to run on a regular schedule, enter the periodic run intervaland time of day to run the task.

3. In the Ping inclusion ranges, templates and/or hosts files field, enter the IP addresses to includefor pinging. For example, if your local subnet IP ranges from 1 to 254, the default Ping inclusion ranges,enter 172.25.76.1-172.25.76.254.

To discover SMI-S storage systems , you must add the IP address of each SMI CIMOM to the System

Automatic Discovery task. Alternatively, you can create a separate discovery task for your SMI CIMOMs. See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more information.


Adding users to the Central Management ServerIn HP Systems Insight Manager (HP SIM), user administration involves adding, editing, and removing users.You can configure users in the First Time Wizard or by selecting Options→Security→Users and

Authorizations. Additional configuration options such as user groups and reports are available in thegraphical user interface (GUI). See HP Systems Insight Manager 5.1 User Guide at http://

h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more information.

Creating users1. Click New. The New User section appears.

2. In the Login name [on central management server (CMS)] field, enter the operating system loginaccount name used to sign in to HP SIM. This information is required.

Note: The user cannot sign in to HP SIM if the account is not a valid login. The account is not validateduntil the user tries to sign in to HP SIM.

3. In the Domain (Windows domain for login name) field, enter the Windows domain name for thelogin name if the CMS is running a Windows operating system. If left blank, the system name of theCMS is used as the domain.

4. (Optional) Enter the user's full name, phone number, and e-mail address in the appropriate boxes.

Enabling system automatic discovery 39















5. In the Copy all authorizations of this user or [template] field, select a template or user that has theauthorizations you want to assign to the sign in account that you are creating. The following predefinedtemplates are available:

• Administrator This template automatically gives the user full configuration rights on the CMSand includes the All Tools toolbox for the CMS and for All Managed Systems.

• Operator This template gives the user limited configuration rights on the CMS and includesauthorizations for the Monitor Tools toolbox on the CMS and the All Tools toolbox on All

Managed Systems.

• User This template gives the user no configuration rights on the CMS and includes authorizationsfor the Monitor Tools toolbox for the CMS and All Managed Systems.

If you do not want to select an existing user or template, select None.

6. In the Central management server configuration rights section, select the level of authority to assignto the new user from the following options. This is a required setting. If you selected an existing user ortemplate in the previous step, this information is already entered for you.

• Full configuration rights. Enables total user control of the database . Users can run discovery ofsystems and data collection ; define users and authorizations; set Cluster Monitor configuration;configure licensing and protocol settings; and create, modify, delete, and run reports, snapshotcomparisons, tools, custom tools, events, automation tasks, and so on.

• Limited configuration rights. Enables the user to create, edit, and delete reports (including predefinedreports).

• No configuration rights. Enables the user to view and run predefined reports on systems they havebeen authorized to view only. A user without configuration rights cannot execute any actions toaffect the system database .

7. Click OK to save and close the New User section, or click Apply to save this user and enter more users.

8. When you are finished entering users, click Next to go to the next First Time Wizard step.

Editing users1. Select a user and click Edit. The Edit User section appears.

2. Make changes to the user information, and click OK.

Deleting users1. Select a user and click Delete. HP SIM prompts you to confirm the deletion.

2. Click OK.

Configuring e-mail settingsTo configure HP SIM to send e-mail notifications through automatic event handling:

1. Access the Simple Mail Transfer Protocol (SMTP) host and CMS e-mail settings through the First Time Wizard or choose Options→Events→Automatic Event Handling→Email Settings. The Email

Settings page appears.

2. Enter the SMTP host name. The SMTP host is the outgoing e-mail server that the CMS will use to sende-mail notifications.

3. Enter the e-mail address that the management server will use when sending e-mail notifications in theSender's e-mail address box.

4. To authenticate your SMTP server, select Server Requires Authentication.

5. Enter the account user name and password in the corresponding boxes.

6. If you are using the First Time Wizard, click Next to go to the next step.

Note If you did not enter a valid SMTP host, HP SIM notifies you that it will not be able to send e-mailnotifications. Click OK, if you do not want to enter e-mail settings now, or click Cancel and enter avalid SMTP host.

If you are changing the e-mail settings from the Options→Events→Automatic Event Handling→Email

Settings page, click OK to save changes.

40 Configuring HP SIM using the First Time Wizard



Configuring automatic event handling Automatic event handling enables HP Systems Insight Manager (HP SIM) to perform an action when a specificevent occurs. The First Time Wizard lets you define one task, based on an existing event collection, that willsend an e-mail notification when an event matching the event collection attributes occurs. For example, youcan configure HP SIM to send an e-mail to the system administrator whenever a failed login event occurs.Perform the following procedure to define a task in the First Time Wizard. The name of this Automatic Eventtask is the System Event Handler task.

NOTE: If this task is already defined, the task information is displayed but there are no editing capabilitiesfor this task in the First Time Wizard. To edit the System Event Handler task, you must selectOptions→Events→Automatic Event Handling→Manage Tasks.

Additional options for defning event handling tasks are available when you selectOptions→Events→Automatic Event Handling. You can configure HP SIM to send a page, run a customtool, assign an event, forward an event as an SNMP trap, write the event to the system log, or clear anevent. See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more information.

Complete the following procedure to define the System Event Handler task. If you do not want to define atask, click Next to skip this step.

1. In the Event Collection box, select the event collection from the dropdown list.

Click View Definition to see a description of the selected criteria.

2. Ensure that the Send e-mail box is selected. Enter the following information:

▲ In the To field, enter the list of e-mail addresses that should receive the notification, separatingeach entry with a comma.

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

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 encoding preferenceof 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 a pagermessage is sent to the recipients

• HTML. An e-mail message in HTML format that is sent to the recipients

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)

3. Click Next to save your settings and view a summary of the selections you made in the First Time Wizard.

First Time Wizard summary When you are finished entering information in the HP Systems Insight Manager (HP SIM) First Time Wizard,review your selections on the Summary Page, and click Finish to save them.

If you enabled Automatic Discovery, discovery runs when you exit the First Time Wizard. If you did notenable Automatic Discovery, discovery will not take place until you select Options→Discovery, and enablea discovery task or select a task and click Run Now.

Configuring automatic event handling 41







5 Configuring HP SIM using the Options menuPerform step 2 to configure HP SIM for your environment or you can use First Time Wizard inChapter 4 “Configuring HP SIM using the First Time Wizard”.


2. Configure HP SIM for your environment. The procedure to complete this step is in this chapter or you

can use the First Time Wizard in Chapter 4 “Configuring HP SIM using the First Time Wizard” to performthe initial configuration of HP SIM.

3. Install and configure the required management software on the systems that will be managed by theCMS. For more information on this step, see Chapter 6 “Setting up managed systems” for details.


This chapter provides you with more configuration options then if you use First Time Wizard. The followingthings need to be done to configure the protocols for the managed systems.

1. Configure protocol settings

2. Add users

3. Add toolboxes

4. Add authorizations5. Configure email settings

6. Set up automatic event handling

7. Configure and execute discovery

NOTE: If you use these option menus to configure HP SIM make sure you run discovery to discover all ofthe systems that you will be managing.

Configuring protocol settingsConfiguring the protocol settings defines how HP SIM communicates with the managed systems.

To configure the protocol settings:

1. Select Options→Protocol Settings→Global Protocol Settings. The Global Protocol Settings

page appears.

2. In the Default ping settings section, select Use the Internet Control Message Protocol (ICMP) for

system reachability (ping) check or Use the TCP protocol for system reachability (ping) check

port number 80. The Use the ICMP protocol for system reachability (ping) check option is thedefault and recommended setting.

Select Use the TCP protocol for system reachable (ping) check. port number 80 if your companyhas disabled ICMP on the corporate network or the corporate policy mandates system firewall softwareto filter out ICMP requests. For example, Windows XP has this feature built in and can result in systemsnot being automatically discovered. This option enables you to run HP SIM and ping all availablesystems.

Note: This option only applies to IP-based systems and is available for global, system-wide settings thatare used when managing all systems in HP SIM. It is used by automatic discovery, hardware statuspolling, the ping tool, and any other tool that must verify system availability. This option is not availableon a single-system basis.

Note: If you select Use the TCP protocol for system reachable (ping) check. port number 80 ,even though HP SIM attempts a connection request to the current system, that system does not need anyadditional software running on it for this option to work. For example, HP does not require that a webserver be running on port 80. Some networking systems might not respond to the TCP request, whichis typically seen in low-end networking equipment. Manual additions can be made if it is necessary.However, this system displays as Critical if hardware status polling is run.

Note: If you need to use a port other than port 80, you can change the NodeReachableTcpPort propertyin the globalsettings.props file located in C:\Program Files\HP\Systems Insight

Configuring protocol settings 42



Manager\config\globalsettings.props for Windows and in/etc/opt/mx/config/globalsettings.props for HP-UX and Linux.

3. Set the Default timeout and the Default retries. If some systems are managed over a WAN or satellitelink, use a larger time-out (for example, five seconds) with at least one retry. For a LAN, a shorter timeout can be used. This setting can be configured on a single-system basis.

4. In the Default WBEM settings section, select Enable WBEM to allow Web-Based Enterprise Management (WBEM) requests to be sent. Enabled is the default setting. Enter as many default usernames and passwords as needed. If your network includes storage systems , enter the user name and

password of each SMI CIMOM in this section. The identification process attempts each of these username and password 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 name shouldinclude the domain name, for example, domainname\username .

Note: If you have WBEM systems and no user name and password pairs are entered, the systems willnot be discovered.

Note: Order the name and password pairs such that root and administrator passwords are listed firstand user and guest passwords are listed second. This order minimizes the search time.

Note: HP recommends limiting the WBEM user name and password pairs to 10 to reduce the overalldiscovery run time. To add more than 10 WBEM user name and password pairs, run mxnodesecurity-a -p wbem -c username :password for each additional set. You can also create an XML file thatdefines your system authorizations prior to running discovery.

Note: OpenWBEM is not supported.

5. In the Default HTTP settings section, select Enable HTTP and HTTPS if it is necessary to allowweb-based agents and other HTTP port scans to be identified. HP recommends leaving this optionenabled for proper management and discovery of systems.

6. In the Default SNMP settings section, select Enable SNMP, which is the system default, and set theDefault time out and Default retries. If some systems are managed over a WAN or satellite link, usea larger time-out (for example, five seconds) with at least one retry. For a LAN, a shorter time out canbe used. These settings can also be configured on a single-system basis.

7. (Optional) Enter the Default write community string. This value is case-sensitive. Only a few toolsneed this option set. Community strings are case-sensitive.

Note: The Write community string is optional and is only required for firmware updates on a GbEswitch. If you need to update the GbE switch firmware, you must first set the write community string fromthis page and then run the existing switch update task. Do not set this feature if the network is not trusted.

8. Enter the Read community string. This value is case-sensitive. Enter as many as needed. Theidentification process attempts communication to the system, using each of these communities in successionuntil a successful response is obtained. Future SNMP requests then use the community string that provideda successful response.

Note: If you have SNMP systems and no read community string that match the systems are entered, thesystems will not be discovered.

9. (Optional) In the Default DMI settings section, select Enable DMI, to enable Desktop Management Interface (DMI) identification to run on systems. DMI is used to manage some older desktops, HP-UX11.0 servers, and some third-party servers. If you do not need to manage these kinds 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 product name,re-enable DMI.

10. Click OK to accept the settings.

Configuring protocol settings 43



Users and authorizations

NOTE: Users that have been added to the Central Management Server (CMS) cannot view or managesystems until authorizations have been configured for them.

NOTE: HP-UX and Linux-provided command line tools, such as ls and df, are run as root by default. Forsecurity reasons, you might want them to run as a specific user to avoid permitting unintended capabilitiesto a user.

HP Systems Insight Manager (HP SIM) enables you to configure authorizations for specific users or usergroups. Authorizations give the user access to view and manage systems. Each authorization specifies auser or user group, a toolbox, and a system or system group. The specific set of tools that can be run againsta system is specified in the assigned toolbox.

It is important that you plan which systems each user is going to manage and which specific set of tools theusers are authorized to execute against the managed systems. A user with no toolbox authorizations on asystem cannot view or manage that system.

Authorizations are additive. If a user is authorized on Toolbox1 on a system and is also authorized forToolbox2 on the same system, the user is authorized for all tools in both Toolbox1 and Toolbox2 on thatsystem. Similarly, a user authorized for the All Tools toolbox needs no other toolbox authorization on thatsystem because the All Tools toolbox always includes all tools.

Adding usersCreate a new user account to sign in to HP Systems Insight Manager (HP SIM). The account must be validon the operating system (includes Active Directory on Windows) on the Central Management Server (CMS)and will be authenticated by the CMS. You must know the operating system user account name of the useryou are adding, but you do not need to know the password.

To create a new user:

1. Select Options→Security→Users and Authorizations→Users, and click New. The New User

section appears.

2. In the Login name (on central management server) field, enter the operating system login accountname to be used to sign in to HP SIM. This field is required.

Note: The user cannot sign in to HP SIM if the account is not a valid login. The account is not validateduntil the user tries to sign in to HP SIM.

3. In the Domain (Windows domain for login name) field, enter the Windows domain name for thelogin name if the CMS is running a Windows operating system. If left blank, the system name of theCMS is used as the domain.

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

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

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

7. In the Copy all authorizations of this user or [template] field, select a template or login that alreadyhas the predefined authorizations that you want to assign to the login account you are creating.

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




9. Under the Login IP Address Restrictions section, in the Inclusion ranges field, enter the IP addressesof the systems that you want this user to be able to use as a client browsing into this CMS. If you list

44 Configuring HP SIM using the Options menu



multiple IP addresses, separate them with a semicolon (;). Each range is a single IP address or two IPaddresses separated by a dash (-). The IP addresses must be entered in the standard dotted decimalnotation, for example, 15.1.54.133. Any spaces surrounding the semicolons or dashes are ignored.Spaces are not allowed within a single IP address in the dotted decimal notation. Enter 0.0.0.0 toprevent a user from logging in through a remote system.

Important: If browsing from the CMS, ensure all IP addresses of the CMS are properly included. Ifbrowsing to localhost, ensure the loopback address 127.0.0.1 is also included.

10. (Optional) In the Exclusion ranges field, enter the IP address of the systems that should be excluded

from this user as clients browsing into this CMS. Use the same format in the previous step for Inclusionranges.

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

11. Under the Pager Information section, in the Phone field, enter the pager phone number of the userassociated with this user account if you are using a Windows operating system. If the Phone field isleft 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 paging message fromthe 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 dropdown list.

16. Click OK to save and close the New User section. The new user account is created. Click Apply tosave and keep the New User section open, or click Cancel to cancel the creation of this user.

Adding user groups

User groups must exist in the operating system. For Windows, they must also exist in Active Directory.Members of the user groups in the operating system can sign in to HP Systems Insight Manager (HP SIM)and inherit the group's attributes for configuration rights, login IP address restrictions, and authorizations. When a group's configuration rights, login IP address restrictions, or authorizations are changed, this changeis immediately reflected in all current members of the group.

To create a new user group:

1. Select Options→Security→Users and Authorizations→Users, and click New Group. The New

User Group section appears.2. In the Group name (on central management server) field, enter the operating system group nameto be used for signing in to HP SIM. This field is required.

3. In the Domain (Windows domain for login name) field, enter the Windows domain name for thegroup if the Central Management Server (CMS) is running a Windows operating system.

4. In the Full name field, enter the full name for the group. This name appears in the table on the Users

tab.

5. In Copy all authorizations of this user or [template] dropdown list, select a template or login thatalready has the predefined authorizations that you want to assign to the group you are creating.

6. In the Central management server configuration rights section, select the level of authority to assignto the new user group from the following options. Users that sign in to HP SIM as members of this groupinherit these configuration rights.




7. Under the Login IP Address Restrictions section, in the Inclusion ranges field, enter the IP addressesof the systems that you want members of this user group to be able to use as a client browsing into this

CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP

Users and authorizations 45



address or two IP addresses separated by a dash (-). The IP addresses must be entered in the standarddotted decimal notation, for example, 15.1.54.133. Any spaces surrounding the semicolons or dashesare ignored. Spaces are not allowed within a single IP address in dotted decimal notation. Enter 0.0.0.0to prevent a user from logging in through a remote system.

Important: If browsing from the CMS, ensure all IP addresses of the CMS are properly included. Ifbrowsing to localhost, ensure the loopback address 127.0.0.1 is also included.

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

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

9. Click OK to save and close the New User Group section. Click Apply to save and keep the New User

Group section open, or click Cancel to cancel to close the New User Group section without savingthe new group.

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

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.

4. Select Toolbox is enabled to enable the toolbox and all authorizations created with this toolbox.

5. In the Show tools in category field, select the category to display a list of tools in the available toolslist. 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 in the Toolbox

contents list, and click << to remove it from the assigned tools list.

Note: For limited and no configuration rights users to clear, delete, assign events, and add commentsto events, you must select Configuration Tool from the Show tools in category dropdown list. Then,select Clear Events, Delete Events, Assign Events, and Comment Events as necessary and click>> to add them to the Toolbox contents.

6. Click OK to save the new toolbox and close the New Toolbox section. Click Apply to save the settingswithout closing the New Toolbox section, or click Cancel to cancel the new toolbox creation and returnto the Toolboxes section.

Adding authorizations Authorize 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 click New. TheNew Authorizations section appears.

2. In the Select dropdown list, select User(s) or UserGroup(s), and select the users or groups in the box.

This field is required.3. In the Enter authorizations for the selected user(s) section, select one of the following options:

• 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 to include.




b. In the Select Systems list box, the two default system groups are displayed. Select one ofthese groups or click Add to display the Add Systems section to select systems for theauthorization.

1. Click the down arrow in the Add targets by selecting from dropdown list, and selecta collection.

2. If you want to use the entire collection as your selection, select Select "collection name"

itself . This option creates a system group based on the currently displayed contents of

the collection.• (Optional) Select Automatically track changes. If this collection changes, so

does the authorization to enable the authorization to automatically be updatedwhen a collection is changed without user intervention.

• (Optional) Select Do not track changes. If this collection changes, the

authorization will not change. If this option is selected, you must manually updatethe authorization after a collection has changed by using the Update button onthe Authorizations tab.

Note: These two selections are only available if a collection of systems is selectedand the Select "collection name" itself option is selected. You must select oneoption or the other. The default selection is based on the

DynamicAuthorizations_AutoUpdateDefaultValue property setting in theglobalsettings.props file. The default is set to yes. This is reflected in theSelect Systems list box in the New Authorizations section with [Auto] appendedto the entry. For example, if you selected All Systems and chose to have itautomatically updated, All Systems 001 [Auto] would be displayed in the Select

Systems box.

You can continue to add systems and collections and can enable automatic updatesfor each selected collection. Since automatic updates for any authorization applyto all authorizations using the same selected collection, changing the setting forone affects any other authorization using the same collection. Therefore, duringsystem selections, if you select a group already associated with an automaticallyupdating authorization, the "Automatically track changes. If this collection

changes, so does the authorization" option is preselected. Likewise, if a non




automatically updating authorization is associated with a collection, the "Do not

track changes. If this collection changes, the authorization will not change"

option is preselected.

3. If you want to select all individual systems from the collection, select the checkbox at thetop of the table view in the column heading to select all systems.

Note: This action creates a separate authorization for each selected system.

4. If you want to select individual systems from the collection, select the systems from thetable view.

Note: This action creates a separate authorization for each selected system.

5. Click Apply to save system selections, or click Cancel to return to the New

Authorizations section without saving changes.

After clicking Apply, a message appears based on the options selections. Click OK toreturn to the New Authorizations section.

Note: A system group is a group of systems based on a system collection and used forauthorizations. It is a static snapshot of the contents of the collection at the time the systemgroup was created. There are two default system groups that are not based on collections.The All Managed Systems system group contains every managed system, except the Central Management Server (CMS). The CMS is excluded so that users are not mistakenly assigned

the authorization to manage the CMS system itself. There is a CMS group created explicitlyfor the CMS. These default system groups cannot be edited, updated, or deleted.

If you selected individual systems of a collection, each selection populates the list box and isselected for inclusion in the authorization. If you selected a collection and the collection hasbeen used previously in an authorization, a message appears stating that a system group forthe collection exists and will be updated with current source collection content. This conditionaffects all authorizations associated with that collection. When a collection is used for thefirst time, no message appears. A system group with the name of the collection followed bythree numbers, usually 001, is displayed in the Select Systems dropdown list and is selected.

c. Click OK to save the new authorization and close the New Authorizations section, or, ifyou do not want to save changes, click Cancel to cancel the creating process.

Configuring email settingsConfiguring email settings enables users to send email notification of certain events.

To configure email settings:

1. Access the Simple Mail Transfer Protocol (SMTP) host and CMS e-mail settings through the First Time Wizard or choose Options→Events→Automatic Event Handling→Email Settings. The Email

Settings page appears.

2. Enter the SMTP host name. The SMTP host is the outgoing e-mail server that the CMS will use to sende-mail notifications.

3. Enter the e-mail address that the management server will use when sending e-mail notifications in theSender's e-mail address box.

4. To authenticate your SMTP server, select Server Requires Authentication.5. Enter the account user name and password in the corresponding boxes.

6. If you are using the First Time Wizard, click Next to go to the next step.

Note If you did not enter a valid SMTP host, HP SIM notifies you that it will not be able to send e-mailnotifications. Click OK, if you do not want to enter e-mail settings now, or click Cancel and enter avalid SMTP host.

If you are changing the e-mail settings from the Options→Events→Automatic Event Handling→Email

Settings page, 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 Modem Settings

page appears.

2. From the COM port field, select the appropriate COM port. See your modem documentation for details.

3. Click OK to save the setting.

Setting up automatic event handling Automatic event handling enables you to define an action that HP SIM performs when an event is received.

To set up automatic event handling:

1. Select Options→Events→Automatic Event Handling→New Task. The Automatic Event Handling

- New Task page appears.

2. Enter a name in the Task name field, or accept the default, and click Next. The Select event collection

page appears.

3. Select one of the following:

a. Use this event collection

i. Select an event collection from the dropdown list.

Note: Select an event collection. The event collection is a collection that is defined by eventattributes. The event collection might be a combination collection containing system information.If the collection contains system information, step iii will not appear. If you select an eventcollection that contains additional event collections, you will receive an error message.

ii. (Optional) Click View Definition to view the attributes that define the event collection.

Note: This field is displayed if you selected an existing private or shared event collection. Ifthe collection was created using the Automatic Event Handling feature that enables you toselect event and system information, this will not be displayed.

iii. Click Next. The Select system collection page appears. If the event collection containssystem information, the select system collection process will not be displayed. Instead, theSelect actions page will appear.

b. Use event attributes that I will specify

i. Click Next. The Select events page appears.

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

c. Click Next. The Select system collection page appears.

4. Select one of the following options:

a. Use this system collection

i. From the dropdown list, select a system collection.

ii. Click View Definition to view the system attributes or the members of the system collectionthat is selected.

iii. Click Next. The Select action page appears.

b. Use system attributes that I will specify

i. Click Next. The Select systems page appears.

ii. Select system 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.

iii. Click Next. The Select actions page appears.




5. Select from the following options:

• Send page (Windows only)

Add users to be paged from the dropdown list of users by clicking >>. Click << to remove selectedusers from the list of users to be paged. The pager number for an HP Systems Insight Manager (HPSIM) user is set on the Users and Authorizations page. If a user name in the Users list is inactive,the pager information for the user has not been configured. You can add the user to the list ofusers to be paged, but pager messages are not sent to this user until the pager information isprovided.

• Send e-mail

In the To field, enter the list of e-mail addresses that should receive the notification, separatingeach entry with a comma.

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

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 encoding preferenceof 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 a pager

message is sent to the recipients.• HTML. An e-mail message that looks like the HTML Event Details page is sent to the

recipients.

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 tool

Select a custom tool from the Name dropdown list. custom tools are created under theTools→Custom Tools→New Custom Tool option, and select CMS tool.

• Assign

Enter the name of the person to whom to assign the task. The event is assigned to this user whenreceived. Setting this field allows you to do searches assigned to this person.

• Forward as SNMP trap

Enter a system name or IP address in the Name or IP field, and click >> to add it to the Trap

recipients box.

Click Delete if you want to delete a recipient after selecting the name in the Trap recipients 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 Application Log,and the Source column of the Event Log is listed as HP SIM for the logged event. On Linux andHP-UX systems, the event details are logged to the system 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

Received events are cleared based on the criteria selected when task executes.

6. After you have made your selections, click Next. The Select time filter page appears.




7. Select the Use time filter checkbox if you want to use time filters, and select an option from the dropdownlist.

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

b. Select the View time filter checkbox. A time filter window appears, showing the times selected.

If the Use time filter checkbox is not selected, actions are triggered whenever the events matchingthe selected criteria are received.

If the Use time filter checkbox is selected, actions are triggered only when they occur during thedays and times specified by the selected time filter.

c. When you have entered the information, click Next to continue with the next step. The Review

summary page appears. The Task name, the events, system criteria, and Action(s) informationare displayed. If a paging or e -mail option was selected, the modem and e-mail settings aredisplayed, along with buttons to change the settings.

8. (Optional) Click Edit modem settings to edit the modem settings, or click Edit email Settings to editthe SMTP settings.

Note: The event and system search criteria appear at the bottom of the page. This information can beextremely complex and long. Therefore, you might need to scroll down to view all of the criteria.

9. Click Finish to create the new task.

Configuring and executing discovery

Discovery is the process that HP SIM uses to find and identify the systems on your network and populate thedatabase with that information. A system must first be discovered to collect data and track system status.There are two basic ways to discover new systems:

• Automatic discovery The process that HP SIM uses to find and identify the systems on your networkto populate the database with that information. A system must first be discovered to collect data andtrack system status.

• Manual discovery The process that enables you to bypass a full automatic discovery and add singleand multiple systems to the database, create or import the HP SIM database Hosts file, and create orimport a generic Hosts file.

Configuring and executing automatic discovery

1. Select Options→Discovery. The Discovery page appears with the Automatic tab selected.

2. In the For all automatic discoveries section, select Configure general settings. The General

Settings section appears.

3. Select from the following options:

• Automatically discover a system when an event is received from it. This option enablessystems to be discovered when a trap or some other supported event is received by HP SystemsInsight Manager (HP SIM). It uses the discovery filters and IP address exclusion ranges for additionalfiltering of these events.

• Automatically discover a server blade when its Integrated Lights Out management

processor is identified. This option adds servers that were indirectly discovered through itsmanagement processor. These servers are discovered when its iLO is discovered, they are listedwith a Disabled state on the system table view page, and the only information displayed is thesystem serial number and the association to iLO and the enclosure. If the iLO is in a c-Classenclosure, then the Discover systems in an enclosure when Onboard Administrator is

discovered option should also be enabled.

• Select Discover systems in an enclosure when Onboard Administrator is discovered. Thisoption adds systems known by the Onboard Administrator even if they are not in the configuredDiscovery range.

• Select Automatically discover HPVM guest(s) when the host is identified. This option addsall HP Integrity Virtual Machine (HPVM) guest systems to the HP SIM database when the HPVMhost system is discovered and identified.




4. (Optional) In the Ping exclusion ranges, templates and/or hosts files field, specify the IP addresses,templates, or Hosts files containing IP addresses to exclude from the automatic discovery process. Thisfield applies to both range pinging and event-based automatic discovery.

Important: When discovering clusters, the ping inclusion range must include the IP addresses of thecluster and the cluster members.

5. (Optional) Select Enable discovery filters.

6. In the Discover the following system types: section, select the type of systems to be discovered.

Important: When discovering clusters, you must include the server system type, so that the cluster membersare not filtered out.

Note: This option is available only when you select Enable discovery filters.

7. In the Limit discovery to systems that meet the following criteria section, select from the following:

• Any system that matches the above filter

• All manageable systems (WBEM, SNMP, DMI, WMI, or HTTP support)

• Manageable systems with HP agents only

Note: This option is available only when you select Enable discovery filters.

8. Click OK to save settings, or click Cancel to close the General Settings section without saving changes.

If you click OK when discovery filters are enabled but have not selected any system types, the following

error message appears:You must make at least one system type selection when enabling filters.

9. Select System Automatic Discovery. Click one of the following options to schedule it for ongoingoperations or to make other changes: Edit, Enable or Run Now. If you would like to create otherdiscovery tasks, click New.

Configuring and executing manual discovery

1. Select Options→Discovery, and click the Manual tab. The System Information section appears.

2. Enter the system name or IP address.

3. Click Add System to add the system to the database. If you have not entered the Simple NetworkManagement Protocol (SNMP) or Web-Based Enterprise Management (WBEM) credentials for this

system previously, click More Settings. Enter the credentials, then click Add System. Or click MoreSettings to enter the following information:




• Specify additional system properties to use only if Identification fails on this system.Includes:

• System type

Click the down arrow and select the appropriate System type.

• System subtype

Click the down arrow and select the appropriate System subtype. You can provide up to eightdifferent system subtypes.

• Product model

This is a free form field and you can enter the system model number here.

• WBEM Settings• User name

• Password

If you do not want to use the default global values for the WBEM user name and password,select Use Custom and enter custom values.

If you are manually discovering a storage system , ensure that the user name and passwordof the SMI CIMOM are present in the global protocol settings, or enter them here as customvalues. Select Options→Protocol Settings→Global Protocol Settings to view the globalsettings.

For Windows-based systems, the user name should include the domain name, for example,domainname\username.

Note: OpenWBEM is not supported.

• SNMP Settings

If you do not want to use the default global values for the SNMP settings, select Use Custom,and enter custom values.

• Timeout (in seconds)

The amount of time HP SIM waits for an SNMP response when it sends a request to thesystem. If a response is not received within the time interval, HP SIM might determinethat the system does not support SNMP. Decreasing this value can result in increasednetwork traffic because the rate of retry attempts is increased. Use caution when changing




this value. A value of three seconds usually works for a LAN. However, If systems areconnected through a WAN, try a higher value, for example, 10 seconds.

• Retries

The number of additional times after the first attempt is made to communicate with asystem before attempts stop.

• Read-only community string and Write community string

Note: The Write community string is optional and is only required for firmware updates

on a GbE switch. If you need to update the GbE switch firmware, you must first set thewrite community string from this page and then run the existing switch update task. Donot set this feature if the network is not trusted.

A community string sets up authentication that enables or prohibits communicationbetween the managed system and the Central Management Server (CMS). The communitystring of the CMS must match the community string of the managed system. Use theread-only community string to read variables. Use the write community string to modifyvariables. Although only one community is valid for a communication attempt, a systemcan belong to multiple communities. However, HP SIM only uses one community stringwhen communicating with a system.




6 Setting up managed systems At this point, steps 1 and 2 below are complete. Perform step 3 to install and configure the requiredmanagement software.


2. Configure HP SIM for your environment. See Chapter 4 “Configuring HP SIM using the First Time

Wizard” or Chapter 5 “Configuring HP SIM using the Options menu” for the recommended tasks.Important: Discovery must be run before setting up managed systems. Configuring Automatic Discoveryis part of the First Time Wizard.

3. Install and configure the required management software on the systems that will be managed by theCMS. The procedure to complete this step is in this chapter.

4. Configure the remaining protocols for the managed systems. See Chapter 7 “Configuring managedsystems”" for details.

Setting up managed systems involves installing the required management software. The management softwarebeing installed depends on the type of managed system.

• HP-UX see the HP SIM Installation and Configuration guide for HP-UX

• Storage systems (see below)• Windows systems (see below)

• Linux - see the HP SIM Installation and Configuration guide for Linux

Setting up managed systems from a Windows CMSUse the following checklist as a guideline to assist you with setting up managed systems from a WindowsCentral Management Server (CMS):

1. Make sure that HP Systems Insight Manager (HP SIM) is installed on the CMS.

2. Make sure that the First Time Wizard has been completed on the CMS.

Important: Discovery must be run before setting up managed systems. Configuring Automatic Discovery

is part of the First Time Wizard.3. Make sure that managed systems have the HP Version Control Agent (VCA) installed before running

the Configure or Repair Agents feature to configure them.

If the VCA has never been installed on the managed systems, see Installing the HP ProLiant SupportPack on Windows systems for the first time.

If the VCA is already installed on the managed systems, continue to the next step.

4. Configure the managed system software. See Configuring the managed system software using theConfigure or Repair Agents feature from the CMS.

Installing the HP ProLiant Support Pack on Windows systems for the first timeFor Windows systems, install the latest HP ProLiant Support Pack with the preconfigured components to all

managed systems using the HP Systems Insight Manager feature Initial HP ProLiant Support Pack Install. When you are installing the HP ProLiant Support Pack for the first time, the Initial HP ProLiant Support PackInstall process enables you to install a HP ProLiant Support Pack to a Windows system because you do nothave any HP Insight Management Agents, especially HP Version Control Agent, installed. This process alsoconfigures the system to use the trust certificate from HP Systems Insight Manager (HP SIM) and the settingto use the desired HP Version Control Repository Manager. After you have run the Initial HP ProLiant SupportPack Install tool, you can use the Install Software and Firmware tool to update systems.

NOTE: Installing the VCRM is not part of this procedure because it is generally installed during the HP SIMinstallation. If you chose not to install a VCRM during installation, you see the HP Version Control Installation

Setting up managed systems from a Windows CMS 56



Guide at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html formore information about installing and configuring the VCRM.

The Install Software and Firmware feature in HP Systems Insight Manager requires that the HP Version ControlRepository Manager be installed on servers containing a repository.

NOTE: You must have Windows administrator privileges on target systems to install a HP ProLiant SupportPack.

NOTE: The Install Software and Firmware and VCA features are only available after the Initial HP ProLiantSupport Pack Install process has been run.

NOTE: For more information regarding HP ProLiant Support Packs, see the HP ProLiant Support Pack and Deployment Utilities User Guide at http://h18013.www1.hp.com/manage/psp.html.

To install a HP ProLiant Support Pack for the first time:

1. Select Deploy→Deploy Drivers, Firmware and Agents→Initial HP ProLiant Support Pack Install.The Initial ProLiant Support Pack Install page appears.

2. Select the target systems. To add targets, select a group from the dropdown list. The contents of theselected group appear, and you can select the contents as targets or choose the collection itself byselecting Select 'collection name' itself .

3. Click Next.

4. On the Enter Windows login credentials page:a. In the User name field, enter the Windows administrator user name for the target system.

b. In the Password field, enter the administrator password for the Windows user name entered instep a.

c. In the Password (Verify) field, reenter the Windows administrator password exactly as it wasentered in the Password field.

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

Note: This field can be left blank if the system is not part of a domain.

5. Click Next. The Select a Windows Support Pack page appears.

6. Under Select a Version Control Repository, select a source repository system from which to retrievethe catalog.

The following fields display:

• 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 configurea trust relationship, click configure.

Note: This section displays systems that are authorized by the current user name. If the current user isnot authorized to view the systems, a message appears, indicating that the user does not haveauthorization rights on the system.

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

Note: To expand the System Software Baseline to display all contents, click the icon located

in the upper-left corner of the Select a Support Pack to Install section. Click the icon to collapsethe listings.

8. (Optional) Select Install and initialize SSH (Secure Shell) if you want to install and configure OpenSSHon the target systems. This option is disabled by default.

9. (Optional) Select Force downgrade or re-install the same version if you are installing a HP ProLiantSupport Pack that is ealier than or the same as the version currently installed. This option is disabledby default.



http://h18013.www1.hp.com/manage/psp.html

http://h18013.www1.hp.com/manage/psp.html




10. (Optional) If you do not want to reboot after the installation, clear the Reboot systems if necessary

after successful install option, which is selected by default. However, the system must be rebootedfor the new HP ProLiant Support Pack to be available.

58 Setting up managed systems



11. Click Next. The Configure Support Pack page appears.

• The following options display:




• Click Configure System Management Homepage to set up the Support Pack to establisha trust relationship with System Management Homepage when it is installed on target systems.The Welcome to the Configuration Wizard for the HP System Management Homepage

Component page appears.

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

Note: After the trust relationship is established, click Last Update to update the status totrusted.

To configure the System Management Homepage:

a. From the Welcome to the Configuration Wizard for the HP System Management

Homepage Component page, click Next. The Operating Systems Groups pageappears.

b. In the Group Name field, enter the name of an operating system group that you wantto assign (for example, vcadmin ).

c. In the Operating Level field, select the appropriate level for the new group from thedropdown list.

Note: The default Administrators Groups always have administrative access.

d. Click Add to assign the group. The new group appears under the operating systemgroup to which it was assigned.

Note: You can add up to five entries per operating system group.e. Click Next. You can click Save to save your changes up to this point or click Cancel

to discard the changes and close the wizard.

f. Select one of the following options:

• Anonymous Access Anonymous Access is disabled by default. EnablingAnonymous Access allows a user to access the System Management Homepage (SMH) without logging in. Select this option to allow anonymous access.

Caution: HP does not recommend the use of anonymous access.

• Local Access Local Access is disabled by default. Enabling Local Access allowsa user to locally gain access to the System Management Homepage without beingchallenged for authentication, which means that any user with access to the local

console is granted full access if Administrator is selected. If Anonymous isselected, any local user has access limited to unsecured pages without beingchallenged for a user name and password.

Caution: HP does not recommend the use of local access unless your managementserver software enables it.

g. Click Next. You can click Save to save your changes up to this point, or click Cancel

to discard the changes and close the wizard.

h. Select one of the following Trust Mode security options:

• Trust by Certificate Sets the System Management Homepage (SMH) to acceptconfiguration changes only from HP SIM servers with trusted certificates. This moderequires the submitted server to provide authentication by means of certificates.

This mode is the strongest method of security because it requires certificate dataand verifies the digital signature before allowing access. If you do not want toenable any remote configuration changes, leave Trust by Certificate selected,and leave the list of trusted systems empty by avoiding importing any certificates.

NOTE: HP strongly recommends using this option because it is more secure.

To trust by certificate:

1. Select Trust by Certificate, and click Next.

2. In the Certificate Name field, click Browse to select the certificate file. Afterthe certificate file is selected, the certificate data appears on the screen.




3. Click Add. The certificate appears under Certificate Files. You can clickSave to save your changes up to this point or click Cancel to discard thechanges and close the wizard.

4. Click Next. The IP Binding page appears.

• Trust by Name Sets the System Management Homepage to accept certainconfiguration changes only from servers with the HP SIM names designated in theTrust By Name field. The Trust By Name option is easy to configure. For example,you might use the Trust By Name option if you have a secure network with two

separate groups of administrators in two separate divisions. It prevents one groupfrom installing software to the wrong system. This option verifies only the HP SIMserver name submitted.

NOTE: HP strongly recommends using the Trust by Certificate option becausethe other options are less secure.

The server name option must meet the following criteria:

• Each server name must be less than 64 characters.

• The overall length of the server name list is 1,024 characters.

• Special characters should not be included as part of the server name: ~ '

! @ # $ % ^ & * ( ) + = \ ": ' < > ? , | .• Semicolons are used to separate server names.

To trust by name:

1. Select Trust by Name, and click Next.

2. In the Trusted Server Name field, enter the server name to be trusted.

3. Click Add. The trusted system name appears under the Trusted Servers list.You can click Save to save your changes up to this point or click Cancel todiscard the changes and close the wizard.


• Trust All Sets the System Management Homepage to accept certain configurationchanges from any system.

NOTE: HP strongly recommends using the Trust by Certificate option becausethe other options are less secure.

To trust all servers:

1. Select Trust All. You can click Save to save your changes up to this point orclick Cancel to discard the changes and close the wizard.





i. IP Binding specifies from which IP addresses the System Management Homepage (SMH)accepts requests and provides control over which nets and subnets requests are processed.

Administrators can configure the System Management Homepage to only bind toaddresses specified in the IP Binding page. A maximum of five subnet IP addressesand netmasks can be defined.

An IP address on the server is bound if it matches one of the entered IP Binding addressesafter the mask is applied.

NOTE: The System Management Homepage always binds to 127.0.0.1. If IP Bindingis enabled and no subnet/mask pairs are configured, then the System ManagementHomepage is only available to 127.0.0.1. If IP Binding is not enabled, you bind to alladdresses.

To configure IP Binding:

1. Select IP Binding. The IP Binding page appears.

2. Enter the IP address.

3. Enter the netmask.

4. Click Add. The IP binding configuration is saved and appears under the IP Binding

List.

5. Click Next. The IP Restricted Login page appears.

j. The IP Restricted Login enables the System Management Homepage (SMH) to restrictlogin access based on the IP address of a system.

You can set address restriction at installation time or by it can be set by administratorsfrom the IP Restricted Login page

• If an IP address is excluded, it is excluded even if it is also listed in the includedbox.

• If there are IP addresses in the inclusion list, then only those IP addresses are allowedlogin access with the exception of localhost .

• If no IP addresses are in the inclusion list, then login access is allowed to any IPaddresses not in the exclusion list.

To include or exclude IP addresses:1. In the From field, enter the IP addresses to include or exclude. You can enter an IP

address range to be included or excluded by entering a beginning IP address inthe From field and an ending IP address in the To field.

2. From the Type field, select Include or Exclude.

3. Click Add to add the IP address or IP address range to the Inclusion List orExclusion List below.

4. Click Save. The HP System Management Homepage Login page for the SystemManagement Homepage system appears. For more information about SystemManagement Homepage, see the System Management Homepage Online Help athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html.

• Click Configure VCA to set up the VCA in the selected Support Pack.

Note: If the VCA has already been configured, you can omit this step.

To configure the VCA:

a. In the Computer Name field, enter the name of the system where the VCRM is installed.

b. In the Login Account field, enter the login name used to connect to the VCRM on the systemspecified.

Note: Use a login account that has administrative privileges, but do not use the login nameAdministrator .

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








d. Click Save to save your settings. Click Cancel to discard your settings and close the VCA

Setup page.

e. Click Next.

12. Back in HP SIM, click Next to start the HP ProLiant Support Pack download. The Download Support

Pack page appears.

13. After the support pack is downloaded, click Schedule to create a scheduled task for the Initial HPProLiant Support Pack Install to run or click Run Now to run the task immediately.

Configuring the managed system software using the Configure or Repair Agentsfeature from the CMSThe HP Systems Insight Manager Configure or Repair Agents tool is a quick and easy way to configureLinux, HP-UX and Windows managed systems to communicate with HP SIM from a Windows CMS.

To run Configure or Repair Agents remotely against multiple systems simultaneously, you must haveauthorizations to run the Configure or Repair Agents tool.

You must have full CMS configuration privileges to modify the HP Systems Insight Manager community stringsin the node security file. In addition, you must enter administrator level user credentials for the target system.

To configure agents remotely:

1. Select Configure→Configure or Repair Agents. The Step 1: Select Target Systems page appears.

Note: The Verify Target Systems page appears if the targets are selected before selecting a tool.2. To add targets, select a group from the dropdown list. The contents of the selected group appear and

can be selected as targets. To select the entire collection, select Select "name of collection"

itself .

3. To remove a target, select the target’s checkbox, and then click Remove Targets.

4. Click Next. The Step 2: Enter login credentials page appears.

5. From the Step 2: Enter credentials page:

a. In the User name field, enter the system administrator or root user name.

b. In the Password field, enter the system administrator or root password for the user name previouslyentered.

c. In the Password (Verify) field, reenter the system administrator password exactly as it was entered

in the Password field.d. For Windows managed systems only, in the Domain field, enter the Windows domain.

Note: The credentials used in this step must work for all target systems that have been selected. HPrecommends using domain administrator or root credentials.

6. Click Next. The Configure or Repair Settings page appears.

Step 3: Configure or Repair Settings enables you to select options to configure the target system.The following options are available:

• Configure SNMP. Select this option to configure SNMP settings.

If this option is selected, the following steps must be considered:

1. Select Set read community string to specify a community string. By default, HP Systems

Insight Manager's first community string, that is not public, appears in the field. If no communitystring exists in HP Systems Insight Manager, then you must enter one.

Note: If only HP-UX systems with default SNMP installation are being configured at this time,you can clear this option. HP-UX enables read by default (get-community-name is set to publicby default on HP-UX systems).

Note: If this option is selected, the Read Only community string is added to the target systems.If the target system is SuSE Linux or Microsoft Windows 2003, the managed nodes do notalways enable SNMP communication between themselves and a remote host. This setting ismodified to enable the instance of the HP SIM system to communicate using SNMP with thesetarget systems.

Note: You can enter a community string up to 255 characters.




Note: Repairing the SNMP settings adds a Read Write community string to the target systemonly if one does not currently exist. This community string is unique for each system, is composedof over 30 characters to include letters and numbers, and is only visible to the user withadministrator privileges for that system. This Read Write community string is required by the Web Agent to perform certain threshold setting capabilities. This community string is onlyused locally on the target system and is not used by HP Systems Insight Manager over thenetwork. Linux and HP-UX systems do not need a Read Write community string, hence theRead Write community is added on Windows systems only.

2. Select Set traps to refer to this instance of HP Systems Insight Manager in the targetsystems' SNMP Trap Destination List. This enables the target systems to send SNMP traps to this instance of HP SIM.

• Trust relationship: Set to "Trust by Certificate". Select this option to require systems to use the Trust

by Certificate trust relationship with the System Management Homepage.

For System Management Homepage on the target systems, this option sets the trust mode to Trust

by Certificate and copies the HP Systems Insight Manager system certificate to the target system'strusted certificate directory. This enables HP Systems Insight Manager users to connect to the SystemManagement Homepage using the certificate for authentication.

• Set administrator password for Insight Management Agents version 7.1 or earlier. Select this optionto repair the administrator password on all Insight Management Agents installed on the target

systems as applicable for Windows and Linux systems.Note: This option does not apply to HP-UX. If you are configuring or repairing HP-UX systems, clearthis option.

Note: Clear this option if you have Insight Management Agents 7.2 or later installed.

Note: If the remote system is running HP-UX, this option is not executed on the remote system sinceit is not applicable on HP-UX systems. If only HP-UX target systems are being configured at thistime, you can clear this option.

If this option is selected, you must complete the following steps:

1. In the Password field, enter the new administrator password.

2. In the Confirm Password field, re-enter the new administrator password exactly as youentered it previously.

• Configure secure shell (SSH) access.

If this option is selected, you must select one of the following options:

• Host based authentication for SSH

Note: For this option to work, the user name and password provided on the previous pagemust be an administrative level account. For Linux or HP-UX targets, it must be the "root"account and password.

• Each user has to be authenticated on the managed system

Note: If the selected systems include Linux or HP-UX systems, and options for Configure SNMPsettings, Trust relationships and administrator password was selected, then SSH authenticationshould be selected now unless already configured earlier.

Note: SSH can be configured only if the OpenSSH service is running on the managed systems.OpenSSH can be installed on Windows systems, by running the Install Open SSH tool underDeploy→Deploy Drivers→Firmware and Agents→Install Open SSH.

• Create subscriptions for WBEM events.

Note: This option is only applicable to HP-UX systems. If this option is selected, the target systemis configured to send WBEM indications or events to HP Systems Insight Manager.




Note: Subscriptions for WBEM events can be created only if WBEM event providers are installedand running on the managed systems.

• Configure the WBEM Services on the target systems to support client certificate authentication.

Note: This option is only available for managing HP-UX systems running HP WBEM Services version A.02.05 or later. If this option is selected, an HP SIM WBEM certificate is registered with the WBEM Services trust store on the target systems. The user name associated with this certificate isthe one provided in step 5, which should have root privilege. When discovery runs, the WBEMServices on the target systems would use this certificate to authenticate WBEM requests from HP

SIM instead of using the basic authentication mechanism. For example, user name and password.The advantage of this technique for authentication is that you do not need to store passwords for WBEM access on your CMS.

7. Click Run Now. The Task Results page appears.

Note: Click Schedule to run this task at a later time.

Note: The Configure or Repair Agents tool can be used to update multiple target systems, each of whichmight potentially have different results. The log results indicate whether the repair attempt was successful.

Note: Repair of SNMP settings and Trust relationships and administrator password for Insight Management Agents 7.1 or earlier on Linux systems are executed by a separate task, which can be viewed in thetasks log menu selection. Repair of SNMP settings, Trust relationships on HP-UX systems is executed bya separate task, which can be viewed in the tasks log menu selection. If Linux and HP-UX systems are

selected, there are two Task IDs, one for Linux and one for HP-UX systems.

The Task Results page displays the following information:

• Status. This field displays the details for each target system within a task instance.

• Exit Code. This field represents the success or failure of an executable program. If the return valueis zero or positive, the executable ran successfully. If a negative value is returned, the executablefailed.

• Target Name. This field displays the name/IP address of the target.

• The stdout tab. This tab displays the output text information.

• The stderr tab. This tab displays information if the executable experienced an error.

•

Files Copied tab. This tab displays what files are in the process of being copied or have beencopied to the target system.

• View Printable Report. Reports can be printed for the currently selected target system or for alltarget systems associated with the task instance.

To print a report:

1. Click View Printable Report.

An Options Message box appears, asking if you want to generate a report containing onlythe currently selected target system or all systems associated with the task instance.

2. Select which report to display.

3. Click OK to display the report, or click Cancel to return to the View Task Results page.

8. If the Management HTTP Server is installed on target systems, the login credentials are updated in theManagement HTTP Server password file.

Setting up managed storage systemsStorage Management Initiative Specification (SMI-S) is a Storage Networking Industry Association (SNIA)standard that enables interoperable management for storage networks and storage devices. HP SIM usesthis standard to discover and manage the storage systems it supports.

You must have a storage system’s WBEM SMI-S provider installed and configured on a managed node forHP SIM to discover SAN storage. This includes storage devices such as Fibre Channel disk arrays, switches,tape libraries, or hosts (with Fibre Channel host bus adapters.)

Setting up managed storage systems 65



See the HP SIM SMI-S Provider webpage, http://www.hp.com/go/hpsim/providers, to view the latestinformation regarding HP SIM support for a particular device. This webpage offers information on obtaining,installing, and configuring SMI-S providers.

Installing SMI-S providersEach storage vendor provides the SMI-S provider and installation instructions for its storage system. Thewebpage referenced in the previous section provides information on obtaining SMI-S providers. Also, consultthe storage vendor’s website or representative for more information regarding their SMI-S providers. For

each storage system:1. Verify that the applicable SMI-S provider is installed.

2. If the SMI-S provider is not installed, obtain and install it per the vendor’s installation instructions.

Verifying SSLHP SIM requires that Secure Sockets Layer (SSL) is enabled for the SMI-S provider in order to discover andmanage the storage system that the provider supports. Verify that SSL is enabled for each SMI-S provider.

Configuring SMI-S providersOccasionally, it might be necessary to modify an SMI-S provider’s port number or password. Use theprovider’s documentation to perform these modifications.

For example, if two CIMOMs exist on the same host, you must configure them to use different ports tocommunicate with the CMS.

Configuring HP SIM to discover storage systems After verifying that each storage system’s SMI-S provider is installed and configured, configure HP SIM todiscover the storage systems by performing the following steps:

1. Enter the user name and password for each provider’s SMI CIMOM in the Default WBEM settingssection on the Setting Global Protocols page.

2. Add each SMI CIMOM IP address to the System Automatic Discovery task or to the Creating a

New Discovery task. See the HP SIM User Guide at http://docs.hp.com/en/index.html for moreinformation.

HP SIM discovers the storage systems after the next automatic discovery task. If you want to discover yourstorage systems immediately, run the discovery task as described in the “Running a Discovery Task” sectionof the HP SIM User Guide at http://docs.hp.com/en/index.html.










7 Configuring managed systems At this point, steps 1 through 3 are complete. Perform step 4 to configure the protocols for the managedsystems


2. Configure HP SIM for your environment. See Chapter 4 “Configuring HP SIM using the First Time

Wizard” or Chapter 5 “Configuring HP SIM using the Options menu” for the recommended tasks.3. Install and configure the required management software on the systems that will be managed by the

CMS. For more information on this step, see Chapter 6 “Setting up managed systems” for details.

4. Configure the protocols for the managed systems. The procedure to complete this step is in this chapter.

Configuring the managed system software using the Configure or Repair Agents feature from the CMS

The HP Systems Insight Manager Configure or Repair Agents tool is a quick and easy way to configureLinux, HP-UX and Windows managed systems to communicate with HP SIM from a Windows CMS.

To run Configure or Repair Agents remotely against multiple systems simultaneously, you must haveauthorizations to run the Configure or Repair Agents tool.

You must have full CMS configuration privileges to modify the HP Systems Insight Manager community stringsin the node security file. In addition, you must enter administrator level user credentials for the target system.

To configure agents remotely:

1. Select Configure→Configure or Repair Agents. The Step 1: Select Target Systems page appears.

Note: The Verify Target Systems page appears if the targets are selected before selecting a tool.

2. To add targets, select a group from the dropdown list. The contents of the selected group appear andcan be selected as targets. To select the entire collection, select Select "name of collection"

itself .

3. To remove a target, select the target’s checkbox, and then click Remove Targets.

4. Click Next. The Step 2: Enter login credentials page appears.

5. From the Step 2: Enter credentials page:a. In the User name field, enter the system administrator or root user name.

b. In the Password field, enter the system administrator or root password for the user name previouslyentered.

c. In the Password (Verify) field, reenter the system administrator password exactly as it was enteredin the Password field.

d. For Windows managed systems only, in the Domain field, enter the Windows domain.

Note: The credentials used in this step must work for all target systems that have been selected. HPrecommends using domain administrator or root credentials.

6. Click Next. The Configure or Repair Settings page appears.

Step 3: Configure or Repair Settings enables you to select options to configure the target system.The following options are available:

• Configure SNMP. Select this option to configure SNMP settings.

If this option is selected, the following steps must be considered:

1. Select Set read community string to specify a community string. By default, HP SystemsInsight Manager's first community string, that is not public, appears in the field. If no communitystring exists in HP Systems Insight Manager, then you must enter one.

Note: If only HP-UX systems with default SNMP installation are being configured at this time,you can clear this option. HP-UX enables read by default (get-community-name is set to publicby default on HP-UX systems).

Note: If this option is selected, the Read Only community string is added to the target systems.

If the target system is SuSE Linux or Microsoft Windows 2003, the managed nodes do not

Configuring the managed system software using the Configure or Repair Agents feature from the CMS 67



always enable SNMP communication between themselves and a remote host. This setting ismodified to enable the instance of the HP SIM system to communicate using SNMP with thesetarget systems.

Note: You can enter a community string up to 255 characters.

Note: Repairing the SNMP settings adds a Read Write community string to the target systemonly if one does not currently exist. This community string is unique for each system, is composedof over 30 characters to include letters and numbers, and is only visible to the user withadministrator privileges for that system. This Read Write community string is required by the

Web Agent to perform certain threshold setting capabilities. This community string is onlyused locally on the target system and is not used by HP Systems Insight Manager over thenetwork. Linux and HP-UX systems do not need a Read Write community string, hence theRead Write community is added on Windows systems only.

2. Select Set traps to refer to this instance of HP Systems Insight Manager in the targetsystems' SNMP Trap Destination List. This enables the target systems to send SNMP traps to this instance of HP SIM.

• Trust relationship: Set to "Trust by Certificate". Select this option to require systems to use the Trust

by Certificate trust relationship with the System Management Homepage.

For System Management Homepage on the target systems, this option sets the trust mode to Trust

by Certificate and copies the HP Systems Insight Manager system certificate to the target system's

trusted certificate directory. This enables HP Systems Insight Manager users to connect to the SystemManagement Homepage using the certificate for authentication.

• Set administrator password for Insight Management Agents version 7.1 or earlier. Select this optionto repair the administrator password on all Insight Management Agents installed on the targetsystems as applicable for Windows and Linux systems.

Note: This option does not apply to HP-UX. If you are configuring or repairing HP-UX systems, clearthis option.

Note: Clear this option if you have Insight Management Agents 7.2 or later installed.

Note: If the remote system is running HP-UX, this option is not executed on the remote system sinceit is not applicable on HP-UX systems. If only HP-UX target systems are being configured at thistime, you can clear this option.

If this option is selected, you must complete the following steps:

1. In the Password field, enter the new administrator password.

2. In the Confirm Password field, re-enter the new administrator password exactly as youentered it previously.

• Configure secure shell (SSH) access.

If this option is selected, you must select one of the following options:

• Host based authentication for SSH

Note: For this option to work, the user name and password provided on the previous pagemust be an administrative level account. For Linux or HP-UX targets, it must be the "root"account and password.

• Each user has to be authenticated on the managed system

Note: If the selected systems include Linux or HP-UX systems, and options for Configure SNMPsettings, Trust relationships and administrator password was selected, then SSH authenticationshould be selected now unless already configured earlier.

Note: SSH can be configured only if the OpenSSH service is running on the managed systems.OpenSSH can be installed on Windows systems, by running the Install Open SSH tool underDeploy→Deploy Drivers→Firmware and Agents→Install Open SSH.

• Create subscriptions for WBEM events.

Note: This option is only applicable to HP-UX systems. If this option is selected, the target systemis configured to send WBEM indications or events to HP Systems Insight Manager.

68 Configuring managed systems



Note: Subscriptions for WBEM events can be created only if WBEM event providers are installedand running on the managed systems.

• Configure the WBEM Services on the target systems to support client certificate authentication.

Note: This option is only available for managing HP-UX systems running HP WBEM Services version A.02.05 or later. If this option is selected, an HP SIM WBEM certificate is registered with the WBEM Services trust store on the target systems. The user name associated with this certificate isthe one provided in step 5, which should have root privilege. When discovery runs, the WBEMServices on the target systems would use this certificate to authenticate WBEM requests from HP

SIM instead of using the basic authentication mechanism. For example, user name and password.The advantage of this technique for authentication is that you do not need to store passwords for WBEM access on your CMS.

7. Click Run Now. The Task Results page appears.

Note: Click Schedule to run this task at a later time.

Note: The Configure or Repair Agents tool can be used to update multiple target systems, each of whichmight potentially have different results. The log results indicate whether the repair attempt was successful.

Note: Repair of SNMP settings and Trust relationships and administrator password for Insight Management Agents 7.1 or earlier on Linux systems are executed by a separate task, which can be viewed in thetasks log menu selection. Repair of SNMP settings, Trust relationships on HP-UX systems is executed bya separate task, which can be viewed in the tasks log menu selection. If Linux and HP-UX systems are

selected, there are two Task IDs, one for Linux and one for HP-UX systems.

The Task Results page displays the following information:

• Status. This field displays the details for each target system within a task instance.

• Exit Code. This field represents the success or failure of an executable program. If the return valueis zero or positive, the executable ran successfully. If a negative value is returned, the executablefailed.

• Target Name. This field displays the name/IP address of the target.

• The stdout tab. This tab displays the output text information.

• The stderr tab. This tab displays information if the executable experienced an error.

•

Files Copied tab. This tab displays what files are in the process of being copied or have beencopied to the target system.

• View Printable Report. Reports can be printed for the currently selected target system or for alltarget systems associated with the task instance.

To print a report:

1. Click View Printable Report.

An Options Message box appears, asking if you want to generate a report containing onlythe currently selected target system or all systems associated with the task instance.

2. Select which report to display.

3. Click OK to display the report, or click Cancel to return to the View Task Results page.

8. If the Management HTTP Server is installed on target systems, the login credentials are updated in theManagement HTTP Server password file.

Configuring the managed system software using the Configure or Repair Agents feature from the CMS 69



8 Initializing the Remote Support Software Manager on theCentral Management Server (CMS)

Understanding the Remote Support Software ManagerThe HP Essential Services Remote Support Pack includes three components:

•

HP Remote Support Software Manager (SWM): SWM, bundled with HP Systems Insight Manager (HPSIM) version 5.1 and installed to the Central Management Server (CMS), facilitates the download andinstallation of HP Remote Support applications. The procedure to complete this step is in this chapter.

• HP Remote Support Tool: The Remote Support Tool is installed and updated by SWM . Once installed,the Remote Support Tool is accessed through HP SIM and is used to enable remote support of eligibledevices in your Enterprise.

• HP Remote Support Client: The Remote Support Client is not visible to users, but it enables communicationof reactive hardware events from the CMS to the HP Support Center.

This chapter focuses on SWM. SWM is bundled with the installation of HP SIM on a supported WindowsProLiant CMS. SWM is installed to the CMS desktop and runs independently of the HP SIM user interface.The Remote Support Software Manager is installed on the CMS through Systems Insight Manager installation.The inclusion and installation of Remote Support Software Manager is part of the standard HP SIM installation,

and optional, but pre-selected by default, in the custom HP SIM installation and/or upgrade. The RemoteSupport Software Manager installation is non-interactive. Once installed, the Remote Support SoftwareManager application can be accessed from an icon on the CMS desktop. After the SIM installation iscomplete, users configure the Remote Support Software Manager to fit their enterprise specifications. Onceconfigured, the Remote Support Software Manager will download and install the Remote Support Tool.

SWM offers the following functionality and benefits:

• Upgrades can be performed remotely, reducing HP Support Engineer time on your site for installations.

• Automated e-mail notifications of new software, deployment statistics, and the state of your configurationsimprove communications, planning, and management of the Customer Enterprise.

• Software configuration data is collected to facilitate the following activities:

Target updates based on existing software versions present on a system•

• Track deployment of software updates

• Report on the state (installed, update available, failed, and so on) of the software on a system

SWM device and access requirementsSWM is supported only on ProLiant servers running:

• Windows 2003 Standard Enterprise

• Windows 2000 Server SP2, Advanced Server

Use of SWM User Interface requires administrator privileges on the Windows operating system. If you donot have an account with administrative privileges, please contact your Remote Support Account Team for

more information or assistance.

The Software Manager on the CMS communicates over HTTPS/443. Likewise, the Remote Support Clientcomponent also communicates over HTTPS/443 to submit incidents to and retreive entitlement informationfrom the HP Support Center. HTTPS provides encryption for confidentiality of software configuration datacollected from the CMS and transferred to HP. Even though this chapter focuses on configuring SWM, it isadvisable to configure your firewall for both communication channels (SWM and Remote Support Client)before proceeding.

IP AddressServer nameService

15.232.64.127isee-updates.americas.hp.comHP Remote Support Software Manager

15.232.48.172services.isee.hp.comHP Remote Support Client

Understanding the Remote Support Software Manager 70



SWM communicates directly with the HP Support Center through the firewall or web proxy server (if a webproxy server is in use). Remote Support SWM supports connecting directly to the Internet or connectingthrough a proxy server and supports all proxy servers conforming to the HTTP/1.0 Specification. RemoteSupport Software Manager does not support proxies using proxy auto-configuration scripts, NTLMauthentication (also known as Integrated Windows Authentication), or Kerberos authentication.

NOTE: You can check for any software or networking updates in the Service Essentials Remote SupportPack Release Notes athttp://docs.hp.com/en/netsys.html#Service%20Essentials%20Remote%20Support%20Pack.

HP Remote Support Software Manager Configuration OptionsThe SWM application settings are configured during the Remote Support Software Manager Initialization.The settings can be modified at any time to meet your unique needs. The two primary SWM abilities on theCMS are:

• The ability to define automation level settings that configure if and how updates will be downloadedand installed.

• The ability to define an update schedule during a time window in which SWM can request and retrieveupdates.

The following table lists items configured during the SWM Initialization:

OptionsRequired Information

The web proxy options enable specified settings which include: Web Proxy Settings are configured to enable the SoftwareManager to function in conjunction with your proxy serverconfiguration.

• Server

• Port

• Proxy Server User Name

• Password

• Server

The default web proxy server settings will be blank and must bepopulated with the correct proxy information to enable thesubsequent connectivity test.

Provide your company nameCustomer’s Company Name

The country or region where the CMS physically resides must beselected from the drop down menu in the SWM Initializationprocess.

Country/Region

You can enter one or more (separated by semi-colons) HP contactsinto this field to receive reports for this CMS. By default, this lineis left blank.

HP Contact Reporting Options field adds the CMS to an internalHP report of systems supported by a specified HP contact.

You might enter one or more (separated by semi-colons) customercontacts into this field to receive e-mail notifications about updates

Customer Contact Notification Options field adds the includedcontacts to a notifications list to be notified when updates are

for the CMS. By default, this field and the associated check boxespublished to the SWM servers at the HP Support Center and toreceive biweekly reports about the CMS and SWM application. are left blank. Unless you add contacts to this list and check the

appropriate boxes, no e-mail notifications will be sent.

The Automation levels are:Global Automation Levels enables you to restrict the applicationof all updates to the CMS.

•

Do not automatically download nor install• Allow automatic download but install manually

• Allow automatic download and install

By default the automation levels are left blank. Therefore, you mustmake a selection. See Automation Levels and Scheduling in theSoftware Manager for more information about using AutomationLevels.

The scheduling options are:Global Update Window settings enable restrictions of whendownloads and installations occur on the CMS.

• Allow updates to occur anytime

• Allow at a specified time on a specific day(s) of the week.

• Allow updates between two specified points in time on aspecific day(s) of the week

By default, Anytime is selected.

Understanding the Remote Support Software Manager 71



See Using the HP Remote Support Software Manager for more information about using Remote SupportSoftware Manager.

Initializing the HP Remote Support Software Manager Software ManagerHP Remote Support Software Manager is installed by default with an HP SIM 5.1 standard installation andoptionally with an HP SIM 5.1 custom installation. When selected, SWM is installed on the CMS but not yetconfigured. The first time you access the SWM interface, you are prompted to complete the initialization.The SWM initialization is an interactive process that both configures and registers the application for regular

usage on your CMS.

NOTE: HP recommends that you reference the required information in the preceding table before beginningthe initialization process.

About the Initialization ProcessThroughout the SWM initialization, Form Submission and Action Submission windows appear Thesewindows confirm that the data you provided or the direction you gave was accepted by the initializationprocess. These windows are mentioned but not displayed in the initialization instructions documented in thefollowing section.

Throughout the SWM installation a yellow Please Wait information box appears periodically as the processcompletes tasks. The following sections do not document every instance where the Please Wait box appears.

Running the Remote Support Software Initialization Process

To initialize the Remote Support Software Manager:1. Start the SWM by double clicking the Remote Support Software Manager (Windows Administrator

Access only) icon on the CMS desktop.

2. Click Continue in the Introduction window.

72 Initializing the Remote Support Software Manager on the Central Management Server (CMS)



3. Select the Enable the following web proxy settings for HTTP communications box, and thenselect the appropriate proxy settings. The User is the user name for the proxy server.

4. Click Continue in the Proxy window.

5. Click Continue in the Form Submission window.

6. Click Continue in the Test Connectivity window to verify your Internet connection to the HP SupportCenter.

7. Click Continue in the Action Submission window.

8. Enter the name of your company and click Continue.

9. Click Continue in the Form Submission window.

10. Select your appropriate Country/Region from the drop down list and click Continue.

Initializing the HP Remote Support Software Manager Software Manager 73



11. Click Continue in theForm Submission window.

12. Select the boxes for the contact options (Customer or HP Account Manager) you want to enable. Then,enter your contact information and select the appropriate reporting and notification options.

13. Click Continue in theContacts window.

You may disable biweekly reports and periodic notifications sent from the HP Support Center through

the Internet to your e-mail addresses at anytime by referencing the steps in Understanding andConfiguring Customer Notifications and Reports


15. Select your bandwidth settings and click Continue.





17. Select your Global Preferences and click Continue.

• If you select Automatic Install to activate automatic downloads and installations of softwarepackages, then you will not be prompted for download or installation activities.

• If you select Automatic Download to activate automatic downloads only, then software packageinstallations must be done manually.

• If you select Manual, then all downloads and subsequent installations will require manual approvaland actions. You can check for software updates by logging into the Remote Support SoftwareManager.

See Understanding Automation Levels in the Remote Support Software Manager for more informationabout using Automation Levels, and for more information about selecting your scheduling options,please see Understanding and Modifying Scheduling in Software Manager.


19. Click Continue in theConfiguration window, and the settings you have configured will be applied tothe Remote Support Software Manager. There will be a several minute delay while the changes areupdated, and you may see applications windows open and close.

NOTE: It is strongly recommended that you configure the settings for Automatic Install and Anytime

and verify that all days of the week are marked, so that when you Update All the correct updates willbe applied to your CMS.

20. Click Continue in theAction Submission window.

21. Click Continue in theRegistration window to register the CMS and the Software Management

application with the HP Support Center. There will be a several minute delay while communication is




established and the registration completes. The status will be displayed in a command prompt window.Do NOT close the command prompt window.


23. It is highly recommended that you click Continue in theUpdate All window. If you do, the CMS willreceive updates of all of the latest packages from the HP Support Center. There will be a delay ofseveral minutes while the changes are communicated to the HP Support Center, and the status will bedisplayed.

While you may click Skip in the Update All window, if you do, new updates will not be applied, and

you will not have the full functionality of the Remote Support Software Manager until you update yourconfiguration.


25. Click Finish in theFinish window to complete the Software Manager initialization. There will be adelay while the initialization completes, after which the Software Manager User Interface will reloadwith the standard display, rather than the initialization display.

NOTE: If the Software Manager Packages window does not list any packages, please review theprevious steps and verify that they were completed successfully and that the Update All process wasselected. You can enter any corrected information in the standard SWM display and resubmit it usingthe steps in the Understanding and Using the Actions Option section.




NOTE: The OSEM application and its read me file will open after the Update All process runs. You canclose these windows.

Using the HP Remote Support Software ManagerModifying HP Remote Support Software Manager Settings

Most of the SWM settings are originally configured during the Initialization. The settings can be modifiedat any time to meet your unique needs. For any of the following sections, this step is required to access theSWM and is then assumed in subsequent instructions:

Start SWM by double clicking the Remote Support Software Manager (Windows Administrators only)icon on the CMS desktop.

Form or Action Submission Windows

When you modify a setting in the SWM, you will receive a Form Submission or an Action Submission

window. These windows confirm that the data you provided or the direction you gave was accepted by andcommitted to the SWM. These windows will be mentioned but not displayed in the instructions documentedin this section.

Automation Levels and Scheduling in the Software Manager

Two significant Remote Support Software Manager abilities on the CMS are:

• The ability to define automation level settings that configure how an update may or may not bedownloaded and/or installed.

• The ability to define an update schedule during a time window in which SWM may request and retrieveupdates.

The Remote Support Software Manager applies a combination of global and package-specific preferencesto the process of updating software packages on the CMS. These preferences apply to both automation




levels and scheduling. The package-specific defaults are set when the package is created, but the settingscan be modified through the Remote Support Software Manager.

The following table outlines the Remote Support Software Manager Automation Levels:

OptionsPreference

The Automation levels are:Global Automation Levels Enable the Customer to restrict theapplication of all updates to the CMS.


• Allow automatic download but install manually

• Do not automatically download nor install

The Automation levels are:Package Automation Levels enable the Customer to restrict theapplication of updates to a specific package.

• Use Global Automation Settings




The default package automation setting is to use the Global Automation Setting.

The scheduling options are: Allow Downloads and Installations (or Global Update Window)settings enable restrictions of when downloads and installationsoccur on the CMS.

• Allow updates to occur anytime

•

Allow at a specified time on a specific day(s) of the week• Allow updates between two specified points in time on a

specific day(s) of the week

The package scheduling options are:Package Scheduling determines when downloads and installationsoccur for each specific package.

• Never

• Allow at a specified time/interval on a specific day(s) of theweek

• Allow at a specified time/interval on every day

• Allow at a specified time/interval on a specific day of themonth

The default scheduling options are specific to each package.

For more information about using the Remote Support Software Manager see“Using the HP Remote SupportSoftware Manager”.

Understanding Automation Levels in the Remote Support Software Manager

The Global Automation Levels are set during initialization of the Remote Software Manager. Individualpackage settings, however, cannot be configured until after initialization. The following descriptions explainthe differences and relationship between the Factory Automation levels, Global Automation levels, andPackage Automation levels.

• Factory Automation Levels: When a software package is created by HP it has factory automation levelsset based on the intended function and business usage of the software package. These settings maybe more or less restrictive than the global or package automation levels set by the Customer. If thefactory automation levels are more restrictive, for instance Automatic Download, than the Global

Settings configured to Automatic Install, then the package will only download and will require manualinstallation.

• Global Automation Levels: Set globally, these levels are applied to all packages received by the RemoteSupport Software Manager, unless an individual package’s levels are configured independently fromthe global setting.

• Package Automation Levels: As the authoritative automation level Package levels are customized perindividual package. If not modified, the package level resolves to the existing global automation levelfor the enterprise.

Example: if a software update was published with a factory automation level of allow automatic downloadbut install manually, a CMS with global automation level setting at do not automatically download nor installwould not download the update.




In the same example, a CMS with a package-level automation level setting of allow automatic downloadand install would download but not install that package. The factory automation level setting cannot bemade less restrictive by a global or package-level setting.

Once the Customer has modified these settings either globally or/and by package, the Customer preferences,if more restrictive than the preferences issued with the update, will always take precedence.

Global Automation Levels enable the Customer to restrict the application of all updates to the CMS.However, Global Automation Levels are overridden by a Package Automation Levels, unless the packageautomation level is set to Use Global Automation Level. Packages that are using customized Package

Automation levels display a triple red asterisk *** next to the Preferences link in the Packages window.The available Global Automation Levels are (The installed default is Allow automatic download and

install):




Package Automation Levels are configurable and enable the Customer to restrict the application of updatesto a specific package. Package Automation Levels override Global Automation Levels unless set to UseGlobal Automation Levels.

The Package Automation Levels are:

• Use Global Automation Levels




Understanding User Automation Levels

User Automation Levels resolve to either the Global Automation Level or the Package Automation Levelapplied to an individual package. The User Automation Level is compared against the Factory AutomationLevel to determine the Effective Automation Level, which ultimately affects the package status and actions.

User Automation LevelPackage Automation LevelGlobal Automation Level

Allow automatic download andinstall

Use Global Automation Levels Allow automatic download andinstall

Package A

Do not automatically downloadnor install

Do not automatically downloadnor install


Package B

Allow automatic download butinstall manually



Package C




Package D

Understanding Factory Automation Levels

Factory Automation Levels are pre-determined by the package creators at HP and vary for each individual

package. This setting is compared to the user automation level to determine the effective automation level.The Factory Automation Level only takes precedence over the User Automation Level if it is more restrictivethan the user automation level.

The available Factory Automation Levels are:




Understanding Factory Effective Levels

Effective Automation Levels ares the settings that are ultimately applied to an individual package after the

resolution of precedence between the User and Factory Automation Levels.




The available Effective Automation Levels are:




Effective Automation LevelUser Automation LevelFactory Automation Level

Do not automatically download

or install

Do not automatically download

or install

Allow automatic download and

install

Package A




Package B

Do not automatically downloador install



Package C




Package D




Package E




Package F

Allow automatic download andinstall Allow automatic download andinstall Allow automatic download andinstallPackage G

Modifying Automation Levels in the Software Manager

The following section explains how to modify the Automation levels for both Global Preferences and PackagePreferences.

To modify Global Automation levels:

• In the Remote Support Software Manager Application, select Options >Preferences. The Global

Preferences window is displayed.

• In the Global Automation Level section

If you select Automatic Install to activate automatic download and install of packages, you willnot be prompted for download or install activities.

•

• If you select Automatic Download to activate automatic download only, installations must bedone manually.

• If you select Manual all downloads and installations must be done manually.

• After making your selection, click Submit.

To modify Package Automation Levels:

1. In the Software Manager, select Packages. The Packages window is displayed, with the details ofthe available packages.




2. To restrict the application of updates for a specific package, select Preferences in the Actions columnof the particular package. The Package Preferences window is displayed.

3. In the Automation Level section:

a. Check Use the Global Automation Setting to defer to the Global Automation Level for this package;this is the Software Manager default of all packages.

b. Select Automatic Install to allow automatic download and installation of this package. You will

not be prompted for download or installation activities for this package.c. Select Automatic Download to allow only automatic download for this specific package.

Installation of this package must be done manually.

d. Select Manual to manually download and install this package when it is available.

4. After making your selection, click Submit.

Understanding and Modifying Scheduling in Software Manager

Scheduling Software Manager updates on the CMS involves the coordination of two scheduling components,the Global Update Window and the Package Update Schedule.

The Global Update Window is a predefined window of time during which the Software Manager is allowedto contact HP to retrieve software updates. Data retrieved can include downloading actual packages, if

allowed by the effective automation level.




The Package Update Schedule is a predefined time frame when the Software Manager will probe HP forupdates of that particular package. If the schedule is set during an open Global Update Window, the updatewill be automatic. If the schedule is set during a time that the Global Update Window is closed, the updateattempt will be queued until such time as a Global Update Window opens. The Package Update Scheduleis subject to a variance of +/- 10 minutes.

Modifying the Global Update Window

The installed Global Update Window default allows updates to occur at any time. The Global Update Window options are:

• Anytime

[on any specific day(s)]

• At a specific time

[hour, minute, am/pm, on X day(s)]

• Between two specific times

[hour, minute, am/pm, on X day(s)]

To modify the Global Update Window:

1. In the Remote Support Software Manager application, select Options→Preferences. The Global

Preferences window appears.

2. In the Allow Downloads and Installations section, choose a Global Update Window type:

NOTE: This section applies only if you have set your Global Automation Level as Automatic Install or Automatic Download.

• Select Anytime to download or install packages any time. The time of download will be determinedby each package’s individual schedule.

• Select At and set the time you want the packages to be downloaded and installed.

• Select Between to set the time range. The packages will be downloaded or installed within thattime range.

3. In the On these days of the week row, select the day(s) of the week that you want to allow thedownload and installation as selected in the previous step.

4. Click Submit. The Form Submission window is displayed, confirming the details of the globalpreferences update that you selected.

Modifying Package Update Scheduling

Package Scheduling enables restrictions of when downloads and installations occur per package. The defaultsfor each package are specific to the Factory Scheduling Settings. Once you have modified a package’sscheduling settings, the Factory Scheduling Settings are lost. If not modified, the Factory scheduling defaultsare preserved.

To modify the Package Scheduled settings levels:

1. In the Remote Support Software Manager, select Packages. The Packages window is displayed, withdetails of the available packages.




2. To modify a specific package schedule, select Preferences in the Actions column of the particularpackage. The Package Preference window will display.

3. In the Update Schedule section:

a. Select Never if you want to specify that an update to the package should NOT occur at any pointof time.

b. Select Daily and specify whether you want the updates to occur Everyday of the week or onlyon Weekdays.

c. Select Weekly to specify which day of the week you want an update to occur.

d. Select Monthly and the number that represents a particular day of the month in the drop downmenu to specify a monthly update to the package.

4. To select a specific time for the updates, select Update at and specify the time frame.

5. To specify a frequency for the update, select Update every and specify the time from the drop downmenu.

6. Click Submit. The Submission Form is displayed, confirming the details of the requested update schedule.

Managing Software Downloads and Installations

Software updates are managed in the Packages window. The following sections describe the differentcolumns in the Packages window and how they interact with each other.




• The Packages Column

The Packages Column displays the name of a software package available from HP.

• The Effective Automation Level

Due to the complexity of the automation levels and package availability, it is important to understandhow the automation level affects behavior of updates, which in turn affects the status of packages onthe CMS. As the status of packages available from HP changes, so do the actions available for thosepackages. The change is dependent on each package’s Effective Automation Level.

• Download Size and Priority Entries Column

The Download Size and Priority columns communicate non-programmatic information that is set by theauthor(s) of a particular software package. These entries are strictly informational and have no impacton the operations of the Software Manager.

• The Package Status

Package status can be any of the following:

• Available: This package has not yet been downloaded or installed on the CMS.• Downloaded: This package has been downloaded onto the CMS but has not been installed.

• Installed: This package has both been downloaded and installed on the CMS.

• Update Available: An update for this package, that was previously downloaded and/or installedon the CMS, has been detected, but it has not been downloaded. No further action has occurred.

• uninstalled: This package has been removed from the CMS.

When and if a Global Update Window opens, a package update schedule runs, and the Effective Automation Level settings allow, the package status for any or all packages may change. Additionally,if you manually execute the Check for Package Updates option the status may change if new updatesare available.

• Available Actions

An application package’s status can be modified through one of two different actions on the CMS:

• Install: Either install the package (if it is already downloaded) or download and install it.

• Remove: Removes a package from the CMS operating system.

It is important to understand that removing a package removes the software from the CMS and resetsthe package automation level to manual. If you do not want that package installed on the CMS, thendo not reinstall it when it reappears in the Packages window.

Understanding and Configuring HP Reports

HP Account Manager field adds this CMS to an HP internal report of devices managed by a specified HP

contact(s). You may enter one or more HP contact(s) into this field to receive reports for this CMS by separating




e-mail addresses with semi-colons. By default, this line is left blank. If you want this CMS included in HPinternal reports for a specific HP engineer, add his/her e-mail address to this field.

To configure reporting:

1. In the Remote Support Software Manager, select Contacts. The Contacts window is displayed.

2. Select Enable e-mail for status and connectivity reporting.

3. In the HP Contact section, enter the e-mail address(es) of the HP contact(s) to whom the reports for thisCMS is to be sent.

4. Click Submit. The Form Submission displays. confirming the details of the HP Contact information thatyou have submitted.

Understanding and Configuring Customer Notifications and Reports

The Customer Contact Option adds the contacts entered into the field to a notifications list for updates asthey are published to HP’s hosting Software Manager servers at the HP Support Center. If package optionsare checked, then notifications are sent to the specified Customer contact for that package update. If leftunchecked, no notifications are sent.

Additionally, you may enable reports for both the software state of the Remote Support Software Managerand connectivity reports for communication from the Remote Support Software Manager. You may enter oneor more Customer contacts into the e-mail field to receive e-mail notifications about updates and reports forRemote Support Software Manager on your CMS.

The types of e-mail messages you will receive through the internet from the HP Support Center are:

• Software State Reports, which are sent biweekly and include the title, current version, status, andupdate availability of supported software applications installed on the CMS.

• Failed CMS SWM Connectivity Alertswhich notify you when the Remote Support Software Manager

has lost connectivity from the CMS to the HP Support Center. The notification will inform you of the lasttime the Remote Support Software Manager logged a successful Software configuration data collectionfrom the HP Support Center.

You may opt in or out of either notification at any time by selecting or disabling the option and submittingyour preferences. See Understanding and Using the Actions Option for information about manually updatingthe HP Support Center with your software configuration change.

To configure notifications:

1. In the Remote Support Software Manager, select Contacts. The Contacts window is displayed.

2. In the Customer Contact section, enter the e-mail address(es) of the Customer contact(s) to which thenotifications on the updates for the CMS are to be sent.

3. Select e-mail announcements and/or e-mail reports and click Submit.

4. The Form Submission window is displayed, confirming the details of the selection for e-mailnotifications.




Modifying Proxy Settings

Proxy settings are configured to enable the Software Manager to function in conjunction with the Customersweb proxy server configuration.

The Web Proxy options are to enable specified settings which are:

• Server

• Port

• Proxy Server User Name

• Password

1. In the Remote Support Software Manager, Select Proxy; the Web Proxy window is displayed.

2. Select Enable the following web proxy settings for HTTPS communications.

3. Enter the Server name and the Port number.

NOTE: The Software Manager does not require entry of a proxy realm value; it will resolve the valueautomatically.

4. Enter the User name and Password and Confirm the password to facilitate access to the server.

5. Click Submit. The Form Submission window is displayed, confirming the details of the proxy settingsthat you have submitted.

Modifying Bandwidth Settings

Bandwidth settings allow the Customer to restrict how much bandwidth the Software Manager uses. Thebandwidth options are:

• Do not limit bandwidth

• Select the percentage of bandwidth (cannot be set to zero).

• Limit bandwidth to a set Kbps measurement

The default setting for bandwidth is 25% of Ethernet (10Mbps). HP recommends retaining the defaultbandwidth settings for timely service. Reducing the bandwidth settings will increase the time required to

transfer files.To configure bandwidth settings:

1. In the Remote Support Software Manager, select Bandwidth. The Bandwidth window is displayed.




2. Select one of the options for setting the bandwidth availability for the Software Manager and clickSubmit. The Form Submission window is displayed, confirming the details of the bandwidth optionsthat you have selected.

Understanding and Using the Actions Option

The Actions window in the Remote Support Software Manager provides access to the following features:

• Restart Agent: this feature stops and restarts the processes associated with the Software Manager.Downloads or installations that are in progress may need to be resumed after the application restarts.

• Check for Package Updates: this feature checks the HP Data Center for any software packageupdates. If updates are available, the status will display in the Package window. If new packages areavailable they will be processed according to their effective automation levels, and if set for automaticupdate they will only update and/or install only during a scheduled update window.

• Test Connectivity: this feature allows you to test the connection between the Remote Support SoftwareManager on the CMS to the HP Support Center. If the test fails, recheck your proxy settings.

• Submit Software Configuration Data: this feature submits updates to the software configuration (suchas contact information) to the HP Support Center. While this task is performed daily, you may use thisfeature to do it immediately.

Removing or Reinstalling the Remote Support Software ManagerThe HP Remote Support Software Manager has its own uninstall software. To uninstall the Remote SupportSoftware Manager, from the CMS select Start > Programs > Hewlett-Packard > Remote Support

Software Manager Uninstall.

If you have already removed the Remote Support Software Manager in MS Windows using Add/Remove

Programs in the Control Panel, you can still run the uninstaller to remove all files.




Reinstalling the Remote Support Software Manager

The Remote Support Software Manager cannot be recovered. In the event that there is an application failure,the SWM application must be reinstalled. If there is a hardware or operating system failure, the SWMapplication would also require reinstallation along with HP SIM.




9 Installing and configuring the Service Essentials RemoteSupport Pack on HP SIM 5.1

This chapter includes the basic steps to configure the Service Essentials Remote Support Pack (RSP) runningon a Windows-based Central Management Server (CMS) with HP SIM 5.1. The following instructions mustbe completed successfully to ensure that the new HP SIM entitlement (Contract and Warranty information)and Remote Support monitoring features work correctly.

PrerequisitesThe following are required to ensure proper setup prior to installing and configuring the Remote SupportPack (RSP):

• The CMS is designated. There must be a single physical system allocated for HP SIM and the RemoteSupport Pack components.

• Insight Management Agents installed on monitored systems (minimum required is version 6.0;recommended is the latest version available).

• SNMP trap forwarding configured from monitored systems to the CMS.

• SNMP community strings configured correctly to allow SNMP Gets to be performed from the CMS to

each monitored system. This is required to ensure correct operation by HP SIM and OSEM for faultanalysis and service incident submission purposes.

• All monitored systems, including the CMS, should be covered under a valid HP hardware warranty,HP Care Pack, or support contract obligation.

• HP SIM 5.1 installed on a Windows-based CMS with Remote Support Software Manager included.

• Ensure that HP SIM 5.1 installs System Management Homepage (SMH), minimum version of 2.1.7,which is automatically installed by HP SIM during a Typical installation.

• Ensure Remote Support Software Manager installs base Remote Support Pack packages includingRemote Support Client A.05.00, OSEM 1.4.1A or greater, and Remote Support Common Components.

Note: Be sure to install OSEM version 1.4.1A or greater, and not version 1.4.1 or lower.

Remote Support Pack setupThis process describes the steps you should perform to obtain Contract and Warranty information (HPcontract, HP Care Pack, and HP warranty entitlement) and Remote Support capabilities.

Note: Steps 1 through 4 should be performed to ensure that both Remote Support and Contract and Warrantyinformation functionality are initialized properly.

1. Ensure all prerequisites are met.

2. If you are using a Web Proxy Server for Internet access from your enterprise, confiugre the Web Proxysettings on the CMS after the Remote Support Pack is installed on the CMS but before you register it.This step is necessary to register the CMS and Remote Support Pack, and it allows the Remote SupportClient to communicate event and entitlement information oto the HP Support Center. To configure your

Web Proxy settings, complete the appropriate process below.For non-aunthenticated Web Proxy Servers:

a. Open a command prompt on the CMS.

b. Change the directory to C:\Program Files Hewlett-Packard\RemoteSupport\bin.

NOTE: The directory path may vary by the regional language of the Windows operating system.

c. Run the command configureProxy -H [hostname] 8080 RUN_AUTHwhere [hostname}is hte fully qualified hostname of your proxy server.

The following output will be returned:

TMP_PROXY_HOST has been set to [hostname]

Prerequisites 89



TMP_PROXY_PORT has been set to 8080

d. Exit the command prompt and continue to the next step.

For authenticated Web Proxy Servers:

a. Open a command prompt on the Central Management Server.

b. Change thedirectorypath toC:\Program Files\Hewlett-Packard\RemoteSupport\bin.

NOTE: The directory path may vary by the regional language of the Windows operating system.

c. Run the command configure Proxy -H [hostname] 8080 RUN_AUTH where [hostname]is hte fully qualified hostname of your proxy server.

d. When prompted, respond to the following questions for your enterprise:

Should proxy authentication use NTLM [yes, no]:

Enter proxy username:

Enter proxy domain for user '[proxy user]':

Enter proxy password for user '[proxy domain/proxy user]':

Confirm proxy password for user '[proxy domain/proxy user]':

NOTE: Because of security encryption, you will not see the responses you are typing displayed

at the prompt.

e. Exit the command prompt and continue to the next step.

3. Configure and register the Remote Support Pack client in HP SIM by selecting Options→Remote

Support Configuration and Services. The Remote Support Configuration and Services pageappears on the Remote Support Settings tab. Complete the form and submit it.

4. From the Remote Support Configuration and Services page, select the Remote Support Services

tab, and select submit test event to ensure the connection between the CMS and the HP Data Centerserver is functioning correctly. The page should indicate if the event was submitted successfully. Thistest validates communication between the Remote Support Pack client and the Remote Support DataCenter.

90 Installing and configuring the Service Essentials Remote Support Pack on HP SIM 5.1



NOTE: Steps 5 through 7 should be performed to ensure that Contract and Warranty Informationfunctionality is configured properly.

5. Ensure HP SIM has discovered the set of systems that Contract and Warranty Information is checkedfor. Verify the All Systems collection to ensure these devices are listed.

6. Select Tasks & Logs→View All Scheduled Tasks. The All Scheduled Tasks page appears. Selectthe Monthly Contract and Warranty Collection task, and click Run Now. This ensures that all systemsdiscovered prior to the client registration have contract and warranty information collected initially.

After the task runs, HP SIM will automatically obtain Contract and Warranty Information from two tasks:

• Initial Contract and Warranty Collection — runs when HP SIM discovers new systems

• Monthly Contract and Warranty Collection — runs once a month.

Remote Support Pack setup 91



(Optional) To change the set of systems for which Contract and Warranty Information is obtained,create a new collection. Then edit the Monthly Contract and Warranty Collection task to replacethe Status Polling List collection with the new collection name. See the HP Systems Insight ManagerUser Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.htmlfor more information on creating collections.

7. Verify Contract and Warranty information in one of the following ways:

• Check the status icons in the CW column for All Systems, Remote Support Eligible, and othercollections. Select the icon to view the status.

• Select the Contract and Warranty Status link under System Status on the System page toview the details.






• Check All HP Service Events for Contract and Warranty expiration under the All HP Service

Events display. All HP Service Events is found under Service Events in the System and

Event Collections panel.

NOTE: The Contract and Warranty information provided depicts the current product warranty andmaintenance contracts you already have in place with HP. It is not a mechanism to order, upgrade, orextend your current service obligations and might be different from the information displayed in theRemote Support Entitlement Check which is covered in step 9.

NOTE: Steps 8 through 11 should be performed to ensure that Remote Support functionality is configuredproperly.

8. Check the Remote Support Eligible collection to verify that systems required to have remote support arelisted under this collection in the System and Event Collections panel.




In HP SIM, the Remote Support Eligible collection is created at the time of the Remote Support Clientinstallation. Any system that meets the criteria of the collection is automatically populated into thecollection. No user actions are required. These criteria can be viewed by selecting Customize in theSystem and Event Collections panel, selecting the collection, and then clicking Edit. HP does notrecommend that you change the information displayed, but this can help in troubleshooting remotesupport problems.

9. To customize and activate remote monitoring capabilities, select the Remote Support Services tabfrom the Remote Support Configuration and Services page and verify the Remote Monitoring

Enabled box is checked in the Remote Support System list to enable remote support for a given system.Unchecking this box disables remote support.

Ensure that a green check is in the Support Obligation column for enabled systems. Perform RemoteSupport Entitlement Checks by selecting a box under the Support Obligation column. This resultindicates:

• whether an event for this particular system would have a valid Service Obligation at the time thatthe Remote Support Entitlement Check is performed

• information on why the entitlement may not be valid




10. Set system properties by selecting Options→System Properties for all systems in the Remote SupportEligible collection, or selecting System Properties from the System Page for an individual system. Thisensures that individual systems or groups of systems can be entitled correctly for remote support andhave adequate information provided to HP to create a support case. This information is provided toHP only as needed to respond to customer inquiries and improve customer service.

Following are procedures to set up initial and subsequently discovered systems with common properties:

Select Options→System Properties→Set System Properties to set up the initial properties for a groupof systems. In Step 1, select Remote Support Eligible as the target collection and check the box Select

“Remote Support Eligible” itself . Click the Apply button to move to the Verify Target Systems screen.Remote Support Eligible will show as the target. Select the Next button to move to step 2, Set Properties. Toensure proper remote support, fill in the fields in the Contract and Warranty Information section, makingsure the fields marked with asterisks are all filled in. Then select the Run Now button to run the Set SystemProperties task to ensure all current systems in the Remote Support Eligible Collection have these properties




set. Write down these fields, or use the browser's print function to print the information, for use in the nextprocedure.

To propagate these properties to newly discovered systems, follow the same steps in the above procedurebut instead of selecting Run Now in step 2, select Schedule to move to step 3, Schedule Task. Select theWhen new systems or events are added to the collection option under When would you like this

task to run? At this point the task name will be changed to something like Set System Properties 1. Thisname can be changed if you choose. Select Done to ensure propagation of common properties for newsystems.




You can also edit these properties manually on individual systems by selecting the system in the RemoteSupport Eligible collection, then navigating to the Tools and Links tab and selecting Edit System

Properties.

The Product Description fields should not be changed since doing so may change whether the system ispart of the Remote Support Eligible collection and hence may affect the ability to obtain remote support forthat system. Serial number and product number should not be changed unless the acquired informationneeds to be superseded for some reason since this can also affect the remote support entitlement status.




See the HP Systems Insight Manager User Guide athttp://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more informationon setting system properties.






11. Send a test trap from a monitored system to test the connection between the monitored system, theCMS, and the HP Data Center server. This connects to the HP call handling system and should resultin a Work Flow Manager (WFM) support case being opened.

NOTE: This step is optional but recommended by HP to verify that communication and configurationsteps have been completed for proper remote support operations.

To send a test trap from a monitored system running either Windows or Linux:

a. Open up the All Systems view from HP SIM.

b. Select the monitored system in the System Name column.c. Select System Management Homepage under the System tab.

d. From the System Management Homepage, select the Settings tab.

e. For a Windows-based system, select SNMP and Agent Settings under SNMP Webagent, thenselect the Send Test Trap button under the SNMP and Agent Configuration panel to send thetrap.

For a Linux-based system, select SNMP Configuration under SNMP Webagent, then select theSend Trap button under the Test Trap section to send the trap.

Check All HP Service Events for Type 4 SOAP service incidents and verify the information under thenew Case ID and Case Status columns. All HP Service Events is found under Service Events inthe System and Event Collections panel.

• Verify links in Type 4 events for analysis details, case properties, and the customer self repair link.




• By default, OSEM will also send Type 3 events which are the older SNMP trap style events. Thiscan be useful in certain configurations, but usually will provide duplicate information. You caneither disable Type 3 traps as an option in OSEM Viewer's Internal Settings, or it can be disabled

in HP SIM by customizing the HP Service Events collection.

To customize reporting of service events in HP SIM perform the following procedures:

a. From HP SIM's System and Event Collections panel, select Customize. The Customize

Collections page appears in the main window.

b. Under Show Collections of , select Events from the dropdown list.

c. Select All HP Service Events.

d. Select Edit.

e. At the bottom, under Search for Events, two entries are displayed. Modify the last entry to "andevent type is."

f. Expand the HP Service Events tree to see the different event types that a user can select or deselect.

g. Select View and/or Save on the bottom right of the screen. View gives you a view of the collection

but is temporary. Save creates a permanent collection.




10 Migrating Insight Manager 7 Service Pack 2.3 to HPSystems Insight Manager 4.2

NOTE: To migrate from Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 5.0, InsightManager 7 Service Pack 2.3 must be upgraded to HP SIM 4.2 first. After this initial upgrade, follow theprocedure to upgrade HP SIM 4.2 to 5.0. See Chapter 11 “Upgrading HP Systems Insight Manager from

4.x or later ” for more information.

The HP Systems Insight Manager Data Migration Tool is used to migrate Insight Manager 7 data to HPSystems Insight Manager. The Data Migration Tool exports user-defined data from Insight Manager 7 byextracting it and storing the information in a portable format. The Data Migration Tool then imports thatuser-defined Insight Manager 7 data into HP Systems Insight Manager. The migration process transferscustom data, which includes the following:

• 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 must be manually recompiled)

In addition, received events and notices are archived.

NOTE: You must be running Insight Manager 7 SP2.3 to migrate to HP Systems Insight Manager 4.2. Ifyou are running a version of Insight Manager 7 earlier than Insight Manager 7 SP2.3, upgrade to InsightManager 7 SP2.3 before upgrading to HP SIM 4.2. If you have Insight Manager 7SP2, 2.1, or 2.2 installed,the migration process offers an automatic upgrade to Insight Manager 7 Service Pack 2.3. If you have a

version earlier than Service Pack 2, you are directed to the HP website to download the Softpaq that willenable you to upgrade to Insight Manager 7 SP2.3. See the Insight Manager 7 User's Guide for informationon upgrading from Insight Manager 7 to Insight Manager 7 SP2.3. See the Migrating from Compaq Insight Manager (WIN32) to HP SIM white paper at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more in-depth detail on this process.

Your system must also meet the operating system and SQL/MSDE requirements listed inChapter 2 “Installation overview and requirements”.

NOTE: The Data Migration Tool must be run by a user with full Windows administrative rights.

NOTE: The HP Performance Management Pack was part of the Insight Manager 7 SP2.3 installation. If itis detected on your system, a migration utility for transferring data 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 ran Insight Manager 7. As partof the in-place migration process, Insight Manager 7 is disabled and can only be re-enabled by uninstallingHP Systems Insight Manager and manually re-enabling Insight Manager 7. In-place migration preservesuser-defined data, including the Insight Manager 7 server certificate.

Remote migration This type of migration enables you to install HP Systems Insight Manager on a different

server than Insight Manager 7. The remote migration process leaves Insight Manager 7 running after data

Types of migration 101







has been exported and requires you to import the Insight Manager 7 and the Performance ManagementPack migration data files to your new HP Systems Insight Manager server. Remote migration preservesuser-defined data except the Insight Manager 7 Server certificate.

Performing an in-place migration1. Export the Performance Management Pack and Insight Manager 7 data:

a. Migrate from Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2 through the7.20 HP Management CD or by downloading the HP Systems Insight Manager 4.2 software. To

download the software, go to http://www.hp.com/go/hpsim, and click Download.b. Begin the migration process by launching setup.exe from the download package or from the

Management CD. Select Products>HP Systems Insight Manager >Install on the Insight Manager7 server. The HP Systems Insight Manager Welcome screen appears. The Welcome screen displayslinks to the following documentation:

• Readme (readme.txt)

• Release notes (hpsim-releaseNote.pdf)

• User guide (hpsim-userGuide.pdf)

A background setup screen appears showing that pre-installation is “In Progress.” If the PerformanceManagement Pack that was installed with Insight Manager 7 is detected on your system, thePerformance Management Pack Migration Utility for data export is launched.

c. Follow the screen prompts to completion before continuing with the Insight Manager 7 data export.On completion of the data export for the Performance Management Pack, setup detects that youare running Insight Manager 7 SP2.3 or later and automatically launches the HP Systems InsightManager Data Migration Tool. The Data Migration Tool dialog screen appears.

d. Click Next to continue.

e. Select Next to confirm data export to the following directory and file: C:\ProgramFiles\HP\Systems Insight Manager Data Migration Tool\user-data.dmt. Theexport of data begins.

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

g. Select the In-place migration (disable Insight Manager 7) radio button.

h. Click Next. The HP Systems Insight Manager Data Migration Tool export success screen appears

and indicates that Insight Manager 7 has been disabled.i. Click Finish to continue with the installation of the HP Systems Insight Manager components. See

Chapter 3 “Installing HP SIM on the Central Management Server (CMS) for the first time” fordetails. The background setup screen shows that pre-installation is “Done” and the installation isnow “In Progress.”

2. Click Finish. The background setup screen shows that installation is “Done” and the post-installation isnow “In Progress.” The import of Insight Manager 7 and the Performance Management Pack data hasautomatically begun.

After all the HP Systems Insight Manager components have been installed, the Insight Manager 7 DataMigration Tool dialog screen automatically appears.

3. Click Next. A data import screen appears, showing that the data will be imported from the following

directory and file: C:\Program Files\HP\Systems Insight Manager Data MigrationTool\user-data.dmt.

4. Click Next to start the Data Import. The process might take more than an hour depending on the amountof user-defined data and the configuration of the HP Systems Insight Manager. A status window showsthe progress.

5. When data import completes, click Next. A message appears, stating that you must log in to HP SystemsInsight Manager to complete the migration process by verifying user accounts, assigning authorizations,and enabling tasks and Automatic Event Handling rules.

6. Click OK.

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

If the Performance Management Pack was upgraded, then the Performance Management Pack Migration

Utility for data import is automatically launched.

102 Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2





8. Follow the screens to completion. The background setup screen shows the post-installation is “Done.”

9. Click Finish on the background setup screen, and reboot the system at this time if any HP SystemsInsight Manager components indicated the need for this.

NOTE: For an in-place migration the DMI Indication handler service should be disabled on the CMS.

Performing a remote migration

1. Export the Performance Management Pack and Insight Manager 7 data:a. Acquire HP Systems Insight Manager 4.2 by downloading the HP Systems Insight Manager softwarefrom http://www.hp.com/go/hpsim and selecting Download or through the 7.20 HP ManagementCD.

b. Start the migration process by launching setup.exe from the download package or from theManagement CD. Select Products>HP Systems Insight Manager >Install.

The HP Systems Insight Manager Welcome screen appears. The Welcome screen displays links tothe following documentation:

• Readme (readme.txt)

• Release notes (hpsim-releaseNote.pdf)

• User guide (hpsim-userGuide.pdf)

A background setup screen appears, showing that pre-installation is “In Progress.” If the PerformanceManagement Pack that was installed with Insight Manager 7 is detected on your system, thePerformance Management Pack Migration Utility for data export is launched.

c. Follow the screen prompts to completion before continuing with the Insight Manager 7 data export.On completion of the data export for the Performance Management Pack, setup detects that youare running Insight Manager 7 SP2.3 or later and automatically launches the HP Systems InsightManager Data Migration Tool. The Data Migration Tool dialog screen appears

NOTE: If Insight Manager 7 Service Pack 2, 2.1 or 2.2 is detected, the HP Systems InsightManager Data Migration Tool displays an option to upgrade to Insight Manager 7 SP2.3. Selectthis option and follow the screen prompts to install the Softpaq. When complete, launch setup.exe

again from the download package or from the Management CD, select Products>HP SystemsInsight Manager >Install again to start the export of Insight Manager 7 data.

d. Click Next to continue.

e. Click Next to confirm data export to the following file: C:\Program Files\HP\SystemsInsight Manager Data Migration Tool\user-data.dmt. The export of data begins.

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

g. Select the Remote migration (do not disable Insight Manager 7) radio button.

h. Click Next. HP Systems Insight Manager Data Migration Tool export success screen appears andinstructs you to copy the export file to the server on which HP Systems Insight Manager will beinstalled.

i. Click Finish to exit the Data Migration Tool. The background process shows pre-installation is“Done” and installation is “In Progress.”

j. Click Cancel from the Welcome screen for the HP Systems Insight Manager install. The backgroundsetup shows that both installation and post-installation are “Not Done.”

k. Click Finish on the background setup screen to close it.

l. Copy the file C:\Program Files\HP\Systems Insight Manager Data MigrationTool\user-data.dmt to a location where it can be accessed from the new HP SIM 4.2 server.

m. Copy the file PMP DMT installation directory\data\pmp.jar to a location where itcan be accessed from the new HP Systems Insight Manager 4.2 server. The PerformanceManagement Pack Data Migration Tool installation directory is usually c:\ProgramFiles\HP\Performance Management Pack Data Migration Tool.

n. Go to the server to be used for the new HP Systems Insight Manager, and launch setup.exe from

the download package or from the Management CD. Select Products>HP Systems Insight

Performing a remote migration 103





Manager >Install to start the HP Systems Insight Manager components installation. The backgroundsetup screen will show pre-installation is “Not Done” and installation is now “In Progress:”

o. Click Install on the HP Systems Insight Manager welcome screen to begin the installation of HPSystems Insight Manager components. See Chapter 3 “Installing HP SIM on the CentralManagement Server (CMS) for the first time” for details.

p. Click Finish when the installation is complete to close the HP Systems Insight Manager Installerwindow. The background set up screen shows installation is “Done” and post-installation is “NotDone.”

q. Click Finish on the background setup screen to close it.2. Import Insight Manager 7 and the 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 Systems InsightManager 4.2 server. The background setup screen will not display. The Insight Manager 7 DataMigration Tool dialog screen automatically appears.

b. Click Next.

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

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 an hour,

depending on the amount of user-defined data and the configuration of the HP Systems InsightManager. 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.exe to importthe Performance Management Pack data. Follow the screens to completion, pointing to the location ofthe pmp.jar file as noted during the export process.

4. If the Performance Management Pack 2.1 server licenses/logged data is migrated and after HPPerformance Management Pack 3.0 is installed, launch pmpshell.exe to import the PerformanceManagement Pack 2.1 server licenses/logged data. Follow the screens to completion, pointing to thePMP data file (pmp.jar) as noted during the export process.

5. Reboot the system at this time if any of the HP Systems Insight Manager components indicate the need.

104 Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2



11 Upgrading HP Systems Insight Manager from 4.x or laterHP SIM supports upgrading from HP SIM 4.0, 4.1, 4.2 to the current version HP SIM. This chapter providesthe steps to upgrading from HP SIM 4.x to HP SIM 5.x.

NOTE: The "\" at the end of each command line indicates that the rest of the command is on the nextline.

NOTE: If you have MSDE installed on a previous version of HP SIM, are using MSDE, and are upgradingto HP SIM 5.x, HP SIM 5.x requires that MSDE have the TCP/IP protocol enabled. Therefore, you mustenable the TCP/IP protocol when upgrading from HP SIM 4.x to 5.x.

1. Select Start>Run and enter svrnetcn.ext.

2. In the Disabled Protocols box, select TCP/IP.

3. Click Enable.

4. Click OK.

Upgrading from HP SIM 4.x or later1. Verify that HP SIM 4.x or later is running on the system.

2. If you have HP Instant Support Enterprise Edition (ISEE) Windows Client software A.03.95 or older,installed on your CMS AND you wish to install HP Service Essentials Remote Support Pack along withHP SIM 5.x, then you must remove the ISEE client software first. To remove ISEE complete the followingsteps:

a. Select Start>Settings>Control Panel> Add/Remove Programs.

b. Select HP Instant Support Enterprise Edition Client from the list of installed programs, thenclick [Change/Remove].

3. If you have an Oracle database, install the Oracle JDBC driver, version 10.1.0.2.0 or newer. See theOracle documentation, or visit the Oracle website athttp://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.htmlfor additional information.If you have an older version of the JDBC driver already installed, do the following:

a. Stop HP SIM.

b. Search for a file named ojdbc14.jar in the [installdir]/lib and [installdir]/jboss/server/hpsim/libdirectories and remove it from any locations where it is found.

c. Download the new driver from the Oracle website athttp://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html.

d. Copy the JDBC driver file (ojdbc14.jar) to the [installdir]/lib and[installdir]/jboss/server/hpsim/lib directories.

4. Download the software, or install it from the HP Management CD.

To download the software, see http://www.hp.com/go/HP SIM, and on the upper-left of the pageunder HP management software, click Download. The HP SIM Download Page appears. Under HP

Systems Insight Manager and related components, select HP SIM-Windows>Download latest

version of HP SIM - Windows for a full product install.

To install the software from the Management CD, place the CD in the CD-ROM drive. The CD has anautorun feature that launches a license agreement. Agree to the license agreement, and click theProducts tab. Click Install under HP SIM to launch the Installer. Or click the Products tab, clickExplore CD, and then run setup.exe located at \HP SIM\win_ia32\ to launch the Installer.

The Welcome to the HP Systems Insight Manager Installer window appears. HP SIM examinesthis system for local instances of MSDE and SQL Server 2000.

Note: Click the drop-down selection box in the upper-right corner of any dialog box to view the HP SIMInstallation and Configuration Guide, Readme or Release Notes.

5. Click Next. The System Inspection window appears. The system is inspected for a previous versionof HP SIM and/or a local database. The Database Configuration window appears.

Upgrading from HP SIM 4.x or later 105



http://www.hp.com/go/HP%20SIM

http://www.hp.com/go/HP%20SIM





6. The database information of the existing HP SIM install is pre-populated. This information cannot beedited. Provide the correct password for the account , and click Next to proceed.

7. When the Select Installation Type window appears, select Typical to install the included componentswith minimal user interaction listed under the Available Components for Install or select Custom toselect the individual components under the Available Components for Install and configure themduring installation.

Custom installationTypical installation Available components for install

IncludedIncludedSystem Management HomepageOptionalIncludedOpenSSH Services 4.3p2

OptionalIncluded WMI Mapper

IncludedIncludedHP Systems Insight Manager

OptionalIncludedHP ProLiant Essentials Performance Management Pack

OptionalIncludedHP Version Control Repository Manager

OptionalIncludedHP ProLiant Essentials Virtualization Management Software

Note: If a component is not listed as being available for installation on the CMS, then the HP SIM installshell has determined one of the following:

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

• A newer version of the component is currently installed.

If the component that is present on the CMS is an older version than what is bundled with the HP SIMinstall shell and it supports an in-place upgrade, it appears in the component list.

Typical upgrade1. Typical upgrades all the components which are marked included under the Available Components for

Install. Click Next, the Service Account Credentials window appears. The Domain and user namefields limit to the HP SIM service account credentials of the existing install. These fields cannot be edited.

2. Enter the password for this account. Click Next, the Summary window appears with the components

that are to be installed.3. Click Install to initiate the installation process. This process installs all the products listed in the Selected

Components table. The Status window appears. As each component is being installed, it states "InProgress" beside the component's name. After the component has installed, it states "InstalledSuccessfully."

4. After all of the components are installed, click Next, the Install Complete window appears. You aregiven the option to reboot. The following message appears: For this upgrade install, HPrecommends that you configure the System Management Homepage to use operatingsystem authentication for HP Version Control Agent access to Version ControlRepository Manager, and then re-configure the servers running HP VersionControl Agent to use the new account. If these actions are not taken,pre-7.20 Version Control Agents will access your upgraded Version Control

Repository via legacy HTTP Server account access. For more information,refer to the Version Control Installation Guide athttp://h18013.www1.hp.com/products/servers/management/agents/documentation.html/.

5. Click Finish to allow the system to reboot. This completes the typical upgrade process. See "Next steps"for more information.

Note: For more information regarding where the System Management Homepage default settings arestored during a Typical installation and how to change them, see the System Management Homepage Installation Guide at http://h18013.www1.hp.com/products/servers/management/agents/documentation.html.

106 Upgrading HP Systems Insight Manager from 4.x or later

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





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



Custom upgrade1. Click Next, the Software Selection window appears. This window displays the complete list of the

available components with a checkbox next to each one. If the checkbox is selected and disabled, thecomponent is deemed a mandatory component and cannot be cleared. The amount of required diskspace is also listed for each component. Select the components you wish to install.

2. Click Next to verify that enough disk space exists for the selected components. If enough space exists,the Service Account Credentials window appears. The Domain and User name fields will default tothe installing account credentials. Enter the password for this account.

3. Click Next. The Summary window appears.

NOTE: This user account is used to run the HP Systems Insight Manager service.

4. Click Install to initiate the upgrade process. This process installs all the products listed in the Selected

Components table. The Status window appears. As you install each component, it states "In Progress"beside the component's name. After the component has installed, it states "Installed Successfully."

5. Install the System Management Homepage:

a. The System Management Homepage Setup window appears. The InstallShield Wizard guidesyou through the install of System Management Homepage. Click Next. The Operating Systems

Groups window appears.

Note: If at any time during the install of System Management Homepage you click Cancel

, theinstallation and setup of the System Management Homepage ends.

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

c. Enter the group name of an operating systems group in the Group Name field. Click Add. Thegroup name is added. A maximum of five entries can be added for each group level. Click Next

to continue.

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

d. From the User Access window, configure the System Management Homepage for the followingaccess types:

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

• Select Local Access Anonymous or Local Access Administrator to set up the SystemManagement Homepage to automatically grant local IP addresses at the selected accesslevel.

Caution: Selecting Local Access with Administrator privileges provides any users with accessto the local console full access without prompting them for a user name or password.

e. Click Next. The Trust Mode window appears.

f. Select the level of security you want to provide from one of the three trust modes:

• Trust By Certificate

Select Trust By Certificate, and click Next. The Trusted Certificates window appears.The Trusted Certificates window allows trusted certificate files to be added to theTrusted Certificate List.

i.

ii. Click Add File to browse and select any certificates to be included in the TrustedCertificate List. The Select File window appears. If an invalid file name is entered inthe file name field, an error message appears, indicating the file does not exist. ClickOK to select another file, or click Open to add the file to the Trusted Certificate List.The Trusted Certificate List appears. Click Next.

Note: If you click Next without adding any certificates to the list, and no certificates existfrom a previous installation, a message appears, indicating that if you do not specifyany trusted certificates, HP SIM cannot access the HP Insight Management Agent on thissystem. Click OK if you do not want HP SIM to access the Insight Management Agenton this system, or click Cancel to close the window and add the trusted certificates tothe list.

Note: The Trust By Certificates option enables the System Management Homepage

system and the HP SIM system to establish a trust relationship by means of certificates.

Custom upgrade 107



This mode is the strongest method of security because it requires certificate data andverifies the digital signature before enabling access.

or

i. Click Import. The Import Server Certificate window 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 Trusted

Certificate List, click Accept and the certificate is added to the Trusted Certificate

List, or click Cancel if you do not want to add it to the Trusted Certificate List. TheTrusted Certificate List appears. Click Next.

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

Note: To delete a certificate, select the certificate, and click Delete. The selected certificateis removed.

v. From the IP Binding window, select the IP Binding checkbox if you would like to bindto IP addresses that match a specific subnet and mask. Click Next.

vi. From the IP Restricted Logins window, select the Enable IP Restricted Logins


• Trust By NameSelect Trust By Name. Click Next. The Trusted Server window appears. Enter thenames of the servers you want to trust.

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

i.

By Name mode sets up the System Management Homepage to only accept certainrequests from servers with the HP SIM names designated in the Trust By Name field.The Trust By Name option is easy to configure and can prevent non-malicious access.For example, you might want to use the Trust By Name option if you have a securenetwork, but your network has two groups of administrators in two separate divisions.The Trust By Name option would prevent one group from installing software to thewrong system. This option does not verify anything other than the HP SIM server name

submitted.Note: The server name cannot contain the following characters:

~ ! ` @ # $ % ^ & * ( ) + = " : ' < > ? , | ;

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

Note: If you click Next without adding any server names to the list, an error messageappears, indicating that if you do not specify any trusted server names, HP SIM cannotaccess the Insight Management Agent on this system. Click OK to proceed withouttrusting any systems, or click Cancel to close the window and add server names to thelist.

Note: To delete a certificate, select the certificate and click Delete. The selected certificateis removed.

iii. From the IP Binding window, select the IP Binding checkbox if you would like to bindto IP addresses that match a specific subnet and mask. Click Next.

iv. From the IP Restricted Logins window, select the Enable IP Restricted Logins


• Trust All

Select Trust All. Click Next. The IP Binding window appears.i.

ii. Select the IP Binding checkbox if you would like to bind to IP addresses that match aspecific subnet and mask. Click Next.

Note: The Trust All option leaves your system vulnerable to security attacks and sets up

the System Management Homepage to accept certain requests from any server. For




example, you might want to use Trust All if you have a secure network, and everyonein the network is trusted.

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 you mightnot be able to connect to the System Management Homepage.

The IP Restricted Logins window appears. The IP Restricted Logins window enablesyou to select specific IP addresses or IP address ranges to include or exclude from gaininglogin access. Although optional, the System Management Homepage can restrict login

access based on the IP addresses of the machine attempting to gain access.iii. Select Enable IP Restricted Logins, and click Next. The IP Addresses to Include

window appears. This window enables you to specify the IP address or IP address rangesto grant 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 Restricted

Logins window. Enter the single address in the first box.

iv. In the Include field, enter a beginning IP address to which you want to grant loginaccess. In the To field, enter an ending IP address to which you want to grant login

access. All IP addresses that fall between the beginning and ending IP addresses aregranted login access. Click Add. The IP address or IP address range is added to theExclusion list. If necessary, select an IP address or IP address range, and click Delete

to remove it from the Exclusion list. Click Next.

Note: If you entered an invalid IP address or IP address range, an error message appearsindicating the IP address is invalid. Click OK. Enter a valid IP address or IP addressrange, and click Add again. The IP Addresses to Exclude window appears.

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

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

access. vi. Click Add. The IP address or IP address range is added to the Inclusion list. If necessary,select an IP address or IP address range, and click Delete to remove it from the Inclusion

list. Click Next.

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

Note: If you select Next without adding any IP addresses to the Include or Exclude

lists, a warning message appears, stating, IP Restricted Login checkbox willbe marked as disabled. Do you want to proceed without addingany IP Address restrictions? If you click OK, the IP Restricted Login optionon the IP Restricted Login window is cleared.

The Summary Panel appears. The Summary Panel lists the location where the SystemManagement Homepage is installed, the amount of space the installation requires, and the summaryof the options that you specified during the installation.

g. Click Next. The installation process is started. Click Finish to exit the wizard.

Note: If HP SIM is installed after System Management Homepage is installed, the SystemManagement Homepage 2048-bit key pair is replaced with the HP SIM1024-bit key pair.

6. Install OpenSSH:

a. On the Welcome to the OpenSSH Services Setup Wizard, click Next. The Select Destination

Location window appears. Setup installs OpenSSH into the following folder C:\Program

Custom upgrade 109



Files\OpenSSH. To change the location, use the Browse button. Click Next. The OpenSSH

Service Log On As User window appears.

b. Enter your account password. The User name and Domain fields are prepopulated. Although thesefields are prepopulated, you can change these values to specify any user you choose. However,the account credentials you do choose must have local administrator rights (be a member of thelocal "Administrators" group.) Click Next. The Ready to Install window appears.

Note: The OpenSSH Service Log On As User window appears only if installing on a WindowsXP or Windows 2003 system. If you are installing on a Windows 2000 system, the OpenSSH

Service runs as "localsystem" and does not ask for credentials.c. Click Install to continue with the installation.

d. After installing OpenSSH, if prompted, click No, I will restart the computer later .

e. Click Finish.

Note: The local security policy is modified to give you the following rights: log on as a service,create a token object, and replace a process level token. See the HP SIM Readme at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more details.

7. Install the WMI Mapper:

a. On the Welcome to the Pegasus WMI Mapper Setup Wizard, click Next. The End-User

License Agreement window appears.

b. After reading the license agreement, click I accept the terms in the License Agreement. ClickNext. The Choose Setup Type window appears.

c. Select the setup type. (The basic requirement for HP SIM is Typical installation. If you select Typical,omit step d.)

d. Select the default location C:\Program Files\The Open Group\WMI Mapper or changethe destination location using Browse. Click OK. Click Next. The Ready to Install windowappears.

e. Click Install to continue with the installation.

f. Click Finish.

Note: For Windows XP SP2 or Windows 2003 SP1 or later, COM security is updated to allowremote access and activation by everyone and anonymous users. See the HP SIM Readme at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more details.

8. Install HP Systems Insight Manager:

a. When the Welcome to the HP Systems Insight Manager Setup Wizard appears, click Next.The Select Destination window appears.

b. Select or enter a different folder name using Browse. Click OK>Next.The Select Start Menu

Folder appears.

c. Select or enter a different folder name using Browse. Click OK>Next. The Ready to Install windowappears.

d. Click Install. The Install Progress window appears.

e. Click Finish when the installation is complete to close the HP Systems Insight Manager Installer

window.

f. Once the HP SIM installation is complete, the Service Essentials Remote Support Pack window

appears. The configuration of the ISEE_CMS_SWMAGENT completes automatically. This processprovides the files needed so that you can access the Service Essentials Remote Support Packapplication and run the installation. The Service Essentials Remote Support Pack is not active untilit is customized to your enterprise. See the HP Remote Support Software Manager Initialization & Usage Guide located at http://docs.hp.com/en/5991-7446/5991-7446.pdf for configurationinstructions.

9. Install the HP ProLiant Essentials Performance Management Pack:

Note: PMP does not support a remote MSDE database. For PMP to connect to a local or remote Oracledatabase, install the Oracle client application on the server on which PMP is installed.














Note: HP BladeSystem Integrated Manager in HP Systems Insight Manager supports PMP only on Windows CMS's running SQL Server.

▲ Optional, if you plan to use an Oracle database. Install the Oracle client. If not, proceed to theHP ProLiant Essentials Performance Management Pack install step a.

a. Insert the Oracle 9i Release 2 CD in the CD-ROM drive of the server on which PMP is installed.

b. At the autorun, click Install/Deinstall Products.

c. At the Welcome screen, click Next.

d. Enter the source and destination path for support files, and click Next.

e. Select Oracle 9 Client 9.2.0.1.0, and click Next.

f. Select Custom, and click Next.

g. In the Available Product Components, select the following options:

• Oracle Network Utilities 9.2.0.1.0

• Oracle Database Utilities 9.2.0.1.0

• SQL *Plus 9.2.0.1.0

• Oracle Windows Interfaces 9.2.0.1.0

• Oracle Call Interfaces 9.2.0.1.0

Click Next.

h. Specify the destination location of the JRE 1.1.8.16.0 or select the default location, and click Next.i. Specify the Port number or select the default Port, and click Next.

j. Verify the installation summary, and click Install.

k. When prompted, insert the next Oracle CD in the CD-ROM drive, and click OK.

l. When prompted, insert the next Oracle CD in the CD-ROM drive, and click OK.

m. At the Oracle Net Configuration Assistant screen, click Cancel.

n. When prompted to cancel the Oracle Net Configuration Assistant, click Yes.

o. Click OK when the error message appears.

p. At the Configuration Tools window, click Next.

q. At the End of Installation screen, click Exit.

r. Click Yes to confirm.

Note: During the installation of the HP ProLiant Essentials Performance Management Pack, the followingwarning appears: "Warning: As part of PMP installation the HP SIM service mustbe stopped and restarted." Click OK to stop the service and continue PMP installation or clickCancel to abort the installation.

The Welcome to the HP ProLiant Essentials Performance Management Pack Setup Wizard appears.Click Next. The Service Account Credentials window appears.

a. Enter your account password. Click Next.

b. If you are using an Oracle database, the Database Configuration screen appears. Enter yourvalid user name, password and database name, and click Next.

c. The HP ProLiant Essentials Performance Management Pack Installing window appears andinstallation begins.

d. Click Finish to exit the HP ProLiant Essentials Performance Management Pack setup.

10. Install the HP Version Control Repository Manager:

a. When the HP Version Control Repository Manager Setup window appears, click Install. TheHP Version Control Repository Manager Setup Repository Directory window appears.

b. Select the directory from which HP Version Control Repository Manager will retrieve support packinformation using the Browse button. This directory must be manually created later if it does notexist. Click OK. Click Next. The HP Version Control Repository Manager Automatic Update

window appears.

c. Select the Enable Automatic Update checkbox to enable automatic downloading of HP ProLiantSupport Packs and components at a specified interval and time.

Custom upgrade 111



d. Click Finish. Installation of HP Version Control Repository Manager proceeds and completes.

Note: If the HP Version Control Agent is configured to use the HP Version Control RepositoryManager, warning appears: "At least one HP Version Control Agent must beconfigured to use the HP Version Control Repository Manager." If noneare configured, verify the HP Version Control Agent settings to ensureproper operation of the automatic update feature. Click OK.

e. Click Close.

11. Install the HP ProLiant Essentials Virtualization Management Software:

Note: During the installation of the HP ProLiant Essentials Virtualization Management Software, thefollowing warning appears: "Warning: The Virtualization Management Softwareinstallation requires HP SIM and database services to be running. Duringinstallation, the HP SIM service will be restarted." Click OK to start the HP SIMstatus check.

a. On the Welcome to the HP ProLiant Essentials Virtualization Management Software Setup

Wizard, click Next to continue with the installation. The Available Components window appearswith the following components to be installed:

• Virtual Machine Management Pack

• Server Migration Pack

b. Click Next to continue.c. The Service Account Credentials window appears.

d. Enter your account password, and Click Next. Installation begins. The VMware VirtualCenter

Settings appears. Select one of the following:

• Configure VMware VirtualCenter Setting later

• Configure VMware VirtualCenter Setting now

e. If you select to configure VMware VirtualCenter Setting now, enter your password and click Next.If you decide to configure at a later time, select Options>Virtualization

Management>Security>VMware VirtualCenter Settings from the HP SIM menu.

The Completing the HP Virtualization Management Software Setup Wizard window appears.

f. Click Finish to exit setup.Note: For Oracle, if you are installing the HP ProLiant Essentials Virtualization Management Softwareand want to connect to a local or remote Oracle database, enter your password and .jar file locationon the Database Configuration screen. The HP ProLiant Essentials Virtualization Management Softwaremust be installed in an empty Oracle database schema. If Oracle is used as your primary HP SIMdatabase, an Oracle database must be created manually with the name VMMV21 before continuingwith the migration. HP ProLiant Essentials Virtualization Management Software database installationmay be omitted if the HP ProLiant Essentials Virtualization Management Software database alreadyexists in the specified schema. Click Yes to bypass HP ProLiant Essentials Virtualization ManagementSoftware database installation and use the current database. Click No to specify a different databasename. For more detailed information, see the HP ProLiant Essentials Virtualization Management Software User Guide at http://www.hp.com/servers/proliantessentials/vmm.

12. The Status window appears again, after all components have been installed, they will have an installedstatus. Click Next.

13. Click Finish to complete the installation. If any of the components indicated that a reboot is necessary,your system automatically reboots after you click Finish.

Note: When installing HP SIM, CMS host name that exceeds 15 characters is truncated, and the truncatedname must be used to complete the installation. After the install, two administrator accounts are created.One account includes the original host name\administrator and the other account includes the truncatedhost name\administrator. To log in, use the original host name in the Domain field on the Sign in page.

Silent upgradeUpgrading HP SIM from the command line with an .xml file.






A silent.xml file resides in the same directory as setup.exe. This text file can be edited with any text editor.If upgrading HP SIM from the CD, copy the silent.xml to a location where the file can be edited. Ifupgrading HP SIM from the web, then after extracting the installation program, edit the silent.xml fileand launch the setup in Silent mode. The silent.xml file contains the paramaters for the upgrade process.

The option to perform a Silent upgrade is available through a command line installation. A silent installoccurs when “setup.exe” is launched with the command line options for a Silent install.

Execute:

setup.exe –s “<path to silent file>” –svcpw “<service password>” –dbpw

“<database password>”

Note: In the Upgrade mode, the svcpw and dbpw passwords provided should be that of the existing installsHP SIM server account and database account respectively. The install will take the existing installationlocations of HP SIM and partner components.

Database information: Set <installMSDE>.

In the upgrade mode this option is ignored; the installer does not install MSDE on the local server even if settrue. The database information of the existing install will be used.

<dbUserName>

Provide the database user account information from the existing HP SIM install.

<dbDomain>

Provide the domain for the user account.<dbHost>

Provide the database server name or IP address of the existing HP SIM install.

Note: Upgrades of HP SIM using silent.xml does not support upgrades from HP SIM configured to anoracle database.

<dbInstance>

Provide a valid existing instance name of the existing HP SIM install.

<dbName>

Provide the valid database name of the existing HP SIM install.

<dbPort>Use default 1433 or provide a valid port. HP SIM service Information:

<svcuserName>

Provide the user account of the existing HP SIM install.

<svcDomain>

Provide the domain for the user account. Installation Location:

<baseInstallLocation>

and


The silent install uses the previous HP SIM installation location on the target system.

<allowReboot>

Set this to true or false as desired. A server reboot is recommended after upgrading HP SIM and partnercomponents. The silent.xml lists all the components with their product IDs for install. Set the

<install>

value to true if you want to upgrade that particular component.

Note: HP SIM and System Management Homepage are always be upgraded even if their

<install>

is set to false.

IMPORTANT: For a Silent upgrade, the service or database user name containing special characters, suchas: &, <, &, <, >, ', " must be escaped appropriately as below in the silent.xml file:

Silent upgrade 113



& &

< <

> >

' '

" "

For example, for a user name such as user&1 , the entry in silent.xml would be user&1.

For a silent install/upgrade embedded quote ( " ) character in service or database password is not supported.

The installation/upgrade status of HP SIM and selected components are logged in the HP SIM.log andsilentstatus.xml files. Both files are created in the root of the system drive.

Next steps After upgrading to HP SIM 5.0, sign in to HP SIM, and run the Daily Device Identification task to ensure thatall your associations are updated correctly.

To run the daily Identification task:

1. Select Tasks & Logs>View All Scheduled Tasks. The All Scheduled Tasks page appears.

2. Select the Daily System Identification task.

3. Click Run Now.




12 Uninstalling HP Systems Insight Manager

Uninstalling HP Systems Insight Manager from a Windows systemFrom the control panel, use the Add/Remove Programs feature in Windows, and complete the followingsteps to remove HP Systems Insight Manager and its dependencies:

1. Select HP Systems Insight Manager , and click Remove. If you want to uninstall HP Systems Insight

Manager, click Yes. Click No to cancel the uninstall.Note: Removing HP Systems Insight Manager does not remove its database files. If you plan to reinstallHP Systems Insight Manager, you do not have to rename or remove the old database.

If you clicked Yes, the HP Systems Insight Manager Component Uninstall window appears. Thiswindow lists some of the installed components each with a checkbox. The components listed for uninstallare: OpenSSH Services 4.3p2, HP Performance Management Pack, and HP Virtualization

Management Software.

Note: The dependent components like HP Performance Management Pack and HP Virtualization

Management Software are selected by default, and these selections cannot be changed. The OpenSSH

Services 4.3p2 may be unselected from uninstallation.

2. Click Next. If you want to cancel the uninstallation, click Cancel.

Note: The components listed in the HP Systems Insight Manager Component Uninstall windowcan also be uninstalled individually from the Add/Remove Programs feature. But System Management

Homepage, HP Version Control Repository Manager , Pegasus WMI Mapper , and MSDE can beuninstalled only from the Add/Remove Program in the Control Panel.

The HP Virtualization Management Software Uninstall box appears

3. Click OK to uninstall. The HP SIM status check is complete.

4. Click Yes to proceed with the HP Virtualization Management Software uninstallation. HP VirtualizationManagement Software was successfully removed from your computer.

5. After uninstalling the selected components, the HP Systems Insight Manager Component Uninstall

window appears. Proceed with the HP SIM uninstallation. The HP SIM uninstall progress screen appears.On completion of HP SIM uninstall, a window prompting for system reboot appears. HP recommends

reboot the system to complete the uninstall process.

Uninstalling HP Systems Insight Manager from a Windows system 115



13 Using the graphical user interfaceHP Systems Insight Manager provides a browser-based GUI.

Accessing the GUIThe graphical user interface (GUI) can be accessed from http://localhost:280/ with any network client thatis running a supported web browser.

▲ Required web browsers

• For Windows:

• Microsoft Internet Explorer 6 with Service Pack 1 or later

See the following note about the required security options.


Note: For all Windows Internet Explorer browsers, you must have the SSL 3.0 or TLS 1.0 browsersecurity options enabled for HP Systems Insight Manager to work properly.

• For HP-UX:


To download, refer to http://www.hp.com/go/firefox.

• For Linux:


Using Internet Explorer 7HP SIM is supported on Internet Explorer 7 (IE7). However, the wording of Microsoft's SSL certificate warningmessage has changed.

When you browse to an HP SIM server for the first time using either IE6 or IE7, an SSL certificate warningis displayed that begins, "There is a problem with this website's security certificate." This warning occurs

because HP SIM is configured with a self-signed SSL certificate that is generated on the server at the time ofHP SIM installation.

IE6 concludes its message with, "Do you want to proceed?"

IE7 concludes its message with, "We recommend that you close this webpage and do not continue to thiswebsite."

You need to proceed in both cases. The same level of security exists whether you are using IE6 or IE7, butIE7's warning message uses stronger wording.

Graphical user interface featuresThis section describes the GUI features. The following figure is a sample screen shot of the GUI.

Accessing the GUI 116

http://localhost:280/

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

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

http://localhost:280/



The GUI includes the following six regions:

1. Banner The banner provides a link to the Home page, a link to Sign Out of HP SIM, and displaysthe user that is currently signed in. Click the minimize icon in the top right corner to minimize the banner.To maximize the banner, click the maximize icon.

2. System Status panel This panel provides uncleared event status, system health status information,and an alarm to notify you of certain events or statuses. The System Status panel can be customizedfor your environment. If you do not need to view this panel at all times, you can collapse it by clickingthe minus sign in the top right corner of the panel. To expand the panel, click the plus sign. If theSystem Status panel is collapsed and an alarm is received, the panel expands to show the alarm.The panel can be enlarged by clicking the Open in new window icon ( ) to display a separate largewindow that can be resized and viewed from across a room without sitting at the HP SIM terminal.

3. Search panel The search feature enables you to search for matches by system name and commonsystem attributes. You can also perform an advanced search for matches based on selected criteria.To speed the search process, as you enter system information in the search box, a dropdown list appearslisting systems that begin with the text you are entering. You can select from the dropdown list or continueto enter the information. See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for information aboutsearch criteria. If you do not need to view this panel at all times, you can collapse it by clicking theminus sign in the top right corner of the panel. To expand the panel, click the plus sign again.

4. System and event collections System and event collections enable you to view all known systemsand events in a specific management environment. A collection can be private, visible only to its creator,or shared, visible to all users. HP SIM ships with default shared collections only. See the HP Systems Insight Manager 5.1 User Guide at http://h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for information about customizing and creating new collections.

Graphical user interface features 117











5. Menus The HP SIM menus provide access to tools, logs, software options, and online help. TheOptions menu is primarily for users who administer the HP SIM software. If you lack authorization touse these tools, you might not be able to access certain menus.

6. Workspace The workspace displays the results of your latest request. It can contain a collection, tool ,or report. Some tools launch a separate browser window or X Window terminal instead of displayingin the workspace . This area contains the Home page when you sign in to HP SIM. By default, theintroductory page is the Home page. The introductory page provides information and tips about HPSIM and links to frequently used features. You can customize HP SIM to display a different page as theHome page. See “Customizing the Home Page” for information on selecting a different introductorypage.

The four default sections on the introductory page include the following:

• Do this now to finish the installation: This section only appears if the following conditions aremet:

• The user has full configuration rights .

• The user has not disabled this section from the Home Page Settings page.

• Monitor This section provides links to common monitoring tasks, including locating and trackingsystems and events .

• Manage This section provides links to frequently used tools and features available from the

menus above the workspace. These links provide access to inventory reports, software and firmwaredeployment, discovery , event handling, integrating custom tools, and authorizations .

• Did You Know You Can...? This section provides useful tips and shortcuts, including where youcan learn more about HP products, service offerings, and software.

This section appears if you have not disabled it from the Home Page Settings page.

Customizing the GUI

Customizing the Home PageCustomize the HP Systems Insight Manager Home page to select which page displays when HP Systems

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 canaccess 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 collection view

Note: The default introductory page is only available when it is set as the Home page. If you want toview 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 on the pageby selecting or clearing the following options:

• Show "Do this now to finish the install" frame. If selected, this section appears on the Home

page.

• Show the "Did You Know?" image. If selected, the image in the bottom right corner of the Home

page appears.

118 Using the graphical user interface



Customizing the System Status PanelCustomize the System Status panel to display the following status information:

• Uncleared Event Status A count that indicates the number of uncleared event statuses that are Critical,Major, Minor, and Normal for any given system collection. Each number is a hyperlink to a detailedlist of events with that particular status. By clicking the number, an event collection appears with thoseparticular events and their corresponding systems.

• Health Status A count that indicates the number of systems, in a given system collection, that have

a system health status that is Critical, Major, Minor, and Normal. Each number is a hyperlink to adetailed list of systems with that particular status. By clicking the number, a system collection appearswith those particular systems. Health status is not shown by default but can be configured to appear.

• Alarm An alarm can be customized to appear for specific criteria for any given system collection.The alarm alerts you that a particular criterion has been met by one or more systems in that collection.For example, you might receive an alarm that a storage system has a critical uncleared event, or criticalhealth status. Because the System Status panel is continually updated, the alarm appears until theevent is cleared, the system is removed from the collection, or the alarm customization is changed sothat it no longer applies. If the System Status panel is collapsed, and an alarm occurs, it opensautomatically so that the alarm is visible. You can collapse the panel, but it continues to open as longas the alarm is relevant. To have the panel remain collapsed, you must clear the offending event orsystem status or reconfigure the status display to no longer display alarms.

• Legend of status icons To display a list of status icons, click Legend in the System Status panel.Legend information appears in a separate window and remains open until you close it.

To customize the System Status panel:

1. Click Customize in the upper-right corner of the System Status panel. The Customize System Status

page appears.

2. Select the first Show summary of , and select uncleared event status or health status.

a. Select the system collection All Systems, or select another system collection from the dropdownlist.

b. Edit the Label if desired.

3. Select the second Show summary of , and select uncleared event status or health status.

a. Select the system collection All Systems, or select another system collection from the dropdownlist.

b. Edit the Label if desired.

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

a. Select the Condition.

b. Select the system collection All Systems, or select another system collection from the dropdownlist.

c. Edit the Label if desired.

5. Click OK to save changes.

Note: Clicking Restore Defaults returns the customization screen to its default condition: only theuncleared event status appears in the banner. Health status and the alarm are disabled. All personalizedinformation is removed.

The System Status panel can be enlarged to enable you to monitor system and event statuses. Click theOpen in New Window icon on the System Status panel title bar and the status panel pop-up window isdisplayed. The window can be resized by clicking and dragging the sides of the window. To close thewindow manually, click the Close Window icon. Otherwise, the window is closed if the HP Systems InsightManager (HP SIM) window is closed or refreshed, or you log out of HP SIM.

The enlarged status panel window mimics the System Status panel. Whenever a status changes there, thepop up window is updated. Clicking one of the status values brings up the main HP SIM window and thecorresponding collection is displayed. For example, if you clicked the Major status value, the All MajorSystems table view page is displayed. This window can be customized using the options for customizingthe System Status panel.

Customizing the GUI 119



14 Using the command line interfaceHP Systems Insight Manager provides a command line interface (CLI) in addition to the graphical user interface (GUI). Many functions available in the GUI are also available through the CLI.

Logging in to the CLI Access the HP Systems Insight Manager CLI directly on the CMS or from any network client using SSH client

software.

NOTE: Only administrators have command line access to HP Systems Insight Manager on a WindowsCMS. For security reasons, administrators should not modify the access control settings put in place by theinstaller.

Logging in directly on the CMS1. Log in to the CMS using a valid user name and password ( SSH system name ).

HP SIM grants authorizations based on your operating system user login.

2. Open a terminal window or a command prompt window to execute HP SIM commands.

Using an SSH client remotelyThe preferred way to log in remotely is using an SSH client. Telnet and rlogin work, but neither provides asecure connection.

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

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

HP SIM grants authorizations based on your operating system user login.

manpages

Viewing manpages on Windows systemsThe HP SIM Windows manpages are available in the following folder: HP\Systems InsightManager\hpwebadmin\webapps\mxhelp\mxportal\en\manpages . Double-click a manpage file toview the contents in a web browser.

Logging in to the CLI 120



15 Configuration optionsSeveral configurable parameters in HP SIM that are not available from the GUI. These parameters can onlybe configured by editing a configuration file on the CMS.

NOTE: All HP SIM parameters have been set to predefined values that are appropriate for most situations.These parameters should only be changed if you are experiencing issues with the default values.

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

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 SIM is not installed in the default location.

These files follow the format of a Java properties file. Therefore, the keys in these files are case-sensitive. Inaddition, the backslash (\) must be represented by a double-backslash (\\). For more 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 SIM audit log configuration”

• “Lifetimes for entries on the Task Results Page”

CPU utilization during data collection

OverviewThe data collection task runs many threads in parallel to overlap computing and database operations withthe wait for managed systems to respond. On slower systems, this could potentially saturate the CPU forsome time, depending on the processor speed of the CMS system and the number of systems being collected.

Therefore, HP SIM provides some strategies to lessen the CPU usage.

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 separate data 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 substantial portionof the CPU load is consumed by the database during data collection. This option is only supported witha Windows CMS.

• Lower the DataCollectionThreadCount parameter in the globalsettings.props file. Thisparameter defaults to 3. Lowering it to 2 or 1 reduces the CPU demand of data collection tasks, but it

increases the time required to complete the tasks.

GUI time-out policy

OverviewHP SIM provides two alternative time-out policies. The first time-out policy is for environments in which HPSIM is used to monitor system status, which is called the monitor time-out policy, and it is similar to the policyused by Insight Manager 7. The second time-out policy is more strict and will time-out inactive users. This iscalled the active time-out policy 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 user has a webbrowser window open displaying the HP SIM GUI. Closing the browser or navigating to another web page

CPU utilization during data collection 121

http://java.sun.com/

http://java.sun.com/



starts the timer for the time-out period. The default time-out period is 20 minutes. Users must use some othermeans to protect an unattended session from illegal use, such as password-protected screen savers.

Active time-out policy The active time-out policy only keeps sessions alive if the user is actively using theGUI, such as clicking on links and buttons. Display and refresh of the banner is not sufficient to keep thesession 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 thesemodes or change the time-out period. The default time-out policy is the monitor policy. The monitorpolicy 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 Windows fileis:

• CC:\Program Files\HP\Systems InsightManager\jboss\server\hpsim\deploy\jbossweb-tomcat50.sar\conf\web.xml

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

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

HP SIM audit log configuration

Overview

Several features of the HP SIM Audit Log are configurable. For example, you can specify which tools logdata and the maximum Audit Log file size. The HP SIM Audit Log is configured through the log.propertiesfile, and tool logging is enabled or disabled through the XML tool definition files.

Tool behaviors The XML tool definition file provides an option to disable logging of single-system aware (SSA) and multiple-system aware (MSA) command tools. The log attribute for the command element specifieswhether the results of the command are output to the HP SIM log file. Command output is logged by default.

Audit log parameters In the log.properties file, you can configure the following Audit Log 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 the path.properties file.

122 Configuration options



ImplementationChanges made to the log.properties file do not take effect until the log manager daemon or service isrestarted. For Windows, restart the HP SIM service.

CAUTION: The queue size should be changed only with extreme care. If the queue is set too high, thelog manager consumes too much system memory.

NOTE: When the Audit Log file reaches the maximum file size, the log is renamed withMX_LOGROLLFILEEXT extension and a new file is started. If a previous version of the file has already beenrenamed with the MX_LOG_ROLLFILEEXT extension, it will be an automatic roll-over of an audit log file. A roll-over will not occur until a task running is completed. However, after one hour of exceeding the maximumfile size, 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:\Program Files\HP\SystemsInsight Manager\config.

Create a file named path.properties under /etc/opt/mx/config.

2. For Windows, add the following entry in the path.properties file: LOG=\\Auditlog\\Logs or LOG=C:/Auditlog/Logs .

Note: C:\\Auditlog\\Log is listed here as an example for Windows. This path is user defined.

3. Restart the HP Systems Insight Manager (HP SIM) daemons (mxstop and mxstart).For Windows,restart the HP SIM service. After restarting the service, a new log file named mx.log resides in thedirectory specified in path.properties file.

Lifetimes for entries on the Task Results Page

OverviewHP SIM enables you to set how long entries remain on the Task Results Page after a task completes.

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

• Web-launch tools

• Tools that run from the mxexec command line using the -O or -o options to save the command output

• Tools that run X-Window commands

• Tools that specify in their tool definition the "job-log" flag as disabled, including:

Hardware Status Polling•

• Data Collection

• Identify Systems

• Software Status Polling

• Delete Events

• System Protocol Settings

• Automatic Discovery

• Hardware Status Polling

Tools in this category have no task output, have task output that is saved outside of HP Systems InsightManager, or have task results that are unlikely to be of long-term interest. Tasks for all other tools have thelong lifetime.

Frequently scheduled tasks Task results can also be removed from the Task Results Page if a certainnumber of task results for a scheduled task accumulate. This setting defaults to 10 instances of a single task.If more than 10 accumulate on the results page, then the oldest task result for this scheduled task is removed.

Lifetimes for entries on the Task Results



Last result tasks A task result is kept indefinitely if it is the last result for a scheduled task. For example, ifa scheduled task is disabled, its final task result is kept indefinitely or until the task is enabled and more taskresults 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 this value,edit:

MX_JOB_MAX_COMPLETED_JOBS_PER_TASK=10

NOTE: The limit of 10 task results applies to scheduled tasks with the "job-log" flag enabled in thetool definition. Scheduled tasks for the tools with the "job-log" flag disabled have a limit of 1. This valueis not configurable.

• By default, the last task results for a scheduled task is kept indefinitely. If you want to keep more than1 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.

124 Configuration options



16 Troubleshooting

Installation issuesI cannot load HP SIM on Windows NT 3.51 or Windows NT 4.0.

Solution: Windows NT 3.51 and Windows NT 4.0 are not supported platforms.

During a Windows install at the database credentials screen, the installer fails with an invalid credentials

error, and I am unable to enter my password.Solution: A user name and password cannot contain a space followed by a double quote. An Oracle username cannot contain a backslash (\) or a forward slash (/).

If you use these characters in your user name or password, you will receive an "Invalid character" error andnot be allowed to sign in.

I receive the error "Database Connection Error" during the Java-based database installation portion of HPSIM installation.

Solution: Verify that the target Microsoft SQL Server service (MSSQL) is running (select Control

Panel→Services→MSSQLSERVER). For SQL Server 2005, servicename will be "SQLServer."

When installing HP SIM on Microsoft SQL Server 2005 Express Edition Service Pack 1 the following error message appears "TCP/IP protocol is not enabled. Run SVRNETCN.exe to enableTCP/IP."

Solution:TCP/IP is disabled in SQL 2005 by default. To enable TCP/IP:

1. Click Start>Microsoft SQL Server 2005 >Configuration Tools> SQL Server Configuration

Manager . The SQL Server Configuration Manager window appears.

2. Select SQL Server 2005 Network Configuration from the left pane. The protocols will be displayedon the right frame.

3. Right click TCP/IP and select Enable.

4. Restart SQL server to reflect the changes.

During the installation, the system reboots, and then the installation launches the browser. Internet Explorer displays a message saying that it could not establish a connection with the local host. The browser is beinglaunched before the service has had time to start.

Solution: Try to access the URL again by placing the cursor in the URL field and pressing the Enter key. Keeptrying until the application loads in the browser.

After installing HP SIM, a CMS that is setup on a desktop is shown as a server.

Sign inI cannot sign in to HP SIM on Windows XP using a blank password.

Solution 1: Use a non-blank password, which provides better security. Have an administrator reconfigurethe Windows User Accounts to specify a non-blank password.

Solution 2: If you must use a blank password, disable the following Security Policy on the Windows XPmachine: Accounts: Limit local account use of blank passwords to console login only .

NOTE: Disabling this policy allows remote logins over the network using accounts that have no passwords.

On a Windows system, to limit local account use of blank passwords to console sign in only, complete thefollowing procedure:

1. Open Local Security Settings MMC Application by selecting Programs→Administrative Tools→Local

Security Policy.

2. Open the Local Security Policies folder, and then open the Security Options subfolder.

3. Disable the policy.

I cannot sign in to HP SIM on Windows XP.

Installation issues 125



Solution: If using a blank password, see the preceding problem. Otherwise, change the following LocalSecurity Policy on the Windows XP machine: Network Access: Sharing and security model for local

accounts from Guest Only to Classic.

NOTE: This setting does not affect remote sign ins using domain accounts. Modifying this policy allowsremote sign ins over the network using any local account configured to do so, not just the Guest account.Ensure all local accounts have appropriate passwords.

To change the setting:

1. Open Local Security Settings MMC Application by selecting Programs→Administrative Tools→LocalSecurity Policy.

2. Open the Local Security Policies folder, and then open the Security Options subfolder.

3. Change the setting from Guest Only to Classic.

If Guest Only is the preferred policy setting, perform the preceding steps, sign in to HP SIM, and then adddomain accounts (not local accounts) or the local Guest account as accounts to HP SIM. Restore the localpolicy setting back to Guest when done.

Single Login fails on cluster systems.

Solution: Single Login does not work on a virtual cluster system. It works on the physical systems that comprisethe cluster.

By using a proxy server, you might inadvertently or intentionally bypass IP address login restrictions configuredfor the user.

Solution: A proxy server can be used to bypass specific IP exclusions, if the proxy server IP address is notincluded in the IP exclusion ranges on the Login IP Address Restrictions page. Likewise, the possibilitythat a valid proxy server is included in the IP exclusion ranges would prevent a valid user from signing inthrough that particular proxy server.

Ensure valid proxy servers are within a valid Inclusion ranges, and make the Inclusion ranges as small aspossible. Using IP inclusion ranges is more effective than using IP exclusion ranges because Inclusion rangesexclude all addresses not specified in the IP inclusion range.

I cannot sign in to HP SIM using Internet Explorer 6.0.

Solution: If your HP SIM server has an underscore in the name, use the IP address of the HP SIM serverinstead of the name in the Internet Explorer address field. Internet Explorer has a problem with underscoresin system names, which prevents the authentication cookie from working properly.

I cannot sign in to HP SIM or to managed systems browsing from HP SIM using Internet Explorer 6.0.

Reason 1: Internet Explorer has a problem with underscores in system names, which prevents the authenticationcookie from working properly.

Solution: If the names of the systems have an underscore, use the IP address of the system. Configure HPSIM to create links to the system using the IP address instead of the name:

1. Browse and sign in to HP SIM.

2. Select Options→Security→System Link Configuration. The System Link Configuration page appears

3. Select Use the system IP address.

4. Click OK.

Note: By using IP addresses instead of names, you might encounter security alerts, if the name in the managedsystem certificate does not match the name in the link. The default certificate for managed systems uses thesystem name, not the IP address.

Reason 2: For managed systems, the privacy policy setting in Internet Explorer 6.0 is blocking theauthentication cookies from the managed systems.

Solution 2A: (Recommended) Remove the systems from the Internet Zone. The privacy policy only affectssystems in the browser Internet Zone. Therefore, by removing systems from that zone, you prevent theprivacy policy from affecting those systems. To change the browser privacy policy setting, select

126 Troubleshooting



Tools→Internet Options, and click the Privacy tab from the Internet Explorer browser menu. Modify theprivacy setting in one of the following ways:

▲ Browsing to systems by IP address instead of by name can cause the browser to consider those systemsto be in the Internet Zone. Instead, browse by name. You can configure HP SIM to use system nameswhen creating links to systems by selecting Options→Security→System Link Configuration andselecting Use the system name.

▲ If your browser is configured to use a proxy server, you can configure your browser to bypass the proxyserver for specific systems, which removes those systems from the browser Internet Zone. From the

browser menu, select Tools→Internet Options, and click the Connections tab. Click LAN Settings,and if you are configured to use a proxy server, click Advanced. In the Exceptions list, you canspecify a list of addresses that should bypass the proxy server. These addresses are no longer in theInternet Zone and are not affected by the privacy settings policy.

Solution 2B: (Not Recommended) Change the browser privacy security policy setting. From the InternetExplorer browser menu, select Tools→Internet Options, and click the Privacy tab. The privacy settingcan be modified in one of the following ways:

• Set the privacy setting to Accept all Cookies by sliding the slider bar to the bottom. This setting allowsa browser to accept all cookies for both first-party and third-party sites. When browsing to HP SIM ordirectly to a managed system, it is considered a first-party site. When navigating to a managed systemthrough HP SIM, the system is considered a third-party site.

• Customize the handling of cookies by clicking Advanced and enabling Override automatic cookiehandling. Then select the appropriate radio buttons for first-party and third-party cookies to Accept

or Prompt. If you select Prompt, the browser prompts you on how to handle a cookie each time acookie is received. You can choose to block or allow the cookie each time, or for all times. EnablingAlways allow session cookies does not resolve the problem because the Web Agents do not usesession cookies.

• Individually specify the handling of cookies for each system. Click Edit in the websites section andadd the address of the system in the specified field. Click Allow to always allow cookies to that system.Repeat this for all systems.

Selecting a link that opens a new browser window requires another sign in.

Solution: If you are browsing using the Internet Explorer link from within Windows Explorer, you must insteadstart Internet Explorer as a separate process. Start Internet Explorer by selecting it from the Windows Startmenu or using the desktop icon.

I cannot sign in to the HP SIM server from Windows NT, Windows 2000, or Windows XP.

Solution: The Windows accounts used to access HP SIM must have the access this computer from the

network right selected.

In Windows NT 4, open the User Manager by selecting Start→Programs→Administrative Tools. In thePolicies menu, select User Rights. In the Rights dropdown list, select access this computer from

network, and ensure the HP SIM users are granted full configuration rights.

In Windows 2000 and Windows XP, open the Local Security Policy by selectingStart→Programs→Administrative Tools. Expand the Local Policies tree, and select User Rights

Assignment. Ensure the HP SIM users have the access this computer from the network right and thatthey do not have the Deny access to this computer from the network right selected.

I am receiving the exception org.apache.jasper.JasperException while signing in to HP SIM.

Solution: Delete all the files in the work directory, and sign in again.

• On HP-UX and Linux: /opt/mx/jboss/server/hpsim/work

• On Windows: \jboss\server\hpsim\work

I am being asked for my sign-in credentials when accessing a trusted system.

Solution: Verify that you have a valid trust relationship set up between HP SIM and the managed system. Also, verify that you are authorized for an appropriate tool on the desired system. Tools that enable SingleLogin to System Management Homepage include System Management Homepage as Administrator, SystemManagement Homepage as Operator, System Management Homepage as User, Replicate Agent Settings,and Install Software and Firmware. For Single Login to Onboard Administrator, tools include Onboard

Administrator as Administrator, Onboard Administrator as Operator, and Onboard Administrator as User.




For Single Login to HP StorageWorks Command View EVA, tools include Command View EVA as Administrator, Command View EVA as Operator, and Command View EVA as User. See for more informationon setting up trust relationships.

After installing the Microsoft MS04-025: Cumulative Security Update for Internet Explorer (867801), I canno longer access HP SIM and System Management Homepage.

Solution: This issue affects any system running Windows XP Service Pack 2 and any version of HP SIM andSystem Management Homepage or any system running Windows XP Service Pack 2 and browsing to HPSIM running on any supported operating system. To resolve:

• Configure Windows XP Service Pack 2 firewall to allow access to System Management Homepage.On the Windows XP system, select Start→Control Panel→Windows Firewall to configure thefirewall settings.

1.

2. Click the Exceptions tab, and click Add Port.

3. Add the following exceptions to the firewall protection. Enter the product name and the port numberfor each.

ProtocolPortDescription

HTTP2301HP SMH Web Server*

HTTPS2381HP SMH Secure Web Server*

HTTP5988 WBEM/WMI MapperHTTPS5989 WBEM/WMI Mapper Secure Port

SSH22SSH port

SNMP161SNMP Agent

ICMP***Ping Discovery (ICMP)**

HTTP80Ping Discovery (TCP)**

* If the system is not being managed from HP SIM, only ports 2301 and 2381 should be configuredto enable browser access to System Management Homepage.

** Usage is configurable in HP SIM.

*** This setting is under the Advanced tab of the Windows Firewall window. Select ICMPSetting→allow incoming echo request.

4. In the Add a Port window, click OK.

5. In the Windows Firewall window, click OK.

This configuration leaves the Windows XP Service Pack 2 security enhancements intact and allowstraffic over the ports listed in the previous table.

Note: HP SIM discovers Web servers on other ports

• Enable file and print sharing and Remote Administration Exception.

Enable file and print sharing:1.

a. Select Start→Control Panel.

b. Click Windows Firewall to configure the firewall settings.c. Click the Exceptions tab.

d. Select the File and Print sharing checkbox.

e. Click OK.

2. Enable Remote Administration Exception:

a. In the Control Panel, open the Group Policy editor.

b. Select Computer Configuration.

c. Select Administrative Templates.

d. Select Network.

e. Select Network Connections.

f. Select Windows Firewall.

128 Troubleshooting



g. Select Domain profile.

h. Select Enable the Windows Firewall: Allow Remote Administration Exception.

• Configure Windows XP Service Pack 2 to allow access to HP SIM on the system running Windows XPService Pack 2 and HP SIM.

1. On the Windows XP system, select Start→Control Panel→Windows Firewall to configure thefirewall settings.

2. Click the Exceptions tab, and click Add Port.

3. Add the following exceptions to the firewall protection. Enter the product name and the port numberfor each.

ProtocolPortProduct

SNMP Trap (UDP)162SNMP Trap Listener

HTTP280HP SIM web Server

RMI2367RMI registry

TCP4444 JBoss RMI/JRMP Invoker**

TCP4445 JBoss Pooled Invoker**

TCP8083 JBoss Web Service port**

HTTPS50000HP SIM Secure Web Server

HTTPS50001HP SIM SOAP *

HTTPS50002HP SIM SOAP with client certificateauthentication*

HTTPS50003HP SIM SOAP*

HTTPS/HTTP*50004HP SIM WBEM Event Receiver*

TCP50005 WBEM Events

TCP50006PostgreSQL

TCP50008 JBoss Naming Service RMI port**

TCP50009 JBoss Naming Service port**

TCP50010HP SIM VMM Essentials v 1.1.2.0

TCP50013 Web services RMI class loader

TCP50014 JRMP invoker

TCP50015Pooled invoker

* Configurable in HP SIM

** Configurable in the SIM/jboss/server/hpim/conf/jboss-service.xml descriptor

4. In the Add a Port window, click OK.

5. In the Windows Firewall window, click OK.

This configuration leaves the Windows XP Service Pack 2 security enhancements intact and allowstraffic over the ports listed in the table.

After installing HP SIM, I changed the Windows administrator password and can no longer sign in to HPSIM.

Solution: If you have SQL Server installed locally, verify that it is running. If it is not running verify the logoncredentials. The service login credentials could have changed. The HP SIM service is registered to run underthe credentials used during installation. To resolve this issue:

1. Change the MSSQL service password:

a. In Windows, open Services (Start→Control Panel→Services).

b. Locate the MSSQL service (SQLserver service for SQL2005) and select Properties.




c. Select the Logon tab, and change the password.

d. Restart the MSSQL (or SQLserver) service.

2. Change the HP SIM service password:


b. Locate the HP SIM service, and select Properties.


d. Restart the HP SIM service.

3. If you are using OpenSSH on Windows Server 2000 or 2003, change the OpenSSH Server servicepassword:


b. Locate the OpenSSH Server service, and select Properties.


d. Restart the OpenSSH and HP SIM service.

Signing in from a dial-up connection takes a long time.

Solution: Your connection depends on many factors that are beyond your control. You might have a slowmodem, the server you are connecting to might not be operating at peak efficiency, or you might have abad phone line.

I cannot sign in to HP SIM.

Solution: This condition can result from any of the following reasons:

• If the IP Address Restriction field (on the New User Group, Edit User , New User , or the Edit User

Group pages) is configured, ensure that is includes all IP addresses of the CMS. If browsing tolocalhost ensure that the loopback address 127.0.0.1 is also included.

• You are not entering the information correctly. Passwords are case-sensitive.

• The account you are entering is not a valid account for HP SIM.

• The account you are entering has been deleted, disabled, or locked out.

• The password for the account must be changed.

• You are attempting to sign in from an IP address that is not valid for the specified account.

• You do not have cookies enabled in your browser or you are using a cookie blocker.I cannot sign in to my Windows HP SIM.

Solution: If you are attempting to sign in with a Windows user account created on the CMS (as opposed toa domain account) and the CMS host name is longer than 15 characters, then you must enter the first 15characters of the CMS name in the domain field to sign in. For example, if your Windows CMS is named"SIMwin2003withsp2" and you have a local account "bob," then sign in with username = "bob" anddomain = "SIMwin2003withs." Any new local user account created cannot sign in, unless they were createdusing only the first 15 characters of the system name entered in domain name field and signed in using thesame.

Upgrade issues

When upgrading from previous versions of HP SIM to HP SIM 5.0, tools that are now obsolete can remainin the Monitor Tools toolbox.

If upgrading from HP SIM 4.2 or later, the tools are listed in the following table:

General toolsMonitor tools

General Toolstype

General toolscat

General toolsfind

If upgrading from a version prior to HP SIM 4.2, the tools are listed in the following table:

General toolsMonitor tools

130 Troubleshooting



General toolstype

General toolscat

General toolsfind

General toolscp

General toolsmv

General toolsrm

General toolscopy

General toolsdel

Solution:

1. To remove the obsolete tools, sign in HP SIM as a full configuration rights user .

2. Select Options>Security >Users and Authorizations, and then click the Toolboxes tab.

3. Select the Monitor Tools toolbox.

4. Click Edit.

5. In the Toolbox contents panel, select the tools to remove, and click the << button.

6. Click OK to save.

Password issuesThe password for the service account used by the HP SIM Windows service is changing. What do I need tochange?

Solution:

1. Stop HP SIM.

2. Access the Services control panel and edit the service credentials to provide the new password forthe HP Systems Insight Manager service.

3. Run mxpassword -g and modify the following password:

MxHPSIMServicePassword

4. Restart HP SIM.

The password for the database account used by the HP SIM Windows service is changing. What do I needto change?

Solution:

1. Stop HP SIM.

2. Run mxpassword -g and modify the following passwords to the new account password:

MxDBUserPassword

MxPMPPassword

3. Restart HP SIM.

Password issues 131



glossary A

agent A program that regularly gathers information or performs some other service without the user'simmediate presence. HP Systems Insight Manager (HP SIM) agents provide in-depth hardwareand software information and subsystem status to HP SIM and numerous third-party managementapplications.See also management agent.

alarm A user-configurable notification displayed in the System Status panel of HP SIM when certainevents occur. For instance, if a monitored item changes, an alarm notifies the user that a changehas occurred.See also trap, event.

all events collection Displays all events that have occurred for all systems.

All Tools toolbox A default toolbox that provides complete access to all tools for the authorized system or systemgroup.

attribute A single characteristic of a manageable product or component, as in an attribute of a ManagementInformation 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 that describes that chip.See also Management Information Format.

authentication The process of identifying an individual, based on a user name and password. Authentication isdistinct from authorizations and ensures that the individual is who they claim to be.

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

automaticdiscovery

The process that HP SIM uses to find and identify the systems on your network and populate thedatabase with that information. A system must first be discovered to collect data and track systemhealth status. The primary source for automatic discovery is ping sweeps configured in theautomatic discovery tasks page. Other sources might include receiving events from unknownsystems or from a management processor that has information about a server. Identificationautomatically runs on discovered systems.

available software A listing of the software components available in the repository to which the HP Version Control

Agent (VCA) has been configured to point. When browsing directly into a VCA, these additionalcomponents can be selected for installation.

B

banner The section of the GUI at the top of the screen that includes the user name and links to the Home

page and sign out functions.

C

caution A note to indicate that failure to follow directions could result in damage to equipment or loss ofinformation.

CentralManagementServer (CMS)

A system in the management domain that executes the HP SIM software. All central operationswithin HP SIM are initiated from this system.

central processingunit polling rate

The rate for how often the Cluster Monitor CPU Resource checks CPU utilization as reported byHP Insight Management Agent on monitored systems.

certificate An electronic document that contains a subject's public key and identifying information aboutthe subject. The certificate is signed by a certificate authority (CA) to bind the key and subjectidentification together.See also certificate authority.

certificate authority(CA)

A trusted third-party organization or company that issues digital certificates used to create digitalsignatures and public-private key pairs. The role of the CA in this process is to guarantee that theindividual who has been granted the unique certificate is the individual they claim to be.

132



certificate key A value used alone or with an encryption decoder (corresponding public or private key) forcryptography. In traditional private key cryptography, the communicators share a key or cipherso that each can encrypt and decrypt messages. The risk in this system is that if any party losesthe key, the system is broken. In public key cryptography, the private key is associated with apublic key, so each person in the system has a personal private key that is never shared.

cleared status A status condition that indicates an event 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 many discrete systems that form a single,unified computing resource. Clusters vary in their features, complexity, and the purposes for whichthey are best suited.

cluster IP address The IP address of the cluster.

cluster monitor A core component of HP SIM. Cluster Monitor adds the ability to monitor and manage multi-nodeclusters. Cluster Monitor also manages multiple cluster platforms in a heterogeneous environment.

cluster monitor resource

A program that provides a monitoring or management function for clustered nodes in a cluster.

cluster systemidentification

Information about cluster systems. This information is stored in the database.

collections The method for grouping system or event.command lineinterface (CLI)

A text-based application that can be executed from a command shell such as sh, csh, ksh or theMicrosoft Windows CMD shell.

commoninformation model(CIM)

An object-oriented schema defined by the Desktop Management Task Force (DMTF). CIM is aninformation model guide that describes and shares management information enterprise-wide.CIM is designed for extending each management environment in which it is used.

commoninformation modelobject manager (CIMOM)

A CIMOM acts as the interface for communication between web-based enterprise management(WBEM) providers and management applications such as HP Systems Insight Manager. A CIMOMthat provides an interface for an SMI-S provider is called an SMI CIMOM.

communications

protocol

See management protocol.

component A component is a single, self-describing, installable (interactive or silent) binary file containing asingle piece of software, such as firmware image, driver, agent, or utility, that is supported bythe management and update tools.

configurationhistory report

The Survey Utility that contains reports that show configuration details for server and comparesconfiguration history files for differences.

Configure or Repair Agents

An HP SIM feature that enables you to repair credentials for SNMP settings and trust relationshipsthat exist between HP SIM and target systems. You can also update Web Agent passwords ontarget systems that have 7.1 agents or earlier installed.

control tasks Sequences of instructions that are associated with a search, event, or both, such as Delete Events,Remove Disk Thresholds, Set Disk Threshold, and Set Device Access community strings.

critical status A state generated when HP SIM can no longer communicate with a managed system.custom tools Custom tools are tools that can be created by the user to run on the Central Management Server

or on target systems. For example:

• Remote tool A tool that runs on selected target systems. It might copy files to the targetsystems or run specific X-Window applications on the target systems. This tool can bescheduled.

• CMS tool A tool that runs on the Central Management Server. It is usually a script or batchfile and can pass in environment variables. Using Automatic Event Handling, this tool canoptionally be configured to run when events are received. This tool can be scheduled.

• Web page tool A tool that launches a web URL. The URL is launched in a separate browser

window on the Central Management Server. This tool cannot be scheduled.

133



D

data collectionreports

Data collection reports include information about discovered systems in a single instance or ahistorical trend analysis report. HP SIM supports Overwrite existing data set (for detailed

analysis), formerly known as Single Instance Data Collection task in Insight Manager 7, andAppend new data set (for historical trend analysis). With Overwrite existing data set (for

detailed analysis), data is collected from a system at a single instance. With Append new data

set (for historical trend analysis), data detailing the system history is collected.

data collection

tasks

Procedure that involves gathering information from a group of managed systems and storing that

information in the database. HP SIM uses Hardware Status Polling and Data Collection Tasks toimplement data collection.

DesktopManagementInterface (DMI)

An industry-standard protocol, primarily used in client management, established by the DesktopManagement Task Force (DMTF). DMI provides an efficient means of reporting client systemproblems. DMI-compliant computers can send status information to a central management systemover a network.

DesktopManagement TaskForce (DMTF)

An industry standard body that defines DMI and WBEM standards for the industry. HP is anactive sponsor and participant in the DMTF body.

digital signatures A technology used to validate the sender of a transaction. This technology uses private keys todigitally sign the data and public keys to verify the sender.

discovery A feature within a management application that finds and identifies network objects. In HPmanagement applications, discovery finds and identifies all the HP systems within a specifiednetwork range.

discovery filters Enables users with full configuration rights to prevent or allow certain system types from everbeing added to the database.

discovery template Files that can be used by automatic discovery in lieu of typing the addresses directly in to thePing inclusion ranges or Exclusion ranges fields on the Automatic Discovery - General

Settings page and are designed to be used as a quick way to change the scope of automaticdiscovery.

DistributedComponent Object

Model (DCOM)

An extension of the Component Object Model (COM) that enables COM components tocommunicate between clients and servers on the same network.

Distributed TaskFacility (DTF)

A management application that manages the remote execution of tasks on managed systems.

DMI See Desktop Management Interface.

Domain NameService (DNS)

A service that translates domain names into IP addresses.

E

e-mail notification One of the notification tasks in HP SIM that sends notifications through e-mail.

edit collection To modify existing collections to add or remove search criteria.

enclosure A physical container for a set of server blades. It consists of a backplane that routes power andcommunication signals and additional hardware for cabling and thermal issues. It also hosts theCPU or server power supplies.

134 glossary



event Information sent to certain users that something in the managed environment has changed. Eventsare generated from SNMP traps. HP SIM receives a trap when an important event occurs. Eventsare defined as:

• Warning. Events of this type indicate a state that might become a problem.

• Informational. Events of this type require no attention and are provided as usefulinformation.

• Normal. Events of this type indicate that this event is not a problem.

• Minor. Events of this type indicate a warning condition that can escalate into a moreserious 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 events by product type.

external sites Third-party application URLs.

F

full configuration

rights user

A user who is authorized for the All Tools toolbox on all systems, including the Central

Management Server. This type of user has been given special privileges to administer the HP SIMsoftware.

G

graphical user interface (GUI)

A program interface that takes advantage of the graphics capabilities of the computer to makethe program easier to use. The HP SIM GUI runs in a web browser.

H

health status Health status is an aggregate status all of the status sources (which can be SNMP, WBEM, DMI,and HTTP) with the most critical status being displayed.See also system health status.

hosts files A file that follows the UNIX, Linux, or Windows host file format, which is an IP address followedby a name and each system is listed on a separate line in this file. This file is used by manualdiscovery to manually add multiple systems to the HP SIM database,

HP BladeSystemIntegratedManager

HP BladeSystem Integrated Manager is an HP Systems Insight Manager (HP SIM) plugin thatenables you to manage blade systems from HP SIM for Windows, HP-UX and Linux. HPBladeSystem Integrated Manager is composed of blade computer systems, integrated connectivityto data and storage networks, and shared power subsystems. The HP BladeSystem IntegratedManager enables you to quickly navigate your HP blade environments including server bladesand desktops, enclosure infrastructures, racks, and integrated switches, through hierarchical treeviews. Users are able to conveniently configure, deploy, and manage individual or groups ofblade systems.

HP InsightManagement Agent

A program that regularly gathers information or performs some other service without the user'simmediate presence.

HP Insight Power Manager

An integrated power monitoring and management application that provides centralized controlof server power consumption and thermal output at the datacenter level. It extends the capacityof datacenters by enabling the user to control the amount of power and cooling required forProLiant servers. Built on ProLiant Power Regulator Technology, it extends new server energyinstrumentation levers into HP SIM for greater Unified Infrastructure Management.

135



HP ProLiantEssentials VirtualMachineManagement Pack(Virtual MachineManagement Pack)

Provides central management and control of Virtual Machines on Microsoft Virtual server, Vmware’sGSX and ESX. Integrated with HP SIM, Virtual Machine Management Pack provides unifiedmanagement of HP ProLiant host servers and virtual machines.

HP ProLiantEssentials

Vulnerability andPatch ManagementPack

The all-in-one vulnerability assessment and patch management tool integrated into HP SIM,simplifying and consolidating the proactive identification and resolution of issues that can impactserver availability into one central console.

HP Systems InsightManager

System management software that is capable of managing a wide variety of systems, includingHP systems, clusters, desktops, workstations, and portables.

HP SIM combines the strengths of Insight Manager 7, HP Toptools, and HP Servicecontrol Managerto deliver a single tool for managing HP ProLiant, Integrity, and HP 9000 systems running Windows, Linux, and HP-UX. The core HP SIM software delivers the essential capabilities requiredto manage all HP server platforms. HP SIM can also be extended to deliver unparalleled breadthof system management with plug-ins for HP storage, power, client, and printer products. Plug-insfor rapid deployment, performance management, and workload management enable systemsadministrators to pick the value added software required to deliver complete lifecycle management

of their hardware assets.HP Systems InsightManager database(database)

The database that stores vital information about HP SIM, including users, systems, and toolboxes.

HP Version Control Agent (VCA)

An agent that is installed on a server to enable you to see the HP software installed on that server.The VCA can be configured to point to HP Version Control Repository Manager, enabling easyversion comparison and software update from the repository.

HP Version ControlRepositoryManager (VCRM)

An HP agent that enables a customer to manage HP provided software stored in a user-definedrepository.

HyperText Transfer

Protocol (HTTP)

The underlying protocol used by the World Wide Web.

I

identification While discovery finds systems, identification attempts to determine what the system type is. Inaddition, it determines what management protocol a system supports, using credentials from theGlobal Protocol Settings page, and attempts to determine the operating system and versionloaded, along with other basic attributes about the system. Finally, it determines if the system isassociated with another system. For example, a management processor in a server.

installed version A particular HP software component that is installed on the server.

Internet Protocol(IP)

Specifies the format of datagrams (packets) and the addressing scheme on a network. Mostnetworks combine IP with Transmission Control Protocol (TCP), which establishes a virtual

connection between a destination and a source.IP range Systems with an IP address that falls in the specified range.

J

Java databaseconnectivity (JDBC)

Similar to Open DataBase Connectivity (ODBC), this set of application program interfaces (APIs)provides a standard mechanism to allow Java applets access to a database.

Java RemoteMethod Invocation(RMI)

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

136 glossary



K

keystore A database that maintains a list of keys. The keystore can contain a subject's own private key. A keystore can also contain a list of public keys, as published in certificates.

L

limitedconfiguration

rights user

A user who has limited capability to configure the Central Management Server. limitedconfiguration rights users have permission to create, modify, and delete all reports and their own

tools.M

Major status Status information collected from the system that indicates one or more of the monitored subsystemsare not operating properly which is impacting the system. Action should be taken immediately.

managed systems Any system managed by HP SIM, such as servers, desktops, storage systems, and Remote InsightBoards (RIBs).

managementagent

A daemon or process running on a managed system. It receives and executes requests from theCentral Management Server on the managed system.

managementdomain

A collection of resources called managed systems that have been placed under the control of HPSIM. Each Central Management Server is responsible for a management domain. The managed

systems can belong to more than one management domain.Management HTTPServer

An integrated piece of software used by the HP suite of HP Web-enabled System ManagementSoftware to communicate over HTTP and HTTPS. It provides a uniform set of functionality andsecurity to HP Web-enabled System Management Software. This version is available in the ProLiantSupport Pack 7.10 or earlier.

ManagementInformation Base(MIB)

The data specification for passing information using the SNMP protocol. An MIB is also a databaseof managed objects accessed by network management protocols.

ManagementInformation Format(MIF)

An ASCII text file in the DMI architecture that describes the manageable features and attributesof a product. The DMI maintains this information in a MIF database and makes it available tooperating systems and management applications. The DMTF has specified MIF formats for a

variety of system types and peripheral systems.managementinstrumentation

Agents running on systems that provide management information for HTTP, DMI, or SNMPprotocols.

management LAN A LAN dedicated to the communications necessary for managing systems. It is typically a moderatebandwidth (10/100 BaseT) and secured through limited access.

managementprotocol

A set of protocols, such as WBEM, HTTP, SNMP, or DMI, used to establish communication withdiscovered systems.

managementscope

A set of systems within the set of all discovered systems that HP SIM manages.

managementservices

A core set of capabilities such as automatic discovery, data collection, a central repository forsystem and event information, event management, basic notification, and secure access. These

functions are used by add-ins from HP, a Management Solutions Partner, and HP SIM users.management tasks Procedures you set up to search systems or events.

manual discovery Similar to automatic discovery, but rather than ping sweeps and events being used to find systems,you manually add systems, either by IP address or name, using template of hosts files. Identificationruns on these systems. Manual discovery can be used to set a system type. However, ifidentification determines the target is something different, the found type is used.

manual discoverytechniques

Processes that enable you to bypass a full discovery for the following tasks:

• Adding a single system

• Editing the system

• Creating or importing an HP SIM database hosts file

• Creating or importing generic hosts files

137



MicrosoftClustering Servicestatus page

A page that summarizes cluster status as defined by Microsoft Cluster Server and lists the statusand values of MSCS-defined cluster attributes. The Cluster Monitor uses color to display statusbased on MSCS condition values (Normal, Degraded, Failed, and Other).

Minor status Status information collected from the system that indicates one or more of the monitored subsystemsare not operating properly which is impacting the system. Action should be taken as soon aspossible to prevent further failure.

Monitor Toolstoolbox

A default toolbox that contains tools that display the state of managed systems but not tools thatchange the state of managed systems.

multiple-systemaware (MSA)

A run type that supports multi-system operations. Tools with this run type operate on the targetsystems using their own internal mechanisms instead of using the Distributed Task Facility. TheMSA run type uses the Distributed Task Facility to launch the tool on a single system before thetool interacting with the other managed systems.

N

network clients Any computer system connected to your network with a compatible browser used to connect tothe HP SIM GUI.

no configurationrights user

A user who cannot configure the Central Management Server. However, the user can view andrun predefined reports on the Central Management Server and all managed systems.

OOnboard

Administrator The Onboard Administrator is the central point for controlling an entire c-Class rack. It offersconfiguration, power, and administrative control over the rack, and its associated blades (ComputeServers), blade management processors (iLOs), network switches (depending on the models ofswitches used) and storage components (such as SAN or SATA). The Onboard Administrator isa single management processor, with shared resources to an optional backup twin processor forfailover.

Open Service EventManager (OSEM)

Enables you to collect, filter, and send problem reports for supported systems (ProLiant andIntegrity) running Insight Management Agents. In addition, OSEM automatically sends serviceevent notifications to HP SIM when a problem is detected on the system.

overall software

status

This section indicates whether the software on the server that the HP Version Control Agent is

installed on has any updates available within the repository in which it has been configured tomonitor.

P

HP ProLiant andIntegrity SupportPack

An HP ProLiant and Integrity Support Pack is a set of HP software components that have beenbundled together by HP, and verified to work with a particular operating system. An HP ProLiantand Integrity Support Pack contains driver components, agent components, and application andutility components. All of these are verified to install together.

HP ProLiantEssentialsPerformance

Management Pack(PMP)

A software solution that detects, analyzes, and explains hardware bottlenecks on HP ProLiantservers. PMP tools consist of Online Analysis, Offline Analysis, Comma Separated Value (CSV)File Generator Report, System Summary Report, Status Analysis Report, Configuration, Licensing,

and Manual Log Purge.

HP ProLiantSupport Pack

A set of HP software components that have been bundled together by HP and verified to workwith a particular operating system. A HP ProLiant Support Pack contains driver components, agentcomponents, and application and utility components. All of these are verified to install together.

ProLiant Essentialslicense key

The contractual permissions granted by HP to the customer in the form of a coded embodimentof a license that represents a specific instance of a license. A single license can be representedby a single key or by a collection of keys.

R

rack A set of components cabled together to communicate between themselves. A rack is a container

for an enclosure.

138 glossary



Red Hat PackageManager (RPM)

The Red Hat Package Manager is a powerful package manager that can be used to build, install,query, verify, update, and uninstall individual software packages. A package consists of anarchive of files and package information, including name, version, and description.

Reference SupportPack

A baseline bundle of HP software components that the HP Version Control Agent can be configuredto point to in the repository. This setting enables users to indicate that they want to keep all oftheir software up to a certain Support Pack level.

remote wakeup Sometimes referred to as Wake-On-LAN (WOL). The remote powering up of a system throughits resident WOL network card, provided that the system has been enabled to be so awakened

using the ROM or F10 Setup.This is a capability on which HP SIM relies to turn on the systems for scheduled Software Updatesor Replicate Agent Settings.

remove all diskthresholds

A task provided by HP SIM to remove disk thresholds for systems in an associated collection. Thistask only removes disk thresholds that were set by HP SIM or by browsing directly to the Web Agent. Any thresholds set by HP SIM for Windows 32, including disk thresholds, are not removedby this task.

Replicate AgentSettings

A tool that can be used to copy web-based agent settings to a group of systems.

repository A directory containing HP ProLiant Support Pack or Integrity Support Packs and Smart Components.

Resource Partition A subset of the resources owned by an operating system instance. The use of those resources is

controlled through technologies such as the Fair Share Scheduler, pSets, and Memory ResourceGroups.

A resource partition also has a set of processes associated with it, and only those processes canuse the resources within the resource partition. Policies established by tools such as ProcessResource Manager (PRM), Workload Manager (WLM), or Global Workload Manager (gWLM)control how resources are allocated to the set of resource partitions within an operating systeminstance.

role See toolbox.

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

S

search criteria A set of variables (information) used to define a requested subset of information from the HP SIMdatabase.

Secure HTTP(HTTPS)

An extension to the HTTP protocol that supports sending data securely over the web.

Secure Shell (SSH) A program to log in to another system over a network and execute commands on that system. Italso enables you to move files from one system to another, and it provides authentication andsecure communications over insecure channels.

Secure SocketsLayer (SSL)

A standard protocol layer that lies between HTTP and TCP and provides privacy and messageintegrity between a client and server. A common usage of SSL is to provide authentication of theserver, so clients can be assured they are communicating with the server it claims to be. It is

application protocol independent.Secure TaskExecution (STE)

A feature of HP SIM that securely executes a task from a managed system. STE ensures that theuser requesting the task has the appropriate rights to perform the task, and encrypts the requestto protect data from snooping.

security roles A feature that enables administrators to restrict system access and manage access on a per-useror per-group basis. This capability enables systems administrators to delegate tasks to junior staffwithout providing access to advanced or dangerous features. It also enables systems administratorsto delegate management of systems to specific organizations or customers without providingaccess to systems owned by other organizations or customers.

self-signedcertificate

A certificate that is its own Certificate Authority (CA), such that the subject and the CA are thesame.See also certificate, certificate authority.

139



server blade Typically a very dense server system containing microprocessors, memory, and network connectionsthat can be easily inserted into a rack-mountable enclosure to share power supplies, fans, switches,and other components with other server blades. Server blades tend to be more cost-efficient,faster to deploy, and easier to adapt to growth and change than traditional rack-mounted ortower servers.See also enclosure.

server blade visuallocator

A feature designed to provide visual representation of ProLiant BL e-Class, p-Class and c-Classservers within their respective enclosures and racks.See also enclosure.

Service AdvertisingProtocol (SAP)

A NetWare protocol used to identify the services and addresses of servers attached to the network.

Service EssentialsRemote SupportPack

The HP Service Essentials Remote Support Pack provides proactive remote monitoring, diagnostics,and troubleshooting to help improve the availability of HP-supported servers and storage devicesin your data center. The Remote Support Pack reduces cost and complexity in support of systemsand devices. The Remote Support Pack securely communicates incident information through yourfirewall and/or Web proxy to the HP Support Center for reactive support. Additionally, basedon your support agreement, system information can be collected for proactive analysis andservices.

set disk thresholds A task provided by HP SIM to set a disk threshold for systems in an associated collection. Thisthreshold is set on all disk volumes on the target systems.

Shared ResourceDomain (SRD)

A collection of compartments—all of the same type—that share system resources. The compartmentscan be nPartitions, virtual partitions, processor sets (pSets), or Fair Share Scheduler (FSS) groups. A server containing nPartitions can be an SRD—as long as nPartition requirements are met. Aserver or an nPartition divided into virtual partitions can be an SRD for its virtual partitioncompartments. Similarly, a server, an nPartition, or a virtual partition containing pSets can be anSRD for its pset compartments. Lastly, a Server, an nPartition, or a virtual partition containing FSSgroups can be an SRD for its FSS group compartments.

A complex with nPartitions can hold multiple SRDs. For example, if the complex is divided intonPartitions, named Par1 and Par2, Par1's compartments could be virtual partitions, while Par2'scompartments are pSets.

Each compartment holds a workload. gWLM manages the workload by adjusting the

compartment's resource allocation.Short MessageService (SMS)

A convenient way to send brief text messages directly to a wireless phone. There is a maximummessage length of 140 characters.

Simple NetworkManagementProtocol (SNMP)

One of the management protocols supported by HP SIM. Traditional management protocol usedextensively by networking systems and most servers. MIB-2 is the standard information availableconsistently across all vendors.

Simple Object Access Protocol(SOAP)

A lightweight protocol for exchange of information in a decentralized, distributed environment.

Single Login Permission granted to an authenticated user browsing to HP SIM to browse to any of the managedsystems from within HP SIM without re-authenticating to the managed system. HP SIM is the initial

point of authentication, and browsing to another managed system must be from within HP SIM.single-systemaware (SSA)

A run type that does not support multi-system operations. Tools with this run type are only awareof the system on which they are running.

SMI CIMOM See common information model object manager.

SMI-S provider An industry-standard WBEM provider that implements a well defined interface for storagemanagement. The manufacturers of host bus adapters (HBAs), switches, tape libraries, and storagearrays can integrate SMI-S providers with their systems, or provide them as separate softwarepackages.See also Web-Based Enterprise Management.

SNMPcommunication

setting

Default SNMP community string used when communicating with systems supporting SNMPcommunications.

140 glossary



SNMP trap Asynchronous event generated by an SNMP agent that the system uses to communicate a fault.

software inventory A listing of the HP software installed on the system where the HP Version 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 confidential or sensitive information, alterdata transactions, or present false or misleading data.

standard error (stderr)

The default place where the system writes error messages. The default is the terminal display.

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

status message list A list created by Cluster Management Resources to collect entries found in the bottom left areaof the Cluster Monitor page to bring your attention to cluster attributes that are in an abnormalstate.

status messagesummary header

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

status type The classification of status messages (for example, Critical, Major, Minor, Normal, Warning,and Unknown).

StorageManagement

InitiativeSpecification(SMI-S)

A standard management interface developed by the Storage Networking Industry Association(SNIA). SMI-S provides a common interface and facilitates the management of storage devices

from multiple vendors. SMI-S uses industry-standard common information model and Web-Based Enterprise Management technology.

storage systems SAN-attached Fibre Channel disk arrays, switches, tape libraries, or hosts (with Fibre Channelhost bus adapters).

subnet On TCP/IP networks, subnets are all systems whose IP addresses have the same prefix. Forexample, all systems with IP addresses that start with 10.10.10. would be part of the same subnet.

Survey Utility An agent (or online service tool) that gathers and delivers hardware and operating systemconfiguration information. This information is gathered while the server is online.

symmetric key A common key that both the server and receiver of a message share and use to encrypt anddecrypt a message.

system Systems on the network that communicate through TCP/IP. To manage a system, some type ofmanagement protocol (for example, SNMP, DMI, or WBEM) must be present on the system.Examples of systems include servers, workstations, desktops, portables, routers, switches, hubs,and gateways.

system group A group of systems based on a system collection; a static snapshot of the source collection at thetime the system group was created. Used for authorizations.

141



system healthstatus

This is aggregate status all of the status sources (which can be SNMP, WBEM, DMI, and HTTP)that are supported on a target system, with the most critical status being displayed. The followingare the different system health statuses that can be displayed:

• Critical HP SIM can no longer communicate with the system. The system was previouslydiscovered but cannot be pinged. The system might be down, powered off, or no longeraccessible on the network because of network problems.

• Major A major problem exists with this system. It should be addressed immediately. Forsystems running an HP Insight Management Agent, some component has failed. The system

might no longer be properly functioning, and data loss can occur.

• Minor A minor problem exists with this system. For systems running Insight Management Agent, some component has failed but the system is still functioning.

• Warning The system has a potential problem or is in a state that might become a problem.

• Normal The system is functioning correctly.

• Disabled The system is disabled from monitoring but is not necessarily turned off.

• Unknown HP SIM cannot obtain management information about the system.

• Informational The system might be in a transitional or non-error state.

systemidentification

Identifying information about systems. This information is stored in the database. The followinginformation 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 the System tab. The system informationincludes:

• Network address

• Network name

• Description

• Contact

• Location

• System links

system informationusing DMI

Agents that conform to the DMI V2 standard and have passed testing. The list of compliant DMI V2 agents can be found on http://www.dmtf.or g.

system informationusing SNMP

Agents that conform to SNMP MIB-2 standards.

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

System

ManagementHomepage (SMH)

An integrated piece of software used by the HP suite of HP Web-enabled System Management

Software to communicate over HTTP and HTTPS. It provides a uniform set of functionality andsecurity to HP Web-enabled System Management Software.

system overviewreport

A report indicating the state of systems that is available at the time that HP SIM is first opened. A system search result contains the number of systems that are registered with the HP SIMdatabases. Systems are grouped by their status conditions. Each number in a column is a hyperlinkto a more detailed list of systems, which displays the systems that correspond to the number inthe overview.

system properties properties can be set for a single system or for multiple systems at the same time and includeoptions such as system name, system type, system sub-type, operating system version, assetnumber, contact information, and whether or not the system properties can be changed or updatedby the discovery process.

142 glossary

http://www.dmtf.org/





system search Logical grouping of systems into a collection based on information in the HP SIM database. Aftera search is defined, you can display the results from the system view page or associate it with amanagement task.

system searchresults

The result of a system search.

system statuspanel

The section of the GUI on the left of the screen that displays status information and system orevent alarms.

system type One of 12 supplied types. You can add your own based on one of these types. For example,

use Server type to create MyServer type. It is still a server and is reported on in the same way,but it has your designation.

System TypeManager (STM)

A utility that enables you to modify the default behavior of the discovery and identification ofobjects classified as Unknown or as another category of systems are discovered and identifiedprecisely as you require. HP SIM discovers and identifies the system and applies the newinformation when an Unknown system matches a rule set that you specify as the primary rule set.Furthermore, creating the new system type provides a System Link page for viewing theinformation returned from the system agent or from the communication protocol of SNMP or DMI.

T

task An executed instance of an HP SIM tool, on one or more systems, with a specific set of arguments.

task scheduling A master scheduling tool for the scheduling of polling, control, and notification tasks.template files Template files are a concept that was used before HP SIM had multiple automatic discovery tasks.

Template files should no longer be used. However, a template file enables you to create the samedata range (IP ranges, and so on) that would be entered in a discover IP inclusion range. Theautomatic discovery task can have as input one or more template files. However, template filescannot be nested.

threshold A preset limit that produces an event when the limit is reached or exceeded.

Tomcat An open source implementation of Java Servlet and JavaServer Pages technologies that is usedby HP SIM as a web server.

tool An application, command, or script that can be executed by HP SIM on one or more systems toperform a task.

toolbox A defined set of tools that a user might need for a particular task, such as database administrationor software management. Each HP SIM toolbox is associated with a set of tools and authorizations.

trap An unsolicited message generated by a management agent that indicates that an event hasoccurred. For example, a monitored item has exceeded a set threshold or changed status.Previously called alarm.See also event.

trap categories Event collection systems found by event type. SNMP traps categorized by HP SIM into logicalgroups according to their functions.

trap forwardingaddress

The IP address of a system that has been specified to receive trap notifications forwarded by theHP SIM systems.

type The classification of a system, which identifies it as a standard system type. The system types areclient, cluster, portable, printer, remote access device, repeater, router, server, switch, unknown,workstation, and other.

143



U

uncleared eventstatus

Events that have a Critical, Major, Minor, Normal, or Informational severity and have not beencleared or deleted from the database. Events can be cleared without being deleted from thedatabase by using the Clear events menu option.

• Critical. A failure has occurred, and immediate attention is 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 required. This status is provided as useful information

unknown status HP SIM cannot obtain management information about the system using SNMP or DMI. Althoughno management instrumentation information is available, the system can be pinged. It might havean invalid community string or security setting.

user A network user with a valid login on the Central Management Server that has been added to HPSIM.

user accounts Accounts used to sign in to HP SIM. These accounts associate a local Windows user account ora domain account with privilege levels and paging attributes inside HP SIM.

user group A group of users defined on the Central Management Server operating system that has beenadded to HP SIM. Members of the user group in the operating system can sign in to HP SIM.

V

VCA log A listing of all the software maintenance tasks completed by the HP Version Control Agent andreports resulting from those tasks.

version control Referred to as the HP Version Control Repository Manager installed on a Windows system for Windows and Linux ProLiant systems, and Software Distributor on HP-UX operating systems.Provides an overview of the software status for all managed ProLiant or Integrity systems and canupdate system software and firmware on those systems programmatically using predeterminedcriteria. Version control identifies systems that are running out-of-date system software, indicates

if an upgrade is available, and provides reasons for upgrading. For HP-UX systems, SoftwareDistributor can be launched from an HP SIM Central Management Server against one or moreinstalled HP-UX systems.

Virtual Server Environment (VSE)

An integrated server virtualization offering for HP-UX, Linux, and Windows servers that providesa flexible computing environment maximizing usage of server resources. VSE consists of a poolof dynamically sizeable virtual servers; each can grow and shrink based on service level objectivesand business priorities. For more information, see http://hp.com/go/vse.

W

WBEM Services HP WBEM Services for HP-UX is an HP product that uses WBEM and DMTF standards to manageHP-UX system resources.

Web-BasedEnterpriseManagement(WBEM)

An Industry initiative to provide management of systems, networks, users, and applications acrossmultiple vendor environments. WBEM simplifies system management, providing better access toboth software and hardware data that is readable by WBEM compliant applications.

Web-BasedEnterprise Services(WEBES)

A tool suite that is aimed at preventing or reducing the downtime of a system.

Web-launch aware(WLA)

A run type for tools that are launched in a web browser using a web server. WLA tools can bedesigned to deal with multiple systems.

WindowsManagementInstrumentation(WMI)

An API in the Windows operating system that enables systems in a network, typically enterprisenetworks, to be managed and controlled.

144 glossary

http://hp.com/go/vse

http://hp.com/go/vse



workspace The section of the GUI where tools are displayed.

X

X client An application or tool that appears on an X server. X clients can also be called X applications.

X server A local application that accepts X client requests and acts on them.

X Window System A cross-platform windowing system that uses the client/server model to distribute services acrossa network. It enables applications or tools to run on a remote computer.

XML document A collection of data represented in XML.

145



Index

A About HP Service Essentials Remote Support Pack

Understanding the Remote Support Software Manager,70

About the SWM Initialization Process, 70accessing the graphical user interface, 116active time-out, 121add authorizations, 46add toolboxes, 46add user groups, 45add users, 44administration

creating users, 39agents, 56 All Tools toolbox, 14applying

time filters, 41

audit log, 15configure, 122

authorizations, 13add, 46creating users, 39

automatic discovery, 38–39, 51automatic event handling, 37, 41, 49automatic event handling task

with specified attributes, 41automatic event handling tasks

creating, 41 Automation Levels and Scheduling in Software Manager,

70

Bbanner

customize, 118

Ccentral management server

Custom install HP Systems Insight Manager, 28overview, 7requirements, 20Typical install HP Systems Insight Manager, 28

certificate authority, 18CMS (see central management server)

configuring for RSP, 89command line interface

Logging in, 120security, 16

commands, 120communication protocols (see management protocols)community strings, 38configuration

add authorizations, 46add toolboxes, 46add user groups, 45

add users, 44

audit log, 122automatic event handling, 49data collection CPU utilization, 121discovery, 51email settings, 48

lifetimes for Task Result entries, 123managed system, 56paging settings, 48protocol settings, 42time-out policy, 121

configuration options, 121configuration rights

full, 14limited, 14no, 14

configure paging settings, 48configuring

CMS, 89

first time wizard, 37, 41HP SIM, 37, 41

configuring email settings, 48conventions, typographic, 2CPU utilization, 121creating

automatic event handling tasks, 41users, 39

custom install, 25customization options, 121customizing the graphical user interface, 118

Ddata collectionperformance, 121

database, 15remote for improved performance, 121

default time-out period, 121default toolboxes, 14Desktop Management Interface, 18disabling

discovery task, 39discovery, 37, 41, 51, 56

automatic, 38–39discovery task

disabling, 39enabling, 39system automatic discovery, 39

Distributed Task Facility, 17DMI, 17–18, 56DTF, 17

Ee-mail

encoding, 41html, 41message format, 41

pager/SMS, 41

146



e-mail settings, 37, 41email

configure, 48email settings, 37enabling

discovery task, 39events

creating tasks, 41examples, 56

execute-as user, 56

Ffeatures, 7firewalls, 19firewalls ports, 19first setup (see initial setup)First Time Wizard, 37first time wizard, 37, 41

SNMP settings, 38system automatic discovery, 39system event handler task, 41

WBEM settings, 38Form or Action Submission Windows, 70frequently scheduled task lifetimes, 123full configuration rights user, 14

Ggetting started, 42global protocol settings, 38graphical user interface

customize, 118logging in, 116overview, 116security, 16

GUI (see graphical user interface)

Hhealth status section, 116Home page

customize, 118overview, 116

HP Remote Support Software Manager ConfigurationOptions, 70

HP Systems Insight Managercommands, 120features, 7

HP Systems Insight Manager database, 15HP Systems Insight Manager Windows Installation, 25HTTPS, 17–18

Iin-place migration, 101initial setup, 42, 56 (see managed systems)

add authorizations, 46add toolboxes, 46add user groups, 45add users, 44automatic discovery, 51

automatic event handling, 49

configuring email settings, 48configuring paging settings, 48discovery, 51manual discovery, 52protocol settings, 42

Initializing the HP Remote Support Software ManagerSoftware Manager, 70

Insight Manager 7 comparison, 7install

central management server requirements, 20managed system requirements, 21process overview, 20

install HP Systems Insight Manager Windows CMS, 28

Llast result task lifetimes, 123legend, 116lifetimes for Task Result entries, 123limited configuration rights user, 14Logging in

command line interface, 120logging ingraphical user interface, 116

Mmanaged node (see managed system)managed system

discovery of, 51overview, 7protocol settings on the CMS, 42requirements, 21setup, 56

managed systems Windows, 56

management agents, 56management domain

overview, 7management protocols, 17, 56

DMI, 18HTTPS, 18SNMP, 18SSH, 17 WBEM, 17

Managing Software Downloads and Installations, 70manpages, 120

manual discovery, 52Microsoft SQL Server 2000, 15Microsoft SQL Server Desktop Engine (MSDE), 15migrating Insight Manager 7

data migration tool, 101Modifying Automation Levels Software Manager, 70Modifying Bandwidth Settings, 86Modifying HP Remote Support Software Manager Software

Manager Settings, 70Modifying Package Update Scheduling, 70Modifying Proxy Settings, 86Modifying the Global Update Window, 70

monitor time-out, 121

147



Monitor Tools toolbox, 14mxexec, 39mxuser, 39

Nnetwork client

overview, 7new features, 7no configuration rights user, 14

node (see managed system)node group (see system group)

OOracle, 15

Ppaging

configure, 48parameter

DataCollectionThreadCount, 121EnableSessionKeepAlive, 121

LOG, 122MX_JOB_CACHE_TIME_COMPLETED_JOBS, 123MX_JOB_MAX_COMPLETED_JOB_AGE, 123MX_JOB_MAX_COMPLETED_JOBS_PER_TASK, 123MX_JOB_MIN_COMPLETED_JOBS_PER_TASK, 123MX_LOG_FILEEXT, 122MX_LOG_FILENAME, 122MX_LOG_FILESIZE, 122MX_LOG_QUEUESIZE, 122MX_LOG_ROLLFILEEXT, 122session-timeout, 121

ports, 19ProLiant Support Pack, 56protocol settings, 42protocols, 17, 56

setting global, 38SNMP, 38 WBEM, 38

RReinstalling the Remote Support Software Manager, 88remote migration, 101Remote Support Software Manager Device and Access

Requirements, 70Remote Support Software Manager Supported Proxy

Settings, 70removing HP Systems Insight Manager

Windows CMS, 115Removing or Reinstalling the Remote Support Software

Manager, 70repository (see database)requirements

central management server, 20managed system, 21

RSP (see Service Essentials Remote Support Pack)Running the Remote Support Software Initialization Process,

72

Ssearch, 116Secure HTTP, 18Secure Shell , 17security

access, 16certificate authority, 18command line interface, 16firewalls, 19

graphical user interface, 16ports, 19self-signed certificates, 18 Web server, 18X applications, 19

self-signed certificates, 18Service Essentials Remote Support Pack, 89Servicecontrol Manager 3.0 comparison, 7setting up

automatic event handling, 49managed systems - Windows, 56

setup

add authorizations, 46add toolboxes, 46add user groups, 45add users, 44automatic event handling, 49configure paging settings, 48configuring email settings, 48discovery, 51managed systems, 56protocol settings, 42

short and long task lifetimes, 123silent install, 25Simple Network Management Protocol, 18SMI CIMOM, 38SNMP, 17–18, 37–38, 41, 56spoofing, 18SSH, 17, 56Storage Management Initiative Specification

storage, 65system automatic discovery, 39system group

overview (see )system key, 116

TTask Results Page

entry lifetime configuration, 123time filters

applying, 41time-out policy

configuration, 121toolboxes, 13

add, 46tools, 14

command line, 14web, 14X Window, 14

troubleshooting, 125

148 Index



types of tools, 14typical install, 25Typical upgrade

upgrade, 106typographic conventions, 2

UUnderstanding and Configuring Customer Notifications

and Reports, 70

Understanding and Configuring HP Reports, 70Understanding and Modifying Scheduling in Software

Manager, 70Understanding and Using the Actions Option, 70Understanding Automation Levels Software Manager, 70Understanding Effective Automation Levels, 70Understanding Factory Automation Levels, 70Understanding the Remote Support Software Manager,

70Understanding User Automation Levels, 70Uninstall Central Management Server

removing HP Systems Insight Manager on Windows,

115upgradeCustom upgrade HP Systems Insight Manager, 107

upgrading HP Systems Insight Manager, 106user groups

add, 45user settings, 37, 41user templates, 39users, 39

add, 44add authorizations, 46creating 39

HP Systems Insight Manager Installation and Configuration Guide

Documents

Transcript of HP Systems Insight Manager Installation and Configuration Guide