74 lines
4.9 KiB
HTML
74 lines
4.9 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>Service processor connection</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="rzahqncserviceprocessorconnection"></a>
|
||
|
|
<h3 id="rzahqncserviceprocessorconnection">Service processor connection</h3>
|
||
|
|
<a name="wq15"></a>
|
||
|
|
<div class="notetitle" id="wq15">Note:</div>
|
||
|
|
<div class="notebody">This section pertains only to iSCSI attached systems.</div>
|
||
|
|
<p>This physical connection is required so that the hosting i5/OS™ can communicate
|
||
|
|
with the service processor of the hosted system. The connection can consist
|
||
|
|
of a simple, switched network or a more complex, routed network. Windows environment
|
||
|
|
on iSeries™ uses IBM® Director over this connection to manage the state of
|
||
|
|
the hosted system.</p>
|
||
|
|
<p>At one end of the connection is a LAN adapter or adapters controlled by i5/OS. This LAN adapter can still be available for other uses. The IP address
|
||
|
|
and other attributes of this adapter are controlled using standard i5/OS configuration
|
||
|
|
methods. Windows environment on iSeries does not configure this adapter. It
|
||
|
|
can can automatically discover the service processor using IBM Director and
|
||
|
|
one or more i5/OS TCP interfaces that are already configured.</p>
|
||
|
|
<p>At the other end of the connection is the service processor. The service
|
||
|
|
processor has its own Ethernet port and TCP/IP stack. This TCP/IP stack
|
||
|
|
is active whenever the server's power cord is plugged into an energized
|
||
|
|
AC outlet, even if the server is not in a powered on state. On certain xSeries® models, a single Ethernet port may be shared by Windows and a
|
||
|
|
particular type of service processor, known as the Baseboard Management Controller
|
||
|
|
(BMC). In this case, the same physical port on the hosted system provides
|
||
|
|
both the service processor connection and an external network connection.</p>
|
||
|
|
<p><span class="bold">DHCP server for the service processor</span>
|
||
|
|
<br />Setting
|
||
|
|
the IP address of the service processor may require an external DHCP server
|
||
|
|
on the network providing the service processor connection. The DHCP server
|
||
|
|
should be active before plugging the hosted system's power cord into
|
||
|
|
an energized AC outlet. (This DHCP server is distinct from the DHCP server
|
||
|
|
that is built into the i5/OS side of the iSCSI network to assist with iSCSI boot
|
||
|
|
of the hosted operating system.) For more information, see <a href="rzahqdynamicipaddressing.htm#rzahqdynamicipaddressing">Dynamic IP addressing (DHCP)</a>.</p>
|
||
|
|
<p><span class="bold">IP multicast</span>
|
||
|
|
<br />There are several options
|
||
|
|
that Windows environment on iSeries offers for discovering the service processor.
|
||
|
|
Note that the choices that provide the most automation require that the network
|
||
|
|
support IP multicast. Some switches and networks do not support IP multicast
|
||
|
|
by default. For more information, see <a href="rzahqspdiscoverymethods.htm#rzahqspdiscoverymethods">Service processor discovery methods</a>.</p>
|
||
|
|
<p><span class="bold">Performance and maximum transmission unit (MTU)</span>
|
||
|
|
<br />There
|
||
|
|
is not a requirement or advantage to having a high speed network or using
|
||
|
|
a large MTU for the service processor connection.</p>
|
||
|
|
<p><span class="bold">Security</span>
|
||
|
|
<br />The security capabilities of
|
||
|
|
your service processor hardware may affect your decision to use an isolated
|
||
|
|
network or a shared network to provide the service processor connection. For
|
||
|
|
more information, see <a href="rzahqconfigseccommwithsp.htm#rzahqconfigseccommwithsp">Configure service processor SSL</a>.</p><img src="deltaend.gif" alt="End of change" />
|
||
|
|
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
|
||
|
|
</body>
|
||
|
|
</html>
|