PRIMEPOWER ServerView Suite PRIMEPOWER …manuals.ts.fujitsu.com/file/8838/o41581e3.pdf · 3 Integration in Tivoli ... 6.3.2 File contents ... for controlling and monitoring

Dok

usch

ablo

nen

(OE

CB

ook)

V1.

82us

by S

. Thu

ms

Ser

vice

s&To

ols

c

ogni

tas

Gm

bH 2

002

9. F

ebru

ar 2

006

Sta

nd 1

4:40

.14

Pfa

d: G

:\HP

OV

-22B

-Dez

05\m

040

77_

eng.

pdf\

inte

grat

ion.

vor

PRIMEPOWER ServerView Suite

PRIMEPOWER ServerView Suite V2.2 Integration in Enterprise Server Management SystemsHolger FunkFujitsu Siemens Computers GmbH Paderborn33094 Paderborne-mail: email: [email protected].: (05251) 14888 15Fax: 0 700 / 372 00001U41581-J-Z775-2-76Sprachen: En

Edition January 2006

Comments Suggestions CorrectionsThe User Documentation Department would like toknow your opinion of this manual. Your feedback helpsus optimize our documentation to suit your individual needs.

Fax forms for sending us your comments are included inthe back of the manual.

There you will also find the addresses of the relevantUser Documentation Department.

Certified documentation according to DIN EN ISO 9001:2000To 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:2000.

cognitas. Gesellschaft fr Technik-Dokumentation mbHwww.cognitas.de

Copyright and Trademarks

Edition January 2006

Copyright 2006 Fujitsu Siemens Computers GmbH.

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

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

This manual is printed on paper treated with chlorine-free bleach.

http://www.cognitas.de

Contents1 Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.1 Target groups . . . . . . . . . . . . . . . . . . . . . . . . . . . 11.2 Notational conventions . . . . . . . . . . . . . . . . . . . . . . 2

2 Integration in CA Unicenter NSM . . . . . . . . . . . . . . . . 32.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32.1.1 Availability of the integration product . . . . . . . . . . . . . . . 42.2 Integration product "CA Unicenter NSM Integration" . . . . . . . 52.2.1 Splitting the functionality for integration purposes . . . . . . . . . 52.2.2 Software requirements . . . . . . . . . . . . . . . . . . . . . . 62.2.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2.4 Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . 72.2.5 Configuring the SNMP agents . . . . . . . . . . . . . . . . . . . 72.2.6 Defining compatibility mode . . . . . . . . . . . . . . . . . . . . 82.3 Scope of performance of the integration product . . . . . . . . . 92.3.1 World View 2D map . . . . . . . . . . . . . . . . . . . . . . . 102.3.2 World View 3D map . . . . . . . . . . . . . . . . . . . . . . . 122.3.3 Representing partitionable systems with Business Process View 132.3.4 Enterprise console . . . . . . . . . . . . . . . . . . . . . . . 152.3.5 Displaying the status of components (Unispace) . . . . . . . . 162.3.6 Object View . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.3.7 Node View . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202.3.8 MIB Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . 212.3.9 DSM View (Properties) . . . . . . . . . . . . . . . . . . . . . 222.3.10 Agent View . . . . . . . . . . . . . . . . . . . . . . . . . . . 232.3.11 Event Browser . . . . . . . . . . . . . . . . . . . . . . . . . . 242.4 SNMP information: Interpretation, implementation and special

features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252.4.1 System object ID . . . . . . . . . . . . . . . . . . . . . . . . 252.4.2 Handling SNMP traps . . . . . . . . . . . . . . . . . . . . . . 262.4.3 PRIMEPOWER integration in Asset Management . . . . . . . 312.4.3.1 UAM requirements . . . . . . . . . . . . . . . . . . . . . . . 312.4.3.2 Creating hardware inventory data . . . . . . . . . . . . . . . . 312.4.3.3 Work steps . . . . . . . . . . . . . . . . . . . . . . . . . . . 322.4.3.4 MIF files on PRIMEPOWER systems . . . . . . . . . . . . . . 33

3 Integration in Tivoli . . . . . . . . . . . . . . . . . . . . . . 393.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.1.1 Availability of integration products . . . . . . . . . . . . . . . . 403.2 Integration product "Tivoli TEC Integration" . . . . . . . . . . . 423.2.1 Software requirements . . . . . . . . . . . . . . . . . . . . . 42

U41581-J-Z775-2-76

Contents

3.2.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.2.2.1 Dependencies on other Tivoli products . . . . . . . . . . . . . 433.2.2.2 Installation via the Tivoli desktop . . . . . . . . . . . . . . . . 433.2.2.3 Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . 493.2.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 503.2.3.1 WebSysAdmin SmartSet for Tivoli . . . . . . . . . . . . . . . 503.2.3.2 The Setup_TEC_for_WSA job . . . . . . . . . . . . . . . . . 523.2.3.3 The Config_SNMP job . . . . . . . . . . . . . . . . . . . . . 553.2.3.4 The Unconfig_SNMP job . . . . . . . . . . . . . . . . . . . . 573.2.3.5 The Config_SNMP_local job . . . . . . . . . . . . . . . . . . 593.2.3.6 The Unconfig_SNMP_local job . . . . . . . . . . . . . . . . . 603.2.3.7 TEC classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 613.2.3.8 TEC rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623.2.3.9 Testing aids . . . . . . . . . . . . . . . . . . . . . . . . . . . 633.2.3.10 if ...? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643.3 Integration product "Tivoli NetView Integration" . . . . . . . . . 673.3.1 Software requirements . . . . . . . . . . . . . . . . . . . . . 683.3.2 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683.3.2.1 Dependencies on other Tivoli products . . . . . . . . . . . . . 683.3.2.2 Installation on Windows NT . . . . . . . . . . . . . . . . . . . 693.3.2.3 Installation on Sun Solaris . . . . . . . . . . . . . . . . . . . . 723.3.2.4 Deinstallation on Windows NT . . . . . . . . . . . . . . . . . 763.3.2.5 Deinstallation on Sun Solaris . . . . . . . . . . . . . . . . . . 783.3.3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . 823.3.3.1 Integration in the NetView IP map . . . . . . . . . . . . . . . . 823.3.3.2 MIB and event integration . . . . . . . . . . . . . . . . . . . . 863.3.3.3 Further PRIMEPOWER ServerView Suite menu calls . . . . . 953.3.3.4 Definition of a PRIMEPOWER ServerView Suite SmartSet . . . 973.3.3.5 WSA event configuration for Tivoli NetView . . . . . . . . . . . 993.3.3.6 Testing aids . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003.3.3.7 What to do if ... . . . . . . . . . . . . . . . . . . . . . . . . . 101

4 Integration in HP OpenView NNM . . . . . . . . . . . . . . . 1034.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1034.1.1 Availability of the integration product . . . . . . . . . . . . . . 1044.2 Integration product "HP OpenView NNM Integration" . . . . . . 1054.2.1 Splitting the functionality for integration purposes . . . . . . . . 1054.2.2 Software requirements . . . . . . . . . . . . . . . . . . . . . 1064.2.3 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074.2.4 Deinstallation . . . . . . . . . . . . . . . . . . . . . . . . . . 1074.2.5 Update installation . . . . . . . . . . . . . . . . . . . . . . . . 1084.2.6 Display of the PRIMEPOWER systems . . . . . . . . . . . . . 1084.2.6.1 Icon classes . . . . . . . . . . . . . . . . . . . . . . . . . . . 1104.2.6.2 Fields and capabilities . . . . . . . . . . . . . . . . . . . . . . 111

U41581-J-Z775-2-76

Contents

4.2.7 Traps of the PRIMEPOWER ServerView Suite . . . . . . . . . 1114.2.7.1 Alarm category . . . . . . . . . . . . . . . . . . . . . . . . . 1114.2.7.2 Data collection (status monitoring) . . . . . . . . . . . . . . . 1114.2.8 Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1124.2.8.1 Calling the PRIMEPOWER ServerView Suite . . . . . . . . . . 1124.2.8.2 Calling the PRIMEPOWER Discovery action . . . . . . . . . . 113

5 Appendix I . . . . . . . . . . . . . . . . . . . . . . . . . . . 1155.1 Configuring the SNMP EMANATE master agent . . . . . . . . 1155.1.1 SNMP agent architecture within the PRIMEPOWER

ServerView Suite . . . . . . . . . . . . . . . . . . . . . . . . 1165.1.2 Security mechanisms for SNMP . . . . . . . . . . . . . . . . 1175.1.3 Extended security mechanisms in SNMPv3 . . . . . . . . . . 1185.1.4 Configuration steps . . . . . . . . . . . . . . . . . . . . . . . 1205.1.5 Configuration file snmpd.cnf . . . . . . . . . . . . . . . . . . . 1215.1.6 Definition of access to the agent via SNMPv1 requests . . . . 1225.1.7 Definition of access to agent via SNMPv3 requests . . . . . . 1285.1.8 Definition of access to an agent via HTTP requests . . . . . . 1325.1.9 Definition of the trap targets . . . . . . . . . . . . . . . . . . . 1355.1.10 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1425.1.11 Configuring the EMANATE master agent for the

