2    Basic Network Connections

This chapter describes the the basic Digital UNIX network environment, how to configure the Ethernet, Token Ring, and Fiber Distributed Data Interface (FDDI) network interfaces, and how to configure the the various network daemons in order to operate in a TCP/IP network environment. In addition, this chapter describes some of the commands to monitor the network environment.

For point-to-point connections, see Chapter 4.

2.1    The Network Environment

Figure 2-1 shows a sample corporate network in which there is an Ethernet backbone and FDDI network or Token Ring network connected to it through a gateway.

Figure 2-1: Network Configuration

2.2    Preparing for the Configuration

You configure the network components by using the Network Configuration application. Appendix A contains a worksheet that you can use to record the information that you need to configure the network components. If you are viewing this manual online, you can use the print feature to print a copy of this part of the worksheet.

2.2.1    Information for Interfaces and Daemons

Figure 2-2 shows Part 1A of the Configuration Worksheet. The following sections explain the information you need to record in Part 1A of the worksheet.

If you are viewing this manual online, you can use the print feature to print a copy of this part of the worksheet.

Figure 2-2: Configuration Worksheet, Part 1A

2.2.1.1    Network Interfaces

Adapter name
The device names of the network interfaces. The following network interfaces are supported on Digital UNIX:
Interface Device Name
Ethernet le
ln
tu
xna
Fiber Distributed Data Interface (FDDI) faa
fta
fza
Token Ring tra

Host name
The fully qualified host name assigned to your system. A fully qualified host name contains the host name and the domain name, with host name and each level of the domain name are separated by a period (.). Ask the network administrator for a unique host name.

Internet address source
The source of your system's network address. If your network is using a Distributed Host Configuration Protocol (DHCP) server to assign IP address to systems at boot time, check DHCP server. If you are going to assign an IP address and network mask as part of system configuration, check User supplied. This is for Ethernet and FDDI interfaces only.

Internet address
Your system's Internet Protocol (IP) address. You should have obtained an IP address for your network from InterNIC Registration Services. After you receive your network's address, you must assign a unique IP address and host name to each system on your network.

To obtain an Internet address for your network, contact:

Network Solutions Inc.
InterNIC Registration Service
505 Huntmar Park Drive
Herndon, VA 22070

Telephone numbers: (703) 742-4777

FAX: (703) 742-4811

E-mail: hostmaster@internic.net (for IP and domain registrations)
WWW: http://rs.internic.net/rs-internic.html

In Europe, you can contact:

RIPE Network Coordination Center
Kruislaan 409
NL-1098 SJ Amsterdam
The Netherlands

Telephone number: +31 20 592 5065

FAX: +31 20 592 5090

E-mail: ncc@ripe.net (for general information)
Hostmaster@ripe.net (for IP and domain registrations)
WWW: http://ripe.net

In Asia and the Pacific region, you can contact:

AP-NIC
c/o United Nations University
3-70 Jingumae 5-chome
Shibuya-ku
Shibuya-ku, Tokyo, 150, Japan

Telephone number: +81 3 5276 3973

FAX: +81 3 5276 6239

E-mail: hostmaster@apnic.net
WWW: http://www.apnic.net

Note

Digital recommends that you register your network with the NIC even if you do not intend to connect to the Internet network. Then, if you decide to connect to the Internet network later, you will not have to change all the host addresses on your network.

Network mask
Your network's subnet mask. Subnetworks allow the systems on a local area network (LAN) to be known by one address to the Internet network, while being known locally by a set of addresses. Subnetworks can represent logical groupings of hosts, or different physical networks. If your network uses subnetwork routing, each system on the network must have the same subnet mask defined.

Use the following table to help identify your subnet mask. If you are not using subnetworks, the n is zero (0); otherwise, the n is greater than zero and less than or equal to 255.
Class IP Address Range Subnet Mask
A 0.0.0.0 to 127.0.0.0 255. n.n.n
B 128.0.0.0 to 191.0.0.0 255.255. n.n
C 192.0.0.0 to 223.0.0.0 255.255.255. n

If you are connecting your system to an existing network that is using subnetwork routing, ask the network administrator for the correct subnet mask.

2.2.1.2    Token Ring Interface

Adapter speed
If your system supports token ring, the speed of your system's token ring adapter. Two speeds are supported: 4Mb/s and 16Mb/s. The default speed is 16Mb/s.

