![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Manager 1.51 Server Management Usage Tips
Contents:
GENERAL USAGE TIPS
Server Monitor can launch Server Status, but they are two separate tools
in the LANDesk(R) Manager Control Panel. Each operates differently.
Server Monitor consists of CONSOLE.EXE, CNSPX.EXE, CONTROL.NLM, and
MONIT386.NLM. No other LANDesk Manager tool uses these NLMs. Novell Labs
tested the functionality of Server Monitor's NLMs with both NetWare*
v3.11 and NetWare v3.12 under the same certification bulletin--N-60 for
LANDesk Manager v1.5 and N-74 for LANDesk Manager v1.51. These NLMs do
not support NetWare v4.x or SFTIII NetWare.
Server Status consists of SERVMON.EXE. Server Status accesses the
NetWare file server bindery to monitor the advertising devices
maintained there.
NMS SNAP-IN
With NMS integration, the Server Monitor and Server Status pull-down
menu options were inadvertently reversed. Using a text editor, exchange
the executables referenced in two lines of the c:\NMS\OLF\LANDESK.OLF
file:
IDM_SAMPLE_4=F:\LANDESK\console.exe, , Server Monitor, 1, 1
IDM_SAMPLE_5=F:\LANDESK\servmon.exe, , Server Status, 1, 1
SERVER MONITOR: COMMUNICATING WITH NLMS
Because Server Monitor converses with NLMs at the file server, you may
need to add the following lines near the top of the workstation's
NET.CFG.
ipx sockets=30
spx connections=20
Also, SAP 0x001BF must pass between the Server Monitor workstation and
the file server running CONTROL.NLM and MONIT386.NLM. Some WAN routers
filter SAP packets beyond the normal Novell packets. Configure the
router to pass 0x001BF packets to run Server Monitor on workstations
beyond the router.
NetWare* sometimes fails to report that the Server Monitor NLMs are
loaded, so we modified our executables to bypass NetWare and maintain
connection. Download SMON.EXE from Intel's online services (LANDesk
Manager current area). Also, we recommend using EMM386.EXE to manage
memory on a Server Monitor workstation.
SERVER MONITOR: TIME STAMPS
Time stamps in Server Monitor can rely on accurate time zone settings at
both the file server and the workstation. NetWare's* SYSTIME.EXE fixes
some time discrepancies between the file server and workstation, but
not all.
To set the proper time zone at the file server, follow the instructions
in the NetWare System Administration manual under SET TIMEZONE. For
example, a file server in Utah would use SET TIMEZONE=MST7 (during
daylight savings, MST7MDT; the default is EST5EDT). To automatically
set this parameter when the file server comes up, place this SET
parameter in STARTUP.NCF or at the beginning of AUTOEXEC.NCF.
Note: Since CLIB.NLM must be loaded after any change to this
parameter to reflect the proper time zone, setting it manually may
require you to unload several NLMs. NetWare does not automatically
adjust the time zone setting for daylight savings changes.
To set an accurate time zone setting at the workstation, use SET TZ with
similar syntax. For example, a LANDesk(R) Manager administrator's
workstation in California would place SET TZ=PST8 in the AUTOEXEC.BAT.
SERVER MONITOR: MISCELLANEOUS NOTES
If you use a Compaq NetFlex NIC in a NetWare* v3.11 or v3.12 file
server, load the LANDesk(R) Manager NLMs (specifically, Server Monitor's
MONIT386.NLM) BEFORE loading the Compaq LAN driver (Token Ring or
Ethernet). Based on Intel's analysis of the situation, Compaq NetFlex is
the only known card with a driver that Novell's MONITOR.NLM and Intel's
LANDesk Manager cannot monitor; this appears to be due to Compaq's LAN
driver not fully conforming to ODI specifications.
Versions of Novell's MONITOR.NLM dated before 1993 uncover the same
Compaq NetFlex issue -- trying to view LAN card statistics in
MONITOR.NLM causes a file server ABEND immediately whether Intel's NLMs
are present or not. MONIT386.NLM makes the same call as Novell's
MONITOR.NLM, so the temporary workaround is to not have MONIT386.NLM
monitor the Compaq NetFlex LAN card statistics by loading MONIT386.NLM
before the LAN driver. We are working with Compaq to address the issue,
but contacting Compaq directly may help you understand their ODI issues
with Novell's MONITOR.NLM that Intel's Server Monitor NLMs also uncover.
If Server Monitor tries to build a 24-hour history file on the network
and a backup runs, the message "Sharing Violation on Drive ?:" may
appear. Change the location of the history file (FILENAME.HST) to a
local hard drive.
SERVER STATUS: RUNNING FROM A LOCAL DRIVE
If you are running Server Status from a server and that server goes
down, you won't receive notification of the change in status. However,
if the files are copied to a local drive and Windows* survives the loss
of file server, the alert should be passed.
Copy the following files to a local drive and the alert will be passed
with the following exception: if you are attached to and are trying to
access the server that went down, Windows will most likely hang.
ASP.DLL
CTL3D.DLL
NWNETAPI.DLL
SERVMON.EXE
SERVMON.HLP
STATUS.DLL
VLB.DLL
Note: Make sure that if you assigned an action to be taken on an
alert, you will need Alert Log running locally as well as Server Status.
See the ALERTLOG.TXT file (Alert Log icon in the LANDesk(R) Manager
Control Panel Read Me folder for more information). Some files listed in
ALERTLOG.TXT are not present unless you've configured a modem, etc.
Ignore a filename listed if you do not have it.
Trademark information