HP Systems Insight Manager 5.2 Installation and Configuration Guide for Microsoft Windows

Transcription

1 HP Systems Insight Manager 5.2 Installation and Configuration Guide for Microsoft Windows * * Printed in the US HP Part Number: Published: 2008 Edition: 5.2

2 Copyright 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 Sales and Service Office. U.S. Government License Proprietary computer software. Valid license from HP required for possession, use or copying. Consistent with FAR and , 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 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 Tomball Parkway Houston, Texas Or, use this web form to send us feedback: Typographic Conventions We use the following typographical conventions. audit(5) Book Title Command ComputerOut Emphasis Emphasis KeyCap Term UserInput Variable 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). Title of a book. On the web and on the Instant Information DVD, it might be a hot link to the book itself. Command name or qualified command phrase. Text displayed by the computer. Text that is emphasized. Text that is strongly emphasized. Name of a keyboard key. Note that Return and Enter both refer to the same key. Defined use of an important word or phrase. Commands and other text that you type. Name of a variable that you can replace in a command or function or information in a display that represents several possible values.

3 [ ] 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.

4 Table of Contents 1 Product overview...9 Features...9 HP SIM management...9 Security...9 Installation...10 Discovery...10 Custom tools...10 Reporting...10 Partner applications...10 What's new?...13 Installation...13 First Time Wizard...13 Security...13 Users and authorizations...13 Discovery and identification...13 Setting up managed systems...14 Data Collection...14 Automatic event handling...14 License Manager...15 Reporting...15 Navigation...15 Task Wizard...15 Miscellaneous features...15 Product architecture...15 Central management server...15 Managed systems...16 Web-browser clients...16 Authorizations...16 Toolboxes...17 Tools...17 Information storage...18 HP SIM audit log...18 Database...18 Database software...19 Secure access...19 Command line interface...19 Graphical user interface...19 Secure data transmission...20 Management protocols...20 Web server security...21 Self-signed certificates...21 X application security...22 Managing servers behind a firewall Installation overview and requirements...23 First time install process overview...23 Upgrade overview...23 System requirements...23 Windows Central Management Server...23 Managed system requirements and recommendations...24 SSH requirements Installing HP SIM on the Central Management Server (CMS) for the first time...28 Preparing the system...28 Typical install...33 Custom install...37 Table of Contents 4

5 Silent install...46 Next steps Configuring HP SIM using the First Time Wizard...49 Using the First Time Wizard...49 Configuring the managed environment...50 Entering WBEM settings...50 Entering SNMP settings...51 Enabling automatic system discovery...51 Configuring managed systems...52 Configuring settings...52 First Time Wizard summary...53 Finishing the First Time Wizard...53 Operating-system-specific collections, reports, and tools...53 Operating-system-specific collections...53 Operating-system-specific reports...54 Operating-system-specific tools...54 Windows...54 Linux...54 HP-UX...55 Other Configuring HP SIM using the Options menu...56 Configuring protocol settings...56 Users and authorizations...58 Adding users...58 Adding user groups...59 Adding toolboxes...60 Adding authorizations...60 Configuring settings...62 Configuring paging settings...62 Setting up automatic event handling...63 Configuring and executing discovery...65 Configuring and executing automatic discovery...65 Configuring and executing manual discovery Setting up and configuring managed systems...70 Setting up managed systems from a Windows CMS...70 Configuring the managed system software using the Configure or Repair Agents feature from the CMS...70 Setting up managed storage systems...76 Installing SMI-S providers...77 Verifying SSL...77 Configuring SMI-S providers...77 Configuring HP SIM to discover storage systems Initializing the Remote Support Software Manager on the Central Management Server (CMS)...78 Understanding the Remote Support Software Manager...78 RSSWM device and access requirements...78 HP Remote Support Software Manager Configuration Options...79 Initializing the HP Remote Support Software Manager Software Manager...80 About the Initialization Process...80 Completing the Remote Support Software Initialization Process...81 Running the Remote Support Software Initialization Process...81 Using the HP Remote Support Software Manager...87 Modifying HP Remote Support Software Manager Settings...87 Form or Action Submission Windows...87 Automation Levels and Scheduling in the Software Manager...88 Understanding Automation Levels in the Remote Support Software Manager...88 Modifying Automation Levels in the Software Manager...90 Understanding and Modifying Scheduling in Software Manager...92 Table of Contents 5

6 Modifying the Global Update Window...92 Modifying Package Update Scheduling...93 Managing Software Downloads and Installations...94 Understanding and Configuring HP Reports...96 Understanding and Configuring Customer Notifications and Reports...96 Modifying Proxy Settings...97 Modifying Bandwidth Settings...98 Understanding and Using the Actions Option...98 Removing or Reinstalling the Remote Support Software Manager...99 Reinstalling the Remote Support Software Manager Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager Types of migration Performing an in-place migration Performing a remote migration Upgrading HP Systems Insight Manager from 4.x or later Upgrading from HP SIM 4.x or later Typical upgrade Custom upgrade Silent upgrade Next steps Uninstalling HP Systems Insight Manager Uninstalling HP Systems Insight Manager from a Windows system Using the graphical user interface Accessing the GUI Security Alert in Internet Explorer Graphical user interface features Customizing the GUI Customizing the Home Page Customizing the System Status Panel Using the command line interface Logging in to the CLI Logging in to the CMS directly Using an SSH client to log in remotely manpages Configuration options CPU utilization during data collection Overview Implementation GUI time-out policy Overview Implementation HP SIM audit log configuration Overview Implementation Lifetimes for entries on the Task Results Page Overview Implementation Troubleshooting Installation Upgrade Sign-in Table of Contents

7 Password glossary Index Table of Contents 7

8 List of Tables 6-1 Version Support Matrix for components used for install

9 1 Product overview Features HP Systems Insight Manager (HP SIM) is the foundation for the HP unified server-storage management strategy. HP SIM is a hardware-level management product that supports multiple operating systems on HP ProLiant, Integrity and HP 9000 servers, HP StorageWorks MSA, EVA, XP arrays, and third-party arrays. Through a single management view of Microsoft Windows, HP-UX 11iv1, HP-UX 11iv2, HP-UX 11iv3, and Red Hat, and SuSE Linux, 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 Enterprise Management (WBEM) to deliver the essential capabilities required to manage all HP server platforms. HP SIM can be extended to provide systems management with plug-ins for HP clients, storage, power, and printer products. Plug-in applications for workload management, capacity management, virtual machine (VM) management, and partition management using HP Integrity Essentials enable you to choose the value-added software that delivers complete lifecycle management for your hardware assets. HP SIM management Security Fault management and event handling HP SIM provides proactive notification of actual or impending component failure alerts. Automatic Event Handling enables you to configure actions to notify appropriate users of failures through , pager, or Short Message Service (SMS) gateway, and enables automatic execution of scripts or event forwarding to enterprise platforms, such as HP OpenView Network Node Manager or HP OpenView Operations. Consistent multisystem management HP SIM initiates a task on multiple systems or nodes from a single command on the CMS. This functionality eliminates the need for tedious, one-at-a-time operations performed on each system. Two user interfaces HP SIM provides the option of a browser-based GUI or a command line interface (CLI) to make it easy to incorporate HP SIM into your existing management processes. Web-Based Enterprise Management (WBEM) indications for HP-UX, Linux, and Storage Management Initiative Specification (SMI-S) devices HP SIM enables you to use the GUI or CLI to subscribe and unsubscribe to WBEM indications. Role-based security HP SIM enables effective delegation of management responsibilities by giving system administrators granular control over which users can perform specific management operations on specific systems. Manage Secure Shell (SSH) keys The SSH Keys feature enables you to view and manage, from the CMS, the public SSH keys stored in the known_hosts file. The SSH keys enable the CMS to authenticate a secure connection with a managed system. 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. Configure or Repair Agents This feature enables you to repair credentials for SNMP settings, System Management Homepage, or Management HTTP Server trust relationships on Windows, Linux, and HP-UX systems supported by HP SIM. Features 9

10 Installation Discovery Custom tools Reporting Easy and rapid installation. HP SIM can be installed, quickly and easily, on HP-UX 11i v1, HP-UX 11i v2, or HP-UX 11i v3 on PA-RISC/Integrity server platforms, or on ProLiant platforms running Windows or Linux. First Time Wizard HP SIM provides you with step-by-step, online instructions for performing the initial configuration of HP SIM. The wizard helps you configure HP SIM settings on the Central Management Server (CMS). 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 prevent discovery of unwanted system types. HP SIM defines tools using simple XML documents that enable you to integrate off-the-shelf or custom tools. These tools can be command line tools, web-based applications, or scripts. Access to these integrated tools is governed by role-based security. Data collection and inventory reports HP SIM performs comprehensive system data collection and enables you to quickly produce detailed inventory reports for managed systems. Reports can be generated in HTML, XML, or CSV format. Data collection and reporting has been added for HP Superdome systems and 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), and hard partitions (npars). The type of data collected depends on what filters are selected, Snapshot comparisons HP SIM enables you to compare configuration snapshots of up to four different servers, or compare configuration snapshots of a single server over a period of time. This functionality assists IT staff in pinpointing configuration issues that can contribute to system instability. Snapshot comparisons can also 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 and HP Integrity 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 Distributor is integrated into HP SIM. HP Service Essentials Remote Support Pack HP SIM includes a new HP Service Essentials Remote Support Pack plug-in. This plug-in leverages elements of the HP Service Essentials Remote Support Pack (Remote Support Pack) technology and provides integrated HP SIM and Remote Support Pack capability. This capability deploys with 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 identify and prevent potentially critical hardware problems Faster restoration of your supported systems and devices to operational status Less disruption to your company s revenue-generating activities and business productivity 10 Product overview

11 The HP SIM single view of your data center is enhanced, with the addition of the following serviceability attributes Contract and warranty details for your systems Service event view, including remote support details such as HP case ID and service case status CMS heartbeat polling, monitored by HP, allowing early notification to your IT team that event submission to HP is not working Web-Based Enterprise Services and Open Service Event Manager These analysis tools 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 service offering and as standalone tools for HP Services customers. WEBES and OSEM generate service notifications to HP SIM through a specific SNMP trap type if analysis determines there are serviceable events. If the Remote Support Pack is installed, the service notification provided by WEBES and OSEM also provides status about the remote support incident. System Management Homepage The System Management Homepage provides a consolidated interface for single-system management. By aggregating the data from HP web-based agents and management utilities, the System Management Homepage provides a common, 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 Performance Management Pack HP SIM provides a software solution that detects, analyzes, and explains hardware bottlenecks on HP ProLiant servers and HP StorageWorks Modular Smart Array (MSA) shared storage. The HP Performance Management Pack (PMP) tools that are available in HP SIM include Online Analysis, Offline Analysis, CSV File Generator Report, System Summary Report, Static Analysis Report, Configuration, Licensing, and Manual Log Purge. The PMP tools operate in conjunction with HP SIM. No software installation on the monitored servers is required, other than the Insight Management Agents. PMP 4.7 includes the following features: Support for HP SIM 5.x (PMP 4.3 does not support HP SIM 4.x.) Support for Oracle databases (local or remote) The following servers are supported on 4.3: ProLiant BL465c G1 servers ProLiant BL68c G1 servers ProLiant BL25p G2 servers ProLiant BL45p G2 VR1 servers ProLiant DL320 G5 servers ProLiant DL360 G5 servers ProLiant DL365 servers ProLiant DL585 G2 servers ProLiant ML310 G4 servers Integrity rx7620 servers Integrity rx7640 servers Integrity rx8620 servers Integrity rx8640 servers Integrity Superdome servers Note: The Integrity Superdome includes support for the Intel Itanium 2 Montecito, M9M, and MX2 processors. Ultra 160 SCSI Adapter HP NC370i NIC Features 11

12 rx8620 Gigabit LoM (5701) NIC rx8640 Gigabit LoM (5703) NIC LAN/SCSI Combo Card (Castor, AB290A) The following new operating systems are supported on PMP 4.3: VMware ESX VMware ESX VMware ESX VMware ESX 3.0 Go to for more information about HP Performance Management Pack. HP ProLiant Essentials Vulnerability and Patch Management Pack HP ProLiant Essentials Vulnerability and Patch Management Pack identifies and provides advice to resolve security vulnerabilities. It delivers advanced patch management through automated acquisition, optimized deployment, and continuous enforcement of security patches. 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 about the HP ProLiant Essentials Vulnerability and Patch Management Pack, go to the HP ProLiant Essentials Vulnerability and Patch Management Pack at vpm. HP ProLiant Essentials Virtual Machine Management Pack Virtual machine management capabilities integrated into HP SIM extend its capabilities to deliver unified management of an IT infrastructure consisting of both physical and virtual server resources, and simplify and consolidate the provisioning, management, and migration of all server resources from one central interface. The virtual machine management capabilities of HP SIM are enabled by the integration of the HP ProLiant Essentials Virtual Machine Management Pack and the HP Server Migration Pack - Universal Edition. HP ProLiant Essentials Virtual Machine Management Pack The Virtual Machine Management Pack provides central management and control for the Microsoft's Virtual Server and the VMware's GSX Server or ESX Server virtual machines. Using the Virtual Machine Management Pack, all virtual machines 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 machine guests 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 Agent. The Virtual Machine Management Pack is now integrated into HP SIM. See for documentation and more information about the Virtual Machine Management Pack. HP Server Migration Pack - Universal Edition The HP Server Migration Pack - Universal Edition (SMP Universal) extends the functionality of the Virtual Machine Management Pack to provide integrated physical-to-virtual (P2V), virtual-to-virtual (V2V), virtual-to-proliant (V2P), and physical-to-proliant (P2P) migrations. SMP Universal enables you to simplify the server consolidation process. To purchase additional licenses, see HP BladeSystem Integrated Manager in HP Systems Insight Manager HP SIM delivers a blade environment designed to consolidate access to blade deployment, configuration, and monitoring tools. Picture views are available of racks and enclosures. The HP BladeSystem Integrated Manager is automatically installed with HP SIM. No license key is required. To access HP BladeSystem Integrated Manager, select Tools Integrated Consoles HP BladeSystem. See products/servers/integrity-bl/p-class/60p/index.html for more information. HP ProLiant Essentials Rapid Deployment Pack The HP ProLiant Essentials Rapid Deployment Pack (RDP) is a multiserver deployment tool that enables IT administrators to easily deploy large numbers of servers in an unattended, automated fashion. The RDP is installed separately from HP SIM. It requires a license for each server managed. You must register your RDP product to purchase licenses or obtain a 10-node 30-day license before installing RDP (a 10-node 7-day evaluation license is built into the 12 Product overview

13 software). The RDP is installed from its own DVD. See for information about RDP including a link to obtain evaluation licenses or register your product. See the RDP documentation for network environment setup, prerequisites for the deployment server, and installation instructions. HP Storage Essentials HP is changing the economics of managing the data center. HP Storage Essentials is the first open, standards-based suite of storage products designed to integrate into HP SIM. See for more information about HP Storage Essentials. HP Insight Power Manager HP Insight Power Manager (IPM) is an integrated power-monitoring and management application that provides centralized control of server power consumption and thermal output at the datacenter level. It extends the capacity of datacenters by enabling the user to control the amount of power and cooling required for ProLiant servers. Built on ProLiant Power Regulator technology, extends new server energy instrumentation levers into HP SIM for greater Unified Infrastructure Management. Support for HP-UX Serviceguard clusters HP SIM recognizes HP-UX Serviceguard clusters and displays them in the GUI. HP Serviceguard Manager opens when you click a Serviceguard cluster in a search list and provides information on the clusters. What's new? Installation Replaced MSDE in HP SIM Windows installation with SQL 2005 Express Edition with Service Pack 2. Added Central Management Server (CMS) and managed system support for Windows Server 2008 and Windows Vista. Streamlined installation by removing HP ProLiant Essentials Vulnerability and Patch Management Pack and HP Performance Management Pack from the default installation set Added support for silent installation for Oracle database First Time Wizard Security Streamlined the application by enabling you to specify the operating systems that are managed in your environment, resulting in collections, reports, and tools for the selected operating systems only. Ability to automatically configure managed systems as discovery runs. Ability to test configurations as settings are configured. Multiple names in SSL web server certificate to alleviate name mismatch errors by the browser when using different names for the system. Users and authorizations HP SIM allows for any user to be configured to have access to features like discovery, view audit logs, automatic event handling and more. In addition, there is a single setting to enable users to add or update security settings on HP SIM. Discovery and identification Simple or Fully Qualified Domain Names (FQDN) host names can be included in ping inclusion and exclusion ranges for discovery. Discovering and identifying the HP Insight Management WBEM Providers for Windows Server 2003/2008 for getting a rich set of hardware information for HP ProLiant hardware. What's new? 13

14 Ability to discover all npars in a complex, including those not currently active, from information gathered in one npar. Ability to discover all vpars in a vparmonitor, including those not currently active, from information gathered in one vpar. Setting up managed systems HP SIM features have been enhanced to make setting up managed systems an easier task. The Configure or Repair Agents feature now includes the following enhancements: HP Insight Management Agents can be installed on ProLiant servers running Windows using the Initial HP ProLiant Support Pack task from a Windows Central Management Server (CMS). SNMP traps can be sent from the managed systems to check the trap reception in HP SIM CMS. WBEM indications can be sent from the managed systems that support WBEM providers and verifies reception in the HP SIM CMS running HP-UX. Configure Single Sign on to managed systems. Can install and configure HP Version Control Agent and Secure Shell (SSH) from Configure or Repair Agents. Can install and configure WBEM providers from Configure or Repair Agents. The new Manage Communications feature enables you to troubleshoot communication problems between the CMS and the managed systems. Data Collection You can now collect and display instant capacity (icap) properties for Cells and Processors, for an icap enabled Complex, using Web based enterprise management (WBEM) protocol. On ISS HP Insight Management WBEM Providers for Windows Server 2003/2008 enabled managed nodes, data collection will give preference to HP Insight Management WBEM Providers for Windows Server 2003/2008 over WMI/SNMP for certain attributes. NOTE: Currently, there is limited SNMP support in HP Insight Management WBEM Providers for Windows Server 2003/2008. When data collection prefers over to HP Insight Management WBEM Providers for Windows Server 2003/2008, a few of the items in the report that were collected from SNMP earlier would be blank. NOTE: The icap provider is available on HP-UX 11i v3 (11.31), HP-UX 11i v2 (11.23) and HP-UX 11i v1 (11.11) which can only be installed on HP 9000 and Integrity servers. Added Horizontal discovery of node partitions (npars) for cell-based Integrity servers or HP 9000 servers. Added Horizontal discovery of virtual partitions (vpars) for cell-based HP-UX 9000 servers or procedure-based HP-UX 9000 servers. Added Data collection of software/firmware (sw/fw) baseline name and version for systems that have a Version Control Agent (VCA) installed. Automatic event handling Support for new ProLiant WBEM indications Therefore, any event collection containing event type criteria having an SNMP trap that correlates to a WBEM indication will be upgraded and the WBEM indications will be selected. User pager information can be specified when creating or managing automatic event handling tasks. 14 Product overview

