Home » Dell Manuals » Servers » Dell EqualLogic PS6210XS » Manual Viewer

Dell EqualLogic PS6210XS EqualLogic Host Integration Tools for Linux Version 1 - Page 116

Block Device Access, Excluding Specific Volumes, Step 3: Recon multipathd

View all Dell EqualLogic PS6210XS manuals

Add to My Manuals
Save this manual to your list of manuals

Page 116 highlights

2. If you are using a single path (using the SD device directly without LVM or multipathd), you must manually unmount the file system and run ehcmcli login --target target to recreate the EqualLogic DM devices after unmounting the file system. You can also run ehcmcli dm create to recreate all DM devices instead of ehcmcli login, which only affects the devices for a single volume. 3. Remount the file systems using the new top-tier device names (/dev/eql/volume-name). 4. Using the new top-tier device names, edit /etc/fstab to mount the file systems on the next reboot. Block Device Access For applications or services that use block devices directly, consult the documentation for those applications or services, then reconfigure them to use the appropriate new top-tier devices (/dev/eql/volume-name). This reconfiguration might require restarting or interrupting the application or service and running ehcmcli login --target target or ehcmcli dm create to refresh the EqualLogic MPIO DM devices before restarting the application or service. For more details, see step 3 in the procedure in Directly Mounted File Systems. Excluding Specific Volumes If a block device cannot be migrated to use EqualLogic MPIO (such as a SAN boot volume), add the following section to the end of eql.conf to exclude the device from MPIO: [MPIO Volume Params volume-name] EnableMPIO = false For more details, see Setting Volume-Specific Configuration Parameters. Step 3: Reconfigure multipathd The Linux multipath tools provide facilities to create and manage multiple connections from the Linux host to the target group member. These connections are combined on the Linux host in the form of a Device Mapper (DM) device that provides fault-tolerance and improved performance. NOTE: If you are using the Linux multipathing tools, HIT/Linux provides automated facilities that without the multipathd service create and maintain the necessary multipath devices for connections to volumes on PS series group. Reconfigure it so that it does not interfere with HIT/Linux. The multipathd daemon is required to manage PowerStore devices. Therefore, if you want to import existing EqualLogic storage to PowerStore, make sure that the multipathd service is running. For more information about importing to PowerStore, see the Importing External Storage to PowerStore Guide. You must blacklist all EqualLogic devices in the multipath configuration file (multipath.conf). As part of the installation, eqltune fix introduces blacklist entries that should correctly blacklist all EqualLogic devices. Run multipath -r to ensure multipathd has completely stopped managing all EqualLogic devices before proceeding to the next step. NOTE: By default, SLES 12 distributions do not contain the multipath.conf file in /etc. Copy the file from the /usr/ share/doc/packages/multipath-tools/ directory using the following command: $cp /usr/share/doc/packages/multipath-tools/multipath.conf.synthetic /etc/multipath.conf If you have already installed HIT/Linux, run eqltune fix to blacklist the EqualLogic devices. If you have already created volumes, log out of the volumes and then log back in. (This action is not required if you have not yet installed HIT/Linux.) Step 4: Complete the Installation After configuring all software to use EqualLogic top-tier multipath devices, answer Yes to the following question from the installation script to begin active management of the MPIO and iSCSI sessions: Are you ready to continue and enable active MPIO and iSCSI session management (Yes/No) [No]? 116 Migrating to HIT Linux Multipath I/O

