Copyright: ® Intel Corp


Help Contents
Contents

LANDesk® Server Monitor Module

September Release

Product Update Information

Product Codes

Summary

ECO Histories

Orderable Spare Parts List

General Product Information

Novell Certification

IPTL Tested Product List

Approved Vendor List for Modems

Definitions

Readme Files

Frequently Asked Questions

Known Errata

Technical Product Summary

Introduction

Core Feature Set

Out-of-Band Features and Functions

Functional Description

On-board Resources

Programming/Software Information

Appendicies

Additional Information


September Release

This file was compiled on September 27, 1995

•	Errata about graph appearance.

•	Updated numerous errata; updates are dated at the status line.

•	Added the final 2 action alerts regarding the battery pack

•	Updated board and software ECO Histories

•	Updated Product Summary

•	Added figures that were previously missing in the TPS section of this file.


Product Codes

Product Code	Description
SERVERMON	Board (no modem), batteries, reset cable, temp cable, Xtended feature cable; manuals, Netware software, Module Utils and Diags software
SERVERMONOEMA	Board (no modem), batteries, Module Utils and Diags software


Summary

SERVER MONITOR MODULE REVISION SUMMARY

Product	PBA	Rev	BIOS Level	Suggested BIOS	Date	Release Notes
SERVERMON /	630543	-002	1.00.02.BJ0	1.00.03.BJ0	1/95	Pre-Production
SERVERMONOEM		-003	1.00.02.BJ0	1.00.03.BJ0	1/95	Pre-Production
		-004	1.00.02.BJ0	1.00.03.BJ0	2/95	Pre-Production
	635909	-001	1.00.03.BJ0	none	3/95	Production Release, Fab 5
		-002	1.00.03.BJ0	none	4/95	Correction in PB Fab, Fab 5'
		-003	1.00.03.BJ0	none	4/95	Added blue wire for connection omitted from fab.
		-004	1.00.03.BJ0	none	5/95	Fixes Columbus front panel board power on issue.
SERVERMON/ SERVERMONOEMA	638661	-001	1.00.03.BJ0	none	7/95	Fab 6.  Fixes problem of powering on Magellan systems when powering down the SMM.  Mechanical correction to I/O panel
		-101	1.00.03.BJ0	none	9/95	Fab 7.  Bury blue wires
		-102	1.00.03.BJ0	none	11/95	J10 and J6 changed to tin plating.


ECO Histories

BIOS History

Board History

Software History

Literature History

QAN History


BIOS History

1.00.03 BJ0, May 95

Initial Release, 1.00.02 BJ0


1.00.03 BJ0, May 95

This update adds I2C capability to the board.  The BIOS file is named HOBBIOS.BIN, and is posted on Notes and the Bulletin Board.


Initial Release, 1.00.02 BJ0

BIOS was initially released 2/95.


Board History

Tin Headers - Class II

SMM Battery Pack - Class I

Fab 7 - Class II

Fab 6 - Class I

Power-on Issue  Class I

Fab 5,  May 95

Fab 4-Never released

Initial Release, Fab 3


Tin Headers - Class II
Tin Headers − Class II

Current Implementation Date: 11/95

The header connectors for  the secondary temperature sensor cable (J10) and the server reset cable (J6) will change from gold plating to tin plating to match the plating on the connecting cable terminals.  This improves reliability of the connections.


SMM Battery Pack - Class I
SMM Battery Pack − Class I

Date Implemented: 9/95

A new battery pack incorporating an auto-resetting, in-line fuse on the battery has been installed on all shipments of the Server Monitor Module since September 1.  Reworked inventory will be marked with a label "OR2516" both on the board and on the shipping container.  All new or reworked battery packs are labeled with a new part number (617247-002).


Fab 7 - Class II
Fab 7 − Class II

Date Implemented: 9/95

Fab 7 will bury blue wires on Fab 6.  This change also includes the new battery pack.


Fab 6 - Class I
Fab 6 − Class I

Current Implementation Date:  7/95

Fab 6 is released.  Included in the changes:  Buries the blue wires on the previous fab. Fixes a problem where a Server Monitor Module will cause both the server and itself to power up when the SMM is trying to power down.  The 638661-001 PBA (Fab 6) resolves this problem by gating the PWROFF#  signal and delaying the SMM power-down sequence.  The I/O panel screw hole was out of specification (the hole center located too close to the bend in the panel), causing difficulty in installation in some chassis, including the Columbus chassis.  All existing inventory was reworked to correct the mechanical issue, and all new PBAs will have a corrected I/O panel.  With this change, customers who purchase the SMM without the software must change to order code "SERVERMONOEMA."

New Schematic:  638664

New PBA Drawing:  638660

New Wire List (WL):  642392

New Progressive Rework Requirements (PRQ):  638392

ECO Number 5523094


Power-on Issue  Class I

Implementation Date: 5/95

If a Server Monitor Module Xtended Feature cable is installed to a Magellan or Columbus Intel system that is turned off, but plugged in, the system powers on.  The 635909-004  PBA resolves this problem by gating the HPWROFF#  signal.

Schematic updated to 639175.

PRQ updated to 638392.

ECO 5521971A


Fab 5,  May 95

Fab 5 was created to bury blue wires in Fab 3 and to add a PAL which corrects an occasional problem with read/write operations (see errata).


Fab 4-Never released

Will never be released.  This item listed for completeness and clarification.


Initial Release, Fab 3

PBA	630543-004

PBA drawing:	630167

Wire List:	635573

Schematic:	634966

PRQ:	635188

Mechanical:	620159


Software History

SMM Software Version 1.2, New Manual - Class I

SMM Software update version 1.12 Class III

SMM Software version 1.11  Class II

LANDesk Software, Version 1.1

Utilities and Diagnostics, Version 1.1


SMM Software Version 1.2, New Manual - Class I
SMM Software Version 1.2, New Manual − Class I

Current Implementation Date: 12/95

Many changes to the software will be made so new manuals will be released to support the software changes.  Software release adds support for NT servers and fixes a number of bugs in the NetWare software. Changes in the application include:

1.	Menu items have changed:  The menu items across the menu bar are now File, Tools, Configure, Window and Help.

2.	SMM 1.2 Console runs on NT:  The NT console portion of SMM 1.2 has been rewritten for the 32 bit environment of NT.  The NT console is native NT and is not NT running 16 bit Windows code.

3.	Intel Server Monitor agent runs on NT Workstation and NT Server:  The agent that supplies the information for the console can be run on NT Workstation as well as NT Server.  NT Workstation monitoring is the same as NT Server monitoring.  The agent can also be run on the same machine that the console is running on.  The agent is loaded as a service.

4.	Able to monitor both NetWare and NT environments from the same console:  The Windows 3.1x console and NT console have the capability to monitor NetWare 3.1x and  NetWare 4.1x servers as well as NT machines.  From the same location and in the same manner, consoles have the capability to monitor NT machines that have the NT agent loaded.  The NT console auto-discovers both NetWare servers and NT machines.  The Windows console auto-discovers NetWare servers, but requires manual input of  the IPX address of NT machines in order for the NT machines to be viewed in the sever tree.

5.	History gathering now an agent of the server:  Histories are now recorded by the server and history files are stored on the server.  The "Historian" shows up the same as NWXAGNT or SMMAGNT in the server tree that is displayed on the console.

6.	New Icons for improved GUI:  New Icons have been created for a better looking GUI.  Most notable changes are noticed with the servers that are listed and also functions of a module session. A new telephone icon has been added to the network view of the tree.  This icon is used to access modem functions for an-out-of band session with the Module.

7.	Two transport protocols supported:  Both TCP/IP and IPX are supported as the transport protocols for communicating information between server and console.  They can be used together, as well as separately.  H)  Event logging in NT Event Log:  Thresholds can be set up on the NT machine and if a threshold is exceeded an event is logged in the Event Log of the NT machine it occurred on.  To view this event, one must manually open the Event Log and look under the Applications option of View menu.  On this release, no alerting will take place on the exceeded thresholds for an NT machine.

Changes in Firmware Release 1.2

Support has been added for multiple alert destinations and scheduling (syntax only). This allows the user to configure the SMM to send alerts to several console workstations and/or pagers, and to assign days and times to each console or pager number. The initial implementation (rel 1.2) supports the command syntax for multiple destinations, however, it will allow only one console and one pager to be defined. The purpose of this limited approach is to provide for message (numeric-only) pagers, the full functionality will be supported in a future release.

2.	Added support for message pagers and assigning an SMM ID. Previous versions of the SMM firmware supported only alphanumeric pagers. It now supports "message" (numeric-only) pagers, as well. Also, it supports assigning an identifying number to each SMM (called the "SMM ID") to allow the receiver of a numeric-only page to determine which SMM originated the page.

3.	Added support for serial-line power control. This allows controlling the server's power via the serial line from the SMM's COM1 port. It supports the "Intelligent Power Module" from Server Technology, Inc. via the DTR pin on the COM port.

4.	"3.3 Volts" is now called "Auxiliary Power". The Feature Connector delivers a voltage line from the baseboard. Originally, this was defined to be 3.3V and the code and documentation reflected this. In fact, different baseboards deliver different voltage levels and this quantity is now be referred to as "auxiliary power". The file HOBBSRV.HDW on the server no longer refers to "3.3 Volts", instead it uses "Auxiliary Power".

5.	Report errors encountered in the shared memory interface messaging protocol. The SMM now reports checksum errors and invalid message types. An error code is be placed in the status register and the error is recorded in the SMM log.

6.	Added a fix for POST code capture. This is a change to the algorithm for handling POST capturing, necessitated by a hardware bug in the POST code capture logic. In previous releases, the SMM would occasionally report a POST code even though the server had not written one to the POST code port. This has been fixed.

7.	Removed floating point routines from ISR. There was one interrupt service routine that used floating point arithmetic. This was unsafe as the emulation routines are not re-entrant. This has been corrected.


SMM Software update version 1.12 Class III

Posted on Notes and the Bullitin Board 7/95, Not released to Manufacturing

This is a maintenance release of the firmware and one utility program  for the Server Monitor Module (SMM). It corrects a few minor bugs and to makes some enhancements requested by key customers. A complete list of changes is provided in the README.TXT file.


SMM Software version 1.11  Class II

Current Implementation Date: 7/95

Software update includes a bug fix for handling 3.3V monitoring on Fab 5 PBAs and beyond, and an increased pulse width for power cycling for compatibility with Columbus chassis.  Fixes a  problem in firmware if the server loses power in the middle of an in-band session. Fixes a problem with the SMM not powering itself off in machines that support power control. An enhancement allows the SMM to recognize when a PCMCIA modem has been inserted; this allows "hot plugging" of the modem.  Fixes the case when an intentional powerdown was done and the SMM reports the source of power as line (it should be battery). Changes the full names of the standard user accounts (root, alert) to remove spaces, since the user cannot include spaces:  changed "SMM Administrator" to "SMM_Administrator", and "SMM Alert Sender" to "SMM_Alert_Sender". Fixes the Agent to support NetFlex cards.  The redirection TSR corrects a problem when using Alt-key combinations. The current Rev 3 BIOS, HOBBIOS.BIN, is included.  The .CFG files for the SCU have the correct list of allowable IRQs.  The on-line help file has been updated to correct an ommision under the Troublehsooting subject.  Diagnostics has been updated to function on a system where the SMM has not been previously configured, to update the diagnostic help file SMMTEST.HLP for accuracy and clarity, to fix the trash flash routine, to update AUTOEXEC.BAT to not load certain unnecessary files, and to change MKBOOT.BAT to have path in front of the sys command. Added README file explaining the contents of this release and any differences in operation from previous releases.

ECO Number 5522832


LANDesk Software, Version 1.1

Initial Release 4/95

3 diskette set; only available with SERVMON product

ECO 5521604


Utilities and Diagnostics, Version 1.1

Initial Release 4/95

Available with purchase of either SERVERMON or SERVERMONOEM.

•	One MS-DOS Utilities disk

•	A Diagnostics disk

ECO 5521604


Literature History

Server Monitor Module Manual  Class II

Current Implementation Date: 6/95

Removed info on pages 3 & 16 about installing 1MB DRAMs for upgrading memory to 2MB, as this cannot be done.  Page 14-Removed EMI suppressor from external modem illustration as it is not required.  Changed connector designation on page 8 from G & H to J9 & J10 respectively.


QAN History

Temperature Cable QAN

Action Alert:  LANDesk® Server Monitor Module Battery Pack, Part 1of 3

Action Alert-Update:  LANDesk® Server Monitor Module, Part 2 of 3

Action Alert ( Update:  LANDesk® Server Monitor Module, Part 3 of 3


Temperature Cable QAN

QAN Number OR-2503

This QAN number may be seen on a label on the temperature probe, on the bag in which the probe ships, or on the shipping container.  It simply shows that the cable has been tested in a special screen.  The labels will be discontinued when the test process meets Intel quality levels.


Action Alert:  LANDesk® Server Monitor Module Battery Pack, Part 1of 3

August 25, 1995

Problem Description

A sustained short circuit on the board between the battery connection, or between traces from the battery connection, can result in a hazard:  rapid heating of the components involved; and if not stopped:  melting of the battery leads, fumes, potential burns, potential fire.  The areas of the board which may present the risk include the battery connector on the primary side of the board, and a few locations on the secondary side of the board between the edge of the battery pack and the gold fingers.

This hazard poses a risk of personal injury and property damage.

Affected Units: LANDesk® Server Monitor Module

SERVERMON

SERVERMONOEM

SERVERMONOEMA

Action

Intel has stopped all new shipments of the affected product until a corrective action is implemented.   You should stop all new shipments of the affected product until a corrective action is implemented.  In addition, you should notify your customers of this hazard and to advise them that they can significantly reduce the risk by unplugging the battery.

Intel will notify you of the corrective action as soon as it is determined and will advise you of product disposition instructions with the update of this action alert, which will be issued by September 1.

OEM Products and Services Division

Intel Corporation


Action Alert-Update:  LANDesk® Server Monitor Module, Part 2 of 3

September 1, 1995

Problem Description

A sustained short circuit on the board between the battery connection, or between traces from the battery connection, can result in a hazard:  rapid heating of the components involved; and if not stopped:  melting of the battery leads, fumes, potential burns, potential fire.  The areas of the board which may present the risk include the battery connector on the primary side of the board, and a few locations on the secondary side of the board between the edge of the battery pack and the gold fingers.

Unplugging the battery while the SMM or system is being serviced reduces risk to the operator significantly. Although recommended in the LANDesk Server Monitor Module Installation and User's Guide, this precaution regarding handling systems containing SMM could be overlooked.

We formally notified you of this situation through the "Action Alert Process" last Friday (8/25/95).  We requested that boards or systems containing them are not serviced without unplugging the battery.

Update

The corrective action we have taken is to incorporate an auto-resetting, in-line fuse (poly fuse) into the battery pack.  This solution limits the current to comply with the industry's most stringent safety requirements -  the Canadian Standards Association C22.2#950-93 safety standard.  We shall begin reworking all battery packs in our inventory as soon as the first fused units arrive from our vendor.   This is scheduled to occur this Friday September 1. All new builds will contain the fused battery, and all finished goods in our inventory will be reworked before being released for shipment.

Affected Units: LANDesk® Server Monitor Module

SERVERMON

SERVERMONOEM

SERVERMONOEMA

Action

If the unit is running in a system which has its access covers installed, the unit can remain running untouched until the replacement battery is delivered.   If there is a need to service the SMM or the system, follow these points:

•	take all standard technical safety precautions.

•	only qualified technical individuals should open the system.

•	unplug the system, and remove any jewelry including watches and rings before working in the system.

•	Unplug the battery on the card as soon as possible before removing the board from the system if accessable, or as soon as the board is removed.

•	Do not lay the board on a conductive surface.

•	Use extreme caution when testing if using probes or screwdrivers.

•	Keep loose screws or small metalic parts away from the board.

Remember that a board with the battery still plugged in is still live, even if removed from the system.

Customers who have taken delivery of SMM have three options for corrective action:

1.	Customers can replace the SMM battery pack themselves. Within two weeks, we can start shipping replacement batteries to all customers with appropriate rework instructions.  The battery is already implemented and documented as a field replaceable item.

2.	We can replace the batteries at our factory.  Return instruction would be provided in this case.

3.	Customers may request a pass-thru bulk shipment of batteries to enable  their respective accounts (VAR's etc.) to perform the battery upgrade.

The bottom line is that we want all batteries replaced as quickly as possible.   We should strongly urge all customers to call back and fix all units that have been deployed to their respective customers and to rework their stock on hand.

Intel Sales Representatives:  Please report all account corrective action requirements to Roberta Cobb via electronic mail.

OEM Products and Services Division

Intel Corporation


Action Alert ( Update:  LANDesk® Server Monitor Module, Part 3 of 3
Action Alert  Update:  LANDesk® Server Monitor Module, Part 3 of 3

September 15, 1995

Update

We are beginning to ship replacement battery packs for the LANDesk® Server Monitor Module to resolve the issues noted in the Action Alert issued on August 25, 1995. Replacement instructions are being shipped with the replacement battery packs, and also are attached.

All replacement packs and all shipments of the Server Monitor Module since September 1 incorporate an auto-resetting, in-line fuse on the battery. Reworked inventory will be marked with a label "OR2516" both on the board and on the shipping container.

All new or reworked battery packs are labelled with a new part number (617247-002).

The PBA number on newly-built Server Monitor Modules will change to 638661-101, and the Intel order codes will change to PSERVERMON and PSERVERMONOEMA. In addition to the battery change, the new code also reflects that product will now be built in Puerto Rico.

Action Required (updated from September 1 Action Alert)

Customers who have taken delivery of the Server Monitor Module have three options for corrective action:

1. Customers can replace the SMM battery pack themselves. We are now shipping replacement batteries to all customers with appropriate rework instructions. The battery is already implemented and documented as a field replaceable item.Customers can replace the SMM battery pack themselves. We are now shipping replacement batteries to all customers with appropriate rework instructions. The battery is already implemented and documented as a field replaceable item.

2. We can replace the batteries at our factory. Return instruction would be provided in this case.We can replace the batteries at our factory. Return instruction would be provided in this case.

3.	Customers may request a pass-thru bulk shipment of batteries to enable their respective accounts (VARs etc.) to perform the battery upgrade.

Users are reminded to follow safety instructions with the replacement packages in replacement of the

batteries.

The bottom line is that we want all batteries replaced as quickly as possible.   We strongly urge all customers to call back and fix all units that have been deployed to their respective customers and to rework their stock on hand.

Intel Sales Representatives:  Please report all account corrective action requirements to Roberta Cobb via electronic mail.

OEM Products and Services Division

Intel Corporation


Orderable Spare Parts List

629794	Replacement Cable Pack  (Xtended Feature cable, Xpress reset cable external thermistor cable)
617247	Replacement Battery Pack.


Novell Certification

8/24/95

Novell has completed certification of Server Monitor Module on NetWare 3.12 and NetWare  4.1. A copy of the "Tested and Approved" bulletin is on its way.


IPTL Tested Product List

The iPTL evaluated the server management board's compatibility with 11 Intel and five non-Intel computer systems using NetWare v3.12 and v4.1.  The testing procedure entailed assessing the performance of 36 different EISA, ISA and PCI adapters with the SMM, including 22 Ethernet, Token Ring and Asynchronous network interface cards, six disk controllers, and eight video adapters.  A total of 47 different configurations were tested.

The full report is posted on Notes.

INTEL SYSTEMS

SYSTEM NAME	CPU	MEMORY	AA/PBA (Intel)	BIOS (Intel)
401 Tower	486DX-25	8MB	504916-001	1.10.20.I0
403E Tower	486DX-33	32MB	515826-001	1.10.34.K1
Classic-E	486DX-33	4MB	612990-002	1.00.02.AB0
Classic-S	486DX2-66	12MB	611018-004	1.00.05.W0
Classic/PCI ED	486DX2-66	32MB	622104-100	1.00.03.AY0
Classic/PCI LP	486DX2-66	8MB	622115-100	1.00.03.AZ0
Preimere/PCI LX	Pentium 60	8MB	620517-5	1.05.BB0
Premiere PCI II	Pentium 100MHz	16MB	624318-001	1.00.12.AX1
Premiere/PCI Baby-AT	Pentium 66MHz	16MB	619771-005	1.00.09.AF2
Premiere/PCI LC LPX	Pentium 60MHz	24MB	622320-002	1.00.03.BC0
Xpress Deskside LX	Pentium 60MHz	16MB	614727-003	1.00.12.AM0
NON-INTEL SYSTEMS

SYSTEM NAME	CPU	MEMORY	AA/PBA (Intel)	BIOS (Intel)
ALR Flyer 32LCT	486SX-25	8MB	N/A	N/A
Ambra SX	486SX-25	8MB	N/A	N/A
AST Bravo	486SX-25	4MB	N/A	N/A
Dell 486D/33	486SX-33	8MB	N/A	N/A
Gateway 2000	486DX2-66	16MB	N/A	N/A


Approved Vendor List for Modems

No other user-installable parts for this product.

Modem Certification Process

The purpose of this plan is to establish a means to certify that modems of selected manufactures are compatible with the Server Monitor Module.  As identified at this time there are three major areas of evaluation that must be performed on each model of modem selected for certification process.  The three areas are summarized briefly below:

1.	Is the modem compatible with the Server Monitor Module product software and BIOS?  This includes both the firmware and Monitoring Console software.

2.	Does the modem degrade the operating temperature performance of the Server Monitor Module product?

3.	Does the modem degrade system level performance in the area of EMI emissions?

If one of the qualified modems listed below does not meet with your acceptance, Intel will qualify your modem of choice at a set upon agreement price with Intel and the requester.

Approved Modem Vendor List

U.S.

Manufacturer	Model	Name
Megahertz	CC3144	14,400/14,400bps PCMCIA FAX Modem
AT&T	3760-B1-261AA	Keep In Touch 14.4Data/14.4 Fax Modem
IBM	114HA	Data/Fax Modem 14.4Kbps/14.4Kbps with Integrated DAA
Intel	MBFM6831	Intel Faxmodem Data14.4/Fax 14.4
International

Manufacturer	Model	Name
IBM	FC3635	High Speed PCMCIA Data/Fax Modem


Definitions

LANDesk Server Monitor Module	A hardware/software server management solution.
Server Monitor	The software including the server NLMs and the Windows Console
Server Monitor Module (SMM)	The hardware portion of the solution
Alert Management System (AMS)	Software included in LANDesk which allows user notifications based on events
Server Monitor Management Server	The server where the hardware and the AMS database reside.
Server Monitor Console	The workstation from where you install the software
In-band	communication across the network
Out-of-band	communication via modem
Module Session	A method of access to the SMM from a Server Monitor Console
Parameters	information to be displayed, graphed, or monitored
Events	Occurrences on a LAN that you have configured criteria for, and when triggered, notify you through pre-defined actions.


Readme Files

Sample TO_DO.TXT File

NOV_TODO.TXT

SERVMON.TXT

README.TXT for Release 1.12


Sample TO_DO.TXT File

This file is generated during installation of LANDesk Server Monitor Module.  Your version may be different from this sample.  The file is found on the server under the SMM directory.

+================================================================+

                 Server Monitor 1.0 Installation

                  on Wed Mar 01 16:48:14 1995

+================================================================+

IMPORTANT: The following changes are necessary to complete your

Server Monitor installation.

For more information on each of these changes, see your

Server Monitor Setup Guide

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

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

      ---------- CRITICAL INFORMATION FOR USERS ---------

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

      Add the following line to your NET.CFG file.

      - IPX sockets=30

      - SPX connections=20

      Do not use EDIT.NLM to work with LDINIT.INI.

      A minimum of 12MB is needed on all Server

      Monitor Servers.

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

                 CONTENTS

     I.   Adding additional servers.

     II.  System file changes.

     III. Btrieve.

     IV.  NetWare requirements.

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

I.   To add an additional server to your console

     double click on the Additional Installation icon in

     the Server Monitor Group.

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

II.  The Server Monitor Setup modified the following files:

       AUTOEXEC.NCF(on the Server Monitor server)

       SYSTEM.INI (on the Server Monitor console)

       WIN.INI (on the Server Monitor console)

     The Server Monitor Setup did not modify the following files:

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

AUTOEXEC.NCF

>>  Check the location of the following lines in your

    AUTOEXEC.NCF file:

      REM *** BEGIN  Server Manager 1.0 Section ***

      SM_AUTO.NCF

      REM *** END  Server Manager 1.0 Section ***

    Make sure these lines do not conflict with your existing

    setup and NLM load commands.

>>  To load the NLM's, either restart your file server or at the

    server console, type the following command:

       SM_AUTO.NCF

SYSTEM.INI

>>  Check the following lines in your SYSTEM.INI file:

       drivers=lowdos.dll

       Outputto=NULL

WIN.INI

>>  Check the following lines in your WIN.INI file:

       [CoreServices]

        ClientDomain=<servername>

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

III. Server Monitor requires a Btrieve 6.10c installation on the

     Server Monitor Server and the Btrieve Requester TSR,

     BREQUEST.EXE, on the Server Monitor Workstation.

    >>  Check the version of Btrieve you have available in the

        SYSTEM directory on the Server Monitor Server.  If it

        is not currently up-to-date please follow the

        guidlines listed below.

    >>  If upgrading from Btrieve v5x:

          Checking for Extraneous Pre_Image files:

           If you have any extraneous .PRE files in your database,

           you must remove them before starting Btrieve v6.x.

           The following procedure explains how to check for and

           remove extraneous .PRE files.  You must have Btrieve v5x

           loaded before performing these steps.

           1. Using your existing version of Btrieve, open the

              Btrieve data file corresponding to the .PRE file

              in Exclusive mode.

           2. Close the data file.

           3. Any .PRE files that remain for the designated file

              after you perform Steps 1 and 2 are extraneous.

              Delete them at this time.

           4. Repeat steps 1 through 3 to find and delete any

              other extraneous .PRE files.

     (note: If you do not remove the extraneous.PRE files before

            installing Btrieve v6.x, file corruption may occur.

    >>  Unloading the earlier version of Btrieve:

          To unload an earlier version of Btrieve from a server's memory

          enter the following command at the server console or at a

          workstation running RCONSOLE:

              BSTOP

    >>  Starting Btrieve:

        After copying the new files, located in the BTRIEVE directory

        on the CD, at the server console or at a workstation running

        RCONSOLE enter:

              BSTART

  (NOTE: If you have any other applications using Btrieve you MUST

   run BSETUP.NLM to increase Btrieve's environment space sufficiently

   for all packages to run.  If your ASTART.NCF loads Btrieve it must

   use the parameters BSETUP.NLM placed in BSTART.NCF)

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

IV.  Read the NOV_TODO.TXT which can be found in the SERVER

     MONITOR (SMM) directory on the Server Monitor server

     or on disk 1.

+=================== END OF REQUIRED CHANGES ===================+


NOV_TODO.TXT

This file provides some additional information regarding the Novell installation on your workstation and server.  It is very important to follow this document.  This file is located on DISK 1 of the Server Monitor Module Installation disk.

This server monitoring application REQUIRES a complete matching set

of NetWare Windows files.  To ensure a successful setup you must use the

NetWare Windows files Novell previously called WINUP9, or newer.  If you

do not have NetWare Windows files satisfying this criteria, you must get

the following self-extracting files from CompuServe - GO NOVFILES (NOVFILES

is part of the Novell NetWire forum) - or from Novell's Internet ftp site, ftp.novell.com:

NWDLL?.EXE (? stands for the latest revision on CompuServe)

WINDR?.EXE (? stands for the latest revision on CompuServe)

NET33X.EXE

VLMUP?.EXE** (? stands for the latest revision on CompuServe)

**VLMUP?.EXE contains a matching set of LSL.COM and IPXODI.COM, which is

also critical to LDMS.  LDMS has been tested with the following sets of

LSL.COM and IPXODI.COM.  Any version of LSL.COM from the left column must

be paired with the corresponding version of IPXODI.COM from the right

column (the version information below was reported by Novell's VERSION.EXE

and/or NDIR.EXE utilities):

LSL.COM	IPXODI.COM

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

v2.00	v2.00

v2.01	v2.10

v2.02	v2.11

v2.05/2.06	v2.12

v2.12	v3.00

After obtaining the four .EXE files mentioned above, certain files must

be extracted and placed in appropriate directories on LDMS management

consoles and LDMS managed workstations.  When the .EXE files are expanded

several subdirectories will automatically be created - IT IS IMPORTANT TO

RETRIEVE FILES FROM THE CORRECT SUBDIRECTORY BECAUSE THERE ARE SOME

INSTANCES WHERE THE SAME FILENAME APPEARS IN MULTIPLE SUBDIRECTORIES.  We

recommend using an empty temporary directory when expanding each of the

files to avoid any possible confusion with existing files.  The rest of

this document explains exactly which files to retrieve and where they

should be placed.

Before placing any files referenced below in the \WINDOWS\SYSTEM directory,

delete any copies you may have in the \WINDOWS directory.

For all workstations

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

Expand NWDLL?.EXE	Retrieve the file ...	And place it in ...

NWDLL402\NWCALLS.DLL	\WINDOWS\SYSTEM

NWDLL402\NWIPXSPX.DLL	\WINDOWS\SYSTEM

NWDLL402\NWLOCALE.DLL	\WINDOWS\SYSTEM

NWDLL402\NWNET.DLL	\WINDOWS\SYSTEM

NWDLL402\NWPSRV.DLL	\WINDOWS\SYSTEM

NWDLL402\NWGDI.DLL	\WINDOWS\SYSTEM

OLDDLLS\NETAPI.DLL^^	\WINDOWS\SYSTEM

OLDDLLS\NWNETAPI.DLL^^	\WINDOWS\SYSTEM

OLDDLLS\NWPSERV.DLL^^	\WINDOWS\SYSTEM

        ^^If any of the three DLLs in the OLDDLLS directory ships from a

        vendor (for example, Windows for Workgroups 3.11 ships a newer

        NETAPI.DLL than the one included in OLDDLLS) use the newest version.

For workstations running NETX

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

Expand NET33X.EXE	Retrieve the file ...	And place it in ...

NETXWIN\NETWARE.DRV	\WINDOWS\SYSTEM

NETXWIN\NETWARE.HLP	\WINDOWS\SYSTEM

Expand WINDR?.EXE 	Retrieve the file...	And place it in ...

VLMDRVS\NWUSER.EXE	\WINDOWS\SYSTEM

For workstations running VLMs

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

Expand WINDR?.EXE	Retrieve the file ...	And place it in ...

VLMDRVS\NETWARE.DRV	\WINDOWS\SYSTEM

VLMDRVS\NETWARE.HLP	\WINDOWS\SYSTEM

VLMDRVS\NWUSER.EXE	\WINDOWS\SYSTEM

For all PCs (This will guarantee a matching pair of LSL.COM and IPXODI.COM)

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

Expand VLMUP?.EXE     Retrieve the file ...	And place it in ...

      VLMS\LSL.COM	NetWare drivers directory

      VLMS\LSL.MSG	NetWare drivers directory

      VLMS\IPXODI.COM	NetWare drivers directory

      VLMS\IPXODI.MSG	NetWare drivers directory


SERVMON.TXT

This file is decompressed during the software installation of Server Monitor Module.  The file resides on the server under the agent directory (SMM by default), and the file is also found on installation disk 1 in uncompressed format.  It contains the release notes for the for release 1.11.

Release Notes for LANDesk(TM) Server Monitor Module release 1.11

This document contains information about release 1.11 of the LANDesk

Server Monitor module software and firmware that was not available at the

time the LANDesk Server Monitor Module Installation and User's Guide was

published. You will find below notes on the usage of the this release, changes

to the firmware and known limitations in the product.

USAGE NOTES for SERVER MONITOR MODULE release 1.11

1.  If the server time is changed you must do the following to have that

    time reflected in the Server Monitor graphs:

    Unload CLIB.NLM

    Set the new time or timezone

    Reload CLIB.NLM

2.  In order to avoid time stamp problems in Server Monitor you must have the

    DOS environment variable set properly on the Server Monitor console.

    For example:

        SET TZ=MST7MDT

3.  Older versions of 3.11 CLIB.NLMs do not report some NetWare events.

    For instance, CLIB.NLM version 3.11d does not report an NLM load event.

    A workaround is to load a 3.12 version of CLIB.NLM on the 311 server.

4.  In order for a polling interval change to take effect visually you will

    need to close the graph and reopen it. This affects presentation of the data

    only. It does not affect the rate at which the information is written to the

    history file.

5. To reset a graphical parameter's maximum value back to its NetWare defaults,

   edit either the NW3AGNT.INI or NW4AGNT.INI as appropriate from the

   SYSTEM directory on the server. Change the "DataSaved=YES"

   line to "DataSaved=NO". Then unload and reload NW3AGNT.NLM or

   NW4AGNT.NLM.

6. It is possible at times for the NLM order in the "Loaded NLMs" parameter

   to be incorrect. If this should happen, only the last few NLMs will appear

   out of order.

7. The navigator window sometimes will only appear to display about 2/3 of the

   actual data.  This is a visual anomaly and does not affect the actual

   functionality of the application.

8. After getting a "Can't update parameter record" error message, the console

   is no longer able to update the list of thresholds.  You must close the

   Server Monitor console and restart the application before you configure any

   more alerts.  None of the previously configured alerts will be affected.

9. Displaying history file data graphically appears to fail when the value being

   displayed is zero (0). This is due to the graph line being drawn on the

   boarder of the graphical window. You can make zero values visible by reducing

   the display resolution to a very small value.

10. The SMM no longer complains if the console work station does not have a

    printer installed when launched. In previous versions an error was generated

    if no printer was detected when SMM was invoked. However, in order to print

    from SMM, a printer must be installed prior to launching SMM.

11. If the history file is corrupted the application will display a totally

    gray screen instead of the expected graph window.  Currently there is no

    way to recover corrupted history files.

12. On various types of multi-processor machines, Server Monitor may report

    the CPU type incorrectly.

13. When loading the NW4AGNT.NLM you may encounter a message indicating that

    there are few "Out dated API calls".  You may ignore this message.  The

    application will run normally despite the error message.

14. Using the EDIT.NLM can corrupt the NW3AGNT.CFG (or NW4AGNT.CFG) file. This

    prevents the NetWare Agent from displaying information about the operating

    system. The solution is to expand the NW3AGNT.CFG (or NW4AGNT.CFG) file

    from the installation disk using the "expand" command.

CHANGES IN SMM FIRMWARE:

1.  "3.3v" monitoring is fixed. Previous releases of the SMM software did not

    account for a change to the SMM card's voltage monitoring circuitry.

2.  SMM now controls power cycling in the Columbus chassis. Previous releases

    of SMM used only a 1 msec pulse, the prescribed width for the Magellan

    chassis power control.  The pulse width has been increased to 5 msec for

    Columbus.

3.  SMM release 1.11 now terminates the login session correctly in the event the

    server crashes in the middle of an in-band session.

4.  SMM now recognizes when a PCMCIA modem has been inserted without requiring

    the SMM to be reset; this allows "hot plugging" of the modem.

5.  SMM now reports the source of power as "battery" when an intentional power

    down is done. Previous releases of SMM incorrectly reported "line."

6.  The full names of the standard user accounts (root and alert) no longer

    include spaces. Spaces in account names are not permitted.

    "SMM Administrator" is now "SMM_Administrator";  "SMM Alert Sender" is now

    "SMM_Alert_Sender."

7.  SMM now correctly powers itself off.

8.  SMM release 1.11 includes the correct BIOS binary; the BIOS in release 1.1

    is out-of-date.

9.  The redirection TSR corrects a problem with Alt-key combinations.

10. The .CFG files for the SCU now contain the correct list of allowable IRQs

    and DMA channels.

11. The SMM Agent now supports NetFlex network adapter cards.

CHANGES IN SMM DIAGNOSTICS:

1. The help file SMMTEST.HLP has been updated for accuracy and clarity.

2. The diagnostics program now correctly initializes an SMM card that has not

   been previously setup.

3. The Trash Flash utility is fixed.

4. The SMM installation procedure's modifications to AUTOEXEC.BAT longer cause

   certain unnecessary files to be loaded.

5. Path to MKBOOT.BAT is now defined before the sys command.

KNOWN LIMITATIONS

1. The "Get DMA Screen Image" does not function unless ISA video is being used.

   This is due to an error in bus mastering in systems with PCI video.

2. SMM software cannot be installed directly over a previous installation. Use

   the uninstall command before installing the SMM version 1.11 software on

   systems with a previously installed. See LANDesk Server Monitor Module

   Installation and Users Guide for more information.

3. SMM continues to report volumes as mounted even after they have been

   dismounted. Volumes mounted while SMM is running are not shown as mounted.

4. On NetWare version 4.1 with outdated LAN drivers, namely EXP16.LAN version

   2.1 or earlier,  the video RAM base address was reported incorrectly. The

   incorrect address would affect the  "Get Status" and "DMA Screen Image"

   options of the "Module" menu of the SMM Console. We recommend that you

   upgrade to the most current LAN driver that is certified for NetWare.

   However, you can also solve the problem by loading MSM.NLM before the

   SMMAGNT.  Do this by placing the command

        load MSM

   before the command

        load SM_AUTO

   in your AUTOEXEC.NCF file.

5. The description in the LANDesk Server Monitor Module Installation and Users

   Guide for setting up the diagnostics incorrectly indicates that you should

   "sys" the diskette in drive A. Instead, insert the diagnostics diskette in

   drive A and type:

       A:

       MKBOOT.BAT

   Also, RAMDRIVE and HIMEM must be present on the system running MKBOOT.BAT.

6. While "3.3v" is the name of one voltage parameter, other voltages (notably

   5.0v) may actually be monitored and reported depending on the SMM's host

   system.

7. Although the Root and Alert users' privileges can be changed, they should not

   be altered. This will be disabled in future release.


README.TXT for Release 1.12

Server Monitor Module Release 1.12

Summary:

    This is a maintenance release of the firmware and one utility program

    for the Server Monitor Module (SMM). It corrects a few minor bugs and

    to makes some enhancements requested by key customers. A complete list

    of changes is given below.

Files that have changed:

    HOBBAPP.BIN   - Server Monitor Module firmware

    HOBLOCAL.TXT  - Server Monitor Module error messages text

    SMMLOAD.EXE   - MS-DOS program to download firmware to SMM

    !INT0110.CFG  - SCU configuration file

    !INT0210.CFG  - SCU configuration file

    !INT0310.CFG  - SCU configuration file

Installation:

    1. With the server running, from a connected workstation, copy the files

       HOBBAPP.BIN and HOBLOCAL.TXT to the server into same directory as the

       LANDesk Server Monitor NLMs reside. This is typically \SYSTEM. Doing

       this will replace the previously installed SMM firmware and error

       message file.

    2. On the workstation, run the LANDesk Server Monitor Console. Choose the

       server that is to be updated. Initiate a Module Session and log into

       the Server Monitor Module.  From the "Module" menu, choose "Update

       Module Software." This opens a dialog box. Choose "Application" and

       press "OK". This will copy the new application to the Server Monitor

       Module; it will take about three minutes to complete.

    3. If you have previously copied the SCU configuration files or SMMLOAD.EXE

       onto your system, you can replace these by copying them from the new

       release.

Changes:

    1. A delay has been added in the SMM reset sequence to allow a slow

       PCMCIA modem to complete its reset before the SMM attempts to use

       it.

    2. When the SMM finds a modem on the serial line or PCMCIA port, it

       now sends an AT command to set the modem up to return "OK" result

       codes. The SMM expects these results for proper operation.

    3. All occurrences of the server's power coming on and going off are

       now logged in the SMM-resident log. Previously there were some

       cases where this was not being logged.

    4. It is no longer possible to change the privileges for users

       "root" and "alert". Doing so allowed the user to put the SMM into

       a state where the user was unable to manage the user list.

    5. Voltage monitoring is now delayed for a short period after server

       power-up. For servers that have a slow power rise time, this

       avoids having the SMM deliver spurious low voltage alerts.

    6. The definition of "zero" for each of the voltage signals (+/-5 V,

       +/-12 V) has been increased. The SMM recognizes that the server

       power is off when all four voltage channels are "zero". The

       definition of "zero" for these lines were 10% of nominal. This

       has been changed to 30% of nominal, to avoid possible misreadings

       due to spurious voltages induced into the system.

    7. A bug that caused spurious "low voltage" alerts when the server

       was quickly, repeatedly power cycled has been fixed.

    8. The utility program SMMLOAD, which is used to manually download

       firmware to the SMM, has been enhanced to provide better error

       reporting.

    9. The SCU .CFG files have been edited to correctly reflect the

       possible selections for the shared memory area, and to improve

       the help text.


Frequently Asked Questions

Troubleshooting

Questions about Hardware

Questions about Installation

Questions about Software


Troubleshooting

If you are unable to log into the Module, there are typically three reasons for this:

•	The Module is attempting to deliver an out-of-band alert or pager message.  The Module may take several minutes to do this, since it retries three times for each alert.  The Module Session Window will report "SMM busy..." when you attempt to log in.  Wait for a minute or two and try to log in again.

•	The Module software is in the process of being updated.  While in the update process, the Module does not respond to login attempts.  The Module Session Window reports, "Trying to Reach Server Monitor Module", three times then closes the window.  The update process requires about 3 minutes.  Wait for 3 minutes, then try to log in again.

•	The Module software is corrupted.  The Module itself should recognize this problem and require that the SMMAGNT download a new copy of the software to the Module.  In rare circumstances, this may not happen.  You can force the SMMAGNT to download new software onto the Module by manually loading the SMMAGNT from the NetWare command line using the switch -d.

If the SMMAGNT.NLM cannot synchronize (establish initial communication) with the Module, it resets the Module and attempts to synchronize again.  If the second attempt fails, the SMMAGNT.NLM displays a message on the server console and unloads.  This may happen for one of two reasons:

•	The Module board is not correctly configured on the server.  On EISA systems the Module is configured through the EISA Configuration Utility (ECU).  Run the ECU and ensure that the Module card is configured in such a way that its interrupt, DMA channel, and shared memory address do not conflict with other cards.

•	The software on the Module is corrupted.  The Module itself should recognize this problem and require that the SMMAGNT download a new copy of the software to the Module.  In rare circumstances, this may not happen.  You can force the SMMAGNT to download new software onto the Module by manually loading the SMMAGNT from the NetWare command line using the switch -d.

If you are able to use DOS DEBUG, here are some other troubleshooting tricks:

A) to see if shared memory is enabled between the SMM and the system:

-o 110 6

-i 111

system should respond with FF (last three bits set).  If the second bit is 0, then shared memory is not enabled.

B) to see if the card is properly configured:  (need to know which address you assigned to the card, for this example cc000)

-i cc000

if system responds with 00, the card is properly configured.  If system responds with FF there is something wrong with the configuration

C) to see if the SMM is responding :

-o 110

If response is 96, the SMM is responding at this port.  If not, try reading ports 210 and 310, one of these should respond with 96 indicating where the SMM is configured.


Questions about Hardware

How do I get the remote temperature to work?

The reset cable doesn't reach on my AltServer!

Why is the "DMA Screen Image" not working?

Why can't I access the on-board PCI video area from the Server Monitor module?

The modem disconnected but the session didn't end.  What's wrong?

I should be able to access the features such as 3.3V monitoring, but they don't appear in the Parameter Window, why?


How do I get the remote temperature to work?

First, make sure the remote temperature sensing cable is plugged in properly.  Then, edit the HOBBSRV.HDW file (originally located on the Utilities diskette, stored on the server in the \SERVER directory).  In this file, change:

"Remote Temperature Probe = 0" to "Remote Temperature Probe = 1".


The reset cable doesn't reach on my AltServer!

The reset cable is not required for the AltServer.  The AltServer and the Xtended Xpress system use the Xtended Feature Cable, and the reset connection is included in that ribbon cable.


Why is the "DMA Screen Image" not working?

Updated 7/95

The "DMA Screen Image" is a feature available after initiating a module session, and it is a choice under the Module menu.  This feature is used to capture a snapshot of the server's video screen, but no keyboard/video interaction is possible while this feature is active.   A failing image will be a full black screen,  a full white screen, or screen of either white or black with the opposite color as a border.  The Server Monitor Module will capture only ISA video; this feature is not supported when the server is using PCI or Local Bus (VESA) video.  If the system is running with ISA video, then  it can capture video from the server's video memory by functioning as an 8-bit ISA bus master.

This facility has been tested on many different EISA and ISA systems, all with ISA or EISA video.   The cause of the failure is under investigation.   Problems have been noted  on the Intel ALTServer, and the DMA Screen Image fails, even with an ISA video add-in card installed.

There is currently no workaround other than to use the View Console feature instead.

D-1789, D-1813


Why can't I access the on-board PCI video area from the Server Monitor module?

The only way you can access the video area from the Server Monitor module is if you have a video controller connected to the ISA bus.  The Server Monitor Module cannot access the video area for video controllers not connected to the ISA bus.  This includes the AltServer system.


The modem disconnected but the session didn't end.  What's wrong?

During an out-of-band session, the modem must remain installed in the Server monitor module.  If the PCMCIA modem is unplugged during the session, the session will not get closed.

(d1707)


I should be able to access the features such as 3.3V monitoring, but they don't appear in the Parameter Window, why?

Check your Feature Connector.  If it is not plugged in at both ends, the software will not display the parameters available with this connection.


Questions about Installation

After I upgraded my software, Get Status still showed the old revision.  What happened?

I want to configure the Module, but when I try to log in, it asks for user and password. Is there a default?

Can I shadow the dual ported RAM on the Server Monitor Module?

I have an ISA system. How can I determine which Base I/O Port  address I can use?

I have an ISA system and I need to load the Server Monitor BIOS and application. How do I unlock the Server Monitor to do that?

When I insert my Server Monitor Module into my ISA system, it hangs my system. What's wrong?

The NOV_TODO.TXT says to use WINUP9. Where do I get it?

I moved my Server Monitor Module to a new server but the configuration is wrong.  What happened?

How do I configure my pager?

My paging service does not require a password, but SMM does.  Will this work?


After I upgraded my software, Get Status still showed the old revision.  What happened?

When you upgrade software, you need to do three things.  First, "uninstall" the old software by running UNINSTAL.EXE from the network SMM directory (SYS:SMM, by default).  This is described in detail in Chapter 2 of the Installation and User's Guide.  Secondly, run Server Monitor Setup to install the new software as was done for the very first installation.  This is also described Chapter 2 of the guide.  Finally, force an update to the BIOS (if necessary) and the application  by starting a Module Session (in band) and choosing the option to Upgrade Module Software.  This step is described in Chpater 6 of the guide.


I want to configure the Module, but when I try to log in, it asks for user and password. Is there a default?

Yes.  The module comes with a default user account through which you can set up other accounts on the Module.  This account name is "root" and its password is "calvin".  This is documented in the Installation and Users Guide, on page 6-11.


Can I shadow the dual ported RAM on the Server Monitor Module?

No. Shadowing must be disabled for the 8K shared memory area.


I have an ISA system. How can I determine which Base I/O Port  address I can use?

Start at port 110, 210 or 310 and read the next 8 ports. If you  read 0FFH at each port, those ports are probably not used by anything else.


I have an ISA system and I need to load the Server Monitor BIOS and application. How do I unlock the Server Monitor to do that?

Write A1H, B2H, C3H to the BASE I/O address. Then read the  BASE I/O address + 1. It should read 96H. The Server Monitor Module is unlocked at this point and you can load the BIOS and application software.


When I insert my Server Monitor Module into my ISA system, it hangs my system. What's wrong?

You probably have a resource (I/O port, memory, IRQ) conflict. Use a memory manager to exclude the 8K shared memory area. Be sure the BASE I/O port address is OK. Use the procedure in the answer to question 2 to check this, then assign the Server Monitor  Module to another interrupt level.


The NOV_TODO.TXT says to use WINUP9. Where do I get it?

If you FTP to Novell, the WINUP9 files were located in directory:  pub\netwire\novfiles.  This was accurate at the time of writing, but is subject to change at any time by Novell.  The files are pulled individually, not as one compressed update.


I moved my Server Monitor Module to a new server but the configuration is wrong.  What happened?

Because the Server Monitor Module has battery backup, be sure to allow the module to shut down by unplugging the board and waiting about 1 minute.  Then unplug the battery backup, wait a few minutes, replug in the battery then continue with your installation into the new server.


How do I configure my pager?

The pager configuration is on a tab under "Configure Module".  There are a few items which might be confusing.  The Server Monitor Module follows the Telocator Alphanumeric Protocol (TAP).

•	Phone number is the phone number of the paging service.

•	The Service ID comes from the paging service. It's part of TAP.

•	The telepage password 000000 works for the way Telepage implemented  TAP. This password is assigned by the paging company.

•	The pager number is the actual device id of the pager itself.

•	To test the paging service, you cannot have the network connected or  an out of band connection available. Paging is a last resort. The  best way to test it is to boot the server machine, but don't start the server. Make sure an event is configured for loss of power and pull the power cord on the server.


My paging service does not require a password, but SMM does.  Will this work?

7/29/95

If your paging service follows the TAP standard, but does not require a password, use any password.  For example use "000000".  The paging service will ignore the password field.


Questions about Software

How many graphs can I have open at one time?

How do I restore a corrupt AMS database?

After I log in to the SMM, I get the message 1106.  What does this mean?

What does error message 600 mean?

When does the SMM actually call out to a pager?

How do I run SMMLOAD?

How do I configure voltage and temperature events?

How do I configure an voltage event to tell me which voltage went over the threshold?

Why does my server seem to hang when I restart it over an Out-Of-Band session?

Why does my Server BIOS version report Unknown?

Why can't I save events that I selected?

Why are my event times different from actual time?

Why does my software update restart?

I'm using NetWare 4.1 and while loading SMMAGNT.NLM, I get an error message.  What should I do?

How do I interpret POST codes?  There are errors listed there that don't seem to be valid.


How many graphs can I have open at one time?

8/95

There is a limit of 20 graphs that can be opened at one time.  If 28 graph windows are opened, a message "Unable to allocate timer" message appears.  More graphs can be opened, but another message may appear "Unable to register with the Server.  Make sure it is still up and try again."  If SMM is now closed, a General Protection Fault (GPF) may occur.

D-1730


How do I restore a corrupt AMS database?

7/31/95

This database cannot be restored.  To prevent loss of data, if you have an event which resets the server, add another tool before the reset which copies the database to a backup.

D-1876


After I log in to the SMM, I get the message 1106.  What does this mean?

If you see the message "1106  Requested Data does not exist," the Console is reporting that it tried to find information but was unable.  The most common cause is that the SMM's modem or pager is not yet configured.

7/12/95


What does error message 600 mean?

The message is "600 - Bus request failure" indicates that the SMM was unable to gain access to the ISA bus.  The user should first ensure that the SMM has been properly installed and configured. In particular, the assigned DMA channel must not be used by any other device, and it must have its mask cleared and configured in cascade mode. For EISA systems, this is all done by the EISA Configuration Utility, or ECU. On ISA systems, this configuration may be done by a setup program, or may be done by the SMMAGNT.NLM through command line parameters. If it is confirmed that the SMM is properly configured and the error message persists, it is a reasonable conclusion that it is not possible for the SMM to act as a bus master on that system.

 (d-539, d-1621, d-1643)


When does the SMM actually call out to a pager?

The AMS will use any means to call out other than the SMM's pager first.  If it cannot find a path to an Alert Converter somewhere, then the last thing it will try is a call to the pager.  There is a good decription of the steps in the manual on pages 4-3 and 4-4.


How do I run SMMLOAD?

If you want to force a BIOS or application update to the SMM from the server, boot the server and go to a DOS prompt.  Run SMMLOAD here. The file is originally located on the Utilities disk. If you want to update BIOS or the application over the network, use the utility within the LANDesk software application.  Details are in Chapter 6 of the manual.


How do I configure voltage and temperature events?

Voltage and temperature events  are configured differently from the other events, because they have both high and low thresholds and because they depend on the SMM for hardware monitoring.  Here's a chart describing some of the differences in configuring a graphical event for a NetWare and configuring an event for the SMM Agent.

Process	NetWare Graphical Parameter	SMM Parameter
Example:	CPU Utilization	+12V
How to Set Thresholds	A) Open Graph B)  Choose menu item Configure|Event	A) Log into Module Session (opening graph NOT required) B) Choose menu item Configure| Server Monitor Module
	C)  set informational, warning, and critical thresholds	C) Tab to either Temperature or Voltage.  For temperature set high, low and rate-of-change thresholds; for voltage set high and low thresholds
	Can also drag and drop bars within the graph	Can only change as listed in C) above
		Note:  SMM status graphs are for real-time view and history only.