15 License Manager Reporting Navigation Task Wizard Extended support for SSH and CLP to include ilo 2 specific extensions. Added license transfer with ilo 2 using the License Manager menu functions in the Graphical User Interface (GUI). Added a Graphical User Interface (GUI) for input of SSH credentials. New HP Version Control Agent report that displays baseline information. Added data collection of software/firmware (sw/fw) baseline name and version for systems that have a Version Control Agent (VCA) installed. The tool search feature provides a quick way to find a tool by entering text (often less than a single word) that is used to search and filter, textually, based on tool names, tool locations in the HP SIM cascading menu structure, and tool descriptions. The Quick Launch menu provides single click access to frequently used tools and can be customized to select which tools are displayed in the menu. Go back to link that returns you to the last viewed collection or tool, including the System Page. You can maximize the workspace so that the System Status overview, Search, System and Event Collections panels, and the HP SIM menus are collapsed, and the banner is minimized. You can also restore the workspace to the default size with a single click. Improved performance. Added ability to select target systems using a search tool. Miscellaneous features You can search software and firmware installed on HP-UX systems. Property pages are implemented for HP Insight Management WBEM Providers for Windows Server 2003/2008 and for OpenVMS providers. HP-UX Property pages have been updated to reflect new HP-UX providers. Support on Property pages for HP-UX 11i.x, Linux Itanium Processor Family (IPF), Windows Server 2003 and 2008, Windows XP, Windows Vista, Windows Longhorn, and OpenVMS. Product architecture HP Systems Insight Manager (HP SIM) leverages a distributed architecture that is divided into three types of systems: Central Management Server (CMS), managed systems, and web-browser clients. The CMS with the managed systems together are called the HP SIM management domain. Central management server Each management domain has a single CMS. The CMS is the system in the management domain that executes the HP SIM software and initiates all central operations within the domain. In addition to the HP SIM software, the CMS maintains a database for storage of persistent objects that can reside locally or on a 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 the network. 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 manage the domain using a separate CMS. Product architecture 15

16 Managed systems Systems that comprise a management domain are called managed systems. A system can be any device on the 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 IP address associated with them. A managed system can be managed by more than one CMS, if desired. Managed systems to be managed must have one or more management agents installed. There is a wide variety of agents, such as the ProLiant Insight Management Agents based on SNMP, or the Windows Management Instrumentation (WMI) for Windows systems,, or Web-Based Enterprise Management (WBEM) providers, and System 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 into the managed system to execute commands through scripts. Web-browser clients HP SIM can be accessed from any supported browser client. The network client can be part of the management domain. However, you must be running a compatible browser to access the GUI or an SSH client application to securely access the CLI. Access to the web server on the CMS can be restricted to specific IP address ranges for specific users. Authorizations Authorizations give users access to view and manage systems. An authorization is composed of users, toolboxes, and discovered systems. When you first access the Authorizations tab, a table appears listing all authorizations and includes the following information: User/User Group This column includes all valid users and user groups. A user group is displayed in bold type. Group-based users are not displayed in this table. However, they are listed in the authorizations for users table and are displayed in italics. Toolbox This column displays the toolboxes assigned to the user or user group for each authorization. System This column displays the systems on which the user or user group has authorizations. A system group is displayed in bold type. Auto This column displays Auto if the authorization is set to automatically update when the collections that the authorization is based upon are updated. A system group is a group of systems based on a system collection that is used for authorizations. Authorizations that use system groups are updated automatically when a change is made to the system collection that the system group is based upon. For authorizations to be updated automatically, the option, Do not track changes. If this collection changes, the authorization will not change must not be selected. You can view all authorizations, or you can view filtered authorizations for users, user groups, toolboxes, system groups, and individual systems. Select the option from the Authorizations for box, and then select the name from the Select name box. The Authorizations tab provides the following options: Creating new authorizations Select Options Security Users and Authorizations Authorizations, and then click New. The New Authorizations section appears. This option is not available for group-based users. Instead, create authorizations for the user group of the group-based user. Deleting authorizations Select Options Security Users and Authorizations Authorizations, select authorizations to delete, and then click Delete. A dialog box appears. To delete the authorizations, click OK, or to cancel the deletion, click Cancel. This option is not available for group-based users. Instead, delete authorizations for the user groups of the group-based user. Viewing and printing authorization reports Select Options Security Users and Authorizations Authorizations, and then click Report. The Authorizations Report window appears. To print the report, select File Print. 16 Product overview

17 Toolboxes Tools Updating authorizations Select Options Security Users and Authorizations Authorizations, select an authorization using a system group based on a collection, and then click Update. The Update Authorizations section appears. NOTE: To sort the information in ascending or descending order, click the appropriate column heading. The column heading that includes the arrow is the column by which the list is sorted. If the arrow is pointing up, the list is sorted in ascending order. If the arrow is pointing down, the list is sorted in descending order. Run SE user security configuration Authorizations defined in HP SIM are not automatically shared with HP Storage Essentials. To update user security in HP Storage Essentials, click the Run SE user security configuration link. You can define separate authorizations in HP Storage Essentials on the Users page. By default, HP SIM users have limited read access to all HP Storage Essentials managed systems and features. You can modify access privileges on the Roles page. Use the Organizations page to control the HP Storage Essentials managed systems that are visible to HP SIM users. The Toolboxes section enables you to configure groups of tools. The following toolboxes are created during the installation process:: The All Tools toolbox contains all tools in the Central Management Server (CMS). The Monitor Tools toolbox contains tools that display the state of the managed systems but not tools that change the state of the managed systems. For example, the Monitor Tools toolbox permits viewing installed software but does not permit installing software. The Full Rights toolbox contains all tools in the Central Management Server (CMS). The Limited Rights toolbox contains only the create and edit both reports and tools. When HP Storage Essentials is installed, a Toolbox for Storage Essentials tools is added to this page. See your HP Storage Essentials documentation for more information. The All Tools toolbox contains all tools in the Central Management Server (CMS). The Monitor Tools toolbox contains tools that display the state of the managed systems but not tools that change the state of the managed systems. For example, the Monitor Tools toolbox permits viewing installed software but does not permit installing software. The Full Rights toolbox contains all tools in the Central Management Server (CMS). The Limited Rights toolbox contains only the create and edit both reports and tools. When HP Storage Essentials is installed, a Toolbox for Storage Essentials tools is added to this page. See your HP Storage Essentials documentation for more information. Tools are applications, commands, or scripts that are launched from within HP SIM. You can add custom tools into HP SIM and execute them across multiple systems simultaneously. Three types of tools are supported in the HP SIM environment: web tools, X Window tools, and command line tools. web tools X Window tools Web tools must reside on a web server. The web server can be running on the CMS or a managed system. HP SIM launches the URL from a CLI or GUI. When a web tool is launched from the command line, HP SIM opens a browser to display the tool. When a web tool is launched from the HP SIM GUI, it opens in the workspace or in a separate browser window. X Window tools require that an X server is running. These tools can reside on the CMS or on a managed system. When accessing HP SIM from a network client, you must have X server software running on the network client to execute an X Window tool. From the CLI or GUI, HP SIM invokes the X Window application using Toolboxes 17

18 the command line and passes the location of the X server by requesting the device for display from the user. Command line tools Command line tools include applications, commands, and scripts. They can reside on the CMS or another managed system. They can be launched directly from the CLI or GUI. 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 target systems or run specific X-Window applications on the target systems. This tool can be scheduled. CMS tool A tool that runs on the CMS. It is usually a script or batch file and can pass in environment variables. Using Automatic Event Handling, this tool can optionally 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. Information storage HP SIM uses an audit log and a database to track activity and store your management domain information. HP SIM audit log Database HP SIM logs all tasks performed by all HP SIM users on all systems. The information is stored in the audit log 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 is only logged by default for the ps command. You can configure the option to log this output for the ps and other commands, as well as other aspects of the audit log, such as maximum file size. Information about configuring the audit log is available in Chapter 13 Configuration options. HP SIM uses a database to store vital management domain information. The database contains the following information: 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 at to get a recommended server configuration based on projected management workloads, installed management applications, and number of console users. 18 Product overview

19 Database software HP SIM supports the use of several databases: SQL Server 2005 Express Edition is supported on a Windows CMS. SQL Server 2005 Express Edition is installed with HP SIM. NOTE: To install SQL Server 2005 Express Edition,.NET 2.0 Framework is required. The.NET Framework requires Windows Installer 3.0 or later. Microsoft SQL Server 2005 is supported on a Windows CMS. HP SIM ships with SQL Server 2005 Express Edition, but you can choose to use Microsoft SQL Server 2005, which provides more advanced enterprise features. Oracle 10g and Oracle 9i Release 2 are supported on all platforms. Secure access NOTE: You must create the Oracle database using Unicode (AL32UTF8) as the character set before installing HP SIM. You must also specify the thin client.jar file location. HP SIM requires Oracle database and 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 database administrator (DBA) must set these services to be restarted when the server is reset. See the Oracle documentation for details on how to auto start these services at Access to this link requires registration, which is free. The Oracle DBA who manages the Oracle installation must perform this task. NOTE: You must install the Oracle JDBC driver, version You can download this driver from the Oracle website at HP SIM utilizes several technologies to provide secure access. You can access HP SIM through the command line 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. You have access to use the HP SIM commands based on your authorizations. If you access HP SIM from any system other than the CMS, be sure you use an SSH client. Programs like telnet, rlogin, and FTP do not provide 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 not spoof-protected. If you have a Windows CMS, then only administrators have command line access to HP SIM. 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 user name 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 SSL protocol. 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 browser should import this certificate to trust the CMS. Secure access 19

20 Network Client Central Management Server Web Browser HTTPS Tomcat Web Server HP-UX Managed System SSH Client SSH HP Systems Insight Manager SSH DMI SNMP WBEM SSH DMI SNMP WBEM Windows Managed System SSH SNMP WBEM HTTPS LINUX Managed System SSH SSH SNMP SNMP WMI WBEM ProLiant Support Pack ProLiant Support Pack Secure data transmission The security of the transaction depends on your networking environment and the management protocol that each 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 to these protocols, and they can provide a custom management protocol. SSH is the only protocol that must be installed on every managed system. Tools require specific protocols, and they can only be run on a managed 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 commands on that system. It also enables you to move files from one system to another, and it provides authentication and secure communications over insecure channels. SSH uses a public/private key pair to provide a secure mechanism to authenticate and encrypt communication. SSH keys are used to identify the execute-as user on the managed system. Typically, the execute-as user is either root or administrator, but other users can be configured, depending on the tool that will be executed on the managed system. The private key is kept secure 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 within the management domain using a single command. This functionality reduces the load on administrators in multisystem 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 the SSH server what tasks must be performed on the system. The SSH server then performs the tasks and returns the 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 of management and Internet standard technologies developed to unify the management of enterprise computing 20 Product overview

21 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 the user names and passwords for each managed system, which are required to provide user authentication for tools 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 the CLI or GUI. For more information, see the "Administering systems and events" section in the HP SIM User Guide at HP SIM uses HTTPS to access WBEM data, providing a secure path for system management data. For access to Windows management data instrumented in Windows Management Instrumentation (WMI), a WMI Mapper running on a Windows system converts the HTTPS WBEM requests into WMI requests, which use Distributed Component Object Model and NT security. A new SSL certificate is created during CMS initialization that is used as a client credential in Web-Based Enterprise Management (WBEM) requests (instead of the CMS certificate). NOTE: The WBEM client certificate authentication feature is only supported on HP-UX systems, that 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 ProLiant agent information. Digital certificates are used instead of user names and passwords to establish trust between the agent and the CMS. The certificate of the CMS should be loaded into each agent to be managed by that 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 client system problems. DMI-compliant computers can send status information to a CMS over a network. DMI is supported 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 SNMP requesters. 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. The community name must match those configured on the management system. The SNMP community names and passwords can be set from the CLI or GUI. For more information, see the "Administering systems and events" section in the HP SIM User Guide at HP SIM does not use SNMP SetRequests. By default, the supported operating system platforms have SNMP SetRequests disabled. For improved security, do not enable SNMP SetRequests on the CMS or the managed systems. Even SNMP GetRequest responses can be spoofed, so all information from SNMP should be regarded as insecure. Web server security HP SIM uses the Tomcat web server on the CMS. Tomcat features that are not required by HP SIM are turned off by default. These features include Server Side Includes and Common Gateway Interface scripts. Self-signed certificates The self-signed certificates used for WBEM and web server authentication make it possible for another system to impersonate the CMS if the valid certificate is not securely imported into the client or browser, which is known 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 importing it into your browser. You can also obtain the server certificate by browsing remotely and saving it in the browser the first time you access HP SIM, but this option is less secure and still susceptible to a possible "man-in-the-middle" attack. Information about importing CA-signed certificates is available in the "Administering systems and events" section of the HP SIM User Guide at Secure data transmission 21

22 X application security The data exchanged between an X client (or application) running on a managed system and an X server on the network client is transmitted in clear text over the network. HP does not recommend X clients in environments in which security is a concern. Managing servers behind a firewall HP 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 for this purpose because they are not secure protocols. The firewall must be configured to allow this traffic through the firewall. The following ports are used: WBEM uses HTTPS over port 5989 Web Agents use HTTPS over port 2381 DTF uses SSH-2 over port 22 For a complete list of ports used by HP SIM, see the Understanding HP SIM Security white paper. This white paper is available at 22 Product overview

23 2 Installation overview and requirements This chapter provides an overview of the HP SIM installation process, and it identifies the system requirements for a Windows CMS, a managed system, and a network client. First time install process overview Perform these steps for a first time install of HP SIM on your Central Management Server: 1. Install and configure the Central Management Server. The procedure to complete this step is in the installation chapter of this guide. 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 the Central Management Server. This step is covered in the first section of Chapter 6 Setting up and configuring managed systems. 4. Configure the remaining protocols for the managed systems. See Chapter 6 Setting up and configuring managed systems for details. Upgrade overview If HP SIM has previously been installed on your Central Management Server proceed to the upgrade instructions in Chapter 8 Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2 " or Chapter 9 Upgrading HP Systems Insight Manager from 4.x or later for details. System requirements This section identifies the hardware and software requirements and recommendations for HP Systems Insight Manager. These requirements are broken into sections for the CMS, managed system, and network client. Windows Central Management Server This section contains the minimum requirements for the Windows operating system that is used for the CMS. Operating system Hardware Software Networking Microsoft Windows Server 2008 Standard and Enterprise for x86 and x64 (32-bit mode) Any HP ProLiant x86 or x64 system with the following configuration: Database software: SQL Server 2005 Express Edition with Service Pack 2 TCP/IP Minimum: 1.5-GHz Note: SQL Server 2005 processor with 1 GB RAM SNMP Microsoft Windows Express Edition requires Server(TM) 2003 Standard 500 MB free disk space.net 2.0 Framework and Enterprise for x86 and recommended installed. x64 (32-bit mode) with Service Pack 2 Recommended: 2.4-GHz Note: SQL Server 2005 processor with 1.5 GB RAM Express Edition supports Microsoft Windows Vista Note: If Microsoft SQL 500 systems and 5,000 Microsoft Windows Server Server is installed on the events R2 Enterprise for x86 CMS, an additional 500 MB Microsoft SQL Server 2005 and x64 (32-bit mode) with of RAM should be installed. with Service Pack 2 (remote Service Pack 2 or local) Microsoft Windows 2003 SMB for x86 with Service Pack 2 Microsoft Windows XP Professional with Service Pack 2 VMware ESX v or later running guest on x86 The Central Management Server supports Microsoft Windows 2000 and 2003 International Server - French, German, Italian, Note: HP Netserver platforms can be used for the Central Management Server as long as the Instant Toptools software is not installed and all other requirements are met. Note: Microsoft SQL Server 2005 supports 5,000 systems and 50,000 events. Microsoft SQL Server 2000, Standard or Enterprise Edition with Service Pack 4 (remote or local) Oracle 9i Standard or Enterprise Oracle 10g Static or dynamic host name resolution First time install process overview 23

24 Operating system Hardware Software Networking Spanish, and Japanese (latest service pack available for each language). Browser software: Microsoft Internet Explorer 7.0 Microsoft Internet Explorer 6.0 with Service Pack 2 Firefox Firefox NOTE: HP SIM 5.2 can run on a Windows Virtual Machine (VM) provided the following requirements are met. The VM must be hosted on an ESX 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 available to this VM (by reserving CPU and Memory resources). Note: HP Integrity VMs do not support running an application at the same level as the host. Note: HP Service Essentials Remote Support Pack, including the Remote Support Software Manager, is NOT supported on Virtual Machines. 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) on which the HP SIM server software is to be installed. NTFS provides the ability to restrict file access based on user accounts and groups. Without NTFS, the CMS cannot be adequately secured against unauthorized access, and potentially sensitive operations and data could be made available to unauthorized users. Note: Service Essentials Remote Support Pack (Remote Support Pack) is not supported on Windows XP Professional. If you install HP SIM on Windows XP Professional, you cannot use Remote Support Pack. Note: Microsoft SQL Server 2005 is only supported if HP SIM is running on Windows Server Note: You cannot run Internet Explorer 6.0 and Internet Explorer 7.0 simultaneously. However, if you uninstall Internet Explorer 7.0, Internet Explorer 6.0 is restored. Managed system requirements and recommendations This section contains requirements and recommendations for managed systems. Operating systems Windows managed systems Microsoft Windows Server 2008 Standard or Enterprise for x86 and x64 (32-bit mode) Microsoft Windows Server 2008 Standard or Enterprise Core for x86 and x64 (32-bit mode) Microsoft Windows Server 2008 Datacenter, Datacenter Core, Web Edition, and for Itanium-based systems Microsoft Windows Server(TM) 2003 R2 Standard or Enterprise for x86 with Service Pack 2 and x64 Microsoft Windows Server 2003 R2 DataCenter with Service Pack 1 or later Microsoft Windows 2003 Standard with Service Pack 1 or later Microsoft Windows 2003 Standard for x64 with Service Pack 2 Microsoft Windows 2003 Standard and Enterprise for x86 and x64 with Service Pack 2 Microsoft Windows 2003 Web Edition for x86 with Service Pack 1 or later Microsoft Windows 2003 Small-Medium Business for x86 with Service Pack 1 or later Microsoft Windows 2003 SMB Business for x86 Microsoft Windows 2000 Datacenter for x86 Microsoft Windows 2000 Server with Service Pack 1 or later for x86 Microsoft Windows 2000 Server and Advanced Server with Service Pack 4 for x86 24 Installation overview and requirements

