Important Information about Intel(R) Server Control v2.5 August 18, 2000 Important Notes A. System Requirements B. Install C. Additional Instrumentation Setup D. Uninstall E. Enterprise Management Console Information F. Direct Platform Control G. Client System Setup Utility H. ISC Console I. Documentation J. General Information NOTE: Known issues with the ISC software are documented in a file called enuerrata.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 2000). *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. The DMI Service Provider Database does not relinquish space from expired and deleted registrations. This space is not reused by the Service Provider and causes the Database to continually grow. This issue can also be seen if components and groups are deleted from the Service Provider Database. Hewlett Packard proactively has announced an update to Network Node Manager* v5.02, patch release NNM_0085, which addresses the issue with the DMI* 2.0 Service Provider. Hewlett Packard will post the update to NNM v5.02 on the world wide web at: http://www.hp.com/go/openview. From this page select "support" and then "patches". Download the update and follow the instructions for installation. 2. For Windows 98* consoles, ISC setup requires that the following software components be installed: - Remote Registry Service The Remote Registry Service can be found on the Windows 98 Resource Kit. Other software applications may also require this software component, so it may already be installed on your system. Before installing ISC, install this software component and then reboot the system. To install the Remote Registry Service the user must be running Windows 98 and have the Resource kit in the CDROM drive then: 1. Access the control panel via "Start" 2. Double click on Network Icon 3. Access the "Configuration" tab 4. Select "service" 5. Press the Add button 6. Press the "Have Disk" button 7. Press the "Browse" button 8. Locate the drive containing the Resource Kit 9. Access the NetAdmin directory 10. Access the Remotreg Directory 11. Highlight "regsrv.inf" file 12. Press the "OK" button on the "Open" screen 13. Press the "OK" button on the "Install from disk" screen 14. Press the "OK" button on the "Select Network Service" screen Remote Registry service should have installed. Check the Configurations in the "Configuration" window and Remote Registry Service should be listed. Note: If the Remote Registry service is not installed on Windows 98, you will get the following error message after manually typing in the system destination: Intel Server Control Setup A dynamic link library (DLL) initialization routine failed. 3. For Windows NT* 4.0 consoles, DPC setup requires that the following software components be installed: - Service Pack 4 or above for Windows NT 4.0 - RAS (Remote Access Service) Note 1: If RAS is not installed on Windows NT 4.0 DPC will not install. Note 2: There is no DPC support for SBT2 & STL2 servers 4. NetWare* Client Services For Windows 95*, Windows 98, and Windows NT Microsoft NetWare Client Services on Windows 95 and Windows 98 DO NOT support DS (directory services) for NetWare systems. Consequently, if a NetWare server is configured not as a tree root, but rather as part of an existing tree it cannot be accessed remotely. However, Novell NetWare Client supports both Bindery and DS services. As a result, remote connection on Windows 95, Windows 98, and Windows NT systems is made possible for all NetWare servers. To summarize, if you are using a Windows 95, Windows 98, or Windows NT console to install remotely to a NetWare server that has been configured as a subtree, you need to install Novell NetWare Client Services. Additionally, you must log on as the administrator/supervisor of the network, not just as a user with administrator/supervisor rights for authentication on the remote server for the ISC Install. If you are not logged in as the administrator/supervisor or the network, ISC can not install to the remote server in a NetWare 5.0 tree. 5. ISC stand-alone is implemented as an ActiveX* control and can run in "container" applications that support ActiveX . Example "container" applications are: Microsoft Internet Explorer* (IE) Netscape Navigator* with plug-in that supports ActiveX controls such as: ScriptActive* by NCompass Labs Inc or Esker Plus 3.0* by Esker US Inc. or Microsoft Management Console (MMC). MMC requires IE v4.0 or higher. 6. 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" 7. UnixWare* 7.1 Requirements UnixWare installations must be installed with multi-processor support (osmp module) during installation or later. For information on adding the osmp package to UnixWare, see: http://www.sco.com/cgi-bin/ssl_reference?110311 The minimum recommended patch list for UnixWare 7.1 should also be applied. It can be located at: http://www.sco.com/support/toolbox/patch.html Please also install the VisionFS* package on the UnixWare server. 8. Intel Server Control supports servers with the following Intel baseboards: Intel(R) N440BX Intel(R) NL440BX Intel(R) AD450NX Intel(R) SC450NX Intel(R) AC450NX Intel(R) L440GX+ Intel(R) C440GX+ Intel(R) OCPRF100 Intel(R) SPKA4 Intel(R) SRKA4 Intel(R) SBT2 Intel(R) STL2 9. For OCPRF100 systems configured with 700MHz or faster Pentium(TM) III Xeon(TM) processors, it is necessary to have the following firmware installed on the system: BMC version 23 VMC version 09 SRPM8 SDR version 01 If these items are not installed on the system, the CPU voltages will display a critical health status in ISC. 10. On servers using LSI Symbios* SCSI controllers, (N440BX, NL440BX, SC450NX, AC450NX, OCPRF100), the 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.05.08 Windows NT : sym_hi.sys v 4.05.14 UnixWare : symc8xx.pkg v 4.21.00 NetWare : sym8xxnw.ham v 4.06.04 NetWare : symhinw.ham v 4.06.04 All versions of a driver are backward compatible within the same chipset. 11. 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" ********************************************************************** B. Install ********************************************************************** 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.04 or greater HPNNM - HP OpenView* Network Node Manager v5.02 with patch release NNM_0085 CA Unicenter TNG Framework* V2.1 or greater 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, or not all the sensor folders being displayed, or on rare occasions, it is possible for the former console (LSC) to be displayed due to the length of initialization of network protocols. 3. We recommend that you reboot your system (console or server) after installing any ISC component. 4. SCO UnixWare 7.1 system have DMI access set to read-only by default. This will prohibit ISC from changing thresholds, enabling the watchdog timer, and various other functions. In order for ISC to perform properly, the DMI SP write permission must be enabled. To enable DMI write permission on UnixWare 7.1, log in as 'root' and perform the following steps: 1. Stop the DMI Service Provider (dmi stop) 2. Edit the file S89dmi (in the directory /etc/rc2.d) 3. Change the line that says '$DMI_PATH $@' to '$DMI_PATH $@ -w' 4. Save the file and restart the service provider (dmi start will start the SP) Once this change is made to S89dmi file it is valid for all future sessions. 5. Under certain circumstances install's attempt to autologon to a local server may fail. Consequently, the server during boot up will display a message that autologon failed and that a password is required to continue with the system logon. To continue with ISC install simply logon to the server as you would normally do, and install will complete successfully. 6. Silent install A. Silent install will work best, if ISC is installed on one server at a time. B. If the current setting of Windows NT only accepts encrypted passwords then the user would not be able to connect to a SCO UnixWare server running SCO VisionFS. Setup will only modify the Windows setting during an interactive install session so that Windows NT can connect to SCO UnixWare server running VisionFS. For Silent install the user must set the registry settings himself as follow: 1- Locate HKLM\System\CurrentControlSet\Services\Rdr\Parameters 2- Create a string value = "EnablePlainTextPassword" 3- Set the data for the above string created to 1 (DWORD) 4- Reboot the system Important: NetWare and UnixWare servers must manually be rebooted after silent install is completed. C. In the text file that is created for silent install, if you are using Windows 98 to run install from, make sure the remote servers have the same user ID and password as the Windows 98 console you are logged on to. Otherwise, install will not be able to connect to the remote servers. 7. LANDesk integration will be done automatically if LANDesk is present on the system on which ISC is installed. 8. To upgrade from ISC 1.x to ISC 2.x on a console or a server, users must uninstall the old ISC version and then install the new ISC version. 9. If the CA-TNG integration is selected during install, the system will be rebooted twice. After the first reboot, the install will start the process to configure the CA-TNG for ISC integration and two dialog boxes will pop up to ask the user for repository name to sign on. However, these dialog boxes might be covered by the install shield and the dialog box asking the user to reboot the system. Please make sure to respond to the CA-TNG dialog boxes (by clicking the OK button) before the system gets rebooted in order for the integration to function properly after the second reboot. ********************************************************************** C. Additional Instrumentation Setup: ********************************************************************** 1. Depending on the baseboard type, the Intel Server Control software installs third party instrumentation (e.g., SCSI, NIC). 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 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) CC440GX+ DP Server: System Event Logging = Enable For Intel(R) OCPRF100 MP Server: System Event Logging = Enable For Intel(R) SPKA4 MP Server: System Event Logging = Enable For Intel(R) SRKA4 MP Server: System Event Logging = Enable For Intel(R) SBT2 MP Server: System Event Logging = Enable For Intel(R) STL2 MP Server: System Event Logging = Enable 3. By default, the ISC ICMB daemon on UnixWare system does not start automatically. To start the ICMB daemon , use the /etc/init.d/isc script with "start-icmb" or "stop-icmb" option. ********************************************************************** 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 enuerrata.txt file, along with possible workarounds. 2. We recommend that you reboot your system (console or server) after uninstalling any ISC component. 3. On Windows NT and Windows 2000* systems, in order to uninstall specific ISC components, you must execute the ISC setup program and select the uninstall option. Then you need to select the specific components that you want to remove. On previous versions of ISC, specific components could be removed from Control Panel "Add/Remove Programs". For ISC 2.x, the only uninstall option under Control Panel is to remove ALL components of ISC. ********************************************************************** 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. 3. If the LDSM snap-in is only installed on the server you are connecting to with LDSM, an Intel Server Control component will still appear in the snap-in folder. This indicates that the snap-in is supported by the server. If the snap-in is also supported on the client, an icon will appear next to the snap-in, identifying that it is ready to launch. 4. If multiple copies of the ISCLDSM.MIF file are installed on a server, then multiple instances of an Intel Server Control component will appear in the LDSM Console. 5. Multiple copies of Intel Server Control components may appear in LDSM if the newest patches are not installed. Patches or support exist for LDSM version 6.04 and greater. The patch releases can be downloaded from the Intel support website. http://support.intel.com/support/landesk/servermgrpro/software.htm 6. Intel Server Control components may not appear in LDSM if the newest patches are not installed. Patches or support exist for LDSM version 3.x and greater. The patch releases can be downloaded from the Intel support website. http://support.intel.com/support/landesk/servermgrpro/software.htm 7. Intel Server Control's AMS alert configuration support requires the LDSM components to be loaded before ISC components. If LDSM is loaded after ISC, an attempt to configure AMS alert actions will result in a message stating that the application is not registered with AMS. This can happen with NetWare servers if the SM_AUTO.NCF is run manually after the ISC support is already running. The best way to avoid this issue is to edit the 'REM Sm_auto.ncf' line that LDSM places in the AUTOEXEC.NCF by removing the 'REM'. Also, make sure that the 'Sm_auto.ncf' line precedes the 'ISC_ON.NCF' line. This will ensure that LDSM support is loaded before ISC support. 8. Intel Server Control's ni_nici.mib released in ISC 2.3 contains a correction that makes it incompatible with the ni_nici.mib released in ISC 2.1 and ISC 2.2. In order to load the new version of the ni_nici.mib and monitor IntelNIC events for ISC 2.3, any previously loaded ni_nici.mib must first be unloaded. ********************************************************************** F. Direct Platform Control: ********************************************************************** 1. Direct Platform Control (DPC) Console provides emergency management of servers remotely. DPC Console provides capabilities to power on or power off a server remotely, or help diagnose a problem on a server. DPC Console is independent of the Operating System installed on the server. DPC Console provides detailed information about the hardware components on the server. For more information, see the DPC Users Guide, ENUDPCUG.pdf, located in the installation directory. NOTE: DPC is not supported in SBT2 & STL2 servers. 2. Server-side modems are configured differently depending on the implementation of the EMP features in the firmware. The following modem configuration setting are required for the following servers: Modem Config Server List AUTO-ANSWER = ON N440BX, T440BX DTR = NORMAL RTS/CTS = OFF Modem Config Server List AUTO-ANSWER = ON L440GX DP through OCPRF100 MP DTR = NORMAL Modem Config Server List AUTO-ANSWER = OFF SPKA4, SRKA4 DTR = ALWAYS_ON ********************************************************************** G. Client System Setup Utility: ********************************************************************** Client Configuration: The Remote Access Service must be installed prior to installing the Client SSU on a Windows NT 4.0 system. NOTE: CSSU is not supported on SBT2 & STL2 servers. Server Configuration: CSSU requires a service partition to be installed on a server it is to connect to. Modem Configuration: The client and server each need to have a Hayes-compatible modem with a minimum speed of 19200 Kbps connected to them. On the server, the modem must be connected to the COM2 port. On the client side, the modem speed should be set to 19200 Kbps. On the server, the modem must be configured for auto-answer mode in order for Client SSU to be able to connect to it. The server's EMP BIOS setting "EMP Direct Connect/Modem Mode" must be set to "Modem Mode". Make sure the modem is connected to the server's COM2 port and powered on prior to setting this option. This will ensure that the modem gets initialized properly. The BIOS setting for EMP Restricted Mode Access needs to be set to disabled; otherwise, the server cannot be reset remotely. Notes: The Client System Setup Utility (CSSU) provides a way for users to configure system settings and view the system error log, sensor data records, and field replaceable unit information. When establishing a connection to a server using CSSU, the server is rebooted to a service partition that is located on a hard drive on the server. Depending on where the hard drive containing the service partition is located on the server, it can take a fair amount of time for the CSSU to be ready to accept user input. If there problems with the files on the service partition that prevent the service partition software from booting correctly, the CSSU will wait indefinitely for a response from the server that will never come. This waiting is done by design, since, as mentioned, the amount of time it takes for the server to boot to the service partition can vary from server to server. If, after waiting an extended period of time, you suspect that the server is not correctly booting to the service partition and the CSSU is not making a connection, you can terminate the CSSU and use DPC Console to try to reset the server and connect to the service partition. Since DPC Console has console redirection, you can tell whether the server is resetting correctly or whether there is a hardware problem that is causing CSSU to not be able to establish a connection to the service partition. ********************************************************************** H. ISC Console: ********************************************************************** 1. The ISC discovery process could be very slow on Windows 98. When the ISC stand-alone console is started on a Windows 98 system, the process can be very slow (comparing to NT) when trying to discover the entire subnet (0 ~ 255). The system is slowed down by the number of threads being started to run ISC discovery on all of the servers. Windows 98 does not handle large number of threads as well as NT and probably lowers priority on most of the discovery threads, which causes the ISC servers being added to the console in a slow manner. A work-around is to start each ISC discovery on a smaller range of IP addresses. Tests show reasonable performance on 128 ISC discovery threads (depending on available system resources), so a discovery on IP address range 0 ~ 255 can be split into two discoveries, 0 ~ 127 and 128 ~ 255. 2. During a discovery process, no hourglass or other feature is displayed to the user indicating that the discovery process is running. Since a discovery process can be slow, users should monitor the progress of the ISC console through the task manager. When the thread count reaches zero, addition discovery tasks can be initiated. 3. The Watchdog Timer is not supported on a server when managing that server through ICMB. Therefore, the user will notice that the Enable Watchdog Timer and Watchdog Timeout Value... items in the Configure dropdown menu will be grayed out when managing a server through ICMB. Similarly, restoring factory defaults is not possible when managing a server through ICMB so the Restore Factory Defaults item in the Configure dropdown menu will also be grayed out. 4. When ISC Console is invoked the first time in a user session with Netscape & Esker Plugin for ActiveX support, an icon with the Esker label may come up into foreground instead of ISC Control. Their logo icon may obstruct your view of ISC GUI & can be removed from view by minimizing and then restoring the Netscape window. ISC users can also simply view your bookmarks or bring another app to the foreground. After this initial restore, ISC & Netscape in successive views of Standalone console will work fine. ********************************************************************** I. 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. 2. On-line documentation for Intel Server Control is available in Adobe Acrobat* version 4.0 format (.PDF). Adobe Acrobat* Reader version 4.0 or higher is needed to read these files. You can obtain Adobe Acrobat* Reader v4.0 or higher, at the following location: http://www.adobe.com/products/acrobat/readstep.html ********************************************************************** J. 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 (for UnixWare and Linux see note below.) To delete the DMI database, follow these steps: 1a. On an Windows 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. NOTE: The DMI SP (dmispd) in UnixWare and Linux has the ability to shrink or compact the database to eliminate MIF components that have been removed. So, there is no need to delete the sldb.dmi database as described above. Starting the dmispd with "-r" command line option performs this shrinking operation. To enable this feature, edit the startup script (/etc/rc.d/init.d/dmisp in Linux and /etc/init.d/dmi in UnixWare) and add the "-r" option to the dmispd startup command. In UnixWare, it is also possible to start the dmispd by invoking the /etc/init.d/dmi with a -r option (see the manpage) but if you want the "-r" option specified at every reboot, it is suggested that you modify the script itself. 2. 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. 3. 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. 4. 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. 5. If the server is configured to use IDE instead of SCSI drives, there should be no negative impact leaving the installed SCSI IHV instrumentation executing. If system resources are an issue, the SCSI instrumentation may easily be prevented from executing the next time ISC starts as detailed below for each operating system. Windows NT and Windows 2000: 1. Open Control Panel, click on Services. 2. For each service to disable, double click on the service, select Startup Type, and set it to Manual. For servers using Adaptec* SCSI controllers, the services to set to manual are CIO Array Management Service, and Adaptec CIODMI. For servers using LSI Logic SCSI controllers, the service to set to manual is LSI SCSI Service. NetWare: 1. Edit the ISC_ON.NCF file. 2. For servers using Adaptec SCSI controllers, ensure that the remark indicator, "rem", begins the lines which would load nwaspi, iomgr and ciodmi. For servers using LSI Logic SCSI controllers, ensure that the remark indicator, "rem", begins the line which would load symcinw2. 3. Save ISC_ON.NCF. UnixWare: 1. For servers using Adaptec SCSI controllers, move the files iomgrd and ciodmi from the /intel/isc directory to another directory. For servers using LSI Logic SCSI controllers, move the file symciuw from the /intel/isc directory to another directory. 6. When a Windows NT or Windows 2000 server using an Adaptec SCSI controller boots, there may be numerous informational events titled CI/O Event for a Storage Device. These events correspond to SMART being enabled on each SMART capable SCSI drive in the configuration. Note: (*)Third-party brands and names are the property of their respective owners. ********************************************************************** End of readme file **********************************************************************