INSTALLATION AND CONFIGURATION INSTRUCTIONS FOR MADGE NETWORKS SMART
====================================================================
16/4 RINGNODES UNDER AIX 3.2 ON THE IBM RISC SYSTEM\6000
========================================================

April 1996
----------


Summary
-------

Two  types  of  Madge  Smart  Ringnodes  may  be  used in the IBM RISC
System/6000 running AIX 3.2,  the Madge Smart 16/4 MC Ringnode and the
Madge Smart 16/4 MC32 Ringnode.  The  driver  for  these  ringnodes is
called MTOKDD.  The following instructions describe how to install the
driver software and how to configure the driver for use.

Note: These  instructions  assume  you are installing the driver under 
      AIX 3.2.5.  Installation under different versions of  AIX  3.2.x
      will be similar, however  the wording of some "smit" options may
      differ.


0. CREATING AN INSTALLATION DISKETTE
------------------------------------

If  you  have received  your  Madge driver on an installation diskette
then you should skip this section and  proceed  directly to section 1.
This section describes how to create an installation diskette with the
installation diskette  image  file  mdgaix32.img  from the Madge CD or
bulletin board.

To create an installation disk:

    a) Log into your AIX system as "root".

    b) Copy the mdgaix32.img file into the /tmp directory.
 
    c) Place a blank formatted disk 3.5inch diskette in  the  diskette
       driver and enter the command:

       dd if=/tmp/mdgaix32.img of=/dev/fd0
     
    d) The diskette  is  now  an installation disk for your the MTOKDD
       driver.


1. INSTALLING THE DRIVER SOFTWARE FOR THE FIRST TIME
----------------------------------------------------

To install the MTOKDD software run the "smit" utility whilst logged in
as "root" and choose the following sequence of options:

    Software Installation & Maintenance
    Install / Update Software
    Install / Update Selectable Software (Custom Install)
    Install Software Products at Latest Available Level

You  will  then  be prompted for the name of the device containing the
software to be installed. Ensure that the MTOKDD installation diskette
is in the diskette drive and enter the text "/dev/fd0" if the diskette
is in the first (or only) drive, or "/dev/fd1" if it is in the second.
After pressing ENTER or selecting  "DO"  you  will be prompted for the
name of the software to install.  Enter the text  "mtokdd"  (in  lower
case)  and  press  ENTER  or select "DO".   Answer "OK" to the message
asking you if you are sure you wish to install the software.

The  installation process will now run.   This  takes around a minute.
 
Once the installation process has  completed  the driver software will
have  been  installed  into the correct places in the AIX file system.
However, the driver software will  not  have  been  configured for use
with an adapter.   Follow  the  instructions in section 3 to configure
the driver.


2. UPGRADING FROM AN EARLIER VERSION OF THE DRIVER
--------------------------------------------------

2.1 DE-CONFIGURING THE EXISTING DRIVER
--------------------------------------
 
Before installing the new software you must de-configure your existing
driver.
First terminate any applications you  may  have  running  that use any
Madge Ringnodes. Second use the following command to find out the name
of your Madge Ringnode devices:

    lsdev -C | more

You will see a list of device names in the left hand column and
descriptions in the right hand column.   There  should be an entry for
one or more Madge Ringnodes with device names "tok0",  "tok1",  "tok2"
etc.

Stop the TCP/IP stack from using any Madge Ringnodes by  entering  the
command:

    ifconfig XXX detach

for each ringnode.   "XXX"  is  "tr0"  for a ringnode with device name 
"tok0", "tr1" for a ringnode with device name "tok1" and so on.

Thirdly stop any other protocol stacks from using any Madge Ringnodes.
For example,  if  you  have  a  DLC  interface  installed  you  should
remove any DLC bindings to your Madge Ringnodes.    (This  may be done
from the Devices menu in "smit".)

Finally de-configure any Madge Ringnodes with the command:

    rmdev -l YYY -d

for each ringnode. "YYY" are the  Madge  Ringnode  device  names  e.g.
"tok0", "tok1" etc.


2.2 INSTALLING THE NEW DRIVER SOFTWARE
--------------------------------------

Follow  the  instructions  in  section  1  to  install  the new driver 
software and then proceed to section 3.


3. CONFIGURING THE DRIVER
-------------------------