25 Microsoft Windows NT4 with Service Pack 6 Microsoft Windows Vista Client Microsoft Windows XP with Service Pack 1or later Microsoft Windows Virtual Server VMware ESX v or later running guest on x86 Integrity Virtual Machine for Windows running guest on Windows VMware GSX Note: Operating systems with only IPX enabled are not identified by an HP-UX or Linux CMS. HP-UX managed systems HP-UX 11i v3 (IA/PA) HP-UX 11i v2 Update 2 (IA/PA) HP-UX 11i v2 (IA only) HP-UX 11i Integrity Virtual Machine HP-UX running guest on HP-UX 11i v2 and v3 Linux managed systems Red Hat Linux 9 Red Hat Linux 8 Red Hat Linux 7.3 Workstation Red Hat Enterprise Linux 5 for x86 with Update 1, AMD64 and EM64T with Update 1, and Itanium-based systems Red Hat Enterprise Linux 4 x86 with Update 6, AMD64 and EM64T with Update 6, and Itanium-based systems Red Hat Enterprise Linux 3 x86 with Update 9, AMD64 and EM64T with Update 9, and Itanium-based systems SUSE Linux Enterprise Server 10 for x86, AMD64 and EM64T with Service Pack 1, and Itanium-based systems SUSE Linux Enterprise Server 9 for x86 with Service Pack 4, AMD64 and EM64T with Service Pack 4, and Itanium-based systems SUSE Linux Enterprise Server 8 for United Linux 1.0 and Itanium-based systems Integrity Virtual Machine Linux running guest on Linux VMware GSX VMware ESX 3.5 NOTE: Server. Operating systems with only IPX enabled are not identified by an HP-UX or Linux Central Management Novell managed systems Netware 6.5 Netware 6.0 SUN managed systems Solaris 9 Intel Platform Solaris 8 Intel Platform Managed system requirements and recommendations 25

26 IBM managed systems OS/2 HP managed systems Tru64 NSK OpenVMS Hardware For HP-UX: Any HP PA-RISC system Any HP Itanium -based system For Windows: Any HP x86 system Any HP x64 system For Linux: Any HP x86 system Any HP x64 system Any HP Itanium-based system Software This software is not required, but if you want improved management capabilities, HP recommends that you install 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 install these 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 2) or later Firefox Firefox Note: For optimum performance, the minimum resolution for the browser should be 1024 x 768. For HP-UX: Firefox Firefox For Linux: Firefox Firefox Installation overview and requirements

27 Note: For all Internet Explorer browsers, you must have the SSL 3.0 or TLS 1.0 browser security options enabled for HP SIM to work properly. Managed storage system To view the latest information regarding HP SIM support for a particular storage system, including Fibre Channel disk arrays, switches, tape libraries, or hosts (with Fibre Channel host bus adapters), see the HP SIM SMI-S Provider web page at This webpage also offers information on obtaining and installing SMI-S providers. SSH requirements SSH is locally configured during HP SIM local installation on the CMS. Custom tools on the Tools menu require SSH on the Central Management Server to run properly. These commands run on the Central Management Server with environment variables set to the context of specific events or devices. SSH on the Central Management Server is also used 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 with the 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 systems. If you choose not to configure it to work with remote SSH clients, then these commands fail. If SSH is not configured on the client, then command line tools, any HP SIM plugins that require SSH, and Configure or Repair Agents do not work properly. SSH requirements 27

28 3 Installing HP SIM on the Central Management Server (CMS) for the first time Preparing the system These steps are for a clean installation of HP SIM on your Windows system. If a previous version of HP SIM or Insight Manager 7 Service Pack 2.3 is installed on your system and you want to upgrade your data, see Chapter 8 Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2 or Chapter 9 Upgrading HP Systems Insight Manager from 4.x or later for more information. This procedure verifies that your system meets the minimum requirements and prepares your system for installation. 1. Install and configure the CMS. The procedure to complete this step is in 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 are to be managed by the CMS. This step is covered in the first section of Chapter 6 Setting up and configuring managed systems. 4. Configure the remaining protocols for the managed systems. See Chapter 6 Setting up and configuring managed systems for details. NOTE: If installing HP SIM with a local SQL database on a Windows XP SP2 machine that is not a member of a domain, Simple File Sharing is automatically disabled. The Simple File Sharing setting on 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 database install. By default, Classic local, user authenticate as themselves. To enable Guest only, local user authenticate as guest, select this option from the dropdown list and click Apply. 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 Service Packs. Note: If you are using an external SQL database, leave the default as "Master" to insure that all necessary databases are created with correct permissions. 3. Verify your system has at least one partition formatted for the NTFS file system, on which the HP SIM server 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 already have HP Instant Support Enterprise Edition (ISEE) Windows Client software A or older, installed on your CMS, then you must decide whether you would prefer to keep the functionality of ISEE or install Service Essentials Remote Support Pack. The two cannot run on the same CMS. Service Essentials Remote Support Pack does provide Remote Monitoring for the same platforms as ISEE. However, only ISEE supports proactive collection data. If you do wish to configure 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 following: a. Select Start>Settings>Control Panel>Add/Remove Programs. b. Select HP Instant Support Enterprise Edition Client from the list of installed programs, then click 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 the Preparing the system 28

29 msado15.dll file. Select Properties, and click the Version tab to display the version number. If the file is not found in this path, use the Windows search engine to find the file. If you must download MDAC, see and search for MDAC Service Pack. 6. Before you proceed with the install, if you are going to perform a custom install for System Management Homepage see System Management Homepage Installation Guide at products/servers/management/agents/documentation.html for specific user name requirements for the product administrator, service account, and database administrator: 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 and to use non-default values for each component. See Custom install for more information. Silent install - Requires no user interaction. Administrators can install HP SIM to target systems using command line options. See Silent install for more information. 7. Download the software, or install it from the HP Management CD or the HP Insight Control Management DVD. To download the software, see and on the upper-left of the page under HP 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 product install. To install the software from the HP Management CD, place the CD in the CD-ROM drive. The CD has an autorun feature that launches a license agreement. Agree to the license agreement, and click the Products tab. Click Install under HP SIM to launch the Installer. Or click the Products tab, click Explore CD, and then run setup.exe located at \HPSIM\win_ia32\ to launch the Installer. To install the software from the HP 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 examines this system for supported versions of SQL Server and Oracle. Note: HP does not recommend running RDP with MSDE installed and HP SIM with SQL Server 2005 Express Edition on the same server. Note: Click the drop-down selection box in the upper-right corner of any dialog box to view the HP SIM Installation and Configuration Guide, ReadMe or Release Notes. Preparing the system 29

30 8. Click Next. The System Inspection window appears. The system is inspected for a previous version of HP SIM and a local database. After the system inspection is complete, the Database Configuration window appears. 30 Installing HP SIM on the Central Management Server (CMS) for the first time

31 Select from the following database options: Install and use SQL Express. This option enables you to install and configure HP SIM to use SQL Server 2005 Express Edition. To install and use SQL Server 2005 Express Edition: 1. From the Database Configuration window, select Install and Use SQL Express. 2. In the Username field, the installing user account appears and can be edited. The account specified must be the user name for the database server. 3. In the Password field, enter the password for the database server. 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 initialization fails. 4. In the Domain field, enter the domain name for the database server. 5. Click Next. A dialog box appears indicating files are being extracted. After the files are extracted, a new dialog box appears indicating SQL Server 2005 Express Edition is being installed. After SQL Server 2005 Express Edition is installed, the Select Installation Type window appears. Use SQL/SQL Express. This option is applicable if you have SQL Server or SQL Server 2005 Express Edition installed and you want to configure HP SIM to use it. To use SQL or SQL Server 2005 Express Edition: 1. From the Database Configuration window, select Use SQL/SQL Express. 2. In the Username field, the installing user account appears and can be edited. The account specified must be the user name for the database server. Preparing the system 31

32 3. In the Password field, enter the password for the database server. 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 initialization fails. 4. In the Domain field, enter the domain name for the database server. 5. Click Next. The Select Installation Type window appears. Use Oracle. This option is applicable if you have Oracle installed and you want to configure HP SIM to use it. To use Oracle: 1. From the Database Configuration window, select Use Oracle. 2. The Oracle database with Unicode (AL32UTF8) as the character set must be created before installing HP SIM. An Oracle user with DatabaseAdministrator (DBA) privileges must be created in this database for the exclusive use by HP Systems Insight Manager. HP SIM must be installed in an empty Oracle database schema. The thin client.jar file must be copied on to the system, and its location must be specified during installation. 3. In the Username field, enter the Oracle user name that has been assigned the DBA role. Note: An Oracle user name cannot contain a backslash (\) or a forward slash (/). 4. In the Password field, enter the password for the user name specified. 5. In the Host field, enter the name of the remote or local server where Oracle is installed. An IP address may also be used. 6. Under Instance name in the Database field, enter the name of the database created on Oracle for the use of HP SIM. 7. In the Port field, the default 1521 appears but can be edited. 8. In the JarFile field, enter the full path to the.jar file or click Browse and navigate to the correct location. This path must be accessible through the file system on the CMS. The installation copies the file to the correct location. 9. In the Host field, the local host name appears and can only be edited if you are performing a fresh install. 10. Click Next. The Select Installation Type window appears. Note: If an HP ProLiant Essentials Vulnerability and Patch Management Pack (VPM) MSDE database exists (within the HP SIM database instance or located on a database instance created by VPM), it is upgraded to SQL Server 2005 Express Edition. If the VPM database upgrade fails, a message displays indicating Failed to Upgrade VPM Database to SQL Express, but the HP SIM installation continues. 9. The Select Installation Type window enables you to select your preferred installation type. 32 Installing HP SIM on the Central Management Server (CMS) for the first time

33 The following installation options are available: Typical. Select this option to install the included components with minimal user interaction listed under the Available Components for Install. The following components are available in the Typical install: Available components for install System Management Homepage OpenSSH Services 4.3p2 WMI Mapper HP Systems Insight Manager Remote Support Software Manager HP Version Control Repository Manager Typical installation Included Included Included Included Included Included Custom installation Included Optional Optional Included Optional Optional Typical install Note: If a component is not listed as being available for installation on the CMS, then the HP SIM install shell 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 SIM install shell and it supports an in-place upgrade, it appears in the component list. Custom. Select this option to select the individual components under the Available Components for Install and configure them during installation. NOTE: The Remote Support Software Manager (RSSWM) is a prerequisite for the Service Essentials Remote Support Pack(RSP). RSSWM installs automatically with a Typical Installation. If you do not want RSP or Typical install 33

34 RSSWM on your CMS you can opt OUT of the SWM installation by running the Custom Installation insteadn and unmarking the check box. 1. 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. NOTE: The Remote Support Software Manager (RSSWM) is a prerequisite for the Service Essentials Remote Support Pack(RSP) and is part of the Typical Installation. If you do not want RSP or RSSWM on your CMS you can opt OUT of the SWM installation by running the Custom Installation instead and unmarking the RSSWM check box. 2. Enter the password for this account. Click Next, the Summary window appears with the components that are to be installed. 34 Installing HP SIM on the Central Management Server (CMS) for the first time

35 3. Click Install to initiate the installation process which installs all products listed in the Selected Components table. The Status window appears. As each component is being installed, it states In Progress beside the component's name. After the component has installed, it states Installed Successfully. 4. After all the components are installed, click Next. The Registration window appears. Register HP SIM or click Register Later. NOTE: The HP Systems Insight Manager Registration window and First Time Wizard appear when a user with administrative rights logs in to HP SIM for the first time. Follow the onscreen instructions to register HP SIM or click the Register Later to register at another time. If your HP SIM system is not connected to the internet, you can go to a system that has internet access and navigate to h20293.www2.hp.com/portal/swdepot/displayproductinfo.do?productnumber=hpsim-lic to register and retrieve a code to confirm to the HP SIM application that it is registered and to discontinue the registration prompt. The First Time Wizard configures only the basic settings of an initial setup for HP Typical install 35

36 SIM. Refer to the HP Systems Insight Manager 5.2 User Guide at products/servers/management/hpsim/infolibrary.html for more information. 5. After registering or clicking Register Later, the Installation complete window appears. For a fresh install, the following message appears For this new install, an operating system account must be created and configured in the System Management Homepage on this computer and each HP Version Control Agent must be configured to use the new account. For more information, refer to the Version Control Installation Guide at 36 Installing HP SIM on the Central Management Server (CMS) for the first time

37 6. The reboot option is presented on this screen. The Yes, reboot the system now option is selected by default. Click Finish to allow the system to reboot. This completes the typical installation process See "Next steps" for more information. Custom install Note: For more information regarding where the System Management Homepage default settings are stored during a Typical installation and how to change them, see the System Management Homepage Installation Guide at documentation.html. NOTE: The Remote Support Software Manager (RSSWM) is a prerequisite for the Service Essentials Remote Support Pack(RSP). If you do install SWM you will be prompted to provide a location path for the download; the default path is c:\programfiles\hp. Additionally, after a custom installation of HP SIM and SWM, the configuration of SWM launches automatically. If you do not want RSP or SWM on your CMS you can opt OUT of the SWM installation by unmarking the check box. 1. 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, the component is deemed a mandatory component and cannot be cleared. The amount of required disk space is also listed for each component. Select the components you wish to install. Custom install 37

38 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 the installing account credentials and can only be edited if doing a fresh install. Enter the password for this account. Note: This user account is used to run the HP Systems Insight Manager service. 3. Click Next. The Summary window appears. 38 Installing HP SIM on the Central Management Server (CMS) for the first time

39 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 next to the component's name. After the component installs, it states Installed Successfully. 5. Install the System Management Homepage: a. The System Management Homepage Setup window appears. The InstallShield Wizard guides you 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, the installation 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. The group 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 following access types: Select Anonymous Access to enable anonymous access to unsecured pages. Select Local Access Anonymous or Local Access Administrator to set up the System Management Homepage to automatically grant local IP addresses at the selected access level. Caution: Selecting Local Access with Administrator privileges provides any users with access to the local console full access without prompting them for a user name or password. e. Click Next. The Trust Mode window appears. Custom install 39

40 f. Select the level of security you want to provide from one of the three trust modes: Trust By Certificate i. Select Trust By Certificate, and click Next. The Trusted Certificates window appears. The Trusted Certificates window allows trusted certificate files to be added to the Trusted Certificate List. 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 in the file name field, an error message appears, indicating the file does not exist. Click OK to select another file, or click Open to add the file to the Trusted Certificate List. The Trusted Certificate List appears. Click Next. or Note: If you click Next without adding any certificates to the list, and no certificates exist from a previous installation, a message appears, indicating that if you do not specify any trusted certificates, HP SIM cannot access the HP Insight Management Agent on this system. Click OK if you do not want HP SIM to access the Insight Management Agent on this system, or click Cancel to close the window and add the trusted certificates to the 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. This mode is the strongest method of security because it requires certificate data and verifies the digital signature before enabling access. 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. The Trusted 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 certificate is removed. v. From the IP Binding window, select the IP Binding checkbox if you would like to bind to 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 address ranges. Click Next, and the Summary Panel appears. Trust By Name i. Select Trust By Name. Click Next. The Trusted Server window appears. Enter the names of the servers you want to trust. Note: Although the Trust By Name mode is a slightly stronger method of security than the Trust All mode, it still leaves your system vulnerable to security attacks. The Trust By Name mode sets up the System Management Homepage to only accept certain requests 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 secure network, 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 the wrong system. This option does not verify anything other than the HP SIM server name submitted. Note: The server name cannot contain the following characters: 40 Installing HP SIM on the Central Management Server (CMS) for the first time

41 ~! # $ % ^ & * ( ) + = " : ' < >?, ; ii. iii. iv. 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 message appears, indicating that if you do not specify any trusted server names, HP SIM cannot access the Insight Management Agent on this system. Click OK to proceed without trusting any systems, or click Cancel to close the window and add server names to the list. Note: To delete a certificate, select the certificate and click Delete. The selected certificate is removed. From the IP Binding window, select the IP Binding checkbox if you would like to bind to IP addresses that match a specific subnet and mask. Click Next. 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 i. Select Trust All. Click Next. The IP Binding window appears. 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 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 everyone in 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 might not be able to connect to the System Management Homepage. The IP Restricted Logins window appears. The IP Restricted Logins window enables you to select specific IP addresses or IP address ranges to include or exclude from gaining login access. Although optional, the System Management Homepage can restrict login access based on the IP addresses of the machine attempting to gain access. iii. iv. 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 ranges to grant login access permission. If there are IP addresses in the Inclusion list, then only those IP addresses are enabled for login privileges. If there are no IP addresses in the Inclusion list, then login privileges are permitted to all IP addresses that are not in the Exclusion 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. In the Include field, enter a beginning IP address to which you want to grant login access. 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 are granted login access. Click Add. The IP address or IP address range is added to the Exclusion 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 appears indicating the IP address is invalid. Click OK. Enter a valid IP address or IP address range, 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 login access. Custom install 41

42 v. In theto field, enter an ending IP address to which you want to deny login access. All IP addresses that fall between the beginning and ending IP addresses are 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 address range, 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 will be marked as disabled. Do you want to proceed without adding any IP Address restrictions? If you click OK, the IP Restricted Login option on the IP Restricted Login window is cleared. The Summary Panel appears. The Summary Panel lists the location where the System Management Homepage is installed, the amount of space the installation requires, and the summary of 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 System Management 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 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 these fields 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 Windows XP or Windows 2003 system. If you are installing on a Windows 2000 system, the OpenSSH Service runs as "local system" 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 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. Click Next. 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 change the destination location using Browse. Click OK. Click Next. The Ready to Install window appears. 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 allow remote access and activation by everyone and anonymous users. See the HP SIM Readme at /h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for more details. 42 Installing HP SIM on the Central Management Server (CMS) for the first time

43 8. If you have an Oracle database, install the Oracle JDBC driver, version or newer. See the Oracle documentation, or visit the Oracle website at for 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/lib directories and remove it from any locations where it is found. c. Download the new driver from the Oracle website at d. Copy the JDBC driver file (ojdbc14.jar) to the [installdir]/lib and [installdir]/jboss/server/hpsim/lib directories. 9. Install HP Systems Insight Manager: a. When the Welcome to the HP Systems Insight Manager Setup Wizard appears, click Next. b. Select or enter a different folder name using Browse. Click Next. The Ready to Install window appears. Custom install 43

44 c. Click Install. The Install Progress window appears. d. Click Finish when the installation is complete to close the HP Systems Insight Manager Installer window. 44 Installing HP SIM on the Central Management Server (CMS) for the first time

45 e. After the HP SIM installation is complete, the Remote Support Software Manager; window appears. The configuration of the ISEE_CMS_SWMAGENT completes automatically. This process provides the files needed so that you can access the Service Essentials Remote Support Pack application 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 for configuration instructions. 10. Install the Remote Support Software Manager (RSSW) a. Choose a path for the RSSWM when prompted. Use the Browse button to select a new path or click the Next button to use the default path. b. The RSSWM installation will begin. When it completes the initialization will begin automatically. See Chapter 7 Initializing the Remote Support Software Manager on the Central Management Server (CMS) for more information. 11. Install the HP Version Control Repository Manager: a. When the HP Version Control Repository Manager Setup window appears, click Install. The HP Version Control Repository Manager Setup Repository Directory window appears. b. Select the directory from which HP Version Control Repository Manager will retrieve support pack information 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 Update window appears. c. Select the Enable Automatic Update checkbox to enable automatic downloading of HP ProLiant Support Packs and components at a specified interval and time. Custom install 45

