Dell EqualLogic Host Integration Tools for Linux Version 1.
Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries.
Contents About This Guide............................................................................................................................ 8 Revision History..................................................................................................................................................................... 8 Audience........................................................................................................................................................................
Example: Initializing a PS Series Array........................................................................................................................ 26 Managing Access to a PS Series Group...........................................................................................................................26 Adding Access to a Group............................................................................................................................................
Select a Smart Copy..................................................................................................................................................... 45 Requirements for Creating Smart Copies.................................................................................................................. 46 About Snapshot Space Borrowing..............................................................................................................................
Logging In to and Out of Smart Copies.............................................................................................................................91 Logging In to a Smart Copy.......................................................................................................................................... 91 Logging Out of a Smart Copy......................................................................................................................................
Step 4: Complete the Installation..................................................................................................................................... 116 Disabling Active Management..................................................................................................................................... 117 Enabling Storage Cluster Support .............................................................................................................................
Preface About This Guide Dell EqualLogic Host Integration Tools for Linux (HIT/Linux) enable you to configure and manage Dell EqualLogic PS Series groups from a Linux host. Revision History Document Number 110-6312-EN Revision Date Description R1 April 2020 Version 1.7 initial release Audience The information in this document is intended for administrators responsible for installing and using the HIT/Linux platform.
1 Introduction to HIT/Linux The Dell EqualLogic Host Integration Tools for Linux (HIT/Linux) provide a collection of applications and utilities to simplify the configuration and administration of Dell EqualLogic PS Series storage arrays. This chapter provides an overview of HIT/Linux features and information about what you can expect when installing, configuring, and using this product.
• • • • SD block device—Disk block devices for iSCSI; a direct connection between a host and a PS Series group member Smart Copy—A snapshot, clone, or replica of an individual volume or component, or a collection of volumes or components Switch device—A top-tier switch device for each volume.
2 Installing and Configuring HIT/Linux This chapter guides describes how to install, update, and configure HIT/Linux. To verify that installation was successful, follow the Verification instructions. Topics: • • • • • Obtain the Installation Kit Installation Prerequisites Installation Procedure Configuration Verification Obtain the Installation Kit Obtain the installation kit from the Dell EqualLogic customer support web site. To download HIT/Linux, you must have a Dell customer support account.
Dell End-User License Agreement (EULA) When you perform a fresh installation or an update, you must accept the Dell End-User License Agreement (EULA). For information about how to accept the EULA, see Installation Steps. Supported Linux Distributions HIT/Linux version 1.7 supports the Linux distributions (platforms) specified in the following table. Linux Distribution Version Red Hat Enterprise Linux (RHEL) Server 7.3, 7.4, 7.5 RHEL Server 32-bit or 64-bit 6.
Linux Packages and Dependencies The HIT/Linux installation script attempts to automatically install all required Linux packages (for example, OpenSSL, libpcap, open-iscsi, DKMS, and Python). All packages are part of the RHEL and SLES base repositories. If the packages are not available in a local repository from which the package manager can install them, the installation script notifies you of missing dependencies and you must manually install the required Linux packages.
By default, the installation runs interactively. To run the installation in the background, accept all defaults, and accept the Dell EULA, enter the following command: # /media/iso/install --noninteractive --accepted-EULA Failure to provide the --accepted-EULA option aborts a noninteractive installation.
• (Conditional) On OEL 7.x systems, to view kernel module contents that might have been installed during the installation procedure: # rpm -qa *dm-switch* equallogic-host-tools-kernel --filesbypkg The following table summarizes the installation components. Table 2. Installation Components Path Description Configuration Files /etc/equallogic/eql.conf Configuration file location for HIT/Linux /etc/equallogic/eqltune.
Path Description Manpages and License /usr/share/man/man8/ Location of manpages for Dell EqualLogic tools /usr/share/docs/equallogichost-tools-version/ Location of the End-Users License Agreement (EULA) and license Uninstalling HIT/Linux You are not required to manually uninstall the HIT/Linux kit when performing an update. HIT/Linux automatically uninstalls the previous version (see Updating HIT/Linux). However, if you want to manually uninstall the kit, perform these steps: 1.
Configuring HIT/Linux To begin using HIT/Linux, review the configuration parameters on your Linux server that impact iSCSI operation. Step 1: Verify Configurable Parameters with eqltune and eqlconfig When you run the HIT/Linux installation script, the installation procedure invokes the eqltune utility to evaluate if your configurable parameters conform to the Dell recommended values. After eqltune identifies critical system issues in a summary table, it repairs each category of critical issue.
EqualLogic Host Performance and Tuning Suite (eqltune) The EqualLogic Host Performance and Configuration Tuning Suite (eqltune) verifies a Linux system for optimal iSCSI performance configuration. The suite analyzes a large number of system settings for compliance with Dellʼs recommended practices, categorizing them into four categories: • • • Critical—The setting must be changed to avoid serious performance issue. Warning—The setting should be changed to enhance performance.
Parameter Abbr.
Sysctl Tunables Sysctl tunables include Network buffer sizes and Multi-NIC settings. The Network buffer size settings are less critical but you should increase these settings to avoid overflowing transmit and receive buffer queues, which can lead to degraded performance. The Multi-NIC settings are critical because they pertain to the ARP Flux and Return Path Filtering issues. Ethernet Devices For every Ethernet device available in the system, the eqltune utility performs a few minor verifications.
iSCSI Settings ------------------------------------------------------------------iscsid.conf defaults 0 4 1 2 External Utility Settings ------------------------------------------------------------------Blacklists 0 0 0 1 EqualLogic Host Tools ------------------------------------------------------------------Running system checks 0 0 0 2 eqlvolume checks 0 0 0 3 Run in verbose mode (eqltune -v) for more details and instructions on how to adjust your settings.
• • • Make sure that you have the correct access controls between the computer and the PS Series group. Verify login access to the PS Series group volumes for which Smart Copies will be created. Ensure that the correct Linux iSCSI initiators are installed on your computer and that you can connect to the iSCSI targets.
3 Remote Setup Wizard Command Line Interface The Remote Setup Wizard Command Line Interface (RSWCLI) provides setup commands that you can execute at the Linux command prompt and a command line interface where you can perform all required setup actions.
rswcli --discover Command Syntax The command syntax is as follows: rswcli --discover | -d [--detail] The following table describes the optional command parameter. Table 5. Discover Command Parameter Parameter Description --detail Specifies whether RSWCLI should output the array MAC address, Host Adapter MAC address, firmware version, and supported RAID levels for each array. Additional information might display, depending on your PS Series Array firmware version.
(or, --serial-number serial_number | --sn) [--admin password (use with cg | --create-group only)] [--chap-user username | --cu (use with cg | --create-group only)] [--chap-secret password | --cs (use with cg | --create-group only)] [--dcb-vlan-id DCBVlanID | --vid] [--raid 10|50|6|6-accelerated (use with --cg | --create-group only)] The following table describes the required and optional command parameters. Table 6. Initialize Command Parameters Parameter Abbr.
1RAID5 is no longer considered a best practice for data protection of business critical data on Dell EqualLogic arrays, but it can be configured using the Group Manager CLI. For more information about RAID policies on PS Series systems, see the Dell Technical Report, PS Series Storage Arrays: Choosing a Member RAID Policy, at http://en.community.dell.com/dell-groups/dtcmedia/m/mediagallery/19861480.
The following table describes the required and optional command parameters. Table 7. Add Group Access Command Parameters Parameter Abbr. Argument Description --group-name --gn group-name Designates the name of the PS Series group to which access is being configured. --group-ip --gip IP_address or FQDN Designates the IP address or fully-qualified domain name (FQDN) to be used for accessing the specified group.
Example: Listing Information for Groups In the following example, the list command produces a list of names and IP addresses for a PS Series group to which access is configured. # rswcli --list-group --gn farm31-grp Processing list-group command... Groups accessible from this computer: Group Name: farm31-grp Group IP Address: 192.x.x.xx The list-group command succeeded.
Group Name: new31-grp Group IP Address: 192.xx.xx.xx The modify-group-access command succeeded. Removing Host Access to a Group Use the rswcli --remove-group-access (or rswcli -r) command to remove host access to the PS Series group. rswcli --remove-group-access Command Syntax The command syntax is as follows: rswcli --remove-group-access | -r --group-name group-name | --gn The following table describes the required command parameter. Table 10.
4 Configuring Multipath I/O Devices EqualLogic Multipath I/O (MPIO) in HIT/Linux enables you to configure redundant network paths from a Linux host to PS Series volumes for high availability and high performance SAN data traffic. MPIO accomplishes two goals: • Creates and manages an optimal number of iSCSI sessions to each SAN volume based on the number of host NICs and the number of group members the volume is using. HIT/Linux monitors the SAN configuration and adds sessions as the configuration changes.
Log In to an MPIO Volume To log in to an MPIO volume, specify: # ehcmcli login --target target-name --portal portal where target-name indicates the full iSCSI-qualified name or a volume name for the PS Series group target node, and portal indicates iSCSI portal (group IP address or name). NOTE: You must specify the full iSCSI-qualified name in target-name if there are multiple volumes with identical names. The appropriate device to mount is returned by the ehcmcli login command.
• EqualLogic storage supports partitions (for example, using fdisk), but recommends using file systems on the full volume instead of partitions on that volume. If you want to suppress creating partition devices on a volume, see Setting Volume-Specific Configuration Parameters. If you want to mount a mount point on system reboot, add it to your /etc/fstab file.
If you created iface records for specific adapters, ehcmd uses the existing records. If ehcmd creates new records, it uses the naming scheme eql.eth0_X. For example: # iscsiadm -m iface | sort default tcp,,,, eql.eth0_0 tcp,00:26:B9:3A:6B:9E,,, eql.eth0_1 tcp,00:26:B9:3A:6B:9E,,, eql.eth1_0 tcp,00:26:B9:3A:6B:9F,,, eql.eth1_1 tcp,00:26:B9:3A:6B:9F,,, eql.
Figure 1. Dell EqualLogic Multipath Device Configuration - Logical View Table 11. Callouts in Figure 1 Callout Number Description of Feature 1 Host file system or application using a block device 2 Device Mapper layer—The Device Mapper allows layering block devices to set up a multipath configuration. HIT/ Linux uses the Device Mapper to build a two-tier device structure with multiple multipath devices (dmmultipath) for each volume and a Device Mapper switch target on top of the multipath devices.
Callout Number Description of Feature queue-length path selector for load balancing. Otherwise, the devices use a round-robin path selector. The dmmultipath device also provides error handling capability and on an I/O error will retry I/Os on alternate paths. If all paths in the preferred priority group fail, paths from the nonpreferred priority group are used for I/O. For information on the supported path selection policies, see Conditions for Configuring Multipath Devices.
• Single-member volume with multiple connections—In some cases, a volume might reside in a single member but might have multiple connections to that member (for example, very small volumes only reside on a single member). In this case, the ehcmd daemon builds a single Device Mapper device that uses the Device Mapper multipath target to allow I/O to all available sessions, because all paths are equally good for each I/O. This device is called eql-PS_volume_id _a.
For additional information troubleshooting problems with the dm-switch kernel module, see Assuring Correct Operation of the dmswitch Kernel Module. Configuring Settings for Multipath I/O HIT/Linux lets you configure multiple multipath devices as redundant paths from a Linux iSCSI initiator to a PS Series volume.
Table 12. MPIO Optional Parameters Parameter Abbr. Argument Description --max-sessions-per-volume-slice maxvols 1-4 Specifies the maximum number of connections for MPIO to use per volume per member. --max-sessions-per-entire-volume maxvole 1-12 Specifies the maximum number of connections for MPIO to use per volume for all members. --default-load-balancing dlb LQD or RR Specifies the default load balancing policy for MPIO as Least Queue Depth (LQD) or Round Robin (RR).
The mpio-parameters command succeeded. rswcli --mpio-list Command Syntax The command syntax is as follows: rswcli --mpio-list | -L [--include-only | -io or --exclude-only | --eo] The following table describes the optional command parameters. Table 13. List of Optional MPIO Parameters Parameter Abbr. Description --include-only --io Specifies that the list should only contain the subnets that are included for use by MPIO. If this parameter is specified, the exclude-only parameter cannot be specified.
Parameter Abbr. Argument Description --mask none subnet-mask Specifies a subnet mask to include. Used with the -network parameter. --adapter none adapter-name Specifies a user-defined string as the name of the adapter to include. For example, eth0, eth1, and so on. --mac none mac-address Specifies a MAC address, or physical address, for an adapter that is to be included.
Excluding a Subnet or Adapter From MPIO Use the rswcli --mpio-exclude (or rswcli -E) command to select the subnets or adapters to exclude from MPIO. You can specify a subnet, an adapter identified by a user-defined string, an IP address, or a MAC address. Dell recommends using a subnet or adapter name based on inclusion/exclusion rules. Including or Excluding Specific Host NICs Include or exclude a host NIC with the IP address of the NIC and a netmask of 255.255.255.
• • • • LoadBalanceType MaxDevicesPerMPIOSession MaxConnectionsPerMember SuppressPartitions To set volume-specific values for any of these values, add a section to the eql.conf file name [MPIO Volume Params volumename] and define the volume-specific parameter settings in this section. Wildcards can be used in volume-name. For example, to increase the IOPerPath value to 100 for all LogVol* volumes, add the following lines to the eql.
5 Introduction to ASM/LE Dell EqualLogic Auto-Snapshot Manager/Linux Edition (ASM/LE) is a component of Dell EqualLogic Host Integration Tools for Linux. ASM/LE is installed as part of the HIT/Linux installation and presented as a configuration option.
The following figure illustrates the Smart Copy creation process. Figure 2. Smart Copy Creation Process Table 15. Smart Copy Creation Process Callouts Callout Number Description 1 Freeze the file system 2 Request made to create a snapshot 3 Snapshot is created 4 Array sends snapshot complete message back to the host 5 File system is thawed After you create a Smart Copy, you can import and mount it, and then restore the original objects from the Smart Copy.
To create a Replica Smart Copy, you must provide credentials for accessing the source volumes. To log in to or mount the completed replicas, you must provide credentials for the replication site partner (that is, the destination). ASM/LE creates a replica for each volume comprising the original object on the PS Series group configured as a replication partner for the original object. Each volume that is part of the original object must already be configured for replication in the group.
These options can be combined, for example, to search for a replica Smart Copy on a particular host. You can also search by comment string or volume name. ASM/LE also performs a case-insensitive glob search and will match any string if you specify multiple strings: • • By the comment string used when the Smart Copy was created By the source target volume name ASM/LE supports the following glob syntax: • • Asterisk (*) matches zero or more characters. Question mark (?) matches exactly one character.
About Group Access Files To successfully access a PS Series group, administrators require network access to the group IP address and a valid group identity (that is, administrative user name and password). Different account types provide different privileges. The default account, grpadmin, provides all privileges. Credentials can also be set up for pool and volume administrators, restricting access to the entire group. Dell recommends using volume administrator credentials.
You can modify a collection by changing its name, by replacing all existing mount points, by adding one or more mount points, or by deleting it. For example, # asmcli update collection --name daily-user-vols --add /source/VolC For information about using ASMCLI to perform these collection operations, see Creating and Managing Collections. About Smart Copy Schedules Schedules perform Smart Copy operations at regular intervals.
You can mount or restore data from a Smart Copy of a volume using mount points referenced when you created the Smart Copy. Restored mount points reference the same volumes they did at the time you created the Smart Copy, unless you manually change the restored mount points to reference different volumes, such as another mounted Smart Copy. About Mounting Smart Copies Mounting a Smart Copy makes its contents accessible to the computer.
• • • Ensure that the computer has the security credentials to access the Smart Copies in the set. Identify the snapshot or Smart Copy Set that you want to log off. Stop using the Smart Copy. About Restoring Data From a Smart Copy If a catastrophic system failure results in data loss, it might be necessary to restore data from a Smart Copy.
• If a volume is running a pre-6.0 version of the firmware, updating that volume to the current of the firmware enables the soft-delete feature on that volume. • The asmcli list smart-copy --check-status command can display soft-deleted Smart Copies, but it cannot restore or purge them. To restore or purge a soft-deleted Smart Copy, use the Recover button in the Volume Recovery Bin interface of the EqualLogic Group Manager GUI.
Some time later, the Smart Copy clone is deleted. The Smart Copy is not displayed as part of a normal asmcli list smart-copy command; it is hidden. [root@rhel69x ~]# asmcli delete smart-copy --latest Dell EqualLogic Auto-Snapshot Manager CLI Version 1.7.0 Copyright (c) 2010-2020 Dell Inc. Deleted Smart Copy: 5-82cd1c-c445d3028-eecf8fc826db539a Successfully removed the Smart Copy. [root@rhel69x ~]# asmcli list smart-copy --type clone Dell EqualLogic Auto-Snapshot Manager CLI Version 1.7.
you can connect to the PS Series group, but access to the volumes for rhel69x is not allowed. As a result, the volumes for rhel69x are hidden. # asmcli list smart-copy --type clone --check-status --group-access-file \ voladmin-sles Dell EqualLogic Auto-Snapshot Manager CLI Version 1.7.0 Copyright (c) 2010-2020 Dell Inc. ======================================================== Smart Copies ======================================================== Source: rhel69x.mycompany.
6 Auto-Snapshot Manager Command Line Interface The Auto-Snapshot Manager Command Line Interface (ASMCLI) provides Smart Copy creation and management commands that you execute at the Linux command prompt.
• • • • • • Use of the equal sign (=) to specify a value to parameters is optional. For example, --name=eqlgroup1 and --name eqlgroup1 are equivalent. Not shown in the syntax for an ASMCLI command is the --verbose option, which you can use to display more detailed information. For more verbose output information, specify --verbose 2 or simply -vv. Use the --help option to display arguments to parameters. Use asmcli help to display all command noun-verb pairs and options.
[--schedule schedule-name | -S] [--source mount-point1 [mount-point2...] -s] [--type volume-type | -t] [--volume volume-name] Table 16. ASMCLI Search Options Search Option Parameter Abbr. Argument Description --collection -c collection-name Search by the name of a Smart Copy collection. Do not use with --source. --comment -C comment-string Search by the comment string you entered when creating a Smart Copy. The comment is set for the PS Series group and stored in the backup document.
Search Option Parameter Abbr. Argument Description --type -t volume-type Search by type of Smart Copy: either clone, replica, snapshot, or thinclone. NOTE: The search option does not apply to the restore smartcopy command. --volume none volume-name Search by the source volume name. By default ASM/LE performs a caseinsensitive glob search and matches any string if you enter multiple strings. You can combine search options to narrow down a long list of Smart Copies.
Parameter Abbr. Argument Description --name -n group-name Specifies the name of the PS Series group. --user-name -u user-name Specifies the user name on the PS Series group. --file -f file-location Specifies the location of the group access file. --ip-address -i IP-address Specifies the permanent IP address of the PS Series group. You must use parameter when creating a new entry for the PS Series group.
• • Using multiple group access files Inserting multiple user names into a group access file and selecting the user name for a given operation on the ASMCLI command line In this example, volume administrator user-admin is an administrator for several user volumes on PS Series group, eqlgroup1. That PS Series group has volumes used by the accounting applications. Those volumes are administered by volume administrator accnt-admin.
Successfully created credentials record in file /etc/equallogic/asm-group-access. # asmcli list group-access ======================================================== Group Access ======================================================== Group name: Group1 IP address: 192.x.x.xx User names: user-voladmin Group name: Group2 IP address: 192.x.x.xy User names: user-voladmin Group name: Group3 IP address: 192.x.x.xz User names: user-voladmin (No stored password) 3 Groups defined.
Group name: IP address: User names: eqlgroup2 192.x.x.xy j_smith Group name: IP address: User names: eqlgroup8 192.x.x.zz John_Smith 3 Groups defined. Example 2: Listing Group Access Records for a Specific Group To list group access information for the group eqlgroup1, specify a group name: # asmcli list group-access --name eqlgroup1 Group name: IP address: User names: eqlgroup1 192.x.x.
Parameter Abbr. Argument Description --user-name -u user-name Specifies the user name on the PS Series group. Examples: Updating Group Access Information This section includes examples of replacing a group access file, changing a group name, updating a group access file for a management IP, and removing a stored password for a group.
--no-password Successfully updated credentials for user "user-voladmin" in group "Group2" in file /etc/equallogic/asm-group-access. # asmcli list group-access ======================================================== Group Access ======================================================== Group name: Group1 IP address: 192.x.x.xx User names: user-voladmin Group name: Group2 IP address: 192.x.x.xy User names: user-voladmin (No stored password) Group name: Group3 IP address: 192.x.x.
Example 2: Deleting Group Access Information for All Users To delete all credentials and group information for eqlgroup1, the --user-name option is omitted: # asmcli delete group-access --name eqlgroup1 Creating and Managing Smart Copies ASMCLI provides commands for creating and managing Smart Copies.
[--force | -F] [--freeze-time n] [--group-access file-location | -g] [--object object-id | -o] [--output error | always] [--read-only | -R] [--retry-count n | -r] [--retry-wait n | -w] [--type volume-type | -t] [--username user-name | -u] The following table describes the required and optional command parameters. Table 21. Create Smart-Copy Command Options Parameter Abbr. Argument Description Required Parameters --collection -c collection-name Specifies the Smart Copy collection name.
Parameter Abbr. Argument Description --retry-wait -w n Specifies the number of seconds to wait before retrying a failed operation. --type -t volume-type clone|replica| snapshot| thinclone Specifies the Smart Copy type to create. If omitted, creates snapshot. ASMCLI reports an error if an incorrect type is applied, such as thinclone for a volume that is not a template volume.
Created snapshot volb-2017-01-05-14:39:14.221.1 on glengrp Created snapshot volc-2017-01-05-14:39:14.222.1 on glengrp Created snapshot vola-2017-01-05-14:39:14.223.1 on glengrp All mount points (3) have been thawed. Successfully created a Smart Copy from 3 targets. Example 4: Retrying Creation of Smart Copy with Multiple Volumes In this example, ASMCLI fails to create a consistent Smart Copy for a large number of source mount points on the first attempt.
Smart Copies ======================================================== Source: myhost.mycompany.com : /mnt/asm-acl Replica: 02-Feb-2017 14:58:37.692088 ObjectId: b-6d91c1-b5427dfda-ccfc656a321b56aa asm-acl on windev33-grp --> asm-acl.1-2017-02-02-01:50:58.533.1 on HitStore4 1 Smart Copy found. # asmcli create smart-copy --object b-6d91c1-b5427dfda-ccfc656a321b56aa --type clone Created clone asm-acl-clone-2017:02:02-14:59:38.
The following part shows the --broken option, which searches for broken Smart Copies. Because this requires ASMCLI to access the group, you are prompted for a password, # asmcli list smart-copy --broken Password for user user-voladmin on 192.0.2.20: ****** 0 Smart Copies found. If you delete the access credentials for a group, the Smart Copy creation operation will fail. In the last part of this example, group access records are deleted for Group3, and the subsequent attempt to create a Smart Copy fails.
Suggestion: Please increase snapshot reserve or delete unnecessary snapshots. For scheduled operations, consider using "keep count" (see "asmcli help schedule"). The mount point has been frozen. Created snapshot myvol-user1-2017-08-16-09:49:20.465.1 on group9 The mount point has been thawed. Successfully created a Smart Copy from 1 target. Listing Available Smart Copies Use the asmcli list smart-copy command to list all available Smart Copies.
Example 1: Listing All Smart Copies The list smart-copy command with no qualifiers lists all Smart Copies. For each Smart Copy, the output identifies the location, the type, the name, the date created, and the status (for example, mounted). The following example shows four Smart Copies, one of which contains multiple mount points. # asmcli list smart-copy ======================================================== Smart Copies ======================================================== Source: hostname.mycompany.
username grpadmin (GroupAdmin) ======================================================== Smart Copies ======================================================== Source: hostname.mycompany.com : /mnt/mnt1 /mnt/mnt3 /mnt/mnt4 Replica: 28-Feb-2017 10:42:54.077954 ObjectId: f-ceea53-2f409c86e-6b29668578db1cac Directory: /mnt/asm/asm-le-node202.equallogic.com/source-e-794700706f6e2b2-c25ce4ca6fda4f46/ File: 20120222-154254.077954-f-ceea53-2f409c86e-6b29668578db1cac.bcd vol1 on group1 --> vol1.3-2017-02-22-11:05:13.
Search option parameters also apply to this command. For information, see ASMCLI Search Options. The following table describes the optional command parameters. Table 23. Delete Smart Copy Optional Command Parameters Parameter Abbr. Argument Description --broken -B none Deletes broken Smart Copies and attempts to access the group access file for a PS Series group. A broken Smart Copy contains a snapshot or replica snapshot that is missing while the source volume is still accessible.
Example 2: Deleting a Smart Copy Identified By Object ID To ensure you are deleting the correct Smart Copy, list Smart Copies in very verbose mode to display full information for the Smart Copies. # asmcli list smart-copy --source /source/VolB -verbose ======================================================== Smart Copies ======================================================== Source: hostname.mycompany.com : /source/VolB Snapshot: 04-Jan-2017 16:24:29.
asmcli restore smart-copy Command Syntax The command syntax is as follows: # asmcli restore smart-copy [--force | -F] [--group-access-file file-location | -g] [--user-name user-name | -u] Search option parameters also apply to this command. For information, see ASMCLI Search Options. The following table describes the optional command parameters. Table 24. Restore Smart Copy Optional Command Parameters Parameter Abbr.
Managing Soft-Deleted Smart Copies Smart Copy clones that have been soft-deleted are held temporarily in the volume recovery bin. You can use the following commands with Smart Copy clones: • Identify clones that have been soft-deleted in the volume recovery bin using the asmcli list smart-copy --check-status command. Access the Volume Recovery Bin interface through the EqualLogic Group Manager GUI.
Example 3: Status of Smart Copy After Recovery The following example shows the status of the Smart Copies after one clone has been recovered and one clone remains in the volume recovery bin. # asmcli list smart-copy --type clone --check-status -vv Logged into PS Series group 192.x.x.xx (earth39-grp) as username grpadmin (GroupAdmin) ======================================================== Smart Copies ======================================================== Source: mysystem.equallogic.
The following table describes ASMCLI commands that are available for synchronous replication volumes. Table 25. ASMCLI Commands Available for Synchronous Replication Volumes Command Description --create Creates a Smart Copy of a synchronous replication volume. Supports snapshots and clones only. --mount Mounts a synchronous replication volume. Applies to active volumes and to alternate volumes after successfully switching the roles of the pools. --unmount Unmounts a synchronous replication volume.
• • • • • Change the schedule without modifying any scripts or cron tables. When the scheduled operation is included in a script or cron table, you can use ASMCLI to change the options to the create smart-copy command without making other changes (see Creating a Smart Copy). Locate Smart Copies created by a given schedule by specifying the --schedule option with the list smart-copy command (see Listing Schedules) Limit the number of Smart Copies kept for a schedule using the --keep option.
Option Abbr. Argument Description the operation times out and a consistent Smart Copy is not created. For most configurations, the default time is sufficient. When creating Smart Copies with a large number of mount points or a heavy I/O load, ASM/LE might not have enough time to freeze all of the mount points and build the Smart Copy. Use this option to increase the time limit.
Table 27. List Schedule Optional Command Parameter Parameter Argument Description --name schedule-name Specifies the name of the scheduled operation. Examples: Listing Schedules This section includes examples of listing schedules with verbose output and listing schedules that are enabled in a cron job.
# Run this scheduled operation every 15 minutes */15 * * * * asmcli do schedule --name 15min >/dev/null # Run this scheduled operation every hour 0 * * * * asmcli do schedule --name hourly >/dev/null # asmcli list smart-copy ======================================================== Smart Copies ======================================================== Source: hostname.mycompany.com : /vol1 Snapshot: 10-Jan-2017 10:15:01.
vola01 --> vola01-2017-01-10-10:59:07.16866 on windev11-grp Snapshot: 10-Jan-2017 11:00:01.853586 Description: Test schedule cron: 15 minutes Schedule: 15min Collection: test1 vola01 --> vola01-2017-01-10-10:59:07.16867 on windev11-grp Snapshot: 10-Jan-2017 11:15:01.881889 Description: Test schedule cron: 15 minutes Schedule: 15min Collection: test1 vola01 --> vola01-2017-01-10-11:14:07.16868 on windev11-grp 5 Smart Copies found.
Example 2: Running a Schedule in a Cron Job In this example, the scheduled operation is included in a cron table. You can modify the schedule with ASMCLI (see Updating a Schedule) without modifying any scripts or cron tables. That is, you can change the options on the create smart-copy command at the command line through ASM without making other changes.
The following table describes the required and optional command syntax. Table 29. Update Schedule Command Options Parameter Abbr. Argument Description -n schedule-name Specifies the name of the schedule. --collection -c collection-name Specifies the name of a Smart Copy collection. All Smart Copies, even a single one, are stored in a collection. Do not use with --source. --comment -C comment-string Provides a comment string to describe the Smart Copy that you are updating.
Parameter Abbr. Argument Description --user-name -u user-name Specifies a particular user identity, when multiple user names have been stored in the group access file. Examples: Updating Schedules This section includes examples of updating a schedule to change the Smart Copy type, to change a schedule name, to delete an option in a schedule, and to create a collection.
1 schedule found. # asmcli update schedule --name user-hourly --delete comment Successfully updated schedule "user-hourly". # asmcli list schedule ======================================================== Schedules ======================================================== Name: user-hourly Command: asmcli create schedule --keep 24 --type snapshot --source /user1 /user2 /user3 1 schedule found.
Name: user-hourly Command: asmcli create schedule --keep 24 --comment "Hourly snapshot of user space" --type snapshot --source /source/VolB Name: user-hourly-all Command: asmcli create schedule --keep 24 --type snapshot --source /source/VolA /source/VolB 2 schedules found. # asmcli delete schedule --name user-hourly-all Successfully deleted schedule "user-hourly-all".
3. Unmount the file system. asmcli mount smart-copy Command Syntax The command syntax is as follows: # asmcli mount smart-copy --destination directory-name | -d [--group-access-file file-location | -g] [--output always | error] [--read-only | -R] [--retry-count n | -r] [--retry-wait n | -w] [--user-name user-name | -u] Search option parameters also apply to this command. For information, see ASMCLI Search Options. The following table describes the required and optional command parameters. Table 31.
asmcli unmount smart-copy Command Syntax The command syntax is as follows: # asmcli unmount smart-copy [--group-access-file file-location | -g] [--limit number ] [--nologout] [--output always | error] [--retry-count n | -r] [--retry-wait n | -w] [--user-name user-name | -u] Search option parameters also apply to this command. For information, see ASMCLI Search Options. The following table describes the optional command parameters. Table 32. Unmount Smart Copy Optional Command Parameters Parameter Abbr.
2. Specify the object ID in the unmount command: # asmcli unmount smart-copy --object 5-392e06-8244f99a7-88d5834731b41690 If you know the Smart Copy is the latest created, you can bypass using the Object ID and unmount using the --latest option. Similarly, you can unmount the earliest-created Smart Copy using the --earliest option. For example: # asmcli unmount smart-copy --latest --source /source/volA Unmounted /snapshots/vola/source/volA Removing sessions to 1 Smart Copy target.
Example: Logging In to Smart Copies The following example logs in to the latest Smart Copy created by a schedule. # asmcli login smart-copy --schedule user-hourly --source/source/VolB --latest Logging in 1 Smart Copy target. Logged in donvolb-2017-01-05-17:03:01.225.1 on glengrp Created device /dev/mapper/eql-8-b8b03d-7444e1f3e-626856b008bde08e+donvolb Successfully logged in 1 file system from 1 Smart Copy target.
Parameter Abbr. --output Argument Description always | error Specifies when to display output to the console. Use error to display output only when an operation fails. Use always (default) to display all output from the operation. --retry-count -w n Specifies the number of times to retry a failed operation. For example, if you are creating a Smart Copy snapshot of two separate volumes and one is offline, the operation will attempt to connect every n seconds.
asmcli create collection Command Syntax The command syntax is as follows: # asmcli create collection --name collection-name --source mount-point1 [mount-point2...] The following table describes the required command parameters. Table 35. Create Collection Required Command Options Parameter Argument Description --name collection-name Specifies the name of the collection. --source mount-point Specifies a list of one or more mount points.
Example: Listing Collections This example specifies the name daily-user-vols and displays a collection containing three volumes. # asmcli list collection --name daily-user-vols ============================================== Collections ============================================== Name: Mount point: Mount point: Mount point: daily-user-vols /source/VolA /source/VolB /source/VolC 1 collection found.
Example 2: Deleting from a Collection This example deletes the volume VolC from the collection. # asmcli list collection --name daily-user-vols ============================================== Collections ============================================== Name: Mount point: Mount point: Mount point: daily-user-vols /source/VolA /source/VolB /source/VolC 1 collection found. #asmcli update collection --name daily-user-vols --delete /source/VolC Successfully updated collection "daily-user-vols".
7 Managing Thin-Provisioned Volumes Thin-Provisioned volumes enable you to recover disk space that has become available and make more efficient use of disk capacity in storage volumes. Using the eqlvolume tool, you can show information on mount points and the EqualLogic volumes that support them. You can also display a list of volumes recommended for thin-provisioning (also called rethinning) or that are mounted with the -o discard option, and specify which volumes are to be thin-provisioned.
• • RHEL 6.8 Server and higher: ext4, gfs2, and xfs. SLES 12 and higher: ext3, ext4, and xfs. NOTE: By default, the file system when installing SLES 12 and later is btrfs, which is not supported by ASM/LE. Select ext4 or xfswhen installing SLES 12. On-Demand Thin-Provisioning On-demand thin-provisioning enables you to disable realtime volume thin-provisioning and to run volume thin-provisioning either manually or as a scheduled maintenance activity.
Group Access Files Access to the PS Series groups by eqlvolume is controlled by entries in the group access file. These entries are built and maintained by the asmcli utility. For more information about group access files, use the asmcli help group-access command. Considerations for Thin-Provisioning Several characteristics are considered when eqlvolume determines whether or not a volume can be thin-provisioned.
Volume Thin-Provisioning Configuration Parameters Configuration parameters in /etc/equallogic/eql.conf control the behavior of the eqlvolume rethin command. The eqlvolume tool uses these parameters, with file system and EqualLogic volume characteristics, to determine if a volume can be thinprovisioned. For information on these characteristics, see Considerations for Thin-Provisioning. The following table describes the volume thin-provisioning configuration parameters. Table 39.
eqlvolume show Command Syntax The command syntax is as follows: # eqlvolume show [--include mount-point | -i] [--exclude mount-point | -e] [--group-access-file file-location | -g] [--user-name user-name | -u] The following table describes the optional command parameters. Table 40. eqlvolume show Optional Command Parameters Parameter Abbr. Argument Description --include -i mount-point Specifies the mount points for which to display information.
vg11 on eqlgroup1 1.71 GB 100.00 GB 1.7% thin replication /lv12a /lv12b /lv12c vg12 on eqlgroup1 150 150 150 5.07 9.84 9.84 9.84 100.00 GB GB GB GB 1.5% 1.5% 1.5% 5.1% ext4 ext4 ext4 thin rw rw rw /VolA vola on eqlgroup2 5.18 GB 2.65 GB 98.43 GB 100.00 GB 0.2% 2.7% ext3 thin rw /mnt/temp/lv11a 662 MB 9.84 GB 1.5% ext4 vg11-2016-07-20-08:46:30.26820.1 on eqlgroup3 replica rw /VolB volb on eqlgroup2 rw MB MB MB GB 534 MB 1.29 GB 9.85 GB 10.00 GB 0.3% 12.
eqlvolume rethin Command Syntax The command syntax is as follows: # eqlvolume rethin [--recommend | -R] [--discard-usage | -D] [--include mount-point | -i] [--exclude mount-point | -e] [--force mount-point | -F] [--group-access-file file-location | -g] [--user-name user-name | -u] The following table describes the optional command parameters. Table 41.
target (2.36 GB) /test06 : File system space used (3.17 GB) is greater than space used by target (2.52 GB) # vi /etc/equallogic/eql.conf # tail -n 4 /etc/equallogic/eql.conf [EQLVOLUME Params] ReThinRecommend = 50 # eqlvolume rethin --recommend --verbose Locating all mount points supported by EqualLogic targets. Logged into PS Series group 192.x.x.xy (eqlgroup2) as username grpadmin (GroupAdmin) No mount points recommended for rethinning.
8 Troubleshooting This chapter provides troubleshooting information for HIT/Linux. Topics: • • • • • • General Troubleshooting Guidelines Using the eqllog Facility Using the udev Facility Using the ehcmcli Diagnostic Tool Running the ehcmd Daemon Considerations When Partitioning iSCSI Volumes General Troubleshooting Guidelines The following general troubleshooting guidelines apply when using HIT/Linux.
A critical part of this process is for ehcmd to issue an iscsiadm –m node –R –T iqn command to direct the Open iSCSI software to rescan all of the block-mode devices so that the attributes (especially the size) for those devices are updated. If this command is slow, you might see ehcmcli diagnostic information similar to the following output: ======================================================== Volume list ======================================================== Volume: user2 Target name: iqn.2001-05.
Linux Distribution-Specific udev Rule Considerations SLES11 ships with a udev rules file (64-lvm2.rules) that may activate LVM volumes. Because this rule bypasses lvm.conf and the special filter that eqltune added, HIT/Linux installs a udev rules file named 64-eqllvm.rules to prevent 64-lvm2.rules from activating LVM on EqualLogic hidden devices.The 64-eqllvm.rules file does not affect any other devices, allowing the SLES 64lvm.
Using the eqllog Facility To gather information for EqualLogic support, you can run the EqualLogic Log Gathering Facility (eqllog) to collect system logs and information about the current running state of your configuration. The eqllog facility gathers log files, configuration files, and command output, and bundles this information in a compressed tar file for easy storage and transmission. The name of the file is eqllog-YYYYMMDDHHMMSS.tar.
Copy directory /var/log/equallogic as logs Copy directory /etc/equallogic as etc Capture 'ehcmcli -dv' to 'ehcmcli.dump' Return code: 0 Capture 'eqltune -v' to 'eqltune.dump' Return code: 1 Capture 'dmsetup status' to 'dmsetup-status.dump' Return code: 0 Capture 'dmsetup table' to 'dmsetup-table.dump' Return code: 0 Capture 'dkms status' to 'dkms/status.
• 11-eqlenv.rules • This udev rule file sets up important environment variables and symlinks used by ehcmd and in other udev rule files. 38-equallogic.rules • These udev rules should serve as a guide for setting up systemwide udev rules for EqualLogic storage devices, and demonstrate how this setup can be done by setting the readahead value for all EqualLogic devices to 1024kb. You can copy this file to /etc/udev/ rules.d/39-eql_user.rules for customization. 99-eqlsd.
Subcommands Options Argument Description help none subcommand Displays a list of the ehcmcli commands and syntax. Specify a subcommand to list the syntax (for example, ehcmcli help pr). dm create none none Builds the initial DM devices for all current EqualLogic devices. dm cleanup none none Removes any unmanaged DM devices (/dev/mapper devices created by ehcmd) that are no longer needed. dm unload_switch none none Replaces all switch DM targets and unloads the dmswitch kernel module.
The ehcmcli diagnostic output includes a report of all the volumes the ehcmd daemon is managing and a list of iSCSI sessions to each volume. The output for each iSCSI session contains the session ID used by iscsiadm, the SD device, the source and target IP addresses, and the uptime. For example, the following output shows the status of the linux-hyb-mpio5 volume: Volume: linux-hyb-mpio5 Target name: iqn.2001-05.
Considerations When Partitioning iSCSI Volumes As a general rule, partitioning an iSCSI volume adds complexity and overhead to the I/O path. For example, you could create one iSCSI volume and partition it into three pieces, or create three separate volumes. When you need to create partitions, HIT/Linux accommodates partitioned environments.
A Migrating to HIT Linux Multipath I/O The following sections describe how to migrate an existing Linux system connected to Dell EqualLogic PS Series storage to use HIT/Linux multipath I/O (MPIO). If you are installing HIT/Linux in an environment without previously configured storage, follow the basic installation steps in Installing and Configuring HIT/Linux. NOTE: This migration is not required if you are updating from a previous version of HIT/Linux.
Step 2: Migrate Existing Storage-Using Applications After the installation script has completed collecting your configuration responses, it displays the following output: ====================================================================== MPIO Device Migration ====================================================================== Starting service: ehcmd Starting service: scsi_reserve_eql Creating initial DM devices Pausing now to allow for manual block device migration.
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.
Any application using an EqualLogic top-tier device will not require any further intervention. Disabling Active Management If you answered No in step 4, active management remains disabled until you explicitly enable it.
B Enabling iSCSI Offload on HIT/Linux Before enabling iSCSI offload functionality, make sure that HIT/Linux is installed on your system and that ehcmd is running and using the (default) TCP initiator. Follow the steps in this chapter to enable Broadcom iSCSI offload functionality for HIT/Linux.
eth3 Link encap:Ethernet HWaddr A4:BA:DB:38:8B:41 inet addr:x.x.x.y Bcast:x.x.x.z Mask:255.255.254.0 To determine the correct ISOE MAC address: 1. Add 1 to the hexadecimal TCP-IP MAC address reported by ifconfig. 2. Update the appropriate interface (iface) records in iscsiadm to associate each ISOE MAC address with a new, unique IP address. For example: # iscsiadm -m iface -I bnx2i.a4:ba:db:38:8b:40 -o update -n iface.ipaddress -v 1 xx.xx.x.x bnx2i.a4:ba:db:38:8b:40 updated. # iscsiadm -m iface -I bnx2i.
After rediscovering the targets, you will see that the isciadm interface records have been updated by ehcmd. For example: # iscsiadm -m iface default tcp,,,, iser iser,,,, bnx2i.a4:ba:db:38:8b:40 bnx2i,a4:ba:db:38:8b:40,1.2.3.4,, bnx2i.a4:ba:db:38:8b:42 bnx2i,a4:ba:db:38:8b:42,1.2.3.
C Bash Command Completion Command-line interfaces in HIT/Linux are integrated with a Bash programmable command completion facility. The Bash commandcompletion script, installed as /etc/bash_completion.
If you enter s followed by a tab, Bash completes the command with the source parameter: # asmcli create smart-copy --s # asmcli create smart-copy --source As a general rule, type as much as you think will enable Bash to complete the command. If you are unsure of the options, enter a command, followed by two tabs, and then select from the options.
D DKMS Considerations for Red Hat Linux Dynamic Kernel Module Support (DKMS) is required on systems where a precompiled binary kernel module is not available, such as on a system running a custom Linux kernel. The HIT/Linux installation script will attempt to install all required Linux packages. However, DKMS is not available in the default Red Hat repositories; extra steps are required to obtain and install DKMS. All other prerequisite packages are installed.
Index A Bash command completion 110, 121 add-group-access command parameters 27 ASM Command Line Interface, See ASMCLI ASM/LE about authentication files 47 about data restoration 50 accessing volumes and snapshots 22 automatic authentication 47, 57 best practices 53 collections 47, 93 configuration 16 configure 21 description 9 environment prerequisites 22 group requirements 22 introduction 43 restoring data 50 ASMCLI accessing help 55 create group-access 57 delete group-access 63 entering commands 54 ide
ehcmd daemon (continued) function of 33–36 managing automatic logins 32 rescanning devices 106 starting 13 updating attributes 106 eqlconfig command syntax 18 description 9 features 18 eqllog command syntax 108 description 9 eqltune command syntax 19 commands and parameters 19 description 9 summary example 20 using 18 verbose-mode example 21 eqlvolume configuration parameters 100 description 9 recommend for thin-provisioning 99 show 100 thin-provisioning 102 EqualLogic Log Gathering Facility See eqllog 108
multipath I/O (continued) sessions 37 setting parameters 37 special cases 35 N network recommendations for group 10 P path selection policy 41 PowerStore import ehcmcli commands 111 enabling import capability 13, 14 IPv6 13 Linux requirement 12 multipathd 12, 36, 116 PS Series requirement 12 PS Series array initializing 24 PS Series array group network recommendations 10 PS Series group listing accessible 27 managing access to 26 modifying access to 28 removing host access to 29 R Remote Setup Wizard Com
volume (continued) ASM/LE access to 22 displaying connections to 32 increasing size of 105 layout 48 managing 100 mount points referenced 49 partitioning 42, 113 recovery bin 76 setting configuration parameters 41 synchronous replication 77 thin-provisioning 102 thin-provisioning parameters 100 volume rethinning, See thin-provisioning volume slice 10 volume thin-provisioning on demand 98
