
EDR-3437 (SGI PCI HIPPI Interface controller card drivers and utilities for
Octane and Origin 200/2000).

RELEASE 1.0.6

IMPORTANT NOTE:  The driver/utility software is presently version specific
for Octane and Origin machines running IRIX 6.5. The driver is SMP, 
cray-link, and Multi-NIC capable. Installation of all core patches 
recommended by SGI is necessary for the proper operation of the driver.

INSTRUCTIONS FOR USE:

- Installation and Configuration of software driver for the SGI PCI HIPPI card.

INSTALLATION OF DRIVER

The following operations are performed as 'root' on the target system.

The kit is distributed in a tar file.  See the customer letter for location
of software kit. 

1.  Copy the distribution file H_IP27IP30_6.5_1.0.6.tar to the /usr/dist (or 
any working directory) directory.

	# su
	# cd /usr/dist (or any working directory you want)
	# cp <location of kit> H_IP27IP30_6.5_1.0.6.tar

2.  Extract the archive

	  # tar xvf H_IP27IP30_6.5_1.0.6.tar

After you have installed the Essential PCI-HIPPI NIC into your Octane or
Origin 200/2000, follow these steps (you must have root privileges), to setup 
the driver: 

NOTE: [ Make sure that if you have an Essential PCI driver already installed 
you use the Software Manager to remove the driver before installing a new one. ]

3.  Launch the Software Manager (swmgr or inst).

    i)   Start 'swmgr', this requires a graphics monitor.

    ii)  Enter <working_directory> (e.g. /usr/dist ) in the Available Software
         text box.

    iii) Click the Lookup button or press the Return key on your keyboard. The
         Software Manager will look for a distribution package in the working
         directory, and the Start button will be highlighted.

    iv)  Select "Default Installation." If you choose "Customize Installation", 
         the "Essential PCI-HIPPI for Octane/Origin..." installation package 
         should appear in the main window. Select the PCI-HIPPI installation 
         package under the Install heading; a check will appear in the 
         check-box.

    v)   Begin the installation by clicking the Start button.

    vi)  When the Software Manager has completed the driver software 
         installation, choose the Exit command from the File menu to close 
         the Software Manager.

If you are using 'inst',

    i)   Start 'inst'

    ii)  Enter your working directory with the "from" command.
         example:
            from <working_directory> (e.g. "Inst> from /usr/dist")

    iii) Select desired subsets with the install command.
         NOTE: This package is shipped with only one subset.

         example:
            install *

    iii) Begin the installation by typing 'go'

    iv)  When the installation program has completed the driver software 
         installation, type the 'quit' command to exit the installation 
         program.

4.  Reboot the system:

	# reboot

You have now completed installation of the Essential HIPPI driver software.

- CONFIGURATION OF DRIVER

Note: When configuring multiple cards, please be sure to include the card 
unit number. The card unit number is of the form essN, where N is the 
number of the card. For example, if you have 2 cards installed, the 
first card is called ess0 and the second card is called ess1. The 
commands that require the card unit number will be de-noted by the 
square `[ ]` braces.

You should make sure that /etc/init.d/Essnic.pre and Essnic.post files contain
the below information.

1. Modify /etc/init.d/Essnic.pre file to include:

	You will need an essarp -l statement, with the information about 
the Logical Switch address, for each card. 

Example:
	/usr/Essential/hippi/bin/essarp -l 00e [card unit number]

2. Modify /etc/init.d/Essnic.post file to include:

	You will need to set the Universal Lan Address (ULA) and logical 
address of the other machines on the HIPPI network as well as the machine 
you are on. To get the ULA of the machine you are on, type 'essarp -h', at
the UNIX prompt. 

Example:
        essarp -h
	ess0: UP RUNNING
        ess0: (201.22.134.45) ULA 00:b1:46:00:14:C6 Logical Address 0xe

	To set the ULA and LA for this and the other hosts on the HIPPI 
network, use the 'essarp -s' command. The syntax for 'essarp -s' is as 
follows:

    essarp -s <hostname> <ULA> <logical address> <card unit number> 

Example:
	essarp -s george-h 00:b1:46:00:14:C6 00e [card unit number] 
        essarp -s bill-h 00:b1:46:00:14:D7 102 [card unit number] 
	
	The above statements will add an ARP entry for the HIPPI host called
george-h, with a ULA of 00:b1:46:00:14:C6, and a Logical Address of 00e. And
another entry for the HIPPI host called bill-h, with a ULA of 00:b1:46:00:14:D7 and a Logical Address of 102.

3. Make sure an IP address and hostname has been assigned for each 
Network Interface Card (NIC), and the /etc/hosts file, NIS and/or DNS 
tables are updated, where applicable. If you are not sure abut the IP 
address and/or hostname for the NIC, please contact your system/network 
administrator.

4. Modify network config files in /etc/config.

    a) Modify the /etc/config/netif.options file and add the next two lines
corresponding with how many network devices that are already present:

Example:
        if2name=ess0
        if2addr=george-h

    b) Create the file /etc/config/ifconfig-X.options, where 'X' corresponds 
with the ifxname=ess0 (see above example) entry in the 
/etc/config/netif.options file. Add the following line.

Example:
	For the above example, the file would be called ifconfig-2.options, 
and it would contain the following: 

        netmask 0xffffff00 up

5. Setup tuning parameters.

You need to load correct tuning parameters into each
NIC's EEPROM by using the following script, as root:

/usr/Essential/hippi/scripts/esssetup.sh [card unit number]

6. Reboot the machine.

-----------------------------------------------------------------------------

Release Information

If you notice any problems report them to us, so that we can fix it on 
the next release.

1) NFS server problems that existed in 1.0.0, have been fixed.

2) Driver does not use system ARP tables anymore. All ARP information is 
   maintained in the driver.

3) The driver does not loopback IP packets through the hosts's local loopback
   interface. All IP packets are passed down to the NIC, regardless of 
   destination address. This feature can be used to verify connectivity 
   using tools such as 'ping' provided the ARP tables are setup correctly. 

4) ARP agent and IP broadcast agents are not supported. Direct connected
   systems process each other's ARP properly. Network connected NICs
   discover ARP properly if arp is manually configured using essarp -s

5) Control-C (^C) functionality for the character driver is supported.

6) Fixed a multi-processor Character driver problem, which existed on the 
   Origin 2000 platforms. 

7) Fixed multiple transmit thread panic, while using CDI mode.

