ServerView Blade System Integration Pack for MS …manuals.ts.fujitsu.com/file/10139/sv_in_bladesystem_scom-en.pdf · ServerView Blade System Integration Pack for ... \FTS-PS\INTEGRATIONEN+TOOLKITS\Integration_SCOM

$Page 1: ServerView Blade System Integration Pack for MS …manuals.ts.fujitsu.com/file/10139/sv_in_bladesystem_scom-en.pdf · ServerView Blade System Integration Pack for ... \FTS-PS\INTEGRATIONEN+TOOLKITS\Integration_SCOM$
User Guide - English

FUJITSU Software ServerView Suite ServerView Blade System Integration Pack for MS System Center Operations Manager Version 8.0

Edition February 2018

Comments… Suggestions… Corrections…The User Documentation Department would like toknow your opinion of this manual. Your feedback helpsus 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:2008To ensure a consistently high quality standard anduser-friendliness, this documentation was created tomeet the regulations of a quality management system which complies with the requirements of the standardDIN EN ISO 9001:2008.

cognitas. Gesellschaft für Technik-Dokumentation mbHwww.cognitas.de

Copyright and Trademarks

© c

ogni

tas.

Ges

ells

chft

für

Tech

nik-

Dok

um

enta

tion

mbH

201

7

Pfa

d: P

:\FT

S-P

S\I

NT

EG

RAT

ION

EN

+T

OO

LK

ITS

\Int

egra

tion_

SC

OM

_B

lade

_8.

0\H

and

buch

\us\

sv_i

n_bl

ade

syst

em

_sco

m20

07-e

n.v

or

Copyright 2017 FUJITSU LIMITED.

All rights reserved.Delivery subject to availability; right of technical modifications reserved.

All hardware and software names used are trademarks of their respective manufacturers.

http://www.cognitas.de

mailto:[email protected]

Blade System Integration Pack for MS SCOM

Contents

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1 Purpose and Target groups . . . . . . . . . . . . . . . . . . . 6

1.2 ServerView Suite link collection . . . . . . . . . . . . . . . . . 6

1.3 Documentation for ServerView Suite . . . . . . . . . . . . . . 8

1.4 Notational conventions . . . . . . . . . . . . . . . . . . . . . 8

1.5 Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Integration requirements . . . . . . . . . . . . . . . . . . . 11

3 Installation, configuration and uninstallation . . . . . . . . 13

3.1 Installing ServerView Integration . . . . . . . . . . . . . . . 13

3.2 Installing the Blade System Monitor Service . . . . . . . . . 143.2.1 Installed files . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.2.2 Blade System Monitor Service configuration . . . . . . . . . . 15

3.3 Installing the Management Pack . . . . . . . . . . . . . . . 173.3.1 Installed files . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.3.2 Importing Management Packs . . . . . . . . . . . . . . . . . . 18

3.4 Update to a new version . . . . . . . . . . . . . . . . . . . . 18

3.5 Updating the ServerView Library Management Packs . . . . 18

3.6 SNMP trap configuration . . . . . . . . . . . . . . . . . . . . 193.6.1 Testing the SNMP trap configuration (optional) . . . . . . . . . 21

3.7 Uninstalling ServerView Integration . . . . . . . . . . . . . 223.7.1 Uninstalling the Blade System Monitor Service . . . . . . . . . 223.7.2 Uninstalling the Management Pack files . . . . . . . . . . . . . 23

4 Features of ServerView Integration in SCOM . . . . . . . . 25

4.1 Discovering and monitoring the Blade System Monitor Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Blade System Integration Pack for MS SCOM

Contents

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik-

Dok

umen

tatio

n m

bH 2

009

P

fad:

P:\

FT

S-P

S\IN

TE

GR

ATIO

NE

N+

TO

OLK

ITS

\Inte

grat

ion

_SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sc

om2

007-

en.

ivz

4.2 Discovering and monitoring the Blade System enclosures . 26

4.3 Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264.3.1 Active Alerts view . . . . . . . . . . . . . . . . . . . . . . . . . 274.3.2 Blade Devices State view . . . . . . . . . . . . . . . . . . . . . 284.3.3 Components Health State view . . . . . . . . . . . . . . . . . 284.3.4 Connect Unit State view . . . . . . . . . . . . . . . . . . . . . 294.3.5 Enclosure State view . . . . . . . . . . . . . . . . . . . . . . . 294.3.6 Monitor Service State view . . . . . . . . . . . . . . . . . . . . 294.3.7 Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

4.4 Fujitsu Blade system Enclosure Tasks . . . . . . . . . . . . 314.4.1 Computer Management Console . . . . . . . . . . . . . . . . . 314.4.2 ServerView Operations Manager (Server List) . . . . . . . . . . 314.4.3 ServerView Remote Management . . . . . . . . . . . . . . . . 33

4.5 SNMP traps, events and alerts . . . . . . . . . . . . . . . . . 33

4.6 Knowledge base . . . . . . . . . . . . . . . . . . . . . . . . . 34

5 Working with ServerView Integration in SCOM . . . . . . . . 35

5.1 Authoring pane - Overriding settings for monitoring . . . . . 355.1.1 Changing the settings (example: Blade System Fan Subsystem

monitoring) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355.1.2 Precautions when overriding the settings for the monitoring

interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.1.2.1 Pairwise change of health monitors and monitoring monitors 375.1.2.2 Recommended values for the IntervalSeconds parameter . . 375.1.2.3 Overriding related parameters of the monitoring monitor . . . 38