How to Configure an Event	From open graph, choose Configure|Event	Graph not needed.  Double Click on the event under the SMM Agent's Module Events
	Choose the Select button Select a pre-configured event from the event list, or create a new event.	same same
For More Details	See chapter 4 of the User's Guide	See Chapters 6 and 4 of the User's Guide


How do I configure an voltage event to tell me which voltage went over the threshold?

If you use a broadcast message or message box as the tool activated when the voltage event occurs, add the argument "Description" to your message.  For example, if you configure an event for low voltage, and the +12V line drops, your message will include "Channel: Plus 12 Volts".  Another way to find out is by examining the AMS Event Log.  In that log, the decription will include the details of which voltage caused the event, and under the heading "Loacation" you will see the actual voltage measured as a value (for example, "Value: 10.490")


Why does my server seem to hang when I restart it over an Out-Of-Band session?

When you are using the SMM in an out of band session, and the server is down, you must use the DOS-based SMMTSR to allow console redirection before the server comes back up.  The SMMTSR needs to be loaded as the first item in your AUTOEXEC.BAT so that you can see the screens and use your remote keyboard.  Secondly, when the server is brought back up, the console redirection is handed off from the SMMTSR to the agent.  In order to perform this cleanly, SM_AUTO must be included in your AUTOEXEC.NCF.

