ServerView Integration Pack for Tivoli TEC - Fujitsumanuals.ts.fujitsu.com/file/8200/sv-intpack-tivolitec-en.pdf · User Guide - English ServerView Suite FUJITSU Software ServerView

User Guide - English

ServerView Suite

FUJITSU Software ServerView Suite

ServerView Integration Pack for Tivoli TEC

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 TrademarksCopyright 2010 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.

mailto:[email protected]

http://www.cognitas.de

SV IP Tivoli TEC

Contents

1 ServerView Integration for Tivoli TEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.2 Background information . . . . . . . . . . . . . . . . . . . . . 7

1.3 Target groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.4 Related publications . . . . . . . . . . . . . . . . . . . . . . . 9

1.5 Changes since the previous version . . . . . . . . . . . . . . 9

1.6 Documentation for ServerView Suite . . . . . . . . . . . . . . 9

1.7 Notational conventions . . . . . . . . . . . . . . . . . . . . 10

2 Introduction and installation . . . . . . . . . . . . . . . . . . 11

2.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

2.2 Installation requirements . . . . . . . . . . . . . . . . . . . 122.2.1 Software requirements . . . . . . . . . . . . . . . . . . . . . . 132.2.2 Hardware requirements . . . . . . . . . . . . . . . . . . . . . 13

2.3 Upgrading ServerView/Plus version 2.7 . . . . . . . . . . . 142.3.1 Uninstalling ServerView Integration in Tivoli Inventory . . . . . 142.3.2 Uninstalling ServerView/Plus module 2.7 for Tivoli . . . . . . . 15

2.4 Installing from the desktop . . . . . . . . . . . . . . . . . . 16

2.5 Installing from the command line . . . . . . . . . . . . . . . 26

2.6 Configuring ServerView Integration in Tivoli Inventory . . . 26

2.7 Uninstalling ServerView Integration for Tivoli TEC . . . . . 272.7.1 Removing ServerView Integration in Tivoli Inventory . . . . . . 272.7.2 Uninstalling ServerView Integration Pack 2.8 for Tivoli . . . . . 28

3 Using the ServerView Integration Pack in Tivoli TEC . . . . 29

3.1 Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

3.2 Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

SV IP Tivoli TEC

Contents

3.2.1 Starting the ServerView for Tivoli module . . . . . . . . . . . . . 313.2.2 Starting ServerView . . . . . . . . . . . . . . . . . . . . . . . . 333.2.3 Starting MMB Web interface . . . . . . . . . . . . . . . . . . . 35

4 Event management via the Enterprise Console . . . . . . . . 37

4.1 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 374.1.1 Tivoli Enterprise Console server . . . . . . . . . . . . . . . . . 374.1.2 Fujitsu servers . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.2 Setting up the Tivoli Enterprise Console server . . . . . . . 384.2.1 Creating a new rule base . . . . . . . . . . . . . . . . . . . . . 404.2.2 Adding to an existing rule base . . . . . . . . . . . . . . . . . 41

4.3 Installing/configuring the SNMP adapter . . . . . . . . . . . 43

4.4 Deconfiguring the SNMP adapter . . . . . . . . . . . . . . . 45

5 ServerView inventory usingTivoli inventory . . . . . . . . . . . . . . . . . . . . . . . . . 49

5.1 ServerView inventory data in Tivoli inventory - overview . . . 495.1.1 PRIMERGY_inventory_pm profile manager . . . . . . . . . . . 505.1.2 PRIMERGY_HW_QUERIES query library . . . . . . . . . . . . 50

5.2 Gathering ServerView inventory data . . . . . . . . . . . . . 515.2.1 Adjustment of the PRIMERGY inventory profiles . . . . . . . . . 535.2.1.1 “Save Results in Database” . . . . . . . . . . . . . . . . . . 545.2.1.2 “Custom MIF Files To Be Read” . . . . . . . . . . . . . . . . 545.2.2 Definition of subscribers for the PRIMERGY inventory profiles . . 555.2.3 Distribution of the “PRIMERGY_HW” inventory profile . . . . . . 555.2.4 Requirements for successful distribution of PRIMERGY_HW . . 57

5.3 Display ServerView inventory data . . . . . . . . . . . . . . . 57

5.4 Tivoli Configuration Repository . . . . . . . . . . . . . . . . 595.4.1 Configuration Repository tables and views for ServerView . . . . 605.4.2 Configuration Repository tables and columns for ServerView . . 62

6 Integrated ServerView MIB files . . . . . . . . . . . . . . . . 71

SV IP Tivoli TEC

Contents

7 What to do if… . . . . . . . . . . . . . . . . . . . . . . . . . 77

7.1 ServerView events are not displayed in the TEC . . . . . . . 777.1.1 Configuring the server as a trap receiver . . . . . . . . . . . . 777.1.2 Communications between the SNMP adapter and the event server

777.1.3 SNMP adapter configuration . . . . . . . . . . . . . . . . . . . 787.1.4 TEC configuration . . . . . . . . . . . . . . . . . . . . . . . . 78

7.2 Error message in the SNMP adapter configuration . . . . . 78

7.3 Error message when running queries . . . . . . . . . . . . 79

7.4 Error message in “Setup TEC Event Server for ServerView” 79

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

SV IP Tivoli TEC 7

1 ServerView Integration for Tivoli TEC

1.1 Preface

Strategies for implementing centralized server administration are becoming more and more important due to the fact that networks based on independent servers are increasingly replacing mainframe systems.

This manual describes the functions and procedures of the product “ServerView Integration Pack for Tivoli TEC” (short “SV IP Tivoli TEC”), version 2.8. The integration of the ServerView Operations Manager in Tivoli TEC provides the system administration functions of the Tivoli Management Environment for use with ServerView. Using ServerView Integration for Tivoli TEC, Fujitsu servers (PRIMERGY and PRIMEQUEST) can be managed across a multi-platform network.

1.2 Background information

ServerView operates in heterogeneous networks based on the network management protocol SNMP (Simple Network Management Protocol). It is easy to connect ServerView with other management systems (e.g. HP OpenView NNM, Microsoft SMS, Novell ManageWise) due to the use of standardized interfaces. In addition, ServerView makes it possible to seamlessly integrate Fujitsu servers (PRIMERGY and PRIMEQUEST) in company-wide network management systems.

ServerView checks important server functions such as hard drives, ventilation fans, the power supply or the temperature. If the values specified for these parameters are exceeded or an error occurs, then messages are output and corrective measures are initiated as required.

Since all Tivoli/Plus modules have a common interface, a system administrator can implement the system management capabilities of the Tivoli with various production control applications while enjoying the simplicity of a common interface. The Tivoli Enterprise Console provides additional management capabilities for event correlation.

8 SV IP Tivoli TEC

Target groups ServerView Integration for Tivoli TEC

All Fujitsu servers can be monitored in a network from a standard PC running Windows (2000/2003/XP/Vista) using ServerView, Fujitsu Technology Solutions’s server management software.

Server management offers operators of large networks decisive advantages:

– increased productivity due to a more reliable server

– reduced costs through automated monitoring of the data processing infra-structure

– flexible system expansion as ServerView can be adapted to changing condi-tions without any problems

– shorter downtimes due to simplified error analysis

– shorter response times when an error does occur

– reduced total operating costs (total cost of ownership) through efficient utili-zation of the network components and their resources

– easy operation through software ergonomics: clear presentation of data, intelligent user interfaces and a supportive help system

1.3 Target groups

This guide is intended for system administrators who use the ServerView Integration for Tivoli TEC module to manage the Fujitsu servers using the server management software ServerView or MMB console.

You should know how to

– operate and administer the Tivoli Platform, i.e. Tivoli

– administer the operating system; you should be familiar with concepts such as directories, files, and symbolic links

– operate and administer ServerView Operations Manager; you should be able to interpret ServerView SNMP traps

– operate and administer PRIMEQUEST and Blade Server MMB Web consoles

SV IP Tivoli TEC 9

ServerView Integration for Tivoli/TEC Related publications

1.4 Related publications

The information in the ServerView Integration for Tivoli TEC User's Guide complements information presented in the Tivoli Framework User's Guide, the Tivoli User's Guide, and the Enterprise Console User’s Guide. You must be familiar with the Tivoli Framework before you can effectively use the specific ServerView/ Integration for Tivoli TEC module. You should also be familiar with the documentation for the ServerView application.

