44
-
To servers equipped with iSCSI HBA – preferably a hardware TOE (TCP/IP Offload
Engine) card, and then to client stations with an Ethernet NIC or iSCSI HBA.
-
The system presents its logical volumes through SCSI-like IDs and LUNs. These RAID
volumes then appear as iSCSI targets through the network.
NOTE
Even though iSCSI initiator software is a cost-effective way of building an iSCSI
SAN, software initiator adds additional workload to the server CPU. It is
recommended to apply iSCSI HBAs that come with TCP/IP offload engines in order to
reduce overhead.
Network & Host Connection Topologies
The iSCSI host ports connect to Ethernet network devices and iSCSI initiators that comply
with the IETF iSCSI standard (RFC 3720). Network connection of the iSCSI ports is flexible.
The use of network connecting devices, subnet, Name Servers, or iSCSI management
software can vary from case to case. In the following sections, configuration diagrams will be
provided to illustrate the possible uses of the PS system in an iSCSI network.
Note that host NIC ports and the storage system’s iSCSI host ports must be configured into
the same subnet.
Please note the following:
-
Use the Ethernet management port for management purposes only, i.e., PAC Management
Software or telnet console. This Ethernet management port is not used for I/O transactions.
-
Configurations such as subnet or Virtual LAN can separate iSCSI host links, decrease
overhead, and eliminate the impact of link failure.
-
Multiple arrays or logical partitions can be created and made available separately through
different IDs or LUN numbers on the host ports. Usually, a RAID5 logical drive of eight (8)
members often brings optimal array performance.
NOTE
If you are using Microsoft’s software initiator, please de-select the embedded MPIO
function when installing the software, as the MPIO selection creates conflicts with
MPIO driver.
