ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahq_5.4.0.1/rzahqbasicsingleserversupport.htm

66 lines
4.7 KiB
HTML
Raw Normal View History

2024-04-02 14:02:31 +00:00
<?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>Basic single server support</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" /><img src="delta.gif" alt="Start of change" />
<a name="rzahqbasicsingleserversupport"></a>
<h4 id="rzahqbasicsingleserversupport">Basic single server support</h4>
<p>To attach or host an xSeries&reg; or IBM&reg; BladeCenter&trade; server via iSCSI to an iSeries&trade;, hardware
must be installed in both the iSeries and the hosted system. The hardware
required at each end is an iSCSI host bus adapter (HBA) or iSCSI adapter.
These two adapters are connected via an Ethernet switch, using standard Ethernet
cables. The simplest form of the physical connection between a hosted system
and an iSeries server is illustrated in <a href="rzahqbasicsingleserversupport.htm#zahqfigiscsiatta">Figure 6</a>.</p>
<a name="zahqfigiscsiatta"></a>
<div class="fignone" id="zahqfigiscsiatta"><img src="delta.gif" alt="Start of change" /><span class="figcap">Figure 6. Single iSCSI attached server</span>
<div class="mmobj">
<img src="rzahq501.gif" alt="This image shows the network connections between i5/OS and the hosted system." /></div><img src="deltaend.gif" alt="End of change" /></div>
<p>The xSeries or IBM BladeCenter server known as the hosted system
has an initiator iSCSI HBA installed. This adapter has an Ethernet network
interface and it is connected via an Ethernet switch to the target iSCSI HBA
installed in the iSeries server. The hosted system is a diskless server.
The virtual disks and virtual removable media devices are hosted or provided
by the iSCSI HBA for iSeries. The SCSI commands to access these devices are
packaged in TCP/IP frames and travel from the hosted system to the iSCSI
HBA for iSeries over the Ethernet network. This mode of communication is known
as Internet SCSI or iSCSI.</p>
<p>The iSCSI attached servers are configured in i5/OS&trade; objects. For more information about these
objects, see <a href="rzahqsoftconcepts.htm#rzahqsoftconcepts">Software concepts</a>.</p>
<p>i5/OS can locate and manage remote systems by sending commands to the
service processor of the remote system over an Ethernet network. IBM Director is
used for these functions and must be installed and running on all partitions
that are connected to iSCSI attached host bus adapters (HBAs). For more information,
see <a href="rzahqdiscoveryandmanagement.htm#rzahqdiscoveryandmanagement">Remote server discovery and management</a>.</p>
<p>Two distinct networks are illustrated in <a href="rzahqbasicsingleserversupport.htm#zahqfigiscsiatta">Figure 6</a>.
The iSCSI network uses an isolated switch. The service processor connection
uses an external network (shared network). There does not have to be two distinct
networks. For example, the service processor connection could use the same
isolated switch as the iSCSI network. This is one way to secure the service
processor connection. However, the i5/OS LAN adapter would not be available for
other applications on the external network.</p>
<p>Both types of networks should be secured. For more information about security
for iSCSI attached servers, see <a href="rzahqsecurity.htm#rzahqsecurity">Security concepts</a>.</p><img src="deltaend.gif" alt="End of change" /><img src="deltaend.gif" alt="End of change" />
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>