You should be familiar with these guides before attempting to use the infor-mation in the ServerView Integration for Tivoli TEC User's Guide.

1.5 Changes since the previous version

This edition of the manual applies to ServerView Integration V2.8 for Tivoli TEC V3.9 and replaces the following manual: “ServerView Integration Pack for Tivoli TEC“, edition May 2009.

ServerView Integration V2.8 for Tivoli TEC V3.9 offers the following new features:

– Support for the ServerView agents as of version 4.92

– Support for additional MIBs of ServerView as of version 4.92

– Japanese localization has been added.

1.6 Documentation for ServerView Suite

The documentation for the ServerView Suite can be found on the ServerView Suite DVD 2 supplied with each server system.

The documentation can also be downloaded free of charge from the Internet. You will find the online documentation at http://manuals.ts.fujitsu.com under the link Industry standard servers.

http://manuals.ts.fujitsu.com

10 SV IP Tivoli TEC

Related publications ServerView Integration for Tivoli/TEC

1.7 Notational conventions

The following notational conventions are used in this manual:

References to text or sections of text in this manual are shown with the chapter or section heading and the page on which that chapter or section begins.

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 Caution 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 shown in italics in descriptive text.

fixed font System outputs are indicated using a fixed font.

semi-bold fixed font

Commands to be entered via the keyboard are written in a semi-bold fixed font.

<abc> Angle brackets are used to enclose variables which are to be replaced by actual values.

[Key symbols] Keys are shown according to their representation on the keyboard. If uppercase letters are to be entered explicitly, then 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.

Table 1: Notational conventions

SV IP Tivoli TEC 11

2 Introduction and installationThrough the integration of ServerView in Tivoli, the Tivoli Framework can be used with ServerView Operations Manager. This integration allows centralized management of the Fujitsu servers across a multi-platform network. ServerView Integration for Tivoli TEC provides the following functions for managing the Fujitsu servers:

– Icons for launching ServerView on Windows 2000/2003/XP/Vista systems

– Icons for launching the PRIMEQUEST and blade server MMB web console

– Tivoli Enterprise Console (TEC) events customized for ServerView-specific tasks and jobs

– ServerView-specific tasks and jobs

– Inventory Profile for gathering ServerView Inventory data

– Queries for representing the gathered ServerView Inventory data

I Both the Tivoli Enterprise Console and Tivoli Inventory applications must be installed and configured before their corresponding ServerView for Tivoli TEC feature is operational.

2.1 Overview

The ServerView for Tivoli TEC module provides for event integration of ServerView SNMP traps in Tivoli, thus allowing you to display ServerView SNMP traps on a TEC.

The TEC consists of distributed event adapters, a central event server and distributed event consoles.

Figure 1: TEC components

12 SV IP Tivoli TEC

Installation requirements Introduction and installation

The SNMP adapter in Tivoli is configured for event integration in such a way that it identifies ServerView SNMP traps and converts them to Tivoli event classes (see section “Installing/configuring the SNMP adapter” on page 43).

The ServerView SNMP traps are made known on the TEC event server in Tivoli event class format. A new ServerView-specific event source is created. The ServerView SNMP traps can be displayed on any TEC which has subscribed to the ServerView-specific event source (see section “Setting up the Tivoli Enter-prise Console server” on page 38).

You can launch ServerView Operations Manager and MMB Web consoles for PRIMERGY and PRIMEQUEST server from the Tivoli desktop (see section “Starting ServerView” on page 33 and section “Starting MMB Web interface” on page 35).

The integration of ServerView data in Tivoli Inventory lets you import inventory data into Tivoli Inventory that has been stored as MIF files and recognized by ServerView. The data is gathered by a predefined inventory scan from Tivoli and can then be graphed using the various predefined queries. Another predefined scan collects more Inventory data provided by ServerView. This data will not be stored as MIF file. This data will be integrated in Tivoli too.

2.2 Installation requirements

Before attempting to install ServerView for Tivoli into the Tivoli Framework, make certain you review the requirements in this section.

The following table provides the context and authorization role required to install ServerView for Tivoli.

The ServerView Integration Pack must be installed on the following servers:

– TMR server (Tivoli Managed Region)

– TEC server (Tivoli Enterprise Console)

– Tivoli Inventory Server

I ServerView Operations Manager can be installed on any server within the network.

Activity Context Required Role

Installing SV IP Tivoli TEC Tivoli install_product

Table 2: Context and authorization role

SV IP Tivoli TEC 13

Introduction and installation Installation requirements

2.2.1 Software requirements

To operate ServerView for Tivoli properly you will need the following software packages:

– Windows 2000, Windows 2003, Windows XP or Windows Vista

– Tivoli Management Framework Version 4.1

I For information about current Tivoli Framework requirements, refer to the release notes

– Tivoli Enterprise Console (TEC) Version 3.9

– Tivoli Inventory Version 3.6

– ServerView Operations Manager as of version 4.92.

ServerView Integration Pack for Tivoli has features that use the Tivoli Enterprise Console. If these applications are not installed, the specific feature requiring these applications will not work. However, the ServerView for Tivoli installation allows you to incrementally re-install those features if you buy the missing products at a later date.

The configuration for the integration in Tivoli Inventory must be added separately. Here will be checked whether Tivoli Inventory has been installed. Tivoli Inventory does not display any requirements for the installation of ServerView/Plus. The integration of ServerView can be added at any time during a later installation of Tivoli Inventory.

I For information about ServerView for Tivoli running under other operating systems, see the readme files.

2.2.2 Hardware requirements

The following table shows the client and server disk space requirements for ServerView for Tivoli. This space is in addition to the space requirements for the Tivoli Framework and the ServerView Operations Manager application.

ServerView for Tivoli is installed on the TMR server (TMR - Tivoli Managed Region), the Tivoli Enterprise Console server (if you have the Tivoli Enterprise Console), and the Fujitsu server (Managed node). The space requirements are the same for all of these machines. The ServerView for Tivoli module uses platform-independent shell and Perl scripts, which is why the ServerView's requirements do not differ from platform to platform.

14 SV IP Tivoli TEC

Upgrading ServerView/Plus v2.0 Introduction and Installation

Moreover, depending on the number of managed inventory clients (see documentation for Tivoli Inventory), adequate space is needed in the inventory database on the RIM server being used (RIM = RDBMS Interface Module, RDBMS = relational database management system).

2.3 Upgrading ServerView/Plus version 2.7

To be able to perform an upgrade on a system on which ServerView/Plus V2.7 is already installed, you must completely remove the previous version. To do this:

– Remove the ServerView Integration from Tivoli Inventory (section “Uninstalling ServerView Integration in Tivoli Inventory” on page 14),

– Uninstall the ServerView/Plus module V2.7 for Tivoli (see section “Uninstalling ServerView/Plus module 2.7 for Tivoli” on page 15).

2.3.1 Uninstalling ServerView Integration in Tivoli Inventory

To completely uninstall ServerView Integration in Tivoli Inventory, enter the following commands in a DOS window:

%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmdbash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\PLUSunconfig inventory.sh

All existing ServerView Inventory data will be deleted, as will all Tables and Views applied to the Inventory database.

Machine Binaries Database Message Catalogs

TMR server - 200 KB -

Tivoli/Plus 3 MB - 100 KB

Managed node - - -

Table 3: Disk space requirements

SV IP Tivoli TEC 15

Introduction and Installation Upgrading ServerView/Plus v2.0

2.3.2 Uninstalling ServerView/Plus module 2.7 for Tivoli

To completely uninstall the ServerView/Plus module 2.7 for Tivoli, enter the following commands in a DOS window:

Step 1

%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmdbash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\PLUSunconfig.sh

Step 2Remove ServerView/Plus programs by entering the following command:

del %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\*.*del %BINDIR%\..\..\msg_cat\C\SERVERVIEW*

Step 3If you have uninstalled the programs successfully, clear the entries in the Tivoli Object Database by entering the following command:

wchkdb -u

I The uninstall routine described above does not remove the components Collection TivoliPlus and Plus Module Support/Link binaries -3.0.o, as these can be used by other Plus modules.

16 SV IP Tivoli TEC

Installing from the Desktop Introduction and Installation

2.4 Installing from the desktop

I The installation tasks described in this section can only be performed with system administrator´s privileges. Hence, you have to log in as system administrator.

