Important Information about Intel Server Control v1.10.x July 1, 1999 Important Notes A. System Requirements B. Installation C. Additional Instrumentation Setup D. Uninstallation E. Enterprise Management Console Information F. Documentation G. General Information NOTE: Known issues with the ISC software are documented in a file named 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 1999 *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: ********************************************************************** 1. For Win95* consoles, ISC setup requires that DCOM95 be installed. Other software also requires DCOM95, so it may already be installed on your system. If you attempt to install ISC and receive the message "unable to load Atl.dll," then DCOM95 is either not installed or not up-to-date on that Win95 system. Before installing ISC, execute/install DCOM95.exe and then reboot the system. Dcom98.exe is the corresponding update for Win98. 2. The ISC stand-alone Console is implemented as an ActiveX control and can run in "container" applications that support ActiveX . Example "container" applications are: Microsoft Internet Explorer (IE) v4.01 SP1 Netscape Navigator(TM) v4.5 with snap-in that supports ActiveX such as: ActiveScript by NCompass Labs, Inc. Microsoft Management Console (MMC). MMC requires IE v 4.0 or higher. 3. Customers using the Intel EtherExpress(TM) Pro/100b LAN Adapter should download and install the most current driver from the following Intel web site prior to installing ISC software: "http://support.intel.com/support/etherexpress/ pro100/software.htm" 4. Intel Server Control supports servers with the following Intel baseboards and minimum BIOS revision levels: Intel(R) SC450NX MP PBA number 688264-401 or higher BIOS Revision S450NX (Production Release 1) or higher Intel(R) LB440GX DP I/O Baseboard number (No information yet) BIOS Revision L440GX (Production Release 3) or higher ********************************************************************** B. Installation ********************************************************************** 1. The Setup utility will only enable the Local Console install if a supported EMC (Enterprise Management Console) environment is detected on the installation machine. Supported EMCs are: LDSM - LANDesk(R) Server Manager v6.03 HPNNM - HP OpenView* Network Node Manager v6.0 CA Unicenter TNG Framework V2.2 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. If an ISC console is started in order to manage the server, prior to all the services being initialized, then ISC may display incomplete information. This may also be reflected in sluggish response from the console, not all the sensor folders being displayed, or, on rare occasions, it is possible for the former console (LSC) to be displayed 3. It is recommended that you reboot your system (console or server) after installing any ISC component. 4. The following are instructions for installation on a Solaris server: 1. Load the ISC CD-ROM into the local windows console system and change the directory to \isc\Solaris. 2. Open an ftp session to the Solaris server. Change the mode to binary. Put the ISCSOL.PKG file on this server, into any directory, such as . Close the ftp session. 3. Log in as root on the Solaris server. 4. Issue the command "pkgadd -d /ISCSOL.PKG". Follow the installation prompts to accept the license agreement and install confirmation. Note: is the directory name used in step 2. 5. Please reboot your Solaris server after the installation is completed. ********************************************************************** C. Additional Instrumentation Setup: ********************************************************************** 1. Depending on the baseboard type, the Intel Server Control software installs third party instrumentation (such as, SCSI or RAID). The enabled/disabled status of the instrumentation varies depending on the server OS. See the Intel Server Control Installation and User's Guide. 2. 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) SC450NX MP server System Event Logging: Enabled For Intel(R) LB440GX DP server System Event Logging: Enabled 3. The Network Interface Card (NIC) Lan adapter component instrumentation delivered with ISC v1.10, does not generate DMI events. Since there were no DMI events to trigger alert actions this component (IntelNic) was removed from the 3rd Party folder of the ISC components tree. NIC Statistics for the NT Operating System Environments are collected and available for viewing with the DMI Explorer. For additional information see the Intel DMI-SNMP Client Instrumentation v1.0.0 document (included as NicDmiNT.txt in the CD-ROM NT IntelNic folder and %ISCPATH%\CI when installed), Summary of Features, item b. Attributes support. 4. In Solaris 7, the default system log only log error and alert to /var/adm/messages. Some of the event generated by ISC is of information type (e.g. "Status Changed to OK"). To enable logging those event in /var/adm/messages, user need to modify /etc/syslog.conf to include logging of daemon.info type message to /var/adm/messages. 5. In order for ISC to forward SNMP trap correctly under Solaris 7, A patch for the Solaris 7 is required. The patch number is 107710-03. The patch can be downloaded from Sun Microsystem's web site http://sunsolve.sun.com. 6. There is additional configuration steps required in order to correctly set up the ISC related SNMP traps. Please consult the QuickStart guide for details. ********************************************************************** D. Uninstallation: ********************************************************************** 1. Several files may not be removed due to services that may be running during the ISC uninstallation. These are documented in the errata.txt file, along with possible workarounds. 2. We recommend that you reboot your system (console or server) after uninstalling any ISC component. 3. The following are instructions for uninstallation on a Solaris server: 1. Log in as root onto the Solaris server. 2. Issue a "pkgrm isc" command. Follow the prompts. 3. Please reboot your Solaris server after isc has been uninstalled. ********************************************************************** 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, it will fail. You can refresh the LDSM information by using the 'Apply' button from the launch window or selecting another area of LDSM and then reselecting ISC, and then trying to launch. 2. In order for the DMI-SNMP Translator traps to be displayed in the HP OpenView event windows, you 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 you want the traps to display. 3. MIB file for use with Enterprise Management Console are included in %ISCPATH%\SnmpMibs on the ISC managed server. ********************************************************************** F. Documentation: ********************************************************************** 1. On-line documentation for Intel Server Control is available in Adobe Acrobat* format (PDF). The file name of the User Guide is Isc110.pdf or Isc1101.pdf depending on the version of ISC software that is being used. 2. An Adaptec readme.txt file is included in the distribution media NT\Adaptec folder (and Server %ISCPATH%\CI folder also) that covers installation issues for the Adaptec instrumentation and hardware. Some items of note are tips for installing SAFTE, DMI, SNMP, NT installation notes, other miscellaneous workarounds and help. 3. An Intel LAN readme files (nicdmint.txt) is included in the NT\IntelNic folder (and Server %ISCPATH%\CI folder also) that contain useful descriptions and information for the LAN Adapter drivers and instrumentation. ********************************************************************** G. General Information: ********************************************************************** 1. The DMI database (sldb.dmi) could grow over time as MIF files are installed and uninstalled. The DMI database does not reclaim or reuse the space when a MIF file is uninstalled, so the database will grow even if the same MIF file is uninstalled and then reinstalled. 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. This issue only exhibit in NT version of the ISC. To delete the DMI database, follow these steps: 1. On a Windows NT server, use 'Control Panel - Services' to stop the Win32 Service Provider (win32sl). 2. Delete the DMI database file (sldb.dmi) from the following two locations: For Windows NT: a. %WIN32DMIPATH%\mifs b. %WIN32DMIPATH%\mifs\backup 3. Any MIF files in the ...\mifs\backup directory that are no longer applicable to this server may be deleted also. 4. On a Windows NT server, move all MIF files except the service provider MIF, Win32sl.mif, from the %WIN32DMIPATH%\mifs\backup directory to the %WIN32DMIPATH%\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 uninstalled and reinstalled, the characteristics of the most recently installed MIF will be used for event generation. 2. The Adaptec component instrumentation can potentially generate 77 event indications. These 77 events fit into 11 unique catagories for the purposes of configuring ISC alert actions. However the DMI-to-SNMP translator will deliver all 77 Adaptec events as unique traps to a third party SNMP console. 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 (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. You 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. 7. You 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 that may prevent lower priority processes from running. 8. Starting with ISC v1.8, a legacy (ISC v1.7, LDSM 3.0 and earlier ) console may no longer be able to view or manage the updated (DMI 2.0-compliant) Third Party components on a newer (ISC v1.8 or later) instrumented server. If the Third Party component is visible in ISC, you may still manage it. New events and indications are not supported by the older instrumentation and therefore will not appear. 9. In Solaris, only error and alert type messages are log into the system log. Informational type message are not logged. Some of the system log message generated by the ISC software are of type Informational (e.g. "Status Changed to OK"). In those cases, those messages are not logged into the system log by default. To configure the system to log the informational type message, user can modify /etc/syslog.conf so that it contains the line "user.info /var/adm/messages" within the ifdef('LOGHOST',...) block. For more details on configuring syslog.conf file, please consult the corresponding Solaris documentation. This change enables the system logging of all informational type messages by all processes into the system log. ********************************************************************** End of readme file **********************************************************************