HP Systems Insight Manager 7.
© Copyright 2013 Hewlett-Packard Development Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Installation overview and requirements..........................................................5 First time install process overview................................................................................................5 Upgrade overview....................................................................................................................5 System requirements..................................................................................................................
Configuring task results...........................................................................................................47 8 Troubleshooting........................................................................................49 9 Support and other resources......................................................................52 Information to collect before contacting HP.................................................................................52 How to contact HP.......................
1 Installation overview and requirements This chapter provides an overview of the HP Systems Insight Manager installation process, and it identifies the system requirements for a Linux CMS, a managed system, and a network client. First time install process overview Perform these steps for a first time install of HP Systems Insight Manager on your CMS: 1. Install and configure the CMS. For details, see “Installing HP SIM on the CMS for the first time” (page 25). 2.
• Red Hat Enterprise Linux 5.
Hardware • • Any HP IA-32 AMD64 or EM64T system with the following configuration: ◦ Minimum: 1.5-GHz processor and 1 GB RAM ◦ Recommended: 2.4-GHz processor and 2 GB RAM Free disk space: ◦ 2 MB for CMS (/) ◦ 400 MB for the CMS and DTF agent (/opt) ◦ 500 MB minimum recommended for data (/var/opt) Software • General: ◦ OpenSSH version 1.0 or later ◦ ProLiant Support Pack for Linux 7.00 or later ◦ Oracle 10g R2 (10.2.0.
NOTE: On Linux, look for the entry 127.0.0.1 localhost, the local system IP address, and the system name in the /etc/hosts file. If they are not present, add the entries manually.
• Windows managed systems ◦ Windows Server 2008 R2 Standard, Server Core, SP1 ◦ Windows Server 2008 R2 Enterprise, Server Core, SP1 ◦ Windows Server 2008 Standard, Server Core, SP2 ◦ Windows Server 2008 Enterprise, Server Core, SP2 ◦ Windows Storage Server 2008 R2 Standard, SP1 ◦ Windows Storage Server 2008 R2 Enterprise, SP1 ◦ Windows Storage Server 2008 R2 Standard ◦ Windows Storage Server 2008 R2 Enterprise ◦ Windows Server 2008 Standard ◦ Windows Server 2008 Enterprise ◦ Windows S
◦ 10 ◦ Windows Server 2008 Enterprise (x64) ◦ Windows Server 2008 Datacenter, SP2 ◦ Windows Server 2008 Small Business Server, SP2 ◦ Windows Server 2008 Web Ed, SP2 ◦ Windows Server 2008 Itanium-based, SP2 ◦ Windows Storage Server 2008 ◦ Windows 2003 R2 Standard ◦ Windows 2003 R2 Standard (x64) ◦ Windows 2003 R2 Standard, SP2 ◦ Windows 2003 R2 Standard (x64), SP2 ◦ Windows 2003 R2 Enterprise ◦ Windows 2003 R2 Enterprise (x64) ◦ Windows 2003 R2 Enterprise, SP2 ◦ Windows 2003 R2 E
• • ◦ Windows 2003 Datacenter (IA64), SP2 ◦ Windows 2003 Web Edition SP1 ◦ Windows 2003 Web Edition SP2 ◦ Windows Small Business Server 2011 Standard ◦ Windows Small Business Server 2011 Essentials ◦ Windows 7 (Professional/Enterprise) ◦ Windows 7 (Professional/Enterprise) (x64) ◦ Windows Vista (Business/Enterprise) SP2 ◦ Windows Vista (Business/Enterprise) (x64) SP2 ◦ Windows Server 2012 Foundation ◦ Windows Server 2012 Essentials ◦ Windows Server 2012 Standard ◦ Windows Server 2
◦ Red Hat Enterprise Linux 6.2 x86 ◦ Red Hat Enterprise Linux 6.2 AMD64/EM64T ◦ Red Hat Enterprise Linux 6.1 IPF ◦ Red Hat Enterprise Linux 6.1 x86 ◦ Red Hat Enterprise Linux 6.1 AMD64/EM64T ◦ Red Hat Enterprise Linux 6 IPF ◦ Red Hat Enterprise Linux 6 x86 ◦ Red Hat Enterprise Linux 6 AMD64/EM64T ◦ Red Hat Enterprise Linux 5.9 IPF ◦ Red Hat Enterprise Linux 5.9 x86 ◦ Red Hat Enterprise Linux 5.9 AMD64/EM64T ◦ Red Hat Enterprise Linux 5.8 IPF ◦ Red Hat Enterprise Linux 5.
• ◦ SUSE Linux Enterprise 11 x86, SP2 ◦ SUSE Linux Enterprise 11 AMD64/EM64T, SP2 ◦ SUSE Linux Enterprise 11 IPF, SP1 ◦ SUSE Linux Enterprise 11 x86, SP1 ◦ SUSE Linux Enterprise 11 AMD64/EM64T, SP1 ◦ SUSE Linux Enterprise 10 IPF, SP4 ◦ SUSE Linux Enterprise 10 x86, SP4 ◦ SUSE Linux Enterprise 10 AMD64/EM64T, SP4 ◦ SUSE Linux Enterprise 10 IPF, SP3 ◦ SUSE Linux Enterprise 10 x86, SP3 ◦ SUSE Linux Enterprise 10 AMD64/EM64T, SP3 ◦ Debian 5.5 ◦ Ubuntu 10.40 LTS ◦ Ubuntu 12.
• • • ◦ Xen on RHEL 5 ◦ Xen on SLES 11 ◦ Xen on SLES 10 ◦ Integrity VM Windows (running guest OS Windows) ◦ Integrity VM Linux (running guest OS Linux) ◦ Integrity VM HP-UX (running guest OS HP-UX 11i v2) ◦ Integrity VM HP-UX (running guest OS HP-UX 11i v3) ◦ Microsoft Virtual Server 2005 R2 SP1 ◦ Microsoft Virtual Server 2005 R2 ◦ Microsoft Windows Server 2008 Hyper-V SP2 running guest Windows ◦ Microsoft Windows Server 2008 R2 Hyper-V SP1 running guest Windows ◦ Microsoft Windows
• ◦ Any HP PA-RISC system ◦ Any HP Itanium®-based system For Linux: ◦ Any HP ProLiant 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 5.9 p1 • HP ProLiant Support Pack baselined at v 9.2 • HP Support Pack for ProLiant (SPP) 2013.02.
Required web browsers • For Windows: ◦ Microsoft Internet Explorer 9 ◦ Microsoft Internet Explorer 8 ◦ Microsoft Internet Explorer 10 (Compatibility mode) ◦ Mozilla Firefox 3.x ◦ Mozilla Firefox 6.x ◦ Mozilla Firefox 9.x ◦ Mozilla Firefox 10.x ◦ Mozilla Firefox Extended Support Release 17.0 NOTE: 768. • • For optimum performance, the minimum resolution for the browser must be 1024 x For HP-UX: ◦ Mozilla Firefox 3.5 (3.5.09.00) ◦ Mozilla Firefox 3.6 ◦ Mozilla Firefox 3.
3. Select the following additional libraries under Base System: • Compatibility libraries • Under Hardware Monitoring Utilities, the following must be selected ◦ • lm_sensors-3.1.1-10.el6- 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 http://www.hp.com/go/hpsim/providers.
Hardware support Table 1 Supported HP c-Class platforms Product Models Minimum Software Management firmware version BladeSystem c3000 2.00 or later BladeSystem c3000 Tower Model 2.10 or later BladeSystem c7000 1.30 or later Table 2 Supported HP e-Class platforms Product Models Minimum Software Management firmware version ProLiant BL 10e Enclosure NA Table 3 Supported HP p-Class platforms Product Models Minimum Software Management firmware version ProLiant p-Class 1U Power Enclosure 2.
Table 4 Supported c-Class Servers (continued) Product Models Minimum BIOS — System ROM required Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required Operating Systems Supported1 Minimum ProLiant Support Pack (PSP) required Windows ProLiant BL465c G5 9/12/2008 1.70 Windows Server 2003 and 2008, Linux, Solaris, and VMWare ESX Server 8.15 ProLiant BL480c 5/1/2007 1.24 or later Windows and Linux 7.50 or later ProLiant BL490c G6 I21 2/23/09 1.75 Windows and Linux 8.
Table 4 Supported c-Class Servers (continued) Product Models Minimum BIOS — System ROM required Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required Operating Systems Supported1 Minimum ProLiant Support Pack (PSP) required Windows VMware Citrix XenServer 20 ProLiant BL620c G7 I25 7/9/2010 iLO 3 Microsoft Windows PSP 8.
Table 4 Supported c-Class Servers (continued) Product Models Minimum BIOS — System ROM required Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required Operating Systems Supported1 Minimum ProLiant Support Pack (PSP) required Windows Systems, Vmware, Citrix XenServer ProLiant BL465c G6 A13, 05/02/2011 ILO2 firmware 2.12 or later Microsoft Windows PSP 8.
1 2 For specific version of the operating systems, browse the ProLiant support matrix at http://h10018.www1.hp.com/ wwsolutions/index.html HP PC BL Enclosure Integrated Administrator Table 6 Supported e-Class Servers Product Models ProLiant BL 10e Minimum BIOS — System ROM required 2003.02.17 (C) Minimum Integrated Lights-Out (iLO) / iLO 2 / firmware version required 4.00 A2 7 Nov 2005 ProLiant BL 10e G2 2003.02.17 (C) 4.
1 For specific version of the operating systems, browse the ProLiant support matrix at http://h10018.www1.hp.com/ wwsolutions/index.html Table 8 Supported c-Class Interconnects/Switches Product Models Minimum Software Management firmware version Cisco Catalyst Blade Switch 3020 for HP c-Class Blade System 12.2(25)SEF1 Cisco Catalyst Blade Switch 3120G for HP IP Base IOS firmware package1 Cisco Catalyst Blade Switch 3120X for HP IP Base IOS firmware package1 Cisco MDS 9124e Fabric Switch 3.
Table 10 Supported p-Class Interconnects/Switches 24 Product Models Minimum Software Management firmware version Brocade 4GB SAN Switch for HP p-class Blade system v5.3.0d Mcdata 4GB SAN Switch for HP p-class Blade system 6.4.0.07.00 HP ProLiant BL p-Class Cisco Gigabit Ethernet Switch Module 12.2(44)SE HP ProLiant BL p-Class GbE Interconnect Switch Module 2.1.9 HP ProLiant BL p-Class GbE2 Interconnect Switch Module 3.2.3.
2 Installing HP SIM on the CMS for the first time Preparing the system Perform step 1 for a first time install of HP SIM on your CMS. 1. Install and configure the CMS. 2. Install and configure the required management software on the systems that will be managed by the CMS. For details, see “Setting up managed systems” (page 34). 3. Configure HP SIM for your environment. For more information, see “Configuring HP SIM” (page 37).
chmod +x HPSIM*.bin 6. Verify that the following required software dependencies are available on your system, and install any that are not already installed. a. Verify that SSH is installed by executing the following command: rpm -qa | grep ssh If SSH is not installed, the previous command does not return any results. Install SSH from your Linux operating system CD before continuing with the HP SIM installation. b.
NOTE: After installation is complete, log out of the operating system and then log back in to set all the correct file permissions and system environments. NOTE: HP Linux VCRM is automatically installed along with HP SIM and HP SMH. The installer will do the automatic Upgrade of Linux VCRM and HP SMH if lower version is found pre-installed. NOTE: Installing VCRM on Linux is only supported via HP SIM. To complete the initial set up of HP SIM refer to “After installing HP SIM” (page 28).
/etc/init.d/hpsmdb start • For SUSE Linux Enterprise Server 11 SP2 or later: a. View the status by executing the following command: /etc/init.d/hpsmdb status b. Configure hpsmdb to run during startup by executing the following command: chkconfig hpsmdb 345 c. If the status is unused in any version of Red Hat Linux or SUSE Linux, start the daemon by executing the following command: ◦ For SUSE Linux Enterprise Server 11 SP2 or later: /etc/init.
Password: Enter the password of your database. Oracle driver jar file: Enter the full location of the Oracle jar file. Force [N]: Press Enter. Or You can use the mxoracleconfig command with all parameters as shown below: mxoracleconfig -h hostname [-n port number] -d database name -u username -p password [-j driver jar file location] [-f ] -h Hostname Full DNS name or IP address of the Oracle server. -n Port number Port number to be used to connect to the oracle instance. Default port is 1521.
NOTE: After upgrading from a previous version of HP SIM, if you notice a pre-existing collection returning an unexpected result, and HP SIM has not been restarted since the upgrade, then stopping and restarting the HP SIM service should resolve this problem. 5.
6. Optional: Configure the system to send SNMP traps. NOTE: These steps might vary slightly, depending on your version of Linux. Refer to your Linux provider for details if these file paths and file names do not exist on your system. a. Verify that SNMP is installed by executing the following command: rpm -qa | grep snmp If SNMP is not installed, the previous command does not return a components list. Refer to your Linux provider for information on installing SNMP. b.
where CommunityName is the SNMP community string used by the CMS and IPaddress is the IP address of the CMS. iii. Save the changes to the file. To save and close this file using the vi editor, press the Esc key, enter :wq!, and press the Enter key. f. Start the SNMP daemon by executing the following command: /etc/init.d/snmpd start g. Start the hp-snmp-agents daemon if it is installed on your system: /etc/init.
NOTE: If the CMS is mapped to a linux VCRM, then you can deploy software and firmware tasks only to a linux target system and not to a windows target system. Next steps Install and configure the required Insight 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. For more information, see “Setting up managed systems” (page 34).
3 Setting up managed systems Perform step 2 to install and configure the required management software. 1. Install and configure the CMS. For more information, see “Installing HP SIM on the CMS for the first time” (page 25). 2. Install and configure the required Insight Management Agents on the systems that will be managed by the CMS. 3. Configure HP SIM for your environment. For more information, see “Configuring HP SIM” (page 37).
Configuring SMI-S providers Occasionally, it might be necessary to modify an SMI-S provider's port number or password. Use the provider 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.
• libXcursor-1.1.10-2.el6.i686.rpm • fontconfig-2.8.0-3.el6.i686.rpm • expat-2.0.1-9.1.el6.i686.rpm • expect-5.44.1.15-2.el6..rpm • zlib-1.2.3-25.el6.i686.rpm • libstdc++-4.4.4-13.el6.i686.rpm • net-snmp-5.5-27.el6..rpm In addition, the build directory for RPMs built from source has changed depending on the name of the user building them. Under RHEL 6, the directory is /root/rpmbuild/RPMS/, if the user is logged in as root.
4 Configuring HP SIM Perform step 3 to configure HP SIM for your environment. 1. Install and configure the CMS. For more information, see “Installing HP SIM on the CMS for the first time” (page 25). 2. Install and configure the required Insight Management Agents on the systems that will be managed by the CMS. For more information, see “Setting up managed systems” (page 34). 3. Configure HP SIM for your environment.
• Configure Managed Systems Configure managed systems as they are discovered, by configuring WBEM and WMI, SNMP, SSH access, and trust relationship. • WBEM/WMI Mapper Proxy To retrieve managed system information on Windows systems, enter the mapper proxy system host name and port number. NOTE: • This page only appears if you selected to manage a Windows operating system.
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.
2. Optional: Configure the system to send SNMP traps. NOTE: These steps might vary slightly, depending on your version of Linux. See your Linux provider for details if these file paths and file names do not exist on your system. a. Verify that SNMP is installed: rpm -qa | grep snmp If it is not installed, see your Linux provider for information on installing SNMP. b. Stop the hp-snmp-agents daemons on the platform where you are installing HP SIM using the following command: /etc/init.
5 Upgrading from HP SIM This chapter provides the steps to upgrade HP SIM 6.x and later. Before beginning the HP SIM upgrade, verify that your user name and password to access to the database are valid. When you perform and upgrade, HP SIM checks for a previous installation of HP SIM, stops HP SIM and all related services and daemons, overwrites or copies files to the appropriate locations on the CMS, and then restarts HP SIM and all related services.
c. d. Select the checkbox, save the changes, and then start the service. To start hpsmdb by using the command line, execute the following command: /etc/rc.d/init.d/hpsmdb start Or /etc/init.d/hpsmdb start • For SUSE Linux Enterprise Server 11 SP2 or later: a. View the status by executing the following command: /etc/init.d/hpsmdb status b. Configure hpsmdb to run during startup by executing the following command: chkconfig hpsmdb 345 c.
7. Complete the upgrade by restarting the HP SIM daemons using mxstop and mxstart. HP SIM is now installed and initialized on the CMS. To browse to HP SIM, start the HP SIM graphical user interface (GUI) using Firefox, or Internet Explorer at http://:280/. 8. After upgrading to HP SIM 6.x and above, sign in to HP SIM, and run the Daily Device Identification task to ensure that all your associations are updated correctly.
6 Uninstalling HP SIM Uninstalling HP SIM from a Linux system CAUTION: Removing HP SIM permanently deletes the information in the database unless you back it up before removing the software. Procedure 6 Removing HP SIM 1. Stop the HP SIM daemons: /opt/mx/bin/mxstop 2. Verify that the daemons are no longer running: ps -ef | grep mx If any of the HP SIM daemons are running, record the PID and kill the process: kill -9 pid where pid is the PID of the daemon. For example, kill -9 3456 3.
7 Configuration options Several configurable parameters in HP SIM that are not available from the GUI. These parameters can only be configured by editing a configuration file on the CMS. NOTE: All HP SIM parameters have been set to predefined values that are appropriate for most situations. These parameters should only be changed if you are experiencing issues with the default values. There are two main default locations where configuration files are stored.
Monitor time-out policy The monitor time-out policy keeps sessions alive, provided the user has a web browser window open displaying the Systems Insight Manager GUI. Closing the browser or navigating to another web page starts the timer for the time-out period. The default time-out period is 20 minutes. Users must use some other means to protect an unattended session from illegal use, such as password-protected screen savers.
Implementation Changes made to the log.properties file do not take effect until the log manager daemon or service is restarted. Restart the Systems Insight Manager service. CAUTION: The queue size should be changed only with extreme care. If the queue is set too high, the log manager consumes too much system memory. NOTE: When the Audit Log file reaches the maximum file size, the log is renamed with MX_LOGROLLFILEEXT extension and a new file is started.
Tools in this category have no task output, have task output that is saved outside of Systems Insight Manager, or have task results that are unlikely to be of long-term interest. Tasks for all other tools are considered long-term. Frequently scheduled tasks Task results can also be removed from the Task Results Page if a certain number of task results for a scheduled task accumulate. This setting defaults to 10 instances of a single task.
8 Troubleshooting Q Q Q Q Q & & & & & A A A A A 8.1 “Browser issues” 8.2 “GUI issues” 8.3 “Installation issues” 8.4 “Sign in issues” 8.5 “GUI issues” 8.1 Browser issues 8.8.1.1 Accessing some of the menu items on a Linux CMS causes the page to go blank. Solution: If using Firefox and this happens, click back on the displayed page, and the menus will be refreshed. 8.2 GUI issues 8.8.2.1 8.8.2.
Starting PostgreSQLpg_ctl: postmaster does not start...failed No PostgreSQL RPM Solution: Manually start the PostgreSQL service by performing the following steps: Procedure 9 Manually starting the PostgreSQL service 1. Navigate to the /etc/init.d directory and execute the following command: ./postgresql stop 2. 3. Log in as user postgres (su postgres). Execute the following command: postmaster -D /usr/local/pgsql/data The postmaster and PostgreSQL start. 4. 8.8.3.5 Run mxinitconfig -a.
4. Click OK. NOTE: By using IP addresses instead of names, you might encounter security alerts, if the name in the managed system certificate does not match the name in the link. The default certificate for managed systems uses the system name, not the IP address. Reason 2: For managed systems, the privacy policy setting in Internet Explorer 6.0 is blocking the authentication cookies from the managed systems. Solution 2A: (Recommended) Remove the systems from the Internet Zone.
9 Support and other resources Information to collect before contacting HP Be sure to have the following information available before you contact HP: • Software product name • Hardware product model number • Operating system type and version • Applicable error message • Third-party hardware and software • Technical support registration number – SAID (Service Agreement Identifier) How to contact HP Use the following methods to contact HP technical support: • In the United States, see the Customer
• If the question is related to HP Insight Remote Support (HP Insight RS), then HP SIM will be supported as it pertains to Insight RS with a Hardware Warranty or Hardware Contract • The customer purchases a HP SIM Care Pack (Part #: UR389E) Support includes one year of 24 x 7 HP Software Technical Support and Update Service. This service provides access to HP technical resources for assistance in resolving software implementation or operations problems.
Websites • HP Insight Control: http://www.hp.com/go/insightcontrol • Systems Insight Manager: http://www.hp.com/go/hpsim Typographic conventions This document uses the following typographical conventions: Table 12 Typographic conventions 54 Book title The title of a book. On the web, this can be a hyperlink to the book itself. Command A command name or command phrase, for example ls -a. Computer output Information displayed by the computer.
10 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, send any errors, suggestions, or comments to Documentation Feedback docsfeedback@hp.com. Include the document title and part number, version number, or the URL when submitting your feedback.
Glossary A administrative rights user A user who is authorized for the All Tools toolbox on all systems, including the Central Management Server. This type of user has been given special privileges to administer the HP Systems Insight Manager software. administrator A user who manages users, resource pools, and self-service requests through infrastructure orchestration console. agent A program that regularly gathers information or performs some other service without the user's immediate presence.
central processing unit polling rate The rate for how often the Cluster Monitor CPU Resource checks CPU utilization as reported by Insight Management Agents on monitored systems. certificate An electronic document that contains a subject's public key and identifying information about the subject. The certificate is signed by a certificate authority (CA) to bind the key and subject identification together. See also certificate authority.
critical status A state generated when HP Systems Insight Manager can no longer communicate with a managed system. custom tools Custom tools are tools that can be created by the user to run on the Central Management Server or on target systems. For example: • Remote tool A tool that runs on selected target systems. It might copy files to the target systems or run specific X-Window applications on the target systems. You can schedule this tool. • CMS tool A tool that runs on the CMS.
edit collection To modify existing collections to add or remove search criteria. enclosure A physical container for a set of server blades. It consists of a backplane that routes power and communication signals and additional hardware for cabling and thermal issues. It also hosts the CPU or server power supplies. event Information sent to certain users that something in the managed environment has changed. Events are generated from SNMP traps.
performance management, and workload management enable systems administrators to pick the value added software required to deliver complete lifecycle management of their hardware assets. HP Insight Control database The database that stores vital information about HP Systems Insight Manager, including users, systems, and toolboxes. HP Insight Control performance management A software solution that detects, analyzes, and explains hardware bottlenecks on HP ProLiant servers.
HyperText Transfer Protocol The underlying protocol used by the World Wide Web. I identification While discovery finds systems, identification attempts to determine what the system type is. In addition, it determines what management protocol a system supports, using credentials from the Global Protocol Settings page, and attempts to determine the operating system and version loaded, along with other basic attributes about the system. Finally, it determines if the system is associated with another system.
management protocol A set of protocols, such as WBEM, HTTP, or SNMP, used to establish communication with discovered systems. management scope A set of systems within the set of all discovered systems that HP Systems Insight Manager manages. management services A core set of capabilities such as automatic discovery, data collection, a central repository for system and event information, event management, basic notification, and secure access.
P ProLiant and Integrity Support Packs An ProLiant and Integrity Support Packs is a set of HP software components that have been bundled together by HP, and verified to work with a particular operating system. An ProLiant and Integrity Support Packs contains driver components, agent components, and application and utility components. All of these are verified to install together.
search criteria A set of variables (information) used to define a requested subset of information from the HP Systems Insight Manager database. Secure HTTP An extension to the HTTP protocol that supports sending data securely over the web. Secure Shell A program 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.
Single Sign On Permission granted to an authenticated user browsing to HP Systems Insight Manager to browse to any of the managed systems from within HP Systems Insight Manager without re-authenticating to the managed system. HP Systems Insight Manager is the initial point of authentication, and browsing to another managed system must be from within HP Systems Insight Manager. single-system aware A run type that does not support multi-system operations.
system health status This is aggregate status all of the status sources (which can be SNMP, WBEM, and HTTP) that are supported on a target system, with the most critical status being displayed. The following are the different system health statuses that can be displayed: • Critical HP Systems Insight Manager can no longer communicate with the system. The system was previously discovered but cannot be pinged.
number in a column is a hyperlink to a more detailed list of systems, which displays the systems that correspond to the number in the overview. system properties properties can be set for a single system or for multiple systems at the same time and include options such as system name, system type, system sub-type, operating system version, asset number, contact information, and whether or not the system properties can be changed or updated by the discovery process.
type The classification of a system, which identifies it as a standard system type. The system types are client, cluster, portable, printer, remote access device, repeater, router, server, switch, unknown, workstation, and other. U uncleared event status Events that have a Critical, Major, Minor, Normal, or Informational severity and have not been cleared or deleted from the database. Events can be cleared without being deleted from the database by using the Clear events menu option. • Critical.
Web Based Enterprise Management This industry initiative provides management of systems, networks, users, and applications across multiple vendor environments. WBEM simplifies system management, providing better access to software and hardware data that is readable by WBEM client applications. Web-Based Enterprise Services A tool suite that is aimed at preventing or reducing the downtime of a system. Web-launch aware A run type for tools that are launched in a web browser using a web server.
Index removing HP SIM, 44 system preparation, 25 A active time-out, 45 audit log configure, 46 C Central Management Server Linux system preparation, 25 central management server installing HP SIM on Linux, 26 requirements, 5 configuration audit log, 46 data collection CPU utilization, 45 lifetimes for Task Result entries, 47 managed system, 34 time-out policy, 45 configuration options, 45 configuring first time wizard, 37 HP Systems Insight Manager, 37 managed systems, 37 CPU utilization, 45 customization
upgrading HP SIM overview, 41 process, 41 71
