Important Information about Intel Server Control v1.10.x
July 1, 1999


Errata Items

A.  Installation
B.  Uninstall
C.  Intel Server Control
D.  LANDesk Server Manager
E.  Adaptec SCSI Instrumentation
F.  Symbios SCSI Instrumentation
G.  AMI RAID Instrumentation

**********************************************************************
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 1999).

*Other product and corporate names may be trademarks or registered 
trademarks of other companies, and are used only for explanation and 
to the owners' benefit, without intent to infringe.
**********************************************************************

**********************************************************************
A. Installation:
**********************************************************************
1. An attempt is made to install ISC and you receive the message
   'unable to load Atl.dll'
PROBLEM: For Win95* consoles, ISC setup requires that DCOM95 be 
   installed.  Other software also requires DCOM95, so it may already
   be installed on your system.  If you attempt to install ISC and 
   receive the message 'unable to load Atl.dll', this means that 
   DCOM95 is either not installed or not up-to-date on that Win95 
   system.  For Windows 98, ISC Setup requires DCOM98.
IMPLICATION: The user will be unable to install ISC
WORK-AROUND: Before installing ISC, DCOM95.exe should be 
  run from the ISC CD and then the system should be rebooted.
  Both Dcom95.exe and Dcom98.exe can be downloaded from Microsoft Web site.
STATUS: Intel is investigating the possibility of fixing this erratum.

2. The Maintenance Release install program might not show the copy status
   correctly.
PROBLEM: The progress bar might not show the copy progress correctly.
   It sometime go from 0% to 100% instantly while the files copying is
   still under progress.
IMPLICATION: User might be confused about the overall copy progress during
   MR install process.  No functionality will be affected by this.
STATUS: Intel is investigating the possibility of fixing this erratum.

**********************************************************************
B. Uninstallation:
**********************************************************************
1. The file sdlink.dll is not removed during uninstallation if SNMP 
   services are running on your system.
PROBLEM: The SNMP services are not automatically stopped during 
   uninstallation, therefore the sdlink.dll file is busy during 
   uninstallation. This causes the file to not be removed.
IMPLICATION: Not all the files that are installed are removed from the
   system during uninstallation.
WORKAROUND: Stop the SNMP services prior to running the ISC 
   uninstallation.
   Or after running ISC Uninstallation, stop the SNMP services, and 
   manually remove the sdlink.dll file.  The default directory is: 
   c:\Program Files\Intel\ISC\CI
   The customer directory may differ.
STATUS: Intel is investigating the possibility of fixing this erratum.

2. For customers using HP OpenView*, the files Ezrpcw32.dll, 
   Wcdmionc.dll, Wcrap.dll, Winrpc32.dll, and Wonctcp.dl are not 
   removed during uninstallation when HP OpenView is running.
PROBLEM: Since the ISC Uninstallation does not have information regarding
   other applications running, ISC does not know to shut down HP 
   OpenView.  Therefore, there are ISC files that are being used by HP
   OpenView that can not be deleted.
IMPLICATION: Not all the files that are installed are removed from the
   system during uninstallation.
WORKAROUND: Stop HP OpenView prior to ISC Uninstallation.
STATUS: Intel is investigating the possibility of fixing this erratum.

3. Files are not removed during uninstallation.
PROBLEM: The following files are not being deleted:
   - %windir%\system32\EnuSISC_Api.lrc
   - %windir%\system32\LangUtil.dll
   - %windir%\system32\msvcrt.isc
   - %windir%\system32\msvcrt40.isc
   - %windir%\system32\DMI\mifs\backup\basebrdm.mif
   - %windir%\system32\DMI\mifs\backup\ISCLDSM.mif 
   - %windir%\system32\DMI\mifs\backup\ISCver.mif 
   - %windir%\system32\DMI\mifs\backup\lra.mif 
   - %windir%\system32\DMI\mifs\backup\MEGARAID.MIF 
   - %windir%\system32\DMI\mifs\backup\scsidmi.mif
