Target group

This manual is aimed at system administrators who use ServerView Integration in DeskView to manage Fujitsu Siemens PRIMERGY servers. It is assumed that you are familiar with the following: Operation and management of DeskView. Administration of the operating system (directories, files and symbolic connections). Operation and management of ServerView S2. Interpretation of ServerView SNMP alarm messages.

Background

ServerView S2
ServerView is implemented in heterogeneous networks based on the network management protocol SNMP (Simple Network Management Protocol). ServerView can easily be connected to other management systems (e.g. HP OpenView NNM, IBM Tivoli NetView, Microsoft SMS, Novell ManageWise) via standardized interfaces. ServerView also enables hassle-free integration of Fujitsu Siemens PRIMERGY servers into client-management software such as DeskView. Within the PRIMERGY ServerView Suite, you can use the ServerView S2 server management software for central administration of Intel-based servers. ServerView S2, the Web-based ServerView, makes the data of the managed PRIMERGY server accessible via intranet and Internet. You can view all data of the managed servers from any computer with intranet or Internet access and a current Web browser.

DeskView

DeskView is client management software developed by Fujitsu Siemens Computers. Optimized for Fujitsu Siemens Computers hardware, it helps to minimize the total cost of ownership of managing your client hardware infrastructure. With DeskView you can also manage mobile clients and clients which are periodically not in the network. With its comprehensive client-management functionalities, DeskView is integrated into the software Altiris Notification Server. The complete solution is based on a central database as the singular source of information. The DeskView client software ensures that the clients data and messages are forwarded to the central database and that centrally initiated operations, such as updating the BIOS or power management, can be performed. The central management interface is the Web-based Altiris Console, which can be launched on any system in the network.
At regular intervals, the inventory service of ServerView S2 sends a command to the ServerView agents on the managed PRIMERGY servers, asking whether an update of the inventory data for this server is necessary. If the response is yes, the relevant data is retrieved and stored in the inventory. This routine has been extended for DeskView for Server: Now at the end of the update, the inventory data of the managed PRIMERGY servers is called up from the ServerView database and transferred to DeskView in the standardized CIM XML format. With DeskView for Server, the data relating to all business systems of Fujitsu Siemens Computers - PRIMERGY servers, PCs, notebooks and tablet PCs - is uniformly displayed in DeskView. You can thus use the management functions for all business systems of Fujitsu Siemens Computers in a console.

Further documentation

The information in this manual is supplementary to the user guides for ServerView S2 (see section PRIMERGY ServerView Suite documentation on page 8) DeskView Version 10 (see section Documentation on DeskView and Altiris Notification Server/ Altiris Console on page 14) Altiris Notification Server and Altiris Console (see section Documentation on DeskView and Altiris Notification Server/ Altiris Console on page 14) You should be familiar with these applications and their documentation. Please read the information in the above manuals before you start working with this one.
PRIMERGY ServerView Suite documentation
A comprehensive range of documentation is available on PRIMERGY ServerView Suite e.g.: Server Installation and Deployment PRIMERGY ServerView Suite - ServerStart This documentation provides an introduction to the functioning and user interface of the software components contained in the ServerStart bundle and describes how to install a server system with the help of the ServerStart CD/DVD. RemoteDeploy This documentation describes the installation of RemoteDeploy as well as how to install numerous servers without having to install each one individually. Configuration of the servers and installation of the operating system and user software can be done completely over the network.
Introduction Administration - Product Installation ServerView - Installation
This documentation describes the installation of ServerView S2 and the AlarmService on a management server, and the installation of the ServerView agents on the managed servers. Administration - Health Monitoring ServerView S2 - Server Management This documentation describes the operation of the Web-based ServerView S2, with which you can view all data of the managed PRIMERGY servers from any computer with intranet or Internet access and a standard Web browser. This makes the data of the ServerView agents accessible via intranet and Internet. Administration - Asset Management Inventory Manager This documentation describes the Inventory Manager, a tool available for asset management. The Export Manager allows the inventory data of multiple servers to be exported to Excel, Access or an SQL database. This allows you to search for servers with a specific configuration based on specific criteria. Archive Manager This documentation describes the Archive Manager, a tool available for asset management. The Archive Manager allows the automated recording and central storage of both static and dynamic system and operating data of servers. This archive data can then be displayed and compared.

You will also find additional useful information on the subject of server administration: in the ServerView information files, especially the Readme file, which contains the latest information that could not be included in the manual. The ServerView information files can be called from the ServerView program group by clicking on the corresponding entry. in the operating system documentation in the technical manual for the system boards in the description BIOS setup
Documentation on DeskView and Altiris Notification Server/ Altiris Console
DeskView The current versions of the documentation in PDF format can be downloaded free of charge at: http://www.fujitsu-siemens.com/solutions/business_solutions/manageability/index.html Altiris Notification Server and Altiris Console The current versions of the documentation in PDF format can be downloaded free of charge at: http://www.altiris.com/Altiris/Support/Documentation.aspx
General notational conventions
The following notational conventions are used in this manual:

V Caution I

italic
This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment. This symbol highlights important information and tips.
This symbol refers to a step that you must carry out in order to continue with the procedure. Commands, menu items, names of buttons, options, variables, file names and path names are written in italic letters in text. System output is written using a fixed font. Commands to be entered via the keyboard are written in a semi-bold fixed font. ??? Angle brackets are used to enclose variables which are to be replaced by current values. ??? Keys are presented according to their representation on the keyboard. If capital letters are to be entered explicitly, the Shift key is shown, e.g. [SHIFT] - [A] for A. If two keys need to be pressed at the same time, this is shown by placing a hyphen between the two key symbols.
fixed font semi-bold fixed font <abc> [Key symbols]
Table 1: Notational conventions

