LAN Manager/X V2.2. (SINIX) SNMP Service. System Administator's Guide

Transcription

1 LAN Manager/X V2.2 (SINIX) SNMP Service System Administator's Guide

2 Is there anything you want to tell us about this manual? Please send us your comments, quoting the order number of the manual. Siemens Nixdorf Informationssysteme AG Documentation Department MR STO SI Paderborn Germany Fax: ( ) This manual was produced using paper treated with chlorine-free bleach.

3 Organizer cases Two-part organizer cases are available in two sizes for storing manuals in the present format. The ordering procedure is the same as for manuals. Width: approx. 5 cm Order No.: U3775-J-Z18-1 Width: approx. 10 cm Order No.: U3776-J-Z18-1

4 Published by Siemens Nixdorf Informationssysteme AG D Paderborn D München Order No.: U22000-J-Z Printed in the Federal Republic of Germany

5 LAN Manager/X V2.2 SNMP Service System Administrator's Guide Edition February 1994

6 Would you like to know more about this product... or about another aspect of information technology? Our Training Centers will be glad to help. Siemens Nixdorf has Training Centers at strategic locations in Germany and more than 20 countries worldwide. Please write to: Siemens Nixdorf International Training Support Oldbury, Bracknell, Berkshire RG12 8FZ United Kingdom or call Ron Johnson, Hounslow Tel: Fax: SINIX is a registered trademark of Siemens Nixdorf Informationssysteme AG. TRANSVIEW is a registered trademark of Siemens Nixdorf Informationssysteme AG. Copyright Siemens Nixdorf Informationssysteme AG 1993 All rights, including rights of translation, reproduction by printing, copying or similar methods, even of parts, are reserved. Offenders will be liable for damages. All rights, including rights created by patent grant or registration of a utility model or design, are reserved. Delivery subject to availability; right of technical modifications reserved.

7

8

9 Contents Preface 1 Product description 1 Target group 2 Summary of contents 2 Notational conventions 3 Installing SNMP Service 5 System requirements 5 Hardware requirements 5 Software requirements 6 Installing the software 6 Deinstallation 8 Starting and terminating SNMP Service 8 Using SNMP Service 9 Operating the SNMP agent 9 System architecture and data model 10 Information reported by SNMP Service 13 Objects supported 14 Common Group 15 Server Group 16 Objects that are not supported 20 Client group Workstation group 20 Domain Group 21 Alert objects 22 Alert group 22 Alert data groups 25 Alert management group 28 U22000-J-Z

10 Contents Status and error messages 29 Glossary 31 Abbreviations 33 Related publications 35 Ordering manuals 36 Index 37 U22000-J-Z

11 Preface This manual is part of the documentation for LAN Manager/X V2.2, a Siemens Nixdorf product. It describes the installation of SNMP Service (Simple Network Management Protocol Service) under LAN Manager/X and provides an overview of the product and its integration into the network architecture. LAN Manager MIB II also supports this SNMP agent extension (Management Information Base II). Any variations are indicated. Product description SNMP Service is offered in conjunction with LAN Manager/X. It can be installed on any SINIX system equipped with LAN Manager/X and TV-SXA (TRANSVIEW -SNMPA Extensible Agent). Installation of SNMP Service allows a network management station to monitor components of a LAN (local area network), e.z. bridges, routers, gateways, personal computers and SINIX systems, which are distributed over a large area, without any difficulty. SNMP Service for LAN Manager/X is an extension of the actual SNMP agent on the SINIX system, which allows communication between the SNMP agent and LAN Manager/X via LAN Manager/X-API by means of a shared library. SNMP Service runs as a daemon process on the SINIX host, which means that it does not burden the LAN. In response to queries from the network management station, it supplies information and values concerning the objects it manages. However, if a situation arises that causes an alert, the SNMP agent automatically sends a corresponding trap to the network management station responsible. In addition to working with TRANSVIEW-SNMP on the SINIX network management system, the Simple Network Management Protocol can also work with other network management systems, as it is a manufacturer-independent protocol. U22000-J-Z

12 Preface Target group This manual is intended for system administrators of LANs with SINIX host systems, and of global networks who monitor and administer a network management system. Users must already know how to install SNMP agents. Summary of contents This manual deals with the following aspects of LAN Manager/X SNMP Service: The Preface gives a brief description of the functions of SNMP Service in the LAN with regard to the SINIX host and the users addressed, and indicates how the manual is to be used. The chapter entitled Installing SNMP Service contains instructions for installation and deinstallation of the product, and lists the system requirements that must be met in order to guarantee successful operation. The chapter Using SNMP Service gives a summary of the functions of the product when it is operational in the network. The chapter entitled Information reported by SNMP Service includes a list of objects supported by LAN Manager MIB II, as well as explanations of certain features of LAN Manager/X SNMP Service. The chapter entitled Status and error messages contains a list of error messages output by SNMP Service during operation to indicate that an error has occurred. The manual also contains a glossary, a list of abbreviations, a related publications section, and an index. 2 U22000-J-Z

13 Preface Notational conventions The following notational conventions are used in this manual: Italics Courier Semi-bold courier 2 2 2Bordered courier 2 Quotation marks File names, command names, variables, options, and screen quotes such as input fields, text fields, menus, etc. in continuous text. System output such as error messages, messages, notes. User input in examples. File examples. References to other chapters and manuals. Keyboard entries in continuous text i 2! Tasks for the user. This symbol accompanies important information that must be read. This symbol indicates a warning about danger to life, machines, or files. Text accompanied by this symbol must be read. U22000-J-Z

14

15 Installing SNMP Service When you install SNMP Service, you basically copy files from the data medium to the hard disk of the SINIX server. This is a simple process. However, before you begin the installation, it is a good idea to read the following pages for information on the system requirements. There is also a step-by-step explanation of the installation process that you should follow. In case you may wish to reconfigure the SINIX server at a later stage, the chapter also includes a description of the deinstallation process. The last section provides instructions for starting and terminating SNMP Service. System requirements Before you begin to install SNMP Service, it is important to check whether your SINIX system fulfils the following hardware and software requirements. Hardware requirements SNMP Service can be installed on the following SINIX systems: MX300i MX500i RM400 RM600 RM600-xxx SE2000 PCE The other hardware requirements are the same as for LAN Manager/X V2.2 (see the LAN Manager/X V2.2 product manual, Overview and Installation ). U22000-J-Z

16 Installing SNMP Service Software requirements The following table provides an overview of the operating system software required System 2SINIX software version MX300i 2SINIX -L V5.41 C00 or later 2 2MX500i 2SINIX -M V5.41 C00 or later 2 2RM400 2SINIX -N V5.41 B10 or later 2 2RM600 2SINIX -P V5.41 B00 or later 2 2RM600/xxx 2SINIX -Y V5.41 B10 or later 2 2SE2000 2SINIX -V V5.41 A00 or later 2 2PC 2SINIX -Z V5.41 A00 or later 2 2 Other requirements include: 1. LAN Manager/X V2.2 must be installed and operational. 2. TV-SXA V1.0A30 must be installed on the SINIX system. Installing the software The SNMP Service package is located on the data medium (SMC or CD-ROM) of LAN Manager/X V2.2. Use the following steps to install the software: 1. Log on to the system console as the system administrator root. If the SNMP agent for the SINIX system is currently running, it is stopped automatically for the duration of the installation. The same applies to any previous version of the daemon process lmx.extd that may have been installed to monitor starting and termination of LAN Manager/X. 2. To start the installation, enter the following command: pkgadd -d <device_name> lmusnmp The installation program requests you to load the data medium. System-dependent device names can be found in the manual Overview and Installation. 3. Insert the data medium in the disk drive and press RETURN. 6 U22000-J-Z

17 Installing SNMP Service 4. In response to the request from the system, enter go and press RETURN. The system now copies the files from the data medium to the target system. 5. Once the copy process has been successfully concluded, the SINIX SNMP agent is restarted automatically. If LAN Manager/X is running, the lmx.extd daemon process for SNMP Service is also started automatically. In such a case, you will receive the message: snmpd: LM/X SNMP extension started. If LAN Manager/X is not running, you will receive the following message: WARNING. LM/X not running! In this case, the lmx.extd daemon is activated automatically the next time LAN Manager/X is started. The daemon process lmx.extd for SNMP Service is configured automatically in the configuration file of LAN Manager/X, lanman.ini. The entry lmxext is also made automatically in the configuration file /usr/lib/snmpd/config of the SNMP agent on the SINIX system. U22000-J-Z

18 Installing SNMP Service Deinstallation If you wish to remove SNMP Service at a later stage, use the following procedure: 1. Log on to the system console as the system administrator root. 2. Enter the following command to start deinstallation: pkgrm lmusnmp If the SNMP agent for the SINIX system is currently running, it is stopped automatically when this command is used. The same applies to the LAN Manager/X SNMP extension, SNMP Service. The entries in the configuration file of the SNMP agent on the SINIX system and the path are removed automatically. Once this process is finished, a restart of the SINIX agent is initiated. You then receive the message: Removal of <lmusnmp> was successful. Starting and terminating SNMP Service LAN Manager/X SNMP Service is one of a range of LAN Mamager/X utilities. However, because it runs as a daemon process, it is not started or terminated separately in the same way as, for example, the utilities Alerter, Replicator, etc. Instead, it is always started in conjunction with LAN Manager/X. To activate/deactivate SNMP Service, enter the following commands: net start server net stop server or lmx start lmx stop Before you start LAN Manager/X SNMP Service, you must ensure that the SINIX SNMP agent is already active. For more detailed information on the SNMP agents in the SINIX system, see the manual Networks: Supplements for RISC Systems or the manual for your operating system. 8 U22000-J-Z

19 Using SNMP Service This chapter provides a summary of how to operate an SNMP agent, which also applies to LAN Manager/X SNMP Service. For more detailed information, see the documentation on your SINIX operating system and on the SINIX SNMP agent (see the chapter entitled Related publications ). The following section contains an explanation of how LAN Manager/X SNMP Service operates within the network. Finally, there are three diagrams illustrating an internal, external, and conceptual view of the system architecture and the data model. Operating the SNMP agent A network can contain one or more network management stations to monitor and manage the network. These management stations communicate with the agents for the components they monitor using the Simple Network Management Protocol. This protocol must be implemented in both the management station and the components being monitored. The SNMP agent runs as a daemon process. Monitoring of the network is controlled by the management station, so that the components being monitored have as few functions to carry out as possible. The SNMP agent waits until it receives a message from the management station. On receiving a message, it becomes active and provides the information requested by the management station. Since SNMP is a manufacturer-independent protocol, a computer using the operating system version SINIX V5.41 can be included in the network management of every network management station running SNMP. The network management station on SINIX systems is run using TRANSVIEW-SNMP (see the chapter entitled Related publications ). U22000-J-Z

20 Using SNMP Service System architecture and data model Only one SNMP agent can be installed on each SINIX server. For this reason, Siemens Nixdorf developed a dynamically extensible SNMP agent for SINIX systems, TV-SXA (TRANSVIEW SINIX Extensible Agent). The functionality of this SNMP agent can be increased by adding the relevant extensions. LAN Manager/X SNMP Service is one of these extensions, and takes the form of a shared library. Internal structure on the SINIX server Applications LAN Manager/X LAN Manager/X SNMP Service Extension Extension Extension 3... n TV-SXA SINIX SNMP Agent SINIX Operating System This diagram illustrates the software architecture on the SINIX server in relation to LAN Manager/X SNMP Service. Only the relevant software components are included. The SINIX SNMP agent is located directly on the operating system, and can have a number of extensions. The LAN Manager/X SNMP Service extension communicates with LAN Manager/X API via LAN Manager/X, as indicated by the double arrow. Other applications on the SINIX server are not affected, and continue to run as normal. 10 U22000-J-Z

21 Using SNMP Service External view of the LAN with LM/X SNMP Service SINIX- Server 1 SINIX- Server 2 TRANSVIEW Netzmanagement- Station Lan Manager/X Lan Manager/X SNMP Agent SNMP Agent SNMP-Konsole LAN Bridge Router LAN Client PC 1 Client PC 2 Client PC 3 SNMP Agent LAN This diagram illustrates how the SINIX server and its client PCs are linked to a network management station, which is equipped with TRANSVIEW from Siemens Nixdorf and the corresponding TRANSVIEW-SNMP. There are also individual SNMP agents available for PCs, which allow the system administrator on the SNMP console to poll the PC directly, i.e. request information. LAN Manager/X SNMP Service, on the other hand, forwards information to the network management station via the LAN Manager/X server. It is not possible to obtain information on an individual client PC in the LAN. LAN Manager/X with SNMP Service is an important component in the connection of LANs with WANs. If your network management station is in a different subnetwork, you can also access the server from there using LAN Manager/X and SNMP Service. Costly system crashes and loss of data are prevented by regular control and early recognition of problems. U22000-J-Z

22

23 Information reported by SNMP Service If the network manager requests information about a device in the network, the host computer supplies a list of objects and their values, which can then be evaluated by the management system. These objects provide various types of information about the device. For example, the host displays the object HardDiskBytesAvail in a list, followed by the amount of free memory on the hard disk of the device. Since different network management services are used for different device types or network management protocols, each service has its own group of objects. The entire object group used by a particular service forms the MIB (Management Information Base) of the service. In principle, LAN Manager/X SNMP Service supports LAN Manager MIB II and a group of LAN Manager/X alert objects. Five objects are not supported (see the section entitled Objects that are not supported ). This chapter provides a list of the objects supported by LAN Manager/X SNMP Service. U22000-J-Z