IMPLICATION: Not all the files that are installed are removed from the
   system during uninstallation.
WORKAROUND: You can manually delete the files after uninstalling
   ISC.
STATUS: Intel is investigating the possibility of fixing this erratum.

4. Registry keys or dependencies are not removed during uninstallation.
PROBLEM: The following registry keys or dependencies are not being
   deleted:
   - SNMP service (HKEY_LOCAL_MACHINE\SOFTWARE\Intel\SDLink)
     has a dependency on Win32sl.
   - NT 3.51 servers (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
     Windows\CurrentVersion\Uninstall\ Intel Server Control CI\
     DisplayName="Intel Server Control Instrumentation")
   - NT 3.51 servers (HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\
     Windows\CurrentVersion\Uninstall\ Intel Server Control CI\
     UninstallString="C:\ISC/uninstall.exe -cu")
   - ISC stand-alone (HKEY_LOCAL_MACHINE, SOFTWARE\Intel\
     IntegratedConsole\1.0, ServerListFileDirectory)
IMPLICATION: Not all the registry keys or dependencies that are
   created during ISC install are removed from the system during
   uninstallation.
WORKAROUND: You can manually delete the registry keys or
   dependencies.
STATUS: Intel is investigating the possibility of fixing this erratum.

5. ISC Class definitions are not being removed from the CA-TNG
   repository after uninstallation.
PROBLEM: After uninstalling the Intel Server Control Console, 
   the Intel_Server_Control and ISC_Business_View classes 
   remain in the TNG repository.
IMPLICATION: The ISC class definitions created during ISC install
   integration with CA-TNG are not removed from the system during
   uninstallation.
WORKAROUND: You can manually delete the class definitions
   from the repository as follows: launch TNG's "Class Wizard" 
   applet, select "Modify Existing Class",  delete 
   "TNGRoot\ManagedObject\Application\Intel_Server_Control" and  
   "TNGRoot\ManagedObject\BusinessView\ISC_Business\View1".
STATUS: Intel is investigating the possibility of fixing this erratum.

6. The Maintenance Release install program leave one unneeded registry
   key.
PROBLEM: One of the registry keys that the MR setup program added is not
   removed after the MR setup is completed.
IMPLICATION: There will be one unneeded registry key after MR is installed.
   No functionality will be affected by this.
STATUS: Intel is investigating the possibility of fixing this erratum.

**********************************************************************
C. Intel Server Control:
**********************************************************************
1. The ISC Console loses communication with the server if the server 
   reboots or shuts down.
PROBLEM: The ISC console loses communication with the server if the 
   server reboots or shuts down.  The server reboot or shutdown could be
   caused by several actions, including LRA-configured actions in 
   response to some event condition, or by manually resetting
   or powering down the system.  Once the server has powered down, 
   the RPC connection used by the console to communicate with the
   server is no longer valid.
IMPLICATION: The ISC console will appear to hang pending a time-out 
   on a DMI request to the server.  This time-out can take up to 
   several minutes to occur.  Once ISC detects a time-out condition
   (loss of communication to the server), ISC will notify the user and 
   terminate.  The current ISC console session cannot re-establish
   communications to the server once the server has been restarted.
   The current ISC console session must terminate, and a new ISC
   console session started to manage the server again.
WORK-AROUND: In order to re-establish communications to the server, 
   you must re-launch ISC to the server once the server has restarted.
   You can wait for the current ISC console session to terminate
   normally (after the time-out is detected), or you can manually stop 
   the ISC console process and then restart ISC.
STATUS: Intel is investigating the possibility of fixing this erratum.

2. 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.
WORK-AROUND: 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.

3. 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 indicate that win32rap attempted to start 
   the NetWare services. They are not a concern if you are using tcp/ip 
   for server communication.
