Search our site   

SyncSwitch

SyncServer

Subsystems Summary

Wanware Linux

Netcom II (Linux, Solaris)

Wanware SNA

Wanware NT

Adapters

Case Studies

Product Documentation

Home

Site Map


The Software Group's Solaris Port of ISODE

Introduction

ISODE is an OSI Development Environment originally created by Marshall T. Rose of the Wollongong Group as a non-proprietary OSI protocol suite. It includes the protocol stack as well as applications such as ftam/ftamd for file transfer.

The OSI protocol stack supports several options for the lower layers. For example, TCP/IP may be used. X.25 is another option, which is where this port of ISODE comes in. This port of ISODE adds support for TSG's X.25 API and allows the use of ISODE over either Netcom II/Solaris Sparc (using an X.25 stack in the same machine as the application) or SyncServer Client (an application utilizing an X.25 stack in a remote, IP-connected device).

What Do I Need?

TSG's support to ISODE takes the form of a tar file. It is based on the standard ISODE version 8.0 source with necessary modifications to allow it to compile on Solaris Sparc 8 or 9 and to use TSG's X.25 API.

Download Now

ISODE 8 for Solaris

In order to compile the source, you will need have a C compiler a yacc parser, lex and make. If you installed your machine with development tools, these will likely be in place.

Because of the architecture of the ISODE applications, two routines were required to be added to the API library, libx25.a. If you have Netcom II for Solaris Sparc version 4.9.1 or earlier, you will need to upgrade your libx25.a. Place the new library in /lib. This library change also requires some header file changes. Place new copies of libx25.h, libx25errs.h and libx25protos.h into /usr/include/sys/x25.

If you have SyncServer Client, you library and header files will already be up-to-date.

Download Now

libx25.a

libx25.h

libx25errs.h

libx25protos.h

If you are using a SyncServer 1000 version 1.3.1 or earlier, you will need to update the software in the SyncServer using ssupdate and a new ss.bin.upd file. No upgrade is required for SyncServer 2000 and higher.

Download Now

ss.bin.upd for SyncServer 1000

How Do I Build It?

  1. Extract the standard ISODE source:

    tar xf /tmp/isode-8.tsg.tar
    cd isode-8.0
  2. Run make:
    ./make all
    ./make all-ftam
    ./make inst-all
    ./make inst-ftam
                              
    You will need to run the last two commands as root if you have the usual system directory permissions.

    Note that you must run "./make" and not just "make". If there are other optional components you wish to use, see the Makefile for details.

Testing

You will need to place an X.25 call. This means that you will either need to be on an X.25 network and call yourself or use two machines with a null modem cable between them. Only netid 0 (link 0) is supported for ISODE. Before you begin with the ISODE testing, make sure that your link is up using tsgstat (Netcom II) or the Link Status in the Link Statistics window (SyncServer).

The ISODE services will act as the default for all incoming X.25 calls, so you need to make sure that no other application has issued a default listen. For Netcom II, you need stop the TSG-supplied call handler from performing a listen. To do this, edit the file /etc/x25net to run "x25daemon -n" rather than just x25daemon and then run x25net restart. This is not necessary for SyncServer.

The default install location for the ISODE files is in the directory /usr/Isode. The sbin directory contains the daemons (services to handle incoming OSI requests) and the bin directory contains the user applications.

On one of the test machines, run:

/usr/Isode/sbin/tsapd

This daemon handles all incoming ISO requests and starts up appropriate auxiliary services (for example, the ftam daemon). tsapd will turn on debugging if its stderr device is a tty.

On the other test machine, run:

/usr/Isode/bin/ftam 12345678

where 12345678 is the X.25 address of the machine you wish to call. It will ask you for a user name and password. These must match a valid login ID and password on the remote machine. If all goes well, you will be told that you are connected and then it will wait for further directions. You can, for example, "get /etc/termcap".