		 Monitrix v3.0 Technical Notes
		 -----------------------------
		      
		      
		      INSTALLATION NOTES
		      ------------------

    1. Supervisory rights are needed to install Monitrix v3.0 on
       NetWare 3.1x and 4.x servers.                

    2. Please unload any previous versions of Monitrix and Alert 
       before installation of Monitrix v3.0.

    3. When installing to 4.x servers and running VLM's, you must 
       first login to the 4.x server under bindery emulation with 
       supervisor equivalents before running the install.
 
    4. For Netware 4.x file servers, bindery emulation must
       be enabled.  If you are logged into Directory Services, 
       the Monitrix Setup program will NOT proceed. You can use 
       the "Set Bindery Context" console command to verify if
       bindery emulation is enabled. If it is not you can use
       the same command to enable it.

    5. Monitrix uses Btrieve v6.10c or higher. There are known
       problems with earlier versions of Btrieve so it is highly 
       recommended that you upgrade to Btrieve v6.10c during the
       installation of Monitrix v3.0. During the installation you 
       will be asked to overwrite older Btrieve files found on 
       your system. Select "YES" for each Btrieve file that needs 
       to be updated. 

    6. Btrieve must be configured properly on the NetWare 3.1x or
       NetWare 4.x server where Monitrix v3.0 was installed.
   
       Use BSETUP.NLM to enter new Btrieve parameters listed below.

       Recommended Btrieve values:

	Number of open files:           100
	Number of handles:              100
	Number of transactions:         100
	Number of locks:                200
	Number of remote sessions:      50

       Use BTRMON.NLM to verify your if your new Btrieve 
       configuration has been saved.

    7. PCINFO.EXE should be added to the file server system
       login script so that users who login will automatically
       have their computer's inventoried.  Use the following as an
       example:

       #<INSTALLED VOLUME>:<MONITRIX DIR.>\PCINFO <SERVER NAME> -V

       NetWare 4.x
       -----------
       When installing onto 4.x servers, all users that will be 
       logging in and running PCINFO.EXE should be assigned to the 
       group EVERYONE. The group EVERYONE is created by the 
       installation program if one did not exist before the start 
       of the Monitrix installation. 

       NetWare 3.1x and 4.x
       --------------------
       The group EVERYONE is assigned the proper trustee assignments
       to the Monitrix directory where Monitrix was installed. These
       trustee assigments allow for the proper operation of all 
       workstation agents (Monitrix agent, PCINFO, and CHEYMON).
  

    8. When installing Monitrix onto a workstation running NMS, the 
       following message may appear:
 
	 NetExplore Manager
	 Are You sure you want to quit ?

       If this message does appear, you must answer YES so that NMS
       can properly install Monitrix under it.

    9. Faxserve 2.0 Users
       The installation program for Monitrix (and Alert) installs 
       the version 1.0 FAXLIB.NLM file to the SYSTEM directory on 
       the Monitrix server. (The version 2.0 FAXLIB.NLM file 
       will not be overwritten if it exists.)

       If Monitrix (and Alert) is installed on a server different
       from the Faxserve v2.0 server, you may need to copy the  
       version 2.0 FAXLIB.NLM file that comes with Faxserve 2.0 to 
       the SYSTEM directory on the Monitrix server.

       This step is necessary if you want to Fax Alert messages 
       via the Faxserve 2.0 server.

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

		       MONITRIX NLM ISSUES
		       -------------------

    1. The versions reported for IPX, SPX, and Shell may vary
       depending upon when the station is scanned.  If the station
       is running Microsoft Windows at the time it may report a 
       different version than when MS-DOS is running.  This due 
       to the different drivers that are running under Microsoft 
       Windows.

    2. Btrieve can not be unloaded while Monitrix is running. 

    3. If SCSI Auto Detection is set to ON, after typing MONSTART
       on Primary or Secondary server, Monitrix.NLM will load two
       NLMs: ASPIAD.NLM and ASPIBT.NLM. These NLMs will unload 
       themselves after a short period of time. DO NOT TRY TO 
       UNLOAD THEM FROM THE SERVER CONSOLE. This may cause an ABEND.

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

		      MONITRIX MANAGER ISSUES
		      -----------------------

    1. Loading brequest.exe inside of winstart.bat may hang
       your system. If this occurs remove brequest.exe from the
       winstart.bat file (located in the windows directory) and load
       it before starting Microsoft Windows.

    2. Make sure that the novdb.ini file in the WINDOWS directory on
       your workstation contains: local=No in the section called 
       [brequestDPMI] when running MONITRIX. You may need to change 
       this back to "Yes" when running other applications that use 
       older versions of local Btrieve instead of the newer 6.x 
       network version.

    3. When installing secondary servers onto 4.x servers, all users
       that will be logging into and running PCINFO should be 
       assigned to the group EVERYONE. The group EVERYONE is created 
       during the installation of secondary server software to a 
       Netware 4.x server. The proper trustee rights are assigned to 
       the group EVERYONE on both NetWare 3.1x and NetWare 4.x 
       servers to allow for the proper operation of workstation
       agents (Monitrix agent, PCINFO, and CHEYMON).

    4. Use Brequest.exe version 6.10c (shipped with Monitrix) as it
       is known to be stable. Brequest.exe version 6.10d has caused
       problems when used with Monitrix v3.0.

    5. When using Monitrix on larger networks (>2000 nodes), the 
       response time for the intial load and refresh may be shortened
       by modifying Monitrix.ini in the Windows directory and setting 
       MaxNodes=2000 under the Settings Section as follows:

		[Settings]   
		MaxNodes=2000

       MaxNodes governs the number of nodes that Monitrix will 
       force fully load into it's browsers during startup and manual 
       refresh. All remaining nodes (above MaxNodes) will be loaded 
       in the background if the auto-refresh option is set. 

    6. There are two undocumented Monitrix.ini settings that can be 
       used to customize the default action taken when double 
       clicking on a Node in the Inventory and Monitor Node Browsers.

		[InventoryBarTool]
		DefaultSelect=2   {where 1=System, 
					 2=Network, 
					 3=Devices,
					 4=Volumes
					 5=Apps,
					 6=Config,
					 7=Env.
					 8=Asset,
					 9=Log,
					 default=2}

		[MonitorBarTool]
		DefaultSelect=1   {where 1=Alarm, 
					 2=Trend,
					 3=IPX,
					 4=SPX,
					 5=System, 
					 6=CPU,
					 default=1}

    7. The Monitrix Manager may experience problems attaching to 4.x
       Monitrix servers using the Set Server option in conjunction 
       with VLM's and NDS. If the Monitrix manager workstation is 
       logged into Netware (via v4.x servers) and is using VLM's and
       NDS while attempting to attach to a 4.x server within the 
       Set Server option you may experience attachment problems when
       selecting CONNECT. You can avoid this problem by using Bindery
       emulation when logging into Netware (via v4.x servers).

    8. Four new Reports were added but do not appear in the 
       documentation: 

	Notification by Alarm Type
	Notification by Notification Method 
	Environments by Node
	Nodes by Segment/Machine Type

    9. There may be problems printing non-realtime graphs. To get
       around this problem scroll through the entire graph before 
       attempting to print. NMS v2.1 will correct this problem.

    10.All printing of graphs and reports go to the default printer.
       If you experience problems printing, check to make sure that
       the default printer is set up properly via the Control Panel
       within Windows v3.1

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

			  OS/2 Issues
			  -----------

  1. To inventory an OS/2 v2.1 machine connected to a file server  
     perform the following steps from the OS/2 machine.

     Note: NetWare requester for OS/2 v2.01 must have been
	   previously installed on th OS/2 pc.

     a. Copy the OS2.CFG file from the Monitrix root directory on
	the Monitrix file server to any directory specified in the 
	COMSPEC path variable. You can view this variable by typing
	SET within the OS/2 Command Window.

     b. Executing CHEYMON.EXE

	1. Using command line 
	   i. Login to the Monitrix server using NetWare requester

	   ii. Map a drive letter , ex. F, to your Monitrix root 
	       directory where CHEYMON.EXE resides

	   iii. Open the OS/2 Full Window and enter the following
		command:

			 CHEYMON <SERVER NAME> -V
			     
		A Cheymon window should appear on the OS/2 desktop
		to indicate it is operational.

	2. Using OS/2 program icon
	   i. Repeat steps i and ii from above.
    
	   ii. Open the OS/2 System folder and double-click on the
	       Drive letter you used to map to the Monitrix root
	       directory, for example: F. A directory tree window
	       should appear for the drive letter you selected. 

	   iii. Double-click on the root of the tree. All files in 
		the Monitrix directory should appear. Highlight 
		CHEYMON.EXE and drag the file to the OS/2 desktop 
		by holding down the CTRL key and right mouse button. 

	   iv. Select the CHEYMON.EXE program item and click the 
	       right mouse button to open the Configuration menu. 
	       Select OPEN from the menu to display the Settings 
	       menu. Select Settings and enter the server name of a
	       Monitrix server (Primary or secondary) in the 
	       PARAMETERS field. 


	    v. Double-click on the icon to display the Cheymon agent
	       window and inventory the workstation.

	       Note that you must be logged into the Monitrix server 
	       when you execute CHEYMON.EXE, otherwise; the OS/2 
	       agent will not operate.

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

		      User Manual Supplement
		      ----------------------

			   Pager Codes
			   -----------
    Pager codes you receive on your pager have the following format:

    (Pager_ID) (Alarm Category) - (Alarm Type) - (Node ID) - (Value)

    Pager ID - refers to Pager ID number entered in the Pager 
	      Notificaton screen. 

    Node ID - refers to the node id number assigned to the node that 
	     was assigned the alarm. Each node record is assigned a 
	     unique node ID number by Monitrix. The administrator 
	     cannot change this number.      

    Value - refers to the actual value of the alarm.

    Alarm Category/Types - there are six alarm categories. Each 
		    alarm category has numerical value associated
		    with it. You can view the alarm categories and
		    types by displaying the Alarm Defaults screen
		    within the Monitrix Manager.

	Alarm Category - Type   Numerical Equivalent
	---------------------   --------------------
	Volume - Free Space            1 - 1
	Volume - Mount Status          1 - 2

	Memory - Cache Buffers         2 - 1

	Traffic - SPX Transmit         3 - 1
	Traffic - SPX Receive          3 - 2
	Traffic - IPX Transmit         3 - 3
	Traffic - IPX Receive          3 - 4
	Traffic - IPX Socket           3 - 5
	Traffic - Driver Transmit      3 - 6
	Traffic - Driver Receive       3 - 7

	Utilization - Open files       4 - 1
	Utilization - Buffers          4 - 2
	Utilization - Connections      4 - 3
	Utilization - CPU              4 - 4
	Utilization - Disk Pending     4 - 5
	Utilization - File Processes   4 - 6

	Machine - Connectivity         5 - 1
 
	Software - Blacklisted         6 - 1


    Example: Let us say you assigned a Volume - Free Space alarm
	     to the file server NY-GIANTS. You want to notify 
	     Joe Smith when the server NY-GIANTS has less than 10%
	     of total disk space available on volume SYS.

	    1. You would enter the following information in 
	       the Pager Notification screen:
		
		USER: Joe Smith
		Phone: 555-123-4567
		Pager ID: 10 (optional, depends on pager service)

	    Note: You would select the appropriate pager type and
		  configure the modem settings screen according to
		  modem type.
		
	    When the disk space goes below 10% Monitrix will send
	    the alarm by modem. You would receive the following
	    pager code on your pager:

			1 - 1 - 23 - 8  where
 
			
			1  - Alarm Category 1 (Volume)
			1  - Alarm Type 1 (Free Space)
			23 - Node ID for NY-GIANTS  
			8  - 8% of sys volume is available                                                                                              

    ----------------------- End of Notes.txt -----------------------


