HP 3PAR RedHat and Oracle Linux Implementation Guide

vendor "3PARdata"
product "VV"
no_path_retry 12
features "0"
hardware_handler "0"
path_grouping_policy multibus
path_selector "round-robin 0"
rr_weight uniform
rr_min_io 100
path_checker tur
failback immediate
polling_interval 5
}
}
4. Run the multipath command for any name changes to be effective.
5. Verify that the multipathd daemon is enabled by the rc script to run on every host boot
up.
The following output shows that it is enabled for run-level 3, 4 and 5. Enable it appropriately
for your configuration.
# chkconfig --list multipathd
multipathd 0:off 1:off 2:off 3:on 4:on 5:on 6:off
6. Check that the appropriate rc scripts have been created for each run level. The start numbers
may not match those shown here.
# ls /etc/rc3.d/*multi*
/etc/rc3.d/S13multipathd
# ls /etc/rc5.d/*multi*
/etc/rc5.d/S13multipathd
Alternatively, you can use the chkconfig command to enable multipathing if it is not enabled:
# chkconfig multipathd on
Configuring CHAP for the iSCSI Host
Two CHAP authentication configurations are available: Host CHAP authentication, where the
HP 3PAR StoreServ Storage iSCSI target port authenticates the iSCSI Initiator host when it tries to
connect to it, and bidirectional (mutual) CHAP authentication, where both the iSCSI target and
host authenticate each other when the host tries to connect to the target.
You must create an iSCSI host definition on the HP 3PAR StoreServ Storage before setting and
configuring CHAP for the iSCSI host. See “Creating the iSCSI Host Definition” (page 21).
Setting the Host CHAP Authentication on the HP 3PAR StoreServ Storage
To set the host CHAP authentication, an iSCSI host definition must have been created on the
HP 3PAR StoreServ Storage, and the HP 3PAR OS CLI sethost initchap command must be
used to set the host CHAP secret.
Configuring CHAP for the iSCSI Host 83