This chapter describes how to configure the IRIS Token Ring product. For an initial IRIS Token Ring installation, the configuration must be done after installation of the software and before installation of the board.
 | Note: The IRIS Token Ring software must be already installed. Information on software installation is provided in the IRIS Token Ring Release Notes. |
The configuration tasks that you may want to perform are divided into these areas:
the physical (MAC) address for the IRIS Token Ring board
the data transmission speed for the IRIS Token Ring board
the IRIS Token Ring driver (including its transmission speed)
all network interfaces on this station
the protocol stack(s)
The procedures you use to accomplish these configuration tasks are dependent on the type of Token Ring board that you have. To summarize:
With the PCI Token Ring board, you use the mtrconfig utility (see mtrconfig (1M)) and its various options to modify the default configuration.
For all other types of Token Ring boards, you either use the trconfig utility (see trconfig(1M)) or manually edit the /etc/config/trconfig.options file to modify the default configuration.
This section describes how to assign a locally defined physical address (MAC address) to the IRIS Token Ring board. If your site uses universally assigned 48-bit MAC addresses, skip this section.
| Note: The IRIS Token Ring product requires the 6-byte (48-bit) MAC address format. The product does not support networks that use the 2-byte (16-bit) format. |
Each Token Ring board must have its own unique MAC address. MAC addresses are either locally assigned (LAA, assigned at the site and guaranteed to be unique only to that site) or universally assigned (UAA, assigned by a standards organization and guaranteed to be unique across the world). Silicon Graphics' Token Ring boards are shipped with IEEE universally assigned 48-bit MAC addresses that are permanently stored within a component on the board. Each board's address is read by the software during reset (startup).
If your Token Ring local area network uses locally assigned MAC addresses, you need to manually override the factory-assigned address for each board. Do this by updating the Token Ring configuration to specify the locally assigned addresses, as described in “Updating the MAC Address.”
| Note: A Silicon Graphics system running the IRIS SNA Server product or the IRIS 5080 Gateway product is a probable candidate for configuration of a locally assigned MAC address. |
The Token Ring board configuration file overrides the IRIS Token Ring board's universally assigned MAC address. The entry in the configuration file becomes the board's functional physical address.
To override the board's MAC address, do the following:
From the appropriate network administrator, obtain a site-assigned MAC address for each IRIS Token Ring board. The address must be a 48-bit address in hexadecimal format (for example, 40.00.70.0c.00.04, which can also be represented as 40.0.70.c.0.4).
Become the superuser with the following command.
% /sbin/su Password: thepassword
If you have a PCI Token Ring board, complete this step; otherwise, go to the next step. At the shell prompt, type the command:
mtrconfig interface -M LLA_address
where interface is the board you want to change (for example, mtr0 for the first board) and LLA_address is the site-assigned MAC address you obtained in step 1.
This update is now complete. Follow the instructions in “Displaying the Current MAC Address” to verify that the new address is being used.
If the board is not installed, continue installing and configuring the IRIS Token Ring product.
Use Table 2-1 to identify the interface name for each of your station's Token Ring boards. If your platform is not listed in the table, refer to the IRIS Token Ring Release Notes.
Table 2-1. Network Interface Names for IRIS Token Ring
Platform | Token Ring Interface Name |
|---|---|
VMEbus-based systems | fv0 for first board encountered |
IRIS Indigo™ systems | gtr0 |
Use any text editor to modify the trconfig.options file. The commands below open the file for editing with jot:
# /usr/sbin/jot /etc/config/trconfig.options
An unaltered trconfig.options file is illustrated in Figure 2-1 .
For each Token Ring board that needs a locally assigned MAC address, do the following:
Copy the appropriate line (for example, #fv0 -M 40.0.70.0.0.4 or #gtr0 -M 40.0.0.b.6c.5) to the last line of the file.
On the new line, remove the “ignore this line” (#) sign from the beginning of the line.
Replace the MAC address (for example, 40.0.70.0.0.4) with the valid MAC address you received from your system administrator. Do not remove the leading -M nor the space between the M and the address.
The altered file should look something like Figure 2-2, where a gtr Token Ring board has been assigned an address of c0.00.70.ff.f1.0b.
Save and close the file.
If the board is already installed, reboot the system to start using the new MAC address(es). Follow the instructions in the next section to verify that the new address is being used.
If the board is not installed, continue installing and configuring the IRIS Token Ring product.
To display an installed device's current MAC address, use one of these commands, depending on the type of board you have:
For the PCI board, use the mtrconfig command as shown below:
mtrconfig interface -v
where interface specifies the interface to report (for example, mtr0 is the first interface). The output should be similar to the following display:
TokenRing controller: mtr0 Burn-in MAC address 00:00:f6:54:02:25 Current MAC address 00:00:f6:54:10:55 ring speed 16Mbit Current broadcast address ff:ff:ff:ff:ff:ff Current max packet size 4472For all other boards, use the netstat command as shown below (see netstat (1)):
# /usr/etc/netstat -ia
The output for the Token Ring board (for example, fv0) should look similar to Figure 2-3. The MAC address displayed is the one currently being used by the system to identify that board.
Note: If you altered the /etc/config/trconfig.options but the display does not show that your locally assigned address is being used, reboot the system.
The IRIS Token Ring board's data transmission speed must be set to match the speed at which the ring is operating: either 4 or 16 megabits per second (Mbps). If the IRIS Token Ring board is configured to operate at one setting and the ring to which it is attached operates at a different speed, the IRIS Token Ring board's attempt to insert itself onto the ring fails and the driver disables itself.
| Note: IRIS Token Ring boards are shipped already configured for 16 Mbps. |
Some IRIS Token Ring boards have a transmission speed component with a jumper that can be moved to change the speed from one setting to another. This configuration method results in fast system reboots.
| Note: To set the jumper on an IRIS Indigo workstation, refer to the IRIS Token Ring for Indigo Installation Guide. To set the jumper on the IRIS Token Ring board for any other Silicon Graphics system, refer to the installation instructions. |
Some IRIS Token Ring boards (for example, for the IRIS Indigo platform) allow the board's transmission speed to be set from the console, using either the mtrconfig or the trconfig command. This method causes the new setting to be written into a memory chip on the board where the driver reads it each time the driver is enabled. The setting in the board's memory takes precedence over the board's jumper setting.
To change the IRIS Token Ring board's data transmission speed from the console, follow the steps below:
Become superuser (root):
% /sbin/su Password: thepassword
Disable the Token Ring network interface, if necessary.
# /usr/etc/ifconfig interfacename down
Change the transmission speed setting. Use the command appropriate for your board.
For PCI boards, use the following command:
mtrconfig interface -s newspeed
where interface is the board you want to change (for example, mtr0) and newspeed is either 4 or 16.
For all other boards, use the following command:
# /usr/etc/trconfig interfacename -s newspeed Warning: Writing interfacename EEPROM. Do not reset the system until finished. Finished.
where interface is the board you want to change andnewspeed is either 4 or 16.
Use the following command to verify that the network interface is enabled. In the display, an UP flag indicates that the interface is enabled.
% /usr/etc/ifconfig interfacename interfacename:flags=c63<UP,BROADCAST,RUNNING,MULTICAST> inet x.x.x.x netmask 0xffffff00 broadcast x.x.x.255
Note: If the interface is not UP, use the command below to enable it:
% /usr/etc/ifconfig interfacename upVerify that the new transmission speed is set with the command below:
% /sbin/hinv . . . IRIS Token Ring controller interfacename: speed Mbit
The configurable items for IRIS network interface drivers change from release to release and, therefore, are documented in each driver's configuration file, located in the /usr/var/sysgen/master.d directory. Some examples of IRIS Token Ring driver configuration files are /usr/var/sysgen/master.d/if_fv (for the fv drivers), /usr/var/sysgen/master.d/if_gtr (for the gtr drivers), and usr/var/sysgen/master.d/if_mtr (for the mtr drivers). Configuration for all of these parameters is optional.
To determine the name of your station's IRIS Token Ring driver, refer to the IRIS Token Ring Release Notes, or, if the Token Ring connection is already functional, use this command:
% /usr/etc/netstat -i |
Some common configurable driver parameters may include the following:
| Note: Promiscuous mode (also referred to as capture-all-frames or CAF) is supported, but is not a configurable item. For more information about promiscuous mode, see “Raw Protocol Stack and Capture All Frames” in Chapter 1. |
The IRIS Token Ring network interface (or interfaces) must be configured before the Token Ring connection will function. During configuration of the Token Ring interface, the configurations of other network interfaces may need to be changed.
| Note: If you do not perform any configuration tasks, the automatic network startup procedure fails during system startup and the Token Ring interface does not function. The failure occurs because the startup script (/etc/init.d/network) searches for, but fails to find, a default name and address entry of tr-hostname in the local /etc/hosts file. The Token Ring network interface cannot be started unless there is an entry in the /etc/hosts file. See Table 2-2 for a summary of the network script's assignments and the default names it expects. |
Easy step-by-step configuration instructions for a basic configuration are provided below in “Quick and Easy Configuration Instructions for Token Ring”.
If your site requires special operational parameters (for example, a network mask for subnetworking) or if your station has a combination of network connections not covered by the step-by-step instructions, follow the more complete instructions outlined in “Network Interface Configuration Outline”.
To configure a Token Ring station with a basic configuration, select one of the configurations listed below, then follow the step-by-step instructions in the corresponding subsection. If the configuration you want is not listed, see “Network Interface Configuration Outline”.
Token Ring as the second interface with Ethernet as primary
(This is the required configuration for a diskless station or any system that boots from the network.)Token Ring as the primary interface with Ethernet as second
Token Ring as the only network interface
The configuration described in this section contains no special configuration items, just the most basic functionality. These steps assume that the station is already connected to an Ethernet. If the station does not currently have a functional Ethernet connection, follow the instructions in the section in the Personal System Administration Guide or the IRIX Admin: Networking and Mail guide for setting up a networked station. Return to these instructions when the station's built-in (or primary) Ethernet connection is operational.
| Note: If your site uses an NIS service, the changes described in this section must also be made to the NIS server. |
Open a shell window.
Become superuser (root):
% /sbin/su Password: thepassword #
Determine your station's host name:
# /usr/bsd/hostname
Note: The host name should not be IRIS. (IRIS is the default name shipped on every system.) If the name is IRIS, follow the instructions in the Personal System Administration Guide for setting up a networked station, or follow the instructions in the IRIX Admin: Networking and Mail guide for assigning a host name to a system. Open the /etc/hosts file with your favorite editor. The command line below opens the file for editing with jot:
# /usr/sbin/jot /etc/hosts
Find the line containing your station's host name.
Note: If the file does not contain a line for your host name, follow the instructions in the Personal System Administration Guide for setting up a networked station or the instructions in the IRIX Admin: Networking and Mail guide for configuring a network's /etc/hosts file. Copy the line and place the copy immediately below the original.
On this new line, change the IP address (all the numbers on the left) to the IP address that has been assigned to the Token Ring connection on this station. This line configures the Token Ring network interface.
Note: The IP address must be in dotted decimal notation (for example, 191.51.69.237). Also on the new line, change each instance of the host name to tr-hostname.
For example, the lines for a station with a host name of mickey residing in a domain of disney.com, would look like this:
x.x.x.x mickey.disney.com mickey #Ether primary x.x.x.x tr-mickey.disney.com tr-mickey #TokenRing sec
where each x represents one to three decimal digits, and the text after the pound (#) sign is your comments.
Save and close the file.
You are now ready to install the Token Ring board. Follow the instructions in the board's installation guide or installation instructions.
If the board is already installed, use these commands to finish the configuration task:
# /etc/init.d/autoconfig
Automatically rebuild the operating system (y/n)? y
# /etc/reboot
The configuration described in this section contains no special configuration items, just the most basic functionality. These steps assume that the station is already connected to an Ethernet. If the station does not currently have a functional Ethernet connection, follow the instructions in the section in the Personal System Administration Guide or the IRIX Admin: Networking and Mail guide on setting up a networked station.
| Note: If your site uses an NIS service, some of the changes described in this section must also be made to the NIS server. |
Open a shell window.
Become superuser (root):
% /sbin/su Password: thepassword #
Determine your station's host name:
# /usr/bsd/hostname
Note: The host name should not be IRIS. (IRIS is the default name shipped on every system.) If the name is IRIS, follow the instructions in the Personal System Administration Guide for setting up a networked station or the instructions in the IRIX Admin: Networking and Mail guide for assigning a host name to a system. Open the /etc/hosts file with your favorite editor. The command line below opens the file for editing with jot:
# /usr/sbin/jot /etc/hosts
Find the line containing your station's host name.
Note: If the file does not contain a line for your host name, follow the instructions in the Personal System Administration Guide for setting up a networked station or the instructions in the IRIX Admin: Networking and Mail guide for configuring a network's /etc/hosts file. Copy the line and place the copy immediately below the original.
Return to the original line and change the address (numbers on the left) to the IP address that has been assigned to the Token Ring connection on this station. This line configures the Token Ring network interface.
Note: The IP address must be in dotted decimal notation (for example, 223.4.69.7). Go to the new line and change each instance of the host name to gate–hostname. This line now configures the Ethernet connection.
For example, the lines for a station with a host name of mickey residing in a domain of disney.com, would look like this:
x.x.x.x mickey.disney.com mickey #TokRng primary x.x.x.x gate-mickey.disney.com gate-mickey #Ether second
where each x represents one to three decimal digits, and the text after the pound (#) sign is your comments.
Save and close the file.
Determine the name of your Ethernet interface with the command shown below. Some common examples include ec0, et0, enp0, mtr0, and fxp0.
# /usr/etc/netstat -i
Determine the name of your IRIS Token Ring interface. This information is listed in the IRIS Token Ring Release Notes. Examples of this name include mtr0, gtr0, and fv0.
Open the /etc/config/netif.options file with your favorite editor. The command line below opens the file for editing with jot:
# /usr/sbin/jot /etc/config/netif.options
Find the line shown below:
: if1name=
Change the line as shown below. Be sure to remove the colon and the leading space.
if1name=TokenRinginterfacename
Find the line shown below:
: if2name=
Change the line as shown below. Be sure to remove the colon and the leading space.
if2name=Ethernetinterfacename
Find the line shown below:
: if2addr=gate-$HOSTNAME
Change the line as shown below. Be sure to remove the colon and the leading space.
if2addr=gate-$HOSTNAME
Save and close the file.
You are now ready to install the IRIS Token Ring board. Follow the instructions in the board's installation guide or installation instructions.
If the board is already installed, use these commands to finish the configuration task:
# /etc/init.d/autoconfig Automatically rebuild the operating system (y/n)? y # /etc/reboot
The configuration described in this section contains no special configuration items, just the most basic functionality for a station with one network connection.
| Note: If your site uses an NIS service, some of the changes described in this section must also be made to the NIS server. |
Open a shell window.
Log on as superuser:
% /sbin/su Password: thepassword #
Determine your station's host name:
# /usr/bsd/hostname
Note: The host name should not be IRIS. (IRIS is the default name shipped on every system.) If the name is IRIS, follow the instructions in the Personal System Administration Guide for setting up a networked station or the instructions in the IRIX Admin: Networking and Mail guide for assigning a host name to a system. Open the /etc/hosts file with your favorite editor. The command line below opens the file for editing with jot:
# /usr/sbin/jot /etc/hosts
Find the line containing your station's host name.
Note: If the file does not contain a line for your host name, follow the instructions in the Personal System Administration Guide for setting up a networked station or the instructions in the IRIX Admin: Networking and Mail guide for configuring a network's /etc/hosts file. Change the address (all the numbers on the left) to the IP address that has been assigned to the Token Ring connection on this station. This line configures the Token Ring network interface.
Note: The IP address must be in dotted decimal notation (for example, 223.4.69.7). The name used must be the station's host name. For example, the line for a station with a host name of mickey residing in a domain of disney.com, would look like this:
x.x.x.x mickey.disney.com mickey #TokRng primary
where each x represents one to three decimal digits, and the text after the # sign is your comments.
Save and close the file.
Determine the name of your IRIS Token Ring interface. This information is listed in the IRIS Token Ring Release Notes. Examples include mtr0, gtr0, and fv0.
Open the /etc/config/netif.options file with your favorite editor. The command line below opens the file for editing with jot:
# /usr/sbin/jot /etc/config/netif.options
Find the line shown below:
: if1name=
Change the line as shown below. Be sure to remove the colon and the leading space.
if1name=TokenRinginterfacename
For example:
if1name=gtr0
Save and close the file.
If the system has a built-in Ethernet interface, follow the instructions in “Network Interface Configuration Outline” to prevent the Ethernet from being automatically started with each reboot. Then continue to the next step below.
You are now ready to install the IRIS Token Ring board. Follow the instructions in the board's installation guide or installation instructions.
If the board is already installed, use these commands to finish the configuration task:
# /etc/init.d/autoconfig Automatically rebuild the operating system (y/n)? y # /etc/reboot
This section summarizes the tasks that must be performed to configure the IRIS Token Ring network interface(s). Details on how to perform each step are provided in the IRIX Admin: Networking and Mail guide.
The network startup script (/etc/init.d/network) runs each time the system is rebooted. It attempts to configure all drivers for which software is installed and a hardware device is found. If you add the names, indicated in the Names column of Table 2-2, to the station's /etc/hosts file, the script configures the network connections in the order shown in the table. The script does not handle other configurations unless the /etc/config/netif.options file is edited, as explained in the instructions that follow.
| Note: The network script handles only one Token Ring board. If your system has two or more Token Ring boards, you must edit the netif.options file as explained below. |
Table 2-2. Default Configurations Handled by network Startup Script
Station's Network Connections | Name searched for in /etc/hosts file |
|---|---|
Primary (only one is selected)[a] |
|
Second (only one is selected): |
|
Third (only one is selected): |
|
Fourth (only one is selected): |
|
[a] At startup, the network script locates all the network interfaces (driver software) that are installed. The script then looks for each interface listed in this table in the order shown. As soon as it locates and assigns a primary interface, it stops looking for the interfaces listed under primary and starts looking for those listed under second. This same procedure is followed for second, third, and fourth. | |
Add an entry (name and IP address) to the local /etc/hosts file for each network connection. (Existing network connections may already have entries. Verify that these are correct.)
Note: For each network interface, the startup script (/etc/init.d/network) searches for a name in the format shown in Table 2-2. If you do not want to use these default name formats, you must do step 3 to tell the script which names to use. If the site uses an NIS service, add to the NIS hosts database the same entries described in step 1.
If the station has any combination of network connections not listed in Table 2-2, or if you want the ordering or naming to differ from the configurations shown in Table 2-2, edit the /etc/config/netif.options file to specify the ordering and naming of the network interfaces.
Note: If the netif.options file is not edited, the startup script configures a single Token Ring interface as the second interface on the system, as summarized in Table 2-2. For any network connection that uses site-specific non-default operational parameters (including netmasks, broadcast addresses, route metrics, ARP usage, and unused built-in Ethernet connections), edit the /etc/config/ifconfig-#.options file (where the pound sign represents the network interface's order).
The default settings for operational parameters are listed in Table 2-3.
Table 2-3. Default Network Interface Configuration: Operational Parameters
Operational Parameter
Default Setting
none
interface's IP address with host portion set to binary 1s (255 decimal for each byte of the host portion)
ARP
(/etc/config/ifconfig-#.options file)on
0
Routing
(/etc/config/routed file)on
Routing behavior
(/etc/config/routed.options file)makes routing information public
(-s option)IP Forwarding (in the operating system, configured by /usr/var/sysgen/master.d/bsd file)
on
Built-in Ethernet is automatically started with each restart
(/etc/config/ifconfig-#.options file)
up (even when file does not exist)If non-default routing behavior is desired, edit the following files to configure the routing behavior between the networks: /etc/config/routed, /etc/config/routed.options, and/or /usr/var/sysgen/master.d/bsd. (The man pages for routed and chkconfig and the comments in the bsd file provide information on these settings.)
Install the IRIS Token Ring board. Follow the instructions in the board's installation guide.
If the board is already installed, use these commands to finish the configuration task.
# /etc/init.d/autoconfig Automatically rebuild the operating system (y/n)? y # /etc/reboot
The services of the IRIS Token Ring network connection are used by the higher layers of the protocol stack, as illustrated in Figure 1-6. Common communication protocols on Token Ring LANs include the Internet Protocol (IP or TCP/IP) suite and the Systems Network Architecture (SNA) protocol suite. This section discusses configuration issues for the IP and SNA protocol stacks.
| Note: For configuration information about NetBIOS, SPX/IPX™ (NetWare), or another protocol, refer to that product's documentation. |
The IP protocol stack (also referred to as TCP/IP) is the Silicon Graphics system's default and required communications protocol. Proper configuration of the IP protocol is required for the system to operate. (For example, the IRIS Token Ring driver does not start running if the IP configuration fails.) When a Silicon Graphics system has the SNA protocol stack configured, it must also have the IP stack configured.
To set up the station's IP over Token Ring protocol stack, follow the instructions in “Configuring the Network Interfaces”.
This section discusses how the Systems Network Architecture (SNA) protocol fits into the configuration of an IRIS Token Ring station.
| Note: You need to configure the SNA protocol stack only when an installed application requires the SNA protocol stack (for example, when the IRIS SNA Server product is installed). Most IBM emulation products developed for Silicon Graphics systems do not require an SNA protocol stack on the local system. |
SNA is IBM's preferred protocol and is used by many IBM products to communicate among each other. TCP/IP is Silicon Graphics' (and UNIX') preferred protocol. An IBM SNA product uses the SNA protocol to communicate with other products and systems, while a Silicon Graphics' IBM emulation product uses TCP/IP (not SNA). When an IBM emulation product running on a Silicon Graphics system needs to communicate with a system that speaks SNA (for example, an IBM host), the IRIS product uses TCP/IP to request the services of a translator (that is, an SNA server/gateway). The SNA gateway must speak both TCP/IP and SNA; therefore, configuration of the SNA protocol stack is required when the IRIS SNA Server product is installed, but is not required for most IBM emulation products.
IBM emulation products for Silicon Graphics systems (referred to as IRIS SNA applications) use the TCP/IP protocols to transfer their data and depend on a translator to handle the SNA protocol issues. IRIS SNA applications running on an IRIS Token Ring workstation use the BSD UNIX socket interface and TCP/IP protocol stack to access a translator (server), which then handles both the SNA protocol and the procedure for accessing the IBM mainframe. The translator can be the IRIS SNA Server product (running on the local system or on a remote system) or an IBM system, as illustrated in Figure 2-4.
To configure the SNA protocol stack, follow the instructions in the IRIS SNA Server Administrator's Guide. Any IRIS SNA applications that depend on this server will not operate properly until the server is operational.
This section describes methods for verifying that the station's applications can use the Token Ring connection(s).
To verify the Token Ring connection through the required IP protocol stack, you can use the standard IP-based software commands (for example, ifconfig and ping).
Use the steps in this section to verify that a Token Ring connection is functional. This example uses the ifconfig and ping commands (see ifconfig
(1M)).
Verify that the Token Ring board(s) is recognized by the operating system:
%/sbin/hinv
If the board is installed correctly and recognized by the operating system, the hinv screen display should be similar to the following:
1 36 MHZ IP12 Processor . . . IRIS Token Ring controller interfacename#: 16Mbit . . .
There should be one line for each IRIS Token Ring board installed. The display indicates the name of the IRIS Token Ring driver as well as the data transmission speed the board is currently using.
Note: If an expected board is not listed, follow the instructions in “When hinv Does Not List a Token Ring Board or Interface”. Verify that the network configuration information for each Token Ring connection is correct. Use the following command for each Token Ring connection listed by the hinv display. For interfacename#, use the network interface name from the hinv display (for example, gtr0, fv1).
# /usr/etc/ifconfig interfacename#
When the interface is configured correctly, you see output similar to the following:
fv0: flags=843<UP,BROADCAST,RUNNING> inet 223.48.50.4 netmask 0xffffff00 broadcast 223.48.50.255
Note: If the display does not list the Token Ring interface as UP, the interface is disabled. Follow the instructions in “When Token Ring Interface Is Disabled” in Chapter 3 to enable the interface before proceeding. For each Token Ring network connection, obtain the name of at least one other station.
One method for obtaining this name is to use one of the commands below. The variable netaddress is the network portion of the Token Ring interface's IP address, which can be discovered with the /usr/etc/netstat -ina command.
If your site uses an NIS server, use this command:
% /usr/bin/ypcat hosts | grep netaddress > stations.intrfacenam#
For sites without NIS, use this command:
% /sbin/grep netaddress /etc/hosts > stations.intrfacenam#
For example:
% /sbin/grep 223.48.50 /etc/hosts > stations.gtr0
From each stations.intrfacenam# file, select one station (host).
Use ping to test communication between the newly configured station and the other stations:
# /usr/etc/ping -r host
When communication between the two stations is working correctly, you see output similar to the following:
PING tr-mickey (223.48.50.4): 56 data bytes 64 bytes from 223.48.50.4: icmp_seq=0 ttl=255 time=10 ms 64 bytes from 223.48.50.4: icmp_seq=1 ttl=255 time=0 ms 64 bytes from 223.48.50.4: icmp_seq=2 ttl=255 time=2 ms
----tr-mickey PING Statistics---- 3 packets transmitted, 3 packets received, 0% packet loss
round-trip (ms) min/avg/max = 3/3/4
Note: If the other station cannot be reached, select a different station from the stations.interfacename# file. If the ping still fails, follow the troubleshooting instructions in Chapter 3, “Troubleshooting and Error Messages.” Use this command to display the activity on the Token Ring network connection. The number of input packets should increment steadily.
% /usr/etc/netstat -I interfacename# 2
When you successfully complete this procedure, the Token Ring connection is functioning and ready to provide network communication services. Successful completion of these steps also verifies the TCP/IP stack; the communication channel (protocol stack) is functional for IP-based applications (including IBM emulation products running on Silicon Graphics systems).
Following is a brief list and summary of some of the IP network management tools available. The on-line manual pages (also referred to as man pages) provide detailed descriptions and instructions on how and when to use these and other management tools. These tools reside in the /usr/etc directory.
| Note: The online manual pages that describe each of these commands can be viewed with the command: |
% /usr/bin/man commandname |