If SM_AUTO is not included in your AUTOEXEC.NCF file, the console redirection will appear to hang while the server is coming up.  A portion of the NLM loading will show on your remote screen, then updates will cease.  If you check the monitor at the server, however, the process will have completed.


Why does my Server BIOS version report Unknown?

Under investigation.


Why can't I save events that I selected?

When configuring events, the AMS must be active.  Make sure it is running first.


Why are my event times different from actual time?

The server and the workstation must both be synchronized, and they must also have the correct time zone in the run-time library.  See the SERVMON.TXT release notes.


Why does my software update restart?

Once a software update to the Server Monitor Module has begun, the server monitor must be left alone until the update is complete, from 1-5 minutes.  Any agent contacting the Server Monitor Module during that time will cause the update to begin again.

D-1795


I'm using NetWare 4.1 and while loading SMMAGNT.NLM, I get an error message.  What should I do?

If the message is: "Server-4.10-3.0:  This module used 3 outdated API calls - you should upgrade to a newer module when it becomes available", then you should ignore the message and the system will work properly.  This message is given when some APIs are imported.  Many of Novell's own NLMs and many commercial NLMs also cause this message to be displayed.


How do I interpret POST codes?  There are errors listed there that don't seem to be valid.

Updated 7/95

The POST codes must only be examined and interpreted for the most recent server boot and for the Power On Self Test period only.  The SMM captures all writes to port 80h.  During POST, the values written there are codes for the state of the machine as it is booting.  These values are then cross-referenced in a table to define the functions performed.  Once the boot process is complete, the system may continue to use port 80h, but the values written there have no correlation to the POST code table.  Since the SMM captures all writes to port 80 and decodes them using the POST cross-reference table, the results may look as though the system is failing even though the system is functioning properly.

A second cause of inproper codes being recorded in the log is due to the different usage of the AEN signal in EISA vs. ISA systems, the AEN signal is ignored during POST code capturing.  It is therefore possible to capture false POST codes.  This is because DMA transfers which use the same memory address as the POST code port I/O address will appear to be I/O write cycles.  In practice, this does not occur very often.

The POST code window should only be interpreted for the most recent boot, and only during that boot process.  There is also errata associated with this feature.  d-1510


Known Errata

see also README Files

Related Topics:

Hardware Errata

Console - Related Software Errata

Modem-related Software Errata

AMS and LANDesk-related Software Errata

Resolved Errata


Hardware Errata

Spurious Post Codes

Remote power cycling not supported on Xtended Xpress

Server Monitor Module doesn't seat properly in a Classic/PCI Low Profile or Premiere/PCI Low Profile system


Spurious Post Codes

8/95

Problem:  At any time during POST or afterwards, a spurious POST code may be captured in the POST code log.  The most probable values are: 01, 03, 07, 0B, 0F, 13, 17, 1B, and 1F.  The problem is intermittenent.  It is due to a hardware issue where inproper interrupts are generated on the SMM board.

Status:  A Software fix will reduce the number of spurious post codes; this will be included in release 1.2.

D-1870


Remote power cycling not supported on Xtended Xpress

Status:  Under investigation.


Server Monitor Module doesn't seat properly in a Classic/PCI Low Profile or Premiere/PCI Low Profile system

Problem:  The module's serial port interferes with the chassis when installing the board into either the Classic/PCI or Premiere/PCI low profile systems.

Status:  under investigation.  d-1544


Console - Related Software Errata

HOBBPOST.TXT line length limit

Setting server time loses connection

Downing the server during an application update

Configure | Users dialog table titles error

Closing tab dialog from upper-left button hangs

Console login window allows only 1 try to login.

Reconfiguring SMM parameter thresholds not reflected in existing graph

Console tries to logout from SMM when no session current

Cannot warm reboot or reset both SMM and Server at the same time

New window placed too low on screen

Odd characters in AMS log for SMM events

Event alert selections not saved

Redirection, reverse video bars incorrect

Log In and Log Out functions still available after logging out.

Focus wrong after adding user


HOBBPOST.TXT line length limit

8/95

Problem:  Each line of the HOBBPOST.TXT  must be 75 characters in length of less.  If not, an error message will be reported when SMMAGNT loads:  "Missing value in line <x> of SYS:SYSTEM/HOBBPOST.TXT."  The error message also gives the wrong line number and and the wrong condition.

Status:  under investigation.

D-1816


Setting server time loses connection

8/95

Problem:  If the server's time is set through the remote module session ("View Console" with "Pass through system keys" option set) the session is ended. The error message displayed indicates a lost module connection.

D-1867


Downing the server during an application update

8/95

Problem:  During an application update, if you down the server, SMMAGNT.NLM continually reports, "Unable to open update fileSYS:SYSTEMHOBBAPP.BIN".

If you down the server just as soon as the first "Application update" message comes from the SMM:

    Error reading file:  SYS:SYSTEMHOBBAPP.BIN

    Unable to open SYS:SYSTEMSMMAGNT.CFG

    Unable to complete initialization.

Workaround:  Do not down the server until the application update has completed.

9/95 Status:  Will not be fixed.

D-1818


Configure | Users dialog table titles error

Problem:  Under the Configure | Users, the titles on the table are "Rights" and "User".  The display actually shows "User" and "Full Name".  (d-1736)


Closing tab dialog from upper-left button hangs

Problem: If you open a console session, then open Configure Module, be sure to close that dialog box using the Close button.  If you try to close that dialog box using the "-" symbol in the upper left corner, the workstation will hang.

Status:  under investigation.

D-1802


Console login window allows only 1 try to login.

Problem:  When trying to log in to the console via an out-of-band session, you will only get one chance to log in.  If the password is mistyped, you will have to dial in again.

9/95 Status:  will be fixed in release 1.2.

D-956


Reconfiguring SMM parameter thresholds not reflected in existing graph

Problem:  If you open a graph window for an SMM parameter (such as temperature), then log into the Server Console and run Configure thresholds, the new thresholds in the original graph are not automatically changed.

9/95 Status:  will be fixed in release 1.2.

D-1011


Console tries to logout from SMM when no session current

Problem:  If the SMM is already busy when you try to initiate a module session, the window will report "SMM busy..." but when you close that window a message "Logging out from SMM" will appear (even though you never logged in).

9/95 Status:  Will be fixed in release 1.2.

D-1797


Cannot warm reboot or reset both SMM and Server at the same time

Problem:  In a console session, under Reset, there are two checkboxes for which device to reset.  If you click both device Module and device Server, the reset or reboot will not occur and you will get an error message that this feature is not available at this time.  Click one box or the other and the function will work properly on the device selected.

Status:  under investigation.

D-1834, D-1835


New window placed too low on screen

Problem:  A new status window is often placed too low in the server manager console window.  The window must be moved to see all of it.

9/95 Status:  Will not be fixed.

D-1257


Odd characters in AMS log for SMM events

Problem:  The AMS log for events generated by the SMM include heavy vertical bars.

Status:  under investigation.

D-1436


Event alert selections not saved

Problem:  Alert selections are not saved unless you click the "save settings on exit" option under File menu.

9/95 Status:  Will not be fixed.

D-1439


Redirection, reverse video bars incorrect

Problem:  If you log into the SMM Console and start redirection, choose or type Load Monitor.  Then use the cursor keys to move to System Modules, and use the cursor keys to move through the list of modules, the reverse video band used to highlight the selected item will split, and only a portion of the highlight will track with the cursor.  This also occurs under "Tracked Resources."  The portion of the highlight that moves with the cursor indicates the current selection.

Status:  under investigation.

D-1801


Log In and Log Out functions still available after logging out.

Problem: If you try to initiate an SMM console session, but the SMM is busy, you will get an error message.  When you close out the window, a message will be displayed "Logging out of Console" even though you never logged in.

Status:  under investigation.

D-1811


Focus wrong after adding user

Problem: In an SMM Console | Configure Console session, after adding or modifying a user the window focus returns to the Main Menu instead of the Configure Console session.

Status:  under investigation.

D-1803


Modem-related Software Errata

A disconnected line does not end a session

When dialing, the time left for disconnect is not accurate.


A disconnected line does not end a session

Problem:  Establish an out-of-band session; then unplug the modem from the SMM. The Console does not end the session, instead, it times out on every command without notifying the user of the connection loss.  Be advised that unplugging the PCMCIA modem from that SMM while a session in in progress will cause a loss of connection, without the Console closing down the current session. The user will then have to manually terminate the session using the "Logout" menu selection.

9/95 Status:  Will be fixed in release 1.2.

D-1808


When dialing, the time left for disconnect is not accurate.

Problem:  When dialing the modem, a small window pops up the specified the amount of time left for a disconnect.  If no carrier is detected within the specified time, the modem disconnects.  The timer may have as much as 30 seconds shown when the message "no carrier detected" is displayed and the disconnect occurs.

Status:  under investigation.

D-1796


AMS and LANDesk-related Software Errata

No line appears in graph if actual reading greater than warning

Need a mouse to install

Alert Converter delivers junk message when server is powered down

TEST of Broadcast Message doesn't always work

AMS Event Log can only select one event at a time

LANDesk Management Suite interaction with SMM

Volumes parameter is not updated real-time

Maximizing one window maximizes all

SMM software installation tries to get files from network.

Dirty Cache Buffers Graph Confusing

LAN Drivers (i) info is IRQ = A

AMS Log and statistics don't match


No line appears in graph if actual reading greater than warning

9/95

Problem:  When displaying a graphical parameter, if the actual value is greater than or equal to either the warning or the critical value, the actual line on the graph is hidden under the drag and drop line.

Status:  under investigation

U-2


Need a mouse to install

8/95

Problem:  While installing the SMM software without a mouse a problem occurrs near the end. The screen that shows which system files would be modified would not toggle the checkboxes with a space or any other key.

Status:  under investigation.

D-1815


Alert Converter delivers junk message when server is powered down

8/95

Problem:  The Alert Converter may send dialogs with random characters under the following scenario: Server is up, running LANDesk NLMs. Console is running Windows, attached to server, Alert Converter running. Using Out-of-Band Server Monitor, log into SMM, select "Restart - Powerdown Server". Server powers down. Alert Converter puts up a dialog containing junk characters. Sometimes, the woskstation reboots, sometimes it just closes the dialog.

D-1819


TEST of Broadcast Message doesn't always work

Problem:  When setting up an alert of a broadcast message, the TEST sometimes fails.  Here's a scenario:  Create an event (for example Privilege Violation).  For the events, select broadcast message.  Tell it to send to Supervisor (assuming you are logged in as Supervisor), and make up a message. Click OK.  Hit TEST button.  It doesn't always work.

D-1873


AMS Event Log can only select one event at a time

8/95

Problem:  The "AMS Event Log" does not allow the common Windows function of using <ctrl> to select multiple choices.

D-1807


LANDesk Management Suite interaction with SMM

7/26/95

Problem:  When using both Server Monitor Module and the LANDesk Management Suite, the tool button inside LANDesk Management Suite labelled Server Monitor (first tool button on the second line) operates, but it uses down-rev version of the SMM software.  In addition, if LANDesk Management Suite was installed after SMM, then the HOBBAPP.BIN file may be very old and cause unexpected operation if an application update occurs.  An application update will automatically occur if the SMM diagnostics run.

Workaround:  Make sure to copy the later version of HOBBAPP.BIN to the System directory after installation of LANDesk Management Suite.  Or, install LANDesk Management Suite first, then Server Monitor Module.

9/95 Status: Will not be fixed.

D-1872


Volumes parameter is not updated real-time

June 1995

Problem: SMM continues to report volumes as mounted even after they have been dismounted. Volumes mounted while SMM is running are not shown as mounted.

9/95 Status:  Will be fixed in version 1.2

D-1529


Maximizing one window maximizes all

Problem:  When multiple windows are open within Server Monitor, if you maximize one window all the windows will resize.  Similarly, if you reduce one window from maximum size, all windows will return to a smaller size.

9/95 Status:  Will be fixed in release 1.2.

D-1817


SMM software installation tries to get files from network.

Problem:  During a boot into Windows, the alert converter tries to pull files over the network instead of locally.  If the server is down, an error message "can't find file F:\SMM\ALCONV.EXE" is displayed.  If an out of band session is attempted, the error message is "OLE INITIALIZATION FAILURE" but login continues.  Under this configuration, warm reset of the server fails.

9/95 Status:  Will not be fixed.

D-1812


Dirty Cache Buffers Graph Confusing

Problem: The graphical parameter under the Netware 3.1x agent, Memory category, for Dirty Cache Buffers displays the y axis values as 1000, 2000, and 3000, but the graph is labeled "%".

9/95 Status:  Will be fixed in release 1.2.

D-1804


LAN Drivers (i) info is IRQ = A

Problem: The informational parameter under the Netware 3.1x agent, LAN Drivers shows the LAN card at IRQ = A when it should report 10.

9/95 Status: Will be fixed in release 1.2.

D-1805


AMS Log and statistics don't match

Problem: If you examine the AMS log and then click the right mouse button to show graphical statistics, the log does not always match the statistics graphed.  The log is correct.

Status:  under investigation.

D-1806


Resolved Errata

Installation into Xtended Xpress required power cord disconnect

Suspend mode not supported for Fab 3

Occasional Read/Write Failure when directly interfacing with the Module

Fab 3 boards (pre-release) J-numbers do not match documentation

Redirection:  using DOS Edit and DOS Help

Using Server Monitor with Compaq NetFlex LAN Drivers


Installation into Xtended Xpress required power cord disconnect

Problem:  If you install a Server Monitor Module into an Xtended Xpress, you MUST disconnect the power cord from the Xtended Xpress System first.  This should be done anyway for safety reasons, but in this particular application, the connection of the Server Monitor Module's Xtended Feature Cable to the Xtended Xpress baseboard will cause the system to power on if the line power remains connected.

Resolution:  PBA 636360-004  corrects this problem, but it is always recommended that the power cord is disconnected from the system before removing the cover of the system.


Suspend mode not supported for Fab 3

Status:  Resolved in Fab 4 and above.  891


Occasional Read/Write Failure when directly interfacing with the Module

Problem:  Occasionally a read or write operation from/to the I/O ports on the LANDesk® Server Monitor Module will result in erroneous data being read or written. This failure has only been noted in one specific stress test program and has not been noted throughout our internal alpha testing and our extensive external beta test program.

This problem can only occur when the user is directly interacting with the LANDesk® Server Monitor Module. We have calculated that based upon this interaction the worst case scenario is that this problem could occur in the LANDesk® Server Monitor Module software once every 90 weeks. If this problem should occur in the LANDesk® Server Monitor Module software, it would present itself as a recoverable soft error and the software will continue to operate normally therafter.

Resolution:  Fab 5 of the board will correct the problem.  1583


Fab 3 boards (pre-release) J-numbers do not match documentation

May 25, 95

Problem:  On Fab 3 boards, the J numbers for the Xtended Feature Cable and for the Remote Temperature Probe are incorrect and do not match the Installation and Users Guide and other documentation.

Resolution:  Resolved in Fab 4 and later.


Redirection:  using DOS Edit and DOS Help

Problem:  If the server is off the network and you log into the Server Monitor Module via out-of-band session and use the console redirection utility, do not use DOS Edit to edit files and do not use DOS Help.  The program that implements redirection on the server (SMMTSR) intercepts BIOS calls to do its job. Some programs do not use BIOS calls for keyboard input, instead they access the hardware directly. Two notable (and common) examples are DOS Edit and DOS Help. Once you try to exit the program using <alt>F, any keystroke after that will not be recognized by the program.  The server will appear as if it is hung but in reality it is waiting for the last character.

Workarounds:  Use editors other than DOS Edit.  Do not use DOS Help. If you do use Edit or Help, you will need go to the server's keyboard to exit the program.

Resolution:  Fixed in Release 1.11.


Using Server Monitor with Compaq NetFlex LAN Drivers

Note:  the following information is included in a card within the software and manual package, will be removed with the release of software version 1.11.

If you are using a Compaq NetFlex LAN card on your server, an ABEND can occur any time after you load NW3AGNT.NLM or NW4AGNT.NLM.  This happens because the NetFlex card is not completely ODI compliant.

While Intel is working with Compaq to solve this problem, a simple workaround consists of deleting or remarking out one section of the file NW3AGNT.CFG or NW4AGNT.CFG, whichever is appropriate for your network.  (You can find this file in the SYS:SYSTEM directory on your server.)  The modified version of the file prevents Server Monitor from displaying the LAN Drivers parameter category in the tree that appears in the Parameter Selection window.

Versions of NW3AGNT.CFG and NW4AGNT.CFG with these changes already made can be found on the MS-DOS Utilities disk (version 1.1) that ships with Server Monitor.  If a NetFlex card is installed on your server, then copy the appropriate file to your SYS:SYSTEM directory before loading any LANDesk Management Suite NLMs onto your server.

Alternatively, you can make the changes to the configuration file yourself.  First make a backup copy of the appropriate file, then load the original into a text editor such as EDIT.COM.  For NW3AGNT.CFG, delete lines 372-539 (or place the character "#" at the beginning of each of these lines).  For NW4AGNT.CFG, delete from line 632 through the end of the file.  Save the new version of your file and exit the text editor.

NexFlex is the only card known with a driver that cannot be monitored by these NLMs.

Resolution:  Resolved in software release 1.11.


Introduction

Figure 1. A typical network arrangement

Local Area Networks (LANs) now connect a significant portion of the more than 100 million MS-DOS* and Windows*-based personal computers found in the workplace. Individual networks often connect hundreds of users and possibly several servers.

As these LANs have grown, users have come to expect the benefits of real-time interactive computing. Corporations also are recognizing the advantages of information exchange and collaboration. This reliance on the distributed processing environment has made it critical that network data be protected so that it is accessible and readily available at all times. The file, print, or application server is the critical node because it can effectively store all of the data needed by users.

At the same time, it has become increasingly important for network administrators to be able to manage data availability both over the network and independent of the network. Because servers are being deployed in remote locations, network administrators need the capability to manage their servers in any of three locations: the local server console, the local management console, or a remote (network-independent) management console.

Maintaining LAN productivity under these conditions - and with a growing number of servers per administrator -is becoming more difficult. As an aid, several vendors have provided server management software with two major components: an agent on the server and a monitoring console. Figure 2 shows a typical network with the addition of server management software.

Figure 2. Typical network with server management software

One example of server management software is Intel's LANDesk Manager product. In this package, the agent interacts with the network operating system to collect information about the server's health and performance. The monitoring console communicates with the agent across the network (the in-band connection) to retrieve and display this information. The administrator may set various conditions (e.g.; server CPU utilization thresholds) for generating alerts. When a specified condition is violated, the administrator is alerted via a dialog box on the monitoring console's screen or even by being paged. The monitoring console software also may be configured to alert the administrator by different means depending on the day and time. For example, the alert could be sent to the console during business hours or sent to a pager via the Server Monitor Module at night or on weekends.

Software-only solutions to server management do have some inherent limitations: the server and network must be operational and there is no way to monitor some essential hardware characteristics.

At the very least, a network management station should be able to provide users with a stable environment by detecting and helping to repair faults quickly. The key to a successful tool is the ability to find little problems before they become big ones. For example, good server management tools should:

Help the network manager automate configuration and control tasks

Provide network managers/administrators with extensive information on network activity at the node level

Provide administrators with information for determining system failures, and adequate warning of such failures

Intel has responded to these needs by introducing a Server Monitor Module that stores application specific software in non-volatile Flash memory. The ISA bus-master card installs easily in one of the server's expansion slots.

Figure 3. Typical network with Server Monitor Module

The DOS engine of this solution is a single 8086-compatible CPU, the Vadem VG-230, that includes:

•	a memory controller;

•	four channel 8237-compatible DMA controller;

•	8254 PIT, 8255 PPI and 8259 PIC compatibility;

•	real time clock; and

•	an ISA bus controller.

Additional features include a file server interface window, a solid state data storage via Flash memory, serial support, 1 MB of system DRAM, PCMCIA interface, and a battery backup. The board has one PCMCIA Type 2 compatible (modem card services only) connector.

When the Server Monitor Module is installed in a server, it can monitor the power supply and operating temperature. When the server is not operating within specified limits, the module attempts to alert a supervisor/administrator in one of two ways. The module first will try to contact a server management console using the in-band connection. If this fails, the module will try to dial out to get to a console. The console, whether contacted in-band or out-of-band, is responsible for delivering the alert to the supervisor/administrator. Corrective action can then be taken, including remote maintenance of the server from a network workstation or modem-equipped computer.

The Server Monitor Module hardware supports power management to reduce battery drain. The software uses the SLEEP and SUSPEND modes. When there is power from the backplane and no user activity, the module runs in SLEEP mode at 1/8th CPU speed. When running off the battery and with no user activity, the module goes into SUSPEND mode (CPU clock and oscillator off, modem off) and will be awakened when some external event happens. The Server Monitor Module normally takes power from the server ISA/EISA bus. During this time, the Server Monitor Module maintains a trickle charge to an on-board Ni-Cad battery. If power is removed from the server bus, the module will remain in SUSPEND mode for up to four hours. During this period, up to 30 minutes of full-function activity can take place (i.e.; communications with remote console via modem).


Core Feature Set

Feature	Purpose	Advantage
User Definable Alerting Capabilities via Monitoring Console Software	Provide network and/or network-independent alerting capabilities during:
	Catastrophic Alerts	Ability to alert administrator when the server is down
	Critical Alerts	Alerts when server crash is imminent
	Warning Alerts	Alert when there are possibilities of a server crash
	Informational Alerts	Ability to send alerts when user-set thresholds are exceeded
Information Access Capability	Ability to Access Server when:
	Server is Healthy	Ability to access information about server health as needed
	Server is Down	Ability to access an information for analysis of why the server went down
Reboot Capability	Ability to reboot the server from a remote location by initiating a:
	Warm Reboot	Can initiate a warm reboot of the server without going through the full POST
	Hard Reset (Available on Xtended Server and ALTServer)	Can initiate a hard reset to force the server to go through POST
Remote Console Capability (Available only with updated BIOS releases for Xpress, Xtended Server, and ALTServer)	Ability to control the server from a remote location when:
	Server is running	Ability to control the server when the server is up but the network is down
	Server is down	Ability to retrieve POST codes and server video buffer contents across the asynchronous communication line
In all situations, the goal of the Server Monitor Module is to be able to predict potentially catastrophic hardware and software issues before they become critical network problems. This is to ensure the server keeps the network running and maintains data integrity.

Should the server crash, the system administrator also must have access to the last known status of the server. This feature is provided by the information access capability features, which contain the current configuration, the last environment status, the time and day, and any final information that might have been saved prior to the crash.

Besides the core feature set mentioned here, password protection and alert signals to a pager are other available features that enhance the complete functionality built into the Server Monitor Module.


Out-of-Band Features and Functions

Out-of-Band Function	Network Down	Operating System Down Network Up	Server Down
Temperature Monitoring	x	x	x
Voltage Monitoring	x	x	x
Remote Soft Reboot	x
Remote Hard Reset	x	x	x
Power On /Off	x	x	x
Server Console Redirection	x	x
Retrieve Capture POST Code	x	x	x
Console Alerting over Modem	x	x	x
Read Server Logs when Server is Down	x	x	x
TAPI Pager Alerting on Thresholds	x	x	x


Functional Description

Figure 4. Component block diagram of Server Monitor Module

Related Topics:

Battery Backup

XT-compatible DOS Engine

CNMC (ASIC)

PCMCIA Interface

Modem

Non-Volatile Flash Memory

Serial Port

Shared Memory Interface (SMI)

Thermal/Voltage Monitor


Battery Backup

The backup power section keeps the Server Monitor Module operational when power is interrupted to the host server. During such conditions, the circuitry automatically switches to battery power. The card is supplied with power for a maximum of one half-hour of continuous active communication. This half-hour can be distributed in any way over a maximum period of four hours. During normal server operation, the battery will be charged from the ISA bus power.


XT-compatible DOS Engine

The DOS engine is an 8086-compatible microprocessor with integrated core logic and I/O support. Using an embedded processor provides the functionality of an entire computer on-board. In today's standard PC designs, Intel controllers (i.e.; 8237, 8254, 8255, 8259, etc.) are widely used as the core peripheral chip sets. Those standards are again implemented in this product. Because the DOS engine is specified to be XT-compatible, only 1 MB of memory and 1 KB of I/O space can be supported. Additional memory space and/or devices  such as PCMCIA  are supported using bank-switching techniques like those described in the LIM-EMS specification.


CNMC (ASIC)

The Critical Node Monitor Controller (CNMC) is a custom Application Specific Integrated Circuit that contains most of the hardware logic and control functions, including Shared Memory Interface (SMI) control, server ISA bus arbitration and mastering, server I/O interfacing, thermal and voltage monitoring, non-volatile memory control, POST code capturing, and Server Monitor Module power control.


PCMCIA Interface

The PCMCIA interface is responsible for the connection between the Server Monitor Module's private ISA bus or processor local bus and any PCMCIA 2.0 compatible modem. Supported modems include those capable of 2400 KBps or greater communication speeds. The PCMCIA expansion modules may contain up to 64 MB of addressable resources, but bank switching must be used to access PCMCIA resources in the XT address range.


Modem

The modem section is shown with dotted lines in Figure 4 to emphasize that the modem may be either a PCMCIA 2.0 compatible modem or a standard serial modem.

Support for both North American and European modems is built into the module firmware. This allows the Server Monitor Module to send out-of-network alert messages. When the module recognizes an alertable condition, it first tries to contact a console in-band (on the network), then attempts to dial out to get to a console. As a final step, the module calls a pager service.

In order for the message to be sent successfully, the modem must always have a line voltage available. If a PCMCIA modem will be used, the battery on the module will provide power when the server line voltage is interrupted. If an external modem will be used, it should be connected to an Uninterruptable Power Supply (UPS).


Non-Volatile Flash Memory

An Intel 28F008SA 8 Mbit Flash memory component is responsible for storing all applications which are to run on the Server Monitor Module and storing all pertinent last-known-state information necessary to recover from catastrophic failures. To save memory space, this block has been mapped into a LIM-EMS page frame of the DOS engine's memory space. The LIM-EMS 4.0 compatible mapping register required to control it is included on the VG-230 component.

In addition to the Flash device, the module also contains 128 KB of non-volatile Flash memory for BIOS, ROMDOS and other firmware which may be updated with a utility. The Server Monitor Module firmware is loaded at boot time into DRAM and is backed-up by an on-board NiCad battery. Therefore, updating the system firmware is accomplished by updating the file on the server's hard drive.


Serial Port

The external serial port resides on the module's private bus and provides a connection for a terminal, terminal emulator, or modem. If a modem is to be connected, it must be configured as COM1 or COM2 since neither COM3 nor COM4 are supported in the XT architecture.


Shared Memory Interface (SMI)

The fastest method by which the Server Monitor Module communicates with the host server is provided by SMI. The primary method of communication is the I/O interface. The memory space is an 8 KB memory window that is mappable in 8 KB increments to any contiguous address space in the host server's lower 1 MB address space. The host server address window and the module's address space do not need to be the same. The interface to the SMI is interrupt-driven to reduce the host processing power requirement. The interrupt level at the host server is user selectable using software-written registers, but the module's interrupt level is preset and cannot be changed.


Thermal/Voltage Monitor

The Server Monitor Module has the ability to measure the server's operating temperature and the ISA bus voltage level (±5V, ±12V, and, if applicable, 3.3V). The operating temperature is measured using the module's onboard thermal transducer. These measurements can be read by software and compared against preset normal operating parameters stored in memory. For an accurate representation of the voltage measurements, registers should be read at approximately 1 ms intervals. For accurate temperature measurements, the temperature should be read at approximately one second intervals.

A secondary temperature probe may be added for monitoring of a strategic component elsewhere in the server, such as the processor or the power supply air intake temperature.

Note: the battery charging circuit draws +12V power from the ISA bus. During the charge cycles, the 12V voltage level may drop, depending on the server's ability to provide adequate power over the bus.


On-board Resources

There are two main sets of functional blocks on the Server Monitor Module: resources that are shared with the server and resources that are used solely by the module. The only resources that are shared by the Server Monitor Module and the server are the I/O configuration registers and the Shared Memory Interface.

Related Topics:

Shared Memory Interface

I/O Interface

Module-only Resources


Shared Memory Interface

The Shared Memory Interface (SMI) is an 8 KB window in memory which is accessible to both the host server and the Server Monitor Module. The shared memory interface is mapped into the Server Monitor Module's address space at B4000h. Unlike the host server, the SMI is not movable within the Server Monitor Module's memory map. Access to the SMI is granted on a cycle-by-cycle basis, with preference given to the host server in the event of a tie. The host server preference requires the software to be carefully designed with a message passing semaphore scheme to avoid one system overwriting the data put by the other into the shared memory interface.

The SMI arbiter watches the SA(19:0) and SMRD signals from the module's ISA bus. When it detects an address which is within the 8 KB window (and SMRD is activated), the module will be granted access to the SMI. If the host server is accessing the SMI when the module is accessing it, the module's IOCHRDY line will be driven inactive until the host completes its access. Since the arbiter grants access to the SMI on a cycle-by-cycle basis, the IOCHRDY signal will never be driven inactive for longer than 600 ns.


I/O Interface

The Server Monitor Module and the host server both have access to the module's configuration registers. However, each accesses these configuration registers in a slightly different manner: the module sees them as part of its I/O space; the host server sees them as two ports, index and data. The actual physical port which stores the configuration information is the same no matter which device is accessing it. Because of this technical function, the module and the host server cannot access the configuration registers at the same time. Hardware must arbitrate between the host server and the module on a cycle-by-cycle basis. This requires a software protocol which can ensure that only the module or only the host server is writing to the configuration registers at any given time. Below is a portion of the Server Monitor's I/O map showing the shared configuration registers.