2.2.1.3    rwhod daemon

rwhod
If you want to run the rwhod daemon, check YES; otherwise, check NO.

Running the rwhod daemon allows you to use the rwho and ruptime commands.

Flags
If the rwhod daemon is to send rwho packets and ignore incoming packets, check BROADCAST ONLY. If the daemon is to collect incoming packets, but not broadcast rwho packets, check LISTEN ONLY. If the daemon is to do both, check BOTH.

2.2.1.4    Routed

Running the routed daemon allows your system's internal routing tables for the Routing Information Protocol (RIP) to be updated automatically.

routed
If you want to run the routed daemon, check YES; otherwise, check NO.

Note

You can choose the routed daemon or gated daemon, but not both.

flags
Specifies how you want routed to run. You can run routed on a gateway host, write all packets to standard output, or log debugging information. Check the options you want. See routed(8) for more information.

RIP data
If routed is supply RIP information, check SUPPLY; otherwise, check RUN QUIETLY.

2.2.1.5    Gateways File

Dest type
If the route is to a network, check NET. If the route is to a specific host, check HOST.

Destination
The destination name or IP address (in dotted-decimal format).

Gateway
The name or address of the gateway host to which messages should be forwarded.

Hop count
The hop count, or number of gateways, from the local network to the destination network.

Route type
If the gateway is expected to exchange RIP routing information, check ACTIVE. If the gateway is not expected to exchange routing information, check PASSIVE. If the gateway is to notify routed that another routing process will install the route (it is not advertised through RIP), check EXTERNAL.

2.2.1.6    Gated

Running the gated daemon allows your system's internal routing tables for different routing protocols to be updated automatically.

gated
If you want to run the gated daemon, check YES; otherwise, check NO.

Note

You can choose the routed daemon or gated daemon, but not both.

Configuration file
The name of an alternate configuration file. By default, gated uses the /etc/gated.conf file.

2.2.1.7    IP Router

You can configure your system as an IP router if you have more than one network interface installed and configured. In addition, you must have configured either routed or gated.

IP router
If you want the system to run as an IP router, check YES; otherwise, check NO.

2.2.2    Information for Network Files

Figure 2-3 shows Part 1B of the Configuration Worksheet. The following sections explain the information you need to record in Part 1B of the worksheet. If you are viewing this manual online, you can use the print feature to print a copy of this part of the worksheet.

Figure 2-3: Configuration Worksheet, Part 1B

2.2.2.1    Static Routes file (/etc/routes)

Route via
If you are routing through a gateway, check GATEWAY. If you are routing through an interface, check INTERFACE.

Gateway
The name or IP address of the gateway or interface.

Destination type
The specific path from your system to another host or network that is stored in the /etc/routes file. A static route is not updated by network software. If you want to a default gateway, check DEFAULT GATEWAY; to a host, check HOST; or to a network, check NETWORK.

Destination
The name or IP address of the destination to which you route. For default gateway, the default destination is default.

2.2.2.2    Host file (/etc/hosts)

Host name
The names of other hosts on the network to be added to the /etc/hosts file.

If your network is running a distributed database lookup service (BIND or NIS), you do not need to list each host on your network in your /etc/hosts file. However, it is a good idea to list four or five systems on the network designated as BIND or NIS servers in your /etc/hosts file.

Internet address
The IP addresses of other hosts on the network to be added to the /etc/hosts file.

Host alias
The aliases, if any, of other hosts on the network to be added to the /etc/hosts file.

2.2.2.3    hosts.equiv file

Host name
The name of the trusted hosts to be put in the /etc/hosts.equiv file. Systems listed in the /etc/hosts.equiv file are logically equivalent to, and therefore treated exactly the same as, the local system.

Setting up an /etc/hosts.equiv file is optional, but, if you choose to have one on your system, you need to create it and add the names of any trusted hosts.

User name
The name of a user on a trusted host.

2.2.2.4    Networks file (/etc/networks)

Network name
The official Internet name of the network.

Network address
The IP address of the network.

Alias
The unofficial names used for the network to be added to the /etc/networks file.

2.3    Configuring the Network Components