24 Information reported Objects supported The objects supported by SNMP Service are listed in the following section, together with their object names in accordance with LAN Manager MIB II. These object names are used by the network management station in conjunction with TRANSVIEW-SNMP, for example. Special object names are required to evaluate the objects listed below using the programs under /opt/snmp/bin, for example. These are contained in the file /usr/lib/snmpd/mibs/lmxext.mib. In the following extract from this file, the object name comversionmaj appears on the righthand side of the line, and is also listed later in this chapter. On the left is the object name that you use for the same object (without inverted commas), e.z. with the program /opt/snmp/bin/getmany. In the center is the object name in point notation. This can also be used for programs under /opt/snmp/bin "LMX_COMVERMAJ" " " comversionmaj Extract from the file lmxext.mib 14 U22000-J-Z

25 Information reported Common Group The following objects apply to both LAN Manager servers and LAN Manager clients. comversionmaj {common 1} The major release version number of the LAN Manager software. comversionmin {common 2} The minor release version number of the LAN Manager software. comtype {common 3} The type of LAN Manager software running on this system, e.z. primary domain controller. comstatstart {common4} The time in seconds since the LAN Manager statistics were last cleared on this node. The comstatstart object applies to statistical objects: com StatNumNetIOs comstatfinetios comstatfcnetios svstatopens svstatdevopens svstatqueuedjobs svstatsopens svstaterrorouts svstatpwerrors svstatpermerrors svstatsyserrors svstatsentbytes svstatrcvdbytes svstatavresponse wkstastatsessstarts wkstastatsessfails wkstastatuses wkstastatusefails wkstastatautorecs U22000-J-Z

26 Information reported Explanations of the objects in this list are contained in the following pages. comstatnumnetios {common 5} The network I/O operations sent from this node. comstatfinetios {common 6} The number of network I/O operations on this node that failed issue. comstatfcnetios {common 7} The number of network I/O operations on this node that failed completion. Server Group The following objects apply to LAN Manager servers. Systems that support this group must also support the common group. svdescription {server 1} A brief description of the server. svsvcnumber {server 2} The number of network services installed on the server. svsvctable {server 3} A list of service entries describing network services installed on the server. svsvcentry {svsvctable 1} The names of the network services installed on the server. svsvcname {svsvcentry 1} The name of a LAN Manager/X network service. scsvcinstalledstate {svsvcentry 2} The installation status of a network. svsvcoperatingstate {svsvcentry 3} The operating status of a network service. svsvccanbeuninstalled {svsvcentry 4} Indicates whether the network service specified by this entry can be deleted. svsvccanbepaused {svsvcentry 5} Indicates whether the network service specified by this entry can be interrupted. 16 U22000-J-Z

27 Information reported svstatopens {server 4} The total number of files that were opened on the server. svstatdevopens {server 5} The total number of communication devices that were opened on this server. svstatqueuedjobs {server 6} The total number of print jobs that were spooled on the server. svstatsopens {server 7} The number of sessions that were started on the server. svstaterrorouts {server 8} The number of sessions that were terminated due to an error on the server. svstatpwerrors {server 9} The number of password violations that occurred on the server. svstatpermerrors {server 10} The number of access-permission violations that occurred on the server. svstatsyserrors {server 11} The number of system errors that occurred on the server. svstatsentbytes {server 12} The number of bytes sent by the server. svstatrcvdbytes {server 13} The number of bytes received by the server. svstatavresponse {server 14} The average time in milliseconds required by the server to process a client I/O request. svsecuritymode {server 15} The type of security running on the server. svusers {server 16} The number of concurrent users that the server can support. svstatreqbufsneeded {server 17} The number of times a server required but could not allocate a request buffer while processing a client request. U22000-J-Z

28 Information reported svstatbigbufsneeded {server 18} The number of times the server required but could not allocate a big buffer while processing a client request. svsessionnumber {server 19} The number of sessions on the server. svsessiontable {server 20} A list of session entries for the current sessions that clients have with the server. svsessionentry {svsessiontable 1} A session that is currently set up on the server. svsesclientname {svsessionentry 1} The name of the remote computer that set up the session. svsesusername {svsessionentry 2} The name of the user who set up the session on a remote computer. svsesnumconns {svsessionentry 3} The number of connections to server resources that are active in the current session. svsesnumopens {svsessionentry 4} The number of files, devices, and pipes that are open in the current session. svsestime {svsessionentry 5} The length of time in seconds since the session began. svsesidletime {svsessionentry 6} The length of time in seconds that the session has been idle. svclienttype {svsessionentry 7} The type of client that set up the session. svsesstate {svsessionentry 8} The status of the current session. (Setting the state of an active session to deleted using the SNMP Set query deletes the client session. The session state cannot be set to active.) svautodisconnects {server 21} The number of sessions that the server terminated as a result of inactivity. 18 U22000-J-Z