References If there are references to text or sections of text in this manual, the chapter or section heading is given in the reference, and the page given refers to the page on which the chapter or section begins.
General notational conventions Screen outputs
Please note that the screen output is partly dependent 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.
Where to get the software, system requirements and installation notes
The DeskView for Server solution allows you to integrate a ServerView S2 environment for managing PRIMERGY servers into a DeskView environment. This integration requires add-ons in both the ServerView S2 and DeskView environments. On the ServerView S2 side, the necessary add-ons are contained in the ServerView installation package as of a specific version (see section ServerView S2 (with component for DeskView for Server) on page 18). On the DeskView side, the solution DeskView for Server has been developed, which is installed into Altiris Notification Server 6.0 (see section DeskView for Server on page 17).
Where to get the software
DeskView for Server is available to download from the Internet: Go to the following Web page: http://www.fujitsu-siemens.com/manageability. Click the links: DeskView-Admin DeskView <version> DeskView <version> for servers Deskview-Altiris downloads.

Preparations

ServerView S2 (with component for DeskView for Server)
ServerView is supplied on the ServerView Suite Software CD. This CD is part of the ServerStart bundle, which comes with any new PRIMERGY server or is available on subscription. You can also download ServerView from the Internet as follows: Go to the following Web page: http://download.fujitsu-siemens.com/prim_supportcd/start.html. You will find the installation file under ServerView Suite ServerView. Click the link: SV_Setup.exe. Save the file SV_Setup.exe.
Requirements, installation notes

2.2.1.1

Requirements and installation notes

Requirements

DeskView for Server requires a DeskView environment. It is installed as a solution into Altiris Notification Server 6.0. For information on the requirements for the environment components listed here, see the relevant DeskView documentation (see section Documentation on DeskView and Altiris Notification Server/ Altiris Console on page 14).
Altiris Notification Server 6.x The Altiris Notification Server in turn requires: Windows server operating system (W2K or Windows 2003 Server) Microsoft SQL Server 2000 SP3 Internet Information Services (IIS) 6.0

DeskView Core Solution DeskView for PC and Mobiles Solution
Requirement for integrated launch of ServerView S2 in DeskView To be able to launch ServerView S2 via the dashboard functionality in DeskView the following is additionally required:
On the system on which the DeskView console was launched, the Java Virtual Machine with which ServerView S2 works must be installed: Java Virtual Machine 1.5
Requirements, installation notes 2.2.1.2 Installation notes
For how to install a DeskView environment and how to install and uninstall a solution - such as DeskView for Server - in Altiris Notification Server 6.0, see the DeskView documentation (see section Documentation on DeskView and Altiris Notification Server/ Altiris Console on page 14).

2.2.2.1

On the ServerView S2 side, the necessary add-ons are included in the ServerView installation package as of the following version:
ServerView S2 version 4.5. For the requirements for ServerView S2, see the ServerView Installation Guide (see section Documentation on DeskView and Altiris Notification Server/ Altiris Console on page 14).
Requirements for data transfer to DeskView
DeskView for Server is only supported for Windows-based ServerView S2Management-Server. For transfer of the server data collected by ServerView S2 to DeskView, a UUID (Universal Unique Identifier) must be set for every server managed by ServerView S2! When the data bound for DeskView is read out of the ServerView database, the system checks for a UUID for each server. If there is no UUID, the process is aborted and no data is transferred to DeskView.
Requirement for integrated launch of ServerView S2 in DeskView To be able to launch ServerView S2 for a specific server, the following is additionally required:
For correct establishment of the URL via which ServerView S2 is to be called from within DeskView, details of the Web server and the SSL encryption must be provided on the ServerView S2 side. As this data cannot be determined automatically from within ServerView S2, you must configure it in an ini file (see section Data for establishing the ServerView S2 URL on page 29). Installation notes

2.2.2.2

For how to install and uninstall ServerView S2, see the ServerView Installation Guide (see section PRIMERGY ServerView Suite documentation on page 8).

Table 2: Parameter to be configured in the file SVInventroyServer.ini
Basically, the transfer of server data from ServerView S2 to DeskView is linked to the update cycle of the ServerView inventory. Thus it may occur from time to time that unchanged data is transferred again. If you want to ensure that a ServerView inventory update is only transferred if the data has changed, you can specify this via an additional parameter: Add the following line to the section [GLOBALS]: DVUpdateOnly=1 Parameter DVUpdateOnly Possible values 0 Default
Data transfer according to 0 update cycle of ServerView inventory Data transfer only if data has changed
Table 3: Parameter to be configured in the file SVInventroyServer.ini
Save and close the file. Configure destination system for data transfer In another ini file you must configure the Notification Server system of your DeskView environment as the destination system for the data transfer. For this you will need the address of the system, the authentication method used for the data transfer, and details of the data transfer.
I Bear in mind that the authentication method must be configured identi-
cally on both communication terminals, i.e. on the ServerView side and the DeskView side.
You will find the file SVUpdateDeskView.ini in the ServerView program folder (e.g. c:\Programs\Fujitsu-Siemens\ServerView\): Windows Scripts/ServerView/SnmpInventory Linux cgi-bin/ServerView/SnmpInventory
Open the file SVUpdateDeskView.ini in a text editor. Search for the section [GLOBALS]. Add the following lines to this section: EnableLogging=0 DVServer=<IP address of Notification Server system> SendData=1 AuthentificationType=basic User=<User name> Domain=<User domain as in \\domain\user> Password=<User password> FileCurlParameters= FileNameSpaces= DataOutfile=<File name of output file> KeepDataOutfile=0 TraceCurl= Parameter EnableLogging DVServer Possible values IP address of the Altiris Notification Server system (with DeskView for Server installed) AuthentificationType User Domain Password FileCurlParameters FileNameSpaces basic ntlm No data transfer, but an output file is created. Data is transferred for Microsoft IIS Web server Default 0 -

SendData

User name of the ID specified for data transfer Domain of the ID specified for data transfer, as \\domain\user Password for the ID that was specified for data transfer Further cURL parameters can be defined in an additional file. (not yet supported)

Table 4: Parameters to be configured in the file SVUpdateDeskView.ini

Parameter DataOutfile

Possible values Name of the output file

Default

Default: tmp_all_profildata_<IP address of a server>.out Part of the name <IP address of a server>.out is automatically created. With this parameter part of the name tmp_all_profildata is changeable. KeepDataOutfile 0 Files which were created for 0 short-term buffer storage are deleted. These files are retained Not activated. 0 Routing and output options are set in a cURL call

1 TraceCurl 0 1

Save and close the file.

Authentication method

Configuring the authentication method
ServerView and DeskView handle their communication via the http protocol. You must therefore configure the authentication method to be used for the data exchange on both sides in the Web server. The default method is standard authentication. Users who are authenticated via the standard authentication method must log on with a valid Windows user name and password.
I To find out how to configure the authentication method, see the
documentation for the Apache Web server or the Windows operating system. Bear in mind that the authentication method must be configured identically on both communication terminals, i.e. on the ServerView side and the DeskView side.

ServerView S2 URL

Data for establishing the ServerView S2 URL
For correct establishment of the URL via which ServerView S2 can be called from within DeskView, details of the Web server and the SSL encryption must be provided on the ServerView S2 side. As this data cannot be determined automatically from within ServerView S2, you must configure it in an ini file. You will find the file AMAddDbValues.ini in the ServerView program folder (e.g. c:\Programs\Fujitsu-Siemens\ServerView\): Windows Scripts/ServerView/SnmpInventory Linux cgi-bin/ServerView/SnmpInventory Open the file AMAddDbValues.ini in a text editor. Configure the following parameters according to the conditions of your ServerView S2 environment: Parameter SV_SSL SV_PortNo Possible values n y No SSL encryption SSL encryption Default n 3169
I These values depend on the
configuration of the WebServer in use!

Any value is possible. The following are proposed: Apache without SSL Apache with SSL IIS without SSL IIS with SSL
Table 5: Parameters to be configured in the file AMAddDbValues.ini

ServerView user ID

DeskView for Server configuration
Configuring DeskView for Server
Entering the ServerView user ID
ServerView S2 transfers the ServerView data to the DeskView installation under a specific user ID. On the system on which the DeskView environment (Altiris Notification Server with DeskView) is installed, you must enter this user ID in the user group DeskViewMTAdministrators.
I For how to set up user IDs, see the documentation for the Windows
operating system. On the Notification Server system, open the user administration: Start Settings Control Panel Administrative Tools Computer Management. Select Local Users and Groups Groups Open the user group DeskViewMTAdministrators by double-clicking it. Add to the user group the user ID under which ServerView S2 transfers its data to DeskView. Close all open windows.
I On the DeskView side you need only configure the authentication
method for the virtual directory DeskView on the preset Web page. A global configuration for all Web pages or directories is not necessary. Bear in mind that the authentication method must be configured identically on both communication terminals, i.e. on the ServerView side and the DeskView side. For how to configure the authentication method, see the documentation for the Apache Web server or the Windows operating system.

ServerView URL

Entering the ServerView S2 URL
To enable integrated?? launching of ServerView S2 via the dashboard functionality in DeskView, you must give DeskView the URL of ServerView S2.
I For the ServerView S2 URL, a few parameters must be set which are a
prerequisite for this functionality (see section Data for establishing the ServerView S2 URL on page 29). On the Notification Server system, open the Altiris Console: Start Programs Altiris Altiris Console. Click the Configuration tab. Select Configuration Solutions Settings Platform Administration ServerView DeskView for Server Configuration.

DeskView for Server integrates the servers managed by ServerView S2 into the resource management of the Altiris Console: In the Altiris Console (see section Launching the Altiris Console on page 35), click the Resources tab.

Display

Navigation
Figure 2: Altiris Console: Resources tab
In the navigation section, select Resource Management Collections ServerView All Primergy Servers. The PRIMERGY servers managed by DeskView for Server are listed in the display area.

Resource Manager

DeskView for Server: Resource Manager
DeskView for Server integrates the ServerView System Data and ServerView Advanced Data tabs in the Resource Manager.
Opening the Resource Manager
In the Altiris Console (see section Launching the Altiris Console on page 35), click the Resources tab. In the navigation section, select Resource Management Collections ServerView All Primergy Servers. The PRIMERGY servers managed by ServerView S2 are listed in the display area. Double-click a PRIMERGY server to open the Resource Manager for this server in a new browser window:
Figure 3: Resource Manager
Information on a specific server
The ServerView System Data tab provides the main data on the selected PRIMERGY server. Open the Resource Manager for the selected PRIMERGY server (see section Opening the Resource Manager on page 37). Click the ServerView System Data tab. The tab opens with a brief overview of the selected PRIMERGY server:

Tabs DfS buttons

Figure 4: ServerView System Data - Summary (DfS = DeskView for Server)
To view detailed information on a particular topic, click one of the buttons at the top of the tab (see figure 4 on page 38). Button Summary Details Mainboard, Graphics, Network, Drives, Software - (Characteristics) Display Quick overview of basic information (e.g. system name, IP address, operating system) All the information on the selected PRIMERGY server in a table Information on the respective topics for the selected PRIMERGY server (Characteristics is currently not yet supported.)
Table 6: Buttons in the Resource Manager
Operating DeskView for Server Further information on the selected topic is displayed:
Figure 5: ServerView System Data - Network
ServerView S2 display for a specific server
Via the ServerView Advanced Data tab of the Resource Manager, you can launch ServerView S2 with all its functions for the selected server.
I Bear in mind that this functionality requires the following conditions:

Figure 9: Reports

Related publications
The documentation for the PRIMERGY manuals can be found on the ServerBooks CD/DVD supplied with each server system. The documentation can also be downloaded free of charge from the Internet: You will find an overview of online documentation available on the Internet at http://manuals.fujitsu-siemens.com/serverbooks/navigation/sv-suite-en.htm. [1] ServerView Suite Basic Concepts PRIMERGY Glossary PRIMERGY Abbriviations Secure PRIMERGY Server Management Enterprise Security PRIMERGY server management for secure, highly available platforms White Paper PRIMERGY ServerView Suite ServerStart User Guide PRIMERGY ServerView Suite RemoteDeploy User Guide PRIMERGY ServerView Suite ServerView Installation User Guide PRIMERGY ServerView Suite ServerView S2 Server Management User Guide PRIMERGY ServerView Suite Local View User Guide

[2] [3] [4]

Related publications [10] PRIMERGY ServerView Suite ServerView S2 Online Diagnostics User Guide PRIMERGY ServerView Suite Inventory Manager ServerView User Guide PRIMERGY ServerView Suite Asset Management Command Line Interface User Guide PRIMERGY ServerView Suite Archive Manager ServerView User Guide PRIMERGY ServerView Suite AlarmService ServerView User Guide PRIMERGY ServerView Suite Performance Manager User Guide PRIMERGY ServerView Suite Download Manager ServerView User Guide PRIMERGY ServerView Suite ServerView RAID Manager User Guide PRIMERGY ServerView Suite GlobalFlash Tool ServerView User Guide
Related publications [19] PRIMERGY ServerView Suite PrimeUp User Guide PRIMERGY ServerView Suite Bootable Update CD User Guide PRIMERGY ServerView Suite ServerView Integration Overview PRIMERGY ServerView Suite ServerView Integration in Microsoft SMS User Guide PRIMERGY ServerView Suite ServerView Integration in Microsoft Operations Manager User Guide PRIMERGY ServerView Suite ServerView Integration in CA Unicenter User Guide PRIMERGY ServerView Suite ServerView Integration in Novell Remote Manager User Guide PRIMERGY ServerView Suite ServerView Integration in HP OV NNM User Guide PRIMERGY ServerView Suite ServerView Integration in HP OV Operations User Guide PRIMERGY ServerView Suite ServerView Integration in Tivoli NetView User Guide PRIMERGY ServerView Suite ServerView Integration in Tivoli/TEC User Guide

Related publications [30] PRIMERGY ServerView Suite RemoteView User Guide PRIMERGY ServerView Suite integrated Remote Management Controller (iRMC) User Guide Baseboard Management Controller (BMC) Configuration for PRIMERGY Systems User Guide RemoteView Service Board Installation Guide RemoteView Service Board S2 User Guide RemoteView Service Board S2 Installation Guide PRIMERGY BX300 Blade Server System Operating Manual PRIMERGY BX600 Blade Server System Operating Manual PRIMERGY Blade Server System RemoteView Management Blade User Interface Description User Guide PRIMERGY Blade Server System LAN Switch Blade User Interface Description User Guide BIOS-Setup Description PRIMEPOWER ServerView Suite System Administration within a Domain User Guide
Related publications [42] DuplexDataManager fr Windows NT DuplexWrite Product Manual DuplexDataManager for Windows NT MultiPath Product Manual DuplexDataManager for LINUX DuplexWrite Product Manual APC network management card Users Guide VMware ESX Server Installation Guide VMware ESX Server Administration Guide
A Altiris Console, launching Altiris Notification Server, documentation 14 authentication 28, 31 B background 6 DeskView 7 DeskView for Server 7 ServerView SC configuration DeskView for Server 30 ServerView ScURL 25 D DeskView background 7 DeskView for Server 7 documentation 14 DeskView for Server authentication method 31 configuring 30 data transfer from ServerView Sinstallation notes 20 reports 44 requirements 19 resource manager 37 server information 38 server list 36 ServerView S2 40, 42 ServerView S2 URL 32 ServerView user ID 30 where to get documentation Altiris Notification Server DeskView 14 further 8 ServerView Suite 8 F further documentation I installation notes 19 DeskView for Server ServerView Sintroduction 14
L launching Altiris Console 35 resource manager (DfS) ServerView SM manual further 8 structure 5 N notational conventions 15
R reports (DfS) 44 requirements 19 DeskView for Server 19 ServerView Sresource manager (DfS) 37 opening 37 server information 38 ServerView S2 40
Index S server information (DfS) 38 server list (DeskView for Server) 36 ServerBooks DVD 13 ServerView S2 authentication method 28 background 6 configuration 23 data transfer to DeskView for Server 24 in DeskView for Server 40, 42 installation notes 21 requirements 20 ServerView S2 URL 29 where to get 18 ServerView Suite, documentation 8 software, where to get 17 structure of the manual 5 T target group 6 29, 32

U URL, ServerView S2 URL user ID 30
W where to get DeskView for Server 17 ServerView Ssoftware 17

Index. 83

Introduction