Digital recommends that you use the Network Configuration application of the Common Desktop Environment (CDE) Application Manager for configuring network components on systems with graphics capabilities. You can configure the following components:

  • Network interfaces (Ethernet, FDDI, and Token Ring)

  • Static routes file (/etc/routes)

  • gated daemon

  • routed daemon

  • rwhod daemon

  • IP router

  • Hosts file (hosts)

  • Host equivalent file (hosts.equiv)

  • Networks file (/etc/networks)

See netconfig(8X) for more information on the Network Configuration application.

To invoke the Network Configuration application, log in as root, do the following:

  1. Click on the Application Manager icon on the CDE front panel.

  2. Double-click on the System_Admin application group icon.

  3. Double-click on the Digital System_Management_Utilities application group icon.

  4. Double-click on the Configuration application group icon.

  5. Double-click on the Network Configuration application icon. The Network Configuration main window appears, showing available network components and configured network components.

To exit the Network Configuration application, choose File then Exit.

Note

For systems without graphics capabilities, you can use the netsetup utility. See netsetup(8) for more information.

The Network Configuration application also has an extensive online help system. You can use it instead of the instructions in this section to configure network components on your system.

2.3.1    Configuring Network Interfaces

To configure the Ethernet, FDDI, or Token Ring network interface, do the following:

  1. In the Network Configuration Main Window, select an interface from the Available Network Components list box. All network adapters that are installed on the system are listed.

  2. Click on Configure. The Configuring Interface Dialog Box for the selected interface appears.

  3. Set the Interface Configuration Enable check button to the ON position to enable the interface on the next reboot.

  4. Enter the name for the interface in the Host Name input text field. If this is the first or only network interface you are configuring and there is a default host name, the utility displays the default.

  5. For the Ethernet interface, do the following:

    1. If you are to obtain the IP address data from the DHCP server, set the Use DHCP Server radio button to the ON position. Otherwise, set the User Supplied Value radio button to the ON position and enter the IP address and network mask data in the appropriate input text fields.

    2. Click on the down arrow button. This expands the window to display the advanced configuration parameters for the selected interface.

    3. Click on the check button for Multicast to enable the reception of multicast packets. See map-mbone(7) for more information on multicast routing.

    4. Click on the check boxes for the appropriate interface options.

    5. Go to step 8.

  6. For the FDDI interface, do the following:

    1. If you are to obtain the IP address data from the DHCP server, set the Use DHCP Server radio button to the ON position. Otherwise, set the User Supplied Value radio button to the ON position and enter the IP address and network mask data in the appropriate input text fields.

    2. Click on the down arrow button. This expands the window to display the advanced configuration parameters for the selected interface.

    3. Click on the check boxes for the appropriate interface options.

    4. Enter the broadcast address for the interface in the Broadcast Address input text field.

    5. Go to step 8.

  7. For the Token Ring interface, do the following:

    1. Enter the IP address for the host device in the IP Address input text field.

    2. Enter the mask variable for the interface in the Network Mask input text field.

    3. Click on the button in option box to display a menu of token ring adapter speeds. Select the appropriate adapter speed: 4 or 16.

    4. Click on the down arrow button. This expands the window to display the advanced configuration parameters for the selected interface.

    5. Enter the broadcast address for the interface in the Broadcast Address input text field.

    6. Go to step 8.

  8. Click on Commit.

  9. Click on OK to save the changes and start the interface.

  10. Click on Close to close the Configuring Interface Dialog Box.

The Network Configuration application also enables you to modify and delete network interface. See the application online Help for additional information.

2.3.2    Configuring the Rwho Daemon

To configure the rwhod daemon, do the following:

  1. In the Network Configuration Main Window, select Rwho Daemon from Available Network Components list box.

  2. Click on Configure. The Configuring rwho Daemon dialog box appears.

  3. Set the rwhod Daemon Enable check box to the ON position to start the rwhod daemon the next time the system is rebooted.

  4. Click on the appropriate rwhod flag.

  5. Click on Commit.

  6. Click on OK to save the changes and start the daemon.

  7. Click on Close to close the Configuring rwho Daemon dialog box.

The Network Configuration application also enables you to modify and delete the rwhod daemon. See the application online Help for additional information.

2.3.3    Configuring the Route Daemon