To install the ServerView Integration for Tivoli TEC via the Tivoli desktop, proceed as follows:

Step 1

Figure 2: Opening the Install Product dialog box

Select the Install – Install Product ... option from the Desktop menu to display the Install Product dialog box.

SV IP Tivoli TEC 17

Introduction and Installation Installing from the Desktop

Figure 3: Install Product dialog box

If the ServerView for Tivoli TEC module is listed in the Select Product to Install scrolling list, skip to Step 5. If it is not listed, proceed to Step 2.

18 SV IP Tivoli TEC


Step 2Click the Select Media... button to display the File Browser dialog box.

Figure 4: File Browser dialog box

The File Browser dialog box enables you to identify or specify the path to the installation media.

I The software image may reside on a network drive, a local file system, or a CD-ROM.

Step 3If you already know the path to the image, proceed as follows:

Step 3.1Enter the full path in the Path Name field.

Step 3.2Click the Set Path button to change to the specified directory.

Step 3.3Click the Set Media & Close button to save the new media path and return to the Install Product dialog box. The dialog box now contains a list of products that are available for installation.

SV IP Tivoli TEC 19


Step 4If you do not know the exact path to the image:

Step 4.1From the Hosts scrolling list, choose the host on which the instal-lation media are mounted. This updates the Directories scrolling list which shows the directories of the host.

Step 4.2From the Directories scrolling list, choose the directory containing the installation media.

Step 4.3Click the Set Media & Close button to save the new media path and return to the Install Product dialog box. The dialog box now contains a list of products that are available for installation.

Step 5

Figure 5: Plus Module Support (Link binaries) - 3.0.o in the Install Product dialog box

20 SV IP Tivoli TEC


After step 3 or 4, the Install Product dialog box now contains a list of products that are available for installation. In the Select Product to Install list, select the entry Plus Module Support (Link binaries) - 3.0.o.

Step 6Click the Install or Install & Close button to install the module.

If you click Install, the Install Product window will remain open after the installation. You can then install the ServerView Integration for Tivoli TEC on another set of clients or you can install another product.

If you click Install & Close, the Install Product window will close after the installation.

If you click Close, the Install Product window will close without the module being installed.

The Product Install dialog box guides you through the installation process. Example:

SV IP Tivoli TEC 21


Figure 6: Product Install before installation of Plus Module Support

This dialog box provides the list of operations that takes place when installing the software. This dialog box also warns you of any problems that you may want to correct before you install the ServerView for Tivoli TEC module.

Step 7Click the Continue Install button to begin the installation process.

When the installation is complete, the Product Install dialog box displays a completion message similar to the following:

22 SV IP Tivoli TEC


Figure 7: Product Install after installation of Plus Module Support (Link binaries) - 3.0.o

Or click the Cancel button to abort the installation process.

Step 8When you see the message Finished product installation in the Product Install window, click Close to complete the installation process. Depending on how you started the installation (via Install or Install & Close), this will either take you back to the Install Product window or the installation will be closed.

SV IP Tivoli TEC 23


Step 9

Figure 8: Entry ServerView/Plus module for Tivoli

Select the ServerView module for Tivoli, Version 2.8 from the Select Product to Install list.

Step 10Click the Install or Install & Close button to install the module.

If you click Install, the Install Product window will remain open after the installation. You can then install the ServerView Integration for Tivoli TEC on another set of clients or you can install another product.

If you click Install & Close, the Install Product window will close after the installation.

If you click Close, the Install Product window will close without the module being installed.

The Product Install dialog box guides you through the installation process. Example:

24 SV IP Tivoli TEC


Figure 9: Product Install before installation of the ServerView Integration Pack

This dialog box provides the list of operations that takes place when installing the software. This dialog box also warns you of any problems that you may want to correct before you install the ServerView for Tivoli TEC module.

SV IP Tivoli TEC 25


Step 11Click the Continue Install button to begin the installation process. When the installation is complete, the Product Install dialog box displays a completion message similar to the following:

Figure 10: Product Install after installation of the ServerViewIntegration Pack

Or click the Cancel button to abort the installation process.

Step 12When you see the message Finished product installation in the Product Install window, click Close to complete the installation process.

26 SV IP Tivoli TEC

Installing from the Command Line Introduction and Installation

2.5 Installing from the command line

I The installation tasks described in this section can only be performed with system administrator´s privileges. Hence, you have to log in as system administrator.

Use the winstall command to install the ServerView for Tivoli TEC module.

Example of the syntax for winstall and its parameters:

winstall -c <cdrom_path> -s <installation_server> -i LINK.IND

or

winstall -c <cdrom_path> -s <installation_server> -i SERVERVIEW.IND

where

-c <cdrom_path>specifies the path to the CD-ROM image.

-s <installation_ server>specifies the server on which the product is to be installed.

-i <index_file>specifies the index file from which the product is to be installed (e.g.: LINK.IND or SERVERVIEW.IND).

2.6 Configuring ServerView Integration in Tivoli Inventory

I The administrative procedures described in this section can only be performed with system administrator permissions. It is therefore necessary to log in as the system administrator.

To configure the ServerView Integration in Tivoli Inventory, enter the following commands in a DOS window:

%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmdbash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\PLUSconfig_inventory.sh

This stores all the necessary tables and views in the inventory database as well as the inventory profiles and queries necessary for operation.

SV IP Tivoli TEC 27

Introduction and Installation Uninstalling ServerView Integration

The configuration of the Inventory Integration checks whether Tivoli Inventory is installed and, if it cannot be found, then cancels the installation. If Tivoli Inventory is installed later, then the configuration of ServerView Integration can be performed again at any time.

2.7 Uninstalling ServerView Integration for Tivoli TEC

I The administration tasks described in this section can only be performed with system administrator´s privileges. You must therefore log in as the system administrator.

2.7.1 Removing ServerView Integration in Tivoli Inventory

To completely remove the ServerView Integration in Tivoli Inventory, enter the following commands in a DOS window:

%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmdbash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\PLUSunconfig_inventory.sh

%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmdbash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\PLUSunconfig_inventory.sh

This will remove all tables and views stored in the inventory database during the configuration and thereby remove all ServerView Inventory data present.

28 SV IP Tivoli TEC

Uninstalling ServerView Integration Introduction and Installation

2.7.2 Uninstalling ServerView Integration Pack 2.8 for Tivoli

To completely delete the ServerView Integration Pack 2.8 for Tivoli, enter the following commands in a DOS window: 0

Step 1%WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmd bash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\PLUSunconfig.sh

Step 2If you want to remove the program files, proceed with the following commands:

del %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\*.*del %BINDIR%\..\..\msg_cat\C\SERVERVIEW*

Step 3To clean up the object database, run

wchkdb -u

Step 4Deleting possible registry entries from ServerView Operations Manager:If ServerView is running, check whether there is data in the registry under the following path: HKLM\SOFTWARE\Fujitsu\ServerView Suite\Tivoli TEC Integration

If this path exists, delete it in the registry. To do this, start the registry editor via Start – Run – regedit and navigate in the left window to the above registry path. Delete the path either via the Edit menu or via the context menu with the item Delete.

I The uninstall procedure does not remove the entries for Collection Tivoli/Plus or the Plus Module Support /Link binaries - 3.0.o module, as these can be used by other Tivoli/Plus modules.

SV IP Tivoli TEC 29

3 Using the ServerView Integration Pack in Tivoli TEC

I The management and administration tasks described in this section can only be performed with system administrator´s privileges. Hence, you have to log in as system administrator.

3.1 Icons

Although the ServerView for Tivoli icons look like (traditional) Tivoli icons, their functionality has been altered slightly to provide a faster, more intuitive approach to navigating and deploying the modules’ features.

The ServerView for Tivoli icons can be activated in either of two ways:

– Opening or executing the icon by double-clicking on it with the left mouse button. In many cases, double-clicking executes an activity (such as a task) without opening another dialog layer.

– Displaying the icon's context menu by pressing and holding the right mouse button.

Generally, either method may be used to access a particular function. There are cases, however, where a particular function can only be accessed by one of these methods.

The following icon represents the ServerView Integration for Tivoli TEC resources:

Figure 11: ServerView icon

30 SV IP Tivoli TEC

Features Using the ServerView Integration Pack in Tivoli TEC

3.2 Features

