Professional Documents
Culture Documents
USER GUIDE
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.
10614
Contents
Introduction
Hardware preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
HBA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Additional resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3
Contents
DynaPath Operations
DynaPath script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Manage DynaPath devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64
Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65
Index
ii
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
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.
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.
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.
HBA Settings
QLogic
Emulex
Node Timeout = 30
Link Timeout = 30
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
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.
The parameters are described in the table below. All settings on this screen will
be carried over to the other disk
Parameter
Description
PDORemovePeriod
RetryCount
RetryInterval
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.
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).
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.
10
HBA Settings
QLogic
Emulex
Node Timeout = 30
Link Timeout = 30
11
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
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.
13
The parameters are described in the table below. All settings on this screen will
be carried over to the other disk
Parameter
Description
PDORemovePeriod
RetryCount
RetryInterval
14
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.
15
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).
16
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.
17
HBA Settings
QLogic
Emulex
Node Timeout = 30
Link Timeout = 30
18
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:
19
20
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
-s spd_id
-e a c s l
-i a c s l
-u spd_id retrydelay
retrycount loadbalance
-d, -m, -t
-x
Examples
List all groups
F:>dynacfg -l
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.
21
Display path
status
F:>dynacfg -s spd_id
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
22
Customize
registry settings
Setting
Description
PDORemovePeriod
300
RetryCount
100
RetryInterval
23
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.
24
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>
9. Run initial setup to create a new configuration file and detect existing devices:
# dpcli setup
25
Manage DynaPath
For information about DynaPath scripts and commands, refer to DynaPath
Operations.
26
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>
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.
27
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";
28
HBA Settings
QLogic
Emulex
Node Timeout = 30
Link Timeout = 30
Uninstall DynaPath
In order to remove DynaPath, enter the following command as root:
# pkgrm dynapath
29
Error codes
The following table contains a description of some common error codes:.
Error codes
Code
Text
Cause/resolution
DPSOL101
DPSOL102
DPSOL103
scsi_hba_tran_alloc failed
DPSOL104
scsi_hba_attach failed
DPSOL105
DPSOL106
DPSOL107
_scsi_destroy_pkt
DPSOL108
_scsi_dmafree
DPSOL109
DPSOL110
DPSOL112
DPSOL113
PSOL114
DPSOL115
30
Error codes
Code
Text
Cause/resolution
DPSOL116
DPSOL117
DPSOL118
DPSOL119
DPSOL120
DPSOL121
DPSOL122
DPSOL123
DPSOL124
DPSOL125
DPSOL126
DPSOL127
DPSOL128
DPSOL129
DPSOL130
31
Error codes
Code
Text
Cause/resolution
DPSOL131
DPSOL132
DPSOL133
DPSOL134
DPSOL135
DPSOL136
DPSOL137
DPSOL138
DPSOL139
DPSOL140
DPSOL141
DPSOL142
32
Error codes
Code
Text
Cause/resolution
DPSOL143
DPSOL144
DPSOL145
DPSOL146
DPSOL147
DPSOL148
DPSOL149
DPSOL150
DPSOL151
DPSOL152
DPSOL153
DPSOL154
DPSOL155
DPSOL156
DPSOL157
33
Error codes
Code
Text
Cause/resolution
DPSOL158
DPSOL159
DPSOL160
DPSOL161
DPSOL162
DPSOL163
DPSOL164
DPSOL165
DPSOL166
DPSOL167
DPSOL168
DPSOL169
DPSOL170
DPSOL171
DPSOL172
34
Error codes
Code
Text
Cause/resolution
DPSOL173
DPSOL174
DPSOL175
DPSOL176
DPSOL177
DPSOL178
DPSOL179
DPSOL180
Invalid dpd_id %d
DPSOL181
DPSOL182
DPSOL183
35
Error codes
Code
Text
Cause/resolution
DPSOL184
DPSOL185
DPSOL186
DPSOL187
DPSOL188
DPSOL189
DPSOL190
DPSOL191
DPSOL192
DPSOL193
36
Error codes
Code
Text
Cause/resolution
DPSOL194
DPSOL195
DPSOL196
DPSOL197
37
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
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
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
39
Install
FalconStor
ODM fileset
'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 -
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
40
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.
41
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.
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
hdisk1
hdisk2
hdisk3
42
Available
hdiskdpd1
Available
hdiskdpdctrl Available
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.
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:
43
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
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
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
32
100
rtrdly
3000
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
44
2. Reboot.
45
46
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:
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.
47
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.
Value
disk/pseudo/hdiskdpd
SCSI3
/sbin/dp_checkreserve.sh
/sbin/dp_breakreserve.sh
false
MKDEV
48
Value
Emulate or Actual:
Actual
No
Logging:
Standard
Example 2:
49
50
Remove
DynaPath
prior to 5.03
Remove the
FalconStor
ODM fileset
Error codes
The following table contains a description of some common error codes:.
Error codes
Code
Text
Cause/resolution
DPAIX101
DPAIX102
DPAIX103
DPAIX104
DPAIX105
DPAIX106
51
Error codes
Code
Text
Cause/resolution
DPAIX107
DPAIX108
DPAIX109
DPAIX110
DPAIX111
DPAIX112
DPAIX113
DPAIX114
%d path%d ok
ERRID_SPD_PATHOK
DPAIX115
%d path %d error
ERRID_SPD_PATHERR
DPAIX116
DPAIX117
52
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
53
Manage DynaPath
For information about DynaPath scripts and commands, refer to DynaPath
Operations.
HBA Settings
QLogic
Emulex
Node Timeout = 30
Link Timeout = 30
54
55
Uninstall DynaPath
To uninstall DynaPath, enter the following commands as root:
1. Stop DynaPath and then verify that the devices are stopped:
# dpcli stop
56
Error codes
The following table contains a description of some common error codes:
Error codes
Code
Text
Cause/resolution
DPLNX101
DPLNX102
DPLNX103
DPLNX104
DPLNX105
DPLNX106
DPLNX107
DPLNX108
DPLNX109
DPLNX110
DPLNX111
57
Error codes
Code
Text
Cause/resolution
DPLNX112
DPLNX113
DPLNX114
DPLNX115
DPLNX116
DPLNX117
DPLNX118
DPLNX119
DPLNX120
DPLNX121
DPLNX122
DPLNX123
DPLNX124
dpd_dbg_dump_ds_map: unexpected
error ds_map is NULL
DPLNX125
58
Error codes
Code
Text
Cause/resolution
DPLNX126
DPLNX127
DPLNX128
DPLNX129
DPLNX130
DPLNX131
DPLNX132
DPLNX133
DPLNX134
DPLNX135
59
Error codes
Code
Text
Cause/resolution
DPLNX136
DPLNX137
DPLNX138
thread->tsk == NULL
DPLNX139
DPLNX140
DPLNX141
DPLNX142
DPLNX143
DPLNX144
DPLNX145
DPLNX146
DPLNX147
60
Error codes
Code
Text
Cause/resolution
DPLNX148
DPLNX149
DPLNX150
DPLNX151
DPLNX152
DPLNX153
no argument specified
DPLNX154
DPLNX155
error: %08x,%d
DPLNX156
DPLNX157
DPLNX158
DPLNX159
DPLNX160
.DPLNX161
61
Error codes
Code
Text
Cause/resolution
DPLNX162
DPLNX163
inquiry mismatch %s %s
DPLNX164
DPLNX165
DPLNX166
DPLNX167
DPLNX168
DPLNX169
DPLNX170
DPLNX171
DPLNX172
DPLNX173
DPLNX174
62
DynaPath Operations
This section describes how to manage DynaPath on Solaris, AIX, and Linux.
DynaPath script
The DynaPath script allows you to:
Usage
dynapath <option>
Option
Description
start
stop
restart
status
xray
63
DynaPath Operations
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
controller
device
SANID
pid
gid
64
DynaPath Operations
Commands
Start/stop devices
Task
Command
Description
start [<dpd_id>|all]
Detach devices
stop [<dpd_id>|all]
restart [<dpd_id>|all]
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.
65
DynaPath Operations
Rescan devices
Task
Rescan
Command
Description
Options:
-p
-f
setup
Ignore controllers /
devices
ignore <controller>|<device>
Options:
-a
-l
Un-ignore controllers /
devices
ignore -d
<controller>|<device>
Clean up unavailable
devices
Option:
-p
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
Share
share[<dpd_id>|all
Option:
-c<0|1>
release_lock<device_name>
Release lock
67
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
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
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
69