Mid-Level Manager User s Guide

Transcription

1 NetView for UNIX Mid-Level Manager User s Guide Version 7 SC

2 Tivoli NetView Mid-Level Manager User s Guide Copyright Notice Copyright IBM Corporation All rights reserved. May only be used pursuant to a Tivoli Systems Software License Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grants you limited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights under copyright are granted without prior written permission of IBM Corporation. The document is not intended for production and is furnished as is without warranty of any kind. All warranties on this document are hereby disclaimed, including the warranties of merchantability and fitness for a particular purpose. U.S. Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation. Trademarks IBM, the IBM logo, Tivoli, the Tivoli logo, are trademarks or registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Notices References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will be available in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, or services is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalent product, program, or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation in conjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York , U.S.A.

3 Contents Preface vii Who Should Read This Document vii Prerequisite and Related Documents vii What This Document Contains vii Typeface Conventions ix Platform-Specific Information ix Online Information ix Accessability Information x Keyboard Access x Contacting Tivoli Support x Chapter 1. Quick Start for AIX Startup Tasks Task 1: Defining a Community Name on the Remote SIA Node Task 2: Defining Community Names on the Distributed MLM Node Task 3: Defining a Community Name on the Tivoli NetView Manager Task 4: Setting a Trap Destination to Forward MLM Traps to Tivoli NetView 4 Task 5: Set an MLM Threshold for a Variable on the SIA Node Startup Troubleshooting Tips Chapter 2. What Is MLM? What Are the MLM Components? MLM Configuration Application MLM What Are the Benefits of MLM? Distributing MLM Software Scenario 1: Systems Management Scenario 2: Distributed SNMP Management Scenario 3: Monitoring in a Wide Geographic Area (Branch Management) 19 Chapter 3. Installing MLM Planning for Your Installation AIX Installation Required Hardware Required Software Setting the LANG Variable What the Installation Process Does What the MLM Configuration Application Installation Process Does What the MLM Installation Process Does Installing from a Local Device (CD-ROM Drive) to a Local Node Removing Local-Node Tivoli NetView MLM Software Solaris and HP-UX Installation Installation Requirements Installing Sun Solstice Enterprise Agents (Solaris Only) Installing Tivoli NetView MLM Software Installing smconfig Removing the MLM or smconfig Windows NT Installation Installation Requirements Installing the Tivoli NetView MLM for NT Chapter 4. Installing MLM on Remote Nodes What the Remote Installation Process Does iii

4 Single Remote-Node Installation Installation Verification Removing Remote-Node Tivoli NetView MLM Software Chapter 5. Configuring MLM Configuring MLM for Your Operational Environment Role of the bsnmpd Daemon (HP-UX Only) Role of the SEAs (Solaris Only) Assigning Ports for SNMP Daemons For HP-UX 9.x and 10.x Only Configuring MLM on Solaris Defining Community Names Used for SNMP Requests Sent by MLM Defining Community Names (HP-UX Only) Defining Community Names (Solaris Only) Configuring Daemons to Work with bsnmpd (HP-UX Only) Community Names and the MLM Configuration Application Examples (AIX only) Chapter 6. Starting, Stopping, and Maintaining MLM MLM Options Using Shell Scripts to Control the Mid-Level Manager Daemons Specifying smmlm Shell Script Parameters Using the Tivoli Desktop to Control the midmand Daemon Specifying Tivoli Desktop Options to Start and Stop Daemons Maintaining MLM Saving MIB Table Configuration Changes in a File Using the MLM Configuration Application Reinitializing the Mid-Level Manager Daemon Distributing MIB Table Configurations to Other Nodes Refreshing the snmpd Daemon on a Remote Node Modifying Log and Collection File Characteristics Accessing Online Information (AIX Only) Accessing Online Help Accessing Online MLM Books Chapter 7. Using smconfig Starting smconfig Using the Tivoli NetView Graphical Interface Using the AIX Command Line Configuring MLM MIB Tables MLM MIB Table Descriptions Selecting a Different Node or Community Name Querying MIB Table Entries Creating New MIB Table Entries Saving MIB Table Configurations Chapter 8. Using MLM with Tivoli NetView Distributing Status Monitoring and Node Discovery to the MLM Setting Up Distributed Discovery and Status Monitoring Using smconfig with Tivoli NetView Using MLM MIB Applications from Tivoli NetView Creating MLM MIB Applications Using the Tivoli NetView Application Builder 66 Cutting and Pasting Information from Tivoli NetView to smconfig Chapter 9. MLM Tables MLM Configurable MIB Tables iv Mid-Level Manager User s Guide

5 Administration Table Administration Table Fields Alias Table Alias Table Fields Community Names and Aliases Data Collection Settings Data Collection Log Filter Table Filter Rule Filter Table Fields General Information Fields Filter Action Fields General Information Criteria Fields Activation and Deactivation Fields Throttle Fields Matched, Armed, and Disarmed Command Environment Variables Node Discovery Settings Fine Tuning Network Sensing (AIX Only) Node Discovery Fields Program Description Status Monitor Table Changing Statuses of Nodes Status Monitoring Entries Tailoring Polling Intervals Status Monitor Fields Network Interface Status Fields Threshold and Collection Table Polling Local and Remote Nodes Generating Traps Expressions Expression Evaluations Threshold and Collection Table Fields Actions Fields Threshold and Rearm Command Environment Variables Threshold Arm Information Table Updates Example Wildcards Threshold Results Table Trap Destination Table TCP and UDP Protocols General Fields Activation and Deactivation Fields Trap Logging Settings Trap Log Table Trap Reception Settings Chapter 10. MLM Traps MLM Trap Delivery Trap Types MLM Trap Format Threshold Traps Threshold Trap Default Messages for Tivoli NetView: Session Traps Session Trap Default Messages for Tivoli NetView: Status Monitoring Traps Contents v

6 Status Monitor Trap Default Message for Tivoli NetView: Node Discovery Traps New Nodes Trap (Specific Trap 31) Default Message for Tivoli NetView: 134 Old Nodes Trap (Specific Trap 32) Default Message for Tivoli NetView: 135 Specific Trap 33 (Duplicated Addresses) Default Message for Tivoli NetView: 135 Table State Change Traps Table State Change Trap (Specific Trap 41) Default Message for Tivoli NetView: Appendix. Reference Pages Tivoli NetView MLM Utilities, Commands, and Shell Scripts midmand(8) smconfig(1) smmlm(1) snmpget(1) snmpnext(1) snmpset(1) snmptrap(1) snmpwalk(1) Tivoli NetView MLM Files Glossary Index vi Mid-Level Manager User s Guide

7 Preface Tivoli NetView for UNIX Mid-Level Manager (MLM) enables you to distribute network monitoring and management from the central network management platform, Tivoli NetView for UNIX. Acting as an intermediate Simple Network Management Protocol (SNMP) manager, MLM reduces the amount of network traffic and the amount of processing that must be done by the central network manager. This document presents information about installing, configuring, and using the following features of MLM: v The MLM Configuration Application (smconfig) v The Mid-Level Manager (MLM) All features are available on HP, Solaris, and AIX. This book provides a general program description, operating behavior details, procedures for installing, configuring and using MLM, and reference information. Who Should Read This Document This book is intended for system administrators who install, configure, maintain, and use the MLM program. It is presumed that the reader has a general understanding of agents and of SNMP network management and how the Tivoli NetView and MLM programs fit into that environment. Also required is an understanding of one of the following relevant operating systems: v AIX Operating Systems Version v HP-UX Version A9.07, Version B10.01and higher v Solaris Version 2.5.1, 2.6, or 2.7 Prerequisite and Related Documents The following is a list of Tivoli NetView related publications: Tivoli NetView for UNIX Administrator s Guide Tivoli NetView for UNIX Administrator s Reference Tivoli NetView for UNIX Database Guide Tivoli NetView for UNIX Diagnosis Guide Tivoli NetView for UNIX Host Connection Tivoli NetView for UNIX Configuration Tivoli NetView for UNIX Programmer s Guide Tivoli NetView for UNIX Programmer s Reference Tivoli NetView for UNIX User s Guide for Beginners TME 10 Framework Reference Manual What This Document Contains v Chapter 1. Quick Start for AIX on page 1 vii