The ServerView for Tivoli TEC tasks use the term profile manager in a somewhat different way than the Profile Manager (configured for inventory integration) or other Tivoli products in general. In both tasks, a profile manager's primary function is similar to a subscription list. A subscription list identifies the machines on which tasks and jobs run when executed. Subscription lists can contain machine names or other profile managers. Adding a profile manager to a subscription list is simply a way of subscribing several machines at a time rather than adding each one individually.

The Tivoli/Plus User's Guide describes the function of profile managers in the ServerView for Tivoli TEC in more detail. For more information, see the section on subscribers and targets in the Tivoli/Plus User's Guide.

SV IP Tivoli TEC 31

Using the ServerView Integration Pack in Tivoli TEC Features

3.2.1 Starting the ServerView for Tivoli module

All Tivoli/Plus modules are kept in a collection under the Tivoli/Plus icon on the Tivoli desktop. The ServerView icon is added to this collection after installation.

Take the following steps to see the modules included in your Tivoli/Plus collection:

Step 1

Figure 12: TME desktop

From the main Tivoli desktop, double-click the TivoliPlus icon or select the Open... option from the TivoliPlus icon's context menu to display the TivoliPlus window.

32 SV IP Tivoli TEC


Step 2

Figure 13: TivoliPlus window

The TivoliPlus window displays an icon for each Tivoli/Plus module installed.

Double-click the ServerView Plus for Tivoli icon or select the Open... option from the ServerView Plus for Tivoli icon's context menu to display the icons representing the tasks and other tools for managing the ServerView product.

Figure 14: ServerView Plus for Tivoli window

I If the ServerView Integration in Tivoli Inventory was not configured, the two icons PRIMERGY_inventory_pm and PRIMERGY_HW_QUERIES will not be available in the ServerView Plus for Tivoli window.

SV IP Tivoli TEC 33


3.2.2 Starting ServerView

When the ServerView Integration Pack for Tivoli is installed on a ServerView management server, the installation process creates a task and an icon for launching the ServerView application from within Tivoli.

The ServerView management console can be started (via Tivoli Desktop) for Tivoli Managed Nodes or LCF Endpoints (LCF = Lightweight Client Framework).

You start the ServerView Operations Manager in the ServerView Plus for Tivoli window via the following icon:

Figure 15: ServerView launch icon

Double-click the ServerView icon to open the ServerView Operations Manager main window.

34 SV IP Tivoli TEC


Starting ServerView Operations Manager the first time

The first time you start ServerView Operations Manager, a dialog box opens in which you must enter the following:

– Name of the server on which ServerView Operations Manager is installed.

– Port number for ServerView Operations Manager.

– Indicate whether a secure connection (SSL) is to be used.

Figure 16: ServerView Operations Manager - requested information

These details are stored in the registry under the path HKLM\SOFTWARE\Fujitsu\ServerView Suite\Tivoli TEC Integration and need only be entered the first time ServerView is launched.

SV IP Tivoli TEC 35


3.2.3 Starting MMB Web interface

From the Tivoli desktop you can start the Web interface of Blade server and PRIMEQUEST using the following icons:

Figure 17: Icons for MMB Web interface

A dialog box opens in which you must enter the IP address of MMB:

Figure 18: IP Address of MMB dialog box

SV IP Tivoli TEC 37

4 Event management via the Enterprise Console

With the Tivoli Enterprise Console (TEC), ServerView for Tivoli provides a set of filters for identifying events. An event is any significant change in the state of system resources or an application. In the case of ServerView for Tivoli, an event is a change in a monitored resource that affects ServerView or the system on which ServerView Agent is running. Examples of events are the starting and stopping of a process, an unsuccessful substitution to a system ID, or a server becoming unavailable. Event management provides a predefined or automated response to specific events, so that potential problems are identified and responded to before causing system downtime. For example, if a process fails, the Tivoli Enterprise Console can automatically rerun the process. The Tivoli Enterprise Console can also notify the system administrator of repeated process failures that may indicate a more severe problem with an application or the network. For some events, there is no automated response except for a message to be displayed in the Tivoli Enterprise Console.

I The management and administration tasks described in this section can only be performed with system administrator´s privileges. Hence, you have to log in as system administrator.

4.1 Configuration

The following describes the configuration activity that occurs when setting up the Tivoli Enterprise Console to be used with ServerView for Tivoli. This activity takes place on the Tivoli Enterprise Console and Fujitsu servers. ServerView for Tivoli performs most of the setup activity automatically.

4.1.1 Tivoli Enterprise Console server

The Tivoli Enterprise Console server is set up to

– recognize and accept ServerView events

– notify the system administrator of the events received

For more information see section “Setting up the Tivoli Enterprise Console server” on page 38.

38 SV IP Tivoli TEC

Setting up the Tivoli Enterprise Console Server Event Management

4.1.2 Fujitsu servers

On the nodes where Fujitsu servers will be running

– a ServerView agent is configured to send events to the SNMP adapter

– the SNMP adapter is configured to recognize and forward ServerView events to the Tivoli Enterprise Console.

For more information see section “Installing/configuring the SNMP adapter” on page 43.

4.2 Setting up the Tivoli Enterprise Console server

Use the procedures in this section to set up the Tivoli Enterprise Console to receive SNMP events.

You configure the Tivoli Enterprise Console via the icon Setup TEC Event Server for ServerView in the ServerView Plus for Tivoli window.


SV IP Tivoli TEC 39

Event Management Setting up the Tivoli Enterprise Console Server

Step 1Double-click the icon Setup TEC Event Server for ServerView or select the Run job... option from the context menu for this icon. This opens the following window:

Figure 20: Setup TEC Event-Server for ServerView window

Step 2Once you have displayed the Setup TEC EventServer for ServerView window, there are two options for setting up the Tivoli Enterprise Console:

– Creating a new rule base, see section “Creating a new rule base” on page 40, or

– Adding the ServerView-Integration-specific rules to an existing rule base, see section “Adding to an existing rule base” on page 41.

40 SV IP Tivoli TEC


4.2.1 Creating a new rule base

Take the following steps to set up the Tivoli Enterprise Console by creating a new rule base:

Figure 21: Creating a new rule base

Step 1Enter the name of the rule base you want to create in the Rule Base Name (new or existing) name field.

Step 2New rule bases are created by copying (cloning) and modifying an existing rule base. Enter the name of the rule base to be copied in the Rule Base to clone (if new) field. Note here that to separate the directory names you must use a forward slash (/) and not - as is standard in Windows - a backslash (\).

Step 3Specify the path name to the directory on the Tivoli Enterprise Console server in which you want to create the new rule base in the Path for Rule Base (if new) field.

I The current user for the TME administrator must have write access to the directory that you specify in this field.

Step 4Click Set and Close.

SV IP Tivoli TEC 41

Event Management Setting up the Tivoli Enterprise Console Server

4.2.2 Adding to an existing rule base

Take the following steps to set up the Tivoli Enterprise Console by adding the ServerView for Tivoli-specific event classes to an existing rule base.

Figure 22: Adding to an existing rule base

Step 1Enter the name of an existing rule base that you want to modify to contain the ServerView event classes in the Rule Base Name (new or existing) name field.


42 SV IP Tivoli TEC


When setup of the Tivoli Enterprise Console is finished, a window displays the debugging output from execution task.

Figure 23: Event server setup finished

SV IP Tivoli TEC 43

Event Management Installing/Configuring the SNMP Adapter

4.3 Installing/configuring the SNMP adapter

To install/configure the SNMP adapter for the Tivoli Enterprise Console, you must configure the managed servers to send SNMP traps to the SNMP adapter. You must also configure the SNMP adapter to send events to the Tivoli Enter-prise Console. The Fujitsu server on which the adapter to be configured runs must be a Tivoli Managed Node or an LCF Endpoint (LCF = Lightweight Client Framework). TME and non-TME adapters can be configured. It is also possible to configure adapters for multiple Fujitsu servers simultaneously in one step.

I Before you configure the SNMP adapter, you should copy the serverview adapter files directory from the installation medium into a temporary directory on the TME server.

To install/configure the SNMP adapter for ServerView on the Tivoli Enterprise Console, proceed as follows:

Step 1

Figure 24: ServerView Plus for Tivoli

In the ServerView Plus for Tivoli window, double-click the Configure SNMP Adapter icon.

