OSI/TS Configuration and Management Manual

Configuring the OSI/TS Subsystem
OSI/TS Configuration and Management Manual—424831-001
3-35
One TSP Process Supporting Each X25AM Line
== Add subdevices for line $X25C
=============================================================
add su $tsp1.#lcs01, like $tsp1.#las01, nspdevice $x25c
add su $tsp1.#lcs02, like $tsp1.#lcs01
add su $tsp1.#lcs03, like $tsp1.#lcs01
=============================================================
== Add subdevices for line $X25D
=============================================================
add su $tsp1.#lds01, like $tsp1.#las01, nspdevice $x25d
add su $tsp1.#lds02, like $tsp1.#lds01
add su $tsp1.#lds03, like $tsp1.#lds01
==
start su $tsp1.*
One TSP Process Supporting Each X25AM Line
In this configuration, each X25AM line is controlled by a separate TSP process.
Figure 3-5 illustrates this type of configuration.
Because transport connect requests can arrive on any line at any time, there must be at
least one transport attach outstanding on one of the TSP subdevices for each X25AM
line.
The following subsections contain a discussion of the advantages and limitations of this
type of configuration, as well as an example command file.
Figure 3-5. Large Application Configuration: Single TSP for Each X25AM Line
305CDT .CDD
Transport Layer
Network Layer
Data Link Layer
$X25A
(X25AM)
$X25B
(X25AM)
$X25C
(X25AM)
$X25D
(X25AM)
$TSP1 $TSP2 $TSP3 $TSP4