SERVERAID LOG MUST BE CLEARED after FIRMWARE/BIOS is UPDATED


Subject: SERVERAID LOG MUST BE CLEARED after FIRMWARE/BIOS is UPDATED
New Netfinity server RETAIN Tip: 

    Record number:       H061134
    Device:              D/T8644
    Model:               M
    Hit count:           UHC00000
    Success count:       USC0000
    Publication code:    PC50
    Tip key:
    Date created:        O98/12/22
    Date last altered:   A98/12/22
    Owning B.U.:         USA


Abstract: SERVERAID LOG MUST BE CLEARED after FIRMWARE/BIOS is UPDATED


SYMPTOM:

There are several symptoms. All are listed below:

  1.  The "IPSSEND GETEVENT 1 DEVICE" may only display part of the expected table.
  2.  The "IPSSEND GETEVENT 1 SOFT" may show no or incorrect data.
  3.  Event logs from the ServeRAID may not contain expected data.
     Format or content may be incorrect.


PROBLEM ISOLATION AIDS:



NOTE: To confirm compatibility see the following Web site:

http://www.pc.ibm.com/us/compat/


FIX:

After updating Firmware/BIOS:

If RAIDADMIN is on the system,
start the program,
select the adapter,
select view soft log,
select erase log,
close soft log window,
select view hard log,
select erase log,
close hard log window,
select view device log,
select erase log,
close device log window.


If you do not choose to install RAIDADMIN, from the supplemental programs use IPSSEND for the NOS you are using.
From the command line type:

"IPSSEND ERASEEVENT 1 SOFT"
"IPSSEND ERASEEVENT 1 HARD"
"IPSSEND ERASEEVENT 1 DEVICE"

NOTE: The 1 implies first or only ServeRAID adapter
(this can be 1-7 depending on the number of ServeRAID adapters installed in the system).

NOTE: A DOS version of IPSSEND is available in the supplemental program area of the ServeRAID programs. If you choose not to install IPSSEND for your NOS a DOS bootable diskette with the ASPI device driver in the CONFIG.SYS would allow the logs to be cleared without the need to do an install. Use the IPSSEND located in the DOS subdirectory.


DETAILS:

The pointers for where the logs are to be stored could be changed with new BIOS/Firmware.
If the pointer does change, then it will begin writing the log to that area and might overlap an area where a log was before.
The result ends up being a mesh of logs which is unreadable.
Clearing the log after updating resets all pointers so that any further data will not be overlapped.


Back to  Jump to TOP-of-PAGE

Please see the LEGAL  -  Trademark notice.
Feel free - send a Email-NOTE  for any BUG on this page found - Thank you.