5.2 Authoring pane - Enabling and disabling alerts . . . . . . . . 38

5.3 Authoring pane - Changing time settings for object discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

6 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

6.1 Creating log files . . . . . . . . . . . . . . . . . . . . . . . . 416.1.1 Discovery and monitoring log files . . . . . . . . . . . . . . . . 416.1.2 Blade System Monitor Service log files . . . . . . . . . . . . . 43

Blade System Integration Pack for MS SCOM 5

1 Introduction The PRIMERGY ServerView Suite from Fujitsu offers numerous ServerView integration modules which enable the PRIMERGY systems and the management software ServerView Operations Manager to be integrated easily into other enterprise management systems.

This manual describes Version 8.0 of the Fujitsu Software ServerView Blade System Integration Pack for MS SCOM, which enables PRIMERGY blade systems to be integrated into the Microsoft System Center Operations Manager 2012 (SCOM 2012).

The Fujitsu Software ServerView Blade System Integration Pack for MS SCOM allows the PRIMERGY blade systems from Fujitsu to be monitored via SCOM. The monitoring of a PRIMERGY blade system is implemented by using the monitors of hardware and software components and is displayed by means of icons.

When the MMB in the Blade Chassis detects errors while monitoring the Blade Chassis hardware and firmware, the errors are forwarded to the Fujitsu PRIMERGY Blade System Monitor Service as SNMP traps. The Fujitsu PRIMERGY Blade System Monitor Service (referred to here as Blade System Monitor Service) writes these errors as event log entries to the event log FujitsuBladeSystemMMB on the local system. SCOM evaluates the event log entries according to predefined rules and displays them as alerts on the SCOM console.

Furthermore, rules can be applied which trigger an appropriate action when an error occurs, e.g. by sending an e-mail providing the hardware support with a description of the error.

6 Blade System Integration Pack for MS SCOM

Introduction

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k01

1.1 Purpose and Target groups

This manual is intended for system administrators, network administrators and service technicians who have a thorough knowledge of hardware, software, and ServerView Operations Manager. Likewise, a sound basic knowledge of the Microsoft System Center Operations Manager is required.

1.2 ServerView Suite link collection

Via the ServerView Suite link collection, Fujitsu provides you with numerous downloads and further information on the ServerView Suite and PRIMERGY servers.

For ServerView Suite, links are offered on the following topics:

● Forum

● Service Desk

● Manuals

● Product information

● Security information

● Software downloads

● Training

I The downloads include the following:

– Current software versions for the ServerView Suite as well as additional Readme files.

– Information files and update sets for system software components (BIOS, firmware, drivers, ServerView Agents and ServerView Update Agents) for updating the PRIMERGY servers via ServerView Update Manager or for locally updating individual servers via ServerView Update Manager Express.

– The current versions of all documentation on the ServerView Suite.

You can retrieve the downloads free of charge from the Fujitsu web server.

For PRIMERGY servers, links are offered on the following topics:


Introduction

● Service Desk

● Manuals

● Product information

● Spare parts catalogue

Access to the ServerView Suite link collection

You can reach the link collection of the ServerView Suite in various ways:

1. Via ServerView Operations Manager.

Ê Select Help – Links on the start page or on the menu bar.

This opens the start page of the ServerView Suite link collection.

2. Via the start page of the online documentation for the ServerView Suite on the Fujitsu manual server.

I You access the start page of the online documentation via the following link:

http://manuals.ts.fujitsu.com

Ê In the selection list on the left, select x86 Servers.

Ê On the right, click PRIMERGY ServerView Links under Selected documents.


3. Via the ServerView Suite DVD 2.

Ê In the start window of the ServerView Suite DVD 2, select the option ServerView Software Products.

Ê On the menu bar select Links.


http://manuals.ts.fujitsu.com


Introduction

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k01

1.3 Documentation for ServerView Suite

The documentation can be downloaded free of charge from the Internet. You will find the online documentation at http://manuals.ts.fujitsu.com under the link x86 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).

1.4 Notational conventions

Screen outputs

Please note that the screen output is dependent in part on the system used and therefore some details may not correspond exactly to the output you will see on your system. You may also see system-dependent differences in the menu items available.

V Warning This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment.

I This symbol highlights important information and tips.

italics Commands, menu items, names of buttons, options, variables, file names, and path names are written in italic letters in the text.


Introduction

1.5 Abbreviations

The following abbreviations are used throughout the manual:

MP Management Pack

SCE (Microsoft) System Center Essentials

SCOM (Microsoft) System Center Operations Manager

SNMP Simple Network Management Protocol


Introduction

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k01


2 Integration requirements The requirements specified below must be satisfied for Integration.

Management station

Microsoft System Center Operations Manager 2012 (R2)

Proxy servers

The Fujitsu Blade System Integration Pack requires that the Fujitsu PRIMERGY Blade System Monitor service is installed on one or more servers with a Windows operating system. The Blade System Monitor Service is needed for accessing the managed blade systems on behalf of the System Center Operations Manager.

For convenience in this document, servers where the Blade System Monitor Service is installed are called “proxy servers”. Any arbitrary server can act as a proxy server if the following conditions are fulfilled:

– Windows Server 2008 (x64) or Windows Server 2008 R2 or Windows Server 2012 or Windows Server 2012 R2 is installed.