46 Silent install 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 Repository Manager, warning appears: "At least one HP Version Control Agent must be configured to use the HP Version Control Repository Manager." If none are configured, verify the HP Version Control Agent settings to ensure proper operation of the automatic update feature. Click OK. e. Click Close. 12. The Status window appears again, after all components have been installed, they will have an installed status. Click Next. 13. The Registration window appears. Register HP SIM or click Register Later. Note: If you do not have Internet access, click Register Later or navigate to h20293.www2.hp.com/portal/swdepot/displayproductinfo.do?productnumber=hpsim-lic to register After registering or clicking Register Later, 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 truncated name 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 truncated host name\administrator. To log in, use the original host name in the Domain field on the Sign in page. 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 occurs 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> 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 installing HP SIM from the Web, then after extracting the installation program, edit the silent.xml file and launch the setup in Silent mode. All errors, warnings or information messages are logged in the HP SIM.log. The installation status of HP SIM and installed components appear in the silentstatus.xml file. These files are created in the root of the system drive. The silent.xml file contains the parameters below for the installation process. Database information: Set <installsqlexpr> TRUE FALSE The following tag is used to install or not install SQL Server 2005 Express Edition during the silent installation: TRUE - used to install SQL Server 2005 Express Edition FALSE - used to not install SQL Server 2005 Express Edition For example: <installsqlexpr>false</installsqlexpr> <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 running SQL server or SQL Server 2005 Express Edition. Provide the host name or IP address of the database server. <dbinstance> 46 Installing HP SIM on the Central Management Server (CMS) for the first time

47 Provide a valid existing instance name already running on the database server or specify a new instance name if you want to install SQL Server 2005 Express Edition on the local server. <dbname> use the default 'master'. <dbport> Use default 1433 or provide a valid port. HP SIM service Information: TRUE FALSE The following flag is used to configure an Oracle database during the silent installation: dboracle TRUE - to use an Oracle database FALSE - not to use an Oracle database NOTE: When dboracle is set to TRUE, installsqlexpr should be set to false. When installsqlexpr is set to TRUE, dboracle should be set to false. The dbdomain and dbinstance parameters should not be set (left blank). dboraclejarfile - must be specified when using an Oracle database. This is used to provide the location of the JDBC driver to be used to connect to the Oracle database. For example, <dboraclejarfile>c:\ojdbc14.jar</dboraclejarfile> <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 the main directory that HP SIM and the partner components are installed to. OpenSSH, HP ProLiant Essentials Virtual Machine Management Pack is installed in the <baseinstalllcation> specified in silent.xml. HP SIM will be installed in <hpsiminstalllocation> specified in silent.xml. If the silent install finds a previous HP SIM installation on the target system, that location will 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 partner components. 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 containing special characters, such as: &, <, >, ', " must be escaped appropriately as below in the silent.xml file: Silent install 47

48 & & < < > > &apos; ' " " Next steps 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. HP SIM is now installed and initialized on the CMS. To browse to HP SIM, use the icon that appears on your desktop after installation is complete, or start the HP SIM GUI using Internet Explorer or Firefox at You will need to configure HP SIM using the First Time Wizard. See Chapter 4 Configuring HP SIM using the First Time Wizard for details. See Chapter 11 Using the graphical user interface for details. See Chapter 6 Setting up and configuring managed systems for details about installing and configuring the required Management Agents on the systems that will be managed by the CMS. Next, complete the initial setup of HP SIM. Initial setup involves adding managed systems, adding users, setting up authorizations, and configuring event handling. See Chapter 7 Initializing the Remote Support Software Manager on the Central Management Server (CMS) for details about installing and configuring the Remote Support Software Manager. See the Service Essentials Remote Support Pack documentation for details about configuring Remote Support Pack. NOTE: If HP SIM has not been registered, the HP Systems Insight Manager Registration window and First Time Wizard appear when a user with administrative rights logs in to HP SIM for the first time. Follow the onscreen instructions to register HP SIM or click Register Later to register at another time. NOTE: The First Time Wizard configures only the basic settings of an initial setup for HP SIM. Additional configuration options are available in the HP SIM graphical user interface. See Chapter 5 Configuring HP SIM using the Options menu or the HP SIM User Guide at for more information. 48 Installing HP SIM on the Central Management Server (CMS) for the first time

49 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 using First 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 SIM on 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 and configuring managed systems for details. 4. Configure the remaining protocols for the managed systems. See Chapter 6 Setting up and configuring managed systems for details. The initial setup of HP SIM uses the First Time Wizard to provide step-by-step instructions for performing the initial 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 perform the initial setup, you must complete the installation of your Central Management Server (CMS) as described in an earlier chapter. NOTE: All the information in this section is also available in the HP Systems Insight Manager 5.2 User Guide at Using the First Time Wizard The First Time Wizard is automatically launched the first time a user with administrative privileges signs in to HP Systems Insight Manager (HP SIM). The administrative account used to install HP SIM is the initial administrative account. If the wizard is canceled before completion, it restarts each time an administrative user 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 selecting Options 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 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. The First Time Wizard does not apply any changes until you click Finish on the Summary page. NOTE: The default settings in Firefox block the First Time Wizard. You must disable the pop-up blocker in Firefox to see the First Time Wizard. NOTE: The selections you make in the First Time Wizard are not applied until you click Finish on the summary page. The First Time Wizard includes the following options: Introduction. Describes the purpose of the First Time Wizard. You can cancel the First Time Wizard and disable the wizard from automatically starting when an administrative user signs in. Managed Environment Specifies all operating systems to be managed by the Central Management Server (CMS). The selections made here configure HP Systems Insight Manager (HP SIM) to show collections, tools, and reports only for managed environments that are selected. WBEM. Enter the default Web-Based Enterprise Management (WBEM) user names and passwords. This information is used to discover systems that use the WBEM management protocol. Enter the mapper proxy system host name and port number to communicate with Windows systems using Windows Management Instrumentation (WMI). Using the First Time Wizard 49

50 SNMP Enter the read community strings to use for all newly discovered systems. Community strings establish the authentication that enables communication between HP SIM and a managed system. This information is required to discover systems that use the SNMP management protocol. See the HP Systems Insight Manager 5.2 User Guide at servers/management/hpsim/infolibrary.html for more information about WBEM and SNMP. Discovery Use the wizard to enable discovery, set up the discovery schedule, and enter the IP address ranges or host names of the systems you want to discover. Discovery is the process HP SIM uses to find and identify systems on your network and populate the database with that information. A system must be discovered to collect data and track system health status. Configure Managed Systems Configure managed systems as they are discovered, by configuring WBEM and Windows Management Instrumentation (WMI), SNMP, Secure Shell (SSH) access, and trust relationship. Enter the settings that the CMS will use to send notifications. You can set up Automatic Event Handling tasks that prompt HP SIM to send s when the CMS receives a specific event. Summary Displays all First Time Wizard settings with the option to modify settings or to finish the First Time Wizard. NOTE: The First Time Wizard configures only the basic settings of HP SIM. Configuring the managed environment From this page, select the operating systems that the Central Management Server (CMS) will manage. There are four options: Windows, Linux, HP-UX, and Other. The selections made here configure HP Systems Insight Manager (HP SIM) to hide collections, tools, and reports for operating systems you do not use. By default the CMS operating system is selected on this page. NOTE: These settings can be changed at any time, and the hidden collections, tools, and reports can be made visible again. To change these settings from the HP SIM menu, select Options Managed Environment. 1. Select the operating systems for the CMS to manage. 2. Click Next to go to the next First Time Wizard step, or click Previous to return to the previous step. Entering WBEM settings HP Systems Insight Manager (HP SIM) uses the Web-Based Enterprise Management (WBEM) protocol to communicate with managed systems. You can enterwbem settings in the First Time Wizard or from the HP SIM menu bar. To disable WBEM communication or enter settings in the GUI, select Options Protocol Settings Global Protocol Settings from the HP SIM menu. 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 not discover them. NOTE: See the HP Systems Insight Manager 5.2 User Guide at servers/management/hpsim/infolibrary.html for more information about fine tuning protocol settings for a single system or a group of similar systems. To enter WBEM settings using from the First Time Wizard WBEM page: 1. In the User name, Password, and Confirm password fields, enter a default user name and password as needed. To add additional default user name and password pairs, click Add. To delete user name and password pairs, click Delete. These defaults apply to all newly discovered systems. HP recommends limiting WBEM user name and password pairs to 10 to reduce the overall discovery run time. To add more than 10 WBEM user name and password pairs, run the mxnodesecurity -a -p wbem -c username:password command for each additional set. You can also create an XML file that defines your system authorizations before running discovery. 50 Configuring HP SIM using the First Time Wizard

51 If your network includes storage systems, enter the user name and password of each SMI CIMOM in this section. For example, if you have an HP host bus adapter (HBA) (Emulex OEM) for Windows, enter the user name cimadmin and password pwd580. See your storage system's SMI-S provider documentation for information about the SMI CIMOM user name and password. The system identification process attempts each user name and password pair until a successful response is obtained. Future WBEM requests to a system will use the user name and password that succeeded the system identification process. For Windows-based systems, the user name must include the domain name, for example, domainname\username. Enter the user name and password pairs such that root and administrator passwords are listed first and user and guest passwords are listed second. This order minimizes the search time. 2. In the WMI Mapper Proxy section, enter the mapper proxy Hostname and Port Number. If a WMI Mapper Proxy has already been discovered, it appears here. If you have selected not to manage Windows systems on the previous page, this section is not displayed. 3. To go to the next First Time Wizard step, click Next, or to return to the previous step, click Previous to return to the previous step. The users that are used for WBEM access do not need to be configured to sign-in. Entering SNMP settings HP Systems Insight Manager (HP SIM) uses SNMP to communicate with managed systems. Community strings establish the authentication that enables communication between HP SIM and a managed system. You can enter read community strings in the First Time Wizard, or from the HP SIM menu bar. To disable SNMP communication, enter community strings, or control other SNMP settings not available in the wizard, select Options Protocol Settings Global Protocol Settings from the HP SIM menu. If you do not have SNMP systems in your network, it is not necessary to enter information here. If you have SNMP systems and you do not enter read community strings that match these systems, HP SIM does not discover them. See the HP Systems Insight Manager 5.2 User Guide at management/hpsim/infolibrary.html for information about fine-tuning protocol settings for a single system or a group of similar systems. To enter SNMP settings from the First Time Wizard SNMP page: 1. In the Read community string field, enter up to 10 read community strings. This value is case-sensitive. The identification process attempts communication with a system, using each of these communities in succession until a successful response is obtained. Future SNMP requests then use the community string that provided a successful response. If you have SNMP systems and no read community string that match the systems are entered, the systems will not be discovered. 2. To go to the next First Time Wizard step, click Next, or to return to the previous step, click Previous. Enabling automatic system discovery HP 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 enable and configure the System Automatic Discovery task in the First Time Wizard, or by selecting Options Discovery from the HP SIM menu. If the System Automatic Discovery task is enabled, it runs immediately when the First Time Wizard is finished to initially populate the HP SIM database. You can create additional automatic discovery tasks by selecting Options Discovery from the HP SIM menu and entering the details, and you can also run manual discovery to discover single systems. To enable automatic system discovery from the First Time Wizard Discovery page: 1. To configure HP SIM to run discovery immediately after you finish the First Time Wizard, select Run discovery once after wizard finishes. 2. To configure the System Automatic Discovery task to run on a regular schedule, select Schedule and enter the periodic run interval and time of day to run the task. Entering SNMP settings 51

52 3. In the Ping inclusion ranges, system (hosts) names, templates, and/or hosts files field, specify the IP addresses to include for pinging. If you want to use this task to discover SMI-S storage systems, include the IP address of each SMI CIMOM. You can also enter Simple or Fully Qualified Domain Names (FQDN) host names. However, you cannot enter a range of host names. To use an existing hosts file, enter the hosts file name in the following format: $HostsFileName. 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.2 User Guide at hpsim/infolibrary.html for more information. 4. To go to the next First Time Wizard step, click Next, or to return to the previous step, click Previous. Configuring managed systems The Configure Managed Systems page in the First Time Wizard enables you to configure managed systems as they are discovered and to specify parameters for running the Configure or Repair Agents. All steps are optional and can be configured from the HP SIM Options menu at a later time. To skip this step, click Next to go to the next First Time Wizard step. To configure managed systems from the First Time Wizard Configure Managed Systems page: 1. To use the First Time Wizard to configure managed systems when they are first discovered, select Configure newly managed systems when Discovery runs for the first time. 2. Enter the user name and password pair for an administrative user account on the managed systems. 3. Under Configure WBEM/WMI, select from the following: Create subscriptions for WBEM events Send a test WBEM or WMI indication to this instance of HP Systems Insight Manager to ensure that events appear in HP Systems Insight Manager events lists Deploy HP Systems Insight Manager WBEM certificate to the target systems to support client certificate authentication This option does not appear if there are no managed HP-UX systems. 4. Under Configure SNMP, select from the following: Set read community strings This string is pre-populated with settings from the SNMP page of the First Time Wizard. Set traps to refer to this instance of HP Systems Insight Manager Send a test SNMP trap to this instance of HP Systems Insight Manager to make sure events appear in the HP Systems Insight Manager events lists 5. Under Configure secure shell (SSH) access, select from the following: Host based authentication Each user has to be authenticated on the managed system 6. Select Trust relationship to set a trust relationship between managed systems and the Central Management Server (CMS). 7. To go to the next First Time Wizard step, click Next, or to return to the previous step, click Previous. Configuring settings To use the First Time Wizard to configure HP SIM to send notifications through automatic event handling: 1. Enter the SMTP host name. The SMTP host is the outgoing server that the CMS uses to send notifications. 2. In the Sender's address box, enter the address that the management server uses when sending notifications. 52 Configuring HP SIM using the First Time Wizard

53 3. (Optional) Select Send test and enter recipients address. Click Send test now. 4. To authenticate your SMTP server, select Server Requires Authentication. 5. Enter the account user name and password in the corresponding boxes. Note If you did not enter a valid Simple Mail Transfer Protocol (SMTP) host, HP SIM notifies you that it cannot send notifications. If you do not want to enter settings now, click OK, or to enter a valid SMTP host, click Cancel. NOTE: If the Server Requires Authentication option is selected, and you enter incorrect account information, event notifications do not reach the intended recipients. 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 then click Finish to save them. If you enabled automatic discovery or initiated Run discovery after the wizard finishes, discovery runs when you exit the First Time Wizard. If you did not enable automatic discovery or the Run discovery once after wizard finishes, discovery does not take place until you select Options Discovery from the HP SIM menu, and enable a discovery task or select a task and click Run Now. Finishing the First Time Wizard When you click Finish in the First Time Wizard, the Finish page appears with a message stating Your changes are being applied, please do not close the window. If you selected Run discovery once after wizard finishes on the Discovery page, you are notified that discovery is running and where to go in the HP Systems Insight Manager (HP SIM) to monitor the progress of discovery. Also included on this page is information on where to go to see discovered systems that you are managing and where to go to better manage these systems. To close the First Time Wizard, click Close. Operating-system-specific collections, reports, and tools Operating-system-specific collections The following collections are removed if the associated operating system is not selected on the Managed Environment page of the First Time Wizard or from the Managed Environment page in the HP Systems Insight Manager (HP SIM) UI (Options Managed Environment). These collections are located in the System and Event Collections panel under Systems by Operating System and Cluster by Type, with the exception of All VSE Resources which is located under Systems by Type. The following table lists collections by operating system. Windows Linux HP-UX Other Microsoft Windows Server 2003 Red Hat Linux HP-UX SCO Unix Microsoft Windows 2000 SuSE Linux HP Serviceguard (under Clusters by Type) HP True64 UNIX Microsoft Windows NT Linux All HP Integrity Virtual Machines* HP OpenVMS Microsoft Windows XP All HP Serviceguard Clusters* All Virtual Partition Servers* HP NonStop Server Microsoft Windows 95, 98, Me All Resource Partitions* HP TruClusters MSCS Clusters All Shared Resource Domains* OpenVMS Clusters Microsoft Vista All HP Serviceguard Clusters* Novell Netware Microsoft Windows Server 2008 All Virtual Partitions* HP Serviceguard (under Clusters by Type) First Time Wizard summary 53

54 Windows Linux HP-UX Other All HP Integrity Virtual Machines* * - Located under All VSE Resources. Operating-system-specific reports The following reports are specific to HP-UX and are added or removed depending on whether HP-UX is selected or not. There are no reports that are specific to Windows or Linux. Cellular Systems - Servers HP-UX File System - HP-UX HP-UX Kernal Parameters - HP-UX HP-UX Logical Volume - HP-UX HP-UX Network Details - HP-UX HP-UX Physical Volume - HP-UX HP-UX Software Bundle - HP-UX HP-UX Software Product - HP-UX HP-UX Volume Group - HP-UX I-O Devices - HP-UX Logical Memory Details - HP-UX Operating System Details - HP-UX The following reports have no data for HP-UX and are removed if HP-UX is the only selection. Batteries System License Info Logical Disk Drives Installed Controllers Physical Disk Drives Operating-system-specific tools Windows Linux The following section lists HP SIM tools (by menu path) that by operating system. Tools Command Line Tools Windows and all tools listed here (copy, del, dir, net, netstat, rmdir, and type). Deploy Drivers, Firmware, Software. Configure Disk Threshold. Configure Replicate Agent Settings. Tools Integrated Consoles Webmin. Deploy Drivers, Firmware, Software. Configure Disk Threshold. Configure Replicate Agent Settings. 54 Configuring HP SIM using the First Time Wizard

55 Deploy RPM Package Manager and all tools listed (Install Package, Query Package, Uninstall Package, Verify Package). Tools Command Line Tools Unix/Linux and all tools listed here (bdf, cat, cp, df, find, ls, my, ps, rm). HP-UX Configure HP-UX Configuration and all tools listed here (Kernal Configuration, Disks and File Systems, Accounts for Users and Groups, Auditing, System Security Policies, Authenticated Commands, Cards, Printers and Plotters, System Properties, Cards and Devices - pdweb, Kernal Configuration - kcweb). Deploy Software Distributor and all tools listed here (View Installed Software, View Depot Software, CLI List Software, CLI Preview Install, CLI Verify Software). Diagnose Event Monitoring Service. Optimize Process Resource Manager and all tools listed here (Display Resource Usage and List Resource Manager Console). Tasks & Logs View SAM Log. Tasks & Logs View Software Distributor Agent Log. Tasks & Logs View Software Distributor Daemon Log. Tools Command Line Tools Unix/Linux and all tools listed here (bdf, cat, cp, df, find, ls, my, ps, rm). Configure Management Processor HP Integrity or HP 9000 ilo and all tools listed here (New User, Modify User, Delete User, LAN Access, LDAP Settings, Firmware Upgrade, ilo Control, and Deploy SSH Public Key). Tools Integrated Consoles Webmin. Other Tools Command Line Tools Unix/Linux and all tools listed here (bdf, cat, cp, df, find, ls, my, ps, rm). Operating-system-specific collections, reports, and tools 55

