FileID = OSILocalESISCnfg.sys

{LocalES}

Example 1
                  NSAP                        SNPA          Comment

: 39 840F 454E45 00000009 0003 000B 00 , 08000B40065E FE ; AFI 39 format

Example 2

: 49 0003 09000B400000 FE 00           ; possible local NSAP with embedded
, 09000B400000 FE                      ; Subnetwork Point of Attachment

{IS}

         Network Entity Title                 SNPA        Router Name

: 39 840F 454E45 00000009 0003 000C 00 , 080020000556 FE , Bridge01 


{END}   THE REMAINDER OF THIS FILE IS DOCUMENTATION.


The above examples form a syntactically correct ESIS configuration file.
Entries may be added, modified or deleted as necessary, or entire sections 
may be deleted if not needed.  It is advisable to read the documentation and 
syntax notes which follow before making any modifications.


LocalES Section Entries.

OSI TransportLAN uses an internal table called the LocalES table to hold 
addressing information for other End Systems (ES) on the local subnet.  
The ESIS routing protocol implemented in OSI TransportLAN allows each end 
system to collect addressing information for all other BTOS OSI end systems 
configured on the local subnet, and dynamically update the LocalES table with 
this information.  

Entries in the LocalES section of this file are used to statically configure 
explicit addressing information which cannot be obtained dynamically by the 
ESIS routing protocol.  This might include information about nonBTOS OSI 
end systems on the local subnet, or end systems located on other subnets.  
Each entry in this section contains two fields 

   1. NSAP.  The format and abstract syntax of a Network Service Access Point 
      entry is implementation dependent, but is limited to 20 bytes in length,
      including the NSAP selector.  The AFI and related syntax shown are for 
      example only.  Any NSAP format may be used.
   2. SNPA.  The Subnetwork Point of Attachment is a concatenation of the 
      48bit MAC address and the 8bit LSAP of the node where the NSAP may 
      be accessed.  This LSAP should be FE for an OSI network layer.

THE ENTRIES IN THE {LocalES} SECTION OF THIS FILE ARE PROVIDED AS EXAMPLES 
ONLY, AND ARE NOT REQUIRED FOR THE PROPER FUNCTIONING OF OSI TRANSPORTLAN.  
THESE ENTRIES SHOULD BE DELETED IF NOT NEEDED, OR MODIFIED AS NECESSARY.


IS Section Entries.

The {IS} section defines the Intermediate System (IS) to be used if the 
specified NSAP is not located on the local subnet and explicit addressing 
information has not been provided in the {LocalES} section.  An IS entry 
requires three fields 

  1.  NET.  The Network Entity Title identifies a network layer entity and
      is generally used in communications between IS's.  It is permissible 
      to leave this field null (no data before the first comma).  Otherwise, 
      the NET has the same syntax as an NSAP but is distinct from any other 
      NSAP address.
  2.  SNPA.  This has the same syntax as that in the Local ES table.
  3.  Router name.  The label chosen for the IS (bridge or router) is a 
      local issue.  This is a character string of up to 8 bytes in length.

THE ENTRY IN THE {IS} SECTION OF THIS FILE IS PROVIDED AS AN EXAMPLE ONLY, 
AND IS NOT REQUIRED FOR THE PROPER FUNCTIONING OF OSI TRANSPORTLAN.  THIS 
ENTRY SHOULD BE DELETED IF NOT NEEDED, OR MODIFIED AS NECESSARY.


Syntax.

This file is organized in logical sections, which are preceded by section 
headers.  These section headers are enclosed in braces {}.  Valid section
tags are LocalES, IS and End.  Sections may have entries or be empty, or 
they may be removed if not required.  Sections may be implemented in any 
order, except that the end tag must be present and it must be last.  
The End tag terminates reading of the file and nothing beyond this tag
is seen by the configuration utility.  Large comments should follow the 
End tag.  Section tags do not terminate comment mode, but they are ALWAYS 
recognized.

Data entries within a section are started by a colon, and the fields within 
an entry are separated by commas.  Any field in an entry can wrap to the next 
line.  An entry is terminated by a new section tag or by the next entry.

A semicolon is used to indicate the beginning of a comment.  Comments are 
terminated by the colon which begins the next data entry, or by the comma 
which begins the next field within an entry.  Comments cannot contain 
braces.  Comments within a data section cannot contain braces, colons or 
commas.  This reading of this file begins in comment mode, and remains in 
comment mode until the first colon in a section is found.

The data entries in this file consist of addressing information.  All 
addresses must be expressed as strings of hexadecimal bytes, with each byte 
expressed as a two character pair in the range 00 to FF.  An exception is 
the IS router name, which is a character (text) string.

Nothing in this file is case sensitive.  Data within a field may be 
presented as a string of contiguous characters, or the characters may be 
separated by any number of spaces or tabs.  This allows data to be 
written in such a way as to separate logical fields within the information 
being presented.