The PRIMERGY ServerView Suite from Fujitsu Technology Solutions offers numerous ServerView integration modules which enable the PRIMERGY servers and the management software ServerView Operations Manager to be integrated easily into other enterprise management systems. This manual describes Version 4.0.3 and 4.0.4, which enables ServerViewOperations Manager to be integrated into the Microsoft System Center Operations Manager 2007 (SCOM 2007). The integration of ServerView permits the PRIMERGY servers from Fujitsu Technology Solutions to be managed via SCOM. Monitoring of a PRIMERGY server is implemented using the monitors of hardware and software components and is displayed by means of icons. If errors occur during hardware monitoring of a PRIMERGY server, the ServerView Agent enters these as event entries in the Windows Event Log of the managed server. The SCOM Agent which is located on the monitored systems sends these events to the SCOM Management Station, where they are evaluated and displayed on the SCOM Console by the Management Pack in accordance with the settings. Furthermore, rules can be applied which trigger an appropriate action when an error occurs, e.g. sending a mail describing the error to hardware support. For detailed analysis, the ServerView Operations Manager, for example, can be started from the SCOM Console. If the SCOM software is already installed on the management station on which ServerView Operations Manager is to be installed, integration occurs automatically when ServerView Operations Manager is installed (provided this has been set by the user). The current ServerView Integration in SCOM 2007 is provided on the latest PRIMERGY ServerView Suite DVD1 from Fujitsu Technology Solutions.

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 2007 is required.
Changes since the previous version
In version 4.0.4 the maximum number of instances of a component that can be recognized and monitored has been increased from 32 to 64. From the viewpoint of the Operations Manager, Version 4.0.3 and 4.0.4 of the integration package in Microsoft Operations Manager 2007 are completely new packages compared to the previous versions 4.0.1/4.0.2 because the classes have been renamed. It takes the interests of the Operations Manager and Fujitsu into account when naming the classes. The monitoring component UPS is no longer supported. How the settings from Version 4.0.1/4.0.2 can be transferred to this new version in the case of an update is described further below.

Notational conventions

The following notational conventions are used in this manual:

V Warning I

italics
This symbol points out hazards that can lead to personal injury, loss of data or damage to equipment. This symbol highlights important information and tips.
This symbol refers to a step that you must carry out in order. Commands, menu items, names of buttons, options, variables, file names, and path names are written in italic letters in the text. Specifications between angle brackets indicate variables which are replaced by values.

<variable>

Table 1:
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. 8

Integration requirements

The requirements specified below must be satisfied for Integration. Management stations
Microsoft System Center Operations Manager 2007 SP1 or Microsoft System Center Operations Manager 2007 R2 Windows Server 2003 SP1 / SP2 or Windows Server 2008 SP2 or Windows Server 2008 R2 SQL Server 2005 SP1 / SP2 / SP3 or SQL Server 2008 SP1

Managed PRIMERGY servers

Windows Server 2003 or Windows Server 2008 ServerView Agent >= V4.70.06 Windows Management Instrumentation (WMI) Management Controller iRMC S2 (for power consumption) Redundant power supply (for power consumption)
Integration requirements Setting trap severities for ServerView Agents To permit ServerView events to be displayed in SCOM, they must be written to the Windows Event Log. For this purpose the required trap severities must be enabled for the ServerView Agents. Using the start menu function Start Programs Fujitsu ServerView Agents Configuration Tools Agents Configuration open the dialog box below, and in the Trap Forwarding tab enable the required trap severities under Report to system event log.
Figure 1: Setting trap severities for ServerView Agents
Installation and uninstallation
Installing ServerView Integration
Installation in the context of ServerView Operations Manager installation If the necessary software requirements for Integration are satisfied on the management station when ServerView Operations Manager is installed (see page 9), you can set ServerView Integration in SCOM in the Installation Wizard of ServerView Operations Manager. In this case the Integration module is installed automatically in conjunction with ServerView. For further information on this subject, please refer to the ServerView Operationss Manager Installation manual.

Manual import

Start the SCOM Console and, under Administration Management Packs in the navigation window, select the menu item Import Management Packs in the context menu.
Figure 3: Importing Management Packs manually (extract)
The Select Management Packs to import dialog is opened. Switch to the directory in which you installed the Integration package (normally <program files>\Fujitsu\ServerView Suite\SCOM Integration). Select the Fujitsu.Servers.PRIMERGY.mp file. Click on Open.
Figure 4: Selecting the Management Pack
Importing Management Packs The Import Management Packs dialog is opened.
Start the import procedure by clicking on Import.
Figure 5: Starting the import procedure
After the Management Pack has been successfully imported, the Cancel button is replaced by the Close button. Click on Close to terminate the import procedure.
Uninstalling ServerView Integration
If the Fujitsu.Servers.PRIMERGY.Overrides.xml and Fujitsu.Servers.PRIMERGY.EventRules.Overrides.xml Management Packs are also to be imported, the same procedure must be repeated with the files concerned.
ServerView Integration is uninstalled in two steps: Execution of the Windows uninstall program Manual removal of the PRIMERGY Management Packs (if they have already been imported)
I You need SCOM administrator rights to remove the Management Packs.
3.3.1 Executing the uninstall program
Click the Start button and open the Windows routine Add or Remove Programs via Settings Control Panel. Use the Remove button there to start the uninstall program.
Figure 6: Windows installation/uninstallation routine
Once the uninstall procedure has been completed, all registry entries and installed files for ServerView Integration will have been removed from the system. If the PRIMERGY Management Packs had already been imported, they are still contained in SCOM 2007 and must be removed manually.
Removing Management Packs
Start the SCOM Console and in the Administration navigation window select the Management Packs folder. All the imported Management Packs are then displayed in the window next to this.

Detecting the hardware components
The hardware components of a PRIMERGY server which are listed below can be detected and monitored. 4.4.1.1 PRIMERGY Overall State
This component is used to display and monitor the overall state of a PRIMERGY server. Components which are not detected by the hardware components described below may possibly also be monitored here.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 2: Information PRIMERGY Overall State <Name of server> <IP address of RMC> ServerView Overall State

4.4.1.2

Processors / Cores
The CPUs which exist physically are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 3: Information Processors <Name of server> <IP address of RMC> <Names of physical CPUs> <Type/Number of cores>
Properties 4.4.1.3 Memory
The memory modules which are connected are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 4: Information Memory <Name of server> <IP address of RMC> <Names of memory modules> <Total available RAM>

4.4.1.4

Storage
The following storages are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 5: Information Storage <Name of server> <IP address of RMC <Name of mass storage> <Capacity of individual mass storages>