Name	Type	Address	Default
ADC Control Port	W	100h	N/A
ADC Status Register	R	100h	FFh
Register Name	Type	Address	Default
Presence Detect	R	180h	96h
Board ID	R	181h	none
Command	R/W	182h	F0h
Shared Memory Interface Mapping	R/W	183h	80h
IRQ level mapping	R/W	184h	F0h
DRQ level mapping	R/W	185h	F0h
SMI/DRQ/IRQ enable	R/W	186h	F8h
Host Interrupt Code	W	187h	F0h
Local Interrupt Code	R	188h	B0h
Server Monitor Status	R/W	189h	00h
Table 1. Selected portion of Server Monitor Module I/O map.


Module-only Resources

Resources used solely by the Server Monitor Module are several interfaces that define the complete functional block for the card. These are the analog-to-digital converter interface (part of the thermal and voltage monitoring block), bus-mastering circuitry, power control/status, host server command/status, POST code capturing, interrupts, and non-volatile memory. Table 2 summarizes the custom circuitry I/O port assignments and are in addition to those normally found in the XT-compatible architecture.

Name	Type	Address	Default
ADC Control	W	100h	N/A
ADC Status	R	100h	FFh
ADC Result	R	101h	00h
Host Server Command	W	106h	00h
Host Server Status	R	106h	00h
POST Code Address, low-order	R/W	107h	80h
POST Code Address, high-order	R/W	108h	00h
POST Code Data	R	109h	00h
On-Board Interrupt Source	R	10Ah	00h
Reserved	N/A	10Bh	N/A
Table 2. Server Monitor Module custom circuitry I/O port summary

Related Topics:

Analog to Digital Converter (ADC) Interface (I/O ports 100h-101h)

Host Server Command/Status (I/O port 106h)

POST Code Capturing (I/O ports 107h-109h)


Analog to Digital Converter (ADC) Interface (I/O ports 100h-101h)

The Server Monitor Module interfaces to the ADC via two I/O ports, the control/status and result port. The control port is write-only, and the status port is read-only. Table 3 summarizes these ports.

Name	Type	Address	Default
ADC Control Port	W	100h	N/A
ADC Status Register	R	100h	FFh
ADC Result Bits	R	101h	00h
Table 3. Analog to Digital Converter register summary

Using the ADC to read the temperature or an analog voltage starts with software writing an appropriate byte to the ADC control port. This byte informs the controller which of the eight channels is to perform a conversion. Table 4 shows the ADC Control register bits and which channels are selected from the appropriate bit selection. A conversion then takes place. At the end of that conversion, the ADC will activate its interrupt signal.

ADC Control

Type:	Write-only

I/O Address:	100h

Default:	N/A

Bit Field Definitions

Bits CH0-CH2 are the ADC channel select bits, used to indicate which one of the eight channels is to perform a conversion. The ADC status register contains the most recent conversion request status. A value of FFh indicates that the conversion is complete and the data in the result port is valid. A value of FEh indicates a conversion is in progress and is not yet complete.

The ADC result bits are the most recent conversion request once the status register indicates that the conversion is complete.

Channel	Nominal Value	Signal
0	80h	Host server +5 Volts
1	80h	Host server -5 Volts
2	80h	Host server +12 Volts
3	80h	Host server -12 Volts
4	80h	Host server operating temperature
5	80h	Server Monitor backup battery voltage
6	80h	Xtended Xpress 3.3V
7	80h	Secondary temperature sensor
Table 4. ADC channel assignment summary

When the server's +5V power line is equal to or greater than 5.00, the ADC result port will read 80h after a +5V conversion is requested. The conversion ratio is 40mV per step for the +5V and -5V lines, (e.g.; the result will be 81h when the voltage is 5.04V). The +12V and -12V power line conversion is at 71.5mV per step (e.g.; the result will be 78h when the voltage is 11.86 volts). The only exception to the ±5V and ±12V nominal values is the Xtended Xpress 3.3V signal. This signal is monitored directly by the ADC with a nominal value of A8h and a conversion ratio of 20mV per step.

The temperature sensor's nominal value is 80h when the temperature is +40C and it has a conversion ratio of 0.5C per step, (e.g.; the result will be 81h when the temperature is 40.5C). When the secondary temperature sensor is not installed, the result will be FFh.


Host Server Command/Status (I/O port 106h)

This I/O port contains both the general purpose interface to the host server and the Xpress/XXpress features. It is through this register that the Server Monitor Module resets the host (if the host is an Xpress or Xtended Xpress system), interrupts the host, and determines if a host is present. Bit assignments and explanations are as follows:

Host Server Command

Type:	Write-only

I/O Address:	106h

Default:	00h

Bit Field Definitions

RFU: Reserved for Future Use. These bits will always read as zero, and they must be written with zeros to avoid conflicts with future generations and upgrades.

PWR OFF: Host Power Supply Off. When the Server Monitor Module is installed in an Xtended Xpress system, setting this bit will force the power supply to shut down. Conversely, clearing this bit will allow the power supply to restore power to the Xtended Xpress. This bit is not connected or utilized by the Xpress baseboard.

HCRI: Host Critical Interrupt. In Xpress systems, this bit is not connected and should be treated as an RFU bit. In Xtended Xpress systems, activating HCRI will drive SMI (system management interrupt) active on the baseboard, and force the system into SMM (System Management Mode).

RESET: Reset Host. Setting this bit to a logical one will activate the reset signal on the Xtended Xpress server system. A feature connector is located on the Xtended Xpress baseboard and must be connected to both the Server Monitor Module and the system baseboard. This hardware will automatically activate the reset signal for 100us and then deactivate it. There is no need for software to clear this bit to bring the server out of reset.

INT: Interrupt Host. Setting this bit to a logic one will activate the interrupt to the Xpress/Xtended Xpress baseboard. This bit is a write-only bit. The only way it can be cleared is by the host server reading the Host Interrupt Code port.

Host Server Status

Type:	Read-only

I/O Address:	106h

Default:	10h

Bit Field Definitions

HPWRGD: Host Power is Good. When the server's power is within 5% of 5V and 12V specifications, this bit will be a logical one. If not within specification, this bit will be a logical zero.

SECMOD: Secure Mode (Xtended Xpress only). When this bit is a logical one, it indicates that the Xtended Xpress keyboard controller has placed the server system in Secure Mode. While in this mode, the server's keyboard is locked, the screen is blanked, and the floppy disk is write protected. The Server Monitor Module cannot bring the server out of the secure mode, it can only report whether the server is in this mode.

CHOPEN: Chassis Open (Xtended Xpress only). Indicates that the server chassis is open. Software can read this bit to generate an alarm or alert for the system administrator. When inactive, the chassis is closed (secure).

LPOK: Line-voltage Power OK. (Xtended Xpress only) This bit indicates the status of the host server's line voltage. When LPOK is high (active), the server has AC line voltage available; when LPOK is low (inactive), the server's AC line voltage is not available. When used in conjunction with the ADC, LPOK can be used to indicate whether the server's power switch has been turned off (LPOK active, but ADC indicates voltages are zero), or if the host server has lost power (LPOK inactive and ADC indicates voltages are zero).

FEAT EN#: Features Enabled (Xtended Xpress only). This bit indicates the module is properly installed in an Xtended Xpress system with the ribbon cable connected to the baseboard feature connector. The bit is zero when the cable is installed and a logical one when not installed. This bit is read-only; writes to this bit will be ignored.

XRSTEN#: Reset Enabled (Xpress only). This bit indicates that the module is installed in an Xpress system with remote reset capability and that the wire-harness interface for the remote reset is installed. When XRSTEN is inactive, this bit indicates that the module is either not installed in an Xpress system, or that the remote reset wire harness is not installed.

HOST PR16#: Host is present in a 16-bit EISA/ISA slot. This bit is a logical zero when the module is inserted in one of the host's EISA/ISA slots that supports 16-bit bus mastering protocols. Conversely, when the HOSTPR16 bit is a logical one, the Server Monitor Module is not inserted into a 16-bit slot.

HOST PR8#: Host is present in an 8-bit slot (active low). This bit is a logical zero when the module is inserted in one of the host's 8-bit baseboard slots. Conversely, when the HOSTPR8 bit is one, it indicates that the Server Monitor Module is not inserted into a backplane. This bit is also active (low) when the module is inserted in a 16-bit slot, since the 8-bit slot is part of the 16-bit slot.


POST Code Capturing (I/O ports 107h-109h)

The POST (Power On Self Test) code capturing block watches the host server bus for I/O writes to the POST port, and captures its own copy of the data when the write is placed on the bus. POST codes are primarily used for diagnostic purposes and always are available during the host's POST. Since the code may be written at any time during the boot-up sequence, the POST code capturing block utilizes an interrupt-driven interface. Upon capturing a new POST code, the processor will be interrupted and the appropriate bit will be set in the Interrupt Source register, indicating that a new POST code has been received. For compatibility in many other servers, the port which the Server Monitor Module watches for POST codes (the POST port) is programmable.

Note: any writes to this port after POST will still be captured, although they likely will signify different information.

POST Code Address, low-order

Type:	Read/Write

I/O Address:	107h

Default:	80h

Bit Field Definitions

PC(7:0): POST Code Address. These eight bits comprise the low-order POST code port assignment bits.

The low-order POST code address bits comprise eight of the ten address lines used to determine if a host I/O Write is directed at the POST code port. These eight bits are concatenated with the high-order bits to form the entire ten-bit address.

POST Code Address, high-order

Type:	Read/Write

I/O Address:	108h

Default:	00h

Bit Field Definitions

RFU: Reserved for Future use. These bits will always read as zero, and they must be written with zeros to avoid conflicts with future generations of this product.

PC(9:8): POST Code Address. These bits comprise the high-order POST code port assignment bits.

The high-order POST code address bits comprise the upper two of the ten address lines used to determine if a host I/O Write is directed at the POST code port. These bits are concatenated with the low-order bits to form the entire ten-bit address.

POST Code Data

Type:	Read-only

I/O Address:	109h

Default:	00h

Bit Field Definitions

D(7:0): POST code data bits. These eight bits comprise the POST code captured from the host server.


Programming/Software Information

Software and various applications make this module into a full-featured server monitoring product. This section reviews the required tools to meet the wide variety of needs for users who have their own operating system, those who install the module in a system other than an Xpress server, and those who choose to buy the LANDesk Manager v 2.0 integrated software.

Related Topics:

LANDesk Manager V2.0 & Module Interactions

Server BIOS & Module Interactions

Server Agent & Module Interactions

Monitoring Console & Module Interactions

Additional Module Features on Xtended Xpress/ALTserver


LANDesk Manager V2.0 & Module Interactions

The LANDesk Manager server monitor application provides proactive server management, allowing corrective action to be taken at the first sign of system degradation. The ability to monitor critical server subsystems and assign customized tasks to non-fatal conditions distinguishes the LANDesk Manager application from reactive management tools, which merely notify the administrator after a failure. Using the Windows-based management console an administrator can:

•	Set system parameters mentioned in the Core Feature Set

•	Assign tasks to system events

•	View real-time server system data in graphical format

•	View and manipulate historical server data

The server monitor object in LANDesk Manager is an application consisting of NLM management agents that run on NetWare servers, integrated as a Windows console program launched from the LANDesk Manager Control Panel. The NLM agents monitor critical variables and data structures of the NetWare operating system and transmit the values of those variables to the server monitor console. The NLMs are able to detect the presence of the Server Monitor Module when it is installed in a NetWare server. Upon detecting the card, the application NLM begins monitoring all variables it maintains.

Third-party programming interfaces are not provided for the server monitor application, but developers can use the integrated event handler API and OLE 2.0 instrumentation to customize and automate its operation. The server monitor application agent NLM uses the Shared Memory Interface and interrupts to detect the presence of the Server Monitor Module and obtain information. When this application is combined with the Server Monitor Module, it is capable of performing alert notification when the host server is down, or when no network connections exist.

This entire concept is defined as the Monitoring Console, which is a Windows-based system viewing and configuration utility. Some of the main tasks performed include:

•	Locating other servers on the LAN that have the Server Monitor Module installed

•	Establishing sessions with the LANDesk Manager control program

•	Assigning thresholds and tasks to the system parameters

•	Monitoring the status of parameters in real-time graphical format

•	Receiving event notifications from attached control programs

•	Retrieving, displaying, and managing parameter history files

•	Enabling OLE 2.0 queries of certain system parameters


Server BIOS & Module Interactions

The Server Monitor Module and its bundled software were designed to run on Intel Xpress, Xtended Xpress, ALTServer or any third-party system running Novell NetWare version 3.1x or 4.x. This section lists some critical considerations for developers who will be using hardware other than the Xpress product line or their own operating system or BIOS.

The Server Monitor Module must be assigned four types of resources:

•	Two bytes of contiguous I/O space

•	One DMA channel

•	One interrupt request line

•	8 KB of contiguous memory space

The host server's BIOS initially has the responsibility of configuring the SMI to communicate with the Server Monitor Module. This is accomplished by a message-passing mechanism implemented out of an 8 KB region of shared memory. The main task of the BIOS is to determine where the module's I/O ports are located in the server's I/O address space. On an EISA system, these resources can be assigned with the EISA Configuration Utility (ECU). For Intel-based servers, a .CFG file is used with the ECU before installing the module to configure resources as follows:

•	I/O addresses 110h-111h, 210h-211h, 310h-311h

•	Any available DMA channel

•	Any available interrupt request line, depending on whether the adapter is installed in an 8-bit or 16-bit slot

•	Any memory area between 0C0000h and 0EFFFFh, on any 2 KB boundary

The ECU automatically assigns free resources to the card when the .CFG file is loaded. The user can then reassign the resources as desired, depending on system resources available.

For non-Intel based systems, BIOS developers can use this same technique to assign resources. To begin this sequence, the Server Monitor Module initially makes available its I/O ports at server addresses 0x110, 0x210 and 0x310. The purpose of using three addresses is to avoid potential conflicts with other devices at one or two of the addresses. The server ECU then needs to read seven addresses; 0x110, and 0x112 through 0x117. If any address returns a result other than 0xFF, the process should be repeated at the other two base addresses. Once the I/O port has been found, the bytes 0xA1, 0xB2 and 0xC3 need to be written to the established base port. After the writes are successful, the host server's ECU should then read the base port plus one additional address to check for a value of 0x96. If this value is found, the communication link between the Server Monitor Module and the host server ECU has been established. If this value is not found, the process must be repeated until it is.

When the system is reset, the EISA BIOS will configure the Server Monitor Module with the values which correspond to the assigned resources. On ISA systems, the assigned values should be determined by the BIOS reading the appropriate CMOS locations determined by the BIOS developers. The ISA setup screens should be modified to perform these tasks and allow the user to choose and change the required resources.

Once the communication link has been established, the Server Monitor Module BIOS will prepare the message-passing data structures in the SMI so the Server can communicate through it. The module will signal when these data structures have been initialized by setting bit 0 of the Command port (182h). The server BIOS should wait for this value before proceeding. There should, presumably, be a time-out mechanism so the server doesn't hang if the module fails to set the bit in a reasonable length of time. In order to enable the board, the server BIOS must enable the SMI, IRQ and DMA by writing the appropriate value into the SMI/DRQ/IRQ Enable port (186h). When the module is installed, the ECU must be used to set the DMA channel, IRQ level and SMI base address to appropriate values. If installed in an ISA system, the system Setup screen must be extended to allow for these options.

After these functions are performed, other tasks still must be performed to properly determine how the host server BIOS interacts with the module. The additional tasks to be handled by a server BIOS extension include:

•	Using the message-passing mechanism

•	Keeping the Server Monitor Module appraised of the current server state

•	Synchronizing with the module during startup

•	Providing server console redirection until the server agent is running

•	Responding when the Server Monitor Module is reset or reboot

The next two sections provide developers with an overview of server BIOS interaction with the module.


Server Agent & Module Interactions

The following section includes some absolute requirements for developers trying to successfully establish a communication link between their own operating system on the Intel Xpress hardware, the server agent, and the Server Monitor Module.

The server agent initially has the responsibility of configuring the SMI to communicate with the Server Monitor Module primarily by means of a message-passing mechanism implemented out of an 8 KB region of shared memory. The agent synchronizes at a low level with the module via the set of I/O ports determined by the host server BIOS upon initialization.

Once a communication link has been properly established, a list of functions must be performed, including five which are identical to those listed in the section on server BIOS/module interactions:

•	Discovering where the I/O ports are located

•	Enabling the Shared Memory Interface

•	Using the message-passing mechanism

•	Keeping the module appraised of the current server state

•	Synchronizing with the module during startup

•	Setting the Server Monitor Module's date and time

•	Sending the module information about the server configuration

