NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  NMS002.EXE: NMS 2.0 Maintenance
README FOR:  NMS002.EXE

NOVELL PRODUCTS and VERSIONS:
NetWare Management System 2.0

ABSTRACT:

NMS002.EXE contains NMS 2.0 Rev C, which is the latest
maintenance patch for NetWare Management System 2.0.  It is
recommended for all NMS 2.0 sites because it includes both fixes
and new features for NMS Console, installation, and NetExplorer
server.  Supersedes NMS001.EXE and NMS202.EXE.  (the binary files
in NMS002.EXE are unchanged since December 1994)



-----------------------------------------------------------------
 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.

-----------------------------------------------------------------


SYMPTOM:

S1. The NetExplorer server would abend if; WellFleet series 7 or
3Com NetBuilder II routers were in the environment.

 S2. After installing NetWare Management Agent 1.6, "Not
Available" alarms were reported in the Alarm Monitor.

 S3. NetExplorer Manager reported a GPF on the NMS console at
0001:1B4C.

 S4. Not all the IP networks, in the environment, were discovered
in the Internet map.

 S5. NetWare RunTime servers were disrupted by the NCP
connections that the NetExplorer server temporarily takes up.

 S6. Network segments, on the Internet map, were improperly
consolidated together.

 S7. Redundant routers, in the network, were not discovered in
the Internet map.

 S8. Interoperability problems with:
 - StonyBrook Services Router Manager for Cisco Systems 2.0
 - StonyBrook Services Router Manager for Wellfleet 2.0
 - Intel LANDesk Manager for NMS 1.51

 S9. The calculation for the legal host address range wasn't
always correct when you selected Open > View > IP Networks and
double-clicked an entry to bring up the IP Nodes list.


 New Features
 ------------
 F1. IP Timeout (NetExplorer Server)
 If IP discovery is being performed over low speed links, such as
a WAN, the default timeout of five seconds might be too short. 
You can change this timeout by starting NXPIP.NLM with a
different timeout value.  You can change this in NETXPLOR.NCF.

 For example:  LOAD SYS:\NMDISK\NXPIP /t 10

 This would change the timeout to 10 seconds.  The default is 5
seconds.    

 F2. Hub Services Manager Update (NMS Console)
 Hub Services Manager has been updated to support token ring and
custom hubs.  The use of this update requires support from the
hub vendor.  This update is transparent to the current hub
management.  Any information required to use the new interface is
supplied by the hub vendor.

 F3. IPX Scoping (NetExplorer Server)
 In NMS 2.0, it was possible to specify IP network addresses to
be used to control the scope of IP discovery.  NMS002 adds a
similar feature to IPX discovery.  The file SCOPE.TXT describes
that feature, and explains how you can use scoping.

 F4. IP Scoping (NetExplorer Server)
 IP discovery, by default, discovers routers that are within the
network to which the NetExplorer system is directly attached. 
NMS 2.0 has a feature to allow you to expand discovery to other
networks, by specifying these addresses in NXPIP.INI.  How to set
up IP scoping using either specified IP network numbers or the
new *.*.*.* wildcard network number is also described in
SCOPE.TXT.

SOLUTION: 

Apply NMS002

 Solution Specifics
 ------------------
 S1. In NMS 2.0 and NMS 2.0 Rev B, NMS assumes IP routers report
the index value of the instrumented interfaces sequentially and
inclusively to the total number of interface instances.  Because
WellFleet 7 series and 3Com NetBuilder II routers behave
differently, NetExplorer might abend the server when it discovers
these routers.

 S2. NetWare Management Agent 1.6 includes a number of new alarms
in the NWALARM.MIB that were not available in previous versions
of NMA.  Installing NMS002 allows you to view information about
these alarms in NMS 2.0.

 S3. In NMS 2.0 and NMS 2.0 Rev B, multiple instances of the same
network were created wrongly for token ring segments monitored by
NetWare LANalyzer Agent software.  Also, some token ring segments
monitored by NetWare LANalyzer Agent had incorrect networks. 
Because of these, whenever NetExplorer Manager was rerun, a GPF
was generated.  The GPF on the NMS Console was 001:1b4c.  This
has been corrected.

 S4. The Object ID type in an SNMP request packet was set to
ASN.1 type OBJECT IDENTIFIER, but should have been set to ASN.1
type NULL in the SNMP request packet.  This resulted in some
routers not responding to the SNMP request.  This occurred in
Timplex routers and some versions of Wellfleet routers.

 S5. NetExplorer temporarily takes up an NCP connection on each