56 5 Configuring HP SIM using the Options menu Perform step 2 to configure HP SIM for your environment or you can use First Time Wizard in Chapter 4 Configuring HP SIM using the First Time Wizard. 1. Install and configure the CMS. The procedure to complete this step is in Chapter 3 Installing HP SIM on the Central Management Server (CMS) for the first time. 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 perform the initial configuration of HP SIM. 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 and configuring managed systems for details. 4. Configure the remaining protocols for the managed systems. See Chapter 6 Setting up and configuring managed systems for details. This chapter provides you with more configuration options then if you use First Time Wizard. The following things need to be done to configure the protocols for the managed systems. 1. Configure protocol settings 2. Add users 3. Add toolboxes 4. Add authorizations 5. Configure 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 of the systems that you will be managing. Configuring protocol settings Configuring 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, choose from the following: (Recommended) Use the Internet Control Message Protocol (ICMP) for system reachability (ping) check. This is the default setting. Use the TCP protocol for system reachability (ping) check port number 80. Select this if your company has disabled Internet Control Message Protocol (ICMP) on the corporate network or if the corporate policy mandates system firewall software to filter ICMP requests. Windows XP has this feature built in and can prevent systems from being automatically discovered. This option enables you to run HP SIM and ping all available systems. This option only applies to IP-based systems and is available for global, system-wide settings that are used when managing all systems in HP SIM. It is used by automatic discovery, hardware status polling, the ping tool, and any other tool that must verify system availability. This option is not available on a single-system basis. When HP SIM attempts a connection request to a system, that system does not need any additional software running on it for this option to work. For example, HP does not require that a web server be running on port 80. Some networking systems might not respond to the TCP request, which is typically seen in low-end networking equipment. You can make manual additions, if necessary. However, this system displays as Critical if hardware status polling is run. To use a port other than port 80, change the NodeReachableTcpPort property in the globalsettings.props file located in C:\Program Files\HP\Systems Insight Configuring protocol settings 56

57 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 satellite link, use a larger time-out (for example, five seconds) with at least one retry. For a LAN, you can use a shorter time-out. You can configure this setting on a single-system basis. 4. In the Default WBEM settings section, verify that Enable WBEM (the default) is selected to allow Web-Based Enterprise Management (WBEM) requests to be sent. Enter as many default user names 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 user name and password pair until a successful response is obtained. Future WBEM requests to that system use the user name and password that succeeded. For Windows-based systems, the user name should include the domain name, for example, domainname\username. If you have WBEM systems and you do not enter a user name and password pair, the systems will not be discovered. Order the name and password pairs such that root and administrator passwords are listed first and user and guest passwords are listed second. This order minimizes the search time. HP recommends limiting WBEM user name and password pairs to 10 to reduce the overall discovery run time. To add more than 10 WBEM user name and password pairs, run the mxnodesecurity -a -p wbem -c username:password command for each additional set. You can also create an XML file that defines your system authorizations before running discovery. OpenWBEM is not supported. 5. In the Default HTTP settings section, select Enable HTTP and HTTPS if you need web-based agents and other HTTP port scans to be identified. HP recommends leaving this option enabled for proper management and discovery of systems. 6. In the Default SNMP settings section, verify that Enable SNMP (the default) is selected and specify values for Default time out and Default retries. For systems managed over a WAN or satellite link, use a larger time-out (for example, five seconds) with at least one retry. For a LAN, a shorter time-out can be used. You can configure these settings on a single-system basis. 7. (Optional) Enter the Default write community string. This value is case-sensitive. Only a few tools need this option set. Community strings are case-sensitive. Note: The Write community string is optional and is required only for firmware updates on a GbE switch. If you must update the GbE switch firmware, you must first set the write community string from this page and then run the existing switch update task. Do not set this feature if the network is not trusted. 8. In the Read community string field, enter up to 10 read community strings. This value is case-sensitive. The identification process attempts communication with a system, using each of these communities in succession until a successful response is obtained. Future SNMP requests then use the community string that provided a successful response. If you have SNMP systems and no read community string that match the systems are entered, the systems 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-UX 11.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. DMI is not currently supported on Linux systems and is not shown in the user interface. 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 57

58 Users and authorizations Adding users NOTE: Users that have been added to the Central Management Server (CMS) cannot view or manage systems 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. For security reasons, you might want them to run as a specific user to avoid permitting unintended capabilities to a user. HP Systems Insight Manager (HP SIM) enables you to configure authorizations for specific users or user groups. Authorizations give the user access to view and manage systems. Each authorization specifies a user or user group, a toolbox, and a system or system group. The specific set of tools that can be run against a 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 the users are authorized to execute against the managed systems. A user with no toolbox authorizations on a system cannot view or manage that system. Authorizations are additive. If a user is authorized on Toolbox1 on a system and is also authorized for Toolbox2 on the same system, the user is authorized for all tools in both Toolbox1 and Toolbox2 on that system. Similarly, a user authorized for the All Tools toolbox needs no other toolbox authorization on that system because the All Tools toolbox always includes all tools. Create a new user account to sign-in to HP Systems Insight Manager (HP SIM). The account must be valid on the operating system (including Active Directory on Windows) on the Central Management Server (CMS) and is authenticated by the CMS. You must know the operating system user account name of the user you are adding, but it is not necessary to know the password. To create a new user: 1. Select Options Security Users and Authorizations Users, and then click New. The New User section appears. 2. (Required) In the Sign-in name [on central management server(cms)] field, enter the operating system login account name 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 validated until the user attempts to sign-in to HP SIM. 3. (Optional) In the Domain (Windows domain for sign-in name) field, enter the Windows domain name for the login name if the CMS is running a Windows operating system. If left blank, the CMS system name is used as the domain. Note: If the user account was migrated from Insight Manager 7, the Domain (Windows domain for login name) field associates a placeholder domain with the user. If the user receives pages, this field must be edited to include a valid domain on your network. 4. (Optional) In the Full name field, enter the user's full name. 5. (Optional) If you are using Windows, in the Phone field of the Pager Information section, enter the pager phone number. If the Phone number field is left blank, the paging information is not saved. This field does not apply to user groups.. 6. (Optional) In the address field, enter the user's address. 7. In the Copy all authorizations of this user or [template] field, select a template (administrator-template, operator-template, or user-template) or sign-in account that already has the predefined authorizations that you want to assign to the sign-in account you are creating. 8. For user accounts that must be able to create, modify, or delete other accounts in the Central management server security configuration right section, select User can configure CMS security access such as creating, modifying or removing other users. If you selected an existing user with administrative rights or the administrator template in the previous step, this option is automatically selected. 9. Under the Sign-In IP Address Restrictions section, in the Inclusion ranges field, enter the IP addresses of the systems you want this user to be able to use as a client browsing this CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP address or two IP addresses 58 Configuring HP SIM using the Options menu

59 separated by a dash (-). The IP addresses must be entered in the standard dotted decimal notation, for example, Any spaces surrounding the semicolons or dashes are ignored. Spaces are not allowed within a single IP address in the dotted decimal notation. Enter to 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. If browsing to localhost, ensure the loopback address is also included. 10. In the Exclusion ranges field, enter the IP address of the systems that should be excluded from management by this user or user group. Use the same format as in the previous step for Inclusion ranges. Enter to prevent a user from logging in through a remote system. Note: Ensure that your inclusion and exclusion ranges do not overlap. 11. Under the Pager Information section, in the Phone number field, enter the pager phone number of the user associated with this user account if you are using a Windows operating system. If the Phone number field is left blank, the paging information is not saved. This field does not apply to user groups. 12. In the PIN number field, enter the PIN number associated with the pager phone number. This field does not apply to user groups. 13. In the Message length field, select how many characters can be accepted in the paging message from the dropdown list. This field does not apply to user groups. 14. In the Baud rate field, select the appropriate baud rate for the pager from the dropdown list. This field does not apply to user groups. 15. In the Data format field, select the appropriate data format for the pager from the dropdown list. This field does not apply to user groups. 16. To save and close the New User section, click OK. The new user account is created. To save and keep the New User section open, click Apply, or to cancel the creation of this user, click Cancel. Adding user groups User groups must exist in the operating system. For Windows, they must also exist in Active Directory. Members of 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, sign in IP address restrictions, and authorizations. When a group's configuration rights, sign in IP address restrictions, or authorizations are changed, this change is immediately reflected for all current members of the group. To create a new user group: 1. Select Options Security Users and Authorizations Users, and then click New Group. The New User Group section appears. 2. In the Group name (on central management server) field, enter the operating system group name to be used for signing in to HP SIM. This field is required. 3. If the Central Management Server (CMS) is running a Windows operating system, in the Domain (Windows domain for login name) field, enter the Windows domain name for the group. 4. In the Full name field, enter the full name for the group. This name appears in the table under the Users tab. 5. In the Copy all authorizations of this user or [template] field, select a template or sign in that already has the predefined authorizations that you want to assign to the group you are creating. 6. For user accounts that must be able to create, modify, or delete other accounts in the Central management server security configuration right section, select User can configure CMS security access such as creating, modifying or removing other users. If you selected an existing user with administrative rights or the administrator template in the previous step, this option is automatically selected. 7. Under the Sign-In IP Address Restrictions section, in the Inclusion ranges field, enter the IP addresses of the systems you want this user to be able to use as a client browsing this CMS. If you list multiple IP addresses, separate them with a semicolon (;). Each range is a single IP address or two IP addresses separated by a dash (-). The IP addresses must be entered in the standard dotted decimal notation, for example, Any spaces surrounding the semicolons or dashes are ignored. Spaces are not allowed within a single IP address in the dotted decimal notation. Enter to 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. If browsing to localhost, ensure the loopback address is also included. Users and authorizations 59

60 8. In the Exclusion ranges field, enter the IP address of the systems that should be excluded from management by this user or user group. Use the same format as in the previous step for Inclusion ranges. Enter to prevent a user from logging in through a remote system. Note: Ensure that your inclusion and exclusion ranges do not overlap. 9. To save and close the New User Group section, click OK. To save and keep the New User Group section open, click Apply, or to cancel to close the New User Group section without saving the new group, click Cancel. Adding toolboxes Create 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. To enable the toolbox and all authorizations created with this toolbox, select Toolbox is enabled. 5. To display a list of tools in the available tools list, in the Show tools in category field, select a category. In the available tools list, select the tools to be assigned to this toolbox, and then click. The selected tools appear in the Toolbox contents list. To remove a tool from the associated tools list, you can select a tool displayed in the Toolbox contents list, and then click. Note: The HP SIM Tools category includes tools that are related to configuration rights on the HP SIM server itself. In previous versions of HP SIM, these rights were only enabled to full configuration rights users. With HP SIM 5.2, any user can be granted these rights if needed based on an authorization. These tools include: Delete Systems in HP SIM, Edit any user tasks in HP SIM, Edit HP SIM Notification Settings, Edit HP SIM Reports, Edit Shared Collections in HP SIM, Edit Systems in HP SIM, Modify HP SIM Events, Run HP SIM Discovery, and View HP SIM Audit Log. Note: For users with operator rights and user rights to clear, delete, assign events, and add comments to 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 then click to add them to the Toolbox contents. 6. To save the new toolbox and close the New Toolbox section, click OK. To save the settings without closing the New Toolbox section, click Apply, or to cancel the new toolbox creation and return to the Toolboxes section, click Cancel. 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. The New Authorizations section appears. 2. In the Select dropdown list, select User(s) or UserGroup(s), and then 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. 60 Configuring HP SIM using the Options menu

61 b. In the Select Systems list box, the two default system groups (All Managed Systems and CMS) are displayed. Select one of these groups, or to select systems for the authorization, click Add to display the Add Systems section. c. In the Add systems by selecting from section, select one of the following: i. Collection Select a collection and click View contents. 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. a. (Optional) To enable the authorization to automatically be updated, without user intervention when a collection is changed, select Automatically track changes. If this collection changes, so does the authorization. b. (Optional) Select Do not track changes. If this collection changes, the authorization will not change. If this option is selected, you must manually update the authorization after a collection has changed by using the Update button on the Authorizations tab. Note: These two selections are only available if a collection of systems is selected and the Select "collection name" itself option is selected. You must select one option or the other. The default selection is based on the DynamicAuthorizations_AutoUpdateDefaultValue property setting in the globalsettings.props file. The default is set to Yes. This is reflected in the Select Systems list box in the New Authorizations section with [Auto] appended to the entry. For example, if you selected All Systems and chose to have it automatically 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 updates for each selected collection. Since automatic updates for any authorization apply to all authorizations using the same selected collection, changing the setting for one affects any other authorization using the same collection. Therefore, during system selections, if you select a group already associated with an automatically updating authorization, the option Automatically track changes. If this collection changes, so does the authorization is preselected. Likewise, if an authorization Users and authorizations 61

62 that does not automatically update is associated with a collection, the option Do not track changes. If this collection changes, the authorization will not change is preselected. c. If you want to select all individual systems from the collection, select the checkbox at the top of the table view in the column heading to select all systems. Note: This action creates a separate authorization for each selected system. d. To save system selections, click Apply, or to return to the New Authorizations section without saving changes, click Cancel. After clicking Apply, a message appears based on the options selections. To return to the New Authorizations section, click OK. ii. Search Enter a system name and click Search, or select a system from the list and click Search. a. Select systems. b. Click Apply, or to return to the New Authorizations section without saving changes, click Cancel. After clicking Apply, a message appears based on the options selections. Click OK to return to the New Authorizations section. A system group is a group of systems based on a system collection that is used for authorizations. Authorizations that use system groups are updated automatically when a change is made to the system collection that the system group is based upon. The option Do not track changes. If this collection changes, the authorization will not change must not be selected for the authorizations to be updated automatically. If you selected individual systems of a collection, each selection populates the list box and is selected for inclusion in the authorization. If you selected a collection and the collection has been used previously in an authorization, a message appears stating that a system group for the collection exists and will be updated with current source collection content. This condition affects all authorizations associated with that collection. When a collection is used for the first time, no message appears. A system group with the name of the collection followed by three numbers, usually (001) is displayed in the Select Systems dropdown list and is selected. 4. To save the new authorization and close the New Authorizations section, click OK, or, if you do not want to create the authorization, click Cancel. Configuring settings Configuring settings enables users to send notification of certain events. To configure settings: 1. Access the Simple Mail Transfer Protocol (SMTP) host and CMS settings through the First Time Wizard or choose Options Events Automatic Event Handling Settings. The Settings page appears. 2. Enter the SMTP host name. The SMTP host is the outgoing server that the CMS uses to send notifications. 3. In the Sender's address box, enter the address that the management server uses when sending notifications. 4. To authenticate your SMTP server, select Server Requires Authentication. 5. Enter the account user name and password in the corresponding boxes. 6. Note If you did not enter a valid Simple Mail Transfer Protocol (SMTP) host, HP SIM notifies you that it cannot send notifications. If you do not want to enter settings now, click OK, or to enter a valid SMTP host, click Cancel. If you are changing the settings from the Options Events Automatic Event Handling Settings page, click OK to save changes. Configuring paging settings Configuring paging settings enables users to receive pages to notify them of certain events. 62 Configuring HP SIM using the Options menu

63 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 then 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. ii. iii. Note: Select an event collection. The event collection is a collection that is defined by event attributes. 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 event collection that contains additional event collections, you will receive an error message. (Optional) Click View Definition to view the collection attributes that define the event collection. Note: This field is displayed if you selected an existing private or shared event collection. If the collection was created using the Automatic Event Handling feature that enables you to select event and system information, this will not be displayed. Click Next. The Select system collection page appears. If the event collection contains system information, the select system collection process will not be displayed. Instead, the Select 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 collection attributes or the members of the system collection that 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: iii. List criteria Comparison option Value for the criteria or comparison options selected To add additional search criteria, click Add. Click Next. The Select actions page appears. Users and authorizations 63

64 5. Select from the following options: Send page (Windows only) 1. Add users to be paged from the dropdown list of users by clicking. Click to remove selected users from the list of users to be paged. The pager number for an HP Systems Insight Manager (HP SIM) 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 of users to be paged, but pager messages are not sent to this user until the pager information is provided. Note: If you select a user that does not have pager information set, the Pager Information section expands where you can enter the information. 2. Enter the paging information. Send Phone number Enter the pager phone number of the user associated with this user account if you are using a Windows operating system. If the Phone number field is left blank, the paging information is not saved. This field does not apply to user groups. PIN number Enter the PIN number associated with the pager phone number. Message length Select how many characters can be accepted in the paging message from the dropdown list. Baud rate Select the appropriate baud rate for the pager from the dropdown list. Data format Select the appropriate data format for the pager from the dropdown list. Click Apply. A dialog box appears stating that the changes were successful. Click OK to close the box. In the To field, enter the list of addresses that should receive the notification, separating each entry with a comma. In the CC field, enter any address that should receive a copy of the , separating each entry with a comma. In the Subject field, enter a note describing the subject of the . In the Message Format field, select from the following formats based on the encoding preference of the recipient: Standard. A default message format that sends a text message to the recipients. Pager/SMS. An message format that sends a message to the recipients with the same information and format as a pager message. HTML. An message format that sends a message to the recipients that looks like the HTML Event Details page. In the Encoding field, select from the following formats: Western European (ISO ) Unicode (UTF-8) Japanese (ISO-2022-JP) Japanese (Shift_JIS) Japanese (EUC-JP) Chinese (GB18030) Chinese (Big5) Korean (EUC-KR) Run custom tool Select a custom tool from the Name dropdown list. Custom tools are created under the Tools Custom Tools New Custom Tool option, and then select CMS tool. 64 Configuring HP SIM using the Options menu

65 Assign Enter the name of the person to whom to assign the task. The event is assigned to this user when received. 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 then 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 and HP-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 then select an option from the dropdown list. 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 matching the selected criteria are received. If the Use time filter checkbox is selected, actions are triggered only when they occur during the days 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, owner, time filters, event collections, system collections, and actions information is displayed. If a paging or option was selected, the modem and settings are displayed, along with buttons to change the settings. 8. (Optional) Click Edit modem settings to edit the modem settings, or click Edit Settings to edit the SMTP settings. Note: The event and system search criteria appear at the bottom of the page. This information can be extremely 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 the database 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 network to populate the database with that information. A system must first be discovered to collect data and track system status. Manual discovery The process that enables you to bypass a full automatic discovery and add single and multiple systems to the database, create or import the HP SIM database Hosts file, and create or import 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 for All Discoveries section appears. Users and authorizations 65

66 3. Select from the following options: Automatically discover a system when an event is received from it. This option enables systems to be discovered when a trap or some other supported event is received by HP Systems Insight Manager (HP SIM). It uses the discovery filters and IP address exclusion ranges for additional filtering of these events. This option is not selected by default. Automatically discover a server blade when its Integrated Lights Out management processor is identified. This option adds servers indirectly discovered through the server's management processor, which are discovered when the server's ilo is discovered. The discovered servers are identified as Disabled on the system table view page. The only information displayed is the system serial number and the association to ilo and the enclosure. If the ilo is in a c-class enclosure, the option,discover systems in an enclosure when Onboard Administrator is discovered should also be enabled. Select Discover systems in an enclosure when Onboard Administrator is discovered. This option adds systems identified by the Onboard Administrator even if the systems are not in the configured discovery range. This option is selected by default. Select Automatically discover VM guest(s) when the host is identified. This option adds all HP Integrity Virtual Machine (HPVM) guest systems to the HP SIM database when the HPVM host system is discovered and identified. This option is selected by default. Note: For automatic identification of virtual machine guests running on a virtual machine host, the IP address of the guest is required. To acquire the IP address from Web-Based Enterprise Management (WBEM) Providers, VMWare tools must be installed on the virtual machine guests. Automatically discover other virtual partitions within the same vpar Monitor when one of the virtual partitions is identified. This option is selected by default. Automatically discover all npars within the same complex when one of the npars is identified. This option is selected by default. 4. 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. You can also enter Simple or Fully Qualified Domain Names (FQDN) host names. However, you cannot enter a range of host names. This field applies to both range-pinging and event-based automatic discovery. Important: When discovering clusters, the ping inclusion range must include the IP addresses of the cluster and the cluster members. 5. Select Enable discovery filters. 6. In the section, Discover the following system types, select the type of systems to be discovered. Important: When discovering clusters, you must include the server system type, so that the cluster members are 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: The option, Limit discovery to systems which meet the following criteria is available only when you select Enable discovery filters. 8. To save settings, click OK, or to close the General Settings for All Discoveries section without saving changes, click Cancel. 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 ongoing operations or to make other changes: Edit, Enable or Run Now. If you would like to create other discovery tasks, click New. 66 Configuring HP SIM using the Options menu