WORK-AROUND: You can ignore the error if your network only supports tcp/ip.
STATUS: Intel is not investigating this erratum.

4. The Windows NT* OS may run CHKDSK on Intel(R) AP450GX servers
   after a reboot.
PROBLEM: If the server performs a "Shutdown the OS and Power Off"
   or a "Shutdown the OS and Hardware Reset" event action on an 
   Intel(R) AP450GX Windows NT server, the OS may run CHKDSK 
   during the next OS boot.
IMPLICATION: The software may flag the file system for possible
   corruption due to system shutdown or reboot before the file system
   terminated normally. During reboot, the OS may run CHKDSK to verify
   file system stability.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.

5. An erroneous message displays in the Windows NT event viewer when the
   Baseboard Service installs the baseboard MIF.
PROBLEM: On Intel(R) AP450GX servers, when the Baseboard service
   installs the baseboard MIF, the following message displays in the 
   Windows NT event viewer:
       "The description for Event ID (0) in Source (Baseboard 
        Service) could not be found. It contains the following 
        insertion string(s): BaseboardService error: 0, About to 
        call SLCiInstallData: c:\smm32\dmi\nt\bin\baseboardc.mif"
IMPLICATION: You may see an erroneous error message in the event 
   log. This does not effect the function of the server.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.

6. 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 you intervenes.
WORK-AROUND: Use other event actions.
STATUS: Intel is investigating the possibility of fixing this erratum.

7. An erroneous message displays in the Windows NT event viewer when ISC
   initiates a Shutdown action
PROBLEM: On Intel(R) MB440LX Windows NT Servers, when ISC initiates
   a Shutdown action in response to an abnormal event, the following error 
   message occasionally appears in the Windows NT event viewer. 
       "The description for event ID (0) in Source (Baseboard 
        Service) could not be found.  It contains the following 
        strings Baseboard Service Error = -536412156, in Shutdown 
        OS."
IMPLICATION: Users may see an erroneous error message in the event 
   log. This does not effect the function of the server.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.

8. The ISC user interface allows configuring actions for unavailable
   thresholds
PROBLEM: On Intel(R) NC440BX, Intel(R) NA440BX, Intel(R) MB440LX
   and Intel(R) RC440LX Servers, the ISC user interface allows event
   configuration for the events that are unavailable. For example, 
   voltage sensors do not have Non-critical thresholds, but the user
   interface allows configuration of the actions for transition to 
   Non-critical state.
IMPLICATION: This may be confusing to users. Setting actions does not
   have any side-effects.
WORK-AROUND: These actions can be ignored.
STATUS: Intel is investigating the possibility of fixing this erratum.

9. Power Supply numbering is not consistent
PROBLEM: On Intel(R) MB440LX AD450NX, and AC450NX servers, ISC displays power 
   supply numbers as sequential, even if the actual location of the Power 
   supplies in the system has a missing Power Supply in a middle slot.
IMPLICATION: This may be confusing to users.
WORK-AROUND: None
STATUS: Intel is investigating the possibility of fixing this erratum.

10. The Memory Data Width displays as 0
PROBLEM: On Intel(R) MB440LX Servers, ISC displays the Memory data 
   width for all DIMMs as 0.
IMPLICATION: The information is incorrect. No other functions are
   affected.
WORK-AROUND: None
STATUS: Intel is investigating the possibility of fixing this erratum.

11. Temperature Resolution/Accuracy incorrect
PROBLEM: For Intel(R) MB440LX Servers, the ISC application displays the
   Temperature Resolution as 10C. For Intel(R) AP450GX servers, the 
   Temperature Accuracy is listed as 0%.
IMPLICATION: The information is incorrect. No other functions are
   affected.
WORK-AROUND: None
STATUS: Intel is investigating the possibility of fixing this erratum.