To configure the routed daemon, do the following:

  1. In the Network Configuration Main Window, select Route Daemon from Available Network Components list box.

  2. Click on Configure. The Configuring Route Daemon dialog box appears.

  3. Set the routed Daemon Enable check box to the ON position to start the routed daemon the next time the system is rebooted.

  4. Set the routed flags to the ON position as needed.

  5. Set the Supply RIP Data radio button to the ON position if routed is to run on a gateway host and supply Routing Information Protocol (RIP) data. Set the Run Quietly radio button to the ON position if routed is not to supply RIP information.

  6. Click on Gateways File. The Gateways dialog box appears. Do the following:

    1. In the Dest Type field, set the net check box to the ON position if if the destination is a network. Set the host check box to the ON position if the destination is a host.

    2. Enter the destination name, IP address, or "default" in the Destination input text box.

    3. Enter the name or IP address of the gateway host in the Gateway input text box.

    4. Enter the hop count in the Hop Count input text box.

    5. Set one of the Route Type check boxes to the ON position.

    6. Click on Add. Repeat steps 1 through this step in this sublist for additional gateways.

    7. Click on Commit and Close to save the changes and close the Gateways dialog box.

  7. Click on Commit.

  8. Click on OK to save the changes and start the daemon.

  9. Click on Close to close the Configuring routed dialog box.

The Network Configuration application also enables you to modify and delete the routed daemon and entries in the gateways file. See the application online Help for additional information.

See routed(8) and gateways(4) for more information.

2.3.4    Configuring the gated Daemon

To configure the gated daemon, do the following:

  1. In the Network Configuration Main Window, select gated from Available Network Components list box.

  2. Click on Configure. The Configuring gated dialog box appears.

  3. Set the gated Daemons Enable check box to the ON position to start the gated daemon the next time the system is rebooted.

  4. Enter the file name of the gated configuration file in the Config File input text field.

    Note

    To configure the gated daemon, you must set up the /etc/gated.conf file in the format specified in gated.conf(4). A default /etc/gated.conf file is provided when you install the software.

  5. Click on Commit.

  6. Click on OK to save the changes and start the daemon.

  7. Click on Close to close the Configuring gated dialog box.

The Network Configuration application also enables you to modify and delete the gated daemon. See the application online Help for additional information.

See gated(8) and gated.conf(4) for more information.

2.3.5    Configuring the System as an IP Router

In order to function as an IP router, your system must have two network interfaces installed and configured and must have routed or gated configured. To configure the system as an IP router, do the following:

  1. In the Network Configuration Main Window, select IP Router from Available Network Components list box.

  2. Click on Configure. The Configuring IP Router dialog box displays.

  3. Set the IP Router Enable check box to the ON position to run the system as an IP router the next time the system is rebooted.

  4. Click on Commit and click on Close. This saves current changes and closes the dialog box.

The Network Configuration application also enables you to deconfigure the system as an IP router. See the application online Help for additional information.

2.3.6    Configuring the Static Routes File

To configure the routes file, you add entries (static routes), to the routes file. Do the following:

  1. In the Network Configuration Main Window, select Static Routes File from Available Network Components list box.

  2. Click on Configure. The Static Routes dialog box appears.

  3. Set one of the Destination Type check boxes to the ON position.

  4. For host and net, enter the full name or IP address of the destination network or host in the Destination input text field.

  5. Set one of the Route Via check boxes to the ON position. Click on the Gateway check box if the route is through a gateway; click on the Interface check box if the route is through an interface.

  6. For a gateway, enter the full name or IP address of the gateway host to which messages will be forwarded in the Gateway input text field.

  7. Click on Add. This accepts the entry. Repeat steps 3 through 7 for additional static routes.

  8. Click on Commit and click on Close. This saves current changes and closes the dialog box.

The Network Configuration application also enables you to modify and delete entries in the routes file. See the application online Help for additional information.

See routes(4) for more information.

2.3.7    Configuring the hosts File

To configure the hosts file, do the following:

  1. From the Network Configuration Main Window, select Host File from Available Network Components list box.

  2. Click on Configure. The Hosts dialog box appears.

  3. Enter the official host name in the Host Name input text field.

  4. Enter the IP address of the new host in the Host Address input text field.

  5. If an unofficial name or names (alias) are assigned to the new host, enter the names in the Aliases input text field.

  6. Click on Add. This accepts the entry. Repeat steps 3 through 5 for additional hosts.

  7. Click on Commit and Close to update the hosts file and close the Hosts dialog box.