67 Configuring and executing manual discovery 1. Select Options Discovery, and then click the Manual tab. The System Information section appears. 2. Enter the system name or IP address. Simple or Fully Qualified Domain Name (FQDN) host names can be entered. However, ranges of host names are not allowed. 3. Click Add System to add the system to the database. If you have not entered the SNMP or Web-Based Enterprise Management (WBEM) credentials for this system previously, click More Settings. Enter the credentials, then click Add System, or click More Settingsand enter the following information: Users and authorizations 67

68 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 input up to eight different system subtypes. Product model Enter the system model number here. This field is free form. 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 then enter custom values. If you are manually discovering a storage system, ensure that the user name and password of the SMI CIMOM are present in the global protocol settings, or enter them here as custom values. To view the global settings, select Options Protocol Settings Global Protocol Settings. 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 the system. If a response is not received within this time interval, HP SIM might determine that the system does not support SNMP. Decreasing this value can case increased network 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. 68 Configuring HP SIM using the Options menu

69 However, if systems are connected 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 a system before the attempts stop. Read-only community string and Write community string Note: The Write community string is optional and is required only for firmware updates on a GbE switch. If you must update the GbE switch firmware, you must first set the write community string from this page and then run the existing switch update task. Do not set this feature if the network is not trusted. A community string sets up authentication that enables or prohibits communication between the managed system and the Central Management Server (CMS). The community string of the CMS must match the community string of the managed system. Use the read-only community string to read variables. Use the write community string to modify variables. Although only one community is valid for a communication attempt, a system can belong to multiple communities. However, HP SIM only uses one community string when communicating with a system. Users and authorizations 69

70 6 Setting up and configuring managed systems At this point, steps 1 and 2 below are complete. Perform step 3 to install and configure the required management software. 1. Install and configure the CMS. The procedure to complete this step is in Chapter 3 Installing HP SIM on the Central Management Server (CMS) for the first time. 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 Discovery is part of the First Time Wizard. 3. Install and configure the required management software on the systems that will be managed by the CMS. The procedure to complete this step is in this chapter. 4. Configure the remaining protocols for the managed systems. Setting up managed systems involves installing the required management software. The management software being 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 Setting up managed systems from a Windows CMS Use the following checklist as a guideline to assist you with setting up managed systems from a Windows Central Management Server (CMS): 1. Ensure that HP Systems Insight Manager (HP SIM) is installed on the CMS. 2. Ensure 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. Configure the managed system software. See Configuring the managed system software using the Configure or Repair Agents feature from the CMS for more information. Configuring the managed system software using the Configure or Repair Agents feature from the CMS The HP SIM Configure or Repair Agents tool is a quick and easy way to configure Linux, 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 have authorizations to run the Configure or Repair Agents tool. You must have full CMS configuration privileges to modify the HP SIM community strings in the system 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 Step 1: Verify Target Systems page appears if the targets are selected before selecting a tool. 2. Select target systems. 3. Click Next. The Step 2: Enter credentials page appears. The credentials specified on this page are for a privileged account on the target system. Note: If you plan to Configure secure shell (SSH) access on a Windows target system, the account specified must be a member of the local Administrators group. For Windows targets using a domain account, the account is automatically added to this group if applicable. Setting up managed systems from a Windows CMS 70

71 4. From the Step 2: Enter credentials page: a. In the User name field, enter the system administrator name. b. In the Password field, enter the system administrator's password for the user name previously entered. c. In the Password (Verify) field, reenter the system administrator's password exactly as it was entered in the Password field. d. In the Domain field, enter the Windows domain if you are using a domain account. Note: The credentials used in this step must work for all target systems that have been selected. HP recommends using domain administrator credentials. Credentials entered here are not saved by HP SIM except to run a scheduled task later. 5. Click Next. The Step 3: Install Providers and Agents (Optional) page appears. 6. You can install Insight Management Agents or providers, either Web-Based Enterprise Management or Simple Network Management Protocol, on managed systems so HP SIM can collect inventory and status information from these systems and receive event notifications from the systems. Installation is supported only on ProLiant or Itanium-based servers with Windows operating system. From the Step 3: Install Providers and Agents (Optional) page: Setting up managed systems from a Windows CMS 71

72 a. Select Install WBEM / WMI Provider (HP Insight Management WBEM Provider) for Windows to install WBEM or WMI providers on Windows managed systems. b. Select Install SNMP Agent (HP Insight Management Agents) for Windows to install the SNMP agent on Windows managed systems. This Insight Management Agent allows network monitoring and control. c. Select Install Open SSH to install OpenSSH on Windows managed systems. d. Select Install the Version Control Agent (VCA) to install the HP Version Control Agent; (VCA) on Windows managed systems. The VCA enables you to view the HP software installed on a system and wheonfigther updates for the software are available in the repository. HP SIM determines the type of agent/provider to install based on the system type, subtype, and operating system description of the system. Table 6-1 Version Support Matrix for components used for install. Supported systems HP WBEM Provider HP ProLiant Agent Open SSH Version Control Agent Unknown 2.1 (32 bit) 7.90 (32 bit) ProLiant systems with 32 bit Windows operating system ( 2003, 2008 ) 2.1 (32 bit) 7.90 (32 bit) ProLiant systems with 32 bit Windows operating system (2003, 2008) 2.1 (64 bit) 7.90 (64 bit) ProLiant systems with 32 bit Windows operating systems (2000) Not supported 7.60 (32 bit) Itanium-based systems with Windows operating system (2003) Not supported System Management Homepage version is also installed, if necessary, with these agents. NOTE: If you wish to install a 64 bit agent or provider, make sure the target system is identified as a 64 bit system in HP SIM. If your system is not correctly identified, go to System Page Edit System Properties. Select the correct system type, subtype and enter the operating system description manually. Example: Installing Insight Management Agents on a ProLiant Windows 64 bit system: 72 Setting up and configuring managed systems

73 1. Select system Type: server. 2. Select system subtype 1: ProLiant 3. Enter operating system description as Microsoft Windows Server 2003, x64 Enterprise Edition Service Pack 1 or the correct operating system description of your system. If you want to configure the agents after installing, select the force reboot option. This allows the newly installed component to be completely initialized before configuring it. Note: Installation with reboot typically takes about 8 minutes to complete. 7. Click Next. The Step 4: Configure or Repair Agents page appears. 8. The Step 4: Configure or Repair Agents page enables you to select options to configure the target system. The following options are available: Configure WBEM / WMI. This section enables you to configure the target Linux, Windows or HP-UX system to send WBEM indications or events to HP Systems Insight Manager. For this section, the following must be considered: Create subscription to WBEM events, so that WBEM events will be sent to the CMS. Send a sample WBEM / WMI indication to this instance of HP SIM to test that events appear in HP SIM in the Event list or All Event User Interface for the selected system. Note: The indication will appear as an Informational Event in the Event List of HP SIM. Setting up managed systems from a Windows CMS 73

74 Note: This is supported only on HP-UX and Windows managed systems with WBEM provider installed. Use an HP SIM WBEM certificate (good for 10 years) rather than username/password to manage the system. This option deploys a WBEM certificate to the managed system and is only valid for HP-UX systems. Configure a non-administrative account for HP SIM to access WMI data. This option is applicable to Windows systems with HP WBEM providers. The configuration of the managed system will be updated to allow the specified user to access WMI information over the network. This user will be used by HP SIM to read inventory and configuration information from the system, and will be configured as the WBEM user in the System Protocol Settings. This configuration step is not necessary if HP SIM is configured with a user with administration rights. This user is not created by HP SIM; it should already exist as either a domain user or one local to the managed system. The user will be added to the "DCOM Users group on the managed system and will be given read-only access to WMI information, plus read-write permissions to the HPQ name space. This user does not need to be an administrator of the managed system and need not have logon rights. A special purpose domain account is recommended, and should be created by the domain administrator. To enter the credentials for HP SIM to use to access the managed systems: 1. In the User name field, enter a user name. 2. In the Password field, enter the password for the user's name previously entered. 3. In the Password (Verify) field, reenter the password exactly as it was entered in the Password field. 4. In the Domain field, enter the Windows domain if the target belongs to a domain. If configuring a non-administrative user is successful, then these credentials are saved as the System Protocol settings for WBEM access in HP SIM. Configure SNMP. This section enables you to configure SNMP settings. For this section, the following must be considered: a. Select Set read community string to specify a community string. By default, HP SIM's first community string, that is not public, appears in the field. If no community string exists in HP SIM, you must enter one. Note: If only HP-UX systems with default SNMP installation are being configured at this time, you need not set this option. HP-UX enables read by default (get-community-name is set to public by 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 systems do not always enable SNMP communication between themselves and a remote host. This setting is modified to enable the instance of the HP SIM system to communicate using SNMP with these target 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 system only if one does not currently exist. This community string is unique for each system, is composed of over 30 characters to include letters and numbers, and is only visible to the user with administrator 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 only used locally on the target system and is not used by HP SIM over the network. Linux and 74 Setting up and configuring managed systems

75 HP-UX systems do not require a Read Write community string; hence the Read Write community is added on Windows systems only. b. Select Set traps to refer to this instance of HP Systems Insight Manager in the target systems' SNMP Trap Destination List. This setting enables the target systems to send SNMP traps to this instance of HP SIM. c. Select Send a sample SNMP trap to this instance of the HP SIM to test that events appear in HP SIM event lists to verify that SNMP events appear in the HP SIM events list. To successfully send a test trap, you must configure target systems to send a trap to this instance. Note: A test trap can only be sent from a Windows managed system with HP Insight Management Agent installed. If you attempt to run this task on a Linux or HP-UX managed system, a message displays indicating the operation is not supported. Note: The trap will appear as a Generic Trap from the system. This event will appear as an Informational Event in the Event List of HP SIM. Configure secure shell (SSH) access. Select this option to configure SSH access on managed systems. 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 in step 2 must 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 you do not want all users that have login access to HP SIM to run the tool and you would like to control which users need to have access, this option is more secure. 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 as done in step three or by selecting the tool under Deploy Deploy Drivers Firmware and Agents Install Open SSH. Set Trust relationship to "Trust by Certificate". Select this option to configure 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 SIM system certificate to the target system's trusted certificate directory. This option enables HP SIM users to connect to the System Management Homepage using the certificate for authentication. You can configure Single Sign-On (SSO) to management processors for Onboard Administrators and for Integrated Lights-Out 2 (ilo2). To configure SSO, select Set Trust Relationship. After SSO is configured, you are not continually prompted to supply the login credentials for the management processor. Note: For systems with Management HTTP Server 4.x and earlier, Configure or Repair Agents adds the Administrator password in the Management HTTP Server store and modifies the SNMP settings but cannot change trust relationship information because Management HTTP Server 4.x and earlier did not deploy trust relationships. Configure Version Control Agent (VCA). Select this option to configure the VCA to point to the HP Version Control Repository Manager (VCRM), where the repository of software and firmware is located, enabling version comparison and software updates. This option is available only for Windows systems. This section can be accessed in the Configuration section of all CMS systems including Windows, Linux and HP-UX. To configure VCA: 1. In the Select the system where the VCRM is installed field, select the server where the VCRM is installed from the dropdown list. 2. In the User Name field, enter the user name to access the VCRM. This user cannot be the default "Administrator" user. It has to be an user with administrative privileges. Setting up managed systems from a Windows CMS 75

76 3. In the Password field, enter the password to access the VCRM. 4. In the Confirm Password field, reenter the password for the VCRM just as you entered it in the Password field. Set administrator password for Insight Management Agents version 7.1 or earlier. Select this option to repair the administrator password on all Insight Management Agents installed on the target systems as applicable for Windows and Linux systems. Note: Do not set 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 since it is not applicable on HP-UX systems. If only HP-UX target systems are being configured at this time, you need not set this option. If this option is selected, you must complete the following steps: a. In the Password field, enter the new administrator password. b. In the Confirm Password field, reenter the new administrator password exactly as you entered it previously. 9. 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 which might potentially have different results. The log results indicate whether the repair attempt was successful. 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 value is zero or positive, the executable ran successfully. If a negative value is returned, the executable failed. This exit code does not indicate that all configuration attempts were successful. It is possible for some to succeed and for some to fail. 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. View Printable Report. Reports can be printed for the currently selected target system or for all target systems associated with the task instance. To print a report: a. Click View Printable Report. An Options Message box appears, asking if you want to generate a report containing only the currently selected target system or all systems associated with the task instance. b. Select which report to display. c. Click OK to display the report, or click Cancel to return to the View Task Results page. 10. If the Management HTTP Server is installed on target systems, the login credentials are updated in the Management HTTP Server password file. Consistent with many other HP Systems Insight Manager tools, the Configure or Repair Agents tool can be configured to run automatically on a schedule, or you can run it manually. Only one instance of Configure or Repair Agents tool can run at a time. Setting up managed storage systems Storage 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 uses this 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 for HP 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.) 76 Setting up and configuring managed systems

77 See the HP SIM SMI-S Provider webpage, to view the latest information regarding HP SIM support for a particular device. This webpage offers information on obtaining, installing, and configuring SMI-S providers. Installing SMI-S providers Verifying SSL Each storage vendor provides the SMI-S provider and installation instructions for its storage system. The webpage referenced in the previous section provides information on obtaining SMI-S providers. Also, consult the 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. HP SIM requires that Secure Sockets Layer (SSL) is enabled for the SMI-S provider in order to discover and manage the storage system that the provider supports. Verify that SSL is enabled for each SMI-S provider. Configuring SMI-S providers Occasionally, it might be necessary to modify an SMI-S provider s port number or password. Use the provider s documentation to perform these modifications. For example, if two CIMOMs exist on the same host, you must configure them to use different ports to communicate 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 to discover 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 settings section 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 for more information. HP SIM discovers the storage systems after the next automatic discovery task. If you want to discover your storage systems immediately, run the discovery task as described in the Running a Discovery Task section of the HP SIM User Guide at Setting up managed storage systems 77

78 7 Initializing the Remote Support Software Manager on the Central Management Server (CMS) Understanding the Remote Support Software Manager The HP Essential Services Remote Support Pack includes three components: HP Remote Support Software Manager (RSSWM): RSSWM, bundled with HP Systems Insight Manager (HP SIM) 5.2 and installed to the Central Management Server (CMS), facilitates the download and installation of HP Remote Support applications. The steps to complete this process are in this chapter. HP Remote Support Client: The Remote Support Client is installed and updated by RSSWM. Once installed, the Remote Support Client is accessed through HP SIM and is used to enable remote support of eligible devices in your Enterprise. The Remote Support Client enables communication of reactive hardware events from the CMS to the HP Support Center. This chapter focuses on RSSWM. RSSWM is bundled with the installation of HP SIM on a supported Windows ProLiant CMS. RSSWM 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. With the Standard or Silent HP SIM Installations, the HP Remote Support Software Manager (RSSWM) installation is non-interactive. Once installed, the Remote Support Software Manager application can be accessed from an icon on the CMS desktop. With the Custom HP SIM Installation, RSSWM prompts for an installation directory path and will launch the RSSWM Configuration automatically. After any version of the HP SIM installation is complete, users configure the Remote Support Software Manager to fit their enterprise specifications. Once configured, the Remote Support Software Manager will download and install the Remote Support Client. IMPORTANT: The process for configuring the Service Essentials Remote Support Client after it is installed on the CMS through Software Manager, is documented in the HP Service Essentials Remote Support Pack Configuration and Usage Guide at This document is required to complete the configuration of the Service Essentials Remote Support Pack. RSSWM offers the following functionality and benefits: Upgrades can be performed remotely, reducing HP Support Engineer time on your site for installations. Automated notifications of new software, deployment statistics, and the state of your configurations improve 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 RSSWM device and access requirements RSSWM is supported only on ProLiant servers running: Windows 2003 Standard, and Windows 2003 Enterprise Windows 2000 Server SP2, Advanced Server The RSSWM downloads and installs software to the CMS only, and operates only on a CMS installed on a supported Windows ProLiant device. RSSWM and Service Essentials Remote Support Pack are NOT supported on Virtual Machines (VMWare). Use of RSSWM User Interface requires administrator privileges on the Windows operating system. If you do not have an account with administrative privileges, please contact your Remote Support Account Team for more information or assistance. Understanding the Remote Support Software Manager 78

79 The Software Manager on the CMS communicates over HTTPS/443. Likewise, the Remote Support Client component also communicates over HTTPS/443 to submit incidents to and retrieve entitlement information from the HP Support Center. HTTPS provides encryption for confidentiality of software configuration data collected from the CMS and transferred to HP. Even though this chapter focuses on configuring RSSWM, it is advisable to configure your firewall for both communication channels (RSSWM and Remote Support Client) before proceeding. Service HP Remote Support Software Manager HP Remote Support Client Server name isee-updates.americas.hp.com services-isee.americas.hp.com IP Address RSSWM communicates directly with the HP Support Center through the firewall or web proxy server (if a web proxy server is in use). Remote Support RSSWM supports connecting directly to the Internet or connecting through a proxy server and supports all proxy servers conforming to the HTTP/1.0 Specification. Remote Support Software Manager does not support proxies using proxy auto-configuration scripts, NTLM authentication (also known as Integrated Windows Authentication), or Kerberos authentication. NOTE: You can check for any software or networking updates in the Service Essentials Remote Support Pack Release Notes at HP Remote Support Software Manager Configuration Options The RSSWM 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 RSSWM abilities on the CMS are: The ability to define automation level settings that configure if and how updates will be downloaded and installed. The ability to define an update schedule during a time window in which RSSWM can request and retrieve updates. The following table lists items configured during the RSSWM Initialization: Required Information Web Proxy Settings are configured to enable the Software Manager to function in conjunction with your proxy server configuration. Customer s Company Name Country/Region HP Contact Reporting Options field adds the CMS to an internal HP report of systems supported by a specified HP contact. Options The web proxy options enable specified settings which include: Server Port Proxy Server User Name Proxy Server Password The default web proxy server settings will be blank and must be populated with the correct proxy information to enable the subsequent connectivity test. Provide your company name. While it is not technically necessary to enter your company name as it appears on your service agreement, doing so will improve communication with HP through consistency of information. The country or region where the CMS physically resides must be selected from the drop down menu in the RSSWM Initialization process. You can enter zero or multiple (separated by semi-colons) HP contacts into this field to receive reports for this CMS. By default, this line is left blank. Customer Contact Notification Options field adds the included contacts to a notifications list to be notified when updates are published to the RSSWM servers at the HP Support Center and to receive biweekly reports about the CMS and RSSWM application. You might enter zero or multipledypyp (separated by semi-colons) customer contacts into this field to receive notifications about updates for the CMS. By default, this field and the associated check boxes are left blank. Unless you add contacts to this list and check the appropriate boxes, no notifications will be sent. Understanding the Remote Support Software Manager 79