12. NWRAP.NLM reports an initialization error
PROBLEM: On Intel(R) MB440LX Servers running NetWare 4.11 OS, 
   disabling (or removing) one of the CPUs occasionally causes 
   NWRAP.NLM to report the following error during SM_AUTO.NCF 
   startup :
       "Registration failed, status = 0x211 - program aborted"
IMPLICATION: When this happens, the ISC application can not be used to
   manage this server.
WORK-AROUND: Edit the SYS:/SYSTEM/ISC_ON.NCF file to include the
   following statement BEFORE load nwrap statement :
       LOAD DELAY 10
STATUS: Intel is investigating the possibility of fixing this erratum.

13. ISC shutdown and power control actions may not work on NT 4.0 SP3
   or Enterprise Edition if the SMM driver is loaded.
PROBLEM:   If NT 4.0 Service Pack 3 is loaded on a system with a 
   Server Management Module (SMM) card installed and a 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.
WORK-AROUND: Use SMM Card functions to power-off or reset the
   system.
STATUS: Intel is investigating the possibility of fixing this erratum.

14. The OS becomes disabled when loading BASEBOARD.NLM in NetWare
   or BASEBRD.EXE for Windows NT.
PROBLEM: For Intel(R) AP450GX MP based systems, thresholds are
   set up in a way that sensors are always in violation of multiple
   thresholds.  Therefore, whenever the System Management Interrupt
   (SMI) handler is done servicing one threshold, another one is waiting.
   The effect is that the machine continuously calls the very high priority
   SMI handler and there are no CPU cycles left for normal OS threads.
   This leads to the condition that the operating system becomes 
   disabled.
IMPLICATION: The system will appear to hang.
WORK-AROUND: Clear CMOS or reload default threshold values from
   the SCU to correct the problem.
STATUS: Intel is investigating the possibility of fixing this erratum.

15. "NO FORMAT DEFINED" event message is displayed for traps 
   generated by ISC.
PROBLEM: If you use the EVENT CONFIGURATION menu 
   option in HP NNM to configure event actions for each trap forwarded 
   from the DMI-SNMP Translator (SDLINK), then the traps being 
   received will have a "NO FORMAT DEFINED" event message.  
   Highlighting the trap from the ALL EVENT window and right 
   clicking the mouse will not display the trap information.  If 
   you do not configure event actions for the traps, the traps in the 
   ALL EVENT window will display the trap OID.  Highlighting and 
   then right-clicking the trap will show information forwarded from 
   SDLINK.
IMPLICATION: Trap information is not available to the user.
WORK-AROUND: To view trap information, do not configure event
   actions from the EVENT CONFIGURATION menu option.
STATUS: Intel is investigating the possibility of fixing this erratum.

16. When the ISC stand-alone discovery function is stopped using
   the Server->Stop Discovery function, a handle and memory
   leak occurs.
PROBLEM: When the ISC discovery function is cancelled, each 
   discovery thread (one per IP address) looses 2 handles and 
   between 10 - 20K of memory.  This is because the threads 
   have no chance to clean up the handles and memory due to 
   the abrupt termination by TerminteThread(), a Win32 API.
IMPLICATION: System resources are not freed until the ISC
   stand-alone application terminates.
WORK-AROUND: After terminating server discovery using the
   Server->Stop Discovery function, stop and restart the ISC
   stand-alone application.
STATUS: Intel is investigating the possibility of fixing this erratum.

17. You may see an "Illegal Operation" error displayed on the 
   console.
PROBLEM: When the ISC GUI is running on a Win95 console, you may 
   see an "Illegal Operation" error after the ISC GUI has lost 
   communication with the backend server.  
IMPLICATION: This error is harmless.  Please ignore.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.

18. The "Immediate Hardware Reset" and "Immediate Power Off"
   features may not work properly during initialization.
PROBLEM: During the ISC GUI initialization, if you select
   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.
WORK-AROUND: You 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.

19. The BASEBRD2.MIB file doesn't support the DMI STATUS 
   DISPLAY group.
