
Installing IBM* Ethernet Quad-BT and -B2 PeerMaster* Server
Adapters into an AT&T System 3000 running AT&T UNIX SVR4
MP-RAS

========
Overview
========

The IBM Ethernet Quad PeerMaster adapter can operate in
either of two modes: traditional adapter mode or VNET
(Virtual Network) mode.  In traditional mode, the four ports
of a PeerMaster adapter are treated as separate adapters
operating on separate subnets, with unique MAC addresses.
Cross-subnet traffic must be routed, either internally by
the server, or externally by a local router.

When a PeerMaster adapter operates in VNET mode, the
multiple LAN segments to which the ports are attached are
treated as a single subnet,  called a VNET.  To protocol
stacks, such as TCP/IP and NetBIOS, a VNET appears to be a
single PPA.  Multiple PeerMaster adapters may be configured
to interoperate in various ways: as one large VNET (up to 24
segments when using 6 adapters); as multiple independent
VNETs; as traditional subnets; or in any combination of
VNETs and traditional subnets.  Each port within a VNET is
configured with the same MAC address.  Cross-segment traffic
within a VNET is switched by the adapter(s), shielding the
server from the task of handling and routing such traffic.
External internetworking devices are not required to provide
communication between segments of a VNET.

The following guidelines apply to PeerMaster adapters in
either traditional or VNET mode:

  *  Do not externally join (using bridges, switches, or
     concentrators) ports of adapters.
  *  You may configure as many nodes as necessary; the
     adapter places no limit on the number of nodes per
     segment.

For additional information on VNET Switch Mode refer to the
IBM Ethernet Quad PeerMaster Installation Guide provided
with your adapters.


================
Before You Start
================

Before you begin installing an IBM Ethernet PeerMaster
adapter into an AT&T System 3000 running AT&T UNIX SVR4 MP-
RAS, do the following:

1. Determine where the adapter is going to be installed; it
   can be installed in any empty MCA expansion slot.

2. Make sure you have a writable, working copy of the AT&T
   Reference Diskette. Also, make sure you label the
   diskette as the working copy of the AT&T Reference
   Diskette.

====================
Preparing the System
====================

Use the following procedure to prepare the system for IBM
Ethernet PeerMaster adapter installation:

1. Shut down the system by entering the following command:

   # shutdown -i0 -g0 -y

2. Turn the power switch of the console and of the system
   to the OFF position. Disconnect the system power cord
   from the rear panel of the system or from the wall
   outlet. On some models, you may also need to flip the
   circuit breakers and remove the CMOS battery fuse.

3. Install the IBM Ethernet Quad PeerMaster adapter into
   the desired slot as instructed in "AT&T 345x/35xx Unit
   Installation, Care and Cleaning".
   
   Note: The IBM Quad PeerMaster is a type 5 Micro Channel
          option adapter. To create sufficient clearance for
          type 5 adapters it is necessary to remove the
          brackets used to position and hold shorter option
          adapters.

4. Reboot the system from the AT&T Reference Diskette; make
   a copy of the Reference Diskette.

========================
Reconfiguring the System
========================

Perform the following procedures to reconfigure the system.

Change the Configuration

1. Press the ESC (escape) key to return to the main menu.

2. Select <Configuration> and then select <Install> or
   <FileCopy>.

3. When instructed to insert the new adapter diskette,
   remove the Reference Diskette and insert the IBM
   Ethernet Quad PeerMaster Option Diskette.

   Alternate diskettes as prompted until the process is
   complete.

4. From the Configuration menu, select <Change>.

5. Use the arrow keys to highlight the slot for the IBM
   Ethernet PeerMaster adapter and press the Enter key.
   Information such as the following will be displayed:

   Fixed resources           "Fixed resources"

   Device I/O Address         1C00h-1C1Fh

   Interrupt Level            Level 3

   MCA Arbitration Level      Level 1

   Streaming Data             Enabled

   Selected Feedback Return   Disabled

   Address and Data Parity    Disabled

6. Using the arrow keys and Enter key, choose values for
   the Device I/O Address, Interrupt Level, MCA Arbitration
   Level, Shared Memory Window Location, and Full Memory
   Window Location so that they do not conflict with other
   adapters or system resources. Conflicts are indicated by
   an asterisk to the left of the selected value.

7. Press the F10 key to save the selected configuration
   values.

   To install more than one IBM Ethernet PeerMaster
   adapter, repeat steps 5 through 7 for each additional
   PeerMaster adapter.

8. Press the Esc key to return to the CONFIGURATION menu.

=========================
Back Up the Configuration
=========================

1. Select <Backup>. A configuration backup file is written
   to the working copy of the AT&T Reference Diskette so it
   can be used to restore the configuration information, if
   necessary.

2. When the Backup is complete, remove the working copy of
   the AT&T Reference Diskette from the drive.

3. Press the Esc key as many times as necessary to exit the
   system setup; the system is automatically rebooted and
   the UNIX operating system is reloaded.

===================================
Installing PeerMaster Program Files
===================================

The MP-RAS program files for the PeerMaster adapter are
located on the MP-RAS Driver Diskette provided with your
adapter. The programs files are stored as an installable
package called xpm on the diskette. This section guides you
through the process of installing the xpm package on your
target system. To complete these steps you will need the MP-
RAS Driver Diskette.

1. Log in as root and make sure that the system date and
   time is correct.

2. Make sure that ild, the AT&T Integrated LAN Driver, is
   installed on your system. If you are not sure whether
   ild is already installed, enter the following command:

   # pkginfo -x ild

   This will indicate whether the package is installed and,
   if so, display the release number. If it is not
   installed, refer to the "Integrated LAN Driver
   Installation and Diagnostics" manual.

3. You might need to make adjustments to ILD tunable
   parameters for proper operation of your PeerMaster
   adpaters.

   As stated in the Integrated LAN Driver Installation and
   Diagnostics manual, the system tunable parameter
   STRTHRESH should be 25% to 50% of total system memory.
   See the "AT&T UNIX SVR4 MP-RAS Administrator Guide:
   Command Line Interface" for more information regarding
   STRTHRESH. To avoid running out of STREAMS resources you
   might need to modify this parameter. For example, use
   idtune to increase the value of this parameter to 8
   Megabytes as follows:

      # /etc/conf/bin/idtune STRTHRESH 0x800000
   
   To install more than four PeerMaster adapters it is
   necessary to increase the ILD tunable parameter,
   ILDMAXPPA, from the default of 16. The value of
   ILDMAXPPA must be greater than, or equal to, the total
   number of PeerMaster ports being installed. If
   necessary, use idtune to increase the value of this
   parameter as follows:
   
      # /etc/conf/bin/idtune ILDMAXPPA 24
        

4. Enter the following command to install the xpm package
   from the diskette:

   # pkgadd -d /dev/rdsk/f03ht xpm

5. Pkgadd will prompt you to insert a diskette into the
   drive. Insert the PeerMaster MP-RAS Driver Diskette,
   then type "go", followed by the Enter key.

6. After a few minutes, the following prompt will be
   displayed: "Do you want to use the existing
   configuration files?"  For an initial installation, type
   "y", followed by the Enter key. For a re-installation of
   the PeerMaster driver you might want to type "n",
   followed by the Enter key. This will cause the existing
   PeerMaster configuration files to be overwritten with
   default files provided by the xpm package.

7. The following prompt will be displayed: "Do you want to
   rebuild UNIX after this installation?"  Type "y",
   followed by the Enter key.

8. The software will now be installed on the system disk,
   and then the operating system will be re-linked to
   include the PeerMaster driver. This process will take a
   while to complete.

