ServerView Integration Pack for Tivoli TEC

Transcription

1 ServerView Suite User Guide - English FUJITSU Software ServerView Suite ServerView Integration Pack for Tivoli TEC Edition February 2018

2 Comments Suggestions Corrections The User Documentation Department would like to know your opinion of this manual. Your feedback helps us optimize our documentation to suit your individual needs. Feel free to send us your comments by to Certified documentation according to DIN EN ISO 9001:2008 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2008. cognitas. Gesellschaft für Technik-Dokumentation mbh Copyright and Trademarks Copyright 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.

3 Contents 1 ServerView Integration for Tivoli TEC Preface Background information Target groups Related publications Changes since the previous version Documentation for ServerView Suite Notational conventions Introduction and installation Overview Installation requirements Software requirements Hardware requirements Upgrading ServerView/Plus version Uninstalling ServerView Integration in Tivoli Inventory Uninstalling ServerView/Plus module 2.7 for Tivoli Installing from the desktop Installing from the command line Configuring ServerView Integration in Tivoli Inventory Uninstalling ServerView Integration for Tivoli TEC Removing ServerView Integration in Tivoli Inventory Uninstalling ServerView Integration Pack 2.8 for Tivoli Using the ServerView Integration Pack in Tivoli TEC Icons Features SV IP Tivoli TEC

4 Contents Starting the ServerView for Tivoli module Starting ServerView Starting MMB Web interface Event management via the Enterprise Console Configuration Tivoli Enterprise Console server Fujitsu servers Setting up the Tivoli Enterprise Console server Creating a new rule base Adding to an existing rule base Installing/configuring the SNMP adapter Deconfiguring the SNMP adapter ServerView inventory using Tivoli inventory ServerView inventory data in Tivoli inventory - overview PRIMERGY_inventory_pm profile manager PRIMERGY_HW_QUERIES query library Gathering ServerView inventory data Adjustment of the PRIMERGY inventory profiles Save Results in Database Custom MIF Files To Be Read Definition of subscribers for the PRIMERGY inventory profiles Distribution of the PRIMERGY_HW inventory profile Requirements for successful distribution of PRIMERGY_HW Display ServerView inventory data Tivoli Configuration Repository Configuration Repository tables and views for ServerView Configuration Repository tables and columns for ServerView Integrated ServerView MIB files SV IP Tivoli TEC

5 Contents 7 What to do if ServerView events are not displayed in the TEC Configuring the server as a trap receiver Communications between the SNMP adapter and the event server SNMP adapter configuration TEC configuration Error message in the SNMP adapter configuration Error message when running queries Error message in Setup TEC Event Server for ServerView 79 Index SV IP Tivoli TEC

6

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. SV IP Tivoli TEC 7

8 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 infrastructure flexible system expansion as ServerView can be adapted to changing conditions 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 utilization 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 8 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 information 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 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 under the link Industry standard servers. SV IP Tivoli TEC 9

10 Related publications ServerView Integration for Tivoli/TEC 1.7 Notational conventions The following notational conventions are used in this manual: V Caution I 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. italics fixed font semi-bold fixed font <abc> [Key symbols] Table 1: Notational conventions Commands, menu items, names of buttons, options, variables, file names and path names are shown in italics in descriptive text. System outputs are indicated 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 actual values. 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. 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. 10 SV IP Tivoli TEC

11 2 Introduction and installation Through 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 SV IP Tivoli TEC 11

12 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 Enterprise 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. Activity Context Required Role Installing SV IP Tivoli TEC Tivoli install_product Table 2: Context and authorization role 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. 12 SV IP Tivoli TEC

13 Introduction and installation Installation requirements 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 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 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. SV IP Tivoli TEC 13

14 Upgrading ServerView/Plus v2.0 Introduction and Installation Machine Binaries Database Message Catalogs TMR server KB - Tivoli/Plus 3 MB KB Managed node Table 3: Disk space requirements 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) 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.cmd bash %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. 14 SV IP Tivoli TEC

15 Introduction and Installation Upgrading ServerView/Plus v 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 Step 2 Step 3 %WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmd bash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\ PLUSunconfig.sh Remove ServerView/Plus programs by entering the following command: del %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\*.* del %BINDIR%\..\..\msg_cat\C\SERVERVIEW* If 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. SV IP Tivoli TEC 15

16 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. 16 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. SV IP Tivoli TEC 17

18 Installing from the Desktop Introduction and Installation Step 2 Click 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 3 If you already know the path to the image, proceed as follows: Step 3.1 Enter the full path in the Path Name field. Step 3.2 Click the Set Path button to change to the specified directory. Step 3.3 Click 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. 18 SV IP Tivoli TEC

19 Introduction and Installation Installing from the Desktop Step 4 Step 5 If you do not know the exact path to the image: Step 4.1 From the Hosts scrolling list, choose the host on which the installation media are mounted. This updates the Directories scrolling list which shows the directories of the host. Step 4.2 From the Directories scrolling list, choose the directory containing the installation media. Step 4.3 Click 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. Figure 5: Plus Module Support (Link binaries) o in the Install Product dialog box SV IP Tivoli TEC 19

20 Installing from the Desktop Introduction and Installation Step 6 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) o. Click 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: 20 SV IP Tivoli TEC