server it discovers.  For some servers, this might not be
desirable; specifically, when the server has no connections to
spare and is periodically performing some operation.  This is
particularly problematic for servers that use NetWare Runtime
software and have only one login connection, such as Intel
StorageExpress.

 NetExplorer logs in to the server only to discover the IPX
addresses and usernames for workstations logged in to the server.

 NetExplorer can avoid logging in to servers for well-known SAP
values by entering these values in NXPIPX.INI in the NMDISK
subdirectory of the server.  For example, you might enter the
following lines:

 ServiceOnAServerNotToBeQuery = 376
 ServiceOnAServerNotToBeQuery = 43B

 where:
 - All values are hexadecimal.
 - The equal sign (=) is required between the keyword and the
value, but spacing before and after the equal sign is not
required.

 The values shown in the sample lines exclude Intel
StorageExpress servers from workstation discovery.

 The benefit of excluding a server from being queried is that it
avoids disruption of critical services, such as server backups.
The disadvantage of excluding a server from being queried is that
no workstations attached or logged in to the server are
discovered by NMS.

 S6. Some network devices have the same MAC address for their
interfaces.  When your network has more than one of these network
devices, they might be improperly consolidated on the NMS maps. 
(The NetExplorer software attempts to consolidate every
individual instance of these devices into a single device on the
map.)

 To avoid the consolidation of these devices, add a DupMac entry
to the NMS.INI file, which is located in the MS Windows directory
on the NMS Console, for every duplicate MAC address on your
network. Each entry must have the following form:

 DupMacn=MAC_address

 where:
 - n is a number that is incremented for each DupMac entry.
 - MAC_address is the specific MAC address that is duplicated.

 Your NMS.INI file has DupMac1 and DupMac2 entries by default;
you might have added DupMac3, DupMac4, and so forth, because of
previously over consolidated segments.

 The following devices are known to be improperly consolidated on
the NMS maps:
 - NetWare Connect servers
 - Cubix Series 3000 and Series 4000 communications processors
 - NetWare DOS Box NLM software
 - NetWare Link/SNA software
 - NetWare MultiProtocol Router 2.1 or later software

 To prevent the improper consolidation for the above devices, add
the following DupMac entry to NMS.INI:  DupMacn=000000

 In addition, to prevent the improper consolidation for the
following devices:
 - NetWare Link/SNA software
 - NetWare MultiProtocol Router 2.1 software or later

 add a DupMac entry to NMS.INI where the MAC_address is the
specific MAC address that is duplicated.

 S7. Redundant routers were not discovered because the routers
were not involved in the routing scheme.  These can be discovered
by adding the IP address of redundant routers to a file.  To
discover these routers, load NXPIP.NLM with the /a option,
followed by the filename.  You can change this in NETXPLOR.NCF.

 For example:  LOAD SYS:\NMDISK\NXPIP /a redrout.lst

 where REDROUT.LST contains the following entries:
 132.54.20.2
 121.22.50.72

 S8. NMS uses an embedded version of the Btrieve database engine;
WBTRCNMS.DLL.  NMS002 updates WBTRCNMS.DLL to fix
interoperability problems with the following third-party NMS
products:
 - StonyBrook Services Router Manager for Cisco Systems 2.0
 - StonyBrook Services Router Manager for Wellfleet 2.0
 - Intel LANDesk Manager for NMS 1.51

 S9. Corrected.


 Continuing Problem
 ------------------
 After installing NMS 2.0 Rev C, all the SNMP family alarm TYPES
on the "Configure Alarm Disposition" window might be blanked out. 
If so, you can recompile the MIBs by selecting Tools > SNMP MIB
Compiler...

Self-Extracting File Name: nms002.exe

Files Included     Size     Date      Time

..\
      NMS002.TXT     (This file)
     INS0762.LIB           18010         12-6-94      2:00:02 am
     INSTALL.INS           83358         12-6-94      2:00:02 am
      NMSPATCH.1          286819         12-6-94      2:00:02 am
      NMSPATCH.2          863218         12-6-94      2:00:02 am
     NMSSTAR.BMP            5998         12-6-94      2:00:02 am
       SCOPE.TXT           17927        11-28-95     11:07:26 am
       SETUP.BMP           22812         12-6-94      2:00:02 am
       SETUP.EXE          276480         12-6-94      2:00:02 am
       SETUP.INS           25267         12-6-94      2:00:02 am
       SETUP.PKG             770         12-6-94      2:00:02 am


Installation Instructions:

1. NMS 2.0 or NMS 2.0 Rev B, must be installed and functioning on
the Console PC.

 2. There must be a minimum of 10MB of free disk space on the