The driver  software  is  now  installed  but  the driver has not been  
configured to work with any Madge Ringnodes.  That is  the driver does
not  known  what  slots  the  ringnodes  are  in  or what their memory 
requirements are.

   BEFORE PROCEEDING ENSURE THAT YOUR MADGE RINGNODE(S) ARE PHYSICALLY
   INSTALLED  IN  YOUR WORKSTATION  AND THAT THE LOBE CABLE(S) IS(ARE)
   PLUGGED IN.   IF  THIS NOTE THE CASE SHUTDOWN  YOUR WORKSTATION AND
   INSTALL  THE  RINGNODE(S)  AND  PLUG  IN  THE  LOBE CABLE(S) BEFORE 
   PROCEEDING.  OTHERWISE THE RINGNODE DRIVER  WILL  NOT  BE  PROPERLY
   CONFIGURED.

To  configure  the  ringnode  driver  run  "smit"  whilst logged in as 
"root".  Select the following sequence of options:

   Devices
   Configure Devices Added After IPL

The driver configuration process will now run. Once this has completed
your  ringnode  driver  will  be  configured  to  work with your Madge 
Ringnodes.

    PLEASE NOTE THAT BY DEFAULT THE MTOKDD DRIVER IS CONFIGURED TO RUN
    AT 16MB/S OVER STP MEDIA.IF THIS CONFIGURATION DOES NOT MATCH YOUR 
    INSTALLATION PLEASE CONSULT SECTION 6 ABOUT HOW TO CHANGE THE RING
    SPEED AND/OR MEDIA TYPE BEFORE PROCEEDING.

If you wish to start the TCP/IP stack select the following sequence of
"smit" options:

    Communications Applications and Services
    TCP/IP
    Minimum Configuration & Startup

From the list of options that is  displayed  choose  one  of the token
ring interfaces.  You  will now be prompted to fill in various details
about your  workstation such as its internet address and network mask.
Please  consult  the   IBM   AIX   documentation  and/or  your  system 
administrator about these details.


4. REMOVING A MADGE RINGNODE
----------------------------
 
Before removing a Madge Ringnode you should carry out the instructions
in section 2.1 to de-configure the driver.


5. MOVING A MADGE RINGNODE
--------------------------

If you need to move a Madge Ringnode to a different slot carry out the 
instructions in section 2.1 to de-configure the driver.   Shutdown and
power-down your  workstation.    Move  the  ringnode.    Re-start your
workstation and then follow the instructions in section 3 to configure
the driver.


6. CHANGING THE CHARACTERISTICS OF THE RINGNODE DRIVER
------------------------------------------------------

There  are  various  characteristics of your Madge Ringnode driver that
may be changed such as its node address and maximum frame size.   These
characteristics may be changed by running "smit".  First, however,  any
applications that use  the  ringnode  must be terminated and the TCP/IP
stack  must be stopped using the  "ifconfig XXX detach"  command   (see
section  2.1  - but do NOT de-configure the device with "rmdev").

Whilst  logged  in  as  "root"  run  "smit" and  select  the  following 
sequence of options:

    Devices
    Communications
    Token Ring
    Adapter
    Change / Show Characteristics of a Token Ring Adapter