21 Introduction and Installation Installing from the Desktop Step 7 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. Click 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: SV IP Tivoli TEC 21

22 Installing from the Desktop Introduction and Installation Step 8 Figure 7: Product Install after installation of Plus Module Support (Link binaries) o Or click the Cancel button to abort the installation process. When 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. 22 SV IP Tivoli TEC

23 Introduction and Installation Installing from the Desktop 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 10 Click 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 23

24 Installing from the Desktop Introduction and Installation 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. 24 SV IP Tivoli TEC

25 Introduction and Installation Installing from the Desktop Step 11 Click 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 12 When you see the message Finished product installation in the Product Install window, click Close to complete the installation process. SV IP Tivoli TEC 25

26 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. 26 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 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.cmd bash %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. SV IP Tivoli TEC 27

28 Uninstalling ServerView Integration Introduction and Installation 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 Step 2 Step 3 Step 4 %WINDIR%\system32\drivers\etc\Tivoli\setup_env.cmd bash %BINDIR%\..\generic_unix\TME\PLUS\SERVERVIEW\ PLUSunconfig.sh If 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* To clean up the object database, run wchkdb -u Deleting 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 o module, as these can be used by other Tivoli/Plus modules. 28 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 SV IP Tivoli TEC 29

30 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. 30 SV IP Tivoli TEC

31 Using the ServerView Integration Pack in Tivoli TEC Features 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. SV IP Tivoli TEC 31

32 Features Using the ServerView Integration Pack in 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. 32 SV IP Tivoli TEC

33 Using the ServerView Integration Pack in Tivoli TEC Features 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. SV IP Tivoli TEC 33

34 Features Using the ServerView Integration Pack in 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. 34 SV IP Tivoli TEC

35 Using the ServerView Integration Pack in Tivoli TEC Features 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 35

36

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 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. SV IP Tivoli TEC 37

38 Setting up the Tivoli Enterprise Console Server Event Management 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 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. Figure 19: ServerView Plus for Tivoli window 38 SV IP Tivoli TEC

39 Event Management Setting up the Tivoli Enterprise Console Server Step 1 Double-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: Step 2 Figure 20: Setup TEC Event-Server for ServerView window Once 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. SV IP Tivoli TEC 39

40 Setting up the Tivoli Enterprise Console Server Event Management 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 1 Step 2 Step 3 Enter the name of the rule base you want to create in the Rule Base Name (new or existing) name field. New 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 (\). Specify 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 4 Click Set and Close. 40 SV IP Tivoli TEC

41 Event Management Setting up the Tivoli Enterprise Console Server 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 1 Enter 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. Step 2 Click Set and Close. SV IP Tivoli TEC 41

42 Setting up the Tivoli Enterprise Console Server Event Management When setup of the Tivoli Enterprise Console is finished, a window displays the debugging output from execution task. Figure 23: Event server setup finished 42 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 Enterprise 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. SV IP Tivoli TEC 43

44 Installing/Configuring the SNMP Adapter Event Management Step 2 Step 3 Step 4 Step 5 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. In 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. In 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. Click Set and Close. The Configure_SNMP_Adapter (SERVERVIEW) Output window opens showing the logging data of the configuration process. 44 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. SV IP Tivoli TEC 45

46 Deconfiguring the SNMP Adapter Event Management Step 1 Figure 27: ServerView Plus for Tivoli window In the ServerView Plus for Tivoli window, double-click the Unconfigure SNMP Adapter icon. The Unconfig_SNMP_Adapter (SERVERVIEW) Output window opens. Step 2 Step 3 Figure 28: Unconfig_SNMP_Adapter window In 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. In 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. Step 4 Click Set and Close. 46 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 47

48

49 5 ServerView inventory using Tivoli 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_pm Starts 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 SV IP Tivoli TEC 49

50 Inventory Data in Tivoli Inventory ServerView Inventory 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 successfully 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 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 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. SV IP Tivoli TEC 51

52 Gathering ServerView Inventory Data ServerView Inventory Figure 31: PRIMERGY_Inventory_pm profile manager 52 SV IP Tivoli TEC

53 ServerView Inventory Gathering ServerView Inventory Data 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 SV IP Tivoli TEC 53

54 Gathering ServerView Inventory Data ServerView Inventory The main adjustments that may be necessary (to match real operating conditions) 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 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 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. 54 SV IP Tivoli TEC

55 ServerView Inventory Gathering ServerView Inventory Data 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 Distribution of the PRIMERGY_HW inventory profile You can distribute the inventory profiles individually or together. The prerequisite 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 1 In the Profile Manager window, mark the desired profiles and the subscriber(s) for which inventory data is to be collected: SV IP Tivoli TEC 55

56 Gathering ServerView Inventory Data ServerView Inventory Step 2 Figure 34: Distribution of the PRIMERGY_HW inventory profile Select the Profile Manager Distribute... menu item in the Profile Manager and confirm the following window with Distribute Now. Figure 35: Distribute Profiles menu 56 SV IP Tivoli TEC

57 ServerView Inventory Display ServerView Inventory Data 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: SV IP Tivoli TEC 57

58 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: 58 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. SV IP Tivoli TEC 59