The Network Configuration application also enables you to modify and delete entries in the hosts file. See the application online Help for additional information.

See hosts(4) for more information.

2.3.8    Configuring the hosts.equiv File

To configure the hosts.equiv file, do the following:

  1. In the Network Configuration Main Window, select Host.equiv File from the Available Network Components list box.

  2. Click on Configure. The Hosts.equiv dialog box appears.

  3. Enter the host name in the Host name text field.

    Note

    If the host is not on the network, you cannot add the host.

  4. Enter the name of a user on the remote host.

  5. Click on Add. This accepts the entry. Repeat steps 3 and 4 for additional hosts.

  6. Click on Commit and Close to update the /etc/hosts.equiv file and close the Hosts.equiv dialog box.

The Network Configuration application also enables you to modify and delete entries in the hosts.equiv file. See the application online Help for additional information.

See hosts.equiv(4) for more information.

2.3.9    Configuring the networks File

To configure the networks file, do the following:

  1. In the Network Configuration Main Window, select Network File from the Available Network Components or Configured Network Components list box.

  2. Click on Configure. The Networks dialog box appears.

  3. Enter the official network name in the Net Name input text field.

  4. Enter the IP address of the network in the Net Address input text field.

  5. If an unofficial name (alias) is assigned to the new network, enter the aliases in the Aliases input text field.

  6. Click on Add to accept the entry. Repeat steps 3 through 5 for additional networks.

  7. Click on Commit and Close to update the /etc/networks file and close the Networks dialog box.

The Network Configuration application also enables you to modify and delete entries in the networks file. See the application online Help for additional information.

See networks(4) for more information.

2.4    Enabling Access Filtering on an Interface

Interface access filtering provides a mechanism for detecting and preventing IP spoofing attacks. To enable interface access filtering on an interface, do the following:

  1. Create an /etc/ifaccess.conf file and add entries against which the source address of input packets are checked.

  2. Use the ifconfig command with the +filter parameter to enable access filtering on the network interface.

See ifaccess.conf(4) and ifconfig(8) for more information.

2.5    Monitoring the Local Host's Status

You use the netstat command to monitor the status of the local host by viewing the contents of network-related data structures. You can select several forms of display; each allows you to specify the type of information you want to emphasize.

To monitor the local host's network status, use the netstat command with the following syntax:

netstat [ options... ]

Table 2-1 shows the netstat command options.

Table 2-1: Options to the netstat Command

Option Function
-A Displays the address of any associated protocol control blocks.
-a Includes information for all sockets.
-f address_family Includes statistics or address control block reports for the specified address family.
-I interface Displays information about the specified interface only.
-i Provides status information for autoconfigured interfaces.
-m Displays information about memory management usage.
-n Lists network addresses in number form rather than symbolic form.
-r Lists routing tables.
-s Provides statistics per protocol.
-t Displays the time until the interface watchdog routine starts (for use with the -i option).

The -I option provides statistics for a specific interface. See Appendix B for an example of using the -I option to monitor Ethernet, Fiber Distributed Data Interface (FDDI), and token ring interfaces, and a description of the counters, status, and characteristics. The -i option gives statistics on each configured network interface. Outgoing packet errors (Oerrs) indicate a potential problem with the local host. Incoming errors (Ierrs) indicate a potential problem with the network connected to the interface.

See netstat(1) for more information on this command.

The following example shows normal output (no Ierrs or Oerrs) from the netstat command with the -i option:

%  netstat -i 

Name  Mtu   Network   Address       Ipkts Ierrs    Opkts Oerrs  Coll
ln0   1500  <Link>                8324125     0  8347463     0 237706
ln0   1500  16.31.16  host1       8324125     0  8347463     0 237706
fza0* 4352  <Link>                      0     0        0     0    0
sl0*  296   <Link>                      0     0        0     0    0
sl1*  296   <Link>                      0     0        0     0    0
tra0  4092  <Link>                     34     0       20     0    0
tra0  4092  16.40.15  host21           34     0       20     0    0
lo0   1536  <Link>                 909234     0   909234     0    0
lo0   1536  loop      localhost    909234     0   909234     0    0

2.6    Displaying and Modifying the FDDI Parameters

You use the fddi_config command to display and modify the FDDI adapter parameters.

To display the FDDI adapter parameters, use the fddi_config command with the following syntax:

fddi_config -i interface_name -d

