This chapter provides instructions and information about configuring the IRIX GSN software, as summarized in this list.
The entire installation and configuration procedure is covered in “Complete GSN Installation Process”.
The following sections provide quick-reference summaries of the configuration tasks required for specific functionality:
Each specific configuration task is described separately in detail in the reference section “Individual Configuration Tasks”.
Table 2-2 provides a listing of all the individual parameters in IRIX GSN that can be configured.
See “Assignment of Unit Numbers and Network Interfaces to GSN Hardware” in Chapter 1 for a description of how the physical network devices (gsn0, gsn1, gsn2, and gsn3) are numbered and assigned to IP/ST-over-GSN logical network interfaces (gsn0, gsn1, gsn2, and gsn3).
This section lists the steps required for configuring your IRIX GSN network connection. The procedures listed below are those that must be performed before an IRIX GSN connection is functional:
Use inst or the System:SoftwareManager to install the IRIX GSN software from CD-ROM, as explained in the IRIX GSN Release Notes. The inst command is described in the online man page and the InSight document IRIX Admin: Software Installation and Licensing that came with the system.
Collect the information you need for the configuration, as described in “Collect Information Before Starting”.
Follow the steps in the section “Configure IP-over-GSN” to configure the IP–over–GSN and ST-over-GSN stacks.
Optional: change the default settings for optional configuration tasks, as summarized in Table 2-2 .
Note: If the system has more than one GSN network interface, the netmask values are not optional; they must be set as described in “Summary of Network Interface Operational Parameters and Default Settings”. Use the decision tree provided in “Configure the Address Resolution Service” to determine which set of HARP configuration instructions you need to follow. Then follow those instructions.
If there are any members of the LIS that do not support dynamic HARP, follow the instructions in “Adding Static HARP Table Entries”.
Arrange to have the hardware installed and its functionality verified as described in SGI GSN XIO Hardware Installation Instructions for SGI Origin Family, SGI\x15 2000\x15 series, and Silicon Graphics Onyx2 Platforms.
It is most efficient to install the IRIX GSN hardware after installing and configuring the software. This avoids at least one reboot of the system.
Note: If the hardware is already installed, follow the instructions in the section “Building a New Driver Into the Operating System”.follow the instructions in “Verify That the Board Has Been Located by the Software” in Chapter 3 and “Verify the SGI GSN Hardware” in Chapter 3 to verify the functionality of the GSN hardware.
To configure the IRIX GSN software, you need the following information. SGI recommends collecting this information before you start to configure the software.
An INET (also known as IP) address and, optionally, a subnet mask for each IP/ST-over-GSN network interface.
If there are multiple GSN network interfaces on this system, each interface must belong to a different LIS. That is, the address and mask for each interface must identify all the interfaces on the system as members of different address spaces (LISs). See “GSN Fabrics and Logical Networks” in Chapter 1 and Figure 1-30 for further explanation.
A network connection name for each INET address. This name usually includes the system's hostname (as configured in the /etc/sys_id file). An example is: gsn3-amazon.
If the GSN port is connected to a GSN switch, answer these questions:
Do all the switches in the GSN fabric support broadcasting?
Does this system have multiple GSN network interfaces?If the answer to either of these questions is yes, collect the information listed below. Otherwise, you are through collecting information; you can proceed to the next step in the installation procedure (step 3 in the “Complete GSN Installation Process”).
If broadcasting is not supported by the GSN fabric, determine the ULAs of the HARP servers for each LIS. (The same HARP servers must be used for all members of an LIS.)
For each GSN interface, identify all members of its LIS that do not support dynamic HARP.
This section describes how to configure the IP-over-GSN and ST-over-GSN network interface. All these steps are standard IP configuration procedures, required for all IRIX network interfaces.
Enable the network layer stack:
# chkconfig network on
Open the local /etc/hosts file for editing. For each GSN physical port, add an entry (like the one below) that maps an INET address (for example, IP address) to a GSN network connection name (“hostname”). Each address is shared by both the IP and ST protocols. (See “Edit hosts File” for detailed instructions.)
gsn-amazon 223.209.1.18
Note: The local hosts file must be edited. In addition, if the site uses an NIS or DNS server, this information must be added to that server's database. Open the /etc/config/netif.options file for editing. For each GSN physical port, add a pair of entries (similar to the pair below) to map the GSN network interface (gsn#) of the port to one of the INET/IP addresses (or network connection names) from the hosts file. (See “Edit netif.options File” for detailed instructions.)
if2name=gsn0 if2addr=gsn-amazon
Edit the /etc/config/ifconfig-#.options file for one or more of the GSN network interfaces to change the default settings for the operational parameters that are listed in Table 2-1. This step is required if there is a subnet mask (netmask) for this network interface; otherwise, this step is optional. (See “Edit ifconfig-#.options File” for detailed instructions.)
Optional: edit the /var/sysgen/master.d/gsn file to change default settings in the IP/ST-over-GSN driver. (See “Edit master.d/gsn File” for detailed instructions.)
If this is the final configuration step, rebuild the operating system so that it includes the newly configured IRIX GSN driver:
% su Password: thepassword # /etc/init.d/autoconfig Automatically reconfigure the operating system (y or n)? y # /etc/shutdown
The system is now ready to have its IRIX GSN hardware installed, or if the hardware is already installed, you can restart the system. The IP/ST-over–GSN functionality automatically becomes operational during this restart.
To verify this configuration, follow the procedures described in “Verifying the IRIX GSN Subsystem” in Chapter 3 once the hardware is installed.
ST-over-GSN address configuration occurs when you follow the instructions in “Configure IP-over-GSN”. Follow the IP instructions even if your site does not plan to use the IP–over–GSN stack.
If any of the following statements are true for your configuration, you must manually configure IRIX HARP, as follows:
The SGI GSN port is directly connected to another host, not to a switch.
One or more of the switches in the GSN fabric does not support broadcasting.
One or more of the hosts on the LIS does not support dynamic HARP.
For each GSN connection/interface, use the decision tree shown in Figure 2-1 to discover which procedures are required for configuring the address resolution software.
This section provides detailed instructions for each individual configuration task. This is a reference section only; the tasks appear in alphabetical order, and are listed below. Most of these tasks are optional. See “Complete GSN Installation Process” for the list of required configuration tasks.
-
Note: For additional details about enabling IP networking software and configuring IP network interfaces, refer to IRIX Admin:Networking and Mail, which is available online through IRIS InSight.
The /usr/etc/gsnarp command makes changes to the address resolution lookup table that is currently in memory for use by static HARP. This table maps 32–bit network–layer INET addresses (or network connection names) to 48-bit physical layer Universal LAN Addresses, or ULAs. HARP table entries made with the gsnarp -s command are lost if the system is restarted; to make changes that survive restarts, follow the instructions in “Adding Static HARP Table Entries”.
To add a static entry for a GSN host to the lookup table, use this command line:
# gsnarp -s name ULA_value
where name is the network connection name or address for a logical network interface as listed in the /etc/hosts file, and the ULA_value is a 6-byte (48–bit) value represented in hexadecimal characters separated by colons (for example, 7:8d:fe:8:13:5).
To delete one entry from the table, use this command line:
# gsnarp -d name
where name is the network connection name or INET address for a logical network interface as listed in the /etc/hosts file.
To purge only the dynamic entries and leave the static entries and HARP server entries in the table, use this command line:
# gsnarp -p
To remove all dynamic (i.e., non-static) entries and reload the harpd configuration file, you must terminate the currently running HARP daemon and restart it, as follows:
# gsnarp -k # harpd
To prevent any more IP-to-ULA mappings from occuring on the system -- and thereby prevent any GSN traffic -- you must stop the HARP daemon and remove all entries from the HARP mapping table, as follows:
# gsnarp -k # gsnarp -r
(The gsnarp -r command is allowed only when the HARP daemon is not running.) To allow GSN traffic again, you must restart the HARP daemon, as follows:
# harpd
Dynamic configuration of the IRIX GSN network interfaces that use INET addresses is done with the /usr/etc/ifconfig command, which is explained in detail in the ifconfig(1M) man page. The command lines listed below are appropriate with IRIX GSN:
# ifconfig [gsn#] INET_addr # ifconfig [gsn#] netmask 0x######## # ifconfig [gsn#] metric # |
where INET_address is the 32-bit INET (IP) address, ######## is the 32-bit netmask value, and # is the routing metric. See the ifconfig(1M) man page for details about acceptable formats.
| Note: Some of the standard ifconfig arguments are not supported for IRIX GSN (for example, broadcast and arp). |
Configuration changes made in this manner do not persist across restarts of the system. To make configuration changes that persist, edit the configuration file as explained in “Edit ifconfig-#.options File” and “Edit netif.options File”.
Each IRIX HARP client running on nonbroadcast media must know the ULAs for all of the HARP servers for each LIS with which it will be communicating.
Each IRIX HARP client running on broadcast media must know the IP-to-ULA mapping for all hosts that do not run the HARP protocol.
These server ULAs and static mappings should be listed in the harpd configuration file, which by default is /etc/config/harpd.options.
Open the /etc/config/harpd.options file for editing.
For each IRIX GSN network interface that requires HARP servers, add one line per HARP server. The lines have the following format:
server gsn# xx:xx:xx:xx:xx:xx
where gsn# is the network interface, and xx:xx:xx:xx:xx:xx is the HARP server's 6-byte ULA in colon-separated hexadecimal notation. For example:
server gsn1 08:00:71:C5:AD:74
Note: All hosts on the LIS (both HARP clients and HARP servers) must have the same list of HARP server ULAs in their harpd configuration files.) Static mapping entries can be added on separate lines, as follows:
static name xx:xx:xx:xx:xx:xx
where name is the IP name of the nonHARP enabled host, and xx:xx:xx:xx:xx:xx is the HARP server's 6-byte ULA in colon-separated hexadecimal notation. For example:
static groucho-gsn0 10:22:f3:03:77:01
Save the changes.
To activate the changes, stop the HARP daemon (if it is running), and restart the daemon with a completely purged HARP table, as follows:
% su Password: thepassword # gsnarp -k # harpd -p
Each LIS that is operating on a nonbroadcast medium must have at least one HARP server defined. These servers, just like the clients, must know the ULAs for all of the HARP servers for each LIS with which it will be communicating.
Each IRIX HARP server must also know the IP-to-ULA mapping for all hosts that do not run the HARP protocol. (This information is not necessary for HARP clients in nonbroadcast LISs, since the clients can request this information from the servers, just like any other IP-to-ULA mappings.)
For a description of how to edit the harpd configuration file and activate the changes, see the preceding section, “Configure IRIX HARP Client”.
If the system already has its GSN hardware installed, use the following command to discover the ULA that is assigned to this endpoint by its switch:
% gsncntl gsn# getmac
PROM ULA Address: 08:00:71:C5:AD:74
Device ULA Address: 00:01:3b:ff:00:0e
where gsn# identifies the GSN hardware that carries traffic for the server's LIS.
Use the Device ULA value; this is the address assigned by the switch. The PROM ULA is the MAC address retrieved from the SGI GSN board.
Otherwise, discover the ULA that the switch will assign to this system, as explained in the switch manufacturer's documentation.
If IRIX HARP is already functioning and you want to make changes to the HARP database, invoke the following command as superuser:
# gsnarp -s name ULA_value |
where name is the remote system's network connection name or INET address and ULA_value is the remote system's ULA address in colon-separated hexadecimal notation (for example, AA:12:CC:34:DD:56).
The /etc/config/harpd.options file is the configuration file read by the HARP daemon when it starts. (The file can have a different name or location. You can start the harpd daemon by using a -c config_file argument on the harpd command, specifying the name of the configuration file.)
The harpd.options file contains the list of HARP servers used by each GSN interface, and any static mappings that are needed.
Each GSN interface that is using nonbroadcast media must have HARP servers defined. The list of HARP servers must be configured identically on all GSN-connected hosts, whether they are HARP clients or HARP servers.
On nonbroadcast GSN media, the HARP servers must also have defined a static IP-to-ULA mapping for all GSN-connected hosts that do not run the HARP protocol. On broadcast GSN, each host must have these static mappings, since there are no HARP servers on broadcast GSN.
Follow these instructions to configure each HARP client:
Open the /etc/config/harpd.options file for editing.
For each IRIX GSN network interface that requires HARP servers, add one line per HARP server. A line has the following format:
server gsn# xx:xx:xx:xx:xx:xx
where gsn# is the network interface, and xx:xx:xx:xx:xx:xx is the HARP server's 6-byte ULA in colon-separated hexadecimal notation. For example:
server gsn0 08:00:de:00:ba:84 server gsn1 08:00:71:C5:AD:74
Save the changes.
The /etc/config/harpd.options file can also contain static HARP entries. Each entry maps a network connection name (or INET address) to a Universal LAN MAC address (ULA) for a host that does not support dynamic HARP.
Follow these instructions to configure static entries for the HARP table:
Open the /etc/config/harpd.options file for editing.
For each host that needs a static HARP entry, add a line of the following format:
static name xx:xx:xx:xx:xx:xx
where name is the IP name of the nonHARP enabled host, and xx:xx:xx:xx:xx:xx is the HARP server's 6-byte ULA in colon-separated hexadecimal notation. For example:
static groucho-gsn0 10:22:f3:03:77:01 static harpo-gsn0 10:22:f3:03:77:02 static gummo-gsn0 10:22:f3:03:77:05
The IRIX HARP 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 ULA value must be the exact ULA (IEEE address) for use as the Destination ULA in HIPPI-6400-PH headers and in the MAC Header of HARP packets.
Note: Do not create an entry in this format for any system for which a "server" entry is defined. Save the changes.
After all changes have been made to the configuration file, you can activate the changes by terminating the current HARP daemon and restarting the daemon with a completely purged HARP table, as follows:
# gsnarp -k # harpd -p If you are not using the standard configuration file name, use the following harpd command: # harpd -p -c config_file |
The /etc/hosts file maps network connection names[4] (commonly referred to as hosts) to INET addresses. Each time the IP–over–GSN and/or ST–over–GSN driver starts (for example, ifconfig gsn# up), it uses information from this file to configure the interfaces. There must be one entry in the hosts file for each local IRIX GSN connection; this statement is true even in environments that are using an NIS or DNS server on an attached LAN. The local hosts file must exist so that the network interface(s) can be configured during system startup, before the NIS service is accessible. Each address in this file must also exist in the /etc/config/netif.options file; the strings (names) in the two files must be identical.
The entries must be similar to the example below, which illustrates four IRIX GSN interfaces for a system whose hostname is amazon:
223.209.1.2 gsn0-amazon.brazil.com gsn1-amazon 223.209.2.4 gsn1-amazon.brazil.com gsn2-amazon 223.209.3.16 gsn2-amazon.brazil.com gsn3-amazon 223.209.4.32 gsn3-amazon.brazil.com gsn4-amazon |
| Note: For systems that have a primary interface served by an NIS or DNS server, this information must also be added to that server's database. |
Each /etc/config/ifconfig-#.options file configures one IP network interface. The # in the filename matches the numeral in the if#name entry in the netif.options file. Table 2-1 lists the operational parameters that can be controlled with this file. Each instance of this file is optional; when a file does not exist for a specific network interface, the default values are used (as listed in Table 2-1).
For IRIX GSN, the parameters that are most commonly configured are netmask and local buffer areas. For a complete description of the IP parameters that can be configured in this file, see the ifconfig(1M) man page.
If your site is using variable-length INET addressing or is dividing its INET network address space into subnets, place a line like this in the ifconfig-#.options file. The netmask entry determines the number of separate address spaces (LISs) possible within the INET address space and the number of hosts possible within each LIS.
netmask 0xyour_netmask |
where your_netmask is a 32-bit value in hexadecimal notation in which each local network bit is a 1 and each local host bit is a 0. For example, FFFFFFE0 subdivides a Class-C INET network address into 8 subnets (LISs) with up to 30 hosts each by dividing the final byte (the 8 bits of host portion) into 3 bits of additional network address and 5 bits of host address (E0=1110 0000 binary).
Hint: From the 32 values possible with a 5–bit local host portion, 00000 and 11111 are not usable, leaving 30 local host addresses available.
To obtain optimal TCP/IP performance on an IRIX GSN interface, the size of the local buffers for handling outstanding/in_transit TCP/IP data must match the sizes used on the other (remote) systems. If possible, the IRIX GSN default value (524288 bytes) should be configured on all the GSN interfaces within the GSN fabric. If this default cannot be used throughout the fabric, you must create an ifconfig-#.options file for each IRIX GSN interface and set the local buffering (sspace) value to the value selected for the other systems within the GSN fabric.
To configure the size of the TCP local buffer areas (in bytes), create an ifconfig-#.options file for the IRIX GSN interface and place these lines in the file:
sspace nnnn rspace nnnn |
where nnnn is any value, divisible by 1024, between 1024 and 524288.
Keep the following in mind:
If the memory used by TCP/IP applications is an issue, you can obtain nearly full performance by using 262144 (256*1024), instead of the default 524288 (512*1024).
If rspace is set to a value significantly smaller than the value used for sspace, TCP acknowledgments (ACKs) can be delayed. This can have a negative effect on performance.
For large TCP windows to work, the tcp_winscale and tcp_tsecho variables in the /var/sysgen/master.d/bsd file must be set to 1 (their defaults).
Table 2-1 lists the operational parameters that can be controlled with each /etc/config/ifconfig-#.options file and the default values that are used for each parameter when the file does not exist or when there is no entry in the file for that item.
Table 2-1. IP Network Interface Operational Parameters
Parameter | Default Setting for GSN Interfaces | Description |
|---|---|---|
The mask, appropriate for the INET address' Class, that does not extend the network portion or reduce the host portion of the address. | Value used by system to know which bits of the INET address are used locally to identify hosts and which bits identify local subnets (that is, LISs). | |
off | Value used by system for broadcasting. | |
ARP | off | Enables/disables address resolution (ARP). |
0 | Number of hops added to the hop count for this interface. The higher the number, the less likely the interface will be selected as a route by the routing module. | |
sspace | 524288 | Value used by the transmitting TCP/IP module for size of buffering for transmitted but outstanding (unacknowledged) data for a specific GSN connection. |
rspace | 524288 | Value used by the receiving TCP/IP module for size of buffering for incoming data that is not yet passed to the application for a specific GSN connection. |
Automatic startup | up | When the parameter is set, each system restart configures and starts this interface. |
The /var/sysgen/master.d/gsn file configures the IRIX GSN hardware device driver and the hardware. This configuration is optional because all parameters have default settings that are considered optimal for most sites. The settings in this file affect all SGI GSN boards installed in the system.
The specific items that are configurable vary from release to release, so they are explained fully within the file. Here are a few of the more important items:
Size of maximum transmission unit. if_gsn_mtu: valid values are 0-65,280 which is the GSN default, or 1 to (232 minus 1) inclusive.
Enable/disable onboard (hardware) IP checksumming for reception, for transmission, for both, or for neither. if_gsn_cksum: valid entries are 0=disabled, 1=receive_only, 2=transmit_only, and 3= both.
Operate GSN board in onboard loopback mode. gsn_use_loopback=1 enables internal loopback and gsn_use_loopback=0 is for normal operational.
Note: Setting gsn_use_loopback is not required when the hardware loopback connector is used. Number of small buffers (2 KB is default size for each buffer) passed by the driver to each IP reception entity on the GSN board. Note that one IP reception entity is associated with each activated interrupt queue (QID). if_gsn_small_mbuf_entries: valid values are 0 to 8,192 inclusive.
Number of large buffers (16 KB is default size for each buffer) passed by the driver to each IP reception entity on the GSN board. Note that one IP reception entity is associated with each activated interrupt queue (QID). if_gsn_large_mbuf_entries: valid values are 0 to 1024 inclusive.
Number of 5 microsecond increments (ticks) for loading the interrupt holdoff timer. While this timer is counting, the hardware does not generate interrupts to the driver. A value of 40 means that interrupts are not generated any faster than one every 200 microseconds. Adjusting this parameter affects latency and throughput. The optimal value depends on site-specific network traffic patterns and application performance requirements. gsn_intr_holdoff_ticks: valid values are 0 to (232 minus 1) inclusive.
Size of queue for Admin micropackets awaiting transmission. gsn_admin_desc_entries: valid values are 2, 4, 8, 16, and 32.
After editing this file, follow the instructions in “Building a New Driver Into the Operating System” to start using the new configuration.
The /etc/config/netif.options file maps local network connection names (or IP addresses) to IRIX GSN network interface names (for example, gsn0, gsn1, and so on), and sets the maximum number of network interfaces for the system. Each time the IP–over–GSN and/or ST–over–GSN driver starts (for example, ifconfig gsn# up), it uses information from this file to configure its interfaces. There must be a two-line entry for each IRIX GSN network interface. Each address (if#addr entry) in this file must also exist in the /etc/hosts file; the strings in the two files must be identical.
The first entry in the netif.options file (that is, the pair of lines: if1name and if1addr) defines the primary interface. In most situations, the primary interface should be Ethernet or FDDI; however, when the GSN fabric supports broadcasting and the LISs on the fabric are using dynamic client/server HARP, GSN can be configured as the primary interface. Any system that functions as a client or server for NFS, NIS, or other major client/server IP program should configure the network interface over which the client/server program functions occur as the primary network interface.
| Note: Systems that function as a client or server for bootp must configure Ethernet as their primary network interface. The IRIX GSN driver is not included in the miniroot. |
The example below illustrates a system with two IRIX GSN network interfaces (gsn#), an FDDI interface (xpi0), and a primary Ethernet interface (ef0). If this system's hostname is amazon, these IRIX GSN entries work with the examples of /etc/hosts file entries used in the section “Edit hosts File”. A line that starts with a colon (:) is a comment.
if1name=ef0 if1addr=$HOSTNAME if2name=xpi0 if2addr=fddi-$HOSTNAME : configuration associated with hardware device /hw/gsn/0 if3name=gsn0 if3addr=gsn0-$HOSTNAME : configuration associated with hardware device /hw/gsn/1 if4name=gsn1 if4addr=gsn1-$HOSTNAME |
The use of the $HOSTNAME variable assumes that the system's hostname has been defined in the /etc/sys_id file.IRIX, by default, allows up to eight logical network interfaces of any type to be configured. To increase this maximum, edit the if_num line in the netif.options file as illustrated below. Change the default entry:
: if_num=8 |
to a numeral equal to the number (decimal format) of logical IP network interfaces that will be configured on this system. For example:
if_num=12 |
To automatically enable the IP/ST network stacks 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 the command–line utility chkconfig network on.
| Note: Enabling networking does not result in IP–over–GSN functionality; it only enables the IP/ST software within the operating system to operate over whatever drivers are available to service it. See “Edit netif.options File” for instructions that associate a network device (that is, its network interface) with the IP/ST stacks. |
This section describes how to rebuild the operating system to include a totally new driver or to include configuration changes to a driver that is already present. In either case, complete all the configuration steps listed in the “Complete GSN Installation Process” before rebuilding the operating system.
For the IRIX GSN subsystem to be functional, the IRIX operating system (kernel) that is currently running the system must be rebuilt (after the configuration) to include the new or reconfigured IRIX GSN driver. When changes are made to any of the following files, or when new IRIX GSN software is installed, it is necessary to rebuild the operating system:
/var/sysgen/master.d/gsn
/var/sysgen/system/gsn.sm
/var/sysgen/master.d/harp
/var/sysgen/system/harp.sm
Note: After any configuration change, it is advisable to verify that the subsystem is functional. Follow the instructions in “Verifying the IRIX GSN Subsystem” in Chapter 3 to verify the functionality of the GSN subsystem.
Each set of instructions below builds a new operating system and starts it running. It is not important which set of instructions you use. Note that in the second set, you shut the system down twice.
% su Password: thepassword # /etc/init.d/autoconfig Automatically reconfigure the operating system (y or n)? y # /etc/reboot .....<various messages are displayed on console>... configuring gsn0 as hostname configuring gsn1 as hostname |
% su Password: thepassword # /etc/shutdown |
After the system shuts down, restart it by turning/pressing the reset/restart key or button. When the following question is displayed, answer with yes or y.
Automatically reconfigure the operating system (y or n)? y <log on> % su Password: thepassword # /etc/reboot |
After the system shuts down, again restart it by turning/pressing its reset/restart key or button. When the above question is displayed, answer no or n.
Table 2-2 lists all the parameters that can be configured for the IRIX GSN product.
Table 2-2. Summary of Configurable Items for IRIX GSN
Parameter | Required (R)/ Optional (O) | Default Setting | Location of Configuration Instructions | How to Start Using the New Configuration |
|---|---|---|---|---|
IP parameters: |
|
|
|
|
assign #s to GSN network interfaces | O | see “Assignment of Unit Numbers and Network Interfaces to GSN Hardware” in Chapter 1
| “Assignment of Network Interface to Hardware Device” in Chapter 1
| init 0 or shutdown or reboot |
assign netmask | O | 0 for each Class-defined host bit and 1 for each netid bit | “Edit ifconfig-#.options File”
| ifconfig gsn# down,
then |
map name (alias) to IP address | R | none |
| same as above |
assign IP/INET address | R | none | same as above | same as above |
map address/name to gsn# | R | none |
| same as above |
enable IP networking | R | disabled |
| same as above |
enable broadcast | O | automatic, if needed | none | same as above |
ARP (i.e., HARP) | O | see HARP entries in | “Individual Configuration Tasks”
|
|
maximum MTU size | O | 65,280 bytes |
| autoconfig, then reboot |
# of IP reception entities/queues | O | 4 | same as above | same as above |
# buffers for IP reception | O | 50 small and 50 large | same as above | same as above |
Hardware parameters: |
|
|
|
|
ULA address | NA with switch[a] | switch provides addr | instructions for switch | each time link is activated |
| NA for pt-to-pt | read from PROM | none | with each restart |
set hold-off timer for | O |
|
| autoconfig, then reboot |
# buffers for IP reception | O | 50 small and 50 large | same as above | autoconfig, then reboot |
assign unit #s to GSN boards | O | usually, hardware #s | “Assignment of Unit Numbers to Hardware” in Chapter 1
| init 0 or shutdown or reboot |
HARP parameters: |
|
|
|
|
HARP server | O for fabric with broadcasting | distributed dynamic HARP |
|
|
| R for non-broadcast fabric | No default ULA |
and “Configure IRIX HARP Server”
| gsnarp -k harpd -p |
| R if LIS contains any hosts that do not support dynamic HARP | dynamic HARP | “Adding Static HARP Table Entries”
|
|
| O for other server parameters | assumes defaults in /var/sysgen/mast er.d/gsn file are used |
| autoconfig, then reboot |
HARP client | O | FF:FF:FF:FF:FF:FF to locate HARP service on broadcasting fabric; 00:10:3b:ff:ff:e0 to locate HARP server on non-broadcasting fabric |
|
|
| R if defaults not used | see “HARP client” cell (above) | same as above | ifconfig gsn# down, |
HARP table | O | dynamic HARP |
|
|
| R only when LIS contains clients that do not support dynamic HARP | none | “Adding Static HARP Table Entries”
| gsnarp -k harpd -p |
[a] NA stands for not applicable. | ||||
[4] A network connection name is associated with an IP address (by an entry in the /etc/hosts file) and with an IP network interface (by an entry in the /etc/config/netif.options file). For example, for the entries “223.209.1.2 gsn1-amazon; if1name=gsn0 and if1addr=gsn-amazon,” 223.209.1.2 is the IP address, gsn1-amazon is the network connection name, and gsn0 is the IP network interface name. Due to UNIX convention, the hostname (in the /etc/sys_id file) for this machine is probably amazon.