86 lines
5.6 KiB
HTML
86 lines
5.6 KiB
HTML
<?xml version="1.0" encoding="utf-8"?>
|
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
|
|
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
|
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-us">
|
|
<head>
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
|
<meta name="dc.language" scheme="rfc1766" content="en-us" />
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
|
<!-- US Government Users Restricted Rights -->
|
|
<!-- Use, duplication or disclosure restricted by -->
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
|
<meta name="dc.date" scheme="iso8601" content="2005-09-13" />
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1998, 2006" />
|
|
<meta name="security" content="public" />
|
|
<meta name="Robots" content="index,follow"/>
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
|
<title>Network server description</title>
|
|
<link rel="stylesheet" type="text/css" href="ibmidwb.css" />
|
|
<link rel="stylesheet" type="text/css" href="ic.css" />
|
|
</head>
|
|
<body>
|
|
<a id="Top_Of_Page" name="Top_Of_Page"></a><!-- Java sync-link -->
|
|
<script language = "Javascript" src = "../rzahg/synch.js" type="text/javascript"></script>
|
|
|
|
<img src="delta.gif" alt="Start of change" />
|
|
<a name="scnwsd"></a>
|
|
<h4 id="scnwsd">Network server description</h4>
|
|
<p>The network server description (NWSD) object shown in <a href="rzahqscattixaixs.htm#rzahqiscinosec">Figure 15</a> is
|
|
basically the same as described for <a href="rzahqscixsandixa.htm#ixsixaconf">Figure 14</a> except for the
|
|
following:</p>
|
|
<ul>
|
|
<li>It contains a reference to a remote system configuration object instead
|
|
of an iSeries™ hardware resource name.</li>
|
|
<li>Unlike an IXA attached server which uses one IXA card in the xSeries® system to
|
|
manage all of the SCSI and virtual Ethernet data flows, on an iSCSI attached
|
|
server solution both the iSeries and the xSeries can have multiple iSCSI host bus adapters
|
|
(HBAs). This allows multiple SCSI and virtual Ethernet data paths between
|
|
the iSeries and xSeries or IBM® BladeCenter™ systems, which can provide greater
|
|
bandwidth and connection redundancy.</li>
|
|
<li>You can define one or more storage paths. These storage paths reference
|
|
the NWSH objects that are associated with the iSCSI HBAs that are used by
|
|
the integrated server. You can choose which storage path is used for the
|
|
SCSI data flows for each virtual disk drive. By associating your virtual
|
|
disk drives with different storage paths, you can spread the overall server
|
|
SCSI data flow workload across the storage path iSCSI HBAs for greater bandwidth.</li>
|
|
<li>You can define a multi-path group, which is a subset of the configured
|
|
storage paths. You can then associate a virtual disk drive with the multi-path
|
|
group, instead of associating it with a specific storage path. Using the
|
|
multi-path group for a virtual disk drive has the advantage that if the iSCSI
|
|
HBA for one of the NWSHs in the multi-path group fails or the network connection
|
|
to the iSCSI HBA fails, the SCSI data flow workload for that virtual disk
|
|
drive is automatically routed to one of the other iSCSI HBAs that is configured
|
|
in the multi-path group. This provides connection redundancy and improves
|
|
availability.</li>
|
|
<li>You can define one or more virtual Ethernet paths. These virtual Ethernet
|
|
paths also reference the NWSH objects that are used by the integrated server.
|
|
You can choose which NWSH is used for each virtual Ethernet port that the
|
|
integrated server uses. By associating different virtual Ethernet ports with
|
|
different NWSHs, you can spread the overall server virtual Ethernet data flow
|
|
workload across the virtual Ethernet path iSCSI HBAs for greater bandwidth.</li>
|
|
<li>Just as with an IXS or IXA attached server, the iSCSI attached xSeries or IBM BladeCenter server
|
|
hardware is controlled by i5/OS™.
|
|
<ul>
|
|
<li>An iSCSI attached server is started and shut down the same as with an
|
|
IXS or IXA attached server (see <a href="rzahqscixsandixa.htm#ixsixaconf">Figure 14</a>), by varying on
|
|
or off the NWSD for that server.</li>
|
|
<li>For an iSCSI attached xSeries or IBM BladeCenter server, i5/OS communicates over an Ethernet network
|
|
with the service processor (SP) for the xSeries system or the IBM BladeCenter management
|
|
module for an IBM BladeCenter server to perform the start and shut down tasks.</li></ul>
|
|
<p>For server hardware power control, the main difference between the
|
|
IXS/IXA configurations and the iSCSI configuration is that for IXS or IXA
|
|
attached servers, the server hardware is identified by the iSeries hardware
|
|
resource name, while for iSCSI attached servers, the server hardware is identified
|
|
by the remote system configuration object.</p>
|
|
<a name="wq28"></a>
|
|
<div class="notetitle" id="wq28">Note:</div>
|
|
<div class="notebody">Since the xSeries or IBM BladeCenter server
|
|
that an iSCSI that an iSCSI attached server runs on is simply defined via
|
|
the remote system configuration name in the NWSD, it is easy to switch the
|
|
hardware that an iSCSI attached integrated server runs on. By changing the
|
|
remote system configuration name, the xSeries or IBM BladeCenter server that the existing NWSD is
|
|
booted on can be hot spared. For more information, see <a href="rzahqhotsparebetw.htm#rzahqhotsparebetw">Hot spare between server hardware</a>.</div></li></ul><img src="deltaend.gif" alt="End of change" />
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
|
</body>
|
|
</html>
|