PROBLEM: The BASEBRD2.MIB file doesn't support the DMI
   STATUS DISPLAY group.  When managing an Intel(R) 
   AD450NX MP server from an SNMP management console, you
   cannot monitor or set the status display string (LCD).
IMPLICATION: You cannot monitor or set the status display 
   string on a Intel(R) AD450NX MP server.
WORK-AROUND: Use the ISC application to monitor or set the
   status display string.
STATUS: Intel is investigating the possibility of fixing this erratum.

20. The ISC Console leaks between 1 and 2 MB of memory in 
   24 hours of use.
PROBLEM: The ISC console leaks memory as health thread(s) 
   continue running.
IMPLICATION: If the ISC console is kept running on a machine 
   for several hours or days, it may use up most of the virtual 
   memory(VM) on that machine. This may eventually slow down
   ISC or other applications running on that machine.
WORK-AROUND: In order to free the virtual memory occupied 
   by the ISC console application, the ISC console application
   should be restarted.
STATUS: Intel is investigating the possibility of fixing this erratum.

21. The refresh key on the ISC console application fails to show
   newly discovered ICMB devices the first time the device is 
   added to the ICMB bus.
PROBLEM: Every time a new device is discovered and added 
   to the ICMB bus while the ISC console application is running, 
   the ISC console application looses visibility of all ICMB 
   discovered devices (even those previously discovered).
IMPLICATION: Refresh on the ICMB configuration dialog
   fails to show newly discovered ICMB devices.
WORK-AROUND: After enabling the ICMB feature on the 
   ICMB configuration dialog, wait several minutes all ICMB 
   devices to be discovered and then restart the ISC console
   application.
STATUS: Intel is investigating the possibility of fixing this erratum.

22. The Reclaim Inactive Resources menu option does not 
   function correctly.
PROBLEM: The memory associated with inactive ICMB
   devices is not freed when this menu option is selected.
IMPLICATION: Unneeded memory is not returned for
   system use.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.

23. Restore Factory Defaults menu option is enabled for
   ICMB devices.
PROBLEM: When the ISC console application view is 
   displaying information for a remote ICMB device, the Restore
   Factory Defaults option is incorrectly enabled.  This feature
   is not supported for ICMB devices.
IMPLICATION: If you select this menu option, nothing will
   occur.
WORK-AROUND: None.
STATUS: Intel is investigating the possibility of fixing this erratum.

24. ISC doesn't support dynamic swapping of power supplies.
PROBLEM: If the system is running with 3 power supplies, ISC will 
   display the 3 power supplies under the 'power' folder. When one
   power supply is removed (hot swapped) while the system is running, 
   ISC doesnot update the 'power' folder to indicate that the power 
   supply has been removed. If a power supply is added while the system
   is running, then a new entry will not be added in 'power' folder 
   either.
IMPLICATION: The 'power' folder may display incorrect information when
   removing or inserting a power supply when the system is running.
WORK-AROUND: Shutdown and re-boot the system.
STATUS: Intel is investigating the possibility of fixing this erratum.

25. The chassis status of a server seen through ICMB may be different from the 
    chassis status of the server seen locally.
PROBLEM: The chassis status seen through ICMB is overloaded with the
    power status and the intrusion status. But, only the intrusion status of the
    chassis is instrumented when seen locally. Because of this, the chassis status
    information of the same server seen locally and through ICMB may differ.  
 IMPLICATION: The 'chassis' folder may not display consistent information when a
    server is seen locally and through ICMB.  
WORK-AROUND: The power status and the intrusion status can be seen through the
    DMI browser in the ICMB generic chassis group. Proper information will be
    reflected on the DMI groups both locally as well as through ICMB. 
STATUS: Intel is investigating the possibility of fixing this erratum.

26. The EIF service for ICMB has been noted to infrequently 
    cause Dr. Watson exception errors.