9. Upon completion of the re-build process, you will be
   prompted to re-boot the system. To configure PeerMaster
   adapters to operate in VNET (Virtual Network) Mode you
   should perform the instructions in this step prior to re-
   booting the system. Continue with step 10 (re-booting
   the system) to configure PeerMaster adapters to operate
   as multi-port traditional adapter cards.

   For information on VNET Mode, refer to the IBM Ethernet
   Quad PeerMaster Installation Guide provided with your
   adapters.

   Configuration information for the VNET feature of the
   PeerMaster driver is stored in the file
   "/etc/ild/vnetcf". A sample vnetcf file, with no VNETs
   configured, is included in the PeerMaster package.  The
   file is an ASCII text file which can be modified by
   using a standard UNIX text editor such as "vi" or "ed".
   Lines beginning with a '#' are comments, and are ignored
   by the VNET scripts. Lines which are not comments must
   contain four or more arguments, delimited by one or more
   tabs or spaces. The arguments are:

   a)  VNET number: This is an arbitrary number from zero
       to seven, chosen by the administrator, and used as a
       handle to initialize, un-initialize, and gather
       statistics regarding a VNET.
   
   b)  VNET aging: To support virtual networking
       functions, the PeerMaster driver dynamically builds
       and maintains an in-kernel MAC address table. This
       table, which may contain up to 4096 entries, is used
       to forward trasmitted packets to the appropriate
       adapter/port. Inactive entries may be purged on a
       periodic basis to prevent overflow of the table.
       This parameter specifies the time, in seconds, that
       unused entries shall be purged from the table. If
       set to zero, inactive entries will not be purged.
       The recommended default value for this parameter is
       60 seconds. Valid values range from 5 to 65535 (use
       decimal without commas). Values outside the
       acceptable range will be silently adjusted to the
       nearest valid value.
   
   c)  Maximum entries: This is the maximum number of
       entries created for a VNET's in-kernel address
       learning table. If set to zero, the default of 2048
       will be used. Valid values range from 128 to 4096
       (use decimal). Values outside the acceptable range
       will be silently adjusted to the nearest valid
       value.
   
   d)  Slot(s): This and optional subsequent arguments
       specify the slot number of PeerMaster adapters to be
       configured into this VNET.
   
       Note: Port 1 of the master adapter specified in each
             VNET becomes the "master PPA" for that VNET.
             The master adapter is defined to be the first
             adapter listed for the VNET, not the adapter
             with the least significant slot number. When
             configuring protocol stacks you must only
             "bind" the "master PPA" under the protocol
             stack.

Sample /etc/ild/vnetcfg files:

      The following examples show various ways in which
      three PeerMaster adapters in slots 3, 4, and 5, could
      be configured:

      #
      # VNET 1: Consisting of adapters in slots 3, 4, and 5
      #
      1   60   0   3   4   5

      #
      # VNET 1: Consisting of adapter in slot 3
      # VNET 2: Consisting of adapter in slot 4
      # VNET 3: Consisting of adapter in slot 5
      #
      1   60   0   3
      2   60   0   4
      3   60   0   5

      #
      # Slot 3: Adapter in traditional mode
      # VNET 1: Consisting of adapters in slots 4 and 5,
      #         4096 entries in the learning table.
      #         Port 1 of adapter 4 is the master PPA.
      #
      1   60   4096   4   5

      #
      # Slot 3: Adapter in traditional mode
      # VNET 1: Consisting of adapters in slots 4 and 5.
      #         Port 1 of adapter 5 is the master PPA.
      #
      1   60   4096   5   4

10.  The system must be re-booted to load the newly built
     kernel. Enter the following commands to re-boot the
     system:

     # cd /
     # shutdown -y -i6 -g0

11.  Allow the newly built kernel to boot, then log in as
     root.

12.  Enter the following command to generate the ILD
     configuration file, /etc/ildcf, for all LAN adapters
     present:

     /etc/ildbldcf

     For more information on aspects of ILD configuration,
     please see the Integrated LAN Driver Installation and
     Diagnostics manual.

13.  Protocols, such as TCP/IP, must be configured to use
     the PeerMaster adapters. See the appropriate guide for
     protocol installation and configuration information.

     IMPORTANT:
     When binding protocol stacks to VNETs you must only
     bind the "master PPA" under the protocol stack. The
     "master PPA" for each VNET is Port 1 of the master
     adapter specified in the vnetcfg configuration file
     (not necessarily the adapter installed in the least
     significant slot number). Although non-master PPA's of
     the VNET cannot prevent binds they will fail transmit
     requests from protocol stacks bound to them.  Frames
     sent to the "master PPA" will be transmitted to the
     appropriate adapter/port(s). From the protocol's
     perspective, all frames received from all of the VNET's
     ports will appear to have been received from the
     "master PPA".