80 Required Information Global Automation Levels enables you to restrict the application of all updates to the CMS. Global Update Window settings enable restrictions of when downloads and installations occur on the CMS. Options The Automation levels are: 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 must make a selection. See Automation Levels and Scheduling in the Software Manager for more information about using Automation Levels. The scheduling options are: 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 By default, Anytime is selected. See Using the HP Remote Support Software Manager for more information about using Remote Support Software Manager. Initializing the HP Remote Support Software Manager Software Manager The initialization and registration of HP Remote Software Manager can only be performed by a user who is logged onto the CMS via the system console or a console-mode RDC Session. Users should not attempt to initialize or register a CMS with the Remote Support Software Manager via a non-console mode Terminal Services or RDC session. HP Remote Support Software Manager is installed by default with an HP SIM 5.2 typical installation and optionally with an HP SIM 5.2 custom installation. When selected, RSSWM is installed on the CMS but not yet configured. With a custom installation, the RSSWM UI starts automatically. With a typical installation the RSSWM UI does not start automaticallly. The first time you access the RSSWM interface after a typical or silent installation, you are prompted to complete the initialization. The RSSWM 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 beginning the initialization process. About the Initialization Process Throughout the RSSWM initialization, Form Submission and Action Submission windows appear These windows confirm that the data you provided or the direction you gave was accepted by the initialization process. These windows are mentioned but not displayed in the initialization instructions documented in the following section. Throughout the RSSWM installation a yellow Please Wait information box appears periodically as the process completes tasks. The following sections do not document every instance where the Please Wait box appears. 80 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

81 Completing the Remote Support Software Initialization Process After a custom installation the Remote Support Software Initialization starts automatically. The same instructions apply in this situation as are documented in the following section with two exceptions: 1. When the RSSWM initialization starts after a custom installation the User Interface does not display an Update All option in the left panel. The first example below is what the menu looks like when the initialization starts automatically after a custom installation. The second example is what the menu looks like if you open the RSSWM initialization after a typical or silent installation. 2. At the end of the initialization, additional steps may be required to update the components outside of the default download window; this is documented in step 22 in the following section. Please procede to the next section, starting with step 2, to configure RSSWM after a custom installation. Running the Remote Support Software Initialization Process To initialize the Remote Support Software Manager: 1. Start the RSSWM by double clicking the Remote Support Software Manager (Windows Administrator Access only) icon on the CMS desktop. 2. Click Continue in the Introduction window. Initializing the HP Remote Support Software Manager Software Manager 81

82 3. Select the Enable the following web proxy settings for HTTP communications box, and then select 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 Support Center. 7. Click Continue in the Action Submission window. 8. Enter the name of your company and click Continue. 82 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

83 9. Click Continue in the Form Submission window. 10. Select your appropriate Country/Region from the drop down list and click Continue. 11. Click Continue in the Form 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 the Contacts window. You may disable biweekly reports and periodic notifications sent from the HP Support Center through the Internet to your addresses at anytime by referencing the steps in Understanding and Configuring Customer Notifications and Reports 14. Click Continue in the Form Submission window. 15. Select your bandwidth settings and click Continue. NOTE: The bandwidth settings are set to a low value (10 Mpbs) by default, and this default will add to the duration of the RSSWM configuration. To expedite the configuration of RSSWM AND Service Initializing the HP Remote Support Software Manager Software Manager 83

84 Essentials Remote Support Pack, you may choose to increase the bandwidth settings to at least 100Mbps. You can restore a lower setting once the configuration and registration are complete. 16. Click Continue in the Form Submission window. 17. Select your Global Preferences and click Continue. If you select Automatic Install to activate automatic downloads and installations of software packages, then you will not be prompted for download or installation activities.during an Automatic Installation, you may see the status Aborted in the Packages window. This is normal behavior during the installation phase. If the status does not change to Installed in a reasonable amount of time, you may check the HP Remote Support Software Manager Troubleshooting guide at If you select Automatic Download to activate automatic downloads only, then software package installations must be done manually. If you select Manual, then all downloads and subsequent installations will require manual approval and actions. You can check for software updates by logging into the Remote Support Software Manager. See Understanding Automation Levels in the Remote Support Software Manager for more information about using Automation Levels, and for more information about selecting your scheduling options, please see Understanding and Modifying Scheduling in Software Manager. 18. Click Continue in the Form Submission window. 19. Click Continue in the Configuration window, and the settings you have configured will be applied to the Remote Support Software Manager. There will be a several minute delay while the changes are updated, and you may see applications windows open and close. 84 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

85 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 will be applied to your CMS immediately. You may reset to more restrictive options after the initialization is complete. 20. Click Continue in the Action Submission window. 21. Click Continue in the Registration 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. 22. Click Continue in the Action Submission window. IMPORTANT: If you originally performed a custom installation, this is your last step in the Initilization UI. You must now exit the RSSWM User Interface, and restart it to update your software packages immediately, or if you wait for up to six hours (if not restricted by update window settings) it will update itself automatically. To update immediately, upon reopening the RSSWM UI, choose the Actions option and in the Actions window, initiate the Check for Package Updates option by clicking the Check button. Once the packages are available, manage your package downloads and installation as directed in the section titked Using the HP Remote Support Software Manager. 23. It is highly recommended that you click Continue in the Update All window. If you do, the CMS will receive updates of all of the latest packages from the HP Support Center. There will be a delay of several minutes while the changes are communicated to the HP Support Center, and the status will be displayed. 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 your configuration or until the packages are updated according to your Automation Level options. Initializing the HP Remote Support Software Manager Software Manager 85

86 24. Click Continue in the Action Submission window. 25. Click Finish in the Finish window to complete the Software Manager initialization. There will be a delay while the initialization completes, after which the Software Manager User Interface will reload with the standard display, rather than the initialization display. NOTE: If the Software Manager Packages window does not list any packages, please review the previous steps and verify that they were completed successfully and that the Update All process was selected. You can enter any corrected information in the standard RSSWM display and resubmit it using the steps in the Understanding and Using the Actions Option section. 86 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

87 NOTE: The OSEM application and its read me file will open after the Update All process runs. You can close these windows. Using the HP Remote Support Software Manager Modifying HP Remote Support Software Manager Settings Most of the RSSWM settings are originally configured during the Initialization. The settings can be modified at any time to meet your unique needs. For any of the following sections, this step is required to access the RSSWM and is then assumed in subsequent instructions: Start RSSWM 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 RSSWM, 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 and committed to the RSSWM. These windows will be mentioned but not displayed in the instructions documented in this section. Initializing the HP Remote Support Software Manager Software Manager 87

88 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 be downloaded and/or installed. The ability to define an update schedule during a time window in which RSSWM may request and retrieve updates. The Remote Support Software Manager applies a combination of global and package-specific preferences to 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 settings can be modified through the Remote Support Software Manager. The following table outlines the Remote Support Software Manager Automation Levels: Preference Global Automation Levels Enable the Customer to restrict the application of all updates to the CMS. Package Automation Levels enable the Customer to restrict the application of updates to a specific package. Allow Downloads and Installations (or Global Update Window) settings enable restrictions of when downloads and installations occur on the CMS. Package Scheduling determines when downloads and installations occur for each specific package. Options The Automation levels are: Allow automatic download and install Allow automatic download but install manually Do not automatically download nor install The Automation levels are: Use Global Automation Settings Allow automatic download and install Allow automatic download but install manually Do not automatically download nor install The default package automation setting is to use the Global Automation Setting. The scheduling options are: 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: Never Allow at a specified time/interval on a specific day(s) of the week Allow at a specified time/interval on every day Allow at a specified time/interval on a specific day of the month The default scheduling options are specific to each package. For more information about using the Remote Support Software Manager see Using the HP Remote Support Software Manager. Understanding Automation Levels in the Remote Support Software Manager The Global Automation Levels are set during initialization of the Remote Software Manager. Individual package settings, however, cannot be configured until initialization. The following descriptions explain the differences and relationship between the Factory Automation levels, Global Automation levels, and Package Automation levels. Factory Automation Levels: When a software package is created by HP it has factory automation levels set based on the intended function and business usage of the software package. These settings may be more or less restrictive than the global or package automation levels set by the Customer. If the factory automation levels are more restrictive, for instance Automatic Download, than the Global 88 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

89 Settings configured to Automatic Install, then the package will only download and will require manual installation. Global Automation Levels: Set globally, these levels are applied to all packages received by the Remote Support Software Manager, unless an individual package s levels are configured independently from the global setting. Package Automation Levels: As the authoritative automation level Package levels are customized per individual package. If not modified, the package level resolves to the existing global automation level for the enterprise. Example: if a software update was published with a factory automation level of allow automatic download but install manually, a CMS with global automation level setting at do not automatically download nor install would not download the update. In the same example, a CMS with a package-level automation level setting of allow automatic download and install would download but not install that package. The factory automation level setting cannot be made 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 package automation 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): Allow automatic download and install Allow automatic download but install manually Do not automatically download nor install Package Automation Levels are configurable and enable the Customer to restrict the application of updates to a specific package. Package Automation Levels override Global Automation Levels unless set to Use Global Automation Levels. The Package Automation Levels are: Use Global Automation Levels Allow automatic download and install Allow automatic download but install manually Do not automatically download nor install Understanding User Automation Levels User Automation Levels resolve to either the Global Automation Level or the Package Automation Level applied to an individual package. The User Automation Level is compared against the Factory Automation Level to determine the Effective Automation Level, which ultimately affects the package status and actions. Global Automation Level Package Automation Level User Automation Level Package A Allow automatic download and install Use Global Automation Levels Allow automatic download and install Package B Allow automatic download and install Do not automatically download nor install Do not automatically download nor install Package C Allow automatic download and install Allow automatic download but install manually Allow automatic download but install manually Package D Allow automatic download and install Allow automatic download and install Allow automatic download and install 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. Initializing the HP Remote Support Software Manager Software Manager 89

90 The Factory Automation Level only takes precedence over the User Automation Level if it is more restrictive than the user automation level. The available Factory Automation Levels are: Allow automatic download and install Allow automatic download but install manually Do not automatically download nor install 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: Allow automatic download and install Allow automatic download but install manually Do not automatically download nor install Factory Automation Level User Automation Level Effective Automation Level Package A Allow automatic download and install Do not automatically download or install Do not automatically download or install Package B Allow automatic download and install Allow automatic download and install Allow automatic download and install Package C Do not automatically download or install Allow automatic download but install manually Do not automatically download or install Package D Allow automatic download and install Allow automatic download and install Allow automatic download and install Package E Allow automatic download and install Do not automatically download or install Do not automatically download or install Package F Do not automatically download or install Allow automatic download and install Do not automatically download or install Package G Allow automatic download and install Allow automatic download and install Allow automatic download and install Modifying Automation Levels in the Software Manager The following section explains how to modify the Automation levels for both Global Preferences and Package Preferences. To modify Global Automation levels: In the Remote Support Software Manager Application, select Options >Preferences. The Global Preferences window is displayed. 90 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

91 In the Global Automation Level section If you select Automatic Install to activate automatic download and install of packages, you will not be prompted for download or install activities. If you select Automatic Download to activate automatic download only, installations must be done 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 of the available packages. NOTE: You may mouse-over the Package Name to get more information about that package. 2. To restrict the application of updates for a specific package, select Preferences in the Actions column of the particular package. The Package Preferences window is displayed. Initializing the HP Remote Support Software Manager Software Manager 91

92 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 allowed to 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 for updates of that particular package. If the schedule is set during an open Global Update Window, the update will be automatic. If the schedule is set during a time that the Global Update Window is closed, the update attempt will be queued until such time as a Global Update Window opens. The Package Update Schedule is 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)] 92 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

93 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 determined by 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 that time range. 3. In the On these days of the week row, select the day(s) of the week that you want to allow the download and installation as selected in the previous step. 4. Click Submit. The Form Submission window is displayed, confirming the details of the global preferences update that you selected. Modifying Package Update Scheduling Package Scheduling enables restrictions of when downloads and installations occur per package. The defaults for each package are specific to the Factory Scheduling Settings. Once you have modified a package s scheduling settings, the Factory Scheduling Settings are lost. If not modified, the Factory scheduling defaults are preserved. To modify the Package Scheduled settings levels: 1. In the Remote Support Software Manager, select Packages. The Packages window is displayed, with details of the available packages. Initializing the HP Remote Support Software Manager Software Manager 93

94 2. To modify a specific package schedule, select Preferences in the Actions column of the particular package. 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 point of time. b. Select Daily and specify whether you want the updates to occur Everyday of the week or only on 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 down menu 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 down menu. 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 different columns in the Packages window and how they interact with each other. While, the configuration of RSSWM 94 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

95 is detailed in this document, it is important to consult the full HP Service Essentials Remote Support Pack documentation set to fully understand which packages you should install and maintain for your business needs. The Packages Column The Packages Column displays the name of a software package available from HP. You may mouse-over a package listed in the column to see a description of that particular package. The Effective Automation Level Due to the complexity of the automation levels and package availability, it is important to understand how the automation level affects behavior of updates, which in turn affects the status of packages on the CMS. As the status of packages available from HP changes, so do the actions available for those packages. The change is dependent on each package s Effective Automation Level. Download Size The Download Size column communicate non-programmatic information that is set by the creator(s) of a particular software package. These entries are strictly informational and have no impact on the operations of RSSWM. CMS Installation Proposal The CMS Installation Proposal column indicates whether or not the package is necessary for Remote Support Monitoring. The field may include any of the following entries: Compulsory Required for Remote Support functionality or is a dependency for another component Optional Not required for Remote Support Reboot The reboot column indicates whether or not the package installation will require the CMS to reboot. 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. Initializing the HP Remote Support Software Manager Software Manager 95

96 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 installed on 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 updates are 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 resets the package automation level to manual. If you do not want that package installed on the CMS, then do 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 addresses with semi-colons. By default, this line is left blank. If you want this CMS included in HP internal reports for a specific HP engineer, add his/her address to this field. To configure reporting: 1. In the Remote Support Software Manager, select Contacts. The Contacts window is displayed. 2. Select Enable for status and connectivity reporting. 3. In the HP Contact section, enter the address(es) of the HP contact(s) to whom the reports for this CMS is to be sent. 4. Test the connectivity with the Test Connectivity option in the Actions page. 5. Click Submit. The Form Submission displays. confirming the details of the HP Contact information that you 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 as they are published to HP s hosting Software Manager servers at the HP Support Center. If package options are checked, then notifications are sent to the specified Customer contact for that package update. If left unchecked, no notifications are sent. Additionally, you may enable reports for both the software state of the Remote Support Software Manager and connectivity reports for communication from the Remote Support Software Manager. You may enter one or more Customer contacts into the field to receive notifications about updates and reports for Remote Support Software Manager on your CMS. The types of 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, and update availability of supported software applications installed on the CMS. Failed CMS RSSWM Connectivity Alerts which notify you when the Remote Support Software Manager has lost connectivity from the CMS to the HP Support Center. The notification will inform you 96 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

97 of the last time the Remote Support Software Manager logged a successful Software configuration data collection from the HP Support Center. You may opt in or out of either notification at any time by selecting or disabling the option and submitting your preferences. See Understanding and Using the Actions Option for information about manually updating the 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 address(es) of the Customer contact(s) to which the notifications on the updates for the CMS are to be sent. 3. Select announcements and/or reports and click Submit. 4. The Form Submission window is displayed, confirming the details of the selection for notifications. Modifying Proxy Settings Proxy settings are configured to enable the Software Manager to function in conjunction with the Customers web 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 value automatically. 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 settings that you have submitted. Initializing the HP Remote Support Software Manager Software Manager 97

98 Modifying Bandwidth Settings Bandwidth settings allow the Customer to restrict how much bandwidth the Software Manager uses. The bandwidth 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, at a minimum, retaining the default bandwidth 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 click Submit. The Form Submission window is displayed, confirming the details of the bandwidth options that 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 package updates. If updates are available, the status will display in the Package window. If new packages are available they will be processed according to their effective automation levels, and if set for automatic update 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 Software Manager 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 (such as contact information) to the HP Support Center. While this task is performed daily, you may use this feature to do it immediately. 98 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

99 Removing or Reinstalling the Remote Support Software Manager The HP Remote Support Software Manager has its own uninstall software. However, before removing the RSSWM application, you should remove the applications (Remote Support Common Components, OSEM, and Remotes Support Client software) that were installed using HP Remote Support Software Manager. To uninstall the all of the Service Essentials Remote Support Pack components, including Software Manager, from the CMS, complete the following steps: 1. From the Packages window in RSSWM, select Remove for each of the individual applications, following the prompts to remove each application from the CMS. 2. Select Start > Programs > Hewlett-Packard > Remote Support Software Manager Uninstall. Initializing the HP Remote Support Software Manager Software Manager 99

100 NOTE: Should you receive the following alert from Remote Software Manager, you may select no provided you followed Step One above. 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 RSSWM application must be reinstalled by rerunning the HP SIM installer (you do not necessarily need to reinstall HP SIM). If there is a hardware or operating system failure, the RSSWM application would also require reinstallation along with HP SIM. 100 Initializing the Remote Support Software Manager on the Central Management Server (CMS)

101 8 Migrating Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 4.2 NOTE: To migrate from Insight Manager 7 Service Pack 2.3 to HP Systems Insight Manager 5.0, Insight Manager 7 Service Pack 2.3 must be upgraded to HP SIM 4.2 first. After this initial upgrade, follow the procedure to upgrade HP SIM 4.2 to 5.0. See Chapter 9 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 HP Systems Insight Manager. The Data Migration Tool exports user-defined data from Insight Manager 7 by extracting it and storing the information in a portable format. The Data Migration Tool then imports that user-defined Insight Manager 7 data into HP Systems Insight Manager. The migration process transfers custom 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. If you are running a version of Insight Manager 7 earlier than Insight Manager 7 SP2.3, upgrade to Insight Manager 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 will enable you to upgrade to Insight Manager 7 SP2.3. See the Insight Manager 7 User's Guide for information on 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 hpsim/infolibrary.html for more in-depth detail on this process. Your system must also meet the operating system and SQL/SQL Server 2005 Express Edition requirements listed in Chapter 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 it is detected on your system, a migration utility for transferring data specific to it will also be launched. Types of migration There 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 part of the in-place migration process, Insight Manager 7 is disabled and can only be re-enabled by uninstalling HP Systems Insight Manager and manually re-enabling Insight Manager 7. In-place migration preserves user-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

