       NOTES ON THE SET OF TRAFFIC GENERATOR CONFIGURATION FILES

There is two kinds of configuration files for FR traffic generator:

 - factory provided,

 - user defined.

The factory provided files are available for quick loading and running by
selecting F3 from the main menu of the traffic generator while the
user defined files are available by selecting F4 from this menu.
Both files can be also loaded by selecting F9 from traffic generation
screen but in that case the emulation does not start automatically.

The main differences between the two kinds of files are:

 - the factory provided files do not override the current selection
   of line configuration parameters (all the parameters selectable
   via functions F6 and shift F6 from the main menu), e.g. they do
   not change media, link control protocol, DCE/DTE clock selection, etc.

 - the factory files prompt for DLCI numbers when loading if the PVC
   coverage is "single DLCI" or "sel group",

 - the factory files cannot be overwritten by saving the changed
   configuration under the same name (a different name must be
   provided if someone wants to create a user defined file based on
   factory provided file).

One can notice the difference between the two kinds of files when
browsing through the directory of "FTG" files (the box at the top of
the screen reports TYPE: factory defined or TYPE: user defined,
respectively) and when looking at the top line of the traffic
generation screen (the name of test loaded is marked with [F] or
[U] flag).

There is three sets of "FTG" files provided with LM2000 executables:

 - 12 factory provided files with names starting from "FAC_"

 - 16 user defined files that make LM2000 emulate the network side of
   FR interface (for internal use only) with names starting from "NET_"

 - 116 files (with names starting from "E_") that define example
   configurations for demo purposes.

The file naming is structured in order to reflects several
configuration factors (those factors are given in the descriptive
name and comment used by the configuration loader).


1. FAC_*.FTG files

The file name pattern is:

 FAC_??0.FTG, FAC_??1.FTG, and FAC_??_L.FTG

where ?? is one of the following:

 SG stands for single PVC coverage,
 GR stands for selected group (up to 32 PVCs) coverage,
 AC stands for "all active circuits" coverage,
 PR stands for "all provisioned circuits" coverage.

0 stands for "low" (10% of CIR) traffic, 1 stands for "nominal" (100%
of CIR) traffic and _L stands for loopback function.

The test with "single" or "group" coverage prompt for DLCI number(s)
when loading.  CIR is 64K by default unless defined differently in
CONFIG.FR database file for LAPF statistics.


2. NET_*.FTG files

The file name pattern is:

 NET_xy.FTG or NET_xr_R.FTG

where x is either R (RS232 interface at 64K) or V (V.35 interface at
1.5M) and y represent the link control protocol:

 N for none,
 A for ANSI,
 C for CCITT,
 L for LMI.

Loading any of the above files puts the product in a very special
mode in which it emulates (in a rudimentary form) a DCE FR device
(both clock and link control protocol) prepared for looping back
frames coming over circuits with predefined DLCIs.  The files with
"_R" ending in names force also to XOR the received DLCIs in order to
imitate scenario in which outgoing and incoming traffic uses different
DLCIs. The predefined DLCIs are: 111, 222, ..., 888 for "same DLCI
both ways" case and 111, 400, 222, 289, 333, 178, 444, 67 for
"different DLCIs" case.

The files can be used for showing performance of the FR TG subsystem
both with factory provided files (instead their loopback
counterparts) or with example configuration files.

3. E_*.FTG files

There are four groups of files depending on the PVCs coverage factor:

 E_SGnxy.FTG for single PVC coverage,
 E_GRnxy.FTG for selected group (up to 32 PVCs) coverage,
 E_ACnxy.FTG for "all active circuits" coverage,
 E_PRnxy.FTG for "all provisioned circuits" coverage.

in all cases digit n represents traffic load type (meant differently for
different types of coverage), x is either R (RS232 interface at 64K) or V
(V.35 interface at 1.5M), and y represent the link control protocol
or special DCE clock mode with no link protocol:

 S for auto sensed,
 N for none,
 A for ANSI,
 C for CCITT,
 L for LMI,
 D for special DCE clock mode.

For E_SGnxy.FTG files n takes one of the following values:

 0 - "light" (10% of CIR) traffic,
 1 - "nominal" (100% of CIR) traffic,
 2 - "bursty" (50% of CIR, burstiness of 50%) traffic.

For E_GRnxy.FTG files n takes one of the following values:

 0 - three symmetrical PVCs,
 1 - three diversified PVCs,
 2 - mix of bursty and nonbursty PVCs,
 2 - mix of "short frame" and "long frame" PVCs.

For E_ACnxy.FTG and E_PRnxy.FTG files n takes one of the following values:

 0 - "light" (10% of CIR) traffic,
 1 - "nominal" (100% of CIR) traffic.

All the above files except for those with y=D can be played either
for the "real life" scenario with the analyzer hooked to an access
line of a FR network (preferably with some kind of loopback
arrangements either via networking equipment or another analyzer in
software loopback mode) or to another LM2000 box configured to
emulate the network side of FR interface (manually via shift F7 from
the main TG menu or by loading the appropriate one of NET_*.FTG
files).  In all the cases a user can stop the emulation after loading
and running an *.FTG file to change any parameters, specifically
"sensing return DLCI" if the scenario uses different DLCIs for
outgoing and incoming traffic.

The E_??nxD.FTG files are meant as a demoing tools because they do
not require a second LM2000 box or access to FR network to operate.
The preferred way of doing this is with the appropriate physical
loopback connection.


4. Possible uses of *.FTG files by LM2000 customers

