SNMP Management for BS2000/OSD User Guide
Total Page:16
File Type:pdf, Size:1020Kb
1Preface SNMP Basic Agent BS2000 V5.0 (SBA-BS2) and SNMP Standard Collection BS2000 V5.0 (SSC-BS2) provide the basic functionality for linking BS2000/OSD systems into SNMP- based management environments, e.g. the Unicenter TNG of COMPUTER ASSOCIATES. SBA-BS2 and SSC-BS2 provide network, system and application management capability from a central network management station, via SNMP.An integration package (SMBS2 or SMAWsmbs2) is supplied for integration in management platforms. The Console Monitor in SBA-BS2 comprises a management application (CMBS2 or SMAWcmbs2) on the management side. The SNMP subagent for SM2 (SSA-SM2-BS2), the SNMP subagent for openUTM (SSA-OUTM-BS2), and the subagents for the products openNet Server (BCAM subagent) and interNet Services supplement the continuously increasing number and functionality of BS2000/OSD subagents. SNMP management for BS2000/OSD also permits web access to management information. 1.1 Contents of the manual This manual describes the embedding of SBA-BS2, SSC-BS2 and the additive subagents SSA-SM2-BS2 and SSA-OUTM-BS2 into BS2000/OSD, the installation and configuration steps required for operation, and operation itself. The agents required for monitoring, together with their MIBs, are described in detail. The installation and configuration of SMBS2 / SMAWsmbs2 and PMBS2 / SMAWpmbs2 on the management station are also described. A separate chapter is devoted to web access. 1.2 Target group This manual is aimed at network planners, administrators and operators as well as system administrators who integrate the BS2000/OSD systems into an SNMP-based network, system and application management, or those who wish to operate such a system. Prior knowledge of the BS2000/OSD operating system and the basic TCP/IP terms is assumed. U24387-J-Z135-5-76 1 Summary of contents Preface 1.3 Summary of contents This manual is structured as follows: Chapter 2: Overview This chapter leads into the SNMP architecture, introduces fundamentals and describes the embedding into BS2000/OSD/OSD and the functionality of SBA-BS2, SSC-BS2, SSA-SM2 and SSA-OUTM. The function of the master and subagents is also described. Chapter 3: Installation and configuration The installation requirements and installation itself are described in this chapter for SBA-BS2, SSC-BS2 and the additive subagents into BS2000/OSD, and for SMBS2 / SMAWsmbs2, CMBS2 / SMAWcmbs2 and PMBS2 / SMAWpmbs2 on the management station. The configuration steps are also shown from the viewpoint of BS2000/OSD and of the management station. Chapter 4: Operation Chapter 4 describes the BS2000/OSD commands for startup and shutdown of the master and subagents. Chapter 5: Functions of the BASIC AGENT This chapter describes the system and SNMP group for management via the master agent and supervisor subagent, as well as application monitoring via the Application Monitor subagent and console monitoring via the Console Monitor subagent. It also describes the functions of the HTML subagent for generating customized web sites. Chapter 6: Functions of the STANDARD COLLECTION The subagents in the STANDARD COLLECTION are described in chapter 6. It also includes a description of functions and complete listings of the MIBs concerned. Chapter 7: SNMP management for extended performance monitoring with SM2 The topic of chapter 7 is the additive subagent for SM2-based performance monitoring. The functionality is described and the MIB is listed. Chapter 8: SNMP management for monitoring openUTM and openUTM applications The functionality and MIB of the additive subagent for monitoring openUTM applications are described in chapter 8. Chapter 9: Operating the management station Chapter 9 describes in detail the management applications available for use on management stations. 2 U24387-J-Z135-5-76 Preface Notational conventions Chapter 10: Web access to management information Chapter 10 describes the access to management information via the world wide web (WWW). The description of the web interface and the handling of the web interface is followed by an explanation of the how create and configure custom pages. Chapter 11: Trap server Chapter 11 describes the trap server offered for Solaris and Reliant UNIX. In addition to the trap server process, the command program for server configuration, the trap send program, and the trap receive program are also explained. Chapter 12: Configuration examples This chapter provides configuration examples for the topics basic monitoring, message monitoring, monitoring of applications and performance monitoring. Annex The Annex contains a list of the DCAM return codes (Application Monitor subagent). This manual contains a series of Figures, which show the information displayed by the relevant subagents on the various management platforms and on the web interface. 1.4 Notational conventions This manual uses the following symbols and formatting to emphasize particularly important sections of text: i for general information ! for warnings Italics for file names, names of management windows and parameters, menu titles and menu items, as well as commands and variables included in continuous text. <angled brackets> designate variables which have to be replaced by current values. fixed-width text for the representation of system inputs and outputs and file names in examples. command In the syntax description of commands, those parts that must be input unchanged (names of commands and parameters) are shown bold. U24387-J-Z135-5-76 3 Changes compared to the previous version Preface 1.5 Changes compared to the previous version Version 5.0 of the SNMP management for BS2000/OSD supports the following new functions: Availability of the integration package SMAWsmbs2 under Solaris (in connection with the management platform Unicenter TNG). Support of a trap server for Solaris and Reliant UNIX Remote capability of the master agent for the SINIX2000 subagents. Trap Acknowledge group for the supervisor subagents. Addition of HSMS subagents to the STANDARD-COLLECTION (SSC-BS2). Support for a generic trap format in the Application Monitor subagents and in the Con- sole Monitor subagents. Filters in file monitoring in the Application Monitor subagents. Addition of new traps to the openFT subagents and of new MIB objects which are sent in conjunction with the traps. Trap display in the web browser. 1.6 README file Please see the product-specific README file for functional changes and updates to the current product version, if necessary. This file is stored on your BS2000/OSD computer under the file name SYSRME.SBA-BS2.050.E. Please ask your responsible system admin- istrator for the user ID of the README file. The README file can be viewed with the /SHOW-FILE command or with an editor, or it can be printed out to a standard printer with the following command: /PRINT-DOCUMENT filename,LINE-SPACING=*BY-EBCDIC-CONTROL 4 U24387-J-Z135-5-76 2Overview SNMP stands for Simple Network Management Protocol and was developed as a protocol for network management services in TCP/IP networks. The original task of SNMP was only the monitoring and administration of LAN components such as bridges, routers, hubs, etc. in heterogeneous networks with TCP/IP protocols. In the meantime, the application range of SNMP has been extended to include system and application management. SNMP does not stand for the protocol alone, but rather for the complete corresponding management system, in the same way that the term TCP/IP designates the complete network rather than just the protocol as such. The documents relevant to SNMP are stored in RFCs (Request for Comment) by the IAB (Internet Architecture Board) as is normally the case with TCP/IP. The basic RFCs for SNMPv1 (version 1) are: – RFC 1155: “Structure and Identification of Management Information for TCP/IP-based Internets (SMI)”, May 1990 – RFC 1157: “A Simple Network Management Protocol (SNMP)”, May 1990 – RFC 1212: “Concise MIB Definitions”, March 1991 – RFC 1213: “Management Information Base for Network Management of TCP/IP-based Internets: MIB-ΙΙ”, March 1991 SNMP Level 5 of the SNMP Management of BS2000/OSD also supports SNMPv3 (version 3). The following are the associated RFCs: – RFC 2271: “An Architecture for Describing SNMP Management Frameworks”, January 1998 – RFC 2272: “Message Processing and Dispatching for the Simple Network Management Protocol (SNMP)”, January 1998 – RFC 2273: “SNMPv3 Applications”, January 1998 – RFC 2274: “User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)”, January 1998 – RFC 2275: “View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP)”, January 1998 U24387-J-Z135-5-76 5 Basic features of the SNMP management architecture Overview 2.1 Basic features of the SNMP management architecture The management platform is the central component of an SNMP installation. The management platform is a master console with graphical terminal, which enables a well- structured display of the components it manages and offers easy operation. The network and all of its systems and applications can be monitored and controlled from the management platform. SNMP is not fixed to a particular platform. The SNMP manager, also referred to as management station, resides in the management platform. The SNMP manager is an application that communicates with partner applica- tions, the SNMP agents via SNMP over a TCP/IP network. Each managed component has an agent that provides the SNMP manager with current information about the component. The initiative for controlling the activities mainly rests with the SNMP manager, which ensures that the components to be managed only have to cope with a small volume of management tasks. The basis for managing the components concerned is an exact description of the parts of these components that are to be administered (objects) in the MIB (Management Infor- mation Base). The MIB is the informational backbone of each Management Agent. It contains information on the characteristics, such as name, syntax, access rights and state, of each separate component. Specific MIBs are supplied by many hardware and software component manufacturers.