– The SNMP Service feature is enabled.

– The SCOM agent is installed.

Managed PRIMERGY servers

Fujitsu PRIMERGY blade system (BX400, BX600, BX900)


Integration requirements

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k02


3 Installation, configuration and uninstallation

3.1 Installing ServerView Integration

The installation package is located on the ServerView Suite DVD under SVSSoftware/Software/Integration_Solutions/SCOM_BL or as a download on the website at: http://download.ts.fujitsu.com/prim_supportcd/SVSSoftware/

At the website navigate to the folder ServerView/Integration Solutions and find the package ServerView Blade System Integration Pack for Microsoft System Center Operations Manager 2012 and 2012 R2. Download the package and expand the ZIP file in an appropriate folder.

The software package includes the following files:

– Blade System Monitor Service 64 bit.exe

– SVISCOM-BL.exe

– Readme_en.pdf

– Readme_jp.pdf

– THIRDPARTYLICENSEREADME.txt

The software package contains two parts to install:

– The Fujitsu PRIMERGY Blade System Monitor Service which runs on one or more proxy servers.

– The Fujitsu PRIMERGY Blade System Management Pack must be installed on the management server and then imported in the SCOM.


Installation, configuration and uninstallation

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k03

3.2 Installing the Blade System Monitor Service

Start the installation program Blade System Monitor Service 64 bit.exe and follow the instructions displayed during the installation process.

3.2.1 Installed files

Default installation path on the proxy server:

%ProgramFiles(x86)%\Fujitsu\ServerView Suite\SCOM Integration\SVISCOM-BL\MonitorService

The installation program copies the necessary files (see table above) and installs and starts the Blade System Monitor Service.

Folder Files

Installation folder BladeLogMsg.dll

converter.vbs

log4cplusU.dll

PRIMERGYBladeSystemMonitor.exe

PRIMERGYBladeSystemSNMP.dll

Readme_en.pdf

comm sub folder ManagedPRIMERGYBlades.xml

config sub folder PRIMERGYBladeSystemConfigSNMP.xml

PRIMERGYBladeSystemConfigSNMP.xsd

S31.traps

log sub folder FujitsuBladeSystemMMB.log

Misc sub folder eula_en.pdf

eula_jp_V2.pdf

SelectBlades sub folder

AddBladeEnclosureToSCOM.exe

AddBladeEnclosureToSCOM.exe.config

Table 1: Installing the Blade System Monitor Service: Default installation path



3.2.2 Blade System Monitor Service configuration

After installing the Blade System Monitor Service of the software package, start the tool AddBladeEnclosureToSCOM.exe:

– In Windows Server 2008, you will find this program under:

Start - All Programs - Fujitsu - ServerView Suite

– In Windows Server 2012, you will find this program under:

Apps - Fujitsu

Figure 1: Configuring the Discovery Service

After the GUI has started, you can configure your desired IP ranges and communities by clicking Configure Discovery Service in the left upper corner.

This opens the Configure PRIMERGY Blade Server Monitor dialog, which allows you to specify different search keys.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k03

Figure 2: Configuring the PRIMERGY Blade Server Monitor

SNMPv1 Community Strings Allows you to configure SNMP community strings.

Discover IP Address ranges Allows you to define IPv4 and IPv6 address ranges to find Fujitsu PRIMERGY blade systems.

If only the Start IP address is configured, then this single address is scanned.

Discover DNS Names Allows you to configure MMB DNS Names to scan the DNS Names for Fujitsu PRIMERGY blade systems.

Ê Click OK to enable your settings.

After configuration is completed, click Restart Discovery.

I Please note:

For IP ranges with more than 256 IP addresses to check, the discovery will take some time.

After the discovery has finished, there should be entries in the left table:

Ê To select a blade system to be monitored, click the corresponding entry in the left table, and then click Add to move the entry to the right table.

Ê To remove a blade system from monitoring, select the corresponding entry in the right table, and click Remove.

Ê Click Apply, to monitor all blade systems shown in the right table.

Now you can install and import the management pack. (see section "Installing the Management Pack" on page 17.)



3.3 Installing the Management Pack

Start the installation program SVISCOM-BL.exe on the system where the SCOM Console is installed and follow the instructions displayed during the installation process.

3.3.1 Installed files

The default installation path on the management station is as follows:

%ProgramFiles%\Fujitsu\ServerView Suite\SCOM Integration

I After installation has finished, it is necessary to restart the SCOM console to enable the environment variables which are used by console tasks (see section "Fujitsu Blade system Enclosure Tasks" on page 31).

I If one or more SCOM Consoles are installed on different computers than the management station, and you intend to use the ServerView Operations Manager console task, install the Management Pack on these computers as well (see section "ServerView Operations Manager (Server List)" on page 31).

I If other Fujitsu Integration Packs are also installed on the SCOM, the Management Packs folder may contain both the old ServerView Core Library (Fujitsu.ServerView.Library.mp) and the new ServerView Core Library (Fujitsu.ServerView.Library.mpb) after installation.

Folder Files

SVISCOM-BL sub folder eula_en.pdf

PRIMERGYBladeSystemEventsSCOM_en.pdf

Readme_en.pdf

SVISCOM-BL.Log.ini

Management Packs sub folder

Fujitsu.ServerView.Library.mpb

Fujitsu.PRIMERGY.BladeSystem.Service.mp

Fujitsu.PRIMERGY.BladeSystem.mp