44 SV IP Tivoli TEC

Installing/Configuring the SNMP Adapter Event Management

Step 2

Figure 25: The SNMP Adapter Configuration dialog

In the Endpoint or ProfileManager field, enter the network name of the Fujitsu server on which the adapter is installed. If you enter a profile manager, all its subscribers will be affected.

Step 3In the Directory of adapter files field specify the location of the adapter configuration files (*.cds and *.oid) on the machine where the adapter is running. The process will merge these files with the ones currently in use by the adapter.

When this process is finished click Set and Close. This will add an additional entry to the file via the task Configure ServerView SNMP Event Adapter in order to re-route logging into the file, designated in the Audit File Name field. For additional information concerning logging please refer to the ServerView documentation.

Step 4In the Directory of SNMP adapter field specify the installation directory of the SNMP adapter. When a TME Adapter is used on the machine, this file can be left blank.

Step 5 Click Set and Close.

The Configure_SNMP_Adapter (SERVERVIEW) Output window opens showing the logging data of the configuration process.

SV IP Tivoli TEC 45

Event Management Deconfiguring the SNMP Adapter

Figure 26: Logging data for the configuration process

4.4 Deconfiguring the SNMP adapter

Double-clicking the Unconfigure SNMP Adapter icon in the ServerView Plus for Tivoli window causes the specified SNMP adapter to stop forwarding ServerView-specific traps to Tivoli Enterprise Console.

The Fujitsu server on which the adapter to be deconfigured runs must be a Tivoli Managed Node or LCF Endpoint. It is also possible to deconfigure the adapter on multiple hosts in one step.

46 SV IP Tivoli TEC

Deconfiguring the SNMP Adapter Event Management

Step 1


In the ServerView Plus for Tivoli window, double-click the Unconfigure SNMP Adapter icon. The Unconfig_SNMP_Adapter (SERVERVIEW) Output window opens.

Figure 28: Unconfig_SNMP_Adapter window

Step 2In the Endpoint or ProfileManager field, enter the Fujitsu Server on which the adapter is installed. If you enter a profile manager, all its subscribers will be affected.

Step 3In the Directory of SNMP adapter field specify the installation directory of the SNMP adapter. When TME Adapter is used on the machine, this file can be left blank.


SV IP Tivoli TEC 47

Event Management Deconfiguring the SNMP Adapter

The Unconfig_SNMP_Adapter (SERVERVIEW) Output window opens showing the logging data of the deconfiguration process:

Figure 29: Output of the deconfiguration process

SV IP Tivoli TEC 49

5 ServerView inventory usingTivoli inventory

5.1 ServerView inventory data in Tivoli inventory - overview

After the configuration of ServerView inventory integration, two additional icons are displayed in the ServerView Plus for Tivoli window:

– PRIMERGY_inventory_pmStarts the profile manager PRIMERGY_inventory_pm,

– PRIMERGY_HW_QUERIES Starts querying the ServerView inventory data.

Figure 30: “ServerView Plus for Tivoli“ with configured inventory integration

50 SV IP Tivoli TEC

Inventory Data in Tivoli Inventory ServerView Inventory

5.1.1 PRIMERGY_inventory_pm profile manager

The PRIMERGY_inventory_pm profile manager contains the predefined profiles PRIMERGY_HW and PRIMERGY_HW_SNMP. If this is distributed to suitable subscribers (systems with correctly configured ServerView agents), ServerView inventory data are defined there and then transferred to the Tivoli Configuration Repository.

– PRIMERGY_HW profile

This profile defines the inventory data distributed by the ServerView agents in ServerView MIF files. The prerequisite for this is the use of the ServerView SMS agent, which generates the ServerView MIF files.

– PRIMERGY_HW_SNMP profile

This profile allows inventory data to be defined without the need to use the ServerView SMS agent. If the profile is distributed to subscribers, then with the aid of local SNMP requests, inventory data are gathered from the subscriber into the ServerView agents. The inventory data are displayed in their own MIF files.

The inventory data collected by the two profiles overlap slightly because the most important ServerView inventory data are gathered by both profiles. To obtain the largest possible volume of ServerView inventory data, both profiles must be used. If the ServerView SMS agent is not used, but other ServerView agents are used, then only the PRIMERGY_HW_SNMP profile can be success-fully used. If, on the other hand, you only use the ServerView SMS agent then inventory data are only supplied from the PRIMERGY_HW profile.

For more information on configuring the profiles, see section “Gathering ServerView inventory data” on page 51.

5.1.2 PRIMERGY_HW_QUERIES query library

The PRIMERGY_HW_QUERIES query library contains series of predefined queries for the retrieval of ServerView inventory data. The inventory data defined by the two predefined profiles (PRIMERGY_HW and PRIMERGY_HW_SNMP) can be displayed with the corresponding queries.

For more information on gathering and displaying the ServerView inventory data, see section “Display ServerView inventory data” on page 57.

SV IP Tivoli TEC 51

ServerView Inventory Gathering ServerView Inventory Data

5.2 Gathering ServerView inventory data

To gather ServerView inventory data on the managed PRIMERGY servers (subscribers) with the help of the predefined PRIMERGY profile, you must do the following:

1. Adjust the inventory profiles (see section “Adjustment of the PRIMERGY inventory profiles” on page 53)

2. Define subscribers for the inventory profiles (see section “Definition of subscribers for the PRIMERGY inventory profiles” on page 55)

3. Distribution of the inventory profiles (see section “Distribution of the “PRIMERGY_HW” inventory profile” on page 55)

Start the profile manager to perform these steps. Double-click the relevant icons n the ServerView Plus for Tivoli window to start the profile manager.

52 SV IP Tivoli TEC

Gathering ServerView Inventory Data ServerView Inventory

Figure 31: “PRIMERGY_Inventory_pm” profile manager

SV IP Tivoli TEC 53


5.2.1 Adjustment of the PRIMERGY inventory profiles

To adjust one of the PRIMERGY inventory profiles, right-click the symbol of the relevant profile in the Profile Manager window and select Customize....

Figure 32: Adjustment of the “PRIMERGY_HW” inventory profile

54 SV IP Tivoli TEC


The main adjustments that may be necessary (to match real operating condi-tions) are described in the following two paragraphs.

I As a general rule, all the other fields should not be changed when you are gathering ServerView inventory data. The meanings of the additional fields are described in the Tivoli Inventory documentation.

5.2.1.1 “Save Results in Database”

For the first scan of inventory data, Replace with Current Results must be selected. This is also the default setting after the configuration of the ServerView integration. If, during a later scan, the available data should not be replaced but rather the changes only stored in the database, then the selection must be changed to Update with Differences.

5.2.1.2 “Custom MIF Files To Be Read”

As a default setting, all MIF files that can be generated by ServerView are specified during the configuration of the ServerView integration. This selection must be adjusted, however, if not all MIF files are generated on the subscriber system. If, for example, a system is not equipped with RAID, then the entry for the SniRaidMlx.mifMIF file must be removed from the PRIMERGY_HW profile. Otherwise, an attempt to store unavailable data in the inventory database will produce a corresponding error message.

If only a portion of the systems with ServerView agents is equipped with RAID, then an additional profile must be created, preferably a clone of the PRIMERGY_HW profile in which the SniRaidMlx.mif MIF file is removed. All systems with RAID are then assigned to the original profile as subscribers, whereas those systems without RAID are assigned to the new profile. (The production and cloning of a profile is described in the documentation for Tivoli inventory).

In the PRIMERGY_HW_SNMP profile, the procedure just described must not be followed. If this system is distributed to a system not equipped with RAID, or without running Mylex agents, the profile generates an empty MIF file sv_myles.mif. This allows the distribution of the profile to be successfully concluded.

SV IP Tivoli TEC 55


5.2.2 Definition of subscribers for the PRIMERGY inventory profiles

By selecting Profile Manager – Subscribers… from the menu in the Profile Manager window, you can define subscribers for the profiles:

Figure 33: Subscribers for the “PRIMERGY_inventory_pm” inventory profile

I Details on defining subscribers can be found in the documentation for Tivoli inventory.

5.2.3 Distribution of the “PRIMERGY_HW” inventory profile

You can distribute the inventory profiles individually or together. The prereq-uisite is that the profiles PRIMERGY_HW and PRIMERGY_HW_SNMP have been adjusted as described above and one or more subscribers have been defined. The inventory profiles can be distributed as follows:

Step 1In the Profile Manager window, mark the desired profiles and the subscriber(s) for which inventory data is to be collected:

56 SV IP Tivoli TEC


Figure 34: Distribution of the “PRIMERGY_HW” inventory profile

Step 2Select the Profile Manager – Distribute ... menu item in the Profile Manager and confirm the following window with Distribute Now.

Figure 35: Distribute Profiles menu

SV IP Tivoli TEC 57

ServerView Inventory Display ServerView Inventory Data

5.2.4 Requirements for successful distribution of PRIMERGY_HW

In order to successfully distribute the PRIMERGY_HW inventory profile, the subscribers must satisfy the following requirements:

● ServerView SMS Agent (SMS - Systems Management System) as of version 2.03 must be installed.

● The MIF files defined in the profile must be generated by SMS Agent. If, for example, RAID is not available and the generated RAID MIF file is therefore always empty, then the entry for SniRaidMlx.mif must be removed in the profile configuration (see page 54).

● For the creation of MIF files by SMS Agent, the Extended=2 setting must be used. Further information can be found in the documentation for Tivoli inventory.

● The templates for the generating of MIF files must be adjusted to the DMTF standard.

For more information on the ServerView agent, see the ServerView installation guide.

So that the PRIMERGY_HW_SNMP can be successfully distributed, the correct SNMP community must be known during the scan. By default, the community public is used. Another community can be defined for each Tivoli endpoint on the last line of the following file:

$LCFDIR/inv/$SCANDIR/sv_snmp_community

So that the successfully collected ServerView inventory data can also be displayed with the queries in the PRIMERGY_HW_QUERIES query library, it is necessary to perform a generic Tivoli hardware scan at least once. This can be done either within one of the two PRIMERGY profiles or through any other inventory profile. The sequence of the scans does not play any role.

5.3 Display ServerView inventory data

Double-clicking on the PRIMERGY_HW_QUERIES symbol opens the query library which contains a list of predefined queries for the retrieval of ServerView inventory data:

58 SV IP Tivoli TEC

Display ServerView Inventory Data ServerView Inventory

Figure 36: PRIMERGY HW_Queries

To successfully perform a query, the corresponding data must be available in the database, that is, the PRIMERGY_HW profile must previously have been successfully distributed to suitable subscribers. Otherwise, for example, when performing the query SV_BUS_BOARDS, the following error message is displayed:

SV IP Tivoli TEC 59

ServerView Inventory Tivoli Configuration Repository

Figure 37: Error Message

If the corresponding data is available in the database, performing a query displays this data in a table:

Figure 38: Run Query window

5.4 Tivoli Configuration Repository

The Tivoli Configuration Repository, stored in the underlying relational database, forms the basis for Tivoli Inventory. To integrate ServerView Inventory data into Tivoli Inventory, the various necessary tables and views are created which are described in the following section.

60 SV IP Tivoli TEC

Tivoli Configuration Repository ServerView Inventory

5.4.1 Configuration Repository tables and views for ServerView

Every MIF group is mapped to a corresponding table in the database; the attributes of an MIF group are mapped to the appendant columns. To represent the data, for each table there exists a view which contains the exact contents of the table as well as the OID and label of the systems from the Tivoli object database.

In this way, for example, the PRIMERGY Peripheral Bus: Boards table and the PRIMERGY_BUS_BOARDS_VIEW are derived from the PRIMERGY Peripheral Bus: Boards MIF group from SniAdapter.mif. The following table lists all tables and views as well as the corresponding MIF file and a brief description. For simplicity, the PRIMERGY_ prefix has been omitted from the names of the tables.

Table / View MIF file Description

BUS_BOARDS SniAdapter.mif Information on ISA/EISA/PCI adapters

CABINETS SniServCtrl.mif Information on cabinets

EMERGENCY_PAGER SniServCtrl.mif Information on emergency pager

FANS SniServCtrl.mif Information on fans

MEMORY_MODULES SniServCtrl.mif Information on memory module

POWER_SUPPLY SniServCtrl.mif Information on and status of the power supply

PROCESSORS SniServCtrl.mif Information on system board processors

PROCESSOR_CACHE SniServCtrl.mif Information on processor cache

RAID_CONTROLLERS SniRaidMlx.mif Information on Mylex RAID controllers

RAID_DEVICES SniRaidMlx.mif Information on physical RAID devices

RAID_LOG_DRIVES SniRaidMlx.mif Information on logical RAID drives

REBOOT_SETTINGS SniServCtrl.mif Information on reboot settings

SMS_INTEGRATION SniSMS.mif Information on ServerView SMS integration

SNMP_AGENTS SniSMS.mif Information on and status of ServerView agents

STORAGE_BOARDS SniHd.mif Information on mass storage boards

STORAGE_DEVICES SniHd.mif Information on mass storage devices

SV IP Tivoli TEC 61


SYSTEMBOARD_INFO SniServCtrl.mif General information on the system board

TEMPERATURE SniServCtrl.mif Information on temperature sensors

WATCHDOG SniServCtrl.mif Information on Watchdog

CABINETS2 sv_general.mif Information on cabinets

DEVICES sv_general.mif Information on devices

DPTSCSI sv_general.mif Information on DPT SCSI controller

FIRMWARE sv_general.mif Information on available firmware

GENERAL_INFO sv_general.mif General information

INTERFACES sv_general.mif Information on interfaces

MEMORY sv_general.mif Information on memory modules

MYLEX sv_mylex.mif Information on Mylex RAID controller

Table / View MIF file Description

62 SV IP Tivoli TEC


5.4.2 Configuration Repository tables and columns for ServerView

The following section registers all tables defined in the Inventory database with their columns.

I The table descriptions apply for Inventory 3.6. Due to the modified Tivoli Inventory Repository database scheme in Inventory 4.0, the HARDWARE_SYSTEM_ID column was replaced by the COMPUTER_SYS_ID column. Moreover, the CONFIG_CHANGE_TYPE and CONFIG_CHANGE_TIME columns are no longer present in Inventory 4.0.

Table PRIMERGY_BUS_BOARDSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEBUS_TYPEBUS_NOSLOT_DEVICE_NOMODELTYPEBOARD_ID

Table PRIMERGY_CABINETSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECABINET_INDEXCABINET_TYPECABINET_ATTRIBUTECABINET_IDENT_NOSYSTEMBOARD_TYPESYSTEMBOARD_SERIAL_NOTEMPERATURE_SENSORSFANSPOWER_SUPPLY_SLOTSMINIMUM_POWER_SUPPLIES

SV IP Tivoli TEC 63


Table PRIMERGY_EMERGENCY_PAGERHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEUSER_INDEXTYPEUSER_NAMEUSER_DESCRIPTIONUSER_ACTIVESIZE_BYTESPAGER_NOSERVICE_PROVIDER_NO

Table PPRIMERGY_FANSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECABINET_INDEXFAN_INDEXFAN_PURPOSEFAN_FAIL_REACTIONFAN_FAIL_SHUTDOWN_DELAY_SEC

Table PRIMERGY_MEMORY_MODULESHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEMODULE_INDEXMEMORY_BANKSTATUSSTART_ADDRESSSIZE_BYTES

Table PRIMERGY_POWER_SUPPLYHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECABINET_NOPOWER_SUPPLY_NOPOWER_SUPPLY_STATUS

64 SV IP Tivoli TEC


Table PRIMERGY_PROCESSORSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEINDEX_NOTYPESTATUSFAMILYMODELSTEPCURRENT_SPEED_MHZ

Table PRIMERGY_PROCESSOR_CACHEHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEINDEX_NOLEVEL_SIZE_KBWRITE_POLICY

Table PRIMERGY_RAID_CONTROLLERSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECONTROLLER_NOVENDORMODELBUS_TYPESLOT_NOBASE_ADDRESSIRQFIRMWARE_VERSIONBIOS_VERSIONREBUILD_RATESCSI_CHANNELSLOGICAL_DRIVESPHYSICAL_DEVICESMAX_LOGICAL_DRIVESMAX_PHYSICAL_DEVICESCACHE_SIZE_KBFLASH_EEPROM_SIZE_KBSTRIPE_SIZE_BLOGICAL_SECTOR_SIZE_BPHYSICAL_SECTOR_SIZE_B

SV IP Tivoli TEC 65


