Important Information about Intel Server Control v1.9 August 16, 1999 Important Notes A. System Requirements B. Install C. Additional Instrumentation Setup D. Uninstall E. Enterprise Management Console Information F. Intel Server Control GUI G. Documentation H. General Information NOTE: Known issues with the ISC software are documented in a file called errata.txt. Please review that file for any known product issues. ********************************************************************** Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel's Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. (Intel makes no representations or warranties and specifically disclaims all liability as to the sufficiency, reliability, accuracy, completeness or usefulness of information in this file or in the ISC software). Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to the information contained in this file and/or the ISC Software, specifications, and product descriptions at any time, without notice, (however, Intel has no obligation to provide modifications, updates or support for same.) (Copyright c Intel Corporation 1998). *Other product and corporate names may be trademarks or registered trademarks of other companies, and are used only for explanation and to the owners' benefit, without intent to infringe. ********************************************************************** ********************************************************************** A. System Requirements: IMPORTANT: There are specific software requirements for ISC, please refer to the "Installation Guide" for more information. ********************************************************************** 1. The minimum resolution to display the Intel Server Control Console is 800x600 pixels. 2. On NT 4.0 Workstation, Win95 and Win98 clients, the new system requirements are: Intel (R) Pentium Pro(R) microprocessor (200 mhz) or higher 64 MB Ram At least 60MB of available disk space 3. Mylex Instrumentation requires the Mylex Software Kit 1.06 or later to be installed. The software kit 1.06 can be downloaded from Mylex support web site http://www.mylex.com. 4. Some versions of the Mylex RAID driver (DAC960NT.SYS) available on Windows* NT 3.51, are incompatible with the Server Control software. Using these versions causes the operating system to crash. Before you enable the support for Mylex RAID devices in the Server Control software, use one of the following tested versions of this driver from Mylex: revision 4.01, 3/25/96, 10688 bytes revision 4.03g, 7/10/96, 11568 bytes 5. On Intel(R) N440BX and Intel(R) NL440BX servers, LSI Logic (Symbios) SCSI instrumentation will only work if you use the following versions (or later) of the drivers: NetWare : sym8xxnw.ddi v 2.02.03 NetWare : sym8xxnw.ham v 2.02.03 Windows NT : sym8xx.sys v 4.02.07 On Intel(R) SC450NX and AC450NX servers, LSI Logic (Symbios) SCSI instrumentation will only work if you use the following versions (or later) of the drivers: NetWare : sym8xxnw.ddi v 4.01 NetWare : sym8xxnw.ham v 4.00.14 NetWare : symhinw.ddi v 4.01 NetWare : symhinw.ham v 4.00.14 Windows NT : symc8xx.sys v 4.04.03 Windows NT : sym_hi.sys v 4.06 On Intel(R) OCPRF100 servers, LSI Logic (Symbios) SCSI instrumentation will only work if you use the following versions (or later) of the drivers: Windows NT : symc8xx.sys v 4.08.00 Windows NT : sym_hi.sys v 4.10.00 Unixware : symc8xx.pkg v 4.08.00 NetWare : sym8xxnw.ham v 4.04.00 NetWare : symhinw.ham v 4.05.00 All versions of a driver are backward compatible within the same chipset. 6. Customers using the Intel LAN Adapters should download and install the most current driver from the following Intel web site prior to installing ISC software. "http://support.intel.com/support/network/adapter/pro100/index.htm" 7. Intel Server Control supports servers with the following Intel baseboards and minimum BIOS revision levels: Intel(R) N440BX DP server PBA number 681234-400 or higher BIOS Revision N440BX (Production Release 1) or higher Intel(R) NL440BX DP PBA number 695741-201 or higher BIOS Revision NL440BX / T440BX (Production Release 1) or higher Intel(R) AD450NX MP I/O Baseboard number 662379-402 or higher BIOS Revision A450NX (Production Release 1) or higher Intel(R) SC450NX MP PBA number 688264-401 or higher BIOS Revision S450NX (Production Release 1) or higher Intel(R) AC450NX MP I/O Baseboard number 662379-402 or higher BIOS Revision Ak450NX (Production Release 1) or higher Intel(R) LA440GX DP I/O Baseboard number 704293-205 or higher BIOS Revision L440GX (Production Release 1) or higher Intel(R) OCPRF100 MP I/O Baseboard number 702647-501 or higher BIOS Revision (Production Release 1) or higher ********************************************************************** B. Install ********************************************************************** 1. The installation of Mylex instrumentation is not automated and needs manual setup. If a customer's server has a Mylex RAID card correctly installed, users are required to manually install the GAM* software in order to enable the Mylex instrumentation. To do that, use the SCSI Adapter applet of the Control Panel to install a new GAM driver. The GAM driver version 2.11 can be located on the server at %ISCPATCH%\CI\GAMSrvr\Nt after ISC 1.0 has been setup. After the GAM driver software is setup and the server has been rebooted as instructed, users are then required to run the GAM server setup under %ISCPATCH%\CI\GAMSrvr\setup.exe. The Mylex Mdacci Service must be manually configured as 'Manual' or 'Automatic' in the Service applet of the Control Panel. 2. The ISC services on a managed server may take a few minutes to completely initialize. The exact amount of time will vary depending on the speed of the server and the software installed. 3. Before loading either the SYMSDMS2.MIB or SYMBIOS2.MIB files in an EMC, previously loaded versions of SYMSDMS.MIB, SYMSDMS2.MIB and SYMBIOS2.MIB must be unloaded via the EMC's load/unload utility. The SYMSDMS.MIB file is obsolete, and should not be reloaded. 4. If a user installs ISC server instrumentation only and then at later time installs ISC StandAlone on the same server but at a different directory location, they will see the following error every time they reboot and login: "Ian_ac32.exe Initialization file error, unable to invoke file named above" The ISC expects both the server instrumentation and the StandAlone to be installed in the subfolders of the same location, such as C:\Program Files\Intel\ISC. ISC will not function properly if the path for the ISC server instrumentation and the StandAlone portion are different. The user will see the error at every reboot and login, if installing in this manner. We recommend that when a user installs ISC StandAlone onto a server that already has ISC server instrumentation running on it, they should select the same directory as when the server instrumentation was installed. 5. Instructions for installation on a NetWare server: TIRPC (Transport Independent Remote Procedure Call) needs to be configured on the NetWare servers before the ISC console can communicate with the servers. TIRPC.NLM v2.01a (10/7/97) or greater is needed to support NetWare 5.0. The required TIRPC files and installation instructions can be downloaded from the following Intel support website: http://support.intel.com/support/motherboards/server/isc/software.htm 6. Prior to installing ISC on Win95 as an installation console you must install the following: - Win95 SP1 - DCOM95 (dcom95.exe is on CD under \ISC) - Winsocket 2.0 (ws2setup.exe is on CD under \ISC) - Internet Explorer 4.0 SP2 - Remote Registry Service From a Windows 95 console you need to install the "Remote Registry service" (found on the Windows 95 CD). To install the user must be running Win95 and have the Windows 95 CD in the CDROM drive then: - Access the control panel via "Start" - Double click on Network Icon - Access the "Configuration" tab - Press the Add button - Double click on Services - Press the "Have Disk" button - Press the "Browse" button - Locate the drive containing the Windows 95 CD - Access the ADMIN directory - Access the NETTOOL directory - Access the REMOTREG directory - Highlight "regsrv.inf" file - Press the "OK" button on the "Open" screen - Press the "OK" button on the "Install from disk" screen - Press the "OK" button on the "Select Network Service" screen - You will be prompted to specify the setup directory on the Windows 95 CD to install additional system files and complete installation Remote Registry service should have installed. Check the Configurations in the "Configuration" window and Remote Registry Service should be listed. 7. Before installing ISC from a Windows 98 console you need to install the the following: - DCOM98 (DCOM98.exe is on CD under \ISC) - Remote Registry Service (found on the Windows 98 Resource Kit CD) To install Remote Registry the user must be running Win98 and have the Resource kit in the CDROM drive then: - Access the control panel via "Start" - Double click on Network Icon - Access the "Configuration" tab - Double click on Services - Press the Add button - Press the "Have Disk" button - Press the "Browse" button - Locate the drive containing the Resource Kit - Access the NetAdmin directory - Access the Remotreg Directory - Highlight "regsrv.inf" file - Press the "OK" button on the "Open" screen - Press the "OK" button on the "Install from disk" screen - Press the "OK" button on the "Select Network Service" screen - You will be prompted to insert the Win98 CD to install additional system files and complete the installation Remote Registry service should have installed. Check the Configurations in the "Configuration" window and Remote Registry Service should be listed. ********************************************************************** C. Additional Instrumentation Setup: ********************************************************************** 1. Depending on the baseboard type, the Intel Server Control software installs third party instrumentation (e.g., SCSI, RAID). The enabled/disabled status of the instrumentation varies depending on the server OS. See the Intel Server Control Installation Guide. 3. On supported baseboards ISC uses the Event Logging feature of the BIOS. To enable this feature, boot from your server's System Configuration Utility (SCU), System Setup Utility (SSU), or BIOS setup utility (F2) and set the following options under System Management Options: For Intel(R) N440BX DP server System Event Logging: Enabled For Intel(R) NL440BX DP server System Event Logging: Enabled For Intel(R) AD450NX MP server System Event Logging: Enabled For Intel(R) SC450NX MP server System Event Logging: Enabled For Intel(R) AC450NX MP server System Event Logging: Enabled For Intel(R) LA440GX DP server System Event Logging: Enabled For Intel(R) OCPRF100 MP server System Event Logging: Enabled Note: If the Clear Event Log Block option in CMOS Setup is enabled on a the server, some event information may be lost. ********************************************************************** D. Uninstall: ********************************************************************** 1. Several files may not be removed due to services that may be running during the ISC uninstall. These are documented in the errata.txt file, along with possible workarounds. ********************************************************************** E. Enterprise Management Console Information: ********************************************************************** 1. If ISC was operating via LDSM and LDSM continues to run while a remote server goes through a reboot cycle, then the handle information that LDSM is maintaining so that ISC can access that server is no longer valid after the server goes down. If LDSM attempts to launch ISC using the old information then it will fail. You can refresh the LDSM information by using the 'Apply' button from the launch window or select another area of LDSM and then reselect ISC, and then try to launch. 2. In order for the DMI-SNMP Translator traps to be displayed in the HP OpenView event windows, users need to use the EVENT CONFIGURATION menu item, pick the eEventGenerationXXX entry (where XXX is a DMI group name) in the "Enterprises" window, and then double click each trap under "Events for Enterprise eEventGenerationXXX" window. A "Modify Event" window will be displayed. Then go to the "Event Message" page and choose the "Log and Display in Category" radio button and choose the event category in which the users want the traps to display. ********************************************************************** F. Intel Server Control GUI: ********************************************************************** 1. The Refresh interval has been changed to 30 seconds. Keep this value at a minimum of 30 seconds. If the refresh interval is changed to less than 30 seconds, system resources may be depleted. 2. The Intel(R) server will generate an event for any threshold crossing regardless of the direction of the crossing. This means that customers should take great care in configuring event actions. For example, if the server is configured to broadcast a message when the CPU temperature crosses the upper non-critical threshold value, then the server will generate an event and broadcast a message when the CPU temperature rises and crosses from the upper non-critical threshold value (going to a worsening state). The server will also generate an event and broadcast a message when the CPU temperature drops and crosses the upper non-critical threshold value (going to a normal state). The events on more recent systems are more specific to the direction of the threshold crossing. ********************************************************************** G. Documentation: ********************************************************************** 1. On-line documentation for Intel Server Control is available in Adobe Acrobat* format (.PDF). The documentation is installed with the ISC software during installation into the %ISC_PATH%\DOCS directory. This includes a Intel(R) Platform Instrumentation Control User's Guide. There is also an Intel Server Control 1.9 Installation Guide in Word Document (.DOC) format. ********************************************************************** H. General Information: ********************************************************************** 1. The DMI database (sldb.dmi) could grow over time as MIF files are installed and un-installed. The DMI database does not reclaim or reuse the space when a MIF file is un-installed, so the database will grow even if the same MIF file is un-installed and then re-installed. If the size of the sldb.dmi file is a concern, the solution for reducing its size is to delete the file and rebuild the DMI database, keeping in mind that you will lose any threshold settings that are different from the default settings. To delete the DMI database, follow these steps: 1a. On an NT server, use 'Control Panel - Services' to stop the Win32 Service Provider (win32sl). 1b. On a NetWare server, unload the NetWare Service Provider (nwsl.nlm). Other nlm's that depend on nwsl will need to be unloaded also. 2. Delete the DMI database file (sldb.dmi) from the following two locations: For NT: a. %WIN32DMIPATH%\mifs b. %WIN32DMIPATH%\mifs\backup For NetWare: a. SYS:SYSTEM\dmi\netware\mifs b. SYS:SYSTEM\dmi\netware\mifs\backup 3. Any MIF files in the ...\mifs\backup directory that are no longer applicable to this server may be deleted also. 4a. On an NT server, move all MIF files except the service provider MIF, Win32sl.mif, from the %WIN32DMIPATH%\mifs\backup directory to the %WIN32DMIPATH%\mifs directory. 4b. On a NetWare server, move all MIF files except the service provider MIF, nwsl.mif, from the SYS:SYSTEM\dmi\netware\mifs\backup directory to the SYS:SYSTEM\dmi\ netware\mifs directory. 5. Re-boot the server. During the boot process, the DMI database will be rebuilt using the MIF files found in the ...\mifs directory. NOTE: When MIFs are un-installed and re-installed, the characteristics of the most recently installed MIF will be used for event generation. 2. The Mylex component instrumentation can potentially generate 87 event indications. The ISC software is capable of configuring actions responding to 9 of these indications. The DMI-to-SNMP translator, however, will translate all the 87 Mylex events into corresponding SNMP traps. You may be able to see all 87 SNMP equivalent traps via a third party SNMP console. For details on the 9 events supported in Mylex event configuration, please see the on-line help under Mylex event configuration. 3. When the Symbios NTSDMS.EXE is started, it begins a discovery process by scanning the Windows NT SCSI registry entries. However, Windows NT treats all ATAPI drives as if they were SCSI devices. The following Windows NT APIs are called by the Symbios service in order to determine whether the SCSI port registered with Windows NT is a Symbios controller: RegOpenKeyEx RegEnumKeyEx RegQueryValueEx In the case of some CD-ROMs, JAZZ* or Zip* drives, these drives may be present, but without media they will cause check conditions. The miniport driver for these types of devices report "No Disk in Drive x:". For a JAZZ or Zip drive and some CD-Roms this is a valid response and it fulfills the needs of the discovery process by providing information for identifying the device. For this reason the error message is ignored during the discovery process, the drive is 'discovered' and entered into the database of active and available peripherals and processing continues without any attention to the error message, "No disk in drive x: ." As such, this is a artifact of discovery and does not indicate a problem. The status is reconciled later during device polling when the 'discovered' devices are queried for their media status. 4. Customers using HP Openview should not load/install it on a server with LDSM. The HP Openview installation replaces the standard SNMP service handlers with its own, which do not currently handle an SNMP agent with multiple OIDs. This results in an SNMP query not working on the server where HP Openview is installed. Events will continue to be generated correctly, but an SNMP console will no longer be able to query for component information from the affected server. HP Openview should be installed on separate console computer. 5. The first time the server instrumentation runs after installation, all records of the System Event Log (SEL) are read and processed. The server instrumentation will start from the first record of the SEL and return a DMI indication for each record in the SEL. If SNMP services are enabled, then the server instrumentation will also generate a SNMP trap for each indication. All default LRA actions associated with each indication will occur (i.e., log to disk, popup messages, broadcast messages, write to LCD). These events will happen regardless of the date and time when the actual event happened that caused the SEL entry to occur. After the SEL file has been processed once, only new entries to the SEL will generate DMI indications and SNMP traps. 6. Users should not manually delete any instance of the "Intel Corporation ICMB Generic Chassis" MIF from the DMI database. These components are maintained by the ICMB instrumentation and unexpected results can occur if these MIFs are deleted by the user. 7. Users should be careful when configuring the ICMB discovery period. The default is five minutes. A very short discovery period may result in high system overhead which may prevent lower priority processes from running. ********************************************************************** End of readme file **********************************************************************