Table 2: Installing the Management Pack: Default installation path



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k03

Please note that to install the new ServerView Core Library (Fujitsu.ServerView.Library.mpb) it is imperative not to also select the old ServerView Core Library (Fujitsu.ServerView.Library.mp) for import into SCOM. If both libraries are selected, SCOM will not import either of them.

3.3.2 Importing Management Packs

Management packs installed by the ServerView Blade System Integration Pack are located in the Management Packs folder within the installation folder. This folder holds all management packs from ServerView Integration Packs for System Center Operations Manager, and not just from the ServerView Blade System Integration Pack.

PRIMERGY Management Packs are imported in the usual way from the SCOM Console. All Management Packs can be installed simultaneously.

When the management packs have been imported, close the SCOM Console.

I To import the Management Packs, you need SCOM administrator rights.

3.4 Update to a new version

Update installation is not supported by the ServerView Blade System Integration Pack. The process is a full uninstallation of the old version followed by installation of the new version.

For how to uninstall the old ServerView Blade System Integration Pack, see section "Uninstalling ServerView Integration".

For how to install the new ServerView Blade System Integration Pack, see section "Installing ServerView Integration".

3.5 Updating the ServerView Library Management Packs

The ServerView Library Management Pack and the ServerView Image Library Management Pack are used and referenced by all Fujitsu ServerView Integration Packs for System Center Operations Manager.



I If a ServerView Integration Pack contains a newer version of one of the ServerView Library Management Packs, this new version can usually be imported into SCOM without affecting any other Fujitsu ServerView Integration Management Packs.

In the rare case that a new version of one of the ServerView Library Management Packs is not compatible with the old version, you must uninstall all Fujitsu Management Packs, including their Override Management Packs, and reinstall all Fujitsu Management Packs from the Management Packs folder together with the updated ServerView Library and ServerView Image Library Management Packs.

3.6 SNMP trap configuration

To enable the MMBs of the blade systems for receiving alerts from the blade systems, the MMBs must be configured to send traps to the proxy server where the Blade System is configured as SCOM Managed Blade Enclosure.

I All proxy servers must have the SNMP Trap service running.

I To allow the SNMP traps to be sent from the MMB to the proxy server, trap forwarding must be enabled on the MMB.

In the following is shown how to configure the SNMP Trap service via the MMB web interface. For more information, see the user guide for the relevant PRIMERGY blade system.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k03

Proceed as follows:

1. Log on to the MMB of the blade system which is to be monitored, and switch to the settings for SNMP:

Figure 3: Configuring the SNMP Trap service

2. Under Destination IPv4 Address, enter the IP address (IPv4) or the fully qualified domain name of a proxy server as a new trap destination.

I Though the SNMP Trap service receives all traps, only traps with severity level CRITICAL or MAJOR are enabled in the management pack. All traps with severity level MINOR are implemented but disabled in the management pack. They can be enabled in the Authoring pane of the SCOM Operating Console (see section "SNMP traps, events and alerts" on page 33).



3.6.1 Testing the SNMP trap configuration (optional)

You have the option to test the trap communication between an MMB and the proxy server.

Proceed as follows:

1. Log on to the MMB of the blade system that is to be monitored and switch to the configuration settings for SNMP (see page 20).

2. In the SNMP Trap Destination pane, select the proxy server whose communication is to be tested.

3. Click Test.

4. Open the Server Manager on the selected proxy server, and open the Computer Management tool.

5. Navigate to the Event Viewer and expand the Applications and Service Logs folder:

Figure 4: Applications and Service Logs

6. Select the FujitsuBladeSystemMMB log.

7. Look for an log entry with Level = "Information" , Event ID = "1600" and Source = "Blade system MMB service".

If such an entry can be found, this indicates that testing the communication between MMB and the proxy server has been successful.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k03

3.7 Uninstalling ServerView Integration

To avoid alerts in SCOM, the following procedure is recommended:

1. Start the Maintenance Mode for Fujitsu Blade System Enclosures in the Monitoring pane of the SCOM Console:

2. Remove any corresponding override management packs from SCOM. To keep existing override settings, e.g. to re-use in a new version, the override management packs should be exported and saved.

3. Remove the PRIMERGY Blade System Management Packs from SCOM.

I To delete the Management Packs you need SCOM administrator rights.

If other ServerView Integration Packs for System Center Operations Manager have been installed, the ServerView Library Management Packs cannot be uninstalled.

4. Uninstall the Blade System Monitor Service (see section "Uninstalling the Blade System Monitor Service" on page 22).

5. Uninstall the Management Pack files (see section "Uninstalling the Management Pack files" on page 23).

3.7.1 Uninstalling the Blade System Monitor Service

You can uninstall ServerView Integration in two ways:

– Executing the Windows uninstall program on the proxy server(s).

In the Control Panel, call up the installed programs under Add or Remove Programs or under Programs and Features. The following entry will be displayed:

Fujitsu ServerView Blade System Monitoring Service (64 bit)

You can uninstall the Blade System Monitor service here.

– Calling the installation program Blade System Monitor Service 64 bit.exe again.

Start the installation program as if installing, and then uninstall the Blade System Monitor Service.



3.7.2 Uninstalling the Management Pack files

You can uninstall the Management Pack in two ways:

– Executing the Windows uninstall program on the management station.

In the Control Panel, call up the installed programs under Add or Remove Programs or under Programs and Features. The following entry will be displayed:

