19
Figure 9.
Renaming network bonds
The iSCSI SAN Bond 1 interface is now ready to be used. In order for the bond’s IP address to be
recognized, you can reboot the XenServer host; alternatively, use the
host-management-reconfigure
command.
Connecting to an iSCSI volume
While HP StorageWorks iSCSI volumes were created in a previous section, no access was assigned
to those volumes.
Before a volume can be recognized by a XenServer host as an SR, you must use the CMC to define
the authentication method to be assigned to this volume. The following authentication methods are
supported on XenServer hosts:
IQN
– You can assign a volume based on an IQN definition. Think of this as a one-to-one
relationship, with one rule for one host.
CHAP
– Challenge Handshake Authentication Protocol (CHAP) provides a mechanism for defining a
user name and secret password credential to ensure that access to a particular iSCSI volume is
appropriate. Think of this as a one-to-many relationship, with one rule for many hosts.
XenServer hosts only support one -way CHAP credential access.
Determining or changing the host’s IQN
Each XenServer host has been assigned a default IQN that you can change, if desired; in addition,
each volume has been assigned a unique iSCSI name during its creation. Although specific naming is
not required within an iSCSI SAN, all IQNs must be unique from initiator to target.
A XenServer host’s IQN can be found via XenCenter’s
General
tab, as shown in Figure 10. Here, the
IQN of XenServer host
XenServer-55b-02
is
iqn.2009-06.com.example:e834bedd
.