HP

HP Systems Insight Manager Technical Reference Guide

English
  Discovery and Identification  |  Configuring Automatic Discovery  |  System Types   

System Types

»Table of Contents
»Index
»Notices
»Introduction
»Product Overview
»Getting Started
»Discovery and Identification
»Configuring Automatic Discovery
»Creating a New Discovery Task
»Editing a Discovery Task
»Disabling or Enabling a Discovery Task
»Deleting a Discovery Task
»Running a Discovery Task
System Types
»Configuring Discovery General Settings
»Managing Discovery Templates
»Adding a System Manually
»Managing Hosts Files
»Identification
»Manage System Types
»Users and Authorizations
»Networking and Security
»Monitoring Systems, Clusters, and Events
»Storage Integration
»Managing with Tasks
»Tools that Extend Management
»Partner Applications
»Reporting
»Administering Systems and Events
»Troubleshooting
»Reference Information
»Printable version
»Glossary
»Using Help

There are many different system types in HP Systems Insight Manager (HP SIM). All of these are available on the Discovery Filters page, except clusters, complex, racks, and enclosures.

  • Application. 

  • Cluster. A virtual computer usually made up of several servers clustered together with special software. Clusters are typically a fault-tolerant configuration. If a system is expected to be a cluster, but not identified as such, be sure that the agents are properly configured on the cluster nodes and that it is a supported cluster environment.

  • Complex. Computer systems that support multiple hardware partitions are referred to as a complex. For example, the HP Integrity Superdome class systems support multiple hardware partitions within a single complex.

  • Desktop. A small computer system typically located on users desks.

  • Enclosure. A chassis that can hold server blades and other types of blades. Many times, enclosures are not connected to a network but can provide power and cooling to the blades installed in them.

  • Environmental Monitor. A device that monitors the environment around a system, rack, or so on. It checks for temperature, smoke, and security.

  • Handheld. A Personal Digital Assistant (PDA) or small computer that fits in your hand.

  • Hub. Also called a repeater, a simple device typically used to extend the number of ports available on the network.

  • KVM switch. A keyboard, video, and mouse switch used to enable a single keyboard, video monitor, and mouse to be shared by multiple systems, which can be network enabled.

  • Management Processor. Usually a small firmware-based system that is embedded in a server or other server related hardware such as an enclosure. These systems are typically limited in their capabilities, one example would be the Integrated Lights-Out (iLO) card.

  • Notebook. A portable computer.

  • Partition. Certain systems and operating environments can be flexibly configured into partitions, each of which can run a separate instance of the operating system. Partitions provide protection that prevents software errors in one partition from interfering with another partition. Further, server systems that allow for hardware partitions can protect hardware errors from interfering with another partition.

  • Power Distribution Unit. Provides power to multiple systems in a rack, which can be remotely controlled to enable the powering on or off of a given system.

  • Power supply. A device that supplies power for servers on your network.

  • Printer. A device that is used to print on paper, which is typically attached to the network as well.

  • Rack. A non-addressable piece of hardware used to mount servers, enclosures, or networking equipment.

  • Resource Partition. 

  • Remote Access Device. A device to allow remote users to dial in through a phone line or over the LAN to an intranet.

  • Router. A networking device used to route network packets.

  • Server. A computer on a network that is dedicated to a particular purpose. For example, a file, print, or database server.

  • Shared Resource Domain. 

  • Storage Device. A disk drive array.

  • Switch. A network device, similar to a router but uses hardware-based switching technology to route packets in very fast manner.

  • Tape library. A tape library.

  • Thin client. A remote system connecting to a terminal server, a computer that has no disk or local storage and enables you to connect through terminal server packages to a central server or remote desktop.

  • Uninterruptible Power Supply (UPS). A battery backup for servers or other computers.

  • Unknown. In HP SIM, a status indicating that none of the built-in or System Type Manager (STM) based tasks could identify the system. However, some management protocol was detected on the system. Servers might be listed as Unknown for the following reasons:

    • You must be able to ping the system from the server where HP SIM is running. This can be accomplished from a command or terminal window, or from HP SIM selecting the unknown server and selecting menu pull-downs Diagnose and Ping and following the steps listed.

    • Community strings in HP SIM must match the ones used for the remote device. Be sure HP SIM and the systems are using the same community string. Note that community strings are case sensitive. From HP SIM, select OptionsProtocol Settings and select Global Protocol Settings or System Protocol Settings to make the changes.

    • Under Windows NT and Windows 2000, one community name on the system must be set to Read Create. Note that you do not have to use this community string in HP SIM (a community string set to Read is all that is required). The Management Agents connect to themselves using SNMP and require one string set to Read Create.

    • The HP SIM system must be allowed to make SNMP requests to the managed systems. Be sure the SNMP security settings are not preventing this. Under Windows NT and Windows 2000, the Allow SNMP packets from any host must be selected or the address of the HP SIM server must be in the list of allowed hosts.

    • If you are using IP-specific security, localhost (127.0.0.1) must also be allowed to make SNMP requests to the host. The localhost entry enables the Management Agents to connect to themselves using SNMP.

    • The ProLiant Management Agents must be installed and running properly on the ProLiant servers you are trying to manage. For Windows systems, check the Event Log to make absolutely sure they are running (you should see a few Agents started messages and no errors).

    • Routers and switches in the network must allow SNMP traffic to pass on ports 161, 162, and 7.

  • Unmanaged. A type indicating that a system that was found with an IP address, without any detected management protocols. If this is not the expected type, ensure the WBEM user name and password or the SNMP community name is correct. Install agents if possible (for example, for Windows, install the Initial ProLiant Support Pack). Refer to Version Control - Initial ProLiant Support Pack Install for information on installing the Initial ProLiant Support Pack.

  • Workstation. A higher-end personal computer system, sometimes used for graphics or other design work.