The end users are expected to use primarily FAC_*.FTG files.  They
are not going to be given any NET_*.FTG files or E_??nxD.FTG files
(the exception can be E_GR0RN.FTG file that serves as an easy tool
for checking the overall sanity of the product - all it requires is a
wire connecting pins 2 and 3 on the RS232 connector of LM2000 board).
Files E_ACnxy.FTG and  E_PRnxy.FTG are equivalents of FAC_ACn.FTG and
FAC_PRn.FTG, respectively with particular selection of media
interface and link control protocol.  Files E_GRnxy.FTG can be
provided as "theoretical" examples only because they assume certain
DLCI numbers that are unlikely to be real for a given test scenario.

Typically, for a scenario with the analyzer connected to a real FR
network and network-provided loopback, a user is expected to take the
following steps:

 - connect physically to the interface offered by the network (as a
   DTE device),

 - enter a TG screen of LM2000 by selecting F9 on the main menu,

 - make sure the media selection shown in the box displayed above the
   function keys is consistent with that being in use, if not -
   adjust this configuration parameter by entering configuration menu
   via F6,

 - if the network requires a known link control protocol make sure
   that this protocol is selected in the box (leave default NONE if
   "raw" interface or choose AUTO if unknown),

 - (optionally) make sure that other line configuration parameters
   controllable via screens selected with F6 or shift F6 (e.g. max
   frame length, bit encoding, link protocol timers, etc.) are set
   properly (the factory defaults should be OK in 99% cases),

 - (optionally) if a user knows the PVCs involved because he or she
   previously monitored the FR access point with LM2000 and has a LAPF
   statistics database, put name of the database (i.e. *.FR) file
   into the line configuration box,

 - press F3 and choose one of FAC_??n.FTG files (that will run a TG
   session),

 - play with traffic parameters or other configuration parameters as
   needed and (optionally) store some favorite configurations under
   distinct names.


For a scenario with the analyzer connected to a real FR network and
loopbacks to be done via another LM2000 unit(s), a user is expected to
take the following steps:

 - connect physically to the interface offered by the network (as a
   DTE device) with both the unit acting as traffic generator and
   unit(s) acting as software loopback providers,

 - enter a TG screen of LM2000 by selecting F9 on the main menu (for
   all the units),

 - make sure the media selection shown in the box displayed above the
   function keys is consistent with that being in use, if not -
   adjust this configuration parameter by entering configuration menu
   via F6 (all units),

 - if the network requires a known link control protocol make sure
   that this protocol is selected in the box (leave default NONE if
   "raw" interface or choose AUTO if unknown), do it for all units,

 - (optionally) make sure that other line configuration parameters
   controllable via screens selected with F6 or shift F6 (e.g. max
   frame length, bit encoding, link protocol timers, etc.) are set
   properly (the factory defaults should be OK in 99% cases), do it
   for all units,

 - (optionally, only for the traffic generator unit) if a user knows
   the PVCs involved because he or she previously monitored the FR
   access point with LM2000 and has a LAPF statistics database, put
   name of the database (i.e. *.FR) file into the line configuration box,

 - press F3 and choose one of FAC_??_L.FTG files on the loopback
   unit(s) (that will run a loopback session),

 - press F3 and choose one of FAC_??n.FTG files on the traffic
   generation unit (that will run a TG session),

 - play with traffic parameters or other configuration parameters as
   needed and (optionally) store some favorite configurations under
   distinct names.

A user is likely to choose FAC_SG??n.FTG or FAC_GR??n.FTG (with
their loopback counterparts FAC_SG??_L.FTG or FAC_GR??_L.FTG) if he
or she knows DLCIs of the PVCs involved in emulation.  On the other
hand, if the DLCI assignments are not available but the network
provides a link control layer then choosing FAC_AC??n.FTG or FAC_AC??n.FTG
with their loopback counterparts FAC_AC??_L.FTG or FAC_PR??_L.FTG may
be a good idea.



5. Possible uses of *.FTG files by LM2000 "dealers"


A "dealer" is meant here as a label for anybody trying to either sell
or demonstrate the FR TG feature of LM2000.  If this person has two
LM2000 units and proper cabling for a chosen media interface then the
way of his/her using the *.FTG files is going to be similar to that
described below for developers and QA people.  Otherwise (with just
one box and physical loopback for either RS232 or V.35) the most
useful set of files is that of E_SGnxD.FTG and E_GRnxD.FTG (where x
is R for RS232 demo and V for V.35 demo).  The files mentioned allow
immediate and painless start of sample traffic generation sessions.

Alternatively, an operator can enter a TG main screen, press shift F6
to change to DCE clock mode, and then run one of either FAC_SGn.FTG
or FAC_GRn.FTG files.

Obviously, any configurations based on presence of a link control
layer cannot be exercised this way.


6. Possible uses of *.FTG files by the development/QA team

A quick check by a developer/QAer may start from a few "single box"
sessions done in the way described above (for demoing).

A full cycle of tests involve two LM2000 units with one running
NET_*.FTG files (as network emulator) and the other running either
E_*.FTG or FAC_*.FTG files.  Basically for every combination of line
parameters offered by NET_*.FTG files one can try the matching
factory and user (example) configurations on the other side.

The two-unit scenario can be also used to test the loopback function
of the FR TG but only for a case with no link control protocol.  To
do that one can run a E_SGnxD.FTG or E_GRnxD.FTG on one side with
FAC_SG_L.FTG or FAC_GR_L.FTG (and media choice consistent with "x")
on the other side.  The loopback function combined with any link
control protocol cannot be tested without accessing a real network
(because the product cannot emulate the network side of FR link
control interface when generating traffic).