After these tasks are executed, a number of other functions must be performed to enable proper interaction between the server agent and the module. For example, the module must know how to properly construct the text for alert messages. The agent must provide necessary information in the form of a series of LocalizationInfo messages. There must be one for each possible phrase to be localized. The Server Monitor Module will ask for localization information by sending Get LocalizationInfo messages whenever the server or the module reboots. The server agent must be prepared to respond to these requests. The contents of the messages should be worked out between the server agent and Server Monitor Module application designers, but the formats should be similar to these:

The server and the module must next determine whether the monitoring console is still alive. On each system, there should be software that watches for unusually long periods of inactivity on the SMI. When such periods occur, it is assumed that either or both systems are hung. An SMPAlive message (a sort of module "heartbeat") is continuously sent to ensure there is an ongoing interface between the module and the monitoring console.

The agent must provide two algorithms for this process to work:

•	The agent must also have a "heartbeat" equivalent that regularly sends ServerAlive messages

•	The agent must notice when no messages have been received from module for an extended period of time. When this interval is exceeded, the card is considered to be hung.

When the module is able to detect a critical failure in its own operation, it stores an error code in the Server Monitor Status I/O port (189h), then hangs itself. The agent should read the port and include the value it contains as part of the alert. Once the alert has been sent, the agent should reset the module by writing a 1 into the RST bit in the Command I/O port (182h). The board will remain in a reset state until the agent writes a 0 to the RST bit.

After these functions are performed, additional tasks required include:

•	Participation in a server reboot protocol with Server Monitor Module

•	Responding when the module is reset or rebooted

•	Providing server console redirection via the Server Monitor Module

•	Getting voltage and temperature information from the module

•	Periodically storing server status information with the module in the event of a server crash

•	Adding, deleting and modifying entries in the module user table

•	Receiving "indications" from the Server Monitor Module

•	Sending requests to the module to post an alert to the monitoring console via the out-of-band connection

•	Processing agent control information from the console via the module and responding to the console

•	Processing module requests to send information to the console via the in-band connection and vice versa

•	Updating the Server Monitor application software to the module

•	Updating the Server Monitor Module BIOS

The section that follows continues the overview of server agent interaction with the Server Monitor Module.


Monitoring Console & Module Interactions

The following section includes some absolute requirements for developers trying to successfully establish a communication link between their own operating system on the Intel Xpress hardware, the server agent, and the Server Monitor Module.

The monitoring console initially has the responsibility of communicating with the Server Monitor Module by either the in-band network connection, or a dial-up asynchronous connection. Only the routes and the speeds differ  the information being exchanged is identical. The monitoring console therefore must be able to initiate an in-band connection with the module, or accept a dial-in connection. Once this communication link has been properly established, a list of functions must be performed. If the network is not available, the out-of-band connection will be used and console redirection will take place out-of-band to the console.

A packet-based protocol must be employed between the module and the console. This protocol may be implemented on top of two distinct transports: a modem-based serial line connection or a more involved path that includes the in-band network and the server agent. Packet transmissions must be reliable to ensure that commands are sent intact. The developer also should also try to maintain a low-overhead transmission of unreliable packets (e.g.; for console redirection). To meet these requirements, two types of packet transmissions are defined: ACK-required packets and ACK-less packets, which can be distinguished by a type byte in the packet header.