Table PRIMERGY_RAID_DEVICESHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECONTROLLER_NOCHANNELTARGET_IDMODELCAPACITY_MBDEVICE_TYPE

Table PRIMERGY_RAID_LOG_DRIVESHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECONTROLLER_NODRIVE_NOSIZE_MBRAID_LEVELPHYSICAL_SIZE_MBCACHE_WRITE_POLICY

Table PRIMERGY_REBOOT_SETTINGSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMERESTART_RETRY_COUNTERREBOOT_FAIL_OPTIONERROR_RESTART_MINUTESREBOOT_FAIL_PAGERLAST_OFF_REBOOT_REASON

Table PRIMERGY_SMS_INTEGRATIONHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMESERVERVIEW_SMS_AGENTSMS_INTEGRATION_VERSSNMP_AGENTS_VERSION

Table PRIMERGY_SNMP_AGENTSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEOIDNAMEPURPOSESTATUS

66 SV IP Tivoli TEC


Table PRIMERGY_STORAGE_BOARDSHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEBUS_TYPEBUS_NOADAPTERBOARD_NAMESLOT_DEVICE_NO

Table PRIMERGY_STORAGE_DEVICESHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEBUSBUS_NOADAPTERDEVICENAMETYPESMART_COMPLIANTSMART_MONITORINGSMART_STATUS

Table PRIMERGY_SYSTEMBOARD_INFOHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEVENDORBOARD_IDBOARD_SERIAL_NOPHYSICAL_MEMORY_MBSYSTEM_BIOS_VERSION

Table PRIMERGY_TEMPERATUREHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECABINET_INDEXSENSOR_INDEXSENSOR_PURPOSEWARNING_TEMPERATURECRITICAL_TEMPERATURECRITICAL_TEMP_REACTION

SV IP Tivoli TEC 67


Table PRIMERGY_WATCHDOGHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEHW_WATCHDOG_TIME_SECHW_WATCHDOG_ENABLEDHW_WATCHDOG_ACTIONSW_WATCHDOG_TIME_MINSW_WATCHDOG_ENABLEDSW_WATCHDOG_ACTION

Table PRIMERGY_CABINETS2HARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMECABINET_IDIDENT_NOBOARD_IDSYSTEM_NAMEHOUSING_TYPE

Table PRIMERGY_DEVICESHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEBUS_TYPEBUS_NOADAPTER_NODEVICE_NONAMETYPERAW_NAMECAPACITY

Table PRIMERGY_DPTSCSIHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEHBA_NUMBERBUS_NUMBERBUS_TYPESCSI_IDSCSI_LUNSCSI_LEVELSCSI_MODELSCSI_CAPACITY_MB

68 SV IP Tivoli TEC


Table PRIMERGY_FIRMWAREHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEINFO_NOVENDORPRODUCTPRODUCT_NOPRODUCT_DESCRIPTIONVERSIONPRODUCT_DATESERIAL_NO

Table PRIMERGY_GENERAL_INFOHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEHOSTNAMEHOST_OSSERVER_HOUSINGCPU_SOCKETSMEMORY_MODUL_SOCKETSPCI_BUS_NOPCI_SLOTS

Table PRIMERGY_INTERFACESHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEINDEX_NODESCRIPTIONTYPEMAC_ADDRESSSTATUS

Table PRIMERGY_MEMORYHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEMODULE_NOSIZE_BYTESTYPETYPE2MEMORY_SOCKETS

SV IP Tivoli TEC 69


Table PRIMERGY_MYLEXHARDWARE_SYSTEM_IDCONFIG_CHANGE_TYPECONFIG_CHANGE_TIMEINDEX_NOBUS_TYPECLASSCONFIGURED_CHANNELSACTUAL_CHANNELSCACHE_SIZE_MBCACHE_SIZE_KBPHYSICAL_DEVICESLOGICAL_DEVICES

SV IP Tivoli TEC 71

6 Integrated ServerView MIB filesA trap is an alarm signal of the SNMP protocol data unit that is transmitted from an SNMP agent to the administration center. The alarm signal contains information on unexpected events, e.g. fault reports or status changes, that occur if selected thresholds are exceeded.

These event definitions are contained in MIB files. The following table provides an overview of the MIBs that are taken into account:

MIB name File name

Adaptec Raid MIB AAC.MIB

ADIC Device Trap MIB ADICLIBMIB-v2.mib

Acer Advanced ServerManager MIB ASMPRO.MIB

Broadcom Advanced Server Trap MIB baspTrap.mib

Centric Store FS CentricStor-FS.MIB

CLARiiON Storage System Traps CLARIION_FSC_2.MIB

FibreCat MIB CLARIION1.MIB

Rittal CMC MIB CMC32.MIB

Rittal CMC-TC MIB CMC-TC.MIB

Compaq Host Information MIB CPQHOST-MIB.MIB

DuplexDataManager MIB DDM.MIB

Compaq STEAM Agent MIB DEC.MIB

DeskView Trap MIB DESKTRAP.MIB

Dot Hill FibreCat Trap MIB DHTRAPS.MIB

DPT SCSI / Raid controller MIB DPTSCSI.MIB

Adaptec Duralink MIB DURALINK.MIB

DuplexWrite MIB DW.MIB

Fjdary-E60 extended-MIB DX60_80.mib

Egenera Integration Solution MIB egeneraV1.mib

Entity RFC 2737 MIB ENTITY-RFC2737V1.MIB

Eurologic StorageManager MIB EUROLOGIC.MIB

Fujitsu LDSM Trap MIB F5EMT2O.MIB

Fibre Channel Mgmt MIB FCMGMT-MIB.mib

Table 4: List of integrated ServerView MIBs

72 SV IP Tivoli TEC

Integrated ServerView MIB files

Fibre Channel Switch MIB FCSWITCH.MIB

Fibre Cat_TX_S2 MIB FibreCat_TX_S2.mib

Fjdary-E50 extended-MIB FJDARY-E4kM500.mib

Fujitsu Siemens KVMS3 TRAP MIB FSC-KVMS3-TRAP.mib

Fujitsu Siemens RCA4Plus - Trap MIB FSC-RCA4PLUS-TRAP.mib

Avocent KVM Traps FSC-S21611-TRAP.mib

High Availability MIB HA.mib

Mass Storage (Harddisk) MIB HD.MIB

Hardware Platform Interface MIB HPI-MIBV1.MIB

Intel LAN adapters MIB INTELLAN_V1.mib

Adaptec StorageManager MIB IOMMIB.MIB

LANDesk ClientManager MIB LDCM.MIB

LANDesk ServerManager MIB LDSM.MIB

Link Incident MIB LINK-INCIDENT.MIB

LSI Integrated Mirroring MIB Lsi1030.mib

LSI Hance Rapid MIB LSIRAID-IDE.mib

ExaByte MIB MatrixLibraryMib.mib

AMI Raid MIB MEGARAID.MIB

Mylex Raid MIB MLXRAID.MIB

MIB for PRIMEQUEST MMB-COM-MIB.mib

MIB for PRIMEQUEST MMB-ComTrap-MIB.mib

Multipath MIB MP.MIB

FSC's Mylex Raid MIB MYLEX.MIB

Network Appliance MIB NETAPP.MIB

Linux / Net-SNMP MIB net-snmp.mib

Network Appilance MIB NETAPP.MIB

NT Cluster MIB NTCluster.MIB

PCI hot plug MIB PciHotPlug.mib

APC Powernet UPS MIB Powernet.mib

PPC UPS MIB PPC.MIB

Promise Unified Raid MIB PROMISERAID.MIB

MIB name File name


SV IP Tivoli TEC 73


Promise IDE Raid MIB PROMISEV1.MIB

MIB for PRIMEQUEST PSA-COM-MIB.mib

MIB for PRIMEQUEST PSA-ComTrap-MIB.mib

MIB for PRIMEQUEST PSA-ExternalFileUnitTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinBcm5700Trap-MIB.mib

MIB for PRIMEQUEST PSA-LinEmulexTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinGdsTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinGlsTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinGrmpdTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinIntelE1000Trap-MIB.mib

MIB for PRIMEQUEST PSA-LinIntelE100Trap-MIB.mib

MIB for PRIMEQUEST PSA-LinLanComTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinLsiLogicTrap-MIB.mib