Fujitsu ServerView Blade System Integration Pack for MS SCOM

You can uninstall the Management Pack here.

– Calling the program SVISCOM-BL.exe again.

Start the installation program SVISCOM-BL.exe as if installing, and then uninstall the integration pack.

After the uninstallation process is complete, all the Registry entries are removed from the server. A few subdirectories and files are left in the installation directory. You can delete them manually.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k03


4 Features of ServerView Integration in SCOM

The Fujitsu PRIMERGY Blade System Management Pack contains the definitions for the SCOM Integration. The management pack is defined by two files: Fujitsu.PRIMERGY.BladeSystem.mp and Fujitsu.PRIMERGY.BladeSystemService.mp.

4.1 Discovering and monitoring the Blade System Monitor Services

A Blade System Monitor Service is discovered if both of the following conditions are met:

– The Blade System Monitor Service is installed on a Windows server (proxy server, see section "Installing the Blade System Monitor Service" on page 14) and this server has been included in SCOM management (installed SCOM agent on the server to be monitored). This is displayed in the Windows Computers view.

– The Blade System Monitor Service has the correct version (8.0.x.x).

When a Blade System Monitor Service is discovered, it will be displayed in the Monitor Service State view (see section "Monitor Service State view" on page 29).


Features of ServerView Integration in SCOM

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k04

4.2 Discovering and monitoring the Blade System enclosures

Discover Blade system enclosures and their components requires the following steps:

1. Using the selection tool AddBladeEnclosureToSCOM.exe, define a list of blade system enclosures that you want to be managed (see section "Blade System Monitor Service configuration " on page 15). The list of managed blade system enclosures is displayed in the right column of the selection tool window.

2. If the Management Pack is imported, the blade system enclosures to be managed are automatically discovered by the SCOM.

4.3 Views

When integrating the management pack, a Blade System Enclosures directory is created under Fujitsu ServerView Systems directory in the Monitoring pane of the SCOM Console. The following views are displayed in this directory:

– Active Alerts– Blade Devices State– Components Health State– Connect Unit State– Enclosure state– Monitor Service State

The health state in all views is displayed by the usual health state icons of the Operations Manager.



4.3.1 Active Alerts view

The Active Alerts view displays all alerts which are assigned to the Fujitsu PRIMERGY Blade System Management Pack and which have the resolution state New.

The following causes can trigger an alert:

● If a monitored blade system or a blade system component is in a critical health state.

This alert is auto-resolving, i.e. as soon as the cause is resolved, the alert is no longer displayed in the view.

● An event for which a rule is defined in the Management Pack is written in the Windows Event Log of a proxy server. The event may be displayed in the following Windows Logs:

– Application and Services Logs / FujitsuBladeSystemMMB

– Microsoft / Operations Manager event log

These alerts continue to be displayed until they are explicitly closed.

I For an overview of the alerts created by rules from events, see the document PRIMERGYServerEventsSCOM_en.pdf, which comes with the product.

I By default, alerts are only generated by events which have been entered in the Windows Event Log (Operations Manager or System) with severity level Critical (Error). Events with severity level Warning can also be displayed if they are enabled by the user (see section "Authoring pane - Enabling and disabling alerts" on page 38).



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k04

4.3.2 Blade Devices State view

The Blade Devices State view displays the health states of all server blades and storage blades in a blade system enclosure. The server blades and storage blades of all managed blade system enclosures are displayed in this view.

The properties of a selected server blade or storage blade are displayed in a window below this view (Detail view).

View specific tasks:

– ServerView Operations Manager– ServerView Remote Manager

For details, see section "Fujitsu Blade system Enclosure Tasks" on page 31.

4.3.3 Components Health State view

The Components Health State view displays the health states of all component sub systems in a blade system enclosure. In more detail, the health states of the following component sub systems are indicated:

– Power supply units– Fan units– Management Blade units– Temperature sensors– KVM units

The health states of the component sub systems of all managed enclosures are displayed in this view.

The properties of a selected component type are displayed in a window below this view (Detail View).






4.3.4 Connect Unit State view

The Connect Unit State view displays the health states of all connection units in a blade system enclosure.

4.3.5 Enclosure State view

The Enclosure State view displays the overall health state of all enclosures.

The properties of a selected enclosure are displayed in a window below this view (Detail view).

I If there are not-printable characters or Unicode characters included in the Detail view properties System Contact or System Location, then the respective property is not displayed correctly.




4.3.6 Monitor Service State view

The Monitor Service State view indicates the health state of the Blade System Monitor Services which are running on the proxy servers.

The properties of the Blade System Monitor Service running on a selected server are displayed in a window below this view (Detail view).

4.3.7 Monitors

The health states displayed in the Enclosure State view and in the Monitor Service State view represent the current health state of the monitored objects like Fujitsu PRIMERGY blade systems or Monitoring services (see section "Enclosure State view" on page 29 and section "Monitor Service State view" on page 29). The health states in each case are determined by a hierarchy of monitors where the health state of each monitor represents a certain aspect of



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k04

the health of the monitored objects. The monitors are not only used for evaluating the overall health state of a blade system but can also be used for failure analysis.

Example

When the overall state of a blade system indicates an error, the error state is displayed in the Enclosure State view. By selecting the affected blade system and clicking on Health Explorer, the SCOM Health Explorer opens and an extract of the monitor hierarchy is displayed. By default, only those monitors are included which are responsible for propagating low level health states to the overall health state. It is thereby possible to trace back the propagation of an error state from the blade system overall state to those component(s) which caused the error (see the figure below).