29 Information reported svdiscontime {server 22} The time in seconds that the server waits before disconnecting an idle session. svauditlogsize {server 23} The maximum size, in kilobytes, of the server's audit log. svusernumer {server 24} The number of users who have accounts on the server. svusertable {server 25} A table of active user accounts on the server. svuserentry {svusertable 1} A user account on the server. svusername {svuserentry 1} The name of a user account. svsharenumber {server 26} The number of shared resources on the server. svsharetable {server 27} A table of the shared resources on the server. svshareentry {svsharetable 1} A table entry corresponding to a single shared resource on the server. svsharename {svshareentry 1} The name of a shared resource. svsharepath {svshareentry 2} The local name of a shared resource. svsharecomment {svshareentry 3} A comment associated with a shared resource. U22000-J-Z

30 Information reported Objects that are not supported The following objects in the server group are not supported by LAN Manager/X SNMP Service: svprintqtable svprintqentry svprintqnumber svprintqname svprintqnumjobs Client group Workstation group The following objects relate to LAN Manager clients. Each system that supports this group must also support the common group. {workstation 1-5} is not supported by LAN Manager/X. wkstaerrorlogsize {workstation 6} The maximum size of the error log on the workstation in kilobytes. wkstausenumber {workstation 7} The number of currently active applications on the client system. wkstausetable {workstation 8} A table of active accesses made by this workstation. wkstauseentry {wkstausetable 1} An access to a remote network resource. uselocalname {wkstauseentry 1} The name of a local device assigned to a remote resource. useremote {wkstauseentry 2} The name of a remote shared resource to which a local device is assigned. usestatus {wkstauseentry 3} The status of the current connection. 20 U22000-J-Z

31 Information reported Domain Group The following objects relate to both LAN Manager servers and LAN Manager clients. domprimarydomain {domain 1} The name of the primary domain to which the computer belongs. domlogondomain {domain 2} The name of the domain to which the computer is logged on. domotherdomainnumber {domain 3} The number of entries in domotherdomaintable. domotherdomaintable {domain 4} The list of other domains being monitored by the computer. domotherdomainentry {domother DomainTable 1} An entry in the table of other domains. domotherdomainname {domotherdomainentry 1} The name of an additional domain that the computer is monitoring. domservernumber {domain 5} The number of entries in domservertable. domservertable {domain 6} The list of nonhidden servers that are in all of the domains that the computer is monitoring. domserverentry {domservertable 1} An entry in the domain server table. domservername {domserverentry 1} The name a server in one of the domains that the computer is monitoring. domlogonnumber {domain 7} The number of entries in domlogontable. domlogontable {domain 8} The list of domain logons that the computer processed. domlogonentry {domlogontable 1} An entry in the logon table. U22000-J-Z

32 Information reported domlogonuser {domlogonentry 1} The name of a user logged on in this domain. domlogonmachine {domlogonentry 2} The name of a computer to which a user is logged on. Alert objects Some LM/X SNMP Service objects correspond to particular LAN Manager alerts. When one of these alerts is generated, the service uses a group of objects to communicate the presence of the alert and its value. The server can use another set of objects to control the LAN Manager alert mechanism. Objects of this type are divided into three groups: the alert group, the alert data group and the alert management group. The objects in the alert group identify the individual alerts. SNMP Service uses the objects in the alert data group to forward information to the network management. The network management station uses the alert management group to send instructions back to SNMP Service. Alert group The alert objects defined here provide an object ID for identifying a LAN Manager alert type. LAN Manager/X does not yet support all these messages, but they are listed here, as it is expected to support them in the next version. bytesavailalert {alerts 1} LAN Manager checks the disk capacity on all server drives in a time interval specified under svalertschedule. If the available storage on any of the disk drives falls below the level specified in svdiskalertlevel, a LAN Manager disk capacity alert is generated. This alert corresponds to an SNMP bytesavailalert. The data associated with this alert (carried in the SNMP variable-bindings field) is bytesavailentry. After such an alert occurs, subsequent alerts for that drive are disabled until the disk capacity rises above the level specified in svdiskalertlevel (the bytesavailalert is actually the identifier that appears in the SNMP-specific trap field). 22 U22000-J-Z