MIB for PRIMEQUEST PSA-LIN-MIB.mib

MIB for PRIMEQUEST PSA-LinScsiComTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinTg3Trap-MIB.mib

MIB for PRIMEQUEST PSA-WinBcm5700Trap-MIB.mib

MIB for PRIMEQUEST PSA-WinEmulexTrap-MIB.mib

MIB for PRIMEQUEST PSA-WinIntelE1000Trap-MIB.mib

MIB for PRIMEQUEST PSA-WinIntelE100Trap-MIB.mib

MIB for PRIMEQUEST PSA-WinLsiLogicTrap-MIB.mib

MIB for PRIMEQUEST PSA-WIN-MIB.mib

MIB for PRIMEQUEST PSA-LinIbTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinIntelE1000ETrap-MIB.mib

MIB for PRIMEQUEST PSA-LinIntelIgbTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinSvsRaidTrap-MIB.mib

MIB for PRIMEQUEST PSA-LinXframe2Trap-MIB.mib

MIB for PRIMEQUEST PSA-WinDiskMirrorTrap-MIB.mib

MIB for PRIMEQUEST PSA-WinDiskTrap-MIB.mib

MIB for PRIMEQUEST PSA-WinMpdTrap-MIB.mib

MIB for PRIMEQUEST PSA-WinSvsRaidTrap-MIB.mib

MIB name File name


74 SV IP Tivoli TEC


MIB for PRIMEQUEST PSA-WinXframe2Trap-MIB.mib

FSC RAID MIB RAID.mib

Siemens MIB-II Ethernet MIB RFC1157.MIB

Standard UPS MIB RFC1628.MIB

Rittal Rack Mib RMS-C_SNMPv1_contact.mib

Rittal Rack Mib RMS-C_SNMPv1_humid1.mib

Rittal Rack Mib RMS-C_SNMPv1_humid2.mib

Rittal Rack Mib RMS-C_SNMPv1_main.mib

Rittal Rack Mib RMS-C_SNMPv1_output.mib

Rittal Rack Mib RMS-C_SNMPv1_temp2.mib

ROMPilot MIB ROMPILOT.MIB

Blade Server MIB S31.MIB

Pathlight MIB SANMGRV1.MIB

Server Control MIB SC.MIB

New Server Control MIB SC2.MIB

Fujitsu ServerVisor MIB SERVERVI.MIB

ServerView Application MIB ServerView.mib

Status MIB Status.mib

HP Tape Alert MIB TAPEALRT.MIB

FSC PerformanceManager Mib Threshold.mib

Trap MIB TRAP.MIB

RFC1493 Trap MIB TRAP1493.MIB

RFC1757 Trap MIB TRAP1757.MIB

ACCTON Switch Trap MIB UNICORN-TRAP.MIB

UPS Manager MIB UPSMAN.MIB

FSC HACL MIB V1-FSCHACL.MIB

VMWare Traps MIB VMWARE-TRAPS-MIB.mib

Intel WFM MIB WFM.MIB

FSC x10sure MIB x10sureV1.mib

MIB name File name


SV IP Tivoli TEC 75


A more precise overview of which traps/events are considered in this version is provided in the ServerViewSNMPTraps.pdf file. This file can be found on the TME server in the directory %BINDIR%\generic_unix\TME\PLUS\SERVERVIEW.

SV IP Tivoli TEC 77

7 What to do if…This chapter provides information on application and service errors that can occur, and how to solve them.

7.1 ServerView events are not displayed in the TEC

If the TEC display does not display any of the ServerView traps sent, solve this problem with the aid of instructions in the sections below.

7.1.1 Configuring the server as a trap receiver

The server on which the SNMP adapter is implemented must be configured as a trap receiver.

I Read the sections “SNMP Trap Service on Windows” and “Running ServerView Frontend & TEC SNMP Adapter on the same system” in the “ServerView/Plus Module” release notes.

To check whether the traps of the ServerView agents are received by the SNMP adapter, start the SNMP adapter in the debug mode in the adapter directory with the following command:

bin\tecad_snmp.exe -d -c etc\tecad_snmp.conf

7.1.2 Communications between the SNMP adapter and the event server

To test the communications between the SNMP adapter and the event server, enter the following on the command line of the system with the SNMP adapter:

wpostmesg -f ...\etc\tecad_snmp.conf -m “Test message” TEC_Notice xxx

The event Test message should be displayed on the TEC. If this event is not displayed, check the general adapter configuration.

78 SV IP Tivoli TEC

Error message in the SNMP adapter configuration What to do if…

I If you cannot check the communications as described, copy the Tivoli program wpostmesg from the Event Server to the Tivoli Endpoint and try again.

7.1.3 SNMP adapter configuration

In order to receive ServerView traps, the SNMP adapter must be correctly configured. This means that the definitions of the ServerView classes must be present in the SNMP adapter configuration (tecad_snmp.cds and tecad_snmp.oid). To check the configuration of the SNMP adapter, proceed as follows:

Step 1Start the task Configure SNMP Adapter.

Step 2Enter the following on the command line:

wtdumprl -t “Jan 22 09:00:00 2005”

All events received since the date indicated in the TEC are displayed. If the SNMP adapter receives events in the debug mode that are not listed here, the adapter configuration (.cds, .oid) is incorrect. You should also note that events will not be defined in the current TEC rule base if they are displayed using wtdumprl with the comment parsing failed; in this case they are not displayed in the TEC GUI (see “TEC Configuration”).

7.1.4 TEC configuration

The TEC is correctly configured if the definitions of the ServerView classes are present in the current rule base. To configure the rule base, start the task Setup TEC Event Server for ServerView. To display ServerView events on the TEC you must use the configured TEC rule base.

7.2 Error message in the SNMP adapter configuration

If the error message Endpoint: <Endpoint name> not running at the moment! appears when configuring the SNMP adapter, this means that the Tivoli endpoint is not accessible. Check whether the endpoint client has been started or has some error.

SV IP Tivoli TEC 79

What to do if… Error message when running queries

7.3 Error message when running queries

If the error message No data found for Query ‘<xxx>´ occurs when running Primergy queries, this can be due to the following:

● No data are available in the Inventory Repository for the selected query, because the relevant PRIMERGY Inventory Profiles have not yet been distributed, or the corresponding components, e.g. the Mylex agent, are not being used.

● A generic Tivoli hardware scan has not yet been performed.

7.4 Error message in “Setup TEC Event Server for ServerView”

If, after executing the task Setup TEC Event Server for ServerView, a long list of error messages appears, beginning with New <xxx> rulebase does not compile and Superclass Specific SNMP Trap does not exist” this is due to the following:

The definitions of the ServerView classes are derived from the general SNMP class specific_SNMP_trap, which in turn is defined in the Tivoli file tecad_snmp.baroc.

Whenever you configure or clone a rule base for the ServerView events, make sure it contains the tecad_snmp.baroc file.

SV IP Tivoli TEC 81

IndexAactivation, icons for ServerView

integration 29application error 77

Ccommunications

SNMP adapter and event server 77

configuration 29configuring

SNMP adapter 43configuring event management 37creating a new rule base 40

Ddocumentation for ServerView

Suite 9documentation structure 8

Eenterprise event management 37event adapter 11event console 11event management 37event server 11

Hhardware requirements 13

Iicons 29installation requirements 12installing

from desktop 16from the command line 26SNMP Adapter 43SNMP adapter 43

MMMB Web interface

starting 35

Nnotational conventions 10

Ooperation error 77

Pprofile manager 30

Rreceiver

configuring 77removing ServerView/Plus 27rule base 40, 41

SServerView Operations Manager,

starting 34ServerView, starting 33setting up the event server 38setting up the TME 10 Enterprise

Console server 37SNMP adapter

configuring 43, 78installing 43

software requirements 13start 29Starting

MMB Web interface 35starting

ServerView 33ServerView Operations

Manager 34the ServerView/Plus for Tivoli

module 31subscription list 30

Ttarget groups 8TEC

configuration 78

82 SV IP Tivoli TEC

Index

Test message 77troubleshooting

application error 77operation error 77

Uuninstalling ServerView/Plus 27

Documents

ServerView Integration Pack for Tivoli TEC - Fujitsumanuals.ts.fujitsu.com/file/8200/sv-intpack-tivolitec-en.pdf · User Guide - English ServerView Suite FUJITSU Software ServerView