home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 15
/
novell-nsepro-1992-vol15.iso
/
download
/
nsmrme.txt
< prev
next >
Wrap
Text File
|
1992-07-13
|
13KB
|
363 lines
============================================================
NetWare Services Manager (NSM) version 1.0 Update README
============================================================
Installing the Update
----------------------
Five files named NSMUPDT1.EXE, NSMUPDT2.EXE, NSMUPDT3.EXE, NSMUPDT4.EXE,
and NSMUPDT5.EXE should have been obtained along with this file. These
executable files are DOS self-extracting archives of the various NSM
files that have been updated. To install the update:
1) If running OS/2 version 1.3, start a DOS session since NSMUPDTx.EXE
must be executed from DOS. If you are running OS/2 v2.0, this
step is not necessary since OS/2 v2.0 automatically starts up a DOS
session when a DOS application is executed from OS/2.
2) Change to the drive and directory where NSM has been installed. This
will usually be C:\NETMAN. This should be the root level of the tree
structure created by the NSM installation process, not inside the
EXEC, DLL, or DBASE subdirectories.
3) Without changing directories further, execute the update program by
typing the following commands (assuming floppy distribution):
a:\NSMUPDT1 -d -o
a:\NSMUPDT2 -d -o
a:\NSMUPDT3 -d -o
a:\NSMUPDT4 -d -o
a:\NSMUPDT5 -d -o
The two command line arguments are required and are used to cause the
original directory structure to be maintained (-d) and to overwrite
existing files if they are present (-o). If the NSMUPDTx.EXE files
exist on a different drive and/or path simply change the A:\ to
whatever is appropriate.
The executable files will extract the files listed in the following
section and place the files in the appropriate subdirectory in the
NSM-created directory tree.
4) If the NSMUPDTx.EXE files were copied to hard disk, you will probably
want to delete the copy on hard disk (but retain a copy on floppy)
to free up approximately 1 Megabyte of disk space.
Files Updated
--------------
\NETMAN\DLL Directory
CFGRPT DLL 124352 04-20-92 5:09p
DBAPI DLL 135765 04-20-92 4:55p
INSTALLR DLL 80327 05-01-92 9:56a
\NETMAN\EXEC Directory
INSTALL EXE 126192 05-01-92 3:32p
INSTALL HLP 16941 05-01-92 3:32p
MAPEDIT EXE 95632 05-01-92 10:10a
MAPEDIT HLP 3751 04-30-92 5:26p
MCBASE EXE 341520 04-30-92 5:40p
NMS HLP 103947 05-07-92 3:11p
NMS EXE 509424 05-07-92 3:10p
NMSETUP EXE 81488 05-11-92 10:10a
NMSETUP HLP 20940 05-11-92 10:10a
NODSCH EXE 535408 05-07-92 2:35p
NODSCH HLP 80494 05-07-92 2:33p
Problems Fixed With in this Update
-----------------------------------
* Now compatible with OS/2 versions 2.0. NSM still supports OS/2 v1.3.
* Various help files have been changed to more accurately reflect the
program content.
* 'Locate Node' operation on NSM console sometimes failed
* A newly discovered node refresh of the map display would sometimes
cause the map to be positioned improperly.
* Tab characters in a NET.CFG could cause INSTALL to trap
* In INSTALL, the drive F: was hard coded to use during the installation
process. If the PC had F: as a local hard drive, install would fail.
* Certain memory handling situations were improved.
* Several minor problems with the navigator were corrected, relating to
the accuracy of the navigator blue box.
* 'Cable Path Details' would sometimes display incorrect data.
---------------------------------------------------------------------
RELEASE NOTES - NEW OR MODIFIED SINCE INITIAL RELEASE
---------------------------------------------------------------------
OS/2 Screen Fonts
------------------
When installing OS/2 version 1.3 or version 2.0, make sure to select
all available screen fonts for installation. If all of the fonts are
not installed, NSM may exhibit font problems in certain areas. For
OS/2 version 1.3, the list of fonts installed should be:
Courier
Times
Helv
Courier.psf
Helvetic.psf
Timesnrmn.psf
Sysmono
Using Multiple Frame Type in NET.CFG
-------------------------------------
If using more than one frame type in your NET.CFG, make sure that the
first frame type listed in the LINK DRIVER section corresponds to the
default frame type for your preferred server. If the ordering is not
correct, some of the various map actions such as LAN configuration, LAN
statistics, Known Servers, Known Networks, and Connections may cause the
OS/2 requester to trap.
Shell Version
--------------
The following shells and requester have been tested and work with
the NSM product. Use of shells other than those recommended may
work, but are not fully tested.
Some third party shell drivers may cause the workstation to hang
when queried by NSM. Also, some token ring workstations may hang
when queried by NSM. To avoid this problem, turn off workstation
display in the map.
Dos/Windows Shells:
VIPX .386 19197 2-21-92 1:50p
VNETWARE.386 10102 2-24-92 8:22a
LSL .COM 7648 11-20-91 4:57p
IPXODI .COM 20903 11-20-91 4:57p
NETX .COM 52443 2-11-92 4:19p
BNETX .COM 58468 2-11-92 4:26p
EMSNETX .EXE 65083 2-11-92 4:21p
XMSNETX .EXE 62051 2-11-92 4:24p
NWIPXSPX.DLL 35308 1-29-92 10:36a
OS/2 Requester:
For OS/2 v1.3 use requester version 1.3F or above.
For OS/2 v2.0 use the latest available requester (beta or release)
---------------------------------------------------------------------
RELEASE NOTES - FROM ORIGINAL RELEASE
---------------------------------------------------------------------
This section contains notes, hints, and helps intended to
help you work with the NSM program. The items discussed below
are not arranged in any particular order.
Trace
-----
If the NSM system terminates because of an error condition, a
trace screen may appear listing program trace data. If this
screen comes up, either save the data to a file or print it out
and contact your NOVELL service representative.
Swap Space
----------
The NSM system requires a minimum of 5Mb of disk swap space to
run properly. Make sure your SWAPPATH parameter in config.sys is
set to a drive with the required space.
NetWare 3.11, Thousand User Version
------------------------------------
The 1000 user version of NetWare v3.11 should not be instrumented
at this time. Novell will provide future updates to the NSM
product to allow instrumentation of 1000 user systems.
Server Memory Requirements
---------------------------
The NetWare Management agents require up to 2.5Mb of additional
server memory. At least 1Mb of memory (cache non-moveable) is
required to load the NLMs, and at least 1Mb (alloc short term) is
recommended for memory allocations. Alloc memory requirements
are variable, depending on the server's configuration (disks,
lans, vols, NLMs, and etc.). Unpredictable results occur when
there is insufficient server memory.
NetWare v3.11 and NetWare v4.0 Beta Versions
---------------------------------------------
These versions of NetWare should not be instrumented.
48/96 QUEUES/NLM limit
-----------------------
The NSM Node Schematic displays information about a server's
first 48 queues and the first 96 NLMs only.
Duplicate Server Names
-----------------------
Duplicate server names should not be used with NSM.
Unpredictable results may occur where names are duplicated. If
two or more instrumented servers have the same name, rename the
servers or run MAPEDIT to delete one of the duplicates.
Passwords
----------
The NETMAN account on an instrumented server should not be set to
force periodic password changes. If periodic changes are forced,
then NEPFMDD must be run to synchronize the new NSM password with
the new server password each time the password changes.
If the "force periodic changes" feature was turned on before the
NETMAN account was created, you must login as user NETMAN and
manually change the password to the correct one being used. If
this is not done, the first login by NSM will fail because the
server sends back a change password message.
Configuration Descriptions
---------------------------
The Card Type field of the Lan Configuration Details screen in
the map and in Node Schematic may be inaccurate in some cases.
The card type is a number assigned by Novell to a card. All
versions of the NetWare OS prior to NetWare 4.0 return a number
in the range of 0 - 255 only. Therefore, any card type above 255
will be displayed inaccuratly. Use the description string to
determine the card type.
Some difference in data may be observed between the lan details
screens in the map and the data screens in Node Schematic. Data
for the map is obtained by using the SPX diagnostic protocols.
These protocols present the data as known for the IPX/SPX
protocols. The Node Schematic screens show data as read from the
MLID table and are relevent to all protocols running on the
system. For example, Max Packet Data Size in the map details
screen may show 1024, while Max Packet Buffer Size in Node
Schematic may indicate 1514.
Virtual Routers
----------------
Some third party routers do not support the IPX/SPX diagnostic
calls and, therefore, do not show up in the map as individual
entities. Since the map knows there is a route between point A
and point B, but has no information about the route, a virtual
router is inserted between points A and B. If there are multiple
routers between points A and B, it will still show up as one
virtual router. Virtual routers also combine multiple routes
together as one icon. Up to 16 routes per virtual router icon
are possible.
Less virtual routers will be needed as more third party routers
begin to add IPX/SPX diagnostics support to their products.
SYS:SYSTEM Read Only Potential Problems
----------------------------------------
If the .NLM files in the SYS:SYSTEM directory are flagged Read Only
or the file AUTOEXEC.NCF is flagged Read Only, installation of NLMs
will fail. Flag these files as read/write.
Patches
--------
The following patches must be installed on all NetWare 3.11
servers (instrumented or non-instrumented) that are attached to
networks to be managed. The patches fix existing problems in the
NetWare OS. Server crashes may occur if these patches are not
applied.
CROPNFX .NLM 1040 12-18-91 3:18p
DIAGRFSX.NLM 2593 03-18-92 8:21a
OS2OPNFX.NLM 1389 11-22-91 2:45p
PATCH311.NLM 20823 07-29-91 10:52a
PATCHMAN.NLM 8987 03-12-92 11:24a
SPXFIX1 .NLM 1513 03-13-92 12:32p
SPXFSFIX.NLM 1617 12-12-91 1:59p
These patches are on the INSTALL 1 diskette. Do the following for
each 3.11 server to be patched.
1. Login or attach to the server as SUPERVISOR or as a user
with SUPERVISOR rights.
2. Map a drive to SYS:SYSTEM
3. Change to the drive mapped to SYS:SYSTEM
4. Place the INSTALL 1 diskette in the appropriate floppy
drive.
5. Copy all the .NLM files to SYS:SYSTEM.
COPY d:*.NLM
6. Copy the PATCH.NCF file to SYS:SYSTEM.
COPY d:PATCH.NCF
7. From the file server console (or by using RCONSOLE) run the
PATCH.NCF
New Token LAN
--------------
In order to receive Token Ring alerts on instrumented servers,
the Novell token ring lan driver listed below should be used.
TOKEN.LAN 10324 9-9-91 11:30a
Enabling Accounting
--------------------
Refere to NSM User's Guide, p.49, Server Utilization box. The
accounting feature must be enabled (through SYSCON) before user
utilization statistics can be gathered and displayed by NSM.
However, make sure that the NETMAN user account is set to
unlimited. If the NETMAN user account is set too low or the
account balance is exausted, NSM can no longer obtain data from
the server through this connection. The possible result is that
NSM logins and the Node Schematic will fail.
Printing Notification History Report
-------------------------------------
If an HP Laserjet or compatible printer is used to print the
Notification History Report, it must have MORE than 512KB of
memory.
Concurrent Printing
--------------------
Once a request to print is issued to NSM, do not request
subsequent printouts until printing has completed on the last
request.