8 This chapter provides a scenario to help you learn the basic concepts for configuring MLM. After performing the steps in this chapter, you will have a basic distributed manager and a managed SNMP node set up. v Chapter 2. What Is MLM? on page 15 This chapter provides an overview of each feature and describes how the features interact to provide distributed network management. v Chapter 3. Installing MLM on page 21 This chapter contains information about installing, verifying, starting, and removing the MLM program features for the UNIX platforms. v Chapter 4. Installing MLM on Remote Nodes on page 31 Installing the MLM features on a remote node provides additional management capabilities. The features can be installed in the following ways: On a single remote node, from image, by using the Tivoli desktop On multiple remote nodes, from image, by using the Tivoli NetView graphical interface v Chapter 5. Configuring MLM on page 33 This chapter contains information about setting the options that are used when the MLM midmand daemon is started. This chapter also explains how to define community names for nodes sending SNMP requests and for nodes receiving SNMP requests. v Chapter 6. Starting, Stopping, and Maintaining MLM on page 45 This chapter describes how you can use the Tivoli desktop (for the AIX platform) or the shell scripts to start, stop, and control the MLM midmand daemon and the snmpd daemon. This chapter also includes information on accessing online MLM information. v Chapter 7. Using smconfig on page 55 Using smconfig, you can quickly define how MLM will operate. Use smconfig to define entries in the MLM Management Information Base (MIB) tables. The table entries enable you to control system management, collect and examine important data, and view MLM operational status and function. While smconfig works against a single MLM at a time, the Agent Policy Manager (APM) can be used to consistently configure a collection of MLMs. For more information on using APM, refer to the Tivoli NetView for UNIX Administrator s Guide. v Chapter 8. Using MLM with Tivoli NetView on page 61 Read this chapter if you have Tivoli NetView installed in your network. The MLM can work with Tivoli NetView to distribute status monitoring and node discovery tasks throughout the network to reduce wide area network (WAN) traffic, and to quickly find changes in the network. This chapter contains the following sections: Distributing Status Monitoring and Node Discovery to the MLM on page 61 describes how to configure Tivoli NetView and MLM to hand off discovery and status monitoring tasks to local MLMs in the network. Using smconfig with Tivoli NetView on page 64 describes some of the features you can access when smconfig and Tivoli NetView are on the same node. v Chapter 9. MLM Tables on page 69 The MLM provides complete distributed management of local and remote nodes, including polling, thresholding, data collection, trap filtering, node discovery, and status monitoring. The MLM offloads these functions from the top-level manager viii Mid-Level Manager User s Guide

9 Typeface Conventions by performing them at the level of the branch office, local area network (LAN), or LAN segment, depending on how you install and configure the MLM program. Read this chapter to learn about the MLM MIB tables. It explains how to configure these tables, describes how they interact, and defines the fields in each table. v Chapter 10. MLM Traps on page 127 In the MLM program, traps are messages sent by an agent to the top-level manager to provide notification of a network event affecting an agent system or node managed by the system. There are six generic types of SNMP traps in addition to enterprise-specific traps. This chapter explains the flow of traps in the MLM program, how MLM traps are formatted, and describes threshold, session, status monitor, and node discovery traps. The glossary at the end of this document can assist you with terminology. To view additional terminology lists, refer to: This guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Platform-Specific Information Online Information Commands keywords, file names, authorization roles, URLs, or other information that you must use literally appear in bold. The names or titles of screen objects also appear in bold. Italics Variables and values that you must provide appear in italics. Words and phrases that are emphasized also appear in italics. Bold Italics New terms appear in bold italics when they are defined in the text. Monospace Code examples, output and system messages appear in a monospace font. ALL CAPS NetView for OS/390 commands appear in ALL CAPS. Refer to the release notes for platform-specific information. The Tivoli NetView release notes provide the latest information on the Tivoli NetView program. They are available in HTML and PDF versions. The HTML version is accessible from the NetView Console using the Help..Books Online menu item. The PDF version is in /usr/ov/books/$lang/pdf/readme.pdf. The online help facility provides task and user interface information. The online books are available in HTML and PDF versions (DynaText is no longer supported). The HTML versions are accessible from the NetView Console using the Help..Books Online menu item, which will bring up the books in the Netscape Navigator or Netscape Communicator browser. Preface ix

10 Accessability Information PDF versions are available in the /usr/ov/books/$lang/pdf directory. In addition, you can access online documents at this Web site: A user name and password are required. Refer to Tivoli NetView for UNIX User s Guide for Beginners for information about accessability. Keyboard Access Standard shortcut and accelerator keys are used by the product and are documented by the operating system. Refer to the documentation provided by your operating system for more information. Contacting Tivoli Support Refer to Tivoli NetView for UNIX User s Guide for Beginners for more information about keyboard access. If you have a problem with any Tivoli product, you can contact Tivoli Customer Support. See the Tivoli Customer Support Handbook at the following Web site: The handbook provides information about how to contact Tivoli Customer Support, depending on the severity of your problem, and the following information: v Registration and eligibility v Telephone numbers and addresses, depending on the country you are in v What information you should gather before contacting support x Mid-Level Manager User s Guide

11 Chapter 1. Quick Start for AIX Startup Tasks This chapter is intended for those of you who are already familiar with MLM, Tivoli NetView, UNIX commands, and SNMP networking. If you are not familiar with these concepts, you might want to first read Chapter 2. What Is MLM? on page 15. This chapter provides a scenario to help you learn the basic concepts for configuring MLM. After performing the steps in this chapter, a basic distributed manager and a managed SNMP node are set up. The MLM installation scenario described in this chapter shows an MLM installation involving three workstations. The software is installed as follows: v v v nv6kmgr is the network top-level manager. The Tivoli NetView program is installed on the nv6kmgr node. mlmbox is the mid-level manager for a group of nodes. The MLM and SNMP agent (MIB-II) are installed on the mlmbox node. snmpnode is one of the nodes being managed by the MLM. The System Information Agent (SIA) is installed on snmpnode. Assume that the SIA is used as an SNMP agent. Ideally, you should install each software program on a separate workstation. If you do not have the software installed on three separate workstations, you can still follow the steps in this scenario. As you perform the steps, it will become apparent which steps are redundant. For example, in the first task, if the Tivoli NetView program and the MLM are installed on the same machine, you can not define separate community names for the MLM and the Tivoli NetView workstations. Follow the tasks in this chapter to set a threshold on the MLM node, monitor a process on the snmpnode, and to send a trap to Tivoli NetView if the status of the process changes (it stops or starts running). It is assumed that the MLM, SIA, and the Tivoli NetView daemons are already installed and running. The tasks for completing this scenario are as follows: 1. Define read-write community names on the remote snmpnode 2. Define read-write community names on the distributed MLM node 3. Define a community name on the Tivoli NetView manager 4. Set a trap destination to forward traps from the MLM to Tivoli NetView 5. Set an MLM threshold to test the configuration Task 1: Defining a Community Name on the Remote SIA Node 1. Login to snmpnode as root and edit the /etc/snmpd.conf file. This file defines the community name the SNMP agent on snmpnode expects to see in Get or Set requests from other nodes. In the section where community names are defined, add the following lines: #community name snmp agent expects to see in SNMP requests from MLM community tivoli mlmbox readwrite #community name snmp agent expects to see in SNMP requests from smconfig community tivoli nv6kmgr readwrite 1

12 Save these changes and exit. These changes enable you to use a readwrite community name of tivoli for SNMP requests from mlmbox and nv6kmgr. For polling purposes, MLM needs read-only access, but the smconfig tool needs read-write access and any node where it is installed also needs to be configured for read-write access. 2. On the command line, enter the refresh -s snmpd command to refresh the SNMP daemon and pick up the changes you made to the daemon configuration file (the /etc/snmpd.conf file). Task 2: Defining Community Names on the Distributed MLM Node Read This First! Do you have both Tivoli NetView and the MLM on the same machine? If so, use the SNMP Configuration dialog box to make the entries in the ovsnmp.conf file shown in step 1. Editing the ovsnmp.conf file directly is not supported by Tivoli NetView. Task 3 explains how to access this dialog box. 1. Login to mlmbox as root and edit the /usr/ov/conf/ovsnmp.conf file. (If the file is not in this directory, check in the /var/adm/smv2 directory. If it is not there, copy the default ovsnmp.conf file from /usr/lpp/smmlm/original to the /var/adm/smv2 directory.) Add the following entry to the ovsnmp.conf file: #community name that MLM uses for SNMP requests to snmpnode snmpnode::*:::::tivoli When a request is sent by this MLM node to gain information from the SIA node snmpnode, a community name of tivoli will be included in the request. File the changes. 2. Edit the /etc/snmpd.conf file on the MLM node. In the section where community names are defined, add the following line: #community name that MLM expects to see in SNMP requests from NV6K community tivoli nv6kmgr readwrite When a request is received by this MLM node from the Tivoli NetView manager nv6kmgr, the request must have a community name of tivoli for it to be honored. Save the changes and exit the file. 3. On the command line, enter the refresh -s snmpd command to refresh the SNMP daemon and pick up the changes you made to the daemon configuration file. At this point, the snmpnode and MLM manager can communicate and share information. Task 3: Defining a Community Name on the Tivoli NetView Manager 1. Logon to nv6kmgr as root and start the Tivoli NetView graphical interface if it is not already running by entering netview 2. From the Tivoli NetView menu bar, select Options > SNMP Configuration. 3. The SNMP Configuration dialog is a graphical representation of the Tivoli NetView /usr/ov/conf/ovsnmp.conf file. Because this node is running Tivoli 2 Mid-Level Manager User s Guide

13 NetView, you should use this dialog box to change the ovsnmp.conf file, rather than editing the file directly (see Figure 1 on page 3). Enter a community name for the MLM node in the Tivoli NetView SNMP Parameters field of the window: Figure 1. Tivoli NetView SNMP Configuration Window The community name definition controls the community name that is used when you start the MLM smconfig application on the Tivoli NetView node for host mlmbox. In addition, the community name for NetView to use for reading SNMP values from the snmpnode can also be defined. This scenario uses the default of public. Chapter 1. Quick Start for AIX 3

