
			    Alert Version 3.0
		Copyright 1993-1995 by Cheyenne Software, Inc

  Cheyenne Software, Inc.               TEL (516) 484-5110
  3 Expressway Plaza                    FAX (516) 484-3446
  Roslyn Heights, NY 11577              BBS (516) 484-3445
  USA                                   CompuServe:  GO CHEYENNE

  =======================================================================


Alert.NLM and AIOCOMX.NLM
=========================
  AIOCOMX is a Novell NetWare NLM that handles serial port communications
  in the server.

  AIOCOMX will recognize an external modem if it is connected to the COM1 
  port.
  
  AIOCOMX will recognize an internal modem configured as COM1 with default 
  parameters.

  If the COM1 port is not available for a modem on the server,
  AIOCOMX must be loaded with non-default parameters. The following 
  command can be used to load AIOCOMX to recognize a modem configured
  on COM2:

	LOAD AIOCOMX PORT=2F8 INT=3 NODE=0

  Alert recognizes only the first COM port configured with AIOCOMX.

  For additional information regarding AIOCOMX, type "Load AIOCOMX ?" 
  at the server console.

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

  We strongly urge that you use the AIO.NLM dated 5/04/1994 and
  AIOCOMX.NLM dated 6/1/1994. If other versions are used Alert
  may take an inappropriate amount of time to detect and
  initialize the modem.  



Alphanumeric Pagers
===================
  ALERT.NLM supports alphanumeric pagers that comply with the Telocator
  Alphanumeric Protocol (TAP) V1.2 standard and can be accessed only via
  external modems.

  The alphanumeric paging service must provide access to an Alphanumeric 
  Terminal that complies with version 1.2 of the TAP standard.

  Sending Alerts to alphanumeric pagers via internal modems is currently 
  not supported. This is a limitation from AIOCOMX.NLM.
  
  Some paging vendors provide propietary access methods besides the TAP
  standard. If alphanumeric alerts messages are not being received, check
  with your paging service to determine which standard is being used with
  your pager.

  
NetWare 4.x and AIO.NLM
========================
  AIO is a Novell NetWare NLM that provides asynchronous I/O library and
  must be loaded before AIOCOMX.
    
  Currently, AIO.NLM does not load in protected domain, therefore neither
  ALERT.NLM nor InocuLAN.NLM can be loaded in protected domain if pager 
  features are to be used.


Technical Notes
===============

1. Application Configuration 
	Alert v3.0 allows you to configure alert options for individual
	Cheyenne applications. ARCserve v5.01 and InocuLAN v2.5/v3.0 can 
	be custom configured within Alert v3.0. Monitrix v3.0 uses the 
	default configuration only. 

2. SNMP alerts
	SNMP option has been enhanced. Alert can now send SNMP alerts to
	workstations using an SNMP manager such as NetWare's NMS 2.0x, and HP 
	Open View for Windows/Unix. Alert can send ARCserve v5.01, 
	Monitrix v3.0, and InocuLAN v2.5/3.0 alerts via all notification
	methods including SNMP. Alert v3.0 CANNOT send any alerts from 
	FAXserve 2.0 including SNMP.

3. Passwords
	Alert v1.x used the word "ALERT" as the default password. Alert v3.0
	uses no default password when first configured. Passwords are no 
	longer case sensitive (i.e. "TEST" is the same as "test").
	The System Password was removed in Alert v3.0 because the user is no
	longer is required to assign a system password for Alert.

4. Alert 3.0 is not capable of sending messages via a pager and a fax board 
   at that same time when using the same Fax/Modem board. Either the page 
   alert or the fax alert will not be sent. If you have separate boards then
   there will be no problem.

5. The Off Site Server option used in Alert v1.x is no longer supported. 

Cheyenne Product Compatibility Issues
=====================================

   Alert v3.0 is compatible with Monitrix v3.0, FAXserve v2.0, 
   InocuLAN v2.5/v3.0 and ARCserve v5.01. 

1. FAXserve 

   a. The FAXLIB.NLM (dated 6-8-93) shipped with FAXserve 1.x is not
   compatible with Alert v3.0. After installing Alert v3.0 please unload 
   FAXLIB.NLM and reload FAXLIB.NLM 2.00c (which is installed by Alert v3.0)
   on the server. If the older FAXLIB.NLM is loaded and you attempt to send an 
   alert via fax then you will see the following error in the message log: 

	Error sending fax [-0x204]

   b. Alert 3.0 is only compatible to Faxserve v2.0. If you are using FAXserve 
   1.x please upgrade to v2.0. If you currently have FAXserve 2.0 the please
   upgrade to FAXserve 2.0c. FAXserve v2.0c has been certified with NetWare
   NetWare v3.11, v3.12 and 4.1 platforms. Alert v3.0 ships with one certified
   nlm which is FAXLIB.NLM. You can obtain the entire certified FAXserve 2.0c
   nlm set from our Cheyenne BBS. 

2. ARCserve v5.01 

	Severity Message Levels
	-----------------------
	At present only ARCserve v5.01g sends Critical, Warning, and 
	Informational alert messages. Previous versions of ARCserve, such 
	as 5.01f, 5.01e, and 5.01d send informational alert messages only. To 
	receive all three notification message levels please upgrade to 
	v5.01g.
	
	Pager Issues
	------------
	ARCserve v5.01 sends pager notifications to alphanumeric pagers only.
	Therefore if you want Alert v3.0 to send an ARCserve alert via pager it 
	must have its Pager option configured for alphanumeric paging as well.
	If Alert v3.0 is configured to send alerts to a numeric pager only,
	then all critical messages generated by Arcserve v5.01 will not be sent 
	by Alert via pager option.  
	
3. InocuLAN v3.0

	To execute InocuLAN v3.0 from within NMS v2.0x the following files
	need to be copied to the NMS\BIN directory from the InocuLAN\
	directory: 

		CURE.DAT
		VIRUS.LST
		INMUNE.DAT

	The InocuLAN for Windows executable called INOCUWIN.EXE looks for
	the above files in the directory where InocuLAN was installed. 
	The problem is when you execute INOCUWIN.EXE from within NMS 2.0x
	the current directory becomes NMS\BIN and InocuLAN will display a
	dialog box indicating that the cure.dat file could not be found.
	InocuLAN can still be executed outside of NMS 2.0x without a problem.
	Just remember to update these three files in both the INOCULAN\ and
	\NMS\BIN directories when you update the InocuLAN v3.0 signature files.

Installation Issues
===================

	If possible install all Cheyenne applications before installing 
	Alert v3.0. The Alert v3.0 requires applications to be installed
	first to properly copy SNMP files specific to your application.
	If you do install InocuLAN, Monitrix, or ARCserve AFTER
	installing Alert v3.0 and you want to use the SNMP capability please
	perform a full Alert installation and include the Cheyenne application
	you just installed.  

	It is recommended that all Alert versions on each server in your 
	network be upgraded to Alert v3.0.







		
