101 lines
7.1 KiB
HTML
101 lines
7.1 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 network environment" />
|
||
|
|
<meta name="abstract" content="To prepare for your network environment, you need to identify and comply with the minimum network configuration required to set up an Operations Console local console on a network (LAN) configuration." />
|
||
|
|
<meta name="description" content="To prepare for your network environment, you need to identify and comply with the minimum network configuration required to set up an Operations Console local console on a network (LAN) configuration." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrplanconfig.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrbackupconsole.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzajrhardwarereq.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="minnetwork" />
|
||
|
|
<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 network environment</title>
|
||
|
|
</head>
|
||
|
|
<body id="minnetwork"><a name="minnetwork"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Prepare for your network environment</h1>
|
||
|
|
<div><p>To prepare for your network environment, you need to identify and
|
||
|
|
comply with the minimum network configuration required to set up an Operations
|
||
|
|
Console local console on a network (LAN) configuration.</p>
|
||
|
|
<div class="section"><div class="important"><span class="importanttitle">Important:</span> You need to install the LAN adapter for Operations
|
||
|
|
Console according to your iSeries™ model.</div>
|
||
|
|
|
||
|
|
If your server is new and you ordered a local console on a network configuration,
|
||
|
|
the adapter should already be configured for use by the server. The LAN adapter
|
||
|
|
should be dedicated for service tools. It is recommended that you restrict
|
||
|
|
LAN topologies for LAN-attached local consoles to a single, physical ring,
|
||
|
|
hub, switch, and router environment. In the event that the local console
|
||
|
|
on a network is used in a larger network topology, broadcast (DHCP), packet
|
||
|
|
filtering is always recommended. This might be as simple as connecting the
|
||
|
|
PC and server using a crossover cable or using an inexpensive hub with only
|
||
|
|
the PC and server attached. When you have only a single PC or small number
|
||
|
|
of devices connected to the server using a hub and these devices do not connect
|
||
|
|
to another network or the internet, you can then use any numeric numbers for
|
||
|
|
addresses. An example would be 1.1.1.x or 10.220.215.x (where x can be 2
|
||
|
|
through 255 but avoid x.x.x.1 which might cause problems in some hubs). If
|
||
|
|
however, you have a network in which many users share or the devices go to
|
||
|
|
the internet then you should consult a network administrator for addresses.</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">Network security</h4><p>IBM<sup>®</sup> recommends treating the console over
|
||
|
|
a LAN connection with the same physical security considerations and controls
|
||
|
|
as a local console directly attached to the server or a twinaxial console.
|
||
|
|
For instance, consider configuring a local console on a network in a network
|
||
|
|
separate from the main network (or the company intranet) and strictly control
|
||
|
|
access to the machine acting as the console.</p>
|
||
|
|
</div>
|
||
|
|
<div class="section"><h4 class="sectiontitle">BOOTstrap Protocol</h4><p>A local Operations Console on
|
||
|
|
a network uses the BOOTstrap Protocol (BOOTP) to configure the server service
|
||
|
|
IP communications stack. The IP stack configuration plus server serial number
|
||
|
|
and partition ID is requested in the Operations Console configuration wizard.
|
||
|
|
The server broadcasts a BOOTP request. The Operations Console PC replies with
|
||
|
|
the information submitted during the configuration wizard. The server then
|
||
|
|
stores and uses the configuration information for the service IP communications
|
||
|
|
stack.</p>
|
||
|
|
<p>The Operations Console PC must be placed on a network that is
|
||
|
|
accessible by the server. This can be the same physical network or a network
|
||
|
|
that permits broadcast packets to flow. This is an initial setup requirement;
|
||
|
|
normal Operations Console operation does not require this. IBM recommends
|
||
|
|
that this setup occur on the same physical network.</p>
|
||
|
|
<p>The BOOTP request
|
||
|
|
carries the server serial number and partition ID. The server serial number
|
||
|
|
is used to assign the IP configuration information. If you are having problems
|
||
|
|
configuring the service IP communications stack, check that the Operations
|
||
|
|
Console PC is on the same physical network and the server serial number and
|
||
|
|
partition ID is correct in the configuration.</p>
|
||
|
|
<p>A local console
|
||
|
|
on a network (LAN) uses ports 2323, 3001, and 3002. To use Operations Console
|
||
|
|
in a different physical network the router and firewall must allow IP traffic
|
||
|
|
on these ports.</p>
|
||
|
|
<p>The success of BOOTP is dependent on the network hardware
|
||
|
|
used to connect the server and the PC. In some cases you may need an alternate
|
||
|
|
console device to configure the connection in DST. To use BOOTP the network
|
||
|
|
hardware used must be capable of AutoNegotiation of Speed and Duplex if using
|
||
|
|
the 2838 Ethernet Adapter for the Operations Console connection.</p>
|
||
|
|
</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="relref"><strong>Related reference</strong><br />
|
||
|
|
<div><a href="rzajrbackupconsole.htm" title="Here are some suggestions if you would like to plan for a backup for your console:">Plan for your backup console</a></div>
|
||
|
|
<div><a href="rzajrhardwarereq.htm" title="You need to meet the following PC and iSeries hardware requirements for an Operations Console configuration.">Meet Operations Console hardware requirements</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|