82 lines
5.3 KiB
HTML
82 lines
5.3 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>Special considerations for iSCSI attached systems</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="rzahqtrouspecialconsiscsi"></a>
|
||
|
|
<h4 id="rzahqtrouspecialconsiscsi">Special considerations for iSCSI attached systems</h4>
|
||
|
|
<p>For iSCSI attached servers, the server hardware state is used to control
|
||
|
|
access to the hardware and ensure that only one NWSD is using the hardware
|
||
|
|
at any point in time. When starting (varying on) the NWSD, the specific behavior
|
||
|
|
for an iSCSI attached server depends on the type of service processor that
|
||
|
|
the server has:</p>
|
||
|
|
<ul>
|
||
|
|
<li>For xSeries® servers with a BMC service processor, the hardware must initially
|
||
|
|
be in a powered off state.</li>
|
||
|
|
<li>For xSeries server with an RSA II or an IBM® BladeCenter™ with a Management Module, the hardware
|
||
|
|
must not be booted to an operating system (for example DOS or Windows). An xSeries system that is sitting at the insert diskette prompt is allowed,
|
||
|
|
but the system will wait for a period of time to ensure that no other system
|
||
|
|
is attempting to use the system.</li></ul>
|
||
|
|
<p>Otherwise, the start operation will fail. When shutting down (varying
|
||
|
|
off) the NWSD, the NWSD's xSeries or BladeCenter blade hardware will be left in
|
||
|
|
a powered off state.</p>
|
||
|
|
<p>In addition to the case when an NWSD is currently using the server hardware,
|
||
|
|
there are other possible reasons that the server hardware is in a powered
|
||
|
|
on state. For example, the server hardware may have been powered on to perform
|
||
|
|
hardware setup, such as loading firmware or changing BIOS settings. Another
|
||
|
|
example is when the server operating system has encountered an unrecoverable
|
||
|
|
error, resulting in a failed server, but leaving the hardware in a powered
|
||
|
|
on state. For these cases, starting an NWSD in the normal way may fail because
|
||
|
|
the server hardware is not in a powered off state or the service processor
|
||
|
|
indicates that an operating system is still running.</p>
|
||
|
|
<p>There are a couple of ways to recover from this:</p>
|
||
|
|
<ul>
|
||
|
|
<li>If an NWSD is currently using the hardware, but the server operating system
|
||
|
|
failed, then try shutting down the server. In most cases, this will power
|
||
|
|
off the server hardware and make it available to the same or another NWSD.
|
||
|
|
If shutting down the NWSD does not resolve the problem try the method described
|
||
|
|
below.</li>
|
||
|
|
<li>When starting an NWSD, there is a reset system option to force the server
|
||
|
|
hardware to be reset during the start of the NWSD. You can use this option
|
||
|
|
to start an NWSD that uses server hardware that is in a state that would normally
|
||
|
|
cause the start (vary on) of the server to fail.</li></ul>
|
||
|
|
<div class="attention"><span class="attentiontitle">Attention: </span>Use the reset system option only when you are sure that the server
|
||
|
|
hardware is not currently being used by another NWSD. If you use the reset
|
||
|
|
system option to start an NWSD when there is another NWSD that is running
|
||
|
|
on the hardware, the other NWSD will fail and can incur data loss or corruption.</div>
|
||
|
|
<p>To reset a remote system using iSeries™ Navigator, follow these steps:</p>
|
||
|
|
<ol type="1">
|
||
|
|
<li>Expand <span class="bold">Integrated Server Administration</span>.</li>
|
||
|
|
<li>Expand <span class="bold">Servers</span>.</li>
|
||
|
|
<li>Right-click a server from the list available.</li>
|
||
|
|
<li>Select <span class="bold">Start with options...</span></li>
|
||
|
|
<li>Check the <span class="bold">Reset remote system</span> option.</li>
|
||
|
|
<li>Click <span class="bold">Start</span>. A confirmation panel is shown.</li>
|
||
|
|
<li>Click <span class="bold">Start</span> on the confirmation panel to start and
|
||
|
|
reset the remote system.</li></ol>
|
||
|
|
<p>If you want to use a CL command, see the Reset system (RESETSYS) keyword
|
||
|
|
on the Vary Configuration (VRYCFG) command.</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>
|