232 lines
14 KiB
HTML
232 lines
14 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 lang="en-us" xml:lang="en-us">
|
||
|
<head>
|
||
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2005" />
|
||
|
<meta name="DC.rights.owner" content="(C) Copyright IBM Corporation 2005" />
|
||
|
<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))' />
|
||
|
<meta name="DC.Type" content="task" />
|
||
|
<meta name="DC.Title" content="Shutting down Linux servers" />
|
||
|
<meta name="abstract" content="This topic discusses the multiple methods to shut down integrated Linux servers." />
|
||
|
<meta name="description" content="This topic discusses the multiple methods to shut down integrated Linux servers." />
|
||
|
<meta name="DC.Relation" scheme="URI" content="rzau9400op.htm" />
|
||
|
<meta name="DC.Format" content="XHTML" />
|
||
|
<meta name="DC.Identifier" content="rzau9shutdownlinux" />
|
||
|
<meta name="DC.Language" 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. -->
|
||
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
<title>Shutting down Linux servers</title>
|
||
|
</head>
|
||
|
<body id="rzau9shutdownlinux"><a name="rzau9shutdownlinux"><!-- --></a>
|
||
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
<h1 class="topictitle1">Shutting down Linux servers</h1>
|
||
|
<div><p>This topic discusses the multiple methods to shut down integrated Linux<sup>®</sup> servers.</p>
|
||
|
<div class="section"><p>Just as starting Linux servers can be accomplished in multiple
|
||
|
ways, so can stopping Linux servers. In this section we cover ways to shut
|
||
|
down Linux servers,
|
||
|
and unique situations that arise in an integrated environment.</p>
|
||
|
<p>You must
|
||
|
shut down your Linux servers before performing <span class="keyword">i5/OS™</span> system
|
||
|
tasks such as:</p>
|
||
|
<ul><li>Backing up statically linked storage spaces. Statically linked storage
|
||
|
spaces can only be backed up when Linux servers are shut down.</li>
|
||
|
<li>Putting an <span class="keyword">i5/OS</span> partition
|
||
|
into restricted state. When you end <span class="keyword">i5/OS</span> to
|
||
|
restricted state, the iSeries™ can only be accessed through the console.
|
||
|
If you put your iSeries into
|
||
|
restricted state by ending all subsystems immediately, your integrated Linux servers
|
||
|
are not automatically shut down. Because you normally put <span class="keyword">i5/OS</span> into
|
||
|
restricted state to perform a backup, you need to shut down the Linux servers
|
||
|
in order to back up their components. If a server is running, components such
|
||
|
as storage spaces are locked, and excluded from the back up. Therefore, you
|
||
|
should shut down your integrated servers in a controlled manner before putting <span class="keyword">i5/OS</span> into restricted state.</li>
|
||
|
<li>Performing a complete system backup. Performing a complete system save
|
||
|
using option 21 on the Save menu is an easy way to ensure that you have a
|
||
|
complete backup of your iSeries system, including your integrated Linux servers.
|
||
|
Option 21 on the Save menu has an option that allows you to automatically
|
||
|
shut down integrated servers before starting a backup. To set this option:<ol><li>Type go save on the <span class="keyword">i5/OS</span> command
|
||
|
line. Press <span class="uicontrol">Enter</span>.</li>
|
||
|
<li>Type <kbd class="userinput">21</kbd>, press <span class="uicontrol">Enter</span>.</li>
|
||
|
<li>You see the Save the Entire System display. Press <span class="uicontrol">Enter</span>.</li>
|
||
|
<li>On the Specify Command Defaults display there is an option called “Vary
|
||
|
off network servers”. This option defaults to <var class="varname">*NONE</var>, which
|
||
|
does not shut down integrated servers. To ensure that integrated Linux servers
|
||
|
are shut down before the backup starts, specify <kbd class="userinput">*ALL</kbd>.</li>
|
||
|
<li>Fill out the other options. Press <span class="uicontrol">Enter</span> to start
|
||
|
the backup.</li>
|
||
|
</ol>
|
||
|
</li>
|
||
|
<li>Powering down the iSeries. It is strongly recommend that you shut down
|
||
|
your servers in a controlled manner before powering down the iSeries using
|
||
|
the Power Down System (PWRDWNSYS) command. </li>
|
||
|
</ul>
|
||
|
<div class="important"><span class="importanttitle">Important:</span> Always shut down your integrated Linux servers
|
||
|
before you put <span class="keyword">i5/OS</span> into
|
||
|
restricted state, and prior to powering down the iSeries. Otherwise you might lose data
|
||
|
or corrupt the Linux operating system.</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div>
|
||
|
<div class="familylinks">
|
||
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzau9400op.htm" title="This topic introduces i5/OS operations.">i5/OS operations</a></div>
|
||
|
</div>
|
||
|
</div><div class="nested1" xml:lang="en-us" id="rzau9shutdownlinuxinav"><a name="rzau9shutdownlinuxinav"><!-- --></a><h2 class="topictitle2">Shut down a single Linux server using iSeries Navigator</h2>
|
||
|
<div><div class="section">To shut down a single Linux server using iSeries Navigator:</div>
|
||
|
<ol><li><span>Click <span class="uicontrol">Servers</span> under <strong>Integrated Server
|
||
|
Administration</strong>.</span></li>
|
||
|
<li><span>Right-click the server you wish to shut down.</span></li>
|
||
|
<li><span>Select <span class="uicontrol">Shut Down</span> or <span class="uicontrol">Shut Down
|
||
|
and Restart</span>.</span></li>
|
||
|
<li><span>You see a shut down confirmation window. Click <span class="uicontrol">Shut
|
||
|
Down</span>.</span></li>
|
||
|
</ol>
|
||
|
<div class="section">After a few moments you should see the server status change to <tt class="msgph">Shutting
|
||
|
down</tt>. The status automatically changes to <tt class="msgph">Shut down</tt> when
|
||
|
the server is completely shut down. You do not need to refresh the window.</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="rzau9shutdownlinuxinavmult"><a name="rzau9shutdownlinuxinavmult"><!-- --></a><h2 class="topictitle2">Shut down multiple Linux servers using iSeries Navigator</h2>
|
||
|
<div><div class="section"><p>To shut down all integrated servers simultaneously select one
|
||
|
of the following methods:</p>
|
||
|
<ul><li>Right-click Servers in the left pane and select <span class="uicontrol">Shut down all</span>.</li>
|
||
|
<li>Click <span class="uicontrol">Shut down all integrated servers</span> in the Taskpad
|
||
|
pane.</li>
|
||
|
</ul>
|
||
|
<p>To shut down selected servers simultaneously, hold down the control
|
||
|
key (Ctrl) and click each of the servers you want shut down. Then right-click
|
||
|
one of the selected servers and click <span class="uicontrol">Shut down</span>. </p>
|
||
|
<p>Because
|
||
|
of interdependencies between servers, you might wish to shut down the servers
|
||
|
in a specific order. If you want to do this automatically, see <a href="#rzau9shutdownlinuxcl">Shut down a single Linux servers using CL commands</a>.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="rzau9shutdownlinuxcl"><a name="rzau9shutdownlinuxcl"><!-- --></a><h2 class="topictitle2">Shut down a single Linux servers using CL commands</h2>
|
||
|
<div><div class="section"><p>To shut down a single Linux server from an <span class="keyword">i5/OS</span> command
|
||
|
line, select one of the following CL commands.</p>
|
||
|
<dl><dt class="dlterm">WRKCFGSTS</dt>
|
||
|
<dd><ol><li>1. Type <kbd class="userinput">WRKCFGSTS *NWS</kbd>. Press <span class="uicontrol">Enter</span>.</li>
|
||
|
<li>Type <kbd class="userinput">2</kbd> in the Opt column next to the network server
|
||
|
description (NWSD) that you want to vary off. Press <span class="uicontrol">Enter</span>.</li>
|
||
|
</ol>
|
||
|
<p>To shut down multiple Linux servers using the WRKCFGSTS command,
|
||
|
simply type <kbd class="userinput">2</kbd> in the Opt column next to all the network
|
||
|
server descriptions (NWSDs) that you want to vary off. Press <span class="uicontrol">Enter</span>.</p>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
<dl><dt class="dlterm">VRYCFG</dt>
|
||
|
<dd><ol><li>Type <kbd class="userinput">VRYCFG</kbd>. Press <span class="uicontrol">F4</span>.</li>
|
||
|
<li>Enter the following parameters:<ul><li>The NWSD that you want to vary off.</li>
|
||
|
<li>The status: <kbd class="userinput">*OFF</kbd>. </li>
|
||
|
</ul>
|
||
|
</li>
|
||
|
<li>Press <span class="uicontrol">Enter</span>.</li>
|
||
|
</ol>
|
||
|
<p>Here is an example:</p>
|
||
|
<pre>VRYCFG CFGOBJ(nwsd-name) CFGTYPE(*NWS) STATUS(*OFF)</pre>
|
||
|
<p>To
|
||
|
shut down multiple Linux servers using the VRYCFG command, simply list
|
||
|
all the network server descriptions (NWSDs) that you want to vary off in the
|
||
|
CFGOBJ parameter. Press <span class="uicontrol">Enter</span>. For example:</p>
|
||
|
<pre>VRYCFG CFGOBJ(nwsd-name1 nwsd-name2 nwsd-name3) CFGTYPE(*NWS) STATUS(*OFF)</pre>
|
||
|
</dd>
|
||
|
</dl>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="rzau9shuddownlinuxcon"><a name="rzau9shuddownlinuxcon"><!-- --></a><h2 class="topictitle2">Shut down Linux servers from the Linux console</h2>
|
||
|
<div><div class="section"><p>Every Linux server can be shut down from the Linux console
|
||
|
by entering the command <strong>shutdown -h now</strong>. The Linux operating
|
||
|
system shuts down but the NWSD is still considered to be varied on.</p>
|
||
|
<p>The
|
||
|
WRKCFGSTS command shows the NWSD with a status of SHUTDOWN, and the status
|
||
|
of the communications objects under it are FAILED. This is normal for servers
|
||
|
that are shut down from the console. On the WRKCFGSTS *NWS display you can
|
||
|
enter a <kbd class="userinput">2</kbd> next to the NWSD to complete the vary off. </p>
|
||
|
<p>You
|
||
|
can also shut down and restart an integrated Linux server from the console by entering
|
||
|
the appropriate command. You often need to restart the server after installing
|
||
|
new software or reconfiguring the operating system. In this case you do not
|
||
|
need to restart Linux from the <span class="keyword">i5/OS</span> side.</p>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="rzau9shutdownxservercon"><a name="rzau9shutdownxservercon"><!-- --></a><h2 class="topictitle2">Shut down xSeries servers from the Linux console</h2>
|
||
|
<div><div class="section"><p>Shutting down a Linux server that is running on an Integrated xSeries<sup>®</sup> Adapter-attached xSeries from
|
||
|
the Linux console
|
||
|
is a special case. In this case you should not shut Linux down through
|
||
|
the Linux console.
|
||
|
The reason for this is that when you shut down an integrated Linux server
|
||
|
in this way, the xSeries server is turned off completely. This causes
|
||
|
the Integrated xSeries Adapter
|
||
|
to lose power and stop communicating over the HSL loop. The System Licensed
|
||
|
Internal Code (SLIC) on the iSeries interprets this as one of its towers (the
|
||
|
Integrated xSeries Adapter-attached xSeries in
|
||
|
this case) having been turned off, and removed from the HSL loop. The iSeries goes
|
||
|
into HSL recovery. The other iSeries towers in the loop should remain unaffected
|
||
|
because data flows both ways around the loop, and the other towers still have
|
||
|
a connection to the iSeries system unit. But if multiple Integrated xSeries Adapter-based
|
||
|
integrated servers are shut down from the Linux console, towers that are cabled
|
||
|
between the shut down servers on the HSL loop become isolated and no longer
|
||
|
have a connection to the iSeries system unit. If the isolated towers contain
|
||
|
disk units, the iSeries terminates
|
||
|
abnormally. Also, if the loop contains a migration tower, shutting down a
|
||
|
single Integrated xSeries Adapter-based server from the console can
|
||
|
also bring down the iSeries because data can only flow one way around
|
||
|
the HSL loop to a migration tower. </p>
|
||
|
<p>For integrated Linux servers
|
||
|
running on Integrated xSeries Adapter-attached xSeries machines, the correct way to
|
||
|
shut down is from iSeries Navigator or the <span class="keyword">i5/OS</span> command
|
||
|
line. </p>
|
||
|
<p>For more information on HSL configuration, search for redp-3652
|
||
|
at the following Web site: </p>
|
||
|
<p><a href="http://www.redbooks.ibm.com/" target="_blank">http://www.redbooks.ibm.com/</a> <img src="www.gif" alt="Link outside information center" /></p>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="rzau9shutdownforce"><a name="rzau9shutdownforce"><!-- --></a><h2 class="topictitle2">Shut down Linux servers by forcing a shut down</h2>
|
||
|
<div><div class="section"><p>When you issue a shut down command to an integrated Linux server
|
||
|
from iSeries Navigator
|
||
|
or an <span class="keyword">i5/OS</span> command line,
|
||
|
the shut down command is passed to the server to enable it to shut itself
|
||
|
down cleanly. By default, <span class="keyword">i5/OS</span> waits
|
||
|
15 minutes (900 seconds) before it performs a forced shut down of an integrated Linux server
|
||
|
if the server has not already shut itself down. If you want to change this
|
||
|
default value, do the following steps:</p>
|
||
|
</div>
|
||
|
<ol><li><span>Shut down the Linux server.</span></li>
|
||
|
<li><span>On an <span class="keyword">i5/OS</span> command
|
||
|
line enter the Change Network Server Description (CHGNWSD) command and press <span class="uicontrol">F4</span>.</span></li>
|
||
|
<li><span>Scroll down to the Shutdown time-out (SHUTDTIMO) parameter and
|
||
|
enter the new default value. Press <span class="uicontrol">Enter</span>.</span></li>
|
||
|
<li><span>Restart the server.</span></li>
|
||
|
</ol>
|
||
|
</div>
|
||
|
</div>
|
||
|
<div class="nested1" xml:lang="en-us" id="rzau9shutdownpower"><a name="rzau9shutdownpower"><!-- --></a><h2 class="topictitle2">Shut down Linux servers by powering down the iSeries</h2>
|
||
|
<div><div class="section"><p>It is strongly recommended that you do not power down your <span class="keyword">i5/OS</span> partition when Linux servers
|
||
|
are active. When the Power Down System (PWRDWNSYS) *IMMED command is issued, <span class="keyword">i5/OS</span> does not try to shut down
|
||
|
any active integrated Linux servers. When the iSeries powers down it cuts power to
|
||
|
the Linux servers.
|
||
|
There is a possibility of data corruption if the servers suffer a forced shut
|
||
|
down in this way. Always shut down your Linux servers cleanly prior to issuing
|
||
|
the PWRDWNSYS command.</p>
|
||
|
<div class="note"><span class="notetitle">Note:</span> The Power Down System (PWRDWNSYS)
|
||
|
*CNTRLD command will attempt to vary off any active servers prior to powering
|
||
|
down the system.</div>
|
||
|
<div class="important"><span class="importanttitle">Important:</span> Never issue a PWRDWNSYS *IMMED
|
||
|
command without having your integrated Linux servers in shutdown status.</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
</div>
|
||
|
|
||
|
</body>
|
||
|
</html>
|