33 Information reported netioerrorsalert {alerts 2} If the ratio of successful to unsuccessful network I/O requests within the time specified in svalertschedule exceeds the value of netioalertlevel, a LAN Manager I/O errors alert occurs. This alert maps to an SNMP Service netioerrorsalert. The data associated with this alert (carried in an SNMP variablebindings field) is contained in the entries numnetioerrors and networkid. servererrorsalert {alerts 3} If the number of server errors within the time specified in svalertschedule exceeds the value set in sverroralertlevel, a LAN Manager server error alert is generated. The alert then maps to an SNMP Service servererrorsalert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry numservererrors. pwviolationsalert {alerts 4} If the number of password violations within the time specified in svalertschedule exceeds the value of logonalertlevel, LAN Manager alert is generated. This alert maps to an SNMP Service pwviolationsalert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry numpwviolations. accessviolationsalert {alerts 5} When the number of access violations within the time specified in alerttestinterval exceeds the value of accesserrorsupperlimit, a LAN Manager access violation alert is generated. This alert maps to an SNMP Service accessviolationsalert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry numaccessviolations. auditlogfullalert {alerts 6} If the audit log on the server exceeds the size specified in svauditlogsize, a LAN Manager alert is generated to indicate that the audit log is full. The alert maps to an SNMP Service auditlogfullalert. There is no data associated with this alert. auditlog80alert {alerts 7} When the audit log on the server reaches 80 % of the size specified in svauditlogsize, a LAN Manager audit log 80 % full alert is generated. This alert maps to an SNMP Service auditlog80alert. There is no data associated with this alert. U22000-J-Z

34 Information reported upspoweroutwarnalert {alerts 8} If a power failure at the server is detected, a LAN Manager power-out alert is generated. This alert maps to an SNMP Service upspoweroutwarnalert. The server will continue to operate until all backup power sources are exhausted, at which time a upspoweroutshutdownalert is generated. There is no data associated with this alert. upspoweroutshutdownalert {alerts 9} If a power failure at the server is detected, a LAN Manager power out alert is generated. The server continues to operate until all backup power sources are exhausted, at which time a upspoweroutshutdownalert is generated. This alert maps to an SNMP Service upspoweroutshutdownalert. There is no data associated with this alert. upspowerrestoredalert {alerts 10} If a power failure at the server is detected, a LAN Manager power out alert is detected. The server continues to operate until all backup power sources are exhausted, at which time a upspoweroutshutdownalert is generated. If power is restored before the shutdown sequence is initiated, a power restored alert occurs to indicate that no further immediate attention is required. This alert maps to an SNMP Service upspowerrestoredalert. There is no data associated with this alert. logonprimarydcfailurealert {alerts 11} If the primary domain controller for a LAN Manager domain fails, A LAN Manager alert is generated to inform the system administrator. This alert maps to an SNMP Service logonprimarydcfailurealert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry primarydcname. replmasterfailurealert {alerts 12} If the master for a LAN Manager replicated file tree fails, a LAN Manager alert is generated to inform the system administrator. This alert maps to an SNMP Service replmasterfailurealert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry replmastername. diskhotfixalert {alerts 13} If a bad disk sector is detected, and the data can be moved and the sector marked as bad, a LAN Manager alert is generated to inform the system administrator. This alert maps to an SNMP Service diskhotfixalert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry diskdrive. 24 U22000-J-Z

35 Information reported diskharderroralert {alerts 14} If a disk error is detected, a LAN Manager alert is generated to inform the system administrator. This alert maps to an SNMP Service diskharderroralert. The data associated with this alert (carried in an SNMP variable-bindings field) is contained in the entry diskdrive. Alert data groups The objects in the alert data group are only available in three corresponding LAN Manager alerts. Although many of these objects have counterparts in the server alert group, they are not duplicates. primarydcname {pdcfaildata 1} The name of the primary domain controller that apparently failed. primarydcfailed {pdcfaildata 2} The status of the primary domain controller. replmastername {rplfaildata 1} The name of the replication master that apparently failed. replmasterfailed {rplfaildata 2} The status of the replication master running. netioalertlevel {netioerrorsdata 1} The network I/O error ratio (in tenths of a percent) allowed before an administrative alert occurs. numnetioerrors {netioerrorsdata 2} The number of network I/O errors that occurred in the time specified most recently in svalertschedule. This information accompanies the netioerrorsalert. networkid {netioerrorsdata 3} The network ID of the network interface that experienced a network I/O errors alert. This information accompanies the netioerrorsalert. netioerrorstatus {netioerrorsdata 4} The status of the network I/O ratio. This provides a pollable interface to the alert condition. It should be reset to OK by the SNMP manager after polling. servererroralertlevel {servererrorsdata 1} The number of errors that can write to the error log in the time specified in svalertschedule before an administrative alert occurs. U22000-J-Z

36 Information reported numservererrors {servererrorsdata 2} The number of server errors that occurred in the time specified most recently in svalertschedule. This information accompanies the netioerrorsalert. servererrorstatus {servererrorsdata 3} The status of the server error-level. This provides a pollable interface to the alert condition. It should be reset to OK by the SNMP manager after polling. pwlogonalertlevel {pwviolationsdata 1} The number of invalid logon attempts that can be made before an administrative alert is generated. numpwviolations {pwviolationsdata 2} The number of password violations that occurred in the time specified most recently in svalertschedule. This information accompanies a pwviolationsalert. passworderrorstatus {pwviolationsdata 3} The status of the password (logon) error level. This provides a pollable interface to the alert condition. It should be reset to OK by the SNMP manager after polling. accessalertlevel {accessviolationsdata 1} The number of invalid resource-access attempts that can be made before an administrative alert occurs. numaccessviolations {accessviolationsdata 2} The number of access violations that occurred within the most recently specified time in alerttestinterval. This information accompanies the accessviolationsalert. accesserrorstatus {accessviolationsdata 3} The status of the access error level. This provides a pollable interface to the alert condition. It should be reset to OK by the SNMP manager after polling. numdiskdrives {bytesavaildata 1} The number of logical disk drives on the server. This object also represents the number of entries in bytesavailtable. bytesavailtable {bytesavaildata 2} A table showing the number of bytes of disk space available for each of the drives on the server. Each entry corresponds to a particular disk drive. The number of entries in the table is given by numdiskdrives. 26 U22000-J-Z

37 Information reported bytesavailentry {bytesavailtable 1} A table entry showing the number of bytes of disk space available on a particular drive. diskdrive {bytesavailentry 1} The disk drive to which this table entry applies. bytesavail {bytesavailentry 2} The amount of disk space in kilobytes available on the disk drive, indicated by diskdrive. diskalertlevel {bytesavaildata 3} The number of kilobytes of free disk space at which a low disk space administrative alert occurs. diskhotfixes {diskdata 1} The number of LAN Manager disk hotfix alerts received. It enables polling for the alert condition. This number should be reset to zero by the SNMP manager only after correcting the problem. diskharderrors {diskdata 2} The number of LAN Manager hard disk error alerts received. This enables polling for the alert condition. The number should be reset to zero by the SNMP manager only after correcting the problem. auditlogstatus {auditlogdisk 1} The status of the audit log. The status should be reset to OK, unless one of the audit log LAN Manager alerts was received, at which point the status should be changed appropriately. It enables polling for an alert condition. The SNMP manager is responsible for resetting the status after dealing with a problem. powerstatus {powerdata 1} The status of the audit log. The status should be set to OK, unless one of the UPStype LAN Manager alerts was received, at which point the status is changed appropriately. It enables polling for an alert condition. The status is reset to OK at startup and upon receiving upspowerrestoredalert. U22000-J-Z

38 Information reported Alert management group alertnamenumber {alert-mgmt 1} The number of entries in alertnametable. alertnametable {alert-mgmt 2} The list of names to which LAN Manager administrative alerts are sent. alertnameentry {alertnametable 1} An entry in alertnametable. svalertname {alertnameentry 1} The alert name that corresponds to this entry in the alertnametable. alertschedule {alert-mgmt 3} The time in minutes between checks for all alert conditions on the server. 28 U22000-J-Z

39 Status and error messages SNMP Service error messages, which can be issued in conjunction with LAN Manager/X, are recorded on the SINIX system using the error log of the SNMP agent. For further information, see your SINIX system manual. Error numbers within the range 3001 to 3200 have been assigned to SNMP Service DosMak slot = <x> x represents a numerical value. It is the return value of the LAN Manager/X library function DosMak slot. You receive this error message when the system cannot set up the SNMP mailslot \\MAILSLOT\LMXSNMP. It is important to check that no other service is using a mailslot of this name NetLogonEnum = 2455 The netlogon service is not active. Start the Netlogon service Set not supported <x> x represents an internal number for an SNMP object in SNMP Service. A set job is not supported for the specified object. You can ignore this message. 3012(a) NETLOGON, ret = 2184 The netlogon service is not active. Start the netlogon service. 3012(b) REPLICATOR, ret = 2184 The replicator service is not active. Start the replicator service. U22000-J-Z

40

