GEMU User Guide&

EMU User Guide

A
Previous page... 0 | Contents
4

3.5.2 PARAMTBL

 B Each parameter in the EMU database has an associated record G describing how to format it, the privileges needed to view it and ? how the alert mechanism reacts if it is added, deleted or  modified. 

G Each parameter is associated with a protocol and a table. In some H cases where there are multiple tables within a protocol, the table B names are also in this file and can be modified similarly to  parameter names. 
6

3.5.3 Operations

 The start the program: 
$ PARAMTBL 
" A menu appears with 2 items:  
:

3.5.3.1 Parameters

A You may list, add modify or delete parameters. In all cases A selecting an item takes you through a menu structure of the : protocols and tables to find a particular parameter.  
@

3.5.3.2 PARAMTBL Summary

D This utility is very useful for customising your system at low B levels. With a few keystrokes you can change the way data is H displayed across the system and using the security facility, limit G access to a very fine degree. With power comes responsibility; Be F sure of what you are doing before you do it. As a safety, backup E the file EMU5_DAT:MAPPER.DAT before you make changes. If it all / goes horribly wrong, restore your backup. 
J

3.5.4 MIB compiling and Registration

   G MIBs (Management Information Base) are readable files produced by E the manufacturer of a device that supports SNMP (Simple Network E Management Protocol). At this writing SNMP is supported only in B the IP world. The MIB defines the parameters that the device D supports, how to access them, the format of the parameters and 3 (often) a short explanation of what it means. 

E MIBS must be compiled before they are usable by the system. EMU = provides a compiler in 2 parts for a number of reasons: 

 H The private definitions EMU defines are as follows. Note that they F are defined using the ASN.1 tags reserved for private data types B and therefore will not interfere with any existing or future > definitions contained in a valid implementation of SNMP.  

 L  & % $   !     !              
Table 3-3 EMU ASN.1 Private DataTypes
EMU Symbol Tag Value DataType
SNMP_ASN1E_MACADDR 193 Mac address
SNMP_ASN1E_DISPSTR 194 Printable string
SNMP_ASN1E_TBLTOP 195 Table top ¹
SNMP_ASN1E_TBLENT 196 Table entry¹
SNMP_ASN1E_BRIDID 197 Bridge ID
G Note 1: These 2 types are used internally only. They should never ( be edited into a MIB at any stage. 

G There are a number of enhancements included in this compiler that 0 are not present in industry standard ones: 


B

3.5.4.1 Usage Instructions

A To compile a MIB and make it available for use follow these  instructions:    
    E
  1. Ensure the MIB you want to compile is in EMU5_MIB: directory. MIBs D can normally be obtained by contacting the manufacturer of the E device via either the Web or FTP. EMU supplies many of the more D common MIBs precompiled and registered. To find which MIBs are G already available run PARAMTBL, Select Internet and the resulting B menu will display all registered MIBs. Other MIBs are simply , supplied and are located in EMU5_MIB:. H
  2. Run EMU5_EXE:MIB_COMPILE1.The program will ask for the MIB name. # Enter it. This compile phase:  H
  3. Run EMU5_EXE:MIB_COMPILE2.The program will ask for the MIB name. # Enter it. This compile phase:   H
  4. Run EMU5_EXE:MIB_REGISTER.The program will ask for the MIB name. @ Enter it. The program will determine if the MIB is already H registered and if so, you may replace it with the new definitions. G Otherwise it advises the number assigned to this MIB and includes F all definitions in EMU5_DAT:MAPPER.DAT. The MIB is now available ; for the system to use on any device that supports it. I
  5. After making any required adjustments to the system' usage of the F parameters just registered (see below for a hint), you then tell 3 the system which nodes to use this MIB on by:   G You can test this MIB with another utility that is also useful in & browsing the network: MIBWALKER. 

    I Note that by default all IP addresses are assumed to support MIB-II - F the basic MIB that most SNMP devices support - at least in part. G Internally to the system this is MIB number 1. DO NOT CHANGE THIS G DEFINITION. If this is the only MIB a device supports or the only D MIB you want to act upon a device then no action is necessary. 
    5

    3.5.5 MIBWALKER

     F A MIBWALKER is a generic program that allows you to retrieve and @ display the results of data from a node supporting SNMP. A = number of conditions must be met before this will work:  D To run the MIB walker type 'MIBWALKER' at the DCL prompt. This F system wide symbol is set up at EMU start time. Note that EMU is B not required to be running in order to execute this routine. 
    8 Running the program displays a menu on the screen:  H All the functions are independent. That is you can set the MIB and H switch between addresses or vice versa. It is often a good idea to G run this program after compiling and registering a MIB and noting G which parameters should be adjusted using PARAMTBL. For many MIBS A you may not want all the parameters (by default all will be F collected) or you may want to alert when additions, deletions or B modifications are detected on some parameters. By default no  alerts are generated. 
    <

    3.6 Errors and Omissions

    G This is the beta release of software. Some functions described in C the user guide are not implemented and others may not perform D exactly as expected. It is the purpose of this release to find F these errors, note the usefulness of the system as it stands and D to collect feedback for it's further development. This section E describes the known errors and some possible workarounds. These ' are given in no particular order: 
G A file EMU5_DAT:EMUBUG.DAT contains all known errors and fixes at  release time. 
- Please send any additions to this list to: 
system@ccci4.demon.co.uk 
-

3.7 Hints

I This section is included to impart some uses of the system that may not be  immediately obvious. 
I

3.7.1 Further processing of Reports

 B Reports are always generated as flat files and can be easily H formatted and manipulated using simple DCL procedures. Some useful  things to note:  G EMU does not currently provide an interface capable of extracting G data conditionally. That is there is no way to say "Get all nodes F with names beginning with "TST" and having at least 1 IP address = that does not begin with "171". This is however easily E accomplished by generating a report with all occurrences of the C parameters and writing a simple procedure (about 10 lines) to  apply the logic. 
C

3.7.2 Seeding the IP database

  C There is no direct way to add an address to EMU but in the IP F section this can be done indirectly by 'pinging' the address. If B the node answers, it will be added to the database as the IP G module listens for and receives all ICMP frames (A 'ping' uses an H ICMP echo request and response sequence). It may be useful to keep H a procedure containing ping commands to important IP addresses and G run it at system startup as this will speed up finding further IP  addresses. 
F

3.7.3 Finding a MOP console user

 H If, when using TSM to access a server and the connection fails, it D is often because another system is using the console port. The F message returned does not help to make this obvious. Within EMU, F find the server you are trying to connect to and force an update A using the hidden menu. Wait about 30 seconds and redisplay. D Assuming the update has been successful, (note the last update H time at screen top), the MAC address of the system connected to it C will be displayed as 'Console User'. Find this MAC address to 2 identify the system that 'owns' the console. 

 3


Index  | .Contents