## 3.7.2 Topology and IP addressing 

See 3.5, “Planning IP connectivity” on page 51 for examples of topology and addressing schemes that can be used for iSCSI connectivity. 

If you plan to use node’s 1 Gbps Ethernet ports for iSCSI host attachment, dedicate Ethernet port one for the SAN Volume Controller management and port two for iSCSI use. This way, port two can be connected to a separate network segment or virtual local area network (VLAN) dedicated to iSCSI traffic. 

Note:  Ethernet link aggregation (port trunking) or channel bonding  for the SAN Volume Controller nodes’ Ethernet ports is not supported for the 1 Gbps ports. 

## 3.7.3 General preferences 

This section covers general preferences related to iSCSI. 

## Planning for host attachments 

An iSCSI client, which is known as an iSCSI initiator , sends SCSI commands over an IP network to an iSCSI target. A single iSCSI initiator or iSCSI target is called an iSCSI node . 

You can use the following types of iSCSI initiators in host systems: 

GLYPH<SM590000> Software initiator: Available for most operating systems (OS), including AIX, Linux, and Windows. 

GLYPH<SM590000> Hardware initiator: Implemented as a network adapter with an integrated iSCSI processing unit, which is also known as an  iSCSI HBA . 

Make sure that iSCSI initiators, targets, or both that you plan to use are supported. Use the following sites for reference: 

GLYPH<SM590000> IBM SAN Volume Controller V8.2 Support Matrix: 

http://www.ibm.com/support/docview.wss?uid=ssg1S1003658 

GLYPH<SM590000> IBM Knowledge Center for IBM SAN Volume Controller: 

https://www.ibm.com/support/knowledgecenter/STPVGU 

GLYPH<SM590000> IBM System Storage Interoperation Center (SSIC) 

https://www.ibm.com/systems/support/storage/ssic/interoperability.wss 

## iSCSI qualified name 

A SAN Volume Controller cluster can provide up to eight iSCSI targets, one per node. Each SAN Volume Controller node has its own IQN, which, by default, is in the following form: 

iqn.1986-03.com.ibm:2145.< clustername >.< nodename > 

An alias string can also be associated with an iSCSI node. The alias enables an organization to associate a string with the iSCSI name. However, the alias string is not a substitute for the iSCSI name. 

Important:  The cluster name and node name form part of the IQN. Changing any of them might require reconfiguration of all iSCSI nodes that communicate with the SAN Volume Controller. 

