DYNAPATH

USER GUIDE

FalconStor DynaPath User Guide

FalconStor Software, Inc.

2 Huntington Quadrangle, Suite 2S01
Melville, NY 11747
Phone: 631-777-5188
Fax: 631-501-7633
Web site: www.falconstor.com

User Guide content may change between major product versions in order to reflect
product updates released via patches. In the guide and its table of contents, the
heading for changed content will be followed by (updated Month Year).
The document code at the bottom of the page includes the guide publication date.

Copyright 2001-2014 FalconStor Software. All Rights Reserved.

FalconStor is a registered trademark of FalconStor Software, Inc. in the United States and other countries.
Linux is a registered trademark of Linus Torvalds.
Windows is a registered trademark of Microsoft Corporation.
All other brand and product names are trademarks or registered trademarks of their respective owners.
FalconStor Software reserves the right to make changes in the information contained in this publication without prior notice. The
reader should in all cases consult FalconStor Software to determine whether any such changes have been made.

10614

Contents
Introduction
Hardware preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
HBA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

DynaPath for Windows 2012

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Configure HBA settings (updated Oct.2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Install DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
Detect new devices after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Manage DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Configure Windows Server 2012 Cluster for DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . .8
Uninstall DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

DynaPath for Windows 2008

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Configure HBA settings (updated Oct.2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
Install DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Detect new devices after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Manage DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Configure Windows Server 2008 Cluster for DynaPath . . . . . . . . . . . . . . . . . . . . . . . . .15
Uninstall DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

DynaPath for Windows 2003

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Configure HBA settings (updated Oct.2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Install DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Detect new devices after installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Manage DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
DynaPath and Microsoft clusters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
Customize Windows MPIO parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
Uninstall DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

DynaPath for Solaris

Install DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25
Detect dynamic devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Manage DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26
Configure Solaris Fibre Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Label boot device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
Disable Fibre Boot mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
i

Contents

Configure HBA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

Uninstall DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

DynaPath for AIX

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Install DynaPath (updated June 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Detect dynamic device (updated June 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Manage DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Enable Dynamic Tracking and Fast FC error recovery . . . . . . . . . . . . . . . . . . . . . .41
Name DynaPath devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Configure AIX Fibre Boot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Disable Fibre Boot mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Expand an AIX physical volume group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45
Configure share mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Release SCSI reservation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Manual procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
Automated procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .48
Switch between PVID and UDID for virtual SCSI disks . . . . . . . . . . . . . . . . . . . . . . . . .50
Uninstall DynaPath (updated January 2014) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51
Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

DynaPath for Linux

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Install DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Detect dynamic devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Manage DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Configure HBA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Configure DynaPath for the Logical Volume Manager . . . . . . . . . . . . . . . . . . . . . . . . . .55
Create logical volumes and groups using DynaPath devices . . . . . . . . . . . . . . . . .56
Uninstall DynaPath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Error codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .57

DynaPath Operations
DynaPath script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Manage DynaPath devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65

Index

ii

DynaPath User Guide

Introduction
FalconStor DynaPath is a load balancing/path redundancy application that
ensures constant data availability and peak performance across the SAN by
performing Fibre Channel HBA load-balancing, transparent fail over, and fail back
services. DynaPath creates parallel active storage paths that transparently reroute
server traffic without interruption in the event of a storage network problem. Peak
performance of the SAN is ensured by automatically distributing server traffic among
the server's storage paths (load balancing).
DynaPath offers a new level of data accessibility and improved performance for
storage systems by eliminating the point of failure represented by a single input/
output (I/O) path between servers and storage systems and permits I/O to be
distributed across multiple paths. DynaPath may not be available in all IPStor, CDP,
and/or NSS versions. Check with your vendor to determine the availability.
Benefits

Path failover/
Failback data
paths

Increases throughput by directing I/O requests through multiple HBAs and

storage system channels. Logical drives can be assigned to HBAs, manually
balancing the I/O load across paths.

Provides continuous access to mission-critical data by insulating server

applications from I/O path failures.

Installs easily and is transparent to server applications.

By providing alternate I/O paths from the server to the storage system, DynaPath
provides uninterrupted access to mission-critical data. This substantially insulates
server applications from I/O path failures.
In the event of a failed HBA, interface cable, or channel I/O card within the storage
system, DynaPath automatically re-routes I/O traffic to an alternate data path. Path
failover is essentially transparent, ensuring continuous access to data stored on the
storage system. When configured in the recommended failback mode, DynaPath
automatically restores the primary data path and system redundancy once the
defective component is replaced.

I/O load
balancing

DynaPath supports up to 16 data paths per device. Using an algorithm that chooses
the path with the least outstanding I/O counts, load balancing can improve I/O
performance.

How DynaPath
works

The DynaPath filter driver resides between the file system drivers and the disk
device drivers. I/O requests are passed from the file system through DynaPath, the
disk driver, and ultimately to the hardware.
DynaPath monitors the execution of I/O requests through the layered driver
architecture. When it detects a failure along an I/O path, it automatically re-routes
the request to an alternate path. Fail over to the redundant I/O path is transparent to
server applications, allowing continuous access to data stored on the disk array(s).
To applications, there may be a slight delay in normal I/O operations during path
failover. Existing drive numbers and device access functions continue to work as
expected.

DynaPath User Guide

Introduction

Hardware preparation
Although DynaPath will claim and manage qualified devices accessible from the
client by only a single I/O path, one of its primary purposes is the management of
multiple I/O paths to storage system devices. This eliminates the data path as a
potential single point of failure in the storage system.
To be properly configured for this purpose, every I/O-path element in the system
must be redundant. A given client must be equipped with at least two HBAs,
connected, in turn, by at least two cables to the storage system. Dual-port Fibre
Channel RAID devices require at least two Fibre Channel hubs for full I/O path
redundancy in a failover configuration.
Note: If you are adding a new device with multiple paths, install DynaPath first
before formatting the new device.
Refer to the FalconStor Certification Matrix for the latest support information.

HBA settings
DynaPath supports a variety of HBAs. For a complete list, see the Certification
Matrix at FalconStor.com.
In cases where the path failure time is critical, the link down timeout value on the
HBA can be lowered to allow faster switch from the failed path to the active path.
The minimum time that DynaPath requires to switch between paths is approximately
5 seconds plus any additional time that the HBA requires.
For QLogic HBAs, you can modify the BIOS settings using the SANsurfer tool. For
Emulex HBAs, FalconStor supports using the Miniport driver. FC port drivers are not
supported.
Make sure the HBA BIOS Setting has Target Reset enabled.
For all HBAs that support persistent binding, persistent binding should be
configured. Check with the HBA vendor for persistent binding procedures.
It is recommended that you reload the driver (reboot) in order for changes to be
made effective for most operating systems, such as Windows, Linux, and Solaris. It
is not necessary to reboot AIX clients since there are no BIOS settings that need to
be configured.

DynaPath User Guide

Introduction

Additional resources
You can download software builds, patches, and other documentation related to
your FalconStor product from the FalconStor Customer Support Portal at
support.falconstor.com (account required). Click the View Builds, Patches, &
Documentation link in the GA Releases area to complete a simple search form and
display available downloads.
Note that product release notes and patch descriptions may include information that
is not in the user guide. Be sure to review all available documents.
If you need technical support, create a support ticket on the FalconStor Customer
Support portal.

DynaPath User Guide

DynaPath User Guide

DynaPath for Windows

2012
Requirements
Configure HBA settings (updated Oct.2014)
It is recommended that you use the HBA settings specified below. In cases where
the path failure time is critical, the link down timeout value on the HBA can be
lowered to allow faster switch from the failed path to the active path. The minimum
time required by DynaPath to switch between paths is approximately five seconds,
plus any additional time required by the HBA. (HBA BIOS Setting: Target Reset
must be enabled.)
The following table lists the settings for different types of HBAs. These settings apply
for cluster and non-cluster environments unless specified. Refer to the certification
matrix on the FalconStor website for additional support information.
HBA Card Type

HBA Settings

QLogic

Login Retry Count = 8

Port Down Retry Count = 8
Link Down Count = 30
Enable Target Reset = True
FrameSize = 2048
Execution Throttle = 65535
LUNS per target = 256
Tape mode = Disable

Emulex

Node Timeout = 30
Link Timeout = 30

DynaPath User Guide

DynaPath for Windows 2012

Install DynaPath
Follow the steps below to install DynaPath:
1. Log in as Administrator.
2. If a previous version of DynaPath is installed on your system, remove it before
installing this version of DynaPath.
3. Assign devices from the storage server to the DynaPath client.
4. Verify that the client is able to see and access all storage devices through all
available paths. For example, If you have two paths to your storage system,
each logical drive should be displayed twice.
If you cannot see all available storage devices through every path, verify that
you have the latest Fibre Channel HBA drivers loaded on your system.
5. Launch the DynaPath setup.exe program.
6. Follow the step-by-step instructions during the installation process.
7. Reboot the computer.
8. Verify that your storage server disks are configured properly, open Device
Manager and expand Disk Drives.

One device displays for each LUN that is assigned. The path is displayed from
the properties of the device.
DynaPath User Guide

DynaPath for Windows 2012

Detect new devices after installation

After DynaPath has been installed, if you assign new devices to the client, you can
rescan the device and the driver will be installed automatically.
To rescan:
1. Right-click on My computer and select Manage.
2. In the Computer Management window, select Device Manager.
3. Right-click on Disk drives, select Scan for hardware changes.
You should see one multi-path disk device for each device, and one SCSI disk
device for each path to the device.

Manage DynaPath
The load balancing policy defaults to Round Robin for each device.To configure the
load balancing policy and other DynaPath settings, follow the steps below:
1. Navigate to Start --> Control Panel --> Device Manager.
2. Expand the disk drives.
3. Select a device and navigate to Properties --> MPIO tab.
4. Click Details to configure the Timer Counters for DynaPath.
5. Verify the parameters are set properly and click OK. Make sure the parameters
match those displayed in the screen below.

DynaPath User Guide

DynaPath for Windows 2012

The parameters are described in the table below. All settings on this screen will
be carried over to the other disk
Parameter

Description

PDORemovePeriod

If all paths fail, the amount of time (in seconds) DynaPath

should check the paths before FalconStor failover occurs.
Regardless of whether this is a failover or standalone
environment, DynaPath will check the path status before
giving up (timeout and disconnection).

RetryCount

The number of times a failed I/O operation will be retried on

the primary path after it has tried unsuccessfully to use its
alternate path(s) and returned to the primary. When the
specified number of retries has failed, the I/O fails. The
highest value allowed is 100.

RetryInterval

The time interval (in seconds) between the retry attempts

described in the preceding parameter. The default value is 3
seconds. This value can not be set above 100 seconds.

DynaPath User Guide

DynaPath for Windows 2012

Configure Windows Server 2012 Cluster for DynaPath

DynaPath supports cluster configuration on Windows Server 2012.
When a storage server failover occurs, Windows cluster detects the resource failure
and attempts to restart the failed resource according to cluster policy "Response to
resource failure. If the cluster fails to start the failed resource, you will need to bring
the resource online manually.
In order to have the cluster resources constantly available during storage server
failover events, you can configure cluster policy settings and increase the retry count
and interval.
To do this, right click on a disk in the Failover Cluster Management's summary of
storage and select the Policies tab and set the recommended values displayed in
the screen below where the system will try to restart a failed device five times within
five-minute period. You will need to set this parameter for all available devices.

To ensure service continuity during FalconStor server failover events, you should
carefully consider the failover properties of your Windows cluster services and
applications. If the cluster fails to start the service or application, you will need to
bring it online manually.
To view application failover properties, right click on a configured service or
application in the Failover Cluster Management's Services and Applications and
select the Failover tab.

DynaPath User Guide

DynaPath for Windows 2012

The recommended settings are displayed on the screen below.

If you are using DynaPath with Microsoft clusters and both initiators are unplugged
on the node that is the cluster owner, Microsoft Cluster will not fail over to another
node until DynaPath times out (which will take about five minutes).

DynaPath User Guide

DynaPath for Windows 2012

Uninstall DynaPath
Follow the steps below to uninstall DynaPath:
1. In the FalconStor Management Console, unassign devices that are managed by
DynaPath.
2. On the Windows machine, navigate to Start --> Control Panel--> Programs and
Features.
3. Click the Uninstall button.
DynaPath uninstalls and the system automatically reboots.
After DynaPath has been installed, your disk may no longer be managed by MPIO.
To reset MPIO management, add the disks again from the Discover Multi-Paths tab
in the MPIO Properties control panel.

DynaPath User Guide

10

DynaPath User Guide

DynaPath for Windows

2008
Requirements
Configure HBA settings (updated Oct.2014)
It is recommended that you use the HBA settings specified below. In cases where
the path failure time is critical, the link down timeout value on the HBA can be
lowered to allow faster switch from the failed path to the active path. The minimum
time required by DynaPath to switch between paths is approximately five seconds,
plus any additional time required by the HBA. (HBA BIOS Setting: Target Reset
must be enabled.)
The following table lists the settings for different types of HBAs. These settings apply
for cluster and non-cluster environments unless specified. Refer to the certification
matrix on the FalconStor website for additional support information.
HBA Card Type

HBA Settings

QLogic

Login Retry Count = 8

Port Down Retry Count = 8
Link Down Count = 30
Enable Target Reset = True
FrameSize = 2048
Execution Throttle = 65535
LUNS per target = 256
Tape mode = Disable

Emulex

Node Timeout = 30
Link Timeout = 30

DynaPath User Guide

11

DynaPath for Windows 2008

Install DynaPath
Follow the steps below to install DynaPath:
1. Log in as Administrator.
2. If a previous version of DynaPath is installed on your system, remove it before
installing this version of DynaPath.
3. Assign devices from the storage server to the DynaPath client.
4. Verify that the client is able to see and access all storage devices through all
available paths. For example, If you have two paths to your storage system,
each logical drive should be displayed twice.
If you cannot see all available storage devices through every path, verify that
you have the latest Fibre Channel HBA drivers loaded on your system.
5. Launch the DynaPath setup.exe program.
6. Follow the step-by-step instructions during the installation process.
7. Reboot the computer.
8. Verify that your storage server disks are configured properly, open Device
Manager and expand Disk Drives.

One device displays for each LUN that is assigned. The path is displayed from
the properties of the device.
DynaPath User Guide

12

DynaPath for Windows 2008

Detect new devices after installation

After DynaPath has been installed, if you assign new devices to the client, you can
rescan the device and the driver will be installed automatically.
To rescan:
1. Right-click on My computer and select Manage.
2. In the Computer Management window, select Device Manager.
3. Right-click on Disk drives, select Scan for hardware changes.
You should see one multi-path disk device for each device, and one SCSI disk
device for each path to the device.

Manage DynaPath
The load balancing policy defaults to Round Robin for each device.To configure the
load balancing policy and other DynaPath settings, follow the steps below:
1. Navigate to Start --> Control Panel --> Device Manager.
2. Expand the disk drives.
3. Select a device and navigate to Properties --> MPIO tab.
4. Click Details to configure the Timer Counters for DynaPath.
5. Verify the parameters are set properly and click OK. Make sure the parameters
match those displayed in the screen below.

DynaPath User Guide

13

DynaPath for Windows 2008

The parameters are described in the table below. All settings on this screen will
be carried over to the other disk
Parameter

Description

PDORemovePeriod

If all paths fail, the amount of time (in seconds) DynaPath

should check the paths before FalconStor failover occurs.
Regardless of whether this is a failover or standalone
environment, DynaPath will check the path status before
giving up (timeout and disconnection).

RetryCount

The number of times a failed I/O operation will be retried on

the primary path after it has tried unsuccessfully to use its
alternate path(s) and returned to the primary. When the
specified number of retries has failed, the I/O fails. The
highest value allowed is 100.

RetryInterval

The time interval (in milliseconds) between the retry attempts

described in the preceding parameter. The default value is 3
seconds. This value can not be set above 100 seconds.

DynaPath User Guide

14

DynaPath for Windows 2008

Configure Windows Server 2008 Cluster for DynaPath

DynaPath supports cluster configuration on Windows Server 2008.
When a storage server failover occurs, Windows cluster detects the resource failure
and attempts to restart the failed resource according to cluster policy "Response to
resource failure. If the cluster fails to start the failed resource, you will need to bring
the resource online manually.
In order to have the cluster resources constantly available during storage server
failover events, you can configure cluster policy settings and increase the retry count
and interval.
To do this, right click on a disk in the Failover Cluster Management's summary of
storage and select the Policies tab and set the recommended values displayed in
the screen below where the system will try to restart a failed device five times within
five-minute period. You will need to set this parameter for all available devices.

To ensure service continuity during FalconStor server failover events, you should
carefully consider the failover properties of your Windows cluster services and
applications. If the cluster fails to start the service or application, you will need to
bring it online manually.
To view application failover properties, right click on a configured service or
application in the Failover Cluster Management's Services and Applications and
select the Failover tab.

DynaPath User Guide

15

DynaPath for Windows 2008

The recommended settings are displayed on the screen below.

If you are using DynaPath with Microsoft clusters and both initiators are unplugged
on the node that is the cluster owner, Microsoft Cluster will not fail over to another
node until DynaPath times out (which will take about five minutes).

DynaPath User Guide

16

DynaPath for Windows 2008

Uninstall DynaPath
Follow the steps below to uninstall DynaPath:
1. In the FalconStor Management Console, unassign devices that are managed by
DynaPath.
2. On the Windows machine, navigate to Start --> Control Panel--> Programs and
Features.
3. Click the Uninstall button.
DynaPath uninstalls and the system automatically reboots.
After DynaPath has been installed, your disk may no longer be managed by MPIO.
To reset MPIO management, add the disks again from the Discover Multi-Paths tab
in the MPIO Properties control panel.

DynaPath User Guide

17

DynaPath User Guide

DynaPath for Windows

2003
Requirements
Configure HBA settings (updated Oct.2014)
It is recommended that you use the HBA settings specified in the table below. In
cases where the path failure time is critical, the link down timeout value on the HBA
can be lowered to allow faster switch from the failed path to the active path. The
minimum time required by DynaPath to switch between paths is approximately five
seconds, plus any additional time required by the HBA. (HBA BIOS Setting: Target
Reset must be enabled.)
The following table lists the settings for each type of HBA. Refer to the certification
matrix on the FalconStor website for additional support information.
HBA Card Type

HBA Settings

QLogic

Login Retry Count = 8

Port Down Retry Count = 8
Link Down Count = 30
Enable Target Reset = True
FrameSize = 2048
Execution Throttle = 65535
LUNS per target = 256
Tape mode = Disable

Emulex

Node Timeout = 30
Link Timeout = 30

DynaPath User Guide

18

DynaPath for Windows 2003

Install DynaPath
Follow the steps below to install DynaPath:
1. Log in as Administrator.
2. If a previous version of DynaPath is installed on your system, remove it before
continuing with this installation.
3. Assign devices from the storage server to the DynaPath client.
4. Verify that the client is able to see and access all storage devices through all
available paths. For example, If you have two paths to your storage system,
each logical drive should be displayed twice. If you cannot see all available
storage devices through every path, verify that you have the latest Fibre
Channel HBA drivers loaded on your system.
5. Launch the DynaPath setup.exe program.
6. Follow the step-by-step instructions during the installation process.
7. Reboot the computer.
8. Verify that your storage server disks are configured properly, open Device
Manager and expand Disk Drives.
There will be one Multi-Path Disk Device entry per disk. For example, if there is a
single disk and two paths to this disk, there will be one Multi-Path Disk Device
and two physical disk entries under Disk Drives.
Installation note

If the local security policy for an unsigned driver is set to "Do not allow installation",
the following error message displays when attempting to install DynaPath on the
Windows machine:

DynaPath User Guide

19

DynaPath for Windows 2003

To continue installation, follow the steps below:

1. Navigate to Start --> All Programs --> Control Panel --> Administrative Tools -->
Local Security Policy.
2. Under Security Settings, expand Local Policy and highlight Security Options.
3. Right-click on Devices: Unsigned driver installation behavior and click Property
and change the Local Security Setting to Warn but allow installation.
4. Start the DynaPath installation again.
5. Select Yes to continue the installation when the following message displays:

Detect new devices after installation

After DynaPath has been installed, if you assign new devices to the client, you can
rescan the device and the driver will automatically be installed.
To rescan:
1. Right-click on My computer and select Manage.
2. In the Computer Management window, select Device Manager.
3. Right-click on Disk drives, select Scan for hardware changes.
You should see one multi-path disk device for each device, and one SCSI disk
device for each path to the device.

DynaPath User Guide

20

DynaPath for Windows 2003

Manage DynaPath
DynaPath is automatically configured upon installation. By default, both path failover
and load balancing are enabled. Changes to the configuration can be made via the
dynacfg utility. Type dynacfg at a command prompt for a list of available options.
Option

Description

-l

List all groups and displays several options.

-s spd_id

Display status for a specific path.

-e a c s l

Filter what will be displayed with the -s command by

excluding this path. This does not affect any functionality.

-i a c s l

Filter what will be displayed with the -s command by

including this path, if it was previously excluded. This does
not affect any functionality.

-u spd_id retrydelay
retrycount loadbalance

Enable or disable load balancing.

retrydelay - in milliseconds
retrycount - 0 to 1,000,000
loadbalance - 0 for disable or 1 for enable.
Note: While the retrydelay and retrycount can be changed
using this command, we do not recommend doing that.

-d, -m, -t

Technical support use only.

-x

Get and print the latest kernel dbg messages.

Examples
List all groups

F:>dynacfg -l

You will see output similar to the following:

Successfully opened \\.\dpd
Successfully created event
Send SPD_GETALLID
Debug_Level is set to 0
PnP Delay is set to 1 second
Use Page 80 is set to 0
There are 3 groups
-----------------------------------------------------spd_id: 1
spd_id: 2
spd_id: 3

From this example, you can see that there are three groups, debugging is turned off,
the PnP Delay is 1, and the system is using Page 80.

DynaPath User Guide

21

DynaPath for Windows 2003

Display path
status

F:>dynacfg -s spd_id

For example: F:>dynacfg -s 1

You will see output similar to the following:
Successfully opened \\.\dpd
Successfully created event
spd_id is 1
Send SPD_GETPATHSTATE
Group: 1
-----------------------------------------------------npath: 4
balance: 1
retrydelay: 3000
retrycount: 10000
failback: 0
exclude: 0
primarygroup: 0
type: 0
StrID: 600D7790084A57CAFABFDA6D8FD2
Path Status:
------------------------------------Path00:
State: PATH_GOOD
Path00:
OnController: Primary
Path00: Commands Read: 0
Path00: Commands Write: 0
Path00:
Bytes Read: 0
Path00:
Bytes Write: 0
Path01:
State: PATH_GOOD
Path01:
OnController: Primary
Path01: Commands Read: 3
Path01: Commands Write: 0
Path01:
Bytes Read: 1536
Path01:
Bytes Write: 0

In this example, you can see that balance is set to 1, which means load balancing is
enabled (1=enabled, 0=disabled). In addition, you can see that the status for each
path is good.
Enable or
disable load
balancing

dynacfg -u spd_id retrydelay retrycount loadbalance

For example, dynacfg -u 2 3000 100 1

To disable load balancing, set loadbalance to 0 (zero).

DynaPath and Microsoft clusters

If both initiators are unplugged on the node that is the cluster owner, Microsoft
Cluster will not fail over to another node until DynaPath times out (about five
minutes).

DynaPath User Guide

22

DynaPath for Windows 2003

Customize Windows MPIO parameters

An MPIO Parameters key is created during the DynaPath installation. The following
values are added under this key:
MPIO Parameter

Customize
registry settings

Setting

Description

PDORemovePeriod

300

If all paths fail, the amount of time (in seconds)

DynaPath should check the paths before FalconStor
failover occurs. Regardless of whether this is a
failover or standalone environment, DynaPath will
check the path status before giving up (timeout and
disconnection). If you are using FalconStor DiskSafe,
this parameter should be set to 5 to allow a snapshot
unmount in a manageable period of time.

RetryCount

100

The number of times a failed I/O operation will be

retried on the primary path after it has tried
unsuccessfully to use its alternate path(s) and
returned to the primary. When the specified number of
retries has failed, the I/O fails. The highest value
allowed is 100.

RetryInterval

The time interval, in milliseconds, between the retry

attempts described in the preceding parameter. The
default value is 3 seconds. This value can not be set
above 100 seconds.

If necessary, Wbemtest.exe can be used to change registry settings, without

requiring a system reboot. This program is located in the system32\wbem directory.
1. Launch Wbemtest.exe and select Connect.
2. Change Namespace to root\wmi and select Connect.
3. Under IWbemServices, select Open Class.
4. Enter MPIO_TIMERS_COUNTERS.
5. From the Object editor screen, select Instances.
6. Double-click the instance from this window.
7. Under Properties find the required items. (Typically the last three)
8. Double-click on the property, edit the value, and select Save Property.
9. Once all properties have been changed, select Save Object.
A Query Result window launches.
10. Select Close to have the properties dynamically activated.

DynaPath User Guide

23

DynaPath for Windows 2003

Uninstall DynaPath
Perform the following steps to uninstall DynaPath:
1. In the FalconStor Management Console, unassign devices that are managed by
DynaPath.
2. On the DynaPath machine, use Add/Remove Programs from the Control Panel
to uninstall DynaPath.
3. Reboot the machine.

DynaPath User Guide

24

DynaPath User Guide

DynaPath for Solaris

Install DynaPath
Follow these steps to install DynaPath:
1. Set up your system hardware.
2. Log in as root.
3. If a previous version of DynaPath is installed on your system, remove it and
reboot before continuing with this installation.
4. Assign devices from the storage server to the DynaPath client.
5. Verify that the client is able to see and access all storage devices through all
available paths.For example, If you have two paths to your storage system, each
logical drive should be displayed twice in the output of the command:
# format

If you cannot see all available storage devices through every path, verify that
you have the latest Fibre Channel HBA drivers loaded on your system.
6. If you are installing from the CD and running the Solaris Volume Management
daemon, the CD should be mounted automatically at /cdrom/cdrom0 or /
cdrom/ipstor_v2_<build_number>.
If the volume manager is disabled, log on as root, create the mount directory /
cdrom/ipstor and mount the CD-ROM with the commands
# mkdir -p /cdrom/ipstor
# /usr/sbin/mount -r -F hsfs /dev/sr0 /cdrom/ipstor

7. Install DynaPath:
# pkgadd d dynapath-<version number>-<build number>

For example: # pkgadd d dynapath-5.01-1000.pkg

8. Start DynaPath:
# dynapath start

9. Run initial setup to create a new configuration file and detect existing devices:
# dpcli setup

DynaPath User Guide

25

DynaPath for Solaris

Detect dynamic devices

You may be able to add new storage devices and place them under DynaPath's
control without requiring a reboot of the client. This is also known as dynamic LUN
allocation.
To add a Fibre Channel device to an existing path, perform the following steps after
the devices are connected:
1. Scan and load new devices into the system:
# devfsadm
# cfgadm -c configure <c#> [additional commands if using
qlc driver]
2. Verify the new devices have been detected by Solaris:
# echo | format
3. Scan and load the new devices into DynaPath:
# dpcli rescan
4. Verify the new devices have been detected by DynaPath:
# dpcli status

Manage DynaPath
For information about DynaPath scripts and commands, refer to DynaPath
Operations.

DynaPath User Guide

26

DynaPath for Solaris

Configure Solaris Fibre Boot

This section will guide you through the steps necessary to configure Fibre Boot
support. You can configure Fibre Boot using device path or device label.
1. Make a backup copy of the system image without DynaPath.
2. Install DynaPath version 5.01 or above.
3. Make sure the device links are up-to-date:
#devfsadm -Cv

4. Scan for the boot disk:

# dpcli setup

5. Confirm DynaPath detects the boot disk:

# dpcli status

6. Identify the boot device name and path and DynaPath device ID:
#format

7. Enable the disk for Boot Mode using DynaPath device ID:
#dpcli boot -b1 -l <boot disk's dpd_id>

8. Start the DynaPath boot disk:

# dpcli start <boot disk's dpd_id>

9. Run sanboot.sh
# /sbin/sanboot.sh enable

10. At this time you can label the boot device. (Refer to Label boot device.)
11. Reboot.

Label boot device

DynaPath derives the disk GUID (noted as SANID) from the serial number obtained
from the SCSI "INQUIRY" command. The GUID allows DynaPath to validate the
authenticity of the path. In a fibre-boot scenario the administrator may wish to boot
or work from a snapshot image. The new snapshot image will have a different GUID
which will not match the original GUID. If there is a GUID mismatch DynaPath will
fail to consolidate the device. A solution to this problem is to label the disk with a
unique name. DynaPath will then check the label while it is initializing and then
dynamically generate the GUID.
Instructions on how to configure DynaPath to detect the device GUID by device
label:
1. Label the boot device, for example, as root:
DynaPath User Guide

27

DynaPath for Solaris

# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:
>> 1. c6t0d0 <FALCON-IPSTORDISK-v1.0 cyl 39998 alt 2 hd 64 sec
32>
/pseudo/dpn@128/dpd@0,0
Specify disk (enter its number): 1
selecting c6t0d0
[disk formatted]
Warning: Current Disk has mounted partitions.
FORMAT MENU:
disk - select a disk
...
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format> volname
Enter 8-character volume name (remember quotes)[""]:ROOT
Enter "Y" when asked if you are ready to label disk and continue.

2. Identify the DynaPath device ID for the labeled device, for example, device
c6t0d0 labeled as root:
# dpcli status
====================================================
id gid:pid device name status bal buf rtrcnt rtrdly failback
====================================================
0 1:0 c1t210000E08B09D596d0 available 1 32 100 3000 1
>> dpd@0 = c6t0d0 (started) SANID="FALCON IPSTOR DISK
EU38QYL0J45X"
====================================================
The disk c6t0d0 is represented with id #0.

3. Back up /kernel/drv/dpd.conf.
4. Identify the section in /kernel/drv/dpd.conf with the entry dpd_id=0
Replace the configuration item SANID with the volume label, for example,
Before:
name="dpd" parent="/pseudo/dpn@128" target=0 lun=0 dpd_id=0
sdMajor=118 sdMinor="0" group_map="1"
nbuf=32 exclude=0 primarypath=0 boot_mode=1
balance=1 retrycount=100 retrydelay=3000 failback=1
type=4 primarygroup=1 SANID="FALCON IPSTOR DISK EU38QYL0J45X";

After:
name="dpd" parent="/pseudo/dpn@128" target=0 lun=0 dpd_id=0
sdMajor=118 sdMinor="0" group_map="1"
nbuf=32 exclude=0 primarypath=0 boot_mode=1
balance=1 retrycount=100 retrydelay=3000 failback=1
type=4 primarygroup=1 volname="ROOT";

Note: Make sure a semicolon ends the configuration entry.

DynaPath User Guide

28

DynaPath for Solaris

Disable Fibre Boot mode

To remove Fibre Boot disk management by DynaPath, follow the steps below:
1. Remove the boot mode option from all devices using the following command:
# dpcli boot -b0 -lall

2. Modify /etc/vfstab entries to point to original volume.

3. Remove the DynaPath rootdev entry from /etc/system.
4. Reboot machine.

Configure HBA settings

The table below provides recommended HBA settings:
HBA Card Type

HBA Settings

QLogic

Login Retry Count = 8

Port Down Retry Count = 8
Link Down Count = 30
Enable Target Reset = True
FrameSize = 2048
Execution Throttle = 32
LUNS per target = 256
Tape mode = Disable

Emulex

Node Timeout = 30
Link Timeout = 30

Uninstall DynaPath
In order to remove DynaPath, enter the following command as root:
# pkgrm dynapath

DynaPath User Guide

29

DynaPath for Solaris

Error codes
The following table contains a description of some common error codes:.

Error codes
Code

Text

Cause/resolution

DPSOL101

%d: Failed to alloc soft state

This is an internal error. Failed to allocate

device state for device. There may be a
problem with the DynaPath configuration or
devinfo tree.

DPSOL102

%d: Bad soft state

This is an internal error. Failed to allocate

DynaPath nexus device state. There may be
a problem with the DynaPath nexus
configuration or devinfo tree.

DPSOL103

scsi_hba_tran_alloc failed

This is an error with the SCSI Nexus

implementation from the transport HBA.

DPSOL104

scsi_hba_attach failed

This is an internal error for the SCSI Nexus

implementation could not bind DMA attributes
to device info and transport structure.

DPSOL105

%d: cannot detach: reason: bad soft state

This is an internal error. There is no available

device state for the device being referenced.
There may be an issue with the configuration.

DPSOL106

%d: cannot detach reason: nexus driver busy

There are DynaPath devices connected to

the Nexus. Cannot detach in this state.

DPSOL107

_scsi_destroy_pkt

This is an internal error. This should never be

called and will PANIC the machine.

DPSOL108

_scsi_dmafree

This is an internal error. This should never be

called and will PANIC the machine.

DPSOL109

ioctl SPN_UNLOAD cannot unload! device

busy

There are DynaPath devices connected to

the Nexus. Cannot unload driver in this state.

DPSOL110

Driver disabled because booted with "-a" and

dpd:spd_safe_boot != 0

DynaPath driver is not loaded because boot

parameter -a is specified or spd_safe_boot
symbol is set to a non-zero value.

DPSOL112

Cannot construct instance bit map - reason:

Not enough memory!

Memory exhausted. The user will need to

allocate more memory to the system.

DPSOL113

Could not allocate devmap instance

This is an internal error. A device probe was

called for the DynaPath control device. This is
harmless but should not happen.

PSOL114

Could not get spd_id prop!

This is a configuration error. The dpd_id

property is not in the configuration.

DPSOL115

%d: Cannot allocate state - instance #%d

state <%p>.

Memory exhausted. The user will need to

allocate more memory to the system.

DynaPath User Guide

30

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL116

Could not create control raw node for dpd_id

%d

Failed to create device node in the /devices

directory. This can indicate a bad kernel state.

DPSOL117

Error neither volname nor strID is defined in

configuration.

This is a configuration error. The volname or

strID property is not in the configuration.

DPSOL118

Could not get nbuf property, using default %d

This is a configuration error. The nbuf

property is not in the configuration.

DPSOL119

Error: Couldn't get sdMajor property!\n

This is a configuration error. The sdMajor

property is not in the configuration

DPSOL120

Error: Couldn't get sdMinor property!

This is a configuration error. The sdMinor

property is not in the configuration.

DPSOL121

%d: Device configuration is reserved.

SCSI device GUID/dpd_id is reserved. If the

device is removed temporarily and put back
(id reservation) prevents the device id from
changing and confusing the application

DPSOL122

Error: parse error reading threshold value

\"%s\" missing ':' <dpd_id=%d>

This is a configuration error. There is an error

in the threshold_map value.

DPSOL123

Error: parse error threshold group id is not a

number %s <dpd_id=%d>

This is a configuration error. There is an error

in the threshold_map value.

DPSOL124

Error: parse error threshold value is not a

number %s <dpd_id=%d>

This is a configuration error. There is an error

in the threshold_map value.

DPSOL125

Error: invalid group_id value %d

<dpd_id=%d>.

This is a configuration error. There is an error

in the threshold_map value.

DPSOL126

%d: Error: Could not allocate kernel memory!

Memory exhausted. The user will need to

allocate more memory to the system.

DPSOL127

%d: Error: Could not allocate buf!

Memory exhausted. The user will need to

allocate more memory to the system.

DPSOL128

%d: Could not get "balance" property!

This is a configuration error. The balance

property is not in the configuration. DynaPath
will set load balance off by default in this
case.

DPSOL129

%d: Could not get "retrycount" property!

This is a configuration error. The retrycount

property is not in the configuration. DynaPath
will set retrycount to default global variable
dpd:retrycount.

DPSOL130

%d: Could not get "retrydelay" property!

This is a configuration error. The retrydelay

property is not in the configuration. DynaPath
will set retrydelay to default global variable
dpd:retrydelay.

DynaPath User Guide

31

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL131

%d: Could not get "failback" property!

This is a configuration error. The failback

property is not in the configuration. DynaPath
will set failback option to on by default in this
case.

DPSOL132

%d: Could not get "exclude" property!

This is a configuration error. The exclude

property is not in the configuration. DynaPath
will set exclude option to on by default in this
case.

DPSOL133

%d: Disk excluded by this host!

The device is excluded from DynaPath's

view.

DPSOL134

%d: Error with group_map: number of paths

!= number of group_map values!

The number of device paths should equal the

number of values presented in the group map
in the configuration. There is a dpcli error.

DPSOL135

%d: Could not get "primarypath" property!

The primarypath property is not in the

configuration, causing this configuration error.
DynaPath will set the primarypath option to 0
in this case.

DPSOL136

%d: Could not get "primarygroup" property!

The primarypath property is not in the

configuration, causing this configuration error.
DynaPath will set the primarygroup to the
lowest path priority found in the group_map.

DPSOL137

%d: Error: Current group priority is zero;

please check the primary group settings or
group layout.

This is a configuration error. All devices have

a priority of zero, therefore DynaPath cannot
start the device.

DPSOL138

%d: Error: Cannot add anymore devices to

supported_device_table (max=%d)!

This configuration error is due to too many

devices specified in the support_device_table
property.

DPSOL139

"infinite_retry" is on for all devices.

Infinite retry is set. DynaPath will retry buffers

with an unlimited retry count. This is useful if
the device is a boot device.

DPSOL140

Error: Device path #%d failed to open

Reason: Device is in use by another driver/
application.

The actual SCSI disk device is busy.

DynaPath cannot open the device with the
F_EXCL option. DynaPath cannot start the
device.

DPSOL141

%d: path %d Error: Cannot claim slice #%d

(errno=%d)

The actual SCSI disk partition device is busy.

DynaPath cannot open the device with the
F_EXCL option. DynaPath cannot start the
device.

DPSOL142

device does not exist; please verify the

configuration.

The actual SCSI disk partition device does

not exist. DynaPath cannot open the device
with the F_EXCL option. DynaPath cannot
start the device.

DynaPath User Guide

32

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL143

Error: Device serial number mismatch

detected.

Device inquiry does not match expected

device inquiry. Verify the storage assignment.

DPSOL144

%d: Error: There are no available paths.

All device paths are unavailable. DynaPath

cannot start in logical device in this condition.

DPSOL145

%d: Could not create minor block node!

This is an kernel error/internal error. Kernel

could not create device in /devices directory.

DPSOL146

%d: Could not create minor raw node!

This is an kernel error/internal error. Kernel

could not create device in /devices directory.

DPSOL147

Cannot stop device -reason I/O is in

progress.

There are buffers remaining in the retry

queue. Device cannot be stopped in this
state.

DPSOL148

Cannot stop device dpd_id=%d - reason

device is in use

The DynaPath device is busy. It is being used

by an application or another driver/
subsystem.

DPSOL149

Error: Cannot stop device dpd_id=%d reason device is open

The DynaPath device is busy. It is being used

by an application or another driver/
subsystem.

DPSOL150

%d: Exception: open type %d not supported!

Device open failed due to invalid open type.

DynaPath only supports OTYP_BLK,
OTYP_MNT, OTYP_CHR, OTYP_SWP,
OTYP_LYR

DPSOL151

%d: Exception: Close type %d not supported

Device close failed due to invalid open type.

DynaPath only supports OTYP_BLK,
OTYP_MNT, OTYP_CHR, OTYP_SWP,
OTYP_LYR

DPSOL152

%d: Error: Offset %d is not an integral

number of sectors

This is an access error for a character device.

Offset is not a multiple of 512.

DPSOL153

%d: Error: Transfer length %d is not an

integral number of sectors

This is an access error for a character device.

Transfer length is not a multiple of 512.

DPSOL154

%d: I/O to device is denied!

This is an access error for a block device.

The device is either excluded or user
attempted to do a block operation to a ctrl
device.

DPSOL155

%d: Exception: (Strategy) bhead == NULL

This is a fatal error, which will cause the

machine to crash. The buffer device list is not
defined.

DPSOL156

%d: Error: (Select path) access to device is

denied

The device cannot be accessed. Make sure

you have the correct path and credentials.

DPSOL157

%d: I/O failure notification: Buffer error on

available device.

This occurs if the SCSI device is available,

but the block layer is returning EIO.

DynaPath User Guide

33

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL158

%d: I/O failure notification: Chained failure.

If DynaPath fails an I/O all following I/O's will

fail until the device is brought back online.

DPSOL159

%d: Error retry timeout : path %d mybp %x

prv %x retry %d

Retry count expired. DynaPath will fail buffer.

DPSOL160

%d: I/O Error returned : path %d mybp %x prv

%x retry %d fio %d downstream %d

DynaPath will fail buffer. Due to an I/O error.

DPSOL161

%d: SVTOC failed (error %d on primary path

%d)

This is a kernel/internal error. There may be a

problem with the ioctl argument sent to SCSI
disk device.

DPSOL162

%d: GVTOC failed (error %d on path %d)

This is a kernel/internal error. There may be a

problem with the ioctl argument sent to SCSI
disk device.

DPSOL163

%d: Error: Failed to add path invalid major

number %d != %d.

This is a configuration error. dpcli sent invalid

information to the SPD_ADD_PATH ioctl.

DPSOL164

%d: Error: Failed to add path to device.

DynaPath could not add path to configuration.

DPSOL165

Error invalid dpd_id = %d

Unhandled IOCTL sent to DynaPath. (This

error is confusing) It should be Error: Invalid
IOCTL sent to dpd_id = %d

DPSOL166

%d: Path failover from path# %d to path# %d.

Error occurred on the current path and I/O

was transferred to another available path

DPSOL167

%d Failed READ(10) test (path = %d

errno=%d).

Device failed verification. SCSI READ10

command failed. Device is marked as failed

DPSOL168

Exception: Could not create kernel thread!

This is a kernel error. The kernel could not

create a kernel thread for DynaPath.

DPSOL169

%d: Error: Could not obtain devid from device

(%d,%d)!

DynaPath could not obtain device id (devid)

from device. Device may not exist or support
devid.

DPSOL170

%d: Error: Could not register devid!

This is a kernel error. The kernel could not

create devid for DynaPath device.

DPSOL171

%d: Error: path %d error could not obtain

volume name from device errno=%d.

If volname attribute is defined DynaPath will

use the volume name attribute from the
VTOC. If DynaPath fails to obtain the VTOC
due to an ioctl error. It will report this error.
This is an error with the configuration or the
disk may be corrupted (due to lack of VTOC).

DPSOL172

%d: Error: path %d volume name mismatch

\"%s\" != \"%s\"\n

If volname attribute is defined. The VTOC

volume name does not match the expected
volume name of the configuration. The disk
may have been changed.

DynaPath User Guide

34

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL173

dpd%d: path %d: Error: could not update

SANID!

The SANID could not be obtained. There was

a failure with the INQUIRY command. Check
the storage server or the initiator
configuration.

DPSOL174

dpd%d: (Device Verification) path %d serial

number (SANID) mismatch detected
(required)\"%s\" != (actual)\"%s\"

The SANID obtained from the logical unit

does not match the expected SANID. The
logical unit may have changed upstream or
there may be an error with the configuration.
Use dpcli clean and dpcli rescan to fix this
problem.

DPSOL175

dpd%d: (Fabricate devid) path %d cannot

issue standard inquiry!

The SANID could not be obtained. There was

a failure with the INQUIRY command. Check
the storage server or the initiator
configuration.

DPSOL176

dpd%d: (Fabricate devid) path %d cannot

encode scsi inquiry data!

There was an error calling the function

ddi_devid_scsi_encode() internal function.
There may be a parameter error to the
function. The kernel may not support this
anymore and the driver will need to change.

DPSOL177

dpd%d: (Fabricate devid) path %d cannot

register devid!

There was an error calling the function

ddi_devid_register.There may be a parameter
error to the function. The kernel may not
support this anymore and the driver will need
to change.

DPSOL178

%d: Cannot allocate anymore paths for this

driver instance.

The configuration specified more paths then

the limit MAX_SP_PATH. There is an error
with the configuration.

DPSOL179

%d: Device sdminor %d is already allocated.

This logical device is already managed by the

DynaPath driver. This is an error with the
configuration.

DPSOL180

Invalid dpd_id %d

An application attempted to send

SPD_STARTSPD or SPD_STOPSPD to a
device other than dpdctrl.

DPSOL181

Error dip ddi_prop_create() failed returned:

DDI_PROP_NO_MEMORY

Memory exhausted. The user will need to

allocate more memory to the system.

DPSOL182

Error dip ddi_prop_create() failed returned:

DDI_PROP_INVAL_ARG

An invalid argument was sent to

ddi_prop_create(). The kernel may have
changed the interface to this function and the
driver will need to change.

DPSOL183

Error dip ddi_prop_create() failed returned:

unknown error

An unknown error was returned by

ddi_prop_create(). The kernel may have
changed the interface to this function and the
driver will need to change.
DynaPath User Guide

35

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL184

Cannot detach device dpd_ctrl (err=EBUSY).

Cannot unload dpdctrl device if other devices

are running.

DPSOL185

Exception: attempt to decrease usage count

below zero!

This is an internal error. The usage count was

reduced below zero for an object. This is
caused by a bug in the driver and the driver
will need to change.

DPSOL186

%d: error: path current priority value invalid

%d

This is an internal error. The priority value

was not set to a valid value. This is caused by
a bug in the driver and the driver will need to
change.

DPSOL187

%d: Event: path %d Path verification

success: Path has been restored to normal
status.

The device path transitioned from an error

state to a normal state. If this device
transitions from a bad state to a good state
rapidly. It may indicate a problem with the
storage.

DPSOL188

%d: Event: path %d Probe failure: Device

path test failed!

The device path transitioned from a proper

state to an error state. This will occur if there
is are storage port errors, medium errors,
fabric errors etc. This will also occur during a
storage server fail-over transition.

DPSOL189

%d: Event: path %d Device not available:

Cannot access underlying block device.

The SCSI block device returned the error

ENXIO.

DPSOL190

%d: Event: path %d I/O failure: Path returned

I/O error returned.

The device path transitioned to an error state.

This can be due to storage port errors,
medium errors, fabric errors, etc. This can
also occur during a storage server failover
transition.

DPSOL191

%d: Event: path %d I/O failure: Cannot

access underlying block device.

This is an internal error. The strategy routine

forwarded a buffer to a non existent block
device. The device driver will need to be
updated.

DPSOL192

dpd (spd_force_open): unexpected error

devstate pointer is NULL

This is an internal error. The function

spd_force_open was passed a null
parameter.

DPSOL193

Exception: invalid paramater passed into

spd_set_aa_preferred_path_status()!

This is an internal error. The function

spd_set_aa_preferred_path_status was
passed an invalid parameter.

DynaPath User Guide

36

DynaPath for Solaris

Error codes
Code

Text

Cause/resolution

DPSOL194

error: dpd%d:%d Invalid magic number

detected in cs_vpd_page: %x,%x

Any controller can use the inquiry page code

0xFA. We added a magic number in the
response to the page code to guarantee the
controller was presenting a FalconStor virtual
device. This error specifies that the device is
not really a FalconStor device and does not
support symmetric failover.

DPSOL195

Exception: invalid paramater passed into

spd_set_ctrl_mode()!

This is an internal error. The function

spd_set_ctrl_mode was passed an invalid
parameter.

DPSOL196

Exception: invalid data returned from VPD

page 0x00!

This error specifies that the device is not

really a FalconStor device and does not
support symmetric failover. This error can
also indicate a change in the VPD page 0xFA
on a CDP/NSS storage device. The device
driver may need be updated.

DPSOL197

Exception: spd_read_test rsp is NULL

This is an internal error. The function

spd_read_test was passed a null parameter.

DynaPath User Guide

37

DynaPath User Guide

DynaPath for AIX

Requirements
AIX requires approximately 285 KB for each storage path and DynaPath requires an
additional 15 KB of storage. Therefore, the system will require 300 KB for every
storage path. For example: If the system has 10 LUNs each with 4 paths, you will
need 12 MB of memory (10 x 4 x 300 KB = 12 MB).

Install DynaPath (updated June 2014)

Installation of DynaPath on AIX is managed by the SMIT software management
commands. This tool (the installp command) can be run either from the command
line or from a Graphical User Interface (GUI).
The following instructions illustrate using the command line. However, the same
tasks can be accomplished through the GUI. For more information on the GUI
alternative, consult your IBM-AIX documentation for installation details.
Note: If you are using FalconStor failover, read the section Enable Dynamic
Tracking and Fast FC error recovery.
Follow these steps to install the DynaPath driver and its supporting files.
1. Set up your system hardware.
2. Log in as root.
3. You need to install FalconStor Object Data Manager (ODM) fileset to recognize
devices provided by the storage server if it is not already installed. If you have
existing storage server devices, they must all be removed before the ODM
fileset is updated. Refer to Delete existing storage devices. Refer to Install
FalconStor ODM fileset for install information.
4. If a previous version of DynaPath is installed on your system, remove it and
reboot before continuing with this installation.
To determine if an older version of DynaPath is present on your system, examine
the output of the command:
# lslpp L|grep DynaPath

5. Assign devices from the storage server to the DynaPath client.

6. Verify that the client is able to see and access all storage devices through all
available paths. For example, If you have two paths to your storage system,
each logical drive should be displayed twice in the output of the command:
# lsdev Cc disk

If you cannot see all available storage devices through every path, verify that
you have the latest Fibre Channel HBA drivers loaded on your system.
DynaPath User Guide

38

DynaPath for AIX

7. Navigate to the temp directory (cd /tmp) and copy the DynaPath package to
/tmp.
8. Install DynaPath
# install -a -d pwd/DynaPath-<version number>.rte all
For example:
# install -a -d pwd/DynaPath-5.03.rte all
Note: Any time you re-assign SAN Resources to the same LUN, you must
reboot the AIX client after unassigning a SAN Resource.
Delete existing
storage devices

If you have existing storage server devices, they must all be removed before the
Object Data Manager (ODM) fileset is updated.
1. Use the following command to check if you have existing storage server devices.
# lscfg -v

You will see output similar to the following:

fscsi1 P1.1-I1/Q1 FC SCSI I/O Controller Protocol Device
hdisk1 P1.1-I1/Q1-W210000E08B058C20-L0 Other FC SCSI Disk Drive
Manufacturer................FALCON
Machine Type and Model......IPSTOR DISK
ROS Level and ID............76312E30
Device Specific.(Z0)........000003121F000032

hdisk2 P1.1-I1/Q1-W210000E08B07CEA7-L0 Other FC SCSI Disk Drive

Manufacturer................FALCON
Machine Type and Model......IPSTOR DISK
ROS Level and ID............76312E30
Serial Number...............8UYRRGUU
Device Specific.(Z0)........000002122F000032

This example illustrates that there are two storage server devices, hdisk1 and
hdisk2.
2. Remove each of the storage server devices:
The rmdev -l command closes the device and the rmdev -dl command
removes the device from ODM.
# rmdev -l hdisk1
# rmdev -dl hdisk1
# rmdev -l hdisk2
# rmdev -dl hdisk2

DynaPath User Guide

39

DynaPath for AIX

Install
FalconStor
ODM fileset

Object Data Manager (ODM) attributes 'reserve_lock' and 'reserve_policy' define

access to CDP/NSS disk devices and control the SCSI reservation behavior.
The ipstordisk.rte ODM file contains the following default values for SCSI
reservation attributes to open a CDP/NSS disk in exclusive mode in order to avoid
any accidental data corruption on disk devices that are shared across nodes/
systems:

'reserve_lock' = 'yes
'reserve_policy' = 'single_path'

The ipstordisk_ha.rte ODM file contains the following default values for SCSI
reservation attributes to open a CDP/NSS disk in non-exclusive mode, in order to
enable concurrent access of shared disk devices across the nodes/systems. This is
to be used in a high availability and dual VIOS configuration:

'reserve_lock' = 'no
'reserve_policy' = 'no_reserve'

To install:
1. Navigate to the temp directory (cd /tmp) and copy the ODM fileset to /tmp.
2. Unzip the appropriate ODMfileset for your environment:
For standalone or VIOS: ipstordisk.rte
For PowerHA or dual VIOS: ipstordisk_ha.rte
For example:
# gunzip -dc ipstordisk.tar.gz | tar -xvf -

3. Install the unzipped ODM fileset

# installp -ad ipstordisk.rte all

4. Rescan the configuration:

# cfgmgr -v

5. Verify the configuration:

# lsdev -Cc disk

The storage server disks that originally displayed the name Other FC SCSI
Disk Drive will now be displayed as FalconStor IPStor Disk Drive:
hdisk1 Available 04-08-01Falconstor IPStor Disk Drive
hdiskdpd0 AvailableDynaPath Multipath Device
hdiskdpdctrl AvailableDynaPath Multipath Device

DynaPath User Guide

40

DynaPath for AIX

Detect dynamic device (updated June 2014)

You may be able to add new storage devices and place them under DynaPath's
control without requiring a reboot of the client. This is also known as dynamic LUN
allocation.

Claiming new devices

To add a device to an existing path, perform the following steps after the devices are
physically connected, to detect defined devices.
1. Scan and load new devices into DynaPath:
# cfgmgr

2. Verify the new devices detected by AIX:

# lsdev Cc disk

3. Verify the new devices detected by DynaPath:

# dpcli status

4. If the new devices do not display, run one of the following commands:
If the device list is empty, run dpcli setup. If the device list is not empty, run
dpcli rescan to find the newly assigned devices.

Manage DynaPath
For information about DynaPath scripts and commands, refer to DynaPath
Operations.

Enable Dynamic Tracking and Fast FC error recovery

Dynamic Tracking allows DynaPath to detect certain device changes and then reroute traffic destined for that device to the new address while the device is still
online.
Fast FC error recovery allows a path to fail quickly. This is important for DynaPath
because it permits I/O to fail over to another path relatively quickly.
1. Before enabling FC error recovery and Dynamic Tracking you must remove all of
the sub devices beneath the FC adapter.
For example, if fscsi0 contains the devices hdisk3 and hdisk4, you must remove
the devices before enabling FC error recovery and Dynamic Tracking.
2. Turn on Dynamic Tracking and Fast FC error recovery for each initiator.
# chdev -l fscsix -a 'dyntrk=yes fc_err_recov=fast_fail' -P

DynaPath User Guide

41

DynaPath for AIX

where x represents the adapter instance number.

3. Reboot.
# shutdown -Fr

4. Verify that the appropriate attributes have been changed on each initiator.
# lsattr -E -l fscsix

Note: The chdev -P flag, changes the device characteristics permanently in the
Customized Devices object class. If the -P parameter is not used, dynamic
tracking will be reset back to the default value (which is disabled) after an AIX TL/
SP update or after the rmdev -dl fcs# -R; cfgmgr command is run.

Name DynaPath devices

Disk device filenames in AIX have names in the following format:
/dev/hdiskX
/dev/rhdiskX

where X = the controller instance number. A sample listing follows:

hdisk1 Available 30-60-00-0,0 Fibre Channel SCSI FCP Disk Drive
hdisk2 Available 30-60-00-1,0 Fibre Channel SCSI FCP Disk Drive
hdisk3 Available 30-78-00-0,0 Fibre Channel SCSI FCP Disk Drive
hdisk4 Available 30-78-00-1,0 Fibre Channel SCSI FCP Disk Drive

In a typical, single-path disk storage system, each physical disk is represented in the
clients /dev directory by two special device files representing the character and
block mode device instances. For simplicity, we reference the set of device files as a
single device filename and disregard the first part of the path names that distinguish
between raw and block modes.
As a layered driver, DynaPath creates its own device files for devices; it is through
these device filenames that applications access the underlying devices.
When multiple paths to a single device are present, multiple device files are present,
one for each path via the native disk driver. In these cases, DynaPath creates a
single additional device filename for applications to access the device and manages
the original device files transparently to those applications.
Starting with version 5.03, DynaPath is created as a new layered device driver and it
is presenting as a unique device instead of a native AIX device.
# lsdev -Cc disk
hdisk0

Available 04-08-01 FalconStor IPStor Disk Drive

hdisk1

Available 04-08-01 FalconStor IPStor Disk Drive

hdisk2

Available 04-08-01 FalconStor IPStor Disk Drive

hdisk3

Available 04-08-01 FalconStor IPStor Disk Drive

DynaPath User Guide

42

DynaPath for AIX

hdiskdpd0

Available

DynaPath Multipath Device

hdiskdpd1

Available

DynaPath Multipath Device

hdiskdpdctrl Available

DynaPath Multipath Device

Note: It is the virtual device file that will be used by applications to access that
device. The original, redundant data paths should never be used to access the
device, or the data it contains could be corrupted.

Configure AIX Fibre Boot

To set up an AIX Fibre Boot configuration, follow the steps below:
1. Verify DynaPath version 5.03 or higher and the proper ODM fileset are installed.
2. Make a backup copy of the system image and make sure the /tmp folder has
sufficient space to accommodate the bosboot image.
3. Scan for the boot disk if it has not yet been detected by DynaPath:
# dpcli rescan

4. List devices to identify the boot disk:

# lsvg -p rootvg

5. Identify the DynaPath device ID that corresponds to the boot disk:

# dpcli status

6. Configure the disk for Boot Mode using the DynaPath device ID:
# dpcli boot -b1 -l <boot disk's dpd_id>

7. Reboot.
Requirements

Once DynaPath is configured to manage the boot device, you must skip the bosboot
verification when installing third party software with the -b option.
#installp -b -ad <package_name>

all

If a system reboot is required for installing the third party software, use bosboot.dp to
take the system image before rebooting.
# bosboot.dp

-a

If you are using the mksysb command to backup and restore the fibre boot image,
you will need to use mksysb.dp instead of the native AIX mksysb command when
backing up the system image. The mksysb.dp is installed with DynaPath version
5.03 build 1028 or higher under /usr/bin/mksysb.dp. It is AIX version specific and
therefore, cannot be used on different AIX version.
To restore rootvg with multiple paths, follow the steps below:

DynaPath User Guide

43

DynaPath for AIX

1. On the FalconStor Management Console, modify LUNs that are part of rootvg to
one-to-one assignment (single path) before starting the restore process.
2. After restoration, login to the system and check the status using the dpcli status
command.
Only one of the paths for the moified devices will be in an available state.
3. On the FalconStor Management Console, modify LUNs that are part of rootvg
back to the original settings (mutiple paths).
4. Run the following commands on the AIX client:
# cfgmgr -p1
# dpcli start
# dpcli reset_device <device id>
The additional paths will display in a failure state until the reset_device
command is executed.
Note: .Do not run 'cfgmgr -p1' if the original paths are in a detached state.
For example:
id gid:pid
failback
1

0:1

device name

fscsi0::51a02/hdisk0

status

bal buf rtrcnt

detached

1:0

>fscsi0::51e02/hdisk1

1:2

fscsi1::51a02/hdisk2

detached

1:3

fscsi1::51e02/hdisk3

detached

dpd@1 = hdiskdpd1(started/open)
O7GBNXTL4KCH"

32

100

rtrdly
3000

available

SANID="FALCON IPSTOR DISK

If you only see a single path in the dpcli status, run 'cfgmgr -p1'.
For example:
id gid:pid
failback
1

1:0

device name

>fscsi0::51e02/hdisk1

dpd@1 = hdiskdpd1(started/open)
O7GBNXTL4KCH"

status
available

bal buf rtrcnt

1

32

100

rtrdly
3000

SANID="FALCON IPSTOR DISK

5. If the swap device is on a different physical volume (PV), you will need to
manually migrate the swap device to the original path.
For example:
# migratepv -l hd6 hdiskdpd0 hdiskdpd1

DynaPath User Guide

44

DynaPath for AIX

Disable Fibre Boot mode

To remove Fibre Boot disk management by DynaPath, follow the steps below:
1. Remove the boot mode option from the boot device:
# dpcli boot -b0 -l <boot disk's dpd_id>

2. Reboot.

Expand an AIX physical volume group

1. In the FalconStor Management Console, expand the SAN Resource that
corresponds to a physical volume in an AIX volume group.
For example, hdisk1 is a physical volume that maps to the virtual device
physical volume #1 on your storage server
2. Determine the DynaPath instance that is managing the physical device.
# dpcli status
===================================================================================
id gid:piddevice name status
bal
buf rtrcntrtrdly failback
===================================================================================
0 1:0fscsi0::692de8/hdisk1available 1
32 100 3000
1
dpd@0 = hdiskdpd1(started/open)
SANID="FALCON IPSTOR DISK Q30Y936S7Y3H"
===================================================================================

3. Update DynaPath device to recognize the new size:

# dpcli reset_device 0

4. Expand the volume group:

# chvg g testvg

DynaPath User Guide

45

DynaPath for AIX

Configure share mode

There may be situations where you need to enable share mode in a cluster
environment. For example: Both AIX-client hosts are in a cluster and share some
SAN resources. They are configured in CDP/NSS with Read/Write Non-Exclusive
access mode. However, to avoid jeopardizing data integrity, you may want to have
share mode disabled so that only one node is able to access a shared SAN
resource at a given time.
The share mode default value is set dynamically depending on the ODM installed on
the client. The share mode value is set to "1" when ipstordisk_ha.rte ODM is
installed. The share mode value is set to "0" when ipstordisk.rte ODM is installed.
To change the shared mode value:
1. Setup the shared volume group (VG) on all nodes using the DynaPath device
(hdiskdpd#).
2. Deactivate the shared VG.
# varyoffvg share_vg

3. Change the share_mode attribute.

# chdev -l hdiskdpd# -a share_mode=0 -P (to disable)
# chdev -l hdiskdpd# -a share_mode=1 -P (to enable)

4. Restart the dpd device.

# dpcli restart <dpd id>

5. Repeat the above steps on all nodes.

6. Verify the change by activating the share VG on the other nodes.
When share mode is disabled, an attempt to activate a locked VG will display a
message similar to the following:
0516-008 varyonvg: LVM system call returned an unknown
error code (3).

DynaPath User Guide

46

DynaPath for AIX

Release SCSI reservation

The following procedure describes how to release a SCSI reservation lock in a High
Availability Cluster Multi-Processing (HACMP) environment. This allows you to
bring an Extended Resource Group online on an available node of the cluster when
the original node is no longer accessible, and has left a SCSI reservation lock on the
shared disks.
This procedure must be applied only on the disks that are not currently in use by the
LVM sub-system, application or by another active node of the cluster. This
precaution is taken to avoid accidental loss of any active data traffic on the shared
disks.
Pre-operation
checklist
Post-operation
checklist

Make sure that shared disks do not have any active data traffic and check if the
shared disks are not accessible due to SCSI reservation conflict.
Make sure that the Extended Resource Group of the High Availability Cluster MultiProcessing (HACMP) cluster state is online and its Volume Group is varied on,
and its Logical Volumes are mounted and accessible.

Environment
The release SCSI reservation unlock procedure applies to the following
environment:

AIX HACMP cluster setup with two or more nodes.

HACMP cluster with an extended resource group having a Volume Group
(VG) with one or more Physical Volume (PV) disks.
HACMP cluster node with extended resource group made inaccessible/
crashed and resource group need to be brought online on a different node of
the cluster, using the procedure mentioned in this document.

Manual procedure
This procedure contains an example with the detailed steps on a cluster setup with
an extended resource group with a single PV disk VG.
1. Start a DynaPath instance on a different node of the cluster. If it fails to start,
release the SCSi reservation lock and start the DynaPath instance.
Use the following command to release the lock of the hard disk (any one disk/
path for the same LUN):
dpcli release_lock < disk id >
Use the following command to start the DynaPath for the disk:
dpcli start <dpdid >
2. Bring the extended resource group online on a different node of the cluster.

DynaPath User Guide

47

DynaPath for AIX

For example, use the smit command to bring the extended resource group
online on the available node of the cluster.
In the smit hacmp menu options, select the "Bring Resource Group Online"
option.
System Management (C-SPOC)-> HACMP Resource Group and Application
Management-> Bring a Resource Group Online

3. Use the following command to check whether the resource group is online:
# /usr/es/sbin/cluster/utilities/clRGinfo -m

Automated procedure
You can automatically release the SCSI reservation lock via HACMP Custom Disk
Method configuration.
1. Create Custom Disk Method on both nodes with the same value using the smit
hacmp command and selecting Add Custom Disk Methods. For example:
# smit hacmp
select Extended Configuration --> Extended Resource Configuration
--> HACMP Extended Resources Configuration --> Configure Custom
Disk Methods --> Add Custom Disk Methods
The Add Custom Disk Methods screen displays.

Enter the following information for each field:

Add Custom Disk Methods screen values
Field

Value

Disk Type (PdDvLn field from CuDv):

disk/pseudo/hdiskdpd

Method to identify ghost disks:

SCSI3

Method to determine if a reserve is held:

/sbin/dp_checkreserve.sh

Method to break a reserve:

/sbin/dp_breakreserve.sh

Break reserves in parallel:

Method to make the disk available:

false
MKDEV

DynaPath User Guide

48

DynaPath for AIX

Example 1

2. Verify and synchronize the configuration.

For example:
# smit hacmp
Select Extended Configuration --> Extended Verification and
Synchronization

The HACMP Verification and Synchronization screen displays.

Enter the following information for each field:
HACMP Verification and Synchronization screen values
Field

Value

Emulate or Actual:

Actual

Verify changes only?

No

Logging:

Standard

Example 2:

DynaPath User Guide

49

DynaPath for AIX

Switch between PVID and UDID for virtual SCSI disks

DynaPath supports switching between Physical Volume Identifier (PVID) and
Unique Device Identifier (UDID) methods of disk identification for virtual SCSI disks
in Virtual I/O servers. Only one method can be used per VIO server. PVID is the
default method. To convert from the PVID to the UDID method, follow the steps
below:
1. Backup the attached disks.
2. Stop all DynaPath services:
#dpcli stop all

3. Remove all DynaPath devices:

#dpcli remove all

4. Change to PVID or UDID:

#chdev -lhdiskdpdctrl -audid_enable=1 [enable to used UDID]
#chdev -lhdiskdpdctrl -audid_enable=0 [disable to used PVID]

5. Rescan and remap all devices.

DynaPath User Guide

50

DynaPath for AIX

Uninstall DynaPath (updated January 2014)

Remove
DynaPath 5.03

To remove DynaPath, enter the following command as root:

# installp -u DynaPath

Remove
DynaPath
prior to 5.03

To remove DynaPath, enter the following commands as root:

# dpcli stop
# dpcli remove-lall
# dynapath stop
# rmdev -d -l dpdctrl
# installp -u DynaPath

Remove the
FalconStor
ODM fileset

To remove the FalconStor ODM fileset:

1. Remove all previously detected storage server disks.
2. Uninstall the ODM fileset:
#installp -u ipstordisk

Error codes
The following table contains a description of some common error codes:.

Error codes
Code

Text

Cause/resolution

DPAIX101

could not allocate buf

ERRID_SPD_NOMEMORY

Failed xmalloc() memory exhausted.

DPAIX102

disk excluded by this host

ERRID_SPD_EXCLUDED

Device was started with exclusion flag enabled.

(This should not happen in dp 5.0, because dpcli
will refuse to start excluded devices

DPAIX103

use /usr/sbin/setsp to change exclusion

status
ERRID_SPD_UNEXCLUDE

Device was set to exclusion status

DPAIX104

dev %08x is a path of device (dpd%d).

ERRID_SPD_PATHREPEAT

Internal error, device is in use by another dpd_id.

DPAIX105

dev %08x is opened already.

hbadev=%08x.
ERRID_SPD_OPENEDPATH

Device is in use by another driver/application.

DPAIX106

device inquiry data mismatch--device

disabled. ERRID_SPD_UNMATCHED

Device inquiry does not match expected device

inquiry. This could be an error in DynaPath
configuration or the storage device could have
been replaced.
DynaPath User Guide

51

DynaPath for AIX

Error codes
Code

Text

Cause/resolution

DPAIX107

device inquiry data mismatch.

ERRID_SPD_UNMATCHED

Device inquiry does not match expected device

inquiry. This could be an error in DynaPath
configuration or the storage device could have
been replaced.

DPAIX108

Path failed READ test.

ERRID_SPD_INFO

Device failed verification. SCSI READ10

command failed. Device is marked as failed.

DPAIX109

no good paths found

ERRID_SPD_NOGOODPATH

All device paths are unavailable. DynaPath

cannot start in logical device in this condition.

DPAIX110

%d/%d paths operating at start.

ERRID_SPD_BADPATH

Notification that there is a failure with some of the

paths during the start-up process.

DPAIX111

can't detach: configured

ERRID_SPD_NODETACH .

Device is busy cannot stop it

DPAIX112

Error retry timeout! ERRID_SPD_INFO

Maximum number of retries for buffer occurred.

DPAIX113

path failover from%d to%d.

ERRID_SPD_FAILOVER

Path failover occurred. This occurs in response to

a path failure.

DPAIX114

%d path%d ok
ERRID_SPD_PATHOK

Path notification message. Path has recovered

from failure.

DPAIX115

%d path %d error
ERRID_SPD_PATHERR

Path notification message. Path error has

occurred.

DPAIX116

Inquiry mismatch! ERRID_SPD_INFO

Device inquiry does not match expected device

inquiry.

DPAIX117

Error: Could not obtain device capacity

from device path. ERRID_SPD_INFO

Failed to obtain block device capacity though

IOCINFO ioctl.

DynaPath User Guide

52

DynaPath User Guide

DynaPath for Linux

Requirements
Native Linux DM-Multipath is recommended for Linux systems. If no version of
FalconStor DynaPath exists for your Linux kernel, you must use Linux DMMultipath. The Linux DM-Multipath Software and Best Practice Guide can be
downloaded from the FalconStor Customer Support Portal at
support.falconstor.com.

Install DynaPath
Follow these steps to install DynaPath:
1. Set up your system hardware.
2. Log in as root.
3. If a previous version of DynaPath is installed on your system, remove it and
reboot before continuing with this installation.
4. Assign devices from the storage server to the DynaPath client.
5. Verify that the client is able to see and access all storage devices through all
available paths. For example, If you have two paths to your storage system,
each logical drive should be displayed twice in the output of the command:
#cat /proc/scsi/scsi:

If you cannot see all available storage devices through every path, verify that
you have the latest Fibre Channel HBA drivers loaded on your system.
6. If a previous version of DynaPath is installed on your system, remove it before
continuing with this installation.
7. Install DynaPath:
# rpm -ivh dynapath-5.01-xxx.i586.rpm:

8. Start DynaPath:
# dynapath start

9. Run initial setup to create a new configuration file and detect existing devices:
# dpcli setup

DynaPath User Guide

53

DynaPath for Linux

Detect dynamic devices

Perform a rescan to detect new devices. Refer to your HBA vendor documentation
for details.

Manage DynaPath
For information about DynaPath scripts and commands, refer to DynaPath
Operations.

Configure HBA settings

The following table lists the settings for each type of HBA. Refer to the certification
matrix on the FalconStor website for additional support information.
HBA Card Type

HBA Settings

QLogic

Login Retry Count = 8

Port Down Retry Count = 8
Link Down Count = 30
Enable Target Reset = True
FrameSize = 2048
Execution Throttle = 32
LUNS per target = 256
Tape mode = Disable

Emulex

Node Timeout = 30
Link Timeout = 30

DynaPath User Guide

54

DynaPath for Linux

Configure DynaPath for the Logical Volume Manager

You will need to modify the default lvm.conf file if you are using a Linux Logical
Volume Manger (LVM2) with DynaPath. The default file only recognizes sd devices.
Since DynaPath devices are dpd devices, you need to modify the conf file so LVM
can recognize only dpd devices.
1. Edit the file /etc/lvm/lvm.conf.
2. Do not accept every block device:
In the following section:
# By default we accept every block device:

Comment out the following line:

filter = [ "a/.*/" ]

3. Include dpd devices and exclude other devices:

Below the following section:
# Exclude the cdrom drive
# filter = [ "r|/dev/cdrom|" ]

Add the following line:

filter = [ "a|/dev/dpd[a-z]|", "r|.*|" ]

a = makes the device available for rescanning

r = restricts the device from being able to be scanned
4. Allow LVM to recognize the dpd device driver.
Below the following section:
# List of pairs of additional acceptable block device types found
# in /proc/devices with maximum (non-zero) number of partitions.
# types = [ "fd", x ]

Add the following line:

types = [ "dpd", x ]

Where x is the number of partitions desired.

5. Save your changes and close the file.
6. Scan devices:
# vgscan

DynaPath User Guide

55

DynaPath for Linux

Create logical volumes and groups using DynaPath devices

To configure LVM on the Fibre Channel disks that are under DynaPaths control you
can follow the steps as described by the example below. Refer to your LVM
documentation for more details.
1. Create physical volumes from DynaPath controlled devices using the pvcreate
command.
For example:
pvcreate /dev/dpda
pvcreate /dev/dpdb

2. Create a volume group using the vgcreate command.

For example:
vgcreate my_volume_group /dev/dpda /dev/dpdb

3. Verify the volume group using the vgdisplay command.

4. Create a logical volume group using the lvcreate command.
For example:
lvcreate -L1G -nmy_logical_volume my_volume_group

5. Create a filesystem on the logical volume using the mke2fs command.

For example:
mke2fs /dev/my_volume_group/my_logical_volume

Uninstall DynaPath
To uninstall DynaPath, enter the following commands as root:
1. Stop DynaPath and then verify that the devices are stopped:
# dpcli stop

2. Uninstall the DynaPath package:

# rpm -e dynapath

DynaPath User Guide

56

DynaPath for Linux

Error codes
The following table contains a description of some common error codes:

Error codes
Code

Text

Cause/resolution

DPLNX101

dpd_init: no more major numbers

available

Linux kernel was unable to register block device to

kernel. DynaPath driver name may already be in use,
or optional hard-coded major number may already be
in use.

DPLNX102

dpd_init: failed to allocate control

device state

Memory exhausted. Allocate more memory to the

system.

DPLNX103

dpd_init: failed to initialize control

device

This is an internal error. DynaPath could not initialize

control instance. Device driver will need to be
debugged

DPLNX104

dpd_init: failed to spin off kdpdsync

thread

This is a kernel error. DynaPath could not register the

kernel thread kdpdsync. The kernel thread creation
function may have changed, the driver will need to be
changed.

DPLNX105

dpd_init: failed to spin off kdpdtest

thread

This is a kernel error. DynaPath could not register the

kernel thread kdpdtest. The kernel thread creation
function may have changed, the driver will need to be
changed.

DPLNX106

dpd_construct_dsp: cannot create

buffer memory pool.

Memory exhausted. Allocate more memory to the

system.

DPLNX107

dpd_construct_dsp: cannot allocate

generic disk structure.

Memory exhausted. Allocate more memory to the

system.

DPLNX108

dpd_destruct_dsp: error <NULL> dsp

parameter

This is an internal error. The driver called

dpd_destruct_dsp with a null parameter.

DPLNX109

device open failed.dpd device is

deleted

This is an internal/kernel error. The block device

inode does not contain the dsp structure in the
private_data member. The driver will need to be
debugged.

DPLNX110

dpd_ioctl: cannot set load balance for

device %d.reason no such device

Application attempted to set load balance attribute for

a non-existent device. This may indicate an error in
the configuration.

DPLNX111

dpd_ioctl: cannot stop (id = %d) reason no such device

Application attempted to shut down a non-existent

device. This may indicate an error in the
configuration.

DynaPath User Guide

57

DynaPath for Linux

Error codes
Code

Text

Cause/resolution

DPLNX112

dpd_ioctl: cannot stop (id = %d) reason device busy (refs=%d)

Application attempted to shut down a busy device.

The admin needs to unmount any file system or
shutdown any application referencing the block
device. Admin can use fuser to determine the pid
using the block device.

DPLNX113

dpd_ioctl: unexpected error ds_map is

NULL

This is an internal error. The DynaPath device state

map is not allocated. The driver will need to be
debugged.

DPLNX114

dpd_make_request: cannot perform I/O

to offlined device

Buffer was sent to an device in the offline state.

DPLNX115

dpd_make_request: error cannot

perform I/O on a control device

An I/O request was sent to the driver control device.

The control device will reject this buffer request.

DPLNX116

dpd_make_request: unexpected error

could not allocate buffer; ending I/O

Failure to allocate a buffer from the memory pool.

DPLNX117

dpd_make_request: unexpected error

could not allocate buffer from
bh_mem_pool

Failure to allocate a buffer from the memory pool.

DPLNX118

dpd_consolidate_disk: failed to allocate

device state for control device

Memory exhausted. Allocate more memory to the

system.

DPLNX119

dpd_consolidate_disk: failed to initialize

device dpd_id=%d

Driver failed to consolidate disk. The cause of the

error will be reported before this message.

DPLNX120

dpd_consolidate_disk: error cannot

allocate path buffer.

Memory exhausted. Allocate more memory to the

system.

DPLNX121

dpd_consolidate_disk: error could not

open device (%d,%d)

Failure to open SCSI disk device. The error will be

returned to the application. There may be an error
with the configuration. The device may be in an error
state in which it cannot be opened.

DPLNX122

dpd_consolidate_disk: error could not

exclusive open device %s

Failure to exclusively claim a SCSI disk device. The

device may be exclusively claimed by another driver.

DPLNX123

dpd_get_instance: unexpected error

ds_map is NULL

This is an internal error. The DynaPath device state

map is not allocated. The driver will need to be
debugged.

DPLNX124

dpd_dbg_dump_ds_map: unexpected
error ds_map is NULL

This is an internal error. The DynaPathdevice state

map is not allocated. The driver will need to be
debugged.

DPLNX125

dpd_dec_path_use unexpected error

cannot decrease path <%s> reference
counter

This is an internal error. The usage count was

reduced below zero for an object. This is caused by a
bug in the driver and the driver will need to change.

DynaPath User Guide

58

DynaPath for Linux

Error codes
Code

Text

Cause/resolution

DPLNX126

dpd_dec_ds_use unexpected error

cannot decrease path <%s> reference
counter

This is an internal error. The usage count was

reduced below zero for an object. This is caused by a
bug in the driver and the driver will need to change.

DPLNX127

Change path from AVAILABLE to

UNAVAILABLE for reason:%s

The device path transitioned from a proper state to an

error state. This will occur if there is are storage port
errors, medium errors, fabric errors etc. This will also
occur during a storage server fail-over transition.

DPLNX128

Change path from UNAVAILABLE to

AVAILABLE for reason:%s

The device path transitioned from an error state to a

normal state. If this device transitions from a bad
state to a good state rapidly. It may indicate a
problem with the storage.

DPLNX129

dpd_test_path: error could not

exclusive open device %s

Failure to exclusively claim a SCSI disk device. The

device may be exclusively claimed by another driver.

DPLNX130

dpd_test_path: INQUIRY mismatch for

%d:%d:%d:%d.

The SANID obtained from the logical unit does not

match the expected SANID. The logical unit may
have changed upstream or there may be a
configurationerror. Use dpcli clean and dpcli rescan
commands to resolve this problem.

DPLNX131

Exception: invalid data returned from

VPD page 0x00!%d.%d.%d.%d

This error specifies that the device is not really a

FalconStor device and does not support symmetric
failover. This error can also indicate a change in the
VPD page 0xFA on a CDP/NSS storage device. The
device driver may need be updated.

DPLNX132

error: invalid magic number detected in

cs_vpd_page: %x,%x for
%d.%d.%d.%d

Any controller can use the inquiry page code 0xFA.

We added a magic number in the response to the
page code to guarantee the controller was presenting
a FalconStor virtual device. This error specifies that
the device is not really a FalconStor device and does
not support symmetric failover.

DPLNX133

failed to get vpd data for %d.%d.%d.%d

Driver failed to obtain 0xFA FalconStor vpd data. The

version of CDP/NSS may be too old to support 0xFA,
or the 0xFA code page was not registered on the
storage server.

DPLNX134

dpd_test_paths: offlining device

dpd_id=%ld

SANID mismatch was detected. The device is turned

offline to prevent data corruption. The device will
revert to online if the proper device is restored. Use
dpcli clean and dpcli rescan to fix this problem.

DPLNX135

dpd_test_paths: path test failed reason: adapter is in RECOVERY

MODE

The adapter is in error recovery mode. I/O cannot be

issued to adapter when it is in this state. DynaPath
will automatically assume the device is offline.

DynaPath User Guide

59

DynaPath for Linux

Error codes
Code

Text

Cause/resolution

DPLNX136

dpd_test_paths: path test failed reason: HBA (%d) returned %lx

The device path transitioned from a proper state to an

error state. This will occur if there are storage port
errors, medium errors, fabric errors etc. This will also
occur during a storage server fail-over transition.

DPLNX137

exception: invalid parameter for %s inq

<%p> inqbuf <%p> len (min = 48) %d

Invalid parameter was sent to

dpd_parse_standard_inquiry(). The driver will need to
be debugged.

DPLNX138

error: vrscsi table is NULL

This is an internal error. VRSCSI table was not

initialized when sync_vrscsi() was called. The driver
will need to be debugged.

thread->tsk == NULL

This is an internal error. DynaPath's task thread was

not initialized

DPLNX139

%d: path %d error (%s)

The device path transitioned from a proper state to an

error state. This will occur if there is are storage port
errors, medium errors, fabric errors etc. This will also
occur during a storage server fail-over transition.

DPLNX140

%d: path failover from %d to %d.

The buffer was retried on the next path. This occurs

after a path failure. This can also occur when no load
balancing disabled and the primary path transitions
from and error state to a proper state.

DPLNX141

Error: memory exhausted in function

%s

Memory exhausted. Allocate more memory to the

system.

DPLNX142

make_request: i/o error,device

excluded

A buffer request was issued to a DynaPath device

that is exclusive. This should never occur, because
dpcli will not activate an excluded device.

DPLNX143

out of memory in sp_make_request(),

retry...

Memory exhausted. Allocate more memory to the

system.

DPLNX144

Error device instance (%d) dev

(%d,%d) error. Failing instance.

The device does not exist, there is a SANID

mismatch, or DynaPath is unable to obtain the
SANID of the device.

DPLNX145

%d: can't stop: device opened

The DynaPath device is busy. It is being used by an

application or another driver/subsystem.

DPLNX146

%d: can't stop: probe or retried i/o in

progress

The DynaPath device is busy. It is being used by an

application or another driver/subsystem.

DPLNX147

device inquiry data mismatch--device

warning!

The SANID obtained from the logical unit does not

match the expected SANID. The logical unit may
have changed upstream or there may be an error
with the configuration. Use dpcli clean and dpcli
rescan to fix this problem.

DynaPath User Guide

60

DynaPath for Linux

Error codes
Code

Text

Cause/resolution

DPLNX148

%d: can't revalidate: device opened.

Device partition revalidation failed, because the

device was in use by an application or another driver/
subsystem.

DPLNX149

%d: can't revalidate: device excluded.

Device partition revalidation failed, because the

device is excluded. This should not occur since dpcli
does not start excluded devices.

DPLNX150

%d (%s%d) retry timeout

unrecoverable I/O error, rsector=%lu
r=%d rc=%d rd=%d d=%d f=%d.

A retried buffer expired due to a timeout. This is due

to a storage upstream error. The application will be
notified that an error occured.

DPLNX151

%d path %d(%s) size=0.

The logical unit has a block size of zero. This can be

due to a storage error, or this can be an error in the
mapping of the logical device path due to changes in
the kernel structure.

DPLNX152

%d: can't get data of partitions.

Device inquiry does not match expected device

inquiry. This can indicate a configuration error.

DPLNX153

no argument specified

An invalid argument was specified to DynaPath ioctl.

There is an error in the DynaPath application.

DPLNX154

cannot add devices to supported device

table

The maximum amount of device entries was reached

in the supported device table.

DPLNX155

error: %08x,%d

This is an internal error. DynaPath attempted to

forward a IOCTL to non-existent device.

DPLNX156

do_sp_request() is called. Impossible

thing!

This is an internal error. This occurs when DynaPath

is compiled for the Linux 2.2 kernel. Linux 2.2 is
unsupported by this driver.

DPLNX157

error: memory exhausted

Memory exhausted. Allocate more memory to the

system.

DPLNX158

Warning : Can't get scsi disk's address!

Driver is unable to obtain the SCSI gendisk structure

from the kernel. The modules scsi.o or sd.o may not
be loaded.

DPLNX159

cannot register spd device, major=%d.

err=%d

The driver failed to register the DynaPath block

device. This can be caused by a conflict with the
DynaPath major device number.

DPLNX160

cannot register spd ctrl node,

major=%d.

The driver failed to register the DynaPath control

device. This can be caused by a conflict with the
DynaPath major device number

.DPLNX161

%d : cannot exclude an opened device.

The exclusion option was set for a device that is in

use by an application or driver. This is an error with
the configuration.

DynaPath User Guide

61

DynaPath for Linux

Error codes
Code

Text

Cause/resolution

DPLNX162

error: cannot obtain inquiry for device

dpd=%d:%d

The INQUIRY command failed. This can indicate an

error with the storage.

DPLNX163

inquiry mismatch %s %s

The SANID obtained from the logical unit does not

match the expected SANID. The logical unit may
have changed upstream or there may be an error
with the configuration. Use dpcli clean and dpcli
rescan to fix this problem.

DPLNX164

Retry queue dosn't clean!

The DynaPath failed to unload, because there are

buffers in the retry queue. Wait until the retry buffers
expires before unloading the driver.

DPLNX165

Unable to unregistor major %d for sp

This is a kernel error. DynaPath was unable to

unregister the block device from the kernel. This can
indicate corruption in a kernel data structure.

DPLNX166

%d: error: path current priority value

invalid %d

This is an internal error. The priority value was not set

to a valid value. This is caused by a bug in the driver
and the driver will need to change.

DPLNX167

error: NULL command string

This is an internal error. An invalid argument was

sent to spd_GetCustomInquiry().

DPLNX168

error: invalid inquiry SCSI command

specified CDB:%s

The command string is not an INQUIRY command.

DPLNX169

Exception: invalid paramater passed

into spd_set_ctrl_mode()!

This is an internal error. An invalid argument was

sent to spd_set_ctrl_mode().

DPLNX170

Error: memory exhausted!

Memory exhausted. Allocate more memory.

DPLNX171

Exception: invalid data returned from

VPD page 0x00!

This error specifies that the device is not really a

FalconStor device and does not support symmetric
failover. This error can also indicate a change in the
VPD page 0xFA on a CDP/NSS storage device. The
device driver may need be updated.

DPLNX172

Exception: invalid paramater passed

into
spd_set_aa_preferred_path_status()

This is an internal error. The function

spd_set_aa_preferred_path_status was passed an
invalid parameter.

DPLNX173

Error: dpd%d:%d Invalid magic number

detected in cs_vpd_page: %x,%x

Any controller can use the inquiry page code 0xFA.

We added a magic number in the response to the
page code to guarantee the controller was presenting
a FalconStor virtual device. This error specifies that
the device is not really a FalconStor device and does
not support symmetric failover.

DPLNX174

Error: memory exhausted in function

%s

Memory exhausted. Allocate more memory to the

system.

DynaPath User Guide

62

DynaPath User Guide

DynaPath Operations
This section describes how to manage DynaPath on Solaris, AIX, and Linux.

DynaPath script
The DynaPath script allows you to:

Usage

Start, stop, and restart DynaPath driver

Display status information
Take a system X-ray for diagnostic purposes

dynapath <option>

Option

Description

start

Loads the DynaPath driver. Displays OK or FAILURE.

OK: Driver loaded properly.
FAILURE: Driver could not be loaded properly.

stop

Unloads the DynaPath driver. Displays OK or FAILURE.

OK: Driver unloaded properly.
FAILURE: Driver could not be unloaded properly.

restart

Unloads and then loads the DynaPath driver. Displays OK or FAILURE.

OK: Driver loaded/unloaded properly.
FAILURE: Driver could not be loaded/unloaded properly.

status

Shows the status of DynaPath driver. Displays RUNNING or STOPPED.

RUNNING: Driver is loaded.
STOPPED: Driver is unloaded.

xray

Obtains a snapshot of the system state, as well as configuration files. The

X-ray is saved to /var/tmp/dp2-configuration-<timestamp>.tar.Z

DynaPath User Guide

63

DynaPath Operations

Manage DynaPath devices

While DynaPath is automatically configured for you, there may be times that you
need to modify the configuration. You can use the command line interface to
manage DynaPath devices.
Usage

To run a command:
dpcli <command> <parameters>

Note that any command can be combined with verbose mode (-v) for detailed
information.
To see onscreen help for a command:
dpcli [help] [<command>]

Key terms
Variable

Description

dpd_id

DynaPath block device instance number

controller

cX (e.g. c0 as in: /dev/dsk/c0t0d0s2)

device

a full or partial disk name (i.e. c0t0, c0t0d0)

SANID

a unique storage device identifier. (i.e. "FALCON IPSTOR DISK

BF8YHNFKQQX0")

pid

(path id) id representing a unique data path to storage device.

gid

(group id) id representing a group of pids (group id=0 is the spare

group)

DynaPath User Guide

64

DynaPath Operations

Commands
Start/stop devices
Task

Command

Description

Attach and activate

devices

start [<dpd_id>|all]

The start command loads DynaPath and makes

DynaPath devices active. If the start command
detects that there is no configuration, a
recommendation, such as performing the rescan
command, is given.

Detach devices

stop [<dpd_id>|all]

The stop command deactivates DynaPath

devices.

Stop and start devices

restart [<dpd_id>|all]

The restart command stops and then starts

DynaPath.

Display device status

Task
Status

Command
status [<options>]

Options:
l<dpd_id>|all
e<0|1>
s<0|1>
f<0|1>
r<0|1>

Description
The status command displays DynaPath device
information and/or configuration.
For devices that are already started, it displays both
including the current status. For devices that are
not started (i.e. devices newly discovered by the
rescan command), it displays the current
configuration settings.
You can use status options to set filters for the
status display:
Use the -e option to display included (0) /
excluded (1) devices.
Use the -s option to display stopped (0) / started
(1) devices.
Use the -f option to display devices in a failed
state.
Use the -r option to display devices that are
reserved.
Note: Some of the configuration commands do not
become effective until the DynaPath device is
restarted (i.e. the set n <nbuf> command). If
you havent restarted the device, the configuration
changes will not be displayed in the status.

DynaPath User Guide

65

DynaPath Operations

Rescan devices
Task
Rescan

Command

Description

rescan <options> [<dpd_id>|all]

The rescan command discovers and

adds new devices or paths.
After running rescan to detect new
devices, you must run dpcli start to
activate the new devices.
The rescan f command wipes out the
existing configuration and generates a
new one. It is the same as the setup
command.
In preview (-p) mode, DynaPath
performs the operation without
committing any of the changes.

Options:
-p
-f

Rescan devices and

rebuild configuration

setup

The setup command rescans devices

and generates a new configuration. It is
the same as the rescan f command.

Ignore controllers /
devices

ignore <controller>|<device>

The ignore command sets filters for the

rescan command. It adds devices to be
ignored to the configuration. It only affects
future rescan commands. If a device is
already started, the ignore command
would not affect it.
Use the -a option to add devices to the
ignore list.
Use the -l option to display a list of
currently ignored devices.

Options:
-a
-l

Un-ignore controllers /
devices

ignore -d
<controller>|<device>

This command removes devices that

were being ignored from the configuration

Clean up unavailable
devices

clean <options> [<dpd_id>|all]

The clean command cleans up any

orphan devices that are no longer
available to the system. It searches and
removes the invalid entries from the
configuration.
In preview (-p) mode, DynaPath
performs the operation without
committing any of the changes.
For detailed information (such as why
DynaPath is or isnt consolidating a
device), combine with the verbose (-v)
mode.

Option:
-p

DynaPath User Guide

66

DynaPath Operations

Configure devices
Task
Configure
devices

Command
set <options> <dpd_id>|all

Options:
b<0|1>
r<retrycount>
d<retrydelay>
e<0|1>
n<nbuf>
p<path id>
f<0|1>

Boot pseudo
devices

boot [<dpd_id>|all]

Option:
b<0|1>
Remove from
the configuration

remove l<dpd_id>|all

Option:
-i <dpd_id>
-a <adapter controller id>
-p <path_id>

Description
The set command configures DynaPath devices and
saves the changes into the configuration.
Use the -b option to set load balancing. The
default is 0 (off).
Use the -r option* to set the retry count. The
default is 100.
Use the -d option* to set the retry delay. The
default is 3000 ms.
Use the -e option to exclude this device from
DynaPaths use. The default is 0 (device will not be
excluded).
Use the n<nbuf> option* to set the number of
buffers. The default is 32. Configuration changes
made with the n option will not become effective
until the DynaPath device is restarted.
Use the -p option* to configure the primary path. If
load balancing is disabled, DynaPath will utilize
this path.
Use the -f option* to set auto-failback. The default
is 1.
* These options are not available for Linux.
(Solaris and AIX only) The boot command
configures the boot option for a pseudo device.
Use the -b option to set the boot mode on (1) or off
(0, which is the default setting).
The remove command removes a DynaPath device
from the configuration until you run a rescan. You
must stop the device before removing it. Use the
ignore option to permanently remove a device.
Use the -i <dpd_id> option to ignore all devices
within the same unique identifier.
Use the -a <adapter controller id> option to
remove the adapter controller.
Use the -p <path_id> option to remove the data
path.

Allow AIX
volume
expansion

reset_device

(AIX only) The reset_device command allows you to

update a DynaPath device after it has been
expanded on the storage server.

Share

share[<dpd_id>|all

Option:
-c<0|1>

(AIX only) Special mode to support share properties

of a device. Use the -c option to set share on (1) or
off (0). Default setting =0.

release_lock<device_name>

(AIX only) Release SCSI reservation on a device.

Release lock

DynaPath User Guide

67

DynaPath User Guide

Index
A
AIX 38
Claiming new devices 41
Client
SAN Resource re-assignment 39
Device naming 42
Dynamic device detection 41
Dynamic Tracking 41
Expand physical volume group 45
Fast FC error recovery 41
Installation 38
Logical Volume Manager 41
Uninstall 51

Linux 53
Solaris 25
Windows Server 2003 19
Windows Server 2008 12
Windows Server 2012 5
installp command 38

L
Linux 53
Installation 53
Logical Volume Manager 55
Uninstall 56
Logical Volume Manager 41

Command line interface 64

Configure devices 67
Customize registry settings 23

Manage devices 64
mksysb command 43
MPIO parameters 23

Device naming
AIX 42
Device status 65
dynacfg 22
dynacfg utility 21
Dynamic device detection
AIX 41
Dynamic Tracking 41
DynaPath 1
How it works 1
Introduction 1
Operation 63
Script 63
DynaPath for Windows 2003 18
DynaPath for Windows 2008 11
DynaPath for Windows 2012 4

Overview
DynaPath 1

F
Fast FC error recovery 41

P
Persistent binding 2

Q
QLogic
HBA 2

R
Rescan devices 66

S
Script 63
Solaris 25
Installation 25
Uninstall 29
Start/stop devices 65

HACMP 47
Hardware preparation 2

Timer Counters 6, 13

Uninstall
AIX 51

Installation
AIX 38

DynaPath User Guide

68

Index

Linux 56
Solaris 29

V
Virtual I/O (VIO) 40

W
Windows Server 2003
Assigning new devices 20
Installation 19
Microsoft Cluster 22
Uninstall DynaPath 24
Windows Server 2008
Assigning new devices 13
Cluster configuration for DynaPath 15
Installation 12
Uninstall DynaPath 17
Windows Server 2012
Assigning new devices 6
Cluster configuration for DynaPath 8
Installation 5
Uninstall DynaPath 10

X
Xray 63

DynaPath User Guide

69