14 4. Select Add to add this community name definition. When the entry is successfully added, it is moved to the top of the window under Specific Nodes. 5. Now, add an entry for snmpnode, again using tivoli as the Set Community name. Select Add to add this community name definition. 6. Click OK to apply the changes and leave this dialog. 7. From the Tivoli NetView menu bar, select Options > Topology/Status Polling Intervals: IP... On the window that appears, ensure the check box for Enable Polling and Discovery Settings is selected, so that the changes you made to the ovsnmp.conf file through the Tivoli NetView interface become effective immediately. Next, set a trap destination so that traps received or generated by the MLM are forwarded to the Tivoli NetView node. Task 4: Setting a Trap Destination to Forward MLM Traps to Tivoli NetView 1. In this scenario, smconfig is installed only on the Tivoli NetView manager, so you must run it from that node. At the AIX command line on nv6kmgr, start smconfig for mlmbox by entering smconfig -h mlmbox. The Tivoli NetView MLM Config main window is shown in Figure 2 on page 5: 4 Mid-Level Manager User s Guide

15 Figure 2. Tivoli NetView MLM Config Main Window The window you see may differ from this one, depending on what is installed on the MLM node. Chapter 1. Quick Start for AIX 5

16 If the Main Window is not displayed... If you found that the main window is blank, and there are messages saying that MLM agents were not found, check the following: v v Ensure the midmand daemon is running on the MLM node. If it is not, enter /usr/bin/midmand or /usr/etc/smmlm at the AIX command line. Check the community names you defined on the Tivoli NetView node in the ovsnmp.conf database and the community names you defined on the MLM node in snmpd.conf. Remember that they must match. You may need to add entries for loopback that also use the same community name, for example, if both the MLM and smconfig are on the same node. 2. Select MLM Trap Destination Table from the Agent Configuration list and click View/Modify. The Trap Destination Table window, which is shown in Figure 3 on page 7, is displayed. 3. Select nv6kmgr and click Modify. Enter the information as shown in Figure 3 on page 7. 6 Mid-Level Manager User s Guide

17 Figure 3. MLM Trap Destination Table Window 4. Click Apply to make this change. This sends an SNMP set request to the SNMP agent on mlmbox. The message Modify successful is displayed in the Messages area. Chapter 1. Quick Start for AIX 7

18 I Got A NoSuchName Error! Did you get an error saying that the variable may be in read-only mode? This error occurs when the community name that smconfig is sending to the MLM in the request has read-access. This error can be caused by the following: v v The community name has read-only access. Check the ovsnmp.conf file on the node where smconfig is installed to ensure you specified read-write access (not read-only access) for community name tivoli. smconfig is using the default community name of public rather than tivoli. Check the Tivoli NetView MLM Config main window to see what community name is being used. If it is public, look at the ovsnmp.conf file on the node where smconfig is installed to ensure you entered the community name correctly. Now, test your setup by defining an MLM threshold against an SIA MIB variable. Task 5: Set an MLM Threshold for a Variable on the SIA Node To set a threshold on the smsiasystemprocesspid MIB variable that to watches for the existence of a process and generates a trap if the status of the process changes, do the following: 1. If smconfig on nv6kmgr is not running, restart it by entering smconfig -h mlmbox. The Tivoli NetView MLM Config main window is displayed. 2. If smconfig is already started, type mlmbox in the Name or IP Address field and click Refresh. 3. Select MLM Threshold and Collection Table from the Agent Configuration list and click View/Modify. The MLM Threshold and Collection Table window is displayed. 4. In the Name field, select Monitor_Process and click Add/Copy. 5. Complete the fields as shown in Figure 4 on page 9. 8 Mid-Level Manager User s Guide

19 Figure 4. MLM Threshold and Collection Table Window Note that you prefix the character string snmpnode to the beginning of the MIB variable object ID to indicate that the threshold is being set against a MIB variable on a remote node called snmpnode. Chapter 1. Quick Start for AIX 9

20 6. Click Arm Actions. The Threshold Arm Actions window displays. Enter the information shown in Figure 5 on page 10: Figure 5. Threshold Arm Actions window 7. Click Close to close the window and return to the MLM Threshold and Collection Table window. Click on Rearm Actions... On the window shown in Figure 6, enter the following information: Figure 6. Threshold Rearm Actions window 8. Click Close to close the window, returning to Figure 4 on page 9, the MLM Threshold and Collection Table window. Click Apply on the Threshold and Collection Table window to make the changes. 9. On the snmp node, start an xclock process if it is not already running. 10. After a few minutes, from the MLM Threshold and Collection Table Window ( Figure 4 on page 9), you can select the new threshold you defined and click on Start Query to see data being sampled. 10 Mid-Level Manager User s Guide

21 11. To test the threshold, kill the xclock process. A trap should appear on the Tivoli NetView Control Desk on nv6kmgr. Figure 7 shows an example of a trap when it arrives at the Tivoli NetView Control Desk: Figure 7. Tivoli NetView Control Desk window Startup Troubleshooting Tips If you want to continue with a quick overview of configuring the MLM s status monitoring and discovery functions, continue with Distributing Status Monitoring and Node Discovery to the MLM on page 61. If you completed the steps in this quick start chapter, and a threshold trap was not received at the Tivoli NetView Events Display window, follow these steps. Most of the following tips apply to troubleshooting any configuration problem: 1. On the snmp node, ensure that sysinfod and snmpd are running by issuing these commands: ps -ef grep sysinfod ps -ef grep snmpd Ensure that all occurrences of the xclock process are stopped by issuing this command: ps -ef grep xclock 2. On the MLM node, ensure that both midmand and snmpd are running by issuing these commands: ps -ef grep midmand ps -ef grep snmpd 3. Verify the following through smconfig: Chapter 1. Quick Start for AIX 11

22 v In the MLM Threshold and Collection Table window ( Figure 4 on page 9), ensure the entry you created has an enabled state. If a remote node is being polled from the MLM as in the scenario in this chapter, ensure that the SNMP alias, host name, and IP address is prefixed to the MIB variable specified in the Local/Remote MIB Variable Expression field. v In the MLM Trap Destination Table window, ensure that the Activation Time and Deactivation Time are set to 00:00 and both Activation Day of Week and Deactivation Day of Week are set to none. Or, if you have values set, ensure the trap destination is active. 4. On the MLM node, check the /var/adm/smv2/log/midmand.log file to determine whether a trap was generated and forwarded. You can search for the text string Received trap. Here is an example of how a threshold being met and the resulting trap might appear in the midmand.log. The third entry indicates what was done with the trap: : 11/14/94 14:54:41 Threshold cpusm: 92 > 90 met with oid: : 11/14/94 14:54:41 Received trap 6(4) from : 11/14/94 14:54:42 No filter rule was matched: default action = FORWARDED If the third entry says default action = BLOCKED, an entry in the Filter Table on page 76 is preventing this trap from being forwarded. If the third entry says Couldn't resolve destination "xxxx", something is wrong with the node specified in the Trap Destination Table on page 117 for trap forwarding. Check to make sure the node specified (xxxx) is a valid host name. You can also check the /var/adm/smv2/log/smtrap.log file. It contains all traps received by MLM. Note: If a workstation has MLM and the Tivoli NetView program installed, ensure that the MLM and Tivoli NetView programs are not competing for the same Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) port for incoming traps. When the MLM is installed on a node that already has Tivoli NetView installed, the installation process automatically disables the UDP 162 and TCP 162 trap reception ports. You can ensure these are still disabled by checking the Trap Reception table through smconfig. Your quick start installation is now complete. If you have additional installation tasks to complete, refer to Chapter 3. Installing MLM on page 21 or Chapter 4. Installing MLM on Remote Nodes on page 31. Otherwise, refer to the following chapters for more information. Table 1. How to Proceed after Quick Start Set-up If you need information on Setting MLM daemon options and community names Controlling MLM daemons using SMIT or shell scripts Go to Chapter 5. Configuring MLM on page 33 Chapter 6. Starting, Stopping, and Maintaining MLM on page 45 Online MLM information Manipulating MLM MIB tables using the smconfig Chapter 7. Using smconfig on page Mid-Level Manager User s Guide

23 Table 1. How to Proceed after Quick Start Set-up (continued) If you need information on Go to Distributing status monitoring and node discovery to the MLM Accessing the MLM MIB tables from Tivoli NetView Chapter 8. Using MLM with Tivoli NetView on page 61 Configuring the MLM MIB tables Chapter 9. MLM Tables on page 69 Chapter 1. Quick Start for AIX 13

24 14 Mid-Level Manager User s Guide

