Important Information about Intel(R) Server Control (ISC) v3.5.2 March 5, 2002 Important Notes A. System Requirements B. Install C. Additional Instrumentation Setup D. Uninstall E. Enterprise System Management Console (ESMC) Information F. Direct Platform Control (DPC) G. Client System Setup Utility (CSSU) H. Independent Hardware Vendor (IHV) Instrumentation I. LanAlert Viewer J. Documentation K. Platform Instrumentation Control (PIC) L. Platform Instrumentation (PI) M. Special instructions for Novell NetWare v5.1 and v6.0 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, nor shall Intel bear any liability whatsoever for any such changes or modifications.) Copyright (c) Intel Corporation 2002 Intel, LANDesk, and EtherExpress are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. * Other names and brands may be claimed as the property of others. ************************************************************************** ************************************************************************** A. System Requirements: ************************************************************************** 1. The following operating systems are supported for Intel Server Control (ISC) platform instrumentation software: Managed Server Operating Systems: - Microsoft* Windows* 2000 Advanced Server SP2 - Microsoft Windows NT* 4.0 Server SP6a - Novell NetWare* 5.1 SP2A and 6.0 - Red Hat Linux 7.1 & 7.2 - Caldera OpenUnix* 8.0 Console Operating Systems: - Microsoft Windows 2000 Advanced Server SP2 - Microsoft Windows 2000 Professional SP2 - Microsoft Windows NT 4.0 Server SP6a - Microsoft Windows NT 4.0 Workstation SP6a 2. For a list of supported features on each platform, please see the Platform Compatibility Matrix in the ISC Installation Guide. 3. For Windows NT 4.0 consoles, setup of Direct Platform Control (DPC) requires that the following software components be installed: - Service Pack 6a or above. - RAS (Remote Access Service), if the connection will use a modem. See Windows Help for RAS installation instructions. 4. Netware Client Services For Windows NT: Microsoft Client Services DO NOT support directory services (DS) for Netware systems. Consequently, if a Netware server is configured so that it is not a tree root, but rather is part of an existing tree, it cannot be accessed remotely. However, Novell Netware Client supports both Bindery and DS services. If you are using a 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. Also, to ensure authentication on the remote server for the ISC Install, you must log on as the administrator/supervisor of the network, not just as a user with admin/supervisor rights. If you are not logged in as the administrator/supervisor of the network, ISC cannot install to the remote server in a Netware 5.1 & 6.0 tree. 5. Before installing ISC software, customers using the Intel EtherExpress(TM) PRO/100b LAN Adapter or other Intel LAN adapters should download and install the most current driver from: http://support.intel.com/ 6. ISC 3.5.2 software supports servers with the following Intel baseboards: Intel(R) SCB2 Intel(R) SDS2 7. Systems with the above baseboards support remote BIOS updates with initial revisions of BMC firmware and ISC software. The Client System Setup Utility (CSSU) will support remote updates of BMC firmware and HSC firmware on systems using those baseboards in ISC 3.5.x and BMC firmware production software. ************************************************************************** B. Install ************************************************************************** 1. The Setup utility will enable the Local Console install only if a supported Enterprise System Management Console (ESMC) environment is detected on the installation machine. Supported ESMCs are: HPNNM - H-P OpenView* Network Node Manager v6.1 with patch release NNM_0085 CA Unicenter TNG Framework V2.4 For OpenUnix or Linux servers, you must individually install ISC on each system. Choose the installation instructions in the Install_Guide or in this Readme file, according to the operating systems you use. 2. The ISC services on a managed server can 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, ISC may display incomplete information. This may also be reflected in sluggish response from the console or not all the sensor folders being 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. Silent Install A. Silent install works best if ISC is installed on one server at a time. B. To install remotely to a Windows 2000 or Windows NT system, you must use the same user ID and password in the configuration file as the one you use to login to the Windows 2000 or Windows NT system. C. Netware servers must manually be rebooted after silent install is completed. 5. Before installing ISC on OpenUnix systems, do the following on each server: A. Mcopy must be installed on each server. Please refer to the man page for doscp for download and install instruction for mcopy. Mcopy can also be installed by installing the mtools package from the OpenUnix 8.0 Skunkware 8 CD-ROM. B. Desktop Management Interface (DMI) must be installed on each server. By default, OpenUnix systems have DMI access set to read-only. This setting prevents ISC from changing sensor thresholds, enabling the watchdog timer, and executing other functions. To allow ISC to operate correctly, DMI access write permission must be enabled after the DMI installation. Use the following steps: 1. Log in as 'root'. 2. Stop the DMI Service Provider (dmi stop). 3. Open the file /etc/rc2.d/S89dmi for editing. 4. In the dmistart() function, change the line '$DMI_PATH $@' to read '$DMI_PATH $@ -w'. 5. Save the file and restart the DMI Service Provider (dmi start). This change will remain valid for all future sessions. 6. Installation steps for OpenUnix Servers 1. Insert the System Resource CD into the OpenUNIX server CD drive. 2. Enter the mkdir command as follows: mkdir /cdrom 3. Enter the mount command as follows: mount –r –F cdfs /dev/cdrom/cdrom1 /cdrom 4. The ISC package is located in /cdrom/CD/Software/OpenUNIX/iscou.pkg; to install ISC, enter the command: pkgadd –d /cdrom/isc/software/openunix/iscou.pkg 5. Follow the instructions on the screen, which prompts you to read and accept a license agreement. 6. After successful installation of ISC the software prompts you to reboot the system. First unmount the CDROM so you can remove the CD, then reboot the system: umount /cdrom shutdown 7. Customizing OpenUnix Servers after Setup. The set action of some SNMP attributes causes the server to shutdown/power off. Perform these two steps to globally disallow all set requests: 1. Change the ReadOnly entry in the /usr/local/isc/bin/sdlink.cfg file to True 2. Reboot the server. ************************************************************************** C. Additional Instrumentation Setup: ************************************************************************** 1. Depending on the baseboard type, the ISC software installs third party instrumentation (e.g., SCSI, NIC). The enabled/disabled status of the instrumentation varies depending on the server OS. For more details see the ISC Installation 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) and set the following item under System Management Options: System Event Logging = Enable 3. The broadcast action of ISC applies to all active connections. In Windows NT or Windows 2000, even if the connection to a server is persistent, the OS might use a "lazy connection algorithm." This means the connection might not be actually made until there is a need for it (such as when a user clicks on a drive name to expand the content). In such a case, the broadcast would not apply to those non-active connections. 4. By default, the ISC ICMB daemon/service does not start automatically. The service must be started in order for ICMB support to be enabled. To start the ICMB daemon/service manually: - On Windows NT 4.0, launch the Services applet under the Control Panel and manually start the "Intel EIF Agent" service. - On Windows 2000 Advanced Server, launch the Services applet under Administrative tools and manually start the "Intel EIF Agent" service. - On NetWare 5.1 or 6.0, edit the SYS:\SYSTEM\AUTOEXEC.NCF file to uncomment the line "rem load eif" so that it reads "load eif" instead. - On Red Hat Linux 7.1 and 7.2, there is no ICMB support. ************************************************************************** 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. 2. We recommend that you reboot your system (console or server) after uninstalling any ISC component. 3. OpenUnix Systems You must uninstall ISC locally from each OpenUnix system. To do so: 1. Log in as 'root'. 2. Enter the command: pkgrm isc 3. Follow the instructions on the screen. ************************************************************************** E. Enterprise System Management Console (ESMC) Information: ************************************************************************** 1. For the DMI-SNMP Translator traps to be displayed in the H-P OpenView event windows, you must: A. Use the EVENT CONFIGURATION menu item. B. Choose the eEventGenerationXXX entry (where XXX is a DMI group name) in the "Enterprises" window. C. Double-click each trap under the "Events for Enterprise eEventGenerationXXX" window. D. A "Modify Event" window will be displayed. E. Go to the "Event Message" page and choose the "Log and Display in Category" radio button. F. Then choose the event category in which you want the traps to display. 2. Customers using H-P Openview should not load or install it on a server with LDSM. The H-P 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 H-P 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. H-P Openview should be installed on a separate console computer. 3. 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 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. H-P will post the update to NNM v5.02 at: http://www.hp.com/go/openview. From this page select "support" and then "patches". Download the update and follow the instructions for installation. This problem has not been seen with Network Node Manager v6.1. 4. When using CA-TNG Unicenter, the possibility exists that after double clicking on the ISC WorldView icon in the 2D map, no ISC server icons will appear. If this occurs, there are two actions that can be taken that may remedy the situation. Attempt action one first and if that is unsuccessful, attempt action two. Steps for action one: 1. Right click My Computer icon on desktop. 2. Select "Manage" menu item. 3. Expand "Services and Applications" folder in Computer Management dialog box. 4. Select Services item. 5. Right click Intel TNG-ISC AutoDiscovery service. 6. Select Stop. 7. Wait for service to stop. 8. Right click Intel TNG-ISC AutoDiscovery service. 9. Select Start. 10. Check 2D map in CA-TNG Unicenter for ISC server icons. Steps for action two: 1. Select Start -> Programs -> Unicenter TNG Framework -> Repository Import Export. 2. Select Repository. 3. Select Actions -> Import Repository ... menu item. 4. Select Add Scripts ... button in Import Repository dialog. 5. Navigate to the :\TNGFW\Bin folder. 6. Select the IscClass.tng file that appears. 7. Click Start button in the Import Repository dialog. 8. Click the OK button in the Import Completed dialog. 9. Close the Import Repository dialog. 10. Close the Unicenter TNG Repository Import Export dialog. 11. Select Yes to save changes if you desire, but it is not necessary. 12. Check 2D map in CA-TNG Unicenter for ISC server icons. ************************************************************************** F. Direct Platform Control (DPC): ************************************************************************** 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, file ENUDPCUG.pdf, located under the installation directory with other ISC documentation. For the supported DPC features on each server, please see the Platform Compatibility Matrix in the ISC Installation Guide. 2. The following modem configuration settings are required for all servers: Modem Config AUTO-ANSWER = OFF DTR = NORMAL 3. With a serial connection to a server using the SCB2 or SDS2 baseboard, a at the console may drop the modem connection. If this occurs, the user will need to reconnect. 4. The user documentation states that a modem connection is not possible if there is a current LAN connection. This information is accurate only for older platforms. New platforms support simultaneous connections. ************************************************************************** G. Client System Setup Utility (CSSU): ************************************************************************** 1. 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. Note that there may be problems with files on the service partition that could prevent the service partition software from booting correctly. If this is the case the service partition may need to be reinstalled. For the supported CSSU features on each server, please see the Platform Compatibility Matrix in the ISC Installation Guide. 2. In previous releases of ISC software, when configuring the page string it was necessary to terminate the string with a ^M character. This is no longer necessary. The page string will work properly with or without a ^M character at the end. ************************************************************************** H. Independent Hardware Vendor (IHV) Instrumentation: ************************************************************************** 1. 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 can 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 and 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 start are CIO Array Management Service and Adaptec CIODMI. NetWare: 1. Edit the ISC_ON.NCF file. 2. To disable services, add the remark indicator "rem" at the beginning of the lines that start the services: - For servers using Adaptec SCSI controllers, comment the lines which would load nwaspi, iomgr and ciodmi. 3. Save the ISC_ON.NCF file. 2. When a Windows NT or Windows 2000 Advanced 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. 3. When a server with the Adaptec on-board SCSI controller has a zero channel RAID controller installed on the system, the Adaptec SCSI instrumentation will no longer provide reliable information on the SCSI controller or attached SCSI hard disk drives. The steps described in item 1 of this section may be used to disable the Adaptec instrumentation. 4. Intel cannot guarantee the successful operation of third party instrumentation integrated with ISC for on-board components, if the DMI instrumentation for these components is installed outside of the ISC installation procedure. ************************************************************************** I. LanAlert Viewer: ************************************************************************** 1. In order for the LanAlert Viewer to run properly, the minimum display setting must be 256 colors with resolution at 1024x768 or higher. 2. The SNMP trap service needs to be installed so the LanAlert Viewer can receive SNMP traps from ISC servers. The service can be activated by the operating system or installed from the operating system CD. Windows NT 1. Open the Control panel and select "Network". 2. Select the "Services" tab and click the Add button. 3. Select the "SNMP Service" and click the Ok button. Windows 2000 1. Open the Control panel and select the "Add/Remove Programs". 2. Click on the "Add/Remove Windows Components" icon. 3. Click the "Management and Monitoring Tools" check box and then the Next button. 3. The Java Runtime Environment (JRE) must be configured to load the Chinese font file when running in a Chinese Windows environment. The Chinese font file is located at c:\Program Files\JavaSoft\Jre\1.3\lib\font.properties.zh (assuming that JRE is installed in the c:\Program Files folder). The file must be renamed to replace the default font file (font.properties) before launching the LanAlert Viewer. 4. Windows 2000 Service Pack 2 is required in order for SNMP traps to be received correctly when running on Windows 2000 platforms. ************************************************************************** J. Documentation: ************************************************************************** 1. On-line documentation for ISC software is available in Adobe Acrobat* .PDF format. The documentation is installed with the ISC software during installation into the %ISC_PATH%\DOCS directory. You need Acrobat Reader version 4.0 or higher to read these files. You can download Acrobat Reader at the following location: http://www.adobe.com/products/acrobat/readstep.html ************************************************************************** K. Platform Instrumentation Control (PIC): ************************************************************************** 1. After updating the FRU component on a server with ISC 3.5.x instrumentation installed, the password for user authentication when launching Platform Instrumentation Control (PIC) will change to the default supplied with the FRU update. Any previously stored password for that server that you may have used to access PIC will have been invalidated upon updating the FRU component. ************************************************************************** L. Platform Instrumentation (PI): ************************************************************************** 1. The DMI database (sldb.dmi) can 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, you can 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 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, the server instrumentation will also generate a SNMP trap for each indication. All default Local Response Agent (LRA) actions associated with each indication will occur (i.e., log to disk, popup messages, broadcast messages, and 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. For this reason, if the SEL has many entries it takes the ISC GUI a long time to initialize the first time ISC is launched after the installation. The GUI keeps refreshing the screen for each entry in the SEL. To avoid this long initialization, if the old SEL entries are no longer needed, clear the SEL log before launching ISC. To do so: 1. Re-boot the system. 2. Press F2 to run BIOS Setup. 3. Select Server Management. 4. Enable the entry for clearing the SEL. ************************************************************************** M. Special instructions for Novell NetWare v5.1 and v6.0 ************************************************************************** 1. Do not install Native File Access Protocol modules in Netware. For ISC software to function correctly on NetWare environments, the DMI service provider for NetWare is necessary. DMI Service Provider relies on TIRPC.NLM which is installed separately to provide RPC services. However, installing the Native File Access Pack for Unix causes TIRPC.NLM to not function correctly, thus crippling ISC functionality. During installation of Novell NetWare 6.0, there is an option to install Native File Access Protocol modules for these environments: - Apple Macintosh - Windows - Unix Native File Access Protocols allow users on these client operating systems to access NetWare volumes without installing additional client software on their client workstations. If you choose the Native File Access Protocols for Unix components, it installs PKERNEL.NLM. Novell has documented that PKERNEL.NLM conflicts with TIRPC.NLM and recommends that the two NLMs be not loaded together. For NetWare 5.1, Native File Access Protocols is available as an add-on as part of the Service Packs. The instructions on how to install Native File Access Pack on NetWare 5.1 are available from this URL: http://www.novell.com/documentation/lg/nfap10/native/data/abwd9eb.html As with Netware 6.0, you should not install the Native File Access Protocols for Unix, either during OS installation or as an update. Since the DMI Service Provider for NetWare relies on TIRPC.NLM, it is imperative that PKERNEL.NLM be not loaded on servers where ISC is installed. For more information, see http://www.novell.com and search for "Native File Access Protocols." The Novell document that describes the conflict is in TID #10065169 titled "Differences between NFS 3.0 and NFS in NFAP." Item 6 in this document details the issue. To get to the TID, do the following: 1. Go to http://support.novell.com 2. Follow the hyperlink to Knowledgebase 3. a) Under "Select Product Categories" (Option 1) choose "NetWare" b) Under "Select Document Sets" (Option 2) choose "TIDs & Manuals" c) Under "Enter a word, phrase, or Technical Information Document number" (Option 3), enter the TID# 10065169 d) Hit the "Search Now" button and it should bring up the relevant hyperlink for this document e) Follow the result of the search (the hyperlink) to the actual TID ************************************************************************** End of readme file **************************************************************************