41 Glossary agent Processes SNMP requests and supplies information in a specific format. alert Reports an alarm situation in the LAN Manager/X server, which prompts SNMP Service to automatically send a trap to the network management station. host An end system. Internet A group of connected networks. MIB Management Information Base. A group of objects which can be accessed by a network management protocol. network management station The system whose responsibility it is to manage the network. SNMP Simple Network Management Protocol. A network management protocol which exchanges network management information with a network management station. trap A one way communication from an agent to a station used to signal that an event has occurred. U22000-J-Z

42

43 Abbreviations A API L LAN M MIB S SNMP T TV-SXA W WAN Application Programming Interface Local Area Network Management Information Base Simple Network Management Protocol TRANSVIEW SNMPA Extensible Agent Wide Area Network U22000-J-Z

44

45 Related publications The following pages contain a list of other relevant publications. MS LAN Manager V2.2 User's Guide for MS-DOS User's Guide MS LAN Manager V2.2 User's Guide for MS OS/2 User's Guide MS LAN Manager V2.2 Netware Connectivity Administrator's Guide MS LAN Manager V2.2 Using LAN Manager with Microsoft Windows User's Guide MS LAN Manager V2.2 API Programmer Reference Guide MS LAN Manager V2.2 API Programmer's Reference Update Programmer Reference Guide MS LAN Manager V2.2 Installation and Configuration Guide (MS OS/2/MS-DOS) User's Guide MS LAN Manager V2.2 Troubleshooting and Command Reference System Administrator's Guide U22000-J-Z

46 Related publications MS LAN Manager V2.2 Integrating MS Windows for Workgroups with MS LAN Manager MS LAN Manager V2.2 Administering LAN Manager System Administrator's Guide MS LAN Manager V2.2 SNMP Service System Administrator's Guide MS LAN Manager V2.2 Overview and Installation Product Manual MS LAN Manager V2.2 Supplementary Information about MS-DOS Client User's Guide SINIX V5.41 TRANSVIEW-SNMPA Extensible Agent User's Guide SINIX V5.41 Networks: Supplements for RISC Systems Ordering manuals You can order the specified publications through your local Siemens Nixdorf office. 36 U22000-J-Z

47 Index A H abbreviations 33 hardware requirements 5 alert 1 alert data group 22, 25 I alert group 22 information reported by SNMP Service 2, 13 alert management group 22, 28 installation 2, 5 alert objects 22 installation program 6 installing SNMP Service 2, 5 C installing the software 6 CD-ROM 6 client group 20 L client PCs 11 LAN Manager MIB II 1, 2, 13 common group 15 LAN Manager/X 1 configuration 7 LAN Manager/X API 10 configuration file LAN Manager/X SNMP Extension 7, 8 /usr/lib/snmpd/config 7 LAN Manager/X SNMP Service 10, 13 LAN Manager/X V2.2 6 D LAN Manager/X-API 1 daemon process 1, 7, 8, 9 LM/X SNMP Service objects 22 data model 9 lmx.extd 6, 7 deinstallation 2, 5, 8 domain group 21 M Management Information Base (MIB) 13 E management station 9 error log 29 MIB 13 error number 29 mode of operation 9 F N file network management 9 /usr/lib/snmpd/mibs/lmxext.mib 14 network management services 13 lmxext.mib 14 network management station 1, 9, 11 network monitoring 9 G notational conventions 3 glossary 31 U22000-J-Z

48 Index 2 O SNMP Service 1, 8 object group 13 activation 8 objects 1 deactivation 8 managed 1 software architecture 10 not supported 20 software components 10 sent 13 software requirements 6 supported 2, 13 starting and terminating SNMP Service 8 objects from status and error messages 2, 29 client group 20 summary of contents 2 common group 15 supported objects 14 domain group 21 system architecture 9 server group 16 system architecture and data model 10 workstation group 20 system requirements 2, 5 operating system software 6 operating the SNMP agent 9 T target group 2 P target system 7 pkgadd 6 TRANSVIEW SINIX Extensible Agent 10 pkgrm 8 TRANSVIEW-SNMP 1, 9, 11, 14 preface 1, 2 TRANSVIEW-SNMPA Extensible Agent 1 product description 1 trap 1 program TV-SXA 1, 10 /opt/snmp/bin/getmany 14 TV-SXA V1.0A30 6 R U related publications 35 using SNMP Service 2, 9 S W server group 16 workstation group 20 shared library 1, 10 Simple Network Management Protocol 1 SINIX server 10 SINIX systems 5 SMC 6 SNMP deinstallation 2 installation 2, 5 SNMP agent dynamically extensible 10 extensible 1 SNMP agent extension 1 SNMP console 11 SNMP extension 7, U22000-J-Z

49 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009