You have now completed the installation of your Quad
PeerMaster adapter. The following sections provide
additional information pertaining to:

  * PeerMaster POST Error Messages
  * PeerMaster Initialization Messages
  * PeerMaster Runtime Messages
  * PeerMaster Custom Statistics
  * PeerMaster Tunable Parameters
  * vnet Script: Manually Starting and Stopping VNETs
  * vnetconfig: Query/Change VNET configurations
   

==============================================
PeerMaster POST Error Messages
==============================================

PeerMaster adapters contain on-board Power-On-Self-Tests
(POST) that run each time the adapter powers up or is
restarted. POST results are verified by the driver prior to
downloading and initializing the adapter. Should POST fail,
the PeerMaster driver passes the error to the STREAMS error
log and displays the error on the console as follows:

     Adapter POST failed, Code=N

The driver will not download or initialize the adapter if
POST completes unsuccessfully. Should your driver report a
POST error, record the error code and use the following
table to interpret and respond to the error.

POST
Error #             Description
-------             --------------------------

  1       Message:  POST Flash Main Sector Checksum Failure
          Action :  Call for service.

  2       Message:  POST was not performed - board restarted
          Action :  Call for service.

  3       Message:  POST Test Sequencer Internal Failure
          Action :  Call for service.

  4       Message:  POST Flash Boot Sector Checksum Failure
          Action :  Call for service.

  5       Message:  POST DRAM Size Detection Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

  6       Message:  POST DRAM Byte  (8 bit) Wide Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

  7       Message:  POST DRAM Short (16 bit) Wide Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

  8       Message:  POST DRAM Word (32 bit) Wide Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

  9       Message:  POST DRAM Long (64 bit) Wide Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

 10       Message:  POST DRAM Trip (96 bit) Wide Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service

 11       Message:  POST DRAM Quad (128 bit) Wide Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

 12       Message:  POST DRAM Addressability Failure
          Action :  Power down the server. Verify proper
                    seating of the DRAM SIMM on the board
                    and try again. If failure persists, call
                    for service.

 13       Message:  POST SRAM Size Detection Failure
          Action :  Call for service.

 14       Message:  POST SRAM Byte (8 bit) Wide Failure
          Action :  Call for service.

 15       Message:  POST SRAM Short (16 bit) Wide Failure
          Action :  Call for service.

 16       Message:  POST SRAM Word (32 bit) Wide Failure
          Action :  Call for service.

 17       Message:  POST SRAM Long (64 bit) Wide Failure
          Action :  Call for service.

 18       Message:  POST SRAM Trip (96 bit) Wide Failure
          Action :  Call for service.

 19       Message:  POST SRAM Quad (128 bit) Wide Failure
          Action :  Call for service.

 20       Message:  POST SRAM Addressability Failure
          Action :  Call for service.

 21       Message:  POST Timer Failure
          Action :  Call for service.

 22,23    Message:  POST Ethernet Port N Internal Loopback
 24,25                   Failure (N = 1, 2, 3, or 4)
          Action :  Call for service.

 26,27    Message:  POST Ethernet Port N External Loopback
 28,29                   Failure (N = 1, 2, 3, or 4)
          Action :  Call for service.

 30,31    Message:  POST Ethernet Port N Device Verification
 32,33                   Failure (N = 1, 2, 3, or 4)
          Action :  Call for service.


==============================================
Initialization Messages
==============================================

At system boot time the PeerMaster driver may display the
following messages:

Message:   Insufficient memory for adapter structures.
Sent to:   This message is sent to the system console.
Action :   This message indicates the system denied the
           drivers request to allocate memory. Verify the
           amount of memory in your system and check system
           tuning parameters such as STRTHRESH. For more
           information on system tuning refer to the
           "Integrated LAN Driver Installation and
           Diagnostics" manual.

Message:   Adapter initialization step N failed.
Sent to:   This message is sent to the system console and
           the STREAMS error log.
Action :   This message indicates the driver unable to
           communicate with the adapter. Record the error
           number and call for service.

Message:   Adapter Disabled.
Sent to:   This message is sent to the system console and
           the STREAMS error log.