Figure 5: Tracing back the propagation of an error state

The ServerView Blade System Integration Pack includes numerous monitors whose purpose is not only to model the health state of the target objects but also to indicate the health state of the monitoring system itself. You therefore will be informed when a component of the monitoring system fails which means that the health state of the monitored blade system or individual parts of it cannot longer be evaluated. The monitors indicating the health states of the monitoring system here are named "monitoring monitors". These monitors form their own monitor hierarchies. An error of the monitoring system affects both the Monitor Service overall states and the Enclosures overall state (see section "Monitor Service State view" on page 29 and section "Enclosure State view" on page 29).



4.4 Fujitsu Blade system Enclosure Tasks

Tasks are actions which are displayed in the actions pane of the SCOM console. The displayed tasks depend on the selected view and the highlighted entry within the view. The following task are available:

– Computer Management Console– ServerView Operations Manager– ServerView Remote Manager

4.4.1 Computer Management Console

This task is used to start the Microsoft Management Console (MMC application) and permits access to the data of the highlighted PRIMERGY server.

4.4.2 ServerView Operations Manager (Server List)

This task is used to start the ServerView Operations Manager for displaying the list of all servers managed by the ServerView Operations Manager (Server List).

The first time the software starts, a dialog box is displayed which queries the name of the server on which ServerView Operations Manager is installed (see below).



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k04

Figure 6: Launch PRIMERGY ServerView Operations Manager dialog box

The dialog box is displayed as long as the Always show this dialogbox option is selected.

I If the dialog box is no longer displayed and the address or the credentials of ServerView Operations Manager have changed, use a text editor to open the SVOMStart.ini file in the ini subdirectory of the installation directory. For the variable Dialog related to the corresponding server, replace the value "no" with "yes"

After entering the address and port number of the Operations Manager management station and clicking OK, ServerView Operation Manager is started.

I ServerView Operations Manager prompts you to log in to the ServerView Suite Central Authentication Service. Only after successful login the Server List will be displayed.



4.4.3 ServerView Remote Management

This task is used to call the console of the MMB web interface by using its IPv4 address (if available).

I This function works only if the https port is configured with the standard port number 443 for https ports.

4.5 SNMP traps, events and alerts

As described in section "SNMP trap configuration" on page 19, the MMB of a blade system sends SNMP traps to a proxy server. The Blade System Monitor Service converts the SNMP traps to events which appear in the FujitsuBladeSystem event log of the proxy server.

In the Fujitsu ServerView Blade System Integration Pack, there are rules defined for events which trigger an alert. Alerts remain visible in the Active Alerts view until they are explicitly closed i.e. until they are assigned the resolution state Closed. Events and alerts are independent from monitors and have no influence on the status of the server. They are used only to display an event.

An overview of the integrated events is provided in the file PRIMERGYServerEventsSCOM_en.pdf, which is located in the installation folder.

I Only events with severity level Warning or Critical are integrated.

– An SNMP trap with severity level Critical or Major is mapped to a Windows event with severity level Critical.

– An SNMP trap with severity level Minor is mapped to a Windows event entry with severity level Warning.

Enabling / disabling alerts

By default, all events with severity level Critical generate an alert, and all events with severity level Warning do not generate an alert. You can change these default settings by overriding them in the Authoring section of the SCOM Console. The overrides must then be stored in a Management Pack which is writable.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k04

4.6 Knowledge base

A Knowledge Base is provided for the events and alerts. Depending on the alert, various resolutions / actions are displayed after an error occurred. These resolutions are also contained in the PRIMERGYServerEventsSCOM_en.pdf file, in the last column of the events listed.


5 Working with ServerView Integration in SCOM

5.1 Authoring pane - Overriding settings for monitoring

The settings for monitoring can be changed to some extent for the following blade system subsystems and components:

– Blade System Connection Subsystem– Blade System Enclosure– Blade System Enclosure Monitor Service– Blade System Enclosure Server Blade– Blade System Enclosure Storage Blade– Blade System Fan Subsystem– Blade System KVM Subsystem– Blade System MMB Subsystem– Blade System Connection Subsystem– Blade System Temperature Sensors

5.1.1 Changing the settings (example: Blade System Fan Subsystem monitoring)

Proceed as follows

1. Start the SCOM Console.

2. In the navigation window of the Authoring pane, select Management Pack Objects - Monitors directory.

All available monitors are then displayed in the right-hand window.

3. Navigate to the Blade System Fan Subsystem entry and expand this entry. Then first expand the Entity Health entry and then the Availability entry below.

I The entries are sorted alphabetically. To reduce the number of entries displayed, you can also use the search function.

4. Double-click Blade System Fan Health Monitor to open the dialog box containing the settings for the monitor.


Working with ServerView Integration in SCOM

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k05

5. In the Overrides tab of this dialog box, click Override... and select For all objects of class: Blade System Fan Subsystem.

The Override Properties dialog box opens which contains the properties to be changed.

6. To change a property, proceed as follows:

a) Select the property in the Override column.

b) Change the value of the option in the Override Value column.

You can override the following fan monitoring parameters:

The overrides must be stored in a writable Management Pack. Microsoft recommends not to use the Standard Management Pack. You can create a new Management Pack by choosing New.

I It is recommended to first select the Management Pack in which the override is to be saved.

