100 lines
6.7 KiB
HTML
100 lines
6.7 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="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="reference" />
|
||
|
|
<meta name="DC.Title" content="Prepare for your Operations Console and iSeries Navigator configuration" />
|
||
|
|
<meta name="abstract" content="Before configuring your Operations Console and iSeries Navigator, familiarize yourself with this information." />
|
||
|
|
<meta name="description" content="Before configuring your Operations Console and iSeries Navigator, familiarize yourself with this information." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrplanconfig.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahg/rzahginav.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2000, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="opsnav" />
|
||
|
|
<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>Prepare for your Operations Console and iSeries Navigator configuration</title>
|
||
|
|
</head>
|
||
|
|
<body id="opsnav"><a name="opsnav"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Prepare for your Operations Console and iSeries Navigator configuration</h1>
|
||
|
|
<div><p>Before configuring your Operations Console and iSeries Navigator,
|
||
|
|
familiarize yourself with this information.</p>
|
||
|
|
<div class="section"><p>Both iSeries™ Navigator
|
||
|
|
and Operations Console can be run on a single PC. Depending on how you have
|
||
|
|
Operations Console connected to your iSeries server, there are two possible
|
||
|
|
network configuration options available. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>iSeries Navigator
|
||
|
|
is the graphical user interface for managing and administering your iSeries server
|
||
|
|
from your Windows<sup>®</sup> desktop. iSeries Navigator makes operation and
|
||
|
|
administration of iSeries servers easier and more productive. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><p>Operations Console allows you to use a local or remote PC to access
|
||
|
|
and control an iSeries console,
|
||
|
|
a control panel, or both. Operations Console has been enhanced to enable connections
|
||
|
|
or console activities across a local area network (LAN), besides enabling
|
||
|
|
directly cabled connections. A single PC can have multiple connections to
|
||
|
|
multiple iSeries servers
|
||
|
|
and can be the console for multiple iSeries servers. An example is having
|
||
|
|
a logically partitioned server using the same PC as the console for all partitions.
|
||
|
|
Since each partition is considered a separate iSeries server, you need a separate connection
|
||
|
|
to the partition for which you want to use the console. Operations Console
|
||
|
|
allows multiple connections to a single iSeries server, but only one PC can have
|
||
|
|
control of an iSeries server
|
||
|
|
at a time. Based on the Operation Console connectivity, you could have one
|
||
|
|
of two methods of configuration. </p>
|
||
|
|
</div>
|
||
|
|
<div class="section"> <ol><li>The PC using Operation Console as a local console directly attached to
|
||
|
|
the server will require a network connection for iSeries Navigator. In order to complete
|
||
|
|
the iSeries Navigator
|
||
|
|
connection, the iSeries will
|
||
|
|
need to have a network adapter and configured <span class="keyword">i5/OS™</span> line
|
||
|
|
description (LIND). <p>Operations Console connecting over a serial cable attached
|
||
|
|
to an asynchronous card on the iSeries machine. iSeries Navigator is connected through
|
||
|
|
a LAN adapter on the iSeries machine. The PC will communicate to Operations
|
||
|
|
Console through it's communication port while communicating with iSeries Navigator
|
||
|
|
through the LAN connectivity. </p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 1. iSeries Navigator and Operations Console
|
||
|
|
configuration over separate connectivity</span><br /><img src="rzajr513.gif" alt="iSeries Navigator and Operations Console configuration over separate connectivity" /><br /></div>
|
||
|
|
</li>
|
||
|
|
<li> The PC used as a local console on a network may require an additional
|
||
|
|
network connection. iSeries Navigator requires a network connection to
|
||
|
|
the network adapter and configured <span class="keyword">i5/OS</span> line
|
||
|
|
description (LIND). Operation Console will use the service network adapter
|
||
|
|
as defined by the service host name (interface name). If the network adapter
|
||
|
|
and configured <span class="keyword">i5/OS</span> LIND
|
||
|
|
and the service network adapter as defined by the service host name (interface
|
||
|
|
name) are on the same network, then an additional PC LAN adapter is not needed.
|
||
|
|
<div class="fignone"><span class="figcap">Figure 2. iSeries Navigator
|
||
|
|
and Operations Console configuration on the same network</span><br /><img src="rzajr514.gif" alt="iSeries Navigator and Operations Console configuration on the same network" /><br /></div>
|
||
|
|
<p>However, if the network adapter and configured <span class="keyword">i5/OS</span> LIND
|
||
|
|
and the service network adapter as defined by the service host name (interface
|
||
|
|
name) are on separate networks, then an additional PC LAN adapter is required.</p>
|
||
|
|
<div class="fignone"><span class="figcap">Figure 3. iSeries Navigator
|
||
|
|
and Operations Console configuration on separate networks</span><br /><img src="rzajr515.gif" alt="iSeries Navigator and Operations Console configuration with a LAN adapter" /><br /></div>
|
||
|
|
</li>
|
||
|
|
</ol>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzajrplanconfig.htm" title="In order to plan for your configuration, you should find out the specific connectivity types allowed by the various Operations Console configurations. The scenarios included offer specific configurations examples to help you select a console configuration most suited to your needs. If you plan ahead, you can include additional features in your configuration.">Plan for your configuration</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relinfo"><strong>Related information</strong><br />
|
||
|
|
<div><a href="../rzahg/rzahginav.htm">iSeries Navigator</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|