PROBLEM: Infrequently the EIF service takes an exception and   
    and terminates. The EIF (Extensible Instrumentation Framework) service
    is related to the ICMB function in ISC. When this occurs, the servers
    that were monitored through ICMB will no longer be visible.
IMPLICATION: When the EIF service terminates abnormally, the remote
    monitoring capability through ICMB will be lost. Local instrumentation on 
    the monitored server will be unaffected.
WORK-AROUND: Restart the EIF service to regain ICMB functions. To restart 
    the EIF service on Windows NT, go to the control panel, services and start 
    the "EIF Service".
STATUS: Intel is investigating the possibility of fixing this erratum.

27. The 'Beep the Speaker' alert action does not work on SCO UnixWare*
   or Solaris server
PROBLEM:  The 'Beep the Speaker' alert action does not work on SCO UnixWare
   or Solaris server.
IMPLICATION:  The speaker will not beep due to the use of the 'Beep the 
    Speaker' alert action on UnixWare or Solaris systems
WORK-AROUND: Use the 'Broadcast a Message' alert action.  The speaker 
    will beep when the UnixWare or Solaris system receives its own broadcast message.
STATUS: Intel is investigating the possibility of fixing this erratum.

28. ISC StandAlone Console fails to load the help file
PROBLEM: ISC StandAlone Console fails to load the help file when it is 
    launched from a HTM link (from Internet Explorer or other web browsers).
IMPLICATION: The help program will not find the help file.
WORK-AROUND: Select 'Run...' from the Windows 'Start' button menu and select 
    the "Program Files\Intel\ISC\MI\EMC\IC\enuic.hlp"
STATUS: Intel is investigating the possibility of fixing this erratum.

29. The ISC shortcut and/or start menu item does not function or is very slow.
PROBLEM:  If ISC is installed to the local system and one or more remote
    systems, the shortcut target will point to the copy of ISC on a remote
    system.  If the remote system has does not have the ISC StandAlone 
    Operation installed, the launch will not complete.  If the remote system
    is not running when ISC is launched, the launch will not complete.  If the
    remote system is busy when ISC is launched, ISC may take a long time to 
    launch.
IMPLICATION:  The ISC shortcut may not properly launch the ISC application, 
    or the ISC application will launch very slowly.
WORK-AROUND 1: After installing ISC to all remote servers, rerun install and
    install to the local server only.
WORK-AROUND 2: Manually edit the ISC shortcut target to point to the local 
    copy of the "Program Files\Intel\ISC\MI\EMC\IC\iscsa.exe" application.
    Also ensure that the "Starts in:" field points to the 
    "Program Files\Intel\ISC\MI\EMC\IC" directory.
STATUS: Intel is investigating the possibility of fixing this erratum.

30. Unresolved User defined types found in dmtf*.mib
PROBLEM: The dmtf*.mib files included in ISC 1.x contains unresolved user
    defined type DmiString.
IMPLICATION: This is warning and will not affect the functionality
    of the software.
STATUS: Intel is investigating the possibility of fixing this erratum.

31. Icon associated with a ISC managed Solaris server shows Unknown type.
PROBLEM: Under HP OpenView, the server icon that represents an ISC managed
    server will appear as a server of unknown type.
IMPLICATION: ISC managed Solaris server will appear as an ISC managed server
    of unknown type.
STATUS: Intel is investigating the possibility of fixing this erratum.

32. For some sensors, the nominal, maximum and minimal value might not match
    the operating value
PROBLEM: Nominal, maximum, and minimal values for some sensors are not correct.
IMPLICATION: The values are static and do not affect the main functionality
    of the software.
STATUS: Intel is investigating the possibility of fixing this erratum.

**********************************************************************
D. LANDesk* Server Manager:
**********************************************************************
1. A Repair AMS2 database message is displayed after abnormal server 
   shutdown.
PROBLEM: A Repair AMS2 database message is displayed after abnormal 
   server shutdown.
