168 lines
9.6 KiB
HTML
168 lines
9.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 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="concept" />
|
|||
|
|
<meta name="DC.Title" content="Overview" />
|
|||
|
|
<meta name="abstract" content="This topic is an overview of the i5/OS operations." />
|
|||
|
|
<meta name="description" content="This topic is an overview of the i5/OS operations." />
|
|||
|
|
<meta name="DC.Relation" scheme="URI" content="rzau9400op.htm" />
|
|||
|
|
<meta name="DC.Format" content="XHTML" />
|
|||
|
|
<meta name="DC.Identifier" content="rzau9400opoverview" />
|
|||
|
|
<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>Overview</title>
|
|||
|
|
</head>
|
|||
|
|
<body id="rzau9400opoverview"><a name="rzau9400opoverview"><!-- --></a>
|
|||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
|||
|
|
<h1 class="topictitle1">Overview</h1>
|
|||
|
|
<div><p>This topic is an overview of the <span class="keyword">i5/OS™</span> operations.</p>
|
|||
|
|
<p>There are some operational tasks that must be performed from Linux<sup>®</sup>, and others
|
|||
|
|
from <span class="keyword">i5/OS</span>. This information
|
|||
|
|
describes how to operate an integrated Linux server
|
|||
|
|
from the <span class="keyword">i5/OS</span> side.</p>
|
|||
|
|
<p>You can operate the integrated Linux server from <span class="keyword">i5/OS</span> using
|
|||
|
|
either iSeries™ Navigator
|
|||
|
|
or by entering CL commands on the <span class="keyword">i5/OS</span> command
|
|||
|
|
line.</p>
|
|||
|
|
<div class="note"><span class="notetitle">Note:</span> All references to Linux apply equally to the supported Red Hat and SUSE
|
|||
|
|
distributions, except where noted. The term <dfn class="term">storage space</dfn> means
|
|||
|
|
a network server storage space. A storage space is a chunk of iSeries single-level
|
|||
|
|
disk storage that Linux sees as a physical disk drive. The terms storage
|
|||
|
|
space and Linux drive
|
|||
|
|
are used synonymously. An integrated Linux server is an instance of Linux running
|
|||
|
|
on an Integrated xSeries<sup>®</sup> Server, or an xSeries server attached via
|
|||
|
|
an Integrated xSeries Adapter.
|
|||
|
|
Each integrated Linux server has its own corresponding network server
|
|||
|
|
description (NWSD). The Integrated Linux servers are also referred to as
|
|||
|
|
simply <dfn class="term">Linux servers</dfn>.</div>
|
|||
|
|
<p>When an integrated Linux server is installed on iSeries, the following objects are created:</p>
|
|||
|
|
<dl><dt class="dlterm">Network server description (NWSD)</dt>
|
|||
|
|
<dd><p>This is the main configuration object of an integrated server that <span class="keyword">i5/OS</span> uses to control the server
|
|||
|
|
and describe its attributes. Each integrated Linux server instance has a corresponding
|
|||
|
|
NWSD. </p>
|
|||
|
|
<p>The NWSD contains the hardware resource name (LINxx) that points
|
|||
|
|
the Linux server
|
|||
|
|
instance to a physical Integrated xSeries Server or Integrated xSeries Adapter.
|
|||
|
|
All other <span class="keyword">i5/OS</span> objects
|
|||
|
|
needed to run a Linux server are linked to, and controlled by, the
|
|||
|
|
NWSD. The NWSD provides independence between instances of Linux and the
|
|||
|
|
Intel-compatible hardware that they run on (Integrated xSeries Server and Integrated xSeries Adapter).
|
|||
|
|
This unique architecture enables some powerful functions, such as the ability
|
|||
|
|
to:</p>
|
|||
|
|
<ul><li>Create multiple Linux server instances that can be run on the same
|
|||
|
|
integrated hardware resource, although not at the same time. This provides
|
|||
|
|
a “dormant” server capability.</li>
|
|||
|
|
<li>Switch Linux instances
|
|||
|
|
between integrated hardware resources. This provides a “hot spare” backup
|
|||
|
|
server capability that can be quickly activated in the case of failure of
|
|||
|
|
an Integrated xSeries Server
|
|||
|
|
or Integrated xSeries Adapter.</li>
|
|||
|
|
</ul>
|
|||
|
|
</dd>
|
|||
|
|
</dl>
|
|||
|
|
<dl><dt class="dlterm">Server instances</dt>
|
|||
|
|
<dd><p>Each integrated server or network server description represents a Linux or Windows<sup>®</sup> server
|
|||
|
|
instance, not an Integrated xSeries Server or Integrated xSeries Adapter. </p>
|
|||
|
|
<p>Each server
|
|||
|
|
instance has a corresponding network server description (NWSD) and vice versa.
|
|||
|
|
You can create multiple instances of Linux or Windows on one Integrated xSeries Server
|
|||
|
|
or Integrated xSeries Adapter,
|
|||
|
|
although only one instance can be active at a time. In other words, iSeries integration
|
|||
|
|
for Linux and Windows separates
|
|||
|
|
the hardware from the Linux and Windows instances that were created
|
|||
|
|
to run on that hardware. This is a unique feature of the iSeries Windows and Linux integration
|
|||
|
|
architecture, and provides major benefits in terms of availability and hardware
|
|||
|
|
utilization. </p>
|
|||
|
|
<p>When performing operations on integrated Linux servers
|
|||
|
|
using iSeries Navigator,
|
|||
|
|
it is usually addressed in terms of servers. When using CL commands through
|
|||
|
|
the <span class="keyword">i5/OS</span> command line
|
|||
|
|
it is usually addressed in terms of network server descriptions or NWSDs.</p>
|
|||
|
|
</dd>
|
|||
|
|
</dl>
|
|||
|
|
<dl><dt class="dlterm">Network server storage space</dt>
|
|||
|
|
<dd><p><dfn class="term">Storage spaces</dfn> are chunks of iSeries disk storage that are created
|
|||
|
|
in an <span class="keyword">i5/OS</span> auxiliary storage
|
|||
|
|
pool (ASP) and reserved for Linux or Windows. Because storage spaces are
|
|||
|
|
virtual disk drives created from <span class="keyword">i5/OS</span> single-level
|
|||
|
|
storage, each storage space is scattered across all the physical disk drives
|
|||
|
|
in the ASP. They can reside in the system ASP, a user ASP, or an independent
|
|||
|
|
ASP (IASP), and appear as objects in the /QFPNWSSTG IFS directory. </p>
|
|||
|
|
<p>From
|
|||
|
|
an <span class="keyword">i5/OS</span> perspective, this
|
|||
|
|
portion of iSeries disk
|
|||
|
|
storage is called a <dfn class="term">network server storage space</dfn>, or storage
|
|||
|
|
space for short. From the Linux (or Windows) perspective, this portion of iSeries disk
|
|||
|
|
storage is seen as a physical disk drive. In fact these drives are completely
|
|||
|
|
virtual, so we often refer to storage spaces and disk drives as virtual drives
|
|||
|
|
or simply drives. When we are discussing integrated Linux servers
|
|||
|
|
we use these terms interchangeably. Each disk drive icon or storage space
|
|||
|
|
represents a Linux or Windows (virtual)
|
|||
|
|
disk drive.</p>
|
|||
|
|
<p>To associate a storage space with a particular NWSD we <dfn class="term">link</dfn> it.</p>
|
|||
|
|
<p>The
|
|||
|
|
installation process automatically creates two storage spaces, called the <dfn class="term">system
|
|||
|
|
drive</dfn> and <dfn class="term">installation drive</dfn>, and links them to the NWSD.
|
|||
|
|
You can create more storage spaces for your server and link them to the NWSD
|
|||
|
|
after the installation has completed. Linux sees them as additional drives.</p>
|
|||
|
|
<p>The
|
|||
|
|
administration of a Linux server’s disk storage has both an <span class="keyword">i5/OS</span> component
|
|||
|
|
and a Linux component.
|
|||
|
|
On the <span class="keyword">i5/OS</span> side we create
|
|||
|
|
and link the storage space to the Linux server. On the Linux side we
|
|||
|
|
perform disk administration tasks such as partition management and formatting.
|
|||
|
|
These tasks are performed in exactly the same way on an integrated Linux server
|
|||
|
|
as they are on a standalone Linux server. </p>
|
|||
|
|
<p><span class="keyword">i5/OS</span> storage
|
|||
|
|
management relieves Linux of the responsibility for providing physical
|
|||
|
|
device support. Therefore, common disk administration issues encountered in
|
|||
|
|
standalone Linux servers,
|
|||
|
|
such as disk drivers, addressing, configuration, and protection, are eliminated
|
|||
|
|
when you use integrated Linux servers. </p>
|
|||
|
|
</dd>
|
|||
|
|
</dl>
|
|||
|
|
<dl><dt class="dlterm">Virtual Ethernet LAN line descriptions</dt>
|
|||
|
|
<dd><p>Indented under each NWSD is a communications line description that
|
|||
|
|
ends in PP. This line description, known as the <dfn class="term">Point-to-Point Virtual
|
|||
|
|
Ethernet line</dfn>, is automatically configured when the integrated server
|
|||
|
|
is created. This communications line provides a virtual 1 Gbps Ethernet connection
|
|||
|
|
between the integrated server and its hosting <span class="keyword">i5/OS</span> partition,
|
|||
|
|
and enables the server to exchange information with <span class="keyword">i5/OS</span>.
|
|||
|
|
You need a separate line description for each Virtual Ethernet connection
|
|||
|
|
you set up between an integrated Linux server and other integrated servers
|
|||
|
|
or iSeries logical
|
|||
|
|
partitions.</p>
|
|||
|
|
</dd>
|
|||
|
|
</dl>
|
|||
|
|
<dl><dt class="dlterm">TCP/IP interface for Point-to-Point Virtual Ethernet LAN line</dt>
|
|||
|
|
<dd><p>A TCP/IP interface is created specifically for the Point-to-Point Virtual
|
|||
|
|
Ethernet LAN line. By default, it has an address of the form 192.168.x.y,
|
|||
|
|
where x and y are automatically generated, and a subnet mask of 255.255.255.0.
|
|||
|
|
You can change the TCP/IP interface of Point-to-Point Virtual Ethernet LAN
|
|||
|
|
line after the server has been created. This interface should be an IP address
|
|||
|
|
and subnet that are not being used in your network. The Linux server
|
|||
|
|
has a corresponding TCP/IP address (192.168.x.y+1) configured on its end of
|
|||
|
|
the Point-to-Point Virtual Ethernet LAN.</p>
|
|||
|
|
</dd>
|
|||
|
|
</dl>
|
|||
|
|
</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>
|
|||
|
|
</body>
|
|||
|
|
</html>
|