Migrating X.25 over PSI to XOL

11
flowcontrol off
thruputclass off
fast_select_accept disabled
reverse_charge disabled
def_inpacketsize 128
def_outpacketsize 128
def_inwindow 2
def_outwindow 2
def_inthruputclass 11
def_outthruputclass 11
#
# IP Parameters
#
ipaddress 192.168.8.1 255.255.255.0
idletimer 600
holdtimer 300
mtu 1024
LLC2 specific configuration file
The LLC2 specific configuration file is created in the /etc/x25 directory. The filename of the LLC2
specific configuration file is user-defined. The filename of the LLC2 specific configuration file is
llc2_conf_def by default. This file contains the maximum number of XOL interfaces allowed on
each LAN interface in the system and is unique to the host system.
In X.25 over PSI, the X.25 interface maps to a physical interface on the PSI card. In X.25 over LLC2,
the XOL interface (identified by the XOL logical port ID) maps to a logical interface on the physical
LAN interface. Each LAN interface allows a maximum of eight XOL logical interfaces if configurable
SAP support is available in the XOL router. The maximum number of XOL interfaces allowed on each
LAN interface can be modified in the LLC2 specific configuration file.
Following is the syntax of the LLC2 specific configuration file:
lan<#> <max number of XOL interfaces>
Following is a sample LLC2 specific configuration file:
lan0 3
lan1 1
Application Migration
After the XOL interface is configured, the X.25 application uses the XOL interface to communicate
with the peer X.25 systems (an XOL or a PSI port.) The migration of X.25 from PSI to LLC2 is seamless.
The X.25 applications require minimal or no changes after migration to XOL.
XOL does not support packet sizes greater than 1024 bytes in Layer 3. Any X.25 application that
explicitly uses more than 1024 bytes of packet size in Layer 3 must be modified and re-compiled after
migrating to XOL.
The application can use the same interface name for XOL and X.25 over PSI or use a new interface
name. However, it must be modified and re-compiled if the interface name is altered after migration.
X.25 applications are binary compatible if the applications require no change in the packet size or
the interface name while migrating to XOL.
For more information on configuring XOL, see the X.25 User Guide available at:
http://docs.hp.com/en/netcom.html#X.25