IMPLICATION: The LDSM application may fail to start or function
   correctly as a result of a corrupted AMS2 database.  A corrupted 
   AMS2 database may result from an immediate server shutdown, 
   immediate hardware reset or immediate power-off action.
WORK-AROUND: The AMS2 database may be repaired as follows:
   1. Open the Control panel
   2. Select the ODBC icon
   3. Select the System DSN tabbed page
   4. Click the Configure button
   5. Select AMS
   6. Click the Repair button
   If the above steps do not fix AMS2 database corruption, 
   replace the AMS2 database with the one on the LDSM CD-ROM.
STATUS: Intel is investigating the possibility of fixing this erratum.

2. An error message appears on the LDSM console when attempting to 
   start ISC.
PROBLEM: If the ISC server software is installed on a remote server, 
   but the console software is not installed on the machine that has
   LDSM installed, then an error message will appear that reads:
     "Error : Token not defined on the server Result = 80004005. 
      Return Server manager setup and use the Have disk option to 
      install the application. The application should be included
      on disk supplied by the original equipment manufacturer "
   The LDSM software is told, by the server, that ISC is installed and
   so should appear in the Tools menu.  However, if the ISC console
   software is not installed on the LDSM client, then LDSM can not
   run the ISC application.
IMPLICATION: ISC will not start on the console.
WORKAROUND: You must install the ISC console software on the 
   same client computer that has LDSM installed.
STATUS: Intel is not investigating this erratum.

3. ISC may not appear in the Tools menu on the LDSM console.
PROBLEM: The DMI Service Provider maintains a backup copy of the
   DMI database for recovery purposes.  If after installing ISC, the DMI
   database gets corrupted prior to a normal server shutdown, then the
   next time the server boots the DMI database will be restored from a 
   version that does not contain ISC installed components.  If the
   LDSM console is run on this version of the DMI database, then ISC
   would not appear under the Tools menu even though ISC had been
   installed.
IMPLICATION: ISC will not appear in the LDSM Tools menu even though
   it has been installed.
WORKAROUND: There are several workarounds that will solve this 
   problem.  
   * Reinstalling ISC.  
   * Manually copying the DMI database file sldb.dmi to the 
       MIFS\backup directory after installing ISC.
STATUS: Intel is investigating the possibility of fixing this erratum.

4. SNMP traps are not appearing in the LDSM Trap Receiver
PROBLEM: The LDSM SNMP trap receiver log does not appear to be 
   receiving the events that are generated by ISC.  ISC is correctly
   generating the AMS event, because an AMS message box will appear.
   However, LDSM is not creating an SNMP trap and logging it into the 
   trap receiver log.
IMPLICATION: Not all ISC events appear as SNMP traps.
WORKAROUND: None known at this time.
STATUS: Intel is investigating the possibility of fixing this erratum.

5. The LDSM SNMP Event Viewer cannot run on the same machine as
    HP OpenView*.
PROBLEM: A conflict between LDSM and HP OpenView.
IMPLICATION: Only one of these applications can receive traps, if 
   running on the same Windows NT system. 
WORK-AROUND: Run one viewer at a time.
STATUS: Intel is investigating the possibility of fixing this erratum.

6. ISC alerts do not appear in the LDSM alertlog.
PROBLEM: The LDSM alertlog does not receive the events that are generated
   by ISC.  ISC is correctly generating the AMS event, an AMS message box appears.
   However, LDSM is not logging it into the LDSM alertlog.
IMPLICATION: Not all ISC events appear in the LDSM Alertlog.
WORKAROUND: None known at this time.
STATUS: Intel is investigating the possibility of fixing this erratum.

7. LDSM 6.x may fails to launch ISC console.
PROBLEM: Interaction between LDSM 6.x AMS and ISC for Windows 9x/NT4 SP4.
IMPLICATION: ISC cannot be launched under LDSM 6.x on a Windows 9x/NT4 SP4
   system.