25 Chapter 2. What Is MLM? Mid-Level Manager (MLM) helps you manage SNMP information. MLM enables you to move system and network monitoring and management from the central network management platform, Tivoli NetView, to an intermediate SNMP-based manager. Acting as this intermediate SNMP manager, MLM reduces the amount of network traffic and the amount of processing that must be done by the central network manager. What Are the MLM Components? MLM consists of the following feature components: v The MLM X-based configuration tool, smconfig (CFG) v The MLM daemon This section provides an overview of each feature and describes how they interact to provide distributed system and network management. MLM Configuration Application The MLM Configuration Application (smconfig) is a Motif-based graphical interface that is used to configure the MLM features and to perform systems administration. The MLM Configuration Application interacts with the MLM by issuing SNMP get and set commands on the MLM MIB variables on the agent nodes. You can use smconfig to get and set MIB variables for all the supported platforms. MLM The concept of a mid-level manager might already be familiar to you. As a distributed SNMP manager, the MLM can be configured to monitor any set of SNMP devices in a specified network. These nodes can be grouped by location, function, type, or any other convenient group. Through regular polling of local or remote nodes, the MLM can compare the data received against defined thresholds and filters. If the threshold and filter criteria are met, the MLM can forward the information to the overall management system for your network or take some other defined action. Using the MLM, you can customize aliases to each MLM group of managed nodes, and you can use a central set of configuration files. When Tivoli NetView is installed in the network, the MLM can take over responsibility for network discovery and interface status monitoring from Tivoli NetView for the MLM subnet. This reduces the amount of network traffic and reduces the time it takes to discover status changes. The MLM is fully configurable through its MIB. The /usr/bin/midmand daemon handles all requests to get or set MLM management information in the MIB tables and is responsible for performing the configured management tasks. The SIA can be installed on network nodes where you want to access the system information through SNMP. Note: If a fully-deployed Tivoli Management Environment exists, most of the SIA capabilities can be replaced with the Tivoli Distributed Monitoring product. The MLM is installed on network nodes that act as intermediate or mid-level managers in the network. The MLM polls SIA nodes and other SNMP-managed 15

26 nodes for system information and status (node up or down, session up or down, or other changes). It manages these nodes through automated commands and selective trap forwarding to your overall network management program (referred to as the top-level manager in this book). The MLM configuration option is automatically installed with Tivoli NetView. Through this interface, you can configure and administer all MLM agents in your network. You can install the standalone MLM Configuration Application on a non-netview node to configure the MLM. What Are the Benefits of MLM? MLM offers key system and network management benefits in the following areas: v Closely monitors MIB characteristics on a critical node. When an SNMP agent is installed on a node, you can obtain system information about that node and monitor the information from an MLM workstation. The smconfig application also continues to work with the SIA. Using smconfig, you can configure the MLM to monitor information in the SIA MIB and extend the SIA MIB to run commands or monitor files. For example, you could set up a command table entry to monitor status on printer queues using the lpstat command, and monitor the results of this command through the MIB variable created by this entry. Through the file monitor table, you can monitor important files (such as system files and application output files) for various conditions that you define. The conditions you can monitor include the existence of specific character strings, and file status such as changes to the file size or file permissions. You can define what action should be taken when a string of text or some other change occurs in the monitored file. v Manages remote nodes and LAN segments. You can place MLMs in strategic locations throughout a network and move some of the monitoring tasks from the top-level manager to the MLMs. An MLM can poll the managed nodes in its segment and, using its filtering and thresholding capabilities, control the amount of information that is forwarded to the top-level manager in the form of traps. Through the alias table, you can customize a single configuration to work for several groups of managed nodes. For example, you can configure a threshold for a group of nodes using an alias for the group and then customize the alias table for each MLM to resolve to the group of nodes managed by that MLM. v Offloads node discovery and status-checking tasks from the top-level network manager. MLMs in the network can take over discovery and status monitoring for their subnets, reducing network traffic and more efficiently discovering changes in the network. You can provide Tivoli NetView with a seed file of MLMs in the network, or you can let Tivoli NetView automatically discover MLMs and turn over responsibility for discovery and status checking to them. When MLM monitors the nodes on which the program is running and other managed nodes in the network, it provides the following benefits: v Fully distributed network management. This enables you to manage both networks and systems from a single SNMP management platform. v An easy-to-use graphical interface that runs on the UNIX workstation. You can configure the MLM and SIA programs to satisfy specific systems management requirements for your network. 16 Mid-Level Manager User s Guide

27 v v v Automation capabilities. You can configure MLM to automatically issue commands that respond to situations. Reduced WAN traffic. The sophisticated thresholding, analysis, filtering, node discovery, and status monitoring capabilities of MLM reduce the amount of network traffic. You can monitor remote LAN segments and forward only those traps that a network operator monitors. Data collection. With MLM thresholding, you can collect data for use later in trend analysis or problem determination. Distributing MLM Software Your decision on which of the MLM features to install in your network, and how many of each feature, depends on the size and type of your network. The following scenarios illustrate how the MLM software might be distributed in a network. Scenario 1: Systems Management In the example network, certain workstations are considered critical because of their function. These critical nodes have an SNMP agent installed (MIB-II /or SIA) with one MLM installed in the segment. The system administrator has set up MLM to closely monitor applications on these critical nodes and forward traps to the top-level manager if problems arise. Tivoli NetView Configuration Application IBM SNMP IBM SNMP Agent (SIA) IBM SNMP Agent (SIA) SNMP IBM SNMP Agent (SIA) Tru64 UNIX SNMP Agent (SIA) HP-UX SNMP Agent (SIA) Sun Solaris SNMP Agent (SIA) Figure 8. Monitoring Critical Nodes Chapter 2. What Is MLM? 17

28 Note: If a fully deployed Tivoli Management Environment exists, as shown in Figure 8 on page 17, most of the SIA s capabilities can be replaced with the Tivoli Distributed Monitoring product. Monitoring critical nodes provides the following information: v Certain critical nodes, such as file servers or print servers, can be monitored. For example, the file server thresholds can be set for a low capacity of file space or for excessive CPU utilization. v Recovery scripts can be set up and run when thresholds are reached. Important traps are forwarded to the top-level manager. v Polling is frequent because all polls to the LAN are local. The only network traffic is from traps forwarded to top-level manager or occasional polls for SNMP information to other boxes in network. In addition to monitoring these nodes for information in the MLM MIB, you can monitor each node for MIB II information. Scenario 2: Distributed SNMP Management In this scenario, as shown in Figure 9, the MLM acts as a mid-level manager, relieving some systems management duties from the top-level manager. Each managed node has the SIA installed. The managed nodes are grouped together logically through the MLM alias table; thresholds and filters are set against those aliases so that all nodes are being monitored for the same data. Tivoli NetView Critical Data Threshold Analysis Filter Mid-Level Manager (MLM) Commands Polling Traps Others Workstations SNMP Nodes Grouped by Device Type Routers Bridges Figure 9. Using Mid-Level Managers v One MLM manages all nodes in the LAN segment, building, or subnet. This arrangement is repeated for each managed group. Groupings of nodes are 18 Mid-Level Manager User s Guide

29 v v logical (such as all machines that serve the same function or all machines within the same subnet) or physical (all machines in one building). MLM monitors all SNMP nodes in its segment for critical data and forwards critical data to the top-level manager. The system administrator writes shell scripts and sets up automatic command invocation based on threshold and file monitoring so that many problems do not need the attention of the top-level manager. You can optionally use TCP, instead of UDP, for reliable trap delivery of critical traps to the top-level manager. TCP should be used if the MLM reports traps to Tivoli NetView or another MLM. Scenario 3: Monitoring in a Wide Geographic Area (Branch Management) A large and geographically dispersed network, such as the one shown in Figure 10 on page 20, can require high bandwidths to accommodate network traffic when all nodes are managed from a central top-level manager. To keep wide area network (WAN) traffic between the top-level manager and the managed nodes at a minimum, the polling tasks have been moved to local area networks (LANs), including status monitoring of managed nodes, and discovery of status changes in the network, such as new nodes coming online. MLMs within each geographic LAN segment manage the nodes within their segments. The agents in each segment are configured to forward traps to the MLM in that segment. Each MLM filters traps it receives from the managed nodes and sends only the most important data to the top-level manager. This distributed configuration of MLMs in a network provides the following benefits: v WAN traffic is kept to a minimum. v The hierarchy of managers ensures that most problems are handled locally. v Aliasing is used so that each LAN segment has virtually the same MIB table configuration; only the Alias Table for each LAN MLM is modified to reflect the devices within each LAN segment. v Local MLMs are responsible for tracking the statuses of sessions and discovering new nodes or expired nodes; Tivoli NetView is periodically updated with the latest topology. In this example, each MLM is configured to enable traps to be forwarded to more than one manager. For example, you might configure MLM to forward traps to a primary top-level manager during normal business hours and to dynamically change the trap destination to a secondary top-level manager at a specified time. Chapter 2. What Is MLM? 19

30 Tivoli NetView Tivoli NetView Mid-Level Manager (MLM) Threshold Analysis Filter Threshold Analysis Filter Mid-Level Manager (MLM) Commands Polling Traps Commands Polling Traps Figure 10. Managing Network Resources in a Wide Geographic Area 20 Mid-Level Manager User s Guide

