HP-UX 11i v3 Crash Dump Improvements

Page 15
and a new device file name (known as a “persistent” device special file) introduced in HP-UX
11i v3 that corresponds to the LUN itself. If a dump device is configured using a legacy
device file name the dump infrastructure will convert it to the new LUN device file and then
choose a lun path as discussed in Section 3.3. See the man page intro(7) and the HP-UX
11i v3 Mass Storage Device Naming White Paper for general information and details
regarding the HP-UX 11i v3 device file formats.
4.4 HBA Dump Capability
HP-UX 11i v3 provides a new command, scsimgr(1m), which has an option to display whether
or not an HBA port is dump-capable. The following example shows the capability of the HBA
port addressed by the device file /dev/c8xx0:
# scsimgr get_attr -a capability -D /dev/c8xx0
SCSI ATTRIBUTES FOR CONTROLLER : /dev/c8xx0
name = capability
current = Boot Dump
default =
saved =
The following example shows the capability of the HBA port at hardware path 2/0/12/1/1:
# scsimgr get_attr -a capability -H 2/0/12/1/1
SCSI ATTRIBUTES FOR CONTROLLER : 2/0/12/1/1
name = capability
current = Boot Dump
default =
saved =
Both of the HBA ports in the above examples are capable of dump. Some HBAs/drivers may
not support dump, including 3rd party HBAs for example, so the scsimgr command can be
used to quickly discover if dump is supported through a given HBA.
4.5 Ignite-UX Recovery
Dump devices which have been marked persistent using the -s option of crashconf(1m) may
need to be reconfigured for purposes of dump after an Ignite-UX recovery operation. After
completing the recovery run crashconf(1m) to check the dump device configuration and
correct it as needed.