PRIMEPOWER ServerView Suite . . . . . . . . . . . . . . . 1435.1.12 Configuring the EMANATE agent for CA Unicenter integration . 149

6 Appendix II . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516.1 MIB file wsatrap.mib . . . . . . . . . . . . . . . . . . . . . . . 1516.1.1 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1516.1.2 File contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 1546.1.3 Error comments . . . . . . . . . . . . . . . . . . . . . . . . . 1776.2 MIB file domagt.mib . . . . . . . . . . . . . . . . . . . . . . . 1796.2.1 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796.2.2 File contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 1796.3 MIB file uniserv.mib . . . . . . . . . . . . . . . . . . . . . . . 1856.3.1 Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1856.3.2 File contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

U41581-J-Z775-2-76

1 PrefaceAll system management interfaces are combined in Fujitsu Siemens Computers in the ServerView Suite, of which there are two variants for the two server families PRIMERGY and PRIMEPOWER. Accordingly, there is a separate manual series for each of these server families.

The administration interface for the PRIMEPOWER server family is called PRIMEPOWER ServerView Suite. It was previously known as WebSysAdmin (or WSA for short) and is described in a separate manual of the same name. This present manual, which was previously integrated in the old WebSysAdmin 2.1 manual, supplements the aforementioned manual and is now called PRIME-POWER ServerView Suite 2.2.

This manual describes products, which allow PRIMEPOWER systems and their management interfaces to be integrated in the global IT management products CA Unicenter NSM, Tivoli and HP OpenView NNM.

CA Unicenter NSM, Tivoli and HP OpenView NNM are IT management solutions for controlling and monitoring systems, networks, databases and applications. The integration product for CA Unicenter NSM is called CA Unicenter NSM Integration. The two integration products for Tivoli are called Tivoli TEC Integration and Tivoli NetView Integration. The integration product for HP OpenView NNM is called HP OpenView NNM Integration.

I Because of the current classification and the associated renaming of the administration interface from WebSysAdmin to PRIMEPOWER ServerView Suite, overlaps between the old and new names often arise in the mask and component names in the interface as it was not possible to change the names in the integration products mentioned. Therefore, where the old name WebSysAdmin arises, this should often (not always!) be under-stood as the new name PRIMEPOWER ServerView Suite. The old abbrevi-ation WSA also still appears frequently in the path and file names.

1.1 Target groups

This manual is written primarily for system administrators and field engineering staff. Sound operating system and hardware knowledge is required as well as familiarity with the basics of the WebSysAdmin graphical user interface. Similarly, sound basic knowledge of the CA Unicenter NSM, Tivoli TEC, Tivoli NetView and HP OpenView NNM products is also required.

U41581-J-Z775-2-76 1

Notational conventions Preface

1.2 Notational conventions

The following notational conventions are used in this manual.

italics Denote names of commands, system calls, functions, files, procedures, programs etc. as well as menu options and input/output fields from figures in the main body of text.

Name (extension)Commands, system calls, functions, files, interfaces etc., are given an extension in brackets if manual pages are available for them. The extension indicates the chapter in which the manual page is described.

You can show the manual pages on the screen with the man [see man(1)] command. See the manual command for man itself for information about using this command. To do this, enter man man.

fixed-pitch fontIndicates system output, such as error messages, messages, notes, file excerpts and program examples.

fixed-pitch semi-bold fontDenotes user input in examples.

Indicates activities to be carried out by the user.

I Highlights additional information that should be noted.V Indicates the possible risk of data loss.

2 U41581-J-Z775-2-76

2 Integration in CA Unicenter NSM

2.1 Overview

CA Unicenter NSM is a product that allows a worldwide network of the most varied systems (computers, routers, bridges etc.) to be administered centrally.

The integration of the PRIMEPOWER systems in CA Unicenter NSM is charac-terized by the following functions:

1. Representation of PRIMEPOWER systems and their states in Worldview using special icons

2. Grouping of partitionable systems and system consoles with Business Process View

3. Calling of the PRIMEPOWER ServerView Suite by selecting an object menu

4. Ergonomic representation of hardware messages in the enterprise console of CA Unicenter NSM

I The descriptions below do not provide a complete introduction to CA Unicenter NSM. Rather only those parts (masks, menus) that are displayed by the integration product are described.

U41581-J-Z775-2-76 3

Overview Integration in CA Unicenter NSM

2.1.1 Availability of the integration product

I The integration product only runs on Windows systems.

The integration product for CA Unicenter NSM is available on the node on which the PRIMEPOWER ServerView Suite is installed and can be downloaded from there using an Internet browser. The following address should be entered in the URL line:

http://hostname:8883

You then access the following download page:

Figure 1: Download page for the CA Unicenter integration product

By clicking the CA Unicenter NSM Integration link, you load a file called WsaTng-Integration.exe onto your system.

4 U41581-J-Z775-2-76

Integration in CA Unicenter NSM Integration product

2.2 Integration product "CA Unicenter NSM Integration"

2.2.1 Splitting the functionality for integration purposes

The integration of the PRIMEPOWER systems in CA Unicenter NSM is divided into two parts. These are:

The SNMP agents responsible for monitoring the systems and transferring the status.

The files responsible for integrating information transferred by the SNMP agents and displaying it in CA Unicenter NSM.

The SNMP agents are only available on PRIMEPOWER systems and the files for the integration only on Windows platforms.

The next diagram should clarify how the functionality is divided:

The SNMP agents on the PRIMEPOWER system monitor the status of the hardware and the status of the systems in an administration domain (cf. manual "PRIMEPOWER ServerView Suite V2.2. System Administration within a Domain"). The administration system (and hence CA Unicenter NSM) informs the user of these states or any changes to them using SNMP traps. General information on each system is likewise transferred to the administration system via the SNMP protocol. Apart from various other information, this data also

U41581-J-Z775-2-76 5

Integration product Integration in CA Unicenter NSM

includes the system object ID. This ID identifies the system within CA Unicenter NSM and assigns it to a specific system class. Apart from the IP address of the administration system, this system object ID is a parameter that can be configured on the PRIMEPOWER ServerView Suite SNMP agent. The section SNMP information: Interpretation, implementation and special features on page 25 contains a precise description of this parameter and its meaning.

2.2.2 Software requirements

CA Unicenter NSM Version V3.1 or higher is required as well as the PRIME-POWER ServerView Suite Version V2.2.

Furthermore, the following software requirements must be fulfilled for using the integration product:

Operating system

Windows NT, Windows 2000, ...

CA Unicenter software

World View component

Enterprise console

DSM layer

SNMP stack

The basis of the integration is the SNMP stack of the PRIMEPOWER ServerView Suite, which comprises the following components:

SMAWsnmpm (SNMP master agent in.snmpdm)

SMAWadapt (Adapter subagent adaptagt)

SMAWwsagt

PRIMEPOWER ServerView subagent wsaagt, cf. section MIB file wsatrap.mib on page 151

SMAWdoagt

Domain agent domagt, cf. section MIB file domagt.mib on page 179 (only runs on a management server)

6 U41581-J-Z775-2-76

Integration in CA Unicenter NSM Integration product

SMAWunagt

Partition agent unagt, cf. section MIB file uniserv.mib on page 185 (only runs on an SMC)

The PRIMEPOWER ServerView Suite must be installed on the system being monitored

The PRIMEPOWER ServerView Suite application must be installed on the management station

2.2.3 Installation

You install the integration product by starting the downloaded WsaTngInte-gration.exe file and following the installation shield.

The installation procedure checks whether the listed software requirements have been fulfilled. If this is not the case, a suitable message is issued and the installation is aborted.

2.2.4 Deinstallation

The deinstallation process for the integration product deletes all previously installed product files as well as all entries in the start menu and in the registry. The object classes inserted in the repository of the CA Unicenter NSM etc. are likewise deleted and the changes are cancelled in the configuration.

2.2.5 Configuring the SNMP agents

In order for the PRIMEPOWER systems to be monitored by CA Unicenter NSM, it is necessary that these systems send all SNMP traps to CA Unicenter NSM. The SNMP agents of the PRIMEPOWER systems have to be configured appro-priately for this purpose.

In addition, the system object ID must be correctly defined so that the PRIME-POWER systems can also be discovered correctly by CA Unicenter NSM. The settings are made in the snmpd.cnf file.

Further details are provided in the section Configuring the EMANATE agent for CA Unicenter integration on page 149.

U41581-J-Z775-2-76 7

Integration product Integration in CA Unicenter NSM

If changes are made in this file, these new settings are activated the next time the SNMP agent is started.

2.2.6 Defining compatibility mode

New messages are processed in the current version of CA Unicenter integration. The key word Newmode must be entered in the /etc/snmp/wsaagt/wsaagt.cnf file on the PRIMEPOWER systems in order for these new SNMP messages to be sent by PRIMEPOWER ServerView agents.

