MAN page from RedHat Other isode-8.0-2.i386.rpm

ISOTAILOR

Section: File Formats (5)
Updated: 5 July 1988
Index

NAME

isotailor- ISODE tailoring file

DESCRIPTION

The isotailor file contains information used to run-timeconfigure the ISODE distribution.Entries are separated by end-of-line (or the end-of-file).The character `#' at the beginning of a line indicates a comment line.The syntax is:

variable: value

as in

sbindir: /usr/etc/

The entries come in several types. There are general ISODEconfiguration parameters, operating system specific tailoring andinterface specific tailoring parameters.

LOCAL ENVIRONMENT TAILORING

There are some variables that are used to make up for deficiencies inoperating systems, or to override the operating system. These aredescribed as follows.

localname: This takes a string as a parameter and is used asthe name of the local host if the gethostname call(or equivalent, e.g., uname)is not used. This will also override any other run-time determinationof the local hostname.
binpath: This takes a string as a parameter and indicates the directory wherethe ISODE user programs are kept (be sure to use a trailing slash).
sbinpath: This takes a string as a parameter and indicates the directory wherethe ISODE system programs are kept (be sure to use a trailing slash).
etcpath: This takes a string as a parameter and indicates the directory wherethe ISODE configuration files are kept (be sure to use a trailing slash).

LOGGING TAILORING

There are a number of options that can be set for each layer of ISODE.The first variable indicates the default logging directory,the other variables give information about each log file.

logpath: This variable takes a string as a parameter and indicates thedirectory where the ISODE log files are kept (be sure to use atrailing slash).

The remaining variables are all configured in the same way and are inthe general format:

xyzlevel: [none] [exceptions] [notice] [pdus] [trace] [debug] [all]xyzfile: filename

The filename can be either the name of a file of a `-' in which casethe standard error is used. If the filename contains the string `%d'then this is replaced by the current process id.

The normal level for this style of tailoring is to set exceptions. Theother two values can be added in when debugging, if so desired.The current variables in this format are as follows.

compatlevel  native services subsystemcompatfileaddrlevel    addressing subsystemaddrfiletsaplevel    transport leveltsapfilessaplevel    session levelssapfilepsaplevel    presentation elementspsapfilepsap2level   presentation levelpsap2fileacsaplevel   association control levelacsapfilertsaplevel   reliable transfer levelrtsapfilerosaplevel   remote operations levelrosapfile

TRANSPORT STACK TAILORING

There are several variables which can be used to en/disable configuredTS-stacks and to define OSI communities and their relationshipto this system.

TS-STACKS

ts_stacks

which takes one or more of the following values:

[tcp] [x25] [x25-84] [bridge] [tp4] [all]

indicates which TS-stacks should be enabled.This is useful when multiple machines (with different interfaces)share the same executables.For example,the /etc/isotailor file is a normally symbolic link to/private/etc/isotailor.

OSI COMMUNITIES

ts_interim

which takes one or more OSI community names as a value.Each community name must be defined as a macro in theisomacros (5) file.

ts_communities

which takes one or more of the following values:

[int-x25] [janet] [internet] [realns] [localTCP] [all]

This variable is used to distinguish membership in various OSI communities.For example,a site with an X.25 connection might be attached to the International X.25network, but not the JANET.Thus ts_stacks would include ``x25'',and ts_communities would include ``int-x25'' but not``janet''.Note that the ordering of communities is important:network addresses will be tried in the order that their respectivecommunities are listed with this variable.

default_nsap_community

which takes an integer value,declaring the default community to be used for NSAP addresses.

default_x25_community

declaring the default community to be used for X.25 (DTE) addresses.

default_tcp_community

declaring the default community to be used for TCP (RFC1006) addresses.

TS-BRIDGE

These are the parameters that are used in the Transport-Service Bridgeimplementation.

tsb_communities: A list of pairs of values.The first of each value should be a community as defined in thets_communities variable(obviously the values ``none'' and ``all'' are not permissible).The second value of the pair should be a presentation address usingthe ISODE ``string'' format.When a call is to be placed and the network corresponds to oneof the communities given here, then a call through the bridge given inthe second variable will be made automatically.
tsb_default_address: This variable contains a string encoded presentation address which thebridge will listen on by default.This should normally consist of a set of network addresses with no selectorspresent.

Consider the case of a host with access to both the Internet and theInternational X.25 network.This host might have this entry in its isotailor file:

tsb_default_address: Internet=sheriff+17004\|Int-X25(80)=23426020017299+PID+03018000

This tells the bridge to listen on two network endpoints.Hosts in the Internet community wishing to reach the InternationalX.25 community would have this entry in their isotailor file:

tsb_communities: int-x25 Internet=sheriff+17004

Similarly,hosts in the International X.25 community wishing to reach theInternet community, would have the entry:

tsb_communities: internet Int-X25(80)=23426020017299+PID+03018000

INTERFACE SPECIFIC TAILORING

Most interfaces that ISODE runs over have some form of tailoring.These are usually very dependent on the interface. Each interfacewhich supports tailoring will now be described.

General X.25 Tailoring

There are two specific variables that can be used with any X.25interface.

x25_local_dte: This is the X.121 address that ISODE processes will listen onby default.It may be a full X.121 address or a sub-address.
x25_local_pid: This is the X.25 protocol ID that ISODE processes will listen on by default.Traditionally, this is the first four octets of the CUDF in hex-notation,e.g., 03010100.

There are also three variables for performing addressmanipulation as required by some network vendors.

x25_intl_zero: If this has the value `on' then any international DTEs (i.e.having non-local DNICs) will have a leading zero introducedbefore being passed to the network.
x25_strip_dnic: If this has the value `on' then any local DTEs (i.e. having thelocal DNIC) will have this DNIC removed before being passed tothe network.
x25_dnic_prefix: This should be set to the local DNIC (the first four digits of theDTE) of the host machine.It should only be set if one or both of the previous twovariables has the value `on'.It can contain more than one DNIC, this is only relevant if `x25_intl_zero' has the value `on'. All DNICs in the list will nothave the leading zero added. This is useful for private X.25networks (such as the european IXI) that do not need leading zeros.Only the first DNIC listed will be used in striping.

There are also two variables for logging X.25 statistics.

x25level: Defines the level of logging to be used for X.25 statistics logging.(At present, only ``notice'' level messages are generated.)
x25file: Defines the filename to be used for X.25 statistics logging.

SUNLINK X.25

These setting are only useful when SUN_X25 is defined along with X25.The effect of these parameters is more fully documented in the Sun manuals.

reverse_charge: Set to 1 or 0 to enable/disable reverse charging.
recvpktsize
sendpktsize: This should be set to one of 0 (default), 16, 32, 64, 128, 256, 512 or1024 to set the send/receive packet size.
recvwndsize
sendwndsize: This sets the send/receive window sizes. Legal values are 0 (default),7 and 127.
recvthruput
sendthruput: This sets the sending/receiving throughput values. Legal values are 0(default) 75, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 48000.
cug_req: Closed user group request. Set to either 0 or 1.
cug_index: Sets the closed user group index number.
fast_select_type: Sets the fast select parameters. Either 0, 1 or 2.
rpoa_req
rpoa: Recognised private operating agency parameters.

CAMTEC CCL

These are usedwhen the Camtec X.25 is accessed via theCCL (sockets) mechanism.

x25_outgoing_port: This selects which port on the Camtec card will be usedfor outgoing calls, and takes the value A, B or #.A and B are the two X.21 WAN interfaces and # is theEthernet.Listening is automatically done on all three ports.

BRIDGE X.25

These are parameters that are used in the tp0bridge implementation.

x25_bridge_host: The host machine that is running the tp0bridge.
x25_bridge_port: This is the TCP port that is to be usedfor bridging.The default is 146, which should be in defined in /etc/services.
x25_bridge_addr: The X.121 address of the remote host.
x25_bridge_listen: The X.121 address to listen on for incoming calls, on the remote host.
x25_bridge_pid: The protocol ID used for listening along with the previous address.This is encoded as a string of eight hex digits.
x25_bridge_discrim: A string used to discriminate the network. When attempting to place anX.25 call with BRIDGE_X25 and real X25 configured in, this string isused to decide which interface to use. If the string is empty, thebridge will be used. If it is set to `-' the bridge will not be used.If the string is anything else, it is compared against the calledX.121 address. If there is a match, then the bridge is used, otherwisethe real interface is used.

ULTRIX X.25

These setting are only useful when ULTRIX_X25 is defined along with X25.

The values should match definitions made externally (and prior to use ofISODE) as part of the local Ultrix X.25 management procedures. This willinvolve use of the "ncl" command and modification of the default X.25 configuration for the host. Ultrix X.25 does not let arbitrary processesconnect to the network, prior registration of templates, filters andcall classes to be used is required. Outgoing calls have reasonablefreedom to redefine the call DTE, paramaters and facilities, but listeningprocesses cannot specify the DTE and CUDF to be listened on internally.This must be coordinated by external management.

x25_default_filter: The Name of the Ultrix X.25 Management Filter that listening ISODE processes will bind to. This will have to be tailored individually foreach static listener you run, the default value is intended for tsapd oriaed (and is "Isode").
x25_default_template: The Name of the Ultrix X.25 call template that outbound ISODE calls will useby default. The DTE and CUDF values are overridden by the addressinginformation supplied with the connect request, so this value can be usedby all ISODE processes quite safely. (default value is "Default").
x25_default_class: The Name of the Ultrix X.25 call class that ISODE processes will useby default. This can be common to all ISODE processes, and is coupled tothe Template and Filter to identify incoming and outgoing calls.(Default value is "dte-0").
For further details of configuring these values, you should see theUltrix X.25 Management Documentation, and documentation for ncl.interface.

ULTRIX X.25 with DEMSA router

demsa_local_subaddr: The local subaddress. Default "25".
decnet_destination: The decnet destination identifier. Default "TSAPD".

TP4

nsap_default_stack: If the TP4 interface has access to both CONS and CLNS, thisparameter is used to determine the default. The value can be either``CONS'' or ``CLNS'';the default value is ``CLNS''.
local_nsap: A default NSAP for tsapd to listen on if the `-N' flag is used!

TLI TP4

The following setting are only useful when TP_TLI is defined.

tli_cots_dev: The name of the device node used to access COTS(default /dev/ositpi).
tli_cots_dev: The name of the device node used to access CLTS(default /dev/ositpi).

ICL TLI TP4

When using TLI on an ICL DRS6000, the following two addressing parameters will need setting:

tli_initiator_prefix: The sunbet name of the network interface to use for outgoing X.25 calls(default x25_tliin).
tli_responder_prefix: The subnet name of the network interface to use for incomming X.25 calls.(default x25_tlire).

XTI TP4

The following setting is only useful when XTI is defined.

xti_tp0_ident: The string value is the string passed to the XTI interface duringt_bind for X121 addresses.Default ``TOSITP0''
xti_tp4_ident: The string value is the string passed to the XTI interface duringt_bind for TP4 addresses.Default ``TOSITP4''

SESSION SERVICES TAILORING

There are three variables that can be tailored:

ses_abort_timer: The number of seconds to drain on session aborts.
ses_disconnect_timer: The number of seconds to drain on session disconnects.
ses_refuse_timer: The number of seconds to drain on session refuses.

DIRECTORY SERVICES TAILORING

There are two variables that can be tailored:

ns_enable: This takes either the string ``on'' or ``off'' as a parameter.If ``on'',then the ``user-friendly namservice" will be used to performname/address resolution.If the nameservice lookup fails,the stub-directory will be used as a fallback.
ns_address: This is the transport address of the nameservice.It is specified using the ISODE ``string'' format,e.g.,Internet=wp.psi.net+17006which indicates that the nameservice lives in the TCP/IP communications domainon TCP port ``17006'' at host ``wp.psi.net''.The nameservice is accessed via the OSI CO-mode transport service,so other kinds of addresses (e.g., X.25 addresses can be used as well).

PROGRAM-SPECIFIC TAILORING

By defaulta program-specific tailoring file is consulted before the system-widetailoring file.The program-specific file is called .myname_tailor in the user'shome directory,where ``myname'' is the name that the program was invoked with.

FILES

/etc/isotailor   ISODE tailoring file$HOME/.myname_tailor  program-specific tailoring file

AUTHORS

Marshall T. Rose
Simon Walton
Colin Robbins

Index

NAME

DESCRIPTION

LOCAL ENVIRONMENT TAILORING

LOGGING TAILORING

TRANSPORT STACK TAILORING

TS-STACKS
OSI COMMUNITIES
TS-BRIDGE

INTERFACE SPECIFIC TAILORING

General X.25 Tailoring
SUNLINK X.25
CAMTEC CCL
BRIDGE X.25
ULTRIX X.25
ULTRIX X.25 with DEMSA router
TP4
TLI TP4
ICL TLI TP4
XTI TP4

SESSION SERVICES TAILORING

DIRECTORY SERVICES TAILORING

PROGRAM-SPECIFIC TAILORING

FILES

SEE ALSO

AUTHORS

This document was created byman2html,using the manual pages.