Installing and Administering OSI Transport Services

96 Chapter 3

Gathering Conﬁguration Information

Using the Local Parameter Worksheet

Device Interface

Name

For LAN-based subnetworks, you need to provide

the device interface name for the card. This is not

necessarily the same as the device ﬁle name.

Typically, the interface name will be “lanx” where

x is the logical unit number or the select code.

To view existing LAN card interface names, run

the utility lanscan(1M).

The encapsulation method must be IEEE802.3 to

allow OSI to run over an 802.3 LAN. To determine

if you have IEEE, type lanconfig lanX, where

“X” is the LAN interface you wish to use. If the

output does not show “IEEE”, edit the

/etc/rc.config.d/netconf ﬁle and add “ieee”

to the LANCONFIG_ARGS[0] entry.

CLNP Subset U.S. GOSIP requires the use of the full subset

with NULL packets being discarded. This is the

default.

The NULL subset is used only when all

destination OSI nodes are physically connected

via the same LAN. It provides low overhead at the

cost of internetworking. It also requires that the

NSAP match the MAC address of the LAN card.

Non-segmenting and Full subset (accept NULL)

are less frequently used, but are supported by HP.

Routing

Information

These describe how to reach systems that are not

directly connected to your subnetworks, and

require a router. For simple networks, you may

not require any route entries.

You can specify the route for speciﬁc destinations

by using the full remote NSAP. Otherwise, you

can specify a route for a set of destinations by

using a Network ID (or preﬁx) that is common to

all remote systems reachable through this route.

You must also specify the NSAP of the

Intermediate System that will act as the router

for the destinations.