Dell PowerVault MD3200i Deployment Guide - Page 59

Advanced, Target Portals, Discovery, etc/iscsi/iscsid.conf, linux/etc, iscsid.conf

Page 59 highlights

6 Click OK to exit the Advanced menu and click OK again to exit the Add Target Portals screen. 7 To exit the Discovery tab, click OK. If you plan to configure CHAP authentication, do not perform discovery on more than one iSCSI port at this point. Go to "Step 4: Configure Host Access" on page 60. If you do not plan to configure CHAP authentication, repeat step 1 thorough step 6 for all iSCSI ports on the storage array. If you are using Windows Server 2008 Core Version: 1 Set the iSCSI initiator service to start automatically: sc \\ config msiscsi start= auto 2 Start the iSCSI service: sc start msiscsi 3 Add a target portal: iscsicli QAddTargetPortal If you are using Red Hat® Enterprise Linux® 5, Red Hat Enterprise Linux 6, SUSE® Linux Enterprise Server 10, or SUSE Linux Enterprise Server 11: Configuration of the iSCSI initiator for Red Hat Enterprise Linux 5 and SUSE Linux Enterprise Server 10 SP1 distributions is done by modifying the /etc/iscsi/iscsid.conf file, which is installed by default when you install MDSM. You can edit the file directly, or replace the default file with a sample file included on the PowerVault MD3200i Series resource media. To use the sample file included on the media: 1 Save the default /etc/iscsi/iscsid.conf file by naming it to another name of your choice. 2 Copy the appropriate sample file from /linux/etc on the media to /etc/iscsi/iscsid.conf. 3 Rename the sample file to iscsid.conf. 4 Edit the following entries in the /etc/iscsi/iscsid.conf file: a Edit or verify that the node.startup = manual line is disabled. b Edit or verify that the node.startup = automatic line is enabled. This enables automatic startup of the service at boot time. Appendix-Manual Configuration 59

  • 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

Appendix—Manual Configuration
59
6
Click
OK
to exit the
Advanced
menu and click
OK
again to exit the
Add
Target Portals
screen.
7
To exit the
Discovery
tab, click
OK
.
If you plan to configure CHAP authentication
, do not perform discovery on
more than one iSCSI port at this point. Go to "Step 4: Configure Host
Access" on page 60.
If you do not plan to configure CHAP authentication
, repeat step 1 thorough
step 6 for all iSCSI ports on the storage array.
If you are using
Windows Server 2008 Core Versio
n:
1
Set the iSCSI initiator service to start automatically:
sc
\\<server_name>
config
msiscsi
start=
auto
2
Start the iSCSI service:
sc start msiscsi
3
Add a target portal:
iscsicli QAddTargetPortal
<IP_address_of_iSCSI_port_on_storage array>
If you are using
Red Hat
®
Enterprise Linux
®
5, Red Hat Enterprise Linux 6
,
SUSE
®
Linux Enterprise Server 10
,
or
SUSE Linux Enterprise Server 11
:
Configuration of the iSCSI initiator for Red Hat Enterprise Linux 5 and
SUSE Linux Enterprise Server 10 SP1 distributions is done by modifying the
/etc/iscsi/iscsid.conf
file, which is installed by default when you install
MDSM. You can edit the file directly, or replace the default file with a sample
file included on the PowerVault MD3200i Series resource media.
To use the sample file included on the media:
1
Save the default
/etc/iscsi/iscsid.conf
file by naming it to another name of
your choice.
2
Copy the appropriate sample file from
/linux/etc
on the media to
/etc/iscsi/iscsid.conf
.
3
Rename the sample file to
iscsid.conf
.
4
Edit the following entries in the
/etc/iscsi/iscsid.conf
file:
a
Edit or verify that the
node.startup = manual
line is disabled.
b
Edit or verify that the
node.startup = automatic
line is
enabled. This enables automatic startup of the service at boot time.