scsimgr SCSI Management and Diagnostics utility on HP-UX 11i v3 (March 2008)

• The ‘scsimgr activate’ command does not need to be invoked on multiple systems

connected to the storage as invoking on one host is sufficient. Please refer to any device-

specific best practices for more details.

• The ‘scsimgr activate’ command can be used to restore the preferred paths to the

devices. Please refer to any device-specific best practices for more information.

• The ‘scsimgr activate’ command may fail if the SCSI stack is performing internal

configurations on the disk device. Upon detection of certain check conditions, the SCSI stack

re-initiates probing of lunpaths of the disk device and their asymmetric state becomes

unknown. If ‘scsimgr activate’ is invoked at this moment, the SCSI stack causes the

command to fail as if there were no standby path available to the disk device.

The ‘scsimgr activate’ command and the support for T10 ALUA was added after the February

2007 release of HP-UX 11i v3. For full support of this functionality, install patches PHKL_36248,

PHKL_36249, and PHCO_36250 (or any succeeding patches), or a later release of HP-UX 11i v3.

Additional Resources

White papers

White papers can be found at:

http://docs.hp.com/en/netsys.html#Storage%20Area%20Management

• The Next Generation Mass Storage Stack

• HP-UX 11i v3 Persistent DSF Migration Guide

• HP-UX 11i v3 Mass Storage Device Naming

Man pages

• intro(7), insf(1M), ioscan(1M), lssf(1M), mksf(1M), mknod(1M), rmsf(1M)

• scsimgr(1M), scsimgr_esdisk(7), scsimgr_estape(7), scsimgr_eschgr(7)

herein is subject to change without notice. The only warranties for HP products and

services are set forth in the express warranty statements accompanying such

products and services. Nothing herein should be construed as constituting an

additional warranty. HP shall not be liable for technical or editorial errors or

omissions contained herein.