The ACK-required packets have a type byte value of 0 and ACK-less packets have an type byte value of 1 as the first byte. For ACK-required and ACK packets, the type byte is immediately followed by an unsigned 8-bit value, known as the sequence number, which is incremented for each packet transmitted. (This number rolls over every 256 packets, so when comparing two sequence numbers, s1 and s2, to see if s2 = s1 + 1, the arithmetic needs to account for the rollover. Immediately following these bytes are:

•	Two bytes for complete packet total length

•	Two bytes for the sequence number within the subpacket chain

•	Two bytes for the number of packets in the chain

•	Two bytes for the data length in this packet

•	Two bytes for the header CRC

•	The data

•	Two checksum bytes to ensure that the entire packet was valid

After these functions are performed, remaining tasks include:

•	Logging into the Server Monitor Module using the in-band connection

•	Calling the module and logging in using a modem attached to the monitoring console

•	Accepting a call from the module via a modem attached to the console and allowing the module to log in

•	Logging out of a Server Monitor Module session

•	Detecting when the current path has been lost due to network or communication line failure

•	Providing a server console redirection window that can operate concurrently with other console windows

•	Displaying the monitor system log in a window that can operate concurrently with other console windows

•	Once logged in, the Monitoring Console must communicate with the module to:

1.	Send commands to the server monitor and receive results

2.	Perform Server Console redirection

3.	Accept alert notifications from the module

4.	Receive the contents of the Server Monitor Module's system log.

5.	Receive information on the current server state (BIOS running, OS booting, etc.)

6.	Exchange information with the server agent via the module


Additional Module Features on Xtended Xpress/ALTserver

Several additional features are available when the module is installed in an Xtended Xpress or ALTserver system. The module has the ability to recycle power to the Xtended Xpress or ALTserver systems, monitor 3.3V signals, issue intrusion alerts, and provide other security monitoring options. To utilize these features, an Xtended feature connector must be installed and several specifications must be followed.

The figure below illustrates the pin assignments on the Xtended feature connector. The descriptions of each pin are found in the Host Server Command and Host Server Status registers, which are described in detail in the On-Board Resources section.

Name	Pin	Type	Description
SMI#	1	Input	System Management Interrupt
I2CCLK	2	Output	I2C Clock (8MHz)
GND	3	Power	Electrical Ground
key	4		No Connection
PWROFF#	5	Output	Power Supply Off (active low)
I2CDATA	6	I/O	I2C Data signal
LPOK	7	Input	Host Line Power OK
KEYUNLK	8	Input	Keyboard Unlock
NMI	9	Input	Non-Maskable Interrupt
3.3V	10	Input	3.3V power; this line is buffered by an opamp before it is routed to the ADC input.
RESET#	11	Output	Reset baseboard
GND	12	Power	Electrical Ground
GND	13	Power	Electrical Ground
key	14		No Connection
SECURE	15	Input	Host in Secure Mode
GND	16	Power	Electrical Ground
INTRUD	17	Input	Chassis is open
SPARE	18		No Connection.  Reserved for future use.
key	19		No connection
GND	20	Power	Electrical Ground
It may be possible to control Power On/Off from a remote console by using this connector and a modified baseboard on some third-party systems that support this interface and feature.

Related Topics:

Xtended Server 3.3 Volt Interface Specifications

Xpress Reset Connector


Xtended Server 3.3 Volt Interface Specifications

		Min	Max	Units
VAI	Analog Input Voltage	0	5	V
ZI	Input Impedance	100		K
IB	Input current		33	A
Res	Resolution	19	20	mV/step


Xpress Reset Connector

When the Server Monitor Module is installed in an Xpress system, and that Xpress system has the remote reset header installed (a three-pin header J0301 located between slots 2 & 3 of the expansion bus), the Xpress system can be reset by the Server Monitor Module.  A cable to connect between the SMM and the Xpress host is shipped with the Server Monitor Module.  The following figure shows the pin assignments for the reset connector.

NOTE:  The pin descriptions are defined from the host server perspective, but the pin numbering refers to the pins on the SMM card, connection J6. Where differences exist between the host server definition and the signal use on the Server Monitor Module, such differences are noted.

Name	Pin	Description
GND	1	Electrical ground on host server.  Connector Presence detect on Server Monitor Module.
RESET#	2	Active low reset signal
key	3	pin is removed
GND	4	Electrical ground.
It may be possible to control Power On/Off from a remote console by using this connector and a modified baseboard on some third-party systems that support this interface and feature.


Appendicies

Memory Map

I/O Map

Mechanical/Physical Specifications

Electrical Specifications

Reliability (MTBF) Specifications

Environment Specifications

Regulations


Memory Map

These memory and I/O configuration maps apply to a Server Monitor Module with 1 MB of DRAM installed. The module supports up to 2 MB of DRAM using the LIM-EMS 4.0 specification. In a 2 MB configuration, the second megabyte appears in an EMS page frame in the first megabyte. The I/O configuration map includes both the XT-architecture ports as well as the custom port definitions for the Server Monitor Module.

Volatile Memory	1 MB DRAM
Access Time	70 ns
Memory Width	8-bit
Non-volatile memory	1 MB Flash
Access Time	120 ns
Memory Width	8-bit


I/O Map

# Ports	Description	Address	# Ports	Description	Address
16	DMA Controller	000h	1	POST Code Address, low-order	107h
2	Interrupt Controller	020h	1	POST Code Address, high-order	108h
1	VG-230 Index Register	026h	1	POST Code Data	109h
1	VG-230 Data Register	027h	1	On-Board Interrupt Source	10Ah
4	Timer	040h	1	Reserved	10Bh
3	PPI	060h	2	I2C Bus Controller	10Ch
4	Memory Mapping	06Ch	1	I2C Bus Controller Interrupt	10Eh
8	DMA Page Registers	080h	1	Watchdog Timer	10Fh
1	NMI Mask	0A0h	107	Unassigned	114h
1	ADC Control/Status	100h	1	Presence Detect	180h
1	ADC Result	101h	1	Board ID	181h
1	Bus Master Low Page	102h	1	Command	182h
1	Bus Master High Page	103h	1	SMI Mapping	183h
1	Bus Master Command/Status	104h	1	IRQ Mapping	184h
1	System Control/Status	105h	1	DRQ Mapping	185h
1	Host Server Command/Status	106h	1	SMI/DRQ/IRQ enable	186h
1	POST Code Address, low-order	107h	1	Host Interrupt Code	187h
1	POST Code Address, high-order	108h	1	Local Interrupt Code	188h
1	POST Code Data	109h	1	Server Monitor Status	189h
1	On-Board Interrupt Source	10Ah	495	Unassigned	18Bh
1	Reserved	10Bh	8	Parallel Port (LPT1 only)	378h
2	I2C Bus Controller	10Ch	16	LCD Controller	3D0h
1	I2C Bus Controller Interrupt	10Eh	24	Unassigned	3E0h
1	Watchdog Timer	10Fh	8	Serial Port (COM1/COM2)	3F8h
107	Unassigned	114h
Table B-1. Complete I/O Map


Mechanical/Physical Specifications

The Server Monitor Module is a full-length ISA standard form-factor add-in card. The overall dimensions are 13.375 inches long by 4.800 inches high. Refer to the drawings below for details. (Drawings not to scale)


Electrical Specifications

Power Requirements

	Voltage	Current	Wattage
Primary Power Source (Host Server Backplane)	+5V	.1A	500mW
Primary Power Source (Host Server Backplane)	+12V	1.5A	18W
Secondary Power Source (Battery, Nickel Cadmium) Nominal	6.0V	200mA	1.2W
Secondary Power Source (Battery, Nickel Cadmium) Full Load	6.0V	1.2A	7.20W
On-board Battery Backup NICAD Battery	6.0V
Full Load		1.2A
Standby		200 mA
Charging Method	ReFLEX* Charge
Capacity	1.7Amp-Hrs:30mins active, 4 hours standy


Reliability (MTBF) Specifications

The MTBF prediction reveals the inherent reliability of the product. For circuit boards, the MTBF prediction is based on the component hard failure rates. These hard failure rates are assumed to be random in nature and are derived from either component supplier reliability test results or the Bellcore reliability prediction procedure. For the system MTBF predictions, the circuit boards, peripherals, power supply and other sub-assembly reliability data is reviewed and included into the system prediction. A calculated MTBF was generated using the Intel/Bellcore methodology as documented in Intel procedure 187677.

MTBF Prediction	97307.50 hours at 55ºC
Predicted Error Rate	2.70E-06 errors/hour
Demonstrated Results (as of 6/9/95)
MTBF 80% Confidence Limits	21075.04 hours at 40ºC
Observed Error Rate	5.9E-05 Errors/hour


Environment Specifications

Operating Temperature	0C to +50C
Storage Temperature	-30C to +60C
Relative Humidity	92% RH @ 36C


Regulations

Intended for use in systems meeting the following EMI/RFI regulations:

U.S.	FCC Class B

Canada	DOC Class B

Europe	VDE Class B, CISPR-B


Additional Information

Server Monitor Module BIOS POST Codes

Module Error Codes

Comparision of LANDesk® Server Monitor Module and LANDesk® Server Control

Considerations in Determining Analog-to-Digital Converter Accuracy on the Server Monitor Module


Server Monitor Module BIOS POST Codes

The following codes are generated by the Server Monitor Module's BIOS

Code	Meaning
001h	interrupts off after VG230 boot block
002h-004h	memory mapping
005h	reset DMA controller
006h-007h	memory use enabled, not guaranteed
008h	start of test and clear of bottom 64K of RAM
009h	enable interrupts
010h	CMOS validation start
011h	CMOS validation complete
012h	Boot DOS
081h	very first thing after reset vector
082h	after the index registers are set
083h	after the memory mapping registers are setup
084h	after refresh has been setup and enabled
085h	after zeros have been loaded into memory.  Codes 85h through 88h should be seen twice since the test is executed on two blocks.
086h	Zeros read okay.  FFs written.
087h	FFs read okay.  Zeros written.
088h	Zeros read okay.  Move onto next block, or if no more block, to next part of boot block.
089h	Memory test done.  Initialize interrupts.
08Ah	Before code is relocated.
08Bh	Before Int15 vector is hooked
08Ch	Before sharred memory is initialized
08Dh	About to switch BIOS pages
08Eh	Before checking for BIOS update request from server
08Fh	Before checksumming BIOS
090h	Before a BIOS update
091h	Before checking for APP update request from server
092h	Before checksumming the application
093h	Before an application update
094h	Before storing boot option
095h	Before clearing update request bit, if set
096h	Before jumping to run-time BIOS
097h	Memory Test Failure - BIOS hung.


Module Error Codes

These error codes may appear in the module event log , or in the Module Session Window.  This information is part of the Server Monitor Module Users Guide, Appx D.

Code	Text	Explanation/Remedy
100	This command is not yet implemented	An attempt was made to execute a command that is not yet implemented.
500	BIOS update already in the progress	An attempt was made to update the Server Manager Module application or BIOS while a BIOS update was already in progress.  Wait until the update is complete (approximately 30 seconds).
501	Application update already in the progress	An attempt was made to update the Server Manager Module application or BIOS while an application update was already in progress.  Wait until the update is complete (approximately 4 minutes).
502	Agent not responding, unable to update	The Server Manager Module was unable to receive acknowledgment from the Server Agent process, so the update request was aborted.  Ensure that the Agent (SMMAGNT.NLM) is loaded.
504	Agent refused to update BIOS or application	The server Agent process refused the Server Manager Module's request to update its BIOS or application.  The source file (HOBBIOS.BIN or HOBBAPP.BIN) was not found or was not readable.  These files should be in the same directory as SMMAGNT.NLM.
600	Bus request failure	The Server Manager Module encountered an error while attempting to use the ISA bus.  This may be caused by inappropriate settings for the DMA channel on the Server, or the DMA channel is not enabled.  On EISA systems, verify that the Server Manager Module board is properly installed using the EISA Configuration Utility (ECU); on ISA systems, verify that the SMMAGNT.NLM is given proper (non-conflicting) DMA channel information upon loading.
601	Bus relinquish failure	The Server Manager Module encountered an error while attempting to use the ISA bus.  This may be caused by inappropriate settings for the DMA channel on the Server, or the DMA channel is not enabled.  On EISA systems, verify that the Server Manager Module board is properly installed using the EISA Configuration Utility (ECU); on ISA systems, verify that the SMMAGNT.NLM is given proper (non-conflicting) DMA channel information upon loading.
602	Bus read failure	The Server Manager Module encountered an error while attempting to use the ISA bus.  This may be caused by inappropriate settings for the DMA channel on the Server, or the DMA channel is not enabled.  On EISA systems, verify that the Server Manager Module board is properly installed using the EISA Configuration Utility (ECU); on ISA systems, verify that the SMMAGNT.NLM is given proper (non-conflicting) DMA channel information upon loading.
603	Bus write failure	The Server Manager Module encountered an error while attempting to use the ISA bus.  This may be caused by inappropriate settings for the DMA channel on the Server, or the DMA channel is not enabled.  On EISA systems, verify that the Server Manager Module board is properly installed using the EISA Configuration Utility (ECU); on ISA systems, verify that the SMMAGNT.NLM is given proper (non-conflicting) DMA channel information upon loading.
604	IOCHRDY timeout error	The Server Manager Module encountered an error while attempting to use the ISA bus.  This may be caused by inappropriate settings for the DMA channel on the Server, or the DMA channel is not enabled.  On EISA systems, verify that the Server Manager Module board is properly installed using the EISA Configuration Utility (ECU); on ISA systems, verify that the SMMAGNT.NLM is given proper (non-conflicting) DMA channel information upon loading.
1100	User name is not valid	An attempt to add a new Server Manager Module user (or modify an existing user) failed because an poorly formed user name was given.  Valid user names are case-sensitive, up to 8 characters in length and contain upper and lower case letters, or digits (A-Z, a-z, 0-9).
1101	User name length is greater than 32 characters	The full name for a user name must be 1-32 characters long.
1102	Invalid password	An attempt to add a new Server Manager Module user (or modify an existing user) failed because an poorly formed password was given.  Valid passwords are case-sensitive, up to 8 characters in length and contain upper and lower case letters, or digits (A-Z, a-z, 0-9).
1103	Invalid privilege has been specified	An attempt to add a new Server Manager Module user (or modify an existing user) failed because an invalid privilege was specified.  Privileges are given as 'r', 'w', or 'a' (for Read-only, read-Write, and Administrator, respectively).
1104	User does not exist	An attempt was made to change or delete a Server Manager Module user that does not exist.  Check that the user name given is correctly spelled.
1105	Invalid port settings	An attempt was made to set the port settings on the Server Manager Module using a poorly formed port settings string.  Ensure that the correct format is used.  Example: to set the port to eight data bits, no parity, 9600 baud, one stop bit and XON/XOFF flow control, use "8N9600/1X".
1106	Requested data does not exist	An attempt was made to retrieve console or pager settings, but those settings have never been specified on the Server Manager Module.  Ensure that the console and pager have been configured.
1107	User data base is full	The user data base can have no more than 16 entries in it.
1108	User cannot be deleted	The users "root" and "alert" cannot be deleted.
1109	User already exists	An attempt was made to add a user that already exists.  Choose a different user name.
1110	Serial port failure (COM1)	Indicates that the Server Manager Module has an internal error in the serial port hardware.  Contact Service Personnel.
1111	Serial port failure (COM2)	Indicates a problem with the PCMCIA modem.  Check that the card in the PCMCIA slot is a recommended modem.  Try swapping the modem with a known working modem.
1112	PCMCIA modem failure	Indicates a problem with the PCMCIA modem.  Check that the card in the PCMCIA slot is a recommended modem.  Try swapping the modem with a known working modem.
1113	Invalid password length	Passwords must be 1-8 characters long.
1114	Session request failed	Indicates an internal error in the Server Manager Module.  Please contact your Service Personnel.
1115	Invalid phone number	The phone number given for the pager or Console was badly formed.  A phone number may consist of digits, the pound sign (#), asterisk (*), parentheses, dashes, and dial modifiers ( @ ! ; ,).
1116	User information cannot be modified	An attempt was made to modify the "alert" user.  This is not allowed.
1117	Login access violation	A login attempt was unsuccessful because an unregistered user name or incorrect password was used.  Check the user name and password and try again.
1300	Failed to contact the pager	The Server Manager Module attempted to deliver a pager alert but could not contact a pager service.  Check that the pager configuration is correctly set up and that the modem is connected to a working phone line.
1400	Log size too big	The Server Manager Module's log size must be set to 6000 characters or less.
1504	Upper threshold must be greater than lower	When setting thresholds *for temperature or voltage, the upper threshold must be set to a greater value than the lower threshold.  [Note that for normally negative parameters, the absolute values of the thresholds are compared.  For example, for -5V, the thresholds might be set to (-4, -6) where -4 is the lower threshold.]
1800	Access violation	A person attempting to log into the SMM failed to give a valid user name and password.
1801	Battery low	The battery on the SMM in the specified server is running low.
1802	Battery malfunction	The battery on the SMM in the specified server is failing to charge correctly.  Either the battery is not plugged in or the battery needs replacement.
1803	Panic	The firmware on the SMM encountered an unrecoverable error.  The error code and reason are given.  The SMM automatically reboots.
1804	Privilege violation	A user on the SMM attempted to execute a command but did not have rights to do so.  For example, a read-only user may have attempted to change the thresholds.
1805	Server hung	The specified server has stopped responding to the SMM.  Generally, this means that the operating system on the server has hung for some reason.
1806	SMM restart alert	The SMM has reset for an unexpected reason.  The reason is given.
1807	Low temperature	The low temperature threshold has been crossed on the given server.  Among other values, this error message also gives you the channel (on-board or remote probe) and the rate at which the temperature is changing.
1808	High temperature	The high temperature threshold has been crossed on the given server.  Among other values, this error message also gives you the channel (on-board or remote probe) and the rate at which the temperature is changing.
1809	Falling temperature	The rate of temperature decrease threshold has been crossed on the given server.  Among other values, this error message also gives you the channel (on-board or remote probe), the current reading, and the rate at which the temperature is changing.
1810	Rising temperature	The rate of temperature increase threshold has been crossed on the given server.  Among other values, this error message also gives you the channel (on-board or remote probe), the current reading, and the rate at which the temperature is changing.
1811	Low voltage	The low voltage threshold has been crossed on the given server.  Among other values, this error message also gives you the channel (+/5V, +/12V, or 3.3V) and the rate at which the voltage is changing.
1812	High voltage	The high voltage threshold has been crossed on the given server.  Among other values, this error message also gives you the channel (+/-5V, +/-12V, or 3.3V) and the rate at which the voltage is changing.
1813	Power failure	The power on the specified server has failed.  Either the power switch was turned off unexpectedly, the line power to the machine has failed, or the server's power supply is faulty.
1814	Server shutdown	The SMM has shut the server down because the temperature has reached a critical level.  The channel (on-board or remote probe) that caused the shutdown is given.
2400	Invalid number of arguments to the command	A command was given with the improper number of arguments.  (This error should never be seen when using the LANDesk Server Monitor Console.)
2401	Invalid argument	An invalid command argument was given.  For example, a text string was used where a number was expected.  Check that the arguments are correctly specified.  Refer to the User's Guide for information specific to each command.
2402	Positive value required	A negative number was given in a command where a positive value must be used.
2500	PCMCIA card removed from board	Indicates that the PCMCIA modem was removed from its slot.  This is an informational message only.
3200	Server rejected redirection request	The Server Manager Module attempted to begin console redirection, but the Agent on the server refused the request.  Make sure that the Agent (SMMAGNT.NLM) is properly loaded and configured.
3400	Server hardware does not support reset	Some servers contain special hardware that allows the Server Manager Module to reset the Server, some do not.  Whenever the Agent is loaded (SMMAGNT.NLM), it reads a file (HOBBSRV.HDW, found in the same directory as SMMAGNT.NLM), and notifies the Server Manager Module of the server's capabilities.  Check that this file appropriately reflects the server's hardware capabilities.
3401	Server hardware does not support power control	Some servers contain special hardware that allows the Server Manager Module to control the Servers power, some do not.  Whenever the Agent is loaded (SMMAGNT.NLM), it reads a file (HOBBSRV.HDW, found in the same directory as SMMAGNT.NLM), and notifies the Server Manager Module of the server's capabilities.  Check that this file appropriately reflects the server's hardware capabilities.
3402	Server denied reboot request	The Server Manager Module requested that the Agent perform a soft reboot of the server.  The Agent refused the request.
3403	Server is not currently running	An attempt to reboot the server was made when the Agent on the server was not loaded or executing.  Ensure that the Agent (SMMAGNT.NLM) is properly loaded and configured.
3404	Server power is already off	An attempt was made to turn off the server's power when it was already off.
3405	Operation on Server timed out	When the Server Manager Module performs a soft reboot of the server, it sends a message to the Agent on the server requesting that it reboot itself.  The Server Manager Module has timed out while waiting for a response.  Check that the Agent (SMMAGNT.NLM) is properly loaded and configured.
3406	Server power is already on	An attempt was made to turn on the server's power when it was already on.
3407	Flash memory reinitialized due to an access error	The Server Manager Module encountered an error when accessing is non-volatile memory.  The memory was reinitialized.  This will result in loss of all configuration information on the Server Manager Module and requires the user to re-enter this information.
3408	Server rebooted by SMM	The Server Manager Module performed a soft reboot of the server.  This is an informational message only.
3409	Server reset by SMM	The Server Manager Module performed a hard reset on the server.  This is an informational message only.
3410	Server powered off by SMM	The Server Manager Module turned the server's power off.  This is an informational message only.
3411	Server powered on by SMM	The Server Manager Module turned the server's power on.  This is an informational message only.
3412	Server did not power off	The Server Manager Module attempted to power off the server, but the power did not go off.  This may be due to a problem with the server's power control circuitry or with the hardware capabilities file (HOBBSRV.HDW) on the server.  Check that the capabilities file is correct for the particular server.
3413	Server did not power on	The Server Manager Module attempted to power on the server, but the power did not come on.  This may be due to a problem with the power sot the server, the server's power control circuitry, or with the hardware capabilities file (HOBBSRV.HDW) on the server.  Check that the server has AC power and that the capabilities file is correct for the particular server.
3414	No line power to Server	The Server Manager Module has recognized that the AC line power to the server is not available.  Check that the server is connected to a good power source.  [Note: This is only for servers that support the LPOK (line power OK) input on the Feature Connector.]
3415	Internal cable is disconnected	The Feature Connector or Xpress Reset cable is not connected between the Server Manager Module and the server's baseboard.  Check that the cable is connected and in good condition.
3416	Can't power off SMM while Server power is on	An attempt was made to power down the Server Manager Module when the server power was on.  This is not possible, since the Server Manager Module receives power directly from the server.
3417	Can't power off Server while SMM battery is disconnected or not working	The power control circuitry in some server designs require that the Server Manager Module hold the server's power off (as opposed to toggling its state).  For servers in this category, it is not possible to turn off the server while the Server Manager Module has a battery that is inoperable or disconnected.  Check that the battery is connected.  If the battery is connected, it may be failing, contact your Service Personnel.
3418	Can't power off SMM while it is controlling Server power	The power control circuitry in some server designs require that the Server Manager Module hold the server's power off (as opposed to toggling its state).  For servers in this category, it is not possible to turn off the Server Manager Module while it is holding the server's power off (otherwise, the server's power would immediately come back on).
3600	Video RAM size unavailable	Upon loading, the Agent on the server (SMMAGNT.NLM) informs the Server Manager Module of the server's video RAM address and size.  Make sure that the Agent is loaded and properly configured.
3700	Panic threshold cannot exceed 60 degrees	An attempt was made to set the shutdown temperature for the Server Manager Module to above 60 degrees centigrade.  The Server Manager Module must not be operated at temperatures exceeding 60 degrees centigrade.
3800	Invalid command	The command was unrecognized by the Server Manager Module.  Check the syntax of the command and/or refer to the User's Guide for help.
3801	A command is pending already	An attempt was made to issue a command to the Server Manager Module before the previous command had completed.  You can cancel the current command or wait until it has completed before issuing another command.
3803	This command is not valid in this session	An attempt was made to issue a Server Manager Module command that is not supported by the current session type.  For example, it is not possible to turn console redirection on within a TTY session.
3804	Privilege violation	An attempt was made to issue a command that requires greater privileges than the current user has.  For example, it is not possible to reset the server if the user account has read-only privileges.  Re-login using an account that has the proper privileges.
3805	Command canceled	The user canceled the current command.  This is an informational message only.


Comparision of LANDesk® Server Monitor Module and LANDesk® Server Control

The LANDesk Server Monitor Module is a product available separately from Intel's Server platforms.  This add-in ISA card and software are used to monitor and control the server, either via a network connection or via a modem connection.  It adds snap-in functionality to LANDesk Management Suite 2.0.  Its greatest impact is that it allows access to the server when the network is down or even when the server has lost power.

The LANDesk Server Control version 1.0 is only available with Intel's ALTServer products.  It allows server monitoring and control at the server itself, with messaging capability via SNMP. Its greatest advantage is that it requires no additional hardware.

Configuration Tips

Although both the LANDesk Server Monitor Module and the LANDesk Server Control are part of the LANDesk family of PC LAN Management, the Server Monitor Module and the Server Control do not interact with each other. Setting a threshold for the Server Monitor Module for the +12V will not be reflected in the LANDesk Server Control, for example.  Therefore, if both are used in the same system, the operator setting the thresholds and alerts must be cautious.  A recommended use for both would be to disable the voltage control functions with LANDesk Server Control (set all actions to No), as these features are duplicated with the SMM, and the SMM adds the advantage of allowing emergency access.  You may also want to disable some of the temperature monitoring, since there are four locations:  one within the INCA component, a second sensor on the system baseboard, one on the SMM add-in card, and one on a cable for your choice of locations.

If you have installed both SMM and LSC and want to:	Recommended actions:
Have an easy-to-read OK/NOT OK status for all sensors on one screen	Set voltage and temperature thresholds in LSC, and set the Information Level to BASIC.  The screen will show OK levels until a threshold crossed and then go into an error palette with message
Track voltage levels at the EISA bus	Set SMM voltage levels, and disable +5, +12, and -12V monitoring at the LSC.
Monitor temperature in a specific location	Use the SMM's remote temperature probe, and either disable the other temperature monitoring capabilities or be aware that they measure at a different location.
Write alerts to the chassis front panel LCD (if chassis supports this)	Must use alert events from LSC.
Use a Watchdog Timer to reset the system on a presumed system hang	Must use Watchdog Timer feature in LSC.
See alerts for two levels of a sensor (e.g. warning and fatal thresholds)	Use the LSC's alerts
Set alerts based on rate of change of a sensor	Use the alerts in SMM.
Have a wider range of alerting options	Use the alerts in SMM.
Feature Comparison

The following chart compares the features available with LANDesk Server Monitor Module and the LANDesk Server Control.

Feature	LANDesk Server Monitor Module	LANDesk Server Control
	Server UP	Server DOWN	Server UP	Server DOWN
SMM On-board Temp	x
Remote Temp	x
INCA Temp			x
Secondary INCA temp			x
+12V	x		x
-12V	x		x
+5V	x		x
-5V	x		x
+3.3V PCI	FC
+3.3V CPU	x		x
Chassis Intrusion			Chassis
Fan 1 operational			Chassis
Fan 2 operational			Chassis
Manual Reboot	x	Depends
Manual Reset	FC/ RC	FC/ RC
Auto Reboot	x		x
Auto Reset	FC/ RC		x
Power On	x	x
Power Off	x	x	x
POST Code Capture	x	x
Console Redirection	x	x
Watchdog Timer			x	x
NetWare monitoring	x
Notes:

"X" = Feature available under configuration described with no additional software/hardware

"FC" = Feature requires the SMM Feature Cable to be connected and operational

"FC/ RC" Feature requires either the SMM Feature Cable or a Reset Cable

"INCA" = Feature requires motherboard with INCA component (i.e., ALTServer or Xtended Xpress)

"Depends" = ability to reboot the system depends on the state of the system

"Chassis" = Feature requires chassis support


Considerations in Determining Analog-to-Digital Converter Accuracy on the Server Monitor Module

The accuracy of the Analog-to-Digital Converter (ADC) on the Server Monitor Module (SMM) is an important consideration in determining the validity of voltage  measurements, as well as the quality of the product.  To determine the accuracy of the SMM's ADC circuitry, one must compare the results given by the ADC to those of an independent, highly accurate measurement device. An important consideration in determining accuracy is the measurement technique.

The SMM's measurement technique is an instantaneous measurement of the voltage present at the input of the ADC.  The SMM was designed to be able to capture server power supply transients as short as 150us (about 6KHz cutoff frequency).

If the independent, highly accurate measurement device used to verify the SMM's ADC accuracy does not use a similar technique, the measurements cannot be compared, as they are completely different measurements.  For example, a Digital MultiMeter (DMM) uses an integrating filter to measure DC signals.  This filter completely blocks transients and noise which the SMM can detect and report, since it does not filter them.  Hence, the measurements cannot be compared to determine accuracy.  An oscilloscope, on the other hand, can also detect and report transients on server power supply lines, just as the SMM can.  However, careful consideration must be given to the oscilloscope probe placement, and other similar test bench factors which can add or subtract noise from a signal.

We set up a test system  to demonstrate this phenomenon.  A high-speed, calibrated oscilloscope was set up, and the probe attached for very low noise (very short loop area, signal to ground).  Also, a calibrated, low noise external power supply was attached to the SMM to provide a known, stable voltage.  The following waveform plot shows the noise induced by the server onto the power supply signal.  Channel 2 is the ADCCS# signal, which shows the time during which the ADC is sampling the waveform.  Channel 1 is the power supply noise (DC component is 5.00V).  The measurement by the oscilloscope shows the noise is 134mV peak to peak.

Most of the noise is in the tens of MHz range.  However, closer inspection shows noise transients in the KHz range, which the SMM can detect and report.  This noise is ignored by a DMM attached to the same signals as the oscilloscope.

The SMM reported the voltage fluctuating between 4.96 and 5.00 volts.  The DMM reported 5.00V continuously.  The oscilloscope shows (upon closer inspection of low frequency noise) transients in the frequency range the SMM can detect of about 35mV.  This is enough difference for the ADC to give a different output code (it only needs 20mV for this input), which accounts for the fluctuating reading.

Thus, SMM can appear to report "anomolous" voltage values when they are indeed actual voltages. The discrepancy comes in the comparison of these values with values derived from an incompatible or inappropriate measuring device.