4.4.1.5

Ethernet Network Adapters
The following Ethernet Network Adapters are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 6: Information Networks (Ethernet) <Name of server> <IP address of RMC> <Names of Ethernet Network Adapters/Interfaces> <MAC addresses>

Detecting and monitoring the components 4.4.1.6 Remote Management Controller
The existing Management Controller is detected and the health state monitored on the monitor. The best possible monitoring is only provided for the iRMC.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 7: Information Management Controller <Name of server> <IP address of RMC> <Type> Firmware Version: <Version>

4.4.1.7

Fans/Cooling
The connected fan modules of the PRIMERGY server and any disk extension modules are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 8: Information Fans (Cooling) <Name of server> <IP address of RMC> <Names of fans>

4.4.1.8

Temperature Sensors
The temperature sensors which exist physically are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 9: Information Temperature Sensors <Name of server> <IP address of RMC> Temperature <n>: <Name of sensor> Current Temperatures (Celsius): <Name>; <Temperature>
Properties 4.4.1.9 Power Supply
The power supply modules which exist physically are detected, their data displayed, and the health state monitored on the monitor.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 10: Information Power Supplies <Name of server> <IP address of RMC> Power Supply<nn>
4.4.1.10 Power Consumption The power consumption is monitored. If the current value exceeds a particular threshold of the nominal value, the monitor reports the Error state. At least one of the following requirements must be satisfied on the monitored PRIMERGY server for Power Consumption to work: Management Controller iRMC S2 must be installed. A redundant power supply must be available.
Icon Name: Server Name: RMC IP Address: Component(s): Component(s) Info: Table 11: Information Power Consumption <Name of server> <IP address of RMC> Power Consumption Nominal (W): <nnn>; Current (W): <nnn>; Performance Status: <Mode>

Events and alerts

Rules are only defined for events which trigger an alert. Alerts remain visible in the Active Alerts view until they are resolved by an associated event. This can be done manually by assigning the resolution status Closed. Events and alerts are independent of monitors and have no influence on the status of the server. They are used only to display an event. The following event groups are integrated:
TRAP.MIB SC2.MIB HD.MIB NTCluster.MIB ServerView Raid Duplex Data Manager (DDM) ServerView Services (Management Blade Traps of S31.MIB) QLogic Fibre Channel Adapters Emulex Fibre Channel Adapters Broadcom Network Adapters Intel Network Adapters
A detailed overview of the integrated events is provided in the PRIMERGYServerEventsSCOM_e.pdf file, which is contained on the installation medium and can be found in the target directory after installation. Only events with the severity Warning or Error are integrated.
SNMP trap integration for blade server MMB
The traps/events of the Management Blade (MMB) of blade servers BX6xx are integrated via SNMP traps of the S31 MIB. These traps must be generated via the ServerView Event Manager (previously AlertService) in Event Log entries on the server monitored by SCOM. To permit this the ServerView Event Manager must be installed and configured appropriately.
I A detailed description of the ServerView Event Managers filter settings
is provided in the EventManagerConfiguration_e.PDF file, which is contained on the installation medium and can be found in the target directory after installation. The Management Blades traps are compressed to three entries in the ServerView Event Manager:
Information Traps (Event ID = 1; Severity = Information) Not supported in the SCOM Management Pack Minor/Major Traps (Event ID = 2; Severity = Warning) Critical Traps (Event ID = 3; Severity = Error)
Consequently the problem which has occurred can only be assigned precisely via the descriptive text of the Event Log entry. Information on the events and actions after the error occurred is available in the Knowledge Base of the Management Pack and can be displayed there.

Setting a filter for the events of the MMB of a blade server
A Management Blades SNMP traps cannot be received directly in the Management Pack and displayed on the SCOM Console. To make this possible, the events of the ServerView Event Manager are defined in the Management Pack, namely for the severities Warning and Error. The ServerView Event Manager is able to write the SNMP traps received to the Event Log on the PRIMERGY server. To do this it compresses these SNMP traps to two events with the severities Warning and Error. Normally all incoming SNMP traps are converted into Event Log entries there, but this would generate too many alerts on the SCOM Console. A filter must be set to ensure that the ServerView Event Manager enters only the events of the MMB of a blade server as events. A description of how you can set this filter is provided in the EventManagerConfiguration_e.pdf file, which is contained on the installation medium and can be found in the target directory after installation.
Enabling and disabling alerts
By default all events with the severity Error generate an alert, and all events with the severity Warning generate no alert. You can change these default settings in two ways: By overriding them in the authoring area of the SCOM Console The overrides must then be stored in a Management Pack which is not writeprotected. This should preferably be done in the Fujitsu.Servers.PRIMERGY.Overrides Management Pack supplied. By editing and importing the Fujitsu.PRIMERY.Servers.EventRules.Overrides Management Pack Detailed information is provided in the sections Authoring Enabling and disabling alerts on page 64 and Enabling and disabling alerts by editing a special Override file on page 69.

Knowledge Base

A Knowledge Base is provided for the events and alerts. Several possible resolutions / actions after error are feasible.
Figure 32: Example of a Knowledge Base for an alert for a defective fan
The resolutions are also contained in the PRIMERGYServerEventsSCOM_e.pdf file, in the last column of the events listed.
Working with ServerView Integration in SCOM

Monitoring Active Alerts

All generated alerts which are assigned to the PRIMERGY servers and their components are displayed in the Active Alerts view in the Monitoring area.

Displaying properties of an alerts
When you want to view the properties of an alert in the overview, select the alert entry in the table. All the properties of the alert are then displayed in the Alert Details window below the table.
Figure 33: Displaying properties of an alert

Working with Integration

