Important Information about Intel(R) Server Management (ISM) v5.8 February 17, 2004 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 (PI) L. Command Line Interface (CLI) M. SNMP Subagent(SNMP) NOTE: Known issues with the ISM 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 ISM 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 ISM 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 2004 Intel and Xeon 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 Management (ISM) Platform Instrumentation software: Managed Server Operating Systems: - Microsoft* Windows* 2000 Advanced Server SP4 - Red Hat Linux 8.0 Console Operating Systems: - Microsoft Windows 2000 Advanced Server SP4 - Microsoft Windows 2000 Professional SP4 2. Before installing ISM software, customers using the Intel(R) EtherExpress(TM) PRO/100b LAN Adapter or other Intel LAN adapters should download and install the most current driver from: http://support.intel.com/ 4. ISM 5.8 software supports servers with the following Intel baseboard: Intel (R) SE7210TP1-E server platform The PI (Platform Instrumentation) module supports only Intel (R) SE7210TP1-E server platform. The client applications like DPC , DPCCLI and PIC can connect to following servers: Intel (R) SE7501WV2 Intel (R) SE7501BR2 Intel (R) SE7501HG2 Intel (R) SE7500WV2 Intel (R) SSH4 Intel (R) SHG2 ************************************************************************** B. Install ************************************************************************** NOTE: Before installing this version of the Platform Instrumentation Control (graphical user interface) software on a console system, Intel recommends that you remove all previously installed console ISM software from the system. To remove existing console ISM software, use the operating system's "Add/Remove Program" facility. 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 V3.0 2. The ISM 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 ISM console is started in order to manage the server prior to all the services being initialized, ISM 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 ISM component. 4. Silent Install A. Silent install works best if ISM is installed on one server at a time. B. To perform a silent installation, follow the steps below: 1. Copy the file /software/silent.txt from the CD to a directory where you can edit it. These instructions use C:/temp. 2. Edit the file silent.txt and replace the tags and with your network user name and password. 3. Change directory to the local CD drive, then into the Software directory (for example, if f: is the CD drive, then f:/Software) 4. Enter the command, setup.exe /silent:c:/temp/silent.txt 5. The CA TNG Integration agent will be installed only if the WorldView component of the CA TNG suite of applications is already installed on the system. Also, the H-P OpenView Integration agent will be installed only if H-P OpenView Network Node Manager is already installed on the system. 6. Remote installation of the CA TNG Integration Agent is not supported. Even if you select the CA TNG Integration Agent item for installation during a custom remote install, it will not be installed. This is because installation of the CA TNG Integration Agent requires user interaction by answering a CA TNG-specific dialog. 7. If the CA TNG Integration Agent is selected for installation, at some time during ISM installation, a CA TNG-specific modal dialog displays. ISM installation will halt until this dialog has been answered. After you answer the CA TNG dialog, ISM installation will continue. 8. ISM 5.8 supports HP Open View NNM 6.3 and CA UNSM 3.0 only on Windows 2000 platforms. 9. Ensure that the Windows Remote Registry Service is running before attempting a remote ISM installation. ************************************************************************** C. Additional Instrumentation Setup: ************************************************************************** 1. Depending on the baseboard type, the ISM 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 ISM Installation and User Guide. 2. The broadcast action of ISM applies to all active connections. In Windows XP 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. ************************************************************************** D. Uninstall: ************************************************************************** 1. Several files may not be removed due to services that may be running during the ISM 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 ISM component. ************************************************************************** E. Enterprise System Management Console (ESMC) Information: ************************************************************************** Information in this section applies to one or both of the following third-party Enterprise System Management Consoles (ESMCs): - H-P OpenView* Network Node Manager or - Computer Associates (CA) Unicenter The Next Generation* (TNG) 1. 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. 2. 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. 3. When using CA-TNG Unicenter, the possibility exists that after double clicking on the ISM WorldView icon in the 2D map, no ISM 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-ISM AutoDiscovery service. 6. Select Stop. 7. Wait for service to stop. 8. Right click Intel TNG-ISM AutoDiscovery service. 9. Select Start. 10. Check 2D map in CA-TNG Unicenter for ISM 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 ISM server icons. 4. Email Alerts Using SNMP: The ‘Test Email’ feature and the ‘LRA email alert’ action require the following MIB files to be loaded in the ESMC: For servers running a) Windows 2000 Advanced Server b) Novell NetWare or c) Caldera OpenUNIX Load the MIB files BASEBRD4.MIB and LRA.MIB. For servers running RedHat Linux 7.x Load the MIB files MAPBASE4.MIB, MAPSHA.MIB and MAPLRA.MIB. · If MIB files were loaded from a prior version or build of ISC or ISM, please unload them and reload them from the current build. Otherwise, Email alerting may not work with an ESMC. ************************************************************************** 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. 2. Systems that use the On-board Platform Instrumentation, such as the SE7210TP1-E server platform, do not retain the last values of sensors whenever the system is switched off. Hence, the DPC RSA would display 'Unknown' status for the SE7210TP1-E server platform sensors whenever the server is switched off from the Front Panel." For more information, see the ISM Installation and User Guide. For the supported DPC features on each server, please see the Platform Compatibility Matrix available at http://support.intel.com/support/motherboards/server/isc/isc_features.htm. ************************************************************************** G. Client System Setup Utility (CSSU): ************************************************************************** 1. CSSU will not work with mBMC-based platforms such as the SE7210TP1-E server platform as the service partition is not supported on these platforms. 2. 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. 3. In previous releases of ISM 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 to 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 ISM starts as detailed below for each operating system. 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 Adaptec I/O Manager Server 1.00 and I/O Manager DMI. 2. When a Windows 2000 Advanced Server using an Adaptec SCSI controller boots, there may be numerous informational events titled I/O Manager Event for Storage Devices. 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. When a server with an Adaptec on-board SCSI controller has HostRAID enabled, the Adaptec SCSI DMI instrumentation integrated with ISM 5.8 will not work correctly. The Adaptec HostRAID Alert Utility located on the server's resource CD can be installed to receive local alerts for the RAID volume. The Adaptec HostRAID Alert Utility does not include DMI or SNMP support. Contact Adaptec for management software release that provide DMI and SNMP support for their HostRAID products. 5. The Adaptec DMI instrumentation integrated with ISM 5.8 supports only the on-board SCSI controller and will not support any add-in Adaptec RAID cards. 6. In order to have SNMP support for Intel network adapters download the native SNMP agents from the drivers and software download pages for your specific network adapter accessed from the network adapter URL: http://support.intel.com/support/network/adapter/index.htm 7. Intel cannot guarantee the successful operation of third party instrumentation integrated with ISM for on-board components, if the DMI instrumentation for these components is installed outside of the ISM 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 ISM servers. The service can be activated by the operating system or installed from the operating system CD. 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. 5. As mentioned in Section A, number 6 above, the Windows XP Security Patch for Memory Leak in SNMP must be installed on Windows XP Console systems in order to view SNMP traps in LAN Alert Viewer. Download the Windows XP Memory Leak in SNMP Vulnerability patch from the Microsoft web site. ************************************************************************** J. Documentation: ************************************************************************** 1. On-line documentation for ISM software is available in Adobe Acrobat* .PDF format. The documentation is installed with the ISM software during installation into the %ISM_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 (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 a Windows 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 Windows: 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 a Windows 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 ISM GUI a long time to initialize the first time ISM 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 ISM. 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. ****************************************************************************** L. Command Line Interface (CLI) ****************************************************************************** 1. When using the Command Line Interface (CLI) ID command will always give ffffffff-ffff-ffff-ffff-ffffffffffff as output on the SE7210TP1-E server platform. 2. When using the Command Line Interface (CLI), if user incorrectly types in parameters for the "dpccli" commands (ex: dpccli -r), no error message is returned. 3. When using the Command Line Interface (CLI), if user executes power related commands like boot, power, shutdown or reset on the SE7210TP1-E server platform, graceful shutdown will not take place i.e. if OS is up on server and we execute power related commands, OS data might get corrupted. 4. Systems that use the On-board Platform Instrumentation, such as the SE7210TP1-E server platform, do not retain the last values of sensors whenever the system is switched off. Hence, the Command Line Interface (CLI) would display '0' values for the SE7210TP1-E server platform sensors whenever the server is switched off from the Front Panel. In addition, the system FAN sensors have an inverse reading, so their normal 'off' reading is the sensor Maximum reading ******************************************************************************** M. SNMP Subagent(SNMP) ******************************************************************************** 1. The following operating systems are supported for SNMP Subagent(SNMP): Managed Server Operating Systems: - Microsoft* Windows* 2000 Advanced Server SP4 - Red Hat Linux 8.0 ************************************************************************** End of readme file **************************************************************************