2 Basic Network Connections

This chapter describes the basic Tru64 UNIX network environment, including how to configure:

Ethernet

Token Ring

Fiber Distributed Data Interfaces (FDDI)

Automatic network adapter failover (NetRAIN)

Various network daemons in order to operate in a TCP/IP network environment

In addition, this chapter describes some of the commands you use to monitor the network environment.

For information about ATM and point-to-point connections, see Chapter 3 and Chapter 5, respectively.

For troubleshooting information, see Section 14.3.

2.1 Network Environment

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

Figure 2-1: Sample Network Configuration

2.2 Preparing for the Configuration

You configure the network components by using the Network Configuration application. The following sections contain worksheets that you can use to record the information required to configure the network components.

2.2.1 Information for Interfaces and Daemons

Figure 2-2 shows the Interface and Daemon Worksheet. The following sections explain the information you need to record on this worksheet. If you are viewing this manual online, you can use the print feature to print a copy of the worksheet.

Figure 2-2: Interface and Daemon Worksheet

2.2.1.1 All Network Interfaces

Adapter name

The device names of the network interfaces. The following table contains a list of selected network interfaces that the operating system supports:

Interface	Device Name
Ethernet	`le` `ln` `tu` `xna`
Fiber Distributed Data Interface (FDDI)	`faa` `fta` `fza`
Gigabit Ethernet	`alt`
Token Ring	`tra`

Note that if you configuring a NetRAIN interface, as documented in Section 2.4, the adapter name is the virtual device name of your NetRAIN set (nr).

Host name

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

Internet address source

The source of your system's network address for Ethernet, FDDI, and NetRAIN interfaces only. If your network uses a Dynamic Host Configuration Protocol (DHCP) server to assign IP addresses to systems at boot time, check the DHCP server box. If you plan to assign an IP address and network mask as part of system configuration, check the User supplied box.

Internet address

The Internet Protocol (IP) address of your system or NetRAIN interface. If you are going to supply your own IP address, write it in this space. If you will be using DHCP to assign IP addresses on a temporary basis, leave this space blank.

If you do not have a designated IP address for your network, you need to obtain one from one of the following services. Then, after you receive your network's address, assign a unique IP address and host name to each system on your network.

To obtain an Internet address for your network, contact:

American Registry for Internet Numbers
4506 Daly Drive, Suite 200
Chantilly, VA 20151

Voice: (703) 227-0660
FAX: (703) 227-0676
Email: reg-services@arin.net (for general information)
hostmaster@arin.net (for IP address registrations)
WWW: http://www.arin.net

In Europe, you can contact:

RIPE Network Coordination Center
Singel 258
1016 AB Amsterdam
The Netherlands

Voice: +31 20 535 4444
FAX: +31 20 535 4445

E-mail: ncc@ripe.net (for general information)
hostmaster@ripe.net (for IP address registrations)
WWW: http://www.ripe.net

In Asia and the Pacific region, you can contact:

Asia Pacific Network Information Center
Level 1, 33 Park Road
P.O. Box 2131
Milton, QLD 4064
Australia

Voice: +61 7 3367 0490
FAX: +61 7 3367 0482

E-mail: hostmaster@apnic.net (for general information and IP address registrations)
WWW: http://www.apnic.net

Note

You should register your network 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 NetRAIN Interface

Set members: The device names of the network interfaces that are part of the NetRAIN set, as discussed in Section 2.4. When one interface ceases to function, NetRAIN will fail over to another interface on this list.

2.2.1.4 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.5 routed Daemon

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 the routed daemon to run. You can run the routed daemon 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 the routed daemon is to supply RIP information, check Supply; otherwise, check Run Quietly.

2.2.1.6 Gateways File

Destination 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.7 gated Daemon

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, the gated daemon uses the /etc/gated.conf file.

2.2.1.8 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 the routed or the gated daemon.

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 the Network Files Worksheet. The following sections explain the information you need to record on this worksheet. If you are viewing this manual online, you can use the print feature to print a copy of the worksheet.

Figure 2-3: Network Files Worksheet

2.2.2.1 Static Routes File (/etc/routes)

Destination type: The specific path, as stored in the /etc/routes file, from your system to another host or network. A static route is not updated by network software. If you want to route 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 route destination. For default gateway, the default destination is default.
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.

