Huawei SAN Storage How To - Configuring the i-SCSI Communication Protocol

Huawei SAN Storage – How To
Configuring the i-SCSI communication protocol
Huawei SAN Storage – How To :

In this tutorial we will see how to configure a connection between our i-SCSI SAN
(S2200T demo unit) and an application server running Windows 2012.
This activity is divided into 4 main topics:
- IP address configuration on the SAN i-SCSI port
- Configuration of the dedicated network card on the application server (Windows)
- Configuration of the i-SCSI Initiator, still on the application server
- Verify that the Initiator is recognized by the i-SCSI Target (SAN)

We assume that a very simple network configuration has been deployed between
servers and SAN: a simple direct network cable on a dedicated IP subnet, or through
a switch, essentially without routing. In case of more parallel i-SCSI connections,
the most simple way is to apply a not routed subnet to each connection pair.
If the link is routed, or the subnet is "busy" from other traffic, you can get a
performance degradation that, in a so delicate and otherwise simple environment,
is not desirable.
Now let's check the configuration of the SAN.
In our demo unit we have, for each controller, 4 ethernet ports dedicated to i-SCSI
protocol.

In figure one the four
controller A ports are
highlighted, with every detail
of the port H2, so as we can
see in Device Info by ISM.
In total, we have 8 ports that
can work in a variety of
configurations, including
redundancy and aggregation
of flows.
Figure 1

The summary of the i-SCSI ip parameters, and the ability to configure them, are
available in PORTS by ISM, under the tab iSCSI-Host-Ports. Figure 2 shows us only the
first 4 interfaces, all presenting the status of link-down as they are not yet
connected to the application server.
Figure 2

Now let's pass to the server
configuration (Windows).
As we previously
announced, and is better to
reserve one or more
interfaces to i-SCSI only
protocol.
Figure 3 shows us just one
of these interfaces already
with optimized protocols:
disable all but the only one
we need: IP V4
Figure 3

Figure 4 shows the detailed
configuration of IPV4: it is a classic
static IP configuration, strictly reduced
to the minimum necessary values, so
without a dafault gateway and without
DNS, since the traffic of this interface
should not roam the internet and must
not have other functions. All in all, the
presence of more default gateways, in
a windows environment, is not
desirable.
Figure 4

Once configured the IP on both sides of the connection, we can verify it, by, for
example, a simple PING command from server to SAN.
At this point, the IP configuration of both endpoints and is completed and verified:
let's pass to real i-scsi management.
Figure 5

The tool provided to us since a few
of Windows operating system
versions, is iSCSI Initiator. As shown
in Figure 6, is located between the
administration tools for Windows
2012, and essentially has not
changed compared to that of
Windows 2008 and Windows 2008 R2
Figure 6

Once launched, move to the
Configuration tab on the far right: This
page shows the default name with
which this server is presenting itself to
the rest of the i-SCSI worls, and,
frankly, it is a set of long words,
difficult to understand and difficult to
manage (remember that this name
must appear on ISM that, notoriously,
holds data in columns in very tight
spaces).
Figure 7

Can be very helpful to set a name that helps identify the server from the remote side
of the connection (i-SCSI target of SAN). Figure 8 exhibits a much explanatory example.
Figure 8

Now that we have verified our SAN is reachable, let's connect it.
In order to do this, let's click the TARGETS tab on the i-SCSI Initiator: here simply
type the IP address of our i-SCSI conterpart (the SAN), and then click Quick Connect
(Figure 9).
Figure 9

After a few seconds we get a
response equivalent to what is shown
in Figure 10: not very clear but you
can recognize that our Huawei
Oceanstor is responding.
Figure 10

Returning to the Targets tab and
expanding the column appropriately,
we can verify that the IP we wanted to
contact is online and responsive.
In case of multiple connections, you
have to repeat the procedure trying all
the IP remote targets, for which the
Figure 11 will show a row for each
connection.
Figure 11

Now the last verification: the SAN
has to be aware of our
connection: this is visible in the
Initiators in ISM.
The Identifier column shows just
the name of our server, clear and
understandeable,
as set in Figure 8.
Figure 12
For today is all. See you at next tutorial!

More needs?
See hints on www.ipmax.it
Or email us your questions to info_ipmax@ipmax.it

IPMAX is a Huawei Partner in Italy.
IPMAX is the ideal partner for companies seeking quality in products and services.
IPMAX guarantees method and professionalism to support its customers in selecting
technologies with the best quality / price ratio, in the design, installation,
commissioning and operation.
IPMAX srl
Via Ponchielli, 4
20063 Cernusco sul Naviglio (MI) – Italy
+39 02 9290 9171

Huawei SAN Storage How To - Configuring the i-SCSI Communication Protocol

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Similar to Huawei SAN Storage How To - Configuring the i-SCSI Communication Protocol

Similar to Huawei SAN Storage How To - Configuring the i-SCSI Communication Protocol (20)

More from IPMAX s.r.l.

More from IPMAX s.r.l. (9)

Recently uploaded

Recently uploaded (20)

Huawei SAN Storage How To - Configuring the i-SCSI Communication Protocol