friedkiwi/ibm-information-center
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14ed2849c6
ibm-information-center/dist/eclipse/plugins/i5OS.ic.rzahq_5.4.0.1/rzahqinwrf.htm

1285 lines
54 KiB
HTML
Raw Normal View History

Add readme and dist folders
2024-04-02 14:02:31 +00:00
<?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>Installation worksheet for i5/OS parameters</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>
<a name="rzahqinwrf"></a>
<h3 id="rzahqinwrf">Installation worksheet for i5/OS parameters</h3>
<p>Prior to installing Windows 2000 Server or Windows Server 2003, complete
either the <a href="rzahqadvisor1.htm">Windows server installation advisor</a> or
this installation worksheet.</p>
<p>This worksheet will help you to install and configure your system.</p>
<a name="wq74"></a>
<table id="wq74" width="100%" summary="" border="1" frame="border" rules="all" class="singleborder">
<thead valign="bottom">
<tr class="tablemainheaderbar">
<th id="wq75" width="18%" align="left" valign="top">Field</th>
<th id="wq76" width="49%" align="left" valign="top">Description and Instructions</th>
<th id="wq77" width="33%" align="left" valign="top">Value</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left" valign="top" headers="wq75">Network server description (NWSD)</td>
<td align="left" valign="top" headers="wq76">Defines the operating characteristics and
communications connections of the network server that controls the integrated
Windows server. See <a href="rzahqnwsco.htm#rzahqnwsco">Network server descriptions</a>.
<br />Use a name that
is easy to remember. The name can have up to 8 characters. Use only the characters
A - Z and 0 - 9 in the name, and use a letter for the first character. The
network server description name is also the computer name and TCP/IP host
name of the integrated server.</td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Install type (INSTYPE)</td>
<td align="left" valign="top" headers="wq76">Specifies the type of install to perform.
Choose one of the following:
<dl>
<dt class="bold"><span class="bold">*FULL</span></dt>
<dd>
<p><img src="delta.gif" alt="Start of change" />Required when installing on an internal Integrated xSeries(R)
Server (IXS) and is optional when installing on an external xSeries&reg; server attached
with an Integrated xSeries Adapter (IXA) or iSCSI HBA .<img src="deltaend.gif" alt="End of change" /></p>
</dd>
<dt class="bold"><span class="bold">*BASIC</span></dt>
<dd><img src="delta.gif" alt="Start of change" />Optional install type when installing on an externally attached xSeries server attached with an IXA or iSCSI HBA. With this option, the
first part of the install process is controlled by the i5/OS&trade; Install Windows
server INSWNTSVR command. Then the install is completed by the xSeries install
process using the ServerGuide&trade; CD.<img src="deltaend.gif" alt="End of change" />
</dd>
</dl></td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Resource name (RSRCNAME)</td>
<td align="left" valign="top" headers="wq76">Identifies the Windows server hardware.
<p><img src="delta.gif" alt="Start of change" />For iSCSI attached xSeries and IBM&reg; BladeCenter&trade; servers, specify a resource name
of *ISCSI.<img src="deltaend.gif" alt="End of change" /></p>
<p><img src="delta.gif" alt="Start of change" />For both IXS and IXA attached xSeries servers,
enter the File Server IOA resource name. To determine the name, enter <tt>DSPHDWRSC *CMN</tt> (Display Communication Hardware Resources)
at the i5/OS command line. The resource name will appear as LINxx where xx is
a number.<img src="deltaend.gif" alt="End of change" /></p>
<p><a href="rzahqfiptp.htm#rzahqfiptp">Tip: Find resource names when you have multiple integrated servers</a></p></td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">TCP/IP port configuration (TCPPORTCFG)</td>
<td align="left" valign="top" headers="wq76">
<p><img src="delta.gif" alt="Start of change" />Specify the Windows TCP/IP
configuration values that are specific to each locally controlled adapter
port. Otherwise, skip this step and use the default value *NONE.<img src="deltaend.gif" alt="End of change" /></p>
<a name="wq78"></a>
<div class="notetitle" id="wq78">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">Only adapters that are directly managed by the iSeries&trade; and logically
controlled by the IXS can be configured using the TCPPORTCFG parameter. LAN
adapters that are attached with an IXA or iSCSI HBA and are managed by the xSeries server cannot be configured with this parameter.</div><img src="deltaend.gif" alt="End of change" /></td>
<td align="left" valign="top" headers="wq77">
<ul>
<li>Port 1
<ul>
<li>IP address</li>
<li>Subnet mask</li>
<li>Gateway (optional)</li></ul></li>
<li>Port 2
<ul>
<li>IP address</li>
<li>Subnet mask</li>
<li>Gateway (optional)</li></ul></li>
<li>Port 3
<ul>
<li>IP address</li>
<li>Subnet mask</li>
<li>Gateway (optional)</li></ul></li>
<li>Port 4
<ul>
<li>IP address</li>
<li>Subnet mask</li>
<li>Gateway (optional)</li></ul></li></ul></td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">
<p>Virtual Ethernet port (VRTETHPORT)</p></td>
<td align="left" valign="top" headers="wq76">
<p>Specifies the TCP/IP configuration
for the virtual Ethernet networks used by the file server.</p>
<p>A matching
virtual Ethernet port is required to install the Windows Cluster service.</p>
<dl>
<dt class="bold">*NONE:</dt>
<dd><span class="bold"></span> Specifies that there is no virtual Ethernet port
configuration.
</dd>
<dt class="bold"><span class="bold">Element 1: Port</span></dt>
<dd>
<ul>
<li><span class="bold">*VRTETH<span class="italic">x</span>:</span> The network server
virtual Ethernet port <span class="italic">x</span> is configured, where <span class="italic">x</span> has a value of 0 through 9.</li></ul>
</dd>
<dt class="bold">Element 2: Windows internet address</dt>
<dd>The Windows internet address for the port in the form, nnn.nnn.nnn.nnn,
where nnn is a decimal number ranging from 0 through 255.
</dd>
<dt class="bold">Element 3: Windows subnet mask</dt>
<dd>The subnet mask for the Windows internet address in the form, nnn.nnn.nnn.nnn,
where nnn is a decimal number ranging from 0 through 255.
</dd>
<dt class="bold">Element 4: Associated port</dt>
<dd>The resource name that describes the port that is used to establish
a connection between a Windows network server and the network.
<ul>
<li><span class="bold">*NONE</span> An associated port resource name is not associated
with the line.</li>
<li><span class="bold">resource-name</span> The resource name.</li></ul>
</dd>
</dl></td>
<td align="left" valign="top" headers="wq77">
<ul>
<li>Virtual port 1
<ul>
<li>*VRTETHx</li>
<li>IP Address</li>
<li>Subnet mask</li>
<li>Associated Port (Optional)</li></ul></li>
<li>Virtual port 2
<ul>
<li>*VRTETHx</li>
<li>IP Address</li>
<li>Subnet mask</li>
<li>Associated Port (Optional)</li></ul></li>
<li>Virtual port 3
<ul>
<li>*VRTETHx</li>
<li>IP Address</li>
<li>Subnet mask</li>
<li>Associated Port (Optional)</li></ul></li>
<li>Virtual port 4
<ul>
<li>*VRTETHx</li>
<li>IP Address</li>
<li>Subnet mask</li>
<li>Associated Port (Optional)</li></ul></li></ul></td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">TCP/IP local domain name (TCPDMNNAME)</td>
<td align="left" valign="top" headers="wq76">Specifies the TCP/IP local domain name associated
with the integrated server. You can specify *SYS to use the same value the i5/OS system uses.</td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">TCP/IP name server system (TCPNAMSVR)</td>
<td align="left" valign="top" headers="wq76">Specifies the Internet address of the name
server used by the integrated server. You can specify up to three Internet
addresses, or you can specify *SYS to use the same value the i5/OS uses.</td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">To workgroup (TOWRKGRP)</td>
<td align="left" valign="top" headers="wq76">Specifies the name of the Windows server
workgroup in which the server participates.</td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">To domain (TODMN)</td>
<td align="left" valign="top" headers="wq76">Specifies the name of the Windows domain
in which the server participates.</td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Server message queue and library (MSGQ)</td>
<td align="left" valign="top" headers="wq76">Specify the name of the message queue and
the library it will be located in. If the message queue does not already exist,
the INSWNTSVR command creates it. The message queue is where all event logs
and errors associated with this server are sent. You should specify a MSGQ
name and library. You can also specify *JOBLOG to send nonsevere errors to
the job log of the user administration monitor and severe errors to QSYSOPR.
If you specify *NONE, nonsevere errors are not sent to i5/OS, and severe
errors are sent to QSYSOPR.</td>
<td align="left" valign="top" headers="wq77">Queue:
<p>Library:</p></td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Event log (EVTLOG)</td>
<td align="left" valign="top" headers="wq76">Specifies whether or not i5/OS receives event
log messages from the integrated server. The choices are all, system, security,
application, or none:
<dl>
<dt class="bold"><span class="bold">*ALL</span></dt>
<dd>i5/OS receives all event log messages.
</dd>
<dt class="bold"><span class="bold">*NONE</span></dt>
<dd>No event log messages are received.
</dd>
<dt class="bold"><span class="bold">*SYS</span></dt>
<dd>i5/OS receives system event log messages.
</dd>
<dt class="bold"><span class="bold">*SEC</span></dt>
<dd>i5/OS receives security event log messages.
</dd>
<dt class="bold"><span class="bold">*APP</span></dt>
<dd>i5/OS receives application event log messages.
</dd>
</dl>
<dl>
<dt class="bold"><span class="bold">Note:</span></dt>
<dd>If you have the integrated server send its security log to the iSeries (by specifying
*ALL or *SEC), be sure to set up the message queue with the correct security.
</dd>
</dl></td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Installation source and system drive sizes
and auxiliary storage pool (ASP)
<p>(SVRSTGSIZE)</p>
<p>(SVRSTGASP)</p>
<p>(STGASPDEV)</p></td>
<td align="left" valign="top" headers="wq76">Specify the size of the network server storage
spaces for the installation source and system drives and in which ASP (1
- 255) you want them. An ASP device name can be specified in place of the
ASP numbers 33-255 when the storage space should be created in an independent
auxiliary storage pool. However, if a name is used, the ASP number field must
be left as the default value of 1 or the place holder value of *N.
<p>The
installation source drive (drive D) must be large enough to hold the contents
of the I386 directory on the Windows server installation CD image and the IBM i5/OS Integrated Server Support code.</p>
<p>The system drive (drive C) must
be large enough to hold the Windows server operating system. The limit is
1,024 to 1,024,000 MB, depending on your resource capabilities. Consider these
factors:</p>
<ul>
<li>Your version of Windows server (Refer to Microsoft&reg; documentation for operating
system requirements.)</li>
<li>Primary usage (print/file serving) and number of Terminal Server users.</li>
<li>Free space on system drive.</li>
<li>Application resource requirements.</li>
<li>Need for crash dump file.</li>
<li><img src="delta.gif" alt="Start of change" />Installed memory on server<img src="deltaend.gif" alt="End of change" /></li></ul>
<p>i5/OS creates and links the drive as a FAT32 or NTFS network server storage
space, depending on the size.</p>
<p>For more information about these drives,
see <a href="rzahqrstrf.htm#rzahqrstrf">Predefined disk drives for integrated Windows servers</a>.</p>
<p><span class="bold">Notes:</span></p>
<ol type="1">
<li>The INSWNTSVR command automatically sets the system drive size if a size
to a minimum size that is determined based in part on factors such as the
Windows version and installed memory.</li>
<li><img src="delta.gif" alt="Start of change" />When deciding the size of each drive, allow room for future
needs such as new applications or upgrades to the Windows server product.
If you specify *CALC for SVRSTGSIZE, note that i5/OS will allocate the minimum disk size necessary
to install Windows. If you need additional space for applications or data
you should consider manually specifying a drive size.<img src="deltaend.gif" alt="End of change" /></li>
<li>Support for independent ASPs (33 - 255) is provided through iSeries Navigator.
For more information about working with independent ASPs, see <a href="../rzaly/rzalyoverview.htm">Independent disk pools</a>. Both the Information Center and iSeries Navigator
refer to ASPs as disk pools. To use an independent ASP, the ASP device must
be available prior to running the INSWNTSVR command.</li></ol></td>
<td align="left" valign="top" headers="wq77">
<p>Installation source drive:</p>
<p>Size:</p>
<p>ASP:</p>
<p>ASPDEV:</p>
<p>System drive:</p>
<p>Size:</p>
<p>ASP:</p>
<p>ASPDEV:</p></td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">License mode (LICMODE)</td>
<td align="left" valign="top" headers="wq76">Determines the license mode to install Microsoft Windows server.
<p><span class="bold">Element 1 License type:</span></p>
<dl>
<dt class="bold"><span class="bold">*PERSEAT</span></dt>
<dd>Indicates that a client license has been purchased for each computer
that accesses the server.
</dd>
<dt class="bold"><span class="bold">*PERSERVER</span></dt>
<dd>Indicates that client licenses have been purchased for the server to
allow a certain number of concurrent connections to the server.
</dd>
</dl>
<p><span class="bold">Element 2 Client licenses:</span></p>
<dl>
<dt class="bold"><span class="bold">*NONE</span></dt>
<dd>Indicates that no client licenses are installed. *NONE must be specified
when *PERSEAT is specified.
</dd>
<dt class="bold"><span class="bold">number-client-licenses:</span></dt>
<dd>Specifies the number of client licenses purchased for the server being
installed.
</dd>
</dl>
<p><span class="bold">Element 3 Windows Terminal Services:</span></p>
<dl>
<dt class="bold"><span class="bold">*TSENABLE</span></dt>
<dd>For Windows 2000, install Windows Terminal Services and Terminal Services
licensing.
</dd>
<dt class="bold"><span class="bold">*PERDEVICE</span></dt>
<dd>*PERDEVICE Installs and configures Windows Server 2003 Terminal Services
to require that each connected device has a valid Windows Terminal Server
access license. If the client has a Terminal Server access license, it can
access more than one Terminal Server.
</dd>
<dt class="bold"><span class="bold">*PERUSER</span></dt>
<dd>Installs and configures Windows Server 2003 Terminal Server to provide
one Terminal Server access license for each active user.
</dd>
<dt class="bold"><span class="bold">*NONE</span></dt>
<dd>There are no Terminal Server desktop licenses for this server.
</dd>
</dl></td>
<td align="left" valign="top" headers="wq77">
<p>License type:</p>
<p>Client licenses:</p>
<p>Terminal services:</p></td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Propagate domain user (PRPDMNUSR)</td>
<td align="left" valign="top" headers="wq76">Specifies if this server should be used to
propagate and synchronize users to the Windows domain or active directory.
<dl>
<dt class="bold"><span class="bold">*YES</span></dt>
<dd>Send user updates to the Windows domain or active directory through
this server.
</dd>
<dt class="bold"><span class="bold">*NO</span></dt>
<dd>Do not send user updates to the Windows domain or active directory through
this server.
</dd>
</dl></td>
<td headers="wq77">&nbsp;</td>
</tr>
<tr>
<td headers="wq75">Shutdown timeout (SHUTDTIMO)</td>
<td headers="wq76">A value which determines how long i5/OS waits to allow
programs to end before shutting down the integrated server. The delay can
be from 2 to 45 minutes. If you do not specify a value, it will be set to
15 minutes.</td>
<td headers="wq77">Shutdown timeout:</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Restricted device resources (RSTDEVRSC)</td>
<td align="left" valign="top" headers="wq76">Restricts iSeries tape and optical devices from being
used by the integrated server.
<dl>
<dt class="bold"><span class="bold">*NONE</span></dt>
<dd>Restricts no tape or optical devices from being used by the integrated
server.
</dd>
<dt class="bold"><span class="bold">*ALL</span></dt>
<dd>Restricts all tape and optical devices from being used by the integrated
server.
</dd>
<dt class="bold"><span class="bold">*ALLTAPE</span></dt>
<dd>Restricts all tape resources from being used by the integrated server.
</dd>
<dt class="bold"><span class="bold">*ALLOPT</span></dt>
<dd>Restricts all optical resources from being used by the integrated server.
</dd>
<dt class="bold"><span class="bold">restricted-device</span></dt>
<dd>Specify up to 10 device resources that you do not want the integrated
server to use.
</dd>
</dl></td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Time zone</td>
<td align="left" valign="top" headers="wq76">(Optional) Records the time zone of the iSeries for use in the Windows server phase of installation. See <a href="rzahqtimesync.htm#rzahqtimesync">Time synchronization</a>.</td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Virtual Ethernet point to point
<p>(VRTPTPPORT)</p></td>
<td align="left" valign="top" headers="wq76">
<p>A local area network (see <a href="rzahqlanco.htm#rzahqlanco">Networking concepts</a>)
exists between i5/OS and Windows server. Both the i5/OS side and the
Windows server side of this LAN have IP addresses and subnet masks.</p>
<dl>
<dt class="bold"><span class="bold">Note:</span></dt>
<dd>By default, the INSWNTSVR command sets up these addresses automatically.
These addresses are in the form of 192.168.xx.yy. If your site uses class
C addresses, it is possible for duplicate IP addresses to be generated.
<p>To avoid potential conflicts, you can also specify Internet addresses that
you know will be unique across your system. Use addresses in the form a.b.x.y
where a.b.x is the same value for both sides of the point to point virtual
Ethernet and ensure that the point to point virtual Ethernet occupies its
own subnet on i5/OS. Use the Virtual PTP Ethernet port parameter under
additional parameters of the INSWNTSVR command.</p>
</dd>
</dl>
<p>The subnet mask is always 255.255.255.0.</p></td>
<td align="left" valign="top" headers="wq77">
<p>i5/OS-side IP address:</p>
<p>Windows server-side
IP address:</p></td>
</tr>
<tr>
<td align="left" valign="top" headers="wq75">Configuration file (CFGFILE)</td>
<td align="left" valign="top" headers="wq76">During the installation, creates and specifies
a customized NWSD (see <a href="rzahqrzahqcpkpo.htm#rzahqrzahqcpkpo">Network server description configuration files</a>).
<p>The default is
*NONE. To specify a configuration file that you have created, substitute the
name of the file and the library where it is stored (*LIBL, *CURLIB, or the
name of the library).</p></td>
<td align="left" valign="top" headers="wq77">&nbsp;</td>
</tr>
</tbody>
</table>
<p><span class="bold"><img src="delta.gif" alt="Start of change" />Installation worksheet for additional internet
SCSI (iSCSI) parameters<img src="deltaend.gif" alt="End of change" /></span></p><img src="delta.gif" alt="Start of change" />
<a name="wq80"></a>
<table id="wq80" width="100%" summary="" border="1" frame="border" rules="all" class="singleborder">
<thead valign="bottom">
<tr class="tablemainheaderbar">
<th id="wq81" width="18%" align="left" valign="top">Field</th>
<th id="wq82" width="49%" align="left" valign="top">Description and Instructions</th>
<th id="wq83" width="33%" align="left" valign="top">Value</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td headers="wq81">Activation timer (ACTTMR)</td>
<td headers="wq82">
<p>Specifies the amount of time in seconds that the
system will wait for the connection to be established to the remote server's
service processor and to power on the remote server. The default value is
120. Specify a value in seconds ranging from 30 through 1800.</p></td>
<td headers="wq83">Activation timer:</td>
</tr>
<tr>
<td headers="wq81">Communications message queue (CMNMSGQ)</td>
<td headers="wq82">
<p>Specifies the name of a message queue to receive
communications status messages.</p>
<dl>
<dt class="bold">Qualifier 1:</dt>
<dd>
<ul>
<li><span class="bold">*SYSOPR</span> Causes messages to be placed in the system
operator message queue.</li>
<li><span class="bold-italic">name</span> Specify the name of a message queue
to receive communications status messages.</li></ul>
</dd>
<dt class="bold">Qualifier 2:</dt>
<dd>
<ul>
<li><span class="bold">*LIBL</span> All libraries in the job's library list are
searched until the first match is found</li>
<li><span class="bold">*CURLIB</span> The current library for the job is searched.
If no library is specified as the current library for the job, the QGPL library
is used.</li>
<li><span class="bold-italic">library-name</span> Specify the name of the library
to be used</li></ul>
</dd>
</dl></td>
<td headers="wq83">
<p>Message queue:</p>
<p>Library:</p></td>
</tr>
<tr>
<td headers="wq81">Storage path (STGPTH)</td>
<td headers="wq82">
<p>Specifies the storage path the storage spaces can
use. This information consists of the Network server host adapter (NWSH) description.</p>
<a name="wq84"></a>
<div class="notetitle" id="wq84">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You can add additional storage paths after
you install your server.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">name</dt>
<dd>Specify the name of an existing Network server host adapter (NWSH) description.
</dd>
</dl></td>
<td headers="wq83">NWSH name:</td>
</tr>
<tr>
<td headers="wq81">Virtual Ethernet path (VRTETHPTH)</td>
<td headers="wq82">
<p>Specifies the virtual Ethernet paths the Ethernet
line descriptions can use. This information consists of two parts including
the virtual Ethernet port and the Network server host adapter (NWSH) description.
You can enter up to five values for this parameter. You must enter at least
one virtual Ethernet path which is the path to be used by the *VRTETHPTP line
description name.</p>
<a name="wq85"></a>
<div class="notetitle" id="wq85">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You can add virtual Ethernet
paths after you install your server.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">Element 1: Port</dt>
<dd>
<p><span class="bold">*VRTETHPTP</span></p>
<p>The network server virtual
Ethernet point to point port is configured.</p>
<p><span class="bold">*VRTETH<span class="italic">x</span></span> The network server virtual Ethernet port x is configured,
where x has a value of 0 through 9.</p>
</dd>
<dt class="bold">Element 2: Network server host adapter</dt>
<dd>
<p><span class="bold">name</span> Specify the name of an existing Network
server host adapter (NWSH) description. The network server host adapter name
does not need to be unique for each VRTETHPTH parameter on this NWSD.</p>
</dd>
</dl></td>
<td headers="wq83">Virtual Ethernet path:
<p>Port:</p>
<p>NWSH:</p></td>
</tr>
<tr>
<td headers="wq81">Shutdown TCP port (SHUTDPORT)</td>
<td headers="wq82">
<p>Specifies the TCP port to use for shutdown.</p>
<a name="wq86"></a>
<div class="notetitle" id="wq86">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">This is an advanced parameter that may be useful when
there is a firewall in the iSCSI network.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">8700 </dt>
<dd>Use the TCP port number of 8700.
</dd>
<dt class="bold">integer </dt>
<dd>Specifies the port number identifying the port that is to be used for
shutdown. Valid values range from 1024 through 65,535.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Virtual Ethernet control port (VRTETHCTLP)</td>
<td headers="wq82">
<p>Specifies the TCP port to use for virtual Ethernet
control.</p>
<a name="wq87"></a>
<div class="notetitle" id="wq87">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">This is an advanced parameter that
may be useful when there is a firewall in the iSCSI network.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">8800</dt>
<dd> Use the TCP port number of 8800.
</dd>
<dt class="bold">integer </dt>
<dd>Specifies the port number identifying the port that is to be used for
virtual Ethernet control. Valid values range from 1024 through 65,535.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Remote system NWSCFG (RMTNWSCFG)</td>
<td headers="wq82">
<p>Specifies the remote system network server configuration
to use with this server.</p>
<a name="wq88"></a>
<div class="notetitle" id="wq88">Note:</div>
<div class="notebody">It may be preferable or even necessary
to create the remote system configuration before you run the INSWNTSVR command.
See <a href="rzahqcreateanspandrmtsysconf.htm#rzahqcreateanspandrmtsysconf">Create a service processor configuration and a remote system configuration</a>.</div>
<dl>
<dt class="bold">*DFT</dt>
<dd> Use the system generated default remote system network server configuration
name of 'nwsdnameRM' where nwsdname is the name of the network server description.
</dd>
<dt class="bold">name</dt>
<dd> Specify the name of an existing remote system network server configuration.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Service processor NWSCFG (SPNWSCFG)</td>
<td headers="wq82">
<p>Specifies the service processor network server configuration
to use with this server.</p>
<a name="wq89"></a>
<div class="notetitle" id="wq89">Note:</div>
<div class="notebody">It may be preferable or even
necessary to create the service professor configuration before you run the
INSWNTSVR command. See <a href="rzahqcreateanspandrmtsysconf.htm#rzahqcreateanspandrmtsysconf">Create a service processor configuration and a remote system configuration</a>.</div>
<dl>
<dt class="bold">*DFT</dt>
<dd> Use the system generated default service processor network server configuration
name of 'nwsdnameSP' where nwsdname is the name of the network server description.
</dd>
<dt class="bold">name </dt>
<dd>Specify the name of an existing service processor network server configuration.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Connection security NWSCFG (CNNNWSCFG)</td>
<td headers="wq82">
<p>Specifies the connection security network server
configuration to use with this server.</p>
<dl>
<dt class="bold">*DFT</dt>
<dd> Use the system generated default connection security network server
configuration name of 'nwsdnameCN' where nwsdname is the name of the network
server description.
</dd>
<dt class="bold"> name </dt>
<dd>Specify the name of an existing connection security network server configuration.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Default IP security rule (DFTSECRULE)</td>
<td headers="wq82">
<p>Specifies the default IP Security (IPSec) rule used
between the hosting and remote system.</p>
<a name="wq90"></a>
<div class="notetitle" id="wq90">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot
specify a value for this parameter if you specified an existing connection
security configuration in the CNNNWSCFG parameter</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*NONE </dt>
<dd>IP Security rules are not configured.
</dd>
<dt class="bold"> *GEN </dt>
<dd>The system will automatically generate a random pre-shared key.
</dd>
<dt class="bold">pre-shared-key </dt>
<dd>Specify the pre-shared key. A pre-shared key is a nontrivial string
up to 32 characters long.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">IP security rule (IPSECRULE)</td>
<td headers="wq82">
<p>Specify the relative entry of the IP security rules
(IPSECRULE) parameter, defined in the existing connection security network
server configuration that will be used as the initial IP security setting
between the hosting and remote system.</p>
<dl>
<dt class="bold">*DFTSECRULE </dt>
<dd>Use the value specified on the Default IP security rule (DFTSECRULE)
parameter.
</dd>
<dt class="bold">*NONE</dt>
<dd>Remote interface will not use any security rule.
</dd>
<dt class="bold">1-16</dt>
<dd>Remote interface will use security rule specified.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Initialize service processor (INZSP)</td>
<td headers="wq82">
<p>Specifies how the remote system's service processor
is secured.</p>
<a name="wq91"></a>
<div class="notetitle" id="wq91">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify *SYNC if the
service processor configuration already exists. *MANUAL, *AUTO, and *NONE
are only used if the service processor configuration does not exist.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*MANUAL</dt>
<dd>This is the most secure method. You must manually configure the user
name, password and certificate for the service processor. Certificate management
is required. This method is appropriate to protect your service processor
password when you connect to it over public networks.
</dd>
<dt class="bold">*AUTO</dt>
<dd>You do not need to manually configure parameters on the remote system's
service processor. The service processor of the remote system will automatically
generate a certificate. The connection is secure once initialized. This option
is appropriate if you connect to the service processor over a network that
is physically secure or is protected by a firewall.
</dd><img src="delta.gif" alt="Start of change" />
<dt class="bold">*SYNC</dt>
<dd>This network server configuration will synchronize the user, password,
and self-signed certificate with the service processor.
</dd><img src="deltaend.gif" alt="End of change" />
<dt class="bold">*NONE</dt>
<dd>There is no security for the service processor password. Do not use
this unless you connect to the service processor over a physically secure
network.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Enable unicast (ENBUNICAST)</td>
<td headers="wq82">
<p>Unicast is a transmission method where packets are
sent directly to the specified Service processor name (SPNAME) or Service
processor address (SPINTNETA) parameter. The system identification for the
Enclosure identifier (EID) parameter is automatically retrieved if *AUTO is
specified and the system hardware supports it.</p>
<a name="wq92"></a>
<div class="notetitle" id="wq92">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter if you specified an existing
service processor configuration in the SPNWSCFG parameter</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*NO</dt>
<dd>Disable unicast
</dd>
<dt class="bold">*YES</dt>
<dd>Enable unicast.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Enclosure identifier (EID)</td>
<td headers="wq82">
<p>Specifies the identifying serial number, type and
model of the enclosure containing the service processor. They are required
to locate the remote system on the network when ENBUNICAST(*NO) is specified.
Look for these values on the label of the system.</p>
<a name="wq93"></a>
<div class="notetitle" id="wq93">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter if you specified an existing
service processor configuration in the SPNWSCFG parameter</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*AUTO</dt>
<dd> Automatically retrieve the identifier when ENBUNICAST(*YES) is specified.
</dd>
<dt class="bold">Element 1: Serial number</dt>
<dd>Specify the remote system's machine serial number using only alphanumeric
characters without dashs.
</dd>
<dt class="bold">Element 2: Manufacturer type and model</dt>
<dd>Specify the remote system's machine type and model in the form ttttmmm
where tttt is the machine type and mmm is the machine model number.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Service processor name (SPNAME)</td>
<td headers="wq82">
<p>Specifies the remote system's service processor host
name.</p>
<a name="wq94"></a>
<div class="notetitle" id="wq94">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter
if you specified an existing service processor configuration in the SPNWSCFG
parameter</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*SPINTNETA</dt>
<dd>The remote system is identified by the value specified for the Service
processor address (SPINTNETA) parameter.
<p><span class="bold">host-name:</span> Specify
the remote system's service processor host name.</p>
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">Service processor address (SPINTNETA)</td>
<td headers="wq82">
<p>Specify the remote system's service processor internet
address. Internet addresses are expressed in the decimal form nnn.nnn.nnn.nnn
, where nnn is a decimal number ranging from 0 through 255.</p>
<a name="wq95"></a>
<div class="notetitle" id="wq95">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter if you specified an
existing service processor configuration in the SPNWSCFG parameter</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">internet-address:</dt>
<dd>Specify the internet address of the service processor.
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">SP authentication (SPAUT)</td>
<td headers="wq82">
<p>Specifies the service processor user name and password.</p>
<a name="wq96"></a>
<div class="notetitle" id="wq96">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter
if you specified an existing service processor configuration in the SPNWSCFG
parameter</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*DFT</dt>
<dd> The default service processor userid and password are used.
</dd>
<dt class="bold">Element 1: User name</dt>
<dd>Specify the remote system's service processor user name.
</dd>
<dt class="bold">Element 2: User Password</dt>
<dd>Specify remote system's service processor password. Password must be
at least 5 characters in length and contain at least one alphabetic character
and one numeric or symbolic character.
</dd>
</dl></td>
<td headers="wq83">
<p>Name:</p>
<p>Password:</p></td>
</tr>
<tr>
<td headers="wq81">SP certificate identifier (SPCERTID)</td>
<td headers="wq82">
<p>The SP certificate identifier specifies one of three
possible fields that identifies the service processor's certificate. This
parameter is specified to provide additional validation that the certificate
is from the service processor. The contents of the selected field must exactly
match the value of the field that was entered when the certificate was generated
or requested from a certificate authority.</p>
<a name="wq97"></a>
<div class="notetitle" id="wq97">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter if you specified an existing
service processor configuration in the SPNWSCFG parameter.</div><img src="deltaend.gif" alt="End of change" />
<p><span class="bold">Single values:</span></p>
<dl>
<dt class="bold">*NONE</dt>
<dd> Service processor certificate is not configured.
</dd>
</dl>
<p><span class="bold">Element 1: Component</span></p>
<dl>
<dt class="bold">*COMMONNAME</dt>
<dd> Selects the certificates common name specified when the certificate
was generated or requested from a certificate authority. On the remote supervisor
adapter II this correlates to the "ASM Domain Name" field used to generate
a self-signed certificate or generate a certificate signing request.
</dd>
<dt class="bold">*EMAIL </dt>
<dd>Selects the certificate's e-mail address specified when the certificate
was generated or requested from a certificate authority. On the remote supervisor
adapter II this correlates to the <span class="bold">Email address</span> field
used to generate a self-signed certificate or generate a certificate signing
request.
</dd>
<dt class="bold">*ORGUNIT </dt>
<dd>Selects the certificate's organizational unit specified when the certificate
was generated or requested from a certificate authority. On the remote supervisor
adapter II this correlates to the <span class="bold">Organizational Unit</span> field
used to generate a self-signed certificate or generate a certificate signing
request.
</dd>
</dl>
<p><span class="bold">Element 2: Compare value</span></p>
<dl>
<dt class="bold">compare-value</dt>
<dd>Specify the certificates component compare value. Specify no more than
255 characters of text, enclosed in apostrophes.
</dd>
</dl></td>
<td headers="wq83">
<p>Component:</p>
<p>Compare value:</p></td>
</tr>
<tr>
<td headers="wq81">Remote system identifier (RMTSYSID)</td>
<td headers="wq82">
<p>Specifies the identifying serial number, type and
model of the remote system. When specified, they are used to locate the remote
system on the network. Look for these values on the label of the remote system.</p>
<a name="wq98"></a>
<div class="notetitle" id="wq98">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter
if you specified an existing remote system configuration in the RMTNWSCFG
parameter.</div><img src="deltaend.gif" alt="End of change" />
<p><span class="bold">Single values:</span></p>
<dl>
<dt class="bold">*EID</dt>
<dd>Use the service processor enclosure identifier.
</dd>
<dt class="bold">Element 1: Serial number</dt>
<dd>
<p><span class="bold">serial-number</span> Specify the remote system's machine
serial number.</p>
</dd>
<dt class="bold">Element 2: Manufacturer type and model</dt>
<dd>
<dl>
<dt class="bold">type-model</dt>
<dd>Specify the remote system's machine type and model in the form ttttmmm
where tttt is the machine type and mmm is the machine model number.
</dd>
</dl>
</dd>
</dl></td>
<td headers="wq83">
<p>Serial number:</p>
<p>Manufacturer type and model:</p></td>
</tr>
<tr>
<td headers="wq81">Delivery method (DELIVERY)</td>
<td headers="wq82">
<p>Specifies how the parameters necessary to configure
the remote system are delivered.</p>
<a name="wq99"></a>
<div class="notetitle" id="wq99">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot
specify a value for this parameter if you specified an existing remote system
configuration in the RMTNWSCFG parameter.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">*DYNAMIC </dt>
<dd>Parameters are dynamically delivered to the remote system using DHCP.
</dd>
<dt class="bold">*MANUAL</dt>
<dd> Parameters are manually configured on the remote system using the BIOS
utilities (System BIOS or Adapter BIOS - CTRL-Q).
</dd>
</dl></td>
<td headers="wq83">&nbsp;</td>
</tr>
<tr>
<td headers="wq81">CHAP authentication (CHAPAUT)</td>
<td headers="wq82">
<p>Specifies the Challenge Handshake Authentication
Protocol (CHAP) for the host system iSCSI target to authenticate the remote
system initiator node.</p>
<a name="wq100"></a>
<div class="notetitle" id="wq100">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a
value for this parameter if you specified an existing remote system configuration
in the RMTNWSCFG parameter.</div><img src="deltaend.gif" alt="End of change" />
<p><span class="bold">Single values:</span></p>
<dl>
<dt class="bold">*NONE </dt>
<dd>CHAP authentication is not enabled.
</dd>
<dt class="bold">Element 1: CHAP name </dt>
<dd>Specify the CHAP name.
</dd>
<dt class="bold">Element 2: CHAP secret</dt>
<dd>Specify the secret you want to use for the Challenge Handshake Authentication
Protocol as a value up to 24-characters long.
</dd>
</dl></td>
<td headers="wq83">
<p>CHAP name:</p>
<p>CHAP secret:</p></td>
</tr>
<tr>
<td headers="wq81">Boot device ID (BOOTDEVID)</td>
<td headers="wq82">
<p>Specifies the PCI Function Address (Bus/Device/Function)
of the iSCSI adapter in the remote system that will be used to boot from.
This information can be accessed using the BIOS utilities (System BIOS or
Adapter BIOS - CTRL-Q).</p>
<a name="wq101"></a>
<div class="notetitle" id="wq101">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a
value for this parameter if you specified an existing remote system configuration
in the RMTNWSCFG parameter.</div><img src="deltaend.gif" alt="End of change" />
<p><span class="bold">Single values:</span></p>
<dl>
<dt class="bold">*SINGLE</dt>
<dd> The single iSCSI adapter is used on the remote system Note: Remote
systems with more than one iSCSI adapter installed in the server are required
to specify which adapter will be used to boot from.
</dd>
<dt class="bold">Element 1: Bus number</dt>
<dd>Specify the bus number of the remote system's iSCSI adapter that will
be used to boot.
</dd>
<dt class="bold">Element 2: Device number</dt>
<dd>Specify the device number of the remote system's iSCSI adapter that
will be used to boot.
</dd>
<dt class="bold">Element 3: Function</dt>
<dd><span class="bold">function-number</span> Specify the function number of
the remote system's iSCSI adapter that will be used to boot.
</dd>
</dl></td>
<td headers="wq83">
<p>Bus number:</p>
<p>Device:</p>
<p>Function:</p></td>
</tr>
<tr>
<td headers="wq81">Dynamic boot options (DYNBOOTOPT)</td>
<td headers="wq82">
<p>This is an advanced function.</p>
<p>This parameter
is used to configure the internal DHCP Server that is part of the iSCSI Target
Host Bus Adapter firmware and its required to provide IP address and diskless
boot parameters for the remote iSCSI Initiator.</p>
<a name="wq102"></a>
<div class="notetitle" id="wq102">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter if you specified an existing
remote system configuration in the RMTNWSCFG parameter.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">Element 1: </dt>
<dd><span class="bold">Vendor ID </span>The client and server are pre-configured
to a fixed vendor ID. Network administrators can configure clients to define
their own idetifying values to convey hardware, operating system or other
identifying information. DHCP option 60 described in the IETF RFC 2132 is
used for this function.
<dl>
<dt class="bold">*DFT</dt>
<dd> The default vendor ID will be used.
</dd>
<dt class="bold"> vendor-id </dt>
<dd>Vendor ID of the remote system's iSCSI adapter that will be used.
</dd>
</dl>
</dd>
<dt class="bold">Element 2: </dt>
<dd><span class="bold">Alternate client ID </span>Used by clients to specify
their unique identifier to the server. Each client's identifier must be unique
among all other client identifiers used on the effective DHCP network to which
the client is attached (that is, the client's local subnet and any remote
subnets reachable using DHCP relay). Vendors and system administrators are
responsible for choosing client identifiers that meet this requirement for
uniqueness. DHCP option 61 described in the IETF RFC 2132 is used for this
function.
<dl>
<dt class="bold">*ADPT </dt>
<dd>The default Client ID consists of the adapter address for the remote
system's iSCSI adapter. This value will be used to identify the remote system.
</dd>
<dt class="bold">client-id </dt>
<dd>Specify the Client ID of the remote system's iSCSI adapter that will
be used to boot.
</dd>
</dl>
</dd>
</dl></td>
<td headers="wq83">
<p>Vendor ID:</p>
<p>Alternate client ID:</p></td>
</tr>
<tr>
<td headers="wq81">Remote interfaces (RMTIFC)</td>
<td headers="wq82">
<p>Specifies the remote system interfaces. This information
is used to identify and configure the remote system's interfaces. Each adapter
port has two functions to support a SCSI and a LAN interface.</p>
<a name="wq103"></a>
<div class="notetitle" id="wq103">Note:</div><img src="delta.gif" alt="Start of change" />
<div class="notebody">You cannot specify a value for this parameter if you specified an
existing remote system configuration in the RMTNWSCFG parameter.</div><img src="deltaend.gif" alt="End of change" />
<dl>
<dt class="bold">Element 1: SCSI interface</dt>
<dd><span class="bold">Element 1: Adapter address</span> Specify the 12-character
hexadecimal adapter address for the remote system's SCSI interface.
<dl>
<dt class="bold">Element 2: Internet address</dt>
<dd><span class="bold"> internet-address</span> for the remote system's SCSI
interface.
</dd>
<dt class="bold">Element 3: Subnet mask</dt>
<dd><span class="bold">subnet-mask</span> for the remote system's SCSI interface.
</dd>
<dt class="bold">Element 4: Gateway address </dt>
<dd><span class="bold">gateway-address</span> for the remote system's SCSI
interface.
</dd>
<dt class="bold">Element 5: iSCSI qualified name</dt>
<dd>
<p><span class="bold">*GEN </span></p>
<p>The system will automatically
generate the iSCSI qualified name.</p>
<p><span class="bold">iqn-name</span></p>
<p> iSCSI qualified name for the remote system's SCSI interface.</p>
</dd>
</dl>
</dd>
</dl></td>
<td headers="wq83">
<p>SCSI interface</p>
<ul>
<li>Adapter address:</li>
<li>Internet address:</li>
<li>Subnet mask:</li>
<li>Gateway address (Optional):</li>
<li>iSCSI qualified name:</li></ul></td>
</tr>
<tr>
<td headers="wq81">Remote interfaces (RMTIFC) continued</td>
<td headers="wq82">
<dl>
<dt class="bold">Element 2: LAN interface </dt>
<dd>
<p><span class="bold">Element 1: Adapter-address </span></p>
<p>12-character
hexadecimal adapter address for the remote system's LAN or TCP Offload Engine
(TOE) interface.</p>
<p><span class="bold">Element 2: Internet address</span></p>
<p> for the remote system's LAN interface.</p>
<p> <span class="bold">Element 3:
Subnet mask</span></p>
<p> for the remote system's LAN interface.</p>
<p><span class="bold">Element 4: Gateway address</span></p>
<p>for the remote system's
LAN interface.</p>
</dd>
</dl></td>
<td headers="wq83">
<p>LAN interface</p>
<ul>
<li>Adapter-address:</li>
<li>Internet address:</li>
<li>Subnet mask:</li>
<li>Gateway address (Optional):</li></ul></td>
</tr>
</tbody>
</table><img src="deltaend.gif" alt="End of change" />
<p><span class="bold">Windows Cluster Service information</span>
<br /></p>
<dl>
<dt class="bold"><span class="bold">Notes:</span></dt>
<dd>1. Fill in this work sheet only when installing a clustered integrated
server and your hardware model supports Windows Cluster service. (Integrated Netfinity&reg; Servers do not support Windows Cluster service.)
<p>2. Network
adapters are referred to as ports in i5/OS.</p>
</dd>
</dl>
<a name="wq104"></a>
<table id="wq104" width="100%" summary="" border="1" frame="border" rules="all" class="singleborder">
<thead valign="bottom">
<tr class="tablemainheaderbar">
<th id="wq105" width="18%" align="left" valign="top">Item</th>
<th id="wq106" width="49%" align="left" valign="top">Description and Instructions</th>
<th id="wq107" width="33%" align="left" valign="top">Value</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td valign="top" headers="wq105">Cluster name</td>
<td valign="top" headers="wq106">Specifies the name of the cluster. Administrators will
use this name for connections to the cluster. The cluster name must be different
from the domain name, from all computer names on the domain, and from other
cluster names on the domain.
<p>The cluster name is also used to create the
network server storage space that will be used as the Windows cluster quorum
resource.</p>
<dl>
<dt class="bold"><span class="bold">*NONE:</span></dt>
<dd>Do not form or join a Windows Cluster.
</dd>
<dt class="bold"><span class="bold">cluster-name:</span> </dt>
<dd>Specify the name of the cluster.
</dd>
</dl></td>
<td valign="top" headers="wq107">&nbsp;</td>
</tr>
<tr>
<td valign="top" headers="wq105">Cluster configuration:
<br />(Elements 1 - 4)</td>
<td valign="top" headers="wq106">Specifies the parameters required to configure a new
Windows Cluster.
<dl>
<dt class="bold"><span class="bold">Notes</span>:</dt>
<dd>This parameter is used to verify the i5/OS cluster configuration. The Microsoft configuration
wizards are used to install the Cluster service.
<p>This parameter is only
required when forming a new Windows cluster using the Cluster name (CLU)
parameter.</p>
</dd>
</dl>
<p><span class="bold">Element 1: Cluster domain name</span>
<br />Specifies
the domain to which the cluster belongs. If the cluster already exists, the
cluster will be joined, otherwise, the cluster will be formed. If forming
a cluster, the Cluster configuration (CLUCFG) parameter must be specified.</p>
<dl>
<dt class="bold"><span class="bold">cluster-domain-name:</span></dt>
<dd>Specify the domain name to which the cluster belongs when forming a
new cluster.
</dd>
</dl>
<p><span class="bold">Element 2: Quorum resource size</span> Specifies the
size in megabytes of the storage space used as the Windows quorum resource.</p>
<dl>
<dt class="bold">*CALC</dt>
<dd>Specifies that the size should be calculated to be the default value
based on the Windows server version (WNTVER) parameter.
</dd>
<dt class="bold">quorum-size</dt>
<dd>Specifies the Windows quorum resource size in megabytes. The size must
be at least 550 megabytes but no larger than 1024000 megabytes.
</dd>
</dl>
<p><span class="bold">Element 3: Quorum resource ASP</span>
<br />Specifies
the auxiliary storage pool for the storage space used as the Windows quorum
resource. Specify one of the following values:</p>
<dl>
<dt class="bold"><span class="bold">1:</span></dt>
<dd>The storage space is created in auxiliary storage pool 1, the system
auxiliary storage pool (ASP).
</dd>
<dt class="bold"><span class="bold">quorum-ASP:</span></dt>
<dd>Specify a value ranging from 2 through 255 for the ASP identifier.
Valid values depend on how many ASPs are defined on the system.
</dd>
</dl>
<p><span class="bold">Element 4: Quorum ASP device </span> Specifies the
independent auxiliary storage pool device name for the storage space used
as the Windows quorum resource. <span class="bold">Note:</span> You cannot specify
both a Quorum resource ASP and a Quorum ASP device value.</p></td>
<td valign="top" headers="wq107">
<p>Cluster domain name:</p>
<p>Quorum resource size:</p>
<p>Quorum resource ASP:</p>
<p>Quorum ASP device:</p></td>
</tr>
<tr>
<td valign="top" headers="wq105">Cluster configuration: (Elements 5-7)</td>
<td valign="top" headers="wq106">
<p><span class="bold">Element 5: Cluster connection port</span>
<br />Specifies the connection port used for the Cluster
service communication.</p>
<dl>
<dt class="bold"><span class="bold">*VRTETH<span class="italic">x</span>:</span></dt>
<dd>The network server virtual Ethernet port <span class="italic">x</span> is
configured, where <span class="italic">x</span> has a value of 0 through 9.
</dd>
</dl>
<p><span class="bold">Note:</span> The virtual Ethernet port must be configured
to match this value.</p>
<br />
<br /><span class="bold">Element 6:
Cluster Internet Address</span>
<br />Specifies the Internet
address for the cluster.
<dl>
<dt class="bold"><span class="bold">IP address:</span></dt>
<dd>Specify the cluster internet address in the form, xxx.yyy.zzz.nnn,
where xxx, yyy, zzz, and nnn are decimal numbers ranging from 0 through 255.
</dd>
</dl> <span class="bold">Note:</span> The Internet address selected must be unique
across all NWSD objects and the i5/OS TCP/IP configuration.
<p><span class="bold">Element 7: Cluster Subnet Mask</span></p>
<dl>
<dt class="bold"><span class="bold">subnet-mask:</span></dt>
<dd>Specifies the subnet mask for the cluster in the form, nnn.nnn.nnn.nnn,
where nnn is a decimal number ranging from 0 through 255.
</dd>
</dl></td>
<td valign="top" headers="wq107">
<p>Connection port:</p>
<p>Cluster Internet Address:</p>
<p>Cluster Subnet mask:</p></td>
</tr>
</tbody>
</table>
<a id="Bot_Of_Page" name="Bot_Of_Page"></a>
</body>
</html>
Reference in New Issue Copy Permalink