I In order to be able to use the new functions of CA Unicenter integration, the PRIMEPOWER ServerView Suite V2.2 must be installed on the PRIME-POWER systems. Newmode must be set as the compatibility mode for the agents.

8 U41581-J-Z775-2-76

Integration in CA Unicenter NSM Scope of performance

2.3 Scope of performance of the integration product

The following functionality is available to the administrator when integrating the PRIMEPOWER ServerView Suite in CA Unicenter NSM:

Display and monitoring of all PRIMEPOWER systems as a separate host class in the World View 2D map and 3D map.

Option to invoke the PRIMEPOWER ServerView Suite from the popup menu of the selected PRIMEPOWER system directly from the network overview of the World View 2D or 3D map.

Display of all SNMP traps received from the monitored PRIMEPOWER systems on the Enterprise Manager console.

A discovery function must be successfully executed first for the relevant subnet and the SNMP agents listed in section Software requirements on page 6 must be installed on the systems being monitored.

Monitoring of the states of individual hardware components (differentiated on the basis of storage, controller, environmental).

Grouping in the Business Process View.

This functionality is described in greater detail in the next sections.

U41581-J-Z775-2-76 9

Scope of performance Integration in CA Unicenter NSM

2.3.1 World View 2D map

The World View tool offered by CA Unicenter shows the administrator a 2D network map of all components and systems in the network. The systems are represented by the assigned icons. The next diagram shows an extract from such a network map:

Figure 2: World View 2D map

The following icon was selected for displaying PRIMEPOWER systems in the 2D map:

Figure 3: 2D representation

The current status of the systems is communicated to the administrator based on the color of the icon. The following states and colors are defined:

Color of icon Status of system

black down

yellow warning

red critical

green normal

10 U41581-J-Z775-2-76


As soon as an SNMP trap from one of the systems in the network map is received by the administration system, the new status reported in this trap is transferred to this map.

As additional functionality, the administrator is offered a convenient option for calling the PRIMEPOWER ServerView Suite by selecting the icon of the same name.

The right mouse button provides access to a system-dependent popup menu for every system. The PRIMEPOWER ServerView menu option was added to this menu for the PRIMEPOWER systems. This menu is shown in the next diagram:

Figure 4: PRIMEPOWER popup menu

Selecting/activating this menu option invokes the PRIMEPOWER ServerView Suite for the system selected in the network map.

light blue minor

gray unknown

violet major


U41581-J-Z775-2-76 11


2.3.2 World View 3D map

This view shows the administrator the selected network in 3D. The relevant systems are also represented here with their assigned icons. However, the icons in this case are three-dimensional and can thus be observed from all sides as well as from within.

The following icon was assigned to the PRIMEPOWER system for this purpose:

Figure 5: 3D map

If a system does not have the status normal, this is indicated by a flare on the system icon. The colors of these flares correspond to the system states outlined in the section Displaying the status of components (Unispace) on page 16.

The remaining functionality is the same as that in the 2D map and was already described in the previous section.

12 U41581-J-Z775-2-76


2.3.3 Representing partitionable systems with Business Process View

The Business Process View is used to create so-called containers for certain objects, in other words to define the objects as belonging to a group. Such containers are created automatically by the integration product for partitionable systems.

All system management consoles (SMC) are grouped at the top level under Consoles:

Figure 6: Administered objects in the Business Process View

If you click the Consoles icon, you will be shown icons for the individual consoles. You can then open a console and see a Business Process View for every machine (there is only one machine called zar in the example):

U41581-J-Z775-2-76 13


Figure 7: Display of a machine in the Business Process View

If you open the machine zar, you will be shown the partitions of this machine:

Figure 8: Display of partitions of a machine in the Business Process View

14 U41581-J-Z775-2-76


2.3.4 Enterprise console

Apart from other information, the console displays all SNMP traps received by the administration system. These SNMP traps are generally not legible in raw form. The traps sent by the PRIMEPOWER ServerView Suite SNMP agent are converted to readable text so that they can be more readily understood by the administrator. The next diagram shows an example of this:

Figure 9: Trap console display

The entry labeled Trap 1 is an SNMP trap, which is converted to readable form. All traps received from a PRIMEPOWER ServerView Suite SNMP agent are shown in converted form. This conversion is described in the section SNMP infor-mation: Interpretation, implementation and special features on page 25.

U41581-J-Z775-2-76 15


2.3.5 Displaying the status of components (Unispace)

The tools for displaying the system components allow closer investigation of the status of the administered systems. While the World View tool only shows the status of the entire system, this option allows a more in-depth look at the system. If a problem arises, therefore, the administrator can more readily determine which component caused the particular problem.

In order to access this component view for a system, it is necessary to select the desired system in the World View 2D map. Double-click with the left mouse button to access the desired detailed view of the Unispace. This is shown in the next diagram.

Figure 10: World View 2D map

The administrator can also establish the current status of the components in this case by the color of the icons. The assignment is as follows:


black down

yellow warning

red critical

green normal

light blue minor

gray unknown

violet major

16 U41581-J-Z775-2-76


The diagram above therefore shows us the system zeit in the status critical (color of icon = red). This status is caused by the WsaHost component, as this has likewise assumed the status critical. The Ping component, on the other hand, has the status normal (color of icon = green).

An option to call the PRIMEPOWER ServerView Suite directly has also been integrated here for this system so that it is easier for the administrator to find out more about the cause of the critical status from this environment. Right-click the WsaHost icon to open the popup menu shown above, which also contains a menu option for starting the PRIMEPOWER ServerView Suite.

The following view is entered by double-clicking the WsaHost icon in the previous figure:

Figure 11: World View 2D map showing the components

This view shows the components Hardware, Domain, and Partition. The compo-nents represent the hardware, domain and partition status of the selected system. The administrator can also determine the current status of the compo-nents here by the color of the icons.

If you open the Hardware icon by right-clicking it, you will be offered three additional icons, namely Controller, Environment and Storage, which allow an error to be assigned more precisely to a component.

Right-click the Domain icon to open the popup menu displayed above. Apart from the already familiar menu option for starting the PRIMEPOWER ServerView Suite, this menu contains other menu options for calling the different CA Unicenter NSM components.

U41581-J-Z775-2-76 17


The most important of these tools from the point of view of the PRIMEPOWER ServerView integration are described below. You will find more detailed infor-mation in the documentation for CA Unicenter NSM.

18 U41581-J-Z775-2-76


2.3.6 Object View

The Object View starts a MIB browser, which provides access to the MIB variables for the relevant object. The respective data displayed for the selected components depends on how the tool is called.

You can choose the MIBs to be displayed via a popup menu. The next diagram shows how the tool is called via a selected PRIMEPOWER ServerView component:

Figure 12: Call of the Object View tool via a selected component

Of the MIBs offered in the popup menu, the following are important:

wsatrap.mib

dominfo.mib

uniserv.mib

U41581-J-Z775-2-76 19


2.3.7 Node View

Additional detailed information is available on a PRIMEPOWER object via the Node View and the tools that can be called from this view. Node View is called from the popup menu for the selected component. The following diagram shows the view that appears next:

Figure 13: Node View tool view

The status of the component is highlighted in color here also and the last SNMP information received is displayed.

The icons Controller, Environment and Storage allow an error to be assigned more precisely to a component.

Further details are available via the popup menu (right mouse button).

20 U41581-J-Z775-2-76


2.3.8 MIB Browser

When this option is called, the MIB Browser displays information about the component for which this call was made. This is the same information as is also available in the Object View. However, the view in this case is prepared especially for the components. The next diagram shows information about the PRIME-POWER ServerView component.

Figure 14: MIB Browser showing information about the component

U41581-J-Z775-2-76 21


2.3.9 DSM View (Properties)

When you call the Properties menu option, general information is made available on the selected system or the selected component in the DSM View. In the case of the PRIMEPOWER ServerView Suite, this includes information about the agent such as name, class, poll interval etc., in addition to the system name, IP address, etc. The next diagram contains an example:

Figure 15: Properties menu option showing information about the agent

22 U41581-J-Z775-2-76


2.3.10 Agent View

Calling this option in the popup menu invokes a tool, which displays general information about the current system as well as information about the selected component. This can be seen in the next diagram:

Figure 16: Agent View menu option showing information about the current system

U41581-J-Z775-2-76 23


2.3.11 Event Browser

The Event Browser menu option provides information in the form of plain text messages on the PRIMEPOWER ServerView events received. The following diagram shows a snapshot from everyday operation:

Figure 17: Event Browser menu option showing information about events received

24 U41581-J-Z775-2-76

Integration in CA Unicenter NSM SNMP information

2.4 SNMP information: Interpretation, implementation and special features

This section describes the handling of the SNMP traps from the PRIMEPOWER SNMP agent by the CA integration module as well as the special features of the system object ID.

2.4.1 System object ID

