v
controller is the ServeRAID controller number (1–12)
v
drivenum is the logical drive number (1–8)
Problem-isolation and debug functions
The IPSSEND problem-isolation and debug functions include the following:
eraseevent
Use the eraseevent function 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 controller soft and hard
event logs.
Supported operating systems: Windows NT, Windows 2000
Command: ipssend eraseevent controller options
where:
v
controller is the ServeRAID controller number (1–12)
v
options is the designated event log:
– DEVICE for the device event log
– SOFT for the ServeRAID controller soft event log
– HARD for the ServeRAID controller hard event log
getbst
Use the getbst function to display the number of bad stripes in the
bad stripe table for each logical drive.
Supported operating systems: Windows NT, Windows 2000
Command: ipssend getbst controller
where:
controller is the ServeRAID controller number (1–12)
getevent
Use the getevent function to display information about various
unexpected events. IBM service representatives use 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:
v
Parity: An unexpected event occurred while data was being
transferred on the SCSI bus. This usually indicates a problem
with the SCSI cable, connectors, or terminators.
v
Soft: A SCSI device detected a check-condition event.
v
Hard: The SCSI controller detected an unexpected event. The
controller is the most likely cause.
v
Misc: The ServeRAID controller detected an event that was most
likely caused by the device.
The device event log also provides PFA alerts, which indicate that
the device has signaled the ServeRAID controller that it might fail in
the near future.
Supported operating systems: Windows NT, Windows 2000
Command: ipssend getevent controller options
where:
v
controller is the ServeRAID controller number (1–12)
v
options is the designated event log:
– DEVICE for the device event log
Chapter 7. Installing and using the IPSSEND command-line program
47
Summary of Contents for Netfinity ServeRAID-4L Ultra160
Page 1: ...IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference SC06 P461 10...
Page 2: ......
Page 3: ...IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference SC06 P461 10...
Page 12: ...x IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 15: ...Part 1 Installation and configuration Copyright IBM Corp 2000 1...
Page 16: ...2 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 34: ...20 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 50: ...36 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 51: ...Part 2 Utility programs Copyright IBM Corp 2000 37...
Page 52: ...38 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 56: ...42 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 64: ...50 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 68: ...54 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 69: ...Part 3 Maintenance and troubleshooting Copyright IBM Corp 2000 55...
Page 70: ...56 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 93: ...Part 4 Appendixes Copyright IBM Corp 2000 79...
Page 94: ...80 IBM Netfinity ServeRAID 4L Ultra160 SCSI Controller User s Reference...
Page 113: ......