31 Chapter 3. Installing MLM Planning for Your Installation This chapter contains information about installing, verifying, and removing the Tivoli NetView MLM program features. The following list is a guide to help you plan the installation of MLM. 1. Analyze your network management requirements to determine how network segments will be monitored. For example, will you need to manage applications, machines, a network, or a combination of these things? Are some machines more critical than others (thus needing to be polled more frequently)? 2. Organize devices into logical groups based on the function of each machine. For example, put machines that act as file servers in one group, and machines that are running a specific application in another group. 3. Think about how you can group devices together under aliases. You can save time and ensure consistency by using the same aliases for groups of nodes within a LAN segment and changing the list of nodes in that MLM alias (the resolved nodes) after you have distributed the configuration. 4. Decide what aspects of the network devices, in each group, will be monitored and where the monitoring should occur. You can use the examples in Distributing MLM Software on page 17 as a guide for implementing MLM monitoring and management functions in your network. 5. Consider placing an MLM in each segment so that polling is local. Local polling results in faster network response. 6. The stand-alone MLM Configuration Application can be installed on nodes for which you can configure remote MLMs in your network. The stand-alone MLM Configuration Application is a subset of the complete MLM Configuration Application that comes with Tivoli NetView. Item 7 below discusses the complete MLM Configuration Application. You can install the stand-alone MLM Configuration Application on any AIX, Solaris, or HP-UX workstation where Tivoli NetView is not running. 7. If you have Tivoli NetView, the MLM Configuration Application is already available from the NetView Tools pull-down menu. v The Tivoli NetView event configuration file is automatically updated to display MLM-generated threshold traps in the events display area. v The Tivoli NetView graphical interface provides access to a set of predefined MLM MIB applications and the MIB browser. v The Tivoli NetView MIB loader automatically loads the MLM MIBs. v The Tivoli NetView MIB application builder can be used to create your own MIB applications that monitor MLM MIB objects. v The MIB browser can be accessed from smconfig to obtain MIB object IDs and descriptions when creating MIB table entries. v The MLM data in the collection files can be converted to the format used by Tivoli NetView for graphical presentation by the graph applications. 21

32 AIX Installation The install format for AIX MLM installation is installp image. The installation described in this section is through SMIT. Before installing MLM, note the following requirements: v You must have root user authority. v You can install the following feature components of the MLM program: The MLM Configuration Application (CFG) The Mid-Level Manager (MLM) v Refer to the README files provided with the MLM program for additional information not provided in the documentation. The README file names are listed in the following table: Table 2. Location of README Files for the Tivoli NetView MLM Features Feature MLM Configuration Application Mid-Level Manager File Name /usr/lpp/mlmcfg/readme.cfg /usr/lpp/smmlm/readme.midmand Required Hardware The following hardware components are required: v RS/6000 PowerPC, , and v Additional memory is not required above what is required for the AIX operating system. v The following amounts of free disk space, for each Tivoli NetView MLM feature, in megabytes: Table 3. Free Disk Space Requirements for the Tivoli NetView MLM Features Feature Feature Name Free Disk Space MLM Configuration Application mlmcfg.eui.obj 10 MB Mid-Level Manager smmlm.subagent.obj 5 MB v v v v Color display (for MLM Configuration Application) IBM or compatible mouse Connection to your TCP/IP network CD-ROM drive or an installable file image on the server for installing the Mid-Level Manager programs Required Software The following software components must be installed, configured, and operational: v AIX Version v AIXwindows Environment/6000 (for MLM Configuration Application) v X Window System Version 11.4 or later (for MLM Configuration Application) v OSF/Motif Version 1.2 or later (for MLM Configuration Application) v TCP/IP 22 Mid-Level Manager User s Guide

33 Setting the LANG Variable The MLM program has algorithms for finding language sensitive files. An attempt is made to locate the files based on the value of the LANG environment variable. However, the MLM program defaults to operating as though the LANG environment variable is set to C if one of the following happens: v The LANG variable is not set. v The value of the LANG variable is not a recognized locale. v A required file is not found in the path referenced by the LANG variable. What the Installation Process Does This section describes the actions that occur when you install the MLM Configuration Application and MLM features. What the MLM Configuration Application Installation Process Does When you install the MLM Configuration Application (mlmcfg.eui.obj) feature, the installation process performs the following functions: v v v Installs using the directory /usr/lpp/mlmcfg. Adds MIB definitions to /etc/mib.defs for use with the AIX snmpinfo command. Creates an ovsnmp.conf file in the /usr/lpp/mlmcfg/original directory. What the MLM Installation Process Does The installation process for the MLM (smmlm.subagent.obj feature) performs the following functions: v v v v v v Installs using the directory /usr/lpp/smmlm. Updates the /etc/snmpd.conf file with the following items: Comments out all trap destination lines Adds a trap destination loopback ( ) Sets the SMUX timeout to 60 seconds and maximum packet size to 16K Creates an ovsnmp.conf file in the /var/adm/smv2/ directory Adds configuration entries in the /var/adm/smv2/mlm/config/install.config file for those trap destinations that are commented-out in the /etc/snmpd.conf file Disables MLM trap reception if you have Tivoli NetView installed. However, traps that are generated by MLM (for example, threshold, status, and session traps) are still processed by the filter table and sent to the destinations that you configure through the trap destination table. Adds the following entries for the MLM: Table 4. Installation Entries Entry File Purpose start /usr/etc/smmlm "" /etc/rc.tcpip Starts the Tivoli NetView MLM daemon. midmand sm6000 /etc/snmpd.peers Required for a SMUX connection. Installing from a Local Device (CD-ROM Drive) to a Local Node Installing the MLM program using SMIT takes approximately five minutes for each feature. There are two sets of installation procedures. Use the information that is appropriate for the AIX release you are using. Chapter 3. Installing MLM 23

34 Installing on AIX To install the Tivoli NetView MLM features on a system running AIX using SMIT, follow these steps: Table 5. Steps for Installing Tivoli NetView MLM on a System Running AIX Step Action Result 1 Insert the Tivoli NetView CD into the CD-ROM drive, and mount the CD (see your operating system manual for further details.) The CD is mounted. 2 Type smit at the AIX prompt to access the installation program, and press Enter. SMIT System Management menu appears (SMIT main menu). 3 Select Software Installation and Maintenance. Software Installation and Maintenance menu is displayed. 4 Select Install and Update Software. Install and Update Software menu is displayed. 5 Select Install/Update Selectable Software (Custom Install). 6 Select Install/Update from All Available Software. 7 Specify the path to the software you want to install. If you are installing the MLM, the path is /cdmountpoint/mlm/aix/mlm-aix If you are installing the smconfig, the path is /cdmountpoint/mlm/aix/cfg-aix The Install/Update Selectable Software (Custom Install) menu is displayed. The Install Software Products at Latest Available Level menu is displayed. The path to the install image is displayed. 8 Select OK. The installation options are displayed. 9 Select List next to the SOFTWARE to install entry field. A list of features is displayed. 10 Specify the software you want to install: v If you are installing the MLM, select smmlm ALL. v If you are installing the MLM Configuration Application, select mlmcfg ALL. Select OK. 11 Use the List option to change the remaining entry fields. Asterisks indicate required entry fields. See the AIX operating system documentation or use the SMIT online help facility for information on these fields. The selection is displayed in the entry field. The selected options are displayed in the entry fields. 12 Select OK. A message is displayed that asks are you sure you want to install. 13 Select OK. The appropriate Tivoli NetView MLM files are loaded into the system. See Note Mid-Level Manager User s Guide

35 Table 5. Steps for Installing Tivoli NetView MLM on a System Running AIX (continued) Step Action Result 14 Select Done to return to the Install/Update From All Available Software menu or select Exit SMIT from the Exit pull-down menu to leave SMIT. The selected operation is performed. Table Note: 1. Files are displayed during the installation process. See the smit.log file for a listing of these files. The smit.log file is saved under the home directory ($HOME/smit.log) of the user who is performing the installation. Removing Local-Node Tivoli NetView MLM Software Use SMIT to remove the Tivoli NetView MLM features and all related directories and files from a local node. You must have root authority to perform this task. When the MLM program is removed, you can use SMIT to reinstall it. See What the Installation Process Does on page 23 for information on installing the Tivoli NetView MLM program. To remove the Tivoli NetView MLM features using SMIT, follow these steps: Table 6. Steps for Removing the Tivoli NetView MLM Program Using SMIT Step Action Result 1 To access SMIT, choose one of the following methods: v Type smit smv5 at the AIX prompt. v Select Tivoli NetView MLM V5...SMIT from the Tivoli NetView Administer pull-down menu. The Tivoli NetView MLM SMIT menu is displayed. 2 Select Local operations. The Local operations menu is displayed. 3 Select Remove the Systems Monitor for AIX products. 4 Select one of the following operations: v Remove Mid-Level Manager (MLM) product. v Remove MLM Configuration Application product. 5 Select Done to return to the Local operations menu or select Exit SMIT from the Exit pull-down menu to leave SMIT. The Remove the Systems Monitor for AIX products menu is displayed. A verification message box is displayed when this action is complete. The selected operation is performed. Solaris and HP-UX Installation The install format for Solaris, and HP-UX is a tar format. The tar image is installed using the tar command followed by running the install script. Installation Requirements Before installing MLM, note the following requirements: v v You must have root user authority. You can install the following feature components of the MLM program: The MLM Configuration Application (CFG) The Mid-Level Manager (MLM) Chapter 3. Installing MLM 25