WORKAROUND: Use the include ISC StandAlone console instead.
STATUS: Intel is investigating the possibility of fixing this erratum.

8. ISC AMS Alert configuration may not work correctly under LDSM.
PROBLEM: ISC AMS Alert configuration may not work correctly under LDSM.
IMPLICATIONL ISC might not be able to configure AMS alert action(s).
STATUS: Intel is investigating the possibility of fixing this erratum.

**********************************************************************
E. Adaptec SCSI 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.
WORK-AROUND: The SCSI DMI instrumentation requires Adaptec ASPI
   drivers (ASPI32.SYS and WNASPI32.DLL). You 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 you 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.
WORK-AROUND: None required.  The (slightly) non-compliant MIFs 
   can be successfully browsed by LDSM and DMI Explorer (the DMI browser
   bundled with ISC).  We currently believe there should be no effect on 
   your ability to access and use this data.
STATUS: Intel is investigating the possibility of fixing this erratum.

3.  The Adaptec component instrumentation "CI/O Array Management Service"
    will not work with NetWare v5.0.
PROBLEM: The Adaptec component instrumentation "CI/O Array Management
    Service" will not work with NetWare v5.0.
IMPLICATION: Adaptec instrumentation functionality will be unavailable 
    on NetWare v5.0
WORK-AROUND: None.
STATUS: Novell and Adaptec are investigating the the possibility of 
    fixing this erratum.  A fix will be made available through their
    web sites if it becomes available. 
 


**********************************************************************
F.  Symbios SCSI Instrumentation:
**********************************************************************
1. The Symbios icon does not appear in the 3rd Party folder of the Server
   instrumentation view or the 3rd Party folder is missing. 
PROBLEM: On N440BX and M440LX servers, the Symbios icon does
   not appear in the 3rd Party folder of the Server instrumentation view.
   Additionally, examination of the MIF database (sldb.dmi) "Symbios SDMS 
   Mass Storage System Mif Definition" component with DMI explorer shows 
   either that there is a "###!!!DMI error in this component" 
   or that 'This verify is not supported(2)'.  This problem also causes a
   "Could not start the Symbios SCSI service on (server name).  Error 2140!
   An Internal Windows NT error occurred." message box when manually starting
   the Symbios SCSI service.  This error is a reason why the Symbios SCSI 
   service is installed as a disabled service as noted in the ISC manual. 
IMPLICATION: This problem occurs because the Symbios driver
   (Symc810.sys) does not support Symbios instrumentation service.  Version 
   4.1.2 or higher (Symc8xx.sys dated
   after July '97) is required for this feature.  A newer driver may have 
   come with the system Country Kit.  If not, it can be retrieved from the 
   Symbios FTP site "ftp://ftp.symbios.com/pub/symchips/scsi/drivers/". 
WORK-AROUND: Download and install the new driver.  The driver can be found 
   on the Symbios FTP site: "ftp://ftp.symbios.com/pub/symchips/scsi/drivers/".
   Download the appropriate files for your operating system(s) and follow the 
   instructions for loading the new driver.  After installing the new driver,
   it is necessary to reboot the server.  If the new driver is correctly
   installed. the Symbios icon will now appear in the 3rd party folder of
   the Server instrumentation view.
STATUS: This problem is fixed in the current Symbios driver.
   Upgrading the 53c8xx drivers should eliminate this problem.

**********************************************************************
G.  AMI RAID Instrumentation:
**********************************************************************
1. Occasional Error Message from AMI instrumentation.
PROBLEM:  On MB440LX servers, an error message with text Request
   failed Dlg may occasionally appear. This will not appear again if
   the tree is collapsed and expanded again.
IMPLICATION: This has no functional implications.
WORK-AROUND: Collapsing and expanding the tree will fix the problem.
STATUS: Intel is investigating the possibility of fixing this erratum.

**********************************************************************
End of errata file
**********************************************************************