To modify the FDDI adapter parameters, do the following:

  1. Log in as root.

  2. Use the fddi_config command and options as follows:

    fddi_config [ options... ]

Table 2-2 shows the fddi_config command options.

Table 2-2: Options to the fddi_config Command

Option Function
-i interface_name Changes or displays the FDDI characteristics for interface_name. You must provide the interface name.
-c counter_update_interval Determines how often the driver counters are updated by the DEFTA adapter. The default is 1 second. Setting the interval time to zero (0) disables counter updates. (For the DEFTA (fta) FDDI interface only.))
-d Displays the FDDI interface parameters you can set.
-l lem_threshold Sets the error rate threshold of Link Error Monitor (LEM). The LEM error rate threshold is 1×10^-n, where n ranges from 5 to 8, inclusively. The default LEM threshold is 1×10^-8.
-p [1|0] Sets the ring purger state for the specified FDDI interface. A value of 1 enables the ring purger ability; a value of 0 disables it.
-r restricted_token_timeout Sets the Restricted Token Timeout parameter, defining how long a single restricted mode dialog can last before being terminated. The range for this parameter is from 0 to 10000 milliseconds. The default value is 1000 milliseconds.
-t token_request_time Sets the Request Token Rotation Time (T_req) for interface_name. T_req is used during the ring initialization process to negotiate a Target Token Rotation Time (TTRT) for the ring. The range for this parameter is from 4.0 milliseconds to 167.77208 milliseconds. The default value is 8.0 milliseconds.
-v valid_transmit_time Sets the Valid Transmission Time (TVX) timer for a specific FDDI interface. The range for the TVX timer is from 2.35 milliseconds to 5.2224 milliseconds. The default is 2.6214 milliseconds.
-x [1|0] Enables (1) or disables (0) full-duplex operation for the interface. If the full-duplex operation is enabled, the interface can be in one of the following states: Idle, Request, Confirm, or Operational. (For the DEFTA (fta) FDDI interface only.)

See fddi_config(1) for more information on this command.

The following example shows how to display the FDDI interface parameters you can set:

%  /usr/sbin/fddi_config -i fza0 -d 

fza0 ANSI FDDI settable parameters
Token Request Time:                0.0000 ms
Valid Transmission Time:           0.0000 ms
LEM Threshold:                     0
Restricted Token Timeout:          15.8314 ms
Ring Purger State:                 (null)
fza0 Full Duplex Mode: Disabled
fza0 Counter Update Interval: 10 sec

The following example shows how to change the Token Request Time (TRT) value for the fza0 interface to 10.2:

#  fddi_config -t10.2 -i fza0

The following example shows how to turn the ring purger off:

#  fddi_config -p 0 -i mfa0

2.7    Managing Token Ring Source Routing

Source routing is a bridging mechanism that systems on a token ring LAN use to send messages to a system on another interconnected token ring LAN. Under this mechanism, the system that is the source of a message uses a route discovery process to determine the optimum route over token ring LANs and bridges to a destination system. The source system stores the optimum routes in its source routing table.

When the system is booted with the DETRA adapter installed and configured, token ring source routing is initialized by default. To manage token ring source routing, use the srconfig command and options as follows:

srconfig options...

Table 2-3 shows the srconfig command options. All srconfig command options are case insensitive; type them in uppercase, lowercase, or mixed case. The short form for each flag is indicated by uppercase letters.

Table 2-3: Options to the srconfig Command

Option Function
-DElentry mac_address[Table Note 1] Deletes a source routing table entry.
-DISEntry mac_address[Table Note 1] Disables a source routing table entry. This marks the entry as Stale.
-RAttr Displays the source routing attributes.
-RCounter Displays the source routing counters.
-REntry mac_address Displays a specific source routing table entry.
-RTable Displays the source routing table.
-SETAgetimer timer[Table Note 1] Sets the value of the Source Routing Aging Timer, specifying the length of time a source routing table entry remains valid until being marked as invalid or Stale. If not set, the system default is 120 seconds.
-SETDsctimer timer[Table Note 1] Sets the Source Routing Discovery Timer, specifying the amount of time a route discovery process can take before it terminates. If not set, the system default is 5 seconds.
-SETMaxentry value[Table Note 1] Sets the maximum number of entries allowed in the source routing table. The range for this entry is a multiple of 256 from 1024 to 2048. This parameter can be increased, but not decreased. If not set, the system default is 1024.
-u Specifies that the MAC addresses are in uncanonical form. This option can be used with the -DElEntry mac_address, -DISEntry mac_address, and -RTable options only.
-Zcounter Sets the source routing counters to zero.