36 v Refer to the README files provided with the MLM program for additional information not provided in the documentation. The README file names are listed in the following table: Table 7. Location of README Files for the Tivoli NetView MLM Features Feature File Name MLM Configuration Application /usr/lpp/mlmcfg/readme.cfg Mid-Level Manager /usr/lpp/smmlm/readme.midmand Required Hardware The following hardware components are required: v Compaq Alpha workstation. v HP-UX 9000 Series 700 or 800 workstation. v Sun workstation capable of supporting Solaris Version 2.5.1, 2.6, or 2.7. v v v v v v Additional memory is not required above what is required for the HP-UX and Solaris operating systems. 10 MB of free disk space on the Compaq Alpha workstation for the Mid-Level Manager. 7 MB of free disk space on the HP-UX and Sun workstations for the Mid-Level Manager. 15 MB of free disk space for the MLM Configuration Application. Connection to your TCP/IP network. CD-ROM drive. Required Software The following software components must be installed, configured, and operational on the respective workstations: v Compaq Alpha workstation: TCP/IP C++ shared libraries v HP-UX workstation: HP-UX Version A9.07 and greater or Version B10.01 and greater TCP/IP v SUN workstation: Sun Solaris Version 2.5.1, 2.6, or 2.7 TCP/IP Sun Solstice Enterprise Agents (SEAs) packages: SUNWmibii, SUNWsasnm, SUNWsadmi, SUNWsacom, and SUNWsasdk Installing Sun Solstice Enterprise Agents (Solaris Only) Sun Solstice Enterprise Agents (SEAs) packages are a prerequisite to running MLM on the Sun Solaris operating system. These agents and their documentation are included on the CD-ROM. Refer to Appendix C of Tivoli NetView Installation and Configuration for information on installing the Sun Solstice Enterprise Agents. For more information about how SEAs and MLM interact, refer to Role of the SEAs (Solaris Only) on page Mid-Level Manager User s Guide

37 Installing Tivoli NetView MLM Software Installing MLM on manager and agent workstations consists of unloading the product files from the CD and running the smmlm_install script. The execution of this script: v Copies miscellaneous configuration files from the installation directory to the proper directories on the manager and agent workstations. v Copies binary files needed to run the smmlm command to the proper directories on the manager and agent workstations. v For Solaris the socket limit is increased to Note: You must have root authority on the node on which you are installing the MLM program. Installing MLM for Solaris and HP-UX from the Product CD To install the MLM files from a CD-ROM drive that is attached to your local manager or agent workstation, follow these steps: Table 8. Steps for Installing MLM from a Local CD-ROM Drive Step Action Result 1 Insert the Tivoli NetView CD into the CD-ROM drive, and mount the CD (see your operating system manual for further details.) 2 Type the following commands: For Solaris: zcat /cdmountpoint/mlm/solaris/mlm-sol.z tar xvf - For HP-UX: zcat /cdmountpoint/mlm/hpux/mlm-hpux.z tar xvf - 3 To change the directory to smmlm, enter: cd /usr/lpp/smmlm 4 Enter: smmlm_install 5 Check the following log for troubleshooting information if any problems occurred during installation: The CD is mounted. The following components are untarred from the tar file: the subdirectories that contain the executable code, configuration files, and the MLM MIB. The default installation directory is /usr/lpp/smmlm. You are now in the /usr/lpp/smmlm directory. When the installation is complete, you will receive a message indicating that MLM is installed. /usr/lpp/smmlm/smmlm_install.log 6 See Configuring MLM for Your Operational Environment on page 33 to configure MLM for your environment. Installing smconfig You can install smconfig directly from the device onto all supported manager or agent workstations. The process for installing the program includes: v Setting up the directory for the program. v Getting the program files from the Tivoli-supplied product CD, using the tar command. Chapter 3. Installing MLM 27

38 v Running the smconfig install script to install the program. You can use a file transfer utility such as FTP to transfer the files from the CD to other nodes. Run the smconfig installation script on each node on which you want to run smconfig. Note: You must have root authority on the node on which you are installing the smconfig program. Installing smconfig for Solaris, HP-UX, and HP-UX from the Product CD To install the smconfig files from a CD-ROM drive that is attached to your local manager or agent workstation, follow these steps: Table 9. Steps for Installing MLM Configuration Application from a Local CD-ROM Drive Step Action Result 1 Insert the Tivoli NetView CD into the CD-ROM drive, and mount the CD (see your operating system manual for further details.) 2 Type the following commands: For Solaris: zcat /cdmountpoint/mlm/solaris/cfg-sol.z tar xvf - For HP-UX: zcat /cdmountpoint/mlm/hpux/cfg-hpux.z tar xvf - The CD is mounted. The following components are untarred from the tar file: The subdirectories that contain the executable code, configuration files, and the MLM MIB. The default installation directory is /usr/lpp/mlmcfg. 3 To change the directory to mlmcfg, enter: cd /usr/lpp/mlmcfg 4 Enter: mlmcfg_install 5 Check the following log for troubleshooting information if any problems occurred during installation: You are now in the /usr/lpp/mlmcfg directory. When the installation is complete, you will receive a message indicating that MLM is installed. /usr/lpp/mlmcfg/mlmcfg_install.log Installing MLM or smconfig for Solaris and HP-UX to Other Nodes After the MLM or smconfig program has been installed onto a manager or agent workstation in your network, you can install the program on other machines in the network that you want to manage with MLM if you have additional licenses. You have the following options for copying the files to other workstations: v Login to each machine separately and repeat the steps you followed in Installing Tivoli NetView MLM Software on page 27, or in Installing smconfig on page 27. v Use the remote install feature on the Tivoli desktop. See Chapter 4. Installing MLM on Remote Nodes on page 31 for information on this feature. Removing the MLM or smconfig To remove the MLM from the workstation on which it is installed, you must have root authority. Follow these steps to remove the program: 28 Mid-Level Manager User s Guide

39 Table 10. Steps for Removing the MLM from a Workstation Step Action Result 1 To change the directory to /usr/lpp, enter: cd /usr/lpp 2 For MLM enter: smmlm/smmlm_deinstall When the removal is complete, you will receive a message indicating that it was successful. You are now in the /usr/lpp directory. MLM is no longer installed on the workstation. To remove smconfig from the workstation on which it is installed, you must have root authority. Follow these steps to remove the application: Table 11. Steps for Removing smconfig from a Workstation Step Action Result 1 To change the directory to /usr/lpp, enter: cd /usr/lpp 2 For smconfig enter: mlmcfg/mlmcfg_deinstall When the removal is complete, you will receive a message indicating that it was successful. You are now in the /usr/lpp directory. smconfig is no longer installed on the workstation. Windows NT Installation The MLM for NT runs as part of the Microsoft SNMP Service as an extension agent. It is a special dynamic link library (DLL) that is automatically loaded by the SNMP Service. Unlike the UNIX MLM, it is not a process or a daemon. However, it has been designed to function in the same manner as the UNIX MLM, whenever possible. Installation Requirements The following are the minimum installation requirements for MLM for NT: v v v v v An Intel PC. The minimum configuration is a Pentium 133 with 256 KB L2 cache. The size of the serviced network and the intervals of key workloads like status monitoring will drive the need for faster or slower CPU speeds. 32 MB of RAM. Microsoft Windows NT Version 4.0 with Service Pack 3 or higher. TCP/IP Protocol installed and configured. SNMP Service installed and configured. The appropriate service pack (level 3 or higher) must be reapplied after installing the SNMP service. Installing the Tivoli NetView MLM for NT To install the Tivoli NetView MLM for NT, run the mlmsetup.exe program located in the cdmountpoint/mlm/nt directory. This program will launch an InstallShield installation sequence that will create all the necessary registry entries, directories, and files needed to tun the Tivoli NetView MLM for NT. Refer to the cdmountpoint/mlm/nt/readme.txt file for information on how to configure and run the Tivoli NetView MLM for NT. Chapter 3. Installing MLM 29

40 30 Mid-Level Manager User s Guide The Tivoli NetView MLM for NT program can also be configured to function as an attended MLM. Refer to the Tivoli NetView for NT User s Guide in Chapter 8 Managing Network Configuration for more information.