7. Click OK to save the settings in the selected Management Pack. The dialog is closed.

8. In the subsequent dialog for the monitor, click Close to terminate the configuration of settings

Parameter name Override setting

Alert On State The monitor is in a critical health state. / The monitor is in a critical or warning health state.

Alert Priority High / Medium / Low

Alert severity Critical / Information / Warning / Match monitor's health

Auto-Resolve Alert True / False

Enabled True / False

Generates Alert True / False

IntervalSeconds Time interval (in seconds) at which the monitor monitors the component.

Table 3: Blade System Fan Subsystem monitoring parameters



5.1.2 Precautions when overriding the settings for the monitoring interval

The IntervalSeconds parameter determines the time interval of the SCOM monitoring cycle (see table 3 on page 36). The parameter value is optimized for monitoring Blade System Enclosures.

I Normally, it is not necessary to modify this value and it is urgently recommended not to change the IntervalSeconds parameter. If modifying of the IntervalSeconds parameter is essential though, the precautions described below should be taken.

5.1.2.1 Pairwise change of health monitors and monitoring monitors

The Blade System subsystems and Blade System components are monitored by a pair of monitors:

– The <subsystem> Health Monitor indicates the status of the monitored subsystem or component.

– The <subsystem> Monitoring Monitor indicates whether the monitoring system itself works without failures.

If the parameter IntervalSeconds is changed, it must be changed both on the health monitor and the monitoring monitor of a Blade System subsystem or Blade System component. The IntervalSeconds parameter value must be always the same for both types of monitors.

5.1.2.2 Recommended values for the IntervalSeconds parameter

The default value of the IntervalSeconds is 360 seconds. If changed at all, the value should be increased.

I it should be strictly avoided to operate with monitoring intervals shorter than 360 seconds.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k05

5.1.2.3 Overriding related parameters of the monitoring monitor

The override parameters IntervalSeconds, ConsolidatorCount and ConsolidatorTimeWindow are interrelated and should not be changed individually. If one of these parameters is changed, the remaining parameters must be adjusted in a way that the following conditions are met:

– ConsolidatorTimeWindow = IntervalSeconds * ConsolidatorCount + 120

– IntervalSeconds Ï 360

– ConsolidatorCount Ï 2

5.2 Authoring pane - Enabling and disabling alerts

By default, all events with severity level Critical generate an alert, and all events with severity level Warning do not generate an alert. You can override this default setting.

Each alert can also be detected by means of its title and its Event ID in the PRIMERGYServerEventsSCOM_en.pdf file, which contains detailed information on each event and how to solve the underlying problem.

Proceed as follows:


2. In the navigation window of the Authoring pane, select the Management Pack Objects - Rules directory. All rule groups defined in SCOM are then displayed in the right-hand window.

3. Select the Blade System Enclosure Monitor Service and then click on the alert which is to be enabled or disabled.

I The Enabled by default column displays whether an alert is generated for the event concerned (Yes) or not (No). Alerts which have not been enabled can also be recognized from the grayed-out icon in the first column.

4. Double-click the required alert. A dialog box containing the settings opens.



5. In this dialog box, go to the Overrides tab, click Override... and select For all objects of type: Blade System Enclosure Monitor Service.

The Override Properties dialog box opens which contains the properties to be changed.

6. To enable or disable the alert, proceed as follows:

1. Select the Enabled parameter in the Override column.

2. Change the value of the option in the Override Settings column (False → True or True → False).

The overrides must be stored in a writable Management Pack. Microsoft recommends not to use the Standard Management Pack. You can create a new Management Pack by choosing New.

7. Click OK to save the settings in the selected Management Pack. The dialog box is closed

8. Click Close in the subsequent dialog box for the monitor to terminate the configuration of settings.

I Analogously, you can enable or disable alerts for individual servers. In this case, select For a specific object of class: Blade System Enclosure Monitor Service instead of For all objects of class: Blade System Enclosure Monitor Service. You can then select the required proxy server(s) and proceed as described above.

5.3 Authoring pane - Changing time settings for object discovery

The time period for discovering components of blade system enclosures set by default.

To change these default settings, it is recommended to proceed as follows:


2. In the navigation window of the Authoring pane, select the Management Pack Objects - Object Discoveries directory. All discovery rules defined in SCOM are then displayed in the right-hand window.



© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

200

9 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k05

3. In the Object Discoveries window, select the object discovery you want to change.

I For discovering blade system enclosures, this is the group Discovered type: Blade System Enclosure with the entry Blade System Enclosure Discovery Rule.

4. Double-click the required entry. The Blade System Enclosure Discovery Rule Properties dialog box opens.

5. Select the Overrides tab, and click Override... there.

6. Depending on the change you want to make, select either For all objects of class: Blade System Enclosure Monitor Service or For a specific object of class: Blade System Enclosure Monitor Service:

– If you select For a specific object of class: Blade System Enclosure Monitor Service, the override is carried out only for a specific proxy server.

– If you select For all objects of class: Blade System Enclosure Monitore, all discovered proxy servers are offered for selection. Select the proxy server(s) and click OK.

You can select the required override in the Override Properties dialog box.

I Microsoft recommends not to use the Standard Management Pack to save your changes.

7. To change the time period for the discovery, select the corresponding entry in the Override column.

I You can only change the values containing numbers in the Override Value column.