drive where NMS 2.0 resides.

 3. Close all NMS applications running on your system.
 If you fail to close any of the NMS applications, a dialog box
will appear for each application that is open, requesting you to
close it. 
 Respond "Yes" to any of these requests.

 4. From the Windows Program Manager, run the SETUP.EXE found in
the directory in which you extracted NMS002.EXE.

 5. Select the Console Update check box, the Server Update check
box, or both, then click OK.

 If you selected only "NMS Console Update", Setup continues to
completion.  Skip to Step 8.

 Otherwise, Setup will present a list of servers to choose for
updating and you will continue with Step 6.

 6. Select ONE NetExplorer server to update.

 7. Enter the username and password when Setup prompts you.

 The user must have SUPERVISOR equivalent privileges.
 The setup process will continue to completion.

 8. If you successfully updated the NMS Console software, exit
Windows, then start Windows again.  This ensures that the console
software is loaded properly.

 9. If you updated a server, restart the server.

 If you want to update another server, run Setup again.  You do
not need to restart Windows each time you update an additional
server.


 INSTALLING THE NMS 2.0 INSTALLATION UPDATE (OPTIONAL)
 This update modifies the NMS 2.0 installation software to let
you install NMS 2.0 NetExplorer software on a different server,
or to reinstall it on the previously selected server (without
installing the NMS Console software).

 1. Format a 3.5 inch high-density (1.44 MB) diskette and label
it NMS 2.0 Setup.

 2. Copy the contents of the NMS 2.0 Setup diskette (shipped with
NMS 2.0) to the NMS 2.0 Setup diskette that you formatted.

 3. Copy INSTALL.INS from the NMS 2.0 Rev C directory to the root
directory of the new NMS 2.0 Setup disk.

 4. Use the NMS 2.0 Setup disk in place of the original NMS 2.0
Setup disk when you install NMS components.


 DEINSTALLING THE NMS CONSOLE AND NETEXPLORER SERVER UPDATES
 After completing the installation of NMS 2.0 Rev C, if you
experience problems that might have been caused by this
installation, you can deinstall NMS 2.0 Rev C by following these
directions.

 To remove the NMS 2.0 Rev C Console Updates and restore the NMS
2.0 environment, copy the following files from the NMS\BACKUP\001
subdirectory of the directory where NMS 2.0 was installed to
their respective directories listed below:

      DIRECTORY           FILE
      ---------           ---------
      BIN                 N_TDNW.DLL
      BIN                 N_NETADD.DLL
      BIN                 N-OLF.DLL
      BIN                 N-ICON.DLL
      BIN                 N-SNOOPR.DLL
      BIN                 N-DB.DLL
      BIN                 N-TABLE.DLL
      BIN                 N-VER.DLL
      BIN                 N-NMSVER.DLL
      BIN                 WBTRCNMS.DLL
      BIN                 N-OLFI.EXE
      BIN                 N-HUBUTL.DLL
      BIN                 N-HUBGTB.DLL
      BIN                 N-HUBMAN.DLL
      BIN                 N-HUBCON.DLL
      BIN                 N-HUBRES.DLL
      BIN                 N-HUBMIB.DLL
      BIN                 N-HUBNOD.DLL
      BIN                 N-HUBDRW.DLL
      BIN                 N-HUBMAP.DLL
      BIN                 N-HUBDAQ.DLL
      BIN                 HSMID.DLL
      HELP                NWALARM.HLP
      OLF                 N-HUBNOD.OLF
      OLF                 N-HUBMAN.OLF
      OLF                 N-HUBMAP.OLF
      SNMPMIBS\ALLMIBS    NWALARM.MIB
      SNMPMIBS\CURRENT    NWALARM.MIB
      VERSIONS            N_TD.VST
      VERSIONS            N_RSM.VST
      VERSIONS            N_HSM.VST
      VERSIONS            N_NMM.VST
      [windows]           HSM.INI
 [windows] denotes the location where MS Windows is installed on
the system.

 To remove the NMS 2.0 Rev C Server Updates and restore the NMS
2.0 environment, copy the following files from the
NMDISK\BACKUP\001 subdirectory in the root of the SYS volume of
the chosen server to the NMDISK directory of the same volume:
 NXPIP.NLM
 NXPIPX.NLM

 After copying the NXPIP.NLM and NXPIPX.NLM, restart your server.

 __________________________________________________________
 Patch History: NMS002.EXE supersedes NMS001 and NMS202.



-----------------------------------------------------------------
 Any trademarks referenced in this document are the property of
their respective owners.  Consult your product manuals for
complete trademark information.

-----------------------------------------------------------------

