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. The only warranties for HP products and services are set forth in the express
warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
Acknowledgments
Microsoft, Windows, Windows Server, Windows Vista, Windows NT, and Windows XP are U.S. registered trademarks of Microsoft Corporation.
Linux is a U.S. registered trademark of Linus Torvalds.
Publication history
The manual publication date and part number indicate its current edition. The publication date will change when a new edition is released. The
manual part number will change when extensive changes are made.
To ensure that you receive the latest edition, you should subscribe to the appropriate product support service. See your HP sales representative for
details.
Please direct comments regarding this guide to:
Hewlett-Packard Company
HP Systems Insight Manager Learning Products
20555 Tomball Parkway
Houston, Texas 77070
Or, use this web form to send us feedback:
http://docs.hp.com/assistance/feedback.html
Typographic conventions
find
(1)HP-UX manpage. In this example, “find” is the manpage name and “1” is the manpage section.
Book Title
Linked Title
http://www.hp.comA Web site address that is a hyperlink to the site.
CommandCommand name or qualified command phrase.
user inputCommands and other text that you type.
computer outputText displayed by the computer.
EnterThe name of a keyboard key. Note that Return and Enter both refer to the same key. A sequence such as Ctrl+A
termDefined use of an important word or phrase.
variableThe name of an environment variable, for example PATH or errno.
valueA value that you may replace in a command or function, or information in a display that represents several possible
<element>An element used in a markup language.
attrib=An attribute used in a markup language.
Title of a book or other document.
Title that is a hyperlink to a book or other document.
indicates that you must hold down the key labeled Ctrl while pressing the A key.
values.
Table of Contents
I Introduction...............................................................................................11
1 About this document.............................................................................12
User Guide.....................................................................................................................................12
Systems Insight Manager User Guide layout........................................................................................12
G-14New Command Line Tool parameter entry guidelines......................................................................153
H-1MIBs supported in Systems Insight Manager.....................................................................................155
10
Part I Introduction
11
1 About this document
User Guide
HP Systems Insight Manager provides this user guide to help you understand management features.
Systems Insight Manager User Guide layout
•IntroductionDescribes the features, basic concepts, and using the
Systems Insight Manager.
•Setting up Systems Insight ManagerDescribes how to set up Systems Insight Manager by explaining
requirements for systems to be managed by Systems Insight Manager, credentials, discovery, automatic
event handling, and users and
•Systems Insight Manager basic featuresDescribes Systems Insight Manager basic features, including
monitoring systems, clusters, and events, performing basic and advanced searches, editing system
properties, and basic reporting.
•Systems Insight Manager advanced featuresDescribes Systems Insight Manager advanced features,
including managing with
For information on Systems Insight Manager support and how to access related documentation, see Support
and other resources.
authorizations
collections
.
, advanced reporting, and creating custom tools.
graphical user interface
(GUI) in
User Guide12
2 Product overview
What's new in Systems Insight Manager 6.0
•ScalabilityHP Systems Insight Manager can mange up to 10,000 systems (up to 5,000 servers, with
additional 5,000 management processors, VMS, and so on) when using Windows 64-bit.
•ReportingSystems Insight Manager 6.0 introduces enhanced reporting including tables and graphs
for easier access to Systems Insight Manager data.
•MigrationNew migration tool to transfer settings from a Systems Insight Manager 5.3.x Central
Management Server (CMS) to an Systems Insight Manager 6.0 CMS, and from a Systems Insight
Manager 6.0 CMS to another Systems Insight Manager 6.0 CMS.
•Firmware updateFirmware update from Systems Insight Manager integrates with HP SUM and
provides agentless firmware upgrade for management processor and Onboard Administrator.
•Heterogeneous supportDiscovery and identification of non-HP systems through Systems Insight
Manager. The power cycle, power on, and power off commands are supported. Data collection support
is available for non-HP systems through Windows Management Instrumentation (WMI).
•Health statusMouseover of health status icons in system list shows which components are contributing
to the status, making it easier to identify the root cause of failures.
Systems Insight Manager features
•Automatic discoveryAutomatically discovers and identifies systems attached to the network. Use
discovery filters
•Health monitoringColored status icons enable you to see at a glance the operational health of your
systems, and quickly drill down to find the failing component if any are not ok.
•Fault management and event handlingSystems Insight Manager 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 e-mail or pager, , and enables automatic execution
of scripts or
Node Manager.
NOTE:Pager support is only for Windows-based
•InventoryPerforms comprehensive system data collection and enables users to quickly produce
detailed inventory reports for
into popular reporting packages.
•Consistent multisystem managementSystems Insight Manager 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.
•Role-based securityAllows effective delegation of management responsibilities by giving systems
administrators granular control over which management operations users can perform on selected
systems.
to prevent discovery of unwanted system types.
event
forwarding to enterprise platforms such as HP Operations Manager or HP Network
managed systems
Central Management Server (CMS)
. Save reports in multiple formats for easy incorporation
.
•Two user interfacesSystems Insight Manager provides the option of a browser-based GUI or a
command line interface
management processes.
•Customized toolsSimple Extensible Markup Language (XML) documents that allow you to integrate
off-the-shelf or custom command line and web-based applications or scripts into the Systems Insight
Manager user interface.
(CLI) that enables you to incorporate Systems Insight Manager into your existing
What's new in Systems Insight Manager 6.013
Basic concepts
Discovery and identification
Systems Insight Manager can automatically discover and identify systems attached to the network using
information from management protocols such as
Management Instrumentation (WMI), WBEM,
discovery tasks to limit discovery to specific network segments or IP address ranges, or to control the frequency
that each task runs. Use discovery filters to prevent discovery of unwanted system types.
Inventory
Simple Network Management Protocol
Secure Shell
(SSH), and
Secure Sockets Layer
(SNMP), Windows
(SSL). Create
Data collection
Systems Insight Manager collects various information such as system type and sub-type, supported protocols,
and available memory. You can choose to maintain only the most recent data, enabling you to run reports
or compare different systems using Snapshot Comparison. Or, you can store all data collected over time,
which enables use of Snapshot Comparison to view trends on a single system.
Status info
The following status icons are used in the status list columns to show status on different aspects of the managed
systems. For example, the MP column displays the status icon of the management processor if the system
has a management processor board installed.
Table 2-1 Status types
gathers data that can be used for reporting and to populate various fields in the user interface.
Status typeStatus icon
Critical
Major
Minor
Warning
Normal
Disabled
Unknown
For specifics, see:
•Hardware statusHealth status types
•Software statusSoftware status types
•Contract and warranty statusContract and Warranty status
•WBEM statusWBEM operational status
Reports
Systems Insight Manager performs comprehensive system data collection and enables you to quickly produce
detailed inventory reports for managed systems. Reports can be generated in Hyper Text Markup Language
(HTML), XML, or Comma Separated Value (CSV) format. Enhanced reports can be automatically generated
and e-mailed on a scheduled basis. The type of data collected depends on the management software (SNMP
agents or WBEM/WMI providers) that is installed.
Automatic event handling
Automatic event handling enables you to define an action that Systems Insight Manager performs when an
event is received. These actions can include running a program or script, forwarding the event to another
management system, clearing the event, or notifying a user through e-mail or pager.
14Product overview
Informational
Tools and tasks
Tools are actions you perform on the managed systems from within Systems Insight Manager's GUI or CLI.
Many tools ship with Systems Insight Manager, but you can also add your own custom tools. Tasks are
instances of running tools. To create a task, select
on) and then select the tool from the Systems Insight Manager menu. Tasks can be run immediately or
scheduled, and you can view task results by selecting Tools→View Task Results.
Tools can be run from the Systems Insight Manager menus and can be added to a Quick Launch list that is
available from many pages within Systems Insight Manager.
Collections
Collections are groups of systems and events that can be used for viewing information, or as a way to specify
the targets for a tool. They can be created through the Customize link in the System and Event Collections
panel either by selecting specific systems to be included, or by specifying attributes to be matched. Once
created, they are displayed in the System and Event Collections panel for quick access. Shared collections
can be seen by everyone logging into Systems Insight Manager. Private collections can only be seen by the
user who created them.
You can bind event collections and system collections together and use them either separately or together.
For example, after you define a collection of Security Events, you can easy look at those events on any
system collection, such as Security Events on All Servers or Security Events on My FinancialServers.
Conversely, you can choose a system collection, and view any set of events on those systems. For example,
you can easily select My FinancialServers and look at All Events, Sign-in Events, Security Events, or any other
event collection as it applies to that collection of systems.
target systems
(systems or events that the task will work
Users and Authorizations
Systems Insight Manager enables effective delegation of management responsibilities by giving system
administrators granular control over which users can perform specific management operations on specific
systems.
Signing in and using the graphical user interface
Systems Insight Manager provides a browser-based
•For Windows:
Microsoft Internet Explorer 7 or later•
•Firefox 3.0.10 or later
•For HP-UX:
Firefox 3.0.10 or later
To download, go to http://www.hp.com/go/firefox.
•For Linux:
Firefox 3.0.10 or later
NOTE:Browser settings:
For all Windows Internet Explorer browsers, you must have the SSL 3.0 or Transport Layer Security
•
(TLS) 1.0 browser security options enabled for Systems Insight Manager to work properly.
•To use automatic sign-in with Firefox, you must configure Firefox with a list of sites with automatic sign-in.
For more information, see
Initial setup
section of the Systems Insight Manager online help.
GUI
. Supported browsers include:
Security Alerts in Internet Explorer and Firefox
Because the Systems Insight Manager web server uses a self-signed SSL certificate (unless otherwise
configured), you will encounter a browser warning when browsing to the CMS. Firefox warns of an
Connection
measures to avoid repeatedly encountering those warnings. This applies to Systems Insight Manager, SMH,
Integrated Lights-Out (iLO), Onboard Administrator, and all web servers you browse to.
. Internet Explorer warns of a
Certificate Error
Untrusted
. Both browsers let you continue, but you can take
Signing in and using the graphical user interface15
Each time you receive an
exception to avoid seeing the warning again for that host. Note that if you browse to a single system using
its short host name, fully qualified Domain Name Service (FQDN), and IP address (for example, three different
ways), you must add three security exceptions.
With Internet Explorer, you must install the SSL certificate into the Trusted Root Certification Authorities
certificate store, but the browser will continue to warn you (by default) when details in the certificate do not
match (for example, browsing by short host name when the full host name is in the certificate). To avoid
certificate errors when names do not match, the following setting must be turned off: InternetExplorer→Advanced→Security→Warn about cer tificate address mismatch.
If you do not install the SSL certificate in Internet Explorer 8, these warnings appear for each pop-up window
that appears in Systems Insight Manager.
Automatically signing in
You can sign in to Systems Insight Manager using the same account with which you are logged in on your
desktop, bypassing the Systems Insight Manager sign-in page. If user groups are configured for Systems
Insight Manager, membership in these groups is accepted and treated the same as if you manually signed
in.
Configuring the CMS
•Systems Insight Manager must be running on a Windows CMS that is a member of a Windows domain.
The browsing system must be a member of the same domain.
•The Systems Insight Manager service account must be a domain account; local accounts can not be
used.
•The CMS must be registered with an SPN in the domain, which requires a domain administrator to
configure. From any system that is a member of the domain, the domain administrator can run the
setspn.exe utility from the Windows Support Tools. For example:
setspn -a HTTP/<cms_fqdn> <sim_service_account>
Where HTTP is in all capital letters,
is the domain account under which Systems Insight Manager service runs.
Untrusted Connection
<cms_fqdn>
warning in Firefox, you must add a
is the FQDN of the CMS, and
permanent
security
<sim_service_account>
IMPORTANT:Automatic sign-in fails if the SPN registered more than once. If you change the name
of the Systems Insight Manager service account, you must first delete the SPN associated with the old
service account name, and then register the new service account name:
NOTE:Local accounts cannot be used for Systems Insight Manager service account if automatic sign-in
is desired.
•The automatic sign-in feature must be enabled in Systems Insight Manager in the
globalsettings.props file. You can use the mxglobalsettings command, or directly modify
the file. Set the value for the
necessary.
Configuring the browser
•Supported in Internet Explorer 7 and Firefox. Internet Explorer 6 is not supported.
•The browsing system must be remote; browsing locally from the CMS does not perform automatic
sign-in.
•The browsing system and the CMS must be members of the same Windows domain.
•You must be logged in to the browsing system with a domain account that is configured as a user
account in Systems Insight Manager, or is a member of a user group configured in Systems Insight
Manager.
AutomaticSignIn
property to 1. Restarting Systems Insight Manager is not
16Product overview
Behavior
•There must be no proxy servers between the browser and the CMS. Use the proxy bypass list in the
browser, or use no proxy at all.
•The browser must be configured to support automatic sign-in.
Procedure 2-1 Configuring the browser in Internet Explorer
1.In Internet Explorer, enable Integrated Windows Authentication under Tools→Internet
Options→Advanced tab.
2.The CMS must be in the Local Intranet or Trusted Sites zone, which can be configured under the
Tools→Internet Options→Security tab.
3.(Optional) If the CMS is in the Internet Explorer Local Intranet zone, select Automatic Logon only in
Intranet zone.
4.(Optional) If the CMS is in the Internet Explorer Trusted Sites zone, select Automatic logon with current
user name and password.
Configuring the browser in Firefox:
Firefox must be configured with a list of sites (for example, the CMS) where automatic sign-in can be
performed, and should be restricted to local intranet sites. This list can be configured by entering
about:config in the Firefox address bar. From the list of Preference Names, select
network.negotiate-auth.trusted-uris and either double-click or right-click, and select Modify. Here, you
can specify a comma-separated list of URLs or domains, enter the list of URLs used to access Systems Insight
Manager. For example:https://cms_fqdn, where
When automatic sign-in occurs, an intermediate sign-in page appears. If you click Cancel from this page,
the manual sign-in page appears. You might want to cancel automatic sign-in if any unexpected network or
domain errors occur. If any browser configuration errors are detected, automatic sign-in is cancelled and
the manual sign-in page appears along with the configuration error.
Failures encountered during automatic sign-in are logged as normal sign-in failures in both the audit log and
the event log. If automatic sign-in is not attempted, no failure is detected or logged by Systems Insight
Manager.
If automatic sign-in is configured, you can manually sign in to Systems Insight Manager.
cms_fqdn
is the FQDN of the CMS.
•If automatic sign-in fails, the manual sign-in page appearsThis might occur if you are logged in to
the operating system using an account that is not an Systems Insight Manager account.
•If automatic sign-in is not attemptedThis might occur if the browser is not properly configured for
automatic sign-in, or the feature is disabled in Systems Insight Manager.
•If you click Sign Out from Systems Insight ManagerThis enables you to specify another user account
to use if you are signed in to the operating system with a different account.
Signing in and using the graphical user interface17
Guided tour of the Systems Insight Manager user interface
The GUI includes the following six regions:
1.Banner areaThe
Manager, 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 panelThis panel provides uncleared event status,
an alarm to notify you about certain events or statuses. You can customize the System Status panel
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.
You can enlarge the panel by clicking the Open in new window icon ( ) to display a separate large
window that you can resize and view from across a room without sitting at the Systems Insight Manager
terminal.
3.Search panelThe 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. 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 panelSystem 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. All default collections are shared. You can add additional
collections by clicking the Customize link. Collections can optionally be configured to show
status
icons in this area.
5.Systems Insight Manager menusThe Systems Insight Manager menus provide access to tools, logs,
software options, and online help. The Options menu is primarily for users who administer the Systems
Insight Manager software. If you lack authorization to use these tools, you might not be able to view
certain menus.
6.Systems Insight Manager workspaceThe workspace displays the results of your latest request. It can
contain a collection,
terminal instead of displaying in the
to Systems Insight Manager. By default, the introductory page is the Home page. The introductory
page provides information and tips about Systems Insight Manager and links to frequently used features.
You can customize Systems Insight Manager to display a different page as the Home page.
banner
provides a link to the Home page, a link to Sign Out of Systems Insight
tool
, or report. Some tools launch a separate browser window or X Window
workspace
. This area contains the Home page when you sign in
system health status
information, and
health
18Product overview
NOTE:To maximize the workspace, click the Maximize link next to the Help icon (). To restore
the workspace to its original size, click Restore Size.
Customizing views
A Customize link is available in the upper right of many pages in Systems Insight Manager. Use this link
to customize the way the page is presented.
Signing in and using the graphical user interface19
Part II Setting up Systems Insight Manager
20
3 Setting up managed systems
Setting up managed systems involves installing the required Management Agents software and configuring
the supported protocols to communicate with the Systems Insight Manager software.
Setting up Windows servers to be managed by Systems Insight Manager
To be fully managed by Systems Insight Manager, HP ProLiant servers running Windows should have the
Insight Management Agents installed. These agents are part of the ProLiant Support Pack. See below for
instructions on how to do this through Systems Insight Manager. You can also configure these agents to be
installed as part of your normal operating system deployment procedures. For third party servers, enable
WMI and/or SNMP in the operating system. Systems Insight Manager attempts to retrieve information that
is instrumented in an industry-standard way. After setting up the management agents on the managed systems,
the remaining configuration can be done from the Systems Insight Manager user interface. Continue to
Chapter 4 Credentials for further information.
For more information regarding ProLiant Support Pack, see the http://www.hp.com/servers/psp.
Installing the ProLiant Support Pack on a Systems Insight Manager Windows systems
for the first time
The Initial ProLiant Support Pack Install task enables you to install a ProLiant Support Pack from a Windows
CMS to a Windows managed system when you do not have any Insight Management Agents, especially
the HP Version Control Agent, installed. This task also configures the
Systems Insight Manager and the setting to use the desired HP Version Control Repository Manager.
systems
to use the trust
certificate
from
Requirements
•The Initial ProLiant Support Pack Install feature is only supported on a Windows CMS.
•The target system must be a Windows system.
•VCRM must be installed and populated on servers containing a repository.
•You must have Windows administrator privileges on target systems to install a ProLiant Support Pack.
•Only one Initial ProLiant Support Pack Install task can be run at a time. If you execute a second task
before the first one is complete, the second task starts after the first task completes.
Installing the ProLiant Support Pack
Procedure 3-1 Installing the ProLiant Support Pack
1.Select Deploy→Deploy Drivers, Firmware and Agents→Initial ProLiant Support Pack Install.
The Initial ProLiant Support Pack Install page appears.
2.Select the target systems. For more information about selecting target systems, see the Systems Insight
Manager online help.
3.Click Next.The Enter Windows credentials page appears.
4.On the Enter Windows credentials page, complete the following:
Setting up Windows servers to be managed by Systems Insight Manager21
a.In the User name field, enter the Windows administrator user name for the target system.
b.In the Password field, enter the administrator password.
c.In the Password (Verify) field, re-enter the Windows administrator password.
d.In the Domain field, enter the Windows domain. This field can be left blank if the system is not
part of a domain.
NOTE:If ProLiant Support Pack has not been previously installed on the system, you must enter the
credentials here and do not select Use sign-in credentials.
5.Click Next. The Select a Windows Support Pack page appears.
6.Under Step 3: Select a Version Control Repository, select a source repository system to retrieve the
catalog.
The following fields appear:
•Name. Displays the name of the system.
•Status. Displays the status of the system.
•Product Name. Displays the name of the product.
•Trusted?. Displays whether the system trust relationship has been configured. To configure a trust
relationship, click configure.
This section displays systems authorized by the current user name. If the current user is not authorized
to view the systems, a message appears, indicating that the user does not have authorization rights on
the system.
7.Under Select a Support Pack to Install, select a support pack to install. Click theicon to navigate
down and view the contents of the Version Control Repository that you selected.
22Setting up managed systems
NOTE:To expand the System Software Baseline to display all contents, click theicon located
in the upper-left corner of the Select a Support Pack to Install section. Click theicon to collapse
the listings.
8.(Optional) To install and configure
(Secure Shell). This option is disabled by default.
9.(Optional) If you are installing a ProLiant Support Pack that is earlier than or the same as the
version
10. (Optional) If you do not want to reboot after the installation, clear the Reboot systems if necessaryafter successful install option, which is selected by default. However, the system must be rebooted
for the new ProLiant Support Pack to be available.
11. Click Next. The Step 4: Configure Support Pack page appears, showing the following options:
•Configure HP System Management Homepage
•Configure Version Control Agent
, select Force downgrade or re-install the same version. This option is disabled by default.
OpenSSH
on the target systems, select Install and initialize SSH
installed
For more information about preconfiguring the SMH component, see
Installation Guide
documentation.html and for Version Control, see http://h18013.www1.hp.com/products/servers/
management/agents/documentation.html.
12. Click Next to start the ProLiant Support Pack download. The Download Support Pack page appears.
13. After the support pack is downloaded, click Schedule to create a scheduled task for the Initial ProLiant
Support Pack Install to run or click Run Now to run the task immediately.
at http://h18013.www1.hp.com/products/servers/management/agents/
HP System Management Homepage
Setting up HP-UX servers to be managed by Systems Insight Manager
Procedure 3-2 Setting up HP-UX managed systems
1.Understand the basic managed system software for HP-UX.
For HP-UX, the following software, shown with minimum recommended versions, is required for essential
Systems Insight Manager functionality to operate. This software is installed by default as part of the
latest HP-UX 11i v2 and 11i V3 operating environments, but it might need to be installed or updated
on HP-UX 11i v1 or older HP-UX 11i v2 environments.
•T1471AA HP-UX Secure Shell
•B8465BA HP
This WBEM Services bundle contains basic system instrumentation displayed in the Systems Insight
Manager Property pages, supporting collection and reporting by Systems Insight Manager inventory
functionality. To maximize the value of Systems Insight Manager for properties, inventory, and events,
see http://www.hp.com/go/hpsim/providers for the latest WBEM Services bundle.
For the latest WBEM Services bundle, go to http://www.hp.com/go/hpsim/providers.
WBEM Services
for HP-UX
Setting up HP-UX servers to be managed by Systems Insight Manager23
If iCap information is desired, also install:
▲B9073BA version 08.01.01 iCAP for HP-UX
2.Ensure the managed system software is installed.
To verify that the minimum required software is installed, log in to the remote system, and run the
following command:
$ swlist –l bundle T1471AA B8465BA OpenSSL
To verify that the optional providers and HP System Management Homepage are installed, run commands
such as:
3.Acquire and install the managed system software if not previously installed.
The SSH and WBEM bundles are included on the HP-UX Operating Environment and Application Release
media, as well as part of the Systems Insight Manager HP-UX depot downloaded from
After you have obtained the depots containing the software, you can install then from the managed
system:
$ swinstall –s <depot_location> OpenSSL
NOTE:B8465BA and B9073BA version 08.01.01 depends on OpenSSL, so you must install OpenSSL
first.
$ swinstall –s <depot_location> T1471AA
$ swinstall –s <depot_location> B8465BA
$ swinstall –s <depot_location> <names of WBEM providers being installed>
After you have verified that the correct management software is installed on your managed systems, continue
to Chapter 4 Credentials> to finish the configuration from the Systems Insight Manager user interface.
Manually setting up an HP-UX managed system
Although chapters 4-7 explain how to finish configuring managed systems from the Systems Insight Manager
GUI, this section describes how to perform some of these same steps from the command line for HP-UX
systems. You do need to first supply credentials and discover the systems, as described in Chapter 4
Credentials and Chapter 6 Discovery. Then you can do the following actions from the command line, if
desired.
You can use the Systems Insight Manager Configure or Repair Agents tool to configure HP-UX managed
systems simultaneously, or you can configure each managed system manually.
Configuring SNMP to send traps to the CMS
•On the managed system, add the full host name or IP address of the CMS as a trapdest in the following
file:
/etc/SnmpAgent.d/snmpd.conf
trap-dest: hostname_or_ip_address
•Stop the SNMP Master agent and all subagents with the command:
/sbin/init.d/SnmpMaster stop
•Restart the SNMP Master agent and all subagents with the command:
/usr/sbin/snmpd
24Setting up managed systems
Configuring SSH access
On the CMS, copy the SSH-generated public key from the CMS to the managed system using the
mxagentconfig:
Use one of the following commands:
•mxagentconfig -a -n <hostname> -u root -f <file_with_root_password>
•mxagentconfig -a -n <hostname> -u root -p <root_password>
NOTE:Using the -p option exposes the password through ps output, so using the -f option (with a
file only readable by root, and containing only the managed system root password) is highly
recommended when using mxagentconfig -a. If you use the -p option, enclose the password in
single quotes if the password has any special characters, such as & or $. For more information and
options, see the mxagentconfig manpage with man mxagentconfig.
Subscribing to WBEM indications/events:
NOTE:For more information about HP-UX WBEM events, see the Systems Insight Manager online help.
Procedure 3-3 Subsribing to WBEM indications/events
1.From the managed system, be sure WBEM is installed.
swlist -l bundle B8465BA
2.Verify that SysFaultMgmt provider is installed.
Depending on the System Fault Manager configuration, run the following:
cimprovider –lm SFMProviderModule
The EMSWrapperProvider appears.
or
cimprovider –ls
The EMSWrapperProvider appears.
NOTE:For more information regarding System Fault Manager, see HP System Fault Management
Diagnostics.
3.From the CMS:
To subscribe to WBEM Events, you must have root access. You can verify what credentials are used for
WBEM access by running the following command line:
mxnodesecurity –l –p wbem –n <systemname>
If the managed system does not have a root level user credential configured, you can add it for the
individual system.
NOTE:You can use the Configure or Repair Agents tool in the Systems Insight Manager UI to perform
this step without permanently recording a root password.
•To change the individual system:
mxnodesecurity -a -p WBEM -c \
<username:password> -n <systemname>
4.From the CMS, run the WBEM Indications/Events command line:
mxwbemsub -l -n <systemname>
Setting up HP-UX servers to be managed by Systems Insight Manager25
Setting up Linux servers to be managed by Systems Insight Manager
To be fully managed by Systems Insight Manager, HP ProLiant servers running Linux should have the Insight
Management Agents installed. These agents are part of the ProLiant Support Pack. You can install the PSP
manually, or configure it to be installed as part of your normal operating system deployment procedures.
After setting up the management agents on the managed systems, the rest of the configuration can be done
from the Systems Insight Manager UI. Continue to Chapter 4 Credentials for further information.
Installing the ProLiant Support Pack on a Linux system for the first time
For Linux systems, use the Linux Deployment Utility to install the latest support pack with the preconfigured
components to the local system. For more information regarding installing a support pack using the Linux
Deployment Utility, see http://www.hp.com/servers/psp.
Configuring agents remotely using Configure or Repair Agents:
1.For Linux systems, select Install Linux PSP or ESX Agents.
2.Click Next. The Step 3: Configure or Repair Agents page appears.
Manually setting up Linux managed systems
Although chapters 4-7 explain how to finish configuring managed systems from the HP SIM GUI, this section
describes how to perform some of these same steps from the command line for Linux systems. You do need
to first supply credentials and discover the systems, as described in chapters 4 and 6. Then you can do the
following actions from the command line, if desired.
Installing and configuring SSH
Procedure 3-5 Installing and configuring SSH on a Linux system
1.Verify that SSH is installed on the managed system:
rpm -qa | grep ssh
If SSH is not installed, see your Linux provider for information about installing SSH.
2.On the CMS, copy the SSH-generated public key from the CMS to the managed system, and place it
in the authorized keys file of the execute-as user (root or administrator).
IMPORTANT:On a non-English CMS, ensure that an administrator account exists on the CMS, and
that mxagentconfig has run on the CMS for the created administrator account.
a.Launch the Manage SSH Keys dialog box from the CMS command prompt:
mxagentconfig -a -n hostname -u username -p Password
b.Click Connect.
Configuring a Linux 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.
Procedure 3-6 Configuring a Linux system to send SNMP traps
1.Verify that SNMP is installed:
rpm -qa | grep snmp
If it is not installed, see your Linux provider for information about installing SNMP.
2.If the HP Server and Management Drivers and Agents daemons are installed on your system, stop them:
/etc/init.d/hpasm stop
3.Stop the SNMP daemon:
/etc/init.d/snmpd stop
26Setting up managed systems
4.Edit the snmpd.conf file.
For Red Hat Linux, open the following file in the vi editor:
vi /etc/snmp/snmpd.conf
For SuSE SLES 8, open the following file in the vi editor:
vi /usr/share/snmp/snmpd.conf
a.Remove the comment symbol (#) from the trapsink line, and add the IP address of the CMS:
trapsink IPaddress
where IPaddress is the IP address of the CMS.
b.Add the CMS to the read only community by adding the line:
rocommunity CommunityName IPaddress
where CommunityName is the SNMP community string used by the CMS and IPaddress is the
IP address of the CMS.
c.Save the changes to the file. To save and close this file using the vi editor, press the Esc key, enter
:wq!, and then press the Enter key.
5.Start the SNMP daemon:
/etc/init.d/snmpd start
6.If the HP Server Management Drivers and Agents daemons are installed on your system, start them:
/etc/init.d/hpasm start
Setting up Linux servers to be managed by Systems Insight Manager27
4 Credentials
In Systems Insight Manager, credentials are used to enable the CMS to communicate with managed systems,
through WBEM, WS-MAN, SSH, and SNMP. However, the Sign-in credential is used unless you configure
the other protocols. The Sign-in credential is protocol independent and can be tied to systems through the
discovery credential. In Systems Insight Manager, there are three different types of credentials:
•System credentialsCredentials used by
include WBEM, WS-MAN, and SSH credentials, Sign-in, SNMP community string, and
(SSO) credentials.
•Discovery task credentialsCredentials used by a discovery task that apply to all systems discovered
by that task.
•Global CredentialsGlobal credentials are system credentials that apply to all systems.
During the identification process (done automatically during discovery), credentials are tried, starting with
System Credentials. If they do not work, and the Try Others setting is chosen for them, then Discovery
credentials are used. Similarly, if those do not work and the Try Others setting is chosen, then Global
Credentials are tried. As soon as a credential is found that works, Systems Insight Manager notes that
credential as
as it continues to work. If it should fail, then the process is repeated the next time identification is run. To see
the
working
(Options→Security→Credentials→System Credentials). These
Credentials that are in use table.
When a discovery credential is used to successfully communicate with a system, a credential reference is
created for that system. If the credential is later changed on that same discovery task, the credential that is
used on all systems referencing it changes. This enables credentials to be changed in one place (usually
passwords for an account) and immediately be available for use in Systems Insight Manager. The same is
true for global credentials.
Because of this, if a global or discovery credential is deleted, you are asked if all references to that credential
should be removed or if copies should be made as system credentials for each system that is referencing the
current credential.
However, when a credential is overwritten, instead of deleted and then re-added, the credential is changed
and each system referencing it uses the new username/password values.
If the intent is not to change what is currently in use, you must add a new credential. For discovery tasks, a
new discovery task must be created with its own credentials, instead of editing an existing discovery task,
if the systems require different credentials than contained in the existing discovery task.
working
credentials for any managed system, go to the System Credentials page
and continues to use it for regular communications with the managed system as long
identification
to access managed systems. These credentials
Single Sign-On
working
credentials appear in the
Example XML file to add more than 10 WBEM username and password
pairs
To save time and effort, create an XML file that defines your system authorizations before running discovery.
For example:
You can include the IP addresses of the systems to be discovered in an XML comment so that you can maintain
the IP addresses with the XML file and can copy and paste into the Ping inclusion ranges, system (hosts)names, templates, and/or hosts files field when creating or editing a discovery task.
After you create the XML file import it into Systems Insight Manager before running discovery using the
following CLI command:
mxnodesecurity -a -f <path-to-xml-file>
HP recommends limiting the WBEM user name and password pairs to 10 to reduce the overall discovery
run time.
Example XML file to add more than 10 WBEM username and password pairs29
5 WMI Mapper Proxy
Windows systems use a variation on the WBEM
Manager to communicate with Windows systems, the WBEM protocol it uses must be converted to the WMI
protocol and vice versa. This is the function of the WMI Mapper Proxy. This proxy is typically installed on
the same system as Systems Insight Manager when Systems Insight Manager is installed on a Windows
system. For Linux or HP-UX installations where Windows systems will be managed, it can be installed on a
separate Windows system, with its location configured in the Options→Protocol Settings→WMI MapperProxy menu.
You can configure the WMI Mapper Proxy from the First Time Wizard. You can also add, edit, and delete
WMI Mapper Proxies by selecting Options→Protocol Settings→WMI Mapper Proxy.
management protocol
called WMI. For Systems Insight
30
Loading...
+ 148 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.