During installation of the integration functionality in CA Unicenter NSM, the PRIMEPOWER class is defined for displaying the PRIMEPOWER systems in the World View. Among other things, this class is assigned the system object ID 1.3.6.1.4.1.231.1.16.1. This results in all systems that log on to CA Unicenter NSM with this ID being assigned to the PRIMEPOWER class. They are displayed, for example, with the PRIMEPOWER icon in the World View and are described as PRIMEPOWER systems, etc.

However, since some software products assume that they will find these systems in the Host/Solaris class, a second system object ID (1.3.6.1.4.1.231.1.16.2) has also been defined. This ID is added to the Solaris class during installation of PRIMEPOWER integration functionality. This second ID allows users determine how the PRIMEPOWER systems will be displayed in their installations. The desired system object ID must simply be set on the PRIMEPOWER system prior to discovery for the SNMP agent.

The configuration of the Solaris object ID leads to a different view of the systems in the World View and also means that the PRIMEPOWER ServerView Suite can only be called from World View within the Unispace (selection of PRIMEPOWER ServerView agent icon) for these systems. However, the remaining functionality is fully preserved.

I The settings are made in the /etc/snmp/agt/wsaagt.cnf file.

U41581-J-Z775-2-76 25

SNMP information Integration in CA Unicenter NSM

2.4.2 Handling SNMP traps

SNMP traps from the PRIMEPOWER SNMP agent are received by the agents of the Distributed State Machine (DSM) from CA Unicenter NSM. The DSM presents the hardware and domainadmin status of the system in the Hardware, Domain and Partition components. It represents the new status of the PRIME-POWER system following receipt of a trap.

The following traps are processed here:

Hardware traps:

Traps Meaning

wsaAgentStart The PRIMEPOWER ServerView SNMP agent was started.

wsaEnvironmentHardwareDefectSetDefect flag was set for a HW component.

wsaStorageHardwareDefectSetDefect flag was set for a storage component.

wsaControllerHardwareDefectSet Defect flag was set for a controller component.

wsaEnvironmentHardwareErrorSet A HW error flag was set.

wsaStorageHardwareErrorSet A storage error flag was set.

wsaControllerHardwareErrorSet A controller error flag was set.

wsaEnvironmentRepairA HW error was resolved, but an error may still exist.

wsaStorageRepairA storage error was resolved, but an error may still exist.

wsaControllerRepair A controller error was resolved, but an error may still exist.

26 U41581-J-Z775-2-76


DomainAdmin traps:

These different traps give rise to the following states that are to be displayed with DSM:

DomainAdmin states:

I Domain states are only accessible on a management server of PRIME-POWER ServerView Suite.

The tables below show the status derived from the old status combined with the current trap.

Hardware State

The following modules belong to the "Environment" group:

Panel

Fan

Power supplies

External power supply

Traps Meaning

domNodeOffline A node is offline.

domNodeOnline A node is online.

domNodeAdded A node was added to the domain.

domNodeDeleted A node was deleted from the domain.

Status Meaning

OK Domain communication with all nodes is active.

broken The connection to a node is broken.

U41581-J-Z775-2-76 27


Abbreviations for environment traps:

EHES: EnvHardwareErrorSetEHDS: EnvHardwareDefectSetER: EnvRepair

(1): If there are no further error or defect flags(2): If there is still an error flag(3): If there is still a defect flag

Environment traps

Event Error flag set Defect flag set Repair flag set

State

ok EHES/error EHDS/defect ER/ok

error EHES/error EHDS/defect ER/okER/error (2)

defect EHES/defect EHDS/defect ER/ok (1)ER/defect (3)

28 U41581-J-Z775-2-76


All modules that do not belong to the Environment or Storage group belong to the "Controller" group.

Abbreviations for controller traps:

CHES: ControllerHardwareErrorSetCHDS: ControllerHardwareDefectSetCR: ControllerRepair


Controller traps


State

ok CHES/error CHDS/defect CR/ok

