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

Multipath Device Configuration, Traditional Multipath Device Configurations

Page 33 highlights

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.eth2_0 tcp,00:1B:21:46:5E:18,,, eql.eth2_1 tcp,00:1B:21:46:5E:18,,, eql.eth3_0 tcp,00:1B:21:46:5E:19,,, eql.eth3_1 tcp,00:1B:21:46:5E:19,,, iser iser,,,, To avoid interrupting access to any iSCSI storage, these additional iSCSI interfaces will be left in place if the HIT/Linux software is ever uninstalled. Multipath Device Configuration When you configure multipath device I/O, a mounted volume on a host is shown as a single disk. MPIO configuration uses multiple iSCSI sessions to the SAN volume to provide load balancing and ensure that I/O operations, such as writing data to a volume, succeed even if there is a network error. Traditional Multipath Device Configurations Traditional multipath configurations are implemented as a single tier of Device Mapper multipath devices. These configurations spread I/O sent to the multipath device to the constituent SCSI disk (SD) block devices. Multipath Configuration A PS Series volume can have data spread across multiple group members. Multipath device configuration in HIT/Linux improves performance over standard Linux multipathing by ensuring the host has iSCSI sessions to each member. Using information about the volume layout, it routes each I/O directly to the destination group member, reducing the amount of I/O forwarding that is necessary between members. HIT/Linux includes two components that use this configuration: • The EqualLogic Host Connection Manager daemon (ehcmd) monitors the iSCSI session state and the configuration of the Linux server and PS Series group. Running in the background, ehcmd uses the Open-iSCSI management tool (iscsiadm) to add, remove, or modify iSCSI sessions to maintain optimal iSCSI sessions, and gathers information on the volume layout from the PS Series group. • A loadable kernel module, dm-switch, which implements a new Device Mapper target to the multipath devices. Based on the volume layout on the group members, the dm-switch module routes each I/O to the optimal path to the PS Series group. The result is a two-tier device structure for each volume with multiple multipath devices: one for each member containing a portion of the volume and a switch device on top of the multipath devices. The following figure shows the relevant components in the storage stack. Configuring Multipath I/O Devices 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127

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,<empty>,<empty>,<empty>,<empty>
eql.eth0_0 tcp,00:26:B9:3A:6B:9E,<empty>,<empty>,<empty>
eql.eth0_1 tcp,00:26:B9:3A:6B:9E,<empty>,<empty>,<empty>
eql.eth1_0 tcp,00:26:B9:3A:6B:9F,<empty>,<empty>,<empty>
eql.eth1_1 tcp,00:26:B9:3A:6B:9F,<empty>,<empty>,<empty>
eql.eth2_0 tcp,00:1B:21:46:5E:18,<empty>,<empty>,<empty>
eql.eth2_1 tcp,00:1B:21:46:5E:18,<empty>,<empty>,<empty>
eql.eth3_0 tcp,00:1B:21:46:5E:19,<empty>,<empty>,<empty>
eql.eth3_1 tcp,00:1B:21:46:5E:19,<empty>,<empty>,<empty>
iser iser,<empty>,<empty>,<empty>,<empty>
To avoid interrupting access to any iSCSI storage, these additional iSCSI interfaces will be left in place if the HIT/Linux software is ever
uninstalled.
Multipath Device Configuration
When you configure multipath device I/O, a mounted volume on a host is shown as a single disk. MPIO configuration uses multiple iSCSI
sessions to the SAN volume to provide load balancing and ensure that I/O operations, such as writing data to a volume, succeed even if
there is a network error.
Traditional Multipath Device Configurations
Traditional multipath configurations are implemented as a single tier of Device Mapper multipath devices. These configurations spread I/O
sent to the multipath device to the constituent SCSI disk (SD) block devices.
Multipath Configuration
A PS Series volume can have data spread across multiple group members. Multipath device configuration in HIT/Linux improves
performance over standard Linux multipathing by ensuring the host has iSCSI sessions to each member. Using information about the
volume layout, it routes each I/O directly to the destination group member, reducing the amount of I/O forwarding that is necessary
between members.
HIT/Linux includes two components that use this configuration:
The EqualLogic Host Connection Manager daemon (ehcmd) monitors the iSCSI session state and the configuration of the Linux server
and PS Series group. Running in the background, ehcmd uses the Open-iSCSI management tool (iscsiadm) to add, remove, or modify
iSCSI sessions to maintain optimal iSCSI sessions, and gathers information on the volume layout from the PS Series group.
A loadable kernel module,
dm-switch
, which implements a new Device Mapper target to the multipath devices. Based on the volume
layout on the group members, the
dm-switch
module routes each I/O to the optimal path to the PS Series group.
The result is a two-tier device structure for each volume with multiple multipath devices: one for each member containing a portion of the
volume and a switch device on top of the multipath devices.
The following figure shows the relevant components in the storage stack.
Configuring Multipath I/O Devices
33