home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Encyclopedia 96-1
/
novell-nsepro-1996-1-cd2.iso
/
download
/
netware
/
mwlanz.exe
/
MWLANZ.TXT
Wrap
Text File
|
1995-11-20
|
18KB
|
437 lines
NOVELL TECHNICAL INFORMATION DOCUMENT
TITLE: MWLANZ.EXE; ManageWise Update
README FOR: MWLANZ.EXE
NOVELL PRODUCTS and VERSIONS:
NetWare LANalyzer Agent 1.0
ManageWise 2.0 All
ManageWise 1.0
ABSTRACT:
MWLANZ.EXE contains an update of the ManageWise 2.0 console for
ManageWise 2.0 owners which provides both new features and some
fixes. In addition it provides for v1.1 of the NetWare LANalyzer
Agent which can be used by both ManageWise 2 and ManageWise 1.
Novell recommends that ManageWise owners download MWLANZ.EXE.
NOTE: This patch will not work on a SFT III server.
-----------------------------------------------------------------
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:
New Features Provided by MWLANZ.EXE for ManageWise 2.0
------------------------------------------------------
1. Monitoring for Inactive Nodes on a Segment
If NetWare LANalyzer Agent 1.1 is installed on at least one
server on a segment, you will be able to use the ManageWise
Console to select the nodes on a segment that you want monitored
for inactivity. You will then be alerted if a node becomes
inactive (and if it becomes active).
You will be able to monitor any node on the segment, regardless
of the protocol that the node uses.
This Inactive Node Monitor (INM) feature provides an alternative
to using the "Ping Periodically" feature, which is available in
this and previous releases. There are several advantages in
using INM. Unlike "Ping Periodically", INM does not poll the
target nodes and, therefore, does not generate traffic on the
network. INM determines the status of each network adapter,
whereas "Ping Periodically" determines status per node.
Additionally, INM is protocol independent. Therefore, Novell
recommends that you use INM instead of "Ping Periodically",
unless you need the statistics that "Ping Periodically" provides.
2. You will be able view Historical Trends as well as Current
Trends
after you install NetWare LANalyzer Agent 1.1 on a segment, you
will be able to view both current trends and historical trends
over hourly, daily, weekly, monthly, and yearly periods from the
ManageWise Console.
A new MIB (GNTREND.MIB) has been added to the
\NMS\SNMPMIBS\CURRENT and
\NMS\SNMPMIBS\ALLMIBS\NOVELL\LANZ directories on the ManageWise
Console to support historical trends.
3. Performance Enhancements
- Loading the ManageWise Console software will be considerably
faster than previously.
- The ManageWise Console will detect status changes of NetWare
LANalyzer Agent servers more quickly.
4. The Dialog Box for Selecting the Preferred LANalyzer Server
has been enhanced in the Database Object Editor, the Remote
Monitor icon is renamed to LANalyzer Server. Additionally, the
NetWare LANalyzer Agent Server dialog box, which appears when you
click the LANalyzer Server icon, has been enhanced. In addition
to listing all the NetWare LANalyzer Agent servers and LANtern
network monitors on the segment (so you can select the preferred
NetWare LANalyzer Agent server), this dialog box will now provide
other information as well. For example, you will now be able to
see the version of NetWare LANalyzer Agent running on the server,
its status, and its media access control (MAC) address.
5. More Precise Error Messages Provided
NetWare LANalyzer Agent 1.1 provides additional error messages
that identify errors more precisely. These error messages will
appear in the ManageWise Console in the following windows and
dialog boxes:
- Network Segments window (View > All > Network Segments)
- Segment Alarms dialog box (Edit > Database Object > Segment
Alarms icon)
- NetWare LANalyzer Agent Server dialog box (Edit > Database
Object > LANalyzer Server icon).
For detailed explanations and actions for NetWare LANalyzer
Agent status and error messages, refer to the online help for the
windows and dialog boxes mentioned above or to Chapter 16,
"Analyzing Your Network," of the ManageWise 2.0 NMS Management
Guide.
Other Information
-----------------
A. About Clock Synchronization for ManageWise 2.0
When you open a segment trend graph in ManageWise, you might
receive a message that the ManageWise Console clock is not
synchronized with the NetWare LANalyzer Agent server clock. This
message indicates that the time zone or time is set incorrectly
on the console or the server (or both). For detailed instructions
on setting the time zone and system time, refer to NetWare 3.12
System Administration or NetWare 4 Supervising the Network II.
To check the time zone setting on the console, follow these
steps:
1. Go to a DOS prompt.
2. Enter SET | MORE.
3. Check the value of the TZ parameter.
The value indicates the name of the time zone, the number of
hours behind the Universal Coordinated Time (UTC) clock, and
whether daylight savings is set to On. For example, a ManageWise
Console in San Francisco in September would display "PST8PDT,"
indicating the Pacific Standard time zone, 8 hours behind the UTC
clock, and daylight savings set to On.
To change the time zone setting on the console, follow these
steps:
1. Exit Windows.
2. Open AUTOEXEC.BAT and edit the time zone setting as
necessary.
3. Restart the workstation on which the ManageWise Console
software is installed.
To check the time zone setting on the server, follow these
steps:
1. At the server console prompt, enter this command: SET TIME
ZONE
2. Check the value displayed.
To change the time zone setting on the server, follow these
steps:
1. Edit STARTUP.NCF to set the time zone value to the correct
values.
2. Bring the server down.
3. Bring the server up.
The next time you open a segment trend graph, the clock
synchronization message does not appear.
B. Disabling Traps to All ManageWise Consoles
By default, NetWare LANalyzer Agent sends all SNMP traps to all
ManageWise Consoles. If you want to prevent NetWare LANalyzer
Agent from sending traps to all ManageWise Consoles (because you
want to limit the number of traps sent over a dial-up line, for
example), you must change the TRAPREG parameter to zero in
LANZ.NCF and make changes to the TRAPTARG.CFG files. (These
files are on any server with NetWare LANalyzer Agent.) The
online help topic "Preventing NetWare LANalyzer Agent From
Sending Traps to the NMS Console" provides instructions for what
to do. (To find this topic quickly, select the Help > Search for
Help On command, then look for the keywords "NetWare LANalyzer
Agent, limiting alarms sent from.")
If you install both NetWare Management Agent and NetWare
LANalyzer Agent on the same server (as would be the case for a
ManageWise Server), comment out FINDNMS.NLM in NMA2.NCF, and
unload FINDNMS.NLM if it is already loaded. Otherwise, all
ManageWise Consoles continue to receive traps because FINDNMS.NLM
on the NetWare server identifies the SAP each ManageWise Console
sends and directs SNMP traps to those Consoles.
C. Promiscuous Mode and Error Handling Requirements for Ethernet
and Token Ring Drivers
Promiscuous Mode Requirements
For both Ethernet and token ring, NetWare LANalyzer Agent
requires a driver that supports promiscuous mode. Promiscuous
mode is the capability of the adapter and driver to capture good
packets or error packets whose destination address is set to any
node on the network, not just its own.
Error Handling Requirements
For Ethernet, NetWare LANalyzer Agent monitors error packets to
report problems such as fragments and cyclic redundancy check
(CRC) errors. Therefore, your network adapter and its associated
driver must support error packet capture.
However, for token ring segments, your token ring adapter and
driver do not have to support error packet capture. This is
because NetWare LANalyzer Agent monitors error conditions on the
ring through Report Error MAC Frames. These MAC frames are
generated on the network when errors occur on the ring.
For Additional Information About Promiscuous Mode and Error
Handling Requirements
-----------------------------------------------------------------
----
If your vendor cannot answer questions you have about the
capability of your network adapter and driver to operate in
promiscuous mode and handle error packets, contact Novell Labs.
Novell Labs provides reports of adapters and drivers it has
tested. You can obtain information from Novell Labs in the
following ways:
- Through the Novell Labs FAXBack service, by calling (800)
414-LABS or (801) 429-2776
- Through the World Wide Web site http://www.novell.com
==============
KNOWN PROBLEMS
==============
NE3200P.LAN
NE3200P.LAN drivers dated 9/30/93 do not work with Remote
Console (RCONSOLE). Also, this driver filters packets that are
less than 18 bytes long. (Most Ethernet fragment packets are
within this range.)
NE3200P is not included in MWLANZ.EXE. You can run NetWare
LANalyzer Agent with this driver. However, you might experience
the problems noted above. At some future time the NetWire
library may have an updated version of NE3200P.LAN.
NE2_32.LAN
To use the NE2_32.LAN driver, you must use hardware Revision F
or newer, of the NE/2-32 adapter. Older hardware revisions do
not work properly with the supplied NE2_32.LAN driver and NetWare
LANalyzer Agent.
NetWare SFT III
The NetWare LANalyzer Agent 1.1 installation program does not
support NetWare SFT III servers. However, Novell is working on
an updated NetWare LANalyzer Agent 1.1 installation program that
will support SFT III servers.
Replacing Network Adapters
In rare situations, replacing a network adapter in the NetWare
LANalyzer Agent 1.1 server may cause the Historical Segment Trend
graphs on the ManageWise console to appear with no data. If this
occurs, you must unload NetWare LANalyzer Agent 1.1, delete all
trend files on the server volume in the directory SYS:\GTREND,
and then reload NetWare LANalyzer Agent 1.1.
Self-Extracting File Name: mwlanz.exe
Files Included Size Date Time
..\
MWLANZ.TXT (This file)
..\CONSOLE\
..\CONSOLE\DISK\
LSM.WRI 19072 11-2-95 3:02:00 am
SETUP.EXE 276480 12-29-93 7:12:08 pm
SETUP.INS 20663 11-2-95 3:02:00 am
SETUP.LGO 174 11-2-95 3:02:00 am
SETUP.PKG 864 11-2-95 3:02:00 am
SETUP.Z 681364 11-2-95 3:02:00 am
VERSTAMP.BLD 19 11-2-95 3:02:00 am
..\NLA\
..\NLA\DISKS\
..\NLA\DISKS\LANZ_1\
ALIAS.TXT 79 6-30-93 1:30:06 pm
PINSTALL.NLM 81693 11-1-95 10:16:02 am
..\NLA\DISKS\LANZ_1\DRIVERS\
3C503.LAN 5501 10-13-94 9:00:30 am
CPQNF3.LAN 49300 3-14-95 1:10:00 am
CPQTOKEN.LAN 83007 5-8-95 3:01:00 am
CTRSTKFX.NLM 972 12-21-94 12:48:10 pm
E100S.LAN 42447 5-16-95 2:54:00 pm
ETHERTSM.NLM 9362 11-29-94 3:34:30 pm
IBMMPCO.LAN 40202 6-27-95 9:07:48 am
LSLENH.NLM 10658 8-23-93 9:23:10 am
MADGEODI.LAN 101132 8-9-95 1:53:16 pm
MSM.NLM 20252 11-23-94 11:41:26 am
MSM31X.NLM 21308 11-23-94 11:41:38 am
NE1000.LAN 4472 3-28-94 8:28:04 am
NE2.LAN 5050 6-9-95 10:45:02 am
NE2000.LAN 7695 6-9-95 11:04:08 am
NE2_32.LAN 5090 3-28-94 8:48:10 am
PM312.NLM 9221 3-24-94 11:06:46 am
SMC8000.LAN 26120 9-8-94 3:16:34 pm
SMC8100.LAN 45076 9-21-94 2:05:00 pm
TCTOK47H.LAN 54425 10-13-94 9:43:50 am
TCTOKH.LAN 41188 9-21-94 3:40:26 pm
TOKENTSM.NLM 9493 11-23-94 11:55:24 am
TPRO.LAN 24696 9-13-94 3:35:52 pm
..\NLA\DISKS\LANZ_2\
GTREND.NLM 38809 11-1-95 10:14:18 am
LANZAEL.NLM 34163 11-1-95 10:07:12 am
LANZCON.NLM 98851 11-1-95 10:13:14 am
LANZCTL.NLM 41532 11-1-95 10:15:08 am
LANZDI.NLM 151096 11-1-95 10:06:16 am
LANZFCB.NLM 58452 11-1-95 10:08:24 am
LANZHIS.NLM 33225 11-1-95 10:09:14 am
LANZLIB.NLM 19733 11-1-95 10:09:40 am
LANZMEM.NLM 25151 11-1-95 10:09:56 am
LANZSM.NLM 71388 11-1-95 10:11:18 am
LANZSU.NLM 15630 11-1-95 10:14:32 am
LANZTR.NLM 46531 11-1-95 10:12:30 am
LANZUNDO.NLM 26973 11-1-95 10:15:32 am
..\NLA\DISKS\SNMP_1\
A3112.NLM 12425 3-29-94 1:49:32 pm
AFTER311.NLM 14651 3-29-94 1:48:50 pm
INSTALL.TXT 3306 12-20-94 3:13:48 pm
PINSTALL.HLP 3753 10-13-94 1:58:48 pm
PINSTALL.NLM 119868 12-9-94 9:56:20 am
PSCRIPT.DAT 2302 5-22-95 5:21:52 pm
README 453 12-20-94 3:14:02 pm
SNMP.CFG 1084 8-3-94 9:56:18 am
SNMP.NLM 85942 11-22-94 8:59:02 am
TRAPTARG.CFG 1697 3-17-93 8:50:00 am
..\NLA\DISKS\SNMP_1\3X\
CLIB.NLM 344458 10-27-94 1:29:24 pm
..\NLA\DISKS\SNMP_1\40X\
CLIB.NLM 207535 5-25-94 11:37:38 am
..\NLA\DISKS\SNMP_1\NLS\
..\NLA\DISKS\SNMP_1\NLS\4\
CLIB.MSG 11238 4-20-94 10:13:22 am
IPCONFIG.MSG 2141 12-9-94 11:18:36 am
SNMP.MSG 3698 11-22-94 8:58:56 am
TCPIP.MSG 14407 12-9-94 11:06:12 am
..\NLA\DISKS\SNMP_1\TCPIP\
IPCONFIG.NLM 11766 11-21-94 11:44:02 pm
TCPIP.NLM 392273 3-9-95 7:29:06 pm
Installation Instructions:
MWLANZ.EXE consists of two parts:
- NetWare LANalyzer Agent 1.1
- ManageWise 2.0 Console Update 1
Before you install them, ManageWise 2.0 must be installed.
A. Install NetWare LANalyzer Agent 1.1
A1. Install NetWare LANalyzer Agent 1.0 or 1.0a on any server
you intend to
install NetWare LANalyzer Agent 1.1 on. For details, see the
instructions
in the NetWare LANalyzer Agent 1.1 Installation and
Administration guide.
A2. If the server is a 3.1x server (AND it does not have
Novell's
MultiProtocol Router installed) install SNMP (v3.01) according
to the
instructions in the text file "INSTALL" in the SNMP_1 directory
of
MWLANZ.EXE. SNMP 3.01 is included in MWLAZ.EXE.
REMEMBER, do not use the SNMP update in MWLANZ on a NetWare 4.1
server, or
a server with Novell's MultiProtocol Router.
A3. After installing NetWare LANalyzer Agent 1.1, edit
STARTUP.NCF to
increase the value of the Minimum Packet Receive Buffers
parameter, as
necessary. The general rule is to add 32 buffers for every
network
adapter. Refer to "NetWare 3.12 System Administration" or
"NetWare 4
Supervising the Network II" and your adapter's documentation for
additional
information.
- If you have ManageWise 1.0, stop here.
- If you have ManageWise 2.0, continue on to part B.
B. Install the ManageWise 2.0 Console Update 1 software on each
ManageWise
Console in your network. ManageWise 2.0 Console Update 1
provides the
console component that enables you to view and manage the data
provided by
NetWare LANalyzer Agent 1.1.
From your ManageWise Console
B1. Select File > Run in the Windows Program Manager.
B2. Click the Browse button to select the location and filename
of the
Setup program (SETUP.EXE).
B3. After selecting SETUP.EXE, click OK.
A message will appear indicating that Setup will shut down all
running NMS
components.
B4. Click OK to continue.
A message will appear indicating the path to the MW\NMS
directory.
B5. Click OK to continue.
Setup will replace files in and add files to the MW\NMS
directory.
Setup will then display a message indicating the installation
was
successful.
B6. Click OK to continue.
B7. Setup will prompt you as to whether you want to read the
Readme file
now.
a. To read the Readme now, click Yes.
b. To read the Readme after installation, click No. When
you are
ready to read the Readme, double-click the ManageWise Update 1
icon in the
ManageWise program group.
B8. Restart the workstation on which the ManageWise Console
software is
installed.
-----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their respective owners. Consult your product manuals for
complete trademark information.
-----------------------------------------------------------------