To view all the properties of an alert, double-click on the alert entry concerned with the left mouse button or highlight it with the right mouse button and select the menu item Properties. The Alert Properties dialog is opened.
Figure 34: Alert Properties dialog

Executing tasks

Select an alert to execute the following tasks for the PRIMERGY server concerned: Computer Management Remote Desktop Remote Desktop (Console) ServerView Operations Manager (Server Name) ServerView Operations Manager (Server List) ServerView Raid Manager ServerView Remote Management iRMC S2
Setting a user-defined view
If you want to define personal settings for the Active Alerts view, select the menu item Personalize view.
Figure 35: Menu item Personalize view
The Personalize View dialog opens. Here you select the columns which are to be displayed and define their position in the view:
Figure 36: Personalize View dialog
You can enable or disable a column by enabling or disabling the options (check mark set/not set). You can move a column in the table to the left or right using the two blue arrows (on the right above the selection list).
I Personal settings are a function of SCOM. They apply for the registered
user and are not lost when the Management Pack is removed. When the Management Pack is imported again, these personal settings are available again and determine the appearance of the tables in the views.

Deleting an alert

Alerts remain in the Active Alerts view until they are deleted with Closed. To do this, right-click on the alert entry, select the Set Resolution State entry in the context menu which then opens and then click on Closed.
Figure 37: Deleting an alert
Monitoring Components Health State
The state of all hardware components of the PRIMERGY servers is displayed in the Monitoring area of the Components Health State view.
Select a component to execute the following tasks for the PRIMERGY server concerned: ServerView Operations Manager (Server Name) ServerView Remote Management iRMC S2 ServerView Raid Manager
Proceed in the manner described under Active Alerts (see page 57) to set a userdefined view.
Monitoring Server Groups State
The states of the servers in the various PRIMERGY groups are displayed in the Monitoring area of the Server Groups State view.

Monitoring Servers State

The states of all PRIMERGY servers are displayed in the Monitoring area of the Server State view.

Authoring Monitoring settings
Authoring Overriding settings for monitoring
The settings for monitoring can to some extent be changed for the following server components: Fans (PRIMERGY Component) Management Controller (PRIMERGY Component) Memory (PRIMERGY Component) Networks (PRIMERGY Component) Power Consumption Monitor (PRIMERGY Component) Power Supplies (PRIMERGY Component) Processors (PRIMERGY Component) Storage (PRIMERGY Component) Temperature Sensors (PRIMERGY Component) RAID Subsystem PRIMERGY Overall State
Changing the settings, taking fan monitoring as an example Start the SCOM Console and in the navigation window of the Authoring area select the Management Pack Objects -> Monitors directory. All the available monitors are then displayed in the right-hand window. Select the Fans (PRIMERGY Component) component and expand the Availability entry. Double-click on PRIMERGY Fans Collection Health Monitor.
Figure 38: Selecting the monitor for changing the settings
A dialog with the monitors settings opens. In this dialog go to the Overrides tabs, click on the Override button there and select For all objects of type: Fans (PRIMERGY Components).
Figure 39: Overrides tab in the Monitors dialog
The Override Properties dialog containing the properties which are to be changed opens. To change a property enable the checkbox in the Override column by setting a check mark change the value in the Override Settings column enable the checkbox in the Enforced column by setting a check mark so that the changed setting is definitely implemented
Figure 40: Changing monitor settings
Authoring Enabling and disabling alerts
You can override the following fan monitoring parameters: Parameter Name Enabled Generates Alert Alert Priority Alert On State Alert Severity DebugString Override Setting True / False True / False High / Medium / Low (Descriptive text) Critical / Warning / Information YES / NO Defines whether a log file is generated for component monitoring (Seconds) Interval at which the monitor monitors the component
Auto-Resolve Alert True / False

IntervalSeconds

The overrides must be stored in a writable Management Pack. The Fujitsu.PRIMERGY.Servers.Overrides Management Pack should preferably be used here. Click on the OK button. The settings are then saved in the Management Pack selected and the dialog is closed. Terminate this specification of settings by clicking on the Close button in the subsequent dialog for the rule.
By default all events with the severity Error generate an alert, and all events with the severity Warning generate no alert. You can change this default value by means of an override. Each alert can also be detected by means of its title and its user ID in the PRIMERGYServerEventsSCOM_e.pdf file. Here you will find detailed information on each event and on how to solve the problem.
Figure 41: PRIMERGYServerEventsSCOM_e.pdf file
Start the SCOM Console and in the navigation window of the Authoring area select the Management Pack Objects -> Rules directory. All the rule groups which are defined in the SCOM Manager are then displayed in the right-hand window. Select the Fujitsu PRIMERGY Server group and then click on the alert which is to be enabled or disabled.
Figure 42: Selecting an alert for processing
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.
Authoring Enabling and disabling alerts A dialog containing the monitor settings is opened.
In this dialog switch to the Overrides tab, click on the Override button there and select For all objects of type: Fans (PRIMERGY Components).
Figure 43: Overrides tab in the Monitors dialog
The Override Properties dialog containing the properties which are to be changed is opened. To enable or disable the alert enable the checkbox in the Override column for the Enabled parameter by setting a check mark change the value in the Override Settings column (True <-> False) enable the checkbox in the Enforced column by setting a check mark so that the changed setting is definitely implemented
Figure 44: Changing an alert setting
These settings must be stored. In the Select destination management pack line select an overwritable Management Pack. You can use the installed Fujitsu PRIMERGY Servers Overrides Management Pack for this purpose. When you confirm using the OK button, the settings are saved in the Management Pack selected. Terminate the definition of settings by clicking on the Close button in the subsequent dialog box for th rule.
I The rule is still displayed as disabled in the Management Pack.

Appendix