Section	Page
Dell EqualLogic Host Integration Tools for Linux Version 1.7 Installation and User’s Guide	3
About This Guide	8
Revision History	8
Audience	8
Related Documentation	8
Dell Online Services	8
Technical Support and Customer Service	8
Contacting Dell	8
Introduction to HIT/Linux	9
Overview	9
Terminology	9
PS Series Group Network Recommendations	10
Installing and Configuring HIT/Linux	11
Obtain the Installation Kit	11
Installation Prerequisites	11
Installation Script and RPMs	11
Dell End-User License Agreement (EULA)	12
Supported Linux Distributions	12
Array Firmware	12
Supported File Systems	12
Use of the multipathd Daemon	12
Linux Packages and Dependencies	13
Installation Procedure	13
Pre-Installation Steps	13
Installation Steps	14
Installation Results	14
Uninstalling HIT/Linux	16
Updating HIT/Linux	16
Configuration	16
Configuring HIT/Linux	17
Step 1: Verify Configurable Parameters with eqltune and eqlconfig	17
Step 2: Verify Bash Command Line Completion is Configured	17
Step 3: View and Modify MPIO Configuration Settings	17
Step 4: Enable or Disable Multipath I_O	17
Step 5: Discover iSCSI Targets and Create Sessions to Volumes	17
EqualLogic Configuration Utility (eqlconfig)	17
EqualLogic Host Performance and Tuning Suite (eqltune)	18
Features	18
eqlconfig Command Syntax	18
eqltune Command Syntax	19
Evaluating Output Information	19
Block Devices	19
Sysctl Tunables	20
Ethernet Devices	20
iSCSI Settings	20
Logical Volume Management (LVM)	20
EqualLogic Host Tools	20
Examples: eqltune Output	20
Configuring ASM/LE	21
Environment Prerequisites	22
Group Requirements	22
Access to Volumes and Snapshots	22
Verification	22
Remote Setup Wizard Command Line Interface	23
General Command Syntax for the RSWCLI	23
Configuration — Discovering a PS Series Array	23
rswcli --discover Command Syntax	24
Example: Discovering Uninitialized PS Series Arrays	24
Initializing a PS Series Array	24
rswcli --initialize Command Syntax	24
Example: Initializing a PS Series Array	26
Managing Access to a PS Series Group	26
Adding Access to a Group	26
rswcli --add-group-access Command Syntax	26
Example: Adding Group Access	27
Listing Accessible Groups	27
rswcli --list-group Command Syntax	27
Example: Listing Information for Groups	28
Modifying Access to a Group	28
rswcli --modify-group-access Command Syntax	28
Example: Modifying Group Access	28
Removing Host Access to a Group	29
rswcli --remove-group-access Command Syntax	29
Example: Removing Host Access to Group	29
Configuring Multipath I/O	29
Configuring Multipath I/O Devices	30
Accessing Volumes Using Multipath I/O	30
Discovering Targets	30
Log In to an MPIO Volume	31
Logging In to an MPIO Volume	31
Mount an MPIO Volume	31
Logging Out of an MPIO Volume	32
Displaying Connections to a Volume	32
Managing Automatic Logins	32
Managing iSCSI Interfaces	32
Multipath Device Configuration	33
Traditional Multipath Device Configurations	33
Multipath Configuration	33
Example Multipath Device Configuration	35
Special MPIO Configuration Cases	35
Conditions for Configuring Multipath Devices	36
Use of the multipathd Daemon	36
Use of dm-switch Kernel Module	36
Configuring Settings for Multipath I/O	37
Multipath I/O Sessions	37
Setting MPIO Parameters	37
Listing MPIO Subnets	37
rswcli --mpio-parameters Command Syntax	37
Examples: Setting MPIO Parameters	38
rswcli --mpio-list Command Syntax	39
Example: Listing Included MPIO Subnets	39
Including a Subnet or Adapter for MPIO	39
rswcli --mpio-include Command Syntax	39
Examples: mpio-include Command	40
Excluding a Subnet or Adapter From MPIO	41
Including or Excluding Specific Host NICs	41
Configuring I/O Path Selection	41
Load Balancing Policy	41
I/O Scheduling	41
Setting Volume-Specific Configuration Parameters	41
Introduction to ASM/LE	43
About ASM/LE	43
About Smart Copies	43
Types of Smart Copies Created	44
Snapshot Smart Copies	44
Replica Smart Copies	44
Clone Smart Copies	45
Replica Clones	45
Thin Clone Smart Copies	45
Synchronous Replication and Smart Copies	45
Select a Smart Copy	45
Requirements for Creating Smart Copies	46
About Snapshot Space Borrowing	46
Methods of Creating Smart Copies	46
About Group Access Files	47
About Collections	47
About Smart Copy Schedules	48
Advantages of Smart Copy Schedules	48
Constraints of Smart Copy Schedules	48
Data Restoration	48
About Mounting Smart Copies	49
About Unmounting Smart Copies	49
About Logging In to Smart Copies	49
About Logging Off Smart Copies	49
About Restoring Data From a Smart Copy	50
Preconditions for Restoring Data	50
Restoring Data Process	50
About Restoring a Soft-Deleted Smart Copy	50
About Managing Smart Copy Clones After Changing or Deleting Credentials	51
Example	51
Best Practices For Using ASM/LE	53
Auto-Snapshot Manager Command Line Interface	54
Introduction to ASMCLI	54
Entering ASMCLI Commands	54
General Command Syntax for ASMCLI	54
Access Help on ASMCLI Commands	55
ASMCLI Search Options	55
Creating and Managing Group Access Files	57
Creating Access to a PS Series Group	57
asmcli create group-access Command Syntax	57
Examples: Creating Group Access	58
Listing Group Access Information	60
asmcli list group-access Command Syntax	60
Examples: Listing Group Access Information	60
Updating Access to a Group	61
asmcli update group-access Command Syntax	61
Examples: Updating Group Access Information	62
Deleting Group Access Information	63
asmcli delete group-access Command Syntax	63
Examples: Deleting Group Access Information	63
Creating and Managing Smart Copies	64
Creating a Smart Copy the First Time	64
Creating a Smart Copy	64
asmcli create smart-copy Command Syntax	64
Examples: Creating Smart Copies	66
Listing Available Smart Copies	70
asmcli list smart-copy Command Syntax	70
Examples: Listing Smart Copies	70
Access Backup Documents	72
Deleting a Smart Copy	72
asmcli delete smart-copy Command Syntax	72
Examples: Deleting Smart Copies	73
Restoring a Smart Copy	74
asmcli restore smart-copy Command Syntax	75
Example: Restoring Smart Copies	75
Soft-Deleted Smart Copies	75
Managing Soft-Deleted Smart Copies	76
Examples: asmcli list Command	76
Managing Soft-Deleted Smart Copy Clones Without Credentials	77
Smart Copy Operations for Synchronous Replication Volumes	77
Example: Attempting to Restore a Snapshot Created on the Alternate Volume	78
Creating and Managing Smart Copy Schedules	78
Creating a Schedule	79
asmcli create schedule Command Syntax	79
Example: Creating Schedules	80
Listing Schedules	80
asmcli list schedule Command Syntax	80
Examples: Listing Schedules	81
Running a Schedule	83
asmcli do schedule Command Syntax	83
Examples: Running Schedules	83
Updating a Schedule	84
asmcli update schedule Command Syntax	84
Examples: Updating Schedules	86
Deleting a Schedule	87
asmcli delete schedule Command Syntax	87
Example: Deleting a Schedule	87
Mounting and Unmounting Smart Copies	88
Mounting a Smart Copy	88
Mounting Read-Only Smart Copies	88
asmcli mount smart-copy Command Syntax	89
Example: Mounting a Smart Copy	89
Unmounting a Smart Copy	89
asmcli unmount smart-copy Command Syntax	90
Example: Unmounting a Smart Copy	90
Logging In to and Out of Smart Copies	91
Logging In to a Smart Copy	91
asmcli login smart-copy Command Syntax	91
Example: Logging In to Smart Copies	92
Logging Out of a Smart Copy	92
asmcli logout smart-copy Command Syntax	92
Example: Specifying an Object ID with Logout	93
Creating and Managing Collections	93
Creating a Collection	93
asmcli create collection Command Syntax	94
Example: Creating Collections	94
Listing Collections	94
asmcli list collection Command Syntax	94
Example: Listing Collections	95
Updating a Collection	95
asmcli update collection Command Syntax	95
Examples: Updating Collections	95
Deleting a Collection	96
asmcli delete collection Command Syntax	96
Example: Deleting Collections	96
Managing Thin-Provisioned Volumes	97
About Thin-Provisioning	97
Realtime Thin-Provisioning	97
On-Demand Thin-Provisioning	98
Thin-Provisioning as Scheduled Maintenance	98
Group Access Files	99
Considerations for Thin-Provisioning	99
File System and Volume Characteristics	99
Multiple File Systems	99
Volume Thin-Provisioning Configuration Parameters	100
Show Mount Point Information	100
eqlvolume show Command Syntax	101
Examples: Showing Mount Point Information	101
Thin-Provisioning a Volume	102
eqlvolume rethin Command Syntax	103
Examples: Analyzing Thin—Provisioning Recommendations	103
Troubleshooting	105
General Troubleshooting Guidelines	105
Ensuring Correct Operation of the dm-switch Kernel Module	105
Establishing iSCSI Sessions	105
Increasing the Volume Size on a PS Series Group	105
Logical Volume Manager (LVM) Considerations	106
LVM Filtering Rules for EqualLogic Devices	106
Verify and Fix LVM Filters with eqltune	106
Linux Distribution-Specific udev Rule Considerations	107
Considerations when Using the Auto-Snapshot Manager CLI	107
Logical Volume Manager and Read-Only Media	107
Logical Volume Manager and Promoted Replica Volumes	107
Using the eqllog Facility	108
Command Syntax	108
Example: eqllog Output	108
Using the udev Facility	109
Using the ehcmcli Diagnostic Tool	110
ehcmcli Command Syntax	110
ehcmcli Diagnostic Output	111
Running the ehcmd Daemon	112
Considerations When Partitioning iSCSI Volumes	113
Migrating to HIT Linux Multipath I/O	114
Before You Begin	114
Step 1: Install HIT Linux in Migration Mode	114
Step 2: Migrate Existing Storage-Using Applications	115
Logical Volume Manager Considerations	115
Directly Mounted File Systems	115
Block Device Access	116
Excluding Specific Volumes	116
Step 3: Reconfigure multipathd	116
Step 4: Complete the Installation	116
Disabling Active Management	117
Enabling Storage Cluster Support	117
Cluster Logical Volume Manager	117
Enabling iSCSI Offload on HIT/Linux	118
Step 1: Set Up and Verify Your Configuration	118
Step 2: Configure the Network Interfaces	118
Step 3: Configure ehcmd to Use the Offload iSCSI Initiator	119
Step 4: Discover iSCSI Targets	119
Step 5: Logging In to Additional Targets	120
Bash Command Completion	121
DKMS Considerations for Red Hat Linux	123
Index	124
A	124
B	124
C	124
D	124
E	124
F	125
G	125
H	125
I	125
K	125
L	125
M	125
N	126
P	126
R	126
S	126
T	126
U	126

