                                                                              EMU User Guide
                                        EMU User Guide
                                        EMU User Guide                B                    This manual describes the installation, use andE                    interpretation of the displays produced by the EMU                     system                                                                                                                '                ________________________ S                October 2000
               October 2000
               October 2000                                   _________________________________________________________________
            Preface
            Preface
            Preface                                                                                               ]                                              _
                                             v                                   _________________________________________________________________
            preface
            preface
            preface           6             This manual is divided into four sections:  *                o  Introduction and history                  o  Installation                  o  User guide  5                o  Limitations and further information                                                                   _                                             ___
                                            vii                        h                _________________________________________________________________
               Contents                  _________________________________________________________________
               Preface                                                         v                   _________________________________________________________________
               preface                                                       vii     w                _________________________________________________________________
               Chapter 1  Introduction   P                1.1    System Overview........................................1-1  P                1.2    A Brief History of EMU.................................1-2  w                _________________________________________________________________
               Chapter 2  Installation       u                _________________________________________________________________
               Chapter 3  User Guide   P                3.1    Starting the system....................................3-1  P                3.2    Stopping the system....................................3-1  P                3.3    User Interface.........................................3-3  P                       3.3.1     Menu system overview.........................3-3  P                         3.3.1.1       Menu Security..........................3-3  P                         3.3.1.2       Getting help...........................3-3  P                       3.3.2     Main menu....................................3-3  P                       3.3.3     Device menu..................................3-4  P                       3.3.4     Device Query menu............................3-4  P                       3.3.5     Device display format........................3-5  P                         3.3.5.1       Parameter Display......................3-5  P                         3.3.5.2       Hidden Menu............................3-6  P                       3.3.6     Reporting menu...............................3-6  P                       3.3.7     Network menu.................................3-8  P                       3.3.8     System menu..................................3-8  P                         3.3.8.1       Monitor Listener.......................3-8  P                         3.3.8.2       Monitor PSRs..........................3-11  P                         3.3.8.3       Monitor Probes........................3-12  P                         3.3.8.4       View Sections.........................3-13  P                         3.3.8.5       Dump_Database.........................3-15  P                         3.3.8.6       Trace.................................3-15  P                         3.3.8.7       Scanner...............................3-15  P                         3.3.8.8       Translate Tables......................3-16  P                3.4    Alert.................................................3-17  c                                               ___
                                              iii                  M                    3.4.1     Main Menu...................................3-17   M                    3.4.2     Alert Format................................3-18   M             3.5    Utilities.............................................3-18   M                    3.5.1     Error Log...................................3-18   M                    3.5.2     PARAMTBL....................................3-19   M                    3.5.3     Operations..................................3-20   M                      3.5.3.1       Parameters............................3-20   M                      3.5.3.2       PARAMTBL Summary......................3-23   M                    3.5.4     MIB compiling and Registration..............3-23   M                      3.5.4.1       Usage Instructions....................3-24   M                    3.5.5     MIBWALKER...................................3-26   M             3.6    Errors and Omissions..................................3-27   M             3.7    Hints.................................................3-29   M                    3.7.1     Further processing of Reports...............3-29   M                    3.7.2     Seeding the IP database.....................3-29   M                    3.7.3     Finding a MOP console user..................3-30   _             _________________________________________________________________
            Index   a             _________________________________________________________________
            Figures   M                    3-1    Menu System Schematic...........................3-2   `             _________________________________________________________________
            Tables  M                    3-1    Report Output...................................3-7   M                    3-2    PSR Status Bits................................3-10   M                    3-3    EMU ASN.1 Private DataTypes....................3-24           ]                                             __
                                            iv                                   _________________________________________________________________
            Chapter  1
            Chapter  1
            Chapter  1  J             Introduction
            Introduction
            Introduction    L                EMU (Ethernet Monitoring Utility) is a system that listens toH                the attached Ethernet and records all addresses appearingG                on the cable. For each address found it also records the K                protocols enabled on that address and for selected protocols G                it can extract information useful for network management I                purposes. It then uses this database to locate other nodes J                in the wide area network and initiate monitoring functions.  ?                Some of the basic features of the system follow:   F                o  The system is fully automatic. The system builds andE                   formats the database without operator assistance or G                   intervention. All monitoring and control subfunctions M                   start and run without intervention and in fact, no operator C                   assistance is ever required for normal operation.   K                o  An alert screen provides the operator with timely reports H                   on new addresses appearing and for selected protocols,H                   changes to configuration parameters, fault reports and&                   performance reports.  M                o  A number of system management utilities are provided. These E                   utilities are all menu driven and self explanatory.   F                o  A versatile reporting command allows the operator toD                   extract selected information to a user defined andH                   formatted file.This may be useful for input into other2                   management tools and/or reports.  M                o  A comprehensive query facility allows operators to view the L                   database contents. Nodes can be selected by many criteria.  L             For details on what data is available and instructions on how to2             extract it see the user guide section.  _             1.1 System Overview
            1.1 System Overview
            1.1 System Overview   I                This is the 5th version of EMU and it's 3rd major rewrite. D                While all the original goals and much of the code wasG                retained, both the architecture and the engineering have J                been greatly expanded to reflect the ongoing changes in the    N                                                              Introduction  1-1                 L                networking world. Most importantly, the principles that drove#                the design remained:   L                1. Full automation. The system is designed to assist the userI                   in monitoring and managing the network, not the reverse I                   as in many current systems. All data in the database is K                   derived from the network; there is no user input possible K                   at this level. This ensures data integrity and eliminates )                   the burden on the user.   M                2. Full integration. The system maintains full cross referenc- M                   ing of all addresses where there is sufficient information. L                   While it is necessary to implement each network as a sepa-L                   rate entity, the user sees only single devices attached toM                   many networks, or many networks with devices attached. This K                   arrangement allows the system to more effectively monitor L                   any single device using the multiple protocols it supportsH                   and allows more accurate and complete reporting of any                   device.   F                3. The system itself should require no maintenance. AllJ                   processes are self configuring, self monitoring and self                   tuning.   L                4. The complexity of the network itself should be hidden. TheK                   system should be fully usable by non-network personnel to M                   extract useful information; The simple question "How is the L                   network performing?" should be answered simply, completely)                   and with qualification.   J                5. The system will acquire and store sensitive information.H                   It is essential that this system incorporates controlsI                   that protect this information, or even the fact of it's 9                   existence from unauthorised disclosure.   t             1.2 A Brief History of EMU
            1.2 A Brief History of EMU
            1.2 A Brief History of EMU  H                EMU started life as a project to automate an early DECnetC                management system provided by Digital. Once this was D                completed, it was expanded out to include some of theG                other Digital tools then available and the result was an H                unwieldy mass of DCL procedures that none the less provedF                the possibility of unburdening the network manager fromH                the task of managing the system that was intended to saveI                time and effort. This set the first principle of design: A H                network management system should tell the network managerL                about the network, not the reverse. One of the early problemsK                found on all systems, including EMU was the need to poll the M                managed devices constantly in order to acquire the information M                necessary to manage it. In extreme cases substantial resources                1-2  Introduction                  K                are used just to manage and often the tool intended to solve J                problems became the problem. In order to alleviate this theL                concept of listening was developed. All major network schemesJ                implement a protocol that is used to maintain the integrityH                of the network. In most cases they pass information aboutM                nodes or networks that can be reached, nodes that have stopped K                responding and in some cases, service names and other useful G                information. By listening to this conversation, a fairly K                complete picture of any network can be gained without adding G                data to the network. This, though much more difficult to J                implement became the second principle: A network managementE                system should be part of the solution, not part of the                 problem. L                The next stage was to recode the logic into programmes and itK                was about that time that the major systems that we use today I                came out (SunNet manager, HP Openview, Netview and DECMCC) I                and the EMU effort would have ended there had any of these J                systems adhered to these (to us!) most basic of principles.J                The time saving achieved by using the system to monitor theJ                network was used up by having to monitor the system itself.E                A further problem was that while all the manufacturers F                claimed multivendor capability the claims in some casesG                were a bit thin and in no case was integration achieved. F                For example DECMCC had a DECnet module, a TSM (TerminalJ                Servers) and an SNMP module all which worked but internallyH                did not intercommunicate. Thus should a node fail all theJ                individual modules reacted independently without regard forL                each other. It was apparent at the time that this failure notL                only complicated the interface and the network manager's taskL                but had this integration been included, the system could thenI                use it's understanding of the various protocols present to M                enhance it's usefulness. For example, should the DECnet module M                report a failure on a node, the first action the manager would K                normally take is to access the node on an alternate protocol K                to determine if the node is down or if DECnet has failed. As J                this is a routine effort, this routine should be built intoJ                the system so that failures can be reported more completelyJ                and in context. This became the third design principle: EMUJ                would take 2 views of the network equally. The network as aM                collection of devices cooperating on 1 or more networks and as M                a protocol in which many devices cooperate. It is a subtle but %                essential distinction.   L                The first 3 versions became experimental and proof of conceptH                and for version 4 an architecture was drawn up to guide aJ                more formal effort at implementing what was learned so far.K                Version 4 was successful in that it ran without major change L                for about 3 years and it even managed some commercial successL                but changes in the networking world began to overtake it. The  N                                                              Introduction  1-3                 L                most basic flaw was that EMU assumed (accurately at the time)L                that each device on the network had exactly 1 LAN address andM                this was used as the key in all databases. As this became less I                and less true and EMU changed to accommodate, it was clear I                that the original design was inadequate. A decision to re-oK                engineer the system became an opportunity to re-architect it I                and remove some of the built in restrictions. Most notable K                among these restrictions was the over adherence to listening J                and not talking on the network. It was clear that listeningI                was a good mechanism to build the initial picture but that_1                polling was needed to complete it.   K                To shorten this narrative to it's essentials, suffice to say K                that in the 3 years since this decision was taken, 18 months J                was spend exclusively on the architecture document with theM                remaining time spend on coding and testing the implementation._L                The current version implements about 60% of the architecture.                                                                               1-4  Introductionn d  s                             _________________________________________________________________
            Chapter  2
            Chapter  2
            Chapter  2  J             Installation
            Installation
            Installation        K                1. Create the root directory for the EMU system. This can be I                   on any disk at any level. The system resides in various M                   directories under this to a level of 3 max so make sure you_C                   do not create the root at a depth greater than 4. (                   $CREATE/DIR disk:[emu]  J                2. The files created in the next section will consume aboutL                   75,000 blocks of disk space. The running system will (veryG                   dependant on the size of your network) will consume a_2                   further 50,000 - 100,000 blocks.  G                3. Set default to this directory and backup the saveset:.,                   $BACKUP/LO Tape:[...]*.*;*  H                4. Edit [.SRC]EMU_LOGICALS.COM and replace the first exe-K                   cutable line with the device and directory you created inpL                   step 1. Remember to include the final '.' in the directory<                   spec as this will become a rooted logical.  +                5. Execute EMU_LOGICALS.COM:s'                   $ @[.SRC]EMU_LOGICALS1  5                6. Ensure you got the expected effect:.                   $SHO LOG EMU* J                   You should see a list of directories under the directory(                   you created in step 1.                    $DIR EMU5_SRC:5                   You should see a list of .MAR filesS  L                7. All being well set default to EMU5_SRC: and execute BUILD:                   @BUILDG                   Answer 'YES' to the question 'Compile all subroutines.                   (YES/n)'  D                8. The system will then build the necessary libraries  G                9. A number of warning messages will be displayed during.J                   compilation. These can be ignored as long as the process*                   continues to completion.  H               10. When finished (Maybe 20 min or so) answer 'YES' to the                   question/                   Compile all programs? (YES/n)   N                                                              Installation  2-1                 M                   This will build the system on the current version of VMS on +                   the current architecture..  G               11. A number of warning messages will be displayed duringrJ                   compilation. These can be ignored as long as the process                   continues.  M               12. All EMU processes run under the system account. Ensure this.K                   account has the required quotas. A copy of one that works.2                   appears at the end of this list.  =               13. Ensure LAT, DECnet and UCX are all started.   4               14. Ensure LATCP can see all services:4                   $MCR LATCP SET NODE/USER=ENA=0-255K                   The LAT processor will see all LAT devices on the net but M                   updates from the local (VMS created) database. If the above.L                   is not done, EMU will likely find LAT nodes that VMS knows                    nothing about.  ,               15. Finally, start the system:$                   @EMU_SRC:START_EMUK                   You may clear the databases and start fresh each time you4J                   start the system by answering 'y' and confirming this toM                   the prompts. For excessive safety, on the first startup, do                    this..J                   You may clear the log files on each startup. Generally aL                   good idea (after review). There is no mechanism to controlK                   the size of these files automatically and while generally3@                   well behaved can, on occasion become churlish.  G             Following is a snapshot for a system account that EMU works I             with. The most important quota is BYTLM. The listener enables H             promiscuous mode and saves as many frames as possible in theK             driver. This requires a LOT of BYTLM. There are undoutably more.,             optimum settings for the others.5                Username: SYSTEM Owner: SYSTEM MANAGER 4                Account: SYSTEM UIC: [1,4] ([SYSTEM]))                CLI: DCL Tables: DCLTABLES7,                Default: SYS$SYSROOT:[SYSMGR]                LGICMD:                Flags: DefCLI0                Primary days: Mon Tue Wed Thu Fri&                Secondary days: Sat Sun%                No access restrictions >                Expiration: (none) Pwdminimum: 8 Login Fails: 1=                Pwdlifetime: 30 00:00 Pwdchange: (pre-expired)_M                Last Login: 16-AUG-2000 13:46 (interactive), 26-OCT-2000 11:00                  (non-interactive)2                Maxjobs: 0 Fillm: 250 Bytlm: 4000003                Maxacctjobs: 0 Shrfillm: 0 Pbytlm: 0_4                Maxdetach: 0 BIOlm: 150 JTquota: 4096               2-2  Installation. .  .            .                Prclm: 0 DIOlm: 150 WSdef: 2048-                Prio: 4 ASTlm: 250 WSquo: 6400 3                Queprio: 0 TQElm: 20 WSextent: 32000.6                CPU: (none) Enqlm: 2000 Pgflquo: 150000%                Authorized Privileges: 7                ACNT ALLSPOOL ALTPRI AUDIT BUGCHK BYPASS =                CMEXEC CMKRNL DIAGNOSE DOWNGRADE EXQUOTA GROUP_<                GRPNAM GRPPRV IMPERSONATE IMPORT LOG_IO MOUNT6                NETMBX OPER PFNMAP PHY_IO PRMCEB PRMGBL:                PRMMBX PSWAPM READALL SECURITY SETPRV SHARE7                SHMEM SYSGBL SYSLCK SYSNAM SYSPRV TMPMBX #                UPGRADE VOLPRO WORLDa"                Default Privileges:7                ACNT ALLSPOOL ALTPRI AUDIT BUGCHK BYPASSs=                CMEXEC CMKRNL DIAGNOSE DOWNGRADE EXQUOTA GROUPs<                GRPNAM GRPPRV IMPERSONATE IMPORT LOG_IO MOUNT6                NETMBX OPER PFNMAP PHY_IO PRMCEB PRMGBL:                PRMMBX PSWAPM READALL SECURITY SETPRV SHARE7                SHMEM SYSGBL SYSLCK SYSNAM SYSPRV TMPMBXn#                UPGRADE VOLPRO WORLDS  G                Note: EMU enables promiscuous mode on the local EthernetyM                device and attempts to read every packet on the cable. In mostaM                environments this causes very high I/O on the system and ofteniH                results in significant impact on the node. It is stronglyK                advised to run it on a standalone, dedicated VMS system. AnyrG                valid VMS system with a working copy of UCX is adequate.d                                              N                                                              Installation  2-3    n                             _________________________________________________________________
            Chapter  3
            Chapter  3
            Chapter  3  D             User Guide
            User Guide
            User Guide    F             This chapter describes in detail how to start and stop theH             system, monitor it's progress and the various utilities used#             to extract information.Tk             3.1 Starting the system
            3.1 Starting the system
            3.1 Starting the systemo  2             To start the system issue the command:#                $@EMU5_SRC:START_EMUcM                The procedure provides an option to restore all saved files orwL                clear them and build a new database. The default is to reload                all saved files. M                EMU will then start all the processes required and after a fewO0                seconds it will exit back to DCL.k             3.2 Stopping the system
            3.2 Stopping the system
            3.2 Stopping the system   "                To stop the system:#                $ @EMU5_SRC:STOP_EMU J                This deletes the EMU_CONTROL process which in turn triggersH                all other EMU process to shutdown. All database files and<                sections are saved to disk files in EMU5_DAT:                                                N                                                                User Guide  3-1 d  g                            Figure 3-1:  Menu System Schematic
               Figure 3-1:  Menu System Schematic
               Figure 3-1:  Menu System Schematica                                                                                                               3-2  User Guide  u               \             3.3 User Interface
            3.3 User Interface
            3.3 User Interface  E             The user interface is entirely menu driven - there are no H             commands to learn. The menus provide comprehensive access toM             all EMU facilities and data. In addition to the menus there are a M             number of utilities (described in the Utilities section) that areaJ             run as separate procedures. Each menu item is described in the             following sections.o  t             3.3.1 Menu system overview
            3.3.1 Menu system overview
            3.3.1 Menu system overview  J                To start the user interface type EMU at the DCL prompt. The&                main menu then appears.  e             3.3.1.1 Menu Security
            3.3.1.1 Menu Security
            3.3.1.1 Menu Securityr  J                The menu items are controlled by the security system - thatK                is if appropriate privileges are not owned by the user, someeM                items do not appear. Note that the default privileges are usedfK                - the privileges the user has currently enabled are ignored,iH                the system only checks the privileges owned. The requiredH                privileges are detailed in the menu description sections.  b             3.3.1.2 Getting help
            3.3.1.2 Getting help
            3.3.1.2 Getting help  K                The system supplies a comprehensive help facility and can be J                accessed by pressing the help key (on a Digital Keyboard orL                the equivalent on others) in any menu. Simply select the menu?                item help is required on and press the help key.o  S             3.3.2 Main menu
            3.3.2 Main menu
            3.3.2 Main menua  I                The network can be seen as a collection of devices on 1 or M                more networks or a network and it's collection of devices. EMU #                supports both views.tM                There are 3 items in the main menu. In all cases, selecting anw;                item from this menu displays a further menu.t  E                1. Device. This items allows querying and reporting oneK                   devices. There are no privileges required to display thisl                   item.r  F                2. Network. This items allows querying and reporting onL                   networks. There are no privileges required to display this4                   item. This is not yet implemented.  G                3. System. This item allows access to the system manage-xL                   ment/monitoring facilities. If the user does not have OPERI                   privilege, this item is not displayed and access to thed2                   underlying facilities is barred.  N                                                                User Guide  3-3 e  A            Y             3.3.3 Device menu
            3.3.3 Device menu
            3.3.3 Device menu   H                There are no special privileges need to access these menu:                items. From this menu, the user may select:  L                1. Query. Allows access to the live database. Using a furtherF                   menu the user selects individual devices to display.  H                2. Report. Allows access to the reporting subsystem. HereJ                   the user may create, define and view device reports. See-                   reporting menu for details.   k             3.3.4 Device Query menu
            3.3.4 Device Query menu
            3.3.4 Device Query menuh  L                In this menu, the user selects devices to display. RegardlessJ                of how the device is found, the display is always the same:E                all data for the device become accessible. For each ofHH                the following items, selection issues a prompt asking forI                appropriate input. Standard VMS Wildcards are allowed. The F                appropriate database is searched for matches. Any foundJ                are displayed one at a time until no more match. Within theK                display, menus allowing control of direction and content aretH                presented. There are no special privileges need to access                 these menu items.  K                1. Name. A nodename or any part of a nodename with Wildcards L                   is input. A nodename may be up to 400 printable characters                   in length.  J                2. LAN. Either an address or protocol type can be input. InE                   the case of an address the user must input in form:n#                   xx-xx-xx-xx-xx-xx D                   where x is either a hexadecimal digit or wildcard.A                   The protocol type query is not yet implemented.a  B                3. IP. An IP address, or any part is input in form:!                   ddd.ddd.ddd.dddu=                   where ddd is a decimal digit in range 0-255   H                4. DECnet. A DECnet address or any part is input in form:                   aa.nnnnlJ                   where aa is a decimal number in range 1-63 and nnnn is a1                   decimal number in range 1-1023.                            3-4  User Guides w  r            w             3.3.5 Device display format
            3.3.5 Device display format
            3.3.5 Device display formatt  M                Each device found (if any) are displayed in common format. The ,                screen is split into 3 parts:  I                1. Top section displays the device. If a name is known the A                   name is displayed, if not, the address is used.aK                   The class and device are also displayed. These fields are H                   not yet implemented but in the released version, theseK                   will correspond to a user settable field showing relativerJ                   importance and generic device type such as bridge, host,                   router etc.lM                   Once a particular protocol is selected, the time the devicemL                   was last heard and the time the device was last updated on6                   the selected protocol are displayed.  I                2. Control menu. 2 fixed items are followed by the list of K                   supported protocols this device runs. The two fixed itemss                   are:K                   Next. Display the next device matching the search string.tK                   Previous. Display the previous device matching the searchn                   string.aL                   Protocol list. For each EMU supported protocol this deviceH                   runs, a menu item is displayed. Selecting any protocolJ                   item displays either the parameters for this protocol orK                   a further menu of the tables in this protocol. The number K                   of parameters in some protocols can be quite large so EMUiK                   defines each parameter as belonging to a table. SelectingsG                   any table displays the parameters associated with it.b  J                3. Main Section. The parameters are formatted and displayedK                   here in standard format: Parameter name : Parameter value   q             3.3.5.1 Parameter Display
            3.3.5.1 Parameter Display
            3.3.5.1 Parameter Displayu  =                The display of any parameter is controlled by:n  I                o  Security. Each parameter has associated with it the VMSeJ                   privilege required to view it. If the user does not haveI                   the requires privilege, the parameter is not displayed.   K                o  Level. Each parameter is defined as a 'level of interest'_L                   in range 0-5 (0 being most interesting and 5 being least).H                   A hidden menu (described in next section) controls theL                   level of reporting. Any parameter below the current 'level0                   of interest' is not displayed.  J                o  Parameter name and formatting are predefined but you areL                   free to change this with the PARAMTBL utility. (which see)  N                                                                User Guide  3-5                 _             3.3.5.2 Hidden Menu
            3.3.5.2 Hidden Menu
            3.3.5.2 Hidden Menur  M                While in the query display, if you press CTRL / a menu appears)                allowing:  J                o  Logging. A prompt for file name appears at the bottom ofK                   the screen and all further data to screen is also written.K                   to this file. This is a 'flip-flop' selection; If loggingsK                   is on and this is selected it is turned off, if it is offtL                   and then selected, it is turned on. Note that each time it6                   is turned on, a new file is created.  M                o  Report level. You can set the 'level of interest' described L                   above here. Selecting the 2nd item displays a further menu(                   used to set the level:  M                   1. Summary. The lowest level. Only those parameters defined N                      as 'most interesting' are displayed. Generally this would6                      include only names and addresses.  G                   2. Brief. Names, addresses and those considered major .                      parameters are displayed.  D                   3. Normal. All but the most obscure parameters are                      displayed.h  M                   4. Full. All parameter that can be formatted are displayed.s  G                   5. Verbose. All parameters are displayed. If there isoG                      no formatting available for a parameter, a default N                      translation is applied. Note that the level any parameterL                      is defined in can be changed with the PARAMTBL utility.  I                o  Update. Normally whenever a node is updated, it is then K                   set to update again in 3 days. Once a display is started, G                   selecting this forces this node to be updated on this K                   protocol on the next cycle. In the case of LAN (MOP, LAT, I                   SCS, IPX) protocols this will most likely happen within L                   10 - 15 seconds. In the case of WAN protocols (IP, DECnet,@                   OSI) this may take as long as 30 - 45 minutes.  b             3.3.6 Reporting menu
            3.3.6 Reporting menu
            3.3.6 Reporting menu  G                The reporting menu allows the user to define, create anduK                display reports. Reports are generated from report parameterAI                files created by the user and formatted as a 'spreadsheet' K                where all matching parameters are in columns. For example: A L                parameter file specifying IP address and DECnet address finds3                3 nodes and would format as follows:                3-6  User Guides e                               ______________________________________________________________
               Table 3-1:  Report Output
               Table 3-1:  Report Output
               Table 3-1:  Report Output  5                IP
               IP
               IP 8                Ad-
               Ad-
               Ad-                ______________________________________________________________
               dress  Decnet Address
               dress  Decnet Address
               dress  Decnet Address                  1.2.3.450.1[1]b                  1.2.3.5                  1.2.3.6                  1.4.5.650.3[2]                   1.4.5.750.2[3]   d                ______________________________________________________________
               1.4.5.8  E                1. This node 1 has 3 IP addresses and 1 Decnet addressi  E                2. This node 2 has 1 IP addresses and 1 Decnet addressn  E                3. This node 3 has 2 IP addresses and 1 Decnet address   ;             The items in the reporting menu are as follows:   H                1. Display Reports. Displays a menu of previously createdH                   reports. Selecting any item causes the selected reportF                   to be displayed in the TPU editor. The report may beJ                   edited using all standard TPU features. A new version isL                   always created. Upon exit from TPU, the user may elect anyJ                   combination of keeping or discarding the new version and2                   purging or not all old versions.                   Note: The call to TPU always creates a new file unless the
                  Note: The call to TPU always creates a new file unless the
                  Note: The call to TPU always creates a new file unless the                   user explicitly 'quits' out of the editor. For this reason
                  user explicitly 'quits' out of the editor. For this reason
                  user explicitly 'quits' out of the editor. For this reason                   the system assumes a new version is always created. If
                  the system assumes a new version is always created. If
                  the system assumes a new version is always created. If                   you quit out of an editing session be very careful how you
                  you quit out of an editing session be very careful how you
                  you quit out of an editing session be very careful how you                   answer the delete and purge questions!
                  answer the delete and purge questions!
                  answer the delete and purge questions!  L                2. Load Saved List. Displays a menu of all previously createdL                   report parameter files. These files define the contents of                   any report.V  H                3. Create new list. Created report parameter files. MenusI                   of EMU supported protocols, their tables and parameterseK                   are displayed. Selecting a parameter adds it to the list.eK                   Selecting a parameter already in the list removes it from                    the list.     N                                                                User Guide  3-7 S  s            K                4. Save Current. Saves the currently loaded report parameter L                   list to a file. The user is asked for a report name. EnterJ                   ONLY a file name (no type or extension). These files can!                   then be LOADed.   H                5. Create Report. A report is created using the currentlyH                   LOADed parameter file. A parameter file must have been/                   previously created or loaded.n    \             3.3.7 Network menu
            3.3.7 Network menu
            3.3.7 Network menu  G                Using the items in this menu, an overview of the various.K                networks can be obtained. This section is under constructionsH                (hard hats must be worn at all times and is closed to the                public).u  Y             3.3.8 System menu
            3.3.8 System menu
            3.3.8 System menue  I                This section is used to monitor and debug the system. Each J                menu item in the system menu shows a specific aspect of theI                system. Most of these tools will not be useful to a normaleL                user but may be helpful to the system manager should problemsJ                occur on your system. Many of the tools presented here wereE                used as development tools and remain useful in quicklyrI                isolating problems either within EMU or demonstrating thats%                problems are external.   n             3.3.8.1 Monitor Listener
            3.3.8.1 Monitor Listener
            3.3.8.1 Monitor Listener  D                The main Listener and PSR interface is presented as aJ                continuously updated real-time monitor. The display appears                as follows:                                               3-8  User Guide                  H                 CCCI Ltd 1993          Ethernet Monitor Listener Display                  System:2                   Event flags  = 80000000 01FE0000I                   Queued  Lowest    Error      Cmplt  IOSB Err  ProcessedeG                   28       0        72694   15391978    0         50480TU                  Frame errors:          Mcast Src     Zero Src   Zero Dest   Zero PTYdS                                          0               0          0          9350tU                   Name      Status      Limit      Sent      Disc   In Proc      HigheU                  RECORD   00000000         20         0         0         0         0iU                  ETHNET   00000001         16   4716223    219803         1        16 U                  IP       00000005         15   1224266     24677         5        15mU                  MOP      00000005         11     60083         0         0         8cU                  DECNET   00000005         12    726942      1462         1        12dU                  LAT      00000005         10    156502         0         0         6eU                  ARP      00000007         10   1224261         5         0        10gU                  LAVC     00000005         13    409631         0         1         7dU                  IPX      00000005         11    844851      4964         0        11 U                  BRIDGE   00000005          4    156261         0         0         3eU                  OSI      00000005          8    678413       187         0         8   5                The display is interpreted as follows:a  L                o  Event flags are flags used throughout the system to signalL                   events. Normal operation has only the top flag permanentlyI                   set and on occasion you will notice some flags changing L                   rapidly. If any flag other than the highest on remains setJ                   (not 0) it usually indicates the process associated withL                   this flag is no longer responding. Report this to software                   support.  M                o  Queued is the number of buffers queued to Ethernet. As longaJ                   as this remains above 0 all is well. If it reaches 0 andK                   remains there there is a serious problem with the system.e2                   Report this to software support.  H                o  Lowest is the lowest number of buffers queued at any 1I                   time. This will normally start at the number queued andrB                   progress towards 0 as the system uses resources.  L                o  Error. The number of Ethernet read errors. This should al-L                   ways be a very low number (less than .001% of completions.L                   Note there is a bugette here - the count regularly goes upI                   for unknown reasons and there is no other known impact.s  H                o  Cmplt - Completions. The number of Ethernet reads. TheI                   Listener is reading every frame on the Ethernet and the L                   display updates 1 per second so the rate this number risesH                   at is the number of frames per second currently on the-                   segment EMU is attached to.   N                                                                User Guide  3-9    u            K                o  IOSB error. The number of times the Listener successfullysJ                   received a frame but the frame was in error. This shouldK                   always be 0. If this number rises there is either a faultiL                   on the local LAN (most likely) or serious EMU system faultL                   (Less likely) or an operating system fault (Least likely).  F                o  Processed. The listener discards most frames read asK                   being not useful to EMU purposes. This includes any frameeJ                   containing user data. The remaining frames are processedG                   for network management information. This count is thenG                   number of frames processed and this number, expressed H                   as a ratio of Completions gives a rough picture of the1                   efficiency of the attached LAN.   H                o  Frame errors. Each Ethernet frame is validated and anyM                   errors found are recorded here. They are: Multicast source.eG                   A frame was received with a multicast source address.eG                   This is not allowed by Ethernet rules and can trigger I                   a broadcast storm. It cannot be determined who sent the G                   frame. Zero Source. A frame was received with the top F                   3 bytes of the address set to 0. This is not a validM                   Ethernet address. Zero Destination. Same as in Zero Source.rI                   Zero PTY. The protocol type in the frame was 0. This isdL                   meaningless as this type is not defined. No station actingL                   in accordance with Ethernet rules will receive this frame.  L                o  The remainder of the display shows the processors that areM                   active. Each processor has it's own set of counters and area)                   interpreted as follows:   I                   o  Name. Is simply the name this processor is known by.U  I                   o  Status. A bit pattern showing the current processing =                      status. Only the bottom 3 bits are used:l                  ______________________________________________________________
               Table 3-2:  PSR Status Bits
               Table 3-2:  PSR Status Bits
               Table 3-2:  PSR Status Bits                  ______________________________________________________________
               Bit    Meaning When Set
               Bit    Meaning When Set
               Bit    Meaning When Set  2                0      Processor is able to receive  &                1      Type Checked [1]  s                ______________________________________________________________
               2      All Traffic [2]                Notes:  M                   1. Type checked. This processor receives frames only of thea-                      type specified in PSRTBLe               3-10  User Guide d  o            H                   2. All traffic. Most processors receive only multicastN                      traffic. If this bit it is set it receives all traffic on(                      that protocol type.               See warnings in PSRTBL before changing any of these bits.
            See warnings in PSRTBL before changing any of these bits.
            See warnings in PSRTBL before changing any of these bits.r    b             3.3.8.2 Monitor PSRs
            3.3.8.2 Monitor PSRs
            3.3.8.2 Monitor PSRs  K                PSRs are the Protocol Specific Routines. There is 1 for eachoF                protocol EMU processes. The display appears as follows:  C                 CCCI Ltd 1993          Ethernet Monitor PSR DisplayqW                   Name     Rec         Ret    Fmterr  Comm  Err   NoIPC  Alt  Rlt  NameeU                  OSI      681229      681229      0      0     0     0     0    0   0 U                  LAVC     411312      411312      0      0     0     0     0    0   0 U                  LAT      157144      157144      0      0     1     0     0    3   0aU                  MOP       60324       60324    106      0     0     0     0 4470   0aU                  IP      1229358     1229358      0      0     0     0     0   19   0oU                  IPX      849122      849122  44444      0     0     0     0    0   0 U                  ETHNET  4737078     4737078      0      0     0     0     0    7   0eU                  RECORD        0           0      0      0     0     0     0    0   0dU                  BRIDGE   156907      156907      0      0     0     0     0    0   0d  L                The display has been compressed in this example to fit on the2                page. It is interpreted as follows:  K                o  Name. The Name (Usually the protocol name) the routine isp                   known by.a  E                o  Rec. The number of frames the PSR received from the                    Listener.P  I                o  Ret. The Number of frames processed and returned to the ?                   Listener. This should always be equal to Rec.   F                o  Fmterr. Format error. A fame with unexpected format.K                   Usually this is cause by a device sending a faulty frame.aG                   If the number rises dramatically, it can indicate thepK                   processor is faulty. Report this to software support. NotdM                   in the above display the high number being reported by IPX.h-                   This is being investigated.   H                o  Comm. The number of command buffers received. InternalE                   processes can send commands to PSRs to affect their                    processing.   F                o  Err. The number of error messages this processor hasI                   written to the error log. If this number rises quickly, L                   a review the error log should indicate the problem. If theK                   problem cannot be understood or rectified, please contacti#                   software support.n  N                                                               User Guide  3-11 e  n            M                o  NoIPC. No Inter Process Communication Buffer. EMU processes F                   communicate using a common buffer pool. If a processH                   requests a buffer and none are available this event isK                   counted. A small (Less than 5 per hr) number is expected.sL                   These counts are used in the auto tuning process and oftenL                   a restart of EMU will retune the system and alleviate this                   problem.  F                o  Alt. The number of Alerts this processor has raised.  F                o  Rlt. The number of relater frames this processor hasK                   sent. Relater frames carry information that one processor M                   determines is 'of interest' to another. This information is ,                   relayed in Relater frames.  '                o  Name. No longer used.h  h             3.3.8.3 Monitor Probes
            3.3.8.3 Monitor Probes
            3.3.8.3 Monitor Probes  M                Probes are the processes that interrogate cooperating nodes on,L                the network for configuration and performance data. CurrentlyJ                EMU supports SNMP for IP addresses, CMIP for OSI addresses,M                NICE for DECnet, MOP, LAT and Ethernet protocols. This displaydL                charts the amount of data EMU is adding to the network and is$                displayed as follows:S                     Probe                 Sent     Receive       Error    NoResposet  S                  SNMP                     10424        9215         472        1250iS                  CMIP                      1364        2301         742          82lS                  NICE                        95         539           0          20_S                  MOP                        139         139           0           0 S                  LAT                       1713        1713           0           0pK             Note the LAT processor reads only from the local node - it doesAI             not send any data across the network. The same is true of the_             Ethernet probe._  5                The display is interpreted as follows:   7                o  Name. The name the probe is known by.A  ?                o  Sent. The number of queries sent by the probe   @                o  Receive. The number of good responses received  M                o  Error. The number of responses received indicating an error_I                   in either the request or the response. Each response ofd7                   this type is logged in the error log.   H                o  NoResponse. The number of frames sent that received no                   response.d               3-12  User Guide                 e             3.3.8.4 View Sections
            3.3.8.4 View Sections
            3.3.8.4 View Sectionso  L                EMU builds a number of internal databases in memory sections.K                Selecting this item displays a further menu of sections thateL                can be viewed directly. For most sections there is a standardC                format displayed. The display is split into 3 parts:e  M                o  Top level. Gives information about the section being vieweddH                   Entries: The number of physical entries in the section1                   Recsize: The size of each entrysM                   Max Entries: The maximum number of entries the section willhJ                   currently contain. If this number of entries is reached,G                   the controlling process gains exclusive access to the H                   section, writes it out to a file, deletes the section,I                   creates a larger section and restores the data. It thent0                   releases access to the system.  K                o  PID: This is the internal identifier EMU uses to target aeJ                   particular process, and therefore it's section. This PIDE                   relates to the Event Flags in the Listener display.s  3                o  Middle Level: Not currently used.i  D                o  Main Level. Each PSR section displays the standardH                   header and then the PSR specific data. The common part%                   is documented here.!                   o  Common Header:  ;                   o  Flags: This is the PID of this processu  L                   o  Boxid:This is a number generated internally and used toM                      relate the various protocols found on the network to theeN                      various devices detected. Throughout this system a BOX isM                      synonymous with a single physical device. Thus a router,oK                      PC or VAX are all BOXes with a single BOXID associatedi  N                   o  Ptypbits. A bit pattern indicating the protocols detectedK                      on this device. A bit set in this field corresponds to M                      the PID of a protocol this device is running. That is to M                      say, if bit 12 is sent in this field, EMU has determinedaK                      that protocol 12 (Ethernet) is running on this device..  I                   o  Control. A bit pattern indicating the status of thissC                      record. Currently 3 bits are used to indicate:R  M                     o  Record is deleted. This area may be overwritten at anyr                        time.  K                     o  Update. This record has been changed since list time.M                        the corresponding probe updated the record. It will be 1                        updated in the next cycle.r  N                                                               User Guide  3-13 c  t            L                     o  NoPoll. Do not poll this device on this protocol. MayL                        be set by the user or the system. The system will setJ                        this bit if the device responds with any indication5                        that it does not allow logins.n  G                   o  Last. The last time EMU detected a frame from thissH                      address on this protocol. If the last time recordedJ                      exceeds the Ageout for this protocol, the record will                       be deleted.  G                   o  FST. The first time EMU detected a frame from thismE                      address on this protocol. Helpful when trying to N                      determine events around a particular incident. This event'                      is always alerted.3  J                   o  ALT. Time last alert was sent for this device on this                      protocol.  6                   o  Status. Not currently implemented  M                   o  Accesses. The number of times this record was looked up. N                      The search is always done sequentially and during sectionM                      build, the records are sorted such that records accessed N                      most often are nearer the top of the section. This speedsK                      up searching dramatically. Note: Not really true. This8K                      was (and remains) the intention but in fact, it is note!                      implemented.S  L                   o  Len. The length of the main lookup key in this section.L                      The location of the key is constant in all sections andL                      combined with this field, allows a single common search(                      routine to operate.  K                   o  HowSet. How this device was found and the process that J                      caused it to be created. Changed as a result of otherK                      problems. This field is now always set to the 'parent' K                      protocol regardless of who actually set it. Makes it a !                      bit useless.   M                   o  Current Readers. The number of process currently reading M                      this record. Combined with Current Writers, these fields J                      are used to organise access to the record so that anyK                      retrieval is valid. That is a reader will not retrieve L                      a half written record and writers do not overwrite each"                      other's data.  N                   o  Updt. Time this device was last updated on this protocol.  M                   o  Lpol. Last time this device was polled on this protocol.l  N                   o  Polls. The number of times this device was polled on thisL                      protocol. This field along with Responses allows EMU toM                      determine if it should continue polling a device that is )                      unlikely to respond.h               3-14  User Guide                 G                   o  Interval. The number of seconds (Default = 3 days) $                      between updates  J                   o  Support. A bit pattern showing the various managementI                      functions this device supports on this protocol. The 9                      pattern is specific to the protocol.     e             3.3.8.5 Dump_Database
            3.3.8.5 Dump_Database
            3.3.8.5 Dump_Databaseo  L                The database can be formatted and dumped. Selecting this itemJ                displays a prompt for file name. If a file name is entered,M                the dump is sent to both screen and file. If the prompt is noteJ                answered, the dump is to screen only. Be careful here - theK                database is usually quite long - 15,000+ lines will normallye                be printed.  M             3.3.8.6 Trace
            3.3.8.6 Trace
            3.3.8.6 Tracen  K                This is a debugging tool used to see in real time the frames J                passed between EMU processes. Currently 2 processes support"                the trace facility:  K                o  EBUFFS. These are the buffers passed from the listener tobJ                   the PSRs. The trace shows these buffers as they are sendK                   from the listener to the PSRs and the PSRs returning them "                   to the listener.  H                o  Relater. These buffers are passed from the PSRs to theI                   relater and are the controlling inputs to that process.fJ                   Should any node display incorrect relationships (like anK                   address that it does not have or the reverse), this tracel.                   can be used to find out why.  S             3.3.8.7 Scanner
            3.3.8.7 Scanner
            3.3.8.7 Scanner   D                The scanner process scans the database for parametersH                collected from the network via polling that should appearK                in the PSR level databases. A small database detailing which L                parameters to search for and where to send them is controlledM                by this interface. If you value your life, do not change these M                fields. Incorrect entries in this database cause immediate andi6                irreparable brain damage to the system.              N                                                               User Guide  3-15 e  h            n             3.3.8.8 Translate Tables
            3.3.8.8 Translate Tables
            3.3.8.8 Translate Tables  E                The network is parameter driven and the value of thoserD                parameters is what EMU collects, analyses, stores andI                displays. Most parameters are not in any form suitable for J                human consumption and therefore must be translated. Most ofL                the parameters in this area are not documented in any centralM                location nor is there any definitive list. The tables providednL                are the best known to the developers but cannot be guaranteedJ                to be either complete or correct. In this subsystem you canF                edit the source tables and compile them into the systemH                for use by the parameter translation mechanism. There are+                currently 4 tables provided:   I                o  Netware SAP. This is a code showing the service(es) any M                   Netware node broadcasts and the correct translation of this M                   is very useful as it describes in a few words the major use_!                   of this device._  H                o  MOP Device. Any node supporting Digital's MOP protocolJ                   broadcasts a frame describing itself on a regular basis.H                   One of the parameters is it's device type - again veryJ                   useful in describing in a word or two what this node is.  L                o  Ethernet type. Any protocol on the Ethernet must send it'sH                   frames in Ethernet format. In the Ethernet format is aI                   field describing the protocol the application is using. K                   One of the simple tricks EMU pulls is simply reading that L                   field for each frame and therefore is able to list all theL                   protocols any device runs. This table translates the codes*                   into meaningful words. +  F                o  Ethernet UOI (Universal Organisation Identifier). InK                   simpler times, this field was known as the manufacturer's I                   code. Even more simply: The top 3 bytes of any hardware L                   address is a code showing the manufacturer of the EthernetJ                   device in the box. This table controls that translation.                      ____________________J             + Ethernet types are actually in 2 formats:  Type II (a 2 byteM               type field) or IEEE (a 2 byte SSAP/DSAP).If DSAP/SSAP is 'AAAA'cK               then it is extended Ethernet(a 3rd type!)  and a 5 byte field I               is used.  The 5 byte field is in fact the 2 byte type codedtH               with the UOI prepended.  If you find this confusing do notM               panic - it is not a test of networking skills so much as a testL                 of patience.               3-16  User Guide                 A             3.4 Alert
            3.4 Alert
            3.4 Alert   H                For a number of reasons (mostly performance and laziness)K                the user interface to the ALERT subsystem is not implemented0H                under the main EMU menu system but is carried separately.H                This interface allows you to monitor real time alerts andH                browse through previous alerts conveniently. To start the                alert interface:                 $ ALERT:                This brings up a screen with a 3 item menu.  S             3.4.1 Main Menu
            3.4.1 Main Menu
            3.4.1 Main Menus  ?                The main menu in the alert system allows you to:r  J                1. Monitor. Selecting this item clears the screen and waitsH                   for alerts from the system. As each alert is received,K                   it is formatted and displayed here. To return to the mainP%                   menu, press Ctrl Z.f  J                2. Review. Selecting this item allows you to browse throughH                   the alerts previously generated and logged. All alertsJ                   are logged to the file EMU5_DAT:ALERT.DAT. It is advisedK                   to check the size of this file on occasion as there is nolK                   mechanism to control it's size and on an active (some saytJ                   flaky) network many alerts can be generated over a shortC                   time. Selecting this item brings up another menu:g  L                   o  Since. Allows you to set the time from which previouslyI                      logged alerts are re-displayed. The format is in VMS I                      standard absolute time (DD-MMM-YYYY HH:MM:SS.CC) andrL                      any part missing from the input will default to currentM                      time (though you MUST include the separating characters.iL                      For example if you input '- 13' you will get all alertsM                      since 13:00 (1 PM) from today. No input will display all N                      alerts from the time the alert logging file was created -/                      usually system start time.o  K                   o  NodeName. Displays alerts only for the node specified.nN                      Wildcards will be allowed once this section is finished -7                      that is it is not yet implemented.(  N                   o  Class. Alerts are divided into classes: FAULT, CONFIGURA-M                      TION, ACCOUNTING, PERFORMANCE, SECURITY. This is the OSIeN                      standard (FCAPS) arrangement and seemed such a good idea,L                      we stole it. In addition, EMU defines a SYSTEM categoryN                      to allow the system itself to report problems it believesK                      need operator assistance. In the current version, onlynN                      CONFIGURATION alerts are generated. Note this function is)                      not yet implemented.e  N                                                               User Guide  3-17 P  e            I                   o  Execute. Once the selection criteria has been set uptN                      (Currently once time has been established) selecting thisK                      item causes the selected alerts to be displayed 1 at aeM                      time in the screen. The display screen allows 'next' ande7                      'previous' alerts to be displayed.u      \             3.4.2 Alert Format
            3.4.2 Alert Format
            3.4.2 Alert Format  =                All alerts are displayed in a standard format:p  H                o  Line 1 Shows the class of the alert and the device theM                   alert is for. If the system knows the name of the device it L                   is used, otherwise the address of the device is displayed.  G                o  Line 2 shows the date and time the alert was received H                   and the subsystem that sent it. This will usually be a0                   PSR(Protocol Specific Routine)  E                o  Line 3 will usually be the subclass. In the case oftJ                   configuration alerts there are 3 subclasses: ADD, DELETE                   or MODIFY.  J                o  If there is additional information this follows and willK                   normally be a list of parameters that were added, deleted                    or modified.  M             3.5 Utilities
            3.5 Utilities
            3.5 Utilities   H                Utilities are those routines that are little used, not toJ                be used by the uninitiated or otherwise inappropriate to beM                included in the main user interface. It is firmly advised thateJ                these routines be well understood before use. The effect ofM                misuse can be anything from nothing to death by brain removal.iK                In the later case, the effect may be quite subtle with deathnL                taking a long time and inflicting pain and frustration on all                affected.  S             3.5.1 Error Log
            3.5.1 Error Log
            3.5.1 Error Logd  I                The error log file EMU5_LOG:EMU_LOG.ERR is a typeable fileeJ                (that is you can type/print/edit it) that the system writesM                errors and other significant information to. An extract of them.                file and interpretation follow:                       3-18  User Guide                 U                     %RELATR-W-VERADDR, 22-JUN-1998 11:50:00.08 RELATER Invalid Targetn@                     addr 002A54F4 For PID 0000000C From 00000006Q                       -----------------------------------------------------------oU                     %CFGMON-E-SNDALT, 22-JUN-1998 11:51:40.21 NETMON SEND_ALERT Errorc                     00000601Q                       -----------------------------------------------------------TN                     %NODSCN-I-ADDIP, 23-JUN-1998 12:23:05.07 CFGMON Added node#                     171.144.141.128nQ                       -----------------------------------------------------------                 Notes:d  J                1. The first section is the facility(RELATR), message levelM                   (I = Information, W = warning, E = Error) and short form oft.                   the error message (VERADDR).  F                2. The second part is the time and date the message was                   logged.   H                3. The remainder is variable and is intended to provide aH                   complete picture of the problem (or not). The messages                   above mean:   G                   1. The relater received a frame containing an invalid M                      address. The MOP module (00000006) sent address 002a54f4 N                      specifying it as an Ethernet address. This is not a valid&                      Ethernet address.  F                   2. The Network Monitor process sent an alert messageJ                      that was too large for the alert buffer. In EMU errorF                      messages, any time a message contains the keywordK                      'Error', it is always followed by a VMS standard errort>                      code. To translate this code type at DCL::                      $ WRITE SYS$OUTPUT F$MESSAGE("%X601")?                      In this case, code 601 is buffer overflow.a  M                   3. The NodScn process found another IP address and added it %                      to the database.   P             3.5.2 PARAMTBL
            3.5.2 PARAMTBL
            3.5.2 PARAMTBL  J                Each parameter in the EMU database has an associated recordL                describing how to format it, the privileges needed to view itL                and how the alert mechanism reacts if it is added, deleted or                modified.K                Each parameter is associated with a protocol and a table. IntL                some cases where there are multiple tables within a protocol,H                the table names are also in this file and can be modified,                similarly to parameter names.    N                                                               User Guide  3-19 h  p            V             3.5.3 Operations
            3.5.3 Operations
            3.5.3 Operations  %                The start the program:e                $ PARAMTBLF+                A menu appears with 2 items:t  L                o  Parameters. Selecting this item allows you to view, change>                   or delete the characteristics of parameters.  H                o  Tables. Selecting this item allows you to view, changeI                   or delete the characteristics of tables. In the case of I                   tables there is only 1 characteristic - it's name. Note L                   that changing the name will prevent the help entry on thisK                   table name from working unless the corresponding entry inn3                   the help library is also changed.s  \             3.5.3.1 Parameters
            3.5.3.1 Parameters
            3.5.3.1 Parameters  J                You may list, add modify or delete parameters. In all casesJ                selecting an item takes you through a menu structure of theC                protocols and tables to find a particular parameter.   J                o  List. This will list all that parameters in a particular7                   table. There are 5 columns displayed:d  /                   1. PRM. The parameter number.l  E                   2. Keyword. This is the name that will be used when /                      displaying this parameter.u  M                   3. Ctl/Rtn. This is the formatting indicator used to formatsI                      the parameter value for display. It is either an FAO 3                      directive or a routine number.e  I                   4. Flg. This is a bit pattern that controls whether thesG                      parameter should be polled for and included in thelK                      database and if so, what the alert mechanism should dot=                      when it is created, modified or deleted.t  J                   5. LvL. The level this parameter is displayed at. In theN                      user interface the user may select displays from Brief toL                      Verbose displays. This number corresponds to the level.                                                       This function should
                                                     This function should
                                                     This function should
               o  Add. Adds a parameter to the file.                   only be used by developers. It is included here only for
                  only be used by developers. It is included here only for
                  only be used by developers. It is included here only for                   completeness.
                  completeness.
                  completeness.
                                To add a parameter you need to know:  N                   o  The Table the parameter is in. Tables are either assignedN                      internally by the system or calculated from data receivedM                      from the network. Tables are found via menus that appears/                      on the left of the screen.d               3-20  User Guide                 J                   o  The parameter number. Usually this is assigned by theM                      protocol but in cases where the protocol does not assignsK                      this, the system does. All parameters have an assignedb:                      number and belong to exactly 1 table.  N                   o  Formatting. How this parameter is formatted. It is eitherL                      by FAO directive or routine. If the parameter cannot beL                      formatted by a simple FAO string (usual case) a routineN                      is supplied. A menu of available routines is presented on,                      the left of the screen.  0                                                                          Be
                                                                          Be
                                                                          Be
               o  Modify. You may change any aspect of a parameter entry.                   careful and sure of what you are doing here - changes here
                  careful and sure of what you are doing here - changes here
                  careful and sure of what you are doing here - changes here                  can have very subtle and undesired effects.
                  can have very subtle and undesired effects.
                  can have very subtle and undesired effects.
                                                              If Modify isL                   selected a menu of protocols appears. Using this menu willJ                   take you down through the table hierarchy to arrive at aJ                   particular table. Once a table is arrived at you will beK                   asked for a parameter number. This parameter must already K                   exist. To find parameter numbers use the list function. A I                   brief explanation of each field you can change follows:   N                   o  Security. A menu listing all VMS privileges is displayed.H                      Selecting any item causes the selected parameter toM                      require the user to have that privilege in order to view M                      it's presence. That is to say, if you select CMKRNL, theeN                      next time you view the parameter list and you do not haveJ                      the CMKRNL privilege, the parameter will not be seen.A                      Selecting an enabled privilege, disables it.a  J                   o  Keyword. This is the word or phrase this parameter isJ                      known by. Any printable string up to 64 characters isM                      allowed. If you change the name of a parameter, the help L                      entry will cease to work until you also change the helpN                      entry in the help library. Instructions on how to do this7                      are provided in the Hints section.e  H                   o  Formatting. Do not change this. If you do, softwareN                      support will yell at you when you tell them the system isK                      broken. If you change this, you will break the system.O  L                   o  Report Level. All parameters belong to a level in rangeK                      1-5. The level is used in displaying lists. In generaleH                      the most interesting parameters are 1 and the leastL                      interesting parameters are 5. The display is controlledK                      by the hidden menu on the query display and correspond                       as:  G                     1. Summary. The lowest level. Only those parameterslM                        defined as 'most interesting' are displayed. GenerallypC                        this would include only names and addresses.e  I                     2. Brief. Names, addresses and those considered majora0                        parameters are displayed.  N                                                               User Guide  3-21 e               F                     3. Normal. All but the most obscure parameters are!                        displayed.p  D                     4. Full. All parameter that can be formatted are!                        displayed.t  I                     5. Verbose. All parameters are displayed. If there istI                        no formatting available for a parameter, a defaults.                        translation is applied.  H                   o  Include in database. Whether or not to include thisE                      parameter, when received in the database. If nottK                      included, it will not be monitored or processed in any N                      manner. Normally, most parameters are included except forL                      those which are very dynamic and are not useful at this2                      level. Examples of these are:  K                     o  TCP connections in MIB-II. The list of addresses and >                        ports currently connected to this host.  G                     o  Bridge FDB tables. The list of MAC addresses andA0                        destinations in a bridge.  J                      Both of these examples, are (in most cases) very longJ                      lists that change rapidly. The result of putting themJ                      in the database is to use a LOT of space up with dataK                      that is obsolete in minutes and depending on how othert/                                                                      Be sure
                                                                      Be sure
                                                                      Be sure
                     parameters are set, will cause excessive alerts.                       you understand the impact and use of any parameter before
                     you understand the impact and use of any parameter before
                     you understand the impact and use of any parameter before                      changing this field.
                     changing this field.
                     changing this field.
                                         Default is yes.  M                   o  Include in monitors. Essentially the opposite of includeaG                      in database. Monitors are intended to retrieve andeJ                      display the rapidly changing parameters. Monitors are8                      not yet implemented. Default is no.  J                   o  Alert on Create. Exactly that. When this parameter isJ                      created, send an alert to that effect. Default is no.  J                   o  Alert on Modify. Exactly that. When this parameter isK                      modified, send an alert to that effect. Default is no.i  J                   o  Alert on Delete. Exactly that. When this parameter isJ                      deleted, send an alert to that effect. Default is no.                         3-22  User Guide                 n             3.5.3.2 PARAMTBL Summary
            3.5.3.2 PARAMTBL Summary
            3.5.3.2 PARAMTBL Summary  I                This utility is very useful for customising your system at G                low levels. With a few keystrokes you can change the waydI                data is displayed across the system and using the security M                facility, limit access to a very fine degree. With power comes J                responsibility; Be sure of what you are doing before you doJ                it. As a safety, backup the file EMU5_DAT:MAPPER.DAT beforeL                you make changes. If it all goes horribly wrong, restore your                backup.               3.5.4 MIB compiling and Registration
            3.5.4 MIB compiling and Registration
            3.5.4 MIB compiling and Registration  D                MIBs (Management Information Base) are readable filesJ                produced by the manufacturer of a device that supports SNMPL                (Simple Network Management Protocol). At this writing SNMP isM                supported only in the IP world. The MIB defines the parametersuJ                that the device supports, how to access them, the format ofH                the parameters and (often) a short explanation of what it                means..J                MIBS must be compiled before they are usable by the system.J                EMU provides a compiler in 2 parts for a number of reasons:  H                o  It is never advisable to edit a MIB although it is notK                   unknown for errors to be present in the MIB itself. UsingsJ                   the EMU MIB compiler, you can edit the output of the 1st:                   pass to correct any errors of this kind.  J                o  Simple is a relative term. At the protocol level SNMP isJ                   not simple to implement although it is much simpler thanJ                   many. At parameter (MIB) level it is often too simple. AJ                   prime example of this is how a MAC (Ethernet) address isL                   specified; it is always shown as an Octet String - that isJ                   a string of bytes. Octet strings are generally printableM                   characters but in the case of a MAC address this formattingyI                   does not work. EMU therefore redefines these parametersdM                   using private definitions and therefore maintaining correcttL                   output. Again, output from the 1st part of the compile can6                   be edited to correct these problems.  I             The private definitions EMU defines are as follows. Note thateK             they are defined using the ASN.1 tags reserved for private datadG             types and therefore will not interfere with any existing ortK             future definitions contained in a valid implementation of SNMP.t            N                                                               User Guide  3-23 s  t                            ______________________________________________________________
               Table 3-3:  EMU ASN.1 Private DataTypes
               Table 3-3:  EMU ASN.1 Private DataTypes
               Table 3-3:  EMU ASN.1 Private DataTypes  z                                      Tag
                                     Tag
                                     Tag                ______________________________________________________________
               EMU Symbol            Value  DataType
               EMU Symbol            Value  DataType
               EMU Symbol            Value  DataType  7                SNMP_ASN1E_MACADDR    193    Mac address-  <                SNMP_ASN1E_DISPSTR    194    Printable string  9                SNMP_ASN1E_TBLTOP     195    Table top [1]   :                SNMP_ASN1E_TBLENT     196    Table entry[1]                  ______________________________________________________________
               SNMP_ASN1E_BRIDID     197    Bridge ID   M             Note 1: These 2 types are used internally only. They should never-.             be edited into a MIB at any stage.  K                There are a number of enhancements included in this compiler >                that are not present in industry standard ones:  M                o  The 1st pass extracts all the description fields and builds K                   a VMS standard help library. After registration this helpdJ                   library is available to the user interface providing theK                   user with access to all parameter definitions in readable H                   format. Because MIB parameters are many and often haveH                   cryptic or obscure names, this is seen as an essential                   service.  H                o  The private definitions allow more precise and clearerH                   display of values than those that simply following the                   protocol.e  t             3.5.4.1 Usage Instructions
            3.5.4.1 Usage Instructions
            3.5.4.1 Usage Instructions  J                To compile a MIB and make it available for use follow these                instructions:  D                1. Ensure the MIB you want to compile is in EMU5_MIB:H                   directory. MIBs can normally be obtained by contactingK                   the manufacturer of the device via either the Web or FTP. G                   EMU supplies many of the more common MIBs precompiled J                   and registered. To find which MIBs are already availableK                   run PARAMTBL, Select Internet and the resulting menu will M                   display all registered MIBs. Other MIBs are simply suppliedf/                   and are located in EMU5_MIB:.   L                2. Run EMU5_EXE:MIB_COMPILE1.The program will ask for the MIB5                   name. Enter it. This compile phase:c  I                   o  Opens the input file and creates the Help and output L                      files with the same name as the MIB and with extensions/                      .HLP and MC1 respectively.                3-24  User Guide                 I                   o  IMPORTS all files specified in the IMPORT statements J                      in the MIB. These must exist and have been previouslyJ                      complied by this routine. If any do not exist you areM                      given the choice to continue or exit. It is often a good I                      idea to continue as much of the IMPORTED information K                      is not used. If at a later stage the program is unableeI                      to define a parameter, exit the program, compile theh4                      offending MIBs and start again.  K                   o  Extracts all definition statements and writes then out &                      the the HLP file.  N                   o  Builds the schema internally. See the hints section for a5                      brief description of the schema.y  K                   o  Once the MIB is entirely read in, and if there were notK                      errors detected, the schema is written out to the .MC1 M                      file, The Help library is created and the help file justt?                      created is inserted into the help library.e  L                3. Run EMU5_EXE:MIB_COMPILE2.The program will ask for the MIB5                   name. Enter it. This compile phase:l  M                   o  Takes the MC1 file previously created and converts it tobL                      a form usable by the system. It creates a file with theN                      same name as the MIB and extension .MC2. This is the fileN                      that the rest of the system searches for when listing out$                      available MIBs.  M                   o  The program displays it's progress by showing the number I                      of lines read/ written on the screen. If the program G                      exits without error, creation has been successful.   H                4. Run EMU5_EXE:MIB_REGISTER.The program will ask for theG                   MIB name. Enter it. The program will determine if the.I                   MIB is already registered and if so, you may replace it K                   with the new definitions. Otherwise it advises the number L                   assigned to this MIB and includes all definitions in EMU5_L                   DAT:MAPPER.DAT. The MIB is now available for the system to5                   use on any device that supports it.   L                5. After making any required adjustments to the system' usageK                   of the parameters just registered (see below for a hint),bI                   you then tell the system which nodes to use this MIB ony                   by:u  L                   o  In the main EMU user interface select a node supporting                      this MIB.  N                   o  Select IP protocol. If the device does not support IP, it/                      does not support any MIBs.u  K                   o  The menu of available MIBs is displayed along with Sete8                      MIB Params. Select 'Set MIB Params'  N                                                               User Guide  3-25                 =                   o  A further menu appears. Select 'Set MIB'n  M                   o  A menu of available MIBs appears. Each item is a toggle;pG                      Selecting an already selected MIB deselects it andoJ                      selecting an unset MIB sets it. The Selected MIBs areK                      shown in a bit pattern at the top of the screen - each I                      MIB has a corresponding bit in the pattern that whenHL                      set (to 1) indicates to the system to use this MIB when+                      updating this address.   M             You can test this MIB with another utility that is also useful in ,             browsing the network: MIBWALKER.  K                Note that by default all IP addresses are assumed to support I                MIB-II - the basic MIB that most SNMP devices support - at I                least in part. Internally to the system this is MIB number
J                1. DO NOT CHANGE THIS DEFINITION. If this is the only MIB aL                device supports or the only MIB you want to act upon a device+                then no action is necessary.a  S             3.5.5 MIBWALKER
            3.5.5 MIBWALKER
            3.5.5 MIBWALKERe  K                A MIBWALKER is a generic program that allows you to retrieve M                and display the results of data from a node supporting SNMP. A F                number of conditions must be met before this will work:  K                o  The device you are targeting must be running, attached to J                   the network and be prepared to respond to SNMP requests.  =                o  You must use the correct MIB to talk to it.   J                o  If the Device does not allow public access you must know3                   the community string it supports.e  J             To run the MIB walker type 'MIBWALKER' at the DCL prompt. ThisL             system wide symbol is set up at EMU start time. Note that EMU isH             not required to be running in order to execute this routine.A                Running the program displays a menu on the screen:g  K                o  Set IP address. Select this item and enter the IP addressaJ                   you wish to talk to. Wildcards or names are not allowed.M                   In future, this routine may be integrated with EMU to allowc)                   more friendly searches.i  M                o  Set MIB. Set the MIB you want to use on this device. A menuN=                   of available MIBs is presented. Select one.   H                o  Set Community String. By default the transactions willL                   use the public string. If the device does not accept this,L                   select this item and enter the community string the deviceI                   uses. Selecting this item and providing no input causestG                   the public string to be used. Note the string is case                    sensitive.               3-26  User Guide                 H                o  Walk the MIB. This MIB walker is a bit unusual in thatJ                   it does not actually 'walk' the MIB. Selecting this itemJ                   (after setting at least the IP address and MIB) presentsI                   a menu of tables and items this MIB supports. SelectingeJ                   any item sends the appropriate request to the device andJ                   if an answer is received, displays the results. PressingL                   the HELP key anywhere in this menu invokes the help systemL                   and displays and explanations of the associated parameters8                   available. Exit this menu with CTRL Z.  J                o  Toggle Log file. Selecting this item turns logging on orL                   off. If logging is off it turns it on, if off, it turns itL                   on. When on all displays to the screen are also written toC                   the file MIBWALKER2.LOG in the default directory.n  J             All the functions are independent. That is you can set the MIBJ             and switch between addresses or vice versa. It is often a goodJ             idea to run this program after compiling and registering a MIBJ             and noting which parameters should be adjusted using PARAMTBL.I             For many MIBS you may not want all the parameters (by defaulttK             all will be collected) or you may want to alert when additions,tJ             deletions or modifications are detected on some parameters. By,             default no alerts are generated.    n             3.6 Errors and Omissions
            3.6 Errors and Omissions
            3.6 Errors and Omissions  M                This is the beta release of software. Some functions described G                in the user guide are not implemented and others may notsM                perform exactly as expected. It is the purpose of this release L                to find these errors, note the usefulness of the system as itK                stands and to collect feedback for it's further development.rH                This section describes the known errors and some possibleC                workarounds. These are given in no particular order:e  D                o  Monitor Listen Display. The error count incrementsJ                   regularly. No other symptoms found (that is there are noL                   known errors). Probable coding issue. No effect on system.  G                o  On rare occasions the system does not shutdown fully. K                   Before starting the system it is a good idea to start the I                   user interface by typing EMU and the DCL prompt. If the K                   error 'fatal controller error' is returned, the system is K                   fully shutdown. If not, wait a few minutes and try again. J                   If still not shutdown, locate the EMU processes (all EMUH                   processes have 'EMU_' as the 1st 4 characters of theirM                   names) and 'STOP/ID' them. Note if this action is necessary I                   it is imperative that on next startup the databases are                    cleared.  N                                                               User Guide  3-27 e  
            L                o  DECnet IV PSR does not display on the MONITOR PSR display.8                   Reason unknown. No other known effect.  K                o  User interface often hangs upon exit from trace facility. J                   Control Y the process and restart the interface. Will be(                   fixed in full release.  H                o  Bridge Ids in the FDDI display are not translated cor-L                   rectly. The selector wrongly assumes a specific table this:                   is in. Will be repaired in full release.  H                o  System is prone to slowdown after running for about 10L                   days. Cause is fragmentation of the database file which isM                   in turn is caused by excessive read/writes to it. A fix hastM                   been engineered and can be expected in the full release. In L                   the meantime, the file can be reorganised using CONVERT onM                   occasion. Note that the system must be shutdown to do this.f  M                o  Not all parameters are translated. The two main reasons fory                   this are:   I                   1. The parameter is not documented and requires reverse M                      engineering to determine what it is and how to translate                       it.  N                   2. The parameter is complex and requires special routines to<                      format it.  This is an ongoing exercise  I                o  The hidden menu function that filters parameter display H                   based on 'importance' is not effective largely becauseJ                   the parameters are all set to the default of 0 (with theH                   exception of MIB generated parameters which are set toH                   3). The mechanism also needs some adjustment to filterJ                   out untranslatable parameters. The task of revaluing theI                   individual parameters is left to the user at this pointrK                   although the system may provide more convenient templatesf                   in future.  L                o  MOP sends too many relater frames. The MOP module acquiresJ                   both the MAC in use and the burned in MAC address on theL                   card. There is no way for MOP to determine if the hardwareM                   address has been passed to other databases therefore always J                   sends this information on each cycle. There is no effectJ                   other than uselessly using a small resource. A fix is in                   progress.s  M             A file EMU5_DAT:EMUBUG.DAT contains all known errors and fixes atv             release time. 9                Please send any additions to this list to: '                system@ccci4.demon.co.uk)               3-28  User Guide                 A             3.7 Hints
            3.7 Hints
            3.7 Hints   I                This section is included to impart some uses of the system 3                that may not be immediately obvious.y               3.7.1 Further processing of Reports
            3.7.1 Further processing of Reports
            3.7.1 Further processing of Reportss  K                Reports are always generated as flat files and can be easilyaJ                formatted and manipulated using simple DCL procedures. Some%                useful things to note:   M                o  All data is presented as list with each parameter separatedeK                   by a vertical slash (|). The number of slashes present is1I                   always the number of parameters less 1 - if a parameteriK                   does not exist there is nothing between the slashes where L                   it would be if it did. This allows for very easy detectionL                   and extraction using the F$ELEMENT lexical function in VMS.                   and easy importing to Excel.  K                o  The first parameter is always a number. The number itself L                   has little meaning but note that all parameters associatedI                   with a single box always have the same number. Put more L                   simply: When the number changes, it is a different device.I                   A number of example report formatting procedures are in
                   EMU5_RPT:.  M             EMU does not currently provide an interface capable of extracting G             data conditionally. That is there is no way to say "Get all1J             nodes with names beginning with "TST" and having at least 1 IPJ             address that does not begin with "171". This is however easilyK             accomplished by generating a report with all occurrences of the I             parameters and writing a simple procedure (about 10 lines) to              apply the logic.  }             3.7.2 Seeding the IP database
            3.7.2 Seeding the IP database
            3.7.2 Seeding the IP databaseo  L                There is no direct way to add an address to EMU but in the IPL                section this can be done indirectly by 'pinging' the address.K                If the node answers, it will be added to the database as theaK                IP module listens for and receives all ICMP frames (A 'ping' G                uses an ICMP echo request and response sequence). It maypH                be useful to keep a procedure containing ping commands toJ                important IP addresses and run it at system startup as this:                will speed up finding further IP addresses.            N                                                               User Guide  3-29 i  n                         3.7.3 Finding a MOP console user
            3.7.3 Finding a MOP console user
            3.7.3 Finding a MOP console user  G                If, when using TSM to access a server and the connection M                fails, it is often because another system is using the console M                port. The message returned does not help to make this obvious.1K                Within EMU, find the server you are trying to connect to andtK                force an update using the hidden menu. Wait about 30 secondsaL                and redisplay. Assuming the update has been successful, (noteJ                the last update time at screen top), the MAC address of theJ                system connected to it will be displayed as 'Console User'.K                Find this MAC address to identify the system that 'owns' the                 console.B                                                                                         3-30  User Guide B  M                                _________________________________________________________________
               Index
               Index
               Indexa    r                _______________________________
               A                                 MIB Register, 3-25  m                                                  MIBWALKER, 3-26
               Adding a node to IP database,e]                                                  Monitor Listener, 3-8
                  3-29ei                                                  Monitor Probes, 3-12
               Alert - Format, 3-18 j                                                  Monitor PSRs, 3-11
               Alert - Main Menu, 3-17g                                                  MOP console, 3-30
               Alert Subsystem, 3-17eA                                                  MOP Device, 3-16p?                _______________________________
               B                                                   _______________________________
                                                 N
               BOXID, 3-13  `                                                  Netware SAP, 3-16
               BUILD.COM, 2-1B                                                  Network menu, 3-8?                _______________________________
               De                                                  _______________________________
                                                 O
               Device display format, 3-5   e                                                  Obtaining MIBs, 3-24
               Device menu, 3-4h  2                Device Query menu, 3-4            Ps                                                  _______________________________
               Dump_Database, 3-15iX                                                  Parameter Display, 3-5
               E                _______________________________
                                                 Parameters not translated, 3-28 i                                                  PARAMTBL, 3-5, 3-19
               EMU_LOGICALS.COM, 2-1tg                                                  Private DataTypes, 3-23
               Error Log, 3-18l]                                                  PSR, 3-18
               Ethernet type, 3-16                                                     _______________________________
                                                 R
               F
               _______________________________t  g                                                  reporting menu, 3-6
               Forcing Update, 3-6 H                                                  Report Processing, 3-29?                _______________________________
               Ge                                                  _______________________________
                                                 S
               Getting help, 3-3  >                                                  Scanner, 3-15}                _______________________________
               H                                 Seeding the IP database, 3-29   [                                                  SNMP, 3-23
               Hidden Menu, 3-6o_                                                  START_EMU.COM, 2-2
               History, 1-2eD                                                  Supplied MIBs, 3-24z                _______________________________
               I                                 System Account quotas, 2-2b                                                  System menu, 3-8
               installation, 2-1E                                                  System Overview, 1-1d                _______________________________
                                                 System Start, 3-1
               Mc                                                  System Stop, 3-1
               Main Features, 1-1r                                                    _______________________________
                                                 T
               Main menu, 3-3t9                Menu Security, 3-3                TPU, 3-7 <                MIB, 3-23                         Trace, 3-15G                MIB Compilers, 3-24               Translate Tables, 3-16M*                MIB compiling and Registra-                   tion, 3-23                                                                            _______
                                                                         Index-1r o  h            9             _______________________________
            U                UOI, 3-16              Update Cycle, 3-6              User Interface, 3-3              Utilities, 3-18A  9             _______________________________
            V                View Sections, 3-13l'             VMS Error Translation, 3-18                                                                               '             _______
            Index-2i