error CHES/error CHDS/defect CR/okCR/error (2

defect CHES/defect CHDS/defect CR/ok (1)CR/defect (3)

U41581-J-Z775-2-76 29


The following modules belong to the "Storage" group:

Panel

Disc

Floppy

CD-ROM

Abbreviations for storage traps:

SHES: StorageHardwareErrorSetSHDS: StorageHardwareDefectSetSR: StorageRepair


Storage traps


State

ok SHES/error SHDS/defect SR/ok

error SHES/error SHDS/defect SR/okSR/error (2

defect SHES/defect SHDS/defect SR/ok (1)SR/defect (3)

30 U41581-J-Z775-2-76


2.4.3 PRIMEPOWER integration in Asset Management

The hardware inventory data for a PRIMEPOWER machine can be integrated in CA Unicenter Asset Management. This means that the PRIMEPOWER machine is visible as a node on the Unicenter Asset Management (UAM) admin console and that apart from the Solaris data established generally by UAM, additional data groups with special hardware inventory data for the PRIME-POWER machine are displayed.

2.4.3.1 UAM requirements

CA Unicenter supports the integration of the PRIMEPOWER machines with UAM 4.0, Service Pack 1. Apart from the UAM engine, the UAM sector server must also be installed in the UAM domain. The UAM Solaris Agent from UAM 4.0, Service Pack 1 must be installed on every PRIMEPOWER machine.

Following installation of the UAM agent on the PRIMEPOWER machine, this agent must be called once:$INSTALL/UnicenterAssetManagement/Agent/amax_do

The installation directory $INSTALL for UAM4.0 is /opt/CA by default.

2.4.3.2 Creating hardware inventory data

Calling /etc/init.d/updateWsaMif start starts the process of creating the hardware inventory data for UAM, assuming the UAM agent is installed. The data is stored in MIF format in $INSTALL/UnicenterAssetManagement/Agent/data/transfer, which is the transfer directory for UAM.

The PRIMEPOWER inventory data for UAM can be updated regularly via a crontab entry. A corresponding comment entry (#00 22 * * * /etc/init.d/updateWsaMif start # WebSysAdmin Mif) is already made when the PRIMEPOWER ServerView Suite V2.2 is installed and can be modified using the UNIX crontab(1) command or the Task application. In addition, the hardware inventory data can be updated each time the machine is rebooted by invoking /etc/rc2.d/S99WsaMif.

The hardware inventory data is established from the database of the PRIME-POWER ServerView Suite (the DAPS files). A previous update of the database (especially the hardware configuration of the enterprise machines) can be forced by calling /etc/init.d/updateWsaMif force.

U41581-J-Z775-2-76 31


The UAM agent

establishes standard Solaris data and stores this in an internal format in the transfer directory,

converts all MIF files contained in the transfer directory likewise to an internal format and

transfers this data to the sector server.

The UAM agent establishes and transfers the data once a day by default at 11 p.m. The entry in the crontab file is as follows:00 23 * * * /opt/CA/UnicenterAssetManagement/Agent/amax_do ###created by Unicenter Asset Management Agent.

The UAM engine reads the data from the UAM sector and displays it on the UAM admin console.

2.4.3.3 Work steps

If one were to condense the previous statements into concrete instructions for action, a number of work steps would emerge.

Instructions for the one-time transfer of hardware inventory data to the UAM management station:

Install the UAM sector server on the management server

Install the Solaris agent from UAM, Service Pack 1 on the PRIME-POWER machine

The following work steps must all be executed on the PRIMEPOWER machine.

Call $INSTALL/UnicenterAssetManagement/Agent/amax_do in order to create the transfer directory

Call /etc/init.d/updateWsaMif start in order to store the hardware inventory data of the PRIMEPOWER machine in the transfer directory

Call $INSTALL/UnicenterAssetManagement/Agent/amax_do in order to transfer the hardware inventory data of the PRIMEPOWER machine from the transfer directory to the sector server

Instructions for automatically transferring the hardware inventory data:

32 U41581-J-Z775-2-76


Activate the following comment entry on the PRIMEPOWER machine using the crontab(1) command or the Task application#00 22 * * * /etc/init.d/updateWsaMif start # WebSysAdmin Mif, by deleting the comment character

2.4.3.4 MIF files on PRIMEPOWER systems

The following MIF files are created on the PRIMEPOWER systems:

WsaCabinet.mif:

Group Attributes

Cabinets HwKeyVendorRCIAddressCabinet TypeCabinetIdSystemId

Fans HwKeyRCIAddressFanNumber

Power Supplies HwKey RCIAddressPowerSupplyNumber

U41581-J-Z775-2-76 33


WsaSystemboard.mif:(on enterprise systems: view of a HW partition)

WsaBoard.mif:

Group Attributes

Systemboard HwKeyRCIAddressSysBoardNumberBoardIdPOSTVersionOBPVersion

Processors HwKeyRCIAddressSysBoardNumberCPUIndexModelStepFreq_MHzCacheSize_MB

Memory Modules HwKeyRCIAddressSysBoardNumberMemSlotNumberMemSlotNameMemory Size (MB)

Group Attributes

Boards HwKeyRCIAddressBusNumberSlotIdBoardIdNameHardwareRevisionFirmwareRevision

34 U41581-J-Z775-2-76


WsaController.mif:

WsaMassStorage.mif:

Group Attributes

Controllers HwKeyRCIAddressBus NumberSlotIdChannelIdTypeNameMacAddrHardwareRevisionFirmwareRevision

Group Attributes

MassStorageDevices HwKeyRCIAddressCageScsilineSlotIdDeviceClassDeviceNameDeviceTypeDeviceSerialNumberControllerNameCapacity (MB)FirmwareRevision

U41581-J-Z775-2-76 35


Enterprise server- (EPS-) specific info

The following MIF files are only available on the console (SMC) of enterprise servers.

WsaEpsCabinet.mif:

Group Attributes

EPS Cabinets KeyRCIAddressVendorMachineNameServerIDCabinetIndexCabinetTypeModel

EPS Fans KeyRCIAddressMachineNameFanIndex

EPS Power Supply KeyRCIAddressMachineNamePowerSupplyNumber

SCF KeyRCIAddressMachineNameSCFNumber

36 U41581-J-Z775-2-76


WsaEpsSystemboard.mif:

WsaEpsPartition.mif:

Group Attributes

EPS Processors HwKeyRCIAddressMachineNameSysBoardNumber CPUIndexModelStepFreq_MHzCacheSize_MB

EPS Memory Module HwKeyRCIAddressMachineNameModuleIndexSysBoardNumberSize_MB

PCI boards HwKeyRCIAddressMachineNameSlotNameSysBoardNumberBoardType

Group Attributes

EPS_Partitions VendorMachineNamePartitionNamePartitionIDMAC Address

U41581-J-Z775-2-76 37

3 Integration in Tivoli

3.1 Overview

The Tivoli product is a management system that operates on a cross-system basis, though it does not allow the direct administration of computers with proprietary hardware functions. This gap is filled by integrating a product like the PRIMEPOWER ServerView Suite and means that such proprietary computers can now also be administered directly.

In order to integrate the PRIMEPOWER ServerView Suite in Tivoli, two integration products are made available for the Tivoli Enterprise Console (TEC) and for Tivoli NetView. These two integration products are called "Tivoli TEC Integration" (section 3.2) and "Tivoli Netview Integration" (section 3.3).

Both integration products can be installed and used independently of one another. The integration in Tivoli NetView represents the simpler functionality compared with the integration in Tivoli TEC.

U41581-J-Z775-2-76 39

Overview Integration in Tivoli

3.1.1 Availability of integration products

The two integration products for Tivoli are available on the node on which the PRIMEPOWER ServerView Suite is installed and can be downloaded from there using an Internet browser. The following address must be entered in the URL line for this purpose:

http://hostname:8883

You then access the following download page:

Figure 18: Download page for Tivoli integration products

Click the Tivoli TEC Integration link to load a file called WSA-TEC.tar onto your system.

This .tar file must be unpacked using a suitable program. The integration product is then available as a Tivoli image for installation via the Tivoli desktop.

I Both the file and the execution of the installation are identical on Windows NT and Sun Solaris.

40 U41581-J-Z775-2-76

Integration in Tivoli Overview

Click the Tivoli NetView Integration link to load a file called WsaNetViewInte-gration.exe onto your system.

The installation product is available as a UNIX package with the name SMAWtnvS in the following directory on a system running Sun Solaris with an installed PRIMEPOWER ServerView Suite:

/opt/SMAW/SMAWtivX/data

U41581-J-Z775-2-76 41

Integration product "Tivoli TEC Integration" Integration in Tivoli

3.2 Integration product "Tivoli TEC Integration"

The Tivoli TEC Integration integration product allows SNMP traps to be integrated in the Tivoli Enterprise Console (TEC). WebSysAdmin SNMP agents have to be set up on the nodes as trap senders for this purpose, which are monitored via the TEC. An administration system is entered with the Tivoli Enterprise Console as the recipient of WebSysAdmin SNMP traps for all WebSysAdmin SNMP agents. The traps sent by the nodes are depicted as Tivoli events in the TEC with the aid of the integration product.

The Tivoli TEC Integration integration product includes a procedure for config-uring the TEC server in addition to various procedures for configuring and deconfiguring the TEC SNMP adapter. WebSysAdmin SNMP traps are included in TEC event processing in this way.


The following software packages are required for using the integration product:

Operating system:

Windows NT

Sun Solaris 2.6 or higher

Tivoli software:

Tivoli Framework 3.7

Tivoli Enterprise Console 3.7

Tivoli TEC 3.7

42 U41581-J-Z775-2-76

Integration in Tivoli Integration product "Tivoli TEC Integration"

3.2.2 Installation

3.2.2.1 Dependencies on other Tivoli products

The Tivoli Framework and Tivoli Enterprise Console packages must be installed for the Tivoli TEC Integration product.

Before you install the integration product, you have to first install the Tivoli Plus Module Support (Link binaries) - 3.0.o module.

3.2.2.2 Installation via the Tivoli desktop

Step 1

Start the Tivoli program and log in. You have to enter the following details in a Login window for this purpose:

Host Machine: Log In As: Password:

If these details are accepted, the Tivoli desktop then appears for this Tivoli administrator.

U41581-J-Z775-2-76 43


Figure 19: Tivoli desktop

Choose the Install Install Product ... option under Desktop to the above right in the window in order to open the Install Product window:

44 U41581-J-Z775-2-76


Figure 20: Install Product box

U41581-J-Z775-2-76 45


Step 1a

I The old name of the integration product WebSysAdmin for Tivoli, which was not changed for compatibility reasons, comes up repeatedly below in the installation procedure. However, the product with the current name Tivoli TEC Integration is intended in each case.

If the two products WebSysAdmin for Tivoli and Plus Module Support do not appear in the list of products that can be installed or if a box is displayed with the error message Something is wrong with the current installation media settings, click Select Media... or OK in the error message box. A box is then displayed for selecting the correct path for the Tivoli image:

Figure 21: Select Media box

Enter the directory in the line Path Name where the unpacked Tivoli image can be found, identified by the file CONTENTS.LST. Press the Set Path button. Click the Set Media & Close button to exit this dialog window and you will then be shown the two components for installation.

46 U41581-J-Z775-2-76


Step 2

First choose the Plus Module Support (Link binaries) 3.0.o product as well as the relevant TEC server as the client ("Clients to install On") on which the installation is to be performed:

Figure 22: Install Product box for installing the Plus Module Support product

Click Install and Continue Install in the next box to install Plus Module Support.

U41581-J-Z775-2-76 47


Step 3

Now repeat Step 2 to install the WebSysAdmin for Tivoli product:

Figure 23: Install Product box for installing the WebSysAdmin for Tivoli product

Click Install or Install & Close and Continue Install in the next box to install WebSysAdmin for Tivoli.

This completes installation of WebSysAdmin for Tivoli.

Following the installation, a new icon appears on the Tivoli desktop with the name TivoliPlus (see figure 24 on page 50), which can be used to call the integration module.

48 U41581-J-Z775-2-76


3.2.2.3 Deinstallation

WebSysAdmin for Tivoli is deinstalled (on Solaris under the user root and on Windows NT as an administrator using the Bash Shell) by calling the PLUSunconfig.sh script.

Before the call, the Tivoli environment variables must be defined. Both tasks can be performed using the following script:

# UNIX or Windows?if [ x\"$OS\" = x\"Windows_NT\" ]then

$Windir/system32/drivers/etc/tivoli/setup_env.shelse

. /etc/Tivoli/setup_env.shfi$BINDIR/../generic_unix/TME/PLUS/PRIMEPOWER ServerView Suite/PLUSunconfig.sh

I The product is then deinstalled and all associated configurations unset in Tivoli. The files of the integration package itself are not removed in the process however. The Plus Module Support product is likewise not deinstalled because it may also be used by other Tivoli modules.

U41581-J-Z775-2-76 49


3.2.3 Configuration

3.2.3.1 WebSysAdmin SmartSet for Tivoli

The WebSysAdmin for Tivoli SmartSet contains the jobs required for integrating PRIMEPOWER ServerView Suite in Tivoli. Starting from the Tivoli desktop, you access the SmartSet as follows.

Double-click the TivoliPlus icon to open the TivoliPlus SmartSet:

Figure 24: Tivoli desktop

50 U41581-J-Z775-2-76


The following screen appears:

Figure 25: TivoliPlus SmartSet

Now double-click the WebSysAdmin for Tivoli icon to access the WebSysAdmin for Tivoli SmartSet:

Figure 26: WebSysAdmin for Tivoli SmartSet

The WebSysAdmin for Tivoli SmartSet contains five jobs that support the necessary configurations for integrating WebSysAdmin for Tivoli SNMP traps in the TEC:

Setup_TEC_for_WSADefinition of event classes and rules on the TEC server

U41581-J-Z775-2-76 51


Config_SNMPConfiguration of any desired TEC SNMP adapter

Config_SNMP_localConfiguration of the local TEC SNMP adapter

Unconfig_SNMPResetting of the configuration of any desired TEC SNMP adapter

Unconfig_SNMP_localResetting of the configuration of the local TEC SNMP adapter

A local adapter can also be configured by the two general configuration jobs. However, additional input is not required if the local Config_SNMP_local job is used. If only a local TEC SNMP adapter is used, or if adapters on other systems are used exclusively in place of a local adapter, the jobs that are not required can be removed from the SmartSet.

3.2.3.2 The Setup_TEC_for_WSA job

The Setup_TEC_for_WSA job is used to configure the TEC for displaying the Tivoli events, which are sent by the WebSysAdmin for Tivoli SNMP adapter to this console. The classes required for WebSysAdmin for Tivoli events are defined here, as are TEC rules for the WebSysAdmin for Tivoli events. By double-clicking the icon for the Setup_TEC_for_WSA job, you can start the job and the following dialog box is displayed:

Figure 27: Dialog box for the Setup_TEC_for_WSA job

Meaning of the input fields:

Rule Base Name

The name of an existing or new rule base must be entered here.

52 U41581-J-Z775-2-76


Rule Base to clone

Rule base to be copied if a new one is to be created.

Path for Rule Base

Path for the new rule base being created.

Name of Event Console to configure

Name of the event console for which these rules are to be applied.

Two cases can be distinguished:

1. Creation of a new rule base

2. Addition of new rules to an existing rule base

Creating a new rule base

Work through the following steps:

1. Enter the name of a new rule base that is to be created in the Rule Base Name field.

2. Enter the name of a rule base to be copied in the Rule Base to clone field. (A new rule base is always created by copying and changing an existing rule base. The rule base Default always exists).

3. Enter the path name of the directory on the Tivoli Enterprise Console Server in which the new rule base is to be created in the Path for Rule Base field.

I The current user, who is logged in as a TME administrator, must have write rights for the directory you specify in this field.

4. If you want WebSysAdmin for Tivoli events to appear on the event console of a specific Tivoli administrator, enter the name of the event console in the Name of Event Console to configure field. The event group WebSysAdmin is then assigned to this event console.

5. Conclude the action by pressing the Set and Close button.

Adding new rules to an existing rule base

Work through the following steps:

1. Enter the name of an existing rule base, to which the WebSysAdmin rules are to be added, in the Rule Base Name field.

U41581-J-Z775-2-76 53


2. If you want WebSysAdmin for Tivoli events to appear on the event console of a specific Tivoli administrator, enter the name of the event console in the Name of Event Console to configure field. The event group WebSysAdmin is then assigned to this event console.

3. Conclude the action by pressing the Set and Close button.

You are then shown an output box containing either error messages indicating incomplete or invalid details or other errors or documenting the successful configuration of the TEC:

Figure 28: Output box of the Setup_TEC_for_WSA job

54 U41581-J-Z775-2-76


I Please make sure that a /tmp directory is available on the drive or the file system on which the Tivoli framework is installed.

3.2.3.3 The Config_SNMP job

By double-clicking the icon for the Config_SNMP job, you can configure any desired TEC SNMP adapters that exist in the Tivoli environment. The adapter configuration is then extended by the entries required for integrating WebSysAdmin SNMP traps. When the job is started, you are shown the following dialog box:

Figure 29: Dialog box for the Config_SNMP job

In the dialog box for the Config_SNMP job, you must specify where the SNMP adapter to be configured is located. You can define different Tivoli resources for this. To do this you have to:

1. Enter the host in the Endpoint or Profile Manager field on which the adapter is installed. If a Profile Manager is specified, all dependent nodes (subscribers) are affected by this.

2. Enter the complete directory name in which the SNMP adapter is installed in the SNMP adapter directory field.

If you have not specified any particular directory when installing the adapter, it is not necessary to specify the directory.

If you have installed the adapter in a special directory, you have to specify this directory here.

If you have given invalid details, for example an endpoint that does not exist or incorrect details of the directory for the adapter, then messages to this effect are issued in the outbox box.

U41581-J-Z775-2-76 55


The figure below shows the output box for the SNMP_Config job for the Profile Manager PM_SNMP_Adapters, to which the three subscribers pce304, ws6520 and atpcq79c are assigned:

Figure 30: Output box of the Config_SNMP job

The first of these subscribers, a Tivoli endpoint, could not be reached, since the Tivoli endpoint service has not been started. The TEC SNMP adapter was successfully configured and restarted for the two other subscribers.

56 U41581-J-Z775-2-76


3.2.3.4 The Unconfig_SNMP job

By double-clicking the icon for the Unconfig_SNMP job, you can remove any existing configurations for WebSysAdmin SNMP traps for any desired TEC SNMP adapters in the Tivoli environment. The entries for WebSysAdmin traps in the adapter configuration files .cds and .oid are removed. When the job is started, you are shown the following dialog box:

Figure 31: Dialog box for the Unconfig_SNMP job

The input fields are the same as for the Config_SNMP job, i.e. you can again specify either a Tivoli endpoint, a managed node or a profile manager. If you specify a profile manager, the job is executed for all the assigned subscribers.

Once again, the directory of the SNMP adapter can be optionally specified; however, this is also required above all for most Windows NT endpoints.

The figure below shows the output box for the SNMP_Unconfig job for the ws6520 endpoint:

U41581-J-Z775-2-76 57


Figure 32: Output box of the Unconfig_SNMP job

58 U41581-J-Z775-2-76


3.2.3.5 The Config_SNMP_local job

By double-clicking the icon for the Config_SNMP_local job, you can configure the local TEC SNMP adapter. You do not need to make any further input. The result of the job is shown in a separate box:

Figure 33: Output box of the Config_SNMP_local job

U41581-J-Z775-2-76 59


3.2.3.6 The Unconfig_SNMP_local job

By double-clicking the icon for the Unconfig_SNMP_local job, any configurations of the local TEC SNMP adapter that exist for WebSysAdmin SNMP traps are undone. The result of the job is likewise shown in a separate box:

Figure 34: Output box of the Unconfig_SNMP_local job

60 U41581-J-Z775-2-76


3.2.3.7 TEC classes

The following TEC classes are configured by the WebSysAdmin for Tivoli product:

Class Subclass from Parameters

WSA_Trap Specific_SNMP_Trap

WsaLarHardwareDefectSet WSA_Trap wsaServerNamewsaLarCommentwsaTrapTimewsaHWConfAddr

WsaLarHardwareDefec-tUnset

WSA_Trap wsaServerNamewsaLarCommentwsaTrapTimewsaHWConfAddr

WsaLarHardwareErrorSet WSA_Trap wsaServerNamewsaLarCommentwsaTrapTimewsaHW-ConfAddr

WsaLarHardwareErrorUnset WSA_Trap wsaServerNamewsaLarCommentwsaTrapTimewsaHWConfAddr

WsaAgentStart WSA_Trap wsaServerName

WsaErrorRepair WSA_Trap wsaServerNamewsaLarCommentwsaTrapTimewsaHWConfAddr

WsaDefectRepair WSA_Trap wsaServerNamewsaLarCommentwsaTrapTimewsaHWConfAddr

U41581-J-Z775-2-76 61


3.2.3.8 TEC rules

The following TEC rules are configured by the WebSysAdmin for Tivoli product:

Affected TEC class Action

WsaErrorRepair Closes the incoming "all-clear" event and the associated WsaLarHardwa-reErrorSet event.

WsaLarHardwareErrorUnset Closes the incoming "all-clear" event and the associated WsaLarHardwa-reErrorSet event.

WsaDefectRepair Closes the incoming "all-clear" event and the associated WsaLarHardware-DefectSet event.

WsaLarHardwareDefectUnset Closes the incoming "all-clear" event and the associated WsaLarHardware-DefectSet event.

WsaLarHardwareErrorUnset Closes the incoming "all-clear" event and the associated WsaLarHardware-DefectSet event.

62 U41581-J-Z775-2-76


3.2.3.9 Testing aids

In order to test the operability of the Tivoli TEC Integration product, WebSysAdmin SNMP traps must be sent to the TEC SNMP adapter. These traps may also be generated with available test tools from the PRIMEPOWER ServerView Suite or a generic SNMP trap sender program.

For example, the NetView snmptrap command can be used to simulate a hardware defect trap:

TrapTime=`date +%R`snmptrap -p 1162 pc7398 .1.3.6.1.4.1.231.2.41 ws4711 6 1 0 \

.1.3.6.1.4.1.231.2.41.3.1.0 OctetString ws4711 \

.1.3.6.1.4.1.231.2.41.3.3.0 OctetString "2nd CPU down" \

.1.3.6.1.4.1.231.2.41.3.2.0 OctetString "$TrapTime" \

.1.3.6.1.4.1.231.2.41.3.4.0 OctetString "x5:4:just a test"

The following parameters are used here:

-p 1162Sends the trap to port 1162

pc7398Name of trap recipient (= system with active TEC SNMP adapter)

.1.3.6 Enterprise ID under which the WebSysAdmin SNMP traps are sent

ws4711Name of trap sender (= WebSysAdmin server)

6 Generic trap number

1 Specific trap number (1 = "HardwareDefect" trap)

0 Time stamp (not relevant for the test, hence "0")

These are followed by the four trap parameters for WebSysAdmin server, error message, trap time and internal error detection.

U41581-J-Z775-2-76 63


3.2.3.10 if ...?

This section deals with possible application or operation errors and describes their causes and means of resolution.

WebSysAdmin events are not shown in the TEC

Situation:The TEC shows no WebSysAdmin SNMP traps sent.

Cause:Check the following points:

1. The server with the TEC SNMP adapter must be configured as a trap recipient of the WebSysAdmin agent. By default, the TEC SNMP adapter expects incoming traps on port 162. While this value can be changed, the WebSysAdmin agent must then also send to the modified port.

Start the SNMP adapter in debug mode to see whether the WebSysAdmin SNMP traps are received by the adapter.

2. Check the communication between the adapter and TEC server.

Execute the Tivoli wtdumprl command on the TEC server to see whether events are received on the TEC server from the adapter.

3. Check the TEC configuration: In order to ensure that incoming WebSysAdmin events are also displayed, the relevant TEC classes must be known on the TEC server.

Check whether the wsa_traps.baroc class file for WebSysAdmin SNMP traps is loaded in the current rule base of the TEC server. You can load the configuration using the Setup_TEC_for_WSA procedure.

64 U41581-J-Z775-2-76


Endpoint: not running at the moment!

Situation:The above error message appears when one of the jobs for configuring the SNMP adapter is executed.

Cause:The Tivoli endpoint cannot be reached, i.e. the system cannot be reached in general or the endpoint client has not been started or is faulty.

"Failed to import d:/Tivoli/bin/generic_unix/TME/PLUS/PRIMEPOWER ServerView Suite /wsa_traps.baroc to rulebase!"

Situation:The error message appears in connection with the job Setup_TEC_for_WSA.

Cause:wsa_traps.baroc could not be imported into the rule base since it already exists in the rule base. The error message therefore has a purely informal character.

"mv: cannot move `i/bin/w32-ix86/TME/TEC/adapters/etc/snmp.tmp' to `/w32-ix86/TME/TEC/adapters/etc/tecad_snmp.cds': File exists"

Situation:Following execution of one of the jobs to undo the configuration of the SNMP adapter on a Windows NT system, there are still no WebSysAdmin entries in the .cds adapter file.

Cause:It may take longer on Windows NT systems for the associated process to be terminated after the adapter has been stopped. If this is still not the case 30 seconds after the adapter has been stopped, the .cds file opened by the adapter cannot be accessed. It may help in this situation to repeat execution of the job. Alternatively, the adapter can also be manually terminated before the job is executed.

(Even if the WebSysAdmin entries still remain in the .cds file, this does not impact other traps that are passed by the adapter to the TEC.)

U41581-J-Z775-2-76 65


"Problems while stopping TEC SNMP Adapter!"

Situation:The above message is displayed during execution of a job for configuring an SNMP adapter on Sun Solaris.

Cause:The start/stop script init.tecad_snmp for Sun Solaris contains a bug. Replace in the script the line:

# pid=`ps -ef | grep $1 | grep -v grep | grep -v $1.cfg |\ awk {print $2;}`

by the following line:

pid=`ps -ef | grep $1 | grep -v grep | grep -v $1.cfg |\ grep -v $0 | awk {print $2;}`

66 U41581-J-Z775-2-76

Integration in Tivoli Integration product "Tivoli NetView Integration"

3.3 Integration product "Tivoli NetView Integration"

The Tivoli NetView Integration integration product allows the PRIMEPOWER ServerView Suite to be integrated in Tivoli NetView with the following properties:

Unambiguous representation of PRIMEPOWER systems in the NetView map by means of a separate icon.

Representation of the PRIMEPOWER ServerView Suite application in the submap of PRIMEPOWER systems by means of a separate icon.

Simple configuration of NetView attributes for PRIMEPOWER systems in Tivoli NetView with the aid of a NetView map application for the PRIME-POWER ServerView Suite.

Automatic event integration: support of the PRIMEPOWER ServerView Suite MIB and display of the traps defined in it as Tivoli NetView events.

Optional forwarding of these events to a Tivoli Enterprise Console (TEC).

Mapping of the status of the PRIMEPOWER ServerView Suite to the WebSysAdmin icons in the NetView map.

Simple display of status information on the PRIMEPOWER ServerView Suite by means of a MIB application.

Calling of the PRIMEPOWER ServerView Suite directly from Tivoli NetView (if the PRIMEPOWER ServerView Suite application has been installed on the NetView server).

A subagent for the HW diagnosis system (wsaagt of EMANATE Master Agent, cf. section Configuring the SNMP EMANATE master agent on page 115) is required for integrating PRIMEPOWER ServerView Suite in Tivoli NetView. This subagent agent must be installed on every node that is to be monitored by this management tool.

U41581-J-Z775-2-76 67

Integration product "Tivoli NetView Integration" Integration in Tivoli


The following software packages are required for using the Tivoli NetView Integration product:

Operating system:

Windows NT

Sun Solaris 2.6 or above

Tivoli software:

Tivoli NetView 5.1 or 6.0 for Windows NT

Tivoli NetView 5.1 for Sun Solaris

3.3.2 Installation

3.3.2.1 Dependencies on other Tivoli products

The Tivoli NetView Integration integration product is installed on the NetView server and requires Tivoli NetView when it is installed.

If Tivoli NetView is deinstalled, the integration package remains on the system. Please note the following in order to ensure that the PRIMEPOWER ServerView Suite integration still works when Tivoli NetView is reinstalled without the integration package having to be removed first and then reinstalled:

Sun Solaris:Following installation of Tivoli NetView, the configuration of Tivoli NetView Integration must be loaded again using the following call: /opt/SMAW/SMAWtnvS/bin/wsa_load_config.sh.

Windows NT:An "Upgrade" installation must be selected in the Tivoli NetView instal-lation, otherwise the integration package must also be installed again. Event integration for WebSysAdmin SNMP traps must then be configured again by one of the two calls Configure TECConfigure WSA-Events Forward to TEC or Do not forward to TEC.

68 U41581-J-Z775-2-76


3.3.2.2 Installation on Windows NT

Step 1

On the Windows PC, go to the directory where you saved the WsaNetViewInte-gration.exe file after downloading it. Start installation of the Tivoli NetView Integration integration product by double-clicking WsaNetViewIntegration.exe.

If the PRIMEPOWER ServerView Suite has not been installed on the system, you receive the following message:

Figure 35: Warning: WSA client software missing

This means that you cannot start the PRIMEPOWER ServerView Suite from Tivoli NetView. Either click Cancel and abort the installation so that you can install the PRIMEPOWER ServerView Suite and then the integration product, or select OK to continue installation.

I You can subsequently install the PRIMEPOWER ServerView Suite at any time. In this case, start the WSACheck.exe program in the :\usr\ov\wsa\bin directory after installing the PRIMEPOWER ServerView Suite.

U41581-J-Z775-2-76 69


When WsaNetViewIntegration.exe has been executed, the following welcome mask appears. Click Next to continue the installation or Cancel to abort the instal-lation.

Figure 36: Installation on Windows NT Welcome

I The old PRIMEPOWER ServerView Suite logo still appears in this and the next dialog boxes instead of the new PRIMEPOWER ServerView Suite logo; cf. the note in Step 1a on page 46.

When you click Next, the Ready to Install window opens. This is the last window where you can abort the installation.

70 U41581-J-Z775-2-76


Figure 37: Installation on Windows NT Ready to Install

The following dialog boxes mark the start and end of event configuration. Click OK in both cases to continue.

Figure 38: Start of event configuration

Figure 39: End of event configuration

Installation is completed when you click Finish in the following dialog box:

U41581-J-Z775-2-76 71


Figure 40: Installation on Windows NT Completion

Step 2

Start Tivoli NetView and select Edit Properties.... In the Properties box, select the IP Map entry in the Map Application selection field and click Properties. Now disable the Exclusively Set the Status for Nodes property, select Verify and press OK. Close the Properties box with OK.

I If you configure a system as a PRIMEPOWER ServerView Suite node, Tivoli NetView shows this with the icon for PRIMEPOWER. However, the IP Map application regularly polls all the systems and defines the icon type on the basis of the received system object identifier.

This action is used to prevent the assigned PRIMEPOWER icon for an object being replaced again by the original default icon.

3.3.2.3 Installation on Sun Solaris

In order to ensure correct functioning of the installation routine for the SMAWtnvS package, the error in the /usr/OV/bin/nvaddtrapdconf script used for installing SMAWtnvS must be corrected if NetView 5.1 is used. This error has already been corrected in NetView 5.1.3 and higher.

72 U41581-J-Z775-2-76


The integration package SMAWtnvS is installed on Sun Solaris with the pkgadd command. The Tivoli NetView application must be terminated beforehand.

The package installs all the necessary files under /opt/wsaopt/SMAW/SMAWtnvS and then calls the /opt/wsaopt/SMAW/SMAWtnvS/bin/wsa_load_config.sh script. This script copies files to the Tivoli NetView directory structure and enables the installed extensions.

This script can also be called on its own after installation.

Step 1

Exit all the Tivoli NetView applications.

Step 2

This step must only be performed if you are using NetView 5.1. This error has been rectified in NetView 5.1.3 and higher.

Rectification of an error in the Tivoli NetView script //usr/OV/bin/nvaddtrapdconf. Execute the following commands as root user:

cd /usr/OV/bincp nvaddtrapdconf nvaddtrapdconf.original

Comment out line 290

#HIT = match( $0, /["][^\n]+["]/ ) # set RSTART and RLENGTH

and replace it with the following:

HIT = match( CAT[i], /["][^\n]+["]/ ) # set RSTART and RLENGTH

Step 3

Start installation with the following command:

pkgadd -d /opt/SMAW/SMAWtivX/data/SMAWtnvS

The following dialog box is shown:

U41581-J-Z775-2-76 73


Figure 41: Installation on Solaris Start

Enter 1 and press the Return key or simply press the Return key to start the installation.

Figure 42: Installation on Solaris Checking for Tivoli NetView

The installation routine checks that Tivoli NetView exists and specifies the NetView directory found. If Tivoli NetView is not found or if you specify n and thus do not confirm the directory found, the installation is aborted. If you enter y or simply press the Return key (y is the default value), you receive the following query:

74 U41581-J-Z775-2-76


Figure 43: Installation on Solaris Last chance to abort

Commands are executed under the root ID for configuring the integration package. Select y to continue or n to abort installation. This is your last oppor-tunity not to perform the installation.

Figure 44: Installation on Solaris Completion

Installation of the package is completed with configuration for the PRIMEPOWER ServerView Suite integration.

U41581-J-Z775-2-76 75


Step 4

Start Tivoli NetView and select File Describe Map.... In the Map Description box, select the IP Map application and click Configure for this map. Now set Should IP Map override user symbol customization? to False, select Verify and press OK. Close the Map Description box with OK.

I If you configure a system as a PRIMEPOWER ServerView Suite node, Tivoli NetView represents this with the icon for PRIMEPOWER. However, the IP Map application regularly polls all the systems and defines the icon type on the basis of the received system object identifier. If Should IP Map override user symbol customization? is set to True, the icon for PRIME-POWER is also replaced by the previous icon. However, this does not impact the further functionality of the integration package.

3.3.2.4 Deinstallation on Windows NT

Step 1

Undo configuration as a PRIMEPOWER ServerView Suite node for all PRIME-POWER systems. To do this, select the PRIMEPOWER systems and then select WebSysAdmin Configure WSA-Node Unconfigure WSA-Node. (You can select several PRIMEPOWER systems simultaneously. The best way to do this is to use a separate PRIMEPOWER ServerView Suite SmartSet. See section Definition of a PRIMEPOWER ServerView Suite SmartSet on page 97). The integration package can only be deinstalled in full once the configuration of all PRIMEPOWER systems has been undone in this way.

Step 2

Exit all Tivoli NetView GUIs.

Step 3

Open the Control Panel by choosing Start Settings Control Panel and then click the Software icon. Now select the WebSysAdmin Integration in Tivoli/NetView for WIN-NT entry and press the Add/Remove button. The following Welcome window then appears:

76 U41581-J-Z775-2-76


Figure 45: Deinstallation of the integration package on Windows NT

Click the Next button to complete the deinstallation of the integration package in Tivoli NetView:

U41581-J-Z775-2-76 77


Figure 46: Deinstallation on Windows NT Completion

3.3.2.5 Deinstallation on Sun Solaris

Before deinstallation, the configuration of all PRIMEPOWER systems must be undone since the deinstallation routine also deinstalls the corresponding icons. If a system with the PRIMEPOWER icon is still in the map after deinstallation, a default icon that can no longer be changed is used to represent the system.

Following deinstallation with pkgrm or execution of the /opt/wsaopt/SMAW/SMAWtnvS/bin/wsa_unload_config.sh script, the event category PRIMEPOWER ServerView Suite Events must be deleted manually using the Tivoli NetView application.

Step 1

Undo the configuration as a PRIMEPOWER ServerView Suite node for all PRIME-POWER systems. To do this, select the PRIMEPOWER systems and then select WebSysAdmin Configure WSA-Node Unconfigure WSA-Node. (You can select several PRIMEPOWER systems simultaneously. The best way to do this is to use a separate WSA SmartSet. See section Definition of a PRIMEPOWER

78 U41581-J-Z775-2-76


ServerView Suite SmartSet on page 97). The integration package can only be deinstalled in full with the pkgrm SMAWtnvS command once the configuration of all PRIMEPOWER systems has been undone in this way.

Step 2

Exit all Tivoli NetView applications.

Step 3

Start deinstallation with the following command:

pkgrm SMAWtnvS

You are shown the following dialog box:

Figure 47: Deinstallation of the Solaris package SMAWtnvS

Select y to remove the package or n to abort deinstallation.

U41581-J-Z775-2-76 79


Figure 48: Deinstallation on Solaris Last chance to abort

As during installation, note that commands must be executed under the root user ID in order to undo the configuration of the integration package. Select y to continue or n to abort deinstallation. This is your last opportunity to abort deinstallation.

Figure 49: Deinstallation on Solaris Undoing the WSA configuration

80 U41581-J-Z775-2-76


All the files installed by the package are removed. However, files newly copied into the WebSysAdmin directory, such as the postemsg command required for forwarding, remain. This completes deinstallation of the integration package.

Figure 50: Deinstallation on Solaris Completion

Step 4

Start Tivoli NetView and delete the event category WebSysAdmin Events, which can only be reset via the Tivoli NetView user interface: select Options Event Configuration: Trap Customization: SNMP . Click Configure Categories, then select WebSysAdmin Events and click Delete. Now close the Configure Event Categories box with Close and the Event Categories box with OK.

If the WebSysAdmin Events event category still remains, however, this will not have any further effects on Tivoli NetView or the renewed installation of the integration package.

U41581-J-Z775-2-76 81


3.3.3 Configuration

The description of PRIMEPOWER ServerView Suite integration in Tivoli NetView is basically the same regardless of whether Tivoli NetView is used on Windows NT or Solaris. Where there are differences in individual cases, for example in paths or Tivoli NetView menu paths, these are indicated separately.

3.3.3.1 Integration in the NetView IP map

PRIMEPOWER systems are represented in the IP map by their own icon. In addition, the PRIMEPOWER ServerView Suite agent is also represented by its own icon, which symbolizes the states of the agent that are reported by traps. The status of the icon for the PRIMEPOWER ServerView Suite agent is propagated to the PRIMEPOWER icon.

If a system is configured as a WebSysAdmin server by means of a menu call, this is recognized by the WebSysAdmin Map application that runs as a Tivoli NetView process. As a result, the system icon is changed to PRIMEPOWER and the associated Tivoli NetView attributes. As a consequence, the icon for the WSA agent is also configured and the above-mentioned status propagation is enabled.

Configuration of a system as a WebSysAdmin node

Systems with the "node" capability can be configured as WebSysAdmin nodes. For this purpose, the relevant systems must be selected in the map. The following menu item then selected.

WebSysAdmin Configure WSA-Node Configure as WSA-Node

As a result, the selected systems are given the icon Computer:PRIMEPOWER and the WebSysAdmin capability. A new icon of the type Software:WebSysAdmin is generated in the submap of these systems.

The items from the WebSysAdmin menu are then available for these systems.

If this configuration is to be undone, the relevant system is selected in the map and the menu item WebSysAdmin Configure WSA-Node Unconfigure as WSA-Node is selected.

If a new system of the type PRIMEPOWER is created manually, it is also configured automatically.

82 U41581-J-Z775-2-76


Description of the WebSysAdmin Map application

Automatic configuration of WebSysAdmin systems is carried out by the map appli-cation:

Solaris/opt/wsaopt/SMAW/SMAWtnvS/bin/WebSysAdminMapApp

Windows NT\usr\ov\wsa\bin\WebSysAdminMapApp.exe

This map application is enabled by default. However, it can also be disabled.

Solaris:

By calling File Describe Map..., a box opens that, among other things, displays the configurable applications. Select the WebSysAdmin application from the relevant list and press the Configure for this Map...button. This opens a box in which the map application can be enabled or disabled. Under the heading Enable WebSysAdmin for this map, you can select either True or False. You can then accept the selected configuration by pressing Verify and then OK.

U41581-J-Z775-2-76 83


WindowsNT:

A dialog box opens when you select the Edit Properties menu option showing the configurable applications as well as other information:

Figure 51: Dialog box for configuration with map application

Choose the WebSysAdmin entry in the Map Application and press the Properties... button. The map application can then be activated or deactivated in the We

Documents

PRIMEPOWER ServerView Suite PRIMEPOWER …manuals.ts.fujitsu.com/file/8838/o41581e3.pdf · 3 Integration in Tivoli ... 6.3.2 File contents ... for controlling and monitoring