Important Information about Intel(R) Server Control v3.5.2 February 19, 2002 Errata Items A. Install B. Silent Install C. Uninstall D. Documentation/User Interface E. Platform Instrumentation Control (PIC) F. ISC Console G. Platform Instrumentation (PI) H. Independent Hardware Vendor (IHV) Instrumentation I. Direct Platform Control (DPC) Console Manager J. Client System Setup Utility (CSSU) K. Enterprise System Management Console (ESMC) Integration (includes SNMP Support) L. Intelligent Chassis Management Bus (ICMB) This errata.txt document is current at product launch. Any new errata items not mentioned in this file will be documented in the monthly "Intel Server Control v3.x Specification Update" posted on http://support.intel.com. Search on the key words "Intel Server Control." ***************************************************************************** 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 and/or support for same, nor shall Intel bear any liability whatsoever for any such changes or modifications.) This file identifies certain currently characterized errata; however, Intel does not represent or warrant either that such list is all- inclusive or the absence of errata which do not appear on this list. Intel shall not be liable for any damages whatsoever (including without limitation, lost profits, business interruption, computer failure or malfunction, or lost information) arising out of the use of or inability to use the ISC Software. Copyright (c) Intel Corporation 2002 Intel and LANDesk 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. Install: ***************************************************************************** 1. ISC setup and some of the components thereof require a pointing device and will not be driven with keyboards alone. 2. If PI-only install is attempted on a system with a non-supported platform, install will not clean up after itself after determining it should not install PI on this particular system. PI-only install on a supported platform will work properly. ***************************************************************************** B. Silent Install: ***************************************************************************** 1. Silent install will work best if ISC is installed on one server at a time. ***************************************************************************** C. Uninstall: ***************************************************************************** 1. For customers using H-P OpenView*, the files Ezrpcw32.dll, Wcdmionc.dll, Wcrap.dll, Winrpc32.dll, and Wonctcp.dll are not removed during uninstall when H-P OpenView is running. PROBLEM: Since the ISC Uninstall does not have information regarding other applications running, ISC does not know how to shutdown H-P OpenView. Therefore, there are ISC files that are being used by H-P OpenView that can not be deleted. IMPLICATION: Not all the files that are installed are removed from the system during uninstall. WORKAROUND: Stop H-P OpenView prior to ISC Uninstall. STATUS: Intel is investigating the possibility of fixing this erratum. 2. Intel Server Control (ISC) objects are not being removed from the H-P OpenView database and map. PROBLEM: After uninstalling the Intel Server Console, ISC symbols are left on the H-P OpenView map. If the user double clicks on an ISC symbol, H-P OpenView has a Dr. Watson error. IMPLICATION: ISC symbols and objects created during ISC integration are not removed from the system during uninstall. WORKAROUND: Users have to copy manually "c:\Program files\Intel\ServerControl\Bin\UninstIscOv.txt" file to "c:\Openview\registration\C\UninstIscOv.txt". STATUS: Intel is investigating the possibility of fixing this erratum. 3. During a Unixware* uninstall the following message may appear on the server: "S99ISC: Cannot open". This message is not significant, and the file s99isc will be removed once ISC uninstall is complete. ***************************************************************************** D. Documentation/User Interfaces: ***************************************************************************** 1. On internationalized releases, some text may appear in English or may not be correctly translated. PROBLEM: Some user interfaces, Help strings, or documentation may not have been translated, may contain redundant English text, or may contain incorrect translations. IMPLICATION: User may not have a clear understanding of the information being communicated by the user interface or documentation. WORKAROUND: None. STATUS: Intel is investigating the possibility of fixing this erratum. 2. On non-English operating systems, the font display may be unclear in some portions of the user interface. PROBLEM: The user interface may be unclear or difficult to read. IMPLICATION: User may have difficulty reading output. WORKAROUND: None. STATUS: Intel is currently investigating a fix for this erratum. 3. Pressing F1 for Help may not work. PROBLEM: On non-English operating systems, pressing F1 may not cause any Help to appear. Instead, the user may receive a message that Help does not exist. IMPLICATION: User may not have F1 access to needed Help topics. WORKAROUND: Access the Help topic through the menu selection. STATUS: Intel is investigating the possibility of fixing this erratum. 4. On non-English operating systems, the text may be cut off in the dialogs or status box. PROBLEM: The translations may not fit within the space provided, and the user is unable to scroll or resize the dialog or status box. IMPLICATION: User may be unable to read all the output. WORKAROUND: None. STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** E. Platform Instrumentation Control (PIC): ***************************************************************************** 1. Keyboard shortcuts do not always work. PROBLEM: The ISC GUI is split into two windows or panes. The left pane is used for navigation, the right pane is used for presentation of information. If the current window focus is in the right pane, then keyboard shortcuts will not work. For example, the F5 key will not refresh the screen, the tab key will not navigate, and the Alt-A shortcut will not Apply. If the current window focus is in the left pane, then the F5 key will refresh the data displayed including the right pane. IMPLICATION: The mouse and menu must be used instead of the keyboard. WORKAROUND: Use the mouse to click in the left pane to apply the window focus. This will allow use of the F5 key for refresh. The tab key and Alt-A key do not work. STATUS: Intel is investigating the possibility of fixing this erratum. 2. The win32rap service reports several error messages if NetWare* services are not installed. PROBLEM: If ISC is installed on a console or server without installing the NetWare services, then win32rap may report the following error messages in the application event log: "failed to initialize transport 'ddetrdll'" "failed to initialize transport 'ipx' "initializing winsock for ipx failed (winsock error 0x0000273f)" IMPLICATION: These messages simply indicate that win32rap attempted to start the NetWare services. If you are using tcp/ip for server communication then they are not a concern. WORKAROUND: You can ignore the error if your network only supports tcp/ip. STATUS: Intel is not investigating this erratum. 3. Shutting down the Windows NT* OS may fail to complete on a busy system. PROBLEM: If the server performs a "Shutdown the OS", "Shutdown the OS and Power Off", or "Shutdown the OS and Hardware Reset" event action on a Windows NT server, while the server is very busy, the OS shutdown may fail to complete. If the OS shutdown fails to complete, the power off or hardware reset will not occur. IMPLICATION: A very busy server may fail to shutdown completely, and will remain in that state until a user intervenes. WORKAROUND: Use other event actions. STATUS: Intel is investigating the possibility of fixing this erratum. 4. ISC shutdown and power control actions may not work on Windows NT 4.0 SP6a or Enterprise Edition if Intel remote management card (IRMC) driver is loaded. PROBLEM: If NT 4.0 Service Pack 6a is loaded on a system with an IRMC installed and an ISC "Shutdown the OS and Power Off" or "Shutdown the OS and Hardware Reset" event action is attempted, the system will shutdown, but the power off or hardware reset may not occur. IMPLICATION: The system will not perform the requested power off or hardware reset. WORKAROUND: Use IRMC functions to power off or reset the system. STATUS: Intel is investigating the possibility of fixing this erratum. 5. The "Immediate Hardware Reset" and "Immediate Power Off" features may not work properly during initialization. PROBLEM: During the ISC GUI initialization, if the user selects the power control actions "Immediate Hardware Reset" or "Immediate Power Off", the actions may not work as documented. IMPLICATION: The power control actions "Immediate Hardware Reset" and "Immediate Power Off" may not work properly and the server may continue to run without the desired action. WORKAROUND: Users should wait until the ISC GUI has completed initialization (READY state in status bar) before attempting these actions. STATUS: Intel is investigating the possibility of fixing this erratum. 6. Paging alert actions may continue to happen after paging has been removed as an alert action. PROBLEM: If paging is configured as an alert action for a threshold and that threshold is crossed, a page will happen as desired. If paging is then removed as an alert action from the threshold, it may still occur. IMPLICATION: A page may be issued when not desired. WORKAROUND: No workaround has been identified. STATUS: Intel is investigating the possibility of fixing this erratum. 7. If both a shutdown action and a page are selected, the page may not be sent. PROBLEM: If both a shutdown action and a page are selected, the page may not be sent. IMPLICATION: A page may not be issued. WORKAROUND: Do not configure both a page and a shutdown action on the same event. STATUS: Intel is investigating the possibility of fixing this erratum. 8. Some processor temperature sensors may first show a current status of 'unknown' with a current reading of 'unsupported'. PROBLEM: The processor temperature sensors may initially show a current value of 'unknown' and a current reading of 'unsupported'. These values will be replaced by the correct data as soon as the sensor becomes active; this can take up to two minutes. It may be necessary to manually refresh the console application before the health indicators correctly reflect the new status values. IMPLICATION: The processor temperature sensor status information may not be available for approximately two minutes after the server boots. A manual refresh of the console application may be needed to correct the health indicators of a console that started before the status information was available. WORKAROUND: If a processor temperature sensor has a status of 'unknown', wait two minutes and refresh the console display. STATUS: Intel is investigating the possibility of fixing this erratum. 9. Due to the rounding of floating point values, the user can set different threshold values without variance in ISC PIC. PROBLEM: Due to the rounding of floating point values, the user can set different threshold values without any effective difference between them. This is possible only if the user tries to set different threshold values so close to each other that the hardware characteristics of the sensors are bypassed. IMPLICATION: The user may be able to set the same value for different sensor thresholds. WORKAROUND: Do not set different threshold values very close. STATUS: Intel is investigating the possibility of fixing this erratum. 10. Server will not shutdown gracefully and will hang if not logged into. PROBLEM: Under Microsoft Windows NT 4.0, if an event shuts down the server and the server has not been logged into (i.e., the login screen is displayed and the server is waiting for input), the system will be halted and the shutdown will not occur. If the server has been logged into, the shutdown will happen as desired. But, after the server comes back up, if another event attempts to shut down the server before it has been logged into, the system will be halted and the shutdown will not occur. IMPLICATION: Server may not shutdown when needed. WORKAROUND: Logon to the server when it first starts up and again after any subsequent reboots will allow graceful shutdown actions. STATUS: Intel is investigating the possibility of fixing this erratum. 11. Broadcast messages sent from NetWare to a Windows NT/2000 console may not be displayed. PROBLEM: When an alert action "Send Broadcast Message" is selected as one of the LRA actions for a sensor whenever it crosses a threshold, the broadcast message may not get displayed at the console if the console is running Windows NT or Windows 2000. This is the case when Microsoft Client for NetWare is being used at the console to access NetWare resources. IMPLICATION: It gives the impression that NetWare broadcast messages are not sent to the console at all. WORKAROUND: If the Novell client for Windows NT is used instead of the Microsoft client, then this problem does not happen. STATUS: Intel is investigating the possibility of fixing this erratum. 12. ISC PIC may not show all servers manageable via ICMB. PROBLEM: After the user selects the "Enable as Management Point" checkbox in the "Local ICMB Server Configuration" group box in the "ICMB Configuration" tabbed page which is accessed using the ICMB folder in the left pane sensor tree view, PIC may not discover all of the servers that support management via ICMB. IMPLICATION: User will not be able to manage all servers on the network that are manageable via ICMB. WORKAROUND: Relaunch PIC after selecting the "Enable as Management Point" checkbox. STATUS: Intel is investigating the possibility of fixing this erratum. 13. Actions for some hot swappable power supply events may not be set and handled properly. PROBLEM: ISC PIC supports control actions for events such as "Power supply failed", "Power Supply OK," and "Power Supply Likely to fail." These events include situations of the power supply failing or internal power cable coming loose, but they do not cover events such as removal and replacement of the hotswap power supply, or removal of the AC input power cord. The control actions, such as Shutdown the OS, Shutdown the OS and Power off, etc., cannot be set for these events: "Power Supply Inserted", "Power Supply Removed", "Power Supply AC lost", "Power Supply AC lost or out-of-range", and "Power Supply AC out-of-range, but present". Furthermore, after the removal or insertion of a power supply unit, ISC PI may not handle any of the power supply-related events properly. This means that if you set a control action to occur on power supply failure, and then replace a power supply without rebooting the OS, if a power supply subsequently fails, the control action may not occur. IMPLICATION: The system may not perform the requested control actions set for the power supply sensors. WORK-AROUND: None STATUS: Intel is investigating the possibility of fixing this erratum. 14. Auto refresh of health status on the ISC PIC GUI may not work when monitoring a Windows-based server. PROBLEM: Auto refresh in ISC PIC may not work when monitoring a Windows-based server across subnets. IMPLICATION: The PIC console may not accurately reflect the current health status of sensors for Windows-based servers, if the server and client system are in different subnets. WORKAROUND: There are 2 options if this failure occurs: (1) Map a drive to the server being monitored. Then set broadcast alert messages for any sensors you wish to monitor. (2) Use F5 to refresh the ISC PIC GUI; this updates the current health status of the sensors and ISC. STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** F. ISC Console: ***************************************************************************** 1. The ISC Console only displays information upon discovering a supported ISC system. No status or messages are displayed when a user requests the discovery of a non-ISC server by entering its IP address. IMPLICATION: The user is not informed of the status of the discovery, and may get the impression that console did not perform any actions. WORKAROUND: No workarounds. STATUS: Intel is currently investigating a fix for this erratum. ***************************************************************************** G. Platform Instrumentation (PI): ***************************************************************************** 1. BMC/BIOS will not maintain changes to dynamic IP address unless ISC PI component is running. PROBLEM: If you configure a DHCP (dynamic) IP address for a server using the SSU or Client SSU, the IP address is maintained by the Baseboard Management Controller (BMC). Ordinarily, a floating IP address will expire from time to time and the server is notified by the DHCP server of the new IP address. However, under certain circumstances the BMC/BIOS will retain the expired address, causing a network conflict with the entity that now has been assigned that IP address. This occurs if: A. The ISC PI component is not installed or is not running on the server (a PI agent keeps the BMC's IP in sync with the OS's IP address) or B. The OS is not running (e.g., the server is in standby mode or is running only DOS) Under these circumstances, the BMC may issue LAN Alerts or Gratuitous-ARP broadcasts (which are enabled by default) using the expired IP address, until the server is brought back to running the OS. This can occur on the SCB2, SDS2, or later platforms. IMPLICATION: Network traffic may be slow or exhibit access problems. WORKAROUND: Configure the DHCP server to issue only a "fixed" DHCP address to any servers using the BMC. Then the DHCP server will always issue the same IP address to those servers. You cannot use the SSU to do this, but must configure it directly on the DHCP server. Alternatively, you can use SSU to assign a Static IP address to the server, and not use DHCP. STATUS: Intel is currently investigating a fix for this erratum. 2. The ISC PI agent that keeps BMC's IP address in sync with the operating system's IP address does not work on non-English versions of Windows NT. PROBLEM: Non-English installations of Windows NT will not maintain changes to dynamic IP addresses even if the ISC PI component is running (see the previous erratum). IMPLICATION: Network traffic may be slow or exhibit access problems. WORKAROUND: Configure the DHCP server to issue only a "fixed" DHCP address to any servers using the BMC. Then the DHCP server will always issue the same IP address to those servers. You cannot use the SSU to do this, but must configure it directly on the DHCP server. Alternatively, you can use the SSU to assign a Static IP address to the server, and not use DHCP. STATUS: Intel is currently investigating a fix for this erratum. 3. Unloading SENSOR.NLM may show a small number of short term memory allocations that were not free. PROBLEM: SENSOR.NLM may not free all memory associated with some functions. This will cause NetWare to display a message when it frees the memory after unloading the NLM. IMPLICATION: A small amount of memory will be used and will not be made available again until the NLM is unloaded. This should not be a significant number of bytes and should not impact server performance. WORKAROUND: No workaround has been identified. STATUS: Intel is investigating the possibility of fixing this erratum. 4. ISC may cause a floppy error message to be generated on a Linux* server PROBLEM: While starting ISC on a Red Hat* Linux server, the user may see the message "end_request: I\O error, dev 02:00 (floppy), sector 0" on the system console. It is because ISC tries to mount the floppy drive to check for some configuration files. The mount command results in the above message being generated if there is no floppy in the drive. This message comes from the floppy driver in the kernel and can't be suppressed. IMPLICATION: User may think that some errors have occurred when in fact this is the expected behavior if there is no floppy in the drive. WORKAROUND: None. STATUS: Intel is investigating the possibility of fixing this erratum. 5. The SNMP "read only" access option for ISC PI does not function as desired. PROBLEM: The ISC support for disabling SNMP Set Commands on a server using ISC Platform Instrumentation is currently not functioning as expected. By default SNMP Set & Get commands are permitted and work correctly. During installation of ISC there is an option under "Platform Instrumentation" called "SNMP Read Only access". Selecting this option will not actually disable Set commands. There is no impact to generation of SNMP traps, which function normally. Traps are processed and received by the SNMP consoles, as desired. WORKAROUND: The security feature in the Operating System for SNMP Service, allows a user to configure "Community Rights" to "READ ONLY". This is essentially the same as disabling SNMP Sets for all extension agents including ISC Platform Instrumentation. STATUS: Intel is currently investigating a fix for this erratum. 6. The ISC Standalone console health indication might not correctly display current health status for servers running the Red Hat Linux operating system. PROBLEM: The colored icon representing health status displayed in the ISC Standalone console for servers running Red Hat Linux 7.1 & 7.2 might not be the same as the colored icon displayed in the PIC user interface. This situation only occurs in servers running the Red Hat Linux operating system and using a static IP address. During this situtation, the health icon displayed in PIC represents the correct current health status, while the icon displayed in the ISC Standalone console represents an incorrect health status. The condition is caused by the DMI Service Provider running under the Red Hat Linux operating system. Servers running the Red Hat Linux 7.1 & 7.2 operating system and using DHCP and having access to a DNS server for name/address resolution, do not experience this problem. IMPLICATION: The user might see conflicting health information if comparing the colored icon in the Standalone interface to the colored icon in the PIC interface. For these cases, the icon displayed in the PIC interface is correct. All actions and logging of system events continue to operate correctly. WORKAROUND: If the ISC server running Red Hat Linux 7.1 or 7.2 is configured with a static IP address, the following steps will resolve the issue. 1. Edit the "hosts" file (located in "/etc" folder). 2. Add the IP address of the server along with the server name, if it is not already in the file. (e.g. 10.7.180.45 scb2_45). 3. Save the edits. 4. Restart network services on the server or reboot the server Performing these steps will cause the colored icons in both the ISC Standalone console and the PIC interface to display the same correct, current health status. STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** H. Independent Hardware Vendor (IHV) Instrumentation: ***************************************************************************** 1. The Adaptec* SCSI component reports the wrong information about Logical Unit Drives on Mylex* Host Adapters. PROBLEM: On NetWare Servers, a known incompatibility between the Adaptec and the Mylex ASPI drivers can cause the Adaptec SCSI component to report the wrong information about Logical Unit Drives on Mylex Host Adapters. IMPLICATION: The wrong information may display. WORKAROUND: The SCSI DMI instrumentation requires Adaptec ASPI drivers (ASPI32.SYS and WNASPI32.DLL). The user must load these drivers on the server. The Mylex DMI instrumentation does not require Mylex ASPI drivers. Unless some other application requires the Mylex ASPI drivers, do not load the Mylex ASPI drivers. STATUS: Intel is currently not investigating a fix for this erratum. 2. During Wired for Management (WfM) testing, the DMTF CompChk tool reports errors in the Adaptec MIF. PROBLEM: The recent discovery of MIF syntax violations in Adaptec instrumentation does not compromise the Intel(R) AD450NX MP systems standing as "WfM upgradable" system. The SCSI instrumentation supplied by Adaptec is not required on WfM 1.1a servers. IMPLICATION: As a side effect of WfM testing, we have found cases where the Adaptec MIF does not comply with the syntax of DMTF standard groups. The WfM test suite uses the DMTF CompChk tool to scan the entire system MIF. It reports WfM pass/fail on the specific groups required by WfM, and also notifies the user about any problems it detects with respect to general DMI compliance for all other groups it finds registered with the service provider. The Adaptec problems fall into this second category. WORKAROUND: None required. The (slightly) non-compliant MIFs can be successfully browsed by the DMI Explorer browser bundled with ISC. We currently believe there should be no effect on the user's ability to access and use this data. STATUS: Intel is investigating the possibility of fixing this erratum. 3. On server systems with onboard Adaptec SCSI controllers, users will see CIO events messages as the operating system loads. PROBLEM: These messages are not reporting a problem with the system. The messages are normal indications from Self Monitoring and Reporting Technology (SMART) that the SCSI controller and hard drives are communicating normally. IMPLICATION: Some users may find these messages annoying as the operating system is loading. WORKAROUND: In Microsoft Windows operating systems the user may turn off SMART polling to eliminate these messages. This will however also prevent any other SMART messages being generated, including those predicting drive failure. To turn off SMART polling the user can modify the file IOMGR.INI in the following file folder, Program Files\Adaptec\CIO400. Any text editor may be used to open this file. Near the end of this file is a line which reads by default... "SmartPolling = Yes". The user may modify this line to read "SmartPolling = No". STATUS: CIO messages are normal indications. 4. UnixWare* 7.1.1 drivers currently unavailable for the Promise ATA/100 RAID controller for SCB2A. PROBLEM: Currently UnixWare 7.1.1 drivers are unavailable for the Promise ATA/100 RAID controller on the ATA/IDE SKU of the SCB2 baseboard (SCB2A). IMPLICATION: UnixWare 7.1.1 and ISC support for that OS are currently unavailable for the SCB2A baseboard when using the on-board Promise FastTrak ATA/100 RAID controller. WORKAROUND: Install Unixware 7.1.1 to a disk drive using either an add-in IDE or SCSI controller card compatible with the SCB2A board, and supported by UnixWare 7.1.1. ISC support for this configuration may be limited. STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** I. Direct Platform Control (DPC) Console Manager: ***************************************************************************** 1. Redirect doesn't support green (teal) color. PROBLEM: Console redirect does not display green shades. Currently, teal is displayed as cyan (or aqua). IMPLICATION: The Adaptec Option ROM BIOS displays white text on teal background. DPC Console Manager is displaying this as white text on cyan, which is extremely hard to read. WORKAROUND: None identified. STATUS: Intel is investigating the possibility of fixing this erratum. 2. Dial-up connection dialog appears when performing Service Partition operations PROBLEM: On Windows 2000, when connected via DPC to the Service Partition, sometimes when performing Service Partition actions, the dial-up connection dialog appears. Also under this circumstance, any other application, such as a web browser that attempts to access the internet, could cause this dialog to appear. If the user presses 'cancel' the correct dialog box appears. IMPLICATION: Unexpected interface behavior. WORKAROUND: Cancel the extraneous box and continue normal use. Another option is to select the settings option in the dial-up connection dialog. If you see that the option is set to "Always dial my default connection" you can fix the problem by changing that to "Dial whenever a network connection is not present". This problem can also occur in instances where there is no dial-up connection listed. You can create a 'dummy' entry and set it to be the default, with a setting of "Dial whenever a network connection is not present". STATUS: Intel is currently investigating a fix for this erratum. 3. "Graceful Shutdown has failed." or "Graceful reset has failed" dialog appears when you know the OS is up and Platform Instrumentation is running. PROBLEM: On rare occasions (less than 2% of the time), when you attempt to do a reset, shutdown or boot to Service Partition, the Platform Instrumentation service may begin performing this operation, but DPC may not receive notification of this action. Under this circumstance, DPC will present a dialog indicating that this 'graceful' action failed, would you like to 'force' it. IMPLICATION: Unexpected behavior, user thinks the reset, power-down or reboot to Service Partition action failed, when in fact it is successfully being carried out. WORKAROUND: If you see in the status of DPC that the OS is detected, or if you are certain this OS is running and the Platform Instrumentation service is active, and this dialog appears, press 'Cancel' when prompted for a 'Force' operation. Wait 5 minutes and try again. STATUS: Intel is currently investigating a fix for this erratum. 4. FRU loaded twice. PROBLEM: If after downloading FRU, the user attempts to download SDR, the FRU gets downloaded again, and when finished, the SDR information is downloaded. IMPLICATION: Poor performance. WORKAROUND: None. STATUS: Intel is currently investigating a fix for this erratum. 5. FRU Manager displays only Baseboard info (HSC, Power dist brd, Power supply 1 & 2 missing). PROBLEM:FRU information is only available for Baseboard. IMPLICATION: Not all FRU information is available from DPC. WORKAROUND: None. STATUS: Intel is currently investigating a fix for this erratum. 6. DPC cannot connect via modem with access mode set to "Preboot". PROBLEM: The DPC console is unable to connect to a server via modem when the EMP Access Mode is set to "Preboot". IMPLICATION: Users will be unable to connect a server through a modem using DPC, when the access mode is set to "Preboot". WORKAROUND: None. STATUS: Intel is currently investigating a fix for this erratum. ***************************************************************************** J. Client System Setup Utility (CSSU): ***************************************************************************** 1. The system phone number is not saved from the EMP screen in the SSU and CSSU. PROBLEM: When you save the EMP configuration the system phone number is not saved. If you return to the EMP screen the system phone number will still be blank. IMPLICATION: The system phone number field will always be blank when the EMP is loaded and saved. WORKAROUND: There is no workaround. STATUS: Intel is investigating the possibility of fixing this erratum. 2. Pointing device needed to run CSSU. PROBLEM: Most dialogs in CSSU do not have keyboard support; for example, pressing the Enter key will not cause any action to occur in dialogs. IMPLICATION: Ordinary keystrokes, hotkeys or keyboard shortcuts may not work. WORKAROUND: Use a pointing device to access CSSU functions. STATUS: Intel is investigating the possibility of fixing this erratum. 3. FRU files will not load after loading of an invalid FRU file is attempted. PROBLEM: If an attempt is made to load an invalid FRU file with the FRU Manager, then if an attempt is made to load a valid file, an error message will be displayed. IMPLICATION: User cannot load a valid FRU file after trying to load an invalid file. WORKAROUND: Close the FRU Manager and reopen. The valid FRU file should load. STATUS: Intel is investigating the possibility of fixing this erratum. 4. Invalid characters appear for the server name. PROBLEM: When dialed in from an English operating system to a non-English server, the server name may display invalid characters in the server box at the bottom of the Client SSU container. IMPLICATION: User may be unable to identify server. WORKAROUND: None. STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** K. Enterprise System Management Console (ESMC) Integration ***************************************************************************** 1. SNMP Support: Some MIB files will not manually load in some versions of H-P OpenView. PROBLEM: Some of the MIBs provided with ISC will not load in some versions of H-P OpenView. IMPLICATION: H-P OpenView will not provide as rich information when displaying an SNMP trap from ISC. WORKAROUND: No workaround has been identified. STATUS: Intel is investigating the possibility of fixing this erratum. 2. Unable to launch ISM applications from CA-TNG map. PROBLEM: After ISM gets installed and while some ISM servers are being discovered and added to the CA-TNG map, right-clicking on an ISM server and selecting "Launch ISC" fails to launch an ISM application. IMPLICATION: User will be unable to launch ISM applications from the CA-TNG map. WORKAROUND: This problem can be easily fixed by first stopping and then restarting the Intel TNG-ISC AutoDiscovery service. If that fails to fix the problem, a system reboot may be necessary. After the second reboot everything should work properly. STATUS: Intel is investigating the possibility of fixing this erratum. 3. Unable to see ISC objects on the CA-TNG map. PROBLEM: After ISM gets installed, the user is unable to see ISM objects on the CA-TNG map. IMPLICATION: User will be unable to see ISM objects on the CA-TNG map. WORKAROUND: This problem can be easily fixed by first stopping and then restarting the Intel TNG-ISC AutoDiscovery service. If that fails to fix the problem, a system reboot may be necessary. After the second reboot everything should work properly. STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** L. Intelligent Chassis Management Bus (ICMB) ***************************************************************************** 1. Immediate Power Off and Immediate Hardware Reset actions are not functional in ISC 3.5.x using ICMB. PROBLEM: After a successful ICMB connection using Platform Instrumentation Control (PIC), if the user tries to do an Immediate Power Off Server, this error message is displayed: "The attempt to power off server failed". Selecting Immediate Hardware Reset action does nothing. Immediate Power Off and Immediate Hardware Reset do not function as desired. IMPLICATION: Immediate Power Off and Immediate Hardware Reset actions will not work as desired. WORKAROUND: None STATUS: Intel is investigating the possibility of fixing this erratum. 2. ISC Health folder for ICMB chassis always indicates green "OK" status. PROBLEM: Using PIC, the user can access the ICMB folder. If the user selects the "Enable as Management Point" checkbox under "ICMB Configuration" tab, after the discovery period, PIC will discover any ICMB chassis. If the user goes to ICMB menu to choose "View Managed Server(s)..." and selects a remote server, PIC will show the remote ICMB server selected. However, the Health folder for this remote server will always show green "OK" status, even if the Chassis status for that remote server shows red "Critical" error. IMPLICATION: ISC Health folder for ICMB chassis does not function correctly. WORKAROUND: None STATUS: Intel is investigating the possibility of fixing this erratum. ***************************************************************************** End of errata file *****************************************************************************