PRIMERGY ServerView Suite PRIMERGY ServerView Suite ServerView Integration 2.0 in Tivoli NetView A. Matthäus Fujitsu Siemens Computers GmbH München 81730 Munich e-mail: email: manuals@fujitsu-siemens.com Tel.
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. Fax forms for sending us your comments are included in the back of the manual. There you will also find the addresses of the relevant User Documentation Department.
Contents 1 1.1 1.2 1.3 1.4 1.5 1.6 Preface . . . . . . . . . . . . . . . Summary of Contents . . . . . . . . Background Information . . . . . . . Target Groups . . . . . . . . . . . . Related Publications . . . . . . . . . Changes From the Previous Version Notational Conventions . . . . . . . 2 2.1 2.2 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Definitions of Terms . . . . . . . . . . . . . . . . . . . . .
Contents 5 5.1 5.1.1 5.1.7 5.2 5.2.1 5.2.2 5.2.3 5.2.4 5.2.5 5.2.6 5.2.7 5.3 5.4 5.5 5.6 5.7 Configuration and Operation . . . . . . . . . . . . . . . . . . Configuring Fujitsu Siemens Servers with the Map Application . Creating a ServerView Component Symbol for a Fujitsu Siemens Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Selection Name . . . . . . . . . . . . . . . . . . . . . . . . . . Changes to the Fujitsu Siemens Server . . . . . . . . . . . . .
1 Preface Strategies to implement centralized server administration are becoming more and more important due to the increasingly crucial role played by networks based on independent servers in information technology today. This manual describes the functions and procedures for using the ServerView Integration in IBM Tivoli NetView. This Installation of the ServerView Integration for NetView enables the system management functions of IBM Tivoli NetView to be used with PRIMERGY ServerView.
Background Information 1.2 Preface Background Information ServerView runs on heterogeneous networks using the network management protocol SNMP (Simple Network Management Protocol) and can be easily linked with other management systems (e.g. HP OpenView NNM, IBM Tivoli NetView, Microsoft SMS, Novell ManageWise) via standardized interfaces. ServerView enables a trouble-free integration of Fujitsu Siemens PRIMERGY servers in enterprise-wide network management systems such as Tivoli.
Preface 1.3 Target Groups Target Groups This manual is intended for system administrators who use the ServerView Integration in NetView to manage Fujitsu Siemens Entry servers. It is therefore assumed that you already have some experience in the following areas: – operation and administration of Tivoli NetView, – operation and administration of ServerView, e.g., the interpretation of ServerView SNMP traps. 1.
Changes From the Previous Version Preface You will also find additional useful information on the subject of server administration: – in the ServerView information files, especially the Readme file, which contains the latest information that could not be included in the manual. The ServerView information files can be called from the ServerView program group by clicking on the corresponding entry.
Preface 1.6 Notational Conventions Notational Conventions The following notational conventions are used in this manual: V Warning 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. Ê This symbol indicates a step that you must perform in order to continue the procedure. italics Commands, menu items, button names, options, variables, file names and path names are printed in italics.
2 Introduction ServerView is a software package that monitors all important server functions such as the hard disk, fans, power supply and temperature and reports the measured values on a central monitoring console. You can run ServerView Integration in NetView on Windows 2000, Windows 2003 and Windows XP. ServerView Integration lets you use the functionality of ServerView and IBM Tivoli NetView at a central administration system. 2.
Definitions of Terms 2.2 Introduction Definitions of Terms Global directory names of NetView NetView is installed in the folder \usr\ov on the drive stored in the environment variable NV_DRIVE. The “ServerView Integration in NetView” product The “ServerView Integration in NetView” product consists of an integration package that you can add on to an existing NetView installation. ServerView application ServerView is a server management software for all devices with ServerView agents.
Introduction Definitions of Terms Symbol In NetView a symbol represents just one object in the NetView database in the NetView map. The status of a symbol can be determined from the following three sources: – from the status of the associated object, – from the status of all subordinate symbols (i.e.
3 Installation Before you start installing the “ServerView Integration in NetView” integration package, please make sure that you read all the installation requirements in this section. If you want to install the integration package in a NetView client/server environment, proceed as follows: 1. ServerView Integration in NetView must be first installed on the NetView server. 2. If you need the functionality of the integration package on a NetView client, you can then install the package on that client. 3.
Installation under Windows 3.3 Installation Installation under Windows Make the CD with the integration products for Tivoli NetView available on the system and change to the NetView subdirectory. Two installation methods can be selected via parameters on calling SETUP.
Installation Installation under Windows Ê Click Next to display dialog window with the “End User License Agreement”. Figure 2: Installation: “End User License Agreement” dialog window Ê Click Next to display the dialog window with general information on the integration package.
Installation under Windows Installation Ê Click Next. The displayed dialog window will offer you the option of canceling the installation process without applying any changes to the system. Figure 4: Installation: “Ready to install” dialog window Ê Click Next. The installation process will now copy the files to your system and configure NetView. Following a successful installation, the dialog window Installation Completed appears.
Installation Installation under Windows Figure 5: Installation: “Installation Completed” dialog window Ê Click Finish to complete the installation process. Ê Start the NetView console. 3.3.2 Silent Installation You can start the installation in silent mode by issuing the following call from the command line of a shell or from the Run dialog box on the Start menu: :\SETUP.EXE /S where is the letter of the drive associated with the installation medium.
Deinstallation under Windows 3.4 Installation Deinstallation under Windows To fully deinstall the integration package, you must perform the following actions manually in NetView before calling the deinstallation program: Ê Select the menu item Misc – Extended Discover – Reset all Fujitsu Siemens Server in the NetView console to clear all installed Fujitsu Siemens PRIMERGY servers from all NetView maps.
Installation Deinstallation under Windows Figure 7: Deinstallation: Delete Data Collection Ê Then open the Trap Settings window (menu Options – Trap Settings). Select NetView in the Select an enterprise group box. Delete the two traps Polling and Rearm of the ServerView status display. To do this, select SVPollRearm and SVPollThresh one after the other, and confirm each by clicking on Delete.
Deinstallation under Windows Installation Figure 8: Deinstallation: Delete the Polling and Rearm traps Ê Open the Trap Settings window (menu Options – Trap Settings). Delete all traps of the ServerView-specific enterprise systems. You will find a table with the traps that must be deleted in the chapter “Components of ServerView Integration in NetView” on page 29.
Installation Deinstallation under Windows Figure 9: Deinstallation: Delete traps Ê Start deinstallation in Control Panel/Software by selecting Fujitsu Siemens ServerView Integration in Tivoli NetView and clicking on Change/Remove button.
Deinstallation under Windows Installation Figure 10: Deinstallation: Select Control Panel/Software Ê Click on Next in the display deinstallation window to start deinstallation.
Installation Update Installation of ServerView Integration in NetView Ê Following successful deinstallation the Deinstallation Completed window appears. Click on Finish to complete the deinstallation process. Figure 12: Deinstallation: “Deinstallation Completed” window 3.5 Update Installation of ServerView Integration in NetView You can update an existing installation for all systems by first deinstalling and then reinstalling the integration package as described above.
4 Components of ServerView Integration in NetView This chapter describes all the components and configurations added to the NetView management program on installing the ServerView Integration in NetView. You will find details on how to configure, start and run the components of the ServerView Integration in NetView in the chapter “Configuration and Operation” on page 33. 4.
Objects in maps 4.1.1 Components Symbols The following symbol subclasses are created: 1. The symbol class Computer includes the symbol subclass FujitsuSiemens to represent Fujitsu Siemens PRIMERGY servers.
Components Objects in maps 2. The new symbol class FujitsuSiemensServerView is added to the Software symbol class. Figure 14: New symbol subclasses in the “Software” symbol class Component symbols of the Software:FujitsuSiemensServerView symbol type are used in the submap of a Fujitsu Siemens PRIMERGY server to display the status of all ServerView agents on that server. The Map application can automatically create these symbols and objects.
Objects in maps 4.1.2 Components Fields and Capabilities The integration package creates fields for internal use by the Map application and capability fields in the NetView database. The capability fields are special fields for classifying objects. The currently set capabilities of an object can be viewed in the Object Properties of that object. The ServerViewObj capability is used to classify all devices that are managed via the ServerView product.
Components 4.2 Status Display of ServerView Devices Status Display of ServerView Devices All ServerView devices are identified in the NetView map by the graphical symbol subclass FujitsuSiemens. The status of a device is shown in the map with color codes. In the case of Fujitsu Siemens servers that are configured accordingly, this status is determined from the status of all its component symbols. These component symbols can be found in the submap of the respective server.
Status Display of ServerView Devices 4.2.2 Components Threshold and Rearm Events The two events SVPollThresh and SVPollRearm are created in NetView. The Threshold event is triggered on polling the status variable SniInvCondition (Data Collection). This event defines the action (reaction script) that sets the device status in the NetView map. Figure 17: Threshold event The Rearm event is used to limit the threshold range for the Data Collection.
Components 4.2.3 ServerView Traps and MIBs Reaction Script The Reaction script \usr\ov\snistatustrap.bat is executed at every polling interval of the Data Collection for each polled node. This script sets the status of the polled ServerView device in the NetView map, depending on the current value of the status variable SniInvCondition for that device. 4.
Applications Components The ServerView MIBs are installed in the directory \usr\ov\snmp_mibs\fujitsuSiemens. The inventory MIB Invent.mib is loaded during the installation so that the Data Collection with the status variable SniInvCondition can be installed from this MIB. 4.4 Applications of ServerView Integration in NetView This section describes the applications available on installing the integration package. 4.4.
Components 4.4.4 Applications Deinstall Function The Deinstall function deletes the ServerViewObj capability from the NetView database for all PRIMERGY servers (i.e. for all severs for which the ServerViewObj capability was set by the Poll application). 4.4.5 ServerView Application Launch The ServerView Application Launch function starts the ServerView application from the NetView map.
5 Configuration and Operation This chapter describes how you can start up and manage the components installed with the integration package. In NetView you can automatically search your network for any network components in the “managed objects” (Discovery). With Discovery, NetView accesses the SNMP agents and assigns corresponding default symbols to the various device types. The components found are entered in the submap of the relevant device (e.g. IP interfaces or network cards). 5.
Configuring with the Map Application 5.1.1 Configuration and Operation Creating a ServerView Component Symbol for a Fujitsu Siemens Server The Map application creates a ServerView component symbol in the submap of a Fujitsu Siemens server with the following capabilities: – The symbol type is set to Software:FujitsuSiemensServerView – The label of the symbol is set to ServerView – The Status Source attribute of the symbol is set to Propagated, i.e.
Configuration and Operation 5.1.2 Configuring with the Map Application Selection Name The Map application automatically assigns the selection name of the ServerView component symbol, which depends on the selection name of the parent server. I Neither the selection name of the server, nor the selection name of the ServerView component symbol should be changed manually.
Configuring with the Map Application 5.1.3 Configuration and Operation Changes to the Fujitsu Siemens Server The Status Source attribute of the symbol is set to Propagated, i.e. the status of the symbol for the server is derived from the status of all component symbols. The default capabilities of the server are set in accordance with the corresponding symbol definition file.
Configuration and Operation 5.1.4 Configuring with the Map Application Manually Configuring a Fujitsu Siemens Server Select the symbol of the server in the map. You now have two methods by which you can configure a single node as a Fujitsu Siemens server: 1. Using the Context menu, change the symbol type to FujitsuSiemens. 2. Create a new server with one of these two symbol types in the map by selecting the menu item Object – New.
Configuring with the Map Application Configuration and Operation The Poll application enables the symbol type to be assigned more precisely. It can determine the symbol type of a device by checking whether a specific MIB object is supported by that device. All Poll application output is sent to the shell in which NetView was started.
Configuration and Operation Configuring with the Map Application sysObjectID_Value This parameter identifies a value for the MIB variable sysObjectID from the MIB-II in dot notation, beginning with a period, for example: “.1.3.6.1.4.1.231.1.3.1” - this is the value returned by all SINIX-N systems as a sysObjectID. All nodes returning this value for sysObject are to be tested for support of the MIB variables with object identifier MIB_ObjectID.
Status Indication in Map Configuration and Operation 5.2 Status Indication in the Map 5.2.1 The Status from the Viewpoint of NetView NetView determines the status of a device in the map by sending ICMP echo requests to the respective device. The status determined by this method only indicates the accessibility state of the device. To present the ServerView status described below, the Map application creates a ServerView component symbol in the submap of the server.
Configuration and Operation 5.2.3 Status Indication in Map Automatic Monitoring of the ServerView Status The following components automatically monitor this ServerView status: – Data Collection for the MIB object sniInvCondition from the INVENTORY-MIB – The Threshold and Rearm events for this Data Collection – A reaction script for evaluating the values received, which sets the status of the ServerView component symbol accordingly.
Status Indication in Map Configuration and Operation The Fujitsu Siemens servers are configured by the Map application and the Poll application so that NetView can determine the status of a server from the status of all of its component symbols. Consequently, such status changes are passed up through the map hierarchy and can change the status of the relevant server, segment, network, etc.
Configuration and Operation Status Indication in Map This is needed, for example, if the server is no longer accessible via SNMP (the SNMP agent is not running) and you want to prevent the server from being constantly displayed as a “faulty device” in the map. 5.2.6 SNMP Configuration The parameters you set here are used by the Poll application.
Status Indication in Map Configuration and Operation This reaction can be used to call scripts or any applications, to send e-mails, and so on. It is also possible to use this reaction to control (or transfer data to) any external systems with a shell interface, e.g. trouble ticket systems, paging software, etc. For more details on the shell interface and how to use it, please refer to the user documentation of the relevant external system.
Configuration and Operation 5.5 Operation of Status Display Operation of the Status Display for Fujitsu Siemens Servers The menu item Misc – Extended Discovery – Discover Fujitsu Siemens Server produces a graphical view of all devices in a hierarchic map. The Fujitsu Siemens servers are displayed in the map in accordance with their configuration and can be visibly distinguished from other devices.
Operation of Status Display Configuration and Operation Figure 24: Submap of a server with component symbols Component symbols can be created and managed by NetView itself or by any other applications such as the Map application, for example. The overall status of all ServerView agents on a server is determined by a Data Collection with Threshold monitoring and an associated reaction script and mapped to the ServerView component symbol in the submap of that server.
Configuration and Operation 5.6 Reset Server/Display Events Resetting Individual Fujitsu Siemens Servers You can use the menu option Misc – Extended Discovery – Reset selected Fujitsu Siemens Server in the NetView console to reset the configuration of the selected server, i.e., the server is then no longer shown as a Fujitsu Siemens server in the NetView map.
Reset Server/Display Events Configuration and Operation Figure 25: Event Browser window 48 Integration in Tivoli NetView
6 ServerView Application The ServerView application is a manager for all devices with ServerView agents. It is used in the integration in NetView under Windows to graphically represent the MIB variables from the corresponding MIBs and to configure the server. 6.1 Starting ServerView You start ServerView with the Application Launch function. This causes the network parameters of the selected Fujitsu Siemens PRIMERGY server to be passed from the NetView map to ServerView.
Starting ServerView ServerView Application Variant 1 In the NetView map first select the Fujitsu Siemens server (TRINKET in this example) for which the Application Launch function is to be executed. Start the Application Launch function via the menu Fujitsu Siemens – Start ServerView (at the top edge of the NetView window).
ServerView Application Starting ServerView Variant 2 In the NetView map first select the Fujitsu Siemens server (TRINKET in this example) for which the Application Launch function is to be executed. Start the Application Launch function by clicking on the Start Fujitsu ServerView icon (at the right edge of the NetView window).
Installing ServerView ServerView Application In both cases the ServerView window is opened and the selected Fujitsu Siemens server (TRINKET in this example) is shown in the server list. Figure 28: ServerView window showing the selected server 6.2 Installing ServerView If ServerView and NetView are to be installed on the same system, ServerView V3.x or higher must be installed first.
Figures Figure 1: Installation: First Setup window . . . . . . . . . . . . . . 12 Figure 2: Installation: “End User License Agreement” dialog window 13 Figure 3: Installation: “General information” in the dialog window . 13 Figure 4: Installation: “Ready to install” dialog window . . . . . . . 14 Figure 5: Installation: “Installation Completed” dialog window 15 Figure 6: Deinstallation: Menu item selection in the NetView console 16 Figure 7: Deinstallation: Delete Data Collection . . .
Figures Figure 25: Event Browser window . . . . . . . . . . . . . . . . . . 48 Figure 26: Start ServerView via menu . . . . . . . . . . . . . . . . 50 Figure 27: Starting ServerView with the ServerView icon . . . . . . 51 Figure 28: ServerView window showing the selected server 52 54 . . . .
Index A Application Launch function 49 automatic monitoring of ServerView status 41 C Capability ServerViewObj 9 Software 9 capability delete 31 ServerViewObj 26 component symbol 27 create for Siemens server 34 ServerView 46 type and label 34 configure Siemens server 33 contents of the manual 1 D Data Collection 27, 41 threshold range 28 Deinstall function 31 deinstallation under Windows 16 determine ServerView status 40 E element manager 46 environment variable NV_DRIVE 8 event logging 43 OV_Set_Status_Col
Index N NetView client 11 global directory name 8 map 7 object 8 status of a device in the map 40 symbol 9 NetView console 47 start ServerView 49 NetView database 8 NetView map reset server status 42 NetView status determine 41 NetView trap configuration integration of ServerView traps 29 network management system, integration 2 network node configure 30 Notational conventions 5 notational conventions 5 NV_DRIVE (environment variable) 8 O object 8 properties 26 objects 23 operating costs, reduce 2 P Poll ap
Index status variable SniInvCondition 28 symbol 9 symbol class 39 Computer 24 Software 25 symbol subclass 24 symbol type 39 symbol type Software:ServerView 9 T target group of this manual 3 Threshold event 28 threshold monitoring 41 threshold range, for Data Collection 28 trap display 47 trap configuration 29 U update installation 21 W Windows deinstall integration package 16 Integration in Tivoli NetView 57
Fujitsu Siemens Computers GmbH User Documentation 81730 Munich Germany Fax: (++49) 700 / 372 00000 email: manuals@fujitsu-siemens.com http://manuals.fujitsu-siemens.com Submitted by ✁ Comments on PRIMERGY ServerView Suite ServerView Integration 2.
Fujitsu Siemens Computers GmbH User Documentation 81730 Munich Germany Fax: (++49) 700 / 372 00000 email: manuals@fujitsu-siemens.com http://manuals.fujitsu-siemens.com Submitted by ✁ Comments on PRIMERGY ServerView Suite ServerView Integration 2.