Enter the new time period (in seconds) for the discovery in the Override Value column (parameter name: Fujitsu PRIMERGY BladeSystem Enclosure DiscoveryDataSource Interval Seconds)

I Microsoft recommends not to use a time interval less than 4 hours for discoveries.

8. Click OK to save the settings in the selected Management Pack. The dialog is closed.

9. Click OK in the subsequent dialog for the monitor to terminate the configuration of settings.


6 Appendix

6.1 Creating log files

For error analysis, log files of the SNMP Trap Collect Service can be created. The Blade System Integration Pack provides three types of log files:

– Discovery log files providing debug information about the SCOM discovery process

– Monitoring log files providing debug information about the SCOM monitoring process

– Blade System Monitor Service log files providing debug information generated by the Fujitsu PRIMERGY Blade System Monitor

6.1.1 Discovery and monitoring log files

Discovery and monitoring logs are enabled via an initialization file with the name SVISCOM-BL.Log.ini. This file resides in the installation directory (see section "Installed files" on page 17).

The log files are stored in the subdirectory SVISCOM\SVISCOM-BL of the directory entered in the system environment variable TEMP. Usually, this is the C:\Windows\TEMP directory. Here, C: represents the system partition.

If the subdirectory SVISCOM\SVISCOM-BL doesn’t exist, the following applies: For each SCOM discovery, a copy of the initialization file with the name SVISCOM-BL.Log.in_ is generated in the %TEMP%\SVISCOM\SVISCOM-BL folder of each proxy server.

SVISCOMLog.ini contains debug options for all discovery and monitoring features of the management pack. The option DebugMode defines whether monitoring for a specific feature is to be activated. The option DebugLevel defines how detailed the debug information is provided.

In case of an error analysis, proceed as follows:

1. On each proxy server, rename the SVISCOMLog.in_ file to SVISCOMLog.ini.

2. Check the debug options for each feature (discovery and monitoring) to be monitored and set them to the desired value.


Appendix

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

201

4 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k06

Example: Settings in the file SVISCOM.BL.Log.ini

[BladeSystemDiscovery]

DebugMode=yes

DebugLevel=15

[BladeComponentsMonitor]

DebugMode=yes

DebugLevel=15

The following log files are created as desired:

– PYBladeSystemDiscovery_<servername>.log– PYBladeSystemMonitor_<enclosureserialnumber>_ConnectUnits.log– PYBladeSystemMonitor_<enclosureserialnumber>_Enclosure.log– PYBladeSystemMonitor_<enclosureserialnumber>_FanUnits.log– PYBladeSystemMonitor_<enclosureserialnumber>_KVMUnits.log– PYBladeSystemMonitor_<enclosureserialnumber>_MMBUnits.log– PYBladeSystemMonitor_<enclosureserialnumber>_PowerSupplyUnits.l

og– PYBladeSystemMonitor_<enclosureserialnumber>_ServerBlades.log– PYBladeSystemMonitor_<enclosureserialnumber>_StorageBlades.log– PYBladeSystemMonitor_<enclosureserialnumber>_TempSensors.log

These files must be sent to the Fujitsu Support for further analysis.

To disable the creation of log files again, delete or rename SVISCOMLog.ini.

Currentness of log files

Log files are generated promptly only if the initialization file is available and the Fujitsu Management Pack is already imported. If the management pack is already imported, log files are generated depending on the execution interval of the discovery or monitoring scripts. Thus, it may take up to 4 hours until all log files are generated.


Appendix

6.1.2 Blade System Monitor Service log files

The log files of the Blade System Monitor Service are stored in the log subdirectory of the installation folder of the Blade System Monitor Service on a proxy server.

By default, the Blade System Monitor Service log file stores only few information. For creating extended log files of the Blade System Monitor Service, you can modify the PRIMERGYBladeSystemConfigSNMP.xml configuration file. This file is located in the config subdirectory of the Fujitsu PRIMERGY Blade System Monitor Service installation folder (see section "Installed files" on page 14).

To modify the Blade System Monitor Service log files, proceed as follows:

1. Edit the file PRIMERGYBladeSystemConfigSNMP.xml with a text editor (e.g. Notepad):

In the <LogFile> ... </LogFile> section, set the value <Threshold><old_value></Threshold> to <Threshold><new_value></Threshold>, where value must be one of the following:

– ERROR (default)– WARN– INFO– TRACE

With INFO you get more information messages, and with TRACE you get additional DEBUG outputs.

2. Restart the Fujitsu PRIMERGY Blade System Monitor Service for the modified values to take effect.

I To disable the creation of Blade System Monitor Service log files, reset the value <Threshold><value></Threshold> to the initial value <Threshold>WARN</Threshold>WARN and restart the Fujitsu PRIMERGY Blade System Monitor Service.


Appendix

© c

ogn

itas.

Ge

sells

chft

für

Tech

nik

-Do

kum

enta

tion

mbH

201

4 P

fad

: P:\F

TS

-PS

\INT

EG

RA

TIO

NE

N+

TO

OLK

ITS

\Int

egra

tion_

SC

OM

_Bla

de

_8.0

\Han

dbuc

h\us

\sv_

in_b

lad

esys

tem

_sco

m2

007

-en.

k06

Documents

ServerView Blade System Integration Pack for MS …manuals.ts.fujitsu.com/file/10139/sv_in_bladesystem_scom-en.pdf · ServerView Blade System Integration Pack for ... \FTS-PS\INTEGRATIONEN+TOOLKITS\Integration_SCOM