Action :   This message indicates the adapter is not
           properly configured. Boot from the Reference
           Diskette and check for configuration conflicts.

Message:   Duplicate <I/O or Shared Window> Address.
Sent to:   This message is sent to the system console and
           the STREAMS error log.
Action :   This message indicates the adapter is not
           properly configured. Boot from the Reference
           Diskette and check for configuration conflicts.


==============================================
Runtime Messages
==============================================

During normal operation the driver may log the following
messages.

Message:   Adapter did not respond to Watchdog.
Sent to:   This message is sent to the STREAMS error log.
Action :   This message indicates the adapter failed to
           respond to a watchdog timer request sent from
           the driver. This is reported if the adapter
           fails to respond to periodic requests sent by
           the driver. When this occurs, the driver will
           automatically reset and reinitialize the
           adapter. No action is required, however, if the
           problem persists, call for service.

Message:   Slot N: Ethernet Media Port N Tx Carrier Sense
           Errors, check your cable
Sent to:   This message is sent to the STREAMS error log.
Action :   This message indicates that the adapter detected
           a loss of Tx carrier on the specified Slot/Port.
           Verify proper connection of the attached cable.

Message:   Slot N: Ethernet Media Port N Tx Carrier Sense
           Errors corrected
Sent to:   This message is sent to the STREAMS error log.
Action :   This message indicates that the adapter detected
           the recovery of a loss of Tx carrier on the
           specified Slot/Port.

==============================================
PeerMaster Custom Statistics
==============================================

Traditional PeerMaster statistics may be displayed using the
ILD /etc/ild/macstats utility. PeerMaster switch-related
statistics, however, cannot be viewed via macstats.  The
utility, /etc/ild/xpmstats, is provided with the PeerMaster
adapter to display these custom statistics.

Invoke xpmstats as follows to display a list of supported
parameters:

     # /etc/ild/xpmstats ?

xpmstats will display the following:

