Before configuring the IRIS HIPPI software, you need to decide whether or not you want the driver to include support for the IP network stack. The configuration steps are slightly different depending on this decision.

Use the command below to verify the version or to check if the IRIS HIPPI software has been installed.

% versions hippi
I HIPPI date IRIS HIPPI, version

The /var/sysgen/system/hippi.sm file or /var/sysgen/system/hippi_s.sm file tells the system's software which IRIS HIPPI modules to include when it builds the IRIS HIPPI driver into the operating system. Use the hippi.sm file when the copper-based IRIS HIPPI board for Challenge or Onyx is installed; use the hippi_s.sm file with the fiber-based HIPPI-Serial board for Origin2000 or Onyx2. The default file builds IP networking and, when available, BYPASS functionality into the driver.

---

Caution: Do not delete any entries in this file. The operating system (kernel) cannot link properly unless each entry exists, either as an INCLUDE or EXCLUDE.

---

The following line in either the hippi.sm or hippi_s.sm file can be edited to build an IRIS HIPPI driver that does not support IP networking:

---

Note: When the driver is built with IP support, but the IP protocol stack is not enabled, each time the system is started some error messages are displayed; the HIPPI functionality is all right.

---

For Origin2000 or Onyx2 systems only, the following line in the hippi_s.sm can be edited to build an IRIS HIPPI driver that does not support BYPASS functionality:

If you exclude IP or BYPASS functionality, then decide later that you want the function, you must undo the edit (or edits), then, rebuild (autoconfig) the operating system.

The /var/sysgen/master.d/if_hip file configures the IRIS HIPPI driver and board. Driver and board configuration is optional, because all parameters have default settings. The settings in this file affect all IRIS HIPPI boards installed in the system.

The IRIS HIPPI driver and board have very few configurable parameters (for example, the size for the maximum transmission unit and onboard IP checksumming). The specific items vary from release to release, so they are explained fully within the file.

The /usr/etc/hippi.imap file maps hostnames (or IP addresses) to HIPPI I-fields. Optionally, for systems with HIPPI boards that do not store a media access control (MAC) address^[6] , a 6-byte universal IEEE address (called ULA or MAC address) can also be mapped. The file can contain up to 2048 lines.

Each time the HIPPI-LE upper layer protocol (ULP) module is about to program the HIPPI subsystem's source channel to issue a connection request, it obtains the I-field for its destination from a lookup table that has been loaded into memory at startup time. The lookup table maps IP addresses or hostnames to HIPPI I-fields. This table is generated (at startup time) from the hippi.imap file and can be modified in real time with the hipmap command.

Each I-field is a 32-bit value. Each line (entry) in the file can have any of the formats illustrated below:

The IRIS HIPPI software does not check or verify these values. It is the system administrator's responsibility to ensure that each entry is both valid and correct. The I-field value must be the exact I-field for use in the connection request; for example, it must contain the desired settings for the camp-on bit and, if logical addressing if used, the source's address.

Figure 2-1 is a template that can be used for developing each 32-bit I-field for a logical addressed environment; Figure 2-2 is for developing source addressed I-fields. The templates show the values that SGI recommends for use by the IRIS HIPPI-LE upper layer protocol.

---

Note: If the IRIS HIPPI source is connected directly to another HIPPI endpoint (no switch is involved), the lookup table on each system should contain only one line. This single I-field value at each system can be 0x00000000, if the destination implementation accepts this value.

---

Figure 2-1. Template for Creating Logical Addressed I-fields With Recommended Values

Figure 2-2. Template for Creating Source Addressed I-fields With Recommended Values

If IRIS HIPPI is already functioning, and you want to load additional entries into the map currently in memory, the following command can be invoked as superuser:

# /usr/etc/hipmap -f /usr/etc/filename

If IRIS HIPPI is functioning, and you want to load an entirely new map into memory (and to erase the old entries), the following command can be invoked as superuser:

# /usr/etc/hipmap -D -f /usr/etc/hippi.imap

To configure the IP networking interfaces, edit the /etc/hosts and /etc/config/netif.options files, as explained below.

Each time the IP software starts, it uses information from these two files to configure the IP interfaces.

---

Note: For additional details about enabling the IP networking software and configuring network interfaces, refer to the IRIX Site Administrator's Guide, which is available online through IRIS Insight™ or in hardcopy.

---

223.9.1.2   hippi1-goofy.toons.com  hippi1-goofy
223.9.2.4   hippi2-goofy.toons.com  hippi2-goofy
223.9.3.16  hippi3-goofy.toons.com  hippi3-goofy
223.9.4.32  hippi4-goofy.toons.com  hippi4-goofy

The /etc/config/netif.options File

The /etc/config/netif.options file maps local hostnames (or IP addresses) to IRIS HIPPI network interfaces (for example, hip0, hip1, etc.). There must be a two-line entry for each IRIS HIPPI board that services the IP network stack. The first entry (if1addr and if1name) defines the primary interface; in most situations, the primary interface should be Ethernet or FDDI. Each hostname or IP address in this file must also be in the /etc/hosts file; the hostnames or IP addresses in the two files must be identical.

Systems that function as a client or server for bootp should configure Ethernet as their primary network interface. Any system that functions as a client or server for NFS, NIS, or other client/server program should configure the network interface over which the client/server functions occur as the primary network interface.

The example below illustrates a system with three IRIS HIPPI network interfaces, an FDDI interface (that is, xpi0), and a primary Ethernet interface. If this system's hostname is goofy, these IRIS HIPPI entries interwork with the examples of /etc/hosts file entries shown above.

if1name=et0 if1addr=$HOSTNAME if2name=xpi0 if2addr=fddi-$HOSTNAME if3name=hip0 if3addr=hippi1-$HOSTNAME if4name=hip1 if4addr=hippi2-$HOSTNAME if5name=hip2 if5addr=hippi3-$HOSTNAME

---

Note: The use of the $HOSTNAME variable assumes that the system's hostname has been defined in the /etc/sys_id file.

---

To automatically enable the IP network stack each time the system is started, edit the /etc/config/network file so that it contains the single word ON or on. If the file is missing, add the file or invoke chkconfig network on.

---

Note: Enabling IP networking does not result in IP over HIPPI; it only enables the IP software within the operating system to operate over whatever drivers are available to service it.

---

This section describes how to rebuild the operating system. All the configuration steps listed in the “Overview of Configuration Steps” must be performed before the operating system is rebuilt.

For the IRIS HIPPI subsystem to be functional, the IRIX operating system (kernel) that is currently on the system must be rebuilt to include the IRIS HIPPI driver. When changes are made to any of the following files, or when new IRIS HIPPI software is installed, it is necessary to rebuild the operating system:

The three sets of instructions below each build a new operating system and start it running. It is not important which set of instructions is used.

Instruction Set 1

% su
Password: thepassword
# /etc/init.d/autoconfig
Automatically reconfigure the operating system (y or n)? y
<log on>
% su
Password: thepassword
# /etc/reboot
.....<various messages are displayed on console>...
configuring hip0 as hostname 
configuring hip1 as hostname 

Instruction Set 2

% su
Password: thepassword
# /etc/shutdown

When the system shuts down, restart it. When this question is displayed, answer with yes or y.

Automatically reconfigure the operating system (y or n)? y
<log on>
% su
Password: thepassword
# /etc/shutdown

Instruction Set 3

Use the same sequence as Set 2; however, instead of the /etc/shutdown command, use any of the following: