OSI/TS Configuration and Management Manual

Configuring the OSI/TS Subsystem
OSI/TS Configuration and Management Manual—424831-001
3-26
Command File for Configuring OSI/TS Over a LAN
alter service ($tsp1.#L3, $tsp2.#L3), ipx25sndcf on
alter service ($tsp1.#L4, $tsp2.#L4), class 4, multiplex on
=============================================================
== Add and start local (initiating) subdevice.
=============================================================
add su $tsp1.#sndcf1, nspdevice $x25a &
, localtsel "fcfcfc" &
, remotetsel "fcfcfc" &
, localnsap "cfcf" &
, remotensap "fcfc", x25destaddr "432109"
start su $tsp1.#sndcf1
=============================================================
== Add and start remote (responding) subdevice.
=============================================================
add su $tsp2.#sndcf1, nspdevice $x25b &
, localtsel "fcfcfc" &
, localnsap "fcfc", x25port 9
start su $tsp2.#sndcf1
Command File for Configuring OSI/TS Over a LAN
This is an example of a command file to configure a generic (no ES-IS routing exchange
protocol) loopback test over a LAN. In this configuration, there are two TSP processes
on the same system that connect via a LAN (in other words, data goes from one process,
out over the LAN, and back to the same system, to the responding process). LAM1 and
LAM2 represent either TLAM or PAM. $tsp1 is the local process (the initiator), and
$tsp2 is the remote process (the responder). Each TSP process is configured with two
subdevices. Connections can be made between the following subdevices:
#lan1a and #lan2a
#lan1b and #lan2b
Figure 3-3
illustrates this example configuration.
Figure 3-3. Example LAN Loopback Configuration
303CDT .CDD
SU $tsp1.#lan1a SU $tsp1.#lan1b SU $tsp2.#lan2a SU $tsp2.#lan2b
TSP1 TSP2
LAM1 LAM2
LAN