Table notes:

  1. Requires superuser privileges.

See srconfig(8) for more information on this command.

The following example increases the number of routing table entries from 1024 to 1280 by using the shortened form of the -SetMaxEntry option:

#  srconfig -setm 1280 

Current SR Table size is : 1024
New SR Table size is : 1280

The following example displays the source routing attributes by using the shortened form the the -RAttr option:

#  srconfig -ra 

Source Routing is enabled
Current SR Aging Timer     : 120
Current SR Discovery Timer : 10
Current SR Table size is   : 1024

The following example displays the source routing counters by using the shortened form of the -RCounter option:

#  srconfig -rc 

ARE Frames Sent          : 00000001
ARE Frames received      : 00000000
Route Discovery Failures : 00000001

The following example displays all entries, with MAC addresses in canonical form, in the source routing table, by using the shortened form of the -RTable option. The backslash (\) character is included for formatting purposes and does not appear in the actual output.

#  srconfig -rt 

Target Node MAC Address 00-00-0C-01-08-E9 (ip = 130.180.4.3) \
Have Route  [1]
Routing Information: SRF, length 8, direction 0,largest frame \
4472 octets  [2]
Route Descriptors: 021C 7FFC 0220 0000 0000 0000 0000 0000    [3]

 

Target Node MAC Address 00-00-C9-10-1B-F5 On Ring    [4]

 

Target Node MAC Address 08-00-2B-2C-F1-F9 (ip = 130.180.4.2)  \ 
Stale (Have Route)   [5]
Routing Information: SRF, length 8, direction 0,largest frame 4472 octets
Route Descriptors: 021C 7FFC 0220 0000 0000 0000 0000 0000

 

Target Node MAC Address 00-00-C9-0B-33-80 Stale (On Ring)

  1. HaveRoute indicates the source system has a valid path to the destination system. [Return to example]

  2. Information returned by the destination system in response to the route discovery process. [Return to example]

  3. The LAN segments and bridges that constitute the path to the destination system. [Return to example]

  4. OnRing indicates the destination system is on the same ring as the source system and does not need source routing. [Return to example]

  5. Stale indicates the entry is invalid and needs to be updated by the route discovery process. [Return to example]

The following example displays all entries, with MAC addresses in noncanonical form, in the source routing table by using the shortened form of the -RTable option. The backslash (\) character is included for formatting purposes and does not appear in the actual output.

#  srconfig -rt -u 

Target Node MAC Address 00:00:30:80:10:97 (ip = 130.180.4.3) Have Route
Routing Information: SRF, length 8, direction 0,largest frame 4472 octets
Route Descriptors: 021C 7FFC 0220 0000 0000 0000 0000 0000

 

Target Node MAC Address 00:00:93:08:D8:AF On Ring

 

Target Node MAC Address 10:00:D4:34:8F:9F (ip = 130.180.4.2) Stale \
 (Have Route)
Routing Information: SRF, length 8, direction 0,largest frame 4472 octets
Route Descriptors: 021C 7FFC 0220 0000 0000 0000 0000 0000

 

Target Node MAC Address 00:00:93:D0:CC:01 Stale (On Ring)

2.8    Displaying and Modifying the Token Ring IP MTU Size

By default, the DETRA adapter uses an IP maximum transfer unit (MTU) size of 4092 bytes. In a multivendor environment with different adapters using different IP MTU sizes, the bridges connecting different networks can be set up to forward smaller packet sizes. As a result, bridges might drop packets or remote hosts might reject packets. If either occurs on your network, reduce the IP MTU size for all hosts on the network and ensure that all hosts use the same size.

The following command displays the DETRA interface IP MTU size as 4092 bytes:

%  ifconfig tra0 

tra0: flags=9863<UP,BROADCAST,NOTRAILERS,RUNNING>
     inet 16.141.208.3 netmask ffffff00 broadcast 16.141.208.255 ipmtu 4092

The following command changes the IP MTU size of DETRA interface to 2044 bytes:

%  ifconfig tra0 ipmtu 2044