Match case Limit results 1 per page

If you are using a single path (using the SD device directly without LVM or multipathd), you must manually unmount the file system

and run

ehcmcli login --target

target

to recreate the EqualLogic DM devices after unmounting the file system. You can also

run

ehcmcli dm create

to recreate all DM devices instead of

ehcmcli login

, which only affects the devices for a single

volume.

Remount the file systems using the new top-tier device names (

/dev/eql/volume-name

Using the new top-tier device names, edit

/etc/fstab

to mount the file systems on the next reboot.

Block Device Access

For applications or services that use block devices directly, consult the documentation for those applications or services, then reconfigure

them to use the appropriate new top-tier devices (

/dev/eql/volume-name

). This reconfiguration might require restarting or

interrupting the application or service and running

ehcmcli login --target target

ehcmcli dm create

to refresh the

EqualLogic MPIO DM devices before restarting the application or service. For more details, see step 3 in the procedure in

Directly

Mounted File Systems

Excluding Specific Volumes

If a block device cannot be migrated to use EqualLogic MPIO (such as a SAN boot volume), add the following section to the end of

eql.conf

to exclude the device from MPIO:

[MPIO Volume Params

volume-name

]

EnableMPIO = false

For more details, see

Setting Volume-Specific Configuration Parameters

Step 3: Reconfigure multipathd

The Linux multipath tools provide facilities to create and manage multiple connections from the Linux host to the target group member.

These connections are combined on the Linux host in the form of a Device Mapper (DM) device that provides fault-tolerance and

improved performance.

NOTE:

If you are using the Linux multipathing tools, HIT/Linux provides automated facilities that without the multipathd

service create and maintain the necessary multipath devices for connections to volumes on PS series group.

Reconfigure it so that it does not interfere with HIT/Linux.

The multipathd daemon is required to manage PowerStore devices. Therefore, if you want to import existing EqualLogic

storage to PowerStore, make sure that the multipathd service is running. For more information about importing to

PowerStore, see the

Importing External Storage to PowerStore Guide

You must blacklist all EqualLogic devices in the multipath configuration file (

multipath.conf

). As part of the installation,

eqltune

fix

introduces blacklist entries that should correctly blacklist all EqualLogic devices.

Run

multipath -r

to ensure multipathd has completely stopped managing all EqualLogic devices before proceeding to the next step.

NOTE:

By default, SLES 12 distributions do not contain the multipath.conf file in

/etc

. Copy the file from the

/usr/

share/doc/packages/multipath-tools/

directory using the following command:

$cp /usr/share/doc/packages/multipath-tools/multipath.conf.synthetic /etc/multipath.conf

If you have already installed HIT/Linux, run

eqltune fix

to blacklist the EqualLogic devices. If you have already

created volumes, log out of the volumes and then log back in. (This action is not required if you have not yet installed

HIT/Linux.)

Step 4: Complete the Installation

After configuring all software to use EqualLogic top-tier multipath devices, answer

Yes

to the following question from the installation

script to begin active management of the MPIO and iSCSI sessions:

Are you ready to continue and enable active MPIO and

iSCSI session management (Yes/No) [No]?

116

Migrating to HIT Linux Multipath I/O