Enabling and disabling alerts by editing a special Override file
In the Management Pack all the PRIMERGY events with the severity Error which are recorded generate an alert. However, the events with the severity Warning which are recorded do not generate an alert. You can use an Override file, in which rules are defined which override (enable or disable) the recorded alert rules, to enable or disable a large number of alerts. Procedure: Let us assume that you want to disable the event with the event ID 12005 which has the severity Error and is therefore enabled in the Management Pack. This rule can be detected by means of its title and its event ID in the PRIMERGYServerEventsSCOM_e.pdf file.

Figure 45: Event description in the PRIMERGY ServerEventsSCOM_e.pdf file
The ID for this event is SC2_MIB_12005. Use a text editor to open the Override file Fujitsu.Servers.PRIMERGY.EventRules.Overrides.xml. All the alert rules which are contained in the Fujitsu PRIMERGY Servers Management Pack are also defined in this file, but they are not enabled; they are commented out by the XML comment character combination "<!--" and "-->".
PRIMERGY servers supported
Figure 46: Alert rule in the Override file
Remove the two comment characters and save the file under the same name (please back up the original file first under a different name). Then import this file via the SCOM interface menus in the Administration area (see the section Manual import on page 14). After the import operation, the rule for event 12005 of the SC2 MIB is disabled and no longer generates an alert. Proceed in the same way for all the other rules which you want to enable or disable.
I You are responsible for changes to this file. In this case Fujitsu
Technology Solutions shall assume no guarantee for the subsequent releases of the Integration package. This shall apply in particular when the modified file is exported before a change of version of the package and imported again after a change of version of the package.
PRIMERGY BX300 (Single und Dual Blades) PRIMERGY BX620 (INTEL 2-way Blade) formerly known as PRIMERGY BX600 Dual PRIMERGY BX620 S2 (INTEL 2-way Blade) formerly known as PRIMERGY BX600S2 Dual PRIMERGY BX620 S3 PRIMERGY BX620 S4 PRIMERGY BX620 S5 PRIMERGY BX630 (AMD 2-/4-/8-way Blade) PRIMERGY BX630 S2 (AMD 2-/4-way Blade) PRIMERGY BX660 (INTEL 4-way Blade) formerly known as PRIMERGY BX600 Quad PRIMERGY BX920, BX 922

Appendix

Entries in the Operations Managers Event Log
PRIMERGY RX100, RX100 S2, RX100 S3, RX100S4, RX100S5, RX100S6 PRIMERGY RX200, RX200A, RX200 S2, RX200 S3, RX200S4, RX200S5 PRIMERGY RX300, RX300 S2, RX300S3, RX300S4, RX300S5 PRIMERGY RX330
PRIMERGY RX600, RX600 S2, RX600S3, RX600S4 PRIMERGY RX800 (+ Update), RX800S2, RX800S3 PRIMERGY TX100S1 PRIMERGY TX120, PRIMERGY TX120S2 PRIMERGY TX150, PRIMERGY TX150 SATA, TX150 S2, TX150 S3, TX150 S4, TX150S5, TX150S6, TX150S7 PRIMERGY TX200, TX200 S2, TX200 S3, TX200 S4, TX200S5 PRIMERGY TX300, TX300 S2, TX300 S3, TX300 S4, TX300S5 PRIMERGY TX600, TX600 S2, TX600 S3 PRIMERGY ECONEL 40, ECONEL 50 PRIMERGY ECONEL 100, ECONEL 100 S2 PRIMERGY ECONEL 200, ECONEL 200 S2 PRIMERGY ECONEL 230R S1 PRIMERGY S30 PRIMERGY S40 S40ES S40BS PRIMERGY SX35 (Orca-J) PRIMERGY SX40 PRIMERGY S60 PRIMERGY S80

below the server cannot be monitored.
EventID Severity Message text 100 Error Description/Action Components monitoring script was Not enough input parameters were called with not enough arguments. specified when the script was called. Contact the local Fujitsu customer service. 101 Error Fujitsu PRIMERGY Server <server No ServerView Agent is installed. name> has no ServerView agent Install a ServerView Agent >= installed. 4.70.06 Fujitsu PRIMERGY Server <server A ServerView Agent < 4.70.06 is installed. name> has a ServerView agent installed whose version is not Install a ServerView Agent >= supported. 4.70.06 Unable to connect WMI: /root/default:StdRegProv. Check if the WMI service is enabled and running, and ensure this WMI namespace exists on <server name>. The WMI name space could not be opened. Check whether the WMI service is installed and has been started.
A PRIMERGY component cannot Warning PRIMERGYComponentsbe monitored because no valid Monitor.vbs: <component instance name>: The Status of <component> state is recognized. is undefined (<wmi provider name>). Contact the local Fujitsu customer service.

Creating log files

Log files can be created for error analysis. An initialization file with the name SVISCOMLog.ini is provided for this purpose. This file resides in the IniFiles subdirectory of the installation directory. Proceed as described below to perform error analysis using the log files Copy the SVISCOMLog.ini file on the PRIMERGY server for which an anylsis is to be performed to the c.\temp directory. If an installation directory with the name SVISCOMLog.in_ already exists there, please rename this SVISCOMLog.ini. The log files are stored in the directory entered in the system environment variable TEMP. This is normally the directory C:\Windows\TEMP. The path can differ, depending on which partition the operating system is installed on. The following log files are created in this directory as required:
PRIMERGYServerDiscoveryTrace_<servername>.log PRIMERGYServerComponentsDiscoveryTrace_<servername>.log PRIMERGYServerComponentsMonitorTrace_<servername>_<component>.log
These files must be sent to Fujitsu Support for further analysis.
I All the log files are generated promptly only if the Fujitsu Management
Pack was imported for the first time and the initialization file exists. Otherwise it may only be possible to generate all the log files after 24 hours. If you wish to disable the creation of log files again, rename the initialization file SVISCOMLog.ini. Further information is available in the Readme.rtf file, which is contained on the installation medium.