Managed systems, Management domain, Multiple-system aware – HP Systems Insight Manager User Manual

Page 650: Management agents, Management protocol, Manual discovery, Management, Agents, Multiple-system aware (msa), Information base (mib)

Advertising
background image

managed systems

Any system managed by HP SIM, such as servers, desktops, storage systems, and Remote Insight
Boards (RIBs).

management
agent

A daemon or process running on a managed system. It receives and executes requests from the
Central Management Server on the managed system.

management
domain

A collection of resources called managed systems that have been placed under the control of HP
SIM. Each Central Management Server is responsible for a management domain. The managed
systems can belong to more than one management domain.

Management HTTP
Server

An integrated piece of software used by the HP suite of HP Web-enabled System Management
Software to communicate over HTTP and HTTPS. It provides a uniform set of functionality and
security to HP Web-enabled System Management Software. This version is available in the ProLiant
Support Pack 7.10 or earlier.

Management
Information Base
(MIB)

The data specification for passing information using the SNMP protocol. An MIB is also a database
of managed objects accessed by network management protocols.

Management
Information Format
(MIF)

An ASCII text file in the DMI architecture that describes the manageable features and attributes
of a product. The DMI maintains this information in a MIF database and makes it available to
operating systems and management applications. The DMTF has specified MIF formats for a
variety of system types and peripheral systems.

management
instrumentation

Agents running on systems that provide management information for HTTP, DMI, or SNMP
protocols.

management LAN

A LAN dedicated to the communications necessary for managing systems. It is typically a moderate
bandwidth (10/100 BaseT) and secured through limited access.

management
protocol

A set of protocols, such as WBEM, HTTP, SNMP, or DMI, used to establish communication with
discovered systems.

management
scope

A set of systems within the set of all discovered systems that HP SIM 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. These
functions are used by add-ins from HP, a Management Solutions Partner, and HP SIM users.

management tasks

Procedures you set up to search systems or events.

manual discovery

Similar to automatic discovery, but rather than ping sweeps and events being used to find systems,
you manually add systems, either by IP address or name, using template of hosts files. Identification
runs on these systems. Manual discovery can be used to set a system type. However, if
identification determines the target is something different, the

found type is used.

manual discovery
techniques

Processes that enable you to bypass a full discovery for the following tasks:

Adding a single system


Editing the system

Creating or importing an HP SIM database hosts file

Creating or importing generic hosts files

Microsoft
Clustering Service
status page

A page that summarizes cluster status as defined by Microsoft Cluster Server and lists the status
and values of MSCS-defined cluster attributes. The Cluster Monitor uses color to display status
based on MSCS condition values (Normal, Degraded, Failed, and Other).

Minor status

Status information collected from the system that indicates one or more of the monitored subsystems
are not operating properly which is impacting the system. Action should be taken as soon as
possible to prevent further failure.

Monitor Tools
toolbox

A default toolbox that contains tools that display the state of managed systems but not tools that
change the state of managed systems.

multiple-system
aware (MSA)

A run type that supports multi-system operations. Tools with this run type operate on the target
systems using their own internal mechanisms instead of using the Distributed Task Facility. The
MSA run type uses the Distributed Task Facility to launch the tool on a single system before the
tool interacting with the other managed systems.

650 glossary

Advertising