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

Enabling iSCSI Offload on HIT/Linux, Step 1: Set Up and Verify Your Configuration, Step 2: Con

Page 118 highlights

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. Topics: • Step 1: Set Up and Verify Your Configuration • Step 2: Configure the Network Interfaces • Step 3: Configure ehcmd to Use the Offload iSCSI Initiator • Step 4: Discover iSCSI Targets • Step 5: Logging In to Additional Targets Step 1: Set Up and Verify Your Configuration For onboard network interfaces, you might need to use a physical key to enable the functionality. For expansion cards, verify that the functionality is enabled by firmware. If the Broadcom iSCSI Offload Engine (ISOE) functionality is not enabled, messages similar to the following will appear in the /var/log/ messages file: Jan 14 17:38:01 rh6-910 kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.1 (Mar 24, 2017) Jan 14 17:38:01 rh6-910 kernel: iscsi: registered transport (bnx2i) Jan 14 17:38:01 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth3 Jan 14 17:38:03 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth2 Jan 14 17:38:05 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth1 Jan 14 17:38:07 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth0 When enabled, messages similar to the following will display: Jan 14 18:13:55 rh6-910 kernel: Broadcom NetXtreme II iSCSI Driver bnx2i v2.1.1 (Mar 24, 2017) Jan 14 18:13:55 rh6-910 kernel: iscsi: registered transport (bnx2i) Jan 14 18:13:55 rh6-910 kernel: bnx2: eth0: using MSIX Jan 14 18:13:55 rh6-910 kernel: bnx2i [01:00.00]: ISCSI_INIT passed Step 2: Configure the Network Interfaces Network interfaces are created by iscsiadm for each Broadcom iSCSI interface. For example: # iscsiadm -m iface default tcp,,,, iser iser,,,, bnx2i.00:00:00:00:00:00 bnx2i,00:00:00:00:00:00,,, bnx2i.a4:ba:db:38:8b:42 bnx2i,a4:ba:db:38:8b:42,,, bnx2i.a4:ba:db:38:8b:40 bnx2i,a4:ba:db:38:8b:40,,,

  • 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

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.
Topics:
Step 1: Set Up and Verify Your Configuration
Step 2: Configure the Network Interfaces
Step 3: Configure ehcmd to Use the Offload iSCSI Initiator
Step 4: Discover iSCSI Targets
Step 5: Logging In to Additional Targets
Step 1: Set Up and Verify Your Configuration
For onboard network interfaces, you might need to use a physical key to enable the functionality. For expansion cards, verify that the
functionality is enabled by firmware.
If the Broadcom iSCSI Offload Engine (ISOE) functionality is not enabled, messages similar to the following will appear in the
/var/log/
messages
file:
Jan 14 17:38:01 rh6-910 kernel: Broadcom NetXtreme II
iSCSI Driver bnx2i v2.1.1 (Mar 24, 2017)
Jan 14 17:38:01 rh6-910 kernel: iscsi: registered transport (bnx2i)
Jan 14 17:38:01 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth3
Jan 14 17:38:03 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth2
Jan 14 17:38:05 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth1
Jan 14 17:38:07 rh6-910 kernel: bnx2i: iSCSI not supported, dev=eth0
When enabled, messages similar to the following will display:
Jan 14 18:13:55 rh6-910 kernel: Broadcom NetXtreme II
iSCSI Driver bnx2i v2.1.1 (Mar 24, 2017)
Jan 14 18:13:55 rh6-910 kernel: iscsi: registered transport (bnx2i)
Jan 14 18:13:55 rh6-910 kernel: bnx2: eth0: using MSIX
Jan 14 18:13:55 rh6-910 kernel: bnx2i [01:00.00]: ISCSI_INIT passed
Step 2: Configure the Network Interfaces
Network interfaces are created by
iscsiadm
for each Broadcom iSCSI interface. For example:
# iscsiadm -m iface
default tcp,<empty>,<empty>,<empty>,<empty>
iser iser,<empty>,<empty>,<empty>,<empty>
bnx2i.00:00:00:00:00:00 bnx2i,00:00:00:00:00:00,<empty>,<empty>,<empty>
bnx2i.a4:ba:db:38:8b:42 bnx2i,a4:ba:db:38:8b:42,<empty>,<empty>,<empty>
bnx2i.a4:ba:db:38:8b:40 bnx2i,a4:ba:db:38:8b:40,<empty>,<empty>,<empty
Broadcom iSCSI offload engines have two MAC addresses per physical network interface: one for TCP-IP and one for ISOE. In the
following examples, the system was configured with two Broadcom network interfaces whose TCP-IP MAC addresses were listed by
ifconfig
.
#ifconfig
eth2 Link encap:Ethernet HWaddr A4:BA:DB:38:8B:3F
inet addr:x.x.x.x Bcast:x.x.x.z Mask:255.255.254.0
B
118
Enabling iSCSI Offload on HIT/Linux