102 has been exported and requires you to import the Insight Manager 7 and the Performance Management Pack migration data files to your new HP Systems Insight Manager server. Remote migration preserves user-defined data except the Insight Manager 7 Server certificate. Performing an in-place migration 1. 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 the 7.20 HP Management CD or by downloading the HP Systems Insight Manager 4.2 software. To download the software, go to 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 Manager 7 server. The HP Systems Insight Manager Welcome screen appears. The Welcome screen displays links 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 Performance Management Pack that was installed with Insight Manager 7 is detected on your system, the Performance 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 you are running Insight Manager 7 SP2.3 or later and automatically launches the HP Systems Insight Manager 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:\Program Files\HP\Systems Insight 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 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 for details. The background setup screen shows that pre-installation is Done and the installation is now In Progress. 2. Click Finish. The background setup screen shows that installation is Done and the post-installation is now In Progress. The import of Insight Manager 7 and the Performance Management Pack data has automatically begun. After all the HP Systems Insight Manager components have been installed, the Insight Manager 7 Data Migration 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 Migration Tool\user-data.dmt. 4. Click Next to start the Data Import. The process might take more than an hour depending on the amount of user-defined data and the configuration of the HP Systems Insight Manager. A status window shows the progress. 5. When data import completes, click Next. A message appears, stating that you must log in to HP Systems Insight 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

103 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 Systems Insight 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 software from and selecting Download or through the 7.20 HP Management CD. b. Start the migration process by launching setup.exe from the download package or from the Management CD. Select Products>HP Systems Insight Manager>Install. The HP Systems Insight Manager Welcome screen appears. The Welcome screen displays links 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 Performance Management Pack that was installed with Insight Manager 7 is detected on your system, the Performance 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 you are running Insight Manager 7 SP2.3 or later and automatically launches the HP Systems Insight Manager 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 Insight Manager Data Migration Tool displays an option to upgrade to Insight Manager 7 SP2.3. Select this 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 Systems Insight 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\Systems Insight 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 and instructs you to copy the export file to the server on which HP Systems Insight Manager will be installed. 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 background setup 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 Migration Tool\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 it can be accessed from the new HP Systems Insight Manager 4.2 server. The Performance Management Pack Data Migration Tool installation directory is usually c:\program Files\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

104 Manager>Install to start the HP Systems Insight Manager components installation. The background setup 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 HP Systems Insight Manager components. See Chapter 3 Installing HP SIM on the Central Management Server (CMS) for the first time for details. p. Click Finish when the installation is complete to close the HP Systems Insight Manager Installer window. The background set up screen shows installation is Done and post-installation is Not Done. 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, launch dmtshell.exe from the download package or from the Management CD on HP Systems Insight Manager 4.2 server. The background setup screen will not display. The Insight Manager 7 Data Migration Tool dialog screen automatically appears. b. Click Next. c. Specify the location of the user-data.dmt file as noted during the export process 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 Insight Manager. A status bar shows the progress. g. Click OK. h. Click Finish. 3. If a migration file for the Performance Management Pack was created, launch pmpdmt.exe to import the Performance Management Pack data. Follow the screens to completion, pointing to the location of the pmp.jar file as noted during the export process. 4. If the Performance Management Pack 2.1 server licenses/logged data is migrated and after HP Performance Management Pack 3.0 is installed, launch pmpshell.exe to import the Performance Management Pack 2.1 server licenses/logged data. Follow the screens to completion, pointing to the PMP 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

105 9 Upgrading HP Systems Insight Manager from 4.x or later HP SIM supports upgrading from HP SIM 4.0, 4.1, 4.2 to the current version HP SIM. This chapter provides the steps to upgrading from HP SIM 4.x to HP SIM 5.x. NOTE: line. The "\" at the end of each command line indicates that the rest of the command is on the next NOTE: Before beginning the HP SIM upgrade, verify that your user name and password to access to the database are valid. Upgrading from HP SIM 4.x or later 1. 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 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 following steps: a. Select Start Settings Panel Add/Remove Programs. b. Select HP Instant Support Enterprise Edition Client from the list of installed programs, then click Change/Remove. 3. If you have an Oracle database, install the Oracle JDBC driver, version or newer. See the Oracle documentation, or visit the Oracle website at for 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/lib directories and remove it from any locations where it is found. c. Download the new driver from the Oracle website at 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 SIM, and on the upper-left of the page under 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 HP Management CD, place the CD in the CD-ROM drive. The CD has an autorun feature that launches a license agreement. Agree to the license agreement, and click the Products tab. Click Install under HP SIM to launch the Installer. Or click the Products tab, click Explore 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 examines this system for local instances of Oracle, MSDE or SQL/SQL Server 2005 Express Edition. Note: Click the drop-down selection box in the upper-right corner of any dialog box to view the HP SIM Installation and Configuration Guide, Readme or Release Notes. Upgrading from HP SIM 4.x or later 105

106 5. Click Next. The System Inspection window appears. The system is inspected for a previous version of HP SIM and/or a local database. After the system inspection is complete, the Database Configuration window appears. 106 Upgrading HP Systems Insight Manager from 4.x or later

107 6. For HP SIM 5.2 and later, SQL Server 2005 Express Edition replaces MSDE. When HP SIM is upgraded on a system that has an MSDE database installed by a previous version of HP SIM or an HP SIM partner, the MSDE database is detected and is migrated to the SQL Server 2005 Express Edition database. The original MSDE database is not altered and still remains on the system untouched. If you are upgrading HP SIM on a system that already has SQL Server, SQL Server 2005 Express Edition, or Oracle installed, the database is detected and you can create a new instance and configure HP SIM to use that instance. If you are upgrade HP SIM on a system that uses a remotely installed database, the Database Configuration page appears as shown below. The database information of the existing HP SIM install is pre-populated. All information except for the user account cannot be edited. Provide the correct password for the existing account or provide the credentials for another user account with administrative rights and database access. The installation tests for the administrative rights. Click Next to proceed. Select from the following database options: Install and use SQL Express. This option enables you to install and configure HP SIM to use SQL Server 2005 Express Edition. To install and use SQL Server 2005 Express Edition: 1. From the Database Configuration window, select Install and Use SQL Express. 2. In the Username field, the installing user account appears and can be edited. The account specified must be the user name for the database server. 3. In the Password field, enter the password for the database server. 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 initialization fails. 4. In the Domain field, enter the domain name for the database server. 5. Click Next. A dialog box appears indicating files are being extracted. After the files are extracted, a new dialog box appears indicating SQL Server 2005 Express Edition is being Upgrading from HP SIM 4.x or later 107

108 installed. After SQL Server 2005 Express Edition is installed, the Select Installation Type window appears. Use SQL/SQL Express. This option is applicable if you have SQL Server or SQL Server 2005 Express Edition installed and you want to configure HP SIM to use it. To use SQL or SQL Server 2005 Express Edition: 1. From the Database Configuration window, select Use SQL/SQL Express. 2. In the Username field, the installing user account appears and can be edited. The account specified must be the user name for the database server. 3. In the Password field, enter the password for the database server. 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 initialization fails. 4. In the Domain field, enter the domain name for the database server. 5. Click Next. The Select Installation Type window appears. Use Oracle. This option is applicable if you have Oracle installed and you want to configure HP SIM to use it. To use Oracle: 1. From the Database Configuration window, select Use Oracle. 2. The Oracle database with Unicode (AL32UTF8) as the character set must be created before installing HP SIM. An Oracle user with DatabaseAdministrator (DBA) privileges must be created in this database for the exclusive use by HP Systems Insight Manager. HP SIM must be installed in an empty Oracle database schema. The thin client.jar file must be copied on to the system, and its location must be specified during installation. 3. In the Username field, enter the Oracle user name that has been assigned the DBA role. Note: An Oracle user name cannot contain a backslash (\) or a forward slash (/). 4. In the Password field, enter the password for the user name specified. 5. In the Host field, enter the name of the remote or local server where Oracle is installed. An IP address may also be used. 6. Under Instance name in the Database field, enter the name of the database created on Oracle for the use of HP SIM. 7. In the Port field, the default 1521 appears but can be edited. 8. In the JarFile field, enter the full path to the.jar file or click Browse and navigate to the correct location. This path must be accessible through the file system on the CMS. The installation copies the file to the correct location. 9. In the Host field, the local host name appears and can only be edited if you are performing a fresh install. 10. Click Next. The Select Installation Type window appears. Note: If an HP ProLiant Essentials Vulnerability and Patch Management Pack (VPM) MSDE database exists (within the HP SIM database instance or located on a database instance created by VPM), it is upgraded to SQL Server 2005 Express Edition. If the VPM database upgrade fails, a message displays indicating Failed to Upgrade VPM Database to SQL Express, but the HP SIM installation continues. 7. When the Select Installation Type window appears, select Typical to install the included components with minimal user interaction listed under the Available Components for Install or select Custom to select the individual components under the Available Components for Install and configure them during installation. 108 Upgrading HP Systems Insight Manager from 4.x or later

109 Available components for install System Management Homepage OpenSSH Services 4.3p2 WMI Mapper HP Systems Insight Manager HP Version Control Repository Manager Typical installation Included Included Included Included Included Custom installation Included Optional Optional Included Optional Typical upgrade Note: If a component is not listed as being available for installation on the CMS, then the HP SIM install shell has determined one of the following: The installation prerequisites for the component have not been met. The same or 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 SIM install shell and it supports an in-place upgrade, it appears in the component list. 1. Typical upgrades all the components which are marked included under the Available Components for Install. Click Next, the Service Account Credentials window appears. You must use credentials for an administrative account. 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 "In Progress" beside the component's name. After the component has installed, it states Installed Successfully. 4. After all of the components are installed, click Next, the Install Complete window appears. You are given the option to reboot. The following message appears: For this upgrade install, HP recommends that you configure the System Management Homepage to use operating system authentication for HP Version Control Agent access to Version Control Repository Manager, and then re-configure the servers running HP Version Control 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 at 5. Click Finish to allow the system to reboot. This completes the typical upgrade process. See "Next steps" for more information. Custom upgrade Note: For more information regarding where the System Management Homepage default settings are stored during a Typical installation and how to change them, see the System Management Homepage Installation Guide at documentation.html. 1. 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, the component is deemed a mandatory component and cannot be cleared. The amount of required disk space 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 to the installing account credentials. Enter the password for this account. You can also provide the credentials for a different administrative account. 3. Click Next. The Summary window appears. Typical upgrade 109

110 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 guides you 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, the installation 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. The group 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 following access types: Select Anonymous Access to enable anonymous access to unsecured pages. Select Local Access Anonymous or Local Access Administrator to set up the System Management Homepage to automatically grant local IP addresses at the selected access level. Caution: Selecting Local Access with Administrator privileges provides any users with access to 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 i. Select Trust By Certificate, and click Next. The Trusted Certificates window appears. The Trusted Certificates window allows trusted certificate files to be added to the Trusted Certificate List. 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 in the file name field, an error message appears, indicating the file does not exist. Click OK to select another file, or click Open to add the file to the Trusted Certificate List. The Trusted Certificate List appears. Click Next. or Note: If you click Next without adding any certificates to the list, and no certificates exist from a previous installation, a message appears, indicating that if you do not specify any trusted certificates, HP SIM cannot access the HP Insight Management Agent on this system. Click OK if you do not want HP SIM to access the Insight Management Agent on this system, or click Cancel to close the window and add the trusted certificates to the 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. This mode is the strongest method of security because it requires certificate data and verifies the digital signature before enabling access. 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 110 Upgrading HP Systems Insight Manager from 4.x or later

111 List, or click Cancel if you do not want to add it to the Trusted Certificate List. The Trusted 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 certificate is removed. v. From the IP Binding window, select the IP Binding checkbox if you would like to bind to 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 address ranges. Click Next, and the Summary Panel appears. Trust By Name i. Select Trust By Name. Click Next. The Trusted Server window appears. Enter the names of the servers you want to trust. ii. iii. iv. Note: Although the Trust By Name mode is a slightly stronger method of security than the Trust All mode, it still leaves your system vulnerable to security attacks. The Trust By Name mode sets up the System Management Homepage to only accept certain requests 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 secure network, 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 the wrong system. This option does not verify anything other than the HP SIM server name submitted. Note: The server name cannot contain the following characters: ~! # $ % ^ & * ( ) + = " : ' < >?, ; 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 message appears, indicating that if you do not specify any trusted server names, HP SIM cannot access the Insight Management Agent on this system. Click OK to proceed without trusting any systems, or click Cancel to close the window and add server names to the list. Note: To delete a certificate, select the certificate and click Delete. The selected certificate is removed. From the IP Binding window, select the IP Binding checkbox if you would like to bind to IP addresses that match a specific subnet and mask. Click Next. 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 i. Select Trust All. Click Next. The IP Binding window appears. 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 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 everyone in 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 might not be able to connect to the System Management Homepage. The IP Restricted Logins window appears. The IP Restricted Logins window enables you to select specific IP addresses or IP address ranges to include or exclude from gaining login access. Although optional, the System Management Homepage can restrict login access based on the IP addresses of the machine attempting to gain access. Custom upgrade 111

112 iii. iv. 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 ranges to grant login access permission. If there are IP addresses in the Inclusion list, then only those IP addresses are enabled for login privileges. If there are no IP addresses in the Inclusion list, then login privileges are permitted to all IP addresses that are not in the Exclusion 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. In the Include field, enter a beginning IP address to which you want to grant login access. 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 are granted login access. Click Add. The IP address or IP address range is added to the Exclusion 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 appears indicating the IP address is invalid. Click OK. Enter a valid IP address or IP address range, 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 login access. v. In theto field, enter an ending IP address to which you want to deny login access. All IP addresses that fall between the beginning and ending IP addresses are 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 address range, 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 will be marked as disabled. Do you want to proceed without adding any IP Address restrictions? If you click OK, the IP Restricted Login option on the IP Restricted Login window is cleared. The Summary Panel appears. The Summary Panel lists the location where the System Management Homepage is installed, the amount of space the installation requires, and the summary of 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 System Management 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 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 these fields 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 Windows XP or Windows 2003 system. If you are installing on a Windows 2000 system, the OpenSSH Service runs as "local system" and does not ask for credentials. c. Click Install to continue with the installation. 112 Upgrading HP Systems Insight Manager from 4.x or later

113 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 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. Click Next. 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 change the destination location using Browse. Click OK. Click Next. The Ready to Install window appears. 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 allow remote access and activation by everyone and anonymous users. See the HP SIM Readme at /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. b. Select or enter a different folder name using Browse. Click Next. The Ready to Install window appears. Custom upgrade 113

114 c. Click Install. The Install Progress window appears. d. Click Finish when the installation is complete to close the HP Systems Insight Manager Installer window. 114 Upgrading HP Systems Insight Manager from 4.x or later

115 e. After the HP SIM installation is complete, the Remote Support Software Manager; window appears. The configuration of the ISEE_CMS_SWMAGENT completes automatically. This process provides the files needed so that you can access the Service Essentials Remote Support Pack application 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 for configuration instructions. 9. Install the HP Version Control Repository Manager: a. When the HP Version Control Repository Manager Setup window appears, click Install. The HP Version Control Repository Manager Setup Repository Directory window appears. b. Select the directory from which HP Version Control Repository Manager will retrieve support pack information 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 Update window appears. c. Select the Enable Automatic Update checkbox to enable automatic downloading of HP ProLiant Support 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 Repository Manager, warning appears: "At least one HP Version Control Agent must be configured to use the HP Version Control Repository Manager." If none are configured, verify the HP Version Control Agent settings to ensure proper operation of the automatic update feature. Click OK. e. Click Close. 10. The Status window appears again, after all components have been installed, they will have an installed status. Click Next. 11. 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 truncated name 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 truncated host name\administrator. To log in, use the original host name in the Domain field on the Sign in page. Custom upgrade 115

116 Silent upgrade Upgrading 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. If upgrading HP SIM from the web, then after extracting the installation program, edit the silent.xml file and launch the setup in Silent mode. The silent.xml file contains the parameters for the upgrade process. The option to perform a Silent upgrade is available through a command line installation. A silent install occurs 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 installs HP SIM server account and database account respectively. The install takes the existing installation locations of HP SIM and partner components. Database information: Set <installsqlexpr>. In the upgrade mode this option is ignored; the installer does not install SQL Server 2005 Express Edition on the local server even if set true. The database information of the existing install is 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 an oracle 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 <hpsiminstalllocation> 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 partner components. 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> 116 Upgrading HP Systems Insight Manager from 4.x or later

117 is set to false. IMPORTANT: For a Silent upgrade, the service or database user name containing special characters, such as: &, <, &, <, >, ', " must be escaped appropriately as below in the silent.xml file: & & < < > > &apos; ' " " Next steps 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 and silentstatus.xml files. Both files are created in the root of the system drive. After upgrading to HP SIM 5.2, sign in to HP SIM, and run the Daily Device Identification task to ensure that all 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. Next steps 117

118 10 Uninstalling HP Systems Insight Manager Uninstalling HP Systems Insight Manager from a Windows system From the control panel, use the Add/Remove Programs feature in Windows, and complete the following steps 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 reinstall HP 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. This window lists some of the installed components each with a checkbox. The components listed for uninstall include: OpenSSH Services 4.3p2. 2. Click Next. If you want to cancel the uninstallation, click Cancel. Note: The components listed in the HP Systems Insight Manager Component Uninstall window can 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 be uninstalled only from the Add/Remove Program in the Control Panel. 3. Click OK to uninstall. The HP SIM status check is complete. 4. 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 118

119 11 Using the graphical user interface HP Systems Insight Manager provides a browser-based GUI. Accessing the GUI The graphical user interface (GUI) can be accessed from with any network client that is running a supported web browser. Required web browsers For Windows: Microsoft Internet Explorer 6 with Service Pack 2 or later See the following note about the required security options. Firefox 1.5 or later Note: For all Windows Internet Explorer browsers, you must have the SSL 3.0 or TLS 1.0 browser security options enabled for HP Systems Insight Manager to work properly. For HP-UX: Firefox 1.5 or later For Linux: To download, refer to Firefox 1.5 or later Security Alert in Internet Explorer When you browse to an HP SIM server for the first time using either IE6 or IE7, an SSL certificate warning is 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 of HP 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 this website. You need to proceed in both cases. The same level of security exists whether you are using IE6 or IE7, but IE7's warning message uses stronger wording. Graphical user interface features This section describes the GUI features. The following figure is a sample screen shot of the GUI. Accessing the GUI 119

120 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 displays the 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 customized for your environment. If you do not need to view this panel at all times, you can collapse it by clicking the minus sign-in the top right corner of the panel. To expand the panel, click the plus sign. If the System 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 large window 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 common system 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 appears listing systems that begin with the text you are entering. You can select from the dropdown list or continue to enter the information. See the HP Systems Insight Manager 5.2 User Guide at h18013.www1.hp.com/products/servers/management/hpsim/infolibrary.html for information about search criteria. If you do not need to view this panel at all times, you can collapse it by clicking the minus sign ( ) in the top right corner of the panel. To expand the panel, click the plus sign ( ). 4. System and Event Collections panel System and event collections enable you to view all known systems and 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.2 User Guide at management/hpsim/infolibrary.html for information about customizing and creating new collections. 5. Menus The HP SIM menus provide access to tools, logs, software options, and online help. The Options menu is primarily for users who administer the HP SIM software. If you lack authorization to use 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 displaying in the workspace. This area contains the Home page when you sign-in to HP SIM. By default, the introductory page is the Home page. The introductory page provides information and tips about HP SIM and links to frequently used features. You can customize HP SIM to display a different page as the Home page. See Customizing the Home Page for information about selecting a different introductory page. 120 Using the graphical user interface