
              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              Frequently Asked Questions about NMS
DOCUMENT ID:        TID200015
DOCUMENT REVISION:  B
DATE:               30MAR94
ALERT STATUS:       Yellow
INFORMATION TYPE:   Issue
README FOR:         NA

NOVELL PRODUCT and VERSION:
NetWare Management Systems 2.0
NetWare Management Agent
NetWare LANalyzer Agent 1.1

ABSTRACT:

This file contains the most frequently asked questions and answers for the
NetWare Management System product line.  It is broken down into subsection by
the following product names:   NetWare Management System 2.0, NetWare
Management Agent 1.5, NetWare LANalyzer Agent 1.0, and NetExplorer.


DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO NOVELL.  NOVELL
MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS INFORMATION.  HOWEVER, THE
INFORMATION PROVIDED IN THIS DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL
MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.


ISSUE

     
     NETWARE MANAGEMENT SYSTEM (NMS) 2.0 QUESTIONS AND ANSWERS
     

     Q:   What causes the error message "unable to copy or decompress
          AUTOEXEC.BAT" when installing NetExplorer?

     A:   Make sure SHARE is loaded and that 580 KB of base memory is free for
          the install.  However, the most common reason is that you are logged
          in to a server.  To perform the install, just attach to a server by
          running the NetWare Client drivers (LSL, MLID driver, IPXODI, VLM).

     Q:   What causes the error message "NETWARE.DLL file not found" when you
          start up NMS?

     A:   The most common reason for the error is that the user does not have
          the NetWare Client drivers loaded before doing the install.  Also,
          the user should ensure that MS Windows is set up for networking
          (Novell NetWare 4.0).

     Q:   What is the problem when you have been running NetExplorer Manager
          (the minimized magnifying glass) for several hours and your Internet
          map only contains the "Discovery In Progress" segment?

     A:   Most likely your NMS console is not "pointing" to the correct
          NetExplorer server.  To verify that the correct NetExplorer server
          is selected, do the following the steps:

          1.   Select Configure.

          2.   Select Global Preferences.

          3.   Scroll down to the NetExplorer Options icon and select it.

          4.   Verify the NetExplorer server name is the correct server.

     Q:   What is the problem when after installing the NetWare Management
          Agent 1.5, the message "\NMS\BIN\N-SNOOPER...122 db version
          mismatch" is reported when you start the NMS Console?

     A:   Check whether you did the NMM 1.15B and NSM 1.5 update documented
          that is on pages 9 and 10 of the NetWare Management Agent 1.5
          Release Note.  This portion of the Installation should only be
          performed if you have the NetWare Management System 1.1.  To correct
          this error, you need to reinstall the NMS 2.0 Console software.

     Q:   Is a third-party resource guide for NMS available?

     A:   A third-party resource guide for NMS is available on NetWire in the
          file RESRCE.EXE file in NOVLIB Lib 8.  The guide provides a list of
          third-party products designed to work with NMS or Novell's
          MultiProtocol Router.  The guide also includes a brief definition of
          commonly used terms.

     Q:   How do you issue the SET command within the MIB Browser?

     A:   To issue the SET command within the MIB Browser, do the following
          steps:

          1.   Highlight the Attribute value for the variable you want to
               change.  A blinking box will appear.

          2.   Press the <Enter> key.

          3.   Change the value in the pop up box and select OK.

          4.   Then issue the SET request to update the SNMP agent by clicking
               on the finger icon.

     
     NETWARE MANAGEMENT AGENT 1.5 QUESTIONS AND ANSWERS
     

     Q:   On a server running the NetWare Management Agent, what does the
          message "Instrumented OS Emulator unable to Register Object class:
          100.3.1" mean?

     A:   Usually this means you have a corrupt queue (such as a print or FAX
          queue).  Initially, you can try to delete the jobs in the queue.  If
          the error doesn't go away, do the following steps:

          1.   Delete the queue from the SYS:SYSTEM directory.

          2.   Run BINDFIX.

          3.   Recreate the queue.

     Q:   What causes the error message "Communication with server failed
          (Error 251)" to be returned when you double-click on a "manageable"
          server?

     A:   Usually this means the NETMAN user account on the server running the
          NetWare Management Agent is corrupt.

          Use SYSCON or NWADMIN utility to delete the account, recreate
          another user with the name NETMAN, and assign that user a password. 
          (When using the NWADMIN utility, make sure the context in which you
          create the NETMAN user is the same context as the "manageable"
          server.)

          Also, if you give the user a different password, remember to
          register that new password on the NMS console.

     
     NETWARE LANALYZER AGENT 1.0 QUESTIONS AND ANSWERS
     

     Q:   What should I do when while installing NetWare LANalyzer Agent, the
          following message is reported?

          MESSAGE

               Current XXXXX.LAN driver is promiscuous capable but its updated
               driver was not found

     A:   This is a bug in the install.  Copy the driver to the DRIVERS
          directory on Disk 1.  Then restart the installation.

     Q:   What can you do when executing the command View, All, Network
          Segments, the following message is reported in the last column of
          the segment you want to monitor?

          MESSAGE

               Agent Not Monitoring

     A:   When this message is reported do the following procedure:

          1.   Make sure the NetWare LANalyzer Agent NLM files (in LANZ.NCF)
               are running.

          2.   Check to see that the interface (network board) is being
               monitored from the server.  To do this, perform the following
               steps on the NetWare LANalyzer Agent server:

               a.   LOAD NWSNUT.

               b.   LOAD LANZCONF (located on disk 3).

               c.   Highlight the network interface card driver that
                    supposedly is not being monitored.  Then press <Enter>.

               d.   Select "Network Interface Items" from the menu.

               e.   Verify the following information:

                        The "Item" column contains an entry labeled
                         "Statistics" and that the corresponding "Status"
                         column says "valid"

                        The "Owner" column says "monitor"

                        The "Network" column indicates the name of the
                         adapter

               f.   If all the information is correct, then that interface
                    should be monitored by the NetWare LANalyzer Agent; skip
                    to step 3.

               g.   If all the information is not correct, the single-segment
                    version of the NetWare LANalyzer Agent might be installed,
                    and it might not be enabled for this interface.  You can
                    enable the NetWare LANalyzer Agent for that interface by
                    performing the steps on page 3-5 of the NetWare LANalyzer
                    Agent Installation Guide.

          3.   Reinstall the LANalyzer Agent.

     Q:   What do I need to do if when I execute the command View, All,
          Network Segments and I click the Dashboard icon on the desired
          segment that I want to monitor, "only" the Dashboard is displayed
          and the bar chart of the top stations is missing below the
          dashboard?

     A:   Ensure that the Simple Network Management Protocol (SNMP) is
          explicitly loaded with the following parameters:

               LOAD SNMP VERBOSE CONTROL= TRAP=

          If you have this statement in AUTOEXEC.NCF file, make sure that
          another NLM isn't automatically loading SNMP (without the
          parameters).  To make sure that these parameters are being used,
          load the CONLOG NLM (in NOVLIB, Lib 9, CONLOG.EXE) to review the
          loading of the NLMs.  When SNMP loads, it should return the
          following message:

          MESSAGE

               SNMP: ControlCommunity now accepts any community name

     Q:   What can I do if when I try to bring up the Dashboard or the Station
          Monitor table or I try to capture packets, the following message is
          reported?

          MESSAGE

               No Resource on Probe

     A:   Make sure the Simple Network Management Protocol (SNMP) is
          explicitly loaded with the following parameters:

               LOAD SNMP VERBOSE CONTROL= TRAP=

          If you have this statement in AUTOEXEC.NCF file, make sure that
          another NLM isn't automatically loading SNMP (without the
          parameters).  To make sure that these parameters are being used,
          load the CONLOG NLM (in NOVLIB, Lib 9, CONLOG.EXE) to review the
          loading of the NLMs.  When SNMP loads, it should return the
          following message:

          MESSAGE

               SNMP: ControlCommunity now accepts any community name

          The "No Resource on Probe" error could also mean that you have
          exceeded the upper limit on memory that can be allocated dynamically
          by the NetWare LANalyzer Agent.  For an explanation on increasing or
          decreasing the memory used by the NetWare LANalzyer Agent, refer to
          the "bound=" parameter in the SYS:SYSTEM\LANZ.NCF file.

     Q:   What can I do if when I execute the command View, All, Network
          Segments, the following message is reported in the last column of
          the segment that I want to monitor?

          MESSAGE

               No Response

     A:   If this message is received, do the following procedure:

          1.   Make sure the network segment is "pointing" to an "active"
               Remote Monitor by doing the following:

               a.   Highlight the segment reporting "No Response".

               b.   Select "Configure" then "Selected Object".

               c.   Scroll down to the Remote Monitor icon and select it.

               d.   Select an active Remote Monitor and click Save.

          2.   Use the Fault, Test Connectivity feature to verify that the NMS
               console can communicate with the server running the NetWare
               LANalyzer Agent.  Perhaps an intermediate device is down.

     Q:   What can I do when the Dashboard or Top 20 Stations Table is
          displayed and the NMS console reports the following message:

          MESSAGE

                out of Top N resources

     A:   To resolve this problem, use the following steps:

          1.   Make sure the Simple Network Management Protocol (SNMP) is
               explicitly loaded with the following parameters:

                    LOAD SNMP VERBOSE CONTROL= TRAP=

               If you have this statement in AUTOEXEC.NCF file, make sure that
               another NLM isn't automatically loading SNMP (without the
               parameters).  To make sure that these parameters are being
               used, load the CONLOG NLM (in NOVLIB, Lib 9, CONLOG.EXE) to
               review the loading of the NLMs.  When SNMP loads, it should
               return the following message:

               MESSAGE

                    SNMP: ControlCommunity now accepts any community name

          2.   The Dashboard and the Top 20 Station Table use "Top N tables"
               to display the "top talkers" on that segment.  The default
               number of Top N tables is 4.

               To get rid of the "out of Top N resources" error message, you
               do one of the following three actions:

               a.   Close any Dashboard or Top 20 Station Table windows that
                    you are not using.

               b.   Increase the Top N resources value in the
                    SYS:SYSTEM\LANZ.NCF file.  This file contains a detailed
                    description of the "Top N resources" variable.

               c.   You can also use the LANZCONF utility to see how many top
                    N tables have been opened by doing the following steps:

                    1)   Load NWSNUT.

                    2)   Load LANZCONF (located on Disk 3).

                    3)   Highlight the network interface card driver that is
                         being monitored.

                    4)   Select "Network Interface Items" from the menu.

                    5)   Count how many "Host Top N" entries are in use.

                    Each entry will show which console and service (Dashboard
                    or Station table) owns it.

     Q:   Must IPX be bound to each network board for the NetWare LANalyzer
          Agent to monitor each segment?

     A:   The NetWare LANalyzer Agent requires at least "one" network board to
          be bound to IPX for the NMS console to communicate with it.  It does
          not require every network adapter to be bound to IPX or to another
          network protocol.

          Note:  A potential side effect with not binding IPX to each network
          board is that your Internet map may have disjoint or "island"
          segment icons (for those segments which NetExplorer was unable to
          determine where they should be connected).

     
     NETEXPLORER QUESTIONS AND ANSWERS
     

     Q:   What can I do if I encounter any of the following problems running
          the NetExplorer software on a NetWare 4.01 server?

              You cannot communicate from the NMS console to NetExplorer
               using the IPX(tm) protocol.

              The NetExplorer discovery process stops unexpectedly (and there
               are no error messages indicating that this occurred).

              An error message is displayed with a negative value error code.

     A:   If you are running NetExplorer on any NetWare 4.01 server, the
          following NLMs must be updated with at least the following dates:

               IPXS.NLM        8-23-93
               SPXS.NLM        9-14-93
               TLI.NLM         9-14-93
               STREAMS.NLM     9-14-93

          These NLMs are not updated automatically by the NMS 2.0 installation
          process.  To update the NLMs, refer to procedure specified in the
          README.TXT file provided on the NetWare Management System 2.0
          NetWare 4.01 Server Update Disk.  If the server already has a later
          version of these NLMs, then disregard this.

          Note:  Problems with NetExplorer may occur if these NLMs are not
          updated.




