ServerView Integration 4.0 in HP Operations Manager

Transcription

User Guide - English
FUJITSU Software ServerView Suite
ServerView Integration V4.0 in HP
Operations Manager
Edition August 2012
Comments… Suggestions… Corrections…
The User Documentation Department would like to
know your opinion of this manual. Your feedback helps
us optimize our documentation to suit your individual
needs.
Feel free to send us your comments by e-mail to
[email protected].
Certified documentation
according to DIN EN ISO 9001:2008
To ensure a consistently high quality standard and
user-friendliness, this documentation was created to
meet the regulations of a quality management system
which complies with the requirements of the standard
DIN EN ISO 9001:2008.
cognitas. Gesellschaft für Technik-Dokumentation mbH
www.cognitas.de
Copyright and Trademarks
Copyright © 2012 Fujitsu Technology Solutions GmbH.
All rights reserved.
Delivery subject to availability; right of technical modifications reserved.
All hardware and software names used are trademarks of their respective manufacturers.
Contents
1
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.1
Product description . . . . . . . . . . . . . . . . . . . . . . . 6
1.2
Target group . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.3
Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.4
Summary of contents . . . . . . . . . . . . . . . . . . . . . . 7
1.5
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.6
Changes since the previous version . . . . . . . . . . . . . . 8
1.7
Notational conventions
1.8
Documentation for ServerView Suite . . . . . . . . . . . . . . 9
2
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1
ServerView Integration in HP Operations Manager . . . . . 11
2.2
Concept of ServerView integration for Windows events
2.3
Integrated event log entries . . . . . . . . . . . . . . . . . . 14
2.4
Concept of SNMP trap integration
2.5
Integrated SNMP traps . . . . . . . . . . . . . . . . . . . . . 16
3
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3.1
Installation requirements . . . . . . . . . . . . . . . . . . . 20
3.2
Installation process
3.3
Guided installation . . . . . . . . . . . . . . . . . . . . . . . 21
3.4
Installation from the command line . . . . . . . . . . . . . . 26
3.5
Extending the Windows Start menu
3.6
3.6.1
3.6.2
Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Manual uninstallation steps . . . . . . . . . . . . . . . . . . . 27
Automatic uninstallation process . . . . . . . . . . . . . . . . 30
ServerView Integration in HPOM
. . . . . . . . . . . . . . . . . . . . . 8
. . 12
. . . . . . . . . . . . . . 15
. . . . . . . . . . . . . . . . . . . . . . 20
. . . . . . . . . . . . . 26
Contents
4
Extending HP Operations Manager
. . . . . . . . . . . . . . 31
4.1
4.1.1
4.1.2
Integrated PRIMERGY policies . . . . . . . . . . . . . . . . . 31
Policies of the PRIMERGY event groups . . . . . . . . . . . . . 32
Modifying rules for events or creating new ones . . . . . . . . . 36
4.2
4.2.1
4.2.2
PRIMERGY server SNMP traps . . . . . . . . . . . . . . . . . 44
Policies of the PRIMERGY server SNMP trap groups . . . . . . 45
Modifying rules for SNMP traps or creating new ones . . . . . . 55
4.3
4.3.1
ServerView tool . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring the ServerView start tool . . . . . . . . . . . . . . . 62
5
Configuration and operation . . . . . . . . . . . . . . . . . . 65
5.1
Distributing and activating the policies . . . . . . . . . . . . 65
5.2
Displaying the events/traps in the
HP Operations Manager console . . . . . . . . . . . . . . . . 67
5.3
5.3.1
5.3.2
Starting the ServerView management console . . . . . . . . 70
Starting ServerView Operations Manager . . . . . . . . . . . . 70
Starting ServerView Operations Manager from the
event browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
1
Preface
With ServerView Operations Manager, the ServerView Suite offers a software
product that controls all important server functions, such as hard disk, fans,
power supply and temperature. If the values defined for these parameters are
exceeded or if a fault occurs, error messages are forwarded to a central
management console or fault-recovery measures are initiated.
ServerView Integration in HP Operations Manager (HPOM) allows you to use
the functionality of ServerView in HP Operations Manager.
If a fault occurs during hardware monitoring of a PRIMERGY or PRIMEQUEST
server, this is sent as an SNMP event, or by a ServerView agent as an event
entry, to the Windows Event Log. HPOM stores these events in its database and
they can be displayed in various views. Furthermore, rules can be applied which
trigger an appropriate action when a fault is detected, e.g. a mail describing the
fault might be sent to hardware support.
Furthermore, ServerView Operations Manager can be started via HP
Operations Manager.
This allows the PRIMERGY or PRIMEQUEST servers to be managed in a
network with multiple platforms.
5
Product description
1.1
Preface
Product description
ServerView Integration in HP Operations Manager allows you to use both the
ServerView functions and the HPOM functions on a central management
server. ServerView Integration V4.0 in HP Operations Manager supports the
event log entries of ServerView SNMP agents up to V6.00.
After the integration, the PRIMERGY or PRIMEQUEST servers can be
monitored from the central HPOM management console. Incoming events are
displayed via Windows Event Log entries or SNMP traps. Automatic reactions
to these event messages can be configured and triggered.
The integration offers the following benefits:
– Existing management investments are protected.
– The same methods of presentation, monitoring, evaluation and correlation
are used for all the devices being monitored, so that the response to failures
is fast and, in some cases, automatic.
– The network components and their resources are used efficiently.
– Maximum performance and minimum downtimes ensure an optimum
cost/benefit ratio.
6
Preface
1.2
Target group
Target group
This manual is intended for system and network administrators as well as
service specialists. It is assumed that you have a sound knowledge of hardware
and of HP Operations Manager and ServerView.
1.3
Requirements
To be able to install the ServerView integration package, you must have HP
Operations Manager 8.10 or higher for Windows 2003 (Service Pack 1 or
higher) or Windows Server 2008 (R2) or HP Operations Manager 9.00 for
Windows 2008 R2 (64 Bit) installed on your system.
1.4
Summary of contents
This manual describes the integration package of ServerView Integration in HP
Operations Manager. It does not provide any basic information on ServerView,
HP Operations Manager or server management, as it is assumed that you have
sufficient experience of ServerView and HP Operations Manager. The manual
should therefore be seen as complementary to the ServerView documentation.
The various chapters of the manual cover the following topics.
– Chapter 2 introduces the product ServerView Integration in HP Operations
Manager.
– Chapter 3 describes the installation of the ServerView integration package.
– Chapter 4 introduces the components integrated in HP Operations Manager.
– Chapter 5 tells you how to configure and operate ServerView Integration.
1.5
Troubleshooting
In the Readme.pdf file, which you can open using an entry in the Windows Start
menu, you will find further information on error sources which may exist and how
to bypass them.
7
Changes since the previous version
1.6
Changes since the previous version
This edition is valid for ServerView Integration V4.0 in HP Operations Manager
and replaces the following online manual: “ServerView Suite, ServerView
Integration V3.0 in HP OpenView Operations”, edition July 2011.
The manual features the following changes and enhancements:
– The ServerView integration package is now only available via the Fujitsu
download area at http://support.ts.fujitsu.com/com/support/downloads.html.
(Full-text search: "ServerView Integration in HP Operations Manager".)
– Fujitsu PRIMEQUEST servers are integrated in HPOM via SNMP
Interceptor Policies and Tool Policy.
1.7
Notational conventions
The following notational conventions are used in this manual:
V
Warning about potential damage to health, data
loss or device damage.
I
Additional information, notes and tips.
Ê
Actions performed by the user.
italics
Commands, menu items, button names, options,
variables, symbol classes, file names and path
names in the body text.
typewriter text
System output.
Table 1: Notational conventions
8
Documentation for ServerView Suite
typewriter text
boldface
Instructions to be entered from the keyboard.
All of these command lines are concluded with the
Ú key, which is therefore not specified in the text.
If comments are added to the input and output in
application examples, the text of the comment is
separated from the actual input and output with #.
The text of the comment is also shown in
typewriter text boldface.
[Key symbols]
The keys are shown as they appear on the
keyboard. If uppercase characters are to be
explicitly input, the shift key is specified, e.g.
[SHIFT] - [A] for A.
If two keys must be pressed simultaneously, this is
indicated by a hyphen between the key symbols.
Table 1: Notational conventions
References to other sections in the manual indicate the title of the relevant
section or chapter and the page on which the section begins.
1.8
The documentation for the ServerView Suite can be found on the ServerView
Suite DVD 2 supplied with each server system.
The documentation can also be downloaded free of charge from the Internet.
You will find the online documentation at http://manuals.ts.fujitsu.com under the
link Industry standard servers.
For an overview of the documentation to be found under ServerView Suite as well
as the filing structure, see the ServerView Suite sitemap (ServerView Suite - Site
Overview).
9
10
2
Introduction
This chapter explains how the functionality implemented by ServerView under
Windows is transferred to HP Operations Manager.
I
Global directory names in HP Operations Manager (HPOM)
The directories used by HP Operations Manager are determined by the
definition of various environment variables. These environment variables
(e.g. %OvInstallDir%) are used in the path names in this manual.
2.1
ServerView Integration in HP Operations
Manager
The product ServerView Integration Pack for HP Operations Manager is an
integration package for embedding ServerView in HP Operations Manager
under Windows 2003 and Windows Server 2008 (R2) . It is a smart plug-in,
which allows the functionality of ServerView to be used in HP Operations
Manager.
In particular, ServerView Integration in HP Operations Manager includes:
– Policies for the ServerView/controller events
– Tools for starting the ServerView management consoles
For more information on the tools and policies, see the chapter “Extending HP
Operations Manager” on page 31.
11
2.2
Introduction
Concept of ServerView integration for
Windows events
As a basic requirement for correct ServerView integration into HP Operations
Manager, the following basic conditions must be fulfilled:
– The ServerView integration package must be installed on the same
management server as HP Operations Manager
– The ServerView agents must be installed on the managed PRIMERGY
servers
I
The ServerView agents must be appropriately configured for this. For
more details, see the ServerView Operations Manager Installation
Guide.
– The agent that is normally required to manage a server with HP Operations
Manager (HPOM agent) must be installed.
Management server
(HPOM server)
Managed server
(PRIMERGY server)
Events
Event log
Policies & configuration
Tools
Controller
SV agent driver
Reports and graphs
HPOM agent
HPOM message
Figure 1: Concept of ServerView Integration in HPOM (Windows events)
12
Introduction
The ServerView agents or the controller drivers on the managed PRIMERGY
servers (managed nodes) write the events to the Windows Event Log if
appropriately configured.
The entries of the ServerView agents or the controller drivers in the Windows
Event Log are read out by the HPOM agents and dealt with according to the
loaded policies of the ServerView event groups. The HPOM agents on the
managed servers forward the event log entries as messages (HPOM message)
to the management server (HPOM server).
The ServerView events are displayed in the HPOM console.
Figure 2: Events from the Windows Event Log in the event browser of the HPOM console
Furthermore, ServerView Operations Manager can be started both in the list
display and with the single server data under HP Operations Manager.
13
Integrated event log entries
2.3
Introduction
Integrated event log entries
For monitoring the PRIMERGY servers, the event log entries of the following
ServerView components and controller drivers are integrated in HP Operations
Manager.
ServerView agents
–
–
–
–
–
HD MIB
NTCluster MIB
Threshold MIB
ServerControl2 MIB
X10sureV1 MIB
I
With these components, the ServerView agents make the entries in the
Windows Event Log on the managed servers (managed nodes) (even
though the list above refers to MIBs). For this the administrator must
configure the ServerView agents accordingly.
Controller drivers
–
–
–
–
–
–
–
14
ServerView RAID
Duplex Data Manager
QLogic Fibre Channel Adapter
Emulex Fibre Channel Adapter
Broadcom LAN Controller
Intel LAN Controller (Intel LAN software kit)
PowerNet / PowerChute USV from APC
Introduction
2.4
Integration of the events of servers running Linux (e.g. partitions of
PRIMEQUEST servers) cannot be implemented via Windows Event Logs.
In HP Operations Manager monitoring of the Linux servers by means of SNMP
traps is therefore implemented via the SNMP Interceptor.
When the traps are sent to the HPOM system, they are received there by an
agent. These traps are interpreted by the HPOM-SNMP Interceptor and
displayed as results on the HPOM console.
Management server
(HPOM server)
Events
Policies & configuration
PRIMERGY Linux server
Tools
SNMP Interceptor
SNMP agent
SNMP message
Figure 3: Concept of ServerView Integration in HPOM (SNMP traps)
15
Integrated SNMP traps
2.5
Introduction
The SNMP traps of the following ServerView components and controller drivers
are integrated into HP Operations Manager to monitor the PRIMERGY Linux
servers.
ServerView agents
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
–
16
HD-MIB
MMB-ComTrap-MIB.mib
NTCluster-MIB
PSA-ComTrap-MIB.mib
PSA-ExternalFileUnitTrap-MIB.mib
PSA-LinBcm5700Trap-MIB.mib
PSA-LinEmulexTrap-MIB.mib
PSA-LinGdsTrap-MIB.mib
PSA-LinGlsTrap-MIB.mib
PSA-LinGrmpdTrap-MIB.mib
PSA-LinIbTrap-MIB.mib
PSA-LinIntelE1000ETrap-MIB.mib
PSA-LinIntelE1000Trap-MIB.mib
PSA-LinIntelE100Trap-MIB.mib
PSA-LinIntelIgbTrap-MIB.mib
PSA-LinIntelixgbeTrap-MIB.mib
PSA-LinLanComTrap-MIB.mib
PSA-LinLsiLogicTrap-MIB.mib
PSA-LinScsiComTrap-MIB.mib
PSA-LinSvsRaidTrap-MIB.mib
PSA-LinTg3Trap-MIB.mib
PSA-LinXframe2Trap-Mib.mib
PSA-SVAgentsTrap-MIB.mib
PSA-WinBcm5700Trap-MIB.mib
PSA-WinDiskMirrorTrap-MIB.mib
PSA-WinDiskTrap-MIB.mib
PSA-WinEmulexTrap-MIB.mib
PSA-WinGlsTrap-MIB.mib
PSA-WinIntelE1000expTrap-MIB.mib
PSA-WinIntelE1000Trap-MIB.mib
PSA-WinIntelE100Trap-MIB.mib
PSA-WinIntele1expressTrap-MIB.mib
PSA-WinIntelixgbnTrap-MIB.mib
PSA-WinLsiLogicTrap-MIB.mib
Introduction
–
–
–
–
–
–
–
PSA-WinMpdTrap-MIB.mib
PSA-WinSvsRaidTrap-MIB.mib
PSA-WinXframe2Trap-MIB.mib
S31-MIB
ServerControl2-MIB
Threshold-MIB
X10sureV1.mib
Controller drivers
–
–
–
–
ServerView Raid
DuplexDataManager
Broadcom LAN Controller
Intel LAN Controller (Intel LAN software kit)
To permit the SNMP traps to be processed by HP Operations Manager, the
SNMP environment must be specified appropriately on the monitored Linux
systems (PRIMERGY/PRIMEQUEST). This means that the machine on which
HPOM Manager is installed must be set on the managed nodes as the
destination for the SNMP traps. Please refer to the documentation relating to
SNMP on Linux for information on how these SNMP settings are made.
17
18
Introduction
3
Installation
This chapter explains how to install the ServerView integration package on the
HPOM management server.
I
The installation process is also described in the release notice
Readme.pdf, which can be found in the integration package. Please read
this release notice to find out about last-minute technical changes.
ServerView Integration in HP Operations Manager requires the following:
– The ServerView integration package must be installed on the HP Operations
Manager management server,
– The ServerView agents must be installed on the managed PRIMERGY
servers,
– The agent that is normally required to manage a server with HP Operations
Manager (HPOM agent) must be installed on the managed PRIMERGY
servers.
If you want to start ServerView Operations Manager via the HPOM
management console, the ServerView Operations Manager can be installed on
a different management server than the one on which the HP Operations
Manager software is installed. You enter the server name or IP address and port
number of the management server the first time you start ServerView
Operations Manager (see section “Starting ServerView Operations Manager”
on page 70).
I
ServerView Operations Manager and the ServerView agents are
installed from the ServerView Suite DVD 1 from Fujitsu Technology
Solutions. For a description see the ServerView Operations Manager
Installation Guides.
19
Installation requirements
3.1
Installation
Installation requirements
The following requirements must be met:
– Windows 2003 (Service Pack 1 or higher), Windows Server 2008 SP1 or
Windows Server 2008 (R2) must be installed on the management server.
– The server variant of HP Operations Manager 8.10 or higher must be
installed on the management server.
If either of these requirements is not met, the installation will be aborted with a
corresponding error message.
3.2
Installation process
ServerView Integration in HP Operations Manager is available via the download
area at http://support.ts.fujitsu.com/com/support/downloads.html.
The installation package is called SVIPHPOM.exe.
There are two possible ways to start the installation:
– By double-clicking the file SVIPHPOM.exe (see section “Guided installation”
on page 21),
– Via the command line interface (see section “Installation from the command
line” on page 26).
During the installation the following steps are performed automatically:
– The system checks whether the software requirements are met on the target
system.
– The installation path of HP Operations Manager is determined and used as
the basis for installation of the ServerView Integration.
I On x64 Windows operating systems the ServerView integration pack
will be fixed installed into %ProgramFiles(x86)%\HP OpenView).
– The files of the ServerView Integration are copied to the different directories
of HP Operations Manager.
– A number of utility calls are executed in command windows to activate the
policies and tools
– Necessary entries are made in the Registry.
20
Installation
Guided installation
– The Windows Start menu is complemented by an item which enables
installed documents to be opened.
There is no need to restart Windows following the installation.
If the HPOM console is running, it must be restarted after the installation.
3.3
Guided installation
Ê Start the guided installation by double-clicking the file SVIPHPOM.exe.
This opens the Installation wizard.
Here you can select the language for the installation procedure. The
following welcome screen is then displayed in your chosen language.
Figure 4: Starting the Installation wizard
The welcome screen shows the version number of ServerView Integration in
HP Operations Manager.
21
Guided installation
Installation
Ê Click Next.
The license agreement dialog is displayed.
Ê Confirm the license agreement by selecting I accept the license agreement, and
then click Next to proceed to the information on the readme file.
The following dialog with information on the readme file is displayed.
Figure 5: Information on the readme file
The readme file contains important information on installation and
uninstallation. After installation has been completed, you can open the
readme file via the Windows Start menu Start - Programs - Fujitsu ServerView
Suite - HPOM Integration - Readme.
Ê Click Next.
The basic directory for HPOM is displayed in the subsequent dialog. No
change can be made here as the directory is determined by HPOM.
22
Installation
Guided installation
Figure 6: Basic directory for HPOM
Ê Click Next.
In the subsequent dialog you can set which policy rule groups are to be
imported:
– Windows Event Logs
– SNMP Traps
23
Guided installation
Installation
Figure 7: Select policy rule group for import
I
If neither of the policy rule groups is imported, the tools for starting
the ServerView Operations Manager are not imported, either.
Ê Click Next.
Figure 8: Start installation process
24
Installation
Guided installation
Ê Click Next to start the installation.
During the installation process, HPOM commands are also executed which
run in Windows command windows.
When the process has been completed, you will obtain information
regarding the end of installation in a further dialog.
Ê Click Finish to terminate the installation process.
I
If the installation process is terminated incorrectly, you should perform
installation using trace options. You will then be able to create a log file.
Further information on this is provided in the next section.
25
Installation from the command line
3.4
Installation
Installation from the command line
As well as the menu-driven installation, you also have the option of installing
ServerView Integration in HP Operations Manager via the Windows command
line interface (CLI).
Information on installation via the command line is provided in the readme file
ReadmeSVIPHPOM.txt.
3.5
Extending the Windows Start menu
After installation, the Windows Start menu contains an extra item which enables
you to open documents for the integration package:
Start - Programs - Fujitsu ServerView Suite - HPOM Integration
Figure 9: Windows Start menu entries
Four documents can be opened. Adobe Reader must be installed on the
Management Server to read the documents in PDF format.
– (This) manual for ServerView Integration in HPOM
– Readme file containing information which may not yet have been included in
the manual
– Document of the integrated PRIMERGY Server events
– Document of the integrated PRIMERGY/PRIMEQUEST Server SNMP traps
26
Installation
3.6
Uninstallation
Uninstallation
When uninstalling the ServerView integration package, you must uninstall the
following components:
– Tools and directories of ServerView Operations Manager
– Files and directories that were created and copied when the integration
package was installed
– All Registry entries made during installation of the integration package
Before you start the uninstallation via the Windows Start menu, there are a few
manual steps you must perform.
3.6.1
Manual uninstallation steps
Before you start the automatic uninstallation of the ServerView Integration, you
must manually delete its tools and policies.
Deleting the tools
Start the management console of HP Operations Manager and expand the left
navigation window. Go to the folder Operations Manager - Tools.
Figure 10: Context menu for Tools
27
Uninstallation
Installation
On the context menu for Tools, select Configure. Then on the adjacent menu that
opens, select Tools... to open the Configure Tools window.
Figure 11: Deleting the tools
You delete the tools of the ServerView Integration by selecting the entry SPI for
PRIMERGY Server in this window. Then on the context menu for this entry, select
the Delete command. You will be asked to confirm the deletion, in which case
the tools of the ServerView Integration will be deleted. If you want to cancel the
delete operation, click No.
28
Installation
Uninstallation
Deleting the policies
Start the management console of HP Operations Manager and expand the left
navigation window. Go to the folder Operations Manager – Policy.
Figure 12: Deleting the policies
You delete the policies of the ServerView Integration by selecting the entry SPI
for PRIMERGY Server in the Policy groups folder in this window. Then on the
context menu for this entry, select the Delete command. You will be asked to
confirm the deletion, in which case the policies of the ServerView Integration will
be deleted. If you want to cancel the delete operation, click No.
29
Uninstallation
3.6.2
Installation
Automatic uninstallation process
You start the automatic uninstallation of the integration package via the
Windows Start menu.
Ê Start the uninstallation program via the Windows Start menu under Settings –
Control Panel – Add or Remove Programs.
Figure 13: Selecting the Integration package
Ê Select the entry ServerView Integration Pack for HP Operations Manager and
then click the Remove button.
Ê When you are asked to confirm the removal of the Integration module, click
Yes to start the uninstallation.
During uninstallation a window containing a progress bar is displayed.
When all files and entries of the ServerView Integration have been removed,
the message window closes and the corresponding entry is removed from
the Add or Remove Programs window.
30
4
Extending HP Operations
Manager
After successful installation of the integration package, the following new
components are now installed on the management server:
– The policies of the PRIMERGY event groups. See section “Integrated
PRIMERGY policies” on page 31
– The policies of the SNMP traps. See section “PRIMERGY server SNMP
traps” on page 44.
– The two tools for starting the ServerView Management consoles
(ServerView ServerList and ServerView Single Server). See section
“ServerView tool” on page 61.
4.1
Integrated PRIMERGY policies
The Policy Management folder contains the policies of the PRIMERGY event
groups. Every event group has its own policy definition group. The PRIMERGY
event groups begin with FTSPYSVSPI-. The individual events are inserted in
groups under Policy groups/SPI for PRIMERGY Server according to the event type:
– PRIMERGY Server Events
– PRIMERGY Server SNMP Traps
You will find an overview of the policies of the PRIMERGY event groups in the
next section.
The integrated PRIMERGY events are listed in the document “PRIMERGY
Server Events in HPOM“. After the integration package has been installed, you
can open the document using the Start menu Start - Programs - Fujitsu ServerView
Suite - HPOM Integration - IntegratedPRIMERGY Server Events.
You can modify the rules as they exist after the installation or you can define new
ones (see section “Modifying rules for events or creating new ones” on
page 36).
31
4.1.1
Policies of the PRIMERGY event groups
This section provides an overview of the policies of the PRIMERGY event
groups.
Policies of the event group HD MIB
Object:
ServerView Agent Status
Name of the policy group:
FTSPYSVSPI HD MIB
Number of events:
1
Event log:
Application
Source name:
ServerView Agents
Information for displaying the Message group: Hard Disk MIB
event message:
Object: Hard Disk
Policies of the event group Threshold MIB
FTSPYSVSPI Threshold MIB
Number of events:
3
Event log:
Application
Source name:
ServerView Agents
Information for displaying the Message group: ServerView Threshold MIB
event message:
Object: ServerView Threshold
Policies of the event group NTCluster MIB
FTSPYSVSPI NTClusterMIB
Number of events:
13
Event log:
Application
Source name:
ServerView Agents
Information for displaying the Message group: NTCluster MIB
event message:
Object: NTCluster
32
Policies of the event group Server Control2 MIB
FTSPYSVSPI ServerControl2 MIB
Number of events:
42
Event log:
Application
Source name:
ServerView Agents
Information for displaying the Message group: Server Control 2 MIB
event message:
Object: Server Control 2
Policies of the event group X10sureV1 MIB
FTSPYSVSPI X10sureV1 MIB
Number of events:
3
Event log:
Application
Source name:
ServerView Agents
Information for displaying the Message group: ServerView x10sure
event message:
Object: x10sureV1 MIB
Policies of the event group Broadcom LAN Controller
FTSPYSVSPI Broadcom LAN
Number of events:
20
Event log:
System
Source name:
BT /B57W2K
Information for displaying the Message group: Broadcom LAN
event message:
Object: Broadcom LAN Controller BCM57xx
33
Policies of the event group Intel LAN Controller
FTSPYSVSPI IntelLAN
Number of events:
53
Event log:
System
Source name:
E1000/E100B
Information for displaying the Message group: Intel LAN
event message:
Object: Intel LAN Controller PRO1000/
Intel LAN Controller PRO100S
Policies of the event group Duplex Data Manager (DDM)
FTSPYSVSPI DuplexDataManager
Number of events:
38
Event log:
System
Source name:
ddm
Information for displaying the Message group: Duplex Data Manager
event message:
Object: Duplex Data Manager/
Duplex Data Manager Service
Policies of the event group QLogic Fibre Channel Adapter
FTSPYSVSPI QLogicFibreChannel
Number of events:
5 (groups)
Event log:
System
Source name:
ql10wnt, ql1080, ql2100, ql2200, ql2300
Information for displaying the Message group: QLogic Fibre Channel
event message:
Object:
–
–
–
–
34
QLogic Fibre Channel Adapter QLA1040NT
QLogic Fibre Channel Adapter QLA1080NT
QLogic Fibre Channel Adapter QLA2x00NT
QLogic Fibre Channel Adapter QLA2300
Policies of the event group Emulex Fibre Channel Adapter
FTSPYSVSPI EmulexFibreChannel
Number of events:
111
Event log:
System
Source name:
Depends on the controller driver used:
FC Port Driver (Windows 2000, 2003): elxsli2
StorPort Miniport (Windows 2003): elxstor
SCSIPort Miniport (Windows 2000): lpxnds
Information for displaying the Message group: Emulex Fibre Channel
event message:
Object:
– FC Port Driver
– StorPort Miniport
– SCSIPort Miniport
Policies of the event group PowerNet /PowerChute USV von APC
FTSPYSVSPI-PowerNetUSV
Number of events:
39
Event log:
System
Source name:
UPS
Information for displaying the Message group: PowerNet UPS
event message:
Object: PowerNet / PowerChute UPS
35
4.1.2
Modifying rules for events or creating new ones
You can modify the supplied rules for events as necessary or add new ones.
If you want to modify a rule, select the relevant policy group in the folder \Policy
management\Policy groups\SPI for PRIMERGY Server\PRIMERGY Server Events.
Figure 14: Selecting a policy group for events
36
Double-click the selected entry to open the following window:
Figure 15: Specifying the event log name
On the Source tab you must specify the event log name.
On the Rules tab, select the rule you want to modify. Click the Modify... button or
double-click the selected entry to start the modification dialog.
37
Figure 16: Selecting a rule
To create a new rule, click New... to start the creation dialog.
In the following window (see figure 17 on page 39) you define or modify the
conditions for detecting an event (Condition tab) and the actions that you want to
occur in response to an event (Actions tab).
38
Conditions for detecting an event
Figure 17: Modifying a rule: “Condition“ tab
On the Condition tab you can set the following parameters:
Rule description
Title of the rule. The title must be explicit.
The next fields under Specify condition (to match incoming event of type ´Windows
Event Log´) are used to identify the event logs (matching conditions).
Computer
Here you select the name of the managed server. If no specific server is
meant, select <any computer>.
Source
Here you select the source name of the event log group.
Category
Here you select a category from the event log.
Type
Here you select the severity of the event log entry. Possible values:
Information, Warning, Error
39
Event ID
Here you select the number of the event.
Under Format you select the format in which you are specifying the event
ID.
Description
<*> any description; not mandatory.
You only need to make an entry in this field if you want to see a different
text than the one delivered by the event.
40
Defining general actions
Figure 18: Defining an action: “Actions“ tab
On the Actions tab you define what you want to happen when the event is
detected. Only the global reactions are defined in this window. For more
information, see the documentation on HP Operations Manager.
If you click Message..., the Outgoing Message window opens, in which you can set
or change parameters for the reporting of an event to the event browser.
41
Specifying the message
When an event is detected, a message is sent to the active event browser with
the information that you specify in the Outgoing Message dialog box below. To
open it, click Message... on the Actions tab.
Figure 19: Defining a message: “Message attributes“ tab
On the Message attributes tab you can set the following parameters:
Service ID
Not relevant here so leave empty.
Message Key
<$MSG_NODE_NAME>:<$MSG_APPL>:<$EVENT_ID>
The Message Key is formed
– from the name of the node,
– followed by the source name from the event log,
– followed by the event ID.
Message Type
42
Message Group
See event log group
Application
$MSG_APPL
Event source
Object
See event log group
Node
$MSG_NODE_NAME
PRIMERGY server triggering the event
Severity
$MSG_SEV
Replaced by the severity of the event.
The severity from the event log is converted in the message as follows:
Severity in the event log
Severity in the message
Information
Normal
Warning
Warning
Error
Critical
Message Text
$MSG_TEXT
Replaced by the event ID and the description of the event from the event
log.
In this window you can define further parameters for describing an event in the
event browser. For further details see the HP documentation.
43
PRIMERGY server SNMP traps
4.2
You will find an overview of the policies of the PRIMERGY ServerView SNMP
traps in the next section.
The integrated SNMP traps for PRIMERGY and PRIMEQUEST servers are
listed in the document “PRIMERGY Server SNMP Traps in HPOM“. After the
integration package has been installed, you can open the document using the
Start menu Start - Programs - Fujitsu ServerView Suite - HPOM Integration Integrated PRIMERGY Server SNMP Traps.
You can modify the rules as they exist after the installation or you can define new
ones (see section “Modifying rules for SNMP traps or creating new ones” on
page 55).
44
4.2.1
Policies of the PRIMERGY server SNMP trap
groups
An overview of the policies of the PRIMERGY ServerView SNMP trap groups is
provided below:
Policies of the SNMP trap group HD-MIB Traps
FTSPYSVSPI-HDMIBTraps
Number of traps:
1
Information for displaying the Message group: ServerView Agents
event message:
Object: HD-MIB
Policies of the SNMP trap group Threshold-MIB Traps
FTSPYSVSPI-ThresholdTraps
Number of traps:
3
Information for displaying the Message group: ServerView Agents
event message:
Object: Threshold MIB
Policies of the SNMP trap group NTCluster-MIB Traps
FTSPYSVSPI-NTClusterTraps
Number of traps:
13
Information for displaying the Message Group: ServerView Agents
event message:
Object: NTCluster
Policies of the SNMP trap group Server-Control2-MIB Traps
FTSPYSVSPI-ServerControl2Traps
Number of traps:
52
Information for displaying the Message Group: ServerView Agents
event message:
Object: Server Control 2 MIB
45
Policies of the SNMP trap group ServerView RAID MIB
FTSPYSVSPI-ServerViewRAIDTraps
Number of traps:
327
Information for displaying the Message Group: ServerView RAID
event message:
Object: ServerView RAID MIB
Policies of the SNMP trap group Blade Server MMB Traps
FTSPYSVSPI-BladeServerMgmtTraps
Number of traps:
32
Information for displaying the Message Group: Blade Server
event message:
Object: Management Blade
Policies of the SNMP trap group Duplex Data Manager Traps
FTSPYSVSPI-DuplexDataManagerTraps
Number of traps:
6
Information for displaying the Message Group: DDM
event message:
Object: Duplex Data Manager
Policies of the SNMP trap group Broadcom LAN Adapter Traps
FTSPYSVSPI-Broadcom-LANTraps
Number of traps:
1
Information for displaying the Message Group: Broadcom LAN
event message:
Object: Broadcom LAN Adapters
Policies of the SNMP trap group MMBComTrap Traps
FTSPYSVSPI-MMBComTraps
Number of traps:
177
Information for displaying the Message Group: PQ MMB
event message:
Object: MMBComTraps MIB
46
Policies of the SNMP trap group PSAComTrap Traps
FTSPYSVSPI-PSAComTraps
Number of traps:
36
Information for displaying the Message Group: PRIMEQUEST Partition
event message:
Object: PSAComTraps MIB
Policies of the SNMP trap group PSA-ExternalFileUnitTrap Traps
FTSPYSVSPI-PSAExternalFileUnitTraps
Number of traps:
14
Information for displaying the Message Group:PRIMEQUEST Partition
event message:
Object: PSAExternalFileUnitTraps MIB
Policies of the SNMP trap group PSA-LinBcm5700 Traps
FTSPYSVSPI-PSALinBcm5700
Number of traps:
19
Information for displaying the Message group: PRIMEQUEST Partition
event message:
Object: PSALinBcm5700 MIB
Policies of the SNMP trap group PSA-LinEmulexTrap Traps
FTSPYSVSPI-PSALinEmulexTraps
Number of traps:
82
Information for displaying the Message Group:PRIMEQUEST Partition
event message:
Object: PSALinEmulexTraps MIB
Policies of the SNMP trap group PSA-LinGdsTrap Traps
FTSPYSVSPI-PSALinGdsTraps
Number of traps:
16
event message:
Object: PSALinGdsTraps MIB
47
Policies of the SNMP trap group PSA-LinGlsTrap Traps
FTSPYSVSPI-PSALinGlsTraps
Number of traps:
15
event message:
Object: PSALinGlsTraps MIB
Policies of the SNMP trap group PSA-LinGrmpdTrap Traps
FTSPYSVSPI-PSALinGrmpdTraps
Number of traps:
36
event message:
Object: PSALinGrmpdTraps MIB
Policies of the SNMP trap group PSA-LinIb Traps
FTSPYSVSPI-PSALinIb
Number of traps:
77
event message:
Object: PSALinIb MIB
Policies of the SNMP trap group PSA-LinIntelE1000ETrap Traps
PSA-LinIntelE1000ETrap Traps
Number of traps:
31
event message:
Object: PSALinIntelE1000ETraps MIB
Policies of the SNMP trap group PSA-LinIntelE1000Trap Traps
FTSPYSVSPI-PSALinIntelE1000Traps
Number of traps:
31
event message:
Object: PSALinIntelE1000Traps MIB
48
Policies of the SNMP trap group PSA-LinIntelE100 Traps
FTSPYSVSPI-PSALinIntelE100
Number of traps:
25
event message:
Object: PSALinIntelE100 MIB
Policies of the SNMP trap group PSA-LinIntelIgbTrap Traps
FTSPYSVSPI-PSALinIntelIgbTraps
Number of traps:
25
event message:
Object: PSALinIntelIgbTraps MIB
Policies of the SNMP trap group PSA-LinIntelixgbe Traps
FTSPYSVSPI-PSALinIntelixgbe
Number of traps:
33
event message:
Object: PSALinIntelixgbe MIB
Policies of the SNMP trap group PSA-LinLanCom Traps
FTSPYSVSPI-PSALinLanCom
Number of traps:
1
event message:
Object: PSALinLanCom MIB
Policies of the SNMP trap group PSA-LinLsiLogicTrap Traps
FTSPYSVSPI-PSALinLsiLogicTraps
Number of traps:
178
event message:
Object: PSALinLsiLogicTraps MIB
49
Policies of the SNMP trap group PSA-LinScsiComTrap Traps
FTSPYSVSPI-PSALinScsiComTraps
Number of traps:
159
event message:
Object: PSALinScsiComTraps MIB
Policies of the SNMP trap group PSA-LinSvsRaidTrap Traps
FTSPYSVSPI-PSALinSvsRaidTraps
Number of traps:
114
event message:
Object: PSALinSvsRaidTraps MIB
Policies of the SNMP trap group PSA-LinTg3 Traps
FTSPYSVSPI-PSALinTg3
Number of traps:
38
event message:
Object: PSALinTg3 MIB
Policies of the SNMP trap group PSA-LinXframe2 Traps
FTSPYSVSPI-PSALinXframe2
Number of traps:
55
event message:
Object: PSALinXframe2 MIB
Policies of the SNMP trap group PSA-SVAgents Traps
Number of traps:
9
event message:
Object: PSASVAgents MIB
50
Policies of the SNMP trap group PSA-WinBcm5700 Traps
FTSPYSVSPI-PSAWinBcm5700
Number of traps:
10
event message:
Object: PSAWinBcm5700 MIB
Policies of the SNMP trap group PSA-WinDiskMirror Traps
FTSPYSVSPI-PSAWinDiskMirror
Number of traps:
25
event message:
Object: PSAWinDiskMirror MIB
Policies of the SNMP trap group PSA-WinDiskTrap Traps
FTSPYSVSPI-PSAWinDiskTraps
Number of traps:
4
event message:
Object: PSAWinDiskTraps MIB
Policies of the SNMP trap group PSA-WinEmulexTrap Traps
FTSPYSVSPI-PSAWinEmulexTraps
Number of traps:
3
event message:
Object: PSAWinEmulexTraps MIB
Policies of the SNMP trap group PSA-WinGlsTrap Traps
FTSPYSVSPI-PSAWinGlsTraps
Number of traps:
3
event message:
Object: PSAWinGlsTraps MIB
51
Policies of the SNMP trap group PSA-WinIntelE1000expTrap Traps
FTSPYSVSPI-PSAWinIntelE1000expTraps
Number of traps:
31
event message:
Object: PSAWinIntelE1000expTraps MIB
Policies of the SNMP trap group PSA-WinIntelE1000 Traps
FTSPYSVSPI-PSAWinIntelE1000
Number of traps:
31
event message:
Object: PSAWinIntelE1000 MIB
Policies of the SNMP trap group PSA-WinIntelE100 Traps
FTSPYSVSPI-PSAWinIntelE100
Number of traps:
5
event message:
Object: PSAWinIntelE100 MIB
Policies of the SNMP trap group PSA-WinIntele1express Traps
FTSPYSVSPI-PSAWinIntele1express
Number of traps:
12
event message:
Object: PSAWinIntele1express MIB
Policies of the SNMP trap group PSA-WinIntelixgbn Traps
FTSPYSVSPI-PSAWinIntelixgbn
Number of traps:
14
event message:
Object: PSAWinIntelixgbn MIB
52
Policies of the SNMP trap group PSA-WinLsiLogicTrap Traps
FTSPYSVSPI-PSAWinLsiLogicTraps
Number of traps:
6
event message:
Object: PSAWinLsiLogicTraps MIB
Policies of the SNMP trap group PSA-WinMpdTrap Traps
FTSPYSVSPI-PSAWinMpdTraps
Number of traps:
6
event message:
Object: PSAWinMpdTraps MIB
Policies of the SNMP trap group PSA-WinSvsRaidTrap Traps
FTSPYSVSPI-PSAWinSvsRaidTraps
Number of traps:
114
event message:
Object: PSAWinSvsRaidTraps MIB
I
If you want to set up a new policy group for SNMP traps, you must select
SNMP Interceptor as the policy type. For more information on the various
policy types, see the documentation and help for HP Operations
Manager.
Policies of the SNMP trap group PSA-WinXframe2 Traps
FTSPYSVSPI-PSAWinXframe2
Number of traps:
9
event message:
Object: PSAWinXframe2 MIB
53
Policies of the SNMP trap group X10sureV1 Traps
FTSPYSVSPI-x10sureV1
Number of traps:
3
Information for displaying the Message group: ServerView x10sure
event message:
Object: x10sureV1 MIB
54
4.2.2
Modifying rules for SNMP traps or creating new
ones
You can modify the supplied rules for the SNMP traps as necessary or add new
ones.
If you want to modify a rule, select a policy group in the folder \Policy
management\Policy groups\SPI for PRIMERGY Server\PRIMERGY Server SNMP
Traps.
Figure 20: Selecting a policy group for SNMP traps
55
Double-click the selected entry to open the following window:
Figure 21: Selecting a rule
On the Rules tab, select the rule you want to modify. Click the Modify... button or
double-click the selected rule to start the modification dialog.
To create a new rule, click New... to start the creation dialog.
In the following window (see figure 22 on page 57) you define or modify the
conditions for detecting an event (Condition tab) and the actions that you want to
occur in response to an event (Actions tab).
56
Conditions for detecting an event
Figure 22: Modifying a rule: “Condition“ tab
On the Condition tab you can set the following parameters:
Rule description
Title of the rule. The title must be explicit.
The next fields under Specify condition (to match incoming event of type ‘SNMP
Interceptor’) are used to identify the traps (matching conditions):
Node
Here you select the name of the managed server. If no specific server is
meant, select <any node>.
Event object ID
Here you enter the object ID (OID) of the trap.
57
Defining general actions
Figure 23: Defining an action: “Actions“ tab
On the Actions tab you define what you want to happen when an event/trap is
detected. Only the global reactions are defined in this window. For more
information see the documentation on HP Operations Manager.
If you click Message..., the Outgoing Message window opens, in which you can set
or change parameters for the reporting of an event to the message browser.
58
Specifying the message
When a trap is detected, a message is sent to the active event browser with the
information that you specify in the Outgoing Message dialog box below. To open
it, click the Message... button on the Actions tab.
Figure 24: Defining a message: “Message attributes“ tab
On the Message attributes tab you can set the following parameters:
Service ID
Message Key
<$A> <$o>
The Message Key is formed
– from the name of the node that triggered the trap,
– followed by the numeric object identifier (OID).
Message Type
Message Group
See description of the SNMP interceptor group.
59
Application
Object
See description of the SNMP interceptor group.
Node
$MSG_NODE_NAME
PRIMERGY blade server triggering the trap.
Severity
Severity from the MIB. Possible values:
–
–
–
–
–
Normal
Warning
Minor
Major
Critical
Message Text
$MSG_TEXT
Replaced by the trap ID and the message text of the trap.
In this window you can define further parameters for describing an event in the
event browser. For information see the HP documentation.
60
4.3
ServerView tool
ServerView tool
Following the installation, there is a tool available with which you can start the
server management software ServerView Operations Manager of the
ServerView Suite under HP Operations Manager.
ServerView Operations Manager (Single Server/ServerList)
You will find this start tool in the HP Operations Manager console in the directory
Tools/SPI for PRIMERGY Server.
Figure 25: Tool for starting ServerView
You can start whichever management console you want by clicking the
corresponding tool (see section “Starting the ServerView management
console” on page 70).
If you wish, you can modify the configuration of the tool (see section
“Configuring the ServerView start tool” on page 62).
61
ServerView tool
4.3.1
Configuring the ServerView start tool
You can modify the configuration of the ServerView start tool:
– You can adjust the entry in the directory Tools/SPI for PRIMERGY Server, via
which you start the ServerView management console, according to your
requirements.
– You can configure the start tool to enable you to start ServerView Operations
Manager directly for a single server.
If you want to modify the configuration of the start tool, right-click the ServerView
start tool in the directory Tools/SPI for PRIMERGY Server in the HPOM console,
and then select Properties from the context menu. This opens the Properties
window, in which you can make the changes.
Figure 26: “General” tab
On the General tab, you can modify the entry under Tools/SPI for PRIMERGY
Server (see figure 25 on page 61).
The effect of the enabled Show tool in message context option is that the ServerView
Operations Manager tool can also be used in the event browser window of HPOM
via the context menu.
62
ServerView tool
Figure 27: “Details” tab
For more information on starting the ServerView management console, see
section “Starting the ServerView management console” on page 70.
63
ServerView tool
64
5
Configuration and operation
5.1
Distributing and activating the policies
Following installation or after the creation of new policies, the policies must be
distributed over the servers to be monitored (managed nodes) and activated
there. To do this, select the appropriate policy group in the HP Operations
Manager management console.
Figure 28: Selecting a policy
To select the PRIMERGY servers to which the policies are to be distributed,
select All Tasks – Deploy on from the context menu of the relevant policy group.
65
Distribution/Activation of policies
Configuration/Operation
Figure 29: Selecting PRIMERGY servers
Select the PRIMERGY servers on which you want to distribute and activate the
policies.
Click OK to start the distribution of the policies to the selected PRIMERGY
servers. Following the distribution, the policy group is activated by default. If you
do not want to have the policy group activated automatically, you must select
disable policy after deployment.
I
66
The SNMP trap policy groups FTSPYSVSPI-xxxxxxxxTraps only need to be
distributed to and activated on the HPOM management server. In
addition, the SNMP component on the Linux servers must be set such
that the generated traps are sent to the HPOM management server. For
details of how to do this, see the manuals for the Linux servers.
5.2
Displaying events/traps in HPOM console
Displaying the events/traps in the
HP Operations Manager console
Events received from the Windows Event Log can be displayed in the event
browser in the HP Operations Manager console. The figure below shows the
events of an Intel LAN controller (application E100B).
Figure 30: Display showing ServerView events
Double-clicking an entry shows the event in detail. This information is shown in
the following figure.
67
Figure 31: Message properties - displaying event text
The event’s message text is displayed on the Text tab in the Message Properties
dialog. This message describes the error which was reported by the monitored
machine - either by means of a Windows event or an SNMP trap.
68
Figure 32: Message properties - information on possible reactions to the error
Possible reactions to the error which has occurred are described on the
Instructions tab in the Message Properties dialog.
69
Starting the ServerView management consoles
5.3
Starting the ServerView management
console
You can start the ServerView management console under HP Operations
Manager both with the data of the server list and with the data of a server which
you select.
5.3.1
Starting ServerView Operations Manager
You start ServerView Operations Manager by double-clicking the corresponding
tool in the directory Tools/SPI for PRIMERGY Server.
Depending on how the start tool is configured (see section “Configuring the
ServerView start tool” on page 62), one of the following is displayed:
– An additional window, in which you can specify a server that you want to
have displayed directly in ServerView.
– A list of all servers that can be managed via ServerView
70
Specifying managed servers
Figure 33: Selecting a server name
In this case you can have a server displayed directly by selecting the name of
the managed server (in this case FENDER) in the Select the nodes/services to
replace $OPC parameters with: field.
I
All servers which are managed by HPOM are listed and can also be
selected. However, only one PRIMERGY server may be selected.
Specifying the server name and port number
The first time you start ServerView Operations Manager you must specify the
name or IP address of the Web server on which ServerView Operations
Manager is installed, as well as the number of the port via which this connection
is to be established. In order to support the single sign-on feature of the
Operations Manager its account login data is asked here for, too.
71
The following dialog box is displayed:
Figure 34: Specifying the server name and port number
Under Server Name/IP Address, enter the name or the IP address of the server on
which ServerView Operations Manager is installed.
Then under Port No. enter the port number under which ServerView Operations
Manager can be started. With an Apache Web server that ServerView
Operations Manager brings with it on installation, this is the port number 3169
or 3170 when encrypted (SSL). If the Web server (Apache or IIS) is already
installed, it is the port number that was specified when ServerView Operations
Manager was installed.
If the connection to the Web server is established via a secure SSL line (https
protocol), you must enable the SSL switch.
If the ServerView Operations Manager has a login account, you can enter here
its data.
If you also want the dialog to be displayed when ServerView Operations
Manager starts in the future, e.g. to set a different Web server or a different port
number, you must enable the Always show this dialogbox switch.
72
All this information is stored in the file SVOMStart.ini and does not need to be
specified again for the given server during further starts.
I SVOMStart.ini is located in the directory IniFiles in the installation
directory of the ServerView integration pack.
The data for the selected PRIMERGY Server is subsequently displayed on the
ServerView Operations Manager console.
Figure 35: Display of the data of a managed server in the ServerView Operations Manager
(Single System View)
73
If there was no server selected in the ServerView Operations Manager tool, the
ServerView Operations Manager start page is displayed:
Figure 36: ServerView Operations Manager (start page)
To open the main window ServerList of ServerView Operations Manager, click
the ServerList link under ServerList.
74
Figure 37: ServerView Operations Manager (ServerList)
ServerView Operations Manager displays the list of all PRIMERGY servers it
knows in its management area.
5.3.2
Starting ServerView Operations Manager from the
event browser
ServerView Operations Manager can also be started from the event browser of
the managed nodes concerned.
Proceed as follows to do this:
– Right-click the event entry.
– Select the menu item Launch Tool - Message.
75
Figure 38: Select a tool from the event browser
A second dialog is then displayed in which the tools are listed which you can use
in conjunction with the event entry.
Figure 39: Starting ServerView Operations Manager
76
Here you expand the SPI for PRIMERGY Server entry and select ServerView
Operations Manager.
Click Launch...
ServerView Operations Manager is then started with the data of the managed
node from which the event was sent.
77
78

ServerView Integration 4.0 in HP Operations Manager

Transcription

Similar documents

Atsena Otie Key - Mosquito Magnet

Atlantis Energy Systems Inc.

Regions CD Check Viewer Installation Guide

QuadraTec™ - Auralex Acoustics

How to Trap a Leprechaun.pptx - CarrolltonFineArtsFall2013

Glass instructions

Removable prosthesis stabilisation MIB - MInI IMplant

Unit 5 Lesson 3: To Catch a Leprechaun

Epigeal fauna of Bosque Protector Cerro Candelaria