ServeRAID Problem-Isolation and Debug Commands
The IPSSEND problem-isolation and debug commands include the following:
CERTIFY
Use the CERTIFY command to verify the media of a hard disk drive.
If the program finds a media error, it reassigns the sectors.
A summary of reassignments and PFA errors appears upon completion
of the verification.
Supported operating system: DOS
Command:
IPSSEND CERTIFY Controller Channel SID
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Channel with the channel number for the device (1, 2, or 3)
° SID with the SCSI ID for the device (0 to 15)
ERASEEVENT
Use the ERASEEVENT command to clear all logged entries in the designated event log.
See GETEVENT help for information about the contents of the Device Event Log and the
Adapter Soft and Hard Event Logs.
Supported operating systems: Windows NT, O/S2, Netware,
OpenServer, UnixWare, and DOS
Command:
IPSSEND ERASEEVENT Controller Options
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Options with one of the following:
- DEVICE for the Device Event Log
- SOFT for the ServeRAID adapter or controller Soft Event Log
- HARD for the ServeRAID adapter or controller Hard Event Log
FMSTATUS
Use the FMSTATUS command to display the progress of a format operation currently
processing.
Supported operating system: DOS
Command:
IPSSEND FMSTATUS Controller Channel SID
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Channel with the channel number for the device (1, 2, or 3)
° SID with the SCSI ID for the device (0 to 15)
FORMAT
Use the FORMAT command to perform a low-level format of a hard disk drive.
Attention When you issue this command, all data
on the drive will be lost.
Supported operating system: DOS
Command:
IPSSEND FORMAT Controller Channel SID
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Channel with the channel number for the device (1, 2, or 3)
° SID with the SCSI ID for the device (0 to 15)
GETEVENT
Use the GETEVENT command to display information about various unexpected events.
IBM uses the Soft and Hard Event Logs for development and debugging purposes only.
The Device Event Log contains event counters for each attached physical device.
These counters include:
° Parity: An unexpected event while transferring data on the SCSI bus.
This usually indicates a problem with the SCSI cable, connectors, or terminators.
° Soft: A SCSI device detected a check condition event.
° Hard: The SCSI controller detected an unexpected event.
The controller is the most likely cause.
° Misc: The ServeRAID adapter or controller detected an event that was
most likely caused by the device.
The Device Event Log also provides predictive failure analysis (PFA) alerts, which
indicate that the device has signaled the ServeRAID adapter or controller that it might
fail in the near future.
Supported Operating Systems: Windows NT, OS/2, NetWare,
OpenServer, UnixWare, and DOS
Command:
IPSSEND GETEVENT Controller Options
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Options with one of the following:
DEVICE for Device Event Log, SOFT for the ServeRAID adapter or
controller Soft Event Log, or HARD for the ServeRAID adapter or
controller Hard Event Log.
SELFTEST
The SELFTEST command is used to direct an adapter or a device to perform its self-test.
Supported operating systems: DOS
Command:
IPSSEND SELFTEST Controller Options
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Options with AD for the ServeRAID adapter or controller self-test or PD
Channel SID for the Device self-test.
NOTE: Channel represents the drive channel and SID represents the
SCSI ID for the device.
STARTDELY
Use the STARTDELY command to set the number of drives in a group to start up
simultaneously and to set the delay in seconds between the startup of these groups
of drives.
Supported operating systems: DOS
Command:
IPSSEND STARTDELY Controller Options
Replace:
° Controller with the ServeRAID controller number (1 to 8)
° Options with a question mark (?) to display concurrent drive
startup count: Drive Count (1 to 16) and Delay Time (3 to 15 seconds).
Please see the LEGAL - Trademark notice.
Feel free - send a for any BUG on this page found - Thank you.