41 Chapter 4. Installing MLM on Remote Nodes Installing the MLM features on a remote node provides additional management capabilities. The features can be installed on a remote node using the Tivoli desktop. You must have root authority on the remote node on which you are installing the MLM features. What the Remote Installation Process Does The process to install the MLM features on a remote node is similar to the process for installing on a local node from CD. (See What the Installation Process Does on page 23 for an overview of the installation process from CD.) The only difference is what you specify in the INPUT device / directory for software field on the Tivoli Desktop window; for a remote installation, you specify the full path name of the mounted installation image file instead of the device name of a CD-ROM drive. Single Remote-Node Installation Using the Tivoli desktop enables you to install the MLM features on one remote node at a time. To install the MLM features on a single remote node using the Tivoli desktop, follow these steps: Table 12. Steps for Installing the Tivoli NetView MLM Features on a Single Remote Node Step Action Result 1 Click and hold down the right mouse button on the appropriate Tivoli NetView server or client icon. 2 Select Administer MLMs > Install/Control the Mid-Level Manager on a node options from the cascaded menu. 3 "Install w/community file" will be shown as the default operation. See the Table Note for information about the use of the ovsnmp.conf file during the MLM installation process. You must enter the node name or IP address of the node where MLM is to be installed and the root password for that machine. Make sure that all required fields (indicated by an asterisk) are filled in correctly. Click on OK. The icon s pull-down menu is displayed. The Install/Control MLMs dialog appears. A Tivoli NetView Mid-Level Manager is installed on the specified node. Table Note: During MLM installation the ovsnmp.conf file is installed from the /usr/ov/conf directory on the Tivoli NetView server to the /var/adm/smv2 directory of the target node. If the /usr/ov/conf directory does not exist on the MLM, the ovsnmp.conf file in the /var/adm/smv2 directory is used. If you have already configured an ovsnmp.conf file for Tivoli NetView and want to use that file on the target node, select Install w/out community file from the operation choice list. You can use the Tivoli desktop to copy the ovsnmp.conf file to MLM nodes. 31

42 Installation Verification The installation process for the MLM feature automatically starts the midmand daemon on the remote node using the selected startup options. The AIX SNMP agent, snmpd, is also started if it is not running. Use the Tivoli desktop to verify the midmand daemon installation. The Tivoli desktop provides process information about the daemon. To verify the midmand daemon installation, follow these steps: Table 13. Steps for Verifying the Daemon Installation Step Action Result 1 Click and hold down the right mouse button on the appropriate Tivoli NetView server or client icon. 2 Select Administer MLMs > Install/Control the Mid-Level Manager on a node options from the cascaded menu. 3 Select Status from the Operation choice list. Enter the host name or IP address and password for the target node. Click on OK. The icon pull-down menu is displayed. The Install/Control MLMs dialog is displayed. Status information for the midmand and snmpd daemons is displayed. Verify that the midmand daemon is running. If the daemon is not running, start it using one of the remote daemon operations. See Chapter 6. Starting, Stopping, and Maintaining MLM on page 45 for steps on starting the daemons. Removing Remote-Node Tivoli NetView MLM Software Use Tivoli desktop to remove the smconfig and the MLM daemons from remote nodes. When the MLM features are removed, you can use Tivoli desktop to reinstall them. To remove the MLM Features from a Remote Node using Tivoli desktop, follow these steps: Table 14. Steps for Removing the Tivoli NetView MLM features from a Remote Node Step Action Result 1 Click and hold down the right mouse button on the appropriate Tivoli NetView server or client icon. 2 Select Administer MLMs > Remove Mid-Level Manager product from a node options from the cascaded menu. 3 Enter the node name or IP address and root password of the target node. Click on OK. The icon s pull-down menu is displayed. The Remove MLM dialog is displayed. The Tivoli NetView MLM and its associated files are removed from the specified node. 32 Mid-Level Manager User s Guide

43 Chapter 5. Configuring MLM This chapter contains information about setting the options that are used when the midmand daemon is started. This chapter also explains how to define community names for nodes sending SNMP requests and for nodes receiving SNMP requests. Configuring MLM for Your Operational Environment After installing MLM, you need to perform the following configuration tasks: 1. Assign ports for SNMP daemons (midmand, bsnmpd, MIB-II agent). 2. Define community names for SNMP requests sent by MLM. 3. Define community names for validating incoming SNMP requests. 4. Configuring other SNMP daemons to work with bsnmpd. 5. Define which problems can be corrected locally and which should be forwarded to an operator at a Tivoli NetView console. 6. Write programs or shell scripts to correct problems that may be detected during monitoring. 7. Define enterprise IDs and traps for specific problems and load them into Tivoli NetView using the Tivoli NetView event configurator. 8. Configure the MLM MIB tables for filtering traps, thresholding, and executing commands. You can also create tables to perform analysis on returned MIB values, to indicate ownership of various table entries, and to specify trap destinations. Configure these tables using smconfig, saving them to configuration files. Ideally, you should configure each table to use aliases. 9. Use the Tivoli desktop to propagate the configuration files to one machine in each group, or mount the files using the Network File System (NFS). Place the files in the configuration directories for the appropriate MLM daemon. Then start the daemon using the shell scripts. 10. Customize the MLM alias table on each MLM segment to specify that the alias resolves to the specific group of devices that you want to monitor in that segment. 11. Run a test on the machine in each group on which the configuration files reside to verify that it operates as you expect. Role of the bsnmpd Daemon (HP-UX Only) On HP-UX platforms, MLM has a daemon named bsnmpd. On the AIX operating system, this function is performed by the snmpd daemon. On a Solaris system, this function is performed by snmpdx, one of the Solstice Enterprise Agents (SEAs). On the UNIX machines, all SNMP requests are received on port 161 over UDP. Multiple SNMP agents may be running on a UNIX machine, each supporting a different MIB. There needs to be a way to route incoming SNMP requests to the corresponding SNMP agent. The bsnmpd daemon fulfills this requirement. It listens for SNMP requests on port 161 and routes the requests to the corresponding SNMP agent registered in the bsnmpd.conf file. The routing is based on the following types of entries in the bsnmpd.conf file: MIB Object Identifier ServiceName 33

44 The MIB Object Identifier denotes the root of the MIB tree that the agent supports. The ServiceName is the name of the service in /etc/services on which the corresponding MIB-II agent is listening. For example, if your MIB-II agent is running on service gensnmpd, the bsnmpd.conf file should contain the following entry: gensnmpd Role of the SEAs (Solaris Only) The two SEAs relevant to Tivoli NetView MLM are snmpdx and mibiisa. The snmpdx agent is the master agent that controls the other agents. It also routes incoming SNMP requests similar to the way the bsnmpd agent works on the HP-UX platforms. In summary, this agent listens on port 161 and routes the requests to the corresponding SNMP agent based on the registration files residing in the /etc/snmp/conf directory. The mibiisa agent provides support for MIB-II. For details of these two agents, refer to the HTML documentation supplied on the CD-ROM. Also refer to Installing Sun Solstice Enterprise Agents (Solaris Only) on page 26. The midmand daemon is registered with the snmpdx agent. When snmpdx receives SNMP requests for the MIB supported by midmand, it passes the requests to midmand. The configuration files for snmpdx are in the /etc/snmp/conf directory. The snmpdx daemon resides in the /usr/lib/snmp directory. The messages from the snmpdx daemon are put in the /var/adm/messages file. To run snmpdx, enter the following command: /etc/init.d/init.snmpdx start The snmpdx daemon also starts the mibiisa daemon. When you restart your system, the snmpdx and mibiisa daemons start automatically. Assigning Ports for SNMP Daemons This step is specific to the platform on which you are installing MLM. Note: This step is not required for AIX. For HP-UX 9.x and 10.x Only For HP-UX 10.x, you can use one of the following two configurations. For HP-UX 9.x, you must use the second configuration. 34 Mid-Level Manager User s Guide For HP-UX 10.x, use the first configuration if you cannot redefine service snmp in the /etc/services file to a service other than 161/udp (because you may want to have the same definition of snmp across all your machines, which is usually set to 161/udp); otherwise, use the second configuration. First Configuration This configuration cannot be used for HP-UX 9.x because the only way to make snmpd run on a port other than 161/udp is to redefine snmp service in the /etc/services file.

45 If you are using this configuration on HP-UX 10.x, you need to run the snmpdm daemon on a port other than 161/udp by using the -P option in the snmpd command. Relevant entries in the /etc/services file are: snmp 161/udp gensnmpd 1667/udp midmand 1668/udp sysinfod 1669/udp The entry for gensnmpd denotes the port on which the snmpdm daemon is running. The entry for sysinfod is required only if you have installed SIA. The entry for midmand is added automatically during installation. Relevant entries in the /var/adm/smv2/bsnmpd/bsnmpd.conf file are: gensnmpd service snmp The gensnmpd entry makes bsnmpd forward all MIB-II requests to services gensnmpd. The service snmp entry makes bsnmpd listen on port snmp for incoming SNMP requests. Configure the snmpdm daemon so that it runs on a port indicated by service gensnmpd in the /etc/services file. To do this manually, use the following commands: 1. First, stop the snmpdm daemon by entering snmpdm -k. 2. Restart snmpdm by entering snmpdm -P To stop snmpdm subsequently. enter snmpdm -P k. To run snmpdm on port 1667 at system startup, refer to the HP-UX documentation. Second Configuration This configuration works for both HP-UX 9.x and 10.x. This configuration requires that you redefine service snmp as shown. Relevant entries in the /etc/services file are: bsnmp-snmp-in 161/udp snmp 1667/udp midmand 1668/udp sysinfod 1669/udp The entry for sysinfod is required only if you have SIA installed. The entry for midmand is added automatically during installation. Relevant entries in the /var/adm/smv2/bsnmpd/bsnmpd.conf file are: snmp service bsnmp-snmp-in The snmp entry makes bsnmpd forward all MIB-II requests to service snmp. The service bsnmp-snmp-in entry makes bsnmpd listen on port bsnmp-snmp-in for all incoming snmp requests. On HP-UX 9.x, this configuration makes snmpd run on port 1667/udp. On HP-UX 10.x, this configuration makes snmpdm run on port 1667/udp. Chapter 5. Configuring MLM 35