2.2.2.2 Hosts 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 (DNS/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 DNS/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.

Alias

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

2.2.2.3 Hosts Equivalencies File (/etc/hosts.equiv)

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

Use the SysMan Menu application of the Common Desktop Environment (CDE) Application Manager to configure the following network components on your system:

Network interfaces (Ethernet, FDDI, and Token Ring)

Remote who service (rwhod daemon)

Routing services (routed daemon, gated daemon, IP router)

Static routes file (/etc/routes)

Hosts file (/etc/hosts)

Host equivalent file (/etc/hosts.equiv)

Networks file (/etc/networks)

To invoke the SysMan Menu application, follow the instructions in Section 1.1.1.

In the following sections, each configuration utility is invoked independently through the SysMan Menu. Alternatively, you can use the Network Setup Wizard, which leads you step-by-step through the setup process for all of the basic network services. Invoke the Network Setup Wizard by selecting Networking-->Network Setup Wizard from the SysMan Menu.

Note that if you use the Network Setup Wizard, you can cancel the configuration process at any time. No information is saved or applied until you select Finish at the end of the process.

2.3.1 Configuring Network Interfaces

Use the following procedure to configure the Ethernet, FDDI, or Token Ring network interface. For information about how to configure NetRAIN, see Section 2.4.

Note

If you are configuring a system that is new to this environment, verify that the network adapter mode is set correctly at the console level before continuing. For example, if you have a 10base2 Ethernet network and your system is configured to use 10baseT Ethernet, your system fails to see the network until you set the appropriate console variable. See the prerequisite tasks for a full installation in the Installation Guide for more information.

From the SysMan Menu, select Networking-->Basic Network Services-->Set up Network Interface Card(s) to display the Network Interface Card dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman interface
```
All network adapters that are installed on the system are listed in the dialog box.

Select the network adapter that you would like to configure. The dialog box for the selected interface is displayed.

Enter the name for the interface in the Host Name 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.

For the Ethernet interface, do the following:
1. To obtain the IP address data from the DHCP server, select the Use DHCP radio button. Otherwise, select the User Supplied Value radio button and enter the IP address and network mask data in the appropriate fields.
2. Select the Additional Flags button to display the Additional Flags dialog box, which shows advanced configuration parameters for the selected interface.
3. Select the check boxes and radio buttons for the other interface options that you want to enable and enter values where necessary for optional ifconfig arguments.
4. Go to step 7.

For the FDDI interface, do the following:
1. If you are to obtain the IP address data from the DHCP server, select the Use DHCP radio button. Otherwise, select the User Supplied Value radio button and enter the IP address and network mask data in the appropriate fields.
2. Select the Additional Flags button to display the Additional Flags dialog box, which shows advanced configuration parameters for the selected interface.
3. Select the check boxes and radio buttons for the interface options that you want to enable and enter values where necessary for optional ifconfig arguments.
4. Enter the broadcast address for the interface in the Broadcast Address field.
5. Go to step 7.

For the Token Ring interface, do the following:
1. Enter the IP address for the host device in the IP Address field.
2. Enter the mask variable for the interface in the Network Mask field.
3. Select the Additional Flags button to display the Additional Flags dialog box, which shows advanced configuration parameters for the selected interface.
4. Select the check boxes and radio buttons for the interface options that you want to enable and enter values where necessary for optional ifconfig arguments. Select the appropriate adapter speed: 4 or 16.
5. Enter the broadcast address for the interface in the Broadcast Address field.
6. Go to step 7.

Select OK to validate the parameters you entered and to close the Additional Flags dialog box. The dialog box for the adapter you are configuring is displayed.

Select OK to save the changes. You are asked if you want to start the network services.

Select Yes to start network services and apply your changes now, or select No to close the Interfaces dialog box and apply the changes the next time you reboot your system.
If you choose Yes, you are informed that network services are running. Select OK to close the Interfaces dialog box.

You can also use the Network Interface Card dialog box to modify and deconfigure network interfaces. See the online help for more information.

When you deconfigure an interface, all services running over the interface stop and all of the configuration information for the interface is deleted from the system. To restore a network interface after it is deconfigured, you must configure it again using the Network Interface Card dialog box.

Note

Use the deconfigure feature to remove network interfaces only on systems with more than one interface. If you deconfigure the network interface on a system with a single interface, your system is left in a unpredictable state. Once a system is configured to use the network for the first time, the Common Desktop Environment is network-dependent and might function inconsistently if network services become unavailable.

2.3.2 Configuring the rwhod Daemon

To configure the rwhod daemon, do the following:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up remote who services (rwhod) to display the Remote Who dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman rwhod
```
The utility asks if you want to run the remote who service on your system.

Select the Yes radio button to enable the remote who service.

Select the appropriate rwhod flag radio button.

Select OK to save the changes. The utility notifies you that the changes are saved and asks if you want to apply the changes now.

Select Yes to apply your changes now, or select No to close the Routing Services dialog box and apply the changes the next time you reboot your system.

Select OK to dismiss the informational message and to close the Remote Who dialog box.

You can also use the Remote Who dialog box to disable the rwhod daemon. See the online help for more information.

2.3.3 Configuring the routed Daemon

To configure the routed daemon, do the following:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up routing services (gated, routed, IP Router) to display the Routing Services dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman routing
```
The utility displays a list of options you can use to configure the gated and routed daemons and to set up your system as an IP router.

Select Yes (use routed) radio button to enable the routed daemon.

Select the Yes radio button if you would like to run your system as an IP router.

Select the Run routed on a Gateway check box if you want to run the routed daemon on a gateway.

Select the Supply RIP Data radio button if you want the routed daemon to run on a gateway host and supply Routing Information Protocol (RIP) data. Select the Run Quietly radio button if you do not want the routed daemon to supply RIP information.

Select the Configure Gateways button to display the Gateways dialog box. Do the following:
1. Select Add to add a new gateway. The Add/Modify dialog box is displayed.
2. In the Destination Type field, select the Network radio button if the destination is a network. Select the Specific Host radio button if the destination is a host.
3. Enter the destination name, IP address, or "default" in the Destination field.
4. Enter the name or IP address of the gateway host in the Gateways field.
5. Enter the hop count in the Hop Count field.
6. Select one of the Gateway Type radio buttons.
7. Select OK to validate the information you entered and close the Add/Modify dialog box. Repeat steps a through g for additional gateways.
8. Select OK to save the changes and close the Gateways dialog box.

Select OK in the Routing Services dialog box to save the changes. The utility displays a dialog box to confirm the changes and to ask if the daemon should be started.

Select Yes to start the daemon and apply your changes now, or select No to close the Routing Services dialog box and apply the changes the next time you reboot your system.
If you choose Yes, you are informed that the daemon is running. Select OK to dismiss the message and to close the Routing Services dialog box.

You can also use the Routing Services dialog box to disable the routed daemon. See the online help for more information.

See the routed(8) and gateways(4) reference pages for more information about the routed daemon and the gateways file.

2.3.4 Configuring the gated Daemon

To configure the gated daemon, do the following:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up routing services (gated, routed, IP Router) to display the Routing Services dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman routing
```
The utility displays a list of options you can use to configure the gated and routed daemons and to set up your system as an IP router.

Select the Yes (use gated) radio button to enable the gated daemon.

Select the appropriate radio button if you want to run your system as an IP router.

Enter the file name of the gated configuration file in the Configuration File 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.

Select OK in the Routing Services dialog box to save the changes. A dialog box is displayed to confirm the changes and to ask if the daemon should be started.

Select Yes to start the daemon and apply your changes now, or select No to close the Routing Services dialog box and apply the changes the next time you reboot your system.
If you choose Yes, you are informed that the daemon is running. Select OK to dismiss the message and to close the Routing Services dialog box.

You can also use the Routing Services dialog box to disable the gated daemon. See the online help for more information.

See the gated(8) and gated.conf(4) reference pages for more information about the gated daemon and the gated.conf file.

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 the routed or gated daemon configured. To configure the system as an IP router, do the following:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up routing services (gated, routed, IP Router) to display the Routing Services dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman routing
```
The utility displays a list of options you can use to configure the gated and routed daemons and to set up your system as an IP router.

Select the appropriate radio button to run your system as an IP router.

Select OK to save the changes. A dialog box is displayed to confirm the changes and to ask if the routed or gated daemon should be started or restarted.

Select Yes to start the daemon and apply your changes now, or select No to close the Routing Services dialog box and apply the changes the next time you reboot your system.
If you choose Yes, you are informed that the daemon is running. Select OK to dismiss the message and to close the Routing Services dialog box.

You can also use the Routing Services dialog box to deconfigure the system as an IP router. See the online help for more 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:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up static routes (/etc/routes) to display the Static Routes dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman route
```

Select Add to add a static route. The Add/Modify dialog box is displayed.

Select one of the Destination Type radio buttons.

For host and net destinations:
1. Enter the full name or IP address of the destination network or host in the Destination field.
2. Select one of the Route Via radio buttons. Select the Gateway button if the route is through a gateway. Select the Interface button and skip to step 6 if the route is through an interface.

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

Select OK to validate the entry and add it to the list. Repeat steps 2 through 6 for additional static routes.

Select OK to save the current changes. A dialog box is displayed to confirm the changes and to ask if the static routes service should be started.

Select Yes to start the service and apply your changes now. Or, select No to close the Static Routes dialog box and apply the changes the next time you reboot your system.
If you choose Yes, select OK to close the Static Routes dialog box.

You can also use the Static Routes dialog box to modify and delete entries in the routes file. See the online help for more information.

See the routes(4) reference page for more information about the routes file.

2.3.7 Configuring the hosts File

To configure the hosts file, do the following:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up hosts file (/etc/hosts) to display the Hosts dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman host
```

Select Add to add a host. The Add/Modify dialog box is displayed.

Enter an official host name in the Host Name field.

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

Optionally, enter any unofficial name or names for this host in the Aliases field. Also, provide pertinent information, for example, the location of the host, in the Comment field.

Select OK to validate the entry and add it to the list. Repeat steps 2 through 6 for additional hosts.

Select OK to update the hosts file and to close the Hosts dialog box.

You can also use the Hosts dialog box to modify and delete entries in the hosts file. See the online help for more information.

See the hosts(4) reference page for more information about the hosts file.

2.3.8 Configuring the hosts.equiv File

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

From the SysMan Menu, select Networking-->Basic Network Services-->Set up host equivalency file (/etc/hosts.equiv) to display the Hosts Equivalency dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman hosteq
```

Select Add to add a host. The Add/Modify dialog box is displayed.

Enter the remote host name in the Host field.

Note

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

Enter the name of a user on the remote host in the User field.

Select OK to validate the entry and add it to the list. Repeat steps 2 through 5 for additional remote hosts.

Select OK to update the /etc/hosts.equiv file and to close the Hosts Equivalency dialog box.

The Hosts Equivalency dialog box also enables you to modify and delete entries in the hosts.equiv file. See the online help for additional information.

See the hosts.equiv(4) reference page for more information about the hosts.equiv file.

2.3.9 Configuring the networks File

To configure the networks file, do the following:

From the SysMan Menu, select Networking-->Basic Network Services-->Set up the networks file (/etc/networks) to display the Networks dialog box.
Alternatively, enter the following command on a command line:
```
# /usr/bin/sysman networks
```

Select Add to add a network. The Add/Modify dialog box appears.

Enter the official network name in the Network Name field.

Enter the IP address of the network in the Network Address field.

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

Select OK to validate the entry and add it to the list. Repeat steps 2 through 6 for additional networks.

Select OK to update the /etc/networks file and to close the Networks dialog box.

You can also use the Networks dialog box to modify and delete entries in the networks file. See the online help for more information.

See the networks(4) reference page for more information about the networks file.

2.3.10 Configuring IP Aliases

An IP alias is an additional network address for an interface. The alias is usually an address in the same subnet as the primary IP address on the interface.

To configure an IP alias, you need the following information:

IP alias address

Netmask value associated with the IP alias address

Host name associated with the IP alias address

To configure an IP alias, do the following:

Add the IP address and host name to the /etc/hosts file (see Section 2.3.7).

Edit the /etc/inet.local file and add the command to configure the alias. If the IP alias address is in the same subnetwork as the primary IP address of the interface, use the following syntax:
```
ifconfig interface alias IP_alias_address netmask IP_alias_netmask
```
For example:
```
ifconfig tu0 alias 18.54.76.129 netmask 255.255.255.0
```
If the IP alias address is not in the same subnetwork as the primary IP address of the interface, append the string multinet to the entry to inform the kernel that two subnets are configured for this interface:
```
ifconfig tu0 alias 18.54.76.129 netmask 255.255.255.0 multinet
 
```
See the ifconfig(8) reference page for more information on ifconfig parameters.

Restart network services by entering the following command:
```
# rcinet restart
```

2.4 NetRAIN Interfaces

The Redundant Array of Network Adaptors (NetRAIN) interface provides a mechanism to protect against certain kinds of network connectivity failures.

NetRAIN integrates multiple network interfaces on the same LAN segment into a single virtual interface called a NetRAIN set. One network interface in the set is always active while the others remain idle. If the active interface fails, one of the idle set members comes online with the same IP address within an adjustable failover time period.

NetRAIN monitors the status of its network interfaces with the Network Interface Failure Finder (NIFF), a tool used to detect and report possible network failures. These tools can be used independently of NetRAIN. For more information about NIFF, see the niff(7) reference page.

2.4.1 Configuring NetRAIN

The following sections describe how to configure the hardware and the network interfaces for a NetRAIN set.

2.4.1.1 Hardware Restrictions and Configuration

Before you set up the NetRAIN virtual interface, note the following hardware restrictions and configuration tips:

You must construct a NetRAIN set out of interfaces that are currently idle. This means the interfaces cannot be marked as "up" in the Set up Network Interface Card(s) dialog box of the SysMan Menu and they cannot have IP addresses assigned to them.

You must use two or more of the same type of network interface (FDDI, ATM LAN Emulation, or Ethernet) dedicated to a single LAN segment. If you use Ethernet adaptors, they must all be of the same speed.

You cannot run LAT over a NetRAIN virtual interface (nr) or any of the interfaces that compose a NetRAIN set.

You should run separate cables from each network adapter to the appropriate hub or concentrator to provide physically redundant paths back to the network. This reduces the chance of network failure due to cables being accidentally unplugged.

You might need to adjust the timeout values to ensure that NetRAIN will successfully detect and respond to network failure. You can tune these parameters with the sysconfig command, ifconfig command, and the ioctl system call. See the nr(7), ifconfig(8), sysconfig(8), dxkerneltuner(8), and sys_attrs_netrain(5) reference pages for details.
By default, these parameters are tuned for operation over Ethernet, but it is possible that the default values and other suggested timeout values will not work in your environment. For example, if you are connected to a switch, failover time will depend on the switch and its configuration.

You must use UNI Version 3.1 when running NetRAIN over LANE to obtain acceptable failover times with some ATM switches, including the Gigaswitch. If you use UNI Version 3.0, the failover time might be long because the T309 timer is set to 90 seconds by default on some switches. If the T309 timer is adjustable on your switch, you can set the T309 timer to 10 seconds as in UNI Version 3.1 to try to achieve acceptable failover times.

2.4.1.1.1 NetRAIN and MAC Address Licensing Schemes

Licensing schemes that use a network adapter's Media Access Control (MAC) address to uniquely identify a machine can be affected by how NetRAIN changes the MAC address.

All network drivers support the SIOCRPHYSADDR ioctl that fetches MAC addresses from the interface. This ioctl returns two addresses in an array:

Default hardware address
The permanent address that is taken from the small PROM that each LAN adapter contains.

Current physical address
The address that the network responds to on the wire.

Licensing schemes based on MAC addresses should use the default hardware address returned by the SIOCRPHYSADDR ioctl; do not use the current physical address because NetRAIN modifies this address for its own use. See the reference page for your network adapter (for example ln(7) and tu(7)) for a sample program that uses the SIOCRPHYSADDR ioctl.

2.4.1.1.2 NetRAIN and Microsoft Windows NT Clients

When communicating with a Tru64 UNIX server running NetRAIN with the default settings, Microsoft Windows NT clients reset their TCP/IP connections before the server can complete the failover to another interface. There are two possible solutions to this problem.

For environments with only a few Windows NT clients, you can modify the following two TCP parameters on the clients as follows:

Parameter	Value	Purpose
TcpMaxDataRetransmissions	20	Maximum number of retransmissions
TcpTimedWaitDelay	30	Maximum retransmission timer

For environments with many NT clients, you can modify two NetRAIN kernel attributes on the server instead of modifying the TCP parameters on each client system. On the Tru64 UNIX server system, modify the nr_max_retries and netrain_timeout kernel attributes by using the sysconfig -r command or the dxkerneltuner utility. For example, you can set the attributes as follows:

Attribute	Value	Purpose
nr_max_retries	1	Maximum number of retransmissions (default is 4)
netrain_timeout	100	Maximum retransmission timer (default is 1000)

Alternatively, you can set values for the nrmaxretry and nrtmoisr parameters when you issue the ifconfig command to create the NetRAIN set. See sys_attrs_netrain(5) and ifconfig(8) for information on these NetRAIN parameters.

Regardless of the solution you choose, if the network interface cards on the host are connected to a layer 2 switch or bridge that is running a Spanning Tree algorithm, the Spanning Tree configuration parameters on the switch or bridge might dictate the failover time. In this case, the behavior of the TCP retry depends on the switch implementation and configuration. See the documentation accompanying the switch or bridge for information.

2.4.1.2 Configuring the NetRAIN Interface

NetRAIN configuration parameters are stored in the /etc/rc.config file along with the parameters for other network interfaces. Use the rcmgr utility to change the values of the variables. For more information about the rcmgr utility, see the rcmgr(8) reference page.

To configure NetRAIN, do the following:

Log in as root.

Construct the NetRAIN set or sets, as follows:
1. Set the NetRAIN interface name or names:
```
# rcmgr set NRDEV_n netrain-interface-id
```
  For example, to create two NetRAIN sets, you might enter the following commands:
```
# rcmgr set NRDEV_0 nr0
# rcmgr set NRDEV_1 nr1
```
2. Indicate which network interfaces will be part of the NetRAIN set or sets and, if necessary, provide failover timeout values:
```
# rcmgr set NRCONFIG_n interface-id,interface-id [nrtimers integer,integer]
```
  For example, to create two NetRAIN sets, one with two FDDI interfaces called fta0 and fta1 and the other with two ATM LANE interfaces called elan0 and elan1, you would enter the following parameters:
```
# rcmgr set NRCONFIG_0 fta0,fta1
# rcmgr set NRCONFIG_1 elan0,elan1 nrtimers 4,16
```
  The nrtimers values in this example are suggested starting values for ATM LANE. They might not work for your configuration, as described in Section 2.4.1.1. For more information about nrtimers values, see the ifconfig(8) reference page.
3. Indicate to the system that you have configured an additional NetRAIN interface:
```
# rcmgr set NR_DEVICES integer
```
  To create two NetRAIN sets, as in step 2a, you increment integer by 2.

Configure the network parameters for the NetRAIN set or sets that you created, as follows:
1. Set the interface name:
```
# rcmgr set NETDEV_n netrain-interface-id
```
  To create two NetRAIN sets, you might enter the following commands:
```
# rcmgr set NETDEV_0 nr0
# rcmgr set NETDEV_1 nr1
```
  If you configured other network interfaces in the rc.config file, you will need to find and use the next available NETDEV_n variable. For example, if you used NETDEV_0 to configure an Ethernet card that is not part of the NetRAIN set, the next available variable is NETDEV_1.
2. Set the ifconfig parameters that will be used to initialize the NetRAIN interface:
```
# rcmgr set IFCONFIG_n IP-address netmask network-mask
```
  For example, to create two NetRAIN sets, one with an IP address of 18.240.32.40 and a netmask of 255.255.255.0 and the other with an IP address of 18.240.31.42 and the same netmask, you would enter the following parameters:
```
# rcmgr set IFCONFIG_0 18.240.32.40 netmask 255.255.255.0
# rcmgr set IFCONFIG_1 18.240.31.42 netmask 255.255.255.0
```
  If you configured other network interfaces in the rc.config file, you will need to use the next available IFCONFIG_n variable.
3. Indicate to the system that you have configured an additional network interface:
```
# rcmgr set NUM_NETCONFIG integer
```
  To create two NetRAIN interfaces, increment integer by 2.

Restart network services to effect the changes.

After you configure the NetRAIN set, the NetRAIN interface are available each time you restart your system.

Optionally, you can configure NetRAIN interfaces from the command line by using the ifconfig command, but the changes are not preserved when you reboot. For more information, see the ifconfig(8) reference page.

2.4.2 Monitoring NetRAIN Activity

To check which member of a NetRAIN set is the active interface, use the ifconfig command. For example:

#ifconfig nr0
nr0: flags=8c63     NetRAIN Attached Interfaces: ( fta0 fta1 ) Active Interface:
 ( fta0 )inet 18.240.32.40 netmask ffffff00 broadcast 18.240.32.255 ipmtu 4352

This example shows that:

The virtual interface nr0 is running; its IP address is 18.240.32.40.

The NetRAIN set consists of two physical interfaces, fta0 and fta1.

NetRAIN is using fta0 for communication. If NetRAIN determines that fta0 is not active, it switches to the next interface in the set, fta1.

To see the status of all set members while the NetRAIN interface is running, use the niffconfig command. For example:

#niffconfig -u
Interface:   tu1, state: DEAD, t1: 4, dt: 2, t2: 10, time to dead: 0,
current_interval: 2, next time: 2
Interface:   nr0, state: GREEN, t1: 4, dt: 2, t2: 10, time to dead: 0,
current_interval: 4, next time: 4
Interface:   tu0, state: GREEN, t1: 4, dt: 2, t2: 10, time to dead: 0,
current_interval: 4, next time: 4

In this example, you can see that the virtual interface nr0 is running and NetRAIN is using tu0 for communication. This example also shows the nrtimers values for each member of the set. See the ifconfig(8) reference page for more information on these values.

2.5 Configuring Multiple Network Interfaces in the Same Subnet

You can configure multiple active network adapters in one computer, even if they operate on the same subnetwork. For example, you can configure a tu0 interface at 192.24.156.20 and a tu1 interface at 192.24.156.21, both with the same netmask.

When you establish a connection, the kernel routes the connection through the interface that has the fewest number of connections. This connection-balancing effect can lead to greater throughput than on a system with just one network adapter per subnetwork.

This feature differs from NetRAIN because it does not give you increased reliability or failover, it simply gives a system multiple paths to access the network.

Network administrators might choose to configure a system with multiple interfaces in the same subnetwork for various reasons. For example:

The current environment has only a single subnet, but additional bandwidth is needed to certain systems.

The site cannot upgrade its network infrastructure to newer, faster technologies, such as Gigabit Ethernet, which would improve network throughput.

The source of a bottleneck is a particular system's network connection, but the switch to which it is connected is under-utilized and has additional ports and bandwidth available. Another connection to this system would reduce resource contention.

There are no additional IP subnetworks assigned or available for configuration, and the host requires more bandwidth to access the current subnetwork than one network interface card allows.

For the system to function properly when configured in this manner, it must meet all of these conditions:

It must be part of one of the following physical network layouts:
- Switched Ethernet (10/100/Gigabit)
- Switched Fiber Distributed Data Interface (FDDI)
- ATM Classical IP (CLIP)
- ATM LAN Emulation (LANE)

It must not be running a routing daemon (either gated or routed).

It must have access to all remote systems through each interface that is configured in the same subnet. For example, you must be able to successfully issue a ping command to the same remote system when each network interface is configured by itself. This implies that all interfaces in the system are connected to the same physical network switch.

This feature might affect the operation of network software or commands that rely on the network interface staying constant for the life of a connection. For example:

Multicast transmission might not work properly.

Utilities such as traceroute might give inconsistent output, since the interface used might change from packet to packet.

No special settings are required to use this feature. Configure the network interfaces as directed in Section 2.3.1 and assign the interfaces IP addresses in the same subnet.

By default, configuring an interface adds an additional interface route into the routing table. If you wish to add routes using the route command or the /etc/routes file, see the route(8) reference page for details on adding routes on multiple interfaces. For example, you might want to add a default route on multiple interfaces. See netstat(1) for information on how to view the kernel routing table.

2.6 Enabling Access Filtering on an Interface

Interface access filtering helps you detect and prevent IP spoofing attacks. To enable interface access filtering on an interface, do the following:

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

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.7 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.
`-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 A 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 provides 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 and its options.

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.8 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:

Log in as root.

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 is 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 and its options.

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.9 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` ^{[Footnote 1]}	Deletes a source routing table entry.
`-DISEntry mac_address` ^{[Footnote 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` ^{[Footnote 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` ^{[Footnote 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` ^{[Footnote 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.

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

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 -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)

Have Route indicates the source system has a valid path to the destination system. [Return to example]

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

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

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

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

The following example shows 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.10 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 example shows the IP MTU size of DETRA interface to 2044 bytes:

% ifconfig tra0 ipmtu 2044

2.11 Managing Network Quality of Service

As applications place increasing demands for bandwidth on the Internet network, increasing the network bandwidth is only a temporary solution. Newer real-time applications demand both increased bandwidth and low latency. Clearly, the importance of bandwidth management is increasing.

An IP network with its Best Effort delivery service performs a form of passive bandwidth management. If an outgoing queue is full, indicating high network traffic and congestion, the packets are quietly dropped. Some upper-level protocols can detect data loss, others cannot.

Quality of service (QoS) is the phrase commonly associated with the concept of actively managing network bandwidth. In this scenario, all network elements (for example, hosts, applications, and routers) and all network protocol layers cooperate to ensure consistent traffic and service end-to-end in a network. Network bandwidth for real-time applications is reserved, while sufficient bandwidth remains for best-effort traffic.

The major network QoS components in this operating system are as follows:

Traffic Control subsystem -- Provides an application data flow with a QoS that approximates Best Effort delivery through unloaded network interfaces.
Traffic control is supported on the Ethernet and FDDI interfaces.

Resource ReSerVation Protocol (RSVP) -- Provides a mechanism to reserve bandwidth on the local system and through the network. On this operating system, RSVP is implemented in the form of the rsvpd daemon. The rsvpd daemon uses the Traffic Control subsystem to install and modify flows and filters for a specific network interface.

RSVP Application Programming Interface (RAPI) -- Enables a local application that requires enhanced QoS to communicate with the rsvpd daemon. Using the RAPI routines, an application can make resource (bandwidth) reservations on the local system or advertise services to other nodes in the network, or both. See the Network Programmer's Guide for a description of the RAPI routines.

2.11.1 Managing the Traffic Control Subsystem

The Traffic Control subsystem performs the following tasks:

Implements an admission control mechanism that maintains interface parameters, such as the device's peak output rate, the percentage of bandwidth that can be reserved, and the maximum number of concurrent flows.

Ensures that applications do not pace data at a rate faster than allowed.

Interfaces with the rsvpd daemon and the iftcntl command to install and remove flows and filters.

Matches all outgoing packet headers with any existing filter specifications to determine on which output queue to place the packets.

See iftcntl(8) for more information.

The rsvpd daemon requires that traffic control be enabled on the local system in order to install and modify flows and filters for a specific network interface. To enable traffic control on your local system, check that the ether_cl_scheduler system attribute is enabled (set to 1). If it is not enabled, enable it by using the sysconfig command or dxkerneltuner. Then, reboot the system.

2.11.2 Managing RSVP

RSVP assigns QoS to specific IP data flows or sessions, which can be either multipoint-to-multipoint or point-to-point. In order to receive data packets for a particular multicast session, a host must have joined the corresponding IP multicast group. A given session may have multiple senders and if the destination is a multicast address, multiple receivers.

The rsvpd daemon performs the following functions:

Listens for incoming RSVP messages

Communicates with RSVP-enabled applications on the local host through RAPI

Interfaces with the operating system's Traffic Control subsystem

See rsvpd(8) for more information.

2.11.2.1 Starting and Stopping rsvpd

To start the rsvpd daemon, enter the following command:


# /usr/sbin/rsvpd

If you want to start the daemon automatically at system boot time, include the command in the /etc/inet.local file. See rsvpd(8) for more information on the daemon and its options.

To stop the rsvpd daemon, enter the following command:

# kill -9 `cat /var/run/rsvpd.pid`

The rsvpd daemon does not start or stop any applications during its startup or shutdown procedures. It also does not maintain any on-disk configuration information about applications. Whenever the rsvpd daemon starts, it has no knowledge of previous reservations.

Typically all daemons on the operating system are started or stopped together, as the system changes run levels. But applications should correctly handle situations where they start before the rsvpd daemon, or are running while the rsvpd daemon is restarted. In these situations, local applications need to reinitiate communications with the rsvpd daemon.

2.11.2.2 Adding and Deleting Network Interfaces

When you add or delete a network interface on your system, you must stop and restart the rsvpd daemon in order to for it to update its table of available interfaces. Enter the following commands:

# kill -9 `cat /var/run/rsvpd.pid`
# /usr/sbin/rsvpd

2.11.2.3 Displaying RSVP Session Information

You can display RSVP session information on routing systems or end systems to determine if RSVP is working correctly on your system. RSVP session information will show you if connections are are being set up and if reservations are being honored.

To monitor active RSVP sessions on the local system, enter the following command:

# /usr/sbin/rsvpstat

By default, the rsvpstat command displays a list of all RSVP sessions, sender and receiver, active on this system. Information includes the session number, destination address, IP protocol, port number, and the number of PATH and RESV states for the session.

To display sender information, including the contents of the actual PATH message from the sender, enter the following command:


# /usr/sbin/rsvpstat -Sv

To display receiver information, including the contents of the actual RESV message from the receiver, enter the following command:


# /usr/sbin/rsvpstat -Rv

See rsvpstat(8) for more information.