usage: xpmstats [-b][-e][-i][-d][-a][-p][-v][# ...]
   where:
    -b      = display Bridge statistics
    -e      = display Ethernet statistics
    -i      = display Interface statistics
    -d      = display statistics in decimal
              notation (default is hex)
    -a      = list of specific Adapters
              follows
    -p      = list of specific PPA's follows
    -v      = list of specific VNets follows

The -b option displays the following bridge statistics for
each configured PeerMaster adapter:

   Peer   InFrames = 0  OutFrames = 0  InDiscards = 0
   Port 1 InFrames = 0  OutFrames = 0  InDiscards = 0
   Port 2 InFrames = 0  OutFrames = 0  InDiscards = 0
   Port 3 InFrames = 0  OutFrames = 0  InDiscards = 0
   Port 4 InFrames = 0  OutFrames = 0  InDiscards = 0

     Bridge statistics are defined as follows:
     
     Peer InFrames: The number of packets that were sourced
     by peer adapters to this PeerMaster adapter.
     
     Peer OutFrames: The number of packets that were sent by
     this PeerMaster adapter to peer adapters.
     
     Peer InDiscards: The number of packets that were
     sourced by peer adapters to this PeerMaster adapter
     that were discarded (filtered) by the Forwarding
     Process.
     
     Port N InFrames: The number of packets received by port
     N that were passed to the switching function.
     
     Port N OutFrames: The number of packets passed from the
     switching function to port N.
     
     Port N InDiscards: The number of packets received by
     port N that were filtered by the switching function.
     

You may use the -e and -i options to display traditional
statistics for each configured PeerMaster adapter.

You may use the -a, -p and -v options to select specific
adapters/ports/vnets respectively. Statistics will be
displayed only for those adapters/ports/vnets that are
selected.


==============================================
PeerMaster Tunable Parameters
==============================================

The file /etc/conf/cf.d/mtune contains tunable parameters
used by the UNIX kernal and installable packages. The
default values installed for the PeerMaster are adequate for
most network configurations with high data rates. If changes
from the default setting are required, use the UNIX idtune
command to change the PeerMaster tunable parameters. Do not
directly edit the mtune or stune files. The format of the
command is as follows:

  /etc/conf/bin/idtune <param_name> <value>

This command adds an entry to the /etc/conf/cf.d/stune file.
The mtune and stune files are read during the kernel build
process. The values in these files are used to set kernel
and PeerMaster driver variables.

Note:  Changes made by idtune will not take affect until
       the kernal is rebuilt and the system rebooted.

The following table lists the PeerMaster Driver Tunable
Parameters:

----------------------------------------------
Parameter      Default   Minimum   Maximum
----------------------------------------------
XPM_NRXDESC    32           8      64
XPM_NTXDESC    16           8      64
XPM_MACTXQLIM  200          32     1000
XPM_BAGING     0x7FFFFFFF   0      0x7FFFFFFF
XPM_BSMINTVL   7            0      0xFFFF
XPM_ISMINTVL   7            0      0xFFFF
XPM_WDINTVL    0            0      0xFFFF
XPM_LINTEG1    0x01010101   0      0x01010101
XPM_LINTEG2    0x01010101   0      0x01010101
XPM_LINTEG3    0x01010101   0      0x01010101
XPM_LINTEG4    0x01010101   0      0x01010101
XPM_LINTEG5    0x01010101   0      0x01010101
XPM_LINTEG6    0x01010101   0      0x01010101
XPM_LINTEG7    0x01010101   0      0x01010101
XPM_LINTEG8    0x01010101   0      0x01010101
----------------------------------------------

XPM_NRXDESC - Number of receive descriptors configured in
each PeerMaster adapter's shared memory.

XPM_NTXDESC - Number of transmit descriptors configured in
each PeerMaster adapter's shared memory.

XPM_MACTXQLIM - Maximum number of transmit frames that will
be queued to a MAC PPA, in addition to those that are queued
on the adapter's transmit descriptors.

XPM_BAGING - Time interval, in seconds, that inactive
entries will remain in the adapter-based address learning
tables (only affects VNET mode). The default value of
0x7FFFFFFF provides an aging value of 60 seconds. A value of
zero disables aging.

XPM_BSMINTVL - Time interval, in seconds, indicating how
often an adapter's Bridge Statistics are transferred to
system memory (only affects VNET mode).

XPM_ISMINTVL - Time interval, in seconds, indicating how
often each ports's Interface Statistics are transferred to
system memory.

XPM_WDINTVL - Time interval, in seconds, indicating how
often a Watchdog command/reply must be exchanged between the
driver and adapter. A value of zero disables the watchdog
function.

XPM_LINTEG1 thru XPM_LINTEG8 - The link integrity option,
used to configure Link Pulse generation and testing on a per-
port basis. XPM_LINTEG1 represents the first configured
PeerMaster adapter (not necessarily in slot 1), XPM_LINTEG2
represents the second configured PeerMaster adapter, and so
on. The value is a 32 bit hex value as follows:

   wwxxyyzz

   where:
     ww = Port 4 Link Pulse ControlValue
     xx = Port 3 Link Pulse ControlValue
     yy = Port 2 Link Pulse ControlValue
     zz = Port 1 Link Pulse ControlValue

     and ControlValue is an 8-bit hex value as follows:

     01 = Link Pulse enabled
     00 = Link Pulse disabled

Thus, a value of 0x01010101 enables link integrity for all
ports of an adapter. A value of 0x01000100 enables link
integrity for ports two and four and disables link integrity
for ports one and three of an adapter.

=================================================
VNET Script: Manually Starting and Stopping VNETs
=================================================

When the UNIX operating system is being brought up to run-
level 2 or higher, the "vnet" script is invoked with the
"start" argument.  The script parses the file
/etc/ild/vnetcf, and invokes /etc/ild/vnetconfig to
initialize each configured VNET.  This automatic action
takes place after the ILD has been started, but before
protocol stacks have been started.

When the system is being shut down or rebooted, the "vnet"
script is invoked with the "stop" argument.  The script
invokes /etc/ild/vnetconfig to un-initialize all active
VNETs. This automatic action takes place after protocol
stacks have been stopped, but before ILD has been stopped.

To make dynamic changes to the current VNET configuration,
this script can be run manually. First, stop all VNETs, make
the desired changes to /etc/ild/vnetcf, then re-start VNET
to activate the new configuration. The following command
stops the current VNET configuration:

     /etc/init.d/vnet stop

The following command starts a VNET configuration:

     /etc/init.d/vnet start

NOTE:
  All errors will be written to file /tmp/vnet.err. Some
  harmless errors will be written to /tmp/vnet.err when
  attempting to bring VNETs into a state when they are
  already in that state, for example: when attempting to
  "stop" VNET when going from run-level 1 to run-level 0,
  or in attempting to "start" VNET when going from run-
  level 2 to run-level 3.


==============================================
vnetconfig: Query/Change VNET configurations
==============================================

The "vnetconfig" utility, /etc/ild/vnetconfig, is used to
initialize and un-initialize VNETs, and to display the
current VNET configuration(s). Under typical system
operation, vnetconfig is automatically invoked, as the
system is being brought up, to initialize VNETs configured
in /etc/ild/vnetcf.  During system shutdown, vnetconfig is
automatically invoked to un-initialize any configured VNETs.
"vnetconfig" can also be used to manually initialize or un-
initialize a VNET configuration. Manual re-configuration
information is not retained across shutdowns or reboots.

The vnetconfig utility may be invoked as follows to display
the current vnet configuration:

  vnetconfig -i [vnetno ...]

  The "-i" format of the command displays VNET number, age,
  maximum entries, and adapter slot information for the
  specified VNETs. If no "vnetno" argument is entered,
  information is displayed for all currently configured
  VNETs.

The following format of the command is used to initialize a
VNET.

  vnetconfig [-a age]
             [-m maxentries]
             vnetno
             adapter [adapter ...]

  The "-a aging" option sets VNET aging. The PeerMaster
  driver dynamically builds and maintains an in-kernel MAC
  address table to support VNET functions. This table,
  which may contain up to 4096 entries, is used to forward
  trasmitted packets to the appropriate adapter/port.
  Inactive entries may be purged on a periodic basis to
  prevent overflow of the table. This parameter specifies
  the time, in seconds, that unused entries shall be purged
  from the table. If set to zero, inactive entries will not
  be purged.  The recommended default value for this
  parameter is 60 seconds. Valid values range from 5 to
  65535 (use decimal without commas). Values outside the
  acceptable range will be silently adjusted to the nearest
  valid value.

  The "-m maxentries" option sets the maximum number of
  entries that can be inserted into a VNET's in-kernel
  address learning table. If set to zero or not selected, a
  default of 2048 will be used. Valid values range from 128
  to 4096 (use decimal). Values outside the acceptable
  range will be silently adjusted to the nearest valid
  value.

  "vnetno" is an arbitrary number from zero to seven,
  chosen by the administrator, and used as a handle to
  initialize a VNET. The command will fail if another VNET
  is already configured with this VNET number.
  
  "adapter" is the slot number of the PeerMaster adapter(s)
  to be configured into this VNET. The command will fail if
  this adapter is already a member of a VNET.

The vnetconfig utility is invoked as follows to un-
initialize a specified VNET:

  vnetconfig -u vnetno
  
  The "-u" format of the command un-initializes the
  specified VNET. Protocols are not able to transmit or
  receive packets from the ports controlled by un-
  initialized VNETs. For this reason, it is recommended to
  shut down protocols before un-initializing VNETs. The
  command will fail if no VNET is currently configured with
  this VNET number.


----------------------------------------------
TRADEMARKS
----------------------------------------------

The following terms, denoted by an asterisk (*) in this
README file, are trademarks of the IBM Corporation in the
United States or other countries:

IBM          PeerMaster


IBM DISCLAIMS ALL WARRANTIES, WHETHER EXPRESSED OR IMPLIED,
INCLUDING WITHOUT LIMITATION, WARRANTIES OF FITNESS AND
MERCHANTABILITY WITH RESPECT TO THE INFORMATION IN THIS
DOCUMENT.  BY FURNISHING THIS DOCUMENT, IBM GRANTS NO
LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.

(c) Copyright IBM Corporation, 1995.  All rights reserved.

U.S. Government Users Restricted Rights - Use, duplication,
or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp.


