osid.cfg(4) CLIX osid.cfg(4)
NAME
osid.cfg - ISO/OSI STREAMS configuration file
DESCRIPTION
The /etc/osid.cfg STREAMS configuration file specifies the STREAMS drivers
that have been installed, and the ones to be used to build the ISO/OSI
protocol stack.
The file consists of a series of entries that correspond to an installed
STREAMS driver. An entry consists of a symbol that represents the driver,
followed by one or more parameters applicable to the driver, as shown in
the following:
Symbol param1=value1 [param2=value2] ...
The purpose of each entry is to provide a never-changing name to each
STREAMS driver, and to associate this name with the name of a STREAMS
device (which can be changed) accessible to a user program. The osid
configuration utility can thus find the CLIX device name of each STREAMS
driver by searching for its symbol in the osid.cfg file.
There are two types of entries in osid.cfg: specific entries and generic
entries.
The osid daemon uses specific entries to determine which STREAMS drivers
must be linked. The osid utility is designed so that it automatically
builds the correct protocol stack based on the specific entries that the
osid.cfg file contains.
Generic entries are read by networking applications that use transport
products. These entries allow a system administrator to select which
protocol stack the application accesses, which is useful if two or more
similar protocol stacks are installed. In addition, osid reads some
generic entries in cases where specific entries do not provide enough
information to configure a protocol stack. This may occur when other
STREAMS products are used in conjunction with the Intergraph OSI/LAN or
OSI/WAN products.
SPECIFIC FILE ENTRIES
The specific entries for the STREAMS drivers included with OSI/LAN or
OSI/WAN are listed below. Note that each entry has a device name
parameter. Other parameters associated with the entry are also explained.
TIMER device=timer_device
The timer driver. The default timer device name is /dev/tmr.
TP_610 device=tp4_device
2/94 - Intergraph Corporation 1
osid.cfg(4) CLIX osid.cfg(4)
The entry for the driver that incorporates the connection-oriented
Transport Protocol class 4 (TP4) and connectionless Internetwork
Protocol (IP). The default name for this device is /dev/cots.
LLC_610 device=LLC1_device
The entry for the LLC1 driver. The default name for this device is
/dev/dlpi.
PORTn device=/dev/devname [lsap=hex] [esgaddr[=a1]] [isgaddr[=a2]]
PORTn is the entry for a MAC driver; n is a non-negative decimal
integer that identifies a particular MAC driver. In the first
instance of PORT in the configuration file, n must be 0. In each
subsequent instance, n must be incremented by 1.
The /dev/devname entry is the device name of the MAC driver. The
default device name is /dev/dlpi.
The lsap entry is a hexadecimal value, as shown in the example
file.
The a1 entry is the end system multicast address of the device; and
a2 is the intermediate system multicast address. If you include
esgaddr or isgaddr without specifying the address, the value
defaults to the standard multicast address.
The following specific entries can be in the osid.cfg file if you are
using other STREAMS products:
TP024 device=TP024_device
The entry for the Transport Classes 0/2/4 STREAMS interface driver
(included with the OSI/WAN product). The default name for this
device is /dev/cox.
X25 device=X25_device portn nvcs=n
Entry for an X.25 PLP STREAMS interface driver. The X25_device is
/dev/X_25. The portn entry can be 0 or 1, but must match the port
number that is configured in the /etc/configx25.dat file. The
default is 0.
The nvcs parameter specifies the number of X.25 virtual circuits
that TP 0/2/4 can use (including at least one for handling incoming
calls).
GENERIC FILE ENTRIES
Generic entries are read by user applications to determine, when two or
more similar protocol stacks are present, which stack to use. In certain
circumstances (defined below) the configuration utility can read a generic
entry. The generic entries listed below, which are associated with
OSI/LAN drivers, may appear in osid.cfg. Note that all generic entries
2 Intergraph Corporation - 2/94
osid.cfg(4) CLIX osid.cfg(4)
require a single parameter: the device name of the STREAMS driver with
which the entry is associated.
TP4 device=TP4_device
Generic entry for the TP4/IP driver
LLC1 device=/dev/device
Entry for the LLC1 driver. The default is /dev/dlpi.
EXAMPLE FILE
The following shows a configuration file suitable for both an OSI/LAN and
OSI/WAN environment. The TP_NSAP= parameter is automatically written to
the file when you use the osiconfig utility to configure the protocol:
# OSI lower layer configuration file
TP4 device=/dev/cots
LLC1 device=/dev/dlpi
# OSI/WAN (class 0/2/4 transport over CONS)
TP024 device=/dev/cox
X25 device=/dev/x_25 port=0 nvcs=3
# Mandatory lower layer support driver
TIMER device=/dev/tmr
# OSI/LAN (class 4 transport over CLNS)
# can use LLC to provide subnetwork services.
TP_610 device=/dev/cots
LLC_610 device=/dev/dlpi
PORT0 device=/dev/dlpi lsap=fe esgaddr isgaddr
TP_NSAP = 470004003d000100000000000101
RELATED INFORMATION
Intergraph ISO/OSI Administrator's Guide
2/94 - Intergraph Corporation 3