46 Configuring MLM on Solaris Follow these steps for configuring MLM on Solaris: 1. The startup scripts for midmand assume that the snmpdx MIB is accessible using community public for read access for loopback address. This is the default configuration for snmpdx. Therefore, unless you have changed the /etc/snmp/conf/snmpdx.acl file, the default configuration should work for you. The community information for snmpdx is in file /etc/snmp/conf/snmpdx.acl. Refer to the SEAs documentation for details on configuration. To confirm that the access is configured correctly, first ensure that snmpdx is running. If it is not running, enter the following command: /etc/init.d/init.snmpdx start Then, enter the following command: /usr/bin/snmpwalk public This command displays the list of agents that are currently registered with snmpdx. Note: Under some circumstances, snmpdx can delete one of its registered agents. If you find that the agent is running (using the ps command), but not responding to SNMP requests, enter the following command: /usr/bin/snmpwalk public The output of this command should show midmand. If it does not, find the pid of snmpdx and send the SIGHUP signal to snmpdx by entering the following command: kill -1 snmpdxpid In the previous command, snmpdxpid is the pid of the snmpdx process. Also, messages in the /var/adm/messages file may indicate the reason for deletion. 2. This step applies only if you have installed Systems Monitor SIA on your Solaris box and the SIA version number is and the SIA PTF number is not greater than U To determine the SIA versions on your box, look at the Welcome message in the /var/adm/smv2/log/sysinfod.log file. These versions of SIA worked with the bsnmpd agent; the bsnmpd agent was used for routing incoming SNMP requests. With snmpdx, bsnmpd is not required. To make SIA work correctly with snmpdx, first stop sysinfod (/usr/etc/smsia stop) and then enter the following command: /usr/lpp/smmlm/snmpdx.sia/convertsia This script will: a. Copy SIA registration files to the /etc/snmp/conf file. b. Modify the /etc/services file and add service for sysinfod. c. Copy newer versions of /usr/etc/smsia and /usr/etc/sm6000_sysinfod scripts. d. Copy a newer version of /usr/lpp/smsia/smsia_deinstall script. Defining Community Names Used for SNMP Requests Sent by MLM On SNMP-based networks, community names control the MIB access privileges that managers have on agent systems. Community names are passed back and 36 Mid-Level Manager User s Guide

47 forth in SNMP get and set requests and traps. The community name is similar to a password in that it determines whether or not an entity can gain access to information or perform an action. When MLM is sending an SNMP get or set request to a device, it needs to know the community name that it should use for that device. The ovsnmp.conf file, as shown in Figure 11, is used by Tivoli NetView and all of its applications, including MLM and smconfig. # WARNING: DO NOT EDIT THIS FILE DIRECTLY # NetView SNMP Platform now uses an ndbm database # to maintain the snmp configuration to improve performance. This # ovsnmp.conf(4) formatted file is maintained as a mirror image of the # snmp configuration database for backward compatibility of NetView # based snmp applications running on the V4R1 SNMP Platform. # # To modify entries in this file, use the SNMP Configuration commands # which are accessible through the X11/Motif graphical user interface # (OVW menu: Options->SNMP Configuration) or through the xnmsnmpconf # command line options. # # See xnmsnmpconf(1) and ovsnmp.conf(4) for more information. # :private:*:::::private: :rmon_admin:*:8:3:300::rmon_admin: #nv6kmgr nv6kmgr.raleigh.ibm.com:rmon_admin:*:8:3:300::private: #mlmbox mlmbox::*:::::sysmon: Figure 11. Tivoli NetView ovsnmp.conf File MLM looks for this file in the following directories: v /usr/ov/conf v /var/adm/smv2 Rather than defining a community name for each host, you can associate a community with an alias name that you have defined in the Alias Table. Community Names and Aliases on page 73 explains how alias names and community files interact. Defining Community Names (HP-UX Only) You can set up community names so that access to certain MIB variables is available. Because all incoming requests are received by bsnmpd, bsnmpd can enforce compliance with the community names. The community names for incoming requests need to be configured in the /var/adm/smv2/bsnmpd/bsnmpd.conf file. The format of an entry is: community <name> <address> <netmask> <permissions> <MIB subtree> Where <name> is the community name, <address> is an IP address in dotted notation, <netmask> specifies the network mask, and <permissions> is one of: none, readonly, writeonly, readwrite. The default permission is readonly. Chapter 5. Configuring MLM 37

48 The default address and netmask are If an address other than is specified, the default netmask is If a permission is specified, both the address and netmask must also be specified. <MIB subtree> defines a portion of the MIB tree to which this community name allows access. <MIB subtree> must be defined in dotted numeric notation. If <MIB subtree> is not specified, the MIB subtree for this community defaults to the entire MIB tree. Fields to the right of <name> are optional, with the limitation that no fields to the left of a specified field are omitted. For example, the default bsnmpd.conf file contains the following entry: community public This entry enables readonly access to the entire MIB tree from any manager. Also, for example, the default bsnmpd.conf file contains the following entry: community sysmon readwrite This entry enables community sysmon readwrite access to the MIB tree starting at from any manager. For more information, you can refer to bsnmpd.conf(4) Use the man bsnmpd.conf command to display this information. Some SNMP agents may validate their community name. For example, snmpd uses the /etc/snmpd.conf file for community name validation. All SNMP agents will see SNMP requests coming from loopback ( ), they will never know the manager from which the request originated. This occurs because requests are first received by bsnmpd and then sent to the appropriate SNMP agent. Defining Community Names (Solaris Only) All incoming SNMP requests arrive at port 161 and the snmpdx agent listens on that port for such requests. The snmpdx agent will validate the community name in the incoming SNMP requests. For more information, refer to the SEA User s Guide. For information about installing the SEA User s Guide refer to Installing Sun Solstice Enterprise Agents (Solaris Only) on page 26. MLM does not have its own access control file (.acl file). Therefore, the MLM MIB can be accessed using the community names defined in the /etc/snmp/conf/snmpdx.acl file. There is a bug in snmpdx which currently does not allow snmpdx to enforce the community names defined in the snmpdx.acl file for those SNMP packets that are meant for its subagents. Therefore, until this bug is fixed, the MLM MIB has read/write access for all communities. To configure community information for mibiisa, modify the /etc/snmp/conf/snmpd.conf file. By default, mibiisa gives read access to community public and read-write access to community private. The mibiisa agent does not respond if an incoming packet has an incorrect community name. If this happens a few times, snmpdx assumes that the agent is not working correctly and deletes mibiisa from its list of daemons. To correct this problem, ensure that the manager is using the correct community name for polling the MIB-II values. With the default /etc/snmp/conf/snmpd.conf file, community public will work correctly. 38 Mid-Level Manager User s Guide

49 To display the list of agents that are currently registered with snmpdx, enter the following command: /usr/bin/snmpwalk public The mibiisa and the midmand agents should be listed. If they are not in the list, send the SIGHUP signal to the snmpdx process by entering the following command: kill -1 snmpdxpid In the command above, snmpdxpid is the pid of the snmpdx process. Enter the snmpwalk command again and check the output. If the above command times out, determine whether snmpdx is running and if the /etc/snmp/conf/snmpdx.acl file contains read access to community public. Check the /var/adm/messages file for any error messages. Configuring Daemons to Work with bsnmpd (HP-UX Only) If you have an SNMP agent running on your UNIX machine, set up the bsnmpd.conf file and the /etc/services file so that bsnmpd can route SNMP requests to this daemon. Add a service to the /etc/services file that specifies the port on which the new daemon listens, for example, enter the following: newdaemonport 7130/udp Make an entry in the /var/adm/smv2/bsnmpd/bsnmpd.conf file. For example, if this agent supports MIB tree starting at , add the following entry: newdaemonport You may also want to configure a new community name for access to the new MIB. Community Names and the MLM Configuration Application The ovsnmp.conf file defines the community name that is used when you start the MLM Configuration Application. When you start the MLM Configuration Application for an agent node, check to see whether messages as shown in Figure 12 on page 40 are displayed in the Messages area on the main window. If the messages are displayed, ensure that the community name on the agent node matches the community name specified for this agent in the ovsnmp.conf file on the requesting node. Chapter 5. Configuring MLM 39

50 Figure 12. MLM Configuration Application Startup Messages When you start the MLM Configuration Application and look at tables, and see a message like the one shown in Figure 13 on page 41 when you modify a table, the MLM Configuration Application may be using a default community name of public, which usually has read access only. 40 Mid-Level Manager User s Guide

51 Figure 13. MLM Configuration Application Read-Only Table Message In either case, make sure the ovsnmp.conf and remote agent have community names that match. The following section shows some examples of how different configurations affect the community names specified in these files. Chapter 5. Configuring MLM 41