Chip 1995 March

home *** CD-ROM | disk | FTP | other *** search

/ Chip 1995 March / CHIP3.mdf / demo / monitrix / disk1 / notes.txt < prev next >

Wrap

Text File | 1995-03-28 | 19.5 KB | 518 lines

Monitrix v3.00d Technical Notes ------------------------------- INSTALLATION NOTES ------------------ 1. IMPORTANT !!! Update your Windows 3.1 and NetWare drivers with the drivers that come with WINUP9.EXE, DOSUP9.EXE, and VLMUP2.EXE. These files can be down loaded from Novell's bulletin board. WINUP9.EXE contains updated Windows 3.1 NetWare drivers for VLM and NETX requesters. DOSUP9.EXE contains updated DOS client files for VLM v1.10 and NETX v3.32. VLMUP2.EXE contains the VLM v1.11 update kit. Install this update after installing DOSUP9.EXE update. Note1: If the updated drivers specified above are not used then the following Monitrix Manager problems might occur: 1. General Protection faults (especially in WBTRCALL.EXE and when connecting to different Monitrix Primary Servers.) 2. Btrieve errors (GPF's in WBTRCALL.EXE.) 3. NetWare Mapping errors (during install or when trying to connect to different Monitrix Primary Servers.) 4. Netware server connection problems. Note2: It is important that you install the Netware Driver updates properly. When using a Novell update, always update all files that were provided in the update. Failure to do so almost always leads to an inconsistent set of drivers on the workstation causing numerous problems. 2. Supervisory rights are needed to install Monitrix v3.0 on NetWare 3.1x and 4.x servers. 3. Please unload any previous versions of Monitrix and Alert before installation of Monitrix v3.0. 4. 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. 5. 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. 6. 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. 7. 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. 8. 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). 9. 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. 10. 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. 4. When Monitrix v3.0 is running on a NetWare v4.01 server an abend would occur as Monitrix explored the network. Novell has a communication fix called STRTL3.EXE. This self-extracting file contains communication patches which fix this problem. Netware version 4.02 and above already have this fix built into the OS and do not require this patch. This file can be down loaded from Novell's bulletin board. 5. You must load the DSAPI.NLM on 4.x servers before typing monstart at the server prompt, otherwise you will see messages like the following on the server console: Loader cannot find public symbol: NWDSCreateContext Loader cannot find public symbol: NWDSCreateContext Loader cannot find public symbol: NWDSMapIDToName ---------------------------------------------------------------- MONITRIX MANAGER ISSUES ----------------------- 1. When using IPXODI.COM, do not load it with the /D or /A options. These options disable the Diagnostic Responder and SPX support which are needed by the Monitrix Manager. Monitrix will not be able to load it's database (/A option) nor will it be able to view the Segments List under the Explore Segment dialog box (/D option). 2. 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. 3. 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. 4. 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). 5. 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. 6. 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. 7. 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} 8. 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). 9. 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 10. 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. 11. 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 ---------------------------------------------------------------- Fixes since Initial Release --------------------------- Monitrix 3.0 Revision D includes the following changes/fixes since its initial release: 1. Fixed bugs regarding auto-exploring NetWare servers. Primary Monitrix NLMs would fail to find NetWare servers or find NetWare servers and incorrectly identify the NetWare version. 2. The Monitrix Installation program would fail with a GP error if VLM v1.21 client software was used. This problem has been fixed. However, Monitrix cannot be installed on if Windows 3.11 or Windows for Workgroups 3.11 is installed on a server instead of a workstation. 3. The inventory process has been enhanced to gather more detailed information from Compaqs and pentium pcs. Video card memory and screen resolution are now gathered more accurately. 4. The PCINFO.EXE program has been updated as well. PCINFO.EXE can now run on diskless workstations and laptops. Previously PCINFO.EXE would hang laptop computers and diskless workstations. This problem was known to occur with Xircom LAN adapters. New PCINFO Options: If connected to network SYNTAX: PCINFO <Monitrix server name> -N -A -V Ex. PCINFO NY-GIANTS -N -A -V -N Skips software scan on workstations, but still inventories the hardware and network info. -A Auto login feature which allows you to attach to the Primary Server if you are not currently attached. Note: This feature does not work with secondary servers. -V Verbose mode, displays the results of the scan on screen If NOT connected to network (Stand alone) SYNTAX: PCINFO <dir path> <User Name> -N -V Ex. PCINFO a:\test Fred -N -V The above command will create a file called DOS.### on your floppy. You would then copy this file to your \Monitrix\dump directory on your Primary server. A node called Fred would then appear on your Monitrix database after Monitrix parses the file you created. For more syntax information just type PCINFO at the DOS prompt. 5. Previous Monitrix nlms for 3.1x and 4.x would cause Primary and secondary servers to hang during inital Monitrix startup when Auto-Detect SCSI was enabled. This bug has now been fixed. 6. Monitrix nlms have a new command line option. By default Monitrix NLMs will perform a self-inventory scan and 2.x server scan when first loaded. If you specify the 'N' parameter within the MONSTART.NCF file you will turn off this initial scanning process. The next scheduled self scan will take place 4 hours later on a primary server and 2 hours later on a secondary server. The purpose of this option is to allow the administrator to skip a possible long inital scan and begin auto-exploring the network immediately. Example of 'N' parameter format: SYS:SYSTEM\MONSTART.NCF file contents: LOAD ALERT.NLM BSTART LOAD SYS:\MONITRIX\NLM\MONITRIX N NOTE: The Monitrix console will display the following text upon startup when the 'N' option is used: Soft Inventory is OFF If the 'N" option is not used then the above statement will NOT be displayed. 7. The title database has been enhanced. The original released version of Monitrix 3.0 contained 1300+ titles. This release contains over 2000 titles, including MAC, OS/2, DOS, and Windows applications. The database also includes the latest Cheyenne applications which have been released as of March/1995. 8. Volume information was not accurately calculated for hard drives and has since been corrected. All hard drive sizes are also been converted to Megabytes instead of Kilobytes. ----------------------- End of Notes.txt -----------------------