From the list of Token Ring devices that is displayed choose the Madge
Ringnode of which you wish to change the characteristics.  "smit" will
then display a form containing the various characteristics. The values
that may be changed are described below:

    RING speed          
   
                         This is the speed at which your token ring is
                         running. It may be 4 or  16  (MBit/s).  Check
                         with  your   system   administrator  for  the 
                         correct value.

    DMA buffer size    

                         This is the number of KBytes of  memory  that
                         MTOKDD is  allowed  to  use for Direct Memory 
                         Access buffers.  The allowed range is 72-192.
                         The default value of 128 is  optimal  if  you
                         are using a 4096 byte maximum frame size. You
                         may  wish  to increase or decrease this value
                         if you change the maximum frame size. 

    Data cable type    
  
                         This is the type of lobe cable you are using.
                         There are two options, "stp" or "utp".  "stp"
                         is the thick cable with a "D" type connector.
                         "utp" is the  thin  cable  with  a  telephone
                         style connector.

    Data transfer mode for 16/4 MC32 ringnode

                         This characteristic allows you to change  the
                         DMA transfer mode used  on  Smart  16/4  MC32
                         Ringnodes.   Normally  there  is  no  need to
                         change the transfer mode.

                         Streaming  Enabled  permits  host  bus   data
                         transfer rates up to 40 MBytes/s in  machines
                         which support this option. Streaming Disabled
                         permits host bus data transfer rates up to 20
                         MBytes/s.
 
                         When Fair mode is selected, the MC32 Ringnode
                         enters an inactive state when it releases the
                         bus.  This  allows  the system to service any
                        other arbitrating devices in order of priority
                         before the ringnode requests the  bus  again.
                         In Unfair  mode,  the  Node  will immediately
                         re-request the bus after releasing it.

    DMA fairness for 16/4 MC ringnode
    Burst mode for 16/4 MC ringnode

                         These characteristics allow you to change the
                         DMA  transfer  mode  used  on  Smart  16/4 MC
                         ringnodes.   Normally there  is  no  need  to
                         change the transfer mode.

                         Fair/Unfair -  When  Fair mode  is  selected,
                         the MC Ringnode enters an inactive state when
                         it releases the bus.  This allows the  system
                         to service any other arbitrating  devices  in
                        order of priority before the ringnode requests
                         the bus again.  In Unfair mode, the  ringnode
                         will  immediately  re-request the  bus  after
                         releasing it.

                         Burst Mode  -  Four burst modes are available
                         for data transfer. The Delayed Release (Fair)
                         mode generally gives the best  results.   The
                         user may care to  experiment  with  the other
                         modes  which  may  be  better  in some system 
                         configurations (e.g. multiple  bus  masters). 

                         "Delayed Release": if  the  MC  Ringnode   is
                         transferring data when another adapter 
                         requests arbitration it  will  transfer about
                         14 more bytes before releasing the bus.  This
                         mode is not suitable if your system memory is
                         very  slow  or  only  8-bit wide,  as  a  bus
                         time-out may occur.

                         "Immediate Release": if the  MC  Ringnode  is
                         transferring data when another adapter  
                         requests  arbitration  it  will   immediately 
                         release the  bus.  This  has  the  effect  of
                         reducing the arbitration  latency  for  other
                         adapters.

                        "Limited Burst": in this mode, the MC Ringnode
                         will  never  transfer  more  than 18 bytes in
                         each  burst.   It also   releases   the   bus
                         immediately   if   another  adapter  requests
                         arbitration.

                         "Cycle Steal": in this mode, the  MC Ringnode
                         will never transfer more than 2 bytes in each
                         burst.  It will also release the bus 
                         immediately if another adapter requests
                         arbitration.   This  limits the bus bandwidth
                         used by the Node,  allowing  the  system  CPU
                         more processing time.


    Maximum FRAME SIZE  
1234567890123456789012345678901234567890123456789012345678901234567890   
                         This is  the  maximum size of frames that the
                         ringnode will send or receive.  The allowable
                         range  is 1024 to  17839 bytes.   The default
                         value is 4096 bytes.

    RECEIVE queue size  
   
                        This is the number of received frames that the
                         driver can queue before it refuses to receive
                         and more frames.    The allowable range is 20
                         to 150.

    STATUS BLOCK queue size
1234567890123456789012345678901234567890123456789012345678901234567890  
                         This is the number of  status events that the
                         driver can queue. The allowable range is 3 to
                         20.

    Receive ATTENTION MAC frames
    Receive BEACON MAC frames

                         These characteristics control whether 
                         attention and beacon MAC frames are passed up
                         to users of the ringnode driver.  Unless your
                        application specifically requires these frames
                         these characteristics should be  left  at the
                         default value of "no".

    Enable ALTERNATE TOKEN RING address

                         This   characteristics  controls  whether  an
                         alternate token ring address should be  used.
                         Normally the  ringnodes  uses  a  token  ring
                         address  that  is  stored  on  a  ROM  on the 
                         ringnodes.   Setting  this characteristic  to
                         "yes"  means  that  the  ringnode  will   the
                         address specified in the ALTERNATE TOKEN RING
                         address characteristic.

    ALTERNATE TOKEN RING address

                         This characteristic contains the  alternative
                         token ring address.  This should be  a twelve
                         digit hexidecimal  number  with  the  leading
                         digit in the range 4 to 7.e.g. 0x40001234abcd
                         The alternate token ring address is sometimes
                         called   a  "locally  administered  address".

    Apply changes to DATABASE only

                         Normally  any   changes   you   make  to  the
                         driver's characteristics  will   be   applied
                         to  the  driver  immediately;  which  is  why
                         there must not be any  applications using the
                         ringnode.  However if you set this 
                         characteristic to "yes" the changes will only
                         be  made to the configuration database.  This
                         means that the  changes  will  not  come into
                         effect until the machine is next shutdown and
                         re-started.

Once you have made any changes you require press ENTER or select "DO".
You can now re-start the TCP/IP stack.


7. TROUBLE SHOOTING
-------------------

If your Madge Ringnode fails to work correctly an  error  message  may
have been written into a file called "/tmp/mtokdd.log".   To view this
file enter the command:

    cat /tmp/mtokdd.log


Copyright (c) Madge Networks Ltd 1996

**** End of MTOKDD.INF ****

