Interview 8000 TURBO Series Technical Manual Issue 3 Sep95
User Manual: manual pdf -FilePursuit
Open the PDF directly: View PDF 
.
Page Count: 1020
| Download | |
| Open PDF In Browser | View PDF |
Introduction
Coqratulations on your choice of o.ne of the INTERVIEW 8000 TURBO Series line of Data ProtOCQ~
AnalyzerlBntulatol'$.! This wise decision will be rewarded with many productive years of testing and
emulation. a1ol1l with the capability of upgt~c.tUlI your UQit should your netw9rk require it.
For your ease--of..Uie. we have providGd you with four (t)fJve*) texts (and the Easy View On-Line MelW System):
30 Minutes to ProgrammiItJ the INTERYlEW@8O(IOSeries, 951-B0431..()1
lNTERVlEJ¥I>8000~ TeelmkalManwd. SeplCmber 1995, Volume I (951-00424-01)
lNI'ERVIE~ 8OfJ() Series T~l Ala., ~Ptember 1995, Volume II (951-B0427-Ql)
INTERVIEW'» 8000 TURBO S~ Qldck ~e Guide to the C Library (951.~3O..()1)
INTERVIEJ.f10 8000ATM 1'fcknical Manual, Sfptember 1995, (951-B0682.Ql) [with ATM units only]*
10 Miluf,te§ to. ~ the lJiTEBVIEW.8(){){} Series
Begin with the "thirty-minute guide." There is a data disj provided with it to introduce you to and to liVe
you a crash course in general Op¢l'8tion of Ule JNTERVISW 8000 TURBO .Units. You'll fmd this a balf;.bour
well spent as you get a feel for using the function keys and menus, familiarfa:j~i y~~lf with t~ oporation
of the INTERVIEW.
.
T~Jmical Manual
The two volumes of the [NTERV1~ 8000 Series Technical Manual are divided into Part l' Basic Operation
and Part [l' Advanced Programming. These are the complete source of information on your unit and so are
understandably quite large. We do not expect you to read them in their entirety; therefore, the Table of
Contents and the three comprehensive inde;ws--all three are multi-level and cross-referenced-are valuable
tools to use in familiarizing yourself with the technical manual. There is also a Ust of'Thbles following the
Table of Contents in the front matter of tbe tiPt volume.
INTERVIEU'@ 8{)()Q Series
Part I; BiIIk Operqtion. A glance at the Table of Contents reveals the first volume consists of 49
sections grouped into twelve sub-headings, including an index for the first volume:
I
Overview
II
Setup and Display
III
BCC and BERT
IV
Interfaces
File System and Miecellaneous Utilities
V
VI
Statistics
VII
Programming Concepts: Tiers and Layers
VIII
nigger Menus
IX
Protocol Spreadsheet
X
OSI Primitives
XI
Protocol Packages
XII
Index
Part I defines the basic operation of the INTERVIEW in detail and describes the menu fields and their
entries in depth.
SEP'95
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Part II: Advanced Programming. The Table of Contents shows the second volume consists of Sections
50 through 83. These sections are grouped under four sub-headings, along with Appendixes A through
J and two indexes-one combined index for both volumes of the technical manual and tliesecoIid '
index for the C-language structures, variables, and routines defined in the second volume:
XIII
Theory of Operation
XIV
C Language
XV
CLibrary
)(\n
Protocol Library
Appendixes
Index
." ..
'"
,'.'
,
("
Part II is technically for the advanced C-Ianguage programmer who wishes to modify programs already
provided in the software or to create his own programS. Along with a theory of operation of thellnit
and C-Ianguage background, it provides the C-Ianguage and protocol structures. variables, and routines
!JSed in the INTERVIEW 8000 TURBO Series. Structures are defined in depth; variables are discussed
iq'detail with the type, values (hex and decimal), ,and meanings presented
tabular format.' The
, routi'iies ate particularly well documented with a synopsis, a description, Inputs; 'returns, and examples
'given'foreach routine as applicable. The quick reference gl;liqe (described below) is a coinpanionto
" . - ~."
;'"
," ,"
this second volume of the technical manual.
IDa
Quick Reference Guide to the C Library
The quick reference guide is a condensed version of the Clanguage structure, variable, event, and routine
information used in the INTERVIEW as defined in the second volume of the technical manual. This small
reference guide is easy to use and cross-references pages in the technical manual where the C-Ianguage
terms are defined and used.
It is divided into three parts: an alphabetic listing, a listing by fu~ction, and an alphabetic definitions listing.
the iNTERVIEW, you will find this handy
little guide to be very useful.
If you do any programming on the Protocol Spreadsheet with
EasY View On-Line Menu System
When you boot up the INTERVIEW, the Easy View Main Menu is the first menu displayed. You'll find this
on-line documentation to be a valuable tool. Operational information, help, tutorials, and installed
application programs are available at your screen in this menu system at the touch of a key_ Follow the
instructions given on the bottom of the display to access the desired screen menus. Detailed information on
using Easy View is documented in the technical manual in Sections 4, 19, an&20~ ,.
., '
ATM (A!i,YOChronQus uamfer Mode! Technical Manual and Associated Manuals
If your unit is an INTER\nEW 8800 PLUS ATM or INTERVIEW 8750 ATM EXPRESS, you will also be
receiving the ATM technical manual. This manual describes the ATM units and is specific to Asynchronous
Transfer Mode testing. Included with it are various manuals for the on -line ATM application programs.
Again, congratulations on your selection of an INTERVIEW 8000 TURBO Series unit...we hope these
manuals will sexve' toanswer;your questions before you need to ask them.
,
i~
-
, : . "
,t '!." •
f'
SEP '95
Introduction
Introduction
Congratulations on your choice of one of the INTERVIEW 8000 TURBO Series line of Data Protocol
Analyzer/Emulators! This wise decision will be rewarded with many productive years of testing and
emulation, along with the capability of upgrading your unit should your network require it.
For your ease-of-use, we have provided you with four (or five*) texts (and the Easy View On-Line Menu System):
30 Minutes to Programming the INTERVI£Wt!IBOOO Series, 9 5 1 - B 0 4 3 1 - 0 1 \ ·
INTERVIEW'® 8000 Series Technical Manual, September 1995, Volume 1(951-00424-01)
INTERVIEW'®8000 Series Technical Manual, September 1995, Volume n (951-00427-01)
INTERVIEW"> 8000 TURBO Series Quick Reference Guide to the C Library (951-00431)..01)
INTERVIEW'® 8000?fTMTechnicalManual, September 1995, (951-B0682-01) [withATM units only]*
30 Minutes to Programmini theJNrERVIEW 8{)()O Series
.
Begin with the "thirty-minute guide:' There is a data disk provided with it to introduce you to and tRgive
you a crash course in general operation of the INTERVIEW 8000 TURBO units. You'll find this a ~alf-hour
well spent as you get a feel for using the function keys and menus, familiarizing yourself with the operation
of the INTERVIEW..
INTERVIEW® 8000 $erie§ Technical Manual
The two volumes of the INTERVIEWf!> 8000 Series Technical Manual are divided into Part I: Basic Operation
and Part II: Advanced Programming. These are the complete source of information on your unit and so are
understandably quite large. We do not expect you to read them in their entirety; therefore, the Table of
Contents and the three comprehensive indexes-all three are multi-level and cross-referenced-are valuable
tools to use in familiarizing yourself with the technical manual. There is also a List of Tables following the
Table of Contents in the front matter of the first volume.
Part l: Basic Operation. A glance at the Table of Contents reveals the first volume consists of 49
sections grouped into twelve sub-headings, including an index for the first volume:
I
Overview
II
Setup and Display
III
BeC and BERT
~, .
IV
Interfaces
. ,,'
File System and,Miscellaneous Utilities
V
VI
Statistics
Programming Concepts: Tiers and Layers
VII
Trigger Menus'
VIII
IX
PTotocolSpreadsheet
OSI Primitives
X
PTotocolPackages
XI
Index
XII
.:':~, ;;,
,
,',),,',J'J;,
.i.:~ 'iL '. ',~~ .,;'_;~ ":~l!:','t'"
,_,
Part I defines the basic operation of the IIr messages displayed for File Maintenance operations.
• "Communications \\fith Telenex" appendix updated with new information.
General Signal Networlt,s is a newly formed company by the merger of Telenex, Data Switch, and
Tau-non. Telenex ~ation is now General Signal Networb - Mount Laurel; we retain the
same personnel and
which have always been hallmarks of Telenex Corporation and
es within. this WIIlnUIiI to AR, AR Test Systems, and Telenex Corporation
AR Test Systems. Any
now refer to General S~ Networks - Mount LAurel.
hi=dards
I
General Signal Networ~ - Mount Laurel reserves the right to improve this manual or the
equipment it describes ~thout prior notice. Any references to upgraded equipment, options,
NOV '95
iii
ADDENDUM
accessories, and software packages made in the manuals may not apply to your present unit.
Contact Customer Service for information on such upgrades or other purchases.
I
Any duplication of the material in this manual in any form without written permission from General
Signal Networks - Mount Laurel is strictly forbidden.
, General Signal Networks - Mount Laurel will not be held responsible for any damages incurred in
the use of this product.
•
I
For technical information, programming assistance. error decoding. and repairs. contact the factory.
General Signal Networks - Mount Laurel is located in Mount Laurel, New Jersey, approximately
15 miles east of Philadelphia, PA. Local customers should call (609) 234-7900; in the northeastern
United States. call (800) 222-5482; and in the rest of the U.S., call (800) 222:-0187. Access us on the
Internet at http://www.telenex.com.
Address questions and comments about this manual and other technical publications to the
Technical Writing Department on extension 3548 at these same telephone numbers.
iv
NOV '95
Contents
Introduction
Part I: Basic Operation
Overview
I
1 Hardware ..................................................................
1.1
1.2
1.3
1.4
1.5
1.6
1.7
1.8
1.9
1.10
2
Physical Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Keyboard ........................................................
Front Panel .. '. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Disk Drives ......................................................
Back Panel .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Storage Capacity ................................................ "
Clock........ . ............................. ......................
Operating Environment ............................................
Operating Positions ............................................. '"
Power Up ................. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1- 1
1-4
1-4
1-4
1-6
1-8
1-16
1-17
1 -17
1-18
1-19
General Operation .......................................................
2-1
2.1
2.2
2.3
2.4
2.5
2.6
2.7
2.8
2.9
2.10
2-1
2 ... 3
2-7
2-8
2-9
2-16
2-20
2-22
2 ... 26
2-30
PowerUp ............... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Initializing System Software (Booting Up) .. .. .. . . . . . .. . . . . . .. . .. .. . ...
Installing New System Software on Hard Disk .'........................
Backing Up the Hard Disk. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .
The Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Running a Test Program ... ,. ....... . .. .. ........ ... . ....... ... .. ...
Data Flow. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
How to Correct Common Problems ..................................
Optimizing Recording Rates ........................................
OptimizingAnalysis............................. ..................
3 Keyboard
3.1
3.2
3.3
3.4
3.5
3-1
Hard Keys and Softkeys ........................................... . 3-3
Programming Keys ............................................... . 3 ... 3
Real"';Time Keys ................................................. . 3-10
Freeze-Mode Keys .............................................. . 3-13
Remote Control Keys ..... , ....................................... . 3-14
4 Easy View ................................................................ "
4.1
4.2
Booting Up ......................................................
Entering and Exiting Easy View .....................................
SEP'95
4-1
4-3
4-4
v
- -
-------------_._-------_._-
' - - - _ .._,._-----------
4.3
4.4
4.5
4.6
II
Easy View Menus .................................................
Using Easy View ..................................................
Additional Easy View Functions .....................................
Installing Easy View Updates .......................................
4-4
4-8
4-17
4-19
Setup and Display
5 line Setup ................................................................. 5-1
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
Mode. . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 5-3
Source. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 5-5
Code •••..•.. . . . . . . . . . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 5-6
Bits ............................................................. 5-7
Parity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . .. . .. . . . . . . .. 5-7
Format. ......................... ........ ................. .... ... 5-7
Clock Source ..................................................... 5-15
Bit-Order!Polarity ........ .... .................................... 5-16
NRZI........... .. .. ..... .............. ................. ........ 5-17
MIL...... ........................ ....................... ........ 5-17
Sample line Setups................................................ 5-17
6 Run-Mode Display ......................................................... 6-1
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
Auto Configure. .. . ... .. . . . . .. . ...... . .... .. . . . . ... . .... .. . . ......
Entering Run Mode ...............................................
Selecting Character-Data Display ..... , . '" ... . . .. .... .... .. .... . ...
Special Features of Data Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Protocol Trace. ....... . . ................ ........ .......... ........
Program Trace........ . . ........................... ..... ..........
Statistics Display .......................................... . ..... ..
Display Window. . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
User Trace .......................................................
Display Correlation in Freeze Mode.. ....... . .. .. .. .... . ... .. .. ... ...
No Display ........................................ '" . ........ ...
7 Record Setup ......................................... . . . . . . . . . . . . . . . . . . . . ..
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
vi
Format of Recorded Data ..........................................
Recording Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
The Screen Buffer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
SCSI Drive Maximum Recording Times ............................. "
The Record Setup Screen. . . . . .. . . .. . .. . . . . . .. . . .. . . . . .. . . .. . . . . ....
Trigger Control of Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Spreadsheet Control of Recording ...................................
Manual Control of Recording .......................................
6-3
6-5
6-7
6-13
6-17
6-19
6-22
6-23
6-25
6-27
6-28
7-1
7-3
7- 3
7-4
7-5
7- 5
7-11
7-11
7-12
SEP '95
8 Layer Setup ................................................................ 8-1
8.1
8.2
8.3
8.4
Personality Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Selecting and Loading Protocols ........ . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
The Protocol Configuration Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Saving the Layer Setup Screen. . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . . . . . . ..
8- 3
8-3
8-4
8-5
9 FEB Setup ................................................................. 9-1
9.1
ill
Buffering Idle, Control Leads, Ticks, and Timestamps. . . . . . . . . . . . . . . . . . . 9-3
BCC and BERT
10 Block Checking ............................................................ 10-1
10.1
10.2
10.3
10.4
10.5
10.6
BCC Symbols ........ " ................ , ..................... , . . ..
BCC Conditions .....................•............................
Transmitted BCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Standard BeC Parameters . . .. . . . . . . . . . . . . . . . . . . . . . . . .. . . . .. . . . .. . ..
BCC Setup Menu Fields. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . .
BISYNC vs. Selectable CRC Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
10-3
10-5
10-5
10-6
10-11
10-14
11 Bit Error Rate Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . .. .. . . .. 11-1
11.1
11.2
11.3
11.4
11.5
11.6
11.7
11.8
11.9
11.10
IV
Pseudorandom Bit Patterns .........................................
Test Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
BERT Operation: Full Duplex ......................................
BERf Operation: Half Duplex. . . . .. .. . . . . . . .. . . .. . .. . . . . .. . . . . . . . ..
BERT Setup Screen ...............................................
1hmsrnission Format: Line Setup Menu ..............................
Run Mode: Keyboard Control ......................................
Run Mode: Status line ............................................
Run Mode: Statistical Display. . . .. . .. . .. .. . . ... .. .. .. . . . . .. . . . .. . . ..
Loopback atthe TransmittingINTERVrEW .. ........ ...... .... .... ...
11-3
11-4
11-4
11-6
11-7
11-14
11-17
11-18
11-19
11-21
Interfaces
12
Standard Interfaces ............ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 12-1
13
Optional Interfaces ................... ,...................................
V
13-1
File System .d Miscellaneous Utilities
14
SEP'95
DiskMaintenance........................................................
14-1
14.1
14.2
14.3
14.4
14-3
14-3
14-3
14-4
The Disks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
AllooatingDisk Space ............... ..................... ... .......
Data Acquisition Thtcks vs. the Filing System ........... " . ... ... ... . ..
The Disk Maintenance Screen. . . . . . . . .. . . .. . . . . . . . . .. . . . . . . . . . . . . . ..
vii
15
File Management. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
15.1
15.2
15.3
16
Loading and Saving Files .............................. " . .. .... . ... 15-3
Orienting Yourself in the Filing System ............................... 15-4
The File Maintenance Screen ....................................... 15-9
Printer Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
16.1
The Connector ........................... '" ....... .. .. . . ..... . ...
16.2
16.3
16.4
16.5
16.6
16.7
Configuring the Printer Setup Screen . . . . . . . . . . .. . . . . . . .. . . . . . .. . . . . ..
Saving the Printer Setup. . . . . . . .. .. . . . . . . . . . . . . . .. . .. . . . . . . . . .. . . ...
How to Print Static Displays ........................................
How to Print Data .................................................
Spreadsheet Control of Printing .....................................
PrintingDiskFiles .................................................
16-1
16-3
16-3
16-7
16-8
16-10
16-17
16-17
17
TheTune-of-DayClock.................................................
17-1
18
Color Display " ........................................................ "
18-1
18.1
18.2
18.3
19
20
Connectors for External Monitors ................................... 18-3
Color Control from the Miscellaneous Utilities Screen .................. 18-3
18-6
Black and White Data Enhancements
Easy View Setup .........................................................
19-1
19.1
19.2
19.3
19.4
19.5
19.6
19-3
19-4
19-4
19-4
19-5
19-5
Enable Easy View .............................................. ,...
Enter Easy View After Power-Up ...................................
Keep Easy View Menu Information in Memory ........................
Display Program Warning Messages. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . ..
Load Program Edit Timeout ........................................
Screen Saver Timeout ........ , . . .. . . . .. . . . ... ..... ... . .. . . . .. .. . ...
Easy View Maintenance ................................................... 20-1
20.1
20.2
20.3
20.4
20.5
20.6
20.7
viii
15-1
The Easy View Menu File ..........................................
Accessing the Maintenance Program .................................
Automatic Installation .............................................
Customizing Programs .............................................
Script File Format ............................................... "
Creating a Text (Help) File .........................................
Easy View Directory Structure ......................................
20-3
20-4
20-5
20-6
20- 20
20-33
20-34
SEP '95
VI
Statistics
21
22
VII
Thbular Statistics
21-1
21.1
21.2
21.3
21.4
21.5
21.6
21-3
21-4
21-6
21-7
21-9
21-11
Counters and Timers ..............................................
Preparing the Ta.bular Statistics Screen . .. . . . .. . . .. .. . . . . . . . .. .. . . . . . ..
Sampling Current Values ...........................................
Accumulators......................................... ............
Keeping a Statistical Log ...................•...•...................
The Sampling Action as Divisor .....................................
Graphic Statistics ......................................•................ "
22-1
22.1
22.2
22.3
22 - 3
22-4
22-4
Enabling the Grapbic Display .......................................
Cursor Movement on Graphical Statistics Menu. . . . . . . . . . . . . . . . . . . . . . ..
Menu Fields. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Programming Concepts: Tiers and Layers
23
24
VIII
Three-TIered Programming ........... . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
23-1
23.1
23.2
23.3
23.4
nigger Setup Screens. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
The Protocol Spreadsheet ..........................................
C Programming Language ..........................................
Integrating Programming Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
23-2
23-3
23-4
23-4
The Layered Program Model ..............................................
24-1
24.1
24.2
24.3
24.4
24.5
24.6
24-3
24-3
24-4
24-7
24-8
24-8
States. . . . . . . . . . . . .. .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . ..
Tests ....... " ............................. '" ................ , "
Layers and the OSI Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Personality Packages. .. . .. . . .. . . . . .. .. . . . . . .. .. . . . .. . . . .. . . . . . .. ...
Primitives ...................................................... "
Constants ...................................................... "
liigger Menus
25
Trigger Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
25-1
25.1
25.2
25.3
25.4
25.5
25-4
25-4
25-5
25-9
25-9
Active Triggers ............................... '" .......... ... . . ...
Combining Conditions on the Same Trigger Setup Screen .............. "
Receiver. . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
EIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
TImeout.... .....................................................
SEP'95
-----_._-----_ ..
ix
----------------------
_-------_ ...__._---------_.
25.6
25.7
25.8
25.9
25.10
26
IX
Displaying a Prompt ..................................... " ....... ,
Transmitting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . • .• . . . . . . . . . . . . . . . . . . . . ..
Internal Flags. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Enhancing the Display .............................................
Controlling Timeouts ..............................................
Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
TImers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . ..
Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Capture of Data in the Screen Buffer. . . .. . . . . .. . . . . . .. . . . .. . . .. . .. . ..
26-3
26-4
26-6
26-7
26-8
26-8
26-10
26-11
26-11
The Trigger Summary Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 27 -1
Protocol Spreadsheet
28
Programming Blocks ..................................................... . 28-1
28.1
28.2
28.3
28.4
28.5
28.6
29
30
Before You Begin a Spreadsheet Program ............................ .
Creating a Spreadsheet Program .................................... .
Program Structure ................................................ .
Compiled Spreadsheet ............................................ .
Configuring the SizeINumber ofIL Buffers ........................... .
Comments in a Spreadsheet Program ................................ .
28-3
28-3
28-6
28-10
28-13
28-14
Constants .............................................................. . 29-1
29.1
29.2
29.3
29.4
29.5
29.6
29.7
Definition of Constants ........................................... .
Constant Names ................................................. .
Scope .......................................................... .
Referencing Constants ............................................ .
Nested Constants ................................................ .
Precedence ...................................................... .
Expansion ....................................................... .
29-3
29-4
29-4
29-5
29-6
29-6
29-7
Editor ................................................................. . 30-1
30.1
30.2
x
25-10
25-10
25 -11
25-11
25-12
Trigger Actions .......................................................... , 26 - 1
26.1
26.2
26.3
26.4
26.5
26.6
26.7
26.8
26.9
27
Transmission Complete ............................................
Internal Flag Bits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Buffer Full .......................................................
Counter. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Keyboard.................... .....................•..............
Basic Editing Functions ........................................... . 30-3
Editing Function Keys ............................................ . 30-5
SEP'95
..
,""'......,
"
31
Layer-Independent Conditions and Actions. . . . . . . . . . . . .. . . . . . . . . . .. . . . . . . . .. 31-1
31.1
31.2
31.3
31.4
32
33
Naming Requirements .............................................
Rules for Combining Conditions .................................... ,
Layer-IndependentCOnditions.....................................
Layet-IndependentActions ........................................
31-1
31-2
31-3
31-8
Layer 1 Conditions and Actions. .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
32-1
32.1
32.2
32.3
32.4
32-1
32-6
32-8
32-17
Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 33-1
33.1
33.2
X
Single-Port Layer 1 Conditions .....................................
Dual .... Port Layer 1 Conditions ......................................
Single-Port Layer 1 Actions ............... , ...... ..... .......... . ..
Dual-Port Layer 1 Actions.............. .............. .............
Strings 1b Be Matched Against tine Data ............ . . . . . . . . . . . . . . . . . 33-3
Strings To Be Transmitted .......................................... 33-3
OSI Primitives
34
OSI Primitives on the Protocol Spreadsheet .................................. , 34-1
34.1
34.2
34.3
35
Softkey Selections ................................................. 34-4
Sample Primitives: CONNECT INDs and CONNECf REQs ............ 34-7
Sample Primitives: DATA INDs and DATA REQs .. . . . . . . . . . . . . . . . . . . .. 34-9
Automatic OSI Primitives . . . . .. . . . .. .. . . . . . . . . . . . . . . . . . .. . .. .. . . . . . . . .. . . .. 35-1
Protocol Packages
Xl
36
X.21 Layer 1 ............. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36-1
36
X.21 Layer 1 .............. , '" ..... , .................................. '"
36-3
36.1
36-4
36.2
36.3
36.4
36.5
37
X.21 bis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
'fiansmitter/Receiver Phases ........................................
SendIDg From Layer 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
)(,21 Conditions. . . .. . .. .......... . ... ... . . ......... . . .. . ... . .. . ...
X.21'Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
36-4
36-5
36-5
36-7
X.25 Layer 2 ............................................................. 37-1
37.1
37.2
37.3
37.4
Frame-Level Setup. .. . .... .. ....................... ..............
Protocol Trace. . . . .. . . . ..... ........ ... . . .... ... ... .. .. . ... ... . . ..
Monitor Conditions ................................................
EmUlate - Mode Conditions . . . . . . . .. . . . . . .. . . .. . . . . . .. . . . . . . . . . . . ...
SEP '95
37-3
37-5
37-11
37 -15
xi
...
_•......•_ _... _-------_._--------------------.....
37.5
37.6
37.7
37.8
37.9
38
38.4
38.5
38.6
38.7
38.8
40.3
Frame-Level Setup ................. , . ... ....... ... ..... . .... .....
Protocol Trace ....................................................
Monitor Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Emulate-Mode Conditions............................... ..........
Emulate Actions ..................................................
Display Actions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . .. ..
Automatic Primitives ..............................................
39-3
39-6
39-12
39-17
39 - 22
39-32
39-34
Frame-Level Setup ................................. , .. ..... ...... 40-3
SDLC Conditions and Actions ..................................... " 40-4
Protocol Trace .................................................... 40-4
DDCMP Layer 1 ......................................................... 41-1
41.1
41.2
Outsync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 41-1
Block Checking ................................................... 41-1
42
ISDN D Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
43
LAPD.................. .. ....... ........ . ..... ... .. ......... . .......... 43-1
43.1
43.2
43.3
43.4
43.5
43.6
43.7
xii
38-3
38-8
38 -15
38 - 24
38 - 29
38-42
38-44
38-45
SNA.................... ...... .................................. ........ 40-1
40.1
40.2
41
Packet-Level Setup........ .................................. .....
Protocol Trace ....................................................
Monitor Conditions. . . . . . . .. .. . .. . . . .. . . . . . . . . . . . . . . . . . . . . . .. .. . ...
Emulate - Mode Conditions. . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . ..
Emulate Actions ..................................................
Display Actions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Automatic Primitives ..............................................
Programming Example: Forcing Data Packets Out on the Line . . . . . . . . . ..
SDLC .................................................................. 39-1
39.1
39.2
39.3
39.4
39.5
39.6
39.7
40
37-21
37 - 32
37-33
37 - 35
37-36
X.25 Layer 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • .. 38-1
38.1
38.2
38.3
39
Emulate Actions ..................................................
Display Actions ...................................................
Automatic Primitives ..............................................
Programming Example: Converting Protocol Bytes to Hexadecimal .......
Programming Example: A Simple '~utomatic" Layer 2 X.25 Test . . . . . . . . .
Frame-Level Setup...............................................
Protocol Trace .....................................................
Monitor Conditions. . .. . .. . . .. . . .. . . . . . . . . . . .. . . . . . . . . . . . .. . . .. . ...
Emulate-Mode Conditions .........................................
Emulate Actions ..................................................
Display Actions..... ....... ..... .......... .............. ..........
AutomaticPrimitives........ ...... .............. ........ .... ......
42-1
43-3
43-5
43-9
43-14
43-19
43-29
43-31
SEP '95
44
0.931 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 44-1
44.1
44.2
44.3
45
SS#7 'Layer 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 45-1
45.1
45.2
45.3
45.4
46
SS#7 Run-Time Displays ........................................ "
Setup tor SS#7 ...................................................
SS#7 Compression at Layer 1 .......................................
SS#7 Suppression at Layer 1 ...................................... "
45-3
45-3
45-4
45-5
SS#7 Layer 2 ,. . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
46 - 1
46.1
46.2
46.3
46.4
46.5
46.6
47
Protocol Trace .................................................... 44-3
Monitor Conditions. . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 44-9
Display Actions ................. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 44-12
Set Up for SS#7 ..................................................
Protoqol'Irace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Monitor Conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Displ~y Actions ...................................................
SS#7 Emulation ..................................................
SS#7 Frame Structures and Values. .. . .. .. .. . . . . . .. .. . . . . . . .. . . . .. ...
46-3
46-3
46-7
46-10
46-11
46-11
SS#7Layer3 ............................................................ 47-1
47.1
47.2
47.3
47.4
47.5
Packet-Level Setup...............................................
Protocol Trace ....................................................
Monitor Conditions .......................... ............ ..........
Display Actions. ....................... ...........................
StructUre ofSS#7Message Signal Units.......... ....... .............
47-3
47-4
47-7
47-11
47 ... 12
48
SMDS ................................................................ "
48 ... 1
49
ATM ................................................................. "
49-1
49.1
49.2
49.3
49.4
49.5
49.6
49.7
49-1
49-1
49-4
49-8
49 ... 14
49-17
49-18
xn
Recording ATM over TIlE1 Data with the INTERVIEW ................
Oveniiew. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
AAL 1 Protocol ................................................. "
AAL :3/4 Protocol .................................................
AAL 5 Protocol ................................................. "
Operations and Maintenance (OAM) Cells. . .. . . . . . . .. .. . . .. .. .. .. . . ..
ATM'Framing: HECandPLCP .....................................
Index
Index A: Part I of the Technical Manual .......................................
SEP'95
Index A-I
xiii
xiv
SEP'95
Part n: Advanced Programming
xm
so
Theory of Operation
Data Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . . . . . . . . .. 50-1
50.1
50.2
51
ProgramMain ........................................................... 51-1
51.1
51.2
5l.3
52
52-1
52 - 2
52-7
52-13
52-14
Example of Event: fevar_time_oCday ........................ ........ 53-1
vari~ Origins of waitfor Events .................................... 53 - 2
Programming Considerations ....................................... 53-3
Receiving and Transmitting Data. .. .. . . . . . . . . . . . . . . . . . . .. .. .. . . . . . . . . . . . . ... 54-1
54.1
54.2
54.3
54.4
54.5
54.6
54.7
XIV
Layer and Test. . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . ..
State. Enter State, and Next State .. . . . . . . . . . . . . . . . . . .. . . . .. . . . . .. . . ..
Conditions and Actions ............................................
Example of Complete C Program ....................................
SummaryofC Regions.................... ....... .............. ....
Events. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 53-1
53.1
53.2
53.3
54
Translating a Simple Test into C ..................................... 51-1
A Minimum of One Softkey State. . . . . . . . . . . . . . .. . . . . . .. .. . . . . . . . . . .. 51-2
Writing the Test Entirely in C . . . . . . .. .. . . . . . . . . . . . . . . . . . . . .. . . . . . . . .. 51-3
Regions in Spreadsheet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 52-1
52.1
52.2
52.3
52.4
52.5
53
Two'!YpesofCPU ................................................. 50-3
Front~End Buffer ................................................ 50-5
Locating Data in an IL Buffer .. . .. . . .. . . . . . . . . . . . . .. . .. . . . . . .. . . ....
Monitor Path vs. Receive Path .. . .. . . . . . .. . . . . . . .. . . .. . . . . . .. . .. . . . ..
Passipg a Buffer Upwards. .. . .. . . . . . .. . . . . . . . .. .. . .. . .. . . . . . . . . . . . ..
Layer 1 Transmit ..................................................
Passing a Buffer Between Thsks ..................... " ...... .........
Sample Transmit Program: Sync or Async Echo ........................
Sample Transmit Program: BOP Echo ................................
54-1
54-3
54-3
54-4
54-7
54-9
54-10
C Language
55 C Basics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 55-1
55.1
55.2
Notable Variations in C ............................................ 55-3
Editmg a C Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . .. 55-4
SEP '95
--_.._----------------------
55.3
55.4
55.5
55.6
55.7
55.8
56
56.3
56.4
56.5
56.6
56.7
56.8
56.9
56.10
56.11
56.12
56.13
56-1
56-2
56- 3
56-4
56-7
56-8
56-10
56-11
56-12
56-12
56-14
56-15
56-16
Declarations ..................................................... ,
Arguments ...................................................... ,
Returns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
User-Defined Routines......................... ....... ............
Example Routines... . ... . ... . . .. .. .. ... .. .. . .. . . .. . .. .......... . ..
57-1
57-1
57-2
57-3
57-4
CLibrary
58
Monitorrrransmit Line Data
58.1
58.2
58.3
59
60
58-1
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 58-1
Variables ...... , ., ............................................... , 58-2
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58-7
EIA............ ...... ... .... .............................. ..... ........ 59-1
59.1
59.2
Variables....... .......... .................... ................ .... 59-1
Routines.................. ............. .. .. ........ .... .......... 59-3
Display Window and Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 60-1
60.1
60.2
60.3
xvi
Creating or Accessing C Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Declaring Variables . . . . . . .. . . . . . .. . . . . .. . . . .. .. . . . . . . . . . . . . . . . . . . ..
Comparing a Variable to a Value . . . . . . . .. . . . . .. . . . . . . . . . . . . .. . . . . . . ..
Checking a Variable in a waitfor Clause ...... . . . . . . . . . . . . . . . . . . . . . . . ..
Checking and Displaying Equivalent Values of a Variable . . . . . . . . . . . . . . ..
Isolating Bits from a Variable Value ..................................
Pointing to an Address .............................................
Creating a Character Pointer ........................... , . . .. . . . . . ...
Pointing with Subscripts ............................................
Creating a String ....... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Comparing Strings ................................................ ,
Accessing a Variable Inside a Structure ...............................
Creating a Structure Pointer ........................................
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 57-1
57.1
57.2
57.3
57.4
57.5
xv
55-4
55-5
55-13
55 -17
55-19
55-22
Variables. . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . .. 56-1
56.1
56.2
57
Error Reporting in C .............................................. ,
Preprocessor Directives ............................................
Data Types .......................................................
Operator Precedence ..............................................
Strings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Recommended Sources ............................................
Current Display Mode ............................................. 60-1
Softkey Display ....................................... ;........... 60-3
PromptUne ...................................................... 60-5
SEP'95
60.4
60.5
60.6
60.7
61
63
62-1
62.1
62.2
62.3
62- 3
62 -13
62-37
65.1
UnitConfiguration ..... . . .. . . . .. . . . . . . .. . .. . . . . . .. .. . .. . . . . .. . . . .. 65-1
Current Display Mode .............................................
65-1
Remote Port :I/O ......................................................... 66-1
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 66-1
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 66- 2
Routines ........................................................ , 66-4
AUX Port I/O ........................................................... , 67-1
67.1
SEP'96
65-1
65.2
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
67-3
67-5
Other Library Tools ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
68-1
68.1
68.2
68.3
68-1
68-3
68-8
67.2
68
64-1
Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64-1
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 64-3
Status
66.1
66.2
66.3
67
63-1
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63-1
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63- 3
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63-4
Disk I/O ................................................................
64.1
64.2
66
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Variables ..................................................... ',,' . .
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Print ....... '. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
63.2
63.3
65
Counters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61-1
Timers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 61-8
Accumulators. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 61-12
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 61-14
OSI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
63.1
64
60-5
60-31
60-41
60-47
Counters, TiIners, and Accumulators ........................................ 61-1
61.1
61.2
61.3
61.4
62
Display Window .................................................. ,
Program and User'fraces ........ " .. ........... ....... ..... .. ......
Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protok::ol Trace Buffers .............................................
Structures ....................................................... ,
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
xvii
Protocol Library
XVI
69
X.21l:ibrary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 69-1
69.1
69.2
69.3
70
X.25 Layer 2 Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 70-1
70.1
70.2
70.3
71
Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 74-1
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 74-1
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 74-1
75-1
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . ... 75-2
Variables ....................................... , . . . . . . . . . . . . . . . .. 75-2
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 75-6
LAPD Library ...........................................................
76.1
76.2
76.3
xviii
Structures............... ..... . ..................... .............. 73-1
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 73-1
Routines ........... , .. '" .... ..... ... ... ....... . .. . ... ...... . . . .. 73-5
Secondary Channel Library ................................................
75.1
75.2
75.3
76
Structures .......... , ................................ " . ... ... . ... 72-1
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 72-1
Routines ..................................................... , ... 72-10
DDCMP Library ......................................................... 74-1
74.1
74.2
74.3
75
72-1
SNA Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 73-1
73.1
73.2
73.3
74
Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71-1
Variables ....................................................... " 71-1
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 71-10
SDLC Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
72.1
72.2
72.3
73
Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 70-1
Variables ....................................................... " 70-1
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70-9
X.25 Layer 3 Library ................. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 71-1
71.1
71.2
71.3
72
Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 69-1
Variables...... . . . .. .. . .... ........ ...... . ...... ..... .. . .. . . .. . ... 69-2
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 69-4
76-1
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76-1
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 76-1
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 76-9
SEP '95
77
Q.931 Library ............................................................ 77-1
77.1
77.2
773
78
SS#7 Layer 2 Library ..................................................... 78-1
78.1
78.2
78.3
78.4
79
80.3
80.4
SO.5
81.11
Sample Mode .................................................... ,
Discarding Frames ................................................
Layer 1 Primitives for High-Speed Frame Capture Mode.... ...........
Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Routines .......................................... " ............ ,
80-1
80-1
80-2
80-2
80-3
Vari3ibles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
ISDN SffIU Structures .. . . .. .. .. . .. .. . . . . . . . . . .. . . . .. . . . .. . .. . . .. ..
ISDN SffIU Routines. . . .. ... .. . . . . . . . . . .. . .. .. .. . ... . . . . . . . . .. . ...
ISDN Structures .............................•....................
ISDN Routines ...................................................
Dual;... Port T1 Structures .......................................... ,
Dual-PortTl Routines............................................
Dual;""Port G.703 Structures. . . . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . . . . ..
Dual-Port G.703 Routines .........................................
Dual-PortDS-OAStructures ......................................
Dual-PortDS-OARoutines .......................................
81-1
81-1
81-2
81-15
81-15
81-15
81-15
81-15
81-15
81-16
81-16
SMDS Library ........................................................... 82-1
82.1
82.2
82.3
SEP '95
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 79-1
Variaples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • . . . . . . . . . . . . . . . . .. 79-1
Routines.. .. ........... . .. .. . . ... . .... .... ..... . ............ ..... 79-7
TIM -Specific Library. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 81-1
81.1
81.2
81.3
81.4
81.5
81.6
81.7
81.8
81.9
81.10
82
78-1
78-1
78 - 5
78-5
High-Speed Frame Mode Ltbrary .......................................... SO-I
SO. 1
80.2
81
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .• . . . . . . . . . . ..
Variables. . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . • . . . . . • . . . . . . . . . . . . . . . . . ..
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
SS#7'Layer 1 ..... . . . . . . . . . . . . . . . . . . . . . . . . . . .• . . . . . . . . . . . . . . . . . . ..
SS#7 Layer 3 Library ..................................................... 79-1
79.1
79.2
79.3
80
Structures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77-1
Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 77 -1
Routines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 77 - 5
Structures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82-1
Varil1bles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 82 - 3
Routines .................................................... , . ... 82-4
xix
83
KfMLibrary............................................................
83.1
83.2
83.3
83-1
Structures ................•................. " . . . . . . . . . . . . . . . . . . .. 83-1
Variables ..................................... " . .... .•..... .. . ... 83-3
Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 83-5
Appendixes
Appendix A: Operator Messages
Appendix AI:
Appendix A2:
Appendix A3:
Appendix A4:
A-I
Interactive Messages ....................................... .
Easy View Messages ....................................... .
Error Messages Issued by C Translator ......•..................
Error Messages Issued by C Compiler ......................... .
Al-1
A2-1
A3-1
A4-1
Appendix B: Glossal)' of Acronyms, Abbreviations and Mnemonics ...................
B-1
Appendix C: Selectable Data Speeds ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
C-l
Appendix D: Code Charts ...................................................... D-1
Appendix 01:
Appendix02:
Appendix 03:
Appendix D4:
Keyboard-to-Hex Translation.............. .................
Hex-to-OisplayTranslation.................................
User-Defined Codes .......................................
Keyboard - to-PC Conversion ...............................
D1-1
D2-1
03-1
D4-1
Appendix E: Interface Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
E-1
Appendix F: Packing and Shipping Instructions ....................................
F-l
Appendix G: Communications with Telenex .......................................
G-l
Appendix H: Field Service on the INTERVIEW 8000 Series .........................
H -1
Appendix HI:
Appendix H2:
Appendix H3:
Appendix H4:
Appendix H5:
Eliminating Static Electricity .................................
Removing Logic Boards .....................................
Installing Logic Boards .... . . . .. . . .. . . . . . . . .. .. .. . . . .. . . . .. ..
Logic Board Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enabling Automatic Reboot .• , . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Hl-1
H2-1
H3-1
H4-1
H5-1
AppendixI: Rack Mount (OPT-951-98-1) ...................................... I-I
Appendix J: C Language Summary. .. . . .. . .. . . . . . . .. .. . . . . . .. . . .. . .. . . . .. . . . . . ...
J-l
Index
xx
Index B: Technical Manua1 Part I and Part II
Index B-1
Index C: C Structures, Variables, and Routines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Index C-l
SEP '95
List of Tables
Thble 1-1
Standard Customer-Selectable Test Interface Modules .. , ...•.............. 1-13
Table 2·1
Fields That Can Be Changed Without Causing Recompile ..•...•.....•...... 2-17
Table 3-1
Frequently Used Programming Keys ..................................... 3-4
Table 5-1
Synchronization Parameters for Standard Codes ........•.................. 5-9
Table 6-1
Special Display Symbols ...............•.•............•................. 6-14
Table 7-1
SCSI Drive Recording ................................................. 7-5
Table 7-2
RAM Size (qytes) for Normal and High-Speed Recording in the
INTERVIEW8000TURBOSeriesUnits ............................... 7-9
Table 10-2
Standard Block -Check Parameters for Sync or Async/lso¢ Formats ........... 10-7
Block Check Polynomials ............................................... 10-7
Table 10-3
BCC Setup Menu Fields ..............................•................ 10-12
Table 11-1
Full- or Half- Duplex BERT (RS-232/V.24 Interface Control screen) ........ 11-7
Table 11-2
BERT Pattern (BERT Setup screen) ..................................... 11-8
Table 11-3
Half-Duplex BERT: Default Synchronization Points ....................... 11-13
Table 11A
Sync or Asyric BERT (Une Setup screen) ................................. 11-17
Table 13-1
Optional Test Interface Modules ........................................ 13-1
Table 15-1
File Types ........................................•................... 15 -12
Table 16-1
Character Representations on Menu Screen Printouts ....... : .............. 16-7
Table 16-2
Character Representations on Data Printouts .............................. 16-10
Table 27-1
Abbreviatio~, Trigger Summary Conditions
Table 27-2
Abbreviations, Trigger Summary Actions .................................. 27-5
Table 33-1
Valid Entries in Receive Strings ......................................... 33-2
Table 33-2
Valid Entries in Transmit Strings ......................................... 33-6
Table 34-1
Primitive PrefIXes and Associated Layers .................................. 34-4
Table 34-2
OSI Service Primitives ................................................. 34-11
'Thble 37-1
Default Parameters in SEND Actions .................................... 37-23
Table 37-2
Automatic ~tives Generated at X.25 Layer 2 ........................... 37 - 34
Table 38-1
Automatic p;rimitives Generated at X.25 Layer 3 ........................... 38-44
Table 39-1
Automatic Primitives Generated at Layer 2 SDLC .......................... 39-35
Table 40-1
Fields in SNA Trace Display ............................................ 40-8
Table 43-1
Automatic P,rimitives Generated in LAPD ................................ 43-31
Table4()..1
LSSU Sta~ Field (Bits 2-0 of first Status Field Octet) ..................... 46-5
Table 47-1
MSU Serviqe Indicators (Bits 3-0 of the SIO) ............................. 47-17
Table 47-2
Network Management Headers (Octet 9 for CCITT Format;
Octet 12 for ANSI - US Format) ..................•.................... 47 -18
Table 10-1
SEP'95
....................•.......... 27-4
xxi
Table 47-3
SCCP Message Headers (Octet 9 for CCITI International or National Format;
Octet 12 for ANSI-US Format) ....................................... 47-19
Table 47-4
Telephone User Part (TUP) Message Headers ............................ .47 - 20
Table 47-5
ISUP Message Headers .................•................... . .......... 47 - 22
Thble 49-1
Table 49-2
Pre-defined Header Field Values ....................................... 49-13
Payload Type Indicator Encoding ............................•........... 49-13
Table 55-1
Table 55-2
Data Types: Ranges of Values Displayed and Printed ....................... 55 -16
Operator Precedence! ................................................. 55-18
Table 55-3
C String Nonliterals ................................................... 55 - 21
Table 58-1
Table 58-2
Transmit Structures ....•..................................•............ 58-1
Monitorffransmit Variables ............................................. 58-3
Table 58-3
Character Buffer 16-Bit Word ......................... , ................ 58-18
EIA Variables ........................................................ 59-2
Table 59-1
Table 60-1
Table 60-2
Table 60-3
Table 60-4
Table 60-5
Table 60-6
Table 60-7
Current Display Variables .............................................. 60-2
Display Window Variables .............................................. 60-6
Display Window Buffer Structures ....................................... 60-9
Display Windowrrrace Buffer 32..;.. Bit Data Word .......................... 60-15
Special Graphic Character Set .......................................... 60-18
Trace Buffer Structures ................................................ 60-32
Conversion Specifiers ................. , ................................ 60-46
Table 61-1
Protocol Trace Buffer Variables .................•.. , ..............•..... 60-48
Protocol Trace Buffer Structures ...... " ..•.............................. 60-50
Counter Structures .........................•••....... , ................ 61-2
Table 61-2
Table 61-3
Table 61-4
Counter Variables ..................................................... 61-3
Counter, Timer, and Accumulator Structures .............................. 61-5
Timer Structures ...................................................... 61-9
Table 61-5
Table 61-6
Timer Variables ............................................ ,: .......... 61-10
Accumulator Structures ................................................ 61-14
Table 62-1
OSI Structures ........................................................ 62-9
Table 62-2
Layer 1 OSI Variables ................................................. 62-14
Table 62-3
Table 62-4
Layer 2 OSI Variables ................................................. 62-15
Layer 3 OSI Variables ..................................•.............. 62-19
Table 62-5
Table 62.;.6
Table 62-7
Layer 4 OSI Variables ................................................. 62 - 23
Layer 5 OSI Variables ................
62 - 27
Layer 6 OSI Variables ................................................. 62-31
Table 62-8
Layer 7 OS1 Variables ................................................. 62 - 35
Print Structures ....................................................... 63 - 2
Table 60-8
Table 60-9
Table 63-1
Table 65-1
xxii
0<
...............................
Status Structures ...................................................... 65 - 2
SEP '95
Table 66-1
Remote Port I/O Variables ............................................. 66-3
AUX Port 110 Variables .....................................•.......... 67-4
Table 67-1
Table 68-1
Table 68-2
Other Ubrary Variables ..............................•............•.... 68-4
Table 69-1
X.21 Structures ...................................•......•............ 69-1
Table 69-2
Table 7()..1
Table 7()"2
X.21 Variables ...........................•............................ 69 - 3
X.25 Layer tStructures .........................•...................... 70-2
X.25 Layer 2 Variables ....•....................•.........•............. 70-3
X,25 Layer 3; Structures .............................•.................. 71-2
Table 71-1
Table 71-2
Table 72-1
Table 72-2
Table 73-1
Table 74-1
Jahle 75-1
Table 75-2
Table 76-1
Table 76-2
Table 77-1
Table 78-1
Table 78-2
Table 79-1
Table 80-1
Table 81-1
Table 81-2
Table 81-3
Table 82-1
Table 82-2
Table 83-1
Table 83-2
Structure Fie:lds--Other Ubrary Tools .................................... 68-2
X.25Layer 3, Variables .....................•....................•...... 71-3
SOLC Structures . . . . . . . . • . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 - 2
SDLC Variables ....................................•..•.............. 72 - 4
SNA Variabl~[ ......................................•.•......•....... 73-2
ODCMP Variables .................................•.................. 74-2
Secondary Cp,annel Structures .......................................... 75-2
Secondary Channel Variables[ ........................................... 75 - 3
IAPD Structures ..................................................... 76-2
IAPD Variables ...................................................... 76 - 3
0.931 Variables ....................................................... 77 - 2
SS#7 Layer 2 Variables ................................................ 78-2
SS#7 Layer 1 Variables[ ................................................ 78-6
SS#7 Layer:3 Variables .................................•.............. 79-2
High-Speed Frame Capture Variables ................................... 80-2
ISDN Srr/lJStructures ................................................ 81-1
U - Interface Message 1.Ype/Data Decodes
for NT and LT State/SUl:tus Symbols ................ ~ .........•......... 81-8
srr- Interface Message Type/D_ta pecodes
for TE and NT StatelStatus Symbols .................................... 81-8
SMOS SNl Structures ................................................. 82 - 1
SMDS SNI Variables .................................................. 82 - 3
ATM UNI Structures .................................................. 83-1
ATM UNI Variables ................................................... 83-4
Table Dl-1
TableDl-2
Numbered Error Messages Returned for C Coding{ ........................ A4-1
Une Setup Clock Speeds ............................................... C-5
Keyboard-to-EBCDIC ............................................... D1-2
Keyboard-lo-ASCII ................................................. 01-3
Table D1-3
Table D1-4
Keyboard-to-EBCD ......................•.......................... D1-4
Keyboard-to-XS-3(SYN;:::35;EOM-55) ... , .......................... D1-5
TableA4-1
Table C-2
SEP'95
xxiii
Table Dl-5
Table D1-6
Table D1-7
Table D1-S
Table DI-9
Table DI-I0
Table D1-11
TableD2-1
Table D3-1
Table 04-1
TableE-1
TableE-2
Table E-3
TableE-4
TabieE-5
TableE-6
Table E-7
TableE-S
TableE-9
'Thble E-lO
TableE-ll
Table E-12
TableE-13
TableE-14
Table E-15
Table E-16
TableE-17
TableE-18
TableE-19
TableE-20
TableE-21
Table E-22
TableE-23
TableE-24
TableE-25
Table H3-1
xxiv
Keyboard-to-IPARS ................................................. Dl-6
Keyboard-to-REVERSEEBCD ....................................... Dl-7
Keyboard-to-SELECTRIC ..................•........................ D1-8
Keyboard-to-BAUDOT .............................................. D1-9
Keyboard-to-JIS7 .....................................•............. D1-10
Keyboard-to-JISS (space parity) ....................................... Dl-12
Keyboard -to-JISS (mark parity) ....................................... Dl-13
Hex-to-DisplayTranslation ........................................... D2-2
Code-Set Characters .................................................. D3-4
Keyboard-to-PCConversion .......................................... 04-2
Remote Connector .................................................... E-2
Printer Connector ..................................................... E-3
Auxiliary Connector ........................................ " ..... , ... E-4
RGB Monitor ........................................................ E-5
RS-232N.24 Test Interface Module ..................................... E-7
V.35 Test Interface Module ............................................. E-9
X.2I Test Interface Module ............................................. E-ll
RS-485 Test Interface Module .......................................... E-13
RS-449N.36N.37 Test Interface Module ................................. E-15
ISDN Test Interface Specifications ....................................... E -17
ISDN srrIU Test Interface Specifications ................................. E-19
T1 Test Interface Specifications ......................................... E-21
Dual-Port T1 Test Interface Specifications ............................... E-23
G.703 Test Interface Specifications ....................................... E-25
Dual-Port G.703 Test Interface Specifications ..................... " ...... E-27
DS-OA 56KJ64K Dual-Port Test Interface Specifications ................... E - 29
G.703/64K Co - Directional Dual-Port Testlnterface Specifications .......... E - 31
TIL Test Interface Module ............................................. E - 33
EIA-530 (DB-25) to EIA-449 (DC-37) Pin Comparison ................. E-35
V.35 Test Interface Connector Specifications (Dual-Port Mode) ............. E - 36
V.35 Test Interface Connector Specifications (Single-Port Mode) ............ E-37
EIA-530 lest Interface Module (Dual-Port Mode) ....................... E-38
EIA-530 Test Interface Module (Single-Port Mode) ...................... E-39
EIA - 232 Dual- Port Test Interface
Connector Specifications (Dual-Port Mode) ............................ E-40
EIA - 232 Dual-Port Test Interface
Connector Specifications (Single-Port Mode) ........................... E-41
Sl-Switch Settings for MPM Boards in the INTERVIEW 8000 Series ......... H3-2
SEP '95
Part I
Basic Op.eration
._ _ _ _ _
. _ _ _ _ _ _ _. _.. w_._
1 Hardware
1 Hardware
SEP '95
1-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 1-1 INTERVIEW 8800 TURBO.
1-2
SEP '95
1 Hardware
1 Hardware
Telenex Corporation offers five basic INTERVIEW 8000 Series units, each with several specific
variations. Table 1-1 describes the multiplexer board andlor Test Interface Module selections
available as standard for each unit.
•
INTERVIEW 8100 TURBO - one MPM (single-port TIMs only; no ISDN)
INTERVIEW 8100-F TURBO - designed specifically for sing;le-port Frame Relay testing
•
INTERVIEW 8200 TURBO - one MPM
INTERVIEW 8200R TURBO - a remote version
INTERVIEW 8200-B TURBO - designed specifically for ISDN Basic Rate testing
•
INTERVIEW 8600 TURBO - two MPMs
INTERVIEW 8600R TURBO - a remote version
INTERVIEW 8600- P TURBO - designed specifically for ISDN Primary Rate testing
INTERVIEW 8600- I TURBO - designed specifically for both ISDN Basic Rate testing
and ISDN Primary Rate testing
•
INTERVIEW 8700 TURBO - three MPMs
INTERVIEW 8700R TURBO - a remote version
INTERVIEW 8700-SS7 TURBO - designed specifically for SS7 testing
INTERVIEW 8750 ATM EXPRESS* - designed only for ATM (Broadband) testing
•
INTERVIEW 8800 TURBO - four MPMs
INTERVIEW 8800R TURBO - a remote version
INTERVIEW 8800- FR TURBO - designed specifically for Frame Relay and SMDS testing
INTERVIEW 8800-GSM TURBO - designed specifically for GSM and SS7 testing
INTERVIEW 8800- MTS TURBO - designed specifically for multiple -protocol testing
INTERVIEW 8800 PLUS ATM* - designed specificaUy for multiple-protocol testing,
including ATM (Broadband)
* The INTERVIEW ATM units are described in the INTERVIEW1J 8800 PLUS ATM Technical
Manual, Asynchronous Transfer Mode (Broadband).
NOTE: AR offers extended and expedited Maintenance Agreement
plans for INTERVIEW 8000 Series hardware. Call Customer Service for
more information.
SEP '95
1-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
1.1
Physical Dimensions
The protocol analyzers in the INTERVIEW 8000 Series, represented by the INTERVIEW
8800 TURBO in Figure 1-1, measure 7 inches high by 14 inches wide by 18.5 inches deep
(178 mm high by 356 mm wide by 470 mm deep). The unit weighs approximately 32
pounds (14.5 kilograms).
1.2
Keyboard
With the exception of R -Series TURBO units, the INTERVIEW has a 94- key keyboard
containing ASCII keys and special keys separated into pads according to function. The
keyboard is described in detail in Section 3.
The R - Series TURBO units do not come equipped with a keyboard since these remote
units are controlled via a PC keyboard. The PC-to-INTERVIEW keyboard conversion
is contained in Appendix D4 and in the documentation that accompanies the remote
software (available as OPT-951-82-1-X, OPT-951-83-1-X, orOPT-951-248-1).
1.3
Front Panel
(A) Remote INTERVIEWs
The front panels of the R -Series TURBOs have a HARD DISK indicator on the left
that is red when there is activity on the hard disk.
There is also a single floppy-disk drive in the Drive 1 slot and indicator LED. See
Section 1.4 for more information on floppy drives.
There is no display nor keyboard on R - Series TURBO units. As the remote unit
functions, the appropriate screens appear on the display of the controlling Pc. An
optional keyboard may be ordered (OPT-951-153-1) and a CGAmonitor
connected to use with the remote unit, if desired.
(8) Electroluminescent (EL) Display
The INTERVIEW's flat electroluminescent (EL) display screen measures 3.85 inches
high by 7.69 inches wide (97.8 mm high by 193.3 mrn wide). The high-resolution
display (512 X 256 pixels) is black and yellow. No brightness adjustment is required
for the EL display.
The screen has 21 display lines, 16 of which are devoted to data display. Data is
displayed in lines 64 characters long, making the capacity of the screen 1344
characters (of which 1024 characters are devoted to line data). The top 2 lines of the
data screen are devoted to status information; the bottom 3 lines to function key
identification (see Figure 1-2).
1-4
SEP '95
1 Hardware
BL~ .. eeOOe
I~~f;§~t£/BOP
Status
Display Area
~
5 0fV26/8S!
--l
-
••
DA!FI
SlATS
NO DISP
"
/""
Softkey Labels
Figure 1·2 INTERVIEW display screen.
(C) Function Keys
Eight function keys and the 8 key are located directly below the display screen. The
uses of the function keys vary from program menu to program menu; however, their
function is always defined on the screen in rectangular windows located above the keys.
(Refer to Section 3 for a discussion of their use.)
(0) LED's
Twenty LED's are placed above the display screen. These LED's are divided into
three banks: interface status LED's, INTERVIEW status LED's, and theU/A LED.
Figure 1-3 shows the assignment of LED's for an RS- 232 interface.
PAIMAAY
RS-2321V24
INTERFACE
RTS CTS
TO
105
103
CO
RD
DSR OTR SCT SCR
SCTE
104
'07 106.2 114
113
• • • 109
• • • • • • •
106
115
RI
sa
SECONDARY
SRTS SCTS $TO
INTERVIEW
seD SRO
•• • • • • •
125 '10
120
121
118
122
119
REMOTE FREEZE
• •
UlA
•
Fagure 1·3 There are 20 LED'~ divided by function, above the EL display.
1.
Interface status indicators. Interface status indicators may be assigned to different
signals, depending on the Test Interface Module which is installed in the rear
panel. An overlay accompanies each module and should be placed over the front
panel LED's whenever the module is installed. Assignment of each of the front
panel indicators is illustrated in Appendix E, which also gives the interface
specifications for each Test Interface Module.
Primary and Secondary indicators on the front panel glow red to indicate that the
lead is on (space Voltage) and green to indicate that the lead is off (mark
voltage). The eye recognizes orange when the leads are transitioning very
rapidly. UIA lead indicators on Test Interface Modules operate differently. See
Section l.S(F).
SEP '95
1-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
2.
INTERVlEWstatus indicators. There are three status indicators: REMOlE,
FREEZE, and UIA. The REMOTE indicator is red when the INTERVIEW is
under remote control. The FREEZE indicator is red when the display screen has
been frozen (with the ~ key) while in Run mode. Both REMOlE and
FREEZE LED's are dark when off.
3.
U/A LED. The last indicator, UtA, is user-assigned and may be programmed to
track any lead of the operator's choosing. See the RS- 232 TIM documentation
for the use of the UA-inputjack in RS-232/Y.24 testing.
(E) The Test Interface Overlay
Each Test Interface Module is accompanied by a front panel overlay. The overlay is
placed over the interface status LED's and identifies the lead tracked by that LED
when that particular Test Interface Module is installed. The overlay masks out any
unused LED's. Replace the overlay each time that you change the Test Interface
Module.
1.4
Disk Drives
(A) Floppy Disk Drives
The INlERVIEW uses 3.5 inch double-sided, high-density microfloppy diskettes (see
Figure 1-4). Each formatted microfloppy has a storage capacity of 1.4 Mbytes.
Each disk has a write-protect window (see Figure 1-4). To write-protect a disk,
slide the window open so that you can see through the disk.
If a high -density disk has been used on another piece of equipment which has a
1-Mbyte drive, it must be reformatted before it is used on the INlERVIEW. The
data it contains cannot be read.
Disks from the INTERVIEW 5/10/15 PLUS Series can be read by units in the
INlERVIEW 8000 Series when they have been properly formatted. Preparation of
these disks and their use in the INTERVIEW is described in Section 14.
Like the remote 8000 Series TURBO units, the 8100 TURBO has one 3.5 inch
microfloppy disk drive in the Drive 1 slot; the other 8000 TURBO Series units have
two 3.5 inch microfloppy disk drives immediately to the right of the display screen.
An LED just to the right of each drive is lit to indicate that the microfloppy in the
drive is being accessed. Insert disks in the direction shown in Figure 1-5.
To remove a disk, press in the black bar next to the drive containing the disk.
CAUTION: Never remove a disk from its drive when the LED indicates that
the disk is being accessed.
1-6
SEP '95
1 Hardware
D
o
High density
indicator ""'hole
~
roo
Figure 1-4 The INTERVIEW uses 3.5 inch quad- or high-density, double-sided microfloppy diskettes.
Figure 1·5 The INTERVIEW is equipped with two micro-floppy disk drives, except for the 8100 TURBO and
R - Series TURBO units which bave a single floppy drive; an 240- Mbyte SCSI hard disk is standard in all the 8000
TURBO Series units.
(8) Hard Disk Drive
All units in the INTERVIEW series are equipped with an 240- Mbyte SCSI hard disk
drive. When the hard disk is being accessed, the indicator light on the left lower side
of the front panel is lit.
Since the hard disk cannot be write-protected, you may wish to save its contents to
microfloppy backup disks on a regular basis.
SEP '95
1-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
o
o
·0
i
,
i
,
•
•
•I
o
,
,
,
•
,i·
POWER
il
[TIM goes here]
i
.j
j
~
.6
o
ODD
6(&:;;:;;:_
REMOTE RS-232
PRINTER
AUXIUARY
~@>
CRT!R:S
0
RS-170
Figure 1-6 Back panel and connectors.
1.5
Back Panel
The back panel and its various connectors are shown in Figure 1-6.
(A) Power Module
The power connector is located at the bottom left of the rear panel. It is a standard
three-wire grounded male connector, with selectable voltage.
(8) Voltage Selection and Fuse Replacement
Read the following information and instructions for the original INTERVIEW 8000
Series units or for the new ATM/ATM -ready INTERVIEWs.
1.
Original INTERVIEW 8000 Series units. Original INTERVIEW 8000 Series units
are designed to operate at 95 to 130 Volts ac when 115 V is selected or from 190
to 260 Volts ac when 230 V is selected. To determine the voltage currently
selected in original INTERVIEW 8000 Series units, slide the transparent window
of the power connector module to the left (see Figure 1-7). You will see the line
voltage selector card at the bottom of the window. Current voltage selection is
visible-and right side up.
To change the line voltage selection, swing the fuse extractor handle (labeled
FUSE PULL) out toward the left, and remove the fuse. The voltage selector
card can then be removed and turned so the correct line voltage can be read right
side up in the window. When the voltage selector card has been seated correctly,
rotate the fuse extractor handle to the right and in, and replace the 4 amp fuse.
1-8
SEP '95
1 Hardware
Figure 1·7 For original INTERVIEWs, voltage is selectable in the power connector module with a
voltage card; in newer, ATM - ready INTERVIEWs, the required voltage is sensed and selected
automatically, with no voltage card required.
Included in your shipment is a detachable power-supply cord with a NEMA
5 -15 attachment plug rated 15 A, 125 V. If you configure the unit for 220-240
V operation, you should employ a UL-listed power-supply cord set furnished
with a grounding plug suitable for connection to the 220-240 V source of supply.
The unit will operate the display at either 50 or 60 Hz refresh rate. It defaults to
60 Hz unless a file named /syslfifty_hertz is listed on the boot-drive disk. If a file
with this name is created, the unit will operate at 50 Hz. (The content of the file
is irrelevant and will be ignored by the boot -up software.)
2. ATM -ready INTERVIEWs. ATM and ATM -ready INTERVIEWs are designed
to operate anywhere in the range from 95 to 260 Volts ac. These units do not
require a voltage selection card; the power supply in these units senses and
selects the correct voltage. However, for information on changing the 5 amp fuse
in the ATM and ATM-ready INTERVIEWs, refer to Figure 1-7 and subsection
1., above, and follow the same instructions as for changing the old 4 amp fuse.
Note there is no voltage card present in the new models.
As before, a file named /syslfifty_hertz should be listed on the boot-drive disk if
the unit is to be operated at 50 Hz, as described in subsection 1., above.
SEP'95
1-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(C) On/Off Switch
The power switch is located above the power connector and to the right. Press the
side of the switch marked "1" to turn power on. Press the side marked "0" to turn
power off.
(D) The Fan
The INTERVIEW is cooled by a fan which may be accessed through the rear panel.
A fan filter prevents dust and dirt from getting into the INTERVIEW. Ai; the filter
gets dirty, less cooling air gets to the unit. To prevent your INTERVIEW from
overheating, we recommend that you periodically clean the filter. A plastic grill on
the rear of the unit covers the fan filter.
CAUTION: Do not insert objects through the grill covering the fan. Do not
remove the grill without turning off the unit and disconnecting power.
Turn the INTERVIEW off, disconnect the power, and remove the screws holding the
grill in position. Remove the filter, rinse it in clean water, dry it thoroughly, and
replace it. Screw the grill back on the the unit.
If your INTERVIEW is overheating and cleaning the filter does not alleviate the
problem, contact Customer Service.
(E) Connectors
The following is a brief description of all I/O connectors on the rear panel of the
INTERVIEW. Interface specifications for each of the connectors are given in
AppendixE.
1-10
1.
Handset connector. The ISDN Handset Connector is just below the power switch.
It is a standard RJ -11 C connector. This interface is intended for an optional
ISDN handset.
2.
Remote RS-232 connector. This is an RS-232N.24 25-pin connector located
just to the right of the power connector. It provides access to an external modem
(or directly to another INTERVIEW unit).
3.
Printer connector. The RS-232/Y.24 25-pin printer connector is located directly
to the right of the Remote connector. It allows access to most serial printers.
The connector acts as DCE and transmits on RD. Printer operations are
described in Section 16.
SEP '95
1 Hardware
4. Auxiliary connector. The Auxiliary I/O connector is a 16-bit bidirectional TIL
connector which allows access to external peripheral devices. Use the C routines
discussed in Section 67 to control and monitor this interface. Other references to
AUX leads in this manual pertain to the four AUX pins on the RS- 232 TIM
(see Figure E-1).
CAUTION: Never plug an RS-2321Jl24 cable into the Auxiliary connector, as
the signal voltage is likely to damage the interface.
5.
CRT/RGB connector. This is the color video connector. Signals from the
INTERVIEW display can be passed through this connector to a color monitor to
produce color graphics and other displays in color. Color, vertical sync,
horizontal sync, and intensity signals can be controlled from the external monitor.
Use of color in displays is described in Section 18.
6.
Composite video connector. This connector provides RS-170 video output to an
emernal monitor or camera.
SEP '95
1-11
------
---
----------------------------------------
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
Figure 1-8 The right rear panel accommodates interchangeable Test Interface Modules.
(F) The Test Interface Module
The empty receptacle to the right of the rear panel (see Figure 1-6) accommodates
interchangeable Test Interface Modules (TIM's). Whenever the INTERVIEW
monitors a data line or emulates a DTE or DeE, the correct TIM must be installed.
At least one customer-selectable interface is standard with any unit in the
INTERVIEW series; see Table 1-1 for selections. Other test interfaces are available
as options; see Section 13. Most Test Interface Modules are equipped with two
connectors, a TO DTE and a TO DeE connector, with the dual-port series available
with connectors for each port. Figure 1-8 shows a single-port RS-232 module being
1-12
SEP '95
1 Hardware
inserted into the unit. Connect to the data line as descnbed in Section 1.10. The
interface softkey (@ on the Setup Menu) will reflect the type of TIM installed, such
as RS232, \l.as, RS449. RC8245, TTL, etc.
CAUTION: To connect the data line, you must interrupt the flow of data on the
line. Be sure you have permission to break the line before doing so.
Telenex Corporation's DATA -PATCHIP systems and AUTONEX matrix switch
systems often provide non -intrusive access methods for monitoring the line.
NOTE: It is possible to monitor data previously recorded on disk, whether or
not any TIM or the correct TIM is installed.
Table 1-1
Standard Customer-Selectable Test Interface Modules
MUXChoice
Compatible TIM Choice
INTERVIEW 8100
Not applicable
Single-Port EIA-232
Single-Port v.as
Not applicable
INTERVIEW 8100-F
Not applicable
Single-Port E1A-232
Single- Port V.as
Not applicable
INTERVIEW 8200
Not applicable
Single-Port EIA-232
Sihgle- Port V.as
Not applicable
INTERVIEW 8200R
Not applicable
Single-Port EIA-232
Single- Port V.3S
Not applicable
Not applicable
Single-Port EIA-232
Single- Port v.as
Not applicable
INTERVIEW 8000
Not applicable
Single-Port EIA-232
Single- Port v.as
Not applicable
INTERVIEW 8600R
Not applicable
Single-Port EIA-232
Single-Port V.as
INTERVIEW SSOO-P
OIJal-PortT1 (238+0)
DuaI-PortG.703 (308+0)
either
Oual-PortT1 (238+0)
Dual-Port G.703 (308+0)
Oual- Port T1 (23B+ D)
Dual-Port G.703 (3OB+0)
either
Oual-PortT1 (238+0)
Dual-Port G.703 (30B+O)
INTERVIEW 8700
Not applicable
Single-Port EIA-232
Single- Port V.35
Not applicable
INTERVIEW 8700R
Not applicable
Single-Port EIA-232
Single- Port V.as
Not applicable
Unit
INTERVIEW 82OO-B
INTERVIEW 8600-1
1
1
1
Additional TIM Choice
Single-Port EIA-232
Single-Port \l.as
Single-Port EIA-232
Single- Port V.SS
Also equipped with ISDN smu Test Interface Module and MUX board as standard equipment.
SEP '95
1-13
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Table 1-1 (continued)
Standard Customer-Selectable Test Interface Modules
Unit
MUXChoice
INTERVIEW 8700-SS7
Dual-Port T1 (23B+O)
Dual-Port G.703 (308+0)
either
Compatible TIM Choice
Additional TIM Choice
Dual-Port T1 (238+ D)
Dual-Port DS-OA
Dual-Port G.703 (308+D)
Dual-Port G.703/64Kbps
Co- Directional
Dual-Port V.35!
EIA-530(449)/E1A-232
Not applicable
INTERVIEW 8800
Not applicable
Single-Port EIA-232
Single-Port V.35
Not applicable
INTERVIEW saOOR
Not applicable
Single-Port EIA-232
Single-Port V.35
Not applicable
INTERVIEW saoo-FR
Dual-PortT1 (238+0)
Dual-Port G.703 (308+D)
either
Dual-PortT1 (238+0)
Dual-Port G.703 (308+0)
Dual-Port V.35!
EIA-530(449)/EIA-232
Single-Port EIA-232
Single-Port EIA-449
Single-Port V.35
Not applicable
INTERVIEW 88oo-GSM
Dual-PortT1 (238+0)
Dual-Port T1 (238+0)
Dual-Port DS-OA
Dual-Port G.703 (308+0)
Dual- Port G.703!64Kbps
Co- Directional
Dual-Port V.351
EIA-530(449)!EIA-232
Not applicable
Dual-Port G.703 (30B+D)
either
INTERVIEW 88OO-MTS
Dual-Port 11 (23B+D)
Dual-Port G.703 (308+D)
either
INTERVIEW 8800 PLUS ATM Dual-Port 11 (238+0)
Dual-Port G.703 (308+0)
either
Dual-Port DS-OA
Dual-Port G.703164Kbps
Co-Directional
Standard with unit: Dual-Port V.35!
EIA-530(449)/EIA-232
ISDN S/TIU TIM with MUX
Dual-Port T1 (23B+D)
Dual-Port G.703 (308+0)
Dual-Port T1 (238+0)
Dual-Port G.703 (308+0)
Dual- Port V.3S!
EIA-530(449)/EIA-232
Not applicable
NOTE: The INTERVIEW 8750 ATM EXPRESS does not test WAN protocols and so does not have any Test Interlace Modules.
1.
Software control of TIM connectors. When Mode:
or
is
the program selection. the INTERVIEW passively monitors data through either
(or both) TO connectors on the Test Interface Module.
When the INTERVIEW is operating in ';!ili~'J§~; or
modes,
the TO DTE connector is active. The INTERVIEW is transmitting and receiving
1-14
SEP '95
1 Hardware
data through the TO DTE connectof. When Mode: i;f'~ili~{j~~ (Of
:i;:;~§~_ff;~iii ) is the program selection, the INTERVIEW transmits and receives
data through the TO DeE connector. The interface specifications for each Test
Interface Module are given in Appendix E.
Break-out switches on each Test Interface allow any pin to be patched. See the
RS-232 TIM documentation for an explanation of the RS- 232 breakout
switches.
2.
Test interface LED's. There are four LED's on Test Interface Modules which do
not require a MUX board. Tho,labeled EMUlATE DTE and EMUlATE
DCE, indicate the operating mode of the unit. When EMUlATE DCE is red,
the TO DTE connector is active; when EMUlATE DTE is red, the TO DCE
connector is active. When the INTERVIEW is monitoring or auto-monitoring,
both EMUlATE LED's are black.
The two LED's above the UIA input on the patch panel track the voltage level on
the lead patched to U/A. The red LED above the UIA panel is lit to indicate
space voltage (positive voltage above a minimum threshold). When the green
LED above this panel is lit, it indicates a mark voltage (negative voltage within a
specified acceptable range). For intermediate voltages, the VIA LED's are off
(see Figure 1-9).
CAUTION: Power off the INTERVIEW before installing or removing a TIM.
Remember to change the front panel overlay each time that you change the TIM.
UlALED,
Rear Panel
Front-Panel LED's
+
DRIVER
+
RECEIVER
0---
DRIVER
G
R
E
E
N
Figure 1-9 Color phases in green-red LEOs.
1-15
SEP '95
-----------------~---~--
INTERVIEW 8000 Serles 8asic Operation: 951-80424-01
1.6
Storage Capacity
(A) RAM
RAM capacity for line data in the screen buffer is 64 Kbytes-a maximum of 32
Kbytes of characters plus 32 Kbytes of attributes for character data. EIA leads and
time ticks are stored in RAM with the characters, if these options were selected on
the Front-End Buffer menu (see Section 9.1). Each byte devoted to EIA leads and
time ticks reduces the number available for characters. Bit-image RAM is 256
Kbytes in the 8100 TURBO and 8200 TURBO Series units and 1 Mbyte in the 8600
TURBO Series, 8700R TURBO Series, and 8800 TURBO Series units. (Bit-image
RAM may be increased. See Section 7.5.)
(8) Microfloppy Diskettes
Each diskette has a 1.4 Mbyte storage capacity (formatted); thus, total diskette
capacity is 2.8 Mbytes for the INTERVIEW 8200 TURBO, 8600 TURBO, 8700
TURBO, and 8800 TURBO units, and 1.4 Mbytes for the INTERVIEW 8100 TURBO
unit with its single floppy disk drive. (An optional floppy disk drive will increase
storage capacity (formatted) to 2.8 Mbytes for the INTERVIEW 8100 TURBO unit.)
(C) Hard Disk Drive
The hard disk drive has a storage capacity of 240 Mbytes in all
INTERVIEW 8000 Series units with 240 Mbyte SCSI drives and 1.2 Gbytes in those
units equipped with the optional 1.2 Gbyte SCSI drive.
(0) Maximum Data Rates
Maximum rates for data recording are as follows:
- Recording to bit-image RAM
(full-duplex, 100% line use):
2.048 Mbits per second
- Bit-image recording to 80- Mbyte hard disk
(full-duplex, 100% line use):
768 Kbits per second
- Bit-image recording to 240-Mbyte SCSI or optional1.2-Gbyte SCSI hard disk
(full-duplex, 100% line use):
2.048 Mbits per second
- Recording to microfloppy
(full-duplex, 100% line use):
64 Kbits per second
The speed your INTERVIEW actually achieves may vary. Factors which will
influence data - analysis rates are line speed, percentage of line utilization, average
frame length, the layer packages and user program loaded, suppression of idle, and
the time-stamp resolution. Refer to Sections 2.9 and 2.10 on how to optimize the
INTERVIEW's speed of operation.
1-16
SEP '95
1 Hardware
1.7
Clock
Data clocking is provided by a set of high -frequency crystals. The various data speeds
that can be selected are listed in Appendix C.
The INTERVIEW is also equipped with a time-of-day clock which provides readings of
time (hours, minutes. seconds), day, month, and year. Time may be used as an
INTERVIEW program condition. Refer to Section 17 for instructions on setting the
time-of-day clock. Refer to Sections 25 and 31 for a description of Time as a program
condition.
1.8
Operating Environment
The INTERVIEW is designed to operate in an atmospheric temperature ranging from 41
to 122 degrees Fahrenheit (5 to 50 degrees Celsius). At these temperatures, the unit can
operate in (uncondensed) humidity ranging from 30 to 90 percent.
NOTE: Operation at extreme temperatures require the fan filter be clean.
See Section 1.5(D).
CAUTION: Avoid dropping the unit.
Avoid getting the unit wet.
Do not operate the unit with the fan covered.
Avoid operating the unit immediately after exposure to drastic changes in
temperature and humidity.
Avoid placing the INTERVIEW on a radiator or near a source ofheat.
SEP '95
1-17
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Figure 1-10 The INTERVIEW may be operated on a desk top or in a standing position.
1.9
Operating Positions
The INTERVIEW is designed to operate on a desktop (Figure 1-1) or in a standing
position, with the display facing upwards (Figure 1-10). The unit may also be
shelf-mounted in an equipment rack or cabinet. Allow for adequate air flow when
mounting the INTERVIEW in a rack.
CAUTION: To protect the hard disk, do not move the unit with the power on.
Tum the power offfirst to position the hard disk in a protected state. However, do
not tum the power offwhen the disk-access LEDs are on.
1-18
SEP '95
1 Hardware
1.10 Power Up
Before you power up the INTERVIEW, make sure you have performed the preliminary
steps listed below.
(A) Install the Test Interface Module
Check the rear panel to be certain that you are using the correct Test Interface
Module before you test any data. A Test Interface Module is shown in Figure 1-8 and
descnbed in Section 1.5(F).
CAUTION: Never install or remove a TIM unless the INTERVIEW is powered
off
Remove the Test Interface Module by pressing the button to the left of the module
with the thumb of your left hand. Hold the button in as you pull firmly on the TIM
handle with the thumb and forefinger of your right hand.
Install the Test Interface Module right-side-up in the receptacle provided at the
right of the rear panel. Press firmly on the top and bottom of the module until it is
secured and the button to the left clicks into place.
(B) Insert the Correct TIM Overlay
Be certain that the overlay over the front-panel LED's matches the Test Interface
Module installed.
To remove the overlay, grasp the top and bottom edges with the thumb and forefinger
of both hands and bow the strip slightly in the center. The overlay should slip out.
To insert an overlay, bow it slightly. Insert the tabs on either side of the overlay into
the notches on each side of the LED panel. Make sure that the holes on the
underside of the overlay are placed over the small posts at the top of the empty LED
panel, and press the overlay into place.
(C) Connect to a Data Source
It is not necessary to install a Test Interface Module or connect to a data line if you
are reviewing data stored on disk.
If you plan to test a data line, connect to the line as described below.
CAUTION' You must interrupt the flow of data when you connect to a data line.
Be sure you have permission to break the line before doing so.
Break the data line for testing. For single-port testing, connect one end of the line
to the TO DTE connector on the Test Interface installed in the rear panel; connect
the other end ofthe line to the TO DCE connector on the TIM. For dual-port
SEP '95
1-19
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
testing, DTE and DeE are on the same connector for each port; connect each port
on the TIM to the respective line to be tested. Even when the INTERVIEW is
powered off, this provides a through connection for the data line.
An LED next to the connector will be lit if the INTERVIEW is actively testing-or is
programmed to test-on that connector.
Refer to Section 1.5(F) for a description of TIM connector functions.
Check the voltage selection on the card in the small window on the rear panel.
If the voltage is incorrect, refer to Section l.S(B) for instructions.
(D) Open the Keyboard
Place the INTERVIEW on a stable surface. Support the back of the keyboard with
one hand. Unlatch the keyboard by pushing the blue latches on the top of the unit all
the way back. Then lower the keyboard to operating position.
(E) Power On
Connect the female end of the power cord provided to the back of the unit; connect
the other end to a standard power outlet. Depress the side of the power switch
marked "1." A Start Up screen similar to that in Figure 2-1 should appear. Refer to
Section 2 for a discussion of the Start-Up screen, system initialization, and general
operations.
1-20
SEP '95
2 General Operation
2
General Operation
This section discusses the general operation of the INTERVIEW and covers such topics as
updating system software, configuring the menus, starting and stopping a test program,
locating errors detected when the test is compiled. using both the preexistent trigger setup
menus and the free-form spreadsheet to create test programs, and using the
INTERVIEW's analysis features.
For a hands-on introduction to the INTERVIEW, see 30 Minutes to Programming the
INTERVIEW 8000 Series, 951-00431-01.
2.1
Power Up
As you power up the INTERVIEW, perform the preliminary steps listed below. The
procedures for each step are described in Section 1, Hardware.
•
Install the Test Interface Module.
•
Select the correct voltage.
•
Open the keyboard.
•
Insert the proper TIM overlay.
•
Install the initialization disk if you are not booting from hard disk.
•
Connect the power cord and tum power on.
•
Connect to a data source.
(A) Self Tests
When you turn on the unit, you initiate a series of self tests: first, the CPM Module
DRAM, then the MPM Module DRAM, and finally, the MPM to CPM connections.
Any self-test errors will be reported on this screen. Refer to the Appendices for an
explanation of error messages. You may abort the self tests by pressing 8.
(However, we recommend that you allow the tests to run their course.)
Once the self test cycle is complete or once you have aborted the tests, the
INTERVIEW begins to initialize its software. The message BOOTING appears on the
screen. The default drive at power- up is the disk from which the system loads
initialization software. The INTERVIEW first checks FD1, then FD2, and finally,
HRD. As soon as it detects system software, it stops the search and boots up.
SEP'95
2-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
NOTE: You can reset the INTERVIEW directly from the keyboard. Press
the ~-8-~ or ~-8-~ key combination to force the
INTERVIEW to perform the self-test and booting sequences without turning
the unit off. This reset is similar to that of a PC in that it is not a hardware
reset. For hardware resets, you must power the unit off and then back on.
When self tests are complete, a Start Up screen similar to that in Figure 2-1 will
appear. Notice that when you powered on, all the following information appears on
this screen: the types of disk drives installed, the number and types of processors in
your unit, the software and firmware versions, the options installed, the Test Interface
Module in place, and the optional TIM crystal installed (if any).
**
INTERVIEW 8700 TURBO
**
DISKS:
PROCESSORS:
I
(1:58010-8;3:80286-12.5)
SELF-TEST ERRORS:
l1li
Press:
[PROGRAM] to enter the menu page
[RUN]
to run the default program
Software Version: 12.00
Firmware Version: 8.02
OPTIONS: Mux
TIM: RS-232/V.24
TIM CRYSTAL: 6144000
Cop~right (c) 1987, 1995
Telenex Cor oration
Figure 2·1 Power-up screen, INTERVIEW 8700 TURBO.
2-2
SEP '95
2 General Operation
(B) File Searches
During power-up, the INTERVIEW searches specific directories for the files
described below.
1.
print_setup. During boot- up, the /sys directory on the boot drive is searched for
the file print_setup. If it exists, the configured Printer Setup in this file is
8"Utomatically loaded. Otherwise, the INTERVIEW loads the default Printer
Setup. See Section 16.3.
2.
userjntrf. If you have a file named user_intrf in the /usr directory on the hard
disk, the program in user_intrfwill be compiled and run as soon as boot-up is
complete, bypassing the Start Up screen as shown above. See Section 2.2(A).
3. default. The Start Up screen will appear only briefly if you have a file named
default in the /usr directory of your boot-up disk. If you do not press 8 within
five seconds of power-up, the program in default will be compiled and run. See
Section 2.2(B).
4.
ezview jetup. During boot-up, the INTERVIEW tries to locate the file
ezview_setup in the /sys directory on the boot-up disk. The INTERVIEW's Easy
View operation is configured according to the parameter settings in this file. See
Section 19. If the file is not located, the INTERVIEW is configured with all
default
selections on the Easy View Setup menu. If this menu shows the
selection Enter Easy View After Power-Up: ~_(, and neither user_intrf nor default is
located, the Start Up screen appears for five seconds. Then, the first menu in the
Easy View system is displayed. See Section 4. (If userj11.trf or default is located,
the unit does not enter Easy View following boot-up regardless of the setting of
this parameter.)
mi
2.2
Initializing System Software (Booting Up)
The INTERVIEW 8000 TURBO Series units normally do not require a system disk,
since all initialization software is installed on the hard disk. If you need to install new
system software from a floppy disk, refer to Section 2.3.
NOTE: We recommend that you make a copy of system software to
use as your boot disk. Use the Duplicate Disk command on the Disk
Maintenance screen as explained in Section 14.4(D). Then store your
original floppy in a safe place.
SEP'95
2-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 2-2 Insert microfloppy disks as shown.
(A) Creating a User Interface
Regardless of which disk drive you use for boot-up, FDl, FD2, or HRD, the
HRDlusr directory-and only that directory-is searched during power-up for a file
named userjntif. If the file is located, the unit will automatically load, compile, and
run the program as soon as boot-up is complete. Each time the operator presses
the program in user_intifwil1 be loaded, compiled, and run again. Use this
feature when you want to bypass the INTERVIEW's menus and create your own user
interface for specific applications.
~,
CAUTION: Avoid saving emulation programs in user_intrf Booting up
and automatically mnning an emulation program may result in an
inadvertent break of the line.
To enter Program mode, press ~-8 or ~-~. Perform any Program-mode
operation you wish: make selections on menus, execute File or Disk Maintenance
commands, or create a Protocol Spreadsheet program. To enter Run mode again,
press 8. Each time you execute the S key during Run mode, user_intif will be
loaded, compiled, and run.
To prevent the program in user_intiffrom automatically running upon power-up,
change the name of the file. Simply capitalizing the first letter in the file name
(User_intif) is sufficient If userjntrfis not found during power-up, the S
key
cannot be used to enter Run mode, even if userjntif is saved to the HRDlusr
directory and manually loaded, compiled, and run. Turn off the INTERVIEW and
power up again to activate the user-interface feature.
2-4
SEP '95
2 General OPf!ration
NOTE: References to the 8 key throughout this manual assume
that the user..Jntiffile was not located during power-up. In other
words, the 8 key is used to enter Program mode only.
To create auser_intifprogram:
1.
Configure the menus to the selections you want.
2.
Use Protocol Spreadsheet softkey entries or C regions on the spreadsheet to
develop your user-interface program. All of the C structures, variables, and
routines available to the INTERVIEW user are explained in Part II of this
manual, Advanced Programming.
3.
Press 8 to call up the File Maintenance screen.
4.
Check the hard disk for any existing user-interface program. Press @ for
Select Drive: ~. After Name: type in /usr and then
ptess §). Check for a file named user..Jntrf.
Command: .~~1~!1.
Unless the old file is write-protected, any program already stored under this
filename will be overwritten when you save your new file. To keep the old file for
later reference, save it to a new name (its contents will have to be loaded
manually). For a detailed discussion of file-maintenance commands, see Section
15.
5.
Select Command: ~f&t.~*~.~~~jtt11
select the hard disk.
NOTE: The more complex a program is, the longer it takes to
compile. To eliminate compilation each time you use the 8
key,
therefore, we recommend that you save user..Jntif as an object file.
SEP '95
6.
In the Name: field, type in the filename lusrluser_intrf. Only this name can be
used. (Program or object files saved to any other name or directory must be
loaded manually.)
7.
Execute the SAVE command by pressing~.
8.
user_intrf will appear in the Directory Listings when HRDlusr is the current
directory. (The name of the current disk appears as a prefix to the absolute
pathname of the current directory. The name of the current directory appears on
the fourth line of the File Maintenance screen.)
9.
You may alter the user_intif program again at any time by saving a new program
to the same filename.
2-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(B) Running the Default Program
When the INTERVIEW boots up, the lusr directory on the boot-up disk is searched
for a flle named default. Once the start-up screen (Figure 2-1) appears, the program
in default (if it exists) will be compiled and run automatically after five seconds, or
immediately if you press~. You may prevent the default program from running by
pressing ~ before the five-second timeout expires.
Develop a default program to suit your particular needs. One application of the
default program might be defining a new set of default menu selections.
CAUTION: Avoid saving emulation programs in default Booting up
with a defaUlt emulation program may result in an inadvertent break of
the line.
Upon boot-up, all menu selections in the INTERVIEW are set to certain values.
You may change these default selections if you wish by utilizing the default program.
Follow these steps:
1.
Configure the menus using the default selections you want.
2.
Press S to call up the File Maintenance screen.
3.
Check your disk for any existing default program. Press @) for
• Select the boot disk you want to use. After Name:
type in lusr and then press~. Check for a file named default.
Command:
Unless the old file is write-protected, any set of defaults already stored under
this filename on the disk you have selected will be overwritten when you save
your new default file. To keep the old file for later reference, save it to a new
name (its contents will have to be loaded manually), or use a different disk for
your new defaults. For more assistance, refer to Section 15.
4.
Select Command:
Select Type:
, or
Then select the disk from which the system will be initialized.
5.
In the Name: field, type in the filename lusrldefault. Only this name can be used
as the new set of defaults. (Program files saved to any other name or directory
must be loaded manually.)
6.
Execute the SAVE command by pressing I!§J.
7.
The name of the file you have saved will appear in the Directory Listings when
lusr is the current directory and the selected disk is the current disk. (The name
of the current disk appears as a prefix to the absolute pathname of the current
directory. The name of the current directory appears on the fourth line of the
File Maintenance screen.)
2-6
SEP '95
2 General Operation
8.
You may alter these defaults again at any time by saving a new default program
to the same filename.
9.
Be sure that you initialize the INTERVIEW from the disk which contains default.
The unit will load, compile, and run the default program automatically (unless
you press 8). The Run-mode screen displayed will be the one selected in the
Display Setup menu in default. Likewise, all other menus will reflect your
customized defaults.
Refer to Section 15 for more information on the filing system or flie maintenance
commands.
2.3
Installing New System Software on Hard Disk
From time to time, you may need to install new system software on the hard disk of a
INTERVIEW 8000 TURBO Series unit. Use the Duplicate Disk command from the Disk
Maintenance utility. (See Section 14.4(0) for more information on this command.) The
steps are as follows:
1.
Write -protect the master copies of the new system and user disks. Slide the plastic
tab so that you can see through the rectangular write-protect hole.
NOTE: There should also be a second rectangular hole which does
not have a sliding tab. If you have any 3.5 inch disks which do not
have this second hole, they are not compatible with the INTERVIEW.
2.
Insert the new system floppy disk (DSK-951-00l-1.X) into Floppy Drive 1 G{g),
the left-hand floppy drive.
3.
From the Main Program menu, press the UTlL softkey to bring up the Utility menu,
then D/MAINT for Disk Maintenance. Select the softkey labeled DUPDISK to access the
Duplicate Disk command screen.
NOTE: If you are in Easy View (see Section 4), first press 8, then
§3 to access the Main Program menu.
4.
Select From Disk Number:
and To Disk Number:
on the command screen. Then
The system will prompt you to insert a disk. Since the system disk is
already in PD1, press the !TIl softkey (GOAHEAD). When the duplication is completed,
the system will prompt you again to insert the next disk. Remove the system disk from
PDl and insert the user floppy disk (DSK-951-001-2.x) for duplication. Press !TIl.
press~.
The only files overwritten on the hard drive will be the system software files in the
/sys directory and files from the lusr/layerykgs directory. These files comprise the
new system software.
SEP'95
2-7
------.---------------------------------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
5.
Once copying is comp1ete, take the master copy of the user disk out of Drive 1, and
store it and the master copy of the system disk in a safe place.
NOTE: We recommend that you make a working copy of the new
software on floppy disks which can be kept with the INTERVIEW.
6.
2.4
Turn off the power switch for the unit, and wait ten seconds. Then turn the power on
again to reboot the INTERVIEW. Following the self-test, the unit should boot
without error. The new software version should appear on the screen. If there are
errors or the unit will not reboot, repeat Steps 2 through 6. If problems persist,
contact Customer Service.
Backing Up the Hard Disk
Periodic back-up of the hard disk is strongly recommended.
1.
Install a formatted diskette in Drive 1. This disk should not contain operating system
software. For formatting instructions, see Section 14.4(A).
2.
Go to the File Maintenance screen. (From the Main Program menu, press [§].) Use
the File Maintenance Copy command to copy any files you wish from the hard disk to
floppy.
NOTE: Do not copy files of type SYS or any files from the /sys directory
or the lusrilayerykgs directory to the backup disk. These files reside on
the master copies of your system and user software disks.
3.
Once copying is complete, take the backup disk out of Drive 1 and write -protect it.
Slide the plastic tab so that you can see through the rectangular write-protect hole.
Store the disk in a safe place.
Select from the following methods if you need to recopy files from the backup disk to the
hard disk. Keep in mind that files on the hard disk with the same name as those on the floppy
will be overwritten.
2-8
•
Copy files or directories one at a time using the File Maintenance Copy command.
•
Copy the root directory from the floppy to the root directory of the hard disk. The
name to enter for the root directory-once you have selected the correct origin or
source drive in the rotating field-is simply the slash character, J.
•
Use the Dupdisk command on the Disk Maintenance screen to duplicate the contents
of the backup disk on the hard disk.
SEP '95
2 General Operation
NOTE: Do not recopy files from the /sys directory, files whose type is
SYS, or files from the directory /usr/layerykgs. If you need to reinstall
these files. use the master copies of system and user software disks to
avoid inadvertently overwriting more recent software version mes with
older ones.
2.5
The Menus
The INTERVIEW is used to monitor data as it is received through a data line or to
playback and monitor data as it was recorded from the line. The INTERVIEW may also
be set up to emulate one side of a communication, sending data and responding to the
data it receives. A series of menus are used to set the unit for the data you expect to
receive or send and the type of analysis you wish to perform. These menus are categorized
on the main Program menu. Select one of these menus by using the tIiJ or!Jil key, or by
pressing the labeled softkey. Enter the menu by pressing the highlighted function key or
8·
(A) The Program Menu
Press S
to see the Program menu. Notice that the Software and Firmware
Versions are posted at the top of the screen. They are available to you whenever you
return to this menu.
nu
T~bGS
S
SHT
STATS
LAYER
FMAINT
UTIL
REMOTE
**
tup
reens:
Line Setup
BCC Setup
BERT Setup
Display Setup
Front End Buffer
AIM Setup
Record Setup
Interface Control
Tri9gers - Conditions & Actions
Protocol Spreadsheet
Statistics Results:
Tabular Display
Graphics Display
BERT Results
Layer Setup & Protocol Confi9uration
File Maintenance Functions
Utilities:
Disk Maintenance Time/Date Setup
Printer Setup
Miscellaneous Utilities
Easy View Setup
Remote Control Setup
Figure 2-3 Main Program menu.
Think of the Program menu as the top level for every menu selection. Each time you
prepq.re the INTERVIEW for the communications environment, you will start with
the Program menu and move down into the other menus.
SEP '95
2-9
INTERVIEW 8000 Series Basic Operation: 951-80424-01
All setup, trigger, and programming menus are accessible from this main menu. In
general, use the E3 key from other Program-mode screens or from Run mode to
access this menu.
key.
NOTE: There are two exceptions to this rule about the 8
First, if the file named user_intrf is located in the lusr directory of the
hard disk during power-up, pressing ~ loads, compiles, and runs
the program in userjntrf. See Section 2.2(A). Secondly, if you select
and run a program from an Easy View menu, pressing 8
from Run
mode returns you to the Easy View menu instead of the main
Program menu. See Section 4 on Easy View operation.
(8) Configuring Menus
You may configure menus in any order you wish; however, we suggest you configure
the Layer Setup screen before programming on the Protocol Spreadsheet or the
Display Setup screen, since the selections available to you are governed by the
protocols loaded on the Layer Setup screen.
All options on a particular menu are summarized as a diagram which appears in this
manual at the beginning of the section which covers that menu. Programming options
available in each protocol package are discussed in a section pertinent to the protocol
and layer.
To select a submenu from the main Program menu, use [~! or ~ key, or press the
labeled softkey. Enter the menu by pressing the highlighted function key or ~.
The labels on the screen guide you through each step. For example:
•
Access the Layer Setup screen from the main Program menu by pressing @.
•
Access the Disk Maintenance screen from the main Program menu by pressing
{fil for utilities, then ®J for Disk Maintenance.
Other uses of the function keys are described in Section 3 and in sections pertinent to
the various submenus.
Once you have reached the menu you want, the function keys lead you through
selections, down to the smallest level of detail. You may also use cursor keys ffJ and
(±) to move up and down through the menu fields. 8 and 8 move the cursor across a
menu from field to field.
If you wish to return to the last screen, press ~. Should you wish to review the
menus you have configured, this key takes you back one screen at a time until you
reach the main Program menu. Of course, you may press ~ to start again from the
top of the menus. When you are ready, press 8 to start a testing session, no matter
what menu is displayed.
2-10
SEP '95
2 General Operation
Read Section 3 for a further discussion of these and other keys.
(C) The Setup Menus
Some menus in the setup group (listed at the top of the Program menu) are used to
specify how data is sent, received, recorded, and displayed. If you have an ATM unit
with the ATM hardware (an ACE board and an AIM board in the top enclosure, the
menu allows setting parameters for sending and receiving Asynchronous Transfer
Mode (ATM) data, along with the choice of disabling the WAN protocol data
functions. Sample setup menu softkey selections are shown in Figure 2-4. Note that
BERT (FS) will appear or, if you have an ATM unit, an AIM Interface (F6) will
appear, but these two selections will not appear simultaneously.
Figure z.4 Sample softkey rack on Setup Menu screen for TURBO units: installed Test Interface Module is Dual- Port Y.35.
[Note that either BERT (FS) or an AIM Interface (P6) will appear (see Figure 2-5), but not both. ]
Figure 2·5 Sample softkey rack on Setup Menu screen for PLUS ATM units: installed Test Interface Module is Dual- Port Y.35
and installed ATM Interface Module is AIM 302. (Note that BERf (FS) is neither applicable or accessible.)
1.
Line Setup. The Line Setup screen aUows you to designate the role which the
INTERVIEW is to play in testing-whether it is to monitor passively or
participate in an active dialogue as DTE or DeE. Menu settings also determine
the source of the data and the data clock as well as the characteristics of the data
stream you expect to receive or send. These characteristics include the scheme
for character encoding/decoding and the format in which blocks of data are sent
and received (Le., synchronous, asynchronous, bit-oriented, or isochronous).
The Line Setup screen is described in Section 5.
2. Display Setup. The Display Setup (on the Line Setup screen) provides alternative
types of display to aid in analysis. On this screen, designate how you want data to
appear. (Data may be displayed as a stream of bytes alone or in conjunction with
lead transitions; summarized in a protocol trace or customized trace format; or
tracked on one of two statistical displays.) Then, as you require different types of
analysis, use function keys to change from one type of display to another while
testing, without returning to the menu. The Display Setup screen and the
different types of displays are described in Section 6.
3. Record Setup. The Record Setup (also on the line Setup screen) defines
recording conditions for data acquisition tracks on disk; or for RAM (RAM
SEP'95
2-11
INTERVIEW 8000 Series Basic Operation: 951-80424-01
capacity is 256 Kbytes in the 8100 TURBO and 8200 TURBO; 1 Mbyte in the 8600
TURBO, 8700 TURBO and 8800 TURBO). This screen does not influence the
data stored in the character buffer. Storage of data in the screen's character
buffer can be controlled from the Protocol Spreadsheet using the Capture
command. The Record Setup screen is described in Section 7.
4. FEB Setup. Data and control-lead signals entering the INTERVIEW or
generated internally are routed from the receivers through a front-end buffer
(FEB) before being presented to the screen and to the trigger program. Data
bits are buffered automatically in the FEB. The buffering of other
events--controlleads, idle bits, time ticks, and frame timestamps-can be
enabled or disabled on the Front-End Buffer Setup menu, explained in Section
9. Note that this selection line along with its function key label (see Figure 2-4)
will not appear on the Setup Menu when DISABLE is selected on the line Setup
screen-see Section 5.1.
5.
Interface Control Setup. The Interface Control Setup screen provides
programming selections for Test Interface Modules you have installed. The menu
may differ slightly according to whether @1li._if~?tr* or ~~.:l~; is the
Mode selection on the Line Setup Screen. The menu is specific for the installed
TIM (see Section 12). Note that this selection line along with its function key
label (see Figure 2-4) will not appear on the Setup Menu when DISABLE is
selected on the Line Setup screen-see Section 5.l.
6. Bee Setup.
The BCC Setup Menu controls and displays the values of the
INTERVIEW's block-check parameters. For more information on block
checking, refer to Section 10. Note that this selection line along with its function
key label (see Figure 2-4) will not appear on the Setup Menu when DISABLE is
selected on the Line Setup screen-see Section 5.1.
7.
BERT Setup. The INTERVIEW can transmit and analyze Bit Error Rate Tests
(BERT). Once you have selected the BERT mode on the Line Setup menu,
select appropriate parameters on the BERT Setup menu. Note that this selection
line along with its function key label (see Figure 2-4) will only appear on the
Setup Menu when
or
is selected on the Liine Setup
screen. See Section 5.1 and Section 11.
8. AIM Interface Setup. The AIM Interface Setup screen provides programming
selections for the ATM Interface Module (AIM) you have installed. The menus
may differ slightly according to your selections. See the ATM technical manual.
This selection will not appear if Mode:~;;~,J::' , ::;:r;;;~i'!l.l, or
)!;1il • •~§~;~':)I is selected on the Line Setup screen.
(0) The Trigger Setup Menus
The next three groups of menus, Triggers, Spreadsheet, and Statistics, are
programming menus which you use to establish interactive dialogues, create test
scenarios, and make and display measurements.
2-12
SEP '95
2 General Operation
NOTE: BERT testing is handled separately, on the BERT Setup
screen. See Section 11.
The 16 identical Trigger Setup screens are a limited set of test conditions and actions
grouped in a standard menu format. The set of conditions offered on these screens is
described in Section 25. Trigger Setup actions are described in Section 26. The
Protocol Spreadsheet provides a wider range of conditions and actions which vary,
according to the layer and the protocol you are programming. Conditions and actions
available on the spreadsheet are covered in Sections 31 and 32 and in sections
dedicated to each layer protocol.
Trigger Setup screens and the Protocol Spreadsheet may be used together as
described in Section 23. Counters and timers of the same name may be shared
between the two, as can the flag bits from the Trigger Setup screens, which are
accessed as flags on the spreadsheet under the name trig_flags.
(E) The Protocol Spreadsheet
The Protocol Spreadsheet, a more flexible programming tool with more options than
the Trigger Setup screens, is initially a blank menu. Legal programming options are
presented as function key labels at the bottom of the screen. Create your program by
pressing the necessary function keys. Your entries will be posted on the screen. As
you make entries, the function keys reflect the new options enabled.
You may also type your program directly onto the screen, as long as you observe
syntax and use exact keywords (as they are posted on the screen; not as they are
abbreviated in function key labels.) Programming options and errors will still be
tracked.
Syntax errors are indicated by strike-throughs when you have completed an entry.
(If you are typing onto the spreadsheet, completing an entry usually means pressing
the space bar, pushing (3 or 8, or moving the cursor to a different location.)
1.
SEP '95
The spreadsheet pattern. The Protocol Spreadsheet expects a certain pattern of
entries. To gain access to the set of trigger conditions and actions at each layer,
you must first identify what layer you are programming, then what test you are
developing, and finally the name of the state which will contain the triggers you
create. Once you have named the state, press the function key for CONDITIONS:.
At this point, actual programming options will appear. When you complete the
Conditions portion of a trigger, press 8 and then press the function key for
ACTIONS: to display possible trigger actions. Use the NEXT_STATE: action to
indicate movement to another state. The NEXT_STATE: action must be followed by
a state name. It can move to any state within the test; the NEXT_STATE: NEXT
action moves the test to the following state on the spreadsheet. Programming
concepts related to these selections are described in Sections 23, 24, and 28.
2-13
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Here is an example of the spreadsheet pattern you will see repeatedly:
LAYER: 1
TEST: example
STATE: begin
CONDITIONS: One or more conditions appear here.
ACTIONS: One or more actions appear here.
NEXT_STATE: second
(NEXT STATE will not follow every trigger. Also, it may replace
ACTIONS) -
2. Additional spreadsheet capabilities. Constants may be used on the spreadsheet to
represent repeated values or text, and they may be placed so that they apply to all
or part of a program. Constants are explained in Section 29. C programming
language can be introduced at any location on the spreadsheet to create new
testing conditions and actions and generally increase program flexibility. Cis
introduced in Section 55.
(F) The Statistics Screens
The INTERVIEW has two different statistics menus, one in tabular form, the other
in bar-graph format. Both are accessible by softkey while you are analyzing data.
The value of counters and timers named in triggers can be tracked in statistical
screens, once their names have been entered on the corresponding menus. Current,
last, minimum, maximum, and average values are tabulated. Values for several
counters and timers may be totaled by an accumulator. Bar graphs can be scaled and
color-keyed. Refer to Sections 21 and 22 for information on statistics menus and
displays.
(G) The Layer Setup Screen
Before you program the Protocol Spreadsheet, you are advised to load the protocols
you intend to use. Protocols are selected and loaded from the Layer Setup screen.
Your selections, once loaded, determine the set of program conditions and actions
which appear on the spreadsheet.
With most protocols, a secondary screen loaded with the protocol allows you to
modify common parameters for the protocol.
For more information on the Layer Setup screen, see Section 8.
(H) The File Maintenance Screen
The File Maintenance screen is the user's interface with the filing system. The menu
facilitates saving and loading programs, renaming or deleting files. It allows you to
consult the contents of any directory, create a new directory, and write-enable or
write-protect a file. From this menu, you may structure your own filing system
according to your needs.
2-14
SEP '95
2 General Operation
NOTE: The files pertaining to the operating system and menu selections
are stored primarily in the Isys directory. with some files stored in the
lusr directory. These files should not be deleted or moved. You are
othelWise free to manipulate the filing system as you wish.
Section 15 explains file and directory pathnames. how to set up a file hierarchy, how
to move through the filing system, and how to use the various maintenance
commands.
(I) The Utilities Menus
The last group of menus listed on the Program menu is the Utilities menus, used to
manage peripherals: disk., printer. the internal time-of-day clock, and color
monitor.
The Disk Maintenance menu allows you to allocate disk space for data and programs,
to transfer data from one storage medium to another, and to duplicate the contents
of one disk onto another. Section 14 describes disk maintenance commands and their
use in detail.
The Printer Setup screen allows you to configure the INTERVIEW to control most
serial ASCII printers. The various menu fields are described in Section 16.
Consult the time or modify it on the Time/Date Setup screen. The time and date
which appear here are used in time-stamping data blocks and user files. See Section
17 for details on this screen.
The Miscellaneous Utilities screen provides mapping of black and white to color
enhancements for external monitors. Once the mapping is completed, these
enhancements may be placed under trigger control for the production of highlighted
data. Refer to Section 18 for further information on this screen.
The Easy View Setup screen governs the operation of the Easy View system. Use the
menu selections to: enable Easy View, automatically enter Easy View after
power-up, keep Easy View menu information in memory, and display a warning
message before running programs from Easy View. See Section 19.
(J) Remote Control Setup Menu
The Remote Control Setup menu configures an INTERVIEW to operate as a remote
unit under the control of a Pc. For additional information on remote operation,
consult the accompanying documentation for the remote options:
OPT-9S1-82-1-X
OPT-951-83-1-X
OPT-951-248-1
Remote Control Software
Remote Control Software with OS/2® (Std Edition)
X Window System"" Remote Control Software
NOTE: -X indicates size of floppy disk: -1 is a 3 1/2" diskette and -2 is a 5
1/4" diskette. OS/2 is a registered trademark of IBM and X Window System
is a trademark of Massachusetts Institute of Technology.
2-15
SEP '95
_._----------- ------------
.,.,--_~
..
..
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
2.6
Running a Test Program
Press ~ to compile and execute a test program. As the program is compiled, a message
appears at the top of the screen to indicate the phase that the compiler is in. The longer
and more complex the program, the greater the compile time that is required. The
preparations being made in each phase are briefly outlined below.
(A) Test Preparation
1. Phase 1. Trigger Setup screens are converted to the Protocol Spreadsheet format,
the Protocol Spreadsheet is converted to C, and the C Preprocessor directives are
acted upon.
NOTE: Compilation time is somewhat faster if all triggers are programmed
directly on the Protocol Spreadsheet.
2.
Phase 2. The Program is compiled.
3.
Phase 3. The number of processors and the configuration of the equipment (into
which the program is to be loaded) are determined, and internal packages to
support the user's program are structured. Also during this phase,
linkable-object files referenced on the Protocol Spreadsheet are found and the
compiled code in them combined with the compiled spreadsheet program.
4.
Phase 4. Resources are allocated for each separate task in the program.
5.
Phase 5. The run-time operating system is generated.
6.
Phase 6. All code is linked.
7.
Phase 7. A memory image of the code which can be run by the processors is built.
(8) Rerun Without Recompiling
After a program has compiled once, it will enter Run mode "immediately" (within
two seconds) after ~ is pressed in subsequent executions of the program-assuming
that no substantive changes have been made in the program in between the two runs.
Substantive changes may be defined as those changes made to menus and fields not
listed in Table 2-1. That is, changes to fields covered in Table 2-1 will not necessitate
a recompile and will not prevent the unit from entering Run mode immediately.
Any changes to the Trigger Setup menus or to the Protocol Spreadsheet will be
considered substantive and will necessitate a new compile.
Changes to the tabular or graphic statistics screens will not cause the program to
recompile. However, if a counter or timer is added to the screen, it will not update
until the program is recompiled. You can force a recompile by holding down (§) and
pressing~.
2-16
SEP '95
2 General Operation
Table 2-1
Fields That Can Be Changed Without Causing Recompile
Menu
Line Setup
Reid
Disk No (recorded data must be same type)
Block No
Clock Source
Speed
NAZI
MIL
Display Setup
Display Mode
Type
RTS/CTS?
CD?
DTR/DSR?
Cit? (for X.21 Test Interface Module)
Layer (protocol or User Trace; not Program)
Statistics Type
Record Setup
Disk No
OAT Record Size
Initial Cond
Stop At
Front-End Buffer Setup
Idle Suppress
DTE
DeE
SEP '95
T1/G.703 Transmit Setup
(all fields)
T1/G.703 Data Path Setup
(all fields)
T1/G.703 Line Setup
(all fields)
Tabular Statistics
(all fieldS)
Graphical Statistics
(all fields)
File Maintenance
(all functions except L,JAD)
Datemme Setup
(all functions)
Printer Setup
(ali fields except Redirect Run Mode Output)
Disk Maintenance
(all functions)
Mise Utilities
(all fields)
Easy VIew Setup
(all fields)
Remote Control Setup
(all fields)
AIM Interface Setup
(all fields)
2-17
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(C) Errors Detected When A Program Is Compiled
Trigger programs and spreadsheet programs with syntax errors or other errors will not
compile successfully and will prevent the unit from executing the test program.
If an error is detected during the compiling phases (after you have pressed ~), the
user is returned automatically to the Protocol Spreadsheet.
While a program is being compiled, errors are flagged and diagnostic information is
stored. This information is made available to the user when the unit is returned to
Program mode. A diagnostic message for the first error found is automatically
displayed at the top (second line) of the Protocol Spreadsheet screen. The cursor is
automatically moved to the error.
Press GO-ERR once more to move to the next error. For each error, a diagnostic
message is displayed. The search for errors stops at the end of the file and the
message "No more errors" is displayed.
GO-ERR also calls up diagnostic information
on trigger-menu errors.
Error messages are listed in Appendix A of this manual.
2-18
SEP '95
2 General Operation
(D) Recoverable Errors During Run Mode
The following messages indicate MPM processor errors:
MPM MPM MPM MPM MPM -
-
Processor Fault
Divide Fault
Bus Error
Stack Fault
Memory Fault
Do not turn off the INTERVIEW when anyone of these errors is displayed in Run
mode. Instead, press S and check your program, since these messages indicate
programming problems that cannot be displayed as syntax errors but which do
prevent your test from running properly. Consult Appendix Al for an explanation of
these messages. Once you have revised the test, try running it again. If you cannot
resolve the problem, save a copy of the program and contact Customer Service.
2-19
SEP '95
~~~~~~~-------.--------,---.-,-----,-"",----,,----,
---------,
INTERVIEW 8000 Series Basic Operation: 951-80424-01
2.7
Data Flow
Figure 2-6 diagrams the movement of data between the various functional components of
the INTERVIEW. The diagram provides "clues" to many of the operating characteristics
of the unit. For example:
2-20
•
The front-end buffer (FEB) lies squarely in between the line interface and (1)
the recording medium and (2) the program logic. This means that control leads
mayor may not be recorded and mayor may not be seen by the
triggers-depending on the FEB setup (Section 9).
•
Line data may be recorded directly to disk: as bit-image data, recorded to
bit-image RAM and then transferred to disk, or captured as character data in
the display buffer and transferred to disk.
•
Once control leads and time ticks or frame timestamps (that is, the original
timing values) are recorded alongside character data, they are locked in. Since
the FEB is not on the playback path for character data, FEB selections do not
apply.
•
Bit-image data, however, does pass through the FEB during playback. Except
for the Idle Suppress and Frame Timestamps fields, FEB selections apply. This
means that control leads and time ticks, if recorded with the data, must be
enabled in order for the program logic to detect them. (For playback of
bit-image data, the NRZI selection on the Line Setup menu also does not apply.)
•
Only data on disk may be played back.
•
Front-panel green-red LED's are not disabled for line data, and do not blink
for recorded data.
•
Not only characters but also leads and time ticks (or frame timestamps), if
enabled in the FEB setup, are captured automatically in the display buffer (that
is, the screen buffer or character RAM).
SEP '95
2 General Operation
DlE/OCE
1l
TIM :
1~=E'~)IIt:---
P.>------.
Data and
control
leads
Bit-image
data playback
FEB
Transmitted
data and
control leads
,
RAM
,
Record
bit-image
data, control
leads (tf
"
buffered),
. and time ticks
Bit-image
transfer
--
DISK
,
Data, control
leads (if buffered),
and time ticks or
timestamps
(If enabled)
Of enabled)
SCSI or floppy
J
Character-data
playback 1
r-----------~----------~
1Character-data
playback is not
recommended
TRIGGER LOGIC/
APPLICATION
PROGRAM
in high-speed
frame mode
80288 prooessor($)
MPM board(s), MPM RAM 2M to 8M
Program
and
setup
Character data,
control leads,
and time ticks
or timestamps:
...
OPERATOR
INTERFACE
68010 processor
CPMboard
System RAM 4M to 6M
record or
transfer
4 - Capture
Buffer Keyboard Printer
Display
Remote
Figure 2-6 INTERVIEW 8000 Series functional diagram.
2-21
SEP'95
-
--
-.-----.-----.--.-----------------~---------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
2.8
How to Correct Common Problems
(A) Unit enters Run mode even though I press the Program key.
A file called user.Jntrf was located in the lusr directory of the hard disk during
boot-up. In this situation, the program in user_intrfis automatically loaded,
compiled, and run each time the 8
key is pressed. Press 8-~ to enter
Program mode, or rename user_intrfand power-up again. See Section 2.2(A).
(8) Unit does not execute Run: Protocol Spreadsheet returns to
screen instead.
An error was detected during the compiling phases (after you pressed ~). See
Section 2.6(C).
(e) My program does not run; and instead, I get a message about
an "unresolved reference."
Your program is asking the compiler for a send routine that is not available in
Monitor mode. Switch to an Emulate mode, or modify the program. For programs
with C coding, this message usually means that a routine has not been declared or
defined.
(D) Protocol Spreadsheet program which was just loaded shows
syntax error strike-throughs which weren't there before.
Missing softkey selections and pervasive strike-through's on the Protocol
Spreadsheet indicate that the correct Layer Personality Package has not been loaded.
To correct the problem, return to the Layer Setup screen, insert disks if necessary,
and check Personality Package and drive selections. Then press §) to load the
packages manually.
(E) EIA trigger condition does not come true, even though the
front-panel LED indicates a status that makes the condition
true. For example, an ErA RTS ON condition is not coming true,
even though the RTS LED is bright red.
EIA status is not detected by the triggers if Buffer Control Leads: ··1<19> is the selection
on the Front - End Buffer Setup menu. See Section 9.
If the data is being played back from disk and the FEB Setup menu was not
configured to buffer control leads at the time the data was recorded, the leads are no
longer available for triggering.
Front-panel LEDs always reflect line status, never the status of recorded leads.
2-22
SEP '95
2 GeneJaIOpeJaDon
Note also that an EIA condition that is the only condition on a trigger menu (or the
only condition associated with an action or set of actions on the Protocol
Spreadsheet) is transitional. It is only true when it changes to true. To check the
current status of an EIA lead regardless of transitions, pair the EIA condition with a
don't-care character condition (see Section 25.4) or with an ENTER_STATE condition
on the Protocol Spreadsheet. See Section 31.3(A).
(F) Lead lines on the data-plus-leads display are not transitioning,
even though the front- panel LEOs for the same control leads
are blinking.
The leads on the data-plus-leads display are also enabled/disabled by the Buffer
Control Leads field on the FEB Setup menu. See (E). directly above.
(G) My "current" timers seem to be incrementing on the Tabular
Statistics screen, but the other statistical columns always show
0, even when t take statistical samples.
The "current" column is derived from a millisecond "clock on the wall," while the statistical
values may be calculated on the basis of time ticks that occur at one-second intelVais. Your
timer samples may be less than 0.5 seconds, in which case, they are rounded to zero.
Check the FEB Setup menu, and solve the problem in either of two ways. Turn Time
Ticks off, and the statistical columns will use the wall clock. Or change the Tick Rate
from one second to ten milliseconds or smaller (down to ten microseconds).
(H) I am trying to send a transmit string from a trigger menu
(or from Layer 1), but my data does not appear on the screen.
When you are having trouble transmitting, always go to the Line Setup menu and
look at the Clock Source field first. You must have dock to transmit, whether internal
or supplied by an external DCE.
Another frequent problem is receiver synchronization. When you try to transmit, does the
front-panel LED for your transmit lead (TD or RD) blink rapidly? If it does, then you
are transmitting successfully, but your receivers may not be synchronizing with the data.
Check the Sync Char field on the Line Setup menu. Also be sure that the sync pattern
is part of your transmit string. You must supply these characters yourself.
(I) I have loaded in X.2S packages at Layer 2 and Layer 3, and
I am trying to send a data packet from Layer 3; but my data
does not appear on the screen.
The INTERVIEW is a layered emulator. The significance of this is that Layer 3 and
higher layers (in Emulate modes) have no direct access to the physical layer, Layer l.
In practice this means that aRCV condition at Layer 3 does not see packets on the line.
It only sees packets that are delivered up from Layer 2 by a user program at that layer.
SEP'95
2-23
------______"______________..____._.__.__
____..
e_·_~_'.
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Similarly, a SEND action at Layer 3 does not in itself send a packet out onto the line.
A SEND action merely delivers the packet to Layer 2-provided that Layer 2 has
indicated its readiness to receive data from above.
The following program is not any sort of complete Layer 2 emulation. It is the
minimum program that must be entered at spreadsheet Layer 2 in order for a Layer 3
program to have access to the data line. Once this Layer 2 program is entered, Layer
3 can send packets out onto the line and receive packets from the line.
LAYER: 2
STATE: datalink
CONDITIONS: DL CONNECT REQ
ACTIONS: DL CO"f..lNECT CONF
CONDITIONS:DL DATA REQ
ACTIONS: SEND iNFO" «DL DATA)) "
CONDITIONS: Rev INFO
ACTIONS: GIVE_DATA
The elements of this program are discussed in Section 34, OSI Primitives on the
Protocol Spreadsheet, and in the programming example in Section 37.9.
(J) I'm trying to load a program; but instead, I get an error message
about loading a layer package.
When a program or object file is loaded from the File Maintenance screen, the
system must be able to locate any layer personality package that the program
requires. If the necessary layer package cannot be found, the file will not be loaded.
NOTE: Optional applications programs are available for the
INTERVIEW 8000 Series. Make sure that necessary layer packages
are accessible when you load these programs.
In the INTERVIEW 8000 Series, all layer packages are accessible at all times since
they reside in the /usr/layerykgs directory on the hard disk. See Section 8.
(K) My INTERVIEW is overheating.
Collected dust and dirt on the fan filter may be blocking the flow of air into the unit.
Follow the instructions in Section l.5(D) on cleaning the fan filter. If the problem
persists, contact Customer Service.
(L) I power up my INTERVIEW and it gives a message about not
being able to find mstrmenu.cmp.
You have a TURBO unit that is trying to load the menu information for the Easy
View system. First, load HRD/AR_APPS/UTILSIEZVUmaint onto the hard disk.
Next, compile mstrmenu.txt to try to reinstaH the file: press any key except ~ or
~, and use the COMPILE softkey. This should reinstall the file.
2-24
SEP '95
2 General Operation
If the file is not reinstalled, and if you have the Easy View disks, duplicate their contents
onto your hard disk. (See Section 14 for information on the Duplicate Disk command.)
If you do not have the Easy View disks, go to the Easy View Setup screen, select Enter
Easy VIew After Power-Up: iRt and save the setup. (See Section 19.)
(M) I power up my INTERVIEW and it gives a warning message about
the CPM.
During power-up, TURBO units check the revision levels of all boards for
compatibility. Even if the revision levels are not as expected, the general operation
of the unit is unaffected. Contact Customer Service for further information.
(N) I correctly set up my INTERVIEW menus for emulation, but
nothing happens when I try to begin emulating.
Many of the later Test Interface Modules have a switch on the TIM which allows you
to enable or disable emulation. Check to see that this switch is in the ENABLE
position for emulating. For further information. see the TIM documentation.
(0) When running an application program at T1 rates, I get an "FEB
Overflow" message.
Early application programs (especially those developed for some of the older protocols
like SNA) were designed for monitoring specific interface activity such as leads and time
ticks which are important when running at 9600 bps. These programs, some of which are
resident in Easy View, will not run at today's high speeds specifically because of their
excess "baggage" (overhead) which slows down the program. To run such programs, tum
off the leads, change from time ticks to frame timestamps. select bit-image recording on
the Line Setup screen, and run the program in High Speed Frame Mode. This should
allow the program to run at Tl rates.
(P) I'm a new INTERVIEW operator; where do I begin?
Your first step should be to read the 30 Minutes to Programming the
INTERVlEW!J 8000 TURBO Series (951-B0431-01) included with your unit. Work
through the exercises with the data disk provided to familiarize yourself with the
unit's operation. Secondly, an excellent source of general information is found
on-line: go to the Easy View Main Menu by pressing §3 (ifthe menu isn't already
displayed) and press I!I for Help on-line. A third source (also on-line) is located on
a submenu ofthe Easy View Main Menu; arrow down to and select the OPERATION
menu. Selecting any topic from this submenu gives detailed information on that
subject directly on the screen. And, of course, the Table of Contents and Index in this
technical manual also direct you to specific topics.
(Q) My unit is running at a very slow rate.
It is a simple fact that the more tasks there are to accomplish, the longer it takes to
complete them-time is a relative factor. This is also true of the INTERVIEW
When line rates are relatively high, it may be best to strip your program of extraneous
SEP '95
2-25
INTERVIEW 8000 Series Basic Operation: 951-80424-01
tasks which would slow down the unit. This may include loaded Layer Personality
. Packages that are not being utilized by your application, recording data with tick
rates, etc. Refer to the INTERVIEW Technical Manual for more information on
performance optimization.
(R) I'm trying to run an application program that has worked before,
but it won't compile or run.
If you are operating a non - TURBO unit with software revision 8.00 (or higher)
installed. there may not be enough system memory available to run large application
programs. You may need to upgrade your system.
Also, an application specifically designed for operation on an INTERVIEW 8000 Series
unit may not compile on a 7000 Series unit due to memory capacity constraints.
(S) I'm in the Easy View menu system, and I want to run an
application with a dual-port V.35/EIA-530(449)/EIA-232 TIM
installed to test at the EIA-232 interface. What should I do?
To enable the correct parameters for your interlace, you must configure the V.35
Interlace Setup screen before you load the application. This is done in the operating
system; to access the operating system menus from the Easy View menu system, press
!ez wI. This will display the Program Menu.
From the Program Menu, press [ITl SETUp, then press lEI UNE, and configure the
Line Setup screen for the data you wish to test.
Return to the Program Menu by pressing 8 . Once again press !TIl SETUP, then
press ®J D V.3S, to access the V.35/530/232 Dual-Port Interface Control screen.
Choose SINGLE PORT or DUAL PORT for the Mode field. If you have selected
SINGLE PORT for this field, move to the Connector field. Choose V.35,
EIA-530(449), or EIA-232 (your indicated choice) and configure the remainder of
the screen as appropriate for your link.
To run an application program from Easy View, then press [.zwl and access the
program to run.
Refer to Section 5 for information on the Line Setup screen and to the V.35
Multi - TIM documentation which accompanied your dual-port
V.35/EIA - 530(449)/EIA - 232 TIM.
2.9
Optimizing Recording Rates
(A) Recording with Standard Hard Disk Drive (80 Mbyte)
It is a simple fact that the more tasks there are to accomplish, the longer it takes to
complete them-time is a relative factor. This is also true of the INTERVIEW
When line rates are relatively high, it may be best to strip your program of extraneous
tasks which would slow down the unit during recording.
2-26
SEP'95
2 General Operation
One option is to record the data for playback and analysis at a slower rate.
Three sets of program selections for optimizing high -speed recording of data follow.
All three versions assume that you are not loading in any program that will look at
the 1D or RD data, BCC, frames, packets, Or EIA leads. All three versions record
the data so that it can be run against more complex programs later on.
The fastest version records data without displaying the character data to the screen.
The next version records data at maximum speed while still displaying data. The
third version records data with personality packages loaded in the unit so that a
protocol trace is displayed in real-time.
1.
Recording without displaying character data. The first set of programming
selections records all of a data line (including idle and time ticks) in bit-image
data format. This is the fastest of the three recording scenarios.
Beginning with the default screens, make the following selections:
SETUP:
UNE:
Sync Char: delete both sync characters
DISPLAY;
Display Mode:~{NI~JiJi\1(~11
RECORD:
Capture Memory: user choice
Data To Record: t~;ll~
Stop at:
user choice
FEBUFF:
or
with one second to one millisecond selected
Using one-millisecond time ticks, the maximum normal recording
speeds for each of the disk types on the Record setup screen are
as follows:
Single Floppy Disk
Multiple Floppy Disks
Hard Disk
RAM
High -Speed RAM
64 Kbps
64Kbps
768Kbps
768 Kbps
2.048 Mbps (time-ticks off)
NOTE: Time-ticks are not supported above 768 Kbps.
TRIGGERS:
For
format, the following triggers will keep the unit out of
sync; the unit works at optimum speed when it is not in sync. Enter
these conditions and actions on a Trigger Setup screen:
CONDITION: DTE 1 OFlB] ("don't care")
ACTION: OUT SYNC BOTH
CONDITION: DeE 1 OF18l ("don't care")
ACTION: OUT_SYNC BOTH
2-27
SEP '95
--- -
----------------- - - - -- - ---------------------_..
_----_.._._._--
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTE: When line rates approach the maximum recording speed, consider
using high-speed RAM recording. See Section 7.5(A).
2. Recording while displaying character data. The second scenario records data at
optimum speed while still preserving the character display.
Beginning with the default screens, make the following selections:
SETUP:
LlNE/RECORD:
Capture Memory:
user choice for type of i~g:;!
(do not select ;;~:!.' recording)
FEBUFF:
Suppress the idle line pattern under Idle Suppress using the
following patterns:
BOP:
TE
SYNC:
FF
TE
FF"
On the Front End Buffer screen, turn off Buffer Control Leads
and Time Ticks:
Buffer Control Leads:
Time Ticks: [.i
Frame Timestamps:
LAYER:
Do not load any layer personality packages.
TRIGGERS AND PROTOCOL SPREADSHEET:
Do not load in any program that will look at the received data, BCC,
or ErA 1eads.
2-28
SEP'95
2 General Operation
3. Recording while displaying character data or protocol trace. The third setup version
records data at maximum speed with layer personality packages loaded.
Beginning with the default screens, check the following selections:
SETUP:
UNEJRECORD:
Capture Memory:
user choice for type of flB~
(do not select t~ recording)
FEBUFF:
Suppress the idle line pattern under Idle Suppress using the
following patterns:
BOP:
SYNc:
iii.
T"
• TE
~
t appears at the
top left of the spreadsheet screen. In insert mode, the operator types in a block of
data while succeeding text is pushed fOlWard with every keystroke.
Press ~ a second time to exit insert mode and return to overstrike mode.
=
NOTE: ~ is not an alternate-action key that toggles the
accomplishes
spreadsheet from insert to overstrike mode. Only
this function.
Figure 3·3 Spreadsheet keys.
(K) Cursor Keys, Menu Screens
See the bottom right of Figure 3-2. [!1 and ill move the cursor from line to line on
programming menus (including triggers). 8-[!1 moves the cursor to the first field in
the menu. §.B-GJ places the cursor in the last field in the menu. 8 and 8 move the
3-8
SEP '95
3 Keyboard
cursor from field to field on the same line. In text-entry fields, they move
nondestructively right and left over text that has already been entered. ~ and lmJ
rotate the selections at the cursor position.
8
and 8 are field oriented. They move the cursor down or to the right,
depending on where the next menu field is located.
Whenever a programming menu is first entered, the cursor is in the "home" position.
~ moves the cursor back up to this position. Home may be the first field on the
menu, or it may be a softkey rack that selects among menus or among fields on a
lengthy menu. Several screens have more than one home position. Additional
positions are accessed consecutively when you "home upwards" from below. See, for
example, the Line Setup or Trigger or Mise Utilities screens.
When you are accessing a programming screen (except the main -menu screen or the
two Statistics menus), the !Ill key will return you to your previous menu. You may
use this key to backtrack through several previous screens.
On the two multipage Statistics screens.lEl and (lID cause a page-by-page scroll.
(L) Cursor Keys, Spreadsheet Program
In a spreadsheet program, the cursor-arrow keys move the cursor by one column or
one row. 8 moves the cursor to the current indent position on the next line. ~
and (1£1 cause the screen to scroll one line at a time, while I~I and t&J cause a
page-by-page scroll. Roll and page keys do not affect the cursor.
"Home" is the top left of the current screen. To cursor to the beginning of the
spreadsheet program, press 8-0. Press 8-00 to go one line below the last line of
the program.
To cursor to the beginning of a given line, press 8-8. To "express" the cursor to
the end of the data-entry on a line, press ~-8.
To cause the cursor to skip forward from keyword (or "token") to keyword, press
8-8. 8-8 causes a reverse skip.
Any cursor movement across keyword boundaries will change the softkey-option
rack along the bottom of the screen.
S
may be used as a kind of "program tab" to mark a place in the Protocol
Spreadsheet where the cursor will automatically revert on command. With the cursor
in a position you will want to return to quickly and conveniently, press 8 followed by
a number key--m, for example. Then go ahead and move the cursor any distance in
either direction from the marker.
When you wish to return to the "mark 2" position, press 8-8 followed by~. Up
to ten numbered cursor-markers may be reserved in the spreadsheet program.
SEP '95
3-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(M) Softkeys and 8
Depending on which menu field has the cursor, all selections are mapped to softkeys
at various times. On menu fields, the 8 key has the same function as 8: it moves
the cursor to the next field. So there is a way to move around the menu and make
selections without using the cursor-arrow and other keyboard keys.
When the operators are using softkeys to enter a spreadsheet program, they use B
to mean, "Escape to the previous (higher) level of programming." Figure 3-4
illustrates how two depressions of the 8 key can take the program from a specific
EIA condition all the way to the highest level of softkeys.
Figure 34 Moving to a higher rack of softkeys on the Protocol Spreadsheet.
3.3
Real-Time Keys
The keyboard in Figure 3·5 indicates the keys that are valid in Run mode when the data is
displayed in real time (rather than frozen). In addition to the keys highlighted in this
figure, the C programmer may use the variable keyboard_any_key to monitor input from
every key except §], ~, and 8. See Section 68, Other Library Tools.
3-10
SEP '95
3 Keyboard
Figure 3-5 Real-time keys.
(A) Hex
In normal Run-mode operation, the ~ key controls an on/off decoding function
that converts all the data on the screen to hexadecimal. Note that the
screen -decoding function of ~ does not light the LED on the keycap. Only the
data-entry function turns on the LED.
(8) Freeze
8
controls an on/off function that freezes the screen display. For line data,
program activity and bit-image recording continues. Character recording will not
continue since the display buffer (character RAM) is frozen.
action is
A similar freeze function can be activated when a capture:
performed by a trigger. The difference is that while the manual (keyboard) freeze
permits you to scroll through the data buffer, trigger freeze does not.
SEP '95
3-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(C) Record
For line data, S controls a manual start/stop function that records data according to
the parameters selected on the Record Setup menu. For disk data, press 8 to
suspend/resume playback.
NOTE: Although playback is immediately suspended when you press
8. the screen display continues until the character buffer's contents
are fully displayed. (For bit-image data, the FIFO must empty.) At
slower playback speeds, you may notice a slight delay before the
display actually freezes.
Notice the recordipJayback status field next to the block number field in the status
area of the Run - mode display screens. See Section 6.2. The initial status indicator
displayed in this field is determined by Line and Record Setup selections. See
Sections 5.2 and 7. It is subsequently controlled via the E3 key.
(D) Cursor Keys
When a multipage Statistics display (tabular or graphic) is presented in Run mode,
(JiJ and (If) cause the rows of values (or bars) to scroll up or down one line at a time,
while r=:J and !lID cause a page-by-page scroll.
[f) and ffJ serve two purposes. When the Run -mode display screen is the Display
Window, [f) and I!l are under the programmer's control. (Refer to Section 68, Other
Library Tools, for information on keyboard variables and the send_key routine.) For
example, these keys could be used to move from field to field on a menu created in
the Display Window. For all other Run-mode screens, I±l and [!] control the playback
speed of data from a disk. [f) slows the data speed by half, while I!l doubles the
current speed.
NOTE: When you use the [±) and [!] keys to control the data speed
during playback, an alarm will sound if you attempt to slow the data
below the minimum speed required or speed the data beyond the
maximum speed allowed.
(E) Softkeys
In Run mode, the softkeys will change the display selection. Selectable display modes
include character data, character data plus control-lead timing, protocol trace,
program trace of state-to-state movement and of user-entered messages called
"traces," an application-specific "display window," statistical tabulation or graphic
display of counters and timers, and remote operation from a PC or another
INTERVIEW.
There is also a Run-mode softkey selection called NO DIS? This suppresses the
writing of data to the screen (though not to the screen buffer). See Section 6.11 for
an explanation of this display mode.
3-12
SEP '95
3 Keyboard
3.4
Freeze- Mode Keys
The keyboard in Figure 3-6 indicates the keys that are valid in Run mode when the data
display has been frozen.
In addition to the keys highlighted in Figure 3-6, the C programmer may use the variable
keyboard_any_key to monitor input from every key except §J, 11m, and 8. See Section
68, Other Library Tools.
Figure 3-6 Freeze -mode keys.
(A) Hex
In Freeze mode, ~ controls an on/off decoding function that converts all the data on
the screen to hexadecimal.
(B) Freeze
8 will also unfreeze a frozen display. For disk data, it will resume playback and
program activity.
SEP '95
_ _
11"_ _ _"
3-13
_
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(C) Record
The recording of live data can be stopped and started even while the display is frozen.
The 8 key will not resume playback of disk data that was frozen via the 8 key.
(0) Print
Press 8 to send the current frozen screen to a serial printer attached to the
INTERVIEW. [3 together with §.g will send the entire data buffer.
(E) Cursor Keys
The cursor keys work on the frozen data buffer the same way they work on the
spreadsheet screen. Cursor-arrow keys move the cursor by one column or one row.
[m:J and (ItJ cause the screen to scroll one line at a time, while mil and [gJ cause a
page-by-page scroll. Roll and page keys do not affect the cursor.
8
will move the cursor to the first (and oldest) character in the character (screen)
buffer. When ~Jjs pressed together with §.g, the screen and cursor move to the last
(or newest) character in the buffer.
When a multipage Statistics display (tabular or graphic) is presented in Freeze mode,
IJrID and (lID cause the rows ofvalues (or bars) to scroll up or down one line at a time,
while r.=J and (§) cause a page-by-page scroll.
(F) Mark
The 8 key enables/disables the cursor timing feature of three Freeze-mode data
displays (all except dual-line). Wbenyou first enter Freeze mode, cursor timing is
disabled. Press 8 to enable it.
The 8 key is also used to mark the position of an event in the display buffer. The
marked character is replaced by the iBJ symbol. Each time you press 8, you move the
marked position-i.e., you redefine the event.
To disable the cursor timing display, return the cursor to the marked character and
press 8.
For additional information on cursor timing, see Section 6.4(E).
(G) Softkeys
All softkeys are valid in Freeze mode and serve the same functions as in real time.
3.5
Remote Control Keys
The INTERVIEW keyboard-to- PC conversion for remote-control operation is
shown in Table D4-1.
3-14
SEP'95
4 £asyView
4 EasyView
SEP '95
4-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
View Main Menu
Eas~
1
.,..,. MORE .,..,.
BERT
ASYNC
BISYNC
DDCMP
FRAME RELAY
ISDN
SDLC
SNP.
MORE U
U
Go to the Menu of SNA Programs, Tutorials
~.
move selection bar
+- move to prev menu
-+
?
move to next menu
=
Help
& How To's
RETURN select menu entr~
HOME
move to top menu
EZ VU exit/enter menus
Figure 4-1 The main menu in the Easy View system.
**
TRIGS
SPDSHT
STATS
LAYER
FMAINT
UTIL
REMOTE
ogram Menu
**
est etup
Line Setup
BCC Setup
BERT Setup
Displa~ Setup
Front End Buffer
Record Setup
Interface Control
Triggers - Conditions & Actions
Protocol Spreadsheet
StatistIcs Results:
Tabular Displa~
Graphics Displa~
BERT Results
La~er Setup & Protocol Configuration
File Maintenance Functions
Ut i I i ties:
Disk Maintenance Time/Date Setup
Printer Setup
Miscellaneous Utilities
Eas~ View Setup
Remote Control Setup
Figure 4-2 The main Program menu screen in Program mode.
4-2
SEP'95
4 EasvView
4
Easy View
This section provides an overview of the Easy View system. It describes the appearance of screens
and the keys used to interact with those screens. Use the menus in Easy View to load and execute
programs quickly or to access help information or tutorials about INIERVIEW screens, menu
selections, and protocols.
The Easy View Operating System requires software revision 10.00, or higher.
4.1
Booting Up
By default, TURBO units automatically enter Easy View after boot-up. There is a
five-second pause at the power-up scteen before you see the first Easy View menu,
shown in Figure 4-1. Use this pause to obtain any pertinent information you need from
the power-up screen. If you want to bypass this brief timeout and enter Easy View
directly, press~. From this point on, toggle between Easy View and Program mode by
pressing~.
NOTE: If the boot-up disk contains the file /usr/de[ault or the hard disk
contains the fIle /usr/user~intrf, the INTERVIEW does not automatically
enter Easy View following boot-up, even if it is configured to do so.
These are user-created programs that automatically start the
INTERVIEW in Run mode. See Sections 2.1 and 2.2 for more
information on these files.
The INTERVIEW may be configured to enter Program mode instead of Easy View
following boot-up. Go to the Easy View Setup screen and modify (and save) the
configuration. See Section 19.
You can reset the INTERVIEW in Easy View or in Program mode directly from the
keyboard. Press the §.9-§l-1lfl or S-8-~ key combination to force the
INTERVIEW to perform the self-test and booting sequences without turning the unit off.
This reset is similar to that of a PC in that it is not a hardware reset. For hardware resets,
you must power the unit off and then back on.
SEP '95
4-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
4.2
Entering and Exiting Easy View
If you entered Easy View automatically after boot-up, you may exit (from any of its
screens) by pressing~. When you exit Easy View after boot-up or after you run a
program from an Easy View menu, the main Program menu screen shown in Figure 4-2 is
displayed. In general, however, whenever you exit Easy View, you are returned to the
same location in the Program-mode screens where you were when you accessed Easy
View.
As long as the 8 key is enabled, reenter Easy View by pressing I§:~ again. If Easy View
menu information is being kept in memory (see Section 19), you are returned to the same
location in the Easy View menus where you were when you exited. Repeatedly pressing
8 moves you back and forth between Easy View and a Program -mode screen. Use this
feature to access help information about the selections you see on Program -mode menus.
Section 4.4(D) explains how to find help information.
Press @-8 to force the INTERVIEW to enter Easy View and reload its menus from
the hard disk. This feature may be particularly useful if you have copied a new version of
the master menu file from a floppy disk to the hard disk and you want to load the new
version.
NOTE: If you press 8 while the INTERVIEW is performing an extended disk
or file operation from the Disk Maintenance or File Maintenance screen-such
as copying files, formatting a disk, or obtaining the contents of a directory-an
alarm sounds and the screen remains unchanged. Once the operation has been
completed, the 8 key functions normally.
4.3
Easy View Menus
The Easy View menus are organized into a tree-structured hierarchy. See Figure 4-3.
The first time you enter Easy View following boot-up, the menu at the root of the tree,
the Easy View Main menu, is displayed. See Figure 4-1. The root is level one of the
hierarchy. Any menus entered directly from the root menu are level two. Menus entered
from level two menus are level three, and so on.
The Easy View Main menu is organized primarily by protocol, as shown under "Level 1" in
Figure 4-3. Other menu items provide: programs for autoconfiguration (AUTOMON) and
BERT testing (BERT); access to specific information about various operations, screens, and
menu selections of the INTERVIEW (OPERATION); a list of Easy View utility programs
(UTIUTIES) such as file transfer; and updates on available options and new product
information (AR NEWS).
When you select a protocol from the Easy View Main menu and press ~, a menu of
Program Types, Tutorial(s) & How To's is presented. Refer to "Level 2" in Figure 4-3.
From this menu, identify which kind of program you want to run for your selected
protocol, typically monitor, statistics, emulation, or conformance (for
4-4
SEP '95
4 EasyView
Level 2
Level 1
Lgvel3
Lgvel4
AUTOMON
BERT
MONITOR
STATISTICS
EMULATION
CONFORMANCE (X.25 only)
ASYNC
BISYNC
ODCMP
FRAMERELA
ISDN
SOLC
SNA
SS#7
X.21
X.2S/HOLC
TUTORiAl
How To .. ,
T1
G.703
miscellaneous
protocols
MISCPRTCLS
MONITOR }
STATISTICS
EMULATION
ARNEWS
OPERATION
UTILITIES
Figure 4-3 The Easy View system has a tree-structured menu hierarchy, similar to the one shown above.
X.25 only). In addition, you can access tutorial or how-to information about the
protocol. Tutorials provide general information about the selected protocol. How To's
guide you in the setup and operation of the INTERVIEW according to the protocol
environment.
If you select MONITOR, STATISTICS, EMULATION, or CONFORMANCE (if present) from a Program
Types, Tutorial(s) & How To's menu and press 8, a level-three menu lists the available
programs.
(A) Menu Format
Easy View menu screens have the format shown in Figure 4-4.
1.
Master title. The top line of the screen may contain a master title. This title is
centered at the top of all Easy View menu screens. In Figure 4-4, it is blank. See
Section 20.5 for information on defining a master title.
2. Menu title. Each menu has an individual title centeted in the top box of the
screen.
3. Menu level. A number indicating the menu's level in the menu hierarchy is
displayed at the right end of the menu title line.
SEP '95
4-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Master TItle
Menu Level
MenuTItie
Menu of SNA Program
Menu Selections
{
T~pes,
Tutorial(s)
& How To's
2
MONITOR
STATISTICS
EMULAT I ON
TUTORIAL
How To ...
Menu -Item Description
Go to the Menu of SNA Statistic Programs
~~
move selection bar
+- move to prev menu
-+ move to next menu
? = Help
RETURN select menu entr~
HOME
move to top menu
EZ VU exit/enter menus
Menu Keys
FlgUft 4-4 A second -level Easy View menu screen. To access this menu, select SNA on the Easy View Main
menu and press~.
4.
Menu selections. The center box on the screen displays the menu items. A
reverse-video cursor bar highlights the selected menu item. In Figure 4-4,
STATISTICS is selected for SNA protocol.
Not all menus contains selections. These empty menus have been included for
the addition of optional AR programs. You may also use them for your own
programs.
Although a menu has no maximum number of selections, each screen displays no
more than eight menu items at a time. If there are more than eight entries in the
menu, the word "MORE" is displayed in a position that indicates where the
additional items fall in the list. Refer again to Figure 4-l.
5. Menu item description. Each menu item can have an associated line of descriptive
text, centered in the bottom box on the screen. This text is displayed
automatically when the selection bar is over the menu item. The text shown in
Figure 4-5 describes the program that will be run if you select Troubleshoot
Host=DTE and press 8.
If the selection bar is over a program item that is available as an option, but not
currently installed in the INTERVIEW, a message to that effect is displayed.
6.
4-6
Menu keys. At the bottom of each menu screen is a list of the keys you may use
to interact with the menu.
SEP '95
4 EasyView
Menu of SNA Statistic Programs
3
.
Sim:.l e SNA Ut i 1 izat ion
.
"
Troubleshoot Host=DTE
FID 4 Response Time
SNA Statistics (16 PU-Line)
SNA Statistics ( 8 PU-Line)
Anal!:fze Multidrop SNA Line with T!:fpe 2 Controllers
~.
move selection bar
-+
move to next menu
+- move to prev menu
? = Help
RETURN select menu entr!:f
HOME
move to top menu
EZ VU exit/enter menus
Figure 4-5 Statistic program selections for SNA protocol. To access this menu from the screen shown in
Figure 4-4, position the selection bar over STATISTICS and press
8.
(8) Menu Keys
Several keys are used to interact with the Easy View menus.
The most commonly used keys are displayed at the bottom of each menu screen along
with brief descriptions of their functions.
ttl
Moves the selection bar up one menu item on the screen. If the selection
bar is on the top menu item and there are prior items out of view, the list
scrolls down one item and the selection bar remains in position.
~
Moves the selection bar down one menu item on the screen. If the
selection bar is on the bottom menu item and there are additional items out
of view, the list scrolls up one item and the selection bar remains in
position.
8
Returns to the previous, or "parent," menu in the menu hierarchy.
8
If the action associated with the menu item under the selection bar is go to
a menu, you may use the 8 key to move down one menu in the menu
hierarchy. Otherwise, the 8 key has no effect.
m
Accesses help information available about a selected menu item. The help
file presents additional information about the selected menu item.
Executes the action associated with the menu item under the selection bar:
move to another menu, load and run a program, or view a text file. The
SEP '95
lRi!Ii!ljUllliSiW::
1IIIJl!! _ _
l i l _ _ _~ _ _ _ _ _ _ _ _ _ _ _ _ •
4-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
S key can be used instead of the 8 key to move to another menu.
the only means available to run a program or view a text file.
8
is
~
As you move through the menu hierarchy, Easy View records the selections
you make. Use the 8 key to move immediately to the top of the root
menu and clear your selections from memory. The system now acts as if it
is entering each menu for the fIrst time.
8
If enabled, toggles between Easy View and Program mode.
There are additional keys that operate on Easy View menus which are not displayed
on the menu screens:
4.4
mID
Use this key to highlight the fIrst menu item on the screen. If there are
additional entries on a preceding page of the menu and you press mID again,
the cursor is positioned over the first entry on the previous page.
r=J
Use this key to highlight the last menu item on the screen. If the menu has
more than eight items and you press ~ again, the cursor is positioned
over the last entry on the next page of the menu.
Using Easy View
The first time you enter a menu, the initial eight menu items are displayed on the screen. A
reverse -video selection bar is positioned over the top item. Use the cursor keys to move
the selection bar over a menu item and press ~ to perform the action associated with that
entry.
When you select a menu item, one of three actions occurs: another menu is displayed, a
program is loaded and run, or a text file is presented for viewing on the screen.
(A) Moving through the Menus
As you move through the menu hierarchy, Easy View records all the selection paths
you make from its menus. When you return to each menu, its previous state is
restored. This feature allows you to retrace any selection path up (or down) the
menus by repeatedly pressing 8 (or 8).
Press ~ to clear the record of menu selections and return to the Easy View Main
menu. The system now acts as if it is entering each menu for the first time.
(8) Running Programs
Once you have made a program selection on an Easy View menu, press 8
compile, and run the program.
4-8
to load,
SEP '95
4 EasyView
By default, the message shown in Figure 4-6 is displayed when you select a menu item
whose action is to run a program. If you do not want to have this warning message
presented for the rest of your working session (i.e., until the INTERVIEW is turned
off), disable it by pressing @). Then decide whether to run the program or return to
the menu without running it.
NOTE: To disable the warning message completely, go to the
Program-mode Easy View Setup screen. See Section 19.
Menu of SNA Statistic Programs
3
Loading this program will overwrite the triggers,
spreadsheet and parameters now in memor!;;. Proceed?
Press:
to load the program
to return to the menu
to disable this warning
!;;
n
d
Anal!;;ze Multidrop SNA Line with T!;;pe 2 GJntrollers
't..a.
+-
-.
move selection bar
move to prev menu
move to next menu
?
=
Help
RETURN select menu entr!;;
HOME
move to top menu
EZ VU exit/enter menus
Figure 4-6 A warning message is presented before running a program. This program was run by selecting
Troubleshoot Host=DTE from the menu shown in Figure 4-5 and pressing 8.
If you decide to proceed, press lYJ. The screen shown in Figure 4-7 appears. There is
a brief pause at this screen while the program is loaded. Some of the line setup
parameters for Easy View programs can be changed on-line before the program is
actually run. You can elect to modify these parameters by pressing §) from this
screen. See Section 4.4(C). For now, we will leave the parameters intact, so do not
press§).
The INTERVIEW attempts to compile and run the program. If an error occurs at
any step in this process, an error message is displayed and you are automatically
returned to the menu screen from which the selection was made. (You are not
automatically taken to the spreadsheet screen if a compilation error occurs-as you
are when you run a program from Program mode.)
SEP '95
4-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
This program will use self-contained line parameters.
PRESS THE EDIT KEY NOW TO VIEW OR CHANGE THE PARAMETERS.
Press the PROGRAM key to abort running this program.
Abort will occur after program loading is completed.
Figure 4-7 Decide whether you want to view and/or change program line parameters.
If you exit the program by pressing ~ (and the Easy View Setup screen described
), you are
in Section 19 shows Keep Easy YIeW Menu Information in Memory:
automatically returned to the menu screen from which the program was launched.
Figure 4-8 shows the first Run - mode display for an SNA statistic program that was
selected and run from Easy View. (The program was selected in Figure 4-5).
BLK=00000 S 06/21/90 11:11
DATA
SNA
Ai
ALLSDLC 1 CTLR
.4
_ _,
1LUDATA RESPONS GRAPHIC ERRORS
Figure 4-8 Run -mode display of contro!\er and LU activity on an SNA multidrop line.
4-10
SEP '95
4 EasyView
(C) Changing Line Parameters
Some of the line setup parameters can be changed on -line before the program is
actually run. These parameters include Data source, DiSk, Disk Block No., File, Clock,
Speed, and NAZI. (To change other setup parameters, see Section 4.5(A).)
The default parameters associated with an Easy View program (and included in the
same linkable-program or source file) are its self-contained line parameters. If
changes are made to any of the parameters, the edited set is referenced as Easy Vzew
line parameters.
The first time you elect to run a program in any INTERVIEW session, the program is
set to use the self-contained parameters. Refer again to Figure 4-7. If you want the
program to run with these parameters, do nothing. Once the program loads, it will
compile and run. If you want to view the settings or make changes, press ~ before
the program is finished loading. The self-contained parameter settings are
displayed.
Self-contained line parameters for Easy View programs typically, although not
always, have the following default settings:
•
Data source: ~i~~~
•
DI$k: "~"''''';:'''''''h.a.nd
. Disk Block No.: !l(fields appears only when Data source is changed
for all Easy View programs
)
•
File: _ _(field
•
Clock:
to
appears only when Data source is changed to :~!)
tfJ.~~{t;'&~
for monitor and emulate DTE programs
J[$fi;.mlG}i~t0;;
for emulate DeE programs
2fiOO
•
Speed:
•
;DTE~I.i~) and DCE Speed: 2200. (fields appear only when Clock is
•
Use NAZI for SDLC:
To edit self-contained parameters for a program, press §D again. The defaults
(highlighted) and alternate selections for each parameter appear on the screen. See
Figure 4-9.
NOTE: Only those parameters which are applicable to a given
program are available for editing. For example, NRZI can be
modified for SDLC and SNA programs only and Data source can be
changed from .~~ for nonemulation programs only.
SEP '95
4-11
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
This program is set for MONITOR operation.
It will use these Eas~ Vie
parameters:
Data source: Line DAT
Disk:
FDl FD2
Fi 1e:
Disk B1
Clock:
nternal Split
Speed:
(for computations onl~)
III
Use NRZI for SDLC: Yes II
Press the EDIT ke~ to view self-contained parameters.
Press the RETURN ke~ to run the program
or the PROGRAM ke~ to abort the program.
Figure 4-9 To modify selected line parameters for a program, choose from available selections displayed on the
screen.
Use the 8 and {3 keys to change the selection for a field. The selection is
highlighted in reverse-video. Use the 0 and ffl keys to move between parameter
fields. Press §J to toggle between the Easy View line parameters and the
self-contained line parameters.
Once you have made your changes, press {§3 to run the program with the new
Easy View line parameters. The Easy View parameters are now the "default" line
parameters for subsequent programs you nm during the remainder of the cumnt
session (or until you change the parameters again).
Assume, for example, that you changed the Speed from 9600 to 5600. The next
time you select a program to run, it will be set to use 5600 as the line speed. See
Figure 4-10.
NOTE: If the Easy View parameters are set to use disk as the data
source and you subsequently select an emulation program to run, the
Easy View parameters are automatically updated so that the data
source is changed back to line.
The most recent set of Easy View parameters are retained in memory for the rest
of the working session. They are restored to the screen any time you access the
Easy View parameter screen.
If you want to make permanent changes to the setup of a program, see Section
4.5(B).
4-12
SEP '95
4 EasyView
This program will use Eas~ View line parameters:
Data source = LINE
Clock = EXTERNAL
Speed = 5600
(for computations onl~)
Use NRZI for SDLC = NO
PRESS THE EDIT KEY NOW TO VIEW OR CHANGE THE PARAMETERS.
Press the PROGRAM ke~ to abort running this program.
Abort will occur after program loading is completed.
Figure 4-10 The program ready to run is set to use Easy View line parameters. The Speed has been changed
from 9600 to 5600.
(0) Viewing Text Files
When you press m(the ill or 8-0 keys) for help or select a menu item whose
designated action is to present a text file for viewing (TUTORIAL or How To ... ), Easy
View attempts to load the proper file into memory.
If the fue is not found, an error message is displayed. Press any key to return to the
menu screen. If the file is located, it is presented for viewing. Help, Tutorial, and
How To files are alJ presented in the same format.
1.
Fannat. The format ofthe screen used to present text is shown in Figure 4-11.
The top twenty screen lines form a scrolling window. The value at the right end of
the bottom line is the percentage of the text file preceding the last character on the
screen. An indication of the current location in the file appears at the left end of
this line: (top). (more). or (end).
4-13
SEP '95
----.------.---~------------------.--.------
-----------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Program Item Names: Troubleshoot Host=DCE
Troubleshoot Host=DTE
Program File Names: SNAstaC
SNAstaT
Associated F i 1e:
1 inkab Ie program
- 1 i nkab 1e program
SNAstaUsr.s
tech_stats.o
source f i 1e
1 i nkab Ie object
Description:
This application provides several screens which assist in
identif~ing problems on Multidrop SNA lines where T~pe 2
controllers are used. A d~namic graphical presentation of all
activit~ for up to four active controllers is also provided.
~"Lop)
~r'eS's
r"
for
lnstructlons
8%
Figure 4-11 Information on SNA statistic program selected in Figure 4-5. To access this information, press ill
while the selection bar is positioned over Troubleshoot Host=DTE.
2. Keys. Instructions for scrolling through information files are displayed when ill is
pressed. These are shown in Figure 4-12.
Ke~s
Available While Viewing Text
PREV PAGE
NEXT PAGE
HOME
CTRL-HOME
Scroll up 20 lines
Scroll down 20 lines
Move to beginning
Move to end
MARK
ROLL BACK
ROLL FWD
Mark words in text
Displa~ prev marked text
Displa~ next marked text
CTRL-PRINT
Print all of the text
SPACE or RETURN
EZ VU
Return to menus
Exit from menu s~stem
Press
an~
Figure 4-12
4-14
ke~
to continue
Keys available while viewing text files.
SEP '95
4 EasyView
NOTE: If you want to print the contents of a text file, we suggest that
you set the Unes Per Page field on the Printer Setup menu to 062. (See
Section 16.) Each page of the printed output will contain a header and
three of the INTERVIEW's text pages.
3.
Operation. When you first enter a text viewing screen, the initial twenty lines of
the file are presented. Refer again to Figure 4-11. Use the keys described above
to scroll through the file. If Easy View menu information is being kept in
memory and you subsequently leave Easy View (via the 8 key), the system
records which portion of the file was being displayed at the time of exit. When
you reenter Easy View, you are automatically returned to the same position in
the text viewing screen as when you exited. Use this feature and the !ez wI key to
flip between Program-mode screens and help information about the screens.
4. Marking. You may also "mark" all occurrences of a text string within any text file.
The INTERVIEW searches for all words in which the specified string occurs and
highlights, or marks, them in reverse video. The search is conducted throughout
the entire text regardless of the cursor's current location within the file.
For an example of marking, let's view the SNA tutorial. If you ran the Troubleshoot
Host=OTE program, press 8
to abort the program. Now press 13 to return to
the Menu of SNA Program 'IYPes, Tutorial(s) & How To's. Move the selection
bar over the TUTORIAL menu entry and press 8. The screen shown in
Figure 4-13 should be displayed.
INTERVIEW SYSTEMS NETWORK ARCHITECTURE (SNA)
TUTORIAL
INTRODUCTION
The SYSTEMS NETWORK ARCHITECTURE (SNA)~ as it is defined and
implemented b~ IBM, provides the abilit~ to connect man~
different t~pes of devices and programs into a complex network
that allows all of these different devices and programs to
communicate and interact.
This architecture defines the division of all of the network
functions into clearl~ defined la~ers.
These la~ers provide
man~ of the same functions as the Open S~stems Interconnect
(OSI) seven-Ia~ered architecture defined b~ the International
Standards Organization (ISO) but the la~ers are not identical
and ma~ not be inter-operable unless some form of gatewa~ is
provided.
Figure 4-13 First screen in the SNA tutorial.
SEP '95
4-15
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Now press~. A pop-up window, illustrated in Figure 4-14, appears over the
text.
INTRODUCTION
T
i
d
Enter word or phrase to mark:
t
c
T
f
Use +-, -+, CLEAR, RUBOUT, and DELETE CHAR to edit.
Press RETURN to mark text or BRK to cancel.
m
(
Standards Organization (ISO) but the la~ers are not identical
and ma~ not be inter-operable unless some form of gatewa~ is
rovided.
Figure 4-14 Press 8
to enter a search string for highlighting.
Type in the text string you want marked. The field is 56 characters long,
including embedded spaces. (Multiple consecutive spaces are interpreted as a
single space.) If you enter the string as lowercase characters, all words containing
the string are marked regardless of case. If the search string contains any
uppercase characters, only exact matches are highlighted.
Suppose you want to locate information about Physical Units (PUs) without
scrolling through the entire SNA tutorial. Simply type the string "pu" and press
111£1'\1"3. The screen containing the first occurrence of the marked text is
automatically presented. See Figure 4-15. Marking is always expanded, if
necessary, to highlight whole words (although blank spaces within a string are not
highlighted). If no instance of the string is found, a message to that effect is
displayed.
Look at the highlighted box at the very bottom of the screen. The prompt
"MARKED +" tells you that more occurrences of marked text follow. The arrow
direction-+, "', or .,. +-indicates the direction of additional marked text. Press
f1iJ to move to the next screen containing the marked string. Use ~ to locate
the previous screen with the highlighted text.
When you reach the last screen with an instance of the string, the directional
arrow for marked text is .,. and pressing (lID causes an alarm to sound.
4-16
SEP
'~5
4 Easy View
INTRODUCTION (cont)
The specific network address includes information required to
establish the path required to pass information to and from
logical functions (NAUs) operating in some PHYSICAL UNIT l1li or
NODE.
All of the information related to the network address must be
included in the S~stem Generation (SYSGEN) and becomes part of
the SYSTEM SERVICE CONTROL POINT (SSCP) that controls all of the
resources within the network. Network Addressable Units include:
USERS
PERSONS
- APPLICATION
- PHYSICAL UNITS
LOGICAL UNITS (
- SYSTEM SERVICE CONTROL POINTS (SSCPs)
Figure 4-15 All words that contain the specified string-pu-are marked in
reverse video. Press [§D and
to view additional screens with marked text.
lim
Similarly, when the cursor is at the first screen containing the string, the
directional arrow for marked text is "" and pressing ('lID causes an alann to
sound.
To "unmark" the text file, press S again. Clear the text-entry line by pressing
8. Press 8 to execute. All highlighting is removed from the text.
4.5
Additional Easy View Functions
There are additional capabilities related to Easy View which are not essential to its basic
operation.
(A) Changing Other Program Setup Parameters
The on -line editing feature allows you to modify selected line setup parameters. In
some cases, you may want to change other default Setup menus for a selected
program. These changes to the configuration of setup menus are made in Program
mode.
SEP '95
1.
Select the program from an Easy View menu and press 8 to load the program.
Or, use §!1-8 to load and run the source version of the program-see Section
4.5(C).
2.
Once the initial Run - mode screen is displayed, press ~ and then ~ to enter
Program mode.
4-17
INTERVIEW 8000 Series Basic Operation: 951-80424 -01
3.
Enter the appropriate setup screens and make any necessary changes.
4.
Press~.
The program will run using the new setup criteria. Since Easy View
always reloads and runs the hard -disk version of a program, do not reenter Easy
View to run the program or these changes will be overwritten by the default
parameters stored with the original program.
(8) Saving New Setup Parameters
All AR-supplied application programs that you can load and run from Easy View are
stored on the hard disk as linkable-program (LPGM) files. If you anticipate
frequent use of a program with changes to the Setup menus, you may replace the
original LPGM file with your newly configured version using the same pathname.
Then, you can select and run the new version from Easy View. See Section 15 for
information on the File Maintenance Save command and linkable-program files.
1.
Select the program from an Easy View menu and press 8-8. The full
pathname of the program's LPGM file is displayed toward the bottom of the
screen. This is the pathname you must use for your modified version.
2.
Press ~ to load the program.
3.
Once the initial Run - mode screen is displayed, press ~ and then ~l to enter
Program mode.
4.
Enter the appropriate setup screens and make any necessary changes.
5.
Press S, then the FMAINT softkey to access the INTERVIEW's File
Maintenance screen. When the program was loaded from Easy View, the File
Maintenance screen was updated as though the program had been loaded from
that screen. The current directory should be the one containing the program's
file, and the program's filename should be the default entry in the Name field for
most commands.
6.
Select SAVE as the command. Confirm the entries in the fields on the screen.
The Type: field should show !·~f~i'. The entries in the Drive and Name fields
should correspond to the name of the file displayed in step 1. Press (3. (If you
need to modify the filename, remember that filenames are case-sensitive.)
NOTE: You may also create multiple versions of a program to
appear as separate entries in the same Easy View menu. See
Section 20.
4-18
SEP '95
4 EasyView
(C) Additional Menu Keys
There are two more key combinations that operate on Easy View menus:
S-s Displays the full pathname of the file associated with the selected menu
entry.
§) -§3 Active when the selection bar is positioned over a menu item whose
designated action is to load and run a program. Press S-§!3 to load and
run the source version (.s extension) of the program-when it has been
provided-instead of the linkable-program version. In Program mode, the
spreadsheet program is available for viewing and modification.
4.6
Installing Easy View Updates
Easy View updates are not contained on the system or user disk of new system software.
For information on when Easy View updates accompany your purchase of the latest system
software, contact Customer Service.
The Easy View menus and programs are contained on several floppy diskettes. Follow
these steps to install Easy View updates to the hard disk:
Caution: The following installation procedure will cause the existing Easy
View menu structure and any existing program files with names that match
new programs to be overwritten. This means that any changes to Easy View
that you have previously made via the Easy Vrew Maintenance installation
procedure will be lost.
1.
Insert a diskette in Floppy Drive 1, the left- hand drive. (It does not matter in which
order you duplicate the disks.)
2.
If you are currently in the Easy View menus, press ~ to exit. Once in Program
mode, if any screen other than the Program Menu appears, press S. From the
main Program Menu, press UTIL, DIMAlNT to access the Disk Maintenance screen.
3.
Now press the DUPDlSK softkey to set up the Duplicate Disk Command. The From Disk
on the screen should show
; select.' in the To Disk Number: field.
Number: field
4.
Press §J, then GOAHEAD to begin duplication of the first diskette. When the
duplication is completed, the prompt '"'Insert Next Disk - - Depress Fl Key To
Continue" will appear on the status line toward the top of the screen.
SEP '95
-,---------,,------
4-19
INTERVIEW 8000 Series Basic Operation: 951-80424-01
4-20
5.
Remove the floppy disk from the drive and insert the next disk. Press GOAHEAD again.
Repeat this process until all of the Easy View diskettes have been duplicated to the
hard disk.
6.
To see the new Easy View menus, power the unit off and then back on, or press
[3-8-11m to reset the INTERVIEW.
7.
If you want programs you had previously installed in the old Easy View menus to
appear in the new Easy View menus, you must use the Easy View Maintenance
program to reinstall them. See Section 20.
SEP '95
5 LineSetup
5 Line Setup
SEP '95
5-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Line Setup
I
MODE:
Select Mode'
SOURCE:
Select Source of Data:
MONITOR
I
CODE:
BITS:
EM DCE
BERTDTE
UNE
BERTDCE
Rec:
Disk: F\.OPPYI FLOPPY2 HRD DSK
File:
ASCII EBCDIC IPARS BAUDOT EBCD SElEcm XS_3 JIS7 Jlsa
Select Number 01 Bits Per Character.
S BITS 7 BITS 6 BITS 5 BITS
Select Format:
~~
r
T
I
Enter Sync Cha for mai n menu
At
DATA
1
77
STATS
••
_ _ _I
I
DSP WND NO DISP
Figure 6-29 Display Window is useful for tables, as in this SNA Statistics example.
The DSP WND token, when present, is located on the first rack of Run - mode softkeys, as
shown in Figure 6-30.
NOTE: In the absence of display routines (or softkey prompts) in a
spreadsheet program, the Run-mode DSP WND token will not appear
on any softkey rack. In this instance, if you selecdf;t;;;;,1~~~m;; as
the display mode on the Display Setup menu, the Display Window
will be the initial screen during Run mode. but it will be blank. If you
move to a different display screen, you will not be able to return to
the Display Window.
Figure 6-30 Including display routines or PROMPT actions in a program causes the DSP WND token to
appear in Run mode.
6-24
SEP '95
6 Run-Mode Display
6.9
User Trace
There are seven trace buffers in addition to Program Trace. Select anyone by specifying a
user-trace number under£~~Bidisplay mode on the Display Setup menu, as
shown in Figure 6-31. These buffers are similar to the .Program 1l:ace buffer. Messages
are appended to the end of the buffer. Unless its size is increased, a user-trace buffer
maintains a maximum of 4,096 characters, equivalent to four full screens when every
character space is used. (The size of user-trace buffers may be increased to a maximum
of 16,381 elements via the #pragma tracebuf preprocessor directive.) In Freeze mode you
may scroll through the buffer using the cursor keys. The difference between user traces
and Program 1l:ace is that user traces are created only via C trace{, tracec, and traces
routines. See Section 60 for an explanation of the trace routines and the #pragma tracebuf
directive.
Figure 6-31 The initial display in Run mode will be user trace number three.
NOTE: In the absence of spreadsheet-program uses of user traces, a
Run-mode trace token will not appear on any softkey rack. In this
instance, if you select~~i~ the display mode on the
Display Setup menu, the specified user trace will be the initial screen
during Run mode. but it will be blank. If you move to a different
display screen. you will not be able to return to any user trace.
When a user-trace buffer is written to in a spreadsheet program, a Run -mode token will
appear for that buffer. The location of the token depends on the number of user buffers
used. If only one user trace is used, a token indicating the trace number will appear on the
first rack of softkeys, as shown in Figure 6-32.
FIgure 6-32 When only one user trace is used, its token appears on the first rack of softkeys.
SEP '95
6-25
INTERVIEW 8000 Series Basic Operation: 951-80424-01
If more than one user trace is written to, a USER TR token on the first rack provides access
to the next rack containing tokens for all used buffers. See Figure 6-33.
Figure 6-33 To access trace buffers when more than one has been written to, press USER TR.
Use the set_utraceJkey )abel routine to modify Run -mode softkey labels for the user
traces. See Section 60.5(C).
Figure 6-34 shows a trace created via C trace! routines. Note the fields in reverse video,
one of the attributes available to the user with trace[ and displayf. Attributes are not
available with softkey TRACE and PROMPT actions. Another advantage of the user (trace[)
trace is that it can use the screen more economically. Where the softkey TRACE action
assigns each message to a new line, trace! does not automatically generate a new line. A
series of trace! messages may be written across the width of the screen. More information
can be stored on a single screen.
DeE SET
DCE
DTE
DCE
DCE
PAD Reca 11
Data Forwarding
Idle Timer Dela~
Ancillar~ Device
Service Signals
Action On Break
Terminal Flow Cntrl
PAD Echo
READ
PARAM IND PAD Echo
PAD Echo
SET
INV CLEAR
DL.
, or
or i&J!IEiiti
bits rounded to the nearest byte. A block is a component of a test: complete tests
often are measured in blocks.
CAUTION: The definition ofa block varies from standard to standard
and from BERT tester to BERT tester. Some standards define a block as
the pattern length while others specify 1,000 bits. The user must
ascertain and then select the proper definition.
When a !.iii.!BaJJ.1 or ~~~ttij1 pattern is chosen,~1";tl means one
fox message or one message buffer. The mfi'Rt;; selection is not valid for the
~i$j~®[;;I~!t.llIlliMWBrl pattern: a block in this pattern always is a set number of bits.
When a pseudorandom pattern is chosen, the message is one cycle of the pattern.
The shortest pseudorandom block is 63 bits, while the longest block is 32,767 bits.
In half-duplex BERT. each transmission is one block. The line turns around
following each block. After turnaround, the test continues.
11-13
SEP'95
---
._---_.
__ _----_.._----_._----------------------..•
iNTERVIEW 8000 Series Basic Operation: 951-B0424-01
(G) Test Length
Tests are measured in blocks, bits, or seconds. They can also be !iM;JIfIJB1Ii l;I,.
The Test Length:
selection brings up a four-digit # field that accepts
entries from 1 to 9999. The shortest pseudorandom block is 63 bits, so the shortest
pseudorandom test that is one block long is also 63 bits. The longest test measured in
blocks will be 9999 times the longest pattern (32,767), or 327,637,233 bits.
The Test Length: jJr~l~ttii~;'i field also brings with it a # field, with five places for
numbers from 1 to 99,999. The maximum number of seconds comes to slightly more
than twenty-seven and three-quarter hours.
If Test Length: if\!;;*lSv;~ii*l~;~;:lili is selected, a # field appears with these rotating
selections:
~!1~t,~1" andii~ft1.;.
(H) Automatic Error Injection
Errors can be injected in a bit pattern automatically at a preselected rate. (They may
also be injected manually from the keyboard: see Section 11.7 below.) The Error
Injection Rate field defaults to SE-5, equivalent to 5 errors per 100,000 bits. The two
fives are variables in this formula. The first five is the error rate and can be
overwritten with numbers in the range of 0-9. The second five is the negative
exponent and can be changed to any number in the range of2-9.
Read the "E-" in the formula as per 1O-to-the -exponent bits. For example, IE - 2
means 1/102 or 1 error per 100 bits. OE-6 means OlIOS or no errors per 1,000,000
bits, equivalent to zero. Using 0 as the first variable is equivalent to injecting no
errors and, in effect, disabling the field.
The highest automatic-error rate selectable would be 9E-2 or 9/102 or 9 errored
bits per 100 bits. The lowest rate of injected errors would be lE-9 or 1/109 or 1
error per 1 billion bits.
11.6 Transmission Format: Line Setup Menu
Certain selections on the Line Setup menu will affect the pattern of bits transmitted
during a BERT test. The screen is illustrated in Figure 11-4.
(A) Code
If your BERf pattern is a fox message or a user-defmed message that contains
alphanumerics, the Code that you select on the Line Setup menu will affect the
pattern of bits in your test. If your test involves sync characters, remember that the
bit pattern for s" s" is different for ASCII and EBCDIC.
Testers on either side of a transmission link should be configured for the same code.
11-14
SEP '95
11 Bit Error Rate Testing
(B) Bits
Select the number of information bits. This field is invalid for pseudorandom and
alternating 1/0 BERT patterns in m~ format In all other BERT configurations,
characters are formed according to the bit-number specified here.
(e) Parity
For 5, 6, or 7 information bits in async or isoc format, you may select the type of
parity. (For 8 information bits, even, odd, or no parity is available in async or isoc
format. Eight bits plus mark or space parity is not available in any format.) The
parity bit is additional to the information bits.
The BERT test transmits and checks parity. It calculates parity on the data bits it
expects to receive, not the actual data bits. This is to prevent an errored data bit from
causing a parity error and being counted twice as a result.
(D) Format
1.
Sync. If Format: 1aI~~ is selected on the Line Setup menu and a pseudorandom
(or alternating I/O) pattern is the BERt Setup selection, the pattern will be
transmitted bit for bit without synchronization or character-framing. The Line
Setup selection fields from Code down to (but not including) Bit Order/Polarity are
invalid.
If a character-oriented (fox or message-buffer) pattern is selected on the
BERT Setup screen, the precise bit pattern will be determined partly by the Code,
Bits, and Parity selections on Line Setup. The fields from Format:
down to
Bit Order/Polarity are invalid for BER1; however. Sync characters are entered on
the BERT Setup screen. See Section 1l.5(E).
2. BOP. This softkey is nonfunctional. The selections default to the same as if
Format:
were selected.
3. Async. If Format:l~~ti is selected on the Line Setup menu, stop bits (ones) and
a start bit (zero) will be added after every fifth, sixth, seventh, eighth, or ninth bit
in the BERT pattern, depending on the Bits and Parity selections on Line Setup.
This start/stop-bit framing applies to pseudorandom patterns as well as to
character-oriented patterns.
Do not run the alternating 110 pattern if you have selected asynchronous (or
isochronous) start/stop- bit framing on Line Setup.
4. Isoc. This is a cross between async and sync. It uses asynchronous start/stop-bit
framing; but unlike async, internal clock (if selected) will transmit clock pulses on
the clock lead(s) for use by the other device on the interface.
SEP '95
11-15
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(E) Clock
If clock is to be supplied by a modem during the test, you can select Clock:
If no external clock is to be supplied, select
or
}J,~g'{fii and the correct speed or speeds.
Mlf~fli;ti;i\.
Note on synchronous and BOP operation: The INTERVIEW can
transmit using internal clock (SCTE) when it is emulating a DTE;
but in order to display its own transmit data as well as receive data,
it must be connected to a modem or other DCE device that is
providing scr and SCR clock.
If you are have selected Mode: t:.II._l:;wt. i and external clock is
not available for synchronous or BOP operation, choose Clock
Source:::*JW~'ll~:~jI and patch SCTE to SeT.
(F) Bit Order/Polarity
The pattern of bits in sync and async tests will be affected by the selection in the Bit
Order/Polarity field only if a character-oriented (fox or message-buffer) pattern is
selected on the BERT Setup screen.
11-16
SEP'95
r
c
11 Bit Error Rate Testing
Table 11-4
Sync or Async BERT (Une Setup screen)
FORMAT:
SYNC
ASYNC
ISOC
Mode:
BERT DTE or
BERTDCE
BERTDTE
orBERTDCE
BERTDTE
orBERTDCE
Code:
EBCDIC, ASCII,
EBCD,XS-3,
IPARS, SELECTRIC
EBCDIC, ASCII,
EBCD,XS-S,
IPARS, SELECTRIC
EBCDIC, ASCII,
EBCD,XS-3,
IPARS, SELECTRIC
Bits:
8,7,6,or5
8,7,6,or5
8,7,6, a5
Parity:
none
none, even, a odd;
none, evan, or
odd; marnor
space (exceptS
bits)
mark a space
(except 8 bits)
Stop bits:
N/A
10r2
1or2
Clock source:
external, internal,
or internal split
internal or
internal split
external, internal,
or internal split
Speed:
selectable
(except external)
selectable
selectable
(except external)
Bit order/polarity:
nonnal, rev-nor,
nor-jnY, rev-jnY
normal, rev-nor,
nor-jny, rev-jnv
normal, rev-nor,
nor-inv, rev-inv
~,
11.7 Run Mode: Keyboard Control
Whenever you press S, the INTERVIEW will begin to operate as both a BERT
generator and analyzer.
It will begin immediately to transmit the bit pattern chosen on the BERT Setup menu
according to the format entered on the Line Setup menu. The pattern will repeat until the
test ends: see Test Length, Section 11.5(0).
(A) Freezing the Test
The pattern can be interrupted from the keyboard. Pressing 8
or 9 will drive
the analyzer out of sync and stop the counters. Freeze mode retains the latest results
display on the screen (Figure 11-8). Hitting 1-1 a second time will unfreeze the
analyzer and resume the count from the frozen readings.
(8) Restarting the Test
The 8
SEP '95
key restarts a frozen test.
11-17
INTERVIEW 8000 Series Basic Operation: 951-80424-01
To restart a test while it is running, use the (EJ softkey, labeled RESTART. This restart
also reinitializes the syncing process. To clear and restart the counters, press @
RESET. Softkey selections in Run mode are illustrated in Figure 11-8.
Hitting 8
and ~ will also restart everything-test, syncing process, and counters.
(C) Manual Errors
You may introduce errors into the BERT transmission one at a time via softkey. One
errored bit will be sent each time the operator presses §J (INJ1ERR).
(D) Automatic Error Injection
Automatic error-injection can be turned on and off by softkey. Press [EID, ERR INJ, to
toggle this function. See Section 11.5(H), for an explanation of error rates.
(E) Clearing the Results Screen
To clear the counters without losing sync, press ®], RESET.
(F) Restarting the Test Function
The test function length was determined on the BERT Setup screen to be measured
in blocks, bits, or seconds, or to run continuously. Pressing [Hl, RESTART, restarts the
test and reinitializes the syncing process.
(G) Disabling Transmission
You may prevent the BERT pattern from being transmitted while the INTERVIEW
analyzes a received pattern. If the unit is in i~1ii:~_Piri{0i. mode, move the breakout
switch for pin 2 on the test - interface module (TIM) to the open position. If the unit
is in ~N~%~!'!I; mode, open pin 3 instead.
11.8 Run Mode: Status Line
The status line of the Run-mode BERT display, shown in Figure 11-8, identifies the
BERT test and the parameters chosen on the line Setup menu. The INTERVIEW is
using these parameters both to transmit and to analyze. Figure 11-8 shows a BERT 511
test in EBCDIC code; with 8 information bits, no parity, and full duplex pattern; and in
synchronous mode.
11-18
SEP '95
11 Bit Error Rate Testing
PATTERN SYNC STATUS:
Figure 11-8 The BERT Results screen displays setup status, receiver -sync status, error injection rate,
seven counters, and three rate calculations.
11.9 Run Mode: Statistical Display
BERT results are displayed on the Run-mode BERT Statistics screen. You may access
this display by pressing the STATS softkey on the top-level softkey rack, followed by the
BERT softkey.
BERT counters increment to 264 -1, or approximately 1.8 times 1019. For practical
purposes these counters are unlimited.
Each counter enters Run mode at O.OOOOEOO. The top of Figure 11 ~9 shows the block
counter on the verge of rolling over to a new exponential value. The bottom of the figure
shows the effect of the next block received: the exponent has incremented so that the
counter is being updated on every tenth count instead of every one. The counter will be
updated next when ten new blocks have been received.
Figure 11·' This is a before-and-after illustration of the block counter receiving its lOO,OOOth block.
Three of the counters have Rate displays adjacent to them. See Figure 11·8. These rates
are to be read in the same way you would read an entry in the Injection Rate field on the
BERT Setup menu (see Section 1l.5(H»: 9.0000E-3 means 9 times 1/103 or 9 errors
11-19
SEP '95
--
-------------------------------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
per 1,000 bits. Rates are displayed in real time. They enter Run mode at O.OOOOE-O and
remain at zero until a bit error or block error or errored second occurs. Once an error
rate is posted, the displays will behave like decrementing counters: while the number of
bits, blocks, or seconds increases steadily, the rate of error will decrease. The top of
Figure 11-10 shows a Rate display for bit errors that stands at 1.0OOOE-4 or 1 error per
10,000 bits. When the next bit arrives, unless it is an error the rate will decrease. The
bottom of the figure shows the action of the display as the rate of error decreased: 1 per
10,000 became 9.9999 per 100,000 (9.9999E-05).
:S'i;[{E~~S!,ii{?···
;:aiT~R~~9:>·';(
.....
.J;;
l.4080E21
1.00021E-04
9.9999E-05
Figure 11-10 As the rate of error decreases, the minus-exponent grows larger.
(A) Test Seconds
This counter is incremented once for every second the test runs.
(B) Blocks Sent
The current number of blocks sent is recorded here. A block is defmed in Section
1l.5(F).
(e) Blocks Received
This shows the current number of blocks received. If this count is not incrementing,
the INTERVIEW is not syncing on a pattern and the PATTERN SYNC STATUS field on
the lower right of the BERT statistical display screen should say OUT OF SYNC.
(D) Bit Errors
The bit sequence received is compared with that expected in accordance with the
parameters chosen on the Line Setup menu and the BERT Setup screen. The count
of received bits that do not match the expected pattern is displayed here. This
counter value in relation to total bits is given in the Rate column at the right of the
counter, expressed in errors per exponent of 10.
(E) Blocks In Error
The number of blocks in which one or more bit errors have occurred is recorded. A
rate calculation of this value to total blocks received is given to the right of the
counter in real time.
NOTE: If two testers are being used, verify that both are defining
block size in the same way. See Section 11.5(F).
11-20
SEP '95
11 Bit Error Rate Testing
(F) Error-Free Seconds
This counter will increment when the Test Seconds counter increments until one or
more errors have been found during the last second. The rate of this counter value
compared to total seconds is given to the right of the counter in real time.
(G) Number Of Faults
"Fault" has different meanings for full and half duplex. In full duplex, a fault is
recorded whenever an error is detected in more than 25 percent of the bits received
over a certain period of time (approximately 16 bits in 64 contiguous bits). This
percentage is considered sufficient to indicate that a bit time has been missed.
In full duplex, if Resync:~. has been selected on the 1i'ansmit Mode menu the
INTERVIEW's receiver will resynchronize every time a fault is found.
In half duplex, a fault occurs when the analyzer sees bit transitions that indicate a
new block of BERT data but fails to recognize the sync pattern or the sync character.
(H) Error Injection
The status of Error Injection may be ON or OFF; it is toggled manually by the
softkey. In Run mode it is turned on and off by the (EJ softkey.
ERR INJ
(I) Injection Rate
This status field simply reports the error-injection rate that the user has entered on
the BERT Setup menu.
(J) Receiver
BERf analysis begins when the receiver synchronizes on incoming data. The
PAlTERN SYNC STATUS line on the results screen reports on receiver status. At all
times during a BERf run, the line displays one of two messages, IN SYNC or OUT OF
SYNC.
Once synchronization is established, the receiver can go out of sync only if Resync:
is selected. During the out-of-sync condition, data is not analyzed for error.
When the resync function is turned off, the IN SYNC condition, once established, will
remain in effect until the test ends. This setup is appropriate for relatively brief tests
on noisy circuits.
11.10 Loopback at the Transmitting INTERVIEW
The INTERVIEW can analyze its own BERT transmission without being connected to the
data interface. This is a good way for you to become familiar with the BERf test
procedure before you apply it to a system.
~.
f:.
SEP '95
11-21
INTERVIEW 8000 Series Basic Operation: 951-80424-01
With the interface disconnected, power up the unit and select Mode:
on the
tine Setup menu. Then select a configuration compatible with the specifications in
Table 11-2 and Table 11-3. Select internal clock.
Press~.
You will see only the first two counters, Test Seconds and Blocks Sent,
incrementing. This is the way the Run - mode display will appear when you are sending
the BERT pattern to another BERT analyzer. No statistical analysis is being done because
the BERT analyzer is not seeing the transmitted pattern. The report on Receiver status is
OUT OF SYNC.
Press S. On the breakout box on the test-interface module (TIM), patch ID to RD.
Press~. This time you will see the first three counters incrementing: Test Seconds,
Blocks Sent, and Blocks Received. The receiver is now IN SYNC. The INTERVIEW's
BERT analyzer can see its own transmission but it is unlikely that it win find any errors in
its own data.
Use the fITI key to introduce errors into the transmission. Observe the next three counters
and the rate measurements alongside them. The §] key will not introduce a fault.
Run another test into which you have injected automatic errors. An Error Injection Rate
entry of lE-5 on the BERT Setup screen will produce one errored bit for every 100,000
bits and a bit-error rate of 1.0000E-5.
11-22
SEP'95
12 Standard Interfaces
12 Standard Interfaces
The INTERVIEW contains a universal logic interface that supports data rates into the
megabits-per-second range. Physical interfaces that are adapted to the various data rates are
provided in the form oftest-interface modules (or TIMs).
The INTERVIEW 8000 Series offers the user a choice of standard TIMs; see Table 12-1 for the
TIM (and, for some units, MUX board) selections available for each unit. The TIM the user selects
will have its own specific documentation with it. For optional TIMs currently available, see Section
13. Some interface module provides breakout patching and switching for each lead.
TIMs are modular and simple to install. There are two steps to installing an interface module:
1) With tbe unit powered off, insert the TIM into the module slot at the rear of the unit and press
until it latches; 2) apply the proper LED overlay in position on the front of the unit above the
screen. The overlay is a flexible plastic strip with a small tip on each end that fit into notches in the
front panel. The overlay covers the front-panel green-red LEns and gives them
connector-specific identification.
The test-interface module locks into place in the back of the unit and a small release bar must be
pressed to unlock it. The rear of the unit is illustrated in Section 1 of this manual. The interface
softkey (fru on the Setup Menu) will reflect the type of TIM installed, such as RS232, \las, RS449,
RC8245, TTL, etc.
Table 12-1
Test Interface Module Standard Selections for INTERVIEW 8000 Series Units
MODEL
INT -951-0X2-ID<4000
INT -951-1X2-0~OOO
INT -951-1Xz-O~OOO
INT -951-1Xz-691Xs01
INT-951-2X2-0~OOO
INT -951-2X2-0~OOO
<'~,
~-""'-efY'
1
UNIT
MUX
"stTIM
(5eIect one of:)
INTERViEW 8100
TURBO
or Single- Port V:35
INTERVIEW 8200
TURBO
()7
INTERVIEW 8200R
TURBO
or Single-Port V:35
INTERVIEW 8200-8
TURBO
or Single- Port V:35
INTERVIEW 8600
TURBO
or Single- Port V:35
INTERVIEW 8600R
TURBO
or Single-Port V.35
Addn'lTIM
(Select one of:)
Single-Port ElA-232
Single-Port ElA-232
Single-Port V:35
Single-Port EIA - 232
Single-Port E1A - 232
Single-Port EIA-232
Single-Port EIA-232
Plus ISDN srrIU Basic Rate TIM with MUX
SEP '95
12-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Table 12·1 (continued)
Test Interface Module Selections for INTERVIEW 8000 Series Units
MODEL
!NT-951-2X2-X3X42XsO
UNIT
MUX
1st TIM
(Select one of:)
INTERVIEW 86OO-P
Dual-Port Tl wI Dual-Port T1 (23B+D)
TURBO
or Dual-Port 0.703 wI Dual-Pon 0.703 (30B+D)
Addn'ITIM
(Select one ot)
Single- Pon EIA - 232
or Single-Port V.35
INT-951-2X2-X391XsX71 INTERVlEW8600-1
DuaI-PortTl wI Dual-Port Tl (23B+D)
TURBO
or Dual-PortO.703w/Dual-PonO.703(30B+D)
Single- Port EIA - 232
or Single-Port V.35
INT-951-3Xz-0)4000
INTERVIEW 8700
TURBO
or Single-Port V.35
INTERVIEW 8700R
TURBO
or Single-Port V.35
Single-Port EIA-232
Single-Port EIA-232
tNT -951-3Xz-X3X4300
INTERVIEW 87oo-SS7 Dual-Port Tl
TURBO
wI Dual-Port Tl (23B+D)
and Dual-Port DS-OA
or Dual-Port 0.703 wI Dual-Port G.703 (30B+D)
and Dual-Port Co-Directional
or (either MUX)
wI Dual-Port V.35/EIA-530
(449)/EIA-232
tNT -951-4X2-0)4000
INTERVIEW 8800
TURBO
Single-Port EIA-232
or Single-Port V.35
INTERVIEW 8800R
Single-Port EIA-232
or Single-Port V.35
TURBO
INTERVIEW 88OO-FR
TURBO
INT-951-4X2-XsX4000
Dual- Port Tl
or Dual- Port G.703
or (either MUX)
Dual-Port Tl (23B+D)
Dual-Port G.703 (30B+D)
Dual-Pon V.35/EIA-530
(449)/EIA-232
or Single-Port EIA-232
or Single-Port EIA-449
or Single-Port V.35
wi Dual-PortTl(23B+D)
and Dual-Port DS-OA
or Dual-Port 0.703 wi Dual-Port G.703 (30B+D)
and Dual-Port Co-Directional
or (either MUX)
wi Dual-Port V.35/EIA-530
(449)/EIA - 232
INTERVIEW 8800-GSM Dual-PortTl
TURBO
INT -951-4XrXsX45XsC1 INTERVIEW 8800-MTS ISDN SfTIU MUX Dual-Port V.35/EIA-530
TURBO
(449)/EIA-232,
ISDNSfTlU,
andeither Dual-Port Tl2
Dual-Pon Tl (23B+D)
and Dual-Port DS-OA
or Dual-PonO.7032 Dual-Port 0.703 (30B+D)
750 or 1200
and Dual- Pon Co- Directional
1
2
Plus ISDN SfTIU Basic Rate TIM with MUX
MUX board has mounted crystal configured for proper data rates
12-2
SEP '95
13 Optiona/lnterfaces
13 Optional Interfaces
In addition to the standard TIMs available. there are several optional TIMs available for purchase.
Table 13-1 lists currently available TIMs and their option numbers. Telenex offers a TIM expansion
shelf (OPT - 951-42 -1), which connects up to five TIMs for easy use-no changing TIMs when
changing single-port interfaces; just change your connections to the line. Note that dual-port and
ISDN TIMs are not compatible with INTERVIEW 8100 units. For further information, contact
Customer Service.
Table 13-1
Optional Test Interface Modules
TIM
v.ss (North America)
v.SS (MetriC)
TillSON PRI
OPT -951-510-1
OPT -951-510-2
OPT -951-511-2
RS-449
OPT -951-512-1
X.21
RS-232
OPT-951-513-1
OPT -951-514-1
RC-8245 (RS-485, NRZI)
OPT -951-521-2
G.703/1SDN PRI
OPT -951-524-1
OPT -951-545-1
TTL
SEP '95
Option Number
Dual-Port G.703/ISDN PRI (75 ohm)
OPT -951-555-1 (TIM with MUX)
OPT -951-564-1 (TIM only)
Dual-Port G.703/1SDN PRI (120 ohm)
OPT -951-555-2 (TIM with MUX)
OPT -951-565-1 (TIM only)
Dual-PortT1/1SDN PRI
OPT -951-555-3 (TIM with MUX)
OPT-9S1-627-1 (TIM only)
Dual-Port G.703/1S0N PRI (75 ohm)
plus ISDN Basic Rate Interface
OPT -951-556-1 (TIMs with MUXes)
Dual-PortG.703/1SDN PRI (120 ohm}
plus ISDN Basic Rate Interface
OPT-951-556-2 (TIMs with MUXes)
Dual-PortT1/1S0N PRI
plus ISDN Basic Rate Interface
OPT -951-556-3 (TIMs with MUXes)
ISDN smu (TIM, MUX, & Handset)
OPT -951-563-1
ISDN smu (BRI Add-on TIM & MUX)
OPT-951-566-1
Dual-Port DS-OA
OPT -951-569-1 (TIM with MUX)
OPT-951-571-1 (TIM only)
Dual - Port G.7603/64KBPS Co- Directional
OPT -951-570-1 (TIM with MUX)
OPT -951-572-1 (TIM only)
Dual-Port V.35/EIA-530(449)/EIA-232
OPT-951-620-1 (TIM with MUX)
OPT-951 -620-2 (TIM with MUX)
OPT-951-621-1 (TIM only)
OPT -951-621-2 (TIM only)
13-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
13-2
SEP '95
14 Disk Maintenance
14 Disk Maintenance
SEP'95
14-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Disk Maintenance
Depress ~Key to Execute Command
Select Utility Command:
I
F1
FORMAT
"""
--
Disk Name:
II
II
F2
SUMMARY
II
F3
TRANSFR
I
II
F4
DUPDISK
F5
INT10
I
F6
II
F7
INT20
II
I
Fa
I
INTERVIEW 10 PLUS TRANSFER
INTERVIEW 20 PLUS TRANSFER
(drive description)
FORMAT DIS!<
From: FLOPPY!. FlOPPY2
Instrument: DLM. ASYNC TERM. X.25 MONITOR.
SNA MONITOR. BAUDOT. ODCMP
File:
To: FLOPPY1 FlQPPY2 HRD DISK
""""" """"" ~ """"""""
XXXXXK Bytes Available
(Status Field)
I Drive Type: 20M II
II
<14M R! 4! M Kl <13M T1 82MS1 41MS2
I
File:
- - KBytes Reliel'\Ied For Data Acquisition
DUPUCATE DISK
Verify Passes: _
From Disk Number: FLOPPY! FLOPPY2 HRD DSK
To Disk Number: FlOPPY! FLOPPY2 HRD DSK
DISK SUMMARY
Disk Number: FLOPPY! FLOPPV2 HRD OSK
Oescript:
Ei~~1l1ll
(filename)
Summary of FlOPPYj FLOPPY2 HRD DSK
Dil. e&gwdUim
BITIM
1Sec 2K
CHOAT lOOmS 16K
toms
lmS
c!:~I211l11i
XXX.XK XX%
64K
!OCUS
!OuS
IuS
XxS?2
Used:
Free:
Overhead:
Bad:
Total:
XXX.XK
XXX.xK
XXX.xK
XXX.xK
XXX.xK
XX%
XX%
XX%
XX%
XX%
XlOCXX XX%
xxx.xK XX%
XlOCXX XX%
XXX.XX XX%
XXX.xK XX%
XXX.xK XX"k
XXX.xK XX%
XXX.XK XX%
XXX.XX XX%
XXXXK XX%
1 Drive description displayed from drive; SCSI drive description includes
revision level.
rY
DATA TRANSFER
From: ~Ii-
2 K the time licks were disabled in the data. the lick resolution will be
followed by a question mark.
FILE
Disk Number: FLOPPY! FL0PPY2 HAD OSK
Source Fije:
I
Type: B'IMAGE CHARBUF
Start At Bloc!<:
9..9999999999
Number of Blocks:
,
Disk Number: FlOPPY! FlOPPY2 HRD DSK
Start At Block:
.lL9999999999
Number of Blocks:
TO:!
II
~
Disk Number: FLOPPY! FLOPPY:< HRo DSK NEWDISK
Destination Fife:
Disk Number: FLOPPY1 FLOPPY2 HRD DSK NEWDISK
J
Start At: BEGIN END
Figure 14-1 Disk Maintenance menu.
14-2
SEP '95
I
14 Disk Maintenance
14 Disk Maintenance
14.1 The Disks
The INTERVIEW 8200, 8600, 8700, and 8800 TURBO units have two disk drives designed
for 3.5 inch double-sided, high-density microfloppy disks; the INTERVIEW 8100 and
the INTERVIEW 8000 Series remote units have one such disk drive. Maximum storage
capacity of each microfloppy is 1.4 Mbytes.
The maximum storage capacity of the hard disk drive in the INTERVIEW 8000 Series
units varies with the installed drive: the standard SCSI drive has a capacity of 240 Mbytes
and the optional SCSI drive has a capacity of 1.2 Gbytes. (Note that hard disk availability
within the industry may increase disk capacity in future units as necessary.)
The drives are referenced by number. Floppy Disk 1 (FDl) is the disk installed in the
left-hand drive. Floppy Disk 2 (FD2) resides in the right-hand drive. The Hard Disk
drive is referred to as HRD.
14.2 Allocating Disk Space
Each disk must be formatted before it is available for data capture. Memory on each
INTERVIEW disk can be partitioned for two types of storage: data acquisition tracks and
a filing system. This partitioning must be performed before information is stored on disk.
The Format command on the Disk Maintenance screen is used for this purpose. This
command is explained later in this section.
14.3 Data Acquisition Tracks VS. the Filing System
Data acquisition tracks are sequential access data tracks which store Bit-Image or
Character-oriented data in block format. Minimum block size is 2 Kbytes, and each
recorded block is numbered and date/time stamped. When data is recorded on disk in
real-time, it can be captured on data acquisition tracks or to a file.
Recorded blocks can be accessed by block number and played back. However, any
subsequent disk recording session to DAT overwrites the contents of the data acquisition
tracks, so it is advisable to save this recorded data to a file using the Data Transfer
command on the Disk Maintenance screen (see Section 14.4). Any subsequent disk
recording session to a previously recorded file will also overwrite the file.
The filing system is a user-created hierarchy of files and directories for storing and
organizing captured line data, setups (menu contents), protocol package data, C code, or
entire test programs. Files are identified and accessed by name (full or relative pathname).
SEP '95
14-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Existing files and directories, descriptive information, and file management commands all
appear on the File Maintenance screen. The File Maintenance screen, file naming
conventions, and file access are discussed in Section 15.
14.4 The Disk Maintenance Screen
The Disk Maintenance screen is part of the Utilities menu group. All selections available
on the menu are shown in Figure 14-1. The default Disk Maintenance screen is shown in
Figure 14-2. Several disk management functions are grouped on this menu (as evidenced
by the function keys in Figure 14-2). Disk formatting, data transfers, and disk duplication
are all performed from this menu. In addition, the menu provides a summary of disk
space for each of the disks associated with the INTERVIEW.
**
isk Maintenance
**
Command:
From: . .
Disk Number:
110
Start At Block: 0
Number Of Blocks~:~9~9~9~---To:
I11III
Disk Number: 110
Start at: 114 4'11
Depress . . . Ke8 To Execute Command
Figure 14-2 The default screen.
The selected command is always posted at the top of the screen. The screen repaints for
each command. Once you have filled in appropriate menu fields, press [§) to execute the
command. In cases where data could be destroyed, you will have the option to continue
the process by pressing GOAHEAD, or to stop the process by pressing ABORT. Status
messages will inform you of any errors that are encountered. Error messages are listed
and defined in Appendix A.
(A) Format Disk
This command (see menu selections, Figure 14-3) is used primarily to prepare floppy
disks for data acquisition and file creation. A new disk must always be formatted
before use.
14-4
SEP '95
14 Disk Maintenance
The hard disk is formatted prior to delivery. It is not recommended that you format the
hard disk If you do want to format it to reallocate storage space, however, be sure
that you know the size of your hard disk before you begin. Use the Disk
Maintenance Summary command to check the size. See Section 14.4(B}. The total
in the right- hand column should approximate 82 Mbytes for the older-model
standard Winchester drive, 240 Mbytes for the present standard SCSI drive, or 1.2
Gbytes for the optional SCSI drive.
CAUTION: Formatting a disk causes loss ofits entire contents. It is
recommended that you write-protect or duplicate any disk you wish to
preserve. Periodic back-up of the hard disk is strongly recommended.
Backup is required prior to fomtatting the hard disk See Section 2.4 for
instructions on backing up the hard disk
Before this command is executed, a number of subfields must be filled in. Subfields
appear when you press the FORMAT function key.
Figure 14-3 New disks must be formatted for data acquisition and file creation.
1. Disk number. Floppy 1, Floppy 2, or Hard Disk must be designated for
formatting in the Disk Number field. Once the disk is selected, a status field
appears to the right, indicating the total number of Kbytes of storage available on
the disk.
NOTE: Floppy 1 Uf_*l) refers to the INTERVIEW's left-hand
micro-floppy drive; Floppy 2 ttE) to the right- hand drive. The
abbreviation tii9;; represents the hard disk drive.
2. Disk name. When one of the floppy drives is selected, the Disk Name field
appears. A disk name is optional; however, it provides a useful identification for
each disk.
SEP '95
14-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 144 Indicate the size of the hard disk installed in your unit.
3. Drive type. When you select Disk Number: ii,iiJ;, the Drive Type field appears on
ST506 units; SCSI units automatically read the jnformation from the drive itself.
See Figure 14·4. Select from 20M L1, 44M Ri, 41M K1, 43M T1, 82M S1, or 41M S2 to
indicate the size of your hard disk; the INTERVIEW 8000 Series defaults to 82M
S1. If you try to format a disk to a size larger than its capacity, you will get an
error message. If you inadvertently format a disk to a size smaller than its
capacity, you may reformat it to the correct size.
4. Allocate space for data acquisition. The next menu field requests an entry for the
amount of space on the disk which is to be dedicated to the data acquisition
tracks. Legal entries in this field are 0 to 1322 for micro-floppies. (Higher
entries will be accepted, but no additional space will be allocated.) If the field is
left blank, no space is allocated for data storage.
Space allocation on the hard disk depends on the size of hard disk installed in the
unit:
•
Seagate 82-Mbyte hard disk
The range for the 82 - Mbyte hard disk is 49240 through 81396. The
minimum amount of space for data acquisition is 49240 (49M). Lower
entries or a blank field will be accepted, but no less space will be allocated.
This means that the maximum amount of space that can be allocated to the
file system is 32768 Kbytes (32M).
The 82- Megabyte hard disk is factory formatted to allocate approximately
49M to data acquisition and 32M to fIle storage.
•
SCSI 240-Mbyte hard disk
The 240- Megabyte hard disk is factory formatted to allocate approximately
207M to data acquisition and 32M to file storage.
14-6
SEP '95
14 Disk Maintenance
•
SCSI 1.2-Gbyte hard disk
The 1.2-Gigabyte hard disk is factory formatted to allocate approximately
119,967M to data acquisition and 32M to file storage.
The amount of space allocated to data acquisition tracks is subtracted from the
total Kbytes available (as listed in the status field on this menu). When disk
space is allocated to data acquisition tracks, the amount of space is always
rounded upwards to an integral number of cylinders. Remaining Kbytes are
automatically allocated to the filing system. At least two cylinders of disk space
(36 Kbytes) are always reserved for the file system on floppy disks. On the hard
disk, a minimum of eight cylinders is required for the file system: 612 Kbytes on
the 82-Mbyte disk.
5.
Verify Passes. The final entry to be made is the Verify Passes: field. This field
defines the number of media verification passes the unit makes during formatting.
The user may now specify a number from 0 to 99; the default is 2 passes. It is well
to note, however, that the higher the number of verifications, the longer the
process will take; also, it is not recommended that 0 be entered, as the process will
then be totally unverified. If the unit is configured for a SCSI drive, this field
disappears as the SCSI drives have their own format/verify procedure.
Press ~ to start formatting. If the disk selected contains data, the warning message
"Formatting disk will destroy data" appears at the top of the screen. Be sure that you
have backed up your data before continuing. Press GOAHEAf) (IE) to continue the
formatting process. Press ABORT ([f!) if you decide not to format. After you press
~, you may not abort formatting since the disk has already been altered.
(8) Disk Summary
Press SUMMARY, select the disk you want summarized, and press ~ for a synopsis of
disk contents. The Summary of field (see Figure 14-5) is updated when you press~,
so that the number of the disk drive being summarized appears in this field.
Several lines of disk information follow with one column for the file system, one for
the data acquisition tracks, and the third for the totals for the drive selected. The
fields in the Drive Totals column are the sum of the fields of the first two columns.
See paragraph 6. below for the summation information of the Total: fields.
1. Description. There are two types of Descript fields. The File System column field
gives the name of the disk as it was entered in the Disk Name field when the disk
was formatted.
The Data Acquisition column field indicates the type of data (BITIM or CHOAT),
the rate at which it was recorded (1Sec, 100mS, 1OmS, 1mS, 100uS, 10uS,or 1uS) or
whether TO bits or RD bits were selected (TOelle or RDctk), and the DAT record
size (2K, 16K, or 64K).
NOTE: If the time ticks were disabled in the data, the tick resolution
will be followed by a question mark.
SEP'95
14-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
**
Disk Maintenance
*
Command:
Disk Number:
III
5ummar!:j of
F i 1 e S'dstem
Sample #001
5.5K
11.0K
19.5K
0.0K
36.0K
15%
30%
54%
0%
2%
III
Data Acquisition
BITIM lmS 2K
1324.0K
1.5K
78.5K
0,0K
1404.0K
94%
0%
6%
0%
97%
Depress . . Ke!:j To Execute .Command
Figure 14-5 Results of a DISK SUMMARY command.
2.
Used. These fields represent the amount of disk space actually used in Kbytes in
and as a percentage of the disk space allotted to each of the column headers: the
file system, the data acquisition tracks, and the total of the selected drive.
In the Drive Totals columns, the amounts of file space remaining are reported.
Note that the total in the right column always equals 100%, while the total in the
left column always is 1440 Kbytes for a floppy diskette. For the hard disk, the
total should be the size of the drive-82 Mbytes, 240 Mbytes, or 1.2 Gbytes. (If
you formatted to a smaller size selection, the total would be the size of your
selection. )
3. Free. These fields represent the amount of disk space "free" or unused in Kbytes
in and as a percentage of the disk space allotted to each of the column headers:
the file system, the data acquisition tracks, and the total of the selected drive.
4.
Overhead. The Overhead: fields indicate storage that is unusable for holding data;
it may be used by the system, for example, as holding critical bookkeeping
information. As with the other fields, these fields are expressed in Kbytes and as
a percentage of the disk space allotted to each of the columns: the file system,
the data acquisition tracks, and the total of the selected drive.
5. Bad. These fields represent the amount of disk space storage that was found to
be flawed during one of the verify passes when the drive was last formatted; this
is unusable space. As with the other fields, these fields are expressed in Kbytes
and as a percentage of the disk space allotted to each of the columns: the file
system, the data acquisition tracks, and the total of the selected drive.
14-8
SEP '95
14 Disk Maintenance
6.
Total These totals are counts of all blocks in the partition and their respective
percentages of the entire drive space. Note that while the total of the
percentages above the Total: fields line add up to (or approximately to) 100%, the
percentages expressed in the Total: fields are not 100% as they are fractions of the
entire drive space used by the File System and by DAT.
(C) Data Transfer
Use this command (see Figure 14-6) to move data from one storage medium to
another. Available media are the following: data -acquisition memory (whether
character or bit-image) on a disk; files on a disk; bit-image RAM ("RAM" on the
Record Setup menu); or character RAM (the screen buffer). Data transfer is
necessary in some cases. For example, data in bit-image RAM, data in the screen
buffer, and data saved to a fIle must be transferred to disk before it may be played
back.
NOTE: 'Transferring data to disk blocks which contain data or to an
existing file will overwrite the previous contents of the disk or file.
Press TRANSFR to display subfields for the command.
1. From RAM, disk, or file. The From field allows you to specify the source of data to
be transferred. When you select [at !~, or ~.t the screen repaints. New
menu fields are explained at the end of this section.
2. RAM. When fifll is seiected, you must specify type of RAM and the number and
location of blocks you want to transfer. See below, subsection 6.
Figure 14-6 The source of transferred data may be RAM, disk., or file;
the destination may be disk or file.
SEP '95
14-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
3.
Disk. This selection refers to the data acquisition tracks on disk. When @U';\ is
selected, you must specify the disk number and the number and location of blocks
you want to transfer.
4.
File. This selection allows you to transfer data out of the filing system. When
is selected, you must specify the name of the file and the disk number on
which it resides. Data in a file is available for later playback.
5. Disk number. Designate the source disk by selecting 1.% (left-hand drive),
~;. (right - hand drive), or i_I;.
6.
Type. The first subfield which appears when lBt is selected is Type. You must
specify ©wm1liil~~: or ~{~~ in the Type field when transferring data from
RAM.
Bit-image RAM is the RAM that is selected in the Capture Memory field on the
Record Setup menu. For "normal" bit-image record, this RAM is 256 Kbyte in
both the 8100 TURBO and 8200 TURBO and 1 Mbyte in the 8600 TURBO, 8700
TURBO, and 8800 TURBO; for "high-speed" bit-image record, this RAM is 256
Kbyte in both the 8100 TURBO and 8200 TURBO, 1 Mbyte in the 8600 TURBO,
2 Mbytes in the 8700 TURBO, and 3 Mbytes in the 8800 TURBO.
Character RAM is the 64 Kbyte screen buffer (or "character buffer").
7.
Start at block. Enter the number of the first block to be transferred from the data
source (whether disk or RAM) in the Start At Block field. (You can observe the
current block number at the top of the display when you are recording data in
Run mode.) Valid entries in the Start At Block field are 0 to 9999999999. If you do
not enter a value, the value will default to zero. Block 0 means that data transfer
will start from the beginning of the data source, regardless of the actual block
number. All other entries represent actual block numbers.
NOTE: It is not necessary to enter leading zeroes in this field. For
example, you may enter 10 instead of 00010.
14-10
8.
Number of blocks. In this field, enter the total number of blocks you wish to
transfer. Valid entries are 1 to 9999999999; however, your entry is bounded by
and limited to the size of the destination media. Again, it is not necessary to
enter leading zero's.
9.
To disk or file. When you transfer data to\";, the data is transferred onto the
data acquisition tracks for later playback. Specify the disk by selecting
(left-hand drive),t~~;(right-hand drive), orj.j'§'W:1 (for use when you have only
SEP '95
14 Disk Maintenance
one floppy disk drive available and are transferring data from one disk to
another.)
When you transfer data to a ~.~. you must indicate the number of the
destination disk as well as the file name. (Either relative or full pathname may
be given.) Specify the disk by selecting 1m (left -hand drive), optional
$Hi (right- hand drive), or fa (for use when you have only one floppy disk
drive available and are transferring data from one disk to another.) If the name
of an existing file is entered, the contents of the file will be overwritten with new
data during the transfer. Data in a file is available for later direct playback.
10. Start at. Specify in this field whether data will be stored on the destination disk
starting at the beginning of the disk or file (overwriting any existing data), or
whether the transferred data will be appended to the end of existing data.
Once you press ~. you may stop the transfer at any point by pressing @
(ABORT).
(D) Duplicate Disk
If both floppy disk drives are operable, this command allows you to make a copy of
full disk contents.
NOTE: Duplicating the contents of one disk onto another destroys
the previous contents of the destination disk.
Press DUPOISK to see subfields for this command. In the From Disk Number field (see
Figure 14-7), select the drive number for the disk to be copied. Select the disk which
will receive the copy in the To Disk Number field; the field defaults to i~ .
NOTE: If the disk receiving data is write-protected, the Duplicate
command will fail. Otherwise, any data on a receiving floppy disk will
be overwritten. Only those files on a receiving hard disk drive with
the same names as those on the sending disk will be overwritten, but
files with new names will be added to those existing on the hard drive.
From time to time, you may need to use the Duplicate Disk command to install new
system software on the hard disk of the INTERVIEW (if present). See Section 2.3.
Figute 14-7 Entire disks may be duplicated on the Disk Maintenance menu.
14-11
SEP '95
-----
-------_._------_._---_._---------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(E) Transferring INTERVIEW 5 Plus, 10 Plus, 15 Plus, or 20 Plus
Data to the 8000 Series
The INTERVIEW Transfer command (explained in Section 14.4(F» allows you to
copy files from a disk recorded with an INTERVIEW 5, 10, 15, or 20 Plus onto the
hard disk of an INTERVIEW 8000 Series unit, or onto a microfloppy. The
INTERVIEW 5/10/15 Plus and 20 Plus Series uses a 3.5 inch double-sided,
double-density disk which can be distinguished from the INTERVIEW 8000 Series
disk because it has a write-protect/enable window (with a plastic cover) but no
second window on the opposite comer.
These disks are compatible (that is, they may be read by any 8000 Series unit) ifthe
INTERVIEW 5/10/15 Plus or 20 Plus on which they were recorded has been
reconfigured so that it records to disk in the correct format.
D
o
Hi h density
in~icator ~
hole appears
on 8000 Series
disks
o
~
/
Write- protect
Window
(disk protected
if open)
~--------------------------~
Figure 14-8 The INTERVIEW 8000 Seriesuses3.5inchquad-orhigh-density,double-sided
microfloppy diskettes.
NOTE: We recommend that you record disks reconfigured for the
512 bytes/sector format (Software Version l.1OA or higher). If you
are communicating with INTERVIEW 5, 10, or 15 Plus field units
which have not yet been reconfigured for this format (still have
Software Version 1.00c with old 1024 bytes/sector format), we
recommend you contact the factory for instructions on reconfiguring
the unit so that data is recorded to disk in the proper format.
Programs for the INTERVIEW 5/10/15 Plus and 20 Plus Series may not be
transferred to disk for the INTERVIEW 8000 Series. Furthermore, neither data nor
programs recorded on an INTERVIEW 8000 Series unit can be copied or read by the
14-12
SEP '95
14 Disk Maintenance
INTERVIEW 5/10/15 Plus or 20 Plus Series. This precludes the storage of data on
the 8000 Series for later analysis on the INTERVIEW 5/10/15 Plus or 20 Plus.
However, a more sophisticated analysis of this data is possible when it is played back
on the INTERVIEW 8000 Series.
All INTERVIEW 5/10/15 Plus files are transferred as ASCII character data,
regardless of the format in which the data was originally recorded. Because of the
conversion in data format, the size of the file once it is transferred may increase by as
muchas5%.
However, all INTERVIEW 20 Plus files are transferred as the same character data
format in which the data was originally recorded. (For example, data recorded on an
INTERVIEW 20 Plus in EBCDIC format would be transferred as EBCDIC data.)
The resulting data file may be handled as any other character-oriented data. The
only difference is that data originally recorded on the INTERVIEW 5110/15 Plus or
20 Plus Series does not contain the time and date stamp that normally appears at the
upper right of the display screens. The time field in a layered protocol trace,
likewise, does not contain the actual time that the data was recorded; rather, it
contains information on the relative time between frames. The
INTERVIEW 8000 Series stamps the first frame in the trace with the time elapsed
since ~ was pressed. The time displayed for subsequent frames depends on the
delay since the start of Run mode. The time between frames will vary for the same
data depending on the playback speed.
NOTE: Microfloppies configured for 512 bytes/sector have a
maximum storage capacity of 691,200 bytes as opposed to the 766,976
bytes of maximum storage available on the older 1024 bytes/sector
disk. Maximum recording speed of the 512 bytes/sector disks is 64
Kbps.
Data samples captured on the INTERVIEW 5/10/15 Plus and 20 Plus Series and
saved to disk files may be transferred to the INTERVIEW 8000 Series. You must
first, however, know the filenames for the recorded data. If no printout accompanies
the INTERVIEW 5/10/15 Plus or 20 Plus disk, you may obtain a listing of disk files
using the procedure which follows.
1.
Install the INTERVIEW 5/10/15 Plus or 20 Plus disk into the INTERVIEW 5, 10,
15, or 20 Plus.
2.
Press the Menu key until you see the start - up screen. This screen displays the
name of the device in a banner and gives the copyright date and the software
version. The prompt above the function keys instructs you to select an
instrument. Press the function key indicated for more instruments.
3.
A new set of function key labels appears on the screen. Press the function key
indicated for Disk Utilities.
14-13
SEP'95
~-
--.-----------~--~.--.-.--,---~
,-----
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
4.
For INTERVIEW 5/10/15 Plus: The screen repaints to reveal file listings for all
files stored on the disk. As shown in Figure 14-9, for the INTERVIEW 5/10/15
Plus, there are four columns labeled at the top of the screen. The first column
tells the instrument type for the file named on the same line. The second column
tells whether it is a data file (D) or a program file (P). The name ofthe file
appears in the third column. The size of the :file is listed in the final column.
Instr
t'=1l0
Name
Size
2;~
=
27,648
===F"=FS=F&=
Figure 14-9 INTERVIEW 5/10/15 Plus disk file directory.
NOTE: Data samples which have been saved as a memory buffer
rather than a file are not recorded on the microfloppy, will not appear
in the fIle listings, and cannot be transferred to the
INTERVIEW 8000 Series.
If the "-CURRENT" file is to be transferred, we recommend
renaming it. In the event that another file is saved before the
transfer, that new file will overwrite the present "-CURRENT" file.
Select the file to be renamed and press the Rename function key;
enter a new name for the file as the display directs.
5.
For INTERVIEW 20 Plus: The screen repaints to reveal file listings for all files
stored on the disk. For the INTERVIEW 20 Plus, as shown in Figure 14-10,
there are three columns. The first column lists the instrument type for the file
named on the same line and the size of the file is listed in the final column. The
second column contains three pieces of information:
~bCUBBENTI
'W' -
14-14
the "device" in which the file is stored (A - RAM, B Floppy, C and D - ROM disks),
SEP '95
14 Disk Maintenance
"02" -
the type of file (00 and 01 - program names. 02 - DLM
capture buffers. 03 - VT100 capture buffers, 04 - DVOM
capture buffers, PR - printer files), and
"-CURRENT' - the name of the file.
SYSTEM DIRECTORV
Press A,B,C or D to sel Device.
Figure 14·10 INTERVIEW 20 Plus disk System (file) Directory.
(F) INTERVIEW Transfer
To transfer data from a Series 1 INTERVIEW SilO/IS Plus disk to the
INJERVIEW 8000 Series, press the function key labeled INT 10; to transfer data from
an INTERVIEW 20 Plus or a Series 2 INTERVIEW 5/10/15120 Plus disk to the
INTERVIEW 8000 Series unit, press the function key labeled INT 20. These keys
appear when the cursor is at the top of the Disk Maintenance Screen. The screen
then repaints to display the fields shown in Figure 14·11; the Command field will
display INTERVIEW 10 PLUS TRANSFER or INTERVIEW 20 PUJS TRANSFER for the selection
made.
Install the microfloppy from the INTERVIEW 5/10/15 Plus or 20 Plus Series into
either of the floppy disk drives. If you are copying the fues to another floppy, install
a formatted INTERVIEW 8000 Series microfloppy into the other floppy disk drive.
(The two types of disks can be distinguished before they are installed as described in
Section 14.4(E).)
14-15
SEP '95
-
-
----------------------------------_.-._-------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
1. From. In this field, select the drive (FLOPPY1 or FLOPPY2) into which you have
inserted the disk from the INTERVIEW 5/10/15 Plus or 20 Plus.
2. Instntment This field indicates the type of interface used to record data on the
INTERVIEW 5, 10, 15, or 20 Plus. Data from each of the instruments is
recorded in a different format, and this must be taken into account in the
transfer. There are six possible selections in the Instrument field. These are DLM
(data line monitor), TERM (asynchronous terminal). X25 MON (X.25 protocol
monitor), SNA MON (SNA protocol monitor), BAUDOT (Baudot protocol monitor),
and DDCMP (DDCMPprotocol monitor).
Maintenance
**
Command:
INTEPV!L~
**
12 PLUS
lRCNS~ER
Instrument:
rom: . .
i 1e : _ _ _ _ _ _ _ _ _ _ _ _ _ __
To:_
Fi 1e : _ _ _ _ _ _ _ _ _ _ _ _ _ __
Depress . . Ke!::! To Execute Command
I
•
•
Figure 14-11 Use the IntelView Transfer command to transfer data from an INTERVIEW 5/10115
Plus disk to INTERVIEW 8000 Series disk files.
It is possible to determine from the file listings on the INTERVIEW 5, 10, 15, or
20 Plus what instrument was used to record the data. See Section 14.4(E) for
instructions on accessing these file listings.
Once the data is transferred from an INTERVIEW 5110/15 Plus Series unit, it is
stored in the INTERVIEW 8000 Series as ASCII character data, regardless of the
instrument on which it was recorded.
However, all INTERVIEW 20 Plus files are transferred as the same character
data format in which the data was originally recorded. (For example, data
recorded on an INTERVIEW 20 Plus in EBCDIC format would be transferred as
EBCDIC data.)
14-16
SEP '95
14 Disk Maintenance
3. File. Enter the name of the source fIle from the INTERVIEW 5, 10, 15, or 20
Plus. The fIlename for the last data sample conected is -CURRENT (unless the
file has intentionally been renamed). Enter this fIlename exactly as shown. The
initial hyphen is part of the name. Other filenames are listed in the disk fIle
directory of the INTERVIEW 5, 10, 15, or 20 Plus. Obtain directory listings as
described in Section 14.4(E).
Only data files can be transferred to the units in the INTERVIEW 8000 Series.
For the INTERVIEW 5/10/15 Plus, these files are indicated by the letter D in the
second column in the file directory. Do not attempt to transfer program fIles
(markedP).
For the INTERVIEW 20 Plus, these files are indicated by the numbers "02" or
"03" after the colon in the second field of the second column on the system (file)
directory. Do not attempt to transfer other files. For an explanation on how to
distinguish the data rues which can be transferred on an INTERVIEW 20 Plus
from other types of files. see Section 14.4(E)5.
INTERVIEW 5/10115 Plus and 20 Plus filenames are always UPPERCASE single
words (rather than a fun pathname) and must be entered as such in the File field
in the INTERVIEW 8000 Series.
4.
To. Indicate in this field the destination drive to which the data is to be
transferred. You may transfer data to either of the floppy disk drives (PDl or
F02) or to the hard disk (HRD).
5. File. Enter the destination filename in the second File field. You may enter
either a full pathname or a pathname relative to the current directory. For a
description of how pathnames work in the INTERVIEW 8000 Series refer
to Section 15.
None of the information from the INTERVIEW 5/10/15 Plus file listings is
transferred with the file when it is copied into the INTERVIEW 8000 Series. As
a result, it is important to use descriptive filenames (or pathnames) to tag your
data samples properly.
6. XEQ. When all entries on the screen are correct, press~. The message
"Transfer In Progress" appears on the second line of the screen to indicate that
the file is being copied. To abort the transfer while it is in progress, press @.
The message "Transfer Complete" is posted at the top of the screen when the
process is complete. If there is a problem with the transfer, an error message
appears in the same area. Refer to Appendix A for an explanation of error
messages.
Once the transfer is complete, the name of the file, the file type CHOAT (for
character data), the size of the copied file (which is likely to be somewhat larger
SEP '95
14-17
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
than the original file), and the date and time of the transfer are recorded in the
8000 Series directory.. If the file has been placed in a directory other than the
current directory, you must use the Change Directory command to find it in the
listings. This command and the File Maintenance screen are described in Section
15.
Use the regular Data Transfer command to move the data into the data
acquisition tracks of the disk for playback and analysis. The Data Transfer
command is discussed in Section 14.4(C). Playback is discussed in Section 5.2.
14-18
SEP '95
15 File Management
15 File Management
SEP'95
15-1
- -----
_._._._. __ --_._-_..__...- ._.
INTERVIEW 8000 Series Basic Operation: 951-80424-01
File Maintenance
Pus~ To Perform Command
Command: LOAD
Drive: FD1 Name:
Current Directory:
Select File Maintenance Command:
I
F1
LOAD
F2
I I SAVE
II
F3
II
CHNGDIR
F4
II
F5
MAKEDIR
COPY
I
I
I
Select Type Of
File To Save:
PAOGRAM SCl"UP OBJECT LPAGAM
II
II
F6
VIEW
F7
II
PRINT
F8
I
MORE
I
Select Drive: FLOPPYl FLOPPY2 HAD DSK
Enter Pathname Of File:
I
I
Select Drive:
FLOPPY1 FLOPPY2 HAD OSK
Select Drive: FLOPPYl FLOPPY2 HAD DSK
Enter Palhname Of Fde To
Erner Pa1hname of File:
Paginate 0u\puI'? YES NO
Save:
I
Select Drive: FLOPPY1 FLOPPY2 HAD DSK
Erner Palhname Of File:
Select Source Drive: FLOPPY1 FLOPPY 2 HRD DSK
Enter Source Pelhname:
Select Destination Drive: FLOPPY1 FLOPPY2 HAD DSK NEWDISK
I
SeIed Drive: FLOPPY1 FLOPPY2 HAD DSK
1
Enter Directory Palhname:
I
Select Drive:
RENAME
ENABLE
Enter Destination Palhname:
PROTECT
DELETE
COMPILE
1
I
Enter Palhnarne Of File To Rename:
Select Drive: FLOPPY1 FLOPPY2 HAD DSK
Erner Palhname Of File:
Select Drive: FLOPPY! FLOPPY2 HAD DSK
Enter Pathname Of File:
I
I
FLOPPY1 FLOPPY2 HRD DSK
Enter New F"de Name:
I
MORE
1
Select Source of Code to Compile: FILE SP~
Ir
I
Select Source Drive: FLOPPY1 FLOPPY 2 HRD DSK
Enter Source Pathname:
Select Drive: FLOPPY1 FLOPPY2 HRD DSK
Select Destination Drive: FLOPPY' FLOPPY:! HRD OSK
Enter Palhname Of File or Oirecto/y:
Enter Destination Pathname:
I
Figure 15-1 File Maintenance menu.
15-2
SEP '95
15 File Management
15 File Management
The filing system is a set of files and directories, grouped by disk. created and managed by the user.
Files may contain captured line data, setups, protocol package data, entire test programs, or text.
Files are identified and accessed by name. The file's location in the system is indicated by its full or
relative pathname, as explained later in this section.
All file management functions are performed from the File Maintenance screen (FMAlNT; see
Figure 15-1 for menu options and Figure 15-2 for default screen). The menu options are described
at the end of this section. These functions include copying fIles, loading and saving fIles, compiling
fIles or the contents of the Protocol Spreadsheet, permanently deleting files, viewing the contents of
certain fIles, write-protecting or write-enabling files, printing files, and grouping fIles into
directories.
**
(filename)
(type)
ntenance
(write-protect)
(size)
(date/time)
•
Figure 15-2 Default File Maintenance screen.
15.1 Loading and Saving Files
The File Maintenance screen is an important interface between the filing system and the
INTERVIEW's data analysis functions. All INTERVIEW test programs are loaded from
the File Maintenance screen. Newly created or modified tests are saved on this menu as
welL
15-3
SEP '95
-------------------------------------------,-----
---------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTES:
1.
READ and WRITE commands appear as editing functions on the Protocol
Spreadsheet. These commands, described in Section 30, load or save only
Protocol Spreadsheet contents and do not interfere with the contents of
other menus.
2.
Protocol packages, although part of the filing system, are loaded from the
Layer Setup screen. For a description of this menu, see Section 8.
15.2 Orienting Yourself in the Filing System
The INTERVIEW's filing system is a simple tree-structured filing system similar to the
UNIX.... filing system. (UNIX is a trademark of AT&T Bell Labs.) Each disk has its
own hierarchy. At the top of the tree is the "Root" directory, represented by the single
slash (f). When new, the System disk contains this directory and two others, /sys and lusr.
These are subdirectories of the Root directory; that is, they are one step below the top of
the hierarchy. (The slash at the beginning of the name locates the directory with reference
to the Root directory. Naming conventions for directories will be fully explained later in
this section. )
At power-up, the operating system automatically moves you into the lusr directory ofthe
disk from which the system software was loaded. System software is loaded from Floppy
Drive 1 if a system disk is inserted; by next preference, it is loaded from Floppy Drive 2;
and, if no other system software is found and a hard disk is present, it is loaded from the
hard disk.
(A) Directories
Directories may contain both files and other directories. Once you are in a new
directory, the files and subdirectories it contains are listed in the display area of the
File Maintenance screen. Directories are indicated by "DIR" in the second column
(see Figure 15-3).
1.
How to move through the directories. You may use the CHNGDIR (Change
Directory) command to move into any of these directories and view their
contents. As you work within the filing system, you can use this command to
change levels and directories. However, you can never be in more than one
working directory at a time. This working directory is referred to as the "current
directory." The current directory is always posted on the fourth line of the File
Maintenance screen.
To move from the lUST directory of the boot disk up to the Root directory, use the
Change Directory command and enter the pathname /. To move into the Isys
directory, enter the pathname /sys. There will be no other directories on a new
system disk; you must create new directories yourself.
15-4
SEP '95
15 File Management
To move from disk to disk, use the Change Directory command and select the
correct disk drive in the highlighted window below the command line. In the
entry field provided, enter slash (I) to move to the Root directory of the new disk,
or enter the absolute pathname of the directory you want. Absolute pathnames
are described in the next subsection.
2. How to create new directories. New directories are created using the MAKEDIR
(Make Directory) command on this menu. A maximum 256 files andlor
directories may be created on one microfloppy diskette. The maximum for hard
disk is 4,096. Directories follow the same naming conventions as files. These
conventions are explained in the following paragraphs. The patbname you enter
as you make a directory indicates where you wish to locate the directory in the
filing hierarchy. Pathnames are explained later in this section.
_Test_Data
mu 1_327QLTerm
i ne: _E f f _3270
Bind
SNI'=LSess ions
Test_327~LTerm
X25_Cert
X25_Cert_desc
X25_Frm_Lev
X25_Pkt_Size
**
intenance
BITIM
PRGM
PRGM
PRGM
PRGM
PRGM
DIR
ASCII
SETUP
PRGM
114371
126210
4438
31107
1107100
9722
213
110210
25104
93810
W
W
**
01/312V87
11/17/86
11/109/86
09/06/86
109/30/86
11/110/86
103/14/87
103/16/87
02/102/87
02/22/87
12:310
11:27
17:1010
109:11
10:22
07: 12
110:25
19: 12
110:25
14:32
Figw:e 15-3 Contents of the current directory are listed on the File Maintenance Screen.
(8) Absolute Path names
A pathname identifies the path through the directory structure which terminates at a
particular file or directory. Each file and directory has an absolute pathname and a
relative pathname.
An absolute pathname always begins with a slash. This indicates the path from the
"root," or starting point, of the filing system. The directories and/or file it "owns" are
listed to the right, each separated from the next higher level by a slash.
The absolute pathname is useful when you aren't sure of your current location in the
filing system. Using the absolute pathname always alerts the operating system of the
precise location of the directory or file you specify in any command.
SEP '95
15-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(C) Relative Pathnames of Flies and Directories
The relative pathname of a file or directory is the route to the file or directory from
the current directory. The relative pathname may be as simple as a one-word
filename. (It never begins with a slash.) If, for example, your current directory
(dirJ) contains a file (your.file), then the relative pathname of the file is, simply,
your.file. Now suppose that you move to a different current directory (dir_b) which
contains dir_cas a subdirectory. The same file would have a different relative
pathname: dir_clyour.file.
Each time you move up a directory level, the relative pathname gains a new
subdirectory name as a component. The new component is always separated from its
subdirectory (or file) by a slash. The relative pathname of this same file when you are
working in the lusr directory might, for example, be dir_aldir_bldirJlyour.file. The
absolute path name for the same file would be /usrldir_aldir_bldir_cjyour.file.
(D) Files
Files are the basic elements of the filing system. Files can be identified in the Type
field of the Directory Listings. Any type other than "DIR" is a file.
The INTERVIEW files named in the directory listings on the File Maintenance
screen are created in a variety of ways. The files in the /sys directory, for example,
are placed on each system disk at the factory. This directory contains data essential
to the operating system. It is not advisable to store user files in the Isys directory.
The lusr directory, also created on each disk at the factory, is intended for the storage
of files (and directories) which you create.
1.
Program files. Program files, which contain the configuration of all INTERVIEW
menus and the Protocol Spreadsheet contents, are created when you use the SAVE
command on this menu.
2.
Setup files. Use the SAVE command on the File Maintenance screen to create
Setup files. Setup files contain a partial set of configured menus.
3.
Object files. Object files, which contain the configured Setup menus, the Layer
packages, and the object-code compilation of the Trigger menus and the
Protocol Spreadsheet, are created when you use the SAVE command on the File
Maintenance menu.
4.
Linkable-objectfiles. Use the Compile command on the File Maintenance menu
to create linkable-object (LOBJ) files. Linkable-object files may contain the
object-code compilation of standard C code. The compiled C code in
linkable-object files usually contains the definitions of user-created routines.
Linkable - object (LOBJ) files may also contain the compiled contents of the
Protocol Spreadsheet, different from object (OBJ) files which additionally
contain all menu configurations.
15-6
SEP '95
ADDENDUM
fi'
15 File Manaqement
I
5. Llnkable-programfiles. Use the Save command on the File Maintenance menu
to create linkable-program (LPGM) files. Linkable-program files contain all of
the setup menus of program (PROM) files except for 1Iiggers and source-code
Spreadsheet. In addition to the menus, LPGM files contain the linkable-object
code compilation of the Protocol Spreadsheet. When you load an LPOM file and
go to the Protocol Spreadsheet, all you see is an OBJECT block identifier that
references the pathname of the LPGM file.
Once a linkable-program file is loaded (via the File Maintenance Load
command), you may modify the setup menus and rerun or save the program.
Since the spreadsheet program has already been compiled, changes to the setup
m.enus do not cause a lengthy recompile time.
6. Protocol Spreadsheet files. Use the WRITE command provided by the spreadsheet
editor (descnbed in Section 30), specify a filename, and press ~ or 8 to save
only the contents of the spreadsheet. The file which results is listed in the File
Maintenance directory as type ASCII; however, when you want to use the file
again, it should be read in by the spreadsheet editor (rather than loaded from the
File Maintenance screen.)
7.
Data files. Use the Data 1hmsfer command on the Disk Maintenance screen to
store data from disk into a file. See Section 14.4(C). The files which result
~ar in the directory listings on the File Maintenance screen. Before you
replay data files, you must transfer them back onto the data acquisition tracks of
a disk; a file is not a valid ao.- of data on the Line Setup menu. Do not
attempt to load data files from the File Maintenance screen.
(E) Naming ConvenUons for Flies and Directories
There are a few simple rules to keep in mind when naming files. The maximum
length of any component is 12 characters. Legal characters for filenames are letters;
numbers (0-9); and the symbols dash (-), underscore U, dollar sign ($), and period
(.). Filenames must start with a letter or a period. Upper and lower case letters may
be used. Filenames are case-sensitive; that is, the pattern of upper and lower case
letters in an existing name must be repeated exactly any time that file is referenced.
Wildcards may be used in some operations, as described in Subsection (F), below.
•
Filenames may include extensions for convenience, but the system attaches no special
meaning to the extension. When you refer to a file with an extension, you must
include the extension in the filename.
Filenames cannot be duplicated within the same directory. If, for example, there is
already a file in your current directory called unifile and you save a newly created file
to the name unifile, then the old file is destroyed.
Single periods (.) and double periods (..) have special uses when referring to files or
directories. Their uses are described in the paragraphs which follow.
NOV '95
15-7
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(F) Use of Wildcards in Filenames
There are several ways in which you can designate files using wildcards to be acted
upon by a chosen command. Table 15-1 lists the legal wildcard definitions in the
INTERVIEW file system.
Table 15-1
Wildcards With File Designations
Meaning
Wildcard
m
,..
matches 0 or more of any character
?
matches any single character
[]
matches anyone of the listed characters, i.e., [-abcdK23457};
ranges are allowed: [-a-dK2-S7} m
[ .... J
matches anyone character except those listed, i.e., ['" cdef04567S-1;
ranges are allowed: ["'c-f04-S-}
m
The hyphen (-) is used as a wildcard match or exclusion in two ways:
(1) To designate an inclusive range of characters, it is used between characters.
(2) To designate itself, it must be listed either at the beginning or ending of the sequence.
A space ( ) will be read as a space. Spaces are not used in filenames, so neither
should they be used within wildcard bracket designations.
As illustrated in Table 15-1, the hyphen ( - ) is used two ways within brackets: as the
hyphen character, it is placed at the beginning or end of the sequence; or, used
between two characters, it designates inclusive ranges.
For example, using the wildcard designations found in Table 15-1, the me designation
[Aa-kJ*bc.? describes one or more files which have the following attributes:
T
[Aa-k] *hc.?
The filenames described must
have these parts which ...
.
... matches exactly one character
except a through k
These files meet the criteria:
lbc.f
zv;xyybc.y
mlz2xbe.a
... preceding any number
of or no characters
... preceding the letters be
... with any one-character suffix
15-8
NOV '95
ADDENDUM
15 File Management
1.
Limitations.
Wildcards are special characters that do pattern matching and can only be used
when the cursor is in the menu area.
Wildcards cannot be used for the MAKEDIR operation.
A destination file with wildcard designations must only match a single file.
A destination directory with wildcard designations must only match a single directory.
Wildcard symbols may be used to type in "shorthand" filenames with only one
match; these are operated upon as if the real pathname had been entered. If
problems occurred during the operation, errors messages are those displayed as if
a single pathname had been entered for the filename.
2. Marked files.
Generally speaking, marked files and wildcard-designated files and directories are
mutually exclusive, with one exception: you may copy a marked file into a single
destination file or directory whose "shorthand" name includes wildcard symbols, as
long as the name identifies one and only one file or directory. MultipJe files may also
be marked to be copied to a single destination directory named in the same manner.
Like other operations with marked files, the cursor must remain in the file list area.
If errors occur, the operation may have been successfully completed upon some or
none of the marked files; those which encountered errors will remain marked. We
recommend you try the operation again with each of the remaining marked files, one
at a time; this permits the system to report a more specific message for each file.
(G) Use of Periods in Path names
Single periods and double periods, when used alone as file components, have special
meanings. A single period (.) always represents the current directory. A double period ( .. )
always represents the parent directory; that is, the directory immediately above.
The double period ( .. ) is a useful abbreviation for defining pathnames. A common
use for the component would be to change the current directory to the parent
directory. In this case, you don't need to use the name of the parent directory. Just
select the Change Directory command and enter .. as the pathname to the new
current directory. String a series of these together, separated by slashes (for example,
Change Directory .j../.. ) to move up the file tree.
Study the file system in Figure 15-4 to see how the following points apply.
1.
NOV'95
The relative pathname ofyour.jile is dir_clyour.file. Its absolute pathname is
lusrldir_aldir_bldirJ/your.file.
15-9
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
2.
The relative patbname of other.file is dir_dlother.file. Its absolute pathname is
lusrldir_aldir_bldir_dlother.file.
3.
To move up to the lusr directory from the current directory, enter the pathname
../.. when you use the Change Directory command.
4.
To move from the current directory (dir_b) to dir_e, use the Change Directory
command and enter this pathname to the new directory: ../dir_e. (This is simpler
than using the absolute pathname, lusrldir_aldir_e.)
HRD
Current
Directory
0= directory
yourJile
othe r. file
o
=fiJe
Figure 154 The INTERVIEW has a hierarchical filing system.
15-10
NOV'95
ADDENDUM
15 File Management
15.3 The File Maintenance Screen
(A) The Top of the Screen
Twelve commands can be executed from the File Maintenance screen (see
Figure 15-1 for a full set of menu fields). There are two alternate banks of
commands. Use the MORE (@) function key to switch from bank to bank (see
Figure 15-5 and Figure 15-6). When you press the function key to select a particular
colDJll3.nd, the screen repaints, and a set of unique menu fields appears. The selected
command always appears on the top line of the menu.
F"JgUre 15-5 Press MORE to display the alternate bank of function keys.
Figure 15-6 Alternate bank of function keys.
1.
Current drive. At the top of the screen, just below the Command field, the name of
the current disk is given (see Figure 15-7). The files displayed in the directory
listings on the screen reside on the disk named in this area.
NOTE: The current disk at power-up is the disk from which the
INTERVIEW is initialized. If all three drives are present, the
INTERVIEW checks FD1, then FD2. and finally HRD for system
initialization software and boots from the fust system disk it finds.
FJgUre IS-7 The name of the current disk is selected in tile Drive field.
NOV '95
15-11
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
2. Name field. Every command requires at least one filename and provides a field in
the menu area for filename entry (see Figure 15-7) where you MAY enter the
name of the file to be acted upon. The file's absolute or relative pathname can be
entered. If you enter the filename, you must type it exactly as it appears in the
directory listings.
NOTE: There are several ways to specify the file or files which are to
be acted upon. Read Section 15.3(C) before executing any command.
Study the directory listings if you are uncertain of the filename. If you require
more information on a file, use the View command to see the contents of the flle.
(8) Directory Listings
The name of the current directory is listed in a field at the top of the screen. The
contents of the current directory are listed in a 12 -line field in the center of the
menu. Six columns of information appear for each file (see Figure 15-8). The
(relative) fllename is given in the first column.
The Type field to the right defines the contents of the file. All types that may appear
in this column are defined in Table 15-2. When a file is write-protected, the letter
"W" appears immediately to the right of the Type column.
The size of the file (in bytes) is given in the next column. The date and time that the
file was last modified appear in the two far-right columns.
Menu {
Area
Directory
listings
I
File Type
Write- Protected
File or Directory Name
Size of file in bytes
Figure 15-8 Current directory listings. Data types are listed in the column to the right of the file or directory name.
1.
15-12
Moving through directory listings. The contents of the current directory are
displayed on the File Maintenance screen.
NOV'95
ADDENDUM
15 File Management
More than 12 lines of information may be available for the directory. To display
additional lines, position the cursor on the last line of the listings and press l±J.
(This will display new lines one at a time.)
Press 8 and l±J at the same time to move to the end of the listings. Press 1]1) to display
the next 12 lines of information. Position the cursor on the first line and press ffJ to
expose previous lines one at a time. Press iI(J to display the previous 12 lines.
Press 8 and ffl to move to the top of the listings.
To see the listings for another directory, you must use the Change Directory command.
Table 15-2
FilelYpes
Type
Meaning
Comments
PRGM
Program
Full set of configured screens.
SETUP
Setup
Subset of five configured Setup screens,
in particular, excludes Trigger Setup
screens, layer Setup screen, and
Protocol Spreadsheet.
OBJ
Object
FIve configured Setup screens. the layer
packages, and the object-code compilation of the
Trigger menus and the Protocol Spreadsheet
LOBJ
Linkable Object
Object-code compilation of a standard C file or of the
contents of the Protocol Spreadsheet C files may be
generated via the WRITE/U (ecIitor}command on the
Protocol Spreadsheet.
LPGM
Linkable Program
Setup menus of a PRGM file (except for Triggers and
source code of spread$heet) in addition to the
linkable-object code compilation of the Protocol
Spreadsheet. LPGM files are compatible between units
with different hardware and/or software configurations.
BmM
Recorded data
Bit-image data saved for reanalysis. May
be reformatted and rechecked for
error.
CHOAT
Recorded data
Character data saved for reanalysis. This data
has already been formatted and checked for
error (If receiVed block -checking enabled) and may
not be reformatted or rechecked.
ASCII
Text
sec
sec
Text file generated by user on Protocol
Spreadsheet screen.
•
NOV '95
DIR
Directory
A directory, potentially containing files and
subdirectories, which is part of the
structured tile system.
SYS
System files
and internal
INTERVIEW files
Files generated by General Signa! Networks - Mount laurel,
including Personality packages.
15-13
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(C) Selecting Files
There are several ways in which you can designate files to be acted upon by a chosen
command.
1.
Name field. The first means of selecting a file is to enter its name in the Name
field at the top of the menu.
NOTE: The cursor must remain in the menu area (see Figure 15-8) in
order for the command to operate on the named file.
2.
Cursor location. You may designate a single file to be acted on by moving the
cursor into the directory listings and positioning it over the desired file. The file
name will be highlighted.
NOTE: When the cursor is located in the Directory Listings, the
highlighted file will be acted upon by any command executed. Any file
named in the Name field will NOT be acted upon.
If you have selected a file with the cursor, but the file-maintenance command
shown at the top of the screen is not the one you want, press 8. The cursor will
return automatically to the Command field. Choose the appropriate command
and press 8 again. The cursor will return to its previous location, highlighting
the selected file.
3.
Markingfiles. For certain commands, the [3 key can be used to select files on
which you want the command to operate. To mark a file, locate the cursor over it
and press 8. Once a file is marked, you need not flll in the Name field for the
command.
The next command executed will operate on the marked file or fIles. Even if
there is a filename in the Name field, marked files (and NOT the entered file) will
be acted upon.
Marked flles also take precedence over the file at the cursor location. That is, if
files are marked, they will be acted upon by the command, but the flle at the
cursor location will not be acted upon.
With one exception, [3 works only with commands which are used to operate on
multiple files simultaneously. These commands are Copy, Delete, Write- Protect,
Write-Enable, and Print. The exception is the Compile command. In this case,
only a single file should be marked. If you mark more than one file for
compiling, the following error message will be displayed: "Too many source files
selected."
Wildcard symbols may be used during an operation with one or more marked files.
If errors occur, the operation may have been successfully completed upon some or
I
15-14
NOV'95
ADDENDUM
15 File Manaaement
none of the marked files; those which had errors will remain marked.
We
recommend you try the operation again with each of the remaining marked files, one
a1 a time; this permits the system to report a more specific message for each file.
I
4.
Unmmking a file. 8 is an alternate action key. To deselect a marked file, locate
the cursor next to it and press 8 again.
Once the command is executed, the file is no longer marked. Marked files are no
longer marked if you leave the File Maintenance screen.
(D) Exequtlng Commands
To execute any of the 12 commands, make sure that all entries are correct. Then
press 8. Status messages will inform you of any errors. Refer to Appendix A for an
exp~tion of error messages.
(E) Load
For fast access to this command, press 8 as an alternative to accessing the File
Maintenance screen with function keys. Use this command to load a working copy of
a file from disk into the internal memory of the INTERVIEW. The Load command is
frequently used to load complete programs into the INTERVIEW in preparation for
runnjng a test. Any program or setup file you wish to modify must first be loaded.
Only program, se~ object (OBI), or linkable-program (LPGM) files can be loaded
with this command.
•
Program files are a full set of configured menus, induding the Layer Setup
screen, Trigger Setup screens, and the Protocol Spreadsheet.
•
Setup files are a smaller set of configured menus which includes only the five
Setup screens: Line Setup, Interface Control, BCC Control, Front-End Buffer
Setup, and Bit Error Rate Test Setup.
•
Object files are the configured Setup menus, the Layer packages, and the
object-code compilation of the 1iigger menus and the Protocol Spreadsheet.
•
Linkable-program (LPGM) files contain all of the setup menus of program
(pRGM) files except for 1iiggers and source-code Spreadsheet. In addition to
the menus, lPGM files contain the linkable-object code compilation of the
Protocol Spreadsheet. When you load an LPGM file and go to the Protocol
Spreadsheet, all you see is an OBJECT block identifier that references the
patbname of the LPGM file. Although it makes no difference from which drive
you load a linkable-program file, in order for the program to run, the file must
accessible on that same disk drive.
remain
•
fi'
Once a linkable-program file is loaded, you may modify the setup menus and
Since the spreadsheet program has already been
compiled, changes to the setup menus do notcause a lengthy recompile time.
~erun or save the program.
I
NOV '95
15-15
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-80424-01
NOTE: To successfully execute the File Maintenance Copy
command on linkable-program files, you must have software
revision 8.00 (or later). LPGM is an unknown file type to earlier
software revisions.
You must specify the disk on which the file you are loading resides and the (relative
or absolute) pathname of the file before executing the load command. The simplest
means of loading a ftle from the current directory is to place the cursor over the
filename in the directory listings and press~. Cursor selection overrides any entries
that may appear at the top of the menu.
NOTES:
1.
Remember that loading a program or setup overwrites the program or setup
already in the INTERVIEw. Save the resident program or setup if you wish
to use it later, and then load another file.
2.
Loading an object file allows you to enter Run mode without recompiling,
unless you make substantive changes (i.e., changes to menus and fields not
listed in Table 2-1).
3.
The spreadsheet portion of a program (when saved via the Protocol
Spreadsheet WRITE editor command) can be loaded via the READ command
without overwriting the contents of other menus. See Section 30 for an
explanation of the READ and WRITE commands.
4.
Protocol layer setups are loaded from the Layer Setup screen (see Section 8).
They may also be loaded along with a program, linkable-program, or object
flIe.
5.
Data ftles are not "loaded" from the File Maintenance screen. Instead, see
Section 14.4(C), Data Transfer.
6.
Linkable-object (LOBJ) flIes are not loaded from the File Maintenance
screen. Depending on the ftle's contents, use either the OBJECT
block-identifier or the #pragma object preprocessor directive to access the
compiled C code in an LOBJ file. Refer to Sections 28.4 and 55.4.
7.
You cannot load the Printer Setup file (lsys/print_setup) from the File
Maintenance screen. It is loaded automatically during boot-up. See
Section 2.1(B).
(F) Save
For fast access of this command, press 8 as an alternative to accessing the File
Maintenance screen with function keys. Use this command to preserve a newly
created program. setup, or object file or to retain any changes you have just made to
an existing file. If saving to an existing filename, the existing file must be the same
file type as the file you are saving to overwrite it.
15-16
NOV'95
ADDENDUM
15 File Management
Before executing this command, you must select the type of file to be saved.
Program, setup, object (OBJ), and linkable-program (LPRGRM) are the only
options on this screen.
•
A setup is a set of five configured menus: Line Setup. Interface Control, BCC
Control, FEB Setup, and BERT Setup.
•
A program contains all menus, including the Layer Setup screens, Trigger Setup
screens, and the contents of the Protocol Spreadsheet.
•
An object contains the configured Setup menus, the Layer packages, and the
object-code compilation of the Trigger menus and the Protocol Spreadsheet. If
you have not compiled the program prior to saving the object, the compilation
occurs as part of the SAVE process.
•
Linkable -program (LPGM) files contain all of the menus of program (PRGM)
files except for Triggers and source-code spreadsheet. In addition to the menus,
LPGM files contain the object-code compilation of the Protocol Spreadsheet.
The compilation occurs as part of the SAVE process.
When you Save a program as an LPGM file, your spreadsheet program excluding
C #pragmas is saved as compiled linkable-object code. To retain #pragmas in
your program, reference them as the hook text in a #pragma hook 0 before you
save the program. Although the #pragma hook 0 is not saved, the hook text is.
There are two exceptions to this rule: #pragma object and #pragma hook O.
Enter these directives on the spreadsheet following the formats explained in
Section 55, C Basics. They will be saved intact in LPGM files.
To include other #pragmas, #pragma ii_buffers 128 for example, in an LPGM file,
enter them in a #pragma hook 0 as follows:
#pragma hook 0 "#pragma ii_bUffers 128"
NOTE: To successfully execute the File Maintenance Copy
command on linkable-program files, you must have software
revision 8.00 (or later). LPGM is an unknown file type to earlier
software revisions.
Before executing the command, you must also select the drive to which you wish to
save the file, and you must enter the pathname to the file you are saving. If you are
saving toa filename which already exists in the current directory, you may indicate
the :tue by placing the cursor over its name in the directory listings before pressing
§). Cursor selection of a file overrides any entries which may appear at the top of
the menu. The existing file must be the same file type as the file you are saving to
overwrite it.
~
~'
NOV '95
15-17
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-80424-01
You cannot save to a directory which does not already exist. First, create the
directory with the Make Directory command.
Press [3. During the Save operation, status messages are posted at the top of the
File Maintenance screen. For a diagnostic message about errors that prevent
compilation of OBJ or LPGM files, press S, SPDSHT, ~,GO-ERR. Press GO-ERR
again for a message about the next error. Continue until no more errors are
detected.
You may abort the Save procedure by pressing the ABORT softkey or 8 . Note,
however, that if the destination file is an existing file, it may have been partially
overwritten.
NOTES:
1.
You may use the Save command to create a new set of default values for all
menus. If you create a file called lusr/default on the initialization disk, all menus
will be set to your saved selections when the INTERVIEW boots from that disk.
See Section 2.2(B) for a description of this procedure. See Section 14.1 for disk
selection at boot-up.
2.
If you only wish to save the contents of the spreadsheet, use the Protocol
Spreadsheet WRITE command (see Section 30). Or use the File Maintenance
Compile command to save the compiled object-code version of the contents of
the spreadsheet. See Section 15.3(P).
3.
Saving an object or linkable-program file requires a considerable amount of disk
space and should be reserved for frequently used tests with long compilation
times. (The program file for a test may occupy only 5320 bytes, while the object
file for the same test occupies 109894 bytes.)
4.
Preserve a copy of the source code (the program version) of a test as well as the
OBJ or LPGM version. The program code is more versatile than the OBJ file
code: in subsequent software revisions, the program version may still compile
even if the object-code version no longer does. You may then generate a new
object file from the source -code version.
Although linkable-program files are as compatible as program files, editing on
the Protocol Spreadsheet must take place in the source program file.
15-18
5.
Data can also be saved to a file using the Data Transfer command on the Disk
Maintenance screen; see Section 14.4(C). Once data is saved in a file, the file
appears in the directory listings of the File Maintenance screen.
6.
Linkable-object (LOBJ) files are created via the Compile command, not the
Save command. See Section 15.3(P).
NOV'95
ADDENDUM
15 File Management
7.
Save the Printer Setup configuration file (/syslprint_setup) from the Printer Setup
screen, not the File Maintenance screen. See Section 16.3.
(G) Change Directory
This command, labeled CHNGDIR on the function key, is the only method of moving
from one current directory to another. Indicate the drive on which the new directory
resides and give its absolute or relative pathname before executing the command.
The name of the new current directory replaces the old one on the fourth line at the
top of the File Maintenance screen, once the command is executed.
NOTES:
1.
By definition, all relative pathnames of files and directories change once you
change to a new current directory.
2.
To move up to a higher directory, you must name the directory in the Name field.
3.
If the name of the parent (the next higher) directory is not known, enter two
periods ( ..) in the Name field. This moves you up one directory.
4.
To change to a directory on another disk, select the drive in the rotating window
and enter the absolute pathname of the directory in the name field.
(H) Make Directory
You must use the MAKEOIR (Make Directory) command to create a new directory. Use
this command to create your own file hierarchy. You may create any number of
subdirectories to the root (I) or lusr directory on any disk, and you may subordinate
directories to another directory, thereby building as many levels of subdirectories as
you wish.
The relationship of one directory to another is identified by its name, as explained
earlier in this section.
NOTE: When you create a directory, you may use the absolute
pathname for the new directory to locate it anywhere you specify on
any of the disks. If you use a relative pailiname, the new directory
will be created as a subdirectory of the current directory.
(I) Copy
Use this command to copy a file or group of files to a new location. (The original
copy or copies will remain, unless you choose to delete them using the Delete
command.) This command is useful, for example, when you wish to copy certain files
from one disk onto another disk. If you are using only one floppy disk drive, the
system will prompt you to insert the "source" disk or the "destination" disk at the
proper times and you should select ~ as your destination disk on the File
Maintenance screen.
NOV '95
15-19
-------------_.._------
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTE: To successfully execute the File Maintenance COpy command
on linkable-program files, you must have software revision 8.00 (or
later). LPGM is an unknown file type to earlier software revisions.
When you select the Copy command, you will be asked to select the source drive
(where the file or files to be copied now reside), enter the source pathname of the file
to be copied, select the destination drive, and enter the destination pathname (the
intended directory location and filename for the new copy). The pathname you enter
may be relative or absolute.
Wildcards can be used to name source files in a COpy operation; wildcard symbols are
discussed in Section 15.2(F). Multiple source files can also be specified by marking
several files in the file list area.
Table 15-3 illustrates the twelve possibilities for copying both single and multiple files
and directories. The table assumes the directories and files are write-enabled.
Table 15-3
Source and Destination Copy Guidelines
~
File
Source
Single:
File
Overwrite
existing file
Directory
Non -existent
Create file
into directory;
overwrite
existing file
Create
destination
file !!l
rn
Multiple:
Directory
ERROR
Existing files
of same name
overwritten
Create
destination
directory fID
Files
ERROR
Existing files
of same name
overwritten
ERROR
Directories
ERROR
Create
destination
directories ~
ERROR
Example: Copying the file lusr/programs/x25 to the writable directory lusr/save actually copies the file into
lusr/save/x25. If lusr/save/x25 already exists on the specified drive. it is overwritten; if it does not exist, it is created.
[lj Target will be created. but only if all preceding parent directories exist on the destination drive and the last one
parent directory is writable. Example: If destination file is to be /usrlprograms/x25, then the writable directory
/usr/programs must exist on the drive where the destination file is to be created.
[IJ
I1J Source directories are copied into subdirectories of the destination directory on the specified drive; these
destination subdirectories must have the same name as the corresponding source directory.
15-20
NOV'95
ADDENDUM
15 File Management
1.
Q)pying a group ofjiJes. Multiple filenames may be "marked" in the directory for
copying. See Marking Files, Section l5.3(C)3.
If you designate a directory as the source you want to copy, all files and
subdirectories contained in the directory are also copied.
W'tldcard symbols may be used to copy a group of files; wildcards are discussed in
Section 15.2(F). If wildcard symbols are used to copy a group of files, the
~tion filenames begin with the first wildcard, appended to the destination
parent name.
For example, copy multiple files from IHRD/x25/*IxI*k* to the directoty
/FD1/bkup. If the actual source files copied are
/HRD/x25IAlxlaka and IHRD/x25IBlxlback
then the new destination filenames would be
IFDlIbkup/A.lx/aka and /FD1/bkupIBlxlback
NOTE: Copying a group of files to a floppy disk drive may require more
space than is available on one disk. When the first destination floppy
disk is full, you will be prompted to insert the next disk.
If you are copying a group of files from one place to another on the same
floppy disk, you must make certain you have enough space left on the
disk to hold all of the files you wish to copy. This same advice holds for
copying a group of files from any disk drive to the hard disk drive: verify
you have enough space on the destination disk to hold the copied files.
2. Copying an entire directory. You may indicate an entire directory to be copied.
The directoty and all its subdirectories and files will be copied. If the name of an
existing directOty is given, all files and directories are placed inside that directory.
But the original directory is not retained. This means that any files or directories
ip the destination directory are, unless write-protected, overwritten by files or
directories of the same name in the copied directory. You may also copy files to
a fictitious subdirectory. As long as the subdirectoty has a real parent directory,
such a destination pathname is valid. (For example, if you have a directory
named lusrlprograms on FDl, you may copy a directory from the hard disk to
J,usr!progrrnns/x25 on FDI, even though the directory /x25 did not previously
exist.) The subdirectory is created as part of the Copy command, and all files
and directories from the source are copied into it
3. Copying an entire disk. If both floppy disk drives are operable, you would use the
Duplicate Disk command on the Disk Maintenance screen. See Section 14.4(D).
'"
If you have only one floppy disk drive available, the Duplicate Disk command is
pot applicable to your hardware. However, it is posstble to copy an entire disk to
another disk in three steps: format the destination disk, copy the root directory
to the disk, and transfer the data acquisition tracks to the disk.
I
NOV '95
15-21
ADDENDUM
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
After a disk is formatted, it may be copied to via the Copy command. Copy the
root directory from one disk to another; the file name for both the source and
destination disks will simply be "r and the softkey selection for the destination
disk is NEWOISK. The system will prompt you to insert the "source" disk or the
"destination" disk at the proper times. You must then use the Data Transfer
command on the Disk Maintenance screen-see Section 14.4(C)-to copy to
data acquisition tracks to your destination disk. The disk is now duplicated.
NOTE: Copying to a new disk in the same drive will use the same
memory as the current program and the Layer Personality packages.
The procedure may need fewer repetitions of disk-insertion/removal
if it is done at a time when a large program and multiple layer
packages are not loaded in.
(J) View
The purpose of the View command is to allow you to look at the contents of a file
without actually loading the file. The program or data currently in the internal
memory of the INTERVIEW is not overwritten by the View command.
Prior to executing the View command, you must select the drive on which the file
resides and provide the (relative or absolute) pathname of the file.
When you press §J, the screen repaints, displaying the first 12 lines of the file in the
Directory Listing area. New function keys are available as labeled.
Descriptive text is presented to the user when a program or setup file is viewed. For
an ASCII file, the file is presented "as is." Bit-image and character-data files
cannot be viewed.
1.
Moving through a view file. The beginning of a file appears on the screen when a
file is viewed. The cursor location is highlighted. Use l*) to move the cursor to
the bottom of the screen and continue pressing l*) to scroll down through the file
a line at a time. Move the cursor to the top of the screen by repeatedly pressing
ffl and continue pressing it to scroll back up through the file.
Press 8-l*) to move down to the end of the file. Use 8-ffl to move to the top
of the file.
Use fB) to move one page (12 lines) forward in the file. Press ~ to move
backward one page in the file.
To leave the file being viewed and return to the File Maintenance screen, press
or the function key labeled ABORl:
8
(K) Print
This command prints a hard copy of the me when a printer is properly connected to
the INTERVIEW's Printer Port. Indicate the disk on which the file resides, as well as
the file's relative or absolute pathname. Then make a selection in the Paginate field.
If you select Paginate: l:iiL each printed page will contain a header. The header
includes the name of the file (not its pathname) and the page number:
File: filename
15-22
Page: 1
NOV '95
ADDENDUM
15 File Management
Section 16 provides instructions on configuring a printer for use with the
INTERVIEW and explains printed format.
(L) Rename
Use the Rename command to assign a new name to a file. A file can only be
renamed if it resides on the active disk (named on the current directory line). In
order to rename a file, you must indicate the disk on which the file resides, provide
the pathname of the file (that is, give the old filename), and enter the new name you
wish to give the file.
NOTE: When you rename a file, the original file disappears.
The Rename command can also be used to move a file to a new location. Both new
and old locations must be on the active disk (named on the current directory line.)
To relocate a file to a different disk, use the Copy command, and then delete the
original file.
NOTE: Do not use the abbreviations (. and .. ) for naming the new
location for a renamed file since they are valid characters for a file
name. They will be interpreted as part of the new name.
(M)Enable
This command is used to remove the write protection from a file or directory. Once a
file or directory has been write-enabled, the save, delete, and rename commands can
be executed on the file or directory.
When a directory is write-enabled, the files within the directory are also enabled,
unless they have been individually write-protected. In this case, you must also
enable each file before it can be modified or deleted.
Prior to executing the command, you must select the drive on which the file or
directory resides and provide the (relative or absolute) pathname of the file or
directory. Or you may simply cursor-select a filename for write-enabling and press
~. Multiple fIlenames may be "marked" in the directory for write-enabling. See
Marking Files, Section 15.3(C)3.
(N) Protect
Th.i$ is the Write Protect command. It is used as a security measure. When a file is
write-protected, any attempt to save, delete, or rename the file will be rejected.
Prior to executing the Write Protect command, you must indicate the drive on which
the file (or files) reside and you must provide the name of the file (or files) you wish
to protect.
NOV '95
15-23
"----'"------,---_.---------
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
A directory may be named, cursor-selected, or marked for write protection. This
write-protects the individual files within the directory. It is possible to
write-protect the individual files as well; in which case, both the directory and the
ftIe must be enabled before the file can be modified or deleted.
NOTE: Reformatting a floppy disk destroys all ftIes and data,
whether they are protected or not. Floppy disks can be
write-protected manually against formatting, as explained in Section
1. The hard disk cannot be write-protected against a Format
command entered from the Disk Maintenance menu.
It is strongly recommended that you regularly back up the hard disk
as well as any floppies you wish to preserve.
(0) Delete
Use this command to remove files permanently from a disk. Prior to executing the
Delete command, you must select the disk drive from which you are deleting the file
and give the (relative or absolute) pathname of the file you wish to delete. In order
to delete an entire directory, you must first delete all files and subdirectories it
contains. To delete a subdirectory you must be located in the directory above it (the
parent directory).
NOTE: Be aware that you can delete a file by placing the cursor over
a filename in the directory listings and then executing the Delete
command. Cursor selection takes precedence over any filename in
the Name field.
You may also mark one or more files for deletion with 8. Any
marked files take precedence and will be deleted instead of the file at
the cursor location or a file named in the field at the top of the menu.
(P) Compile
Use this command to compile and save as object code the contents of the Protocol
Spreadsheet or a me.
NOTE: If you want to save setup menus in addition to the compiled
spreadsheet program, use the Save command and create a
linkable-program (LPGM) file. See Section (F) above.
One of the advantages of using linkable -object (LOBJ) files instead of object (OBJ)
files is that OBJ files created on one unit will not run on another unit that is
configured differently. In contrast, LOBJ files (as well as LPGM files) are
transparent to the configuration of the unit-i.e., they are just as transparent as the
code would be, were it actually present in the spreadsheet buffer. The code, however,
15-24
NOV'95
ADDENDUM
15 File Manaaement
must still be compatible with the various menu parameters. For example, a call to
II_il_transmit or a SEND action, whether contained in an.LOBJ file or written to the
Protoeol Spreadsheet, would not be compatible with a Line Setup selection of Mode:
110"::0;1:::::
J
. .•
linkable-object files also assist the programmer in efficiently using the
~VlEW's memory and spreadsheet buffer. Refer to Section 28.4(D).
IIIIIIIIIIII! is the default selection. A valid source file for compiling
COntains only standard C code, typically definitions of user-created routines. It
niay also contain #pnJgma hook 0 preprocessor directives. (Refer to Section
55.4.) The code does not have to be a complete program. Program or setup files
ate not valid source files.
1. File. iil~mlll~ilill
NOTE: Write C code from the Protocol Spreadsheet to a file by using
the WRITE/U spreadsheet-editor command. See Section 30. The file
will be type ASCII in the directory listing on the File Maintenance
screen.
IiiI Ri, also select the source drive (where the file resides)
and enter the source pathname of the file to be compiled. To select a source file,
you may enter the relative or absolute pathname of the file, position the cursor
over the filename in the current directory, or mark the file in the current
directory. See Selecting Files, Section 15.3(q. Note that the new file will only
overwrite a file of the same file type.
If you choose Illllilliilill
Depending on whether or not the file contains "hook", use either the OBJECT
block-identifier (Section 28.4) or the #pragma object preprocessor directive
(Section 55.4) on the Protocol Spreadsheet to access the C code in the file.
2
Spreadsheet. If you choose j] i!lllllli]] I 1!1!!ll lm, the contents of the Protocol
Spreadsheet will be compiled. The spreadsheet program may include C code,
softkey-generated entries, or a combination of the two, but it must be a valid
program in order to compile.
The linkable-object file which results will always contain system-generated #pragma
hook directives, at least one of which will be a type-zero hook. (See Section 55.4.) To
access this spreadsheet file, therefore, you must reference it on the Protocol
Spreadsheet with the OBJECT block-identifier. See Section 28.4.
Whether you are compiling a file or the spreadsheet, specify a destination drive and
enter the destination pathname (the intended directory location and filename for the
LOW file). The pathname you enter may be relative or absolute.
~ble-object files
follow the standard naming conventions discussed in Section
15.2(E). As an added convention, you may want to append the suffix.o to the end of
the name.
NOV '95
15-25
ADDENDUM
INTERVIEW 8000 Series Basic Operation: 951-80424-01
NOTE: A Ilib subdirectory (if present in the /sys or /usr directory) is
included in the search routine for linkable-object fIles. See Section
28.4. We recommend, therefore, that you make a /usr/lib directory for
storing the LOBJ fIles you create.
Press §J. During the Compile operation, status messages are posted at the top of the File
Maintenance screen. If there are errors in the source file that prevent compilation, the
following message will be displayed: "Compilation failed - Errors detected." For a diagnostic
message about the fIrst error, press 8 , SPDSHT, §), GO-ERR. Press GO-ERR again for a
message about the next error. Continue until no more errors are detected.
You may abort the Compile procedure by pressing the ABORT softkey or~. Note,
however, that the destination file may have been partially overwritten if compile was to an
existing file.
15-26
NOV'95
16 Printer Control
16 Printer Control
SEP'95
16-1
-------~---~-----~.--.--.--.-.---.--~.---.-~---------.-------------~
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Utility Menu
Select Desired Utility Screen:
I
II
F1
DTmME
F2
PRINTER
F3
II
I ID/MAINT
I I F4 I I
MISC
EZSETUP
1
I
I
See Time-of- Day Clock Section
F6
F5
I
II
I
I
L...--
Y
I
See Color Display Section
See Disk Maintenance Section
F7
II
Fa
I
See Easy View Setup Section
I
I
Printer Setup
Enter Printer Speed: ..2.!2D
Select Number Of Bits Per Character: 8 BITS 7 BITS
Select Parity: NONE EVEN ODD SPACE MARK
Enter New Une Control Sequence:
IR"
FF
Enter Form Feed Control Sequence:
Enter Number Of Pad Characters: .J:J.O
Select Number Of Characters Per Une: 72 120
Enter Number Of Unes Per Page: ..Q.2.6
Format Run Mode Output: YES NO
Select Printer Type: EPSON DUMB
Select Handshaking Mode: DC1/DC3 DTR
Redirect Run Mode Output: YES
!i9
To: FLOPPV1 FLOPPY2 HRD DSK
Append: NO YES
Name:_ _
Figure 16·1 The Printer Setup menu.
16-2
SEP '95
I
16 Printer Control
16 Printer Control
The INTERVIEW will control most serial ASCn printers. In Program mode you may print
program menus, triggers, the spreadsheet, and the contents of most files. In Freeze mode, you may
print character data, statistics, and protocol and program traces. You may print prompts and
statistics in Run mode (real-time.) Printing is controlled from the keyboard, from the Protocol
Spreadsheet, and from the Printer Setup screen (see Figure 16-3), described later in this section.
16.1 The Connector
A male RS- 232N.24 Printer connector is located on the rear of the INTERVIEW (see
Figure 16-2). The Printer connector is a DCE interface: it transmits to the printer on Pin
3 (RO) and applies ON voltage (+12 V) on Pins 5 (CTS), 6 (DSR), and 8 (CD).
Information can be transmitted asynchronously in 7- or 8-bit ASCII code, with
selectable parity.
For flow-control information, see Section 16.2(K).
1--REMOTE RS-232
PRINTER
Figure 16-2 The printer connector is a 25-pin (DB-25) male connector.
16.2 Configuring the Printer Setup Screen
The Printer Setup screen is shown in Figure 16-3. The various menu fields are described
in this section.
SEP'95
16-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Printer Speed: 2400
Number of Bits: §
Parit~ Selection: ~
Nelli Line: tR't
Form Feed: FF
Pads: ea
Chars per Line: ~
Lines Per Page: 066
Format Run Mode ~put: ~
Printer T~pe: 00Ii00
Pr inter HandshaJ<:Tng Mode:
Redirect Run Mode Output:
To: fifiD Name:
Appe"'n'a"r IB Pr
er Printer Speed: 2400
• G*.".I
..
0_.
7
Figure 16-3 Printer Setup screen.
(A) Speed
Enter the speed of the printer in this field. Default entry is 2400 bps. Maximum
print speed is 19200 bps.
(8) Number of bits
Select the number of data bits (i.e., total bits less parity) which the printer expects in
each byte. Possible selections are
(the default) and
(C) Parity
Select the parity of the printer. Available options are Parity:
, and ';~i_iJ.i. The default selection is fig!!;.
(0) New line
In this field, enter the control character or characters which the printer interprets as
"Start a new line." Alphanumeric, control, and hexadecimal characters are legal
entries. Default new-line characters are 'R'l: (Carriage ReturnlLine Feed). Ifthe
field is cleared and left blank, no new-line characters will be sent to the printer.
16-4
SEP '95
16 Printer Control
(E) Form Feed
Enter the printer's Form Feed control sequence (the control characters which cause
the printer to advance to the top of the next page). Alphanumeric, control, and
hexadecimal characters are legal in this field. You may enter up to four characters.
The default entry is F", (press ~-[lJ or ~, lID, @]; do not use ~, (E), IEJ). If the field is
cleared and left blank, no form-feed characters will be sent to the printer.
(F) Number of Pads
Some printers require pad characters following a new line command so that they have
time to return to the start of the line and advance the paper without losing data.
Following each new line command, the INTERVIEW adds the number of nonprinting
pad characters specified in this field. Only numeric entries from 1 to 99 are legal.
The default entry is O.
(G) Characters Per Une
Select the number of characters to be printed per line. Available options are
(default) and ~~. If your printer's line length is 119 characters or less, choose
Lines longer than 72 characters will wrap to the next line.
If your printer's line length is 120 or greater, choose
characters will wrap to the next line.
Lines longer than 120
(H) Unes Per Page
Enter the length of your printer's page (in lines). The default is 66 lines. Numeric
values from 1 to 999 are legal in this field.
(I) Fonnat Run Mode Output
When Wj§"i is selected (this is the default), the Character or Screen Buffer is
formatted before it is printed. (The data in the buffer is not affected.) The formatted
buffer allows three positions per character and assigns symbols to special characters.
IfiE is selected, the character buffer is transmitted to the printer "as is" in
single-line display with ASCII coding. Format Run Mode Output: tl.?! might be
appropriate if you were monitoring data that had already been formatted for a
printer.
(J) Printer Type
Select the type of printer attached to the INTERVIEW. The options are ;~\ and
(l1M;i.
~*~;
formats the menu screens so that the printouts approximate the
INTERVIEW screen. The default selection,ii_m: , places a carriage return after
each field on the menu.
SEP '95
16-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(I<) Printer Handshaking Mode
The INTERVIEW responds to XON/xOFF control characters sent by the printer.
The control character DC3, interpreted by the INTERVIEW as XOFF, causes
transmission of data to the printer to be suspended. When the INTERVIEW receives
the control character DCI (interpreted as XON), it begins transmitting data to the
printer again.
Select
as the handshaking mode, and the INTERVIEW also responds to
DTR status sent by the printer. When DTR is dropped, transmission to the printer is
suspended.
(L) Redirect Run Mode Output
The default selection is
. Select t~! to write real-time prompts, counters, and
timers to a disk file. To redirect Run-mode output, the Source field on the line
Setup menu must be;:Ii.~t! and the Initial Condition field on the Record Setup menu
must show ilit_~fl. Otherwise, the line and Record Setup menus will override
a Redirect Run Mode Output Eli selection.
When a spreadsheet PRINT action is executed, redirected output is captured on disk
together with a time stamp indicating date, hour, and minute. (You cannot use this
selection to redirect buffer output generated in Freeze mode.) If you use the C print
routines discussed in Section 63, the output will not be time-stamped.
NOTE: Output can be redirected to a file while data is being
recorded in bit- image RAM. Recording to disk, however, overrides
the Redirect Run Mode Output: . ; selection. Once you activate
recording (to disk) via the 8 key, the spreadsheet RECORD ON
action, or the startJcrd ylay C routine, output will be sent to the
printer port. Even if you suspend recording, output will continue to
be directed to the printer port.
When
Screen
is selected, additional entry fields will be displayed on the Printer Setup
To: Enter the destination drive. Selections are
/;JliijQ~~~~?
If.ii~;;:~i;, i;tf;ri~.: j, and
The default is i;;~g<:ml~i~;i
Name: Enter the relative or absolute pathname of the ASCII file to which the
output will be written. This can be an existing file or a new file name. If the
designated file doesn't exist on the destination disk, an ASCII file by that name
will be created.
Append: Default selection is
. Use this selection when you wish to overwrite
the data on an existing file. Select
to append the data to the end of an
existing file.
16-6
SEP '95
16 Printer Control
NOTE: The Append: 1,I;;i,l selection will cause the permanent loss of
data in the existing file. If you wish to save the data already in a file,
use Append: Kg or create a new me name.
Table 16-1
Character Representations on Menu Screen Printouts
Plasma Display
Printout
Special characters:
IE] (TE flag),
Character representation:
\7E
\8M
\DC
!Bl (bit mask),
~ (don't care)
((
))
\(
\)
~ (sync)
\:S
\ (backslash)
\\
Not Equal (bar through
character).
\NE Character.
Example: \NE\7E
Example:C:
Control characters.
Examples: s,. , OX. !=ic
Upper-case mnemonic
(displayed as a backslash followed
by two upper-case characters).
Examples: \SV. \EX, \SX
Hexadecimal characters.
Examples:
5.. ,82 , FF'
Displayed as a # followed by
two printed Characters.
Examples: #54, #82, #FF
16.3 Saving the Printer Setup
If there is a Printer Setup configuration that you frequently or always use, the
INTERVIEW can boot-up with that menu configuration.
Press 8-8 to save the configured Printer Setup menu to a me. The resulting ASCII
file is called print_setup and is located in the /sys directory of the boot drive. During
boot-up, only the /sys directory on the boot drive is searched for this file. If it exists, the
configured Printer Setup is automatically loaded. Otherwise, the INTERVIEW loads the
default Ptlinter Setup.
NOTE: Each time you save the Printer Setup, the contents of
print_setup are overwritten. Rename or write-protect this file if you
want to save its contents.
SEP '95
16-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
If you subsequently load a program (PRGM), object (OBJ), or linkable-program (LPGM)
file, the Printer Setup is not affected since these file types do not include the Printer Setup
menu.
You can also load print_setup from the Printer Setup menu. Press 8-8. Loading this
file does not affect any other INTERVIEW menu screen.
16.4 How to Print Static Displays
While displayed, most menus can be printed individually via the I~! key. (See
Figure 16-4.) Some menus, however, are summary screens for a group of submenus.
Pressing §0-S when these menus are displayed produces a printout of the group of
submenus. Symbols for menu screens and the special characters they represent are listed
in Table 16-1.
(A) Printing The Set of Program Menus
Display the Program Menu screen and press §0-S to print all the Program menus
listed, including the Protocol Spreadsheet. (Trigger menus will not print if they have
not received programming entries.)
(8) Printing the Setup Menus
Press ~-8 with the initial Setup screen displayed to obtain a set of print-outs
for all Setup screens (Line, Display, BeC, Front End Buffer, and Interface Control).
(C) Printing Triggers
Display the Trigger Summary screen. Press [?!i.l to print the summary and (§-~
for as many of the trigger menus as have received programming entries. To print an
individual trigger, display it and press 8.
(D) Printing The Protocol Spreadsheet
Display the Protocol Spreadsheet and press §0-S to print the entire contents of
the Spreadsheet. Press (3 alone to print only that portion of the Spreadsheet which
is visible on the screen. The header of every printed page will include software and
firmware revision levels as well as page number as follows:
S/W v10.00ROM v7.00
INTERVIEW 8800
2129/92
15:02
Page: 1
You may insert a form -feed command to the printer anywhere on the Protocol
Spreadsheet by employing the following string:
16-8
SEP '95
16 Printer Control
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
** Trigger Setup **
Trigger Number: 1
C Receiver: NO
o
NEIA:
NO
DTimeout NO
SFlags: NO
Counter: NO
Xmit Complete: NO
Buffer Full: NO
Keyboard:
YES \CR
Prompt: NO
A Xmit: YES \sy\sy\sXFOX\EX
CFlags:
BCC:GOOD
NO
T Enhance: NO
I Timeouts: NO
o Counters: NO
NTimers: NO
SAlarm: NO
Capture: NO
Select Conditions Or Actions
FI F2 F3 F4 F5
F6
F7
F8
CONDS ACTIONS
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
Figure 16-4 Printout of the Trigger Setup screen (Printer Type: EPSON).
If you have a reverse -video block on the spreadsheet (editor mode), press ~ to
print only that block, no matter how long or short.
This string uses the FF character formed by the keys §9-(iJ, not~, 0, 0. The string
will send a form-feed instruction to the printer.
SEP'95
16-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(E) Printing the layer Setup Screen
Display the main Layer Setup screen and press S - ~ to obtain printouts of the
main screen and all layer-specific setup screens for layer packages that are loaded in.
16.5 How to Print Data
Line data, protocol traces, user traces, program traces, and the contents of the Display
Window can be printed in Freeze mode. Both graphical and tabular statistics can be
printed in Freeze mode or in Run mode (real-time.)
Table 16-2
Character Representations on Data Printouts
Plasma Display
Printout
Alphanumeric characters
(all ASCII noncontrol
except space)
Character is preceded and followed
by a space
Fill symbol
(.r~)
Displayed as three dots (...)
Space
Displayed as a blank space followed
by two letters sp
Special characters
IE! (TE flag}.
Character representation:
lID
(good BCC).
II
(bad BCC)
11
(abort)
[2 (sync)
[F]
[G]
[B]
[AJ
[S]
Control characters
Examples: :;,. , !eX, !J<
Lower-case mnemonic
(displayed as a blank space followed
by two lower-case characters).
Examples: sy, ex, sx
Hexadecimal characters
Examples: SA, 92 , 'F
Displayed as a blank space followed
by two printed characters.
Examples: 54. b2, ff
Lead-state symbols
Character representation:
-
(lead state high)
+
_ (lead state low)
16-10
"'L (lead transition high to low)
\-
.r (lead transition low to high)
/+
SEP '95
16 Printer Control
(A) Printing Line Data
Line data can be set up to print in single-line, dual-line, or data-pIus-leads
formats. Setup information, date, time, offset, percentage, and page number are
printed at the top of each page. The date and time are the current system date/time
when printing data from an actual line; for recorded data. the date/time of recording
is displayed. The symbols for data printout and the characters they represent are
listed in Thble 16-2.
Press (3 to print data which is frozen on the screen. Data is formatted according to
the selection made on the Printer Setup screen-see Section 16.2(1). Figure 16-5
shows the frozen dual-line data screen; Figure 16-6 shows the data printouts at 72
and 120 characters per line.
Press 8-8 to print the entire data buffer from the frozen screen. The data buffer
will continue to print until the end of the data or until you exit and reenter Run mode
(press 8, 8.)
Figure 16-5 Data screen in Freeze mode.
16-11
SEP'95
~~~ ~~
--~--~~-~-~,,-~~-~----~--~------.
_ _---_.
..
--------------~
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
o
o
*MONIDISKlFDl* BLK...ooo18 09/29/89 16:13 Page: 1
ASCllf8lNONEIBOP OFFSET-03809 PERC-59%
spe e h
o
o
o
o
o
o
o
0
sp t est sp t
0
sp Van
C 0 U
v e r spf rom sp Tor
on t 0 cr@ [GJ .............................. ex A "[G] ................................ .
.........•.....•.. sh a dl[G) ex b ell et A Q [G] ex d dl et D h e J I 0 , sp t h i
s spi s spa n spe c h
0 spl
est
Spl 0
spY a nco u v e r spf
....................................... ex a sp[G] sh f ell et a 7 [G] ...... sh h ell et d T
rom sp Tor 0 n Iocr' (G] ........................... sh sh rs[GJ. ..............
est cr ' [G].............................. ex sh . (G] ..................... ex t • [G] sh
............... sh t fs[G] ex & ell et a f [G] ex ( ell et f T e S I cr L [GJ............
,. elIetshT[GJ ...... sh, elIetakT est spa g a i n crd[G] ................ ..
............... sh A sb[O]................................................ sh a enrG) ex j dl
............ ex A ,. [OJ ....................................... ex a ([G) sh n ell et! er[O]
et sh k [G] ex J dl et bs T e S I sp a g a i n cr F [0) ........................... sh
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
o
*MON/DISK/FDl* BLK=OOO18 09/29/89 16:13 Page: 1
ASCIII8/NONEfBOP OFFSET=03809 PERC=59%
spe c h
0
spt est spt
0
spY a
nco u v e r sp fro m sp Tor
o
o n t 0 cr@ (0) ...........................
.................. sh a dl[O] ex b dl et A Q
o
... ex A "[0] .................................
[0) ex d dl et D h ell
s sp i s sp a n sp e c h
t
spt
0
0
0 •
sp t h i
sp t e s
spY a nco u v e r spf
....................................... ex a sp
Figure 16-6 Printout of the data display in Figure 16-5 at 120 ( top) and 72 (bottom) characters per line.
16-12
SEP'95
16 Printer Control
0
0
0
0
0
0
0
0
0
0
0
0
0
0
*MONJDISKfFD1* BLK=OOO17 09/29/89 16:13 Page: 1
ASCIII8/NONEIBOP
Nr Ns PIF SIZE TIME
BCC
SRC ADDR TYPE
[G]
1613:30.687
0
0002
DCE 03 DISC
0 0002 1613:30.714 [G]
DTE 03 UA
1 0002 1613:30.835 [GJ
DTE 01 SABM
1 0002 1613:30.897 [G]
DCE 01 UA
0
0 0007 1613:30.934 [G]
DCE 03 INFO
0
0 0 0006 1613:30.938 [G]
0
DTE 01 INFO
0 0002 1613:30.962 [G]
DTE 03 RR
0 0002 1613:31.001 (G]
1
DCE 01 RR
0 0025 1613:31.199 [G]
01
INFO
1
DTE
0 0002 1613:31.264 [G]
2
DCE 01 RR
1 0 0007 1613:31.398 [GJ
2
DCE 03 INFO
0 0002 1613:31.422 (G]
2
DTE 03 RR
2 2 0 0005 1613:31.452 [Gl
DTE 01 INFO
0 0002 1613:31.518 [GJ
3
DCE 01 RR
3 0 0023 1613:31.709 {G]
2
DTE 01 INFO
0
0
0
0
0
0
0
0
0
0
0
0
0
FIgUre 16-7 Layer 2 Protocol Trace printout in Freeze mode.
(8) Printing Protocol Traces
Protocol traces can be printed in Freeze mode via the 8 key. Press ~ to generate
a printout of the current screen (see Figure 16-1). Press §J-8 to print the entire
buffer from the frozen screen. Printing will be aborted if you leave Freeze mode.
SEP '95
16-13
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(C) Printing Program Trace
The Program Trace can be printed in Freeze mode via the 1~1 key. Press 8 to
generate a printout of the current screen (see Figure 16-8). Press 8-~ to print
the entire buffer from the frozen screen. An explanation of Program Trace can be
found in Section 6.
0
0
*EMDCElLINE* BLK""OOOOO 12102189 13:01 Page: I
0
0
0
0
0
0
0
0
0
0
0
0
0
ASCIIJ8INONEIBOP
Program Trace
Layer 3 Test fips_moduIe_a20 state begin_init
restartJeq sent
restart_con recvd
Layer 3 Test fips_module_a20 state can
incoming call sent
Layer 3 Test fips_module_a20 state p3
call_accept recvd
Layer 3 Test fips_module_a20 state bad_PR
invalid peR) sent
Layer 3 Test fips_module_a20 state complete_init
reseCreq recvd
Layer 3 Test fips_module_a20 state tesC06
resecc too long sent
Layer 3 Test fips_module_a20 state pass_faiJ
timeout: no resetJeq
** test failed
**
0
0
0
0
0
0
0
0
0
0
0
0
0
Figure 16-8 Program Trace printout in Freeze mode.
16-14
SEP '95
16 Printer Control
o
o
o
o
o
o
o
o
o
o
o
o
o
*MONIDISKlFDl * BLK=OOO17 09/29/89 16: 13 Page: I
ASCWS/NONEIBOP
o
Echo time in milliseconds:
120
240
360
480
o
o
o
600
No. of samples:
XXX:XXXXXXXXXXXX
6
4
2
10
8
o
o
o
o
*MONIDISKlFDl * BLK-00017 09/29/89 16: 13 Page: 1
ASCW8INONEIBOP
Name
echo
samples
Current Last Minimum Maximum Average
o
3
248
341
452
Unit
407.00 MSECS
o
Figure 16-9 Printout of graphical (top) and tabular (bottom) statistics in Freeze mode.
(O) Printing Statistics
Tabular and graphical statistics can be accessed via softkey in Program mode and Run
mode (frozen and real-time). Either of the statistics screens also may be accessed
via the ~ key if *m~~;;r is the Display Mode selected on the Display Setup menu.
Once a statistics screen is displayed, press 8 to send the current statistics to an
attached printer. Figure 16-9 is an example of graphical and tabular statistical
printouts.
16-15
SEP'95
------_._-_..
_---_..
_----------------------_.-~.-.---,
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
0
0
0
0
0
*MON/DISKlFDl * BLK-OOloo 08/23/89 10:04 Page: I
EBCDICl8INONElBOP
0
-> active pU:'Cl pu status:HOST_SENDING
0
0
SNA STATISTICS
Special Events
0
0
0
0
Primary
0
0
Secondary
0
3
96
0
0
0
Negative Response
7
0
Invalid FID fonnat
0
0
CRCerrors
Retransmissions
Aborts
0
0
0
link startups:
elapsed time:
0
0
0
last sense data:
lastFID:
0
0
0
0
reset count:
348 sees
\()8\1 E\()(J.OO
sample count:
from device:
0
77
0
\00
0
2
enter for stats menu for main menu
Figure 16-10 Printoutofascreen from theSNAStaruticsapplicationsprogram (OPT -951-19-1)
from the Display Window.
(E) Printing from Display Window
Customized screens, such as those in applications programs, can be printed in Freeze
mode from the Display Window. Press I-l to generate printouts like that in
Figure 16-10.
16-16
SEP '95
16 Printer Control
(F) Printing User Traces
User traces can be printed in Freeze mode. Video enhancements are not indicated
on the output. Press ~ to generate a printout of the current screen. Press ~-I-I
to print the entire buffer from the frozen screen. User traces are explained in Section
6.
16.6 Spreadsheet Control of Printing
The Protocol Spreadsheet allows PRINT as a spreadsheet action. This causes the
IN1ERVIEW to respond to a predetermined condition and print a line of tabular statistics
for an accumulator, counter, or timer; or print a user-prompt that is sent to the printer
after it has been written to the second line of the screen. (See Section 31 for an
explanation of spreadsheet-controlled printing.)
The library of C routines includes several print functions. See Section 63.
16.7 Printing Disk Files
Files stored on disk can be printed from the File Maintenance menu. See Section 15.3.
SEP'95
16-17
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
16-18
SEP '95
17 The Time-at-Day Clock
17 The Time-of-Day Clock
17-1
SEP '95
- -
-
--
------------------------~--------------------
---'"----------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Utility Menu
Select Desired Utility Screen:
F1
I I F2 I I F3 I I F4 I I F5 I I
".I OT/TIME
PRINTER
O/MAINT
Mise
ezsETUP
F6
II
F7
II
Fe
I
See Color Display Section
See Easy View Setup Section
Datemme Setup
....L-L..
Current Date:
(Status field - - No Entry)
See Disk Maintenance Section
Current Time:
(Status field - - No Entry)
....L-L..
Set Date:
(Enter Date As MM/DDIVY)
-
Set Time:
(Enter Time As: HH:MM)
See Printer Contro! Section
Figure 17-1 The DateITime Setup menu.
17-2
SEP '95
17 The Time-of-Day Clock
17 The Time-of-Day Clock
The INTERVIEW has a battery-operated real-time clock. The day, month, and year as well as
the current time, posted to the second, are automatically accessible as soon as you power on the
INTERVIEw. Used to time/date stamp recorded data, it is also available as a Trigger Condition on
the Protocol Spreadsheet. The time and date can be reset on the DatelTime Setup screen, which is
a submenu of the Utilities menu.
A sample menu is shown in Figure 17-2. The current date and time appear at the top of the screen.
The time is updated on the screen every second. The clock retains time and date even when
powered off and adjusts itself to accommodate the length of each month. It also takes leap years
into account automatically. The clock menu does, however, permit you to reset the time or date, if
required.
To reset the date, select the Set Date field and enter month, day, and year in that order in the
two-digit space provided (mm/dd/yy). Use 8, S, or 8 to move into each field. The month and
day entries may be either one or two digits; it is not necessary to enter a leading zero. If only one
digit appears in any of the two-digit fields, a leading zero is assumed. You may fill in the month,
day, or year fields individually, if you prefer. (For example, if your only entry is l..J in the month
field, only the month will be altered-it will be set to OIl-when you press (§).)
In the Set Time field, hour and minute entries are made as hh:mm in a 24 hour format. (The seconds
setting cannot be altered.) You may set the hour and the minutes fields simultaneously or
individually. As with the date field, a single-digit entry is assumed to have a leading zero.
Figure 17-2 shows the menu filled in to change the date and time to March 1,1992 and 1:30 p.m.
Figure 17·2 The real-time clock in the INTERVIEW is controlled on the
Date/Time Setup screen.
To set the clock, press the §) key when you have entered the correct date or time. Once the dock
is reset, the status fields Current Date and Current nme should match your entries.
SEP '95
17-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
17-4
SEP '95
18 Color Display
18 Color Display
~.
(
,
SEP '95
18-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
** Mise Utilities **
From B/W ENHANCE
.aw
.BIiY
J.QW
OFF
OFF
OFF
OFF
ON
ON
ON
OFF
OFF
ON
ON
OFF
OFF
ON
ON
ON
OFF
ON
OFF
ON
OFF
ON
ON
To COLOR DISPLAY
g~~
O~}
OFF
OFF
OFF
OFF
ON
ON
ON
(Slatic Values)
.2~
BLU
BLK
BLK
BLK
GRN
BLU
BLK
BLK
GRN
!.~
~
GRN
BlU
BLK
BLK
GRN
}
(Selectable fields,
mapped to Static
Values)
Select Background Display Color:
BLACK GREEN BLUE YEllOW
RED CYAN PURPLE WHITE
-
Select Foreground Display Color:
BLACK GREEN BlUE YELLOW
RED CYAN PURPLE WHITE
" - Select Blink Attribute:
OFF ON
F1
II
F2
II
F3
II
F4
II
F5
II
F6
II
F7
II
F8
Figure 18-1 The Miscellaneous Utilities menu.
18-2
SEP '95
18 Color Display
18 Color Display
Both black and white and color monitors can be used as external displays. Separate connectors are
provided for each type of monitor on the rear panel of the INTERVIEW. For both monochrome
and color displays, a set of video enhancements can be controlled from the INTERVIEW. For color
displays, the enhancements are mapped on the Miscellaneous Utilities screen. Available options on
this screen are shown in Figure 18-1.
18.1 Connectors for External Monitors
Connect a monochrome (black and white) monitor to the RS-170 connector. This is the
round connector located to the far right of the rear panel (see Figure 18-2).
Figure 18-2 Video-out connectors for RS-170(black andwhite ) and ROB (color) signals are located
on the rear panel of the INTERVIEW.
Connect an 8 or 16-color monitor to the 9-pin RGB connector at the right of the rear
panel (see Figure 18-2). Pin configurations for the RGB connector are shown in Appendix
E.
18.2 Color Control from the Miscellaneous Utilities Screen
Three of the data enhancements available as trigger actions (Blink, Reverse, and Low; see
Figure 18-3) are applied differently when a color monitor is attached. There are eight
possible on/off combinations for these three trigger enhancements. The user defines these
eight combinations on the Miscellaneous Utilities screen.
SEP '95
18-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 18-3 The settings in the Trigger Enhance field (0 = off; 1 = on) are mapped to color and blink
definitions selected on the Miscellaneous Utilities screen. The Hex setting does not pertain to screen
colors.
The color setup portion of the Miscellaneous Utilities screen is shown in Figure 18-4. The
screen is divided into two areas: the enhance combinations on the left - hand side of the
screen; and the selectable display options on the right. User entries are made only on the
right-hand portion of the screen.
Figure 18-4 Trigger settings on the left are mapped to user-defined blink and color characteristics,
selected on the right.
(A) Black and White Enhancement List
The eight enhancement combinations are labeled "From B/W ENHANCE." Each
row of three settings (ON/OFF for Blink, Reverse, and Low) represents one
configuration of a trigger Enhance field.
(8) Selectable Color Display Options
The user selects blink, foreground color, and background color options on the right
half ofthe screen, labeled "To COLOR DISPLAY." Use the cursor keys or the ~
key to move from field to field. The aiiiJ and !Ii) keys rotate among the various
selections within a field. The options which you define are matched to the static
combinations to the left in the same row. Thus, when you create a trigger action
Enhance:
Rev:..Q Blnk:..Q Low:..Q, you are specifying that displayed DTE data take on
the color characteristics defined in the first row of the Miscellaneous Utilities screen.
(The Hex enhancement on a trigger does not influence color options.)
18-4
----~--~---
SEP '95
18 Color Display
1. Blink. The frrst column under COLOR DISPLAY, labeled BLNK, determines
whether blink is to be turned on or off in response to the trigger entry on the left.
2.
Character. The center column, labeled CHAR, determines what color is assigned
to the screen foreground (that is, the characters themselves) in response to the
trigger Enhance entry on the far left Possible foreground colors are black, green,
blue, yellow, red, cyan, purple, and white.
3. Background color. The right-hand column, BACK, defmes screen background
color (that is, the square background around subsequent individual characters) in
response to the trigger entry on the far left. Color possibilities are the same as
for foreground.
NOTE: Never use the same foreground and background color on the
display if you have an eight-color monitor. (Data will not be visible.)
If you have a 16-color monitor, you may be able to choose the same
color in the background and the foreground and retain a contrast
between data and the surrounding screen. Check the documentation
for your monitor.
(C) Trigger Control of Color
When you enter the three-bit enhancement option as an Enhance action on a Trigger
Setup screen (see Figure 18-3) or as a Layer 1 ENHANCE action on the Protocol
Spreadsheet, you are designating the color scheme which the screen will adopt
whenever that trigger becomes true. More specifically, you are indicating what color
the next character becomes (foreground color), whether the character blinks, and
what color the small rectangular box surrounding the character will be (background
color). These three characteristics apply to subsequent characters and their
background until another trigger alters the color scheme.
ENHANCE actions above Layer 1 are applied to specific lines on the protocol-trace
display for the given layer. REVERSE, BLINK, and LOW selections may be configured at
Layer 3, for example, so that a Call Request packet receives a different color
enhancement from a Clear Request.
When you program a trigger, only the Enhance entries for Blnk, Rev, and Low
influence screen characteristics. (The Hex field always causes characters to be
displayed in hexadecimal, or turns off the hexadecimal character enhancement.) An
Enhance entry of 1 equates to "ON"; an entry of 0 equates to "OFR"
NOTE: A "Don't Care" (X) after Blnk, Rev, or Low leaves the
enhancement at its previous setting, making the color which results
from the trigger dependent on the effects of previous triggers.
SEP '95
----------_._-----
18-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Each time you run the program, all enhancement settings are initially reset to zero. If
no trigger entries are made, or if the enhance trigger never becomes true, the color
monitor retains its own color settings. (Refer to the technical documentation for the
monitor to determine how colors are set internally.)
(0) Color Graphics
Several colors are offered for bar graphing on the Graphical Statistics menu. These
colors are always displayed against a dark background. Their use is not related to the
color setup screen. See Section 22 for a description of color graphics.
18.3 Black and White Data Enhancements
Blink and reverse data enhancements for the INTERVIEW's plasma display are available
when a monochrome monitor is installed. In addition, a low intensity enhancement can be
produced on a monochrome monitor. These display highlights are controlled by triggers
(see Figure 18-3), either on the Protocol Spreadsheet or on Trigger Setup screens. Refer
to Section 26 or 32 for a description.
18-6
SEP '95
19 Easy View Setup
19 Easy View Setup
SEP '95
19-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Utility Menu
Select Desired Utility Screen:
I
II
F1
DT/TIME
II
F2
PRINTER
F3
D/MAINT
II
F4
II
MISC
II
F5
F6
II
F7
II
Fa
I
EZSETUP
I
I
See Color Display Section
See Disk Maintenance Section
Easy View Setup
See Printer Control Section
See Time-of-Day Clock Section
Enable Easy View: YES NO
Enter Easy View After Power-Up: YES NO
Keep Easy View Menu Information in Memory: YES NO
Display Program Waming Messages: YES NO
Load Program Edit Timeout: .lll seconds
Screen Saver Timeout: QQ minutes
Figure 19-1 The Easy View Setup menu.
19-2
SEP'95
19 Easy View Setup
19 Easy Vi,ew Setup
There are five parameters that control Easy View operation. They are set in the Program-mode
Easy View Setup screen. See Figure 19-2. To access this screen, press UTIL, EZSETUP from the main
Program menu.
**
Enable
Eas~
tup
**
View:
Enter Eas~ View After Power-Up:
III
Keep Eas~ View Menu Information In Memor~:
III
Displa~
III
Program Warning Messages:
~
Load Program Edit Timeout:
Screen Saver Timeout:
Figure 19·2 The Easy View Setup screen.
seconds
00 minutes
-
The default selection of each parameter on the Easy View Setup menu is
. If you press
8-8, the configuration of this screen is saved in a file called ezviewJetup in the /sys directory of
the boot-up disk. Once saved, the parameters are automatically loaded during boot-up.
19.1 Enable Easy View
The first parameter determines whether or not the 8 key is enabled. The default
selection is _1:. Once enabled, 8 moves the user back and forth between
Program-mode screens and Easy View menus. (See Section 4.) Setting this parameter to
disables access to the Easy View menus. An alarm sounds if you press I"" vul when it is
disabled.
19-3
SEP '95
-
-------
------------------------------------------------_._--
INTERVIEW 8000 Series Basic Operation: 951-80424-01
19.2 Enter Easy View After Power-Up
The second parameter determines whether the INTERVIEW enters Program mode or
Easy View following boot-up or a manual reset from the keyboard.
If you set this field to
• there is a five-second pause at the power-up screen before
you see the first Easy View menu. Use the I~l key to exit Easy View and access
Program -mode screens.
NOTE: During boot-up, the INTERVIEW checks the boot-up disk
for a file named lusr/default and the hard disk for a file named
lusr/user_intrf (See Sections 2.1 and 2.2.) If it locates either, it does
not enter Easy View following boot -up regardless of the setting of
this parameter.
If you select
the INTERVIEW is in Program mode at power-up. Use the 8
from any Program-mode screen to enter Easy View.
key
19.3 Keep Easy View Menu Information in Memory
The third parameter controls whether the contents of the mstrmenu.cmp file and the most
recently accessed text file are held in memory while the INTERVIEW runs a selected
program. mstnnenu.cmp is the Easy View menu information file that contains all of the
information needed to present the menu screens and permit the user to interact with
them. This compiled file resides in the IMENU directory on the hard disk.
Easy View keeps track of your path through the menus, even after you have exited Easy
View. Each time you return to Easy View, you are automatically located in the same menu
from which you exited. When this field is
, you can exit Easy View to run an
application program without losing your place in the menus.
If you select
your position in the Easy View menus is lost whenever you load a
program or layer package. When you return to Easy View, the first menu in the hierarchy
is displayed. It is possible that a program you select to run from Easy View may be too
large to compile with mstrmenu.cmp and a text file in memory. In this case, set this
parameter to
19.4 Display Program Warning Messages
By default, the warning message shown in Figure 19-3 is displayed whenever you select a
program to run from an Easy View menu. The message is displayed before the program is
loaded and indicates that loading the program will result in the current setup parameters,
triggers, and spreadsheet being overwritten.
If you do not want this message presented, disable it on the Easy View Setup screen. You
may also disable the warning message temporarily (until the INTERVIEW is turned off)
by pressing !QJ when the message is first presented.
19-4
SEP '95
19 Easy View Setup
MENU of SNA Statistic Programs
3
Loading this program wi 11 overwrite the triggers~
spreadsheet and parameters now in memor\::l. Proceed?
Press:
~
n
d
to load the program
to return to the menu
to disable this warning
Ut iIi z at ion, Frame and Character Rates, Errors, etc.
1".&. move selection bar
+- move to prev menu
-+
move to next menu
? = Help
RETURN select menu entr~
HOME
move to top menu
EZ VU exit/enter menus
Figure 19-3 A warning message displayed prior to loading a program.
19.5 Load Program Edit TImeout
In this field, specify a length of time that the IN1ERVIEW should provide for editing Easy View
setups. The default timeout is 10 seconds. Any value in the range 1-999 is valid as a timeout. If
you leave the field blank, or entet: a zero, the program will run, bypassing the editing screen.
This feature is particularly useful during remote operation. By entering a timeout, you can
ensure that the remote unit will not enter Run mode before you have a chance to edit program
parameters.
19.6 Screen Saver Timeout
The IN1ERVIEW's Screen Saver Timeout feature allows the user to specify the number of
minutes the screen display remains visible when the keyboard is not in use. The screen saver
blanks the internal EL display as well as any optional direct external displays of the unit, such
as an external color monitor and an external RS170 (monochrome monitor); it also disables
the unit's keyboard so that any key pressed will only restore the display. However, any PC
remotely controlling the unit is unaffected by the screen saver.
The default for the Screen Saver TImeout field is zero minutes, which means no timeout is
requested and the screen remains displayed. Enter any integer in this field in the range
1-99 to specify the number of minutes the display remains visible before the screen goes
blank. Press ~ to update the Screen Saver Timeout entry; press 8-8 to save the setup.
To return the display to the screen after the unit times out and the screen blanks, press any
key as stated above. (Note that any key pressed will unblank the screen only; normal key
usage is not in effect with a blank screen but will be restored after the screen display returns.)
SEP '95
19-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
19-6
SEP'95
20 Easy View Maintenance
20 Easy View Maintenance
SEP '95
20-1
(a) Automatic Installation
(b) Create Versions
(c) Install Your Own Program
CAUTION: Before you begin,
make a backup copy of HRD/
MENU/mstrmenu.txt.
CAUTION: Before you begin,
make a backup copy of HRD/
MENU/mstrmenu.txt.
CAUTION: Before you begin,
make a backup copy of HRD/
MENU/mstrmenu.txt.
Access Easy View Maintenance
program.
Access Easy View Maintenance
program.
Place diskette with application
program in FD1.
Place diskette with application
program and script file in FD1.
Press the spacebar (or other key)
to access the Easy View Maintenance Help screen.
Press § i begin the automatic
installation.
Press FNAM ED softkey. Identify
source and destination script files for
merging and source and destination
files for ...nmnlIInn
When installation is comPI:e, p~ss
any key and then
to r um the
Easy View menus.
Use automatic Installation to add ARsupplied application programs to the
Easy View menus.
Press LOAD softkey. Source
script file is loaded.
Press PROG ED softk~ FimlPro.m of
interest. Press
• ~ ~.
t~
entry to create a new version of the original
nrnnr~n
Press MERGE softkey. Source script file
is merged with destination script file.
Press COMPILE softkey. Source file Is
compiled as destination file. All verSions have been added to the Easy
VIew menu
Press ~ return to the Easy
View menus.
If you want multiple versions of a program to be
selectable from Easy View menus, use the Easy
View Maintenance program to create new
versions.
Create a script file for your program on
Protocol Spreadsheet. Mark it as a block
press • BLOCK,[iii;bUT. WRITE/U,
FD1/MENUlinst8lf.txt to save.
Press §3Access Easy View Maintenance program.
Press E3 begin an automatic
installation of your program.
When installation is compl:e. p~ss
any key and then
to r um the
Easy View menus.
To install one of your own programs into
an Easy View menu, create a script file
and then perform an automatic
installation.
(d) Edit mstrmenu.txt
CAUTION: Before you begin,
make a backup copy of HRD/
MENU/mstrmenu.txt.
Access the File Transfer Shell program.
Transfer mstrmenu.txt out of the INTERVIEW
to a local PC.
Use the PC's word processor to
make your desired changes.
Transfer the text back to the INTERVIEW.
Access the Easy View Maintenance program.
Press the spacebar (or other key)
to access the Easy View Maintenance Help screen.
Now press the COMPILE softkey to compile this new version of mstrmenu.txt. It
is automatically saved as mstrmenu.cmp.
Press ~ return to the Easy
View menus.
Although not recommended, you can
directly edit mstrmenu.txt on the
INTERVIEW's Protocol Spreadsheet. The
preferred method, however, is to export it
from the INTERVIEW.
Figure 20·1 Overview of the different uses of the
Easy View Maintenance program.
20 Easy View Maintenance
20 Easy View Maintenance
This section addresses the Easy View Maintenance program, one of the selections on the Utilities,
Model and Demonstration Programs menu. See Figure 20-2. It also provides information on
creating and editing script files used in the installation procedure.
Utilities, Model and Demonstration Programs
2
File Transfer Shell
FDl Install 'ile
FD2 Install File
Make Director~ Trees
HRD Tree
FDl Tree
FD2 Tree
...... MORE U
Install Application Programs and Create New Versions
~~
move selection bar
+- move to prev menu
-+ move to next menu
?
= Help
RETURN select menu entr~
HOME
move to top menu
EZ VU exit/enter menus
Figure 20-2 Easy View Utilities, Model and Demonstration Programs menu.
Figure 20-1 provides an overview of the different uses of the Easy View Maintenance program.
Typically, you will use the Easy View Maintenance program to install AR -supplied application
programs or your own programs into the Easy View system. You can also use it to create multiple
versions of these application programs-for example, versions with different line speeds or line/disk
source selections. Then, all versions are selectable from the Easy View menus.
The Easy View Maintenance program adds entries to the menus. It cannot modify, reorder, or
remove existing menu entries. Whenever you add a selection to an Easy View menu, you are
modifying the Easy View menu file.
20.1 The Easy View Menu File
The menu information file, mstrmenu.cmp, contains all of the information needed by the
Easy View system to present the menu screens and permit the user to interact with them.
This compiled file must reside in the IMENU directory on the hard disk.
SEP'95
20-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
The source text file (also referenced as the script file) for mstnnenu.cmp is an ASCII file
named IMENUlmstrmenu.txt. All script files, including mstrmenu.txt, follow the format
explained in Section 20.5.
When you perform an automatic installation of an application program (or customized
versions of an application program) via the Easy View Maintenance utility, the INTERVIEW
incorporates script information about the new program(s) into mstnnenu.txt and then
generates a new version of mstrmenu.cmp.
20.2 Accessing the Maintenance Program
Regardless of which function you want the Easy View Maintenance program to perform,
first go to the Utilities, Model and Demonstration Programs menu-from the Easy View
Main menu, position the selection bar over the UTIUTlES menu item and press~. Now
position the bar over Easy View Maintenance, as shown in Figure 20·2. Press ~ again. You
may be questioned about whether or not you want to load the program. If so, press 0.
Then, the screen shown in Figure 20-3 should appear.
NOTE: The instructions in this section assume that you are currently
in the Easy View system. See Section 4 on Easy View general
operation and Section 19 for information on enabling Easy View.
*
=B~L~K~=______
****
****~~~~~
~~~Ar~ ~~~~~*~~*~
*~~*~* ~~~
*~~
~~*~4'~~ ~~
m~mm
~* ~~ ~~~.$Y~~~
~~* ~~~ ~~
~**~ m ~~m
***
~*** *~ ~~* *~
**9%~
~**
~~~ ~**
***
~~*
****
~~*~
**~
*~~
**9%~
Eas~
06/21/90 09:15
View Maintenance Program
Version 1.02
Cop~right(c) 1990
Telenex Corporation
All Rights Reserved
This program loads, merges (installs) and compiles Easy View
menu files and customizes Eas~ View programs.
.
Enter To Perform Automatic Installation
Enter
Othe
To Custom ze Pro rams
--~~
Figun 20-3 Easy View Maintenance Program.
This screen identifies the Easy View Maintenance program (and its version number) and
gives a general description of its scope and purpose. Decide which function you want the
program to perform.
20-4
SEP'95
20 Ea§Y View Maintenance
CAUTION: Before you begin, we strongly recommend that you make a
backup copy of mstrmenu.txt
To begin an automatic installation, press S
Press a key other than 8
20.4.
from this screen. See Section 20.3.
to access the screens for customizing programs. See Section
20.3 Automatic Installation
A library of selected application programs has been factory-installed in theAR_APPS
directory of the hard disk. The subdirectories under AR_APPS categorize these programs
by protocol and function. (See Section 20.7 for more information on the directory
structure.) Additional AR -supplied application programs, available as options, may be
added to the Easy View menus via the Easy View Maintenance utility.
If you do not need customized versions of a new application program and want to perform
an automatic installation, place the diskette containing the application program and its
script fIle into FDI, the left-hand floppy disk drive. (The script file that accompanies all
AR -supplied application programs is named /MENU/install.txt and resides on the same
program diskette.) Press 8 from the Easy View Maintenance program start-up screen
(Figure 20*3).
The INTERVIEW automatically installs the application program into the appropriate
Easy View menu so that it may be loaded, compiled, and run from Easy View. The
INTERVIEW looks to FDI for the program's script fIle and then merges it into
rnstrrnenu.txt on the hard disk. Finally, the revised rnstrmenu.txt is compiled to create an
updated version of rnstrrnenu.cmp.
If you press E3 to abort the process and exit the program, you are returned to the
Utilities, Model and Demonstration Programs menu. Once the installation is complete,
press any other key. The Easy View Maintenance Help screen is presented. See
Figure 20-13. To return to the Easy View menus, press 8.
You may also use the automatic installation feature to add selections to the Easy View
menus for your own programs. First, however, create the script fIle the Easy View
Maintenance program needs to perform an installation and save it to FDI as
/MENU/instaILtxt (the default name for the source script file during automatic
installation). See Section 20.5.
~,
('
j
1;
j
"
SEP '95
20-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
20.4 Customizing Programs
Refer again to Figure 20-3. Notice that if you press a key other than 8, you can
customize the setups of application programs. Use this feature to create multiple versions
of a program.
An overview of the screens and commands used in creating program versions is presented
in the example below. Detailed explanations for screens and commands are presented in
the sections which follow.
(A) Example
Before we begin, make a backup copy of mstnnenu.txt.
For this example, we will load the script file mstrmenu.txt and create a new version of
the Easy View ASYNC monitor program, Standard ASYNC Setup.
Access the Easy View Maintenance program. Then press the spacebar, or some other
key except 8 , to present the Easy View Maintenance Help menu. See Figure 20-4.
*
Eas~
VlE"W r'1alnt.enance
Pr'ogram
\ler'slcn
1.:02
(F)NAM ED
Filename Specification Editor
(L)OAD
Load Menus/Programs From Source Menu File
(P)ROG ED - Program Specification Editor
CM)ERGE
Merge Loaded Menus/Programs Into Dest. Menu File
(C)OMPILE
Compile Master Menu From Text To Compiled
CE)RRORS
Error Displa~ Screen
(H)ELP
This Help Screen
Figure 20-4 Easy View Maintenance Help menu.
This screen provides a brief description of the available screens and commands.
First, we need to indicate the script file we want loaded. The program we want to
create new versions for is in this file. Identify the file on the Filename Specification
Editor screen. Press FNAM ED. 'JYpe over the existing entry to change the name of the
Source (Load From) Menu File Pathname toHRD/MENU/mstnnenu.txt. See Figure 20-5.
For now, leave the other entries intact.
20-6
SEP '95
20 Easy View Maintenance
*
Source (Load From) Menu File Pathname:
HRD/MENU/mstrmenu.txt
Destination (Merge To) Menu File Pathname:
HRD/MENU/mstrmenu.txt
Master Menu Text (Compile From) File Pathname:
HRD/MENU/mstrmenu.txt
Master Menu Compiled (Compile To) File Pathname:
HRD/MENU/mstrmenu.cmp
Figure 20-5 Load mstrmenu.txt for editing.
Now press LOAD. All of the setups for all of the programs you can access from Easy
View menus are loaded from mstrmenu.txt.
Press PROG ED. The screen shown in Figure 2()"6 should appear.
Item Name: AUTOMON
I t em De s c r i~P!l:;t:Wiwo~n~:~P""'r-e-s-s-<""""R-==E""=T""U"""R::::N~>--::"'t-o---.::A....u-t,...o-m-a..,-t,..-i-c-a.....,,-l....l-H-.."C....o-n-f..,....,..i-g-u-r-e---'L-"-i
Dest. Pathname: HRD/AReAPPS/RUTOMON/AutomonStd
Idle Suppress: III
DTE: ~ DeE: ~
Buffer Control Leads:
Time Ticks: • H
Mode:
Source:
Block
:
Clock Sour
INT/DTE:
NRZI: . .
III
Capture Memor~:
Data To Captur .
Initial
Figure 2(}·6 This screen shows the setup for theAUTOMON selection on the Easy View Main menu. The
setups for all Easy View programs are contained in mstnnenu.lXt.
20-7
SEP'95
-
-------------------_._--_._--_..
_-------------_._-------
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
Look at the Item Name field at the top of the screen. The names in this field match
selections on the Easy View menus. Use the ~ key to scroll through the listings
from mstrmenu.txt. Watch the Program number in the lower right- hand corner of the
screen. When it reaches 18, you should find the entry for Standard ASYNC Setup. It is
illustrated in Figure 20-7.
Idle Suppress: III
DTE: ~ DCE: ~
Buffer Control Leads:
Time Ticks: III@I
Mode:
Source:
Block 0:
Clock Sour
INT/DTE:
NRZI: . .
Capture Memar!::!:
Data To Captur .
Initial
St
At-
Pr'ogram
811
18
Figure 20-7 This screen shows the setup for the Sumdard ASYNC Setup selection on the
Menu of ASYNC Monitor Programs. This setup is part of mstrmenu.txt.
Press 8 to keep this entry accessible in the program listings.
Now press S-ITI. The dummy entry shown below is inserted into the listing. Do
not directly edit this entry. Dummy entries are place holders only.
20-8
SEP '95
20 Easy View Maintenance
*
Item Name: Item18
Item Descri4p~tUi~0~n~·~:~D~e-s-c--r~i-p~t~io--n~1~8~----------------------------------Dest. Pathname: HRD/filename18
Mode:
Source:
Block
:
Clock Source:
INT/DTE:
NRZI: . .
Idle Suppress:
DTE:
DCE:
Buffer-Contr
Time Ticks:
III
ads:
III
Capture Memorl:j:
Data To Captur
Initial
Figure 20-8 Press ~-~ to create a dummy entry.
Instead, press 8. The dummy entry is overwritten by a numbered version of the
(Standard ASYNC Setup) program you just saved. See Figure 20-9.
III
Idle Suppress:
DTE: ~ DCE: ~
Buffer Control Leads:
Time Ticks: • •
Mode:
Source:
Block
:
Clock Sour
INT/DTE:
NRZI: . .
III
Capture Memorl:j:
Data To Captur .
Initial
FlgUre:zo.9 Numbered version of an Easy View program. Edit this entry to create your own version.
This is the entry we will edit to create a new version of this program. (The original is
still in place; press (Ji) to view it. Then return to the numbered version by pressing
mil.)
SEP'95
20-9
INTERVIEW 8000 Series Basic Operation: 951-80424-01
For this example, we will create a version of the Standard ASYNC Setup program
that monitors a line speed of 9600 bps. Text you type on this screen overwrites
existing text. The 8 and [3 keys move the cursor within a field. 8, I±], and ff.l move
the cursor between fields.
NOTE: Line speed, and other selected line-setup parameters, can be
changed on-line before the program is run. See Section 4.4(C). These
edited Easy View parameters remain in effect until you change them
again, or until the unit is powered off. If you want the changes to be
permanent, use the Easy View Maintenance program as described below.
Type in a new Item Name: Standard A SYNC Setup (9600).
The Item Description field contains the text that appears toward the bottom of Easy
View screens when the selection bar is over the menu item. Change this entry to read
Standard ASCII Setup to Monitor at 9600 bps.
The Dest. Pathname field identifies the name and location of the program to run when
the menu item has been selected. Give our new program the following pathname:
HRD/AR_APPS/ASYNC/MON/ASYNC96Set.
Now we are ready to modify the setup for the program. The only change we want to
make is to the line speed for internal clock. Use the ~ key to move to the INT/DTE:
field. Change the speed from 2400 to 9600.
The information for our new version is complete. See Figure 20-10.
Idle Suppress: III
DTE: ~ DCE:.1.
Buffer Control Leads:
Time Ticks: II1II
Mode:
Source:
Block
:
Clock Sour
INT/DTE:
NRZI: III
III
Capture Memor~:
Data To Captur
Initial
At-
Prograrr-
if?
Figure 20-10 This setup for a new version of the Standard ASYNC Setup program will be added to
mstrmenu.txt when the MERGE command is executed.
20-10
SEP '95
20 Easy View Maintenance
To incorporate this information into the existing mstrmenu.txt file, press the MERGE
softkey. There will be an indication of errors at the end of the merge operation.
Press the ERRORS softkey to view error messages. See Figure 20-11.
Figure 20-11 The Error Display screen.
-
The message you see indicates that an attempt was made to copy the help file that
exists for the original Standard ASYNC Setup program. Duplicate copies of help
files by the same name cannot be made. You can disregard this message, however,
since the help file for the original will still be accessible and generally applicable for
our new menu item.
Now press the COMPILE softkey. This command recreates the menu information file.
Press ~ to return to the Easy View menus. If not already at the top of the menu
hierarchy, press 8 to return to the first location on the Easy View Main menu. Use
the l±l key to move the selection bar to ASYNC and press 8. Select the MONITOR item
on the Menu of ASYNC Program Types, Tutorial(s) & How To's. Press 8. Our new
version of the Standard ASYNC Setup program appears at the end of the Menu of
ASYNC Monitor Programs. See Figure 20-12.
SEP '95
20-11
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Menu of ASYNC Monitor Programs
Standard ASYNC
. . . ...-12·_....
==_
Setu~
11_
3
.111••
Standard ASCII Setup to Monitor at 9600 bps
1'", move selection bar
+- move to prev menu
......
move to next menu
? = Help
RETURN select menu entr!:j
HOME
move to top menu
EZ VU exit/enter menus
Figure 20-12 Our new entry, Standard ASYNC Setup (9600), appears at the end of the
Menu of ASYNC Monitor programs.
Now that you have a general idea of how to create a new version of an Easy View
program, let's examine each screen and command in more detail.
(B) Easy View Maintenance Help Menu
The screen shown in Figure 20-13 is the Easy View Maintenance Help menu. It
provides a brief description of each softkey function. Pressing the function key (or
the fIrst letter of the softkey label) either accesses another screen or performs a
command. LOAD, MERGE, and COMPILE are commands.
20-12
SEP'95
20 Easy View Maintenance
The softkeys are ordered according to the sequence of tasks you will perform. To
customize an application program, first identify the script filename on the Filename
Specification screen. Next, load into memory the setups from the program(s)
referenced in the script file via the LOAD command. Then, move to the Program
Specification Editor screen. Once you find the program of interest, make the
appropriate changes to the setups and menu information to create new versions.
MERGE the new information into the master menu script file. As a final step, COMPILE
the master menu information file. Refer again to Figure 20-1.
NOTE: Except for program editing, the automatic installation
performs these same operations using the files named on the Filename
Specification screen.
*
CF)NAM ED - Filename Specification Editor
CL)OAD
- Load Menus/Programs From Source Menu File
(P)ROG ED CM)ERGE
(C)OMPILE
(E)RRORS (H)ELP
Program Specification Editor
Merge Loaded Menus/Programs Into Dest. Menu File
Compile Master Menu From Text To Compiled
Error Displa~ Screen
This Help Screen
Figure 20-13 Help screen for Easy View Maintenance program.
(C) Filename Specification Screen
The source and destination files for each of the commands are identified on the
Filename Specification screen, shown in Figure 20-14. Before you can customize a
program, you need to identify the appropriate files. Press ® or the FNAM ED softkey
to access this screen.
SEP '95
20-13
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Fllena~e
Sceclflcatlon
Source (Load From) Menu File Pathname:
FD1/MENU/install.txt
Destination (Merge To) Menu File Pathname:
HRD/MENU/mstrmenu.txt
Master Menu Text (Compile From) File Pathname:
HRD/MENU/mstrmenu.txt
Master Menu Compiled (Compile To) File Pathname:
HRD/MENU/mstrmenu.cmp
Figur:-e 20·14 Filename Specification Editor screen.
The following editing keys function in the fields on this screen:
Inserts a character at the cursor position.
Deletes the character immediately preceding the cursor position.
Deletes the character at the cursor position.
Deletes the line containing the cursor.
Clears the field containing the cursor.
Clears the field from the cursor position to the end.
~-§)
Moves the cursor to the end of the current field.
8-8
Moves the cursor to the beginning of the current field.
8-8
Moves the cursor forward one character, or to the next field.
8
8
Moves the cursor back one character, or to the previous field.
~ or §3
Moves the cursor to the next field.
8 - 8 0 r 8 - 8 Moves the cursor to the previous field.
[±]
Moves the cursor to the same location in the field below.
ffl
Moves the cursor to the same location in the field above.
For each field on the screen, enter the pathname of a file, beginning with a drive
specifier-HRD, PDI, or PD2. Filenames are case sensitive. Enter the filename
exactly as it appears in the INTERVIEW file maintenance directory. If you do not
include the drive specifier, an error message is displayed. You will not be able to
enter a name that exceeds the maximum length of 126 characters (including the drive
specifier).
20-14
SEP'95
20 Easy View Maintenance
1.
Source (Load From) Menu File Pathname. The file named in this field is
automatically loaded when you elect to customize programs. It is also the object
of the LOAD command.
The default pathname is FDIIMENUlinstall.txt, the name of the script file for
AR -supplied application programs. The automatic installation uses the script
file named in this field as the source for the install.
If you are creating a script file to install your own program, either name your
script file FDIIMENUlinstall.txt (case does make a difference) or change the
entry in this field.
2. Destination (Merge To) Menu File Pathname. When you use the MERGE command,
the Source file named in the field above is merged into the file named here.
The default filename is HRDIMENUlmstrmenu.txt. In most instances, you do not
need to change the entry in this field.
3. Master Menu Text (Compile From) File Pathname. This is the source file for the
COMPILE command. Typically, it is the same me as the Destination file for the
MERGE command. Again, the default filename is HRDIMENUlmstrmenu.txt.
4. Master Menu Compiled (Compile To) File Palhname. The file named in this field
is the destination file for the COMPILE command. The default filename is
HRDIMENU/mstrmenu.cmp. It is the compiled version of all the Easy View
menu information.
(0) Load Command
Now press LOAD to load the setups for all the programs referenced in the Source file
(named in the Filename Specification screen). The setups may be modified on the
Program Specification screen.
A rotating arrow in the lower, right-hand corner of the display indicates that the
load is in progress. Press ~ if you want to abort the LOAD operation.
NOTE: The default Source file on the Filename Specification screen
is automatically loaded when you elect to customize programs. If this
is the file you wish to modify, you may bypass the lOAD command.
SEP '95
20-15
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
(E) Program Specification Screen
The setups of all of the programs referenced in the Source file (named in the
Filename Specification screen) are available for editing in the Program Specification
screen, shown in Figure 20-15. The versions you create on this screen are
incorporated in the Destination file when you execute the MERGE command.
The fields in the top portion of the screen, Item Name, Item DeSCription, and Dest
Pathname identify one of the programs referenced in the loaded script file. The fields
in the bottom portion of the screen display the current setup parameters for the file
specified in the Dest Pathname field.
Use the cursor keys ~ and 11m) to scroll through the program listings. E3-~
moves you to the beginning of the list, 8-~ to the end. Notice that the field
entries on the Program Specification screen change as you scroll through the list of
files.
If you scroll past the end of the program listings, a dummy entry, similar to the one
shown in Figure 20-15, appears. The program count, explained in Subsection 3.
below, increments to include this extra entry. The dummy entry, explained in
Subsection 1. below, is simply a place holder in the program listing.
BL
=
Item Name: ~I~t~e~m~l__~____~~~~~____________________________________
I t em De s cr i pt ion: .-eD~e,:"s~c~r~iw:p:::..t~i.!::o~n.;-l=--___________________
Dest. Pathname: HRD/filenamel
MONITOR
Mode:
Source: LINE
Block
:
Clock Source:
INT/DTE:
NRZI: III
,
E>i1ity parallels the OSI seven-layer model.
This layered structure is specifically designed to handle protocols which conform to the
CCnT Open Systems Interconnection (OSI) model. The OS! model is fully described in
CCITT Recommendation X.200.
This is a seven-layer model (see Figure 24-4) in which each layer performs a different
data communication function. Conceptually, each layer is independent. One layer can be
modified without other layers being affected, as long as the modified layer respects
prescribed communication with the layer immediately above and the layer immediately
below it.
SEP'95
24-5
"
INTERVIEW 8000 Series Basic Operation: 951-80424-01
AppIi-
calion
Control
Program
Access
Method
OSllayer:
7
Application
6
Presentation
5
Session
4
Transport
3
Network
2
Data Link
1
Physical
Figure 24-4 The seven OSI layers.
Suppose that the physical link between two nodes in a network were changed from copper
wire to optic fiber. In an OSI configuration, only the physical layer (and possibly certain
aspects of the data link layer) would be modified. The remainder of the communication
process would stay the same.
The separation of programs into discrete layers generally reduces the complexity of test
conditions and actions. This simplifies programming for the user. The structure allows
you to verify your system-and to debug your own tests-Iayer-by-layer. For example, it
is not necessary at Layer 3 of a protocol to anticipate variations in line-level or
frame-level events. Searches for strings and protocol elements focus only on the portion
of a frame which pertains to Layer 3. The validity of the frame which contains the string
has already been checked.
24-6
SEP '95
24 The Layered Program ModeJ
24.4 Personality Packages
The layered structure of the OSI model allows you to use different protocols at different
layers-again, provided that the rules of OSI interlayer communication are observed.
The INTERVIEW provides layer-specific protocol packages, called personality packages,
which you can load from the Layer Setup screen. While certain layer protocols are more
commonly used together (SDLC at Layer 2 and SNA at upper layers, for instance), it is
possible to mix and match them. You could, with the correct Personality Package, load and
run X.25 protocol at Layer 2 and SNA protocol at higher layers.
Personality packages are not in themselves protocol emulations; rather, they are
high -level interfaces to routines in the given protocol. A package at Layer 2 X.25, for
example, allows users to design their own applications by simple sofikey-entry of a routine
such as:
CONDITIONS: RCV DISC
ACTIONS: SEND SABM
or
CONDITIONS: T1 EXPIRED
ACTIONS: RESEND
Personality packages are selected and loaded from the Layer Setup screen (shown in
Figure 24-5; see Section 8 for a description of this screen). The contents of each
personality package are described in a section dedicated to the package (refer to the Table
of Contents, Sections 36, and following).
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
La~er
La~er
La~er
La~er
La~er
La~er
La~er
Package:
Package:
Package:
Package:
5 Package:
6 Package:
7 Package:
1
2
3
4
tup
**
Selections
To Load The Selected Package'S
Figure 24-5 Personality packages, which provide the protocol elements in INTERVIEW programming,
are loaded from the Layer Setup screen.
SEP'95
24-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
24.5 Primitives
The OSI Layers use limited -range messages caUed primitives to communicate with each
other. Primitives are defined by the OSI model and are not linked to anyone protocol. No
matter what personality package is loaded, these generic primitives are available at each
layer. This gives you the freedom to create or modify a protocol. Primitives available on
the Protocol Spreadsheet are discussed in Section 34.
24.6 Constants
To represent a frequently used test value, you may define a constant once in your program
and reference the constant elsewhere in the program as needed. Replacing the test value
with a new value then becomes easy, since you need only change the constant definition
onetime.
Constants, which may be used to represent any textual string, can be defined at several
levels in the spreadsheet program. The function key labeled CONSTS: is only present when
it is legal to define constants.
Depending on where they are defined, constants vary in scope. You have the option of
creating constants which can be used globally, throughout a layer, or throughout a test.
Refer to Section 29 for a full description of constants.
24-8
SEP '95
25 Trigger Conditions
25 Trigger Conditions
SEP'95
25-1
Trigger Setup (Conditions)
Trigger Number: _
(Enter O-F)
Select Condition
I
II
F1
RECVR
~onltor
II
F2
EIA
F3
II
TIMEOUT
F4
II
ENDXMIT
II
F5
FLAGS
F6
II
BUFFULL
II
F7
COUNTER
Fa
KEY
I
Receiver: NO OTE DCE
I
Monflor Receiver:
T T
NO
OTE
I
L
I
I
DCE
1
Monitor BuRer Full: NO YES
For:
GO BeC BO BCC PAAERA FRMERA ABORT
Monitor Flags: NO YES
Enler Character SIring:
T
Wafl For End Of Frame; NO YES
I
Enter Bit Mask:
Ml;XXXXXXXX M2:XXXXXXXX M3:XXXlOOOO( M4:XXXXXXXX
T
eTS: _
CD: _
Enter Flag Mask: lO()()OO(J(X
Monitor Counter: NO
Monitor EIA leads: NO Y
RTS: _
I
I
Y.!if
0_ _
Enter Counter Name:
OrR: _
DSR: _
AI: _
EQ
NE
GE
LE
GT
LT
UA: _
(Enler 1 For On, 0 For Ot!, X For Donl Care)
I
Monitor Timeout: NO 1 2
(Enler Counter Value)
I
I
MonHor Keyboard: NO YES
I
MonHor Xmit Complete: NO YES
I
I
I
Figure 25·1 Conditions on Trigger Setup menu.
T
Enter Key:
- I
I
25 Trigger Conditions
25 Trigger Conditions
Triggers can be thought of as "IF, mEN" statements, represented on the screen as "Conditions"
(IE .. ) and '~ctions" (THEN... ). This section pertains to Trigger Conditions available on the
preconfigured Trigger Setup screens, of which there are 16 in the INTERVIEW 8000 Series. All
possible conditions available on the Trigger Setup screen are shown in Figure 25-1.
Triggers are numbered 0 through R To access a particular trigger screen, press the TRIGS function
key on the Main Program Menu. This calls up the Trigger Summary screen. Enter the Trigger
Number desired (it will appear highlighted at the top of the screen) to see that trigger screen.
Each trigger screen is divided in half, with Conditions at the top of the screen and Actions at the
bottom of the screen. A default Trigger Setup screen is shown in Figure 25-2.
EIA:
Timeout:
Flags:
Counter:
Xmit Complete:
Buffer Fu 11:
Ke8board:
Prompt:
Xmit:
Flags:
Enhance:
Timeouts:
Counters:
Timers:
Alarm:
Figure 25-2 Default trigger menu.
SEP'95
25-3
)WIIIIi'if£J&
ifli£
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
25.1
Active Triggers
Only active triggers are tested. Trigger Setup screens are continuously active. (This is not
true of triggers on the Protocol Spreadsheet, where triggers are configured in alternately
active states as a matter of program design.)
25.2 Combining Conditions on the Same Trigger Setup Screen
A trigger is true and can take action only at the instant that all trigger conditions are met.
(A) Static vs. Instantaneous Conditions
Internal flag, Counter, ElA lead, and Buffer Full conditions differ from other
conditions on the Trigger Setup screen. When it is used in a trigger by itself, each of
these conditions, like other independent conditions, initiates its trigger actions only
at the instant that it transitions to true. In addition, these four conditions can retain
a status of true for a long period of time.
The static value of these four conditions is tested for true or false when they are
combined in the same trigger with another condition.
All other trigger conditions are true only at the instant that they happen. We will
refer to them as "instantaneous" or "transitional" conditions.
NOTE: It is important to remember that even a "static" condition is
"transitional" when it is used alone in a trigger. An ElA condition,
for example, used by itself in a trigger cannot come true without a
transition.
An exception to this rule is when the test enters Run mode. At that
moment, static conditions-flags, counters, EIA leads, and buffer
full-used alone on a Trigger Setup menu (not on the Protocol
Spreadsheet) are tested once for a status oftrue. Then they revert to
being true only upon transitions.
(8) Rules for Combining Conditions
These "static" conditions can be combined with other trigger conditions on the same
Trigger Setup screen to form compound "IF" statements. Here are some rules to
remember in combining trigger conditions:
1.
When "static" conditions appear on the same trigger menu with an
"instantaneous" condition, the trigger is keyed to the instantaneous condition.
All static conditions must be true when the instantaneous condition transitions to
true. On that transition, trigger actions are taken.
Suppose, for example, that a trigger is looking for a Bad Bee and a counter
value = 20. The counter value must first increment to 20, then the Bad BCe
25-4
SEP '95
25 Trigger Conditions
must be detected. As soon as the Bad BCC is detected, the trigger becomes true
and takes action.
2.
When static conditions are combined, both (or all) are transitional. When one of
them transitions true, the other(s) becomes a static condition and is checked for a
status of true. The user does not have to try to anticipate which of two (or more)
conditions will transition first.
NOTE: On the Protocol Spreadsheet, static conditions are prioritized
in the order that the user lists them: only the first is transitional. The
Protocol Spreadsheet therefore requires you to define which static
condition will be the controlling, transitional condition. See Section
31.2.
25.3 Receiver
This condition monitors the data lead specified (DCE or DTE) for designated data.
When Receiver. gi or _~ is selected, several options become available: String, 10f,
Good BCC, Bad BCe, Parity Error, Frame Error, and Abort.
(A) DTE or OCE
r;.
In using the Receive condition, you must specify which side of the line you wish to
monitor. Select
to denote the TO lead. Select f@r to denote the RD lead.
(B) String
This selection allows you to enter a string of up to 16 characters in the field provided.
The entire, exact sequence of characters entered must be received for the condition
to be true.
(C) "One of"
When
is selected, the trigger looks for anyone of the characters entered
in the next field. Up to 16 individual characters can be entered.
(D) Good or Bad BCe
%{f~IIl~\{ji (Good Block Check Calculation) and
(Bad Block Check
Calculation) cannot be used as conditions unless Rev Blk Chk is on in the unit
(selectable on the Line Setup screen; see Section 5). Select
or ;;iljftli~~;/,
when you want the trigger to take action on receipt of the Block Check Calculation
(referred to as FCS, or Frame Check Sequence in Bit-Oriented Protocols).
25-5
SEP '95
iii
m
il!l__
Y
_*
PC
lllE9l
KiZV
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(E) Parity Error
:;1iI\j~IiJill,;!i looks for a parity error in relation to the Parity selection made on the Line
Setup screen.
(F) Framing Error
liJ!ff.~;1;f~1 applies to start-stop formats (ASYNC and ISOC) and locates framing
errors, based on the stop bits anticipated. Both Format and Stop Bits are selected on
the Line Setup screen.
(G) Abort
This selection applies to all Bit-Oriented Protocols. When
is selected,
the INTERVIEW triggers off of the seven consecutive 1- bits which constitute an
Abort.
should be used as Format on the Line Setup Menu when
is
selected.
NOTE: The trigger condition will not respond to idle-time aborts,
unless Display Abortf'Bl, has been selected on the Line Setup screen.
(H) Character Entry Field
This field appears only if *~~~![Ml.~;:;!: or 8}1;f~1X~&i;:I: is selected. It is the data -entry
line for a sequential character string, if
has been selected; or a
nonsequential character list,
has been selected. Up to 16 characters
may be entered, in either case.
1.
String entry. The 16 characters allowed in the string may include any of the
following in any order or number:
All upper and lower-case ASCII characters available on the keyboard.
All control character mnemonics on the keyboard.
Two-digit hexadecimal entries. These are entered by first turning the §] key
on, then using alphanumeric keys IjJ through @ and 0 through tEl. Two
alphanumeric key strokes are required for each hex character. A hex character is
represented on the screen as a pair of small characters, the first ascending and
the second descending. Compare hex characters to regular alphanumeric
characters in Figure 25-3.
25-6
SEP '95
25 Trigger Conditions
Figure 25·3 Both alphanumeric and hexadecimal characters can be entered as part of a condition
search string.
Characters entered in hexadecimal are not translated, and parity is not calculated
for them; therefore, you must include the parity bit, whether good or bad, in your
entry.
2. Flags. You must press 8
to enter the 7£ Flag byte used in Bit-Oriented
Protocols. The INTERVIEW's logic will not read a hexadecimal entry made with
~ asa flag.
3.
Sync. Press 8-8 to enter the sync symbol. The characterfID is displayed on
the mgger screen.
4. Not equal (¥=-) entry. When a character key is preceded by 1Al, all characters not
equal to that character will satisfy that position in the string. These characters
are represented in the data entry field with a horizontal bar through them.
5. Don't care.
m;v permits any character received in that position to satisfy the
condition.
6. Bit masks. Four bit masks can be positioned anywhere in the data -entry string.
To enter a bit mask, use GIQ at the desired location in the string. Each time you
press ~. a new mask field appears below the string-entry field. To move the
cursor to the next position in the string-entry field, press 8. The mask fields
are numbered Ml through M4, to denote the order in which they appear in the
string (see Figure 25-4).
Figure 2S4 Four bit masks can be used as part of the search string.
If you have used Bit Masks 1 and 2, for example, at positions 5 and 8 of the string
(as in Figure 25-5), you may decide to change the character at position 1 to a bit
mask. Return the cursor to position 1 of the string and press~. The character
SEP'95
25-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
at position 1 will be overwritten with !!:!I, the two prior bit masks will be
renumbered to 2 and 3, and their menu location shifted to make room for the
new Bit Mask 1. The cursor will be on the left - most bit of the new mask.
(Compare Figure 25-5 and Figure 25-6.)
Figure 25-5 Bit masks Ml and M2 are entered at positions 5 and 8 of this string.
Figure 2S-('j A third bit mask has been entered at position 1, and the old Ml and M2 have
shifted automatically to M2 and M3.
NOTE: When a Bit-Oriented Protocol is being tested, the
INTERVIEW ignores inserted zero bits. You can specify the search
string on the Trigger Setup screen without considering zero bit
insertion.
7.
Double parens. A global constant declared on the Protocol Spreadsheet can be
entered as part of a Receiver String. Enter the name of the constant exactly as it
appears on the spreadsheet and enclose it in double parentheses, as follows:
((drop)). The double parentheses are special characters created by pressing
~-(§) for «( , and ~-I!l for)). When constants are used, the receive string
cannot be longer than 32 characters after all constants are expanded.
(I) "1 OF" Character Entry
Up to 16 characters may be entered. The same types of characters valid in String
entry are valid 1 OF characters. The trigger will take action upon receipt of the first
character that matches anyone of the characters anywhere in the list. If ~ is used,
only this character should appear in the 1 OF entry field (since any character is a match
for Don't Care). If one or more characters in the field are entered as ~. only those
characters not in the field will satisfy the condition. Thus,1I"'C! z in the 1 OF field
means the same thing as~: all characters other than p, q, and z will satisfy the
condition.
25-8
SEP'95
25 Trigger Conditions
(J) Wait For End of Frame
This is a subfield which appears when
or
is selected. The
default selection is ~.. When Walt For EOF: t.1~ is selected, the trigger first tests for
the data specified on the trigger. Then it evaluates the block check at the end of the
frame. The trigger will not take action when a Bad Block Check or an Abort is
detected on a received frame.
25.4 EIA
Select if81 in the EtA field if you want a trigger to monitor status of up to seven
RS - 232N.24 leads (see Figure 25-7).
NOTE: For line data, EIA lead -status is not detected if control
leads are not buffered in the Front-End Buffer. See Section 9. For
recorded data, EIA lead -status is not detected if control leads were
not buffered in the FEB at the time of recording.
Figure 25-7 Each trigger can monitor the status of seven EIA leads.
Enter a 1 in the box under a lead to indicate ON; a 0 for OFF. No entry (X) is read as
Don't Care. Entry fields are provided for six leads: RTS (Pin 4), crs (Pin 5), DSR (Pin
6), DTR (Pin 20), CD (Pin 8), and RI (Pin 22). You may monitor a seventh RS- 232N.24
lead by strapping the desired lead to UA on the Test Interface Module (see Section 12 for
instructions).
In using the EtA condition, you should keep the following points in mind.
•
If only EIA conditions are selected, the trigger will wait for all EIA conditions to be
satisfied. It will become true on the last transition necessary to satisfy these
conditions.
•
The EtA condition is a static condition. The rules for combining static conditions with
other conditions are explained in Section 25.2.
25.5 Timeout
Two timeout timers can be monitored from the Trigger Setup screen.
The decrementing timeout timer is set for a specific time as part of a trigger action. The
trigger which sets a monitored timeout may be any of the Trigger Setup screens or any
trigger on the Protocol Spreadsheet.
The default Timeout selection is
. Select
to monitor Timeout timer 1;
monitor Timeout timer 2. The condition is satisfied at the instant of the timeout.
to
SEP'95
25-9
~
.._._..................._-_..._
. _._.._
..............."
~~~~~~~~~~-~~~~~----------.-.------------~-.-.-
INTERVIEW 8000 Series Basic Operation: 951-80424-01
25.6 Transmission Complete
When Xmit Complete: 1m;, is selected, the INTERVIEW tests for the end of its own
transmissions.
NOTE: The INTERVIEW transmits only when operating in Emulate
DTE or DeE mode (selectable on the Line Setup screen; see Section
5).
The Xmit Complete condition is frequently used with an internal flag or counter condition to
control when or how many times it will be tested.
25.7 Internal Flag Bits
There are eight internal flag bits reserved for the INTERVIEW's Trigger Setup screens.
The purpose of the flag bits is to provide a simple way to interconnect several triggers in
order to make one trigger dependent on another or to set up triggers in sequence. Each
bit is a simple switch that one trigger may set as an action and all triggers can test later.
Internal flags may all be monitored and set by any individual trigger. (The same flag bit
can be set and sensed by a single trigger.) Since each flag bit can be set and monitored
separately, it can also be shared among the Trigger Setup screens.
The internal flag condition is a static condition and can be used in combination with other
trigger conditions as explained in Section 25.2.
To test internal flags, select Flags:
. In the flag mask which then appears, enter a 1 to
test for a flag bit turned ON, a 0 to test for a flag bit turned OFF. Enter X in the
appropriate position of the mask (or press ~) if you do not wish to test a particular bit.
See the example in Figure 25-8.
Figure 2S-SThe internal tlagcondition is frequently used in combination with other triggerconditions.
NOTES:
25-10
SEP'95
25 Trigger Conditions
All flags are set to 0 as the IN1ERVIEW enters Run mode.
The eight flag bits on the Trigger Setup screens are the low-order
bits of a flag mask that can be accessed on the Protocol Spreadsheet
by the name trifLflag. See Section 31.3(G).
25.8 Buffer Full
This condition checks the screen's 64 Kbyte character buffer and becomes true as soon as
the buffer is full. The condition then remains true throughout the program. Buffer Full is
a static condition which may be used in conjunction with other conditions. The rules for
combining trigger conditions are outlined in Section 25.2.
25.9 Counter
Each Trigger Setup screen can monitor a counter with a range of 0 to 999,999. The
counter which is monitored may be named and controlled either on a Trigger Setup screen
or on the Protocol Spreadsheet.
The default selection is Bit.. When Counter:i.k is selected, new menu fields appear (see
Figure 25-9).
Figure 25-9 Any counter named on a trigger can be monitored as a Trigger Setup screen condition.
(A) Counter Name
Enter the counter name in the field provided. Names must start with a letter. Any of
the 52 alpha characters (upper and lower) and the 10 numerals in addition to the
underscore ( _ ) character are legal in aU other positions. A counter name may be up
to eight characters in length.
(8) Relational Operator
Make the appropriate selection to specify when the Counter condition will be true.
The counter may be tested for a value equal to (m), not equal to (~), greater than
or equal to (~), less than or equal to (B), strictly greater than (~), or strictly less
than (i~) the entered value on the trigger screen.
SEP '95
25-11
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(C) Counter Value
Enter the counter value as a whole decimal number in the field provided.
25.10 Keyboard
Select Keyboard: t~i to display a one character entry field. Then press the key which you
wish to use as the condition. In Run mode when that key is pressed, the condition will be
true and (if this is the only condition) will initiate a trigger action, such as a transmission.
Any key or key-combination that produces a character listed in the ASCII chart in
Appendix D1 is valid input in this field.
25-12
SEP '95
26 Trigger Actions
26 Trigger Actions
SEP '95
26-1
Trigger Setup (Actions)
Trigger Number: __ (Enter O-F)
Select Action:
Select Action:
I
II
F1
II
F2
PROMPT
XMIT
II
F3
FLAGS
F4
II
ENHANCE
II
F5
TIMEOUT
II
COUNTER
=r
Entm Prompt: _ _ _
I
II
F7
TIMER
I
Display Prompt NO YES .
I
F6
I
Fa
I
!'"
MORE
L-
I
I
I
Control Flags:
II
F1
ALARM
Sound Alarm: NO YES
I
F2
CAPTURE
I
NO ;rINCDEC
Xmft:NO Y~
Enter Flag Value:
I
Enler Xmlt String:
BCC: GOOD BAD
---
NONE ABORT
I
Control CaptUfe: NO BOTH OTE DCE
XXXXXXXX
I
I
Select Capture ActiOn:
ON OFF
Enhanoo Oisplay: NO BOTH OTE DCE
I
I
Rev: _
Sink: _
Low:
_
Hax: _
(Enler 1 For On, 0 For Olf, X For Don't Care)
I
Control Timers?
1st: _
NOY¥NO RESTART STOP CaNT SAMPLE CLEAR
(Enler Timer Name)
Control Tlmeouts: NO yFJt#1: NO RESTART STOP
:r=
I-
Seconds
2nd: _
...,-
#2: NO RESTART STOP
(Enler Timeout Value)
NO RESTART STOP CONT SAMPLE CLEAR
(Enter Timer Name)
I
Conlrol CO\Jnlers: NO YE+
lsI:
2nd:
NO INC DEC ST-SAMPLE CLEAR
(Enter Counler Name)
r_
(Enter Counter Value)
1
Figure 26·1 Actions on nigger Setup menu,
NO INC OEC S1-SAMPLE CLEAR
(Enler Counter Name)
1_
(Enter Counter Value)
I
I
26 Trigger Actions
26 Trigger Actions
Figure 26-1 shows all actions available on the Trigger Setup screen. Figure 26-2 shows a default
trigger menu. The top half of the menu contains available trigger conditions. discussed in Section
25. A more complete set of trigger conditions and actions is available on the Protocol Spreadsheet
(see Sections 31 and 32, as well as individual sections on the Protocol Packages).
All conditions selected on the top half of the Trigger Setup menu must be satisfied for the trigger to
be true. Only then will the actions on the lower half of the menu be taken.
*
EIA:
Timeout:
Flags:
Counter:
Xmit Complete:
Buffer Fu 11 :
Ke!:;;board:
--,--------------------------------------------------
Prompt:
Xmit:
Flags:
Enhance:
Timeouts:
Counters:
Timers:
Alarm:
ons
w
•
Figure 26-2 Default trigger menu.
26.1 Displaying a Prompt
Select Prompt _~ to display a data entry field (see Figure 26-3). You may enter a
message of up to 47 characters here. Any ASCII characters are legal entries. When the
trigger is true, the Prompt will be displayed on line 2 of the screen. (The prompt is NOT
transmitted.) It will stay on the screen until it is replaced by another prompt, or until you
clear it by changing the display mode or by pressing the 8 key.
SEP '95
26-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTE: A new prompt does not reinitialize the prompt line on the
screen. Instead, it oveIWrites the old prompt to the extent of the new
one. If the prompt "LINK - UP" is oveIWritten by the prompt
"CALL," the result will be "CALL-up'''
FIgUre 26-3 Messages entered in the Prompt field will appear on the second line of the screen in Run
mode.
Prompts can be used to call your attention to certain occurrences, or to help you follow the
course of a test. Prompts are also useful in program development because you can use a
prompt to tell you when a trigger is true. Any alphanumeric or control character from the
keyboard, including spaces, may be part of a prompt.
26.2 Transmitting
INTERVIEW transmissions-with the exception of BERT transmissions, described in
Section l1-are continuously under trigger control, either from the 'Digger Setup screen
or from the Protocol Spreadsheet. (You may, however, control trigger operation manually
by selecting Keyboard trigger conditions; see Section 25.)
Select
to display a data entry field and a rotating window for Bee (see Figure 26-4).
When the trigger is true, the INTERVIEW will transmit any message you enter here (up to
37 characters), ending with the block-check selection you make in the Bee field. ASCII
characters, hexadecimal entries, and control characters are valid in this field.
Any global constant declared on the Protocol Spreadsheet may be referenced as part of
the XmH string on a Trigger Setup screen. Enter the name exactly as it was declared on the
Protocol Spreadsheet, and enclose it in double parentheses-for example, ((drop)). The
double parentheses are special characters created by pressing ~-@ for (C, and ~-@ for
)).
Since the standard fox message, containing the set of upper-case alpha characters and the
ten numerals, is predefined, you may reference it as a constant on a Trigger Setup screen.
It need not be declared on the Protocol Spreadsheet. Enter it as follows: ((FOx)).
26-4
SEP '95
26 Trigger Actions
Figure 264 Transmitted messages may be terminated with good or bad BCC's or an Abort.
(A)
Bee
You have the option of following each text block transmitted from the Trigger Setup
screen with a block-check calculation. Block checks are calculated according to your
selections on the BCC Setup screen (see Section 10).
On the INTERVIEW screen, the final byte of the calculation appears as a highlighted
overlay (@l,IlI, orll), as long as you have selected Rev BUt Chk: !~.~ on the Line Setup
screen (see Section 5). This selection is only available for synchronous and
asynchronous formats. When Rev Blk Chk is tBZ: for these two formats, block-check
characters appear as they are actually transmitted.
The block-check symbol will be displayed for Bit-Oriented Protocols.
In the rotating acc window, you may select ~§£~.~i!!:, ~~1~;, ~~~.~l'~, or ~jt~~.
The default selection is ;fi@~t~;.
1.
Good Block Check. Select ~t~Jij to terminate your text blocks with a correct
block check. (Remember that not all transmissions are text blocks: a bisync poll
will not receive a block check even if lii~iatii or
is selected.)
2. Bad Block Check. Select ~;I~_jm to end your transmission with an erroneous
block check. For Bit-Oriented Protocols, the bad BCC is CRC-16 instead of
CCITf; for other formats, the bad BCC is an inverted good BCC.
3. None. When ~i%Ml~t. is selected, no block check is sent at the end of the
transmission. (For BOP transmissions, f;~~!:111 has the same effect as jg~ili .)
You may cause messages to be sent in succession by different triggers, with no
intervening block checks if you wish; however, at least one full character of idle
(or7E flag, in the case of Bit-Oriented Protocols) will be transmitted between
blocks. When leads are switched (as indicated on the Interface Setup screen; see
Section 12), the interface leads will be controlled between blocks.
4.
Abort. This selection causes the message to which it is appended to abort before
completion. When selected with Bit-Oriented Protocols, this action causes the
INTERVIEW to transmit seven consecutive 1's at the end of the message. (For
non - BOP transmissions, selecting
has the same effect as selecting
\;t.~t;J.)
SEP'95
26-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
26.3 Internal Flags
Internal flags are bits that can be set on or off and sensed by triggers. Eight internal flag
bits are shared among the Trigger Setup screens. Any combination of flag bits can be
controlled by any trigger or combination of triggers.
NOTE: The flag bits on the Trigger Setup can be controlled and
monitored on the Protocol Spreadsheet, where they are referred to as
triSLftag (see Section 31).
By default the Flags option is
window: 1.1Im, It.~, and rt~1.
. Three other selections are available in the rotating
(A) Set
When you select ~Ijjt, a flag mask appears (see Figure 26-5). Use the arrow keys (8
and 8) to move the cursor to the bits you wish to set.
Enter a 1 or a 0 in any position you wish to set. Enter an X for "Don't Care." The
trigger will not change the existing value of this bit.
Figure 26-5 A set of eight flag bits may be set on any of the trigger menus.
(8) Increment
The internal flags, consisting of Flags 0 through 7, can be thought of as a binary
number. This action increases the value of the flags by one each time the trigger is
true. (Other trigger actions may change the value of the flag bits in the intervening
period.) Incrementing flags is one technique for controlling recursive routines.
As the flag bits increment past 255, they roll over to zero.
(C) Decrement
This action decreases the value of the flag byte by one each time that the trigger is
true. In the event that the flag decrements below zero, the value of the byte wraps to
255.
NOTE: The value of the flag bits is continuously reset to zero when
you enter Run mode.
26-6
SEP '95
26 Trigger Actions
26.4 Enhancing the Display
Triggers can be used to enhance dispJay data selectively. Data on either or both sides of
the line can be enhanced. Enhanced data is also stored in the character buffer with the
enhancements for later review.
(A) BOTH, DTE, or DeE
_£i
Select Enhance: iBt~,
or
to enable enhancement options (see
Figure 26-6). ~_,(j indicates that enhancements will be turned on or off on both TD
and RD data at the same time.
filiB'i!pinpoints TD data for enhancement; ~~ specifies RD data for
enhancement.
Figure U-6 Data may be enhanced with respect to DTE, DeE, or both.
Four options, Rev, Blnk, Low, and Hex, appear to the right. To turn on an
enhancement, enter a 1 on the line immediately following it. To tum off an
enhancement, enter a 0 on the same line. When an X follows the enhancement, the
trigger takes no action.
1.
Reverse image. Reverse-imaged (Rev) characters are presented as dark letters on
a lighter background.
2.
Blink. Blnk causes data to blink on and off rapidly. This is the most conspicuous
highlight for small portions of data.
3. Low intensity. Low has no effect on the plasma display. However, if you have
installed a black and white monitor, it provides a low-intensity highlight for
selected data.
4.
Hexadecimal. When Hex is turned on, all data affected by the trigger is displayed
in hexadecimal. Once data is stored in the buffer as hexadecimal, it remains in
hexadecimal form.
(8) Col9r Enhancement
Color enhancement is controlled by the settings of three trigger enhancements:
Reverse, Blink and Low. The three combined settings are mapped to color
enhancements on the Miscellaneous Utilities screen as described in Section 18.
SEP '95
26-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
26.5 Controlling Timeouts
Each Trigger Setup screen can restart or stop either or both of the two timeout timers.
These timers decrement from a value set on any of the triggers and, like flags and
counters, serve as useful trigger conditions for internal program control.
When Timeout:
is selected, identical new fields appear for Timeout #1 and
Timeout #2. Both fields may be filled in on the same trigger.
(A) RESTART
Select ~~t~ to start or reset the timeout timer. The amount of time remaining on
the timeout timer is entered in the data entry field provided (see Figure 26-7).
Yagure 26-7 Timeout #1 activated to expire in three seconds.
1.
Entering timeout values. The duration of the timeout is entered in seconds in the
5-character data-entry field provided. To enter a timeout value that is less than
one second, use a leading zero before the decimal point, as follows: 0.25. The
smallest valid timeout is 1 millisecond (0.001). The largest valid timeout is 65.535
seconds.
Create a ten-minute timeout as follows: Start a timeout with a value of 60
seconds. When it expires, restart a similar timeout and increment a counter.
When the counter equals ten, ten minutes will have elapsed.
(8) STOP
Select
to halt and clear the timeout timer, without causing the timeout to
occur. If Timeout is selected as a trigger condition, the condition will not become true
in this instance.
NOTE: Timeouts created on a Trigger Setup screen can be
monitored and controlled from the Protocol Spreadsheet. These
timeouts are entered as tri9..timeout_1 and tri9_timeout_2 when referred
to on the Protocol Spreadsheet.
26.6 Counters
Each Trigger Setup screen can control two counters. These counters can be unique to the
trigger (controlled only by it), or they may be shared with other triggers, which can
monitor them and change their values. As long as the same counter name is used, the
same counter is invoked.
26-8
SEP '95
26 Trigger Actions
NOTE: Counter names used on the Protocol Spreadsheet also refer
to these counters, if the names match any counter name on the
'lligger Setup screens. This means that program control can be
shared between these screens and the spreadsheet.
NOTE: Trigger Setup screens monitor counter values from 0 to
999,999. However,Protocol Spreadsheet triggers can monitor
counter values up to 4,294,967,295.
(A) Menu Fields
When counters:
is selected, two sets of new menu fields, labeled 1st and 2nd,
appear (see Figure 26-8).
1.
Counter name. Enter the counter name in the field provided. The name may be
up to eight characters long and must start with a letter. Upper- and lower-case
alpha characters, numerals, and underscore ( _ ) are legal in the other positions.
When the name field is empty, the trigger takes no action for that counter field.
Figure 26-8 One counter is incremented, another decremented in this action.
2. No. The default selection is
counters.
3. Increment. When
SEP '95
. It allows you to disregard one or both
*rM is selected, each trigger occurrence adds 1 to the counter.
4.
Decrement. When_i is selected, each trigger occurrence subtracts 1 from the
counter. When a counter decrements below zero, it wraps not to 9,999,999, but
to the decimal equivalent of 232 - 1, the actual maximum value of a 32-bit
counter. The seven least-significant decimal digits that appear on the Tabular
Statistics screen are 4967295. The complete number is over 4 billion.
5.
Set. Select
in order to specify the value which the counter will take when
the trigger becomes true. Then, enter the decimal value of the counter in the
field provided. The field is six positions long, making it possible to set counters
to a value from 0 to 999999. Any leading positions not specified in your entry will
26-9
INTERVIEW 8000 Series Basic Operation: 951-80424-01
be set to zero. This action does not cause statistical samples to be taken, nor
does it reset last value, minimum value, maximum value, or average value for the
counter. (Compare to Sample and Clear.)
6.
Sample. This action causes the counter to reset to zero and causes measurements
to be taken for last value, minimum value, maximum value, and average value.
Refer to Section 21 for an explanation of how statistics are gathered and
tabulated.
7.
Clear. This action resets the counter to zero and also resets minimum value,
maximum value, and average value for the counter.
26.7 Timers
Tho timers are shared among the Trigger Setup screens. While these timers are not
available as trigger conditions, they can be run and sampled as trigger actions. When
timers are invoked by triggers, their values can be tracked on the statistics screens (see
Sections 21 and 22).
NOTE: Timer names referred to on the Protocol Spreadsheet may
also be used on Trigger Setup screens. Thus, timer control of
programs is shared between these screens and the spreadsheet.
(A) Menu Fields
The default timer selection is
When
is selected, two identical
subfields appear, for Timer 1 and Timer 2 (see Figure 26-9).
Figure 26-9 One or two timers may be controlled by the same trigger (second field not shown).
1. No. The default selection for each Timer is also t{!if:i1ibti!
This allows trigger
action to disregard both timers or to focus on one timer, if necessary.
2. Restart. When selected, ~i;_~l'jJ£ causes the timer to reset to zero and begin
incrementing. il.r~1Ii.,~" does not cause statistical measurements to be taken.
(Compare to;gJJ;~}ji~ and !;:m~p_;¥f~ii.)
26-10
SEP '95
26 Trigger Actions
3.
Stop. The ~l¥.ii_@!ill1 action suspends the timer and allows it to retain its value.
The timer may be started again at this value by a [~~i action on another
trigger.
4.
Continue. I~, when selected, causes the specified timer to increment,
starting from the value at which it was stopped.
5.
Sample. The~J~~!~ action resets and stops the timer. Prior to resetting the
timer, its value is read as a "last" value and passed along for other statistical
measurements. Refer to Section 21 for an explanation of how statistics are
gathered and tabulated.
6.
Clear. The ;ffl%:Mi'lI; action resets the current value, the last value, the minimum
value, the maximum value, and the average value of the timer. Refer to Section
21 for an explanation of statistical measurements.
26.8 Alarm
The alarm is a short beep. The alarm is useful for calling your attention to the data being
analyzed, especially when the situation of interest occurs infrequently. When you select
Alarm: tw1\, it is sounded each time the trigger becomes true.
26.9 Capture of Data in the Screen Buffer
Capture of character-oriented data to the screen buffer can be stopped and restarted by
triggers, using the Capture action (see Figure 26-10). When capture is turned off, data is
neither presented to the screen nor stored in the buffer.
FtgUre 26-10 Data capture to the screen buffer can be controlled by triggers.
(A) NO, BOTH, DTE, or DeE
The default capture selection is
. This represents no change; that is, the
trigger does not influence character buffer capture. By default, data is continuously
captured in the character buffer.
Select
to control capture to the character buffer for TD and RD data at the
to control only TD data;
to control only RD
same time. Select
data.
SEP'95
26-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
1.
26-12
OFF; ON. Select
to suppress data from the screen buffer. Select .
li:;ll~If;\iJ~?; when another trigger has turned off capture and you wish to begin
storing data in the buffer again.
SEP '95
27 The Trigger Summarv Screen
27 The Trigger Summary Screen
SEP'95
27-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
#0
#1
#2
#3
#4
#5
#6
#7
#8
** Trigger
Trigger Summar!:! **
Number: ~
:#9
#A
:#B
:#c
*D
*E
#F
Enter Tri 9 &r Number (0 F):
3
0
_
•
I
Figure 27·1 Default Trigger Summary screen.
27-2
SEP '95
27 The Trigger Summary Screen
27 The Trigger Summary Screen
The Trigger Summary screen is the access screen to all nigger Setup screens. The default Trigger
Summary screen is shown in Figure 27-1. Call up the Trigger Summary screen by pressing the
function key marked TRIGS on the main Program Menu. With the summary displayed, access any
trigger by typing the number of the desired screen (0 through F). To see a synopsis of configured
Trigger Setups, you may return to the summary screen from any trigger menu by pressing
rnm.
Entries you make on any of the 16 nigger Setup screens appear on the summary in abbreviated
form. Each setup screen is allotted a one-line summary. A summary of conditions appears on the
left - hand side of the line; a summary of actions appears on the right - hand side of the line. The
summary for Trigger Setup screen 0 (Figure 27-2) is shown in Figure 27-3.
Abbreviations for possible Trigger Setup conditions are listed in Table 27-1. Abbreviations for
Trigger Setup actions are given in Table 27-2.
ce
Ml:~~~~
E1A:
Timeout:
Flags:
Counter:
•
Xmit Complete:
Buffer Fu 11 :
Ke!:;board:
.=0_ _
Prompt:
Xmit:
Flags:
Enhance:
Timeouts:
Counters:
Timers:
Alarm:
n
Figure 27-2 Entries on each Trigger Setup screen are indicated on the Trigger SummaIy.
SEP '95
27-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTES:
Abbreviations displayed on the Trigger Summary screen are not
necessarily keywords and should not be referred to when you are
typing entries on the Protocol Spreadsheet.
When multiple conditions or actions are selected on a single Trigger
Setup screen, the summary screen may not be able to show all
selections; however, as many conditions and actions as possible will be
displayed in the available space.
Figure 27·3 Summary of entries made on Trigger Setup screen 0, shown in previous figure.
Table 27-1
Abbreviations, Trigger Summary Conditions
Receiver
~ord
does not appear on summary.)
DTE, DCE
STR: String, 10F: One of (Character string also appears for STR and 10F.),
@ ; Good BCe, @: Bad Bee, PrErr: Parity Error, FrErr: Frame Error,
II: Abort, [BJ: Bit Mask
EIA:
RTS, CTS, CD, DTR, DSR, RI, UA
TimeOut 1, 2
Xmit_Cmpl: Transmission Complete
Flag: (Value only appears.)
Counter: (Name and value only appear.)
KeyBd: Keyboard (Key indicated.)
27-4
SEP'95
27 The Trigger Summary Screen
Table 27·2
Abbreviations. Trigger Summary Actions
Pmpt Prompt (Prompt string also appears.)
Xmit Transmit (Xmit string also appears.)
@l: Good Bce. @: Bad Bce•• : Abort
(Nothing appears if no acc is selected.)
Flag: INC: Increment, DEC: Decrement (Value only appears if selection is SET.)
ENH: Enhance Display
8TH: Both DTE and DCE, DTE, DeE
REV=: Reverse, BLN=: Blink, LOW=: Low, HEX=: Hexadecimal
TO #1, TO #2: Timeout #1 or 2
RST: Restart, STP: Stop
Counter: (Only name and value appear.)
INC: Increment, DEC: Decrement, =: Set
SMP: Sample, CLR: Clear
TM: Timer (Name also appears.)
RST: Restart, STP: Stop, CNT: Continue, SMP: Sample. CLR: Clear
Alarm: Audible Alarm
Capture: Capture Memory
8TH: Both DTE and DCE, DTE, DCE
ON, OFF
SEP'95
27-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
27-6
SEP '95
28 Programming Blocks
28 Programming Blocks
SEP '95
28-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
1.
These keys are at highest level;
2.
+
Press STATE: enter name and presS
or the spacebar to obtain:
3.
Press CONDS; (Conditions) to obtain variable set of Conditions. * Press(§} to access
alternate racks of Conditions keys. Complete entries, then press
to obtain:
8
4.
+
Press ACTION: to obtain variable set of Actions.* Press(§} to access
alternate racks of Actions keys. Complete entries, then press ~ to obtain:
5.
"
Press NEXTST:, enter name of next state, and pres8 or the spacebar to obtain rack 3.
(Pressing CONDS: obtains variable sets of conditions.)
"Conditions and Actions available depend on what protocols are loaded and what layer
number you have specified. The following selections are always available:
GENERAL CONDITIONS
GENERAL ACTIONS
ENTER STATE
TIMEOUT
KEYBOARD
BUFFER FULL
COUNTER
FLAG
ACCUMULATE
SIGNAL
COUNTER
TIMER
TIMEOUT
TIME
FLAG
ON_SIGNAL
LOAD_PROGRAM
PROMPT
PRINT
TRACE
ALARM
RECORD
Figure 28-1 Function key hierarchy, Protocol Spreadsheet.
28-2
SEP '95
28 Programming Blocks
28 Programming Blocks
The Protocol Spreadsheet is a highly flexible progrannning approach which enhances trigger
conditions and actions provided on the 'nigger Setup menus, furnishes new general options, and
incorporates protocol-specific conditions and actions on a layer-by-layer basis.
28.1
Before You Begin a Spread$heet Program
Be certain prior to programming that you have loaded the Personality Packages for the
protocols you will be testing. Automatic protocol options are part of each layer's
Personality Package. These packages are loaded from the Layer Setup screen as described
in Section 8.
Check the configuration of the various Test Setup screens before you test or save your
program, since the behavior of the INTERVIEW during testing is influenced by setup
selections.
28.2 Creating a Spreadsheet Program
Press §) to access the Protocol Spreadsheet from the Program Menu. Any program which
you have loaded from the File Maintenance screen appears on the spreadsheet. If no
program hliS been loaded or created, the Protocol Spreadsheet, since it is a free-form
menu, will be blank except for a header line, function key labels, and tildes ( - ) down the
left side of the screen. Tildes always mark the end of your program file.
(A) Two Sets of Function Keys: Programming and Editing
Two full sets of softkeys are active with the spreadsheet. One set of softkeys groups
available programming options, including keywords (LAYER:, TEST:, CONomONS: etc.).
The alternate set groups sophisticated editing functions.
These editing functions, which complement the editing keypad, are accessible from
the spreadsheet at any time. Press S to activate edit softkeys. Press ~ again to
return to program softkeys. For a discussion of editing options, refer to Section 30.
(8) Programming Functions
Use the programming softkeys to make program entries, from the highest level of the
program (OBJECT), down to individual trigger conditions and actions and their
subfields. Softkeys guide you as you create your program by listing available options
SEP '95
28-3
- ---------------------- ----..- - - - - .- - -______._.,,__._._w_._..___._............". . . . . . . .__
INTERVIEW 8000 Series Basic Operation: 951-80424-01
and providing correct syntax wherever possible. (Errors are indicated by strikeover of
incorrect text as you make your program entries.) For each level of function keys, a
cue near the bottom of the screen explains selectable options or prompts you for
keyboard entry.
Program softkeys are immediately available when you enter the spreadsheet. The
hierarchy of the program softkeys is shown in Figure 28-1. The conditions and
actions listed, which are always available, are explained in Section 31. Other trigger
conditions and actions are added when protocol packages are loaded. Because
protocols are layer-specific, trigger options will vary from layer to layer. For each
LAYER block within your program, different options are likely to appear when you
enter the keyword CONDITIONS or ACTIONS. For more information on the specific
trigger options enabled by a protocol, consult the section devoted to that protocol
(see Table of Contents, Section 36 and following.)
You also have the freedom of typing in any program entry, if you prefer, as long as
you enter the block identifiers and conditions and actions keywords as they would be
posted on the screen by softkeys. Syntax errors still are automatically highlighted by a
strike-through.
NOTE: Softkey labels are not necessarily legal spellings on the
spreadsheet. Pressing the function key usually posts an expanded
keyword on the screen. Use these expanded keywords when typing
entries.
1.
Successive racks of softkeys. The rack of softkey options at the bottom of the
spreadsheet screen (or the instructional prompt on the third line up from the
bottom, or both the option rack and the prompt) will change automatically each
time you complete a keyword entry. Keyword entries are complete when you
make them via softkey or when you type the keyword followed by a space or a
hard 8. (Pressing the softkey has the same effect as typing the keyword and
then typing a space to complete the entry.)
Programming movement is generally down the tree of softkey racks, as in this
series of keywords:
CONDITIONS: ErA CTS ON
Each ofthe four keywords was selected from a rack of options, and each
succeeding rack is a step farther down the "branch." The rack that follows ON,
however-listing RTS, CTS, CO, and other EIA leads-is back up the tree, since
"there is nowhere to go but up," and since a trigger with multiple EIA conditions
(like the following) is valid.
CONDITIONS: EIA CTS ON CD OFF
SEP '95
28-4
-~----~--
--
--
28 Programming Blocks
2. Additional racks of valid softkeys. There may be many more keywords that are
valid to enter at a given point in the program than are showing on one rack of
sofikeys. Additional racks may be accessible via the @ sofdey (MORE); and
higher racks are generally available via the 8 key. In this series, 8 was pressed
following the sofikey for ON to access the softkey for COUNTER:
CONDmONS: EIA ers ON
COUNTER xmit LT IS
In the next series of keywords, (3 was pressed twice following the softkey for ON,
to access the softkey for ACTIONS:
COMrnnONS: eACTSON
ACTIONS: SEND" «FOX)) " GOOD_BCC
Note that 8 is not a valid keystroke following CTS above, since the condition
syntax is not "done." Whenever it is not valid to move to a rack of softkeys
higher up the tree, 8 produces an alann tone.
Note also that it is never necessary to press 8 if you are typing in your keywords
directly from the keyboard. 8 merely changes the rack that is showing, not the
entire set of keywords that is valid. A keyword does not have to be showing to be
typed in legally.
3.
Insert mode versus overstrike mode. Touch-typists in particular should be aware
that the Protocol Spreadsheet has an insert mode as well as an overstrike mode.
The insert mode is invoked byeithcr of two keys, •
or~. When the mode is
enabled, the word appears at the top left of the screen. In insert mode,
the programmer types in a block of data while succeeding text is pushed forward
with every keystroke.
Press fill (but not ~) a second time to exit insert mode and return to overstrike
mode.
The remainder of this section is devoted to the fundamentals of program structure
and to programming components available on the Protocol Spreadsheet which are
independent of trigger options.
SEP'95
28-5
------------------------.- - - -
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 28·2 Discrete states inhabit separate tests at separate layers.
28.3 Program Structure
The components of the INTERVIEW's programming model, introduced in Section 24, are
integrated into a spreadsheet program as discrete blocks according to specific structural
rules. Compare the abstract program model in Figure 28-2 to the spreadsheet program
outlined in Figure 28-3.
(A) Block Identifiers
The INTERVIEW's compiler must respect the distinction between one layer and the
next and between one test and the next. Further, it must group triggers into
designated states and track the transition from one active state to another. To
indicate the boundaries of these various blocks, specific keywords are used. Each
block normally begins with an identifier in upper-case letters, (optionally) followed
by a colon. A block ends when a new block identifier is inserted in the program.
NOTE: The identifier must not be enclosed in quotes (that is, must
not be part of a text string) if it is intended as a block delimiter.
Available program blocks, from largest to smallest, are described in subsequent
paragraphs. The valid block identifier for each is printed above its description.
28-6
SEP '95
28 Programming Blocks
OBJECT:
(OBJECT identifer(s), if included, must precede all other identifiers,
except IL_BUFFEAS)
IL.BUF"F'ERS:
CONSTANTS:
(IL BUFFERS identifier, If included, must precede aU other
idinti1lers, except OBJECT)
(global constants are defined here; they can be
accessed throughout the test)
LAYER:!
CONSTANTS:
(Layer 1 constants defined here apply to
this and following layers)
TEST:
CONSTANTS: (test constants are defined here;
they apply to all states within the test)
STATE:
CONDITIONS:
T
first
trigger
Program
ACTIONS:
-1
CONDITIONS:
i
State Block
Test Block
Layer
Block
second
trigger
ACTIONS:
l
STATE:
CONDITIONS:
NEXT_STATE:
TEST:
CONSTANTS:
(constants for this test are defined here)
STATE:
CONDITIONS:
ACTIONS:
NEXT.J5TATE:
LAYER: 2
CONSTANTS:
(Layer 2 constants defined here apply to
thIS and following layers)
Figure 28-3 Program Structure. Component blocks begin with a keyword.
SEP '95
28-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
OBJECT:
1. Referencing linkable-object files. Use the OBJECT block - identifier to access the
compiled code in a linkable-object file. See Section 28.4 below. The OBJECT
identifier(s) must appear at the top of the Protocol Spreadsheet.
IL_BUFFERS is the only identifier which may precede OBJECT. C regions or
spreadsheet comments may also precede the OBJECT block identifier.
IL_BUFFERS
2.
Configuring the number/size ofIL buffers. Interlayer (IL) message buffers are used
to pass data up the layers as it is received and down the layers as it is transmitted.
Press the IL BUFS softkey to set the number and size of the lL buffers. The
IL_BUFFERS identifier(s) must appear at the top of the Protocol Spreadsheet.
OBJECT is the only identifier which may precede IL BUFS. C regions or spreadsheet
comments may also precede the IL_BUFFERS block identifier.
CONSTANTS:
3.
Defining constants. There are three legal locations for the definition of a
constant: in the opening lines of a program, at the beginning of a layer, or at the
beginning of a test. The relative placement of a constant's definition within a
program determines its scope, or active range. For a complete discussion on
constants, refer to Section 29.
LAYER:
4.
Layers. The largest block, the layer, corresponds to the OSI modeL There may
be up to seven layers in any test.
TEST:
5.
Tests. A layer may contain any number of simultaneous tests. Every test resides
inside a layer.
STATE:
6.
States. In turn, each test may contain any number of states. A state always
resides inside a test. Only one state in each test is active at one time.
Within each state, there may be a number of triggers. A trigger always resides
inside a state. Each trigger is composed of a conditions portion and an actions
portion.
CONDITIONS:
7.
Trigger conditions. A single condition or a group of conditions is normally listed
after the CONDITIONS identifier. Rules for grouping trigger conditions, as well as
the meaning of each trigger condition, are explained in Sections 31 and 32.
28-8
SEP'95
28 Programming Blocks
ACTIONS:
8.
Trigger actions. The ACTIONS identifier precedes the list of trigger actions. This
list may be empty, or it may include one or several trigger actions. The various
trigger actions are described in Sections 31 and 32.
9. Next state. The identifier NEXT_STATE, explained in the following paragraphs, can
replace the ACTIONS: identifier in a trigger if there are no other actions; or it can
follow the ACTIONS: identifier to indicate that branching to another state is one of
several actions taken by the trigger.
(B) Run-time Transitions Between States
Run - time transitions between states are controlled by triggers. To indicate a
run-time branch from one state to another, use the NEXT_STATE action, followed by
(a) the name of the state you wish to go to, or (b) the NEXT token, indicating whatever
state happens to follow sequentially in the spreadsheet program.
You may use a NEXT_STATE action once per trigger and as many times as needed in
one state to allow for multiple branching possibilities.
When two triggers come true at the same time and both potentially result in
branching to another state, the trigger which is checked last (the last trigger
sequentially displayed on the spreadsheet) will cause branching to the state it names.
(The first trigger will not cause branching.)
Look at the two triggers shown in the example which follows. The first searches for
any SDLC Information frame. The second searches for an Info frame with a
particular frame address. By definition, whenever the second trigger is true, the first
trigger is also true. When an Info frame with the correct address is received, the
second trigger causes the test to branch to the State respfrm. However, if these
triggers are reversed as shown in the second example, the test always branches to the
State otherirm, regardless of the frame address.
STATE: frmadd
CONDITIONS: DTE INFO
NEXT_STATE: otherfrm
CONDITIONS: DTE INFO ADR=C1
NEXT_STATE: respfrm
correct
{
wrong
order
{
order
STATE: frmadd
CONDITIONS: DTE INFO ADR=C1
NEXT_STATE: respfrm
CONDITIONS: DTE INFO
NEXT_STATE: otherfrm
28-9
SEP'95
~ --~ .~-~~--.--.-
......................
.. ~-----.-.----------------------
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
(C) Recommended Format
The format of a Protocol Spreadsheet is entirely flexible. The only rule is that block
identifiers must (with rare exception) be included in the program to designate
boundaries between programming blocks.
The following is a suggested program format. To create a visual distinction, the
keywords which define program blocks are placed at the beginning of a line. Smaller
blocks are indented to show that they reside within a larger block. An automatic
indent feature, described in Section 30, is included as an editing function and is
turned on by default.
LAVER: 1
TEST: echo_msg
STATE: message
CONDITIONS; DTE STRING "hello·
ACTIONS: PROMPT: 'Spreadsheet trigger true.•
NEXT_STATE: echo
STATE: echo
CONDITIONS: DCE STRING "hello·
ACTIONS: PROMPT· Echoed message received"
NEXT_STATE: message
(D) Omitted Block Identifiers
It is recommended that, for ease of tracking a program, block identifiers be placed at
the beginning of every block. However, in brief programs, certain block identifiers
may be omitted.
It is, in fact, possible for a program to begin with a STATE identifier. The compiler
then assumes that you have begun the first test inside the first layer of the program.
To start another program block, you must use a STATE, TEST, or LAYER identifier.
NOTE: Any constant declared in the opening lines of a test which
omits the LAYER and/or the TEST keyword is still a global constant, as
long as it precedes a STATE or CONDITIONS identifier.
28.4 Compiled Spreadsheet
Using the Compile command on the File Maintenance screen, you can compile and save
the contents of the Protocol Spreadsheet in a linkable-object file. Later, this program
can be combined with an active spreadsheet program. To do so, simply reference the file
at the top of the Protocol Spreadsheet.
(A) The OBJECT Block-ldentHier
Use the OBJECT block-identifier on the Protocol Spreadsheet to access the compiled
spreadsheet code in a linkable-object flle.
Note to C Programmers: The OBJECT identifier may also be used to
access definitions for user routines. Refer to Section 55.4(C).
28-10
SEP '95
28 Programming Blocks
1.
Placement. The OBJECT block-identifier(s) must appear at the top of your
spreadsheet program, ahead of any other identifier (except IL BUFFERS). Access
the OBJECT: softkey by pressing MORE on the initial rack of softkeys. Notice that
the MORE, IL BUFS, and OBJECT: softkey tokens are not available once any other
programming block-identifier has been selected.
NOTE: Use OBJECT in your active spreadsheet program only. Do not
incorporate it in a spreadsheet that will be compiled and saved as an
LOBJ file. Although the code will compile, the referenced LOBJ file
will not be read.
2. Format. The format for the OBJECT block-identifier is as follows:
OBJECT: "filename.o·
The identifier references only one linkable-object file, but you may include as
many OBJECT identifiers as you wish.
The relative or absolute pathname of the linkable-object file is enclosed in
quotation marks.
3.
SEP '95
Search rules for linkable-object files. As your spreadsheet program compiles, the
INTERVIEW's filing system is searched for the linkable- object files referenced
in OBJECT identifiers.
•
If the referenced LOBJ filename begins with FD11, FD2/, or HRD/, the
INfERVIEW interprets it as the absolute patbname and makes only that one
search.
•
Pathnames beginning with a / indicate that the root directory on each drive
should be the beginning point of the search. The drives are searched in the
following order: current drive, FDl, FD2, and HRD.
•
Otherwise, the name may be a one-word filename or a relative pathname
which includes the directories leading to the file. The highest directory in a
relative pathname must reside in the current directory or in one of the /lib
subdirectories. The following directories-and only the following
directories-are searched, in the order given:
28-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
1.
2.
3.
4.
5.
6.
7.
8.
9.
current directory on the current drive (indicated on the File
Maintenance screen)
lusr/lib on the current drive
Isysllib on the current drive
FDlIusrllib
FD21usrilib
HRD!usrllib
FDlIsys!lib
FD2!sysllib
HRDlsysllib
If the pathname is not located in any of these directories, the program will not
compile and an error message wi11 be returned to the operator.
(8) Compiled LOBJ Code is Combined with Spreadsheet
During compilation, the compiled spreadsheet in the LOBJ fIle is combined with your
active spreadsheet program. This means that the LOBJ code must be compatible
with the current menu setups and spreadsheet program-as though the source code
of the LOBJ file were actually present in the spreadsheet buffer.
(C) Counter and Flag Conditions
Special consideration is given to COUNTER and FLAG conditions during the Compile
;%~t operation. The system identifies the condition as either transitional or
status. (See Section 31.2.) If it is used both ways in the same spreadsheet fIle, it will
always be identified as transitional.
Within a single spreadsheet program, you may reference more than one LOBJ file
which uses the same COUNTER or FLAG. If one of the files uses the COUNTER (or FlAG)
as a transitional condition, however, all other referenced files containing the same
COUNTER (or FLAG) must also use it as a transitional condition at least once. This rule
ensures that each action on the specified COUNTER (or FLAG) will consistently trigger
the appropriate COUNTER (or FLAG) conditions.
(D) Advantages of Compiled Spreadsheet
Linkable-object fIles assist the programmer in efficiently using the INTERVIEW's
memory and spreadsheet buffer.
28-12
•
When commonly utilized conditions and actions are saved in linkable-object
files, space in the spreadsheet buffer otherwise dedicated to this purpose can be
used for additional programming.
•
Since the code in LOBJ files has already been compiled, the INTERVIEW can
support a larger program without a corresponding increase in compilation time.
•
The spreadsheet code in a linkable-object file is transparent to the configuration
of the unit. LOBJ files created on one unit can be used on a unit configured
differently, as long as the code is compatible with the various menu parameters.
SEP '95
28 Programming Blocks
28.5 Configuring the Size/Number of IL Buffers
Interlayer (IL) message buffers are used to pass data up the layers as it is received and
down the layers as it is transmitted. (See Section 24 on the layered-programming model
and Sections 34 and 62 for more information on the uses of IL buffers.) The
INI'ERVIEW allocates IL buffers, as needed, to pass data between layers. Then, the
buffers are automatically erased and used again. In this way, the INTERVIEW maximizes
its use of available memory space. Without these reusable buffers, data in Run mode
would quickly eat up all of the memory in the unit. (See Section 62.3(A) for information
on manipulating IL buffers.)
IL buffers contain the data itself or point to the memory location (outside the buffer) of
the data. It follows, therefore, that the larger the IL buffer, the more data it can hold. By
default there are 16 IL buffers that can be in use at a given time. The size of each buffer is
4,096 bytes.
When you are performing emulation with windowing, you can quickly use up these sixteen
buffers. Once all buffers are in use, additional data is lost. To prevent this from
happening, you may want to reconfigure the number and size of IL buffers.
Press the IL BUFS softkey to set the number and size of the IL buffers. Figure 28-4 shows
the softkey selections. Select one of seven number/size combinations for the
INI'ERVIEW's IL buffers. The default selection is 16/4K. This means that the
INTERVIEW will have a maximum of 16 IL buffers in use at a given time, each one 4,096
bytes (4 Kbytes). This size, and all others, includes a 32-byte buffer header.
Figure 28-4 Softkey path to the seven number/size combinations for IL buffers.
Note to C Programmers: There are two preprocessor
directives-#pragma ii_buffers and #pragma iCbuffer_size-which the
C programmer may also use to configure the IL buffers. These
directives provide additional flexibility. See Section 62.1(A).
SEP '95
28-13
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Notice that each number/size combination utilizes 65,535 bytes (64 Kbytes) of RAM. This
total represents the maximum amount of RAM that can be allocated for IL buffers from
the Interlayer Buffers menu.
NOTE: Keep the following points about object-file compatibility in mind
when setting the number/size of IL buffers:
•
If the number of buffers is less than or equal to 16, the file will load
and operate on any unit with equivalent hardware, with a software
release earlier than 8.00.
•
If the number of buffers is greater than 16, the file cannot be loaded
on a unit with a software release earlier than 8.00.
•
An object file generated under a software release earlier than 8.00
will run on software revision 8.00, or higher, with 16 buffers of 4
Kbytes each (the default).
28.6 Comments in a Spreadsheet Program
You may write comments to yourself or to others who may view your spreadsheet program.
Comments begin with 1* and end with */, as in the examples below. Use comments
generously throughout spreadsheet programs. Since comments are ignored by the
compiler, they do not affect the compilation time of the program.
(A) Characteristics
1.
Valid characters. When an opening 1* is detected by the compiler, everything that
follows is disregarded until a closing */ is encountered. This means that all
hexadecimal, control, and ASCII characters (or character combinations) are valid
in comments. The[],[2,[8J, and not-equal symbols are also legal entries.
Two entries are not legal in comments. The first is the IBl symbol. It cannot be
used because it is not a valid Protocol Spreadsheet entry. (Bit masks on the
spreadsheet are delimited by « and ))). An alarm will sound if you try to use the
bit-mask symbol. The second invalid entry is the closing delimiter (*1). An
embedded */ causes the comment to be ended prematurely. Since the remainder
of the comment (and the programmer's intended closing *1) is a syntax error, the
program will not compile.
28-14
2.
Length. For practical purposes, make comments as long as you wish. They may
span several lines, or they may be empty.
3.
Location on spreadsheet. Comments may be placed within any of the
programming blocks: OBJECT, IL_BUFFERS, CONSTANTS, LAYER, TEST, STATE,
SEP'95
28 Prpgramming Blocks
CONDITIONS, ACTIONS, or NEXT_STATE. In CONDITIONS blocks, however, they must
appear with at least one valid condition. The following CONDITlONS block
containing only a comment will cause compilation to be aborted:
STATE: message
CONDITlONS: /* KEYBOARD· "*!
ACTIONS: SEND "( FOX)) - GOOD_BCC
Since the compiler ignores anything inside the 1* */ delimiters, it can find nothing
in the CONomONS block. When you go to the Protocol Spreadsheet and search
for error messages, the following message will be displayed: "Empty Conditions
Section. »
Comments may not be embedded within a keyword. This program also will not
compile:
STATE: message
CONOmONS: KEY!* This comment wilt cause a syntax error*/BOARD ••
ACTIONS: SEND "((FOx»)» GOOD_Bce
(8) Using Comments
Comments are particularly useful in describing the purpose of a programming block.
Let's return to the two programming examples in which branching to another state
occurs based on DTE Info-frame addresses. The following comment makes the
programmer's intentions clear.
STATE: frmadd
/* If a DTE INFO frame has an address of C1 , go to state "respfrm.» For all other DTE INFO
frames, go to state ·otherfrm." */
CONDITlONS: DTE INFO
NEXT STATE: otherfrm
CONDmONS: DTE INFO ADR= C1
NEXT_STATE:~pmm
Comments can be useful debugging tools. Suppose the same comment appeared in
the programming example with the order of the two triggers reversed.
STATE: frmadd
/* If a DTE INFO frame has an address of C1, go to state "respmm: For all other DTE INFO
frames, go to state "otherfrm.» *1
CONDITIONS: DTE INFO ADR= C1
NEXT STATE: respfrm
CONDiTIONS: DTE INFO
NEXT_STATE: otherfrm
With the comment present, it is easier to identify the discrepancy between the
programmer's expectations and the actual program.
SEP'95
28-15
- -_ _ _ _ _
k_ilIIIl.~
~'
INTERVIEW 8000 Series Basic Operation: 951-80424-01
28-16
SEP'95
29 Constants
29 Constants
SEP '95
29-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
OBJECT:
(OBJECT identifer(s}, if included, must precede all other identifiers,
except IL_BUFFERS)
IL-BUFFERS:
CONSTANTS:
LAYER:!
CONSTANTS:
QL BUFFERS identifier, if included, must precede aU other
Identifiers, except OBJECT)
(global constants are defined here; they can be
accessed throughout the test)
(Layer 1 constants defined here apply to
thIS and following layers)
TEST:
CONSTANTS: (test constants are defined here;
they apply to all states within the test)
STATE:
CONDITIONS:
i
first
trigger
ACTIONS:
Program
CONDITIONS:
State Block
1
Test Block
f
Layer
Block
second
trigger
ACTIONS:
·1
STATE:
CONDITIONS:
NEXT STATE:
TEST:
CONSTANTS:
(constants for this test are defined here)
STATE:
CONDITIONS:
ACTIONS:
NEXT_STATE:
LAYER: 2
CONSTANTS:
(Layer 2 constants defined here apply to
thiS and following layers)
Figure 29-1 Constants may be defined in three different locations: before the first layer, after a layer identifier, or
after a test identifier.
29-2
SEP '95
29 Constants
29 Constants
The Protocol Spreadsheet permits the use of constants as a means of simplifying the creation and
modification of test programs. A constant is merely a symbolic reference to a predefined string of
characters.
29.1 Definition of Constants
There are three legal locations for the definition of a constant: in the opening lines of a
program, at the beginning of a layer, or at the beginning of a test (see Figure 29-1).
Constants must always be defined at the beginning of the programming block in which they
are referenced. A test-level constant may not be preceded by a lower-level block
identifier (STATE, CONDITIONS, or ACTIONS). A constant definition or definition block must
be followed by another keyword.
A constant definition begins with the identifier CONSTANTS. A colon (:) may follow. The
constant name is then entered. Next comes the definition, a text string which the constant
represents. The constant name and text string may be separated by an equal sign ( =).
The text string is enclosed in double quotes. Each constant definition comprises a single
logical line. Logical lines wrap as needed to subsequent lines on the spreadsheet, but they
do not contain hard returns. See Section 30.1(A).
More than one constant can be defined following a single CONSTANTS identifier. Following
is the suggested format for a constant definition block. A constant definition block
(whether it contains one or more definitions) must be followed by another block identifier.
CONSTANTS:
cmd adr = "03"
resp:adr = ~01"
resend
= "1.5"
retries
== "10·
To include quotation marks or backslashes in the definition string of a constant, precede
each with a backslash escape-character (\). Here, for example, is the constant definition
of a general poll:
CONSTANTS: drop_A= " M\" \" "U"
The backslash will be deleted by the parser when the constant definition is scanned:
M" "EQ
SEP '95
29-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
If the constant is contained in a search or transmit string, it will not be scanned for the
escape character or for closing quotation marks. The characters shown above represent
the expanded constant. Notice that the enclosing quotation marks of the definition string
are not actually part of the constant. In our example, the following string will be searched
for or transmitted:
AA"" EO
29.2 Constant Names
Constant names must begin with a letter or underscore character. They may include any
of the following characters: underscore ( _ ), upper or lowercase letters, and decimal
numbers 0 through 9. Upper and lower case letters are distinguishable in constant names;
for example, constants big, Big, and BIG will not be confused by the INTERVIEW's
compiler.
29.3 Scope
The relative placement of a constant's definition within a program determines its scope, or
active range.
(A) Global Constants
If you want to be able to reference a constant anywhere within a program, you must
define it in the first lines of the program. Only an OBJECT or IL_BUFFERS block may
precede global constants. No other block-whether a block identifier (LAYER, TEST,
STATE. CONOmONS, or ACTIONS) is entered or implied-may be placed before a global
constant.
(8) Layer Constants
A layer constant must be defined before the first reference to it. The definition is
placed in the lines foHowing the LAYER identifier. (In a single-layer program, the
LAYER identifier may be omitted.)
The definition of a layer constant must faU outside component blocks of the layer
(outside tests and states).
A layer constant can be referenced within any test, state, or trigger which that layer
contains. It may also be referenced in any other layer which foHows on the
spreadsheet. The only exception to this is when the constant is superseded by a
constant of the same name (see the section on precedence which follows).
29-4
SEP '95
29 Constants
(C) Test Constants
A test constant must be defined at the beginning of a test block and before the first
reference to the constant. While the TEST identifier may be absent in a single-layer,
single-test program. the scope of a constant can only be limited to a test if it follows
a TEST identifier.
A test constant cannot be defmed within a state, but it can be referenced by any
trigger in any state which the test contains.
29.4 Referencing Constants
Whenever you refer to a constant in your spreadsheet program, the constant name must
be enclosed in double parentheses-for example, «Frmsize)). Use the key sequence §9-@J
and S -@ to create double parentheses. Shown here is the constant ADDRESS which
replaces an SDLC frame address used throughout the test. When the frame address is
modified, only the constant need be changed.
LAYER: 2
TEST: poUing
CONSTANTS:
ADDRESS
·C1
STATE: init
CONDmONS: ENTER_STATE
ACTIONS: SEND SNRM ADR= «ADDRESS» P!F= 1
TIMEOUT retransm RESTART 3.000
CONDmONS: RCV UA ADR= (CADDRESS») P/F= 1
.ACTIONS: TIMEOUT retransm STOP
RESET NR RESET NS
NEXT STATE: info xfr
CONDiTIONS: TIMEOUT retransm
NEXT_STATE: init
=
ff
As long as syntax is observed, a constant may be used to replace a large block of text which
would otheIWise be repeated. Following is an example of a long, repetitive text block
given as a constant defmition and referenced within the program as (UK_SETUP». Notice
that the constant definition is contained in a single logical line. The highlighted plus
symbols, automatically generated by the spreadsheet editor, indicate the point at which the
line wraps on the screen.
LAYEA:2
CONSTANTS:
LK_SETUP == "ACTIONS: SEND DISC PROMPT \"Disconnect link\ft CONDII
TlONS: RCV UA ACTIONS: PROMPT \"Disconnected\" CONDmONS: RCV
DISC ACTiONS: SEND UA CONDmONS: ReV SASM ACTIONS; SEND UA PRCII
MPT \"wnk restarted\R.
TEST: link_up
STATE: fr_setup
CONDmONS: ENTER_STATE
LK_SETUP))
NEXT STATE: fr
STATE:fr
CONDmoNS: ENTER STATE
ACTIONS: SEND INFONR= 01
CONOmoNS:RCVFRMR
ACTIONS: PROMPT "FRMR received-test OK·
«
29-5
SEP'95
._..
_--------_._-_._-----------,------------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
NOTE: Global and layer constants declared on the Protocol
Spreadsheet may be referenced on any of the Trigger Setup screens as
part of a receive or transmit string.
29.5 Nested Constants
The definition of a constant may include a reference to another constant. This is called
nesting. An example of nested constants is shown below. On the Protocol Spreadsheet, it
is possible to nest constants eight levels deep.
CONSTANTS:
= ·000"
rev
·001"
send len
-'00
=
send_data
send_pkt
:=
"data (Csend-'cn))"
= "send «send_data)) "
NOTE: It is illegal to define two constants circularly. If, for example,
you define CONSTANTS: peat = ( repeat)) and CONSTANTS: repeat =
« peat)) , you will receive an error message when you attempt to run
the program.
29.6 Precedence
Programming practice usually restricts constants to a single definition. A given name
should remain the same throughout the entire program.
In some special cases a constant name may have definitions that differ in separate parts of
the test. It is not legal to define the same constant name twice at the same level within the
same block; however, the same constant name can be defined differently inside of distinct
blocks. You might, for example, define a global constant as maxlength ="8" at the beginning
of a program. Nothing prevents you from defining a constant as maxlength = "128" within a
layer or test included in the same program.
NOTE: Use the ability to give different definitions to the same
constant name sparingly and with great caution.
The rule of thumb is this: When the same constant name is defined more than once, the
value of the constant is controlled by the smallest block in which it resides. When that
block ends, its value is controlled by the next larger block, and so on. So, a constant might
have different values within a TEST, within a LAYER, and throughout the remainder of the
program.
29-6
SEP '95
29 Constants
Consult the following example. Globally, the constant maxlength has a value of 8. This
value holds until the constant takes on a new value in Layer 2. where it is defined as
maxlength = "128". Inside the Layer 2 test named shortfrm, maxlength is briefly given a value
of 4. In Layer 3, the constant maxlength is not redefined, and its value returns to 8 (since
this is the global definition of the constant).
CONSTANTS:
maxlength = "8
LAYER: 2
CONSTANTS;
maxlength = -128
TEST:shortfrm
CONSTANTS:
maxlength =: "4"
STATE: supfrm
CONDITIONS:
ft
ft
LAYER: 3
TEST: pktlen
STATE: datapkts
CONDITIONS:
29.7 Expansion
The spreadsheet editor checks constant definitions and references for several types of
errors as you enter your program. In the interest of time, however, it will not expand a
reference to a constant embedded in a text string. This means that nested constants are
not checked for errors as you write your program.
The compiler expands these constants when you run the program, and any obvious errors
will result in an operator message. Be advised, however, that it is possible for embedded
constants, once expanded, to produce a valid, but unintentional, program variation.
SEP'95
29-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
29-8
SEP '95
30 Editor
30 Editor
SEP'95
30-1
--
,=............"'_,.._.,....
,,_
- - - - - - · - - - - - - - - - - - - - - - - - -_ _ _ _
' ....
n ....
_ ......._•• ~_._
.......
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
Figure 30·1 Press the EDIT key to access special editing functions on the Protocol Spreadsheet.
Press Fl, then F7, to access additional editing functions.
30-2
SEP'95
~
30 Editor
1
30 Editor
As you create a spreadsheet program, you may use any of the keys on the editing keypad to modify
your entries. Sophisticated editing options are added to these basic functions when you press ~
(see Figure 30-1). I!i!J is an alternate action key which returns you to program function keys if you
press it a second time.
30.1
Basic Editing Functions
Use the editing keypad on the right of the keyboard to perform simple editing functions
(see Figure 30-2).
Figure 30-2 The editing keypad.
(A) Insert and Delete Keys
The top three rows of the keypad contain insert and delete functions. Available
functions are insert a character, delete a character, rubout a character and insert,
delete, or clear a line.
Insert Line and Delete Line functions apply to the logical line, not the physical line.
A logical line has segments which end at the end of the screen but are not terminated
with a 8. Instead, the logical line wraps to the next line or lines on the screen. You
can distinguish a logical (wrapped) line by the highlighted plus symbols (a) at the
end of each segment on the screen. When you insert a line, it appears above the first
segment of the wrapped line. When you delete a logical line, all of its segments are
deleted.
SEP '95
30-3
H_
••_.____
- - - - - -_ _ _ _ _ _ _ _ _ _
m ______
~_N~
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
1.
=
is an alternate action key. Press it once to enter Insert mode (the label
appears at the top left of the screen). Then type a character. The
character is entered at the cursor position. All text moves right. Continue to
insert characters as needed.
Press ~ again to leave Insert mode. Any character you type subsequently will
overwrite an existing character at the cursor location.
2.
1m inserts a blank line above the logical line where the cursor is located. It also
puts you into character mode. Use IB:J as described in the previous
paragraph to exit mode.
3.
~ deletes the character under the cursor. The next character to the right
moves under the cursor, and remaining text shifts left.
4.
~
5.
8
erases the remainder of the logical line from the cursor position and to the
right, leaving the line empty. 8 - 8 erases the entire logical line which the
cursor is on, but not the space the line occupies.
6.
00 deletes the character just to the left of the cursor and moves the cursor left
one space. Use 00 to correct an error in the most recent keystrokes.
removes the logical line that the cursor is on.
(8) Cursor and Movement Keys
1.
ill and 0 move up or down the screen one line at a time. 8-ff] moves the
cursor to the first line of the file. 8-0 moves the cursor to the last line of the
file.
2.
8 and 13 move the cursor to the right or left one space at a time. 8-13 moves
the cursor forward to the beginning of the next field. 8-8 moves the cursor
back to the beginning of the previous field. ~ -8 moves the cursor forward to
the end of the current line. ~ - [3 moves the cursor back to the beginning of the
current line.
30-4
3.
~
4.
~
5.
mID moves text up one line at a time, without changing the cursor location.
6.
~ recalls the previous screen of text and locates the cursor at the same relative
position on the screen.
7.
[BJ moves the cursor to the same relative position on the next screen of text.
moves the cursor to the top left- hand corner of the current screen.
leaves the cursor where it is and moves text down one line at a time.
SEP '95
30 Editor
(C) Other Keys on the Pad
1.
8
2.
~
provides a means for "saving a place" in a program file. With the cursor at a
desired location, press 8. then any number from 0 through 9. This marks the
column and row in memory (no mark actually appears). At any time, you may
locate one of ten possible marks in the file. Press 8-8, then the desired
number to move fOlWard or back through the file to the desired location.
is not currently implemented.
30.2 Editing Function Keys
The editing softkeys shown in Figure 30-1 appear when you press §) with the Protocol
Spreadsheet displayed. Press §J again to move back to the program function keys. When
you press ®J for BLOCK, a subset of editing options appear. Press 8 to move from this
subset back to the top level of editing functions.
(A) Block Functions
With the regular spreadsheet programming selections displayed, press §), then
BLOCK (If]) to display the block commands. Six editing commands (keys §] through
@) operate on blocks of text. When you are using a Clear, Delete, Move, Copy or
Write command, you must mark the beginning and end of a block prior to executing
the command.
1.
Begin and End. Use BEGIN to mark the first character of a block at the cursor
location. Move the cursor one position to the right of the last character you want
to include in the block. Then press END. The block, once defined, is highlighted.
Whenever a block is highlighted, you may clear, delete, move, or copy the block
or write it to another file.
NOTE: The block may be defmed in the reverse direction. The
cursor must be located one position to the right of the first character
of the block and located over the last character of the block.
2.
Clear. Press !TIJ for CLEAR to "unmark" a block. The highlighting disappears to
indicate that there is no longer an active editing block.
3. Delete. Press!El for DELETE to remove the marked block. Text below the block
fills in the deleted area.
SEP '95
30-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTE: You may recover a deleted block using the Undelete
command on the alternate set of editing function keys. Repeated use
of the Undelete command will recover up to ten deleted blocks. The
text is recovered in the reverse order in which it was deleted-i.e.,
last deleted, first recovered.
4.
Move. To move text, define a block and locate the cursor at the position where
you want the text block to start. Then press MOVE. The text is removed from its
original location and is inserted at the cursor location. The moved text remains
highlighted as a block.
To retain the original line breaks in the text, insert a blank line at the position
where the new text will be located. Otherwise, inserted text will be placed at the
beginning of the line marked by the cursor.
5. Copy. To copy text, mark a block, move the cursor to the desired location, and
press COPY. A duplicate of the text block appears, highlighted. Since the block is
already marked, you may copy it repeatedly without remarking it.
6. In/Out. To access the four ReadIWrite options, press the function key marked
IN/OUT. A new rack offunction keys appears (see Figure 30-1). These functions
are explained in Section 30.2(B).
(8) Read and Write
The READ and WRITE commands are block commands but are exceptions in that they
allow you to move text into and out of your program file. You can use a READ
command as you would a load command to call in other Protocol Spreadsheet files.
Likewise, you can save a copy of the Protocol Spreadsheet using a WRITE command.
The four command options on this rack of function keys are Read Formatted. Read
Unformatted, Write Formatted, and Write Unformatted.
1.
Formatted Read and Write commands. Read Formatted and Write Formatted are
intended for use with spreadsheet files and any other files which contain
nonprintable (non - ASCII) characters:
•
Special characters such as bit masks, 1EI,@),II,riJ,!8], (C, and))
•
Any control characters outside the limited subset listed in the following
paragraphs for unformatted Read and Write commands
•
"Packed" hex characters; that is, hex characters as they appear on the screen
(for example 7(,3", and 40 ).
The Write Formatted command saves these nonprintable characters as expanded
ASCII and uses pound signs (#) and backslashes (\) as prefIXes to mark their
location for later decoding. Thus, when a file is written, # becomes ##, \
becomes \\, while 30 becomes #30, lEI becomes \7E, and so on.
30-6
SEP '95
30 Editor
The Read Formatted command decodes the expanded representations properly
and displays them as they previously appeared on the Protocol Spreadsheet. If by
mistake you use the Read Formatted command on a pure ASOI file which
contains backslashes or pound signs, the INTERVIEW will attempt to decode the
characters which immediately follow. For example, a preprocessor directive from
an #include file such as
#define max 5
will be decoded as
DE
2.
fine
max 5-which obviously cannot be interpreted by the preprocessor.
Unformatted Read and Write commands. Read Unformatted and Write
Unformatted are intended for use with #include files and other pure ASCII files.
Any files that contain only ASCII and a limited subset of control characters may
be successfully read in or written to disk with these commands. The set of control
characters which are recognized and retained by these commands follows:
•
Tab (1:1,.)
•
Form Feed (FF )
•
Carriage Return (Cit )
•
Bell (8.. )
•
Line Feed ('1- )
Any other control characters are stripped from the file when one of these
commands is used-as are packed hex characters (3.. , "'0, and so on) and special
characters.
NOTES:
3.
SEP'95
a.
If you mistakenly use a Write Unformatted command on a file which contains
nonprintable characters, these characters will be stripped from the file
without warning.
b.
Since no messages inform you of whether file contents are formatted or
unformatted when you perform a Read or Write, you should keep track of
the file type for later reference. An easy way to do this is to append a suffix
(such as _u for unformatted or Jfor formatted) to the filename. #include
files, which end with the SUffix .h, require the Read Unformatted and Write
Unformatted commands.
How to execute a Read command. To copy an existing file into the Protocol
Spreadsheet, place the cursor at the location where you want the file to start.
30-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Press READ/F or READ/U, whichever is appropriate (see previous paragraphs), and
type in the exact filename (full or relative pathname). Then press ~ or~.
The entire file is highlighted and copied at the cursor location. Any original
spreadsheet text beyond the cursor position is pushed to the end of the file which
has been read in.
NOTES:
4.
a.
When giving the filename to be read, provide the location of the file by disk.
If the destination disk is omitted, only that one named in the current
directory on the File Maintenance screen will be searched. If the file is
located on the current directory disk, it will be read; otherwise, an error
message will appear at the top of the screen.
b.
You may read in an entire spreadsheet file without affecting the
configuration of other menus in the IN1ERVIEW. A full program,
containing the spreadsheet and the contents of all other menus, must be
loaded from the File Maintenance screen. See Section 15.3(E).
How to execute a Write command. You may file a copy of all or part of your
spreadsheet entries using one of the Write commands. First, mark the beginning
and end of the block you wish to save to a file. Then press WRITE/F or WRITEIU,
whichever is appropriate (see previous paragraphs), and give the full or relative
pathname of the file when prompted. Press §] or 8. The file will appear in
the directory listings on the File Maintenance screen. If you type in the name of
a file which already exists, your spreadsheet text block will overwrite the entire
file if the file is the same file type.
NOTE: If you wish to save the configuration of other menus along
with your spreadsheet program, use the Save command on the File
Maintenance screen; see Section 15.3(F).
(C) Other Editing Commands
To return to the main set of edit keys from the bank of Block commands, press ~.
The remaining commands in the set are described in subsequent paragraphs.
1.
Undelete. You can return the last deleted line or block to the screen. First, locate
the cursor where you want the deleted text to appear, and press UNDELET. The
deleted text will be inserted at the cursor location. Repeated use ofthe Undelete
command will recover up to ten deleted blocks.
2. Find. Press FIND, and the prompt "Find:", along with the cursor, appear at the
top of the screen. Type in the string you wish to locate, and press 8. The
30-8
SEP '95
30 Editor
command performs a forward search to the end of the file. Press AGAIN to search
for another occurrence of the same string. The message "Text not found" is
posted at the top of the screen if the entered text does not occur between the last
cursor location and the end of the file.
3. Replace. To replace a text string (with a maximum of 50 characters), press
REPLACE. The prompt "Find:" appears at the top of the screen. Type in the string
that you want to replace, and press ~ or 8. The prompt "Replace with:"
appears. 'JYpe in the new string, and press §) or S. The command searches
forward in the file from the cursor position and replaces the first occurrence of
the string. To continue replacing the old string, press AGAIN, until the message
"Text not found" is displayed at the top of the screen. The search for the text
string stops at the end of the file.
NOTES:
a. If you want the entire file to be searched, make sure the cursor is positioned
at the beginning by pressing 8-ffJ.
b.
Case does make a difference. If the string "echo" is replaced, "Echo" will
not be replaced.
4. Again. You may repeat Find and Replace commands by executing the command,
then pressing AGAIN.
5.
Go-line. To move from one line to any other line in the file, press GO-UNE.
When prompted, enter the sequential number of the line you want, and press G§J
or 8.
6. Auto-indent. will appear at the top right of the screen when
Auto-indent is on. Auto-indent is an alternating function key. If the indent
cue does not appear, press the function key once to turn on Auto-indent. Press
the function key again to tum off indentation. Auto-indent is active both when
editing keys and program function keys are active.
NOTE: To move through the program one line at a time at the points
of indentation, use the 8 key instead of the ttl and!±) keys.
This feature is an aid in setting up spreadsheet programs. When you use a
function key to enter a keyword, the keyword appears on a new line, and, if it is a
component belonging to a larger block, it is indented. For example, if you press
LAYER:, the keyword is not indented, but if you press TEST, the keyword TEST:
appears on a new line, indented three spaces from the first letter of its "owner"
SEP'95
30-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(LAYER). When you press STATE, the keyword STATE: is indented another three
spaces, to show that it is a component of the test.
NOTE: If you type in your spreadsheet entries, the last level of
indentation is observed; however, other auto-indent features are not
applied to manual entries.
7. Go-en-or. Most syntax errors made on the Protocol Spreadsheet are indicated
by strike-through of the text where the error occurs. Press GO-ERR to move to
the first editing error found moving forward (down) through the file. Press
GO-ERR once more to move to the next editing error. The search for editing
errors stops at the end of the file, and the message "No more errors" is displayed
at the top of the screen.
Errors which are detected by the C translator, preprocessor, or compiler are not
indicated by the editor. When you press G!] and the test is compiled, the errors
will be noted. If there are errors in the test, the INTERVIEW will revert to the
Protocol Spreadsheet and display a diagnostic message about the first error
rather than run the test. Press GO-ERR to search for additional errors until the
"No more errors" messages is displayed.
If you leave the Protocol Spreadsheet to go to another screen, but then want to
review the list of the errors again, return to the Main Program menu. Press @],
§), lW (spreadsheet screen, edit, GO-ERR). Repeat GO-ERR for the next one.
When there are no more errors, a prompt to that effect will appear at the top of
the screen.
Error messages are listed in Appendix A.
30-10
SEP '95
31 Layer-Indepgndent Conditions and Actions
31 Layer-Independent Conditions
and Actions
Condition - and- action triggers are the basic programming elements on the INTERVIEW Protocol
Spreadsheet. Triggers can be thought of as "If, Then" statements, organized on the spreadsheet
under the headings CONomONS and ACTIONS. Each pairing of CONomONS and ACTIONS on the
spreadsheet represeJ;lts one trigger, similar to but also more comprehensive than one of the sixteen
Trigger Setup screens (see Sections 25 and 26). Any number of triggers may be created in the
spreadsheet program.
During a test, a trigger condition is active (potentially true) whenever the state it belongs to is
active. An action is taken whenever the condition (or set of conditions) preceding it is true.
This section covers those conditions and actions that are not local to a particular protocol at a
particular layer of ptogramming. These are the conditions and actions that are made available as
softkey selections in every state in the program without exception.
31.1
Naming Requirements
Flags, accumulators, signals, counters, timers, and timeouts are layer-independent trigger
entities that are created by the user in any number and combination and called out by
keyword (FLAG, ACCUMULATE, SIGNAL, COUNTER, TIMER, TIMEOUT) and by name. The names
are assigned by the user and referenced in triggers throughout the program.
A name on the Protocol Spreadsheet must not exceed sixteen characters nor include any
except theftfty-two alpha characters (upper and lower cases) and the ten numeric
characters in addition to the underscore (_ ) character. The first character in each name
must be an alpha character.
The practical size limit for the names of counters, timers, and accumulators is eight
characters~ since a longer name cannot be called out on the tabular and graphic statistics
screens.
For the sake of program readability, we recommend that all user-assigned names be
entered in lower case. In this way they will be distinguishable from keywords. The
spreadsheet compiler does not insist on lower case for user-assigned names, however.
31-1
SEP '95
~
--~~-----------.--------------.---
-----------_
__.
_.
_ _._-
................. ......"'''''
... ''''.......
INTERVIEW 8000 Series Basic Operation: 951-80424-01
The spreadsheet compiler does treat upper- and lower-case names as distinct. A timer
named delay will not be referenced by the name DELAY (or Delay), for example. Keywords
are treated differently: typing timer has the same effect as typing Timer or TIMER or pressing
the softkey that writes TIMER to the screen.
Names of different entities need not be kept distinct. The program will have no trouble
keeping a SIGNAL named ready separate from a FLAG of the same name. (The user may
have difficulty keeping them separate, however.)
31.2 Rules for Combining Conditions
Several layer-independent conditions are "transitional" (or "instantaneous") conditions,
in that they are true only for the instant that they transition to true. These transitional
conditions are enter-state, timeout, keyboard, time-of-day, and signal conditions.
Triggers that combine two transitional conditions are illegal and will not compile, since
there is no chance of two transitional events occurring simultaneously.
The other class of layer-independent conditions, comprised of buffer-full, counter, and
flag conditions, may be thought of as transitional/status. When used alone in a trigger,
these conditions are true only at the moment they transition to true.
For example, the condition COUNTER retries GE 5, used by itself preceding an Actions block,
will be true once when the counter increments from 4 to 5, but not when the same counter
increments to 6. For the condition ever to be true again, the counter must first transition
to a value less than 5.
When used in combination with transitional conditions, these transitionallstatus conditions
are checked for a current status of true at the moment the transitional condition
transitions true. They may retain this status of true indefinitely.
Here is an example of a transitional/status condition (counter) used in combination with a
transitional condition (timeout).
CONDITIONS: TIMEOUT response
COUNTER retries GE 5
ACTIONS: AlARM
This set of conditions will be true every time the timeout occurs as long as the counter
retains a status of greater than or equal to 5.
When a transitional/status condition is used in combination with one or more other
transitional/status conditions, the first condition in the user-defined sequence of
conditions will be transitional, while the others will be checked for truth or falsity only
when the first condition transitions to true. Take, for example, a scenario where a counter
increments five times and then a flag increments five times. On the fifth flag increment,
the following set of conditions will be true:
CONDITIONS: FLAG true last 101
COUNTER true_first EQ 5
31-2
SEP '95
31 La't,er-Independent Conditions and Actions
The conditions are satisfied because the flag is transitional while the counter is static: at
the moment the flag transitions to binary 101 (decimal 5), the counter is checked for a
status of 5. Both are true. But given the same scenario, this set of conditions is false:
CONDITIONS: COUNTER true first EO 5
FLAG trueJast 101
-
Here, the counter condition is transitional, the flag is static-simply because the counter
condition is listed first. The flag condition is checked only at the moment the counter
attains the count of 5. After that, the flag is not checked again.
The condition logic is streamlined in this manner in order to be economical of processor
time, on the assumption that in a typical application the user knows which of two
conditions will be satisfied first. If users do not know whether the counter or the flag in
the above example will increment to 5 first, nothing prevents them from entering two
triggers, both having the same conditions but in a different sequence. Or they may enter
the pair of conditions on a 1tigger Setup menu, where combined transitional/status
conditions generate enough code to cover all contingencies. See Section 25.2(B)2.
NOTE: Additional rules may apply when the COUNTER or FLAG
transitional/status condition is used in a spreadsheet program
compiled and saved as a linkable-object file. See Section 28.4(B}.
31.3 Layer-Independent Conditions
The eight softkeys that represent the full set of layer-independent conditions are shown
in Figure 31-1.
(A) Enter State
This condition is true immediately as the current state is entered. Control of the
action in effect reverts to the previous state. In the example below, ENTER_STATE is
used as the condition for an alarm action in second state. The counter condition in
first state effectively controls this alarm.
STATE: first
CONOmONS: COUNTER frm err EO 10
NEXT STATE: second
STATE: second
CONOITIONS: ENTER STATE
ACTIONS: AlARM
-
SEP '95
31-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 31·1 The eight layer-independent conditions are shown in the bottom two racks of softkeys.
(8) Timeout
Any number of decrementing timeout timers may be started as trigger actions and
monitored by trigger conditions. The condition is true when the timeout timer
expires.
Here is an example of a timeout condition:
TIMEOUT response
where response is the name of the timeout timer.
After pressing the TIMEOUT softkey or typing TIMEOUT followed by space, enter a name.
The name can reference a timeout timer that was started either in a spreadsheet
action or a trigger-menu action.
(C) Keyboard
Enter a list of characters produced by keystrokes. Any key or key-combination that
produces a character on the ASCII table in Appendix D1 is valid input in this field.
lists in the spreadsheet program can extend to 128 characters.
In Run mode when any key on the list is pressed, the condition will be true and (if
this is the only condition) will initiate a trigger action.
An example of a keyboard condition is the following:
CONDITIONS: KEYBOARD "1 •
Note the space following the 1 entry. Here the ITl key or the space bar will satisfy the
trigger condition. Dual quotation marks are required for all lists and strings on the
Protocol Spreadsheet.
31-4
SEP'95
31 Laver-lndeR'endent Conditions and Actions
(0) Buffer Full
This condition is true at the moment the 64-Kbyte character buffer is full. Use this
condition to trigger a display-freeze (CAPTURE BOTH OFF) whenever the earliest data
in the display buffer is the most important and you do not want it to be overwritten.
Here is an example of a trigger that will retain the first full buffer of data:
CONomONS: BUFFER FULL
AcnONS: CAPTURE BOTH OFF
(E) Counter
Any counter named and operated as a trigger action may be monitored as a trigger
condition. To create a counter condition, press the COUNTER softkey or type COUNTER
followed by a space.
NOTE: A counter named on a Trigger Menu screen also refers to a
spreadsheet counter as long as the name matches. Timeouts and timers can
also be shared between the Trigger Menu screens and the spreadsheet.
NOTE ALSO: mgger Setup screens monitor counter values from 0
to 999,999. However, Protocol Spreadsheet triggers can monitor
counter values up to 4,294,967,295.
The following is an example of a spreadsheet counter condition:
CONomONS: COUNTER byte_no EO 128
where byte_no is the name, EO(ual) is the relational operator, and 128 is the decimal
value.
1.
Enter counter name. Name the counter to be monitored. See Section 31.1,
Naming Requirements.
2.
Relationaloperator. As soon as a counter name has been typed and followed by a
space, a rack of softkeys appears with names of relational operators. See
Figure 31-2.
Figure 31-2 A set of relational operators compares the counter value to a user-entered
value.
SEP'95
31-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Make the appropriate selection to specify when the counter condition will be
true. The counter may be tested for a value equal to (EQ), not equal to (NE),
greater than or equal to (GE), less than or equal to (LE), strictly greater than (GT),
or strictly less than (LT) the value entered on the spreadsheet.
When a COUNTER condition is used alone, it is a transitional condition. This
means that it is true only when it transitions to true. For example, a condition
that said COUNTER drops NE 5 would be true when COUNTER drops transitioned from
5 to 6-that is, on the transition from equal 5 to not equal 5; but the condition
would not be true when 6 changed to 7.
In combination with another condition (that is, more than one conditionper
action or set of actions), a COUNTER condition normally is a status condition, not a
transitional condition. As a status condition, COUNTER drops NE 5 is true any time
the status of the counter is not 5. Refer to Section 31.2, Rules for Combining
Conditions.
NOTE: Additional rules may apply when the COUNTER
transitional/status condition is used in a spreadsheet program
compiled and saved as a linkable-object file. See Section 28.4(B).
3.
Enter the counter value. Enter the value as a whole decimal number. Each
condition can monitor a 32-bit counter for decimal values ranging from 0 to
4,294,967,295.
NOTE: The Current value for a counter on the Tabular Statistics screen is
maintained to seven decimal places, for a maximum counter display of
9,999,999. The 32-bit binary counter can attain much higher values than this,
however-the decimal display on the statistics screen merely rolls over to zero
and continues counting. Spreadsheet counter conditions can monitor for
values up to the maximum of over four billion. If a trigger looks for a counter
value higher than this maximum, it will never be satisfied.
(F) Time
The time of day once a day or once a month can satisfy a trigger condition. Here, for
example, is a trigger condition that comes true at 3 P.M. each day:
CONDITIONS: TIME 1500
1.
Enter day ofmonth or time of day. Press the TIME softkey or type TIME followed by
a space. The next entry will signify day of month if it is a two-digit entry. If it is
four digits, it will signify the time of day in twenty-four hour format.
2. Enter time of day. If the entry following TIME is a two-digit, day-of-month
entry, it must be followed by time of day in a four-digit, twenty-four hour
format.
31-6
SEP '95
31 Layer-Independent Conditions and Actions
(G) Flag
Sixteen internal flag bits are reserved for every flag mask that is named in Protocol
Spreadsheet conditions and actions.
NOTE: The eight flag bits on the 1Hgger Setup screens are the low-order
bits of a flag mask that can be accessed on the Protocol Spreadsheet by the
name trig_ftag.
A flag condition still is valid when fewer than sixteen flag bits are specified. The flag
values that are specified are right-justified when the program is compiled, and
leading X's (don't cares) are assumed.
The internal flag normally is a static condition when it is used in combination with
other trigger conditions-that is, more than one condition per action or set of
actions. Refer to Section 31.2, Rules for Combining Conditions. Since flag bits are
completely under program control and can be used in combination with other
conditions, they are useful chiefly to enable or disable entire triggers.
NOTE: Additional rules may apply when the FLAG transitional/status
condition is used in a spreadsheet program compiled and saved as a
linkable-object file. See Section 28.4(B).
For example, a trigger action is taken if a flag bit is 1 and a "k character is seen.
Setting the flag to zero effectively disables this trigger.
The following is an example of a flag condition:
CONDITIONS: FLAG nak 1X
where nak is the name of the flag and XXXXXXXXXXXXXX1 X is the flag bit mask.
SEP '95
31-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
1.
Enter the flag name. After pressing the FLAG softkey or typing FLAG followed by
space, enter a name not exceeding eight characters, beginning with an alpha
character.
2. Enter the flag condition bit mask A flag mask follows the flag name. The mask
can include up to sixteen bits (with no spaces between them). Since the number
of flag masks in your program is unlimited, you may want to restrict your masks
to one or two bits. In effect you will be giving each bit or pair of bits a name.
Legal bit-entries are 1,0, or X (for "don't care"). Press IRl or ~ to enter an X.
The condition will not test this bit.
(H) On Signal
Signals are communicated between tests and between layers. They are the simplest
way to use an event in one test to start a state or an action in another test. Here is an
example of an on-signal condition:
After pushing the ONSIGNL softkey or typing ON_SIGNAL followed by space, enter the
name of a signal you have created (or intend to create) in a trigger action.
31.4 Layer-Independent Actions
When a block of conditions has been entered, press ~ to access the ACTIONS softkey. The
actions that are available in all states without exception are shown in Figure 31·3 as they
appear in three successive racks of softkeys.
(A) Counter
The Protocol Spreadsheet screen can control any number of counters. The Thbular
Statistics screen is an expanding display that can provide statistics for 100 counters,
timers, and accumulators.
Here is an example of a counter action:
ACTIONS: COUNTER datapaks INC
1.
31-8
Enter counter name. A counter can be unique to one trigger action or it may be
shared with other actions and other triggers, which can monitor it and change its
values. As long as the same counter name is used, the same counter is invoked.
SEP'95
31 Layer-Independent Conditions and Actions
Figure 31-3 The twelve layer-independent actiousarespreadover the bottom three racks of
softkeys in this fJ.gUre.
NOTE: A counter named on a Trigger Menu screen also refers to a
spreadsheet counter as long as the name matches. Timeouts and timers can
also be shared between the Trigger Menu screens and the spreadsheet.
NOTE ALSO: Trigger Setup screens monitor counter values from 0
to 999,999. However. Protocol Spreadsheet triggers can monitor
counter values up to 4,294,967,295.
After naming the counter, select among the actions shown in the rack of softkeys
in Figure 31-4.
Figure 314 Counter actions.
2.
SEP'95
Increment. Thirty-two bits are reserved for each counter. Therefore a counter
will roll over after it attains a decimal value of 4,294,967,295. Spreadsheet
31-9
INTERVIEW 8000 Series Basic Operation: 951-80424-01
conditions can monitor a counter for any value from zero to the maximum.
(Trigger Menu conditions can monitor up to a count of 999,999.) Note, however,
that the counter value will only be displayed up to seven decimal places on the
Tabular Statistics screen. The maximum displayed value therefore is 9,999,999.
3. Decrement. When tbis action is selected, each trigger occurrence subtracts 1 from
the counter. A counter that decrements below zero wraps to 4,294,967,295. The
last seven decimal places of this maximum value will be displayed in the Current
column on the Tabular Statistics screen.
4.
Set. Select seT in order to specifY the value that the counter will take when the
trigger comes true. Enter a decimal value for the counter. To reset a counter
without taking a statistical sample, use the seT action and enter a value of zero.
5.
Sample. This action stores the current value of tbe counter and then resets it to
zero. The stored value is posted immediately to the statistics display in the Last
column. This value is compared with previous Last values in order to compute
Minimum, Maximum, and Average values for statistical display. Refer to Section 21
for a discussion of tabular statistics.
6.
Clear. This action resets the counter to zero and also resets last, minimum,
maximum, and average values for the counter.
(8) Timer
The Protocol Spreadsheet can control any number of timers. The Tabular Statistics
screen is an expanding display that can provide statistics for 100 counters, timers, and
accumulators.
While timers can be run and sampled as trigger actions, they are not available as
trigger conditions. Timeouts, not timers, are the mechanism that allows you to
trigger off of elapsed time.
Timer values may be based on an internal "wall" clock, or, if time ticks are enabled
on the Front- End Buffer menu screen, on ticks that are stored along with the data.
The «tick" mode of timing is the most accurate. especially when data is played back
and you do not want playback conditions such as speed and idle-suppression to
affect the timers.
Here is an example of a timer action:
ACTIONS: TIMER session SAMPLE
1.
Enter timer name. After pressing the TIMER softkey or typing TIMER followed by a
space, enter a name. Like counters and timeouts, a timer can be shared between
the spreadsheet program and the Trigger Menu screens. If the same name is
used, the same timer is invoked.
31-10
SEP '95
,~
31 Laver-Independent Conditions and Actions
After naming a timer, select among the actions shown on softkeys in Figure 31-5.
FJgUre 31-5 Timer actions.
2. Restart. Use RESTART to start a timer. This causes the timer to reset to zero and
begin incrementing. A restart does not affect any statistical values except Current.
3. Stop. A stop action suspends the timer at its present value. The timer may be
started again at this value by a Continue action on another trigger.
4.
Continue. This action restarts the timer beginning at the value that was frozen in
the Current column when the timer was stopped. The Continue action has no
effect on a timer that is incrementing already.
5.
Sample. Sampling a timer resets it at zero and stops it. Prior to resetting, the
current value is posted as a La$!: value and passed along for other statistical
tabulation.
6.
Clear. Clearing a timer resets and stops the timer and clears the last, minimum,
maximum, and average values.
(C) Timeout
Any number of timeouts can be started and stopped in the spreadsheet program.
Timeouts are timers that count down instead of up. Their values are not read on any
statistical display; but when they time down to zero, they satisfy trigger conditions
that monitor them by name. Timeout timers that are named on the Protocol
Spreadsheet also may be monitored and controlled on the Trigger Menu screens.
Here is an example of a timeout action:
ACTIONS: TIMEOUT t2 RESTART 3
where t2 is the name of the timeout and 3 is its duration in seconds.
1. Enter timeout name. After pressing the TIMEOUT softkey or typing TIMEOUT
followed by space, enter the name of the timeout. As soon as a name has been
entered and followed by a space, a rack of softkeys appears with the names of two
timeout actions, RESTART and STOP.
2. Restart. Select RESTART to start the timer running down.
3.
SEP'95
Stop. Select STOP to halt the timer and prevent the timeout.
31-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
4. Enter timeout value. The duration of the timeout is entered in seconds. The
timeout value is a decimal field in which entries are valid to the millisecond
(0.001). For values under 1 second, you must precede the decimal with a leading
zero, as follows:
TIMEOUT delay RESTART 0.25
The maximum timeout entry in this field is 65.535 seconds.
You may expand the maximum timeout with a program such as the following,
which produces an alarm every twenty minutes.
STATE: twenty_min_alarm
CONDITIONS: ENTER STATE
ACTIONS: TIMEOUT siXtysec RESTART 60
CONDITIONS: TIMEOUT slxt.ysec
ACTIONS: COUNTER minutes INC
TIMEOUT sixtysec RESTART 60
CONDITIONS: COUNTER minutes EO 20
ACTIONS: COUNTER minutes SET 0
ALARM
(0) Prompt
Prompts are user-entered ASCII messages that appear on the second status line at
the top of the screen in Run mode as a result of a trigger coming true. They are
messages to operators, from the program, alerting them to important protocol or
program events. Prompts are written to the second status line of any current
Run -mode display screen. Switching to Freeze mode or to another display screen
clears the prompt from aU screens except the Display Window.
NOTE: The prompt line is not zeroed out with each new prompt, and
prompts are overwritten only to the extent of the new prompt. For example,
the prompt "POLe' does not completely overwrite the prompt
"SELECT"-the result will be "POLLCT." It is a good practice to establish a
uniform prompt length and space-fill shorter prompts to that length.
SpeciaJ C functions that position the cursor anywhere on the prompt line (or
elsewhere in the display) and write messages to the cursor position are
discussed in Section 60.
A prompt that has been triggered in Run mode is illustrated in Figure 31-6. Here is
the same prompt as it appears on the Protocol Spreadsheet:
ACTIONS: PROMPT "Echoed message received"
Backslashes and double-quotation marks may be included in prompt messages if
they are preceded by backslashes, in accordance with the rules for entering these
characters in transmit strings. See Table 33-2. Example:
ACTIONS: PROMPT" \" hello\" string received"
31-12
SEP '95
31 Layer-Independent Conditions and Actions
1. Enter prompt message. After pressing the PROMPT softkeyor typing PROMPT
followed by a space, enter a message in quotation marks. The message should
not exceed 64 characters, the width of the screen.
prompt line
Figure 31·6 User-defined prompts are displayed at the top of the Run screen.
(E) Alarm
The alarm is a tone of less than a second duration. The alarm is sounded each time
the trigger comes true. If the tone lasts longer than a second, the alarm has been
triggered more than once.
The alarm action on the spreadsheet is simply the word AlARM.
(F) Flag
Internal flags are special programming bits. They can be set on or off by triggers and
sensed by triggers. Flags come in masks of up to sixteen bits. Each flag mask is
named and referenced by the spreadsheet program.
Any number of flag masks may be created. Flags are common to all tests and layers:
if a flag name is used in tests in two different layers, it refers to the same sixteen
programming bits.
A flag action still is valid when fewer than sixteen flag bits are specified. The flag
values that are specified are right-justified when program is compiled, and leading
X's (don't cares) are assumed.
NOTE: The eight flag bits on the Trigger Setup screens are the low-order
bits of a flag mask that can be accessed on the Protocol Spreadsheet by the
name trig_flag.
Here is an example of a flag action:
ACTIONS: FlAG nak SET
ox
where nak is the name of the flag, SET is the action, and 0 is the only bit in the mask
affected by the set action.
SEP'95
31-13
INTERVIEW 8000 Series Basic Operation: 951-80424-01
1. Enter the flag name. After pressing the softkey for FLAG. or typing FLAG followed
by a space, a rack of softkeys appears with the names of flag actions. See
Figure 31-7.
Y&gnre 31·7 Flag actions.
2. Increment. The mask can be used as a 16-bit binary counter. The INC action
increases the value of the mask by one each time the trigger is true.
As the mask increments above 65,535, it wraps to zero.
The INC action always toggles the least significant flag bit. If you monitor the flag
for only one bit (for example, FLAG flagname 1), the INC action will toggle the
condition truelfalse. This can be a useful tool when you want every second
occurrence of an event to trigger an action.
3. Decrement. This action decreases the value of the flag byte by one each time the
trigger is true. When the mask decrements below zero, it wraps to 65,535.
4. Set. This action rewrites the flag bits according to the flag-action bit mask that
you enter following the SET keyword. The bit mask is comprised of up to sixteen
O's, l's, and X's (no change).
When you enter fewer than 16 bits, you are leaving the leftmost bits in the mask
unspecified. The action will not change the condition of unspecified bits.
(G) Signal
Use signals to convey instructions to other tests and other layers where conditions are
monitoring these signals by name.
Other internal programming mechanisms, such as flags and counters, are common to
all tests and layers and may perform a signalling function. Signals, however, are more
efficient in that they are reusable: a signal that is sent and monitored can be sent and
monitored again ten seconds later, but an action that sets a flag to 1 cannot be used
again until another action has intervened to reset the flag to zero.
After pressing the SIGNAL softkey or typing SIGNAl followed by space, enter the name
of the signal. Often the name will be descriptive of the event being signalled. The
following is an example of a signal action:
ACTIONS: SIGNAl testfail
31-14
SEP '95
31 Laver-Independent Conditions and Actions
(H) Accumulate
The accumulate action reads a specified value for a counter or timer and presents this
value to tabular and graphic statistics screens for statistical breakout This action is
distinct from the sampling action of a counter or timer in this important respect:
sampling a counter or timer also resets it to zero. Accumulating a counter or timer
has no effect on the ongoing counting or timing function. Examples of accumulators
are given in Section 21, Tabular Statistics.
Values for more than one counter or timer may be brought into a single accumulator.
For example, separate timers might measure response times for a group of
multidropped OTEs. At th.e end of the test, a value for each timer could be brought,
in separate trigger actions, into one accumulator.
Each accumulate action specifies one value only for a counter or timer. Thus, the
accumulator might provide meaningful statistical data based, for example, on
maximum values only for a group of timers.
Here is an example of an accumulate action:
ACTIONS: ACCUMULATE alldrop COUNTER baclbcc_a LAST
where alldrop is the name of the accumulator, badbCc_G is the name of a counter, and it
is the last value of the counter that is being accumulated.
1.
Enter the accumulator name. Both the accumulator and one counter or timer are
referenced in the accumulate action. Counters and timers are referenced, not
created, in accumulate actions.
An accumulator is created by being named in an accumulate action. Like
counters and timers, accumulators can be given display lines on either or both of
the statistics screens.
2.
Clear. This action clears the last, minimum, maximum. and average values of the
accumulator. (Since accumulators neither count nor time, they never display a
current value.)
3. Counter. This action accumulates a value for the counter named immediately
following the keyword COUNTER. After the counter is named, one value for that
counter is selected from the rack of softkeys in Figure 31-8.
4.
Tuner. This action accumulates a value for the timer named immediately
following the keyword TIMER. After the timer is named, one value for that timer
is selected from the rack of softkeys in Figure 31-8.
31-15
SEP'95
~
~--~
---_._-_.
__ _._----..
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Figure 31-8 Counters and timers are accumulated with respect to one
statistical value only.
(I) Print
Time-stamped printouts of single lines of data can be commanded by the
spreadsheet program. The data can be a line of tabular statistics for an accumulator,
counter, or timer; or a user-prompt that is sent to the printer after it has been
written to the second line of the screen.
The following is an example of a print action:
ACTIONS: PRINT TIMER echotime MIWSECONDS
Mer pressing the softkey for PRINT or typing PRINT followed by a space, select an
option for the type of data to be printed from the new rack of softkeys shown in
Figure 31-9.
Figure 31-9 Four types of data may be printed out as a trigger action.
1. Accumulator. When this action is taken, the line of tabular statistics for the
accumulator that you name will be printed. A line of tabular statistics includes
last, minimum, maximum, and average values for an accumulator. Since
accumulators neither count nor time, they never display a current value.
2.
Counter. When this action is taken, the line of tabular statistics for the counter
that you name will be printed. A line of tabular statistics includes current, last,
minimum, maximum, and average values for a counter.
3.
Timer. After the timer is named, a timer rate is selected from a new rack of
softkeys as shown in Figure 31-10.
Figure 31·10 After a timer is named for printout display, a new softkey rack allows you to
specify unit of time.
31-16
SEP '95
31 Layer-Independent Conditions and Actions
The selected rate will only display values to the smallest place value afforded by
the tick rate selected on the FEB Setup screen. For example, if milliseconds is
selected on the FEB screen, choosing microseconds on the print-timer softkey
selection will simply display three additional zeros as place holders-it will not
calculate a more precise reading. Thus, the most accurate selection for this
example would be milliseconds, matching the FEB selection.
When a timer is controlled by a nondata event such as a keyboard condition, it
will reference a ''wall-time'' clock whose smallest resolution is a millisecond.
When the PRINT TIMER action is taken, the line of tabular statistics for the timer
that you name will be printed. A line of tabular statistics includes current, last,
minimum, maximum, and average values for a timer. Figure 31-11 is an example
of such a printout for the program given below.
STATE: message
CONDITIONS: OTE STRING 'hello~
ACTIONS: PROMPT "String sent by DTE"
TIMER echotime RESTART
NEXT STATE: echo
STATE:
CONDmONS: DeE STRING "hello"
ACTIONS: PROMPT "Same string by OCEw
TIMER echotime STOP
TIMER echotime SAMPLE
PRINT TIMER echotime MILUSECONOS
NEXT_STATE: message
ecoo
o
o
Time
o
o
Name
Current Last Minimum Maximum Average Unit
09/29 16: 13 echotime
09/29 16: 13 echotime
09129 16: 13 echotime
o
o
o
452
452
341
428
341
341
452
452
452
452.00 MSECS
396.50 MSECS
407.00 MSECS
o
o
o
o
o
o
o
o
Figure 31·11 In this printout, a PRINT TIMER action has been triggered three times.
SEP '95
31-17
INTERVIEW 8000 Series Basic Operation: 951-80424-01
4. Prompt. The PRINT PROMPT action is designed to be added to an action block that
already contains a prompt The example below inserts PRINT PROMPT actions into
the program described in the previous section. The user does not have to key in
a long prompt message twice, once for the printout and once for the screen. The
printout for this program is shown in Figure 31-12.
STATE: message
CONDITIONS: DTE STRING "hello'
ACTIONS: PROMPT 'String sent by DTE"
PRINT PROMPT
TIMER echotime RESTART
NEXT STATE: echo
STATE: echo
CONDITIONS: DCE STRING "hello"
ACTIONS: PROMPT "Same string by DCE"
TIMER echotime STOP
PRINT PROMPT
TIMER echotime SAMPLE
PRlNTTIMER echotime MILUSECONDS
NEXT_STATE: message
o
o
Time
o
o
o
o
Name
Current
Last Minimum Maximum Average Unit
09129 16: 13 String sent by DTE
09129 16: 13 Same string by DCE
0 452
09129 16: 13 echotime
09/2916:13 String sent by DTE
09129 16: 13 Same string by DCE
0912916:13 echotime
0 341
09129 16: 13 String sent by DTE
09/29 16: 13 Same string by DCE
09/29 16: 13 echotime
0 428
o
452
452
452.00 MSECS
o
341
452
396.50 MSECS
o
341
452
407.00 MSECS
o
o
o
Figure 31-12 Printout resulting from a combination of PRINT PROMPT and PRINT TIMER
actions.
NOTE: If you want to print multiple prompts, place each PROMPT and PRINT
PROMPT pair in its own conditions/actions block. (Otherwise, only one prompt
will be printed since prompts overwrite each other.)
(J) Trace
Traces are user-entered ASCII data strings, identical to prompts in all ways except in
their mode of display: traces are posted one to a line in the multiline Program Trace
display (see Section 6.6), while prompts appear on the second status line in all
data -display modes (including the Program Trace).
31-18
SEP '95
31 Laver-Independent Conditions and Actions
Numerous layers and numerous tests per layer can be active concurrently in the
INTERVIEW. The Program Trace can be set up to track state-to-state movement
only in a particular Layer and Test identified by the operator on the Display Setup
menu, State names can be included in the Program lIace via the Display States:
selection on the the Display Setup menu. See Figure 31-13.
Fagure31-13 The user may select a particular layer and test for a Program Trace.
Traces are debugging tools. Inside a dead-end state they can inform you whether a
particular condition that you are expecting is coming true. Prompts, by contrast, have
a much fainter "trail": it is hard to be certain that a prompt was not activated and
then overwritten by another prompt.
Traces also allow you to keep a record of selected protocol events-to design your
own protocol analysis. Since they are written to consecutive lines rather than
overwritten by other traces, they are highly useful when you are trying to track
protocol events that occur in quick succession.
The following is an example of a trace action:
ACTIONS: TRACE" Network congestion"
1.
Enter trace message. After pressing the TRACE softkey or typing TRACE followed by
a space, enter a message in quotation marks.
(I<)
load Program
A program (source code or object code) or setup that is stored in a file on hard disk
or on a disk in either of the microfloppy drives can be loaded in by trigger action.
This Load Program function is a means of chaining tests together.
Program files are a full set of configured menus, including the Layer Setup screen,
Trigger Setup screens, and the Protocol Spreadsheet. Object files are the precompiled
object-code versions of programs. Setup files are a set of configured menus which
excludes trigger setups, the Layer Setup screen, and the spreadsheet. Remember that
loading a program or setup file overwrites the program or setup file already in
memory. Loading an object file overwrites only the object code of whatever program
(if any) was compiled most recently. The new object file will not affect the data on
any setup menu or programming screen.
EIA statuses can be maintained in between programs by a special menu selection on
the Interface Control menu screen. (See Section 12.)
31-19
SEP'95
-----------------------
-----
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
The following is an example of a Load Program action:
ACTIONS: LOAD_PROGRAM AFD1!usrlsna/sna_bind"
where FDl is microfloppy-diskette drive 1, the first slash (I) is the root directory, usr
is the highest level of user-created files, sna is another directory, and sna _bind is the
filename.
1.
Enter program name. Enter the absolute pathname of your file. Put the name in
quotation marks.
(l) Record
Use the RECORD action to activate or suspend line-data recording or disk-data
playback. When the Line Setup menu is configured to monitor a disk, RECORD
controls playback; otherwise it applies to recording. There are two selections under
RECORD. Select ON to activate, or OFF to suspend, recording or playback.
During recording, the top status line of Run - mode screens will show incrementing
block numbers and an "R" displayed in the record/playback field. During playback, a
"P" is displayed. Whenever recording or playback has been suspended, an "S" is
displayed.
For data playback, the status field will be blank if a disk is not present in the selected
drive or when the end of the data - acquisition tracks are reached. This field will also
be blank if you enter a starting block number on the Line Setup menu that a)
precedes the block number at which data actually begins, or b) exceeds the block
number at which data actually ends. Change your entry to zero.
For data recording, the status field will be blank when the end of RAM or the
data -acquisition tracks is reached. It will also be blank if the Capture Memory field
indicates that you will record to disk, but no disk is present in the selected drive or
data-acquisition tracks are not available on the disk.
31-20
SEP '95
32 Layer 1 Conditions and Actions
32 Layer 1 Conditio,ns and Actions
There are seven protocol layers in the OSI (Open Systems Interconnect) model that is adopted in
the INTERVIEW 8000 Series. Each layer reserves a distinctive set of trigger conditions and actions
on the Protocol Spreadsheet.
As a rule, spreadsheet components for a given layer are loaded from disk via the Layer Setup
screen. Layer 1, the Physical Layer, is an exception to this rule. Layer 1 conditions and actions are
enabled on the Protocol Spreadsheet when the unit powers up.
Depending on the Test Interface Module (TIM) installed in the unit, the power-up also enables an
Interface Control Menu screen, different for each module, that controls many Layer 1 parameters.
For this reason, the set of Layer 1 conditions and actions is relatively small. For units equipped
with a dual-port TIM, the selections are slightly different from units using a single-port TIM.
32.1
Single- Port Layer 1 Conditions
To bring up the bank of softkey conditions for Layer 1 using a single-port TIM, first press
the CONDITIONS softkey. This key becomes available when the cursor enters a
programming block at the state level.
The first four condition softkeys-DTE, DeE, RECEIVE, and ElA--belong to Layer 1. These
are followed by generic conditions discussed in Section 31. The set of Layer 1 conditions
is shown in Figure 32-1. The softkey for a fifth Layer 1 condition-XMIT_COMPLETEappears on the second rack of condition softkeys shown at the bottom of the figure.
EtA is a transitional/status condition and may be combined with other conditions. The
other Layer 1 conditions are transitional only. Refer to Section 31.2 for a discussion of
how conditions may be combined.
32-1
SEP '95
--=-__.__. . . .
........
IlIIiI_._~_
._iI!'2__
:oHL ...
' ........
' ___
lIae~1Il
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 32·1 Layer 1 conditions.
(A) Data
The first three trigger conditions at Layer 1 are valid when using a single-port TIM
and for Port 1 when using a dual-port TIM (Port 2 is discussed in Section 32.2).
They can monitor one of the two data leads for a specific data event. This event can
be any of several characters, a string of characters, a good BCC following the
character or string, an error revealed by a block or parity check, and so on.
Data conditions at Layer 1 monitor the entire data stream (for Port 1 when using a
dual-port TIM). Conditions in other layers also check the data leads, of course, but
conditions at Layer 2 and higher look for protocol events.
In searching the data stream byte by byte, Layer 1 data conditions behave similarly to
Receiver conditions on the Trigger Setup screens. This is another way of saying that
the 16 trigger menus constitute a Layer 1 test. This test has a single state that is
always current. Trigger menus with selections made on them are always active.
The three data conditions are DTE, DCE, and RECEIVE (for Port 1 when using a
dual-port TIM). When one of these conditions is selected, a new rack of softkeys
appears. The new options are shown in Figure 32-2.
32-2
SEP '95
32 Layer 1 Conditions and Actions
Figure 32-2 A spreadsheet trigger will monitor either data lead looking for these events.
(8) DTE
When DTE is selected, data on the 1D lead will be monitored (on the main port when
using a dual-port TIM).
(C) DeE
This condition monitors the RD lead (on the main port when using a dual-port
TIM).
(D) Receive
This condition is intended for use in the emulate modes. It allows you to change the
emulate mode of a program on the Line Setup screen without modifying the
spreadsheet. When RECEIVE is selected, the INTERVIEW will always monitor the
lead opposite its own transmit lead (on the main port when using a dual-port TIM).
With Mode: llif.IlliJlIII as the Line Setup selection, the trigger will monitor RD. In
Emulate DCE mode, the trigger will monitor ID.
(E) String
When a trigger monitors a data lead for a string, it searches for the exact, entire
sequence of characters entered in the condition. Strings have a size limit of 32
characters. If constants are entered in the string, the 32-character limit is applied
after all constants have been expanded.
After pressing the STRING softkey or typing STRING followed by a space, begin the
string. Strings are always enclosed in quotation marks on the spreadsheet.
Here is an example of a Layer 1 data condition:
CONDITIONS: RECEIVE STRING
.~ %Rff
WArr_EOF
where WAIT_EOF delays trigger-true until the block of data holding the string has
ended with a good block check.
(F) One-Of Character
When ONE_OF is entered, the trigger looks for anyone of the characters in the list that
follows. A single character in the data is all that is necessary to match a list. The
effect of a "not-equal" character in a one-of list is explained in Section 25.3(1).
SEP'95
32-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
After pressing the ONE_OF softkey or typing ONE_OF followed by a space, begin the list.
Lists and strings are always enclosed in quotation marks.
(G) Good or Bad Bee
BCC is partly a Layer 1 function, in that the calculation normally is a "hardware"
function that tests the physical medium. It also is a Layer 2 function, in that the
frame-check calculation is transmitted as part of the Layer 2 protocol. BCC,
therefore, appears as a set of spreadsheet functions both at Layer 1 and Layer 2.
GOOD_BCC (good block-check calculation) and BAD_BCC can only be used as
conditions when Rev Blk Chk is turned on. Rev Blk Chk is a menu field on the Line
Setup menu: see Section 5.
NOTE: Rev Blk Chk is on automatically when Format: W'il;~~tli.\ is the Line
Setup selection.
Press the softkey for GOODBCC or BAD_BCC when you want the trigger to take action
on receipt of the BCC. The INTERVIEW does the block-check calculation that the
user has defmed on the BCC Parameters menu and compares it with the received
block-check characters. See Table 10-1 and Table 10-2 for the block-check
calculations done by the INTERVIEW.
(H) Parity Error
PARITY_ERROR looks for an error in relation to the Parity selection made on the Line
Setup menu.
(I) Framing Error
FRAMING_ERROR applies to start-stop formats (ASYNC and ISOC) and detects
framing errors in relation to the Stop Bits field on the Line Setup menu.
(J) Abort
When Format:
has been selected on the Line Setup menu, you can enter ABORT
as a trigger condition. In 7£ -framed protocols, seven consecutive I-bits in midframe
constitute an abort.
(K) Enter Receive String
Enter strings and lists inside quotation marks. A list is a series of characters that can
be matched by a single data character. (A string must be matched by a data string.)
A one-of condition is an example of a list. All ASCII - keyboard, control, and
hexadecimal characters are legal in a receive string or list. Of the special-character
keys, t&I. (§J, §), and 8-~ are valid. 8-§l displays the sync symbol 12 on
the screen, and causes a search for the sync pattern.
32-4
SEP '95
32 Layer 1 Conditions and Actions
~
is not valid. Bit masks are entered in receive strings by the keying sequence
illustrated in Table 33-1.
Constants are also legal in any character position in a list or string. See Section 33,
Strings, for an explanation of these string-search tools.
(L) Walt for End Of Frame
After the double-quotation mark is entered to close a string or list, the final Layer 1
condition appears under lEJ on the rack of softkeys. The condition is WAIT_EOF, or
"wait for the end of the frame" before coming true and taking any actions. See
Figure 32-3.
Figure 32-3 String and one-of conditions can be linked to a good BCC at the end of the frame
("EOF").
The WAIT_EOF condition does not occur above Layer 1, since data is not passed up to
those layers until the frame is completed.
(M)EIA
Layer 1 conditions can monitor the status of six RS- 232N.24, V.35, or RS-449
control leads plus an additional seventh lead, the user-assigned (UA) input jack on
the RS-232fV,.24, Y.35, or RS-449 test-interface module (TIM). Leads available
for triggering are RTS, CTS, CD, DTR, DSR, and RI.
The EtA condition is a transitional/status condition. This means that when it is used
alone it is true only if it transitions to true; but used in a trigger in combination with
other conditions, it retains its status of on or off without having to transition to either
status. The rules for combining conditions are explained in Section 31.2.
After pressing the EIA softkey or typing EtA followed by a space, make your lead
selection from the upper rack of softkeys in Figure 32-4. Then select a status of ON or
OFF.
SEP'95
32-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Figure 324 EIA leads monitored by the spreadsheet program.
For the standard RS- 232(Y.24 interface, ON implies that a lead is more positive than
+3 volts with respect to signal ground. OFF implies only that a lead is not at or above
the ON threshold, not necessarily that a minus threshold has been attained.
This is an example of an EIA condition:
CONDITIONS: EIA DTR OFF
(N) Xmit Complete
"sENDing" a transmission means queueing a transmission to send. The layer protocol
(the RTS-CTS handshake, for example, at Layer 1) may delay the actual
transmission. The XMIT_COMPLETE condition (selectable in the bottom rack of softkeys
in Figure 32-1) will not come true until the transmission actually has been sent. Use
this condition to start accurate response-time measurements.
32.2 Dual- Port Layer 1 Conditions
To bring up the bank of softkey conditions when using a dual- port TIM at Layer 1, first
press the CONDITIONS softkey. This key becomes available when the cursor enters a
programming block at the state level.
The first three condition softkeys-DTE, DCE, and RECEIVE-belong to Layer 1 for the main
port. These are followed by generic conditions discussed in Section 31. The set of
dual-port Layer 1 conditions is shown in Figure 32-1. The softkey for a fifth Layer 1
condition-XMIT_COMPLETE-appears on the second rack of condition softkeys shown at
the bottom of the figure. The last three condition softkeys-DTE2. OCE2. and RECV2-belong
to Layer 1 for the secondary port.
The Layer 1 conditions are transitional only. Refer to Section 31.2 for a discussion of how
conditions may be combined.
AU of the conditions except for the three secondary port condition softkeys are explained
in Section 32.1; the secondary port softkeys are explained in the following subsections.
32-6
SEP '95
32 Layer 1 Conditions and Actions
Figure 32-5 Dual-port Layer 1 conditions.
(A) Data
The first three and the last three trigger conditions at Layer 1 can monitor one of the
two data leads for a specific data event; the first three are for the main port and the
last three are for the secondary port. This event can be any of several characters, a
string of characters, a good BCC following the character or string. an error revealed
by a block or parity check, and so on.
Data conditions at Layer 1 monitor the entire data stream. Conditions in other
layers also check the data leads, of course, but conditions at Layer 2 and higher look
for protocol events.
In searching the data stream byte by byte, Layer 1 data conditions behave similarly to
Receiver conditions on the Trigger Setup screens. This is another way of saying that
the 16 trigger menus constitute a Layer 1 test. This test has a single state that is
always current. Trigger menus with selections made on them are always active.
The three data conditions for the main port are DTE, DCE, and RECEIVE; these are
explained in Section 32.1. The three data conditions for the secondary port are DTE2,
DCE2, and RECV2. When one of these conditions is selected, a new rack of softkeys
appears. The new options are shown in Figure 32-6. See Section 32.1 for
information on these options.
SEP'95
32-7
-----.--.-.---..
---.--~--------
. . ."-......- - . - - - " _ _ _ _ _ _ _ _ _
~_"'~T
!B_iJIMI_......._ _.......
._._1IIIi~_1!i'
_'U!~
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 32-6 A spreadsheet trigger will monitor either data lead on the secondary port looking for these events.
(8) DTE2
When DTE2 is selected, data on the secondary port TO lead will be monitored.
(C) DCE2
This condition monitors the RD lead on the secondary port.
(D) Receive2
This Receive condition on the secondary port is intended for use in the emulate
modes. It allows you to change the emulate mode of a program on the Line Setup
screen without modifying the spreadsheet. When RECV2 is selected, the INTERVIEW
will always monitor the lead opposite its own transmit lead on the secondary port.
With Mode: \W!~~~l§~t~; as the Line Setup selection, the trigger will monitor RD on
the secondary port. In Emulate DeE mode, the trigger will monitor TO on the
secondary port.
32.3 Single - Port Layer 1 Actions
When a block of Layer 1 conditions has been entered, press 8
to access the softkeys for
ACTIONS. The set of seven Layer 1 actions is shown in the softkeys in Figure 32-7. The
names of these actions are SEND, EIA, OUT_SYNC, IDLE_UNE, ENHANCE, and CAPTURE. The
other, darkened softkeys in the figure are layer-independent actions present at every
layer, discussed in the previous section of this manual.
32-8
SEP '95
32 Layer 1 Conditions and Actions
Fwgure32-7 Layer 1 actions.
(A) Send
There is one SEND action-transmit a string-for single-port TIMs (or the main port
on a dual-port TIM). While transmissions occur at all layers, only Layer 1 allows the
user to type in a complete transmission, character by character. At higher layers, the
user types the names of protocol elements and the software converts these
mnemonics to strings. The user enters character strings directly at higher layers only
into specified user-data fields.
The spreadsheet compiler identifies strings by the quotation marks surrounding them.
Send-strings have no size limit (for practical purposes). All ASCII - keyboard,
control, and hexadecimal characters are legal in a send-string. Special keys (~,
rml,~) are not legal.
SEP'95
32-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
To insert a canned fox .message into a transmit string, type FOX inside double parens,
as follows: ((FOx»). Remember that the double parens are special characters produced
by the ~-@ and ~-I!l combinations. Constants, counters, and flags can also be
embedded in a string. See Section 33, Strings.
Press the SEND softkey or type SEND followed by space to begin the entry. The prompt
appears as in Figure 32-8. Enter the string inside quotation
marks.
Enter Transmit String
Figure 32-8 Transmit a string.
After quotation marks are typed in to close the transmit string, a set of softkeys
appears for the error-checking value that will be appended to the transmit string.
One of these must be selected; otherwise, the program will not compile and a
Premature End of File error message is generated.
Figure 32·9 Select a block - check calculation to end the transmission.
1.
32-10
Good Bee. This softkey entry allows you to append a good block-check
sequence to your transmitted message. The INTERVIEW will make the proper
calculation based on the parameters selected on the Bee Setup screen (see
Section 10).
SEP '95
32 Laver 1 Conditions and Actions
2. Bad Bee. Press the softkey labeled BAD_BCe to append an errorred block-check
to your transmission. Assuming that Rev BIk Chk: Mi] is the selection on the Line
Setup menu, a BCC error will be indicated on the screen of the INTERVIEW by
all symbol. See Figure 32-10.
For BOP format, the bad BCC will be CRC-16 instead of CCrn: For other
formats it will be an inverted good BCC.
Figure 32·10 The INTERVIEW'sID monitor has detected a bad BeC transmitted by the
unit's own ID driver.
3. No Bee. The NO_BCC softkey pertains to non-BOP formats only. Instead of
appending a block -check calculation to a text message, the transmitter will
revert directly to idle-line condition.
Please note that receivers that are expecting BCC characters will treat the idle
characters generated by the INTERVIEW as block -check characters. The
INTERVIEW's own receivers (unless they go out of sync first) will display a
bad-BCC symbol on the screen. (Refer to Figure 10-4.) The device under test
probably will detect a BeC error and reject or ignore the message.
The user may, of course, enter a good BCC "manually" as part of the text string
that precedes the NO_BCC selection.
4. Abort. Abort is a BOP function only_ Instead of appending a proper
frame-check sequence (FCS), the transmitter will hold the lead at mark for eight
bits (or longer if the transmitter is idling Fr). Inside a frame, seven 1-bits in a
row are s.ufficient to signal an abort.
An aborted message is shown in Figure 32-11.
Figure 32·11 The INTERVIEW aborts a BOP frame by closing it with a byte of FF instead
of7E.
32-11
SEP '95
---~--------- _
___
JII_U_;tllll_I!D"'!§,I_IIffliE_'_ 1 1
...........
__
aa _ _
.. 4~_
.......
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(8) EIA
Press the softkey for EIA or type EIA followed by a space to bring five RS- 232 leads
and four auxiliary leads under spreadsheet control. The nine softkeys that represent
EIA actions are illustrated in two separate racks of keys in Figure 32-12.
EIA actions are available only when the unit is in one of the emulate modes. A
maximum of three RS- 232 leads are controllable at one time. When Mode:
?{'fi~_1 is the Line Setup parameter, you control CTS, CD, and DSR. You may
enter RTS ON or OTR ON as a spreadsheet action; but the DTE, not the INTERVIEW,
controls these leads, and the actions will not take effect. To turn RTS or DTR on,
first you must emulate a DTE.
The AUX softkeys allow you to apply off/on voltage to any of the AUX output jacks
(four on the RS- 232 Test Interface Module, three on the Y.35 and RS-449 TIMs
installed seated in the rear of the unit). (Refer to the documentation accompanying
the interfaces.) These AUX outputs are useful for turning on and off a signal that is
not a softkey selection or not under the control of your emulation.
NOTE: The AUX actions on the spreadsheet have nothing to do with the
25-pin TTL AUXILIARY connector at the rear of the INTERVIEW
After selecting a lead to control, select a status of OFF or ON. In the RS- 232
specification for drivers, on is defined as +5 V to + 15 V while off means a range of
-SVto-lSy'
This is an example of an EIA action:
ACTIONS: EIA OTR ON
Figure 32·12 Five EIA leads and four AUX leads are under program control.
32-12
SEP '95
32 Layer 1 Conditions and Actions
(C) Outsync
When the outsync action is taken, one or both receivers go out of synchronization
from trigger true until the next synchronization pattern is received. All data that
occurs in between outsync and resynchronization is considered "idle." If Display Idle:
tD is selected on the line setup, a receiver out of synchronization will prevent data
from being presented to the screen and the character buffer as well as to the test
program.
The outsync action also initiates the search for sync. Receivers that are already in
sync do not look for sync. As soon as a receiver goes out of sync, the formatting logic
begins to test for the one- or two-character sync pattern one bit at a time.
The outsync action may be useful when the information following a header group, for
example, is of no interest. Simply go out of sync until the beginning of the next
frame, when synchronization will restore the data display automatically. CAPTURE OTE
(or DeE) OFF performs a similar function, except that "capture" must be turned on
again by trigger when you want to resume the display.
Figure 32·13 The spreadsheet program can force one or both data leads out of sync.
Mer you have pressed the OUT_SYN softkey or typed OUT_SYNC followed by a space,
select one or both leads from the softkeys illustrated in Figure 32-13. RECEIVE and
TRANSMT may refer to DTE or DCE, depending on your emulate mode at the
moment. These selections allow you to change your emulation on the Line Setup
menu without having to worry about changes to the spreadsheet program.
(0) Idle Line
IDLE_UNE allows you to use a trigger action to change the idle-line condition applied
by the INTERVIEW. If you press the softkey for IOLE_LN (see Figure 32-13) or type
IDLE_UNE followed by a space, the words Enter Idle Character String will appear on the
prompt line in the softkey area at the bottom of the screen. Enter a single
alphanumeric, control, or hexadecimal character in quotation marks. The red LED
on the ~ key should be on for hexadecimal entry.
SEP'95
32-13
-----------------------------______u._. . . . . . .
INTERVIEW 8000 Series Basic Operation: 951-80424-01
The idle -line action applies only when Format:
has been selected on the Line
Setup menu. This trigger action is useful for tests in protocols that employ different
idle characters to signal changes in protocol state. An example is X.21 or X.21 his,
which in various states will idle FF , 'l!I, +, and so on.
Here is an example of an IDLE_UNE action:
ACTIONS: IDLE_UNE "+"
(E) Enhance
The spreadsheet program can be used to enhance display data selectively. Data on
either or both sides of the line may be enhanced. Figure 32-14 shows typical
reverse-image enhancements. Enhancements are stored in the character buffer for
later review: see Section 7.3.
Enhancements that pertain to the plasma display are reverse-image, blink, and hex.
In addition to these, a low-intensity enhancement can be applied to data that is
transmitted to a black-and-white monitor connected at the RS-170port (see
Figure 1-6).
Blink, reverse and low enhancements activated by the trigger-menu or spreadsheet
program can be mapped to colors on a color monitor attached at the INTERVIEW's
RGB port (Figure 1-6). See Section 18.2 for an explanation of how blink, reverse,
and low enhancements relate to character and background colors in the RGB output.
Enhancements are available at every protocol level, but only Layer 1 enhancements
affect the raw-data display. Higher-level enhancements are applied to the protocol
trace for a given layer.
Figure 32·14 Enhancements may be used to highlight protocol fields.
After pressing the ENHANCE softkey or typing ENHANCE followed by a space, select one
or both leads from the second level of softkeys in Figure 32-15.
Next, select the type of enhancement from the third tier of softkeys in Figure 32-15.
Enhancements may be used in combination (such as reverse blink, or low-intensity
reverse). Then at the final level, turn the enhancement ON or OFF.
1.
Reverse image. Reverse-imaged characters are presented as dark letters on a
lighter background.
32-14
SEP '95
32 Layer 1 Conditions and Actions
2.
Low intensity. This attribute does not affect data on the plasma display, which
supports one display intensity only. Characters that are given this attribute will
appear in low intensity on a CRT that is attached to the INTERVIEW through
the RS-170 port.
Figure 32-15 Layer 1 enhancements must be turned off as well as on by trigger.
3. Blink. BLINK causes data to be highlighted by a high - intensity area that blinks on
and off. This is the most conspicuous highlight for small portions of data.
4.
Hexadecimal. When the HEX enhancement is turned on, all data affected by the
trigger is displayed in hexadecimal. Once data is stored in the buffer as
hexadecimal, it remains in this format even if the ~ key is toggled.
Refer to Figure 6-17 for data in which hex translation has been turned on for
protocol characters and off for user (ASCII) data.
SEP '95
32-15
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(F) Capture
This action turns on and off the presentation of data to the screen-that is, it stops or
"freezes" the display-and capture of data to the screen buffer (character RAM).
Unlike the Manual Freeze mode initiated by the II'IIEEZEI key, however, the "capture off"
action does not allow you to scroll through the buffer while the test continues.
This action allows you to use the spreadsheet program to find important data and
then preserve it in the buffer when it would otherwise be overwritten and lost.
Here is a sample capture action:
ACTIONS: CAPTURE BOTH OFF
where OFF means freeze the display and BOTH means with respect to DTE and DeE.
After pressing the CAPTURE $Oftkey or typing CAPTURE followed by a space, select DeE,
DTE, or BOTH from the rack of softkeys shown in Figure 32-16. On a subsequent set of
softkeys, select ON or OFF as the capture action.
Figure 32·16 Screen display ("capture") can be turned on or off with respect to one data lead or
both.
1. DeE. This option disables or enables the buffering and display of DeE (RD)
data. Suppressing one data lead only does not serve the purpose of preserving
data indefinitely in the buffer, since the other lead eventually will overwrite the
buffer.
2.
DTE. The TD lead by itself can likewise be suppressed or displayed.
3.
BOTH. This option suppresses or displays a1l data.
4. LEADS. This option suppresses the lead changes to the display.
32-16
5.
ON. This action enables buffering and display of the selected data.
6.
OFF. This action suspends buffering and display.
SEP '95
32 Laver 1 Conditions and Actions
32.4 Dual-Port Layer 1 Actions
When a block of Layer 1 conditions has been entered using a dual-port TIM, press ~ to
access the softkeys for ACTIONS. The set of seven Layer 1 actions for dual-port use is
shown in the softkeys in Figure 32-17. The names of these actions are SEND, OUT_SYNC,
IDLE_UNE, ENHANCE, CAPTURE, and SEND2. With the exception of SEND2, they are all
described in Section 32.3 of this manual. The other, darkened softkeys in the figure are
layer-independent actions present at every layer, discussed in Section 31. SEND2, the
secondary port send action, is described below.
Figure 32·17 Dual-port Layer 1 actions.
(A) Send2
Transmitting a string is the only send action, and when using a dual-port TIM
transmissions can be done on both the main port (using SEND) and the secondary port
(using SEND2). While transmissions occur at all layers, only Layer 1 allows the user to
type in a complete transmission, character by character. At higher layers, the user
types the names of protocol elements and the software converts these mnemonics to
strings. The user enters character strings directly at higher layers only into specified
user-data fields.
32-17
SEP '95
--_._--_ ...•
__ ...__._-----------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Using a dual-port TIM, the SEND and SEND2 actions are executed in the same
manner as the SEND action when using a single-port TIM.
The spreadsheet compiler identifies strings by the quotation marks surrounding them.
Send-strings have no size limit (for practical purposes). All ASCII -keyboard,
control, and hexadecimal characters are legal in a send-string. Special keys (B,
~, ~) are not lega1.
To insert a canned fox message into a transmit string, type FOX inside double parens,
as follows: ((FOX)). Remember that the double parens are special characters produced
by the ~-® and ~-@ combinations. Constants, counters, and flags can also be
embedded in a string. See Section 33, Strings.
For the main port, press the SEND softkey or type SEND followed by space to begin the
entry; for the secondaI)' port, press the SEND2 softkey or type SEND2 followed by space
to begin the ent:rf. The prompt Enter Transmit String appears as in Figure 32-8. Enter
the string inside quotation marks.
Figure 32·18 Transmit a string to the main port (SEND) and to the secondary port (SEND2) using a dual-port TIM.
After quotation marks are typed in to close the transmit string, a set of softkeys
appears for the error-checking value that will be appended to the transmit string.
One of these must be selected; otherwise, the program will not compile and a
Premature End of File error message is generated.
Figure 32·19 Select a block-check calculation to end the transmission.
See Section 32.3(A) for specific information on entering a block-check calculation to
end the transmission as well as on the other softkeys.
32-18
SEP'95
33 Strings
33 Strings
A string on the Protocol Spreadsheet is a sequence of text characters that the operator encloses in
quotation marks and enters following certain ke}Words. Strings are valid in both conditions (at
Layer 1) and actions (at any layer). Depending on its use in the program, the string may be
searched for, transmitted, printed out, or written to the screen while the program is running.
"Lists" are a subset of strings with an important distinguishing feature: where a string is a sequence
of characters, a list is a set of single characters. Examples of lists are one-of conditions at Levell
of the spreadsheet, or keyboard conditions at any level.
Apart from Layer 1 receive conditions and transmit actions at all layers ( discussed below), strings
are valid also in KEYBOARD conditions, where a list of keys may be entered, anyone of which will
satisfy the condition; in IDLE_UNE actions, where a single-character "string" entry represents the
new idle character; in LOAD_PROGRAM actions, where the string must match the absolute pathname
of the file to be loaded; and in PROMPT and TRACE actions.
All ASCII - keyboard, oontrol, and hexadecimal characters are legal both in receive and transmit
strings.
Two ASCII characters are treated in a special way. If you wish to include a quotation mark within a
string, you must precede it with a backslash character (\"). If you wish to include a backslash
character in a string, you must precede it with a second backslash character (\\). A single backslash
is never included in the string.
Control characters are entered into text strings by the action of the eJ key together with the key
that bears the control-character mnemonic at the top right corner. Note that CR ("carriage
return") is the mnemonic at the top right corner of the @l key. Press ~-IMI to enter Cit into a text
string. The 8 key does not produce a character entry.
33-1
SEP '95
-_....
_._._-------------------
Table 33-1
Valid Entries In Receive Strings
Type entry
Example
ASCII
2
®
"
\"
51
\\
Control
Example in
string or list
(lOt)
Key sequence
This data
satisfies string
condition
Data beginning
(arbitrarily) wI AB
satisfies 10f condition
"123"
123
AB2
"1\"3"
1"3
AB"
!SJ51
"1\\3"
1\3
AB\
\
~J.lYJ
"1\3"
1\3
AB\
Hex
°e
E§f!I@
"1°e3"
10e3
AEfa
Not Equal
i!-
~®
"1i!-3"
11S
A
Bit Mask
« XXXX1111))
§9-@) [RI (8)[81 [RI
mmaHIl§9-@
1°,,3
AB"F
Not equal
to bit mask
IXXXX1111))
~ §9-0 [RI [RI [RI
"1IXXXX1111)) 3"
123
A
Don't Care
t8J
(lIJ
"1t8J3"
153
A
Flag
IEl
§J
"'03"
iIEl3
A@
Sync
12
8-8
"1ills"
1ills
AE@
Constant
« A»)
~-@) ~-0 ~.f!I
1« A» 3
labcdefg3
ABabcdefg
~-O
"1(
tID
XXXX1111)) 3"
mmmm§Y·@
where A is
defined in a
CONSTANT field as
A = "abcdefg"
33 Strings
33.1
Strings To Be Matched Against Line Data
String conditions are legal in STRING and ONE_OF conditions at Layer 1 only.
Receive strings (and DTEIDCE strings) have a size limit of 32 characters. Their size
cannot be expanded through the use of constants. (Any constants will be expanded before
the size limit is enforced during compilation of the program.)
(A) Special Characters
Of the special-character keys,!iIUJ, \1m, ~, and 8-8 (for the ~ character) are
valid. f!WJ is not valid. Bit masks are entered in receive strings by the keying
sequence illustrated in Thble 33-1.
(8) Embedded Strings ("Constants',)
The string represented by a constant may be embedded in a receive string or a list. A
constant is a textual string that is represented by a symbolic name. This name is
inserted into a string or list inside double parens. Double parens are special
non- ASCII characters produced on the keyboard by ~-@ and ~-@.
The following is an example of a constant used in a spreadsheet condition:
CONDITIONS:
RECEIVE STRING "CCAODR_A)) "u "
The data that satisfies this string will depend on the definition of the constant. Here
is one possible definition:
CONSTANTS:
AOOR_A:=
·AA7"T,,~
The data that satisfies the condition will include the expanded constant along with
the rest of the string: AAT" 7" eo .
33.2 Strings To Be Transmitted
Only Layer 1 allows the user to type in a complete transmit string, character by character.
In the following transmit string, the entire transmission including sync characters, is inside
quotation marks:
SEND "s.-s.- 't 70 ~ NO_BCC
At higher layers, the user types the names of protocol units and values as "keywords" and
the software converts these elements to strings. Immediately following the keyword
entries, the user may add a string in quotation marks. Here is an example of a string
following nonstring entries in Layer 2 SDLC:
SEND FRMR AOR=C1 P/F=1
SEP'95
u\ 66 0&" GDBCC
33-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
All ASCII - keyboard, control, and hexadecimal characters are legal in a transmit string.
None of the special-character keys (1iBJ, r&J, !III, 8) is valid.
(A) Constant
Constants may be transmitted. Simply place the name of the constant inside double
parens and insert the unit into the string. While the test is being compiled, the
constant is replaced in the string by the text that is assigned to it.
The canned "fox" message is a built-in constant named FOX that is dermed
internally as follows: FOX = "nIE QUICK BROWN FOX JUMPS OVER TIlE
lAZY DOG 0123456789." An example of the FOX constant, as it appears in a
transmit string, is given in Thble 33-2.
(8) Transmit Variables
Certain variables may be transmitted also. Any number of counters and flags may
have their values transmitted at any point.
H a counter or flag is named inside double parens in a transmit string, the current
hexadecimal value of the low-order byte of that counter or flag is transmitted with the
rest of the string. An example of a counter used in a transmit string is given in
Table 33-2.
In order to be referenced in a transmit string, a counter or flag must first be created
in a trigger-menu or spreadsheet condition or action. The counter or flag need not
be named on a statistics screen.
Do not name a counter (or flag) in a transmit string if it has the same name as
another flag (or counter). It is unpredictable which one will be transmitted.
The low-order byte of a counter or flag is the default byte to be transmitted. The
second byte will be transmitted instead if the name of the counter or flag is followed
by [1] inside the double parens. Here is an example of a Layer 2 transmission that
includes both bytes of a flag named seq (as well as a fox message):
Flags are two bytes long, counters are four. All four bytes of a 32-bit counter may be
transmitted. Here is a transmit string that sends a complete counter named fourbyte:
SEND·
33-4
counter =((fourbyte[3]D (Cfourbyte[2]D ((fourbyte[1])) ((fourbyteD •
SEP'95
33 Strings
(e) Data Request
A transmit string that is created at one protocol layer may be passed down
transparently to lower layers, one layer at a time. A user-entered message that is
sent down at Layer 4, for example, is detected at Layer 3 as an N_DATA REO primitive
and may be handed down to Layer 2 as an "«N_DATA))" string.
The string is appended either to a SEND DATA action (or to a DL_DATA REO primitive).
See the example below. The SEND DATA action will append a packet header to the
N -data automatically. The Dl_DATA REO primitive will not add a header to the
N -data string; but the user may enter additional data inside the quotation marks
(not inside the double parens).
Layer 2, in turn, detects the data as a DL_DATA REO primitive, and may hand it down to
Layer 1 in the form of a "CCDL_DATA)) " string appended to a SEND INFO action (or to a
PH_DATA REO primitive).
LAYER: 4
STATE: transport
CONDITIONS: KEYBOARD· •
ACTIONS: N_DATA REO ~( FOX)) "
LAYER:3
STATE: network
CONDITIONS: N DATA REO
ACTIONS: SEND-DATA PATH"" 0 "«N_DATA))"
LAYER:2
STATE: datalink
CONDITIONS: DL CONNECT REO
ACTIONS: DL cONNECT CONF
CONDITIONS:DL DATA REO
ACTIONS: SEND iNFO ,,«oL_DATA)) •
Data is sent up the layers also. The mechanism for passing data upward is the
GIVE_DATA action included in the protocol personality package at each layer. Since the
user will not normally wish to add protocol headers to upward -moving data, this data
is not treated as a separable string inside quotation marks. It is passed upward
transparently in the GIVE_DATA action.
SEP'95
33-5
Table 33·2
Valid Entries in Transmit Strings
Example in
transmit string
Data transmitted
Type entry
Example
Key sequence
ASCII
2
III
"123"
123
"
\If
fSJ 8-0
"1\"3"
1"3
\\
fSJfSJ
"1\\3"
1\3
Control
s"
§g-@l
"1$,. 3"
1$,. 3
Hex
09
~ 00 lID
"1 oe3"
1oe3
Constant
(CA) where A is defined
§.9·@8-0
§.9·oo
"1 «A)) 3"
1abcdefg3
"1«FOX)) 3"
HHE QUICK BROWN FOX JUMPS
in a CONSTANTS field
as A = "abcdefg"
Fox
«FOX))
~-@
!mID (E) (§J IE]
~-[ID
Counter or
«addr))
flag,
(low-order byte)
where addr is the name
of a counter with a current
decimal value of 14
Counter or
«seq (1))) where seq is
flag, second byte
the name of a flag. the
second (high-order)
byte of which has a
binary value of 01010100
Data in a
«DL_DATA)) at Layer 2,
data - request
where Layer 3 string is
primitive
fox message and Layer 3
header is 10 °7 6£
OVER THE LAZY DOG 01234567893
~-@
"1 «addr» 3"
tOE
§.9-(il
@@@lDmrn
~-0
"1(seq[1 j)) 3"
f l 43
§0.(il
(QJ [1J 8-8 @ 01fl0
~Hill
"1 «OL_DATA)) 3"
o tID tID @ 8·00
3
110 0r"'E THE QUICK BROWN FOX
JUMPS OVER THE LAZY DOG
01234567893
34 OSI Primitives on Spreadsheet
34 OSI Primitives on the Protocol Spreadsheet
34-1
SEP '95
-- -
--------------_...
_---------------_.. ----,
.........
" ....................
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 34-1 The softkey path for a DL_CONNECT IND condition primitive at Layer 3.
34-2
SEP '95
34 OSI Primitives on Spreadsheet
34 OSI Primitives on the Protocol
Spreadsheet
Primitives are defined in the Open Systems Interconnect (OSI) Reference Model as
protocol-independent interactions between adjacent layers of the model.
For example, data that comes into the INTERVIEW at Layer 1 or starts down the OSI "ladder" at
a layer above Layer 1 is stored in a structure caned an IL (interlayer) buffer. This buffer is passed
between layers along with a primitive data unit (PDU), or primitive.
Since primitives are layer-specific, they are not available on the Trigger menus which offer
conditions and actions at Layer 1. You must use the Protocol Spreadsheet to send, receive, or
monitor primitives.
The Protocol Spreadsheet is divided into seven layers in accordance with the OSI model. By giving
the operator control of the boundaries between these layers, primitives make layered programming
possible.
Primitives for a given OSI layer may be entered in the Protocol Spreadsheet whether or not a
protocol personality package is loaded in for that layer. Table 34-2 lists the primitives that may be
entered on the current Protocol Spreadsheet. Due to the uncomplicated, "always-connected"
nature of the RS- 232N.24, V.35, and RS -449 interfaces, Layer 1 primitives are automatic and do
not appear on the Protocol Spreadsheet for that layer. OSI service for Layers 2 through 7 currently
is available.
NOTE: Unless a Layer 1 package (such as DDCMP) is loaded in,
primitives are not available when Format
is selected on the
Line Setup screen.
On the Protocol Spreadsheet, primitives take the form of conditions and actions. A condition
primitive monitors the layer boundaries for action primitives that are sent down from above or up
from below. An action primitive at any layer is sent either up or down to the next layer. Each
primitive is shared by two layers. DL_CONNECT IND, for example, is an action primitive at Layer 2.
At Layer 3, the same primitive is a condition. The prefix (DL) is an abbreviation for the name of
the lowermost layer (Data Link) which shares the primitive. Table 34-1 lists all primitive prefixes
and the layers which share them.
SEP'95
34-3
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Table 34-1
Primitive Prefixes and Associated Layers
Prefix
Lowest Layer
of Operation
PH
DL
Physical (Layer 1)
Data Unk (Layer 2)
Network (Layer 3)
Transport (Layer 4)
Session (Layer 5)
Presentation (Layer 6)
N
T
S
P
34.1
Shares with
Layer
2
3
4
5
6
7
Softkey Selections
The condition and action primitives specific to a given layer will be arrayed on softkeys
that appear when you press the softkey for OS!. OSI is IEl on the second rack of condition
softkeys. Figure 34-1 shows the softkey path to an OSI condition primitive at Layer 3. OSI
is r.m on the third rack of action softkeys. Layer-specific softkey racks corresponding to
the following general categories appear successively as selections are made:
(A) Direction
Indicate the direction from which the condition primitive will come. At Layer 3, for
example, the first choice (DL) will detect primitives handed up from the layer below;
the second selection (N) will detect primitives handed down from the layer above. As
an action, you select the direction which you wish the primitive to go: the first choice
(DL) sends the primitive to the layer below; the second selection (N) sends the
primitive to the layer above.
(8) Type
Choose among the primitive types offered at each layer. Each layer has its own set of
primitives, but they all can be grouped into four major phases: establishment, data
transfer, release, and debug and error reporting.
In the establishment phase, a layer establishes a connection with the layer above
and/or below. The activate and connect primitives provide this function. Data
transfer is accomplished via the data, expedited data, and reset primitives.
Deactivate and disconnect primitives break the connection between layers in the
release phase. Debug and error reporting primitives include debug, error report, and
unitdata.
34-4
SEP '95
34 OS! Primitives on Spreadsheet
(C) Request/Response
For some primitives, you must indicate whether you are searching for-or sending-a
request (REO or INO) or a response (RESP or CONF). INDications and CONFirms
come from the layer below or go to the layer above; REQuests and RESPonses come
from the layer above or go to the layer below.
(D) Path
Provide a path. if necessary. Interlayer primitives must handle channel or "path"
information in order to insure that data moving down from Layer 4 is given the
correct logical channel at Layer 3, or that data moving from Layer 3 to Layer 2 bears
the correct frame address when it goes out on the data link.
A softkey sequence that leads to the PATH= selection for a primitive on the Protocol
Spreadsheet is shown in Figure 34-2.
Figure 34-2 DATA andEXPEDITEPATA action-primitives may carry path information as well as a
data string.
Refer to Section 38.1(E) for a discussion of how paths are tied to call parameters
(and directly or indirectly to logical channel numbers) via user entries on the Packet
Level Setup screen (Figure 38-2) at X.25 Layer 3.
Primitive paths are only an important consideration when more than one layer is
multiaddress or multichannel. In that situation, the vertical path numbers should
match. Layer 3 might provide several logical channels, for example, while Layer 2
services more than one link address. When a set of call parameters is assigned by the
user to path #1 at Layer 3, path #1 on the setup screen at Layer 2 should reference
the appropriate link address for that call.
Remember that data primitives along with their path parameters usually are handled
automatically (see Section 35). Automatic primitives will carry the same path
information as the SEND or GIVE_DATA actions that generated them.
SEP '95
34-5
--------------------------'-------------......._ , _
........_.............._n_.__._..
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(E) String
Optional strings may be added to DATA or EXPEDITED_DATA action -primitives at any
layer. A string is external data that is referenced in the list node of an interlayer
buffer. (See Figure 62-1.) This buffer is passed with the selected primitive. One
special use of the string field is to identify an IL buffer that has just been handed
down from above. The macro N_DATA (or T_DATA or PH_DATA) enclosed in double
parens in a data-primitive string field will identify the buffer that was just received
from above. When the current action primitive is processed, the IL buffer will be
passed to the layer below. One softkey sequence leading to a string selection is given
in Figure 34-2. Always enclose a string in double quotation marks.
Here is an example of a data primitive at Layer 4 passing a string down to the next
layer below:
LAYER: 4
STATE: transport
CONDITIONS: KEYBOARD· •
ACTIONS: N_DATA REO "«FOX)"
LAYER:3
STATE: network
CONDITIONS: N DATA REO
ACTIONS: SEND-DATA PATH= 0 "(eN_DATA»)·
LAYER:2
STATE: datalink
CONDITIONS: DL CONNECT REO
ACTIONS: DL CoNNECT CONF
CONDITIONS:DL DATA REO
ACTIONS: SEND iNFO "(COL_DATA)) •
This program is designed as a "quick" demonstration of OSI service primitives and
will transmit a fox message out on the interface (and display it on the INTERVIEW
screen) whether or not an actual link and call have been established. (Layer packages
must of course be loaded in at Layers 2 and 3.) Note the following:
34-6
•
The action at Layer 4 forces the fox message down to Layer 3.
•
The SEND DATA action at Layer 3 adds an appropriate Layer 3 header to whatever
data is referenced in the action.
•
The string that contains the macro ((N_DATA») indicates that the Layer 3 header
should be copied into the IL buffer that was passed with the N_DATA primitive
from Layer 4.
•
The same SEND action at Layer 3 triggers an automatic DL_CONNECT
REQUEST primitive, since Layer 3 does not send packets to Layer 2 unless the
link has been established.
•
The Layer 2 program bypasses link-establishment by forcing a DL_CONNECT
CONFIRM primitive up to Layer 3.
•
Now the data packet can be passed down to Layer 2, where a SEND INFO action
inserts a frame header in the buffer received (in a DL_DATA REO primitive) from
Layer 3.
SEP '95
34 OSI Primitives on Spreadsheet
•
Layer 1 primitives are automatic.
The fox message will also be transmitted if DATA REQUEST primitives are used
instead of SEND actions at Layers 2 and 3 (or if no protocol packages are loaded); but
the data in that case will not receive protocol headers.
34.2 Sample Primitives: CONNECT INOs and CONNECT REQs
Figure 34-3 and Figure 34-4 illustrate the flow of "connect" primitives between Layer 2
and Layer 3. The primitives in the figures are the labeled arrows positioned between the
layers.
LAYER 3:
LAYER 2:
RCVSABM
SENDUA
Figure 34-3 The (arrow -shaped) primitives moving between Layers2 and 3 are intended to satisfy Layer
2 that a Layer 3 entity really is "up there." (The three rectangles contain spreadsheet conditions and
actions.)
In Figure 34-3, Layer 2 receives a Set Mode command (SABM) from the data link. Before
it responds positively (UA) to this command, Layer 2 passes up a DL_CONNECT INO primitive
in order to verify that a Layer 3 entity reaDy is "up there." When the active status of a
Layer 3 entity is confirmed, Layer 2 sends the poSitive response (UA) down to Layer 1 and
out onto the link to invite its Layer 2 peer to begin transferring data (Info frames).
,,~
.'
SEP '95
34-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
The spreadsheet block that accomplished this exchange of primitives would be the
following:
LAYER: 2
STATE:establish link
CONDITIONS: RCV SABM
ACTIONS: DL CONNECT IND
CONDITIONS:DL CONNECT RESP
ACTIONS: SEND UA
LAYER: 3
STATE: dl connect
CONDITIONS: DL CONNECT IND
ACTIONS: DL_CONNECT RESP
In Figure 34-4, the request for confirmation of an adjacent layer is downward. Layer 3
wishes to send a Restart packet to the Layer 3 entity on the other side of the link; but it
doesn't want to pass the packet down to Layer 2 if there is no mechanism at that layer to
handle it. So Layer 3 precedes the Restart packet with a DL_CONNECT REO primitive.
LAYER 3:
ENTER_STATE
DL CONNECT
- REO
DL CONNECT
-CONF
SEND RESTART
etc.
LAYER 2:
DL CONNECT
- REO
SEND SABM
RCVUA
DL CONNECT
-CONF
Figure 34-4 Layer 3 uses connect primitives to be sure that the Layer 2 entity below has established a
link.
34-8
SEP '95
34 OSI Primitives On Spreadsheet
In the scenario illustrated in the figure, Layer 2 has not yet established the link. It
responds to the connect-request primitive by sending aSABM. the X.25 command that
initiates "connection" between link -level peers. When the SABM is acknowledged in a
VA response, Layer 2 gives the Dl_CONNECT CONF primitive up to Layer 3.
34.3 Sample Primitives: DATA INDs and DATA REQs
Figure 34-5 illustrates the primitives that are generated and monitored by the Protocol
Spreadsheet when data is passed in both directions through an intermediate protocol layer
(Layer 2). In this example, X25 is the protocol package loaded in for both Layer 2 and
Layer 3. Here a call-request packet is passed up through Layer 2 and received at Layer
3, and a call-confirm packet is sent down by Layer 3. The primitives in the figure are the
labeled arrows positioned between the layers.
Data is in the form of physical-layer (PH) data when it moves in either direction between
Layer 1 and Layer 2. PH_DATA primitives control the movement of this data. In between
Layers 2 and 3, the data takes the form of data-link-layer (DL) data, with DL_DATA
primitives responsible for data - delivery.
I
LAYERS:
LAYER 2:
RCVINFO
/
RCVCALL
GIVE_DATA
SEND RR RESP
I
Dl_DATAREQ
/
SEND INFO
"(( DL_DATA )).
Figure 34-S These (arrow- shaped) primitives are generated and monitored at Layer 2 when Layer 3 receives
and sends data. (The tbree rectangles contain X.25 conditions and actions.)
SEP'95
34-9
INTERVIEW 8000 Series Basic Operation: 951-80424-01
The PH and DL versions of the data are not exactly the same. DL data has one less layer
of protocol attached to it. In the example in Figure 34-5, the Layer 2 protocol was
stripped off by the GIVE_DATA action when the call-request packet was being passed
upward. On the call-confirm packet's trip down through the layers, Layer 2 protocol was
added to the DL data by the SEND action-thus yielding PH data.
Note that "DL data" refers to data that moves above the DL layer (Layer 2), not below it.
"DL data" can be taken literally to mean that as far as the DL layer is concerned, this is
pure data, with no protocol that is recognizable at Layer 2.
When data is being passed upward, the primitives that signal the data are called
indications (DATA INDS). When data is sent downward, the primitives at each layer are
termed requests (DATA REQs).
34-10
SEP '95
Table 34-2
051 Service Primitives
Conditions
Layer
7
6
From Layer Below
Actions
From Layer Above
P CONNECT INO
P-CONNECT CONF
P-OATAINO
P-EXPEOITEO DATA INO
P-RELEASE INO
P-RELEASE CONF
P-UNITOATAINO
P-ERROR REPORT INO
P-MGT FACILITY INO
P-oEBUG INO
P-TO OATAINO
P-RO-oATAINO
P-TO-EXPEOITEO OATAINo
P-RO-EXPEDITEo-OATAINO
P-TO -UNITOATA INO
P:Ro:UNITOATA INo
S CONNECT INO
S-CONNECT CONF
S-oATAINO
s-eXPEOITED DATA INO
S-RELEASE 'NO
S-RELEASE CONF
S-UNITOATA INO
S-ERROR REPORT INO
$-MGT FACILITY INO
S-OEBUG IND
S:TO_DATAIND
S RO DATAINO
S-TO -EXPEDITED DATA INO
S-RD-EXPEOITED DATA INO
S-TO -UNITOATA INO
S:RO:UNITDATA INO
To Layer Below
To Layer Above
P CONNECT REO
P-CONNECT RESP
P-OATAREQ
P-EXPEOITEo DATA REO
P-RELEASE REO
P-RELEASE RESP
P:UNITOATAREO
P MGT FACIUTY REO
P:oEBUG REQ
S CONNECT REO
P CONNECT REO
P-CONNECT RESP
P-OATAREQ
P-EXPEOITEO DATA REO
P-RElEASE REO
P-RELEASE RESP
P:UNITOATA REO
S-CONNECT RESP
S-OATAREo
S-EXPEDITEO DATA REO
S-RELEASE REO
S-RELEASE RESP
S:UNITOATA REO
P MGT FACIUTY REO
P:DEBUG REO
S MGT FACIUTY REO
S:OEBUG REO
P CONNECT INO
P-CONNECT CONF
P-OATAINO
P-EXPEOITEO DATA INO
P-RELEASE INO
P-RELEASE CONF
P-UNITOATAINO
P-ERROR REPORT INO
P-MGT FACILITY INO
P-OEBUG INO
P:TD_OATAINO
PAD OATAINO
p-TO-eXPEOITEO OATAINO
P-RO-EXPEOITEO-OATA INO
P-TO -UNITOATA IND
P:RO:UNITDATA INO
Table 34·2 (Continued)
OSI Service Primitives
Conditions
Layer
5
From Layer Below
T CONNECT INO
T-CONNECT CONF
T=DATAIND
T_EXPEDITED_DATA IND
T_DISCONNECT IND
T UNITOATA IND
T-ERROR REPORT IND
T-MGT FACILITY IND
T=DEBUG IND
T_TD_DATAIND
T RD DATA/NO
T-TO -EXPEDITED DATA IND
T-RO-EXPEDITED-OATA IND
T-TO -UNITDATA U\JD
(RO=UNITDATA INO
4
N CONNECT IND
N=CONNECT CONF
N DATAIND
N=DATA_ACK IND
N EXPEDITED DATA IND
N-RESET IND N-RESET CONF
N-DISCONNECT IND
N-UNITDATA IND
N-ERROR REPORT IND
N=MGTfACILITY IND
N DEBUG IND
N-TD DATA IND
N-RD-DATA IND
N-TO -EXPEDITED DATA IND
N-RD-EXPEDITED-DATA IND
N-TD-UNITDATA IND
N=Ro::.UNITDATA IND
Actions
From Layer Above
To Layer Below
To Layer Above
S_CONNECT REO
S CONNECT RESP
S=DATAREO
S_EXPEDITED_DATA REO
T CONNECT REO
T-CONNECT RESP
T=DATAREO
T EXPEDITED DATA REO
T=DISCONNECT REO
S CONNECT IND
S-CONNECT CONF
S=DATAIND
S_EXPEDITED_DATA IND
S_RELEASE REO
S RELEASE RESP
(UNITOATA REO
T_UNITDATA REO
S MGT FACILITY REO
S=DEBUG REO
T MGT FACILITY REO
T=DEBUG REO
T CONNECT REO
T-CONNECT RESP
T=DATAREO
T DISCONNECT REO
(UNITOATA REO
N CONNECT REO
N-CONNECT RESP
N=DATAREO
N_DATA_ACK_REO
N EXPEDITED DATA REO
N-RESET REO
N-RESET RESP
N-DISCONNECT REO
N=UNITOATA REO
T MGT FACILITY REO
T=DEBUG REO
N MGT FACILITY REO
N=DEsUG REO
T_EXPEDITED_DATA REO
S_RELEASE IND
S_RELEASE CONF
S UNITDATA INO
S=ERROR_REPORT IND
S MGT FACILITY IND
S-DEBUG IND
S-TD DATAIND
S=RD=DATA IND
S_TD_EXPEDITED_DATA IND
S RD EXPEDITED DATA IND
S-TO - UNITDATA IND
(RD=UNITDATA IND
T CONNECT IND
T-CONNECT CONF
(DATAIND
T_EXPEDITED _DATA IND
T DISCONNECT IND
T- UNITDATA IND
T-ERROR REPORT IND
T-MGT FACILITY IND
T-DEBUG IND
T=TD_DATA IND
T RD DATAIND
T- TO -EXPEDITED DATA IND
T=RD=EXPEDITED=DATA IND
T TO UNITDATA IND
(RD=UNITDATA IND
Table 34·2 (Continued)
OSI Service Primitives
Conditions
Layer
3
From Layer Below
OL CONNECT INO
OL-CONNECT CONF
OL:OATAINO
OL EXPEDITED DATA IND
OL-RESET INO DL-RESET CONF
DL-DISCONNECT IND
DL-UNITDATA INO
OL-ERROR REPORT INO
OL-MGT FACIUTY INO
OL-OEBUG INO
OL-TO DATAIND
DL-RO-OATA IND
OL- TO -EXPEDITED DATA INO
OL-RDEXPEOITED-DATA INO
OL-TO -UNITOATA INO
OL=RO:UNITOATA INO
2
PH ACTIVATE INO
PH-ACTIVATE CONF
PH:OATAINO
PH RESETIND
PH-RESET CONF
PH:OEACTIVATE INO
Actions
From Layer Above
To Layer Below
To Layer Above
N CONNECT REO
N-CONNECT RESP
N-OATAREO
N-OATA ACK REQ
N-EXPEoITEO DATA REO
N-RESET REO
N-RESET RESP
N-DISCONNECT REO
N:UNITOATA REO
OL CONNECT REO
OL-CONNECT RESP
O(OATAREO
OL EXPEDITED DATA REO
DL-RESET REO
OL-RESET RESP
OL-DISCONNECT REO
DL:UNITDATA REO
N MGT FACIUTY REO
N:OEBUG REO
OL MGT FACILITY REO
OL:OEBUG REO
N CONNECT INO
N-CONNECT CONF
N-OATAINO
N-OATA ACK INO
N-EXPEOITED DATA INO
N-RESET INO N-RESET CONF
N-DISCONNECT IND
N-UNITDATA IND
N-ERROR REPORT IND
N- MGT FACIUTY IND
N-OEBUG IND
N-TO DATA INO
N-RD-DATA IND
N-TO-EXPEDITED DATA INO
N- RO-EXPEDITED DATA INO
N-TO -UNITOATA INO
N:RO:UNITOATA INO
DL CONNECT REO
OL-CONNECT RESP
DL:OATAREO
PH ACTIVATE REO
PH:ACTIVATE RESp
PH_DATA REO
DL EXPEDITED DATA REO
OL-RESET REO
O(RESET RESP
PH_RESET REO
PH RESET RESP
PH:DEACTIVATE REO
OL DISCONNECT REQ
OL:UNITOATA REO
PH ERROR REPORT INO
PH-MGT FACILITY INO
PH-DEBUG INO
PH-TO OATA INO
PH:RO:OATA INO
OL MGT FACILITY REO
DL:OEBUG REO
PH MGT FACIUTY REO
PH:OEBUG REO
DL CONNECT INO
OL:CONNECT CONF
OL_OATAINO
OL EXPEDITED OATA INO
OL-RESET INO OL:RESET CONF
OL DISCONNECT INO
OL-UNITDATA INO
OL-ERROR REPORT INO
OL-MGT FACILITY INO
OL- OEBUG INO
OL-TD DATA INO
Ot.-RD-OATA INO
OL-TO-EXPEDITEO DATA INO
OL-RO-EXPEDITEO-OATA INO
OL-TD-UNITDATAINO
OL:RO:UNITOATA INO
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
34-14
SEP'95
35 Automatic OSI Primitives
35 Automatic OSI Primitives
Often the Protocol Spreadsheet primitives that operate below a given layer are handled
automatically by the protocol package at that layer.
Data primitives are automatic any time a SEND or GIVE_DATA softkey action is entered on the
spreadsheet.
Connect Requests are automatic when the fIrst spreadsheet data primitive is passed downward.
The DL_CONNECT REO in Figure 344 does not have to be entered in the user program. The connect
request (but not the confIrm) is handled automatically by the layer-package software, which
assumes that the user never wishes to pass data downward to an empty layer.
The Connect lnd and Connect Resp primitives in Figure 34-3, on the other hand, are not
automatic. They are completely at the discretion of the programmer of the Protocol Spreadsheet.
If the programmer wishes Layer 2 to complete the link setup and begin transferring Info frames
without the active participation of a higher layer, that is a viable alternative.
In the sequence in Figure 34-5 all of the primitives designated by arrows-with one exception-are
generated and monitored automatically by the Rev, GNE_DATA, and SEND spreadsheet entries. (The
lone exception is the DL_DATA REO primitive that is used as a condition in Layer 2.) This automatic
handling of primitives frees the user at the top layer from programming considerations outside of
his own immediate protocol.
When protocol packages are loaded, monitor primitives (such as DLJD_DATA IND) are passed up the
layers automatically. These primitives allow the Layer 2 and Layer 3 protocol-trace screens to
display frame and packet information even when emulate primitives have not been passed up.
Automatic handling of primitives will vary with different protocols. Refer to the sections on the
individual protocols for information on which primitives are tied to which protocol conditions and
actions.
SEP'95
35-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
35-2
SEP'95
36 X.21 Layer 1
36 X.21 Layer 1
SEP '95
36-1
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
Depress
La~er
La~er
La~er
La~er
etup
**
1 Package:
2 Package:
3 Package:
La!::ler 4 Package:
La~er 5 Package:
La!::ler 6 Package:
La~er 7 Package:
III
Ke!::l To Load The Selected Packages
SA
Figure 36-1 In addition to being an optional Test Interface Module, X.21 is a
"layer-personality package" of softkey functions at Layer 1.
Figure 36-2 A special set of leads are available for monitoring once the X.21
package has been loaded in.
36-2
SEP '95
36 X.21 Layer 1
36 X.21 Layer 1
In addition to being an optional Test Interface Module (available as OPT-951-13-1), X.21 is a
"layer personality package" of functions loaded into memory from disk via the Layer Setup screen.
Figure 36-1 shows the Layer Setup screen configured to load in the X.21 package from the
hard-disk drive. Refer to Section 8 for information on operating the Layer Setup screen.
The X.21 package consists of a group of conditions and actions at Layer 1 on the Protocol
Spreadsheet that facilitate X2I programming. Figure 36-2 shows the softkey path to a rack of
condition softkeys that represent X211eads. These softkey conditions allow you to detect lead
changes and lead status. Of the conditions on the first rack of softkeys below CONDS:, only LEADS is
specific to X2I and will be documented fully in this section.
Figure 36-3 shows the highest rack of softkeys containing actions that are specific to X2l. The SEND
softkey includes a CALL_SETUP_SEND function that sends text messages always in ASCII code
(consistent with X.21 call-setup protocol). The LEADS softkey gives the user control of X.21 control
and data leads in emulation mode. The PROTOCL softkey includes functions that switch the line
setup back and forth from ASCII 7 - bit odd parity for call setups, to whatever line setup the user
has configured for data transfer on the Line Setup menu.
Other softkey actions in Figure 36-3 are not specific to X.21 and are discussed elsewhere in the
manual.
A group of Figures at the end of this section, Figure 36-10 through Figure 36-13, shows the
INTERVIEW emulating either the user or the switch in caning, called, clearing, and cleared
scenarios. The "conditions" and "actions" in these drawings are softkey conditions and actions in the
X.2I Layer 1 personality package. The "new states" in the drawings are standard X.2I state names
which may be borrowed as state names on the Protocol Spreadsheet.
36-3
SEP '95
---------- _.
__._-_. _..._. -
.. __ ...
_. -.------.- - . -_._-_._---_._._--- .-.. -.-.....- - - -
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 36-3 The SEND, LEADS, and PROTOCL softkeys branch
to actions that are specific to X.21.
36.1 X.21 bis
The X.2I Layer 1 package also will work with the standard RS- 232N.24 TIM in an X.21
bis configuration. With the standard RS- 232 TIM installed, the lEADS softkey shown in
Figure 36-2 will be replaced by the EIA softkey that branches to standard EIA control-lead
names: RTS, CTS, etc. The X.2I bis recommendation maps X.2I data and control leads to
EIA leads according to the following conversions:
T
C
R
= TO
= DTR
=
=
RD
DSR
The LEADS softkey in Figure 36-3 changes to ErA in X.2I bis. When the RS-232 TIM is
installed, data leads can be set to one of the standard X.21 idle conditions ( +, It , ~ , '6, and
so forth) only via the IDLE_LN softkeyaction.
36.2 Transmitter/Receiver Phases
X.2I requires that data such as selection signals (the destination phone number) be
transmitted during call setup. The data is transmitted in the following synchronous format:
ASCII code, s,- s,- sync pattern, 7 data bits, odd parity, no BCe.
Once the call is established, a different format and code may be used at the link level and
above. In order to monitor and transmit X.21 data and higher-level data correctly without
exiting Run mode and reconfiguring the line setup, the X.21 layer package provides two
different "phases" of the transmitter and the receivers. These phases are called
CALL_SETUP and DATA_TRANSFER, and they are entered into the program via softkey. See
Section 36.5(C), below.
When the program is in call-setup phase, data is monitored and sent according to the
synchronous format and ASCII code defined above. In data-transfer phase, the format
and code are as defined by the user on the Line Setup menu.
36-4
SEP '95
36 X.21 Layer 1
36.3 Sending From Layer 2
When Layer 1 is in data - transfer phase, a SEND action at Layer 2 will cause a transmission
to go out onto the line automatically. No SEND action at Layer 1 is required.
When Layer 1 is in call-setup phase, a SEND action at Layer 2 will be ignored. If Layer 1
wishes to communicate to Layer 2 its readiness to send data, it must do so by SIGNAL action
(see Section 31.4), since primitives are not currently operative at Layer 1.
36.4 X.21 Conditions
Th bring up the bank of softkey conditions for Layer 1, first press the CONDITIONS softkey.
This key becomes available when the cursor enters a programming block at the state level.
The first three condition softkeys-DTE, DeE, and RECEIVE-are common to all Layer 1
configurations. The fourth condition softkey, LEADS, is specific to the X.21 test-interface
module. To the right of the LEADS softkey are general (layer-independent) conditions
discussed in Section 31.
LEADS is a transitional1status condition and may be combined with other conditions
(including other LEADS conditions). Refer to Section 31.2 for a discussion of how
conditions may be combined.
(A) Data
The first three X.2I conditions can monitor one of the two data leads for a specific
data event. This event can be any of several characters, a string of characters, a good
Bee following the character or string, an error revealed by a block or parity check,
and so on. When DTE is selected, data on the T lead will be monitored. A DCE
condition monitors the R lead. RECEIVE conditions are intended for use in the emulate
modes. When RECEIVE is selected, the INTERVIEW will always monitor the lead
opposite its own transmit lead.
The fourth X.21 condition, LEADS, also can monitor both data leads. Figure 36-4
shows that T and R leads can be monitored for ZERO or ONE status. A data lead will
satisfy one of these conditions when it is valid zero or valid one-that is, when it has
retained its zero or one status for 16 consecutive bit times.
SEP '95
36-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 364 T and R leads can be monitored for zero or one status.
A mere transition from zero to one (or from one to zero) has no significance in X.21
protocol and cannot be detected by a LEADS T or LEADS R condition. (Control leads C
and I, on the other hand, may be monitored either for a mere transition or for a valid
status-see below.)
(8) Control Leads
X.21 conditions can monitor the status of C and I control leads. The C and I softkeys
are in the conditions rack below LEADS. See Figure 36-5.
NOTE: Before you may monitor the status of C and I leads, the
buffering of control leads must be enabled on the Front - End Buffer
Setup menu. See Section 9.1(B).
C and I may be tested for true status or for valid status. In the X.21 protocol, the
state of the lead is valid if it has been true for 16 bit times. LEADS C ON, for example,
checks the true state of the C lead. If the condition is alone in a CONDITIONS block,
any momentaty transition of the C lead from off to on will satisfy the condition. If the
condition is used in a context where it is static rather than transitional-see Section
31.2 for a definition of this context-the true on state at the moment the lead is
checked will satisfy the condition.
Figure 36-5 C and I leads may be tested for true status or for valid status.
36-6
SEP '95
36 X.21 Layer 1
The lEADS C ON_VAUD condition requires not only that the state be true but also that it
be valid. Valid conditions may be transitional or static, depending on how they are
combined with other conditions in the same CONDITIONS block. When LEADS C
ON_VAUD is used alone in a CONDITIONS block, it is transitional. A transitional ON_VAUD
condition will be valid 16 bit times after the transition from off to on-assuming that
it retains its true status for the entire 16 clock pulses.
(C) User Assigned
A LEADS UA condition detects an on or off state only if that state is valid. If a data lead
is patched to the VA input, ON equals zero and OFF equals one.
36.5 X.21 Actions
When a block of conditions has been entered, press 8 to access the ACTIONS softkey. The
actions that pertain to the X.21 Layer 1 personality package are SEND, LEADS, and
PROTOCL, shown in Figure 36-3. SEND and lEADS actions are operative in emulate modes
only.
(A) Data leads
Data leads may be programmed to send character strings via the SEND softkey. They
also may be programmed to idle constant mark, constant space, bell characters, plus
characters, sync characters, and an alternating pattern of O's and 1's via the LEADS
softkey.
1.
Data-transfer send. Figure 36-6 shows the three send options that branch under
the SEND softkey. If you press SND_DTA, the keyword SEND is written to the
spreadsheet screen and this prompt appears below the screen: "Enter Transmit
String." This is a normal Layer 1 send action and it is appropriate whenever you
are in Data Transfer state according to the X.21 protocoL
Press the SND_DTA softkey or type SEND followed by space to begin the entry.
Enter the string inside quotation marks. After quotation marks are typed to close
the transmit string, a set of softkeys appears for the error-checking value that
will be appended to the transmitstring-GOODBCC, BAD_BCC, NO_BCC, or ABORT.
To execute a data-transfer send. the program must be in data-transfer
phase-see below. In this phase, the transmitter and receivers are obeying the
code and format options selected on the Line Setup menu.
2.
SEP'95
Call-setup send. The SEND softkey includes a CALL_SETUP_SEND function that
sends text messages always in a code and format that is consistent with X.2I
call-setup protocol. Press the SND_cu. softkey (Figure 36-6) or type
CALL_SETUP_SEND followed by space to begin the entry. Enter the string inside
quotation marks.
36-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 36-6 1\vo separate SEND actions are used to transmit either in data - transfer or
call-setup format.
The code and format of a call-setup send action always is the same: ASCII code,
7 data bits, odd parity, no block check transmitted. Synchronization characters
are ~ ~ (hex II; 11;). The synchronization pattern must be provided in the transmit
string-it is not automatic.
To execute a call-setup send, the program must be in call-setup phase-see
36.5(C), below. In this phase, the transmitter and receivers are disregarding the
code and format options selected on the Line Setup menu.
3.
Can - setup send idle. The SEND softkey also includes a CALL_SETUP_SENDJDLE
function. This action combines the CALL_SETUP_SEND action and the LEADS action
that specifies an idle character. When entered as these two separate actions, the
change in idle may occur slightly before or after the transmission.
Especially during high-speed operation, use the CALL_SETUP_SEND_IDLE action
(and the NEW_IDL selection below it) to guarantee that the specified change in the
idle character occurs during the string transmission. Press NEWJDL and enter the
(ASCII) idle character inside double quotation marks. Use the ~ key to enter
hexadecimal characters.
4.
Idle. Data leads also may be programmed to idle constant mark, constant space,
bell characters, plus characters, sync characters, and alternating 0 and l.
Figure 36-7 shows the softkey path going through LEADS and T or R to the various
idle states.
5.
One orzero. Select ONE to idle constant mark, ZERO to idle constant space.
Assuming that the program is in call-setup phase, a data lead idling mark will
appear on the data display as FF" • Space idle will be displayed as ~.
6.
Plus, bel~ or sync. Plus ( +) characters, bell (It) characters, and sync ("-' )
characters also may be transmitted as contiguous idle characters. A transmit
SEP '95
36-8
~--
-
------
36 X.21 Layer 1
stream of any of these characters will be preceded by two ASCII sync characters
(hex 1. ). In other respects, the action LEADS R BELLS has the same effect as the
action IDLE_UNE "'t ".
FIgUre 36-7 X.21 data leads T and R sometimes perform a "control" function by idling
various characters.
Plus-, bell-, and sync-character idle actions do not take effect unless the
program is in call-setup phase at the time the action is executed. The LEADS R
ZERO action or the LEADS T ONE action will take effect even in data -transfer
phase. The monitors may not be set up properly to detect or display the idle
state, however, and we recommend that the programmer switch to call-setup
phase as soon as one of the control leads first signals a clear request or
indication.
7.
Data. A ONE or ZERO leads action will clamp the line to the requisite voltage
level. Once a lead is clamped, it must be undamped before it can be used again
for data. The DATA softkey shown in Figure 36-7 represents the "unclamp" action.
To change from idling space to transmitting selection signals, for example, you
would insert the unc1amp action (lEADS T DATA) shown here:
STATE: call_request
CONDmONS: ENTER STATE
ACTIONS: LEADS T zeRO
PROMPT ·Press S to send selection signaisff
CONDmONS: KEYBOARD "S9'
ACTIONS: lEADS T DATA
CALL_SETUP_SEND "s"s" 123123+"
The PLUSES, BELLS, SYNCS, or ALT_O_1 action also will unclamp the line
automatically.
SEP'95
36-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
8. AltematingO/I. Press the softkey for ALT_O_1 to send an alternating series of
zeroes and ones. The sequence is not preceded by sync characters. This idle
action does not take effect unless the program is in call-setup phase at the time
the action is executed.
(8) Control Leads
Control leads C and I may be controlled by spreadsheet action. Press the LEADS action
softkey to bring up the rack of X.211eads shown in Figure 36-8. Press C or I to access
the softkeys that allow you to set a control lead to ON or OFF voltage.
Figure ~ Control leads C and J may be turned on or off via softkey.
(C)Two Phases
The X.211ayer package provides two different "phases" of the transmitter and the
receivers. These phases are called CALL_SETUP and DATA_TRANSFER, and they are
entered into the program via softkey in the ACTIONS softkey rack that branches below
PROTOCL See Figure 36-9.
Fagure 36-9 The X.21 layer package provides two different "phases" of the transmitter and the
receivers, Call Setup and Data Transfer.
The initial configuration phase that the program adopts upon entering Run mode is
selectable on the X.2I Interface Control setup menu. See the documentation that
accompanies OPT -951-13-1. The default program-initiating phase is data transfer.
36-10
SEP '95
36 X.21 Layer 1
1.
Call setup. When the program is in call-setup phase, data is monitored and sent
according to the synchronous format and ASCII code defined above in Section
36.2. Idle display is automatically on. This means that when receivers encounter a
condition that normally would send them out of sync (such as one or more
FF -idle characters), the receivers begin looking for sync as they normally would
but the raw data continues to be displayed, in reverse video.
With idle display automatically on, the transition will appear on the screen as a
series of ~ (NULL) characters when the data lead goes to zero to signal a call
request or a clear request. For this reason, we recommend that the program
adopt CAU._SETUP phase as soon as possible after a clear request or clear
indication is signalled. In this way, the screen display of~ characters will record
the clear request. In data -transfer phase, the steady zero signal will not be
preceded by a special sync pattern and, depending on the line setup, may not be
displayed.
Figure 36-10 shows the INTERVIEW on the user side of the X.21 interface. Here
the INTERVIEW adopts call-setup phase prior to clamping its leads to signal
dte_clearJequesL
Figure 36-11 shows the INTERVIEW on the network -switch side of the X.21
interface. When the user side clears a call, the INTERVIEW programs a change
to call-setup phase prior to clamping its leads to signal dee_clear_confirmation.
The appropriate SEND action in call-setup phase is CAU._SETUP_SEND. See
Section 36.5(A)2. The simple SEND action, appropriate for data -transfer phase,
will not be executed in call- setup phase.
When Layer 1 is in call-setup phase, a SEND action at Layer 2 will be ignored. If
Layer 1 attains data-transfer phase and wishes to notify Layer 2 that it now is
ready to send data, it must do so by SIGNAL action (see Section 31.4), since
primitives are not currently operative at Layer 1.
2. Data transfer. When you press the softkey for DATAJX (Figure 36-9) or type
DATA_TRANSFER in an Actions block on the spreadsheet, you are sending the unit
into data-transfer phase. In this phase, the unit monitors and sends according to
the parameters selected by the user on the Line Setup menu. See Section 5.
The appropriate SEND action in data -transfer phase is entered on the Protocol
Spreadsheet via the SEND softkey labeled SND_DTA. This action is written to screen
simply as SEND. CALL_SETUP_SEND cannot be executed in data-transfer phase.
When Layer 1 is in data-transfer phase, a SEND action at Layer 2 will cause a
transmission to go out onto the line automatically. No SEND action at Layer 1 is
required.
SEP '95
36-11
-------------------------------------------------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
EMULATE USER, USER CALLING AND CLEARING
T
New STATE
ACTIONS
CALL_SETUP
LEADS T ONE C OFF
R
NEW STATE
CONDmONS
LEADS R ONE I 'lAU~ OFF
TONECVALlD_OFF -
ready
calLrequest
LEADS T ZERO CON
LEADS T DATA
CALL_SETUP_SEND'
c
.L-l.. ~ J!.....l. ~
selecDorulignals
RECEIVE srRlNG •
00 + +
RECEIVE srRlNG' •
II!
s"Q23123+
RECElVE STRING'
RECElVE STRING'
"II! /
"II! '"
RECElVE srRING' • fS1
LEADS RONE I VAUD_01"F
dceJlfOllidedJnformation
(calIedJine_identlfication)
dee_wailing
connection)n..P'OQres5
LEADSTOATA
DATA TRANSFER
SEND "link-level data"
CALL SETUP
LEADS T ZERO C OFF
LEAOSTONE
ready
Figure 36·10 In this DTE-caliing-and-cJearing scenario, the INTERVIEW is on
the user (DTE) side of the X.21 interface.
36-12
SEP '95
36 X.21 Layer 1
EMULATE SWITCH, USER CALLING AND CLEARING
T
CQNDmONS
NEW STAIE
R
ACTIONS
NEW STATE
~S~r:'e I OFF
LEADS TONE C VAUO OFF
R ONE I VAUOJ)f'F
RECEIVE STRING' •
c
.L.L Jlt:!....W' .L.l.. ~
I!l
LEADS R SYNCS
dee_wailing
LEAOSTONE
LEADSRONE
LEADS ION
LEAOSRDATA
DATA TRANSFER
SEND "'ink-level data"
f~~OIOFF
LEADS R ONE
LEAOS TONE C VAUD Of'F
R ONE I VAUD_OFF
Figure 30-11 In this DTE-calling-and-clearing scenario, the INTERVIEW is on
the network/switch side of the interface.
36-13
SEP '95
--~---
---------
--------~--------------.-.---------.---'"'-----"-.-----
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
EMULATE USER, USER CALLED AND CLEARED
T
NEW STATE
ACTIONS
c
R
CONDITIONS
NEW STATE
CAll SETUP
LEADS TONE C OFF
lEADS R ONE I VALID_OFF
TONE C VAUO_OFF
ready
LEADSCON
RECEIVE STRING'
RECEIVE STRING'
i!l /
ffl *
dee.J>rO"idedJnformation
(c;a!lingJine)dentilic;a!ion)
connectionInJII'09fI!SS
LEADS T DATA
DATA TRANSFER
SEND-ulink-Ievel data
data_transfer
D
CALL SETUP
LEADS T ZERO C OFf
LEADS T ONE
ready
LEADS R ONE r VAUD_OFF
Figure 36-12 In this DTE-called-and-c1eared scenario, the INTERVIEW is on
the user (DTE) side of the X.21 interface.
36-14
SEP '95
36 X.21 Layer 1
EMULATE SWITCH, USER CALLED AND CLEARED
T
CONomONS
c
R
NEW STATE
NEW STATE
ACTIONS
CAlL SETUP
LEADS R ONE I OFF
!.EADS T ONE C VAUD_OFF
R ONE I VAlID _OFF
LEADS R SYNCS
CAU._SETUP_SENO·
I '\etC.»
LEADRONE
!.EADSION
LEADS R DATA
DATA_TRANSFER data_transfer
SEND
"link-level data~
LEADSRONE
I..EAOSTONECVAlIO_OFF
R ONE I VAlID_OFF
ready
Figure36-13 In this DTE-called-and-cleared scenario, the INTERVIEW is on
the network/switch side of the interface.
SEP '95
36-15
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
36-16
SEP '95
37 X.25 Laver 2
37 X.25 Layer 2
SEP '95
37-1
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
**
DRIVE:
DRIVE:
DRIVE:
IVE:
IVE:
IVE:
IVE:
La~er
La~er
La~er
La~er
La~er
La~er
La~er
Ke~
La!;:1er
tup
**
1 Package:
2 Package:
3 Package:
4 Package:
5 Package:
6 Package:
7 Package:
To Load The Selected Packages
Figure 37·1 The X.25 personality package for Layer 2 is loaded from the
Layer Setup screen.
**
X.25 Frame Level Setup
**
Tl (for INFO frame):
Emulate:
Mode of operation:
Window size:
Enter Window Size (1 to 7) For Outstanding Frame:. 7
-
• •
i 111111 • ••,1-1
Figure 37·2 Protocol Configuration screen for X.25 Layer 2.
37-2
SEP '95
37 X.25 Layer 2
37 X.25 Layer 2
Layer 2 X.25 is a "layer personality package" of functions that are loaded into memory from disk
via the Layer Setup screen. Figure 37-1 shows the Layer Setup screen configured to load in the
Layer 2 X.25 package from floppy-disk Drive 2~ Refer to Section 8 for details on operating the
Layer Setup screen.
The Layer 2 X.25 package consists of the following:
•
A special X.25 Frame Level Setup screen that controls certain parameters when the unit is
tracing or emulating X.25.
•
A protocol trace (illustrated in Figure 37-3) that distills from X,25 data the Level 2 events that
have protocol significance. This trace is accessible by softkey in Run mode at all times.
•
A group of conditions and actions at Layer 2 on the Protocol Spreadsheet that facilitate X.2S
programming. Figure 37-8 shows the softkey path to the first rack of condition softkeys when
the X.25 package is loaded in at Layer 2.
37.1 Frame- Level Setup
The parameters on the X.25 Frame Level Setup screen must be configured correctly for an
accurate t~ce display and for proper emulation.
To bring up this screen, first go to the Layer Setup screen (press ~ lEI). Execute the
X.25 selection at Layer 2: X.25 should appear in the Packages Loaded column. Press @)
(labeled PROTSEL) to bring up a prompt to Select Protocol Configuration Screen. Then press
(@ (LAYER-2) to call up the X.25 Frame Level Setup screen.
The four parameter fields on this screen are shown in Figure 37-2. T1, Emulate, and Window
Size apply to interactive (emulate) tests only. MOde of Operation must be configured
correctly for the protocol trace as well as for proper emulation.
37-3
SEP '95
-
-------,--------,
---------------------------------------,-,--,--
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(A) T1
Enter a four-digit (including decimal point) T1 timeout value in this field. The
largest valid entry is 65.5 seconds. The smallest entry is .001 second, or 1 millisecond.
Tl is the name given to the retransmission timer for INFO frames. When a value is
entered in the 11 field on this menu, the Layer 2 package will handle Tl timings
correctly, as follows:
•
Whenever the INTERVIEW sends an I - frame at Layer 2 and there are no
previous frames sent by the INTERVIEW currently outstanding (unacknowledged),
the timer starts timing down from the value entered on the Frame Level Setup
screen.
•
An acknowledgment by the device under test of the most recent frame
transmitted by the INTERVIEW stops the timer (so that it does not expire).
•
An acknowledgment by the device under test of a frame that is not the most
recent frame transmitted by the INTERVIEW-an "incomplete"
acknowledgment-restarts the T1 timer to the value selected on the
configuration screen.
Expiration of this Frame Level Setup timeout can only be detected by a T1_EXPIRED
condition on the Protocol Spreadsheet at Layer 2. This particular timeout cannot be
detected by a generic condition of TIMEOUT n.
According to the protocol, a T1_EXPIRED condition should result in a RESEND action.
(B) Emulate Logical DTE/DCE
There are two selections in the Emulate field on the X.25 Frame Level Setup screen,
;l~~~~,; and ~~:_~l~,;t'. The entry in this field determines the Layer 2 address
bytes used by the INTERVIEW during interactive testing.
Configured as a logical DTE, the INTERVIEW uses address 01 for commands and 03
for responses. Usually a logical DTE is the PAD at the user site.
Configured as a logical DCE, the INTERVIEW sends commands to address 03 and
responds using address 01 • UsuaHya logical DeE is a network switch.
Use the Mode selection (fn~'i'(i:€~~: orli. .~'r) on the Line Setup menu to
regulate the physical interface-whether to use Pin 2 or Pin 3 to transmit, and so on.
(C) Mode of Operation
The Mode of Operation field refers to the mode of numbering INFO and supervisory
frames. There are two options,
and jg,~~i': .
MOD 8 uses sequence numbers 0-7. MOD 128 adds an extra byte to the control
field in INFO, RR, RNR , REJ, and SREJ frames. See Figure 37-5. This extra byte
allows sequence numbers in a range of 0-127.
37-4
SEP '95
37 X.25 Layer 2
The correct "modulus" must be selected in this field in order to conduct interactive
communications and also to generate an accurate X.25 Layer 2 trace.
(0) Window Size
Any window size may be entered up to the current modulus minus one: 7 or 127.
The window size is the maximum number of unacknowledged I-frames that Layer 2
will buffer for retransmission. When the limit is reached, any further INFO frames
that are named in SEND actions triggered at Layer 2 will be passed to Layer 1 for
transmission but not buffered for retransmission.
The window is a queue that buffers frames for retransmission in case one or more
transmissions are lost or in error. A RESEND action will resend the first (earliest)
frame in the window. Successive RESENDs will send successive frames until there are
no more frames to resend; or until the window is reset by an acknowledgment or by a
RESEND FIRST action.
37.2 Protocol Trace
The Layer 2 X.25 package includes an automatic frame-trace display that summarizes
link-level activity. This trace mode is enabled whenever the unit is in Run mode, both
real-time and frozen.
While the unit is in Run mode, press the softkey for 12TRACE to bring the protocol trace for
X.25 Layer 2 to the screen. (If the X.25 package for Layer 3 is also loaded in, the L2TRACE
softkey will appear after you have pressed PROTOCL, @ on the primary rack of
display-mode softkeys.)
When running in High-Speed Frame Mode, more data could be passed to Layer 2 than
there is room for in the buffer; this will cause an FEB overrun. If this happens, the error
message FE Buffer OVerflowed - Some Frames Lost will appear on the prompt line. The first
time an FEB overrun occurs, an audible alarm will also sound; subsequent reccurrences
will cause only the message to display (without any alarm). The trace will restart again but
some data is lost with each occurrence.
Figure 37-3 is an example of the Layer 2 trace display. Each horizontal row in the trace
represents a frame.
(A) The Protocol Trace in Freeze Mode
Press 8 to prevent the addition of new data to all the display buffers, including the
trace buffers. The frozen trace display may be scrolled through or paged through.
The top line always is the cursor line (though there is no actual cursor on the trace
display). Pressing (IitJ or moves the viewing "window" down relative to the data to
add one line of fresher data to the bottom of the screen. Pressing ~ or ffl moves
the viewing window up to add a line of older data to the top of the screen.
m
37-5
SEP'95
-----._--
_._-_. --
--_._._-------_._._._-----
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Figure 37·3 Each horizontal row on the trace display represents a frame.
Depression of the (BJ key adds ftfteen lines-one full page-of newer frames to the
frozen trace screen. Depression of rm::J adds fifteen lines of older frames.
The frame displayed on the top line of frozen trace-data will appear as the first
frame in the raw-data or data-plus-leads display. To view the raw data that
generated a particular line in the trace display, use ~ or mID (or ff) or 0) to move
the line in question to the top of the screen. Then press one of the data softkeys.
Figure 37-4 shows part of a dual-line data screen in Freeze mode. The ftrst frame in
the display is the same one that is traced at the top of Figure 37-3.
Figure 37-4 Data-display of Protocol Trace shown in Figure 37-3.
37-6
SEP'95
37 X.25 Layer 2
(8) Trace Columns
The columns in the protocol trace for Layer 2 X.25 are explained below.
1.
Source. The SRC column identifies the lead on which the frame was monitored,
TO (OTE) or RD (DeE). This column identifies the physical source of the frame,
not the logical source. The physical OTE uses the TO lead to transmit. The
physical OCE uses RD to transmit.
Just as on the data display, RD data is underlined.
2.
Address. The address octet (see Figure 37-5) is given in the ADDR column, with its
two hexadecimal quartets presented as full-size alphanumerics. The address
may be °1 or 0) in single-link operation.
This column identifies the logical OTE and OCE. The logical OTE uses address
for INFO frames and other command frames, and address °3 for responses. The
logical DCE uses address °3 for INFO frames and other commands, and address
°1 for responses.
°1
3.
Type. The mnemonic (abbreviated) names for eleven frame types as they appear
in the TYPE column of the protocol trace are shown in Figure 37-5 under
"CONTROL." The control field, therefore, indicates the frame type. If a
control octet does not fit any of the patterns in the figure, the frame is listed in
the TYPE column as UNKWN followed by the hexadecimal value of the control byte:
UNKWN=F3.
If the number of bytes in the frame is below the required minimum, the frame is
posted as INVAUO.
4.
SEP '95
N(R) and N(S). One column on the frame-level trace is devoted to N(R) values,
and one column to N(S). The frame types that include N(R) or N(S) fields in
their control fields are indicated in Figure 37-5. N(R) and N(S) occupy three bits
each in modulo 8, seven bits each in modulo 128.
37-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
I
I
I
I
I
I
I
ADDRESS
TOOCE
TODTE
HEX = q~
ASCII=
~
87654321
CONTROL
INFO-MOD 8
I::'~,~
876 543 2 1
87654321
/'
J
INFORMATION
FCS
CONTROL=INFO
Higher-level
Protocol &
0aIa
»
<
>
DO
67654321
"-
"'87854321
87654321
87654321
"-
0
r.O:~ ~e-je_-Cled_oI~F~ield~ ~ t~I=' J
:
87654321
/'
/'
I
I
I
I
I
I
87654321
HEX; 2F or 3F
ASCII = lor?
/'
'"
RR-MOD8
I
OM
:- "1;1 •••
Sz or 'S
ASCII =
876 5 4 3 2 1
i 0 DolFI 1 1 1 1
II 7 6
543 2 1
HEX ..
-lor
CotS
•0 1 1
T)
87654321
I~'
FRMR
ASCII =
B..
mAl
q7
8 7 0(
,
I~I
o
Q
1
876 5 .. 3 2 1
Fa
or
87654321
RNR- MODS
IFI 0 0 1 1
87654321
HEX =
RR - MOO 128
~,D
VA
ASCII ..
'"
RNR - MOD 128
~,D
8 7 6 5 4 3 2 1
DISC
HEX ..
4)
or 5)
87654321
87654321
ASCII .. CorS
REJ - MODS
1 1
I
SARM
HEX = °F
"
I
•
~·
----------J/
a7\i~4~3~?~1--____
r--------""-."
ADDReSS
LENGTH = No.
:t __________ .>
I
'&
CALL USER DATA
,
________ ;,.
81654321
81654321
lYPE = CALLACCEPTED
IADOOEs'S-----j fC'A1.i:ED---"", fCALU,."G----' f~e;---l r--------".. r-;:;;--~'~
f LENGTH .. No. :I II ~
ADDRESS:
<..
I ADDRESS: ,~~" :I No
LENGTH:
: :
,
:
"
I of " •.• ~
'"
,.~ I Quartet :
........._-I I FACILI11ES
.." I USeR
.."
•
........,,,...
, I Binary-'CodeCI ,
I Binary-Coded , I
...... '""""'"
I I
,
I DAe
LS~~~_: l~ ___ .. /
:~ ____ /
~~.IlL ______ .! L _______ /
L
__ ~___ / \
87654321
B
87854321
lYPE = CLEAR REO
CAUSE
1"----------1 1"AO'.•-,;:'S8-----1
o
f'CAum----, f'CAU:iNG----' i'F~nES---l ;--------..... ;--~~--'"
II DIAGNOSTIC II !I 01LENGTH
.. No.
I:
ADDRESS:
\
I ADDRESS: <..., .f LENGTH'
I I
<.. I USER <.........
Qualtets
I I Cluar1et..
(l> I Cluar1e1 ..
No 01 odets
I I FACIUTlES .".- I
I
I I callin
• CaUed I I BinaIy-Coded
I Binary-Coded '( 1'1
II
'I
DATA
L__________! L. ___ j ..! ____..J
____../ t.JrllQWI!____ /
-------.. l_______ ,' 1________
,.'\
87854321
~
87654321
"g,~
87654321
87854321
1YPE .. CLEAR CONFIRM
iAO'ORESi-----i f'CAu.eo,----,. fCAWNG---"', rF;C;~----l r--------'·,
I
I t AOOFIESS'
~'I AlltlAESS'
<,
I I
!
t LENGTH .. No.
I I ...... ~.
~ I ..... _~.
.. I LENGTH:
I I FAClUTIES
'
,
ofQ"~~
I
.... "''''
I " .._ .... z
.... , ......"' .... =
I I Binary-Coded " . I Binary-Coded
LkliWllI!l ____ /
LJ!I!.!!d_~~..J
L~
.... , No olOclelS
I I
.......
I
.
___..;"'"( t9.!i.l.
______ .!I lI ________ ......\
876S4321
87654321
lYPE = INTERRUPT
1= }
EJ
1YPE .. RESET 01' RESTART REO
CAUSE
81654321
r----------1
I
I
: OIAGNOSllC
I
I
...
II
---------_
..
67654321
EJ
I
lYPE= D I A G N O S T I C B D
DIAGNOSTIC
0-----------1
I :
EXPLANATION
I
I
87654321
87854321
87654321
lYPE '" REGISTRATION REO
AOORESS
1"D'cit-----..., rOTe------.. ,
LENGTH '" No.
: ADDRESS:
I Quartet
<....:
ADDRESS:
'.. Ou.trtet =
=
<:
____ ..·""
of Quarte:s
I Binary-Coded
I,...;O.;.T;;;E""",-OC;;.;;;E;;....oJ L~
<"
I
I Binary-Coded (
L~
....
___ ... ,""
I
I
------------_..
,...-----.., ,----------"
REGISTRATION
LENGTH:
I
' ..
: REGISTRATION ,
Octets:L _________,,.<'
~._
of _ _ _--'
.._OL
87654321
87654321
lYPE .. REGISTRATION CONFIRM
EJ
&
87654321
SEP '95
I
~
87654321
_~~
1 .. ............;_No_·_ _
01 Ouart~s
OTE I DeE
87654321
f~!;:---·\. f~~~:---'~> ~~T1ON
I Binary-Coded (
t~
____ .....
I Binary-Coded '(
t~
01 Octets
____ / .....No.
o)"'-I_ _ _ _
:,1~~::~~~~~-'\
I
~ L __________ ,
,,'
87854321
38-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(8) Trace Columns
The columns in the protocol trace for Layer 3 X.25 are explained below.
1. Source. The SRC column identifies the lead on which the packet was monitored,
TD (OTE) or RD (DeE). This column identifies the physical source of the packet,
not the logical source. The physical DTE uses the TD lead to transmit. The
physical DeE uses RD to transmit.
Just as on the data display, RD data is underlined.
2.
LeN. The LeN for each packet is given in this three-column "hex" field. Each
column displays a hexadecimal digit (0 through F) that represents four bits out of
the 12-bit LeN.
3.
Type. The mnemonic (abbreviated) names for seventeen packet types as they
appear in the TYPE column of the protocol trace are shown in Figure 38-6 under
"TYPE." If a Type octet does not fit any of the patterns in the figure, the packet
it listed in the TYPE column as UNKWN followed by the hexadecimal value of the
type byte: UNKWN=03.
If the number of bytes in the packet is below the required minimum, the packet is
posted as INVAUD.
4.
P(R) and P(S). One column on the packet-level trace is devoted to P(R) values,
and one column to P(S). The packet types that include P(R) or P(S) fields in
their control fields are indicated in Figure 38-6. P(R) and P(S) occupy three bits
each in modulo 8, seven bits each in modulo 128.
Figure 38-7 MOD 128 sequence numbers are displayed in two-digit
hexadecimal characters.
38-12
SEP'95
38 X.25 Laver 3
P(R) and P(S) values are presented in decimal format in modulo-8 traces. Each
column displays a single digit that represents a 3-bit binary value (0 through 7).
For modulo 128, the values 00 to'TF are given in "character" format, where the
columns contain a two-digit hexadecimal character (see Figure 38-7).
Note that the Pr and Ps columns on the trace are staggered to suggest four
columns. The two outside columns, comprised of the DTE's peR) value and the
DCE's P(S) value, form a numbering sequence for DCE data packets. The arrows
in Figure 38-8 indicate the sequence: the DCE sends packet 4, the DTE
acknowledges 4 by returning P(R) 5; the DeE sends 5, the DTE expects 6; the
DeE sends 6, the DTE expects 7; the DCE sends 7, the DTE expects 0; the DCE
sendsO.
FJgUre 38-8 Pr and Ps columns are staggered. with the outside columns representing the
sequence of DeE numbered data packets.
The two inside columns reveal a similar pattern for DTE data packets (and DeE
acknowledgements).
5.
Q, D, and M. QDM is a three-column field. If the Q (data -qualified) bit is set in
a data packet, a Q will appear in the Q column for that row. See Figure 38-4 for
examples of this letter-Q display. The position of the Q-bit in the first packet
byte is indicated at the top left of Figure 38-6.
When the D (delivery) bit is set in a Call, Call Accept/Connect, or Data packet,
the letter 0 appears in the D column. The position of the D-bit in the first packet
byte is indicated in Figure 38-6.
SEP'95
38-13
----------------------------._.. -------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
When the M (more) bit is set in a data packet, the letter M appears in the M
column on the trace display. The position of the M-bit in the Type field of data
packets is shown in Figure 38-6.
6. Misc. The Mise field presents up to 16 bytes of character data (decoded in hex)
for all packet types other than data packets that contain data beyond the Type
octet. All such packets and their "miscellaneous" fields are indicated on the right
half of Figure 38-6.
Twelve bytes of "miscellaneous" data were expanded for the Call packet in the
trace in Figure 38-4. The data in this example includes the address-length byte,
four called-address bytes, the facilities-length byte, two facilities bytes, and four
bytes of call-user data.
7.
Size. The number of bytes in each packet is given in this field in four decimal
digits.
8.
Time. The time of the arrival of the end of the frame containing the packet at the
DIE or DCE monitor is provided by a 24- hour clock and posted to the trace
display. The clock is accurate to the milli - or microsecond.
When time values are incorporated in data, times posted to the trace display will
not be affected when recorded data is played back, even at varying speeds. To
incorporate time values into recorded data, make the following selections:
•
. For bit-image data
Data To Record: t11'\If,~f~f; (Record Setup menu; see Section 7)
nme TIcks: ~l!~li (Front-End Buffer Setup screen; see Section 9)
•
For character data
Data To Record: 1~ft
nme Ticks: 1l.B\
or
Data To Record: ~~i~lil;;;!,
Time Ticks:
Frame Timestamps::i¥~r (Front- End Buffer Setup screen; see Section 9)
Timestamp Resolution:
or ~• •
If time values are not incorporated in data during live recording, times on the
trace during playback will be influenced by "local conditions" such as playback
speed, idle suppression, etc.
9.
Frame checking. An X.25 frame ends as soon as a 7£ flag or seven 1-bits in a row
are detected. If a flag ends the frame, a frame check is performed and the result
is posted both to the data display and to the Bee column of the trace display.
The symbol@] denotes a good frame check, while iii symbolizes a bad frame.
II for abort is posted to the trace row when a frame is ended by seven 1-bits.
38-14
SEP '95
38 X.25 Layer 3
38.3 Monitor Conditions
When the Layer 3 X.25 personality package is loaded in (via the Layer Setup screen), a set
of conditions checks DTE and DCE leads both in monitor and emulate modes. This set of
conditions is accessed by the DTE and OCE selections on the first rack of condition softkeys
at Layer 3. See Figure 38-9.
Figure 38-9 Unlike RCV conditions, the softkeys for DTE andDCE are valid when the INTERVIEW is
monitoring the line passively.
After the keyword OTE (or OCE) is written to the spreadsheet, a rack of softkeys appears
that represents types of packets: DATA, RR, RNR, REJ, CAU-, and so forth.
(A) Packet Type
The softkeys for data, supervisory, unnumbered, and "other" packets are illustrated
in Figure 38-10.
Press a wftkey to write one of these packet types to the Layer 3 spreadsheet. OTE or
OCE followed by a packet-type mnemonic-OTE DATA, for example, or DCE CLEAR-is a
complete condition and will come true if a matching packet is monitored. An LeN
condition may be added to the simple packet mnemonic, but it is optional. Other
optional conditions that may apply are Q-bit value, D-bit value, M-bit value, cause
code, and diagnostic code.
NOTE: A packet-type condition will not come true with respect to a
packet that is inside a frame with a bad frame check, or inside an
aborted frame.
1.
Data packets. Data packets differ for MOD 8 and MOD 128 numbering schemes.
(See Figure 38-6.) For spreadsheet conditions to match data packets accurately,
SEP '95
38-15
INTERVIEW BOOO Series Basic Operation: 951-80424-01
the correct numbering system ("Mode of Operation") should be selected on the
Packet Level Setup screen.
Figure 38-10 Packet types.
When DTE or DeE is monitored for a data packet, a specific LeN may be
specified in the spreadsheet condition. A specific value for the Q-, D-, or
M -bit also may be indicated in the rack of spreadsheet softkeys just below DATA.
(Refer to Figure 38-12.)
2.
Supervisory packets. The three supervisory-packet types that can be searched for
on the data leads are RR (Receive Ready), RNR (Receive Not Ready), and
REJect. These packets always contain peR) fields (see Figure 38-6) and serve
mainly to acknowledge or reject data packets.
Like data packets, supervisory packets are constructed differently according to
the numbering scheme, MOD 8 or MOD 128.
When DTE or DeE is monitored for a supervisory packet, a specific LeN may
be specified in the spreadsheet condition. See Figure 38-11.
3.
Unnumbered packets. Unnumbered packets generally assist in call setup, call
management, call clearing, and subscription services.
38-16
SEP '95
38 X.25 Layer 3
The thirteen unnumbered packet types are laid out consecutively from CALL to
DlAG on the softkey racks in Figure 38-10. Because these packets lack P(R) and
P(S) sequence numbers, they are constructed identicany for MOD 8 and MOD
128.
All unnumbered-packet conditions may be made specific to a particular LCN.
Call and ean Confirm conditions may specify a D-bit value (Figure 38-13).
Restart, Reset, Clear, and Registration Confirm conditions may optionally test
for causes and diagnostic codes (see Figure 38-14, Figure 38-15. and
Figure 38-16). Diagnostic packets (F5 on on the bottom rack of softkeys in
Figure 38-10) also may specify a diagnostic code.
4. Other packets. Any packet type may be entered as a hexadecimal value instead of
by name. Press the softkey for OTHER. (See F6 in the bottom rack of softkeys in
Figure 38-10.) Then enter the hex byte in the form of two alphanumerics. Here,
for example, is a Clear Request entered as a hexadecimal:
CONOITIONS: OCE OTHER 13
(8) LeN
All DTE and DCE conditions that name a packet type may specify one particular
LCN (logical channel number) as an added condition. For example, a spreadsheet
condition may be satisfied by any DTE Clear Request packet:
CONDmONS: DTE CLEAR
Or it may be satisfied by a DTE Clear Request packet only if it carries an LCN of,
say, 005:
CONDITIONS: OTE CLEAR LCN= 005
SEP '95
38-17
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Figure 38-11 LCN is the Condition option available for these nine packet types.
Figure 38-11 indicates the packet types that offer LCN as their only Condition
option.
Enter the LCN as one, two, or three hexadecimal digits. Type each digit as an
alphanumericin the range 0-9 andA-F (or a-f): do not use the §J key. Each digit
will represent four bits of the 12-bit LeN. A single-digit or two-digit entry will
represent the low-order bits, with the high-order bits zero-filled. Thus LeN: 005 is
the same entry as LeN= 05 or LeN= 5.
(C) Q, D, and M Bits
Q -, D -, and M - bit values of 0 or 1 may be specified in Layer 3 conditions that
search for DATA packets. See Figure 38-12.
38-18
SEP '95
38 X.25 Layer 3
Figure 38-12 When data packets are monitored, Q, D, and M values of 1 (alongwitb LCN values)
may be specified.
A D-:bit value also may be specified for Call and Call Confirm packets: see
Figure 38-13.
The positions of the Q -, D-, and M - bits in the packet header are illustrated in
Figure 38-6.
SEP'95
38-19
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 38-13 Conditions that look for Call and Call Confirm packets also can test for LeN and
D-bit values.
(0) Cause and Diagnostic Value
Conditions that look for Restart, Reset, Clear, and Registration Confirm packets may
be refined further to test for a particular cause code and/or diagnostic code.
1.
Cause. The names of causes as well as their hexadecimal values are indicated on
the softkey- prompt line near the bottom of the Protocol Spreadsheet screen. To
specify a particular cause, the user does not have to memorize cause codes or
consult a table. The user simply presses @, ROLL, and repeats the keystroke to
cycle through the list of cause names for a given packet type. Figure 38-14 shows
the cycle of causes that pertain to Restart packets. The user presses !TIl, SELECT,
when the right cause has "rolled" up onto the prompt line. The SELECT softkey
writes the current cause onto the spreadsheet screen.
Here is an example of a cause-code entry on the Protocol Spreadsheet:
CONDITIONS: DCE CLEAR CAUSE= NOT_OBTAINABLE
Causes also may be entered into the spreadsheet test as two hexadecimal digits,
as in this example:
CONDITIONS: DeE CLEAR CAUSE= 00
Notice that each digit is an alphanumeric in the range 0-9 and A -F (ora-f): do
not use the ~ key.
38-20
SEP '95
38 X.25 Layer 3
Figure 38-14 A Restart packet may be tested for one of these four causes.
38-21
SEP '95
---------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(a) Reset
causes
Clear
causes
(b)
(c) Registration
Confirmation
causes
Figure 38-15 The various causes available for (aJ Reset, (b) Clear, and
(c) Registration Confirm packets.
38-22
SEP '95
38 X.25 Layer 3
Figure 38-16 These four packet types (plusDiagnostic) aUowyou to enter a diagqostic-code value
as a spreadsheet condition.
2. Diagnostic code. Diagnostic-code values are optional conditions for the
following packet types: Restart, Reset, Clear, Diagnostic, and Registration
Confirm. Figure 38--16 shows the softkey sequences that branch down to the
diagnostic-code condition for most of these packet types.
Enter the diagnostic code as two hexadecimal digits. Type each digit as an
alphanumeric in the range 0-9 and A -F (or a-f): do not use the 8 key. Here is
an example of a spreadsheet condition that specifies both a cause and a
diagnostic code:
DCE RESET CAUSE= LOCAL_PROCEDURE_ERROR DIAGNOSTIC= 01
SEP'95
38-23
- - ---------------------~---.---.-------------"---------
....-------.---
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
38.4 Emulate-Mode Conditions
The remaining conditions are functional only when the Line Setup menu is configured for
Mode: m~.tili!} or ~{~._t~~&
(A) Receive Conditions
Like DTE and DeE conditions, RCV conditions monitor a data path for X.25 packet
types. RCV conditions operate only in emulate modes, and they check only the data
path that the INTERVIEW is not using to transmit. While a RCV condition may look
like a DTE or DCE condition-f!CV DATA a looks the same as DCE DATA Q-there are
important differences that are noted below.
1. Access to the data inteiface. The INTERVIEW is a layered emulator. The
significance of this is that Layer 3 and higher layers have no direct access (in
Emulate modes) to the physical layer, Layer 1. In practice this means that a RCV
condition at Layer 3 does not see packets on the line. It only sees packets that are
delivered up from Layer 2 by a user program at that layer.
(Similarly, a SEND action at Layer 3 does not in itself send a packet out onto the
line. A SEND action merely delivers the packet to Layer 2 -provided that Layer 2
has indicated its readiness to receive data from above.)
The following program is not any sort of complete Layer 2 emulation. It is the
minimum program that must be entered at spreadsheet Layer 2 (with the X.25
personality package installed) in order for a Layer 3 program to have access to
the data line. Once this Layer 2 program is entered, Layer 3 can send packets out
onto the line and receive packets from the line.
LAYER: 2
STATE: datalink
CONDITIONS: DL CONNECT REQ
ACTIONS: Dl CONNECT CONF
CONDITIONS:DL DATA REO
ACTIONS: SEND iNFO "C',,~ ~ '_ .. '':
c_
~ ~ ~=
-
:-
~
i:?C:'=
t>u"1E
~
0003
Figure 38..J4 An interrupt packet has been highlighted.
(6) Suppress
Individual packets that are suppressed in Layer 3 actions are deleted from the trace
display. Figure 38-33 shows the softkey path to SUPPRES.
SEP '95
38-43
- - - -___________
0_'.___
.. _________________
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
38.7 Automatic Primitives
In Section 34, Table 34-2 lists the OSI service primitives that are monitored at the
boundaries of Layer 3 as trigger conditions and sent up to Layer 4, or down to Layer 2, as
user-entered spreadsheet actions. These primitives are layer-specific rather than
protocol-specific and are not part of the personality package for X.25 Layer 3; but a few
of the primitives are set in motion automatically by X.25 Layer 3 spreadsheet actions.
These automatic primitives can be thought of as part of the Layer 3 actions themselves,
and by extension, as part of the X.25 protocol package.
Table 38-1 gives the set ofX.25 Layer 3 actions that have action-primitives built into
them. For example, whenever a GIVE_DATA action occurs at Layer 3, an N_DATA IND
primitive is fotwarded to Layer 4, where an N_DATA IND condition may be waiting to
monitor it.
Table3&-1
Automatic Primitives Generated at X.25 layer 3
X.25
Layer 3
Action
Automatic
Primitive
To
Layer
GIVE..DATA
N..DATAIND
4
SEND {TYPE}
(DL..CONNECT REO*)
DL_DATAREO
2
2
RESEND
(DL..CONNECT REO·)
DL..DATAREO
2
2
*Sent if Layer 2 shows inactive status. DL_DATA REO delayed until
DL..CONNECT CONF returned by Layer 2.
Whenever a SEND or RESEND action is initiated at Layer 3, a DL_DATA REQ primitive is
sent downward along with the DL data (the entire packet). This automatic primitive,
which was nowhere entered by the user as an action at Layer 3, still will cause a DL..DATA
REO condition to be true at Layer 2.
If a SEND or RES END action is triggered at Layer 3 while the data link at Layer 2 is inactive,
Layer 3 will sense the absence of a link and delay the DL_DATA REQ. Instead, it will
send a DL_CONNECT REQ primitive. Only when a DL_CONNECT CONF has been
returned by Layer 2 will Layer 3 release the data and the data primitive.
38-44
SEP '95
38 X.25 Layer 3
38.8 Programming Example: Forcing Data Packets Out on the
Une
This program is constructed around the "line-access" program that was given at the
beginning of Section 38.4(A). It has elements in common with the Layer 2 emulation in
Section 37.9.
The program allows you to send data packets containing fox messages out onto the line
interface (and up on the display) even when you are not connected to another device. In
other words, it allows you to get the feel of layered programming before you attempt a live
emulation.
The bulk of the program is entered at Layer 2. Personality packages for X.25 must be
loaded in at Layers 2 and 3.
Sample Test: Force Data -Packet Transmit:
LAYER: 3
STATE: fox
CONDmONS: KEYBOARD" Ff"
ACTIONS: SEND DATA" «(FOX)) "
LAYER: 2
STATE: UNK
CONDmONS: DL CONNECT REO
ACTIONS: DL CONNECT CONF
NEXT_STATE:info_xfr
STATE: info_xfr
CONDmONS: DL DATA REO
ACTIONS: SEND iNFO" (COL_DATA) "
CONDITIONS: RCV INFO
ACTIONS: SEND RR RESP
GIVE_DATA
CONDITIONS: T1 EXPIRED
NEXT_STATE: xm'Cwodw
STATE: xmt_wndw
CONOmONS: ENTER STATE
ACTIONS: RESEND RRST
CONDmONS: FRAME SENT
MORE TO RESENO
ACTlONS:RESENO NEXT
CONomONS: FRAME SENT
NO MORE TO RESENO
ACTIONS: AlARMNEXT_STATE: info_xfr
SEP'95
38-45
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
At Layer 3, you simply enter a KEYBOARD condition and a SEND action. During Run mode,
you will press the [E] key in order to send a fox message inside a data packet.
The DL_CONNECf REO primitive is sent automatically by Layer 3 before it hands the
first data packet down to Layer 2. The DL_CONNECT CONF action-primitive is
entered "manually" at Layer 2. It is meant to fool Layer 3 into thinking that there is a
link.
When Layer 2 does not receive an acknowledgment to its first INFO frame before a Tl
timeout expires, it resends the INFO frames containing the data packet (containing the
fox message). The RESEND action restarts the Tl timer automatically. Subsequent
timeouts will cause additional resends.
Each time the user presses the [E] key, a new data packet is added to the retransmit window
at Layer 2. With each Tl timeout, the entire window is resent.
38-46
SEP'95
39 SDLe
39 SOLe
SEP'95
39-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
etup
**
La!::jer 1 Package:
La!::jer 2 Package:
La~er 3 Package:
La~er 4 Package:
La~er 5 Package:
La~er 6 Package:
La~er 7 Package:
Ke~
To Load The Selected Packages
Figure 39·1 The SDLC personality package for Layer 2 is loaded from the Layer Setup screen.
**
Idle Timeout:
Emulate:
Mode of Operation:
Window Size:
Emulation Addressing:
DROP
o
ADDR
DROP
1
5
6
7
**
MUL T 1--DROP
ADDR
4
2
3
tup
DROP
8
9
10
ADDR
11
ing _
DROP
12
13
14
15
AD DR
•
Figure 39·2 Protocol Configuration screen for SDLC.
39-2
SEP '95
39 SDLC
39 SOLe
SDLC is a "layer personality package" of Layer 2 functions that are loaded into memory from disk
via the Layer Setup screen. Figure 39-1 shows the Layer Setup screen configured to load in the
SDLC package from floppy-disk, Drive 2. Refer to Section 8 for details on operating the Layer
Setup screen.
The SDLC package consists of the following:
•
A special SDLC Frame Level Setup screen that controls certain parameters when the unit is
tracing or emulating SDLC.
•
Multidrop or point-to-point operation.
•
A protocol trace (illustrated in Figure 39-3) that displays significant SOLC events. This trace is
accessible by softkey in Run mode at all times.
•
A group of conc;l.itions and actions at Layer 2 on the Protocol Spreadsheet that facilitate SDLC
programming. Figure 39-8 shows the softkey path to the first rack of condition softkeys when
the SDLC package is loaded in at Layer 2.
39.1 Frame-Level Setup
The parameters on the SOLC Frame Level Setup screen must be configured correctly for
an accurate trace display and for proper emulation. Use this screen also to enable
multidrop operation.
To bring up this screen, first go to the Layer Setup screen (press S , (§]). Execute the
SOLC selection at Layer 2: SDLe should appear in the Packages Loaded column. Press §)
(labeled PROTSEL) to bring up a prompt to Select Protocol Configuration Screen. Then press
@ (LAYER~2) to call up the SDLC Frame Level Setup screen.
The parameter fields on this screen are shown in Figure 39-2. Idle Tuneout, Emulate, Window
Size, Emulation Addressing, and ADDR apply to interactive (emulate) tests only. Mode of
Operation must be configured correctly for the protocol trace as well as for proper
emulation.
SEP '95
39-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(A) Idle Timeout
Enter a four-digit (including decimal point) timeout value in this field. The largest
valid entry is 65.5 seconds. The smallest entry is .001 second, or 1 millisecond.
Idle timer is the retransmission timer for SDLC INFO and supervisory command
frames. When Emulate:Hiii@i~~;ji,\:::'·lli is selected on the SDLC Frame Level Setup
screen and a value is entered in the Idle Timeout field on this menu, the Layer 2
package will handle timings as follows:
•
Whenever the INTERVIEW sends a command INFO or supervisory frame with
the P-bit set and there are no previous polling frames sent by the INTERVIEW
currently outstanding (unacknowledged) to the same address, the timer starts
timing down from the value entered on the Frame Level Setup screen.
•
An acknowledgment by the secondary of the most recent polling INFO or
supervisory frame transmitted by the INTERVIEW stops the timer (so that it
does not expire). This acknowledgment must occur in a frame with the F-bit set.
•
If F = 0 in the acknowledgment by the secondary of the most recent polling
frame sent by the primary, the idle timer restarts at the value selected on the
configuration screen.
•
An acknowledgment by the secondary of a frame that is not the most recent
polling frame transmitted by the INTERVIEW is an incomplete acknowledgment,
even if F 1. This acknowledgment also will restart the idle timer.
=
Expiration of this Frame Level Setup timeout can only be detected by a T1_EXPIRED
condition on the Protocol Spreadsheet at Layer 2.
(8) Emulate Primary/Secondary
There are two selections in the Emulate field on the SDLC Frame Level Setup screen,
rl:!.~;:":\::'!I and:!!ftf~_~,~.. The difference between these two modes is that the
primary device makes use of the idle timer. The secondary does not.
(C) Mode of Operation
The Mode of Operation field refers to the mode of numbering INFO and supervisory
frames. There are two options, t@~rtr and(fg;t~i.
MOD 8 uses sequence numbers 0-7. MOD 128 adds an extra byte to the control
field in INFO, RR, RNR, REJ, and SREJ frames. See Figure 39-5. This extra byte
allows sequence numbers in a range of 0-127.
The correct "modulus" must be selected in this field in order to conduct interactive
communications and also to generate an accurate SDLC Layer 2 trace.
39-4
SEP '95
39 SDLe
(0) Window Size
Any window size may be entered up to the current modulus minus one: 7 or 127.
The window size is the maximum number of unacknowledged I -frames that Layer 2
will buffer for retransmission. When the limit is reached, any further INFO frames
that are named in SEND actions triggered at Layer 2 will be passed to Layer 1 for
transmission but not buffered for retransmission.
The window is a queue that buffers frames for retransmission in case one or more
transmissions are lost or in error. A RESEND action will resend the first (earliest)
frame in the window. Successive RESENDs will send successive frames until there are
no more frames to resend; or until the window is reset by an acknowledgment or by a
RESEND FIRST action.
(E) Emulation Addressing
Indicate in this field whether the link is Mi_~ or !igw1~~¥t(~;1.
WiR~"
.
For t he INTERVIEW to trackN(R) and
&1".,_";,.",,
~A' ,~.x{ IS thed
efaut lsel ection.
N(S) for multiple addresses, you must choose ~&fu_1i'E'ffi'm;. If you select
r;Hlwtift~&'@' an addl'ti'onal field "
ADDR
-i:.::«;{..<):::;".,
, . will appear..
·",#;:"·;;;.;~"v~:.;:-"..:·;:,,,·~::.:;.:*:~:;'
(F) AOOR
Specify the addresses of particular controllers in the ADDR table. You may enter up to
16 addresses in the table. The INTERVIEW uses the drop number associated with
each listed address to track N(R) and N(S) for resend purposes. All other INFO and
supervisory frames with addresses not included in this table will be tracked as a single
group. All frames will be displayed on the SDLe protocol trace.
Enter each address as a two-digit hexadecimal value. Use the numbered keys only
(not with the G€J key) to make these entries. Addresses in the range 00 through FF
are valid.
NOTE: If you enter multiple addresses in this table, consider
increasing the number of IL buffers. (The default number of buffers is
16.) Use the following formula to determine the number of IL buffers
you may need:
number of buffers = «number of addresses) '" (window size»
+ 3.
See Sections 28.5 and 62.1 for information on changing the number of
ILbuffers.
SEP '95
39-5
----------------------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
39.2 Protocol Trace
The SDLC package includes an automatic frame-trace display that summarizes
link-level activity. This trace mode is enabled whenever the unit is in Run mode, both
real-time and frozen.
While the unit is in Run mode, press the softkey for L2TRACE (@ on the primary rack of
display-mode softkeys) to bring the protocol trace for SDLCLayer 2 to the screen.
When running in High - Speed Frame Mode, more data could be passed to Layer 2 than
there is room for in the buffer; this will cause an FEB overrun. If this happens, the error
message FE Buffer Overflowed - Some Frames Lost will appear on the prompt line. The fIrst
time an FEB overrun occurs, an audible alarm will also sound; subsequent reccurrences
will cause only the message to display (without any alarm). The trace will restart again but
some data is lost with each occurrence.
Figure 39-3 is an example of this trace display. Each horizontal row in the trace represents
a frame.
(A) The Protocol Trace in Freeze Mode
Press ~ to prevent the addition of new data to all the display buffers, including the
trace buffers. The frozen trace display may be scrolled through or paged through.
The top line always is the cursor line (though there is no actual cursor on the trace
display). Pressing OOD or ffi moves the viewing "window" down relative to the data to
add one line of fresher data to the bottom of the screen. Pressing rm:l or I!l moves
the viewing window up to add a line of older data to the top of the screen.
Depression of the mID key adds 15 lines-one full page-of newer frames to the
frozen trace screen. Depression of !Ill adds 15 lines of older frames.
39-6
SEP '95
39 SDLe
DTE
DTE
DTE
DTE
DTE
DTE
DTE
DTE
DTE
C2
C1
C1
C1
C1
C1
C1
C1
C1
SNRM
INFO
INFO
INFO
INFO
INFO
INFO
INFO
RR
7
7
7
7
7
7
7
7
0
1
2
3
4
5
6
1
0
0
0
0
0
0
0
1
0002
0011
0046
0236
0264
0264
0264
0136
0002
2220:06.230
2220:06.276
2220:06.441
2220:07.247
2220:08.151
2220:09.059
2220:09.976
2220:10.445
2220:10.466
@J
@
@
@
@J
@
@
@
@
Figure 39·3 Each horizontal row on the trate display represents a frame.
The frame displayed on the top line of frozen trace-data will appear as the first
frame in the raw-data or data-pius-leads display_ To view the raw data that
generated a particular line in the trace display, use (It) or [lID (or I!l or f.fl) to move
the line in question to the top of the screen. Then press one of the data softkeys.
Figure 39-4 shows part of a dual-line data screen in Freeze mode. The first frame in
the display is the same one that is traced at the top of Figure 39-3.
Figure 394 Data-display of Protocol Trace shown in Figure 39-3.
SEP'95
39-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(8) Trace Columns
The columns in the protocol trace for SDLC are explained below.
1.
Source. The SRC column identifies the lead on which the frame was monitored,
TO (OTE) or RD (OCE).
Just as on the data display, RD data is underlined.
2. Address. The address byte (see Figure 39-5) is given in the ADDR column, with its
two hexadecimal digits presented as full-size alphanumerics.
The address in SDLC always belongs to the secondary.
3. Type. The mnemonic (abbreviated) names for twenty frame types as they appear
in the TYPE column of the protocol trace are shown in Figure 39-5 under
"CONTROL" The control field, therefore, indicates the frame type. If a
control octet does not fit any of the patterns in the figure, the frame is listed in
the TYPE column as UNKWN followed by the hexadecimal value of the control byte:
UNKWN=3F.
If the number of bytes in the frame is below the required minimum, the frame is
posted as INVALID.
4.
N(R) and N(S). One column on the frame-level trace is devoted to N(R) values,
and one column to N(S). The frame types that include N(R) or N(S) fields in
their control fields are indicated in Figure 39-5.
In multidrop operation, each address listed in the table on the Frame Level Setup
screen (Section 39.1) has N(R) and N(S) tracked. All other addresses not
included in the table are tracked as a single group.
N(R) and N(S) occupy three bits each in modulo 8, seven bits each in modulo
128.
39-8
SEP '95
39 SDLC
I·
ADDRESS
CONTROL
INFO-MOO
a
1
6
5
II .,:.sm'
r
~
a
4
3
2
1
816 5 4 321
I I
L-
RR-MOOB
HEX '" 1'1
87
4~
432
1 0 1
87654321
EBCOIC=
If,.
N
00000101
87654321
~
87654321
eBCDIC,.
N
1001
NR
00001001
87654321
~
81654321
8:,
or \-
gorp
EBCOIC '"
1 0 OIFlo 1 1 1
87654321
or
EI3COIC '"
Sz
00
otFh
11~ll
CFGR
HEX., '1' 01'
OS
1 1 1
87654321
(}
"3
(HEX)
111'1001
8765432
0
1 1 1
87654321
HEX .. cF" or °F
EBCOIC.. (HEX)
1 1 ol?ll 1 1
8765432
OISC
TEST
HEX .. "" or 53
HEX .. 1:" or
"3
ESCDIC '" (HEX)
eBCDIC '"
T
Of
01
0'1'10 0 1 1
87654321
1 1
;l~
$)
(HEX)
01 F 10
0 1 1
87654321
HEX=
&"
or
7)
(HEX)
0 0
1
3
t
81654321
RO
~ or
EBCDIC =
I
Dr
SHAME
or
ESCOIC..
00
I~I
I
I
I
I
I
I
GorP
EBCDIC '"
t 1
UP
HEX '" 2)
1 1
87654321
1.Of
&"
EBCOIC., (HEX)
1 0
OM
0".
Hex",
0'
Ir;:;\----S-REJ-...-r~~ I~I
HEX.,
HEX .. "'" or
(HEX)
011'10 11
8165432
EaCOIC '"
87654321
or
00
HEX",
1>0
or 1.,.
ESCOIC.. ~
SREJ-MO08
HEX:
1
$1M
°7
HEX",
...8...5 .. 3 2 1
128
or ~
mor (HEX)
00 01F1 0 1 1 1
87654321
REJ-MO08
HEX: ?Cj
C or
RIM
°7
HEX=
RNR-MOOI28
rro;'\oH-EX-"-Os--'
"3
or
93
1 0 0'1'10 0 1 1
81654321
0
RNR-MOD8
N
SNRM- - - - - , .
HEX..
NR
P
87654321
81654321
ESCOIC '"
RR-MOO 128
87654321
0000
81654321
-----
Ul
;o
87654321
Il=-I 0" ~
And here is a SEND action that includes a full complement of optional fields,
including a string:
ACTIONS: SEND INFO ADR= C3 P/F= 0 NR= AUTO NS= AUTO
04,00°200°0°0°3"00015 This is user data,iS' GDBCC
Most ASCn - keyboard, control, and hexadecimal characters are legal in a
send-string. Special keys (§), [lID, ~) are not legaL Refer to Table 33-2.
To insert a canned fox message into a transmit string, type FOX inside double
parens, as follows: (CFOX)) • Remember that the double parens are special
characters produced by the S-~ and §g-® combinations. Constants,
counters, and flags can also be embedded in a string. See Section 33, Strings.
to.
Bee. There are three BCC options for every SEND action at Layer 2 SDLe. One
of the options, GDBCC, is the default. Any frame that does not request a bad BCC
or an abort will have a good frame-check sequence calculated for it and
appended to it. BCC also is an option for SEND actions at Layer 1; but it does not
occur at Layer 3 or higher.
The three softkey selections for BCC are shown in Figure 39-25. A 16-bit
CeITT frame check is selected automatically for BOP protocols and cannot be
changed or disabled. A bad BCC will be CRC-16 instead of CCITI.
SEP '95
39-27
INTERVIEW 8000 Series Basic Operation: 951-80424-01
When ABORT is the Bee selection, instead of appending a proper frame check,
the transmitter will hold the lead at mark for eight bits (or longer if the
transmitter is idling FF ). Inside a frame, seven 1-bits in a row are sufficient to
signal an abort.
Figure 39-25 Type of Bee is a SEND option for frames at Layer 2.
(8) Give Data
the first rack of action softkeys (refer to Figure 39-18).
This action takes the I -field from a received INFO frame and passes it up to Layer 3
along with a DL_DATA IND primitive. (See Figure 34-5 in the section, OSI
Primitives on the Protocol Spreadsheet.) In an emulate mode,. data is delivered up to
Layer 3 only by one of two actions at Layer 2: GIVE_DATA, or else a DL_DATA IND
primitive followed by the data string.
GIVE_DATA is the (W action on
(e) Resend
The RESEND function is mapped to §] on the second layer of action softkeys at Layer
2 for SDLC. See Figure 39-26. A RESEND action will resend the first frame in the
window. The window is a queue that buffers INFO frames for retransmission in case
one or more transmissions are lost or in error.
The first frame in the window always is the earliest outstanding (unacknowledged)
frame. Every time an acknowledgment is received, the window is cleared to the
extent of the acknowledgment and a new "first-frame" position is established. The
first RESEND after an acknowledgment always sends the first window frame.
39-28
SEP '95
39 SDLe
Figure 39·26 The RESEND action allows you to recover from sequence errors.
The second and subsequent RESENOs following an acknowledgment also will send the
first window frame, provided that the keyword FIRST is appended directly to the
RESENO entry. Otherwise, they send the NEXT (second) and subsequent window
frames_ Figure 39-27 shows the position of the the resend "pointer" after four
consecutive RESEND actions. RESEND NEXT is the default resend when neither FIRST nor
NEXT is specified.
39-29
SEP '95
--~-.-~------
..
-~
..
~----~--~------.-.--.-
-----_.._----,._._-----
.. - .........
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
FRM6
FRM7
--------------
............-
FRMO
FRM 1
WINDOW
FRM 2
. - pOinter moves
to here after
four RESEND NEXTs
FRM3
FRM4
Window moves to here
after FRM 7 is acknowleged
(NR=O); pointer resets to
"first in window" position
Figure 39-27 Resends cause the pointer to move, while acknowledgments move the pointerand the
entire window.
The resend -pointer is reset to the beginning of the window automatically by any
acknowledgment, or by a RESEND FIRST action in the spreadsheet program.
1.
Resend first/next. RESEND FIRST means that the resend - pointer is reset to the
beginning of the window, the flrst frame in the window is resent, and the pointer
is advanced to the second position in the window. The effect of a RESEND FIRST
action is illustrated in Figure 39-28.
The RESEND FIRST action makes it possible for you to resend all the frames in the
window one by one, and then resend them again if necessary.
2. ADR =. Although not strictly required, you should designate the controller
address of the resend frame. Two-digit hexadecimal values in the range 00
through FF are valid.
There is also a LOOPBAK softkey selection for the address field. This selection
causes the RESEND action to refer to the address of the most recently received
frame.
If you selected Emulation Addressing:
on the SDLC Frame Level
Setup screen, you also should have entered controller addresses in the table
immediately below. (See Section 39.1.) The IN1ERVlEW tracks N(R) and N(S)
for each address on the table. It can resend frames to any of these addresses, but
only if you complete the ADR= entry. Then, the INTERVIEW will resend the
appropriate frame from that address' transmit window. If you bypass the ADR=
softkey selection or specify an address which does not appear in the table, the
INTERVIEW will not resend to any address.
39-30
SEP '95
39 SDLC
When Emulation Addressing: !WI_~~i;~; is the selection, you sbould still enter
an address. The INTERVIEW will not necessarily default to the appropriate
address.
3. PIP=. The P/F-bit in the resend-frame can be set to zero or one by this
optional action. (Default is 1 in a RESENO action.)
FRM6
-
-
-
-
-
-
-
-
-
-
-
-
-
FRM 7
-
......- pointer moves to here
after RESEND FIRST
action resends FRM 6
FRMO
WINDOW
FRM 1
FRM2
FRM3
FRM4
~
pointer is here
after seven
RESEND NEXTs
Figure 39-28 RESEND FIRST resets the pointer, allowing you to resend the entire window
repeatedly.
(0) Reset N(R) and Reset N(S)
the (0 and ®l actions on the second rack of action
softkeys for SDLC. (Refer to Figure 39-26.) The sequence-number fields in
I-frames and supervisory frames can be reset by these two Protocol Spreadsheet
actions. Sequence numbers are not reset automatically during a test by any frame
that is sent or received.
RESET_NR and RESET_NS are
RESET_NS also clears
the transmit window.
If you press RSET_NR or RSET_NS, another softkey rack will be presented.
1. ADR=. Although not strictly required, you should designate a specific controller
address. Two-digit hexadecimal values in the range 00 through FF are valid.
There is also a LOOPBAK softkey selection for the address field. This selection
causes the RESET_NR and RESET_NS actions to refer to the address of the most
recently received frame.
SEP '95
39-31
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
If you selected Emulation Addressing:
on the SDLC Frame Level
Setup screen, you also should have entered controller addresses in the table
immediately below. (See Section 39.1.) The INTERVIEW tracks N(R) and N(S)
for each address on the table. It can reset N(R) or N(S) for any ofthese
addresses, but only if you complete the ADR= entry. Then, the INTERVIEW will
reset N(R)-or N(S)-for that address only. If you bypass the ADR= softkey
selection or specify an address which does not appear in the table, the
INTERVIEW will not reset N(R)-or N(S)-for any address.
When Emulation Addressing: t~~m~lii is the selection, you should still enter
an address. The INTERVIEW will not necessarily default to the appropriate
address.
39.6 Display Actions
ENHANCE and SUPPRESS pertain to lines of data on the Layer 2 protocol trace (see Section
39.2). They do not suppress and enhance data on the raw-data display. Raw data is
enhanced and suppressed at Layer 1.
DTE, DCE, and RCV conditions can trigger an ENHANCE or SUPPRESS action. These conditions
are active when the INTERVIEW is in monitor mode or in either of the emulate modes.
(A) Enhance
Whenever a DTE, DCE, or RCV condition comes true at Layer 2, the frame that satisfied
the condition can be enhanced on the SDLC protocol-trace display, or it can be
deleted from the trace completely. In an actions block on the Protocol Spreadsheet,
press the ENHANCE softkey-@ on the third rack of action softkeys. Figure 39-29
shows the three softkey subselections beneath ENHANCE. They are REVERSE, BUNK, and
ww.
Reverse-image and blink enhancements affect the plasma-display screen. In
addition, a low-intensity enhancement can be applied to screens that are transmitted
to a black-and-white monitor connected at the RS-170 port at the rear of the
INTERVIEW.
Reverse, blink, and low enhancements can be mapped to colors on a color monitor
attached at the INTERVIEW's RGB port (Figure 1-6). See Section 18.2 for an
explanation of how reverse, blink, and low enhancements relate to character and
background colors in the RGB output.
39-32
SEP'95
39 SDLC
Figure 39-30 shows one screen of a Layer 2 protocol trace in which DTE SNRM
frames have been enhanced in reverse video. The trigger that caused this
enhancement was as follows:
CONomONS: OTE SNRM
ACTIONS: ENHANCE REVERSE
(8) Suppress
Individual frames that are suppressed in Layer 2 actions are deleted from the trace
display_ Figure 39-29 shows the softkey path to SUPPRES.
Figure 39"29 Selected frames on the protocol trace may be enhanced (or suppressed).
SEP '95
39-33
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
DTE
DTE
DTE
DTE
DTE
DTE
DTE
DTE
C1
C1
C1
C1
C1
C1
C1
C1
INFO
INFO
INFO
INFO
INFO
INFO
INFO
RR
7
7
7
7
7
7
7
7
o
1
2
3
4
5
6
o
o
o
o
o
o
o
1
0011
0046
0236
0264
0264
0264
0136
0002
2220:06.276
2220:06.441
2220:07.247
2220:08.151
2220:09.059
2220:09.976
2220:10.445
2220:10.466
FIgUre 39·30 Set Normal Response Mode (SNRM) commands have been enhanced
on the DTE side.
39.7 Automatic Primitives
In Section 34, Table 34-2 lists the OSI service primitives that are monitored at the
boundaries of Layer 2 as trigger conditions and sent up to Layer 3, or down to Layer 1, as
user-entered spreadsheet actions. These primitives are layer-specific rather than
protocol-specific and are not part of the personality package for SDLC; but a few of the
primitives are set in motion automatically by SDLC spreadsheet actions at Layer 2. These
automatic primitives can be thought of as part of the Layer 2 actions themselves, and by
extension, as part of the SDLC protocol package.
Table 39-1 gives the set of SDLC actions that have action -primitives built into them. For
example, whenever a GIVE_DATA action occurs at Layer 2, a DL_DATA IND primitive is
forwarded to Layer 3, where a DL_OATA !NO condition may be waiting to monitor it.
Whenever a SEND or RESEND action is initiated at Layer 2, a PH_DATA REO primitive is
sent downward along with the PH data (the entire frame).
If a SEND or RESEND action is triggered at Layer 2 while the physical connection at Layer 1
is inactive, Layer 2 will sense the absence of a physical connection and delay the
PH_DATA REO. Instead, it will send a PH_ACTIVATE REO primitive. Only when a
PH_ACTIVATE CONF has been returned by Layer 1 will Layer 2 release the data and the
data primitive.
39-34
SEP '95
39 SDLe
NOTE: The RS-232 interface does not distinguish active/inactive
status at the physical level. This interface returns PH_ACfIVATE
CONF automatically whenever it sees PH_ACTIVATE REO.
Table 39-1
Automatic Primitives Generated at layer 2 SOle
SDLC
Layer 2
Action
*
Primitive
To
Layer
Dl_OATAIND
3
Automatic
SEND {TYPE}
(PH_ACTIVATE REO")
PH_DATA REO
RESEND
(PH_ACTIVATE REO*)
PH_DATA REO
1
Sent if Layer 1 shows inactive status. PH_DATA REO delayed until
PH_ACTIVATE CONF returned by Layer 1.
SEP '95
39-35
------_.__._._------_.
INTERVIEW 8000 Series Basic Operation: 951-80424-01
39-36
SEP'95
40 SNA
40 SNA
SEP '95
40-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
La~er
La~er
La~er
La~er
La~er
La~er
La~er
Ke~
La8er
tup
**
Selections
1 Package: NO PACKAGE
2 Package: SNA
3 Package: NO PACKAGE
4 Package: NO PACKAGE
5 Package: NO PACKAGE
6 Package: NO PACKAGE
7 Package: NO PACKRGE
To Load The Selected Packages
Figure 40-1 The SNA personality package for Layer 2 is loaded from the Layer Setup screen.
**
tup
Idle Timeout:
Emulate:
Mode of Operation:
Window Size:
Using LU 6.2?
Host Port:
Emulation Addressing:
DROP
0
1
2
3
ADDR
DROP
**
U~T:::-:JROP
ADDR
DROP
4
8
5
6
7
10
11
ADDR
9
ing
DROP
12
13
14
ADDR
15
••
Figure 40-2 Protocol Configuration screen for SNA.
40-2
SEP '95
40 SNA
40 SNA
SNA is a "layer personality package" of functions that are loaded into memory from disk via the
Layer Setup screen. Figure 40-1 shows the Layer Setup screen configured to load in the SNA
package from floppy-disk, Drive 1. Refer to Section 8 for details on operating the Layer Setup
screen.
The SNA package consists of the following:
•
A special SNA Frame Level Setup screen that controls certain parameters when the unit is
emulating SDLC or tracing SNA and SDLe.
•
Multidrop or point-to-point operation.
•
A group of conditions and actions at Layer 2 on the Protocol Spreadsheet that facilitate SDLe
programming. This is the same set of conditions and actions that is documented in Section 39 of
this manual. Refer to Section 39 for a discussion of the spreadsheet conditions and actions that
are specific to the SDLe and SNA Layer-2 packages.
•
A protocol trace (illustrated in Figure 40·3) that distills from SNA data the SDLe and SNA
events that have protocol significance. This trace is accessible by softkey in Run mode at all
times.
40.1 Frame-Level Setup
The parameters on the SNA Frame Level Setup screen must be configured correctly for an
accurate trace display and for proper emulation. Use this screen also to enable multidrop
operation.
To bring up this screen, first go to the Layer Setup screen (press 8, [ffi). Execute the
SNA selection at Layer 2: SNA should appear in the Packages Loaded column. Press (ill
(labeled PROTSEL) to bring up a prompt to Select Protocol Configuration Screen. Then press
@ (LAYER-'-2) to call up theSNA Frame Level Setup screen.
The parameter fields on this screen are shown in Figure 40-2. Idle TImeout, Emulate, Mode of
and ADDR are covered in Section 39.1 and will
not be discussed here.
Operation, Window Size, Emulation Addressing,
Using LU 6.21 allows you to set
up the SNA trace to monitor LV 6.2 sessions correctly. The
default selection in this field is
Selection
or
in the Host Port field allows the SNA protocol trace to
distinguish properly between two kinds of FMD headers-NS headers and FM
headers-in SNA Request Units.
SEP'95
40-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
40.2 SOLe Conditions and Actions
The same set of special conditions and actions documented for the SDLC Layer 2 package
is implemented on the Protocol Spreadsheet in SNA. Refer to subsections 39.3 through
39.7.
40.3 Protocol Trace
The SNA package includes an automatic real-time trace that summarizes link-level, TH,
RH, and RU activity. This trace mode is enabled whenever the unit is in Run mode, both
real-time and frozen.
While the unit is in Run mode, press the softkey for L2TRACE (@ on the primary rack of
display-mode softkeys) to bring the protocol trace for SNA to the screen. Figure 40-3 is
an example of this trace display. Each DTE or DeE entry on the SNA trace marks the
beginning of a frame.
In both Run and Freeze modes, the trace may be displayed as either hexadecimal data or
text code data. The text code will be that selected on the Line Setup menu. Press [§ to
toggle between the two display formats. You may print the Protocol Trace from Freeze
mode in either hexadecimal or text code format. (See also Section 16.)
When running in High-Speed Frame Mode, more data could be passed to Layer 2 than
there is room for in the buffer; this will cause an FEB overrun. If this happens, the error
message FE Buffer OVerflowed - Some Frames Lost will appear on the prompt line. The ftrst
time an FEB overrun occurs, an audible alarm will also sound; subsequent reccurrences
will cause only the message to display (without any alarm). The trace will restart again but
some data is lost with each occurrence.
(A) The Protocol Trace in Freeze Mode
Press 8 to prevent the addition of new data to all the display buffers, including the
trace buffers. The frozen trace display may be scrolled through or paged through.
The top line always is the cursor line (though there is no actual cursor on the trace
display). Pressing ~ or (±J moves the viewing "window" down relative to the data to
add one line of fresher data to the bottom of the screen. Pressing I1ill or I!l moves
the viewing window up to add a line of older data to the top of the screen.
Depression of the (=:J key adds 16lines-one full page-of newer trace data to the
frozen trace screen. Depression of ~ adds 16 lines of older data.
The frame displayed on the top line of frozen trace-data will appear as the first
frame in the raw-data or data-plus-leads display. To view the raw data that
generated a particular line in the trace display, use lIJ or ~ (or ff) or 0) to move
the line in question to the top of the screen. Then press one of the data softkeys.
40-4
SEP '95
40 SNA
TIME=1142:22.793
ADDRESS=C1 FRAME TYPE=INFO NR=0 NS=2 P/F=0
TRANSMISSION HEADER (TH)
FID TYPE=2 MPF=ONL Y EFI =0 DAF=oo OAF=o2 SNF=oooo
REQUEST HEADER CRH)
RU CATEGORY=FMD FI=l SDI=0 CHAIN=ONLY DRlI=l DR2I=0 ERI=0
QRI=0 PI=0 BBI=0 EBI=0 CDI=0 CSI=0 EDI=0 PDI=0
REQUEST UNIT (RU)
TYPE=NOTIFY (SSCP--)LU)
lID
BYTES=0002
TIME=1142:22.800
ADDRESS=S FRAME TYPE=SNRM P/F=l
DTE:.- - _ _
lID
BYTES=0014
TIME=1142:22.834
ADDRESS=c1 FRAME TYPE=INFO NR=2 NS=l P/F=0
:,.
3
•
Figure 40-3 Each DTE or DeE entry on the SNA trace marks the beginning of a frame.
(8) Trace Fields Common to All Frames
1.
Source. On the initial line in each frame expansion, the source of the frame (OTE
or DCE) is identified. This is the only field on the frame-trace that begins at the
left border of the screen, and it acts as a visible separator of frame expansions
that take up varying amounts of display space. Note on the screen in Figure 40-3
that two whole frame expansions and part of a third are presented.
In the leftmost ("Source") column in the trace, DCE is always underlined.
2.
SEP '95
Character data. Character data decoded in hexadecimal is presented in reverse
video immediately following the source field. See Figure 40-3. Character data is
presented in blocks separated by spaces. These blocks correspond to the
following protocol fields:
•
Frame header
•
Transmission header (TH)
•
Request/response header (RH)
•
Request/response unit (RU)
40-5
INTERVIEW 8000 Series Basic Operation: 951-80424-01
When an individual block is longer than ten bytes, another separator is used: the
vertical bar (: ). Bars occur after every ten bytes within a block. Note the bar in
the RU block of the DCE frame at the top of Figure 40-3.
The hex-character display does not exceed two lines on the trace, or 70 bytes of
RU.
Note that the four protocol blocks may not be present in every unit. Non - Info
frames have only the frame header. Middle- and last-segment messages lack
the RH block. Many response messages lack the RU.
3. Frame checking. An SDLC frame ends as soon as a 7e flag or seven 1-bits in a
row are detected. If a flag ends the frame, a frame check is performed and the
result is posted both to the data display and to the BeC field on the first trace
line for the frame. The symbol@} denotes a good frame check, while.
symbolizes a bad frame. II for abort is posted to the displays when a frame is
ended by seven I-bits.
4. Size. The number of bytes in each frame is given in the BYTES= field in four
decimal digits. The count begins with the address byte and excludes the
two-byte FCS. Frames without I -fields show a byte-count of two.
Time. The time of the arrival of the end of the frame at the DTE or DCE monitor
is provided by a 24- hour clock and posted to the trace display. The clock is
accurate to the milli - or microsecond.
5.
When time values are incorporated in data, times posted to the trace display will
not be affected when recorded data is played back, even at varying speeds. To
incorporate time values into recorded data, make the following se1ections:
•
For bit - image data
Data To Record:
Time Ticks:
•
(Record Setup menu; see Section 7)
(Front-End Buffer Setup screen; see Section 9)
For character data
Data To Record: ·.~~F
Time Ticks:
or
Data To Record: f;.i~_
Time Ticks:
Frame Timestamps:
Timestamp Resolution:
40-6
(Front- End Buffer Setup screen; see Section 9)
or
SEP '95
40 SNA
If time values are not incorporated in data during live recording, times on the
trace during playback will be influenced by "local conditions" such as playback
speed, idle suppression, etc.
6. Address. The address byte is given as a hexadecimal character (from 00 to FF ) in
the ADORESS= field.
7. Frame type. The mnemonic (abbreviated) name for the frame type is given in the
FRAME TYPE= field.
8. PIP. The status of the poll or the final bit is given in the P/F= field.
(C) Other Trace Fields
Most of the fields on the SNA trace are not common to all frames, but are specific to
the type of frame (Info, for example), FID type, request messages, response
messages, R U type, and so forth. These fields are included in Table 40-1.
SEP '95
40-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Table 40-1
Fields in SNA Trace Display
Mnemonic
Name
Meaning
Data Columns
# cols value each
in field
column
Frame header
(SOURCE=)
(Bec=)
lID,lI,.
0-9
0-9
time of end offrame. given as hhmm:ss.mmm
BYTES=
TlME=
ADDRESS=
FRAMETYPE=
NR= (mod 8)
number (next) receive frame
NR= (mod 128)
number (next) receive frame
2
O-F
NS= (mod 8)
NS= (mod 128)
P/F=
number (frame) sent
number (frame) sent
polf/final
2
O-F
O-F
4
9
DTE,DCE
ASCII
symbol
°O_FF
ASCII
O-F
SNRM, INFO, etc.
present only if frame type=info, rr, mr, rej, or
srej
present only if frame type=info, rr, mr, rej, or
srej
present only if frame type=info
present only if frame type=info
0-1
Transmission header. FID Q or 1
FlO TYPE=O, 1
MPF=
EFI=
OAF =
format identifier
mapping field
expedited flow indicator
destination address field
OAF=
SNF=
origin address field
sequence number field
DCF=
data count field
ASCII
0-1
2
00 _Fr
2
2
2
°O_FF
10-byteth
MIDDL, LAST, FIRST, ONLY
0= normal 1 =expedited
00 _F,
°0-".
Transmission header. FID 2
FIDTYPE=2
MPF=
EFt=
OAF=
format identifier
mapping field
expedited flow indicator
destination address field
OAF=
SNF=
Origin address field
sequence number field
ASCII
0-1
6-byte th
MIDDL, LAST, FIRST. ONLY
O=normal 1 =expedited
00 _FF
1
00 _FF
2
00 _FF
Transmission header. FlO 3
FIDTYPE=3
MPF=
EFI=
SESSION=
LAF=
40-8
format identifier
mapping field
expedited flow indicator
ASCII
0-1
ASCII
local address field
6
2-byteth
MIDDL, LAST, FIRST, ONLY
0= normal 1 =expedited
SSCP-PU, SSCP-LU, RESERVD, LU-LU
0-1
SEP '95
40 SNA
Table 40-1 (continued)
Fields in SMA Trace Display
Mnemonic
Name
Data Columns
#: cols
in field
Meaning
value each
column
Transmjssion header. FlO 4
26-byteth
FlO TYPE =4
TGSI=
VRSI=
VRPCI=
NP=
IERN=
ERN=
VRN=
TPF=
VRCWI=
TGNFI=
VRSTl=
format identifier
transmission group sweep indicator
er & vr support indicator
virtual route pacing count indicator
network priority
initial explicit fOute number
explicit route number
virtual route number
transmiSSion priority field
vr change window indicator
tg non-fifo indicator
vr sequence & type indicator
TGSNF=
VRPRQ=
VRPRS=
tg sequence number field
virtual route pacing request
virtual route pacing response
VRCWRI=
VRRWI=
vr change window reply indicator
virtual route reset window indicator
VRSSN=
DSAF=
virtual route send sequence number
destination subarea address field
3
O-F
4
00_",
OSAF=
SNAI=
origin subarea address field
4
00 _FF'
sna indicator
1
0-1
MPF=
EFI=
DEF=
mapping field
expedited flow indicator
destination element field
1
2
0-1
OEF=
origin element field
2
00 _FF
SNF=
sequence number field
2
DO_F.
DCF=
data count field
2
1
1
1
1
0-1
0-1
0-1
0-1
O-F
O-F
O-F
1
1
0-3
0-1
0-1
0-3
3
O-F
0-1
0-1
0-1
0-1
ASCII
°O_F.
00 _,.
1 =piu order maintained in tg
1 =one or more nodes does not support er, vr
Oavr pacing count not equal to zero
1 =piu flows at network priority, not tpf
same as vm
em + vm + tpf == vrid
Q-Iow 1=medium 2=high
O=increment 1 =decrement
O=tg fifo required
O=nonseq. nonsupv 1 =nonseq. supv
2=singly seq
used when tgnfi=:Q
1=vr pacing response requested
1=vr pacing response sent in response to
vrprq=1
when vrprs=1. O=increment 1=decrement
O=do not reset
1 =reset window to minimum size
piu sequencing for vrsti=2
cIsaf + osaf + vm = vr
O=destination is non-sna device, convert to
fld 0
MIDDL, LAST, FIRST, ONLY
O=normal 1=expedited
dsaf + daf = destination network address
osaf + oaf = origin network address
biu sequence number, segments have same
snf
biu or biu segment length for piu blocking
Transmission header. FlO F
FIDTYPE=F
CF=
format identifier
command format
CT=
CSN=
command type
command sequence number
DCN=
data count number
SEP '95
26-byteth
00 _FF
°1
1
00 _F.
01
2
00 _".
2
00 _F'F
=tg snf wrap acknowledgment
40-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Table 40-1 (continued)
Fields In SNA Trace Display
Mnemonic
Name
Data Columns
# cols value each
in field
column
Meaning
Request header
RU CATEGORY=
FI =
format indicator
SOl =
CHAIN =
OR1I=
sense data indicator
OR21=
definite response 2 indicator
ERJ=
exception response indicator
ORI=
PI ==
B81=
E81=
queued response indicator
pacing indicator
begin bracket indicator
end bracket indicator
CDI=
CSl=
EOI=
POI =
CEBI",
change direction indicator
code selection indicator
enciphered data indicator
padded data indicator
conditional end bracket indicator
definite response 1 indicator
ASCII FMO, NC, DFC, SC
1
0-1
ru category=fmd, lu-Iu session:
1=fm header follows
ru category==fmd, sscp session:
O=character-coded ru 1 =field-fonnatted ru
ru category=nc, dfc, so: fi always == 1
0-1
1 =sense data included
ASCII
MIOOL, LAST, FIRST, ONLY
0-1
O=no response requested (but may be
requested by dr2i)
1 =response requested
0-1
O=no response requested (but may be
requested by dr1i)
1 response requested
0-1
if response requested by dr11 or dr2i
O=definite response 1 =exception response
1
0-1
O=bypass tc queues
0-1
1 = pacing request
0-1
1 == begin bracket
0-1
configured for non-LU 6.2 (see Sec. 40.1),
1 = end bracket
0-1
1 =change direction
0-1
O=code 0 1 ""code 1
0-1
1 =ru is enciphered
1 =ru was padded before enciphennent
0-1
configured for lu 6.2,
0-1
1= conditional end bracket
=
Response header
RU CATEGORY=
FI=
format indicator
SOI=
CHAIN=
ORlI=
OR2I=
RTI=
ORI=
definite response 1 indicator
definite response 2 indicator
response type indicator
queued response indicator
PI=
pacing indicator
40-10
sense data indicator
ASCII FMO, NC, DFC, SC
1
0-1
ru category=fmd, lu-Iu session:
1=fm header follows
ru category:::;fmd, sscp session:
0= character-coded ru 1=field-formatted ru
ru category=nc, dfc, sc: fi always = 1
0-1
1 =sense data included
ASCII
ONLY
0-1
1 =drii response
1 =dr2i response
0-1
0-1
O=positive response 1 =negative response
0-1
O=response bypasses tc queues
1 =enqueue response in tc queues
0-1
1 = pacing response
SEP '95
40 SNA
Table 40-1 (continued)
Fields in SNA Trace Display
Mnemonic
Name
Data Columns
# coIs value each
in field
column
Meaning
Request unit
(REQUEST CODE=)
ASCII
ACTLU, BIND, etc. (present if ru category=nc,
(FMD NS HEADER=)
ASCII
(FM HEADER) 1YPE=
0-9
(BIND1YPE=)
ASCII
CONTACT, NOTIFY. etc. (sscp session only:
present if ru category=fmd and fi=1)
lu-Iu session only: present if
ru category=fmd andfi=1
NEGOTIABLE, NONNEGOTIABLE (this field
and remaining request-unit fields present
only if request code: bind)
c:Ifc, or sc)
FM PROFILE =
TSPROFILE=
FM USAGE PRIMARY LU PROTOCOLS
FOR FM DATA=
FM USAGE SECONDARY LU PROTOCOLS
FORFM DATA=
1
1
00 _1'1'
2
6
6
00_1'1'
TSUSAGE=
MAX RU FROM SLU=
MAX RU FROM PLU=
6
FM USAGE COMMON LU PROTOCOLS=
00
_f'r:
0-9,
UNKNOWN
0-9,
UNKNOWN
°0_'"
PSPROFILE=
PS CHARACTERISTICS
11
°
USER COUNT
1
°0 _FF
length of user data in bind ru
(REQUEST CODE=)
ASCII
(FMD NS HEADER=)
ASCII
ACTLU, BIND, etc. (present if ru category=nc,
c:Ifc, or sc)
ADDUNK, CDINIT, etc. (present if
ru category=fmd and fj = 1)
this and the following 3 fields present only if
0 _1'1'
Response unit
SENSE DATA=
4
sdi=1
CATEGORY".
ASCII
USER SENSE DATA ONLY,
REQUEST REJECT, REQUEST ERROR.
STATE ERROR, RH USAGE ERROR,
PATH ERROR
MODIFIER=
SENSE INFORMATlON=
SEP'95
2
40-11
---.~--~--------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
40-12
SEP '95
41 DDCMP Laye' 1
41 OOCMP Layer 1
DDCMP is a "layer personality package" of functions loaded into memory from disk via the Layer
Setup screen. Figure 41-1 shows the Layer Setup screen with the DnCMP package loaded in from
the hard-disk drive. Refer to Section 8 for information on operating the Layer Setup screen.
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
Depress
La~er
La~er
La~er
La~er
La~er
La~er
La~er
till
Ke~
La~er
tup
**
1 Package:
2 Package:
3 Package:
4 Package:
5 Package:
6 Package:
7 Package:
To Load The Selected Packages
Figure 41·1 DDCMP is a "layer-personality package" of softkey functions at Layer 1.
The DnCMP package takes control of two functions that normal1y are configured by the user on
the Line Setup menu: outsync and block checking. Control of these functions from the Line Setup
menu is disabled when the nDCMP package is loaded in.
41.1 Outsync
In synchronous format, the sync pattern is selectable by the user in the Sync Char field on
the Line Setup menu. Outsync parameters are not selectable. Outsync cannot be turned
off. A receiver will go out of sync at the end of a message unless the first byte of the new
message is ~, EO, or'l.. with the correct parity.
41.2 Block Checking
Screen display of good and bad BCes is automatic when DDCMP is loaded in at Layer 1,
and cannot be disabled on the Line Setup screen. The BCC setup for nDCMP cannot be
modified or controlled in any way from the BCC Setup menu.
SEP '95
41-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
The results of both header and data block checks are displayed on the screen. If you want
your program to detect good or bad BCCs, you may use the BCC selections on the trigger
menus and at Layer 1 of the Protocol Spreadsheet to interrogate the header block check
only_
If you want to detect a good or bad data block check, you must use one of the following C
event variables:
extern fost _event fevar..gd_hee2_td;
extern fost _event fevar..J¢ _hee2..Jd;
extern fast_event fevar_btl_bee2jd;
extern fast_event fevar_btl_hee2..Jd;
Here is a program that counts bad DTE BCes for both header and data:
{
}
LAYER: 1
STATE: count all bad dte bees
CONDmONS:DTEBAD BeC
ACTIONS: COUNTER t bdbcc INC
CONDmONS:
{
}
ACTIONS: COUNTER t_bdbcc INC
Note to C programmers: the DDCMP Layer 1 package takes every message and places it in
an IL buffer for use at Layer 2 and above. At the same time, it triggers the event
mJoyhyrmtv and updates the variables associated with upward-going monitor-path
primitives at Layer 2 (see Table 62-3). As a result, the OS1 condition PH_TO_DATA IND (or
PH_RD_DATA IND) comes true at Layer 2.
41-2
SEP '95
42 ISDN D Channel
42 ISDND Channel
SEP'95
42-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
La~er Setup
**
1 Package:
2 Package:
Lal;;er 3 Package:
La!::jer 4 Package:
La!::jer 5 Package:
Lal;;er 6 Package:
La!::jer 7 Package:
La~er
La~er
Kel;; To Load The Selected Packages
Figure 42·1 The ISDN_D personality package may be loaded from the Layer Setup screen.
42-2
SEP '95
42 ISDN D Channel
42 ISDN D Channel
The Basic Rate ISDN service provides an aggregate data rate of 192 Kbps, with 144 Kbps available
to users: two 64-Kbps B-channels and one 16-Kbps D-channel per interface (2B+ D). The
additional 48 Kbps are used for framing and maintenance. The INTERVIEW 8200 TURBO units,
INTERVIEW 8600 TURBO units, INTERVIEW 8700 TURBO units, and INTERVIEW 8800
TURBO units, with an ISDN TIM and its multiplexer board in place (OPT -951-563-1 or
OPT -951-566-1), support Basic Rate ISDN testing. Primary Rate ISDN data is carried over Tl
and G.703 circuits.
NOTE: The INTERVIEW 8100 TURBO unit supports neither Basic
Rate ISDN testing nor Primary Rate ISDN testing.
ISDN_D is a "layer personality package" of functions loaded into memory from disk at Layer 1 via
the Layer Setup screen. Figure 42-1 shows the Layer Setup screen configured to load in the
ISDN_D package from the hard drive. Refer to Section 8 for information on operating the Layer
Setup screen.
The ISDN_D package consists of a set of three C-Ianguage event variables and two C routines (see
Section 75). These variables and routines allow the C programmer to construct 0.921 (LAPD) and
0.931 functions for use on the D channel. The ISDN trace application package (available as
OPT - 951-35) is built upon the D-channel variables and routines provided at Layer 1 by the
ISDN_D package.
The ISDN_D layer package allows the user to send, receive, and monitor frames on the D channel
via an application program written in C. Meanwhile, the line setup, data display, and layer
packages can be focused on channel B1 or B2, whichever is selected on the ISDN Interface Setup
menu (see accompanying documentation for the ISDN option). For Primary Rate ISDN in T1 or
G.703, the ISDN_D layer package is also loaded at Layer 1 for the same use on the D channel as in
Basic Rate ISDN; the B channel is selectable on their respective Interface Control screens.
NOTE: The ISDN_D package should not be loaded when the D
channel is selected for single-channel monitoring or emulating; that
is, when the D channel is selected in the Channel: field on the ISDN
Interface Setup menu.
SEP '95
42-3
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
42-4
SEP '95
43 LAPD
43 LAPD
SEP '95
43-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
Depress
..
La!::ler
La!::ler
La!::ler
La!::ler
La!::ler
La!::ler
La!::ler
La!::ler
1 Package:
tup
**
•
NO PRCKRGE
2 Package: LRPD
3 Package: X.
4 Package: NO PACKRGE
5 Package: NO PRCKRGE
PACKAGE
6 Package:
7 Package: NO PRCKRGE
Ke!::l To Load The Selected Packages
LAYER-5
Figure 43-1 The LAPD personality package is loaded from the Layer Setup screen.
**
tup
**
1 (for INFO frame):
late:
de of operation:
indow size:
Figure 43·2 Protocol Configuration screen for LAPD.
43-2
SEP '95
43 LAPD
43 LAPD
LAPD is a "layer personality package" of functions that are loaded into memory from disk via the
Layer Setup screen. Figure 43·1 shows the Layer Setup screen configured to load in the Layer 2
LAPD package from floppy-disk, Drive 2. Refer to Section 8 for details on operating the Layer
Setup screen.
The LAPD package consists of the following:
•
A special LAPD Frame Level Setup screen that controls certain parameters when the unit is
tracing or emulating LAPD.
•
A protocol trace (illustrated in Figure 43-3) that distills from LAPD data the Level 2 events
that have protocol significance. This trace is accessible by softkey in Run mode at all times.
•
A group of conditions and actions at Layer 2 on the Protocol Spreadsheet that facilitate LAPD
programming. Figure 43-5 shows the softkey path to the first rack of condition softkeys when
the LAPD package is loaded in at Layer 2.
43.1 Frame- Level Setup
The parameters on the LAPD Frame Level Setup screen must be configured correctly for
an accurate trace display and for proper emulation.
To bring up this screen, first go to the Layer Setup screen (press 8, [ITJ). Execute the
LAPD selection at Layer 2: LAPD should appear in the Packages Loaded column. Press @
(labeled PROTSEl) to bring up a prompt to Select Protocol Configuration Screen. Then press
@ (LAYER-2) to call up the LAPD Frame Level Setup screen.
The four parameter fields on this screen are shown in Figure 43-2. T1, Emulate, and Window
Size apply to interactive (emulate) tests only. Mode of Operation must be configured
correctly for the protocol trace as well as for proper emulation.
SEP '95
43-3
----------------.--,
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(A) T1
Enter a four-digit (including decimal point) Tl timeout value in this field. The
largest valid entry is 65.5 seconds. The smallest entry is .001 second, or 1 millisecond.
Tl is the name given to the retransmission timer for INFO frames. When a value is
entered in the T1 field on this menu, the Layer 2 package will handle T1 timings
correctly, as follows:
•
Whenever the INTERVIEW sends an I -frame at Layer 2 and there are no
previous frames sent by the INTERVIEW currently outstanding (unacknowledged),
the timer starts timing down from the value entered on the Frame Level Setup
screen.
•
An acknowledgment by the device under test of the most recent frame
transmitted by the INTERVIEW stops the timer (so that it does not expire).
•
An acknowledgment by the device under test of a frame that is not the most
recent frame transmitted by the INTERVIEW-an "incomplete"
acknowledgment-restarts the Tl timer to the value selected on the
configuration screen.
Expiration of this Frame Level Setup timeout can only be detected by a T1_EXPIREO
condition on the Protocol Spreadsheet at Layer 2. This particular timeout cannot be
detected by a generic condition of TIMEOUT T1.
According to the protocol, a T1_EXPIRED condition should result in a RESEND action.
(8) Emulate Logical DTE/DCE
There are two selections in the Emulate field on the LAPD Frame Level Setup screen,
(;~m~i;T and~;J~~llltW. Usually, a logical DTE represents the user side of a
link and a logical DeE is the network side of the link.
Use the Mode selection Oi~m1.~g ori.'::~l~%) on the Line Setup menu to
regulate the physical interface-whether to use Pin 2 or Pin 3 to transmit, and so on.
(C) Mode of Operation
The Mode of Operation field refers to the mode of numbering INFO and supervisory
frames. There are two options, :';lmll!!~J~~';; and (;i_;t~i:·: .
MOD 8 uses sequence numbers 0-7. MOD 128 adds an extra byte to the control
field in INFO, RR, RNR , and REJ frames. See Figure 43-4. This extra byte allows
sequence numbers in a range of 0-127.
The correct "modulus" must be selected in this field in order to program successfully
in Monitor mode and also to generate an accurate LAPD trace.
43-4
SEP '95
43 LAPD
(D) Window Size
Any window size may be entered up to the current modulus minus one: 7 or 127.
The window size is the maximum number of unacknowledged I -frames that Layer 2
will buffer for retransmission. When the limit is reached, any further INFO frames
that are named in SEND actions triggered at Layer 2 will be passed to Layer 1 for
transmission but not buffered for retransmission.
The window is a queue that buffers frames for retransmission in case one or more
transmissions are lost or in error. A RESEND action will resend the first (earliest)
frame in the window. Successive RESENDs will send successive frames until there are
no more frames to resend; or until the window is reset by an acknowledgment or by a
RESEND FIRST action.
43.2 Protocol Trace
The LAPD package includes an automatic frame-trace display that summarizes
link-level activity. This trace mode is enabled whenever the unit is in Run mode, both
real-time and frozen.
While the unit is in Run mode, press the softkey for I.2TRACE to bring the protocol trace for
LAPD to the screen. (If the 0.931 package for Layer 3 is also loaded in, the I.2TAACE
softkey will appear after you have pressed PROTOCl, @ on the primary rack of
display-mode softkeys.)
When running in High-Speed Frame Mode, more data could be passed to Layer 2 than
there is room for in the buffer; this will cause an FEB overrun. If this happens, the error
message FE Buffer Overflowed - Some Frames Lost will appear on the prompt line. The first
time an FEB overrun occurs, an audible alarm will also sound; subsequent reccurrences
will cause only the message to display (without any alarm). The trace will restart again but
some data is lost with each occurrence.
Figure 43-3 is an example of the Layer 2 trace display. Each horizontal row in the trace
represents a frame.
(A) The Protocol Trace in Freeze Mode
Press ~ to prevent the addition of new data to all the display buffers, including the
trace buffers. The frozen trace display may be scrolled through or paged through.
The top line always is the cursor line (though there is no actual cursor on the trace
display). Pressing I1iID or f±l moves the viewing "window" down relative to the data to
add one line of fresher data to the bottom of the screen. Pressing [lID or !!J moves
the viewing window up to add a line of older data to the top of the screen.
Depression of the [lID key adds 15 lines-one full page-of newer frames to the
frozen trace screen. Depression of (BJ adds 15 lines of older frames.
SEP '95
43-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
The frame displayed on the top line of frozen trace-data will appear as the first
frame in the raw-data or data-plus-leads display. To view the raw data that
generated a particular line in the trace display, use (1iD or (5) (or!!) or [±)) to move
the line in question to the top of the screen. Then press one of the data softkeys.
SRC
S~PI
TEl
C/R
TyoE
Nr
Ns
-
p/~
S~ZE
TIME
BCC
-,
Figure 43-3 Each horizontal row on the trace display represents a frame.
(8) Trace Columns
The columns in the protocol trace for Layer 2 LAPD are explained below.
1.
Source. The SRC column identifies the lead on which the frame was monitored,
TO (DTE) or RD (DeE). This column identifies the physical source of the frame,
not the logical source. The physical DTE uses the TO lead to transmit. The
physical DCE uses RD to transmit.
Just as on the data display, RD data is underlined.
2.
SAP!. The Service Access Point Identifier (SAP!) is given in the next column.
The SAPI is a network link-station address that appears in a six-bit field in the
first frame-address byte: see Figure 43-4.
The SAP! is presented on the trace display as two hex digits, with the righthand
digit expressing the four low-order bits of the SAPI and the lefthand digit
expressing the two remaining bits.
43-6
SEP '95
43 LAPD
I
I
ADDRESS
I
I
CONTROL
INFO-MO~ 8
FCS
INFORMATION
I
CONTROL",lNFO
(t~ ,J:iJ t ,~,"I): I;" ~:; ): I~~ 1:J""Jl"""J
-......
......I
I
INFO-MOO 128
~/,
-
878S4321
FlR-MOO8
I
L::::.:J
~
I
87654321
87654321
.,.
.......
HEX", "1
I~I
0
0
1
6 5 4 3
2
1
N(R)
,. . .
0
8 7
0
.......
.......
.......
.......
.......
.......
RR - MOO 128
:-1-~=-01-~--0
ASCII-/or?
o
1 'pIll
1
1
87654321
OM
-
D:~~D
87654321
HEX '" 2~ or 3,
-
00000001
p
87654321
87654321
y
87654321
.......
FRMR
RNR-MOOS
ASCII =
Sr
or l\;
Il.. or '8
ASCII '"
1
I~I
1
87654321
NIBl
n
' ..0
0
0
IFI "
•
87854321
87654321
UA
HEX '"
OISC
RNR - MOO 128
HEX" 413 or 53
{,3 or '3
ASCII .. Cor5
ASCII" cars
1
1
87854321
=
H;:
(,rO< 77
ASCII = gorw
876543
ASCII=
'!,
87854321
0
1
"""0
til
'pi
1
1
87654321
Hex ..
/":'toHEX-'"0-"
87854321
1
D
ml00t
00001001
1
D
REJ - MOO 128
Fr
ASCII '" gotw
1
Ipl
UI
87654321
511
HEX= Erot
/}
?q
N@
1
1
87654321
FlEJ - MOOS
I
SIO
HEX
87854321
/}
N
87654321
N
ASCII
~
o
87654321
1
{,F
=0
or
TF
or
Ipl 1
~
1
1
1
67854321
Figure 434 Frame fields in LAPD.
SEP '95
43-7
~.----.----------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
3.
TEl. The Terminal Endpoint Identifier (TEl) is the address of a link station on
the user side. It occupies seven bits in the second frame byte inside the leading
flag (see Figure 43-4).
The TEl is presented on the trace display as two hex digits, with the righthand
digit expressing the four low-order bits of the TEl and the lefthand digit
expressing the three remaining bits.
4.
C/R. The CommandlResponse (C/R) column identifies the logical DTE (user
side) and the logical DCE (network side). The logical DTE uses CIR 0 for INFO
frames and other command frames, and CIR 1 for responses. The logical DCE
uses CfR 1 for INFO frames and other commands, and CfR 0 for responses.
5.
TYpe. The mnemonic (abbreviated) names for thirteen frame types as they
appear in the TYPE column of the protocol trace are shown in Figure 43-4 under
"CONTROL." The control field, therefore, indicates the frame type. If a
control octet does not fit any ofthe patterns in the figure, the frame is listed in
the TYPE column as UNKWN followed by the hexadecimal value of the control byte:
UNKWN=47.
If the number of bytes in the frame is below the required minimum, the frame is
posted as INVAUO.
6.
N(R) and N(S). One column on the frame-level trace is devoted to N(R) values,
and one column to N(S). The frame types that include N(R) or N(S) fields in
their control fields are indicated in Figure 43-4. N(R) and N(S) occupy three bits
each in modulo 8, seven bits each in modulo 128.
N(R) and N(S) values are presented in decimal format in modulo-8 traces.
Each column displays a single digit that represents a 3-bit binary value. For
modulo 128, the values 00 to 1", are given in "character" format, where the
columns contain a two-digit hexadecimal character.
7.
P and F. The status of the poll or the final bit is given in the P/F column.
Whether this bit is the P- or F -bit is indicated for most frame types in
Figure 43-4 (under "CONTROI.:').
The setting of the P-bit in an INFO frame often denotes the retransmission of
an unacknowledged frame following a Tl timeout.
8.
Size. The number of bytes in each frame is given in this column in four decimal
digits. The count begins with the first address byte and excludes the two-byte
FeS. Frames without I -fields show a count of three (MOD 8).
9.
Time. The time of the arrival of the end o/the frame at the DTE or DCE monitor
is provided by a 24-hour clock and posted to the trace display. The clock is
accurate to the milli - or microsecond.
When time values are incorporated in data, times posted to the trace display will
not be affected when recorded data is played back, even at varying speeds. To
incorporate time values into recorded data, make the following selections:
•
For bit-image data
Data To Record:
Time Ticks:
43-8
(Record Setup menu; see Section 7)
(Front- End Buffer Setup screen; see Section 9)
SEP '95
43 LAPD
•
For character data
Data To Record: !li1~~
Time Ticks: 1'l~fJ
or
Data To Record: ~~lj
11me Ticks:"
Frame Timestamps:.t (Front-End Buffer Setup screen; see Section 9)
Timestamp Resolution: IiII or.8
If time values are not incorporated in data during live recording, times on the
trace during playback will be influenced by "local conditions" such as playback
speed, idle suppression., etc.
10. Frame Checking. A lAPD frame ends as soon as a TE flag or seven I-bits in a
row are detected. If a flag ends the frame, a frame check is perforined and the
result is posted both to the data display and to the Bee column of the trace
display. The symbol@ denotes a good frame check, while. symbolizes a bad
frame .
• for abort is posted to the displays when a frame is ended by seven I-bits.
43.3 Monitor Conditions
When the LAPD personality package is loaded in (via the Layer Setup screen), a set of
conditions checks DTE and DeE leads. This set of conditions is accessed by the OTE and
DCE selections on the first rack of condition softkeys at Layer 2. See Figure 43-5.
Figure 4J.5 The softkeys for DTE and DeE are used to monitor LAPD protocol events at Layer 2.
After the keyword orE (or DeE) is written to the spreadsheet, a rack of softkeys appears
that represent types of frames: INFO, SABM, UA, and so forth.
SEP'95
43-9
I_IIIB_._ _ _ _......._ _
---------.------------.---••- - . - - - - - - - - - - -_ _ _ _ _ _ _ _ _ _ _
l!/I,l\.t_mo_ _:_
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(A) Frame Types
The softkeys for INFO, supervisory, unnumbered, sequenced information, and
"other" frames are illustrated in Figure 43-6. Press a softkey to write one of these
frame types to the Layer 2 spreadsheet. DTE or DCE followed by a frame-type
mnemonic-DTE INFO, for example, or DCE SABM-is a complete condition and will
come true if a matching frame is monitored. SAPI, TEl, C/R, polVfinal, and BCC
conditions may be appended to the simple frame mnemonic, but they are optional.
1.
Info frames. INFO frames differ for MOD 8 and MOD 128 numbering schemes.
(See Figure 43-4.) For spreadsheet conditions to match I -frames accurately, the
correct numbering system (Mode of Operation) should be selected on the LAPD
Frame Level Setup screen.
2.
Supervisory frames. The three supervisory-frame types that can be searched for
on the data leads are RR (Receive Ready), RNR (Receive Not Ready), and
REJect. These frames always contain N(R) fields (see Figure 43-4) and serve
mainly to acknowledge or reject INFO frames.
Like INFO frames, supervisory frames are constructed differently according to
the numbering scheme, MOD 8 or MOD 128.
3.
Unnumbered frames. Unnumbered frames generally assist in link -setup and
takedown.
Figure 43-6 Frame type or block-check type may be specified as a complete condition for
DTEorDCE.
4.
Sequenced infonnation frames. Sequenced information frames (SID and SIl) have
a 1-bit sequence-numbering field that toggles 0 (SID) and 1 (S11). (See
43-10
SEP '95
43 LAPD
Figure 43~4.) These frames are used instead of INFO frames in MOD 2
operation where the limit for outstanding information frames is 1.
FIgUre 43-7 The hex value of any frame may be specified under OTHER.
5.
Other frames. Any frame type may be entered as a hexadecimal value instead of
by name. Press the softkey for OTHER. See Figure 43~7. Then enter the hex byte
in the form of two alphanumerics. Here, for example, is a SABM (with the P-bit
set) entered as a hexadecimal:
CONDITIONS; DCE OTHER SF
SEP '95
43-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
SAPI, TEl, ClR, PIF, and Bee conditions may be appended to OTHER conditions
(see Figure 43-8). In MOD 8, the PIF bit is already specified in the hex entry,
and a P/F condition will be ignored.
Figure 43-8 The bottom softkey rack shows conditions that may be linked to frame-type
conditions.
6.
SAP!. A SAPI condition may be added to all frame types. Press the softkey for
SAPI=, shown in Figure 43-9. Then enter the 6-bit SAPI value as two hex digits in
a range from 00 to 3F. (Do not use the ~ key.) The entry will appear as in this
example:
CONDfTlONS: DTE INFO SAPI= 15
Figure 43·9 The hex value of the SAPI is entered as two alphanumerics.
To bypass the SAPI"" selection (as well as the other options on the same rack of
softkeys in Figure 43-9) press 8.
7.
43-12
TEl. Like SAPl, a TEl condition may be added to all frame types. Press the
softkey for TEI=, shown in Figure 43-10. Then enter the 7-bit TEl value as two
hex digits in a range from 00 to 7F. (Do not use the ~ key.)
SEP '95
43 LAPD
Figure 43·10 The TEl is an optional condition within all frame-type conditions.
8.
CIR. A C/R value of 0 or 1 may be entered as an optional condition added to any
frame-type condition.
Figure 43-11 The value of the CIR bit may be chosen as a condition.
Press 8 to bypass the C/R= condition and the other conditions on the same
softkey level in Figure 43-11.
9.
Poillftnal bit. PIF conditions are optional for all frame types. PIF values of 0 or 1
are entered by the softkey sequence in Figure 43-12.
Figure43·12 The value ofthe P/F bit may be chosen as a condition for any frame type.
Press 8 to bypass the P/F= condition and the other conditions on the same
softkey level in Figure 43·12.
43-13
SEP '95
_ _._._-_ .._------_.. _----_._.
.. ..
__.. _..._._--
-------_.. _.-----------------------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 43·13 A condition may search for all good, bad, or aborted frames.
(B) BCC Conditions
DTE and DeE frames may be monitored for good and bad frame checks and for aborts.
All DTE or DeE frames may be monitored with respect to frame checking, as in this
example:
CONDITIONS: DTE eDeCC
The softkey sequence for this spreadsheet entry is given in Figure 43-13.
Or a particular type of frame may have a Bee or abort condition appended to it:
CONDITIONS: DCE INFO ABORT
43.4 Emulate- Mode Conditions
The remaining conditions are functional only when the Line Setup menu is configured for
Mode: ·.~'j'§B1§\ or tit~.m~.
43-14
SEP '95
43 LAPD
(A) Receive Conditions
Like OTE and OCE conditions, RCV conditions monitor a data lead for LAPD frame
types. RCV conditions operate only in emulate modes, and they check only the data
lead that the INTERVIEW is not using to transmit. While a RCV condition may look
like a OTE or DeE conditiOn-RCV INFO P1F=11ooks the same as OCE INFO P/F=1-there
are important differences that are noted below.
1.
J1l1id frame sequencing. To satisfy RCV conditions, numbered frames must have
correct N(R) and N(S) sequencing.
2.
Good Bee. RCV conditions cannot match frames with bad frame checks, nor can
they match aborted frames. (Emulate-mode conditions are designed for ease of
programming, and the assumption is that as a LAPD emulator, you are not
required to acknowledge-or negative- acknowledge-bad or aborted frames.)
If you wish to count bad Bees or aborts, use OTE or DCE conditions instead of RCV
conditions.
Figure 43·14 INVAUD and UNKNOWN are frame types for ReV conditions.
3.
SEP'95
Tjpe invalid. RCV conditions can detect frames that are invalid "types"-the
control field is missing, for example, or the I -field is missing in an I -frame. The
Protocol Spreadsheet entry for this condition is RCV INVAUO, and the softkey
sequence is illustrated in Figure 43-14.
43-15
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
4.
1Ype unknown. A frame may be valid in all respects but have a control field that
indicates a nonstandard frame type. Such a frame may be matched by a Rev
UNKNOWN condition (Figure 43-14).
(8) N(S) Error
As a Layer 2 emulator, you do respond to INFO frames that have N(S) errors. These
are detected as NS_ERR conditions, not as RCV INFO conditions.
NS_ERRS apply only to frames
received when you are emulating. The same frame that
triggers an NS_ERR condition also may satisfy a OTE INFO or DeE INFO condition-but
not a Rev INFO condition.
come true for any received INFO frame whose N(S) value is not one
higher than the previous N(S).
NS_ERR will
NS_ERR will
not come true for out-of-sequence SIO and SIl frames.
In the first rack of condition softkeys at Layer 2, press PROTOCL. Then press the
softkey for NS_ERR. See Figure 43-15.
Figure 43-15 The PROTOCL key brings up six LAPD emulate conditions.
(C) N(R) Error
Received INFO or supervisory frames may have N(R) errors. Such errors are
detected as NR_ERR conditions, not as Rev INFO or RR (or RNR or REJ) conditions.
A valid N(R) is any value that (1) acknowledges a frame that is outstanding (waiting
for acknowledgment); or (2) repeats the last acknowledgment. Any other N(R) value
is detected as an error.
(D) T1 Expired
This condition detects the expiration of the Tl timeout-timer that is regulated on
the LAPD Frame Level Setup screen. See Section 43.1(A), above.
43-16
SEP '95
43 LAPD
(E) Frame Sent
This condition is true when, as a result of a SEND or RESEND action, a frame has been
passed down to Layer 1.
(F) Window Conditions
The size of the Layer 2 retransmit window is configured on the LAPD Frame Level
Setup screen. See Section 43.1(D). There are four conditions that test the current
status of this window. They are WINDOW FULL, WINDOW EMPTY, WINDOW NOT_FULL, and
WINDOW NOT_EMPTY. The softkey sequence for the WINDOW options is shown in
Figure 43-16.
Figure 43-16 When the retransmit window fills, Layer 2 stops buffering frames for retransmission.
WINDOW FULL is true when the window is full of unacknowledged frames and the Layer
2 protocol package will not buffer additional frames until some acknowledgment is
received.
Each time an acknowledgment is received, the window is flushed to the extent of the
acknowledgment. WINDOW EMPTY means that the latest acknowledgment was complete
and left no frames outstanding (unacknowledged). If an RR response is received and
the acknowledgment is only partial, this condition will be true:
CONDITIONS: RCV RR
WINDOW NOT_EMPTY
CAUTION: Window conditions are status conditions (see Section 31.2)
and must always be used in combination with a transitional condition
such as a Rev condition.
SEP'95
43-17
---------------_._--------------------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
(G) More to Resend
Frames in the window may have to be resent, usually as the result of a Tl timeout or
a Reject frame. One RESEND action retransmits one frame in the window, beginning
with the earliest. Subsequent RESEND actions retransmit subsequent frames. The
MOREJO_RESEND and NO_MORE_TO_RESEND conditions allow you to retransmit the
entire window, as in the "recover" state in this example:
CONDmONS: RCV REJ
NEXT ST: recover
STATE: recover
CONDmONS: ENTER STATE
ACTIONS: RESEND FiRST
CONDITIONS: FRAME SENT
MORE TO RESEND
ACTIONS:RESENO NEXT
CONOmONS: FRAME SENT
NO MORE TO RESEND
NEXT).T: xfer- MORE_TO_RESEND and NO_MORE_TO_RESEND conditions may be written to the Protocol
Spreadsheet by the softkeys shown in Figure 43-17.
Figure 43·17 The MORE_TO_RESEND condition allows you to resend the entire window of
frames and then stop when there are NO_MaRE_TO_RESEND.
CAUTION: MOREJO_RESEND and NO_MOREJO_RESEND are status
conditions (see Section 31.2) and must always be used in combination
with a transitional condition such as FRAME_SENT.
43-18
SEP '95
43 LAPD
43.5 Emulate Actions
When you have completed a block of conditions in a Protocol Spreadsheet test at Layer 2,
press 8 to access the set of actions that can be taken as a result of the block of conditions
coming true. The set of actions that are specific to the I.APO personality package are
shown in the racks of softkeys in Figure 43~18. Except for ENHANCE and SUPPRES, the
actions shown have meaning only when the INTERVIEW is emulating OTE or DCE, and
not when it is monitoring the line passively.
Figure 43-18 Action softkeys specific to LAPD.
(A) Send Actions
Press the softkey for SEND to access two racks of softkeys with names of frame types
that may be named in SEND actions. All data generated by the LAPD package must be
enclosed in a frame that is identified in a SEND action by type. (Only at Layer 1 can
data be generated as a simple character string without any protocol building blocks.)
The complete set of frame types is given in Figure 43-19.
SEP '95
43-19
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
When conditions are true for a SEND action, frames are sent immediately down to
Layer 1 to be transmitted there.
Figure 43-19 SEND actions always specify a frame type.
1. INFO frames. SEND INFO is a complete action-entry. SAPI, TEl, command-bit,
poll-bit. N(R), N(S), string, and BCC parameters may be added to an INFO
frame, but they are optional.
If a Layer 3 package is installed and Layer 3 data is being handed down to Layer
2, the following condition - and - action trigger will accept this data and convey it
properly to Layer 1:
CONDITIONS: DL DATA REQ
ACTIONS: SEND iNFO" (COL_DATA})"
actions pass the INFO frame immediately to the next layer down. If the
retransmit window is full, the frame is still sent-but it is not buffered in the
window and cannot be resent.
SEND INFO
An INFO frame will be buffered for retransmission regardless of the status of the
window if a specific value is entered for the NS= parameter (see "N(S)," below).
The specific N(S) value will clear the window and the INFO frame will be
buffered in the first window position.
43-20
2.
Supervisory frames. SEND RR, SEND RNR, and SEND REJ are complete action entries.
SAPI, TEl, CIR bit, P/F bit, N(R), string, and Bee parameters may be added to
the SEND action, but they are optional.
3.
Unnumbered frames. SAPI, TEl, e/R bit, PIP bit, string, and Bee parameters
values may be included as adjuncts to a SEND action for an unnumbered frame.
SEP '95
43 LAPD
Figure 43-20 SAPI, TEl, OR, PIF, string, and Bee options may be added to SEND
unnumbered-type and 51-type actions.
4.
Sequenced information frames. SAPI, TEl, C/R bit, PIF bit, string, and Bee
values also may be added to SEND SIO and SEND SI1 actions.
Figure 43-20 shows the optional fields that may be specified inside unnumbered
and SI send-actions.
5.
Otherframes. Any frame type may be entered in a SEND action as a hexadecimal
value instead of by name. Press the softkey for OTHER, on the bottom rack in
Figure 43-19.
FIgUl'e 43-21 SEND OTHER actions always specify a type value in hex.
SEP'95
43-21
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
Enter the hex value in the form of two alphanumerics. Here is a DISConnect
command entered as a SEND OTHER action:
SEND OTHER 43 SAPI= 04 TEl = 1A C/R= 0
Note that PIF, N(R), and N(S) fields are implied already in the user-entered
hexadecimal control field. In MOD 128, P/F is not included in the hex entry and
is a valid optional entI)'.
6.
SAPI. An SAPI may be specified for all frame types. The SAPI= entry is always
typed as two hex digits, with the right-hand digit expressing the four low-order
bits of the SAPI and the left - hand digit expressing the two remaining bits. The
SAPI field 000100, for example, appears as follows:
SEND RR SAPI= 04 TEI= 1A
7.
TEl. A TEl may be specified for all frame types. The TEI= entry is always typed
as two hex digits, with the right-hand digit expressing the four low-order bits of
the TEl and the left-hand digit expressing the three remaining bits. The TEl
field 0011010 is illustrated in the SEND RR example above.
Figure 43-ZZ The correct Command/Response bit will depend on the logical emulation.
8.
Command/response bit. The C/R bit may be specified for all frame types. The
logical DTE uses CJR 0 for INFO frames and other command frames, and C/R 1
for responses. The logical DCE uses CJR 1 for INFO frames and other
commands, and CJR 0 for responses. Since the response bit echoes the command
bit, a CIA"" LOOPBACK selection is provided (see Figure 43-22).
9. Poll/final bit. The P/F bit is an optional entry in all SEND actions. PtFvalues of 0,1,
or LOOPBAK are entered by the softkeys in Figure 43-23. If P/F= LOOPBAK, the bit
will echo the last PtF bit received. (Looping the P/F bit is appropriate for VAs
and supervisory frames.)
43-22
SEP '95
,r~,
43 LAPD
Figure 43-23 A P/F value is optional in all SEND entries.
10. N(R). N(R) fields are transmitted in INFO and supeIVisory frames.
To specify an N(R) value, press the softkey for NR= (see Figure 43-24). Enter a
hexadecimal value written as one or two alphanumeric digits. For example, an
entry that represented the highest valid N(R) in MOD 8 would be NR= 7. The
highest valid entry in MOD 128 would be NR= 7F.
Other N(R) options are ACK_NS, lAST_NR, and AUTO. (See Figure 43-24.) ACK_NS
means that your N(R) will acknowledge (that is, it will be one higher than) the last
N(S) value you received. Normally this will be the correct N(R), except in cases
where the last N(S) received was erroneous. The NR= ACK_NS selection allows you
to overlook N(S) errors.
F'lgUre 43-24 The N(R) field may be specified in INFO and supervisory frames to be sent.
lAST_NR means that you simply repeat the last N(R) you sent. Normally this is the
correct N(R) following a bad N(S). The NR= LAST_NR option allows you to force
the other side to initiate recovery.
AUTO means that you will behave as a normal LAPD station, ACKing valid N(S)
values and repeating your last N(R) whenever an invalid N(S) is received.
11. N(S). N(S) fields are transmitted in INFO frames only. (See the frame-field
diagrams in Figure 434.) Entries for N(S) in SEND INFO actions are optional. The
softkeys that open below NS= are illustrated in Figure 43-25.
SEP '95
43-23
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -_ _ _
._._._'m_ _ _ _ _ _ __
INTERVIEW BOOOSeries Basic Operation: 951-80424-01
To specify an N(S) value, press the softkey for NS=, then enter a hexadecimal in
the form of one or two alphanumerics. Valid hex entries are the same as for
N(R). A SEND INFO action that specifies an N(S) value-NS= 0, for example-will
clear the window so that the INFO frame is buffered immediately.
Figure 43-25 The N(S) field may be specified in a SEND INFO action.
Other N(S) options are RCVD_NR, SKIp, and AUTO. RCVD_NR means that you send
the N(S) value that the other side says it is expecting. This is the valid N(S) in
most cases, but not when you send two or more I -frames in a row without
waiting for acknowledgment.
SKIP means that you add one to your correct N(S). This will look to the other side
as though the line has taken a "hit" and a frame has been lost. This selection
causes the window to be cleared.
NS= AUTO is the default setting for SEND INFO actions. AUTO means that every new
INFO frame sent will have an N(S) value of one higher than the previous.
12. String. Strings are sent in LAPD only as adjuncts to frame-types when they are
named in SEND actions. If you want to send a string of raw data without a
protocol "envelope," you must go to Layer 1 and send the raw string from there.
Press the SEND softkey followed by the softkey for a frame type. Add any
necessary or desired SEND options for the particular frame type. Then press the
STRING softkey (labeled F7 in Figure 43-25).
There is no spreadsheet keyword that identifies send-strings at any layer. The
spreadsheet compiler identifies strings by the quotation marks surrounding them.
Always enclose strings in quotation marks. (To send an actual" -character in
your string, type \" .) See Section 33 for more information on strings.
Here is a simple SEND action that includes no options besides a string:
And here is a SEND action that includes a full complement of optional fields,
including a string:
43-24
SEP '95
43 LAPD
ACTIONS: SEND INFO SAPI= 04 TEI= 1A CIA;; 0 P/F= 0 NR= AUTO NS= AUTO
.. 7e 2coA 7036449000" GDBCC
Most ASCII - keyboard, control, and hexadecimal characters are legal in a
send-string. Special keys (§3, B), ~) are not legal. Refer to Table 33-2.
To insert a canned fox message into a transmit string, type FOX inside double
parens, as follows: «FOX)) • Remember that the double parens are special
characters produced by the §.9-@ and ~-@ combinations. Constants,
counters, and flags can also be embedded in a string. See Section 33, Strings.
13. Bee. There are three BCC options for every SEND action in LAPD. One of the
options, GDBCC, is the default. Any frame that does not request a bad BCC or an
abort will have a good frame-check sequence calculated for it and appended to
it. Bec also is an option for SEND actions at Layer 1; but it does not occur at
Layer 3 or higher.
t
Figure 43-26 Type of BCC is a SEND option for frames at Layer 2
The three softkey selections for BCe are shown in Figure 43-26. A 16-bit
CC1TI frame check is selected automatically for BOP protocols and cannot be
changed or disabled. A bad BeC will be CRC-16 instead of CCITT.
When ABORT is the BCC selection, instead of appending a proper frame check the
transmitter will hold the lead at mark for eight bits (or longer if the transmitter is
idling FF ). Inside a frame, seven 1-bits in a row are sufficient to signal an abort.
(8) Give Data
GIVE_DATA is the [W action on the first rack of action softkeys (refer to Figure 43-18).
This action takes the I -field from a received INFO frame and passes it up to Layer 3
along with a DL_DATA IND primitive. (See Figure 34-5 in the section, OS1
SEP '95
43-25
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Primitives on the Protocol Spreadsheet.) In an emulate mode, data is delivered up to
Layer 3 only by one of two actions at Layer 2: GIVE_DATA, or else a Dl_DATA IND
primitive followed by the data string.
(C) Resend
The RESEND function is mapped to !fiJ on the second layer of action softkeys. See
Figure 43-27. The first RESEND action will resend the first frame in the window. The
window is a queue that buffers INFO frames for retransmission in case one or more
transmissions are lost or in error.
The first frame in the window always is the earliest outstanding (unacknowledged)
frame. EveI)' time an acknowledgment is received, the window is cleared to the extent
of the acknowledgment and a new "first-frame" position is established. The first
RESEND after an acknowledgment always sends the first window frame.
Figure 43·27 The RESEND action allows you to recover from sequence errors.
43-26
SEP '95
43 LAPD
FRM6
FRM7
-------------FRMO
WINDOW
FRM 1
FRM 2
FRM3
FRM4
~
.........-
pOinter moves
to here after
four RESEND NEXTs
Window moves to here
after FRM 7 is acknowleged
(NR=O); pOinter resets to
"first in window" position
FJgUl"e 43-28 Resends cause the pointer to move, while acknowledgments move the pointer and the
entire window.
The second and subsequent RESENDs following an acknowledgment also will send the
first window frame, provided that the keyword FIRST is appended directly to the
RESEND entry. Otherwise, they send the NEXT (second) and subsequent window
frames. Figure 43-28 shows the position of the the resend "pointer" after four
consecutive RESEND NEXT actions. RESEND NEXT is the default resend when neither
FIRST nor NEXT is specified.
The resend-pointer is reset to the beginning of the window automatically by any
acknowledgment, or by a RESEND FIRST action in the spreadsheet program.
1. &send first/next. RESEND FIRST means that the resend-pointer is reset to the
beginning of the window, the first frame in the window is resent, and the pointer
is advanced to the second position in the window. The effect of a RESEND FIRST
action is illustrated in Figure 43-29.
The RESEND FIRST action makes it possible for you to resend all the frames in the
window one by one, and then resend them again if necessary.
2.
SEP '95
P/F=loopback/O/l. The P/F bit in the resend-frame can be set to 0 or 1 by this
optional action. If PF= LOOPBACK, the bit will echo the last P/F bit received.
(Default is 1 in a RESEND action.)
43-27
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
FRM6
-
-
-
-
-
-
-
-
-
-
-
-
FRM 7
-
-
.....- pOinter moves to here
after RESEND FIRST
action resends FRM 6
FRMO
WINDOW
FRM 1
FRM2
FRM3
FRM4
....- pOinter is here
after seven
RESEND NEXTs
Figure 43-29 RESEND FIRST resets the pointer, allowing you to resend the entire window repeatedly.
(0) Reset N(R) and Reset N(S)
RESET_NR and RESET_NS are the @ and
®J actions on the second rack of action
softkeys in the LAPD personality package. (Refer again to Figure 43-18.) The
sequence-number fields in I-frames and supervisory frames can be reset by these
two Protocol Spreadsheet actions. Sequence numbers are not reset automatically
during a test by any frame that is sent or received.
RESET_NS also clears the transmit window.
43-28
SEP '95
43 LAPD
43.6 Display Actions
ENHANCE and SUPPRESS pertain to lines of data on the Layer 2 protocol trace (see Section
43.2). They do not suppress and enhance data on the raw-data display. Raw data is
enhanced and suppressed at Layer 1.
OTE, OCE. and RCV conditions can trigger an ENHANCE or SUPPRESS action.
(A) Enhance
Whenever a OlE, DCE, or RCV condition comes true at Layer 2, the frame that satisfied
the condition can be enhanced on the lAPD protocol-trace display, or it can be
deleted from the trace completely. In an actions block on the Protocol Spreadsheet,
press the ENHANCE softkey-@ on the third rack of action softkeys. Figure 43-30
shows the three softkey subselections beneath ENHANCE. They are REVERSE, BUNK, and
LOW
Figure 43·30 Selected frames on the protocol trace may be enhanced or suppressed.
SEP'95
43-29
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Reverse-image and blink enhancements affect the plasma-display screen. In
addition, a low-intensity enhancement can be applied to screens that are transmitted
to a black-and-white monitor connected at the RS-170 port at the rear of the
INTERVIEW.
Reverse, blink, and low enhancements can be mapped to colors on a color monitor
attached at the INTERVIEW's RGB port (Figure 1-6). See Section 18.2 for an
explanation of how reverse, blink, and low enhancements relate to character and
background colors in the RGB output.
•
•
=
F"tgUre 43-31 A DTE SABM has been enbanced.
Figure 43-31 shows one screen of a Layer 2 protocol trace in which DTE SABM
frames have been enhanced in reverse video. The trigger that caused this
enhancement was as follows:
CONDITIONS: DTE SABM
ACTIONS: ENHANCE REVERSE
(8) Suppress
Individual frames that are suppressed in Layer 2 actions are deleted from the trace
display. Figure 43-30 showed the softkey path to SUPPRES.
43-30
SEP '95
43 LAPD
43.7 Automatic Primitives
In Section 34,OSI Primitives on the Protocol Spreadsheet, Table 34-2 lists the OSI service
primitives that are monitored at the boundaries of Layer 2 as trigger conditions and sent
up to Layer 3, or down to Layer 1, as user-entered spreadsheet actions. These primitives
are layer-specific rather than protocol-specific and are not part of the personality
package for LAPD; but a few of the primitives are set in motion automatically by LAPD
spreadsheet actions. These automatic primitives can be thought of as part of the Layer 2
actions themselves, and by extension, as part of the LAPD protocol package.
Table 43-1 gives the set of LAPD actions that have action -primitives built into them. For
example, whenever a GIVE_DATA action occurs at Layer 2, a DL_DATA IND primitive is
forwarded to Layer 3, where a DL_DATA IND condition may be waiting to monitor it.
Whenever a SEND or RESEND action is initiated at Layer 2, a PH_DATA REQ primitive is
sent downward along with the PH data (the entire frame).
If a SEND or RESEND action is triggered at Layer 2 while the physical connection at Layer 1
is inactive, Layer 2 will sense the absence of a physical connection and delay the
PH_DATA REO. Instead, it will send a PH_ACTIVATE REQ primitive. Only when a
PH_ACTIVATE CONF has been returned by Layer 1, will Layer 2 release the data and
the data primitive.
NOTE: All Layer 1 interfaces for the INTERVIEW 7000 Series will
return PHfiCfIVATE CONF automatically whenever they see
PH_ACfIVATE REO.
Table 43-1
Automatic Primitives Generated in tAPD
LAPD
Layer 2
Action
Automatic
Primitive
To
Layer
3
SEND {lYPE}
(PH_ACTIVATE REO*)
PH_DATA REO
RESEND
(PH..ACTIVATE REO*)
PH_DATA REO
*Sent it Layer 1 shows inactive status. PH_DATA REO delayed until PH_ACTIVATE
CONF returned by Layer 1.
SEP '95
43-31
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
43-32
SEP '95
44 Q.931
44 Q.931
SEP '95
44-1
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
**
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
DRIVE:
La~er
La~er
Lal::!er
Lal::!er
Lal::!er
Lal::!er
Lal::!er
1
2
3
4
5
6
7
Package:
Package:
Package:
Package:
Package:
Package:
Package:
tup
**
Selections
i"10
PPCK~jGE
NO PAOz
ASCII =
22
Q
00100010
87654321
SUSPEND
00100101
87654321
SUSPENDACK
HEXx
°0
HEX=
ASCII ..
'R
ASCII
00001101
87654321
=<
E
FACIUTYACK
HEX:
ASCII =
"A
j
01101010
87654321
RELEASE
FAClUlYREJ
HEX:
'b
HEX:
72
ASCII '"
M
ASCII =
r
01001101
87654321
RELEASE
COMPLETE
HEX: SA
Z
01011010
87654321
CANCEL
01110010
87654321
INFO
HEX =
ASCII
T8
={
0111101 I
87654321
REGISTER
"b
HEX= 100
HEX= 6 4
-
ASCII = •
ASCII=
00101 101
87654321
01100000
87654321
SUSPENDREJ
CANCELACK
HEX:
21
ASCII =
!
HEX", "8
ASCII=
h
00100001
87654321
01'01000
87654321
USER INFO
CANCELREJ
d
01100100
87654321
REGISTER ACK
HEX= f>C
ASCII=
1
01101100
81654321
REGISTER REJ
HEX '" 20
HEX= 7 ..
ASCn = (space)
ASCII = t
00100000
81654321
Figure 44-3 Message fields in 0.931.
"s
01100010
87654321
01000101
87654321
ASCII=
SETUPACK
0'110000
87554321
HEX=
"0
CONGESTlON
CONTROL
HEX", 7q
ASCII",
@
ASCII =
DETACH
01000000
87654321
44-6
DISCONNECT
HEX =
OF
00000101
87654321
FACIUTY
H
01001000
87654321
HEX= \:
HEX ..
00001111
87654321
OETACHACK
HEX= 48
lie
00000010
87654321
SETUP
/
RESUME
HEX= 02
\::l
01111001
87654321
01110100
87654321
STATUS
HEX = TO
ASCII= )
01111101
87654321
SEP '95
44 0.931
--------
INFORMATION ELEMENT 1
TERMINAL CAPA8IUTIES
F~~I
OCTETS
I".::.;~;"::':'=--'
67654321
67654321
------
o \olI. :. :. :.: .=.: D:. E_STl~f~1 687854321
~D
HEX = 0Il
L.l:,;ASC1=':,,:."'=lIs::.-...
67654321
------REOIRECTlNG ADDRESS
CAUSE
o
INFO ElEMENT 2, etc.
~~D
~
87654321
87654321
~ASC1~~':~~'~Jf=~ 10
o~:~f~D
87654321
KEYPAD ECHO
o
HEXs
"0
&..::.:ASCI:.:...:.'.::.==0::.-~
87654321
87654321
~
L-=:J
87654321
87654321
1r------.D
o
I.DW LAVER COMPATlBIUTY
87654321
~-':~~r;::j 0
87654321
87854321
; ;.H; ;.EX~ ~1~a.-. r;.s~ I0
O..
ASCII ..
<).,
o
.....
01101100
87654321
87854321
c:J
1000
87654321
6
SW~D
~
87654321
~.r-f~;ID
-.~~r;.;jDES
ASCII'"' "S
RESERVED
#(;
00110110
67654321
87654321
o
HEX ..
ASCII ..
SHIFT
c:J
1001
87654321
RESERVED {ESCAPE)
~(1 r------.
LENGTH IN
87854321
OCTETS
0
87654321
MOI'IEOATA
HEX", AI)
ASCII '" (space)
10100000
87654321
CONGESTION LEVEL
c:J
1 0 11
87654321
44-7
SEP'95
----
-------------------_._---------------
INTERVIEW 8000 Series 8asic Operation: 951-80424-01
The first info-element data in Figure 44-2, for example, begins with the hex
character °4 . This translates on the field diagrams in Figure 44-3 as a "Bearer
Capability" info element. The next byte, °2 , indicates that the remaining contents
are two bytes long, followed by the end of the data or by another information
element. This means that 1$, "Channel ID," is the next info-element identifier
in the string; and so forth.
Note in the field diagrams in Figure 44-3 that there are four types of single - byte
information element.
6.
Time. The time of the arrival of the end of the frame containing the message at the
DTE or DCE monitor is provided by a 24- hour clock and posted to the trace
display. The clock is accurate to the milli- or microsecond.
When time values are incorporated in data, times posted to the trace display will
not be affected when recorded data is played back, even at varying speeds. To
incorporate time values into recorded data, make the following selections:
•
For bit-image data
Data To Record: • 1.!1m~i1im
nme TICks:
•
(Record Setup menu; see Section 7)
(Front - End Buffer Setup screen; see Section 9)
For character data
Data To Record: fi~R~,:
Tune TICks:
or
Data To Record: @i~ij'
nmencks:
Frame nmestamps:
(Front-End Buffer Setup screen; see Section 9)
nmestamp Resolution: ~g~ or
If time values are not incorporated in data during live recording, times on the
trace during playback will be influenced by "local conditions" such as playback
speed, idle suppression, etc.
7.
Frame Checking. A BOP frame ends as soon as a TE flag or seven I-bits in a row
are detected. If a flag ends the frame, a frame check is performed and the result
is posted both to the data display and to the Bee column of the trace display.
The symbol@] denotes a good frame check, while II symbolizes a bad frame.
II for abort is posted to the displays when a frame is ended by seven 1-bits.
44-8
SEP '95
44 0.931
44.2 Monitor Conditions
When the Q.931 personality package is loaded in (via the Layer Setup screen), a set of
conditions checks DTE and DCE leads both in monitor and emulate modes. This set of
conditions is accessed by the OTE and DeE selections on the first rack of condition softkeys
at Layer 3. See Figure 44-4.
,~,'
,~,
Figure 444 The softkeys for DTE and DeE are used to monitor ISDN protocol events once Layer. 3 has
been entered on the Protocol Spreadsheet.
After the keyword orE (or DeE) is written to the spreadsheet, a rack of softkeys appears
that represent types of message: ALERT, CONN, STATUS, and so forth.
(A) Message Types
The softkeys for the thirty standard as well as "other" message types are illustrated in
Figure 44-5. Press a softkey to write one of these message types to the Layer 3
spreadsheet. OTE or OCE followed by a message - type mnemonic-DTE SUSp, for
example, or DeE REL-is a complete condition and will come true if a matching
message-type is monitored. Call-reference, origination-link, and destination-link
conditions may be added to the simple message-type mnemonic, but they are
optional.
44-9
SEP '95
--------------------.------~.
----
.-.-~---.
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 44-S Message types.
(B) Call Reference Value
A specific call-reference value may be added as a condition to any of the message
type conditions. Once you have pressed the softkey for a particular message type (or
once you have touch-typed the message type followed by a space), the rack of
softkeys shown in Figure 44-6 will appear.
Press the softkey for C_REF=, shown in Figure 44-6. Then enter the call-reference
value as a sequence of hex digits inside quotation marks. The sequence may be from
one to twelve semioctets long. Type each digit as an alphanumeric in the range 0-9
andA-F (ora-f), without using the ~ key. The call reference 7" with flag bit 0, for
example, appears as follows:
CONDITIONS: DTE SETUP C_REF= "7F"
44-10
SEP'95
44 Q.931
FIgUre 44-6 CalI-reference, origination-link., and destination -linkconditionsmaybeadded toa
message-type condition.
Include the origination/destination-flag bit in your string. If the DeE, for example,
gives call reference #4 to a call that originated at a remote link, the entry C_REF= "84"
(with flag = 1) will detect this call reference, while the string "04" (flag = 0) will not
detect it.
(C) Origination/Destination Link
A message-type condition may be set to come true only with respect to calls that
originated locally (or remotely).
To make a message-type condition specific to calls that originated with a user on the
link that is being monitored by the INTERVIEW, press the softkey for ORIG (F2 on
the rack of softkeys in Figure 44-6). Only messages that have zero as the
call-reference flag bit will satisfy this condition.
This condition, for example, looks for a Facility-type message that references a call
that originated locally:
CONDITIONS: DTE FAC ORIG
Or a message-type condition may require remote origination of a call. In that case,
the link being monitored is the "destination" of the call, and you will press the
softkey for DEST, F3 on the rack of softkeys in Figure 44-6. Only messages that have 1
as the can-reference flag bit will satisfy this condition.
SEP '95
44-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
44.3 Display Actions
ENHANCE and SUPPRESS pertain to lines of data on the Layer 3 protocol trace (see Section
44.1). They do not suppress and enhance data on the raw-data display. Raw data is
enhanced and suppressed at Layer 1.
DTE and DeE conditions can trigger an ENHANCE or SUPPRESS action.
(A) Enhance
Whenever a DTE or DeE condition comes true at Layer 3, the message that satisfied
the condition can be enhanced on the Q.931 protocol-trace display, or it can be
deleted from the trace completely. In an actions block on the Protocol Spreadsheet,
press the ENHANCE softkey-(fjJ on the first rack of action softkeys. Figure 44-7 shows
the three softkey subselections beneath ENHANCE. They are REVERSE, BUNK, and LOW
Figure 44-7 Selected messages on the protocol trace may be enhanced or suppressed.
Reverse-image and blink enhancements affect the plasma-display screen. In
addition, a low-intensity enhancement can be applied to screens that are transmitted
to a black-and-white monitor connected at the RS-170 port at the rear of the
INTERVIEW.
Reverse, blink, and low enhancements can be mapped to colors on a color monitor
attached at the INTERVIEW's RGB port (Figure 1-6). See Section 18.2 for an
explanation of how reverse, blink, and low enhancements relate to character and
background colors in the RGB output.
44-12
SEP '95
44 0.931
Figure <14-8 A DCE SETIJP has been enhanced.
Figure 44-8 shows one screen of a Layer 3 protocol trace in which DeE SETUP
messages have been enhanced in reverse video. The trigger that caused this
enhancement was as follows:
CONDITIONS: DCE SETUP
ACTIONS: ENHANCE REVERSE
(8) Suppress
Individual message-types that are suppressed in Layer 3 actions are deleted from the
trace display. Here is an example of an action that suppresses all DTE Information
messages:
CONDITIONS: DTE INFO
ACTIONS: SUPPRESS
SEP '95
44-13
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
44-14
SEP '95
45 55#7 Layer 1
45 SS#7 Layer 1
SEP '95
45-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
PROTOCL
NO DISP
Figure 45-1 SS#7 Dual-line data display, with 7E flags suppressed and redundant LSSUs and FISUs compressed.
**
ppression
tup
**
SUPPRESS
Main Channel Mode:
condar~ Channel Mode: TRANSPARENT
FtgUre 45·2 Configuration screens for the SS#7 Suppression and SS#7 Compression personality packages for Layer 1.
45-2
SEP '95
45 SS#7 Layer 1
45 SS#7 Layer 1
SS#7 (CCSS#7) is an abbreviation for the CCnT -defmed Common Channel Signalling System
#7. The IN1ERVIEW 8000 Series provides modifiable data display at Layer 1 and special displays
for Layer 2 (link) protocol and for Layer 3 (network management) protocol. Automatic selections
for SS#7 protocol appear at Layers 2 and 3 of the Protocol Spreadsheet when the correct protocol
packages are loaded.
45.1
SS#7 Run-Time Displays
(A) Data Display
Figure 45-1 shows SS#7 data being monitored as dual-line data. 7E flags have been
suppressed on the Line Setup screen and Fill-In Signal Units (FISUs) and Link
Status Signal Units (LSSUs) have been compressed. As with all dual-line displays,
TD and RD data appear on alternate lines and the RD data is underlined. Time fill
characters maintain the timing relationships between RD and TD characters,
accurate to within one character on the display.
(8) SS#7 Layer Traces
An SS#7 Layer 2 trace is available when SS#7 protocol is loaded at Layer 2. A
Layer 3 trace is available when SS#7 is loaded at Layer 3. Uyou select illM~\~!~ifJty
and Layer.
or
as the display, this trace will be active when you press~. Refer
to Sections 46 and 47 for more information on and examples of these traces.
45.2 Setup for SS#7
Three steps are involved in setting up for SS#7 protocol. First, load the desired protocol
from the Layer Setup screen as described in Section 8. Then select the correct Mode and
data Fonnat on the Line Setup menu, and, finally, select the options you prefer on the
Display Setup menu.
(A) Layer Setup
SS#7packages are available at Layers 1, 2, and 3. The Layer 1 packages provide
data compression or suppression and are described at the end of this section.
Options available with the Layer 2 and the Layer 3 packages are discussed in Sections
46 and 47, respectively.
45-3
-
-
'
-
-
-
.
-
-
~
"
SEP'95
••- - - - - - - - - - - - - - - - _ . _ ".._ . _ _ _ _ _ _m_UIi'i_lIIJlU_IIIIl_Wh_ _ _ _
• _ _ _ _ _......
INTERVIEW 8000 Series Basic Operation: 951-80424-01
(8) Line Setup
The Format selection on the Line Setup menu should be
(Bit-Oriented
Protocol) when SS#7 is analyzed. This and other Line Setup selections are described
in Section 5.
(C) Display Setup
Select initial display options on the Display Setup menu. All available display modes
are applicable to SS#7 data. Protocol displays specific to SS#7, which appear only
when an SS#7 Personality Package has been loaded, are described in Sections 46 and
47. Data, Display Window, and Program nace displays are described in Section 6.
You have the option of suppressing 7E flags on the Display Setup menu. See Section
6.3(C).
Data suppressed from the display is available for triggering in real-time. However, it
is not available for triggering when character-oriented data from the screen buffer is
played back.
It is also possible to suppress all occurrences of a particular type of frame from the
display. Refer to the description of the SUPPRESS action in Section 46.
45.3 SS#7 Compression at Layer 1
When the L"ayer 1 package SS7_CMPRESN is loaded, redundant FISUs and LSSUs are
suppressed from the character display and also the Layer 2 trace display in Run mode.
That is, only the first in a series of identical Link Status or Fill-In Signal Units is
displayed and presented to the trigger program. Subsequent identical units are
compressed, until a different type of signal unit is transmitted on the same side of the line.
When you are operating the INTERVIEW in a dual-port environment, you may
configure the unit to compress the data on the main channel only, the secondary channel
only, or on both channels. A configuration screen is accessible when the SS7_CMPRESN
Layer 1 package is loaded; press PROTSEL, LAYER-1 (see Figure 45-2). You may designate
(l~!lf~ or'i11~;§:1 for each channel.
NOTE: When running an application program such as GSM
Dual-Protocol Trace (LAPD/SS#7 MTS), OPT-951-106-1, and
monitoring SS#7 data on one port, the user may wish to compress or
suppress the data on the other port.
When you are operating in a single-port environment, the choice you make in the Main
will be utilized for your data at all times. If you choose ii~~i\ffii in
this field, data compression will not take place. The selection in the secondary Channel Mode
field is ignored when ;\i;,'_m?@.~~: is not selected (or not an option) on the TIM Setup
screen.
Channel Mode field
45-4
SEP '95
45 8S#7 Layer 1
NOTE: Additional overhead is added when this personality package
is loaded, causing some performance degradation. This occurs with
either choice on the Setup screen. If you are operating in a
single-port environment and do not wish data compression to occur,
we recommend that you load ~~~i.'¥ at Layer 1 rather than
simply choose Main Channel Mode: ~t~~~ on the Setup screen.
Compare Figure 45-3 to Figure 45-4 (in which FISUs and lSSUs have been compressed).
NOTE: The number of suppressed signal units and flags can be
monitored via C variables. Refer to Table 78-1.
Bit-image recording of data is not affected by Layer 1 compression. Simply select and
load NO PACKAGE at Layer 1 and play the same bit-image data back again., to cancel the
effects of compression. All the original Link Status and Fill-In Signal Units will be
presented to the screen display and the triggers.
45.4 SS#7 Suppression at Layer 1
The Layer 1 SS7_SUPP package is similar to the compression package described above.
The suppression package, however, passes only Message Signal Units (MSUs) up to Layer
2. Link Status Signal Units are suppressed and all Fill-In Signal Units are suppressed,
except the fIrst one in which the value of the Bm has been inverted.
A similar confIguration screen is present for channel setup in a dual-port environment
when the SS7_suPP Layer 1 package is loaded (see Figure 45-2).
NOTE: When running an application program such as GSM
Dual-Protocol Trace (LAPDISS#7 MTS), OPT-951-I06-1, and
monitoring SS#7 data on one port, the user may wish to suppress or
compress the data on the other port.
The suppression package has one associated C variable, ss7_compression_mode. When the
value of this variable is zero, FlSUs are suppressed; when its value is non -zero, FISUs are
compressed, exactly as in the SS#7 compression package.
SEP '95
45-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
SRC
fyP[
~:;:
BIB
BSf'l
r-::B
r-SN
1 IM~
BeC
lIMl
Eee
•
5
Figure 45·3 All LSSUs and FISUs detected are displayed on this screen.
SRC
lYPE
~I
00
BIB
3~N
~IE
=
FSN
-
Figure 45-4 Redundant LSSUs and FISUs have been compressed in this data.
45-6
SEP '95
46 88#7 Layer 2
46 5S#7 Layer 2
46-1
SEP'95
-
------
-
-------------------------------------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
**
La~er
La~er
La~er
La~er
La~er
La~er
La~er
Ke~
1
2
3
4
5
6
7
La~er
Setup
**
Package:
Package:
Package:
Package:
Package:
Package:
Package:
To Load The Selected Packages
Figure 46-1 The SS#7 personality package for Layer 2 is loaded from the Layer Setup screen.
46-2
SEP '95
46 SS#7 Layer 2
46 55#7 Layer 2
SS#7 (CCSS#7) is an abbreviation for the CCITI -defined Common Channel Signalling System
#7. At Layer 2, SS#7 is a "layer personality package" of functions that are loaded into memory
from disk via the Layer Setup screen. Figure 46-1 shows the Layer Setup screen configured to load
in the Layer 2 SS#7.package from the hard disk. Refer to Section 8 for details on operating the
Layer Setup screen.
46.1
Set Up for SS#7
(A) Layer Setup
The SS#7 package at Layer 1 allows you to compress redundant frames, as explained
in Section 45.
The Layer 2 SS#7 package consists of the following:
•
A protocol trace (illustrated in Figure 46-2) that distills from 5S#7 data the Level
2 events that have protocol significance. This trace is accessible by softkey in
Run mode at all times.
•
A group of conditions and actions at Layer 2 on the Protocol Spreadsheet that
facilitate SS#7 programming. Figure 46-4 shows the softkey path to the first rack
of condition softkeys when the 5S#7 package is loaded in at Layer 2.
(8) Line and Display Setup
Be sure that the Format selection is
(for Bit-Oriented Protocol) when you are
testing SS#7. Select display options on the Display Setup menu. These options are
discussed in Section 45.2.
46.2 Protocol Trace
The Layer 2 5S#7 package includes an automatic frame-trace display that summarizes
link -level activity. This trace mode is enabled whenever the unit is in Run mode, both
real-time and frozen.
While the unit is in Run mode, press the softkey for L2TRACE to bring the protocol trace for
SS#7 Layer 2 to the screen. (If the SS#7 package for Layer 3 is also loaded in, the
L2TRACE softkey will appear after you have pressed PROTOCt., @ on the primary rack of
display-mode softkeys.)
SEP'95
46-3
------------------_._----------------------_._----
INTERVIEW 8000 Series Basic Operation: 951-B0424 -01
When running in High-Speed Frame Mode, more data could be passed to Layer 2 than
there is room for in the buffer; this will cause an FEB overrun. If this happens, the error
message FE Buffer Overflowed - Some Frames Lost will appear on the prompt line. The first
time an FEB overrun occurs, an audible alarm will also sound; subsequent reccurrences
will cause only the message to display (without any alarm). The trace will restart again but
some data is lost with each occurrence.
Figure 46-2 is an example of the Layer 2 trace display. Each horizontal row in the trace
represents a frame.
Figure 46-2 SS#7 Layer 2 Protocol Trace.
(A) The Protocol Trace in Freeze Mode
Press E3 to prevent the addition of new data to all the display buffers, including the
trace buffers. The frozen trace display may be scrolled through or paged through.
The top line always is the cursor line (though there is no actual cursor on the trace
display). Pressing cmJ or ill moves the viewing "window" down relative to the data to
add one line of fresher data to the bottom of the screen. Pressing ~ or ffl moves
the viewing window up to add a line of older data to the top of the screen.
Depression of the r:=J key adds 15 lines-one full page-of newer frames to the
frozen trace screen. Depression of (1IU adds 15 lines of older frames.
The frame displayed on the top line offrozen trace-data will appear as the first
frame in the raw-data or data-plus-leads display. Compare Figure 46-2 with
Figure 46-3. To view the raw data that generated a particular line in the trace display,
46-4
SEP '95
46 SS#7 Layer 2
use f1ID or {Ii} (or ffl or l±J) to move the line in question to the top of the screen.
Then press one of the data softkeys. Figure 46-3 shows part of a dual-line data
screen in Freeze mode. The first frame in the display is the same one that is traced at
the top of Figure 46-2.
Figure 46-3 Data-display of Protocol Trace shown in Figure 46-2.
(8) Trace Columns
The columns in the protocol trace for Layer 2 SS#7 are explained below.
1.
Source. The SRC column identifies the lead on which the signal unit was
monitored, TO (OTE) or RD (DeE). Just as on the data-display, RD data is
underlined.
2.
Type. The second column, TYPE, lists the signal-unit type [STATUS= for a Link
Status Signal Unit (LSSU), FILLJN for a Fill-In Signal Unit (FISU), or MESSAGE
for a Message Signal Unit (MSU)J. For an LSSU, the status type is also given as
an abbreviation.
The format for FISUs and LSSUs are shown at the end of this section, in
Figure 46-10 and Figure 46-11. Abbreviations and values for Link Status Signal
Unit types are defined in Table 46-1.
Table 46-1
LSSU Status Field
(Bits 2 -0 of first Status Field Octet)
Acronym
o
Definition
N
Out of Align
Normal
E
Emergency
OS
OUt of Service
Processor Outage
PO
B
Binary Value
Busy
000
001
010
011
100
101
Note: Bits 7 -3 of the First Status Field Octet (SFO) are spare.
A second Status Field Octet may be present
SEP '95
46-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Length indicator. The value of the Length Indicator byte (u) is given in the third
column of the display. A value of 00 here indicates a FISU, a value of 01 or 02
indicates an LSSU, and a hex value of 03-3F indicates an MSU.
3.
4. Backward indicator bit. The fourth column, labeled BIB, provides the value of the
Backward Indicator Bit.
5. Backward sequence number. The hex value of the Backward Sequence Number
(SSN) is listed in the next column.
6.
Forward indicator bit. The FIB column provides the Forward Indicator Bit.
7.
Forward sequence number. The Forward Sequence Number (FSN) is displayed in
hex in the next column.
8.
Time. The time of the arrival of the end of the frame at the DTE or DeE monitor
is provided by a 24- hour clock and posted to the trace display. The clock is
accurate to the milli - or microsecond.
When time values are incorporated in data, times posted to the trace display will
not be affected when recorded data is played back, even at varying speeds. To
incorporate time values into recorded data, make the following selections:
•
For bit - image data
Data To Record: : !i.U€l:t) (Record Setup menu; see Section 7)
lime Ticks:
(Front - End Buffer Setup screen; see Section 9)
•
For character data
Data To Record: F~~t:
lime licks:
or
Data To Record: !:'il~~%;{
lime licks:,;.:;;
Frame limestamps:
(Front-End Buffer Setup screen; see Section 9)
Timestamp Resolution: ';:.JI or
If time values are not incorporated in data during live recording, times on the
trace during playback will be influenced by "local conditions" such as playback
speed, idle suppression, etc.
9. Frame checking. An SS#7 frame ends as soon as a 71; flag or seven 1-bits in a
row are detected. If a flag ends the frame, a frame check is performed and the
result is posted both to the data display and to the Bee column of the trace
display_ The symbol@} denotes a good frame check, whileD symbolizes a bad
frame.
46-6
SEP '95
46 SS#7 Layer 2
II for abort is posted to the displays when a frame is ended by seven I-bits.
46.3 Monitor Conditions
When the Layer 2 SS#7 personality package is loaded in (via the Layer Setup screen), a
set of conditions checks DTE and DeE leads both in monitor and emulate modes. This
set of conditions is accessed by the DTE and DeE selections on the ftrst rack of condition
softkeys at Layer 2. See Figure 46-4.
Figure 46-4 To monitor line conditions, first select DTE or DeE.
(A) Signal- Unit Types
Mer the keyword DTE (or DeE) is written to the spreadsheet, a rack of softkeys
appears that represents types of Signal Units.
1.
Fill-In and Message. The softkeys for FlLLJN (Fill-In Status Unit), MESSAGE
(Message Signal Unit), and STATUS= (Link Status Signal Unit) are illustrated in
Figure 46-5. Press a softkey to write one of these signal-unit types to the Layer
2 spreadsheet.
DTE (or DeE) ALLJN and DeE (or DTE) MESSAGE are complete conditions and will
come true if a matching frame is monitored. BIB, FIB, and BCC conditions may be
added to the simple frame mnemonic, but they are optional.
2.
SEP'95
Link Status.
DTE (or DeE) STATUS= is not a complete condition. Select an LSSU
type from the third softkey rack shown in Figure 46-5. The full set of
abbreviations and their meanings is given in Table 46-1.
46-7
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Figure 46-5 Frame types.
(B) Forward and Backward Indicator Bits
For any SS#7 frame type, you have the option of specifying the value of the
Backward Indicator Bit (BIB= 0, BIB= 1) and the value of the Forward Indicator Bit
(FIB= 0, FIB= 1):
CONDITIONS: DTE FILLJN BIB= 1 FIB= 1
The softkey path to BIB and FIB is shown in Figure 46-6. If you omit either the FIB or
the BIB field. the omitted FIB or BIB is not checked in the received frame. Press 8 to
bypass the BIB and FIB conditions.
To make BIB and FIB selections for Link Status Signal Units, follow the softkey path
shown in Figure 46-7.
(C) BCC Conditions
For any SS#7 frame type, you also have the option of specifying a Bee or abort
condition:
CONDITIONS; DTE MESSAGE BD_BCC
The softkey path to Bee selections for Fill- In and Message Signal Units is shown in
Figure 46-6. Press 8 to bypass the BCC condition.
46-8
SEP '95
46 SS#7 Laver 2
Figure 46-6 You may specify BIB, FlB, or Bee conditions immediately following FILLjN or
MESSAGE selections.
To make BCC selections for Link Status Signal Units, follow the softkey path shown in
Figure 46-7.
Figure 46-7 You must specify the type of Unk Status Signal Unit for a STATUS= spreadsheet
condition. BIB, FIB, and Bee conditions may then be selected.
SEP '95
46-9
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
46.4 Display Actions
ENHANCE and SUPPRESS pertain to lines of data on the Layer 2 protocol trace (see Section
46.2). They do not suppress and enhance data on the raw-data display. Raw data is
enhanced and suppressed at Layer 1.
OTE and DCE conditions can trigger an ENHANCE or SUPPRESS action. These conditions are
active when the INTERVIEW is in monitor mode or in either of the emulate modes.
(A) Enhance
Whenever a OTE or OCE condition comes true at Layer 2, the frame that satisfied the
condition can be enhanced on the SS#7 Layer 2 protocol-trace display, or it can be
deleted from the trace completely. In an actions block on the Protocol Spreadsheet,
press the ENHANCE softkey-ITIJ on the first rack of action softkeys. Figure 46-8 shows
the three softkey subselections beneath ENHANCE. They aTe REVERSE, BUNK, and LOW
Figure 46-8 Selected frames on the protocol trace may be enhanced or suppressed.
Reverse-image and blink enhancements affect the plasma-display screen. In
addition, a low-intensity enhancement can be applied to screens that are transmitted
to a black-and-white monitor connected at the RS-170 port at the rear of the
INTERVIEW.
Reverse, blink, and low enhancements can be mapped to colors on a color monitor
attached at the INTERVIEW's RGB port (Figure 1-6). See Section 18.2 for an
explanation of how reverse, blink, and low enhancements relate to character and
background colors in the RGB output.
46-10
SEP '95
46 SS#7 Layer 2
Figure 46-9 DlE Message Signal Units have been enhanced.
Figure 46-9 shows one screen of a Layer 2 protocol trace in which DTE MSUs have
been enhanced in reverse video. The trigger that caused this enhancement was as
follows:
CONDITIONS: DTE MESSAGE
ACTIONS: ENHANCE REVERSE
(8) Suppress
Individual frames that are suppressed in Layer 2 actions are deleted from the trace
display. Figure 4()"8 shows the softkey path to SUPPRES.
46.5 SS#7 Emulation
You may use SS#7 protocol for interactive testing of a DTE or a DCE. However,
transmitted strings must be entered manuaUy, since no automatic selections are currently
available for emulation, either at Layer 2 or Layer 3.
46.6 SS#7 Frame Structures and Values
The format for Fill- In Signal Units is given in Figure 46-10.
The format for Link Status Signal Units is given in Figure 46-11. Table 46-1 lists possible
LSSU status values.
SEP'95
46-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Refer to Section 47 for the structure of a Message Signal Unit and for the differences in
CCITI and ANSI (US Standard) frame format. Also, consult Section 47 for any
information pertinent to SS#7 Level 3.
NOTE: Frame format, unless otheIWise stated, reflects the frame as
displayed on the screen, not the actual transmission order.
SyteO
:
I
I
J
B I BaCkward
I I Sequence
B I Number
I
I
1E
Flag
.
Length in BIts:
•8
'
2
3
~
I
F I FoIward
I I Sequence
B I Number
I
I
"'"'!. •7 . "'"I' . •7
'
"'" '-.--'
2
1E
Check Bits
I=r
,
' t
•15
",
6
Flag
U
s
elB: BacJ2)
,
Length in Bits
8
(lSSlO right of each byte)
5
7
6
;
SlC
~
; ;
I : I
~
,'.l$eMee
w t
f •
l'oInt Code
(tlf'C)
indicator
ole S
I I
r
k
I
t
~
!
"'"'....,~
122
I
I
I
I
I
I
I
us (ANSI)
FOIImII
4
f:lyte 4
Sll'
, ..
u
5
•
6
0esIInaIi0n Point
Code(OPC)
kit I
I Y
f
""" """ ~ -
II
•
I SI.S
I
I
7
:
I
I
I
I
I
I
~
'
8
"'"""""
4
9
.t .,
22<4
•
Qfjg~
Point
(OPe)
~
4
Head$'
(Notes)
I
I
4
14
14
l
N I f> I
e I r ,
w I 0 I indIcaIor
o I r I
f I i I
SIB: Backward Indtcator Bit
SI.S: SigNllling Link SeIecIion
I
.
t1il$eMee
SIF: Signalling lntormlllion Field
FIB: Forward IndiI:aIor Sit
I
I
I
I
I
I
9
8
U2
24
,
4
'
8
11
10
12
~A
I
I
I
I SlS
I
I
~
(NoteS}
V~...., .
' ""'3""
5
•8
t
Figure 47·9 Format ofa Message Signal Unit (MSU).
SEP'95
47-13
_--_.._ _ - --_._.._-_._----_..._------------------------------------
.. _---_ ....•........•.
.. ....
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
NOTES:
1. The Length Indicator for an MSU has a value of 3 to 63 (3 to 3F,
hex).
2. The Service Information Octet contains a Service Indicator
(Thble 47-1), Bits 3-0 and a Network Indicator, Bits 7-6. In
ANSI (US) format only, a Priority Code is present in Bits 5-4.
Bits 5 -4 are spare in CCnT International or National format.
3. The Signalling Information field contains a Label and a Header.
There are two label formats: ANSI (US), a 56-bit format, and
CCIIT, a 32-bit format. The CCnT National label follows the
same format as a CCITT International label (see expansions,
this figure). The header is located at Octet 9 in CCITT
International or National format and at Octet 12 in ANSI
format.
4. The two octets preceding the closing flag are block check results.
Only the first octet will appear in SS#7 line data. The second is
replaced by a block check symbol (@l,II,II). See Section 10 for
an explanation of block checking in Bit-Oriented Protocols.
5. Network Indicators:
00-01 = CCITT International format
10-11 = ANSI (US Standard) or CCnT National format
6. The Priority Code has a value of 0-3 for ANSI format. These
bits are undefined for CCITT International format. They are
also undefined in CCnT National format.
7. A Service Indicator with Bits 3-2 = 01 (in either ANSI or
CCITT International or National format) indicates a User Part.
The subsequent structure of the signal unit is dependent on the
User Part Type and is not reflected by this figure. Values for TUP
and ISUP headers are given in Table 47-4 and Table 47-5.
47-14
SEP'95
47 SS#7 Laver 3
8. The header gives the NETM Header (Table 47-2), SCCP Header
(Table 47-3), or NTR/NTS Header.
In NTR/NTS Messages (S10 = 0001), the four low-order bits
detennine the type:
=LTM (Signalling IJnk Test Message)
0010 =LTA (Signalling Link Test Acknowledge)
0001
The four high -order bits are defined as 0001 for Test (NTR/NTS)
Messages.
9. Since the label in CCITT International or National fonnat is not
byte-aligned, the values displayed in hexadecimal on the
INTERVIEW screen are skewed. As a result, CCITT labels
must be interpreted as shown in Figure 47-10.
SEP'95
47-15
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
OPe .. 3412
Label values enlered in spreadSheet conditions:
OPC=0856
Bit sequence !hat will satisfy the OPC" and ope" ConditioN;:
,
ByteS
Byter
ByteS
II
I
I
I
I
0010
0111
I
I
I
HEADER
Byte 5
I
0001
0101
1fl
0100
0001
0010
I
I
.........,:..
(LSB Transmi1leO First)
I
""
'"'
OPC
"
¥
OPC
Xmit
Os
Data as it appears
fm hex) on INTERVIEW screen or in send string:
Byte 6
ByteS
Byte 7
ByteS
:
I
I
I
I
0001
0010
1~1
I
I
0001
0100
0101
0111
.
~
4
OPe
''''PI'
I
0010
HEADER
I
I
I
I
»
,t
•
oPC
:
'....,~
SLS
ope
- - - - - - Distribution of Label Values
- - - - - - - - Hex Values Displayed
(or Enlered in Xmit Strings)
(MSB 10 left of each byte)
Figure 47,10 CCITI labels are entered and transmitted as shown.
47-16
SEP'95
47 SS#7 Layer 8
TabJe41..1
MSU Service Indicators
(Bits 3-0 Of the SIO)
Meaning
Mnemonic
NETtA (2)
NTR (2)
NTS (2)
sccP (2)
TUP (1)
ISUP (1) (2)
DUPO
DUP1
(1)
(2)
(3)
(4)
Network Management
Network Test &. Management Regular
Network Test &. Management Special
Signalling Connection Control Part
Telephone User Part
ISDN User Part
Data User Part (call/Circuit)
Data user Part (Facility Aegis/Cane)
Spare
Spare
Spare
Spare
Binary Value
0000
0001
0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
1100
Spare
Spare (3)
1101
Spare (4)
Spare
1110
1111
Containsa CIC.
Contains an SLS.
ECIS6 for ANSI (US Standard) format.
Reserved, if ANSI format.
47-17
SEP '95
------- ----------_...
_--, -------
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
Table47~2
Network Management Headers
(Octet 9 for CCITT Format; Octet 12 for ANSI-US Format)
Mnemonic
Message
Hex
Added
Bytes
Shown
ANSI
COO
COA
CBD
CBA
ECO
ECA
RCT
TFC
TFP
TCP (1)
TPA
TFR
TCR (1)
TFA
TCA (1)
TAA
RSP (1) (4)
RSR (1) (4)
RCP (1)
RCR (1)
UN
LUN
UA
iliA
UD
LFU
ill (1)
LAI (1)
DLC
CSS
CNS
CNP
(1)
(2)
(3)
(4)
47-18
Changeover Order
Changeover Acknowledgment
Changeback Declaration
Changeback Acknowledgment
Emergency Changeover Order
Emergency Changeover Acknowledgment
Signalling Route-Set-Congestion-Test
Transfer Controlled
Transfer Prohibited
Transfer Cluster Prohibited
Transfer- Prohibited Acknowledgment
Transfer Restricted
Transfer Cluster Restricted
Transfer Allowed
Transfer Cluster Allowed
Transfer-Allowed Acknowledgment
Route-Set-Test Destination Prohibited
Route-Set- Test Destination Restricted
Route-Set-Test Cluster Prohibited
Route-Set- Test Cluster Restricted
Unk Inhibit
Unk Uninhibit
Unk Inhibit Acknowledgment
Unk Uninhibit Acknowledgment
Unk Inhibit Denied
Unk Forced Uninhibit
Unk Local Inhibit Test
Unk Remote Inhibit Test
SignaUing-Data-Unk Connection Order
Connection Successful
Connection Not Successful
Connection Not Possible
11
21
51
61
12
22
13
23
14
24
CCITT
2
2
2
2
1
1
0
4
3
3
1
1
0
0
0
2
2
24
34
44
54
64
64
15
25
35
45
16
26
36
46
56
66
3
3
3
3
3
3
3
3
1
2
2
0
0
0
0
0
0
76
86
18
2
28
38
48
2
0
0
0
ANSI (US) format only.
CCITT format only.
CCITT format only, National option.
CCITT format uses the generiC Route-Set- Test (RST) for both hex 15 and hex 25. This
mnemonic is not presented on the softkey rack: it has been replaCed by the ANSI designations
RSPand RSR.
SEP '95
47 SS#7 LayerS
Table 47-3
secp Message Headers
(Octet 9 for CCITT International or Nattonal Format; Octet 12 for ANSI-US Format)
Message
Mnemonic
CR
CC
CREF
RlSo
RLe
0T1
oT2
AK
uor
UoTS
ED
EA
RSR
RSC
ERR
IT
SEP '95
Connection Request
Connection Confirm
Connection Refused
Released
Release Complete
Data Form 1
Data Form 2
Data Acknowledgment
Unitdata
Unltdata Service
Expedited Data.
Expedited Data Acknowledgment
Added
Bytes
Shown
Hex
01
02
03
04
US
Int'l
4+
7+
4+
7+
4+
7+
4+
7+
6
4+
05
6
06
07
6+
3+
5+
08
09
OA
4
5
08
DC
1+
1+
4+
1+
1+
3+
3
3
Reset Request
Reset Confirmation
00
7+
7+
OE
6
6
Error
OF
4+
4+
Inactivity Test
10
3
3
47-19
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Table 47-4
Telephone User Part (TUP) Message Headers
Mnemonic
lAM
IAI
SAM
SAO
GSM
COT
CCF
GRO
ACM
CHG
SEC
CGC
NNC
ADI
CFL
SSB
UNN
LOS
SST
ACB
DPN
MPR
EUM
ANU
ANC
ANN
CBK
CLF
RAN
FaT
CCl
EAM
RLG
BLO
BLA
UBL
UBA
CCR
RSC
MGB
MBA
MGU
MUA
47-20
Message
Initial Address Message
Initial Address Message With Additional Information
Subsequent Address Message
Subsequent Address Message With One Signal
General FOlWard Set-up Information Message
Continuity Signal
Continuity-Failure Signal
GeneralReque~Message
Address Complete Message
Charging Message
Switching-Equipment-Congestion Signal
Circuit-Group-Congmion Signal
National-Network - Congestion Signal
Address Incomplete Signal
GalI- Failure Signal
Subscriber-Busy Signal
Unallocated-Number Signal
Une-Out-Of-Service Signal
Send-Special-Information Tone Signal
Access Barred Signal
Digital Path Not Provided Signal
Misdialed Trunk Prefix
Extended Unsuccessful Backward Set-up Info Message
Answer Signal, Unqualified
Answer Signal, Charge
Answer Signal, No Charge
Clear-Back Signal
Clear-Forward Signal
Reanswer Signal
Forward-Transfer Signal
Calling Party Clear Signal
Extended Answer Message Indication
Release-Guard Signal
Blocking Signal
Blocking -Acknowledgment Signal
Unblocking Signal
Unblocking-Acknowledgment Signal
Continuity- Check - Request Signal
Reset- Circuit Signal
Maintenance Group Blocking
Maintenance Group Blocking Acknowledgment
Maintenance Group Unblocking
Malntenance Group Unblocking Acknowledgment
Hex
Added
Bytes
Shown
11
3+
3+
1+
21
31
41
12
32
42
13
14
24
15
25
35
45
55
65
1
2+
0
0
0+
0
0
0
0
0
0
75
85
95
0
0
AS
0
0
85
C5
F5
0
06
0
3
0
16
0
26
36
46
0
0
0
56
0
66
0
0
0
0
76
F6
17
27
37
47
0
67
0
0
0
0
77
0
18
1+
1+
1+
1+
57
28
38
48
SEP '95
47 SS:fI7Lmr3
Table 47-4 (Continued)
Telephone User Part (TUP) Message Headers
Mnemonic
Message
Hex
Added
Bytes
Shown
HGB
HBA
HGU
HUA
GRS
GRA
SGBt
SBAt
SGut
SUAt
CFM
CPM
CPA
CSV
CVM
CAM
CU
t
SEP'95
Hardware Failure Group BlOCkIng
ijardware Failure Group BlockIng Acknowledgment
Hardware Failure Group Unblocking
Hardware Failure Group Unblocking Acknowledgment
Circuit Group Reset Message
Circuit Group Reset-acknOWledgment Message
Software Generated Group BlOcking Message
Software Generated Group Blocking-Acknowledgment
Software Generated Group Unbiooking Message
Software Generated Group UnblOCkIng-Acknowledgment
cess Facility Message
Called Party Free Message
Called Party Answer
Closed User Group SeIeclionNalidation Request
CloSed User Group Validation Cheak
Closed User Group SelectionNalidation Response
Connected Une Identity
58
68
78
88
93
AS
as
C8
OS
E8
19
29
39
49
59
69
79
1+
1+
1+
1+
1+
1+
1+
1+
1+
1+
1+
0+
0+
0+
3+
5
1+
National option.
47-21
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Table 47-5
ISUP Message Headers
Mnemonic
lAM
SAM
INR
INF
COT
ACM
FOT
ANM
UBM
REL
PAU
RES
RLSD
RLC
CCR
RSC
BLO
UBL
BLA
USA
GRS
CGB
CGU
CGSA
CGUA
CMR
CMC
RCM
FAR
FAA
FRJ
FAD
FAI
CSVR
CSVS
DRS
PAM
GRA
47-22
Message
Hex
Added
Bytes
Shown
Initial Address
Subsequent Address
Information Request
Information
Continuity
Address Complete
Forward Transfer
01
02
03
04
05
06
08
5+
0+
1+
1+
Answer
09
Unsuccessful Backward Set-up Information
Release
Pause
Resume
Released
Release Complete
Continuity Check Request
Reset Circuit
Blocking
Unblocking
Blocking Acknowledgment
Unblocking Acknowledgment
Reset Circuit Group
Circuit Group Blocking
Circuit Group Unblocking
Circuit Group Blocking Acknowledgment
Circuit Group Unblocking Acknowledgment
Call Modification Request
Call Modification Completed
Reject Connect Modify
Facility Request
Facility Accepted
Facility Reject
Facility Deactivated
Facility Information
Closed User Group SelectionNalidation Request
Closed User Group SelectionNalidation Response
Delayed Release
Pass Along
Reset Circuit Group Acknowledgment
OA
OS
00
OE
OF
10
1
2+
0+
2+
1+
0+
0+
0+
0
0
11
0
12
0
13
0
14
0
0
15
16
0
17
0+
1+
1+
1+
1+
1+
1+
1+
1+
1+
2+
1+
2+
0+
18
19
1A
1B
1C
10
1E
iF
20
21
22
23
25
26
1+
27
28
0+
0+
0+
29
SEP'95
48 SMDS
48SMDS
INTERVIEW 8000 Series units now support applications for monitoring and emulation on the
SMDS (Switched Multimegabit Data Service) SNI (Subscriber Network Interface) at Tl data rates
and DX! ( Data Exchange Interface) at Tl and El data rates with no additional hardware
requirement.
•
The SMDS SNI for Tl is defined in Bellcore document TR - TSV -000772 as a public service
offering. The sm is based on 53-byte cells and uses a PLCP (Physical Layer Convergence
Protocol) to map cells onto the Tl framed data streams.
NOTE: The SMDS specifications require all octets are transmitted most
significant bit first.
To record at these rates with SCSI drive, select the following:
SETUP:
LINE:
Sync Char:
'F 14
HS Frame Mode: ¥J'itII~:
RECORD:
capture Memory: ~~_1~
..-
........ No
;f~;
:~
Data To Record: ~1I;
DAT Record Size:
Stop at:
•
w~,~,&w«
t_~
user choice
The DXI protoCol is used between routers and SMDS DSUs. It is in BOP format with an
optional 32-bit CRC.
To record at these rates with SCSI drive, select the following:
SETUP:
LINE;
Format: ~1.~%~
High Speed Frame Mode:
RECORD:
Capture Memory:
Disk No: ~1I1
Data To Record: $t.t:~t'lJ,t~
DAT Record Size: ~_t
Stop at
user choice
Bec:
CClTT Polynomial:
\_;@!i or a i .
Monitoring and emulating at up to 2.048 Mbps circuit may be accomplished using application
programs specifically designed for the INTERVIEW 8000 units.
SEP'95
48-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
48-2
SEP '95
49 ATM
49ATM
INTERVIEW 8800 TURBO units now support applications for monitoring and emulation in ATM
(Asynchronous Transfer Mode) with no additional hardware required:
Trace and Statistics: Asynchronous Transfer Mode (TlIEl) [OPT-951-232-1] and
Emulation with Trace and Statistia: Asynchronous 1kmsferMode (TUE1) [OPT-951-233-1].
ATM for Tl is defined in the ATM Forum 081 ATM UN! (draft) Specification and the ITU Draft
Documentation 1.432 and G.804. ATM is based on 53-byteceUs; the INTERVIEW decodes it using
either a PLCP (Physical Layer Convergence Protocol) to map cells onto the Tl framed data streams
(via 576-byte superframe) or the standard ATM BEC (Header Error Control) framing.
49.1
Recording ATM over T1/E1Data with the INTERVIEW
To record TllEl data at ATM rates with ·a SCSI drive in an INTERVIEW 8800 TURBO
unit, setup the following parameters:
SETUP:
UNE:
Format:
~"I
Sync Cbaracter:
GI'" 14
(when using PLCP framing; otherwise not
applicable)
"_"A.
~tlli~~'~
HS Fram
. e ...
_ . ~il'~"""
HEC CRC-a Coset:
Ss
Payload ~bJed: user choice
PLCP Framing: user choice
RECORD:
Capture Memory: ~~~I~Jf
DiskNo: ~_
Data To Record: t'1:~~i.fMI~A
DAT RecorcfSi2.e: R&ll
Stop at: user choice
49.2 Overview
Asynchronous Transfer Mode (ArM) is a technology· that offers the "bandwidth on
demand" £eatures of packet ~switching with the high speeds required for LAN and WAN
networks ~ay. This cell-relay technology operates independently of the type of
SEP '95
49-1
INTERVIEW 8000 Series Basic Operation: 951-80424-01
transmission being generated at the upper level and of the type and speed of the physical
layer medium being used. This allows sending of virtually any type of transmission (e.g.,
voice, data, video) in a single integrated data stream operating over any medium ranging
from existing Tl!Ellines to SONET OC-3 at speeds of 1.5 to 155 Mbps - and faster.
The technology permits both public (i.e., RBOC or local carrier) and private (i.e., LAN or
LAN-to-internal switch) ATM networks. This capability gives a seamless and
transparent (to the user) connection from one end user to another, whether in the same
building or across two continents.
(A) OSI Layer Similarity
At the end user site, ATM operates with a layered structure similar to the OSI
7 -layered modeL However, ATM only addresses the lower two layers of this model:
•
Layer 1 - Physical Medium
•
Layer 2 - Data Link
All other layers are only part of the encapsulated information portion of the cell,
which is passed transparently through the ATM network.
These two OSI layers are handled by three layers for ATM:
•
Physical Layer - This layer defines the medium for transmission, any
medium-dependent parameters (e.g., the Quality of Service requirements), and
the framing used to find the data contained within the medium.
•
ATM Layer - This layer provides the basic 53-byte cell format and defines the
cell header content.
•
ATMAdaptation Layer (AAL) - This layer adapts the higher-level data into
formats compatible with the ATM Layer requirements. It is dependent on the
type of service(s) being transported by the higher layer.
When the end user sends traffic over the ATM network, the higher-level data unit is
passed down to the AAL Layer, which prepares the data for the ATM Layer as
appropriate for the AAL protocol being used. This can include padding the data unit
to a fIxed length, adding headers andlor trailers for error checking and higher-level
routing, and segmentation (with or without additional information added to the
subunits).
The prepared data unit or segment is then passed down to the ATM Layer, which
affIXes a necessary 5-byte ATM header to the segment. This 53-byte ATM cell is
then passed down to the Physical Layer for transmission (HEC framing) or packaging
into a Physical Layer Convergence Protocol superframe (PLCP framing).
49-2
SEP '95
49 ATM
(8) AAL .Protocols
Four AAL protocols have been defined for use in ATM networks. These protocols
loosely correspond to specific data classes, but are not necessarily exclusive to that
data type:
•
AAL 1- Constant bit rate. connection -oriented, synchronous traffic (e.g.,
uncompressed voice)
•
AAL 2 - Variable bit rate, connection-oriented, synchronous traffic (e.g.,
compressed video)
•
AAL 3/4 - Variable bit rate, connection-oriented, asynchronous traffic (e.g.,
X.25 data) or connectionless packet data (e.g., LAN traffic) with additional
information on segmentation and cell order
•
AAL 5 - Variable bit rate, connection-oriented, asynchronous traffic (e.g.,
X.25 data) or connectionless packet data (e.g., LAN traffic) with a simplified
information scheme for resegmentation
Examples of data flow for the commonly used AAL 3/4 and AAL 5 protocols are
given on the next few pages.
SEP'95
49-3
INTERVIEW 8000 Series Basic Oeeration: 951-80424-01
49.3 AAL 1 Protocol
47 bytes
47 bytes
47 bytes
Segment 2
Segment 1
L.
Segment 3
J
(Not Shown)
SM Header
(1 byte)
/
"-
/
rJ~d ~
{i~, Ij';$J
ATM Header
(5 bytes)
...
"-
ATM Payload
ow
..
53-byte ATM Cell
Figure 49-1 AAL 1 protocol: flow of a 141-byte SDU from the end user to the ATM layer.
The AAL 1 example shown in Figure 49-1 follows the flow of a 141-byte message (Service
Data Unit) from the end user to the ATM Layer. The SDU is passed unchanged through
the Convergence Sublayer to the Segmentation and Reassembly Sublayer (SAR). The
steps to accomplish this are documented in the following pages in Figure 49-2 through
Figure 49-4.
49-4
SEP'95
49 ArM
47 bytes
47 bytes
Segment 1
47 bytes
Segment 2
L
..
Segment 3
.J
(Not Shown)
Figure 49-2 AAL 1 protocol: the SAR sublayer divides the entire PDU into 47 -byte segments from the beginning and adds a i-byte
header to each segment.
The AAL 1 example follows the. flow of a 141-byte message (Service Data Unit) from the
end user tothe ATM Layer. The SDU is passed l.lftchanged through the Convergence
Sublayer to the Segmentation and Reassembly Sublayer (SAR).
Figure 49-2 shows that the SAR subblyer divides the entire PDU into 47 -byte segments
from the beginning and adds a i-byte header to each segment. This header adds
information concerning the sequencing of the segments and providing an error-check
mechanism.
The 1-byte SAR header consists of the following, as shown in Figure 49-3:
SEP '95
•
SN - Sequence Number, a 4-bit field which indicates the sequence number
information for this segment.
•
SNP - Sequence Number Protection,a 4-bit field which providesilie
error-checking mechanism for the SAR header.
49-5
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
/
/
/
/
"-
"-
"- '\.
/
/~
SN
SNP
(4 bits)
(4 bits)
"-
"
""
/
/
/
'\.
/
'\.
"
/
/
CSI
(1 bit)
I
SC
CRC
(3 bits)
(3 bits)
I
""I
EPC
(1 bit)
I
Figure 49-3 AAL 1 protocol: the 1- byte SAR header consists of two 4 -bit fields: SN and SNP. Eacb of these fields is in turn subdivided
into a 3-bit and a 1-bit field.
The Sequence Number portion of the header is further subdivided into two subfields, as
shown in Figure 49-3:
•
CSI- Convergence Sublayer Indications, a I-bit subfield which is used to convey
CS-specific information. This is not utilized for all AAL 1 implementations.
•
SC - Sequence Count, a 3-bit sequence number for the entire CS-PDU. This is
generated by the CS and remains constant for all segments created from that
CS-PDU.
The Sequence Number Protection portion of the header is also subdivided into two
subfields, as shown in Figure 49-3:
•
CRC - Cyclical Redundancy Check, a 3 - bit sequence that functions as an error
check for the SN field only.
•
49-6
EPC - Even Parity Check, a 1-bit check of the previous 7 bits of the header, ie., the
SN field and the eRC subfield.
SEP'95
49 ArM
SAR-SOU
SAR-SOU
..
ATM Header
(5 bytes)
ATMPayload
-
.JII
53-byte ATM Cell
Figure4'"" AAL 1 protocol: as-byte ATM header is added to the SAR-PDU segment (which becomes the transparent 48-byte
payload for the ATM cell) to create the ATM cell.
This SAR...., PDU (segment) becomes the transparent 48-byte payload for the ATM cell.
As shown mFigure 494, a 5 - byte ATM header is then added. to the segment to create the
AN cell.. l1ris header contains the information necessary to transport the cell to its
destinatio~ identify the payload type, assign the cell a loss priority, and provide an
error-checking mechanism.
The ATM header consists of the following fields:
•
GFC -; Generic Flow Control,of local significance only and used to provide
standardized local functions onthe end user premises.
•
VPI-Virtual Path Identifier, which with the VCI provides the routing from node to
node throughout the network from end user to destination.
•
VCI-Virtual Channel Identifier (see above).
•
PT - Payload '!Ype. used to indicate if the cell contains user information or flow
control information. This 3-bit field may also be used to indicate network congestion
or network resource .management information.
SEP'95
•
CLP ....;.. Cell Loss Priority, to optionally indicate cells that may be discarded when
congestion occurs.
•
HEC T Header Error Control, used to detect bit errors in theATM Header only_
49-7
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
49.4 AAL 3/4 Protocol
121 bytes
CPCS-SDU (Message)
Segment 1 (BOM)
44 bytes
44 bytes
44 bytes
Segment 2 (COM)
L
Segment 3 (EOM)
ow
(Not Shown)
48 bytes
48 bytes
...
-
...
53-byte ATM Cell
Figure 49-5 AAL3/4 protocol: transformation of a I2l-byte CPCS-SDU message from the end user into a 53-byte ATM cell.
The AAL 3/4 example shown in Figure 49-5 follows the flow of a I2l-byte message
(Service Data Unit) from the end user to the ATM Layer. The steps to accomplish this
are documented in the following pages in Figure 49--6 through Figure 49-9.
49-8
SEP'95
49 ArM
-
121 bytes
cpcs-sou (Message)
CPCS Trailer
(4 bytes)
/
/
/
/
/
AL
(1byte)
Length
(2 bytes}
Figure 49-6 AAL3I4 protocol: Tile SDU is passed to the Convergence Sublayer. where a 4-bytc header and a 4-byte trailer are added to
the front and end of the SDU.
The SDU is passed to the Convergence Sublayer, where a 4-byte header and a 4-byte
trailer are added to the front and end of the SDU (see Figure 49.6). In addition, the data
segment is padded with 0 to 3 bytes of data at the end. as necessary. to make the entire
Protocol Data Unit (PDU) size a multiple of 4 bytes.. (In our example, the pad is 3 bytes.)
The Common Part Convergence Sublayer (CPCS)· header consists oithe following:
•
CPI -: Common Pan Illdicator. used to interpret the remainder of the fields in the
header and the trailer added for this sublayer.
•
Btag - Beginning lag, an "error check" for this segment. The value in this field is
also placed in the Etag field of the trailer, allowing a quick. comparison after receipt to
determine if the PDU has been corrupted.
•
BASize - Buffer Allocation Size, encoded to indicate the CPCS- PDU payload
length.
The CPCS,trailer consists of the following:
•
AL - Alignment, used to make the trailer size 4 bytes and passed transparently
through the network.
•
Etag - End Tag (see Btag)
•
LengtA -- Used to indicate the length of the PDU payload. This field is encoded to
indicate the number of counting units in the length of the payload, with the counting
unit site indicated in the CPI of the header.
SEP '95
49-9
INTERVIEW 8000 Series Basic Operation: 951-80424-01
Segment 1 (80M)
Segment 2 (COM)
L
Segment 3 (EOM)
y
(Not Shown)
Figure 49-7 AAL3/4 protocol: The entire CPCS-PDU is then passed to the Segmentation and Reassembly (SAR) sublayer for further
processing.
Figure 49-7 shows that the entire CPCS-PDU is then passed to the Segmentation and
Reassembly (SAR) sublayer for further processing. This sublayer divides the entire PDU
into 44-byte segments from the beginning and adds a 2-byte header and a 2-byte trailer
to each segment. These headers and trailers add information concerning the segment
order and provide a cyclical redundancy check (eRC) for the segment.
49-10
SEP'95
49 ArM
MID
(10 bits)
Figure 49-8 A.AL3!4 protocol: SAR header.
The SAR header consists of the following:
•
ST - Segment Type, oneoi the four possibJe segment types; Beginning of Message
(BOM), Continuation of Message (COM), End of Message (BOM), or Single
SegmeJitt Message (SSM).
NOTE: In the example above, the BOM is a full 44 bytes in length. This will
not necessarily be true of all PDUs, as the only requirement is that of
maintaining a PDU length divisible by 4 bytes. Therefore, this segment will
contain whatever portion remains after all of the previous 44-byte segments
have been created by the segmentation process padded with zeroes as
necessary.
•
SN - Sequence Number, allowing the stream of SAR Sexvice Data Units (SDUs) to
be nUIllbered using modulo 16 in order to provide a "loss of segment" check for each
full PDU that is segmented.
•
MID -" Multiplexing Identification, used to multiplex CPCS connections on a single
ATM Layer connection, when applicable
The SAR trailer consists of two parts:
•
U - Length Indipation, binary encoded to indicate the number of bytes of the
CPCS-PDU are contained in the payload portion of the segment. For the BOM and
COM segments this value must be 44. For BOM segments, the value can range from 4
to 44 as appropriate. For SSM segments, permissible values range from 8 to 44.
•
CRC -.- Cyclical Redundancy Check, a lO-bit sequence that functions as an error
check for the entire SAR - SDU, including the header, payload, and the LI field of the
trailer.
<
This SAR ..... POU is then handed down to the ATMLayer for further processing.
SEP'95
49-11
INTERVIEW 8000 Series Basic Operation: 951-B0424-01
SARHeader
(2 bytes)
ATM Header
(5 bytes)
SAR-SDU Payload
SAR Trailer
(2 bytes)
SAR Header
(2 bytes)
SAR-SDU Payload
ATM Payload
SARTrailer
(2 bytes)
48 bytes
..
ATMHeader
(5 bytes)
ATM Payload
53-byte ATM Cell
Figure 49·9 AAL3/4 protocol: The SAR-PDU (segment) becomes the transparent 48-byte payload for the ATM cell.
This SAR - PDU (segment) becomes the transparent 48-byte payload for the ATM cell
(see Figure 49-9). A 5-byte ATM header is then added to the segment to create the ATM
cell. This header contains the information necessary to transport the cell to its
destination, identify the payload type, assign the cell a loss priority, and provide an
error-checking mechanism.
The ATM header consists of the following fields:
49-12
•
GFC - Generic Flow Control, of local significance only and used to provide
standardized local functions on the end user premises.
•
VPI - Virtual Path Identifier, which with the va provides the routing from node to
node throughout the network from end user to destination. See Table 49-1 for
pre-defined header field values.
•
VCI - Virtual Channel Identifier (see VPI, above).
•
PT - Payload Type, used to indicate if the cell contains user information or flow
control information. This 3-bit field may also be used to indicate network congestion
or network resource management information. See Table 49-1 for pre-defined
header field values and Table 49-2 for PT encoding.
•
CLP - Cell Loss Priority, to optionally indicate cells that may be discarded when
congestion occurs. See Thble 49-1 for pre-defined header field values.
•
HEC -
Header Error Control, used to detect bit errors in the ATM Header only.
SEP '95
49 ATM
Table 49-1
Pre-defined Header Field Values t
Value 1.2,3.4
Use
Unassigned cell indication
Meta-signalling (default) 5.7
Meta-signamng6.7
Octet 1
Octet 2
Octet 3
Octet 4
00000000
OOOOOOOO
0000yyyy
OOOOOOOO
OOOOOOOO
0000xxx0
OOOOOOOO
yyyyOOOO
00000000
yyyyOOOO
OOOOOOOO
yyyyOOOO
00000000
00000000
OOOOOOOO
00010a0c
0001080c
aaaaOOOO
General Broadcast signalliryg (default) 5
00000000
General Broadcast signalling 6
ooooyyyy
Point-to- point signaling. {default} Ii
Point -to- point signaHing $
OOOOOOOO
0000yyyy
Invalid Pattern
XXXXOOOO
Segment OAM F4 flow
ceU·7
End-to-End OAM F4 flow cell
7
OOOOaaaa
0000aaaa
aaaaOOOO
OOOOOOOO
oolooaac
oooooooo
00100aac
OOOOOOOO
0101Qaac
OOOOOOOO
OOOOOOOO
0101Qaac
00000000
OOOOOOOO
00110808
OOOOXXX1
01000aOa
1 a indicates that tbebit is~aitabfetor . . by the appropriate ATM layer function.
2 x indicates "don't tare" bitS.
3 Y indicalS any VPl value otfter1han 00000000.
4 C indicates that the originafing signalling entity shall set the CLP bit to O. The network may change the value of the
CLP bit.
.
5 Reserved for user signalling with the local exchange.
6 Reserved for signalling with other signalling entities (e.g., other users or remote networks).
7 The transmitting ATM entity shall set bit 2 of octet 4 to zero. The receiving ATM entity shall ignore bit 2 of octet 4.
Table 49-2
Payload Type b1dicator Encoding t
PTI Coding
(MSBfirst)
001 *
010
*
== 0
User data cell, congestion not experienced, SOU-type == 1
User data cell, congestion not experienced, SDU-type
000
011
Interpretation
*
User data cell, congestion experienced. SOU-type == 0
User data cell, congestion experienced, SDU-type == 1
100
101
Segment OAM F5 flow related cell
110
Reserved tor future traffic control and resource management
111
Reserved for future functions
End-to-end CAM F51tow related cell
This coding indicates this is the end of a SAR - PDU segment for AAL 5
t Table information from ATM Forum UNl Specification, Subsections 3.4.4 and 3.4.5, respectively
SEP'95
49-13
INTERVIEW 8000 Series Basic Operation: 951-80424-01
49.5 AAL 5 Protocol
92 bytes
OPes-sou (Message)
•
(Not Shown)
53-byte ATM Can
Figure 49-10 AAL 5 protocol
The AAL 5 example follows the flow of a 92-byte message (Service Data Unit) from the
end user to the ATM Layer. The procedure is further broken down and explained in
Figure 49-11 and Figure 49-12.
49-14
SEP'95
49 ATM
92 bytes
cPcs-sou (Message)
------
cpcs-
CPt
UU
(1 byte) (1 byte)
Length
(2 bytes)
,
CRC-32 (4 bytes)
Figure 49<-11 AAL 5 protocol; the SDU is passed to the Convergence Sublayer, where an S-byte trailer is added to the end of the SDU.
Figure 49-11 illustrates the SDU is passed to the Convergence Sublayer, where an 8-byte
trailer is added to the end of the SDU. In addition, the data segment is padded with 0-47
bytes of data at the end, as necessary, to place the trailer at the end of the last 48-byte
segment. (In our example, the pad is 44 bytes.)
The CPCS trailer consists of the following:
•
CPCS- UU - CPCS User- to - User indication, used to transparently transfer CPCS
information from the origination user to the destination user.
•
CPI- Common Part Indicator, used to align the CPCS-PDU trailer to the 32-bit
boundary.
•
Length - Used to indicate the length of the CPCS payload (not including the PAD
bytes).
•
CAe - Cyclical Redundancy Check, a 32-bit error check for the entire contents of
the CPCS - PDU, including the payload, the PAD field, and the first 4 bytes of the
trailer.
This entire CPCS-PDU is then handed to the SAR sublayer for segmentation.
SEP'95
49-15
INTERVIEW 8000 Series Basic Operation: 951-80424-01
..
(Not Shown)
53-byte ATM Cell
Figure 49-12 AAL 5 protocol: the ATM header is the same as that discussed for AAL 3/4 with one exception-the PT code can identify
the end cell of a SAR-PDU segment. (See Table 49-2.)
The SAR sublayer segmentation for AAL 5 consists solely of dividing the CPCS - PDU
into 48-byte segments. These segments are then handed down to the ATM Layer, where
the ATM Header is added to create the 53-byte ATM cells.
NOTE: Refer to the AAL 3/4 explanation for details of the AAL 5 header
format. The ATM Header structure is the same for all AAL types, with one
exception for the AAL 5 format: two of the Payload Type codes identify the
end cell of a SAR - PDU segment. The footnote of Table 49-2 for the Payload
Type encoding describes the end cell PT codes as:
001 User data cell, congestion not experienced, SOU-type = 1
011 User data cell. congestion experienced, SOU-type = 1
49-16
SEP '95
49 ATM
49.6 Operations and Maintenance (OAM) Cells
OAM
Cell Type
(4 bits)
Functlon
Type
(4 bits)
"
""
Function-Specific Fields (45 bytes)
----------
,
'\
VCI (2 bytes)
CRC-10*
(2 bytes)
OAM Cell Payload
--
/
'"Consists of the 10-bit
CRC and 6 bits of PAD.
Figure 49-13 Operations and Maintenance (OAM) cells.
The INTERVIEW 8000 TURBO Series also supports one additional format in ATM over
T1IE1. The Operations and Maintenance (OAM) cells are used to provide various
maintenance functions within the ATM network, including connectivity verification and
alarm surveillance. These cells consist of a single segment with the following 48- byte
format:
•
OAM Cell Type - A 4-bit indicator of the type of OAM cell (e.g., 0001 to indicate
Fault Management).
•
Function Type - A 4-bit indicator of the purpose for this particular OAM cell (i.e.,
Alarm Indication Signal, Far End Receive Failure, Loopback).
•
Function-Specific Fields - Functions and information for this cell (up to 45 bytes),
used to denote destination and failure information.
•
CRC - Cyclical Redundancy Check, a lO-bit error check for the OAM payload,
including the type indicators and the function-specific fields.
This 48-byte OAM cell is passed to the ATM Layer, which adds the A1M Header to
create the 53-byte ATM cell.
49-17
SEP'95
_........ _---_._......... _....
_._----------_.----,---------
INTERVIEW 8000 Series Basic Operation: 951-80424-01
49.7 ATM Framing: HEC and PLCP
Two types of framing for ATM are supported by the INTERVIEW 8000 TURBO Series:
BEC (Header Error Control) framing and PLCP (Physical Layer Convergence Protocol)
framing.
For HEC framing, the ATM cells (regardless of AAL format) are streamed across the physica1
medium of the ATM network as processed by the ATM Layer and the Header Error Control
values are used to achieve synchronization. With this format, alignment is achieved when the
appropriate number of successive cells with good HEC values are detected (six is
recommended). Cell Delineation Loss or loss of synchronization occurs when an appropriate
number of successive HEC errors are detected (seven is recommended).
Figure 49-14 illustrates PLCp, the alternate framing mode. PLCP framing bundles 10
ATM cells into a superframe that adds 4 bytes of information to the beginning of each cell.
The first two bytes of this information (Al and A2.) act as a 2-byte synchronization
sequence. The next byte (P9 to PO) is the path overhead indicator for each ATM cell in
the superframe. The fourth byte (24-21, F1, 61, G1. M2-M1, and C1) is the path
overhead for the superframe. These consist of Growth octets (Z4 - Zl), Bit-Interleaved
Parity (Bl), PLCP Path Status (Gl), Cycle/Stuff Counter (Cl), and three fields (Fl, M1,
and M2) that are irrelevant to the ATM network.
ATMHeader
A1
A1
A1
A1
A1
A2
A1
A1
A1
A1
A2
A2
P9
P8
P7
P6
P5
P4
P3
P2
P1
A1
A2
PO
M1
C1
POI
POH
A2
A2
A2
A2
A2
A2
PLCP
Framing
(2 bytes)
Z4
Z3
Z2
Z1
F1
61
Gl
Trailer*
PlCP Payload
(1 byte) (1 byte)
*T1 only
(6 bytes)
Figure 49-14 PLCP frame format.
In addition, a 6-byte trailer is added when Tl is utilized. This trailer consists of the same
character (Cc) repeated six times and is used to increase the superframe to the required
576-byte size for Tl. It serves no other purpose.
49-18
SEP'95
Index A: Part I
Index A:
Technical Manual Part I
Symbols
II abort, overlay for BOP abort, 6-13
II badbcc, overlay for bad BCC or FCS, 6-13
[HI bit mask symbol, in Receive string condition,
25-7
)) close double parens symbol, 3-5, 26-4,29-5
"/ closing delimiter for comment, 28-14
18) don't care symbol
in Receive string condition, 25-7
in spreadsheet string search, 37 - 35
IE! flag, 7E flag symbol, 6-14
fill goodbcc, overlay for good BCC or FCS, 6-13
I
highlighted plus symbol, indicates wrap in logical
line, 30-3
[5 not equal flag symbol
in Receive string condition, 25-7
in spreadsheet string search, for beginning of
frame, 37 - 35
(( open double parens symbol. 3-5, 26-4, 29-5
/* opening delimiter for comment, 28-14
~
pad, in Outsync Char field, 5 -13
? key, Easy View, 4-7
I (root) directory, 15-4
1I1 sync, sync symbol, 5-8, 6-14
- tilde symbol, 3-5, 28-3
.:-~
time-fIll, 6-8
A
AAL
inATM,49-2
protocols in ATM, 49- 3
AAL 1, protocol in ATM, 49-3, 49-4-49-8
AAL 2, protocol in ATM, 49- 3
AAL 3/4, protocol in ATM, 49-3,49-8-49-12
SEP '95
AAL 5, protocol in ATM, 49-3, 49-14-49-16
Abort
adjunct to monitor-frame condition
LAPD, 43-14, 43-15
SDLC, 39-15, 39-17
X.25 Layer 2, 37 -14, 37 -15
adjunct to send-frame action
LAPD,43-2S
SDLC,39-28
X.25 Layer 2, 37-28
adjunct to send-string action, Layer 1 (BOP),
single-port, 32-11
appended to transmit string, 10-6
defined for BOp, 10-6,37 -11,38-14,43-9,
44-8,46-7,47-7
field on BCC Setup menu, 10-13
monitor/receive condition, Layer 1 (BOP only),
32-4
overlay, BOP only, 10-4
Absolute pathnames, files and directories, 15-5
Accumulate, layer-independent action, 31-15
Accumulate action, 21-7
may apply to current, last, minimum, or maximum values, 21-9
not found on trigger menus, 21-8
used to log one hour per day over days or weeks,
21-10
Accumulate counter. layer-independent action,
31-15
Accumulate timer, layer-independent action,
31-15
Accumulator
created by being named in Accumulate action,
31-15
may be given display line on stat screen(s),
31-15
printing line of tabular statistics for, 31 -16
Actions
capture memory on/off, 7-11
Enhance, control of color display, 18-5
Layer 1
accessed via Done key, 32-8
dual-port, 32-17
dual-port, 32-17
IndexA-1
Index A: Part I
single -port, 32 - 8
layer-independent, 31-8-31-13
Protocol Spreadsheet, programming block, 28-9
comments in, 28-15
record on/off, 7-11
ADDR
address, trace column
SDLC,39-8
X.25 Layer 2, 37-7
field on SDLC Frame Level Setup screen, 39-3,
39-5,40-3
Address
adjunct to monitor/receive-frame condition
SDLC, 39-14
X.25 Layer 2, 37-14
adjunct to send-frame action
SDLC, 39-24
X.25 Layer 2, 37 - 25
trace field, SNA -SDLC, 40-7
OAM cells, 49-17
overview, 49-1
packet-switching features, 49-1
Physical Layer, 49-2
PLCP framing, 49-1, 49-18
recording selections, TIlE1 data, 49-1
SARheader
AAL 1,49-5
AAL 3/4, 49-11
SAR trailer, AAL 3/4,49-11
transmission
data, 49-2
video, 49-2
voice, 49-2
ATM Adaptation Layer (AAL), in ATM, 49-2
ATMheader
AAL 3/4, 49-12
AAL5,49-16
in ATM, AAL 1, 49-7
Affects, field on BCC Setup menu, 10-13
ATM Layer, in ATM, 49-2
Again, editor command, 30-9
Auto Configure, screen in automonitor mode, 6-3
AIM Interface Setup, overview of screen, 2-12
Auto-indent, editor command, 30-9
Alarm
field on nigger Setup menu, 26-11
layer-independent action, 31-13
Automatic OSI primitives. See Primitives
Allocating disk space, 14-3
ANSI format, SS#71ayer 3, 47-4
Append, run-mode printer output to existing disk
file, 16-6
ASCII, default BCC parameters, 10-9
ASCII keys, in programming menus and spreadsheet, 3-4
Async
data setup, 5 -15
sample Line Setup, 5 -18
ATM,49-1
AAL protocols, 49-3
ATM Adaptation Layer (AAL), 49-2
ATM header, AAL 1,49-7
ATM Layer, 49-2
cell relay, 49-1
CPCS header, AAL 3/4, 49-9
CPCS trailer
AAL 3/4, 49-9
AAL5,49-15
framing
HEC,49-2
PLCp,49-2
HEC framing, 49-1, 49-18
IndexA-2
Automatic X. 25 Layer 2,37-36
Automonitor mode
setting up, 5- 3
stage in autoconfiguration displayed in Status
field,6-3
updates Line Setup screen, 6-4
with no clock, speed defaults to 168 kbps, 6-4
Autosync, subfield on Line Setup menu, 5-8,
5-12,5-13
AUX 1/0, connector, 1-11
AUX leads, 1-11
AUX outputs, on/off, Layer 1 emulate-mode action,32-12
Auxiliary TTL connector, 1-11
Average, column on Tabular Statistics screen,
21-6,21-11,31-10
B
Back panel, 1-8
fan, 1-10
fan filter, clean to prevent overheating, 1-10
frequency selection, 1-9
Input/Output connectors, 1-10
AUXILIARY TTL, 1-11
SEP '95
Index A: Part I
CRT/RGB,1-11
ISDN handset, 1-10
PRINTER, 1-10
REMOTE RS-232, 1-10
RS-170 composite video, 1-11
on/off (power) switch, 1-10
power connector, 1-8
voltage selection, 1-8
Backslash, entry of inside prompt message, 31-12
Bad, Summary subfields on Disk Maintenance
menu, 14-8
BadBCC
adjunct to monitor-frame condition
I.APD, 43-14, 43-15
SDLC, 39-15, 39-17
X.25 Layer 2, 37 -14, 37-15
adjunct to send-frame action
I.APD,43-25
SDLC,39-27
X.25 Layer 2, 37 - 28
adjunct to send-string action, Layer 1, singleport, 32-11
appended to transmit string, 10-5
as condition, 10-5
monitor/receive condition, Layer 1,32-4
operational only when Rev Blk Chk enabled,
32-4
overlay, 10-3
Baudot, no default BCC parameters, 10-10
BCC
See also Block checking
cross between a Layer 1 and Layer 2 function,
32-4
Layer 1 condition, 32-4
operational only when Rev Blk Chk enabled,
32-4
subfield on Trigger Setup menu, 10-5,26-4
trace column
I.APD,43-9
0.931,44-8
SDLC,39-11
SNA -SDLC, 40-6
SS#7 Layer 2, 46-6, 47-7
X.25 Layer 2, 37 -11
X.25 Layer 3, 38-14
BCC Setup, overview of screen, 2-12
BCC Setup screen, SMDS Fume Mode, 10-4
Begin, editor command, 30-5
SEP '95
BERT
"force-Ioopback" programming example,
11-21-11-22
analyze-only mode, 11-18
automatic error injection, 11-14
enabling/disabling by softkey, 11-18
status message, 11-21
block size, 11-13
clearing counters, 11-6
clearing the results screen, 11-18
counters, 11-19
five pseudorandom patterns, 11-3
algorithms, 11-3
freeze mode, 11-17
half duplex, 11-6
"receive and analyze" versus "generate" mode,
11-6
initiating the send -receive cycle, 11-7
manual error injection, 11-18
operating mode, selected on line Setup menu,
11-5
patterns, 11-7
reinitializing a running test, 11-18
relation of BERT Setup menu to Interface Control screen, 11-7
relation of BERT Setup menu to Line Setup
menu, 11-6, 11-14
results, 11-19
statistics display, 11-19
synchronous versus asynchronous, 11-15
test length, 11-14
BERT modes, setting up, 5-4
BERT Setup, overview of screen, 2 -12
Binary display, of cursor characters, 6-15
in relation to order of transmission, 6-15
Bisync
CRC mode, 10-14
advantage over selectable mode, 10-14
field on BCC Setup menu, 10-12
sample Line Setup, 5-18
Bit mask
in Protocol Spreadsheet strings, 33 - 3
in Receive string condition, 25-7
in Suppress field, 6-11
to detect XON and XOFF only, 6-12
Bit Mask key, 3-6
Bit order
in relation to hexadecimal notation, 6-14
in relation to pattern sync in BERT, 11-11
normal versus reverse, 5-16
Bit Order/Polarity, field on Line Setup menu,
5-16,11-15
significance in BERT testing, 11-16
IndexA-3
Index A: Part I
Bit-image data, 7-3
playback, 7-4
Bits
field on Line Setup menu, 5 -7, 11-15
in BERT testing, 11-15
number of, in setup, 5-7
Bits In Error, BERT counter, 11- 20
Blnk, subfield on Trigger Setup menu, 26-7
Block
component of BERT test, 11-13
editor command, 30-5
Block checking
automatically on for BOp, 10-4
distinction between transmitting and evaluating
BCC, 10-3
enabling BCC overlays, 5 -13, 10-3
forDDCMP
automatically on, 41-1
data BCC may be tested as event variable in C,
41-2
header BCC only may be tested by trigger,
41-2
looking under BCC overlay, 10-4
parameters defined on BCC Setup menu, 10-6
result used as trigger condition, 10-5
Block Size, field on BERT Setup menu, 11-13
Blocks In Error, BERT counter, 11- 20
Blocks Received, BERT counter, 11-20
Blocks Sent, BERT counter, 11-20
Boot-up
creating a user interface, HRD/usr/user_intrf,
2-4
enable Easy View, /sys/ezview_setup, 2 - 3
entry into Easy View, 4- 3
from the keyboard, 2-2, 4-3
loading Printer Setup, /sys/print_setup, 2 - 3,
16-7
running default program, lusr/default, 2-6
c
C, color, field on Graphical Statistics menu, 22-7
C language, third tier in programming hierarchy,
23-4
C/R
adjunct to monitor/receive-frame condition,
LAPD,43-13
adjunct to send-frame action, LAPD, 43-22
Command/Response, trace column, LAPD, 43-8
CAL - REF - VAL, call reference value, trace column, Q.931, 44-5
CALL, send action, X.25 Layer 3,38-31
Call Confirm
send-packet action, X.25 Layer 3, sending
"short" version without addresses and facilities, 38-33
sent down (as primitive) to Layer 2, 34-9
Call reference value
adjunct to monitor/receive-message condition,
Q.931,44-10
monitor/receive condition, 0.931,44-10
trace column, Q.931, 44-5
Call Request
as character data, 38-9
as entry on X.25 Packet Level Setup screen,
38-6
as packet on trace display, 38-8
send-packet action, X.25 Layer 3, 38-32
sent up (as primitive) from Layer 2,34-9
Call Request user data, may be longer than ten
character spaces, 38-7
CALL_CONF, send action, X.25 Layer 3,38-31
CALLED, field on X.25 Packet Level Setup
screen, 38-6
Called address, entered in CALLED field on X.25
Packet Level Setup screen, 38-6
CALUNG, field on X.25 Packet Level Setup
screen, 38-6
BOp, synchronization and BCC parameters always
defined for, 5-14, 10-4, 10-8
Calling address, entered in CALUNG field on
X.25 Packet Level Setup screen, 38-6
Break key, 30-5
in Easy View, 4-16
Capture, field on Trigger Setup menu, 26-11
Buffer Control Leads, field on Front- End Buffer
Setup screen, 9-5
Buffer Full
condition, Trigger Setup menus, 25 -11
layer-independent condition, 31-5
IndexA-4
Capture data to screen (on/off), Layer 1 action,
single-port, 32-16
Capture Memory, field on Record Setup menu,
7-4,7-6,7-10,14-10
Capture memory
See also Data capture; Recording data
SEP'95
Index A: Part I
Freeze key, 3-11
Carriage Return, produced by operation of CTRL
and M keys, 33-1
Cause byte
adjunct to Restart, Reset, Clear, and Reg Confirm actions, 38-36
adjunct to Restart, Reset, Clear, and Reg Confirm conditions, 38-20
listed for Reset, Clear, and Reg Confirm packets,
38-22
listed for Restart packet, 38-21
listed for Send Clear actions, 38-37
CCIrr
format, SS#71ayer 3,47-4
Open Systems Interconnection model,
24-4-24-8
See also Layers
CCSS#7. See SS#7
CD
available for triggering, 32-5
field on RS-232 Interface Control menu, 11-4,
11-6
CD on/off, Layer 1 Emulate DCE action, 32 -12
Cell relay, for ATM,49-1
Chaining, of programs via Load Program action,
31-19
Change Directory, File Maintenance, menu selection,15-18
Change idle character, Layer 1 action, single-port,
32-13
Char, subfield on Line Setup menu, 5-13
Character buffer, 7-4
capacity, 6-27
data, 7-3
playback, 7-4
recording, 7 -11
storage capacity, 1-16
Character data
buffer correlation with trace data, 6- 27
display of
accessed by DATA softkey, 6-7
dual line, 6-8
single line, 6-8
Character field, defined, 38 .... 7
Circuit Identifier Code (ClC), SS#7 Layer 3,
47-6,47-10
Clear, editor command, 30-5
SEP'95
Clear key, 30-4
in Easy View, 4-16
in menu fields, 3-7
in spreadsheet, 3-7
Qear path, emulate-mode action, X.25 Layer 3,
38-41
Clear statistical accumulator values, 31-15
Clear statistical counter values, layer-independent
action, 31-10
Clear statistical timer values, layer-independent
action, 31-11
Clock
field on Line Setup menu, 11-16
in BERT testing, 11-16
signal, 1-17
See also Speed
time-of-day, 1-17
See also Date!I'ime Setup
Clock Source, field on Line Setup menu, 5-15
Code
field on Line Setup menu, 5-6, 10-9, 11-14,
11-15
significance in BERT testing, 11-14
standard codes, 5-6
Color display
color graphics, 18-6
connectors for external monitors, 18-3
miscellaneous utilities, 18-3-18-6
selectable options, 18-4-18-5
background color, 18-5
blink,18-5
character, 18-5
trigger control of, 18-5-18-6
Command
field on File Maintenance menu, 3-6
in Easy View script file, 20-25
Command addressing, adjunct to send - frame action, X.25 Layer 2, 37-24
Comment, 28-14
debugging tool, 28-15
delimiters, 28-14
length of, 28-14
location on spreadsheet, 28-14-28-15
purpose of, 28-15
valid characters, 28-14
Common Channel Signalling System #7. See $$#7
Compilation
automatic during LPRGRM save, 15-16
automatic during object -code save, 15 -16
error diagnostics, 2-18
IndexA-5
Index A: Part I
fields that can be modified without causing recompile, 2-17
rerun without recompiling, 2 -16
seven phases, 2 -16
Compile, File Maintenance
compiles contents of f.tle or spreadsheet, 15 - 22
compiling spreadsheet generates #pragma
hooks, 15-23
menu selection, 15-22
Conditions
EIA, fails to come true, 2 - 22
Layer 1
dual-port, 32-6
single-port, 32-1
layer-independent, 31-3-31-7
counters in linkable-object files, 28-12
PTotocolSpreadsheet
naming requirements, 31-1
programming block, 28-8
comments in, 28-15
rules for combining conditions, 31-2
transitional vs. status, 31-2, 31-6
Confirm primitives, 34-5
CONNECT IND primitive, example on spreadsheet, 34-7
CONNECT REO primitive, example on spreadsheet, 34-8
Connectors
back panel, 1-8
power, back panel, 1-8
RGB,18-3
RS-170video, 18-3
RS-232 printer connector, 16-3
Test Interface Module, 1-12-1- 20
Constants, 29-3-29-7
expansion of, 29-7
fox message, 33-4
in Receive string condition, 25 - 8
in spreadsheet string, 33-3
legal names of, 29-4
nesting of, 29-6
Protocol Spreadsheet, 24-8
programming block, 28-8
comments in, 28-14
referencing, 29-5
scope of,29-4
transmitting, 33-4
Control characters
data-entry of, 33-1
enhancement of via bit mask, 6-13
IndexA-6
Control leads
See also EIA leads
playback, 2 - 20
of bit-image data, 2-20, 9-5
of character data, 2-20, 9-5
Copy
editor command, 30-6
File Maintenance, menu selections, 15 -18
Counter
accumulated, 31-15
condition
Protocol Spreadsheet, 21-4, 31-5
when used in linkable-object files, 28-12
Trigger Setup menus, 21-4, 25-11
identified by name on statistics screen, 21-4
layer-independent action, 31-8
maximum value vs. maximum stat display, 31-6
may be identified on statistics screen following
run,21-6
printing line of tabular statistics for, 31-16
relational operators, 31-5
shared between spreadsheet and Trigger Setup
menus, 31-5,31-9
transmitted, 33-4
CPCS header, in ATM, AAL 3/4,49-9
CPCS trailer, in ATM
AAL 3/4, 49-9
AAL 5, 49-15
CR control character, 3-6
CRC Mode, field on BCC Setup menu, 10-9,
10-12, 10-14, 10-16
CRT/RGB connector, 1-11
CTS
available for triggering, 32-5
field on RS-232 Interface Control menu, 11-4,
11-6
CTS on/off, Layer 1 Emulate DCE action, 32-12
Current, column on Tabular Statistics screen,
31-10,31-11
Current Date, field on Dateffime Setup menu,
17-3
Current directory
File Maintenance screen, 15 -11
filing system, 15-4
Current Time, field on Dateffime Setup menu,
17-3
Cursor keys
in Easy View, 4-7, 4-16
in spreadsheet, 3-9
SEP '95
Index A: Part I
may be programmed in the Display Window,
3-12,6-23
on menu screens, 3-8
used to control playback speed, 3-12
Cursor timing
in data-plus-leads displays, 6-16
Mark key, 6-16
o
D, trace column, X.25 Layer 3, 38-13
Dbit
adjunct to monitor/receive-packet condition,
38-18
adjunct to send-packet action, 38-36
position diagrammed, 38-13
value selectable for Call and Call Confirm pack·
ets as well as Data, 38-19
DAT, source of playback data from disk, 5 - 5
DAT Record Size, field on Record Setup menu,
7-7
DATA, field on X.25 Packet Level Setup screen,
38-7
Data
See also Character data
ATM transmission, 49-2
bit-image data, 7-3
buffered automatically in FEB, 9- 3
character-oriented, 7 - 3
Data acquisition tracks, 14-3
Data capture, 2-20
See also Playback; Recording data
manual control of, 7 -12
RAM, data storage, 1-16
trigger control of, 7-11
Data compression, SS#7, Layer 1, 45-4
Data display, black and white enhancements, 18-6
display of, 6-9
control leads selected for, 6-9
softkey access, 6-9
failure of leads to transition, 2 - 23
DATA REQ primitive, example on spreadsheet,
34-9
Data source, connection to, 1-19
Data suppression, SS#7, Layer 1,45-5
Data to Record, field on Record Setup menu, 7-7
Data Transfer, Disk Maintenance, menu selection,
14-9
Data transfer
INTERVIEW 5, 10, 15 PLUS data,
14-12-14-18
prior to playback, 7-4
DateITime Setup, 17-3
menu selections, 17 - 2
set date, 17-3
set time, 17-3
Day of month, as trigger condition, 31-6
DCE, monitor condition
LAPD,43-9
Layer 1, 32-3
Q.931,44-9
SDLC,39-12
SS#7 Layer 2, 46-7, 47-7
X.25 Layer 2, 37-11
X.25 Layer 3,38-15
DCE2, monitor condition, Layer 1, 32-8
DDCMP, Layer 1 package, 41-1
Decimal field, defIned, 38-6
Decrement counter, layer- independent action,
31-10
Decrement flag byte, as 16-bit binary counter, layer-independent action, 31-14
Default menus, how to change, 2-6
Delete
editor command, 30-5
File Maintenance, menu selection, 15-22
DATA IND primitive, example on spreadsheet,
34-9
Delete Char key, 3-7, 30-4
in Easy View, 4-16
Data packet
monitor/receive condition, X.25 Layer 3, 38-15
send action, X.25 Layer 3, 38 - 31
Delete Line key, 3-7, 30-4
Data playback, control of, 7-10
Destination Point Code (DPC), SS#7 Layer 3,
47-10
Data plus leads
cursor timing, 6-16
display available during playback, 9-5
display enabled/disabled by FEB setup, 9-5
SEP '95
Descript, Summary subfields on Disk Maintenance
menu, 14-7
Diagnostic byte
adjunct to Restart, Reset, Clear, Diag, and Reg
Confirm conditions, 38-23
IndexA-7
Index A: Part I
adjunct to Restart, Reset, Clear, Diag, and Reg
Confirm send actions, 38-38
entered as two hex digits, 38-23
Directories
Isys, 15-6
lusr, 2-4, 15-6
lusr/default, 2-6
absolute pathnames, 15-5
directory listings, 15 - 11
filing system, how to create, 15 - 5
naming conventions, 15-7
relative pathnames, 15-6
root (I) directory, 15-4
write-protected,15-11
DISABLE, mode on Line Setup screen, 5-5
Disk drives, 1-6
current disk, filing system, 15-10
drive references and priority, 14-3
filing systems, moving from disk to disk, 15-5
microfloppies
compatibility, 1-6
write protection, 1-6
microfloppy disks, storage capacity, 1-6
Winchester hard disk, 1-7
Disk Maintenance, 14-3-14-18
allocating disk space, 14-3
command
Data Transfer, 14-9
Disk Summary, 14-7
Duplicate Disk, 14-11
Format Disk, 14-4
INT 10,14-12-14-18
data acquisition tracks, 14-3
data transfer, 15-7
description of disks, 14 - 3
initializing system, INTERVIEW 7000, 2 - 3
installing new system software, 2-7
menu selections, 14-2, 14-4-14-18
overview, 2-15
Disk Name, subfield on Disk Maintenance menu,
14-5
Disk No
field on Line Setup menu, 7-4
field on Record Setup menu, 7-6, 7-10
Disk Number, subfield on Disk Maintenance
menu, 14-5
Disk Summary, Disk Maintenance, menu selection,
14-7
Display, electroluminescent (EL), 1-4
IndexA-8
Display Abort
field on tine Setup menu, 25-6
subfield of BOP Format, 5-14
subfield on Line Setup menu, 5-14
Display Idle
field on tine Setup menu, 32-13
subfield on Line Setup menu, 5-13, 6-10, 9-3,
9-4
cannot display idle if suppressed in FEB, 9-4
Display Mode, field on Display Setup menu, 6-7,
6-18
Display Program Warning Messages, Easy View
Setup menu field, 19-4
Display Setup
menu selections, 6-2
traces, 2 - 23
Display Setup screen, overview, 2-11
Display States, field on Display Setup menu, 6- 20,
31-19
Display Window
cursor keys under programmer's control, 6 - 23
display mode, 6-23
softkey labels under programmer's control, 6-24
DL data, 34-10
DL_CONNECTCONF
entered manually at Layer 2 to "fool" Layer 3
into thinking there is a link, 38-46
primitive forced up by user program at Layer 2,
34-6
primitive sent upward by Layer 2 to confirm the
link, 34-9
DL_CONNECT IND
action primitive at Layer 2, 34-3
condition primitive at Layer 3, 34-3
DL_CONNECf REO
automatic when data primitives are passed down
by Layer 3, 35-1
primitive passed down from Layer 3, 34-8
primitive triggered automatically by Layer 3
Send action, 34-6
sent down automatically at Layer 3 if Layer 2
inactive, 38-44, 38-46
DL_DATA
macro, 33-5
primitives between Layers 2 and 3, 34-9
DL DATAIND
condition at Layer 3, 43-31
sent up automatically by Give Data action at
Layer 2,37-28,37-34,39-28,39-34,
43-25,43-31
SEP '95
Index A: Part I
DL_DATA REQ, sent down automatically by Send
or Resend action at Layer 3, 38-44
Don't Care key, 3-6
in Receive string condition, 25 - 7
Done key
on menu screens, 3-10
used to change real-time display softkeys. 6-6
used to exit softkey rack in spreadsheet, 3-10
used to move from Conditions to Actions,
37-21,38-29,39-22,43-19
Double parens, 3-5
in Protocol Spreadsheet string, 33-3
in Receive string condition, 25-8
Down Arrow key, 30-4
Drive, field on Layer Setup screen, 8-4
Drive 1YPe, subfield on Disk Maintenance menu,
14-6
DSR, available for triggering, 32-5
DSR on/off, Layer 1 Emulate DCE action, 32-12
$~
y
DTE, monitor condition
LAPD,43-9
Layer 1, 32-3
Q.931,44-9
SDLC,39-12
SS#7 Layer 2, 46-7,47-7
X.25 Layer 2, 37 -11
X.25 Layer 3, 38-15
DTE2, monitor condition, Layer 1, 32-8
DTR, available for triggering, 32-5
DTR on/off, Layer 1 Emulate DTE action, 32-12
Dual-Port directive, #pragma quad_display,
creates QUAD softkey, 6-6
Dual- Port DS-OA, optional TIM, 13-1
Dual-Port G.703, optional TIM, 13-1
Dual- Port G.703 Co-Directional, optional TIM.
13-1
Dual- Port T1, optional TIM, 13-1
Dual- Port V.35IEIA - 530(449)/EIA - 232, optional TIM, 13-1
Duplicate Disk
Disk Maintenance, menu selection, 14-11
installing new system software via the DUPDISK
command, 2-7
DXI, SMDS interface, 48-1
SEP'95
E
Easy View
default in TURBO units after power-up, 4-3
display warning messages, 19-4
enable/disable, 19-3
enter after power-up, 19-4
EZ VU key, 4-4
installing updates, 4-19
keep menu info in memory, 19-4
keys used in, 4-7, 4-14
load program edit timeout, 19-5
menus
format, 4-5
help information about selections, 4- 7
item description. 4-6
keys, 4-6, 4-7
leveis,4-4
master title, 4-5
changing the title, 20-22
menu level, 4-5
menu title, 4-5
changing the title, 20-23
selections, 4-6
tree-structed hierarchy, 4-4
mstrmenu.txt, format, 20-20
overview, 4-3
printing text fIles, 4-15
screen saver timeout, 19-5
script fIle
commands, 20- 25
format, 20-20
help-fIle pathname, 20-25
item date, 20-24
item description, 20-25
item name, 20-24
labels, 20-23, 20-25
master information, 20-21
master title, 20-22
master title date, 20-22
menu date, 20-24
menu information, 20-23
menu title, 20-23
menu-item information, 20-24
sample, 20-27
setup menu, 4-3
uses
access help or tutorial information, 4-3
quickly load and run programs, 4 - 3
Easy View Setup, 4- 3
oveIView, 2-15
Easy View Setup screen, menu selections, 19-2,
19-3
IndexA-9
Index A: Part I
Easy View system. See Easy View
EBCD
default BCC parameters, 10-10
reverse bit order appropriate for, 5-16
EBCDIC, default BCC parameters, 10-9
Edit key, 3-7
Editing keypad, 30-3
Editor, Protocol Spreadsheet
See also Protocol Spreadsheet editor
function keys, 30-5-30-10
EIA
condition, nigger Setup menus, 25-9
Layer 1 conditions, 32 - 5
Layer 1 emulate-mode actions, single-port,
32-12
trigger conditions, fails to come true, 2-22
EIAleads
buffered or discarded in FEB, 9-3
effect on character-buffer capacity, 6-27
effect on data-plus-leads display, 9-5
effect on EIA trigger conditions, 9-3
maintaining lead statuses during program chaining,31-19
storage of, 1-16
Emulate
field on LAPD Frame Level Setup screen, 43-3,
43-4
field on SDLC Frame Level Setup screen, 39-3,
39-4
field on SNNSDLC Frame Level Setup screen,
40-3
field on X.25 Frame Level Setup screen, 37-3,
37-4,37-24
field on X.25 Packet Level Setup screen, 38-3,
38-4
Emulate modes, setting up, 5-4
Emulation, connectors used, 1-12
Emulation Addressing, field on SDLC Frame Level
Setup screen, 39-3, 39-5, 40-3
Enable Easy View, Easy View Setup menu field,
19-3
End, editor command, 30-5
End/Incl, field on BCC Setup menu, 10-13
End/N/Incl, field on BCC Setup menu, 10-13
End/Staystarted/Incl, field on BCC Setup menu,
10-13
IndexA-10
End/Staystarted/N/Incl, field on BCC Setup menu,
10-13
Enhance
field on Display Setup menu, 6-12, 7-5
field on Miscellaneous Utilities menu, 18-4,
18-5
field on Trigger Setup menu, 26-7
Enhance character data
as Layer 1 action, single-port, 32-14
on Display Setup, 6-12
Enhance selected trace rows
LAPD action, 43-29
map to color display, 37-33, 38-42, 39-32,
43 - 30, 44-12, 46-10, 47-11
0.931 action, 44-12
SDLC action, 39-32
SNA action, 40- 3
SS#7 Layer 2 action, 46-10
SS#7 Layer 3 action, 47 -11
X.25 Layer 2 action, 37-32
X.25 Layer 3 action, 38-42
Enhancements
black and white, 18-6
color, 18-3-18-6
low intensity, 32-15
must be turned off as well as on at Layer 1,
32-14
used to highlight Bisync addresses, 32-14
Enter Easy View After Power- Up, Easy View Setup menu field, 19-4
Enter State, layer-independent condition, 31-3
Error Injection Rate, field on BERT Setup menu,
11-14,11-22
Error-free seconds, BERT counter, 11-21
Errors
in BERT
automatic injection, 11 -14
manual injection, 11-18
recoverable, 2 -19
Execute key, 3-7
External monitors
control of enhancements
black and white, 18-6
color, 18-3-18-6
RGB color video connector, 1-11, 18-3
RS-170 video connector, 1-11, 18-3
EZ VU key, 3-4, 3-6, 4-4, 4-8
SEP '95
Index A: Part I
F
FACILITIES, field on X.25 Packet Level Setup
screen, 38-7
Facilities
adjunct to send-call action on Protocol Spread~
sheet, X.25 Layer 3, 38-32
relation to FACIUTIES field on X.25 Packet
Layer Setup screen, 38-32
length byte handled automatically, 38-7
Fan
back panel, 1-10
clean filter to prevent overheating. 1-10
Fault, in half-duplex BERT, 11-9
on noisy circuit, 11-9
FEB. See Front end buffer
FEB Setup, overview of screen, 2-12
File, source of playback data from disk, 5 - 5
File Maintenance, 15 - 3-15 -18
absolute pathnames, 15-5
creating new directories, 15-5
current directory, 15-11
default directory, 15-4
directories, 15-4
File Maintenance screen, 15 - 9
current disk, 15-10
directory listings, 15-11
overview, 2-14
files
data files, 15-7
description of, 15-6
linkable program files, 15-14
linkable-object files, 15-6,28-10
compiled contents of spreadsheet, 28-10
linkable-program files, 15-7
loading and saving, 15 - 3
marking files, 15-13
moving from file to file, 15-4
object files, 15-6, 15-14
program files, 15-6, 15-14
Protocol Spreadsheet, 15-7
selecting files for command execution, 15-13
setup files, 15-6, 15-14
types, 15-12
unmarking files, 15-13
menu selections, 15-2
Change Directory, 15 -18
Compile, 15 - 22
compiles contents of file or spreadsheet,
15-22
compiling spreadsheet generates #pragma
hooks, 15 - 23
Copy, 15-18
Delete, 15 - 22
how to execute, 15-14
Load,15-14
Make Directory, 15-18
Print, 15 - 20
Rename, 15-21
Save, 15-15
View, 15-20
Write Enable, 15-21
Write Protect, 15-21
moving from disk to disk, 15-5
naming conventions, files and directories, 15-7
pathnames, the use of periods, 15-8
relative pathnames, 15-6
root (I) directory, 15-4
the Isys directory, 15-6
the lusr directory, 15-6
write-protected fIles, 15-11
Find, editor command, 30-8
Flag key, 3-6
in Receive string condition, 25-7
valid in Suppress field, 6-11
Flags
common to all tests and layers, 31-13
condition, Trigger Setup menus, 25-10
layer-independent action, 31-13
as toggling mechanism, 31-14
layer-independent condition, 31-7
transmitted,33-4
FLG, flag, trace column, 0.931, 44-5
Force data-packet transmit, 38-45
Force receivers out of sync, Layer 1 action, singleport,32-13
Format, field onLine Setup menu, 5-7, 5-13,
11-15,25-6,32-4,32-14
significance in BERT testing. 11-15
Format Disk, Disk Maintenance, menu selection,
14-4
Fox message, 32-10, 32-18,37-27,38-38,
39-27,43-25
"forced down" from Layer 3 to the Layer 1 interface, 34-6
in BERT, 11-7
really a built-in constant, 33-4
Frame fields
diagrammed for LAPD, 43-7
diagrammed for SDLC, 39-9
IndexA-11
SEP '95
-
---"---"-----------"""-----------------------,_."-----------
Index A: Part I
diagrammed for X.25, 37-8
Frame Mode, 5-14
Frame mode, optimizing high - speed performance,
2-30
Frame sent, emulate-mode condition
LAPD,43-17
SDLC, 39-19
should be used along with More/No More to Resend, 37-20,39-21, 43-18
X.25 Layer 2, 37 -18
Frame Timestamps, field on Front-End Buffer
Setup screen, 9-8, 37-10, 38-14,39-11,
40-6,43-9,44-8,46-6,47-7
Framing
HEC, in ATM, 49-2
PLcp, in ATM, 49-2
Framing error, monitor/receive condition, Layer 1,
32-4
Free, Summary subfields on Disk Maintenance
menu, 14-8
Freeze key, 3-11
contrasted with Capture On/Off trigger action,
3-11
Freeze LED, front panel, 1-6
Freeze mode
in BERT, 11-17
initiated by trigger. See Capture data to screen
(on/off)
parallel cursor movement during, 6-27, 37-6,
38-8,39-7,40-4,44-4,46-4,47-4
Frequency selection, back panel, 1-9
From
field on Disk Maintenance menu, 7-4
subfield on Disk Maintenance menu, 14-9
From Disk Number, subfield on Disk Maintenance
menu, 14-11
Front end buffer
applies to playback of bit-image data, 2-20
Idle Suppress field, does not apply to playback of
bit-image data, 2-20
on playback path of bit-image data, 2-20, 9-5,
9-6
setup
effect on character-buffer capacity, 6-27
effect on data -plus-leads display, 6-9
time ticks and EIA leads, storage of, 1-16, 2 - 20
Front End Buffer Setup, menu selections, 9-2
IndexA-12
Front panel, 1-4
electroluminescent (EL) display, 1-4
function keys, 1-5
LED overlay, 1-6
LED's, 1-5,2-20
U/A,1-15
Function keys, 1-5
G
G.703
optional TIM, 13-1
record setup, 7-8
General operation, 2 -1-2 - 30
boot-up program, creating a user interface, 2-4
changing default menus, 2-6
common problems, 2-22-2-26
data capture, 2-20
front end buffer, 2-20
front end buffer, on playback path of bit-image
data, 2-20
initializing system, INTERVIEW 7000,2-3
installing new system software, 2-7
o'Verview of menus, 2-9-2-15
power up, 1- 20, 2-1
rerunning a test program, 2-16
running a test program, 2-16
running default program, 2-6
Give data, 33-5
LAPD,43-25
SDLC action, 39-28
X.25 Layer 2 action, 34-10, 37 - 28
X.2S Layer 3 action, 38-39
Go-error, editor command, 30-10
Go-line, editor command, 30-9
GoodBCC
adjunct to monitor-frame condition
LAPD, 43-14, 43-15
SDLC, 39-15, 39-17
X.25 Layer 2, 37 -14, 37 -15
adjunct to send-frame action
LAPD,43-25
SDLC,39-27
X.25 Layer 2, 37-28
adjunct to send-string action, Layer 1, singleport, 32-10
appended to transmit string, 10-5
as condition, 10-5
default BCC for frames, 37-28, 39-27, 43-25
monitor/receive condition, Layer 1, 32-4
operational only when Rev Blk Chk enabled,
32-4
SEP '95
Index A: Part I
overlay, 10-3
parameters defined on BCC Setup menu, 10-6
Graphical Statistics menu, color graphics, 18-6
H
Half-duplex BERT, 11-6
Home key, 3-9, 30-4
in Easy View, 4-8, 4-14
Host Port, SNA frame setup selection, 40-3
HRD/usr/user_intrf
affect on Start Up screen, 2 - 3
boot-up program, creating a user interface, 2-4
HS Frame Mode, subfield on Line Setup menu,
5-9
Handset connector, 1-10
Handshake, field on BERT Setup menu, 11-5,
11-6,11-7,11-12
relation to Interface Control screen, 11-7
I
I, intensity, field on Graphical Statistics menu,
22-7
Hardware, 1-3-1-20
back panel, 1-8
clock, 1-17
disk drives, 1-6
front panel, 1-4
keyboard,1-4
operating environment, 1-17
operating positions, 1-18
physical dimensions, 1-4
power up, 1-19
storage capacity, 1-16
Idle
change idle -line character, 32-13
display in relation to Outsync action, 32-13
display used for visual record of time intervals,
9-4
displaying for visual record of lead timings, 6-10
displaying synchronous idle, 5-13
retained/discarded on FEB Setup menu, 9-3,
9-4
selecting transmit idle, 5 -14
voltage not affected by inverted polarity,S -17
Header Error Control. See HEC framing
Idle line action, used in X.21 bis, 36-4
HECframing
for ATM, 49-1, 49-18
in ATM, 49-2
Idle Suppress, field on Front-End Buffer Setup
screen, 9-4
does not apply during playback, 2 - 20
Help file, pathname, in Easy View script file,
20-25
Idle Timeout
conditions under which timer expires, 39-4
expired, emulate-mode condition, SDLC,
39-19
field on SDLC Frame Level Setup screen, 39-3
field on SNNSDLC Frame Level Setup screen,
40-3
maximum and minimum values, 39-4
Hex, subfield on Trigger Setup menu, 26-7
Hex key
for hexadecimal data entry, 3-6
for hexadecimal translation of line data, 6-14
LED display on keycap, 6-14
Hexadecimal display
in relation to order of transmission, 6-14
turned on/off by trigger action, 6 -15
Hexadecimal field, defined, 38-6
High Outgoing Channel #, field on X.25 Packet
Level Setup screen, 38-3
High speed
data recording, 7-8
optimizing performance, 2;"'25, 2-26
frame mode, 2 - 30
High Speed Frame Mode, subfield of BOP Format,
5-14
SEP '95
IL buffer
See also lL BUPS
and primitives, 34-3
configuring number/size of, via IL BUFS identifier,28-13
created by DDCMP package, 41-2
default number/size of, 28-13
string to be referenced in. 34-6
ILBUFS
See also lL buffer
Protocol Spreadsheet, programming block, 28-8,
28-13
comments in, 28-14
In/out, editor command, 30-6
IndexA-13
Index A: Part I
Increment counter, layer-independent action,
31-9
Integrated Services Digital Network (ISDN), SS#7
Layer 3,47-22
Increment flag byte, as 16-bit binary counter, layer-independent action, 31-14
Interface Control Setup, overview of screen, 2-12
Indication primitives, 34-5
versus "Requests", 34-10
Interlayer message buffer. See IL buffer
Info element, 0.931,44-5
INFO frame
monitor/receive condition
LAPD,43-10
SDLC,39-13
X.25 Layer 2, 37 -12
send action
LAPD,43-20
SDLC,39-23
used to convey DL data sent down from Layer
3,37-23,43-20
X.25 Layer 2, 37 - 22
INFO-ELEMENT, trace column, 0.931,44-5
Initial Condition, field on Record Setup menu,
7-10
Initial State, field on BCC Setup menu, 10-12
Initializing system software, INTERVIEW 7000,
2-3
Injection Rate
field on BERT Setup menu, 11-19
status field on BERT results screen, 11-21
Input/output connectors, back panel, 1-10
AUXILIARY TIL, 1-11
CRT/RGB, 1-11
ISDN handset, 1-10
PRINTER, 1-10
REMOTE RS- 232, 1-10
RS -170 composite video, 1-11
Insert Char key, 30-4
in menu fields, 3-7
used to exit insert mode, 3-8
Insert Line key, 30-4
in spreadsheet, 3-7
on statistics screens, 3- 7
Insert mode, 3-8, 30-4
Installing new system software, on hard disk, 2-7
Instrument, menu field on Disk Maintenance
screen, for INTERVIEW 10 transfer, 14-16
INT 10, Disk Maintenance selection,
14-15-14-18
IndexA-14
Interlayer buffer. See IL buffer
Interrupt packet, sample program to enhance all,
38-43
INTERVIEW transfer, INTERVIEW 5, 10, 15
PLUS data, transfer from Disk Maintenance
screen, 14-12-14-18
Invalid frame
defined, 37-7, 39-8, 43-8
receive condition
lAPD,43-15
SDLC,39-17
X.25 Layer 2, 37 -16
Invalid packet
defined, 38-12
receive condition, X.25 Layer 3, 38-26
Invert BCC, field on BeC Setup menu, 10-12
IPARS
default BCe parameters, 10-9
default sync pattern, 5-8
reverse bit order appropriate for, 5-16
SY characters inappropriate for, 5-8
ISDN
See also 0.931
handset connector, 1-10
ISDN_D,42-3
sample Line Setup, 5 -18
ISDN SfT/U, optional TIM, 13-1
Isoc
data setup, 5 -15
format in BERT, 11-15
Item date, in Easy View script file, 20-24
Item description, in Easy View script file, 20- 25
Item name, in Easy View script file, 20-24
K
Keep Easy View Menu Information in Memory,
Easy View Setup menu field, 19-4
Keyboard, 1-4
condition, Trigger Setup menus, 25-12
editing keypad, 30- 3
function keys, 1 - 5
layer-independent condition, 31-4
programming keys, 3 - 3-3 - 5
SEP '95
Index A: Part I
real-time keys. 3-10-3-12
soft (function) keys, 3-3
for editing. 30-5-30-10
green-red characteristics not affected by logic
(polarity), 5-17
Test Interface Module, 1-15
Left Arrow key, 30-4
Keyword, 33 - 3
/lib directory, filing system, 15 - 24, 28 -11
Line data, data capture, 2-20
L
L, label, field on Graphical Statistics menu, 22-4
Labels, in Easy View script file, 20- 23, 20-25
LAPD,43-3
diagram of frame fields, 43-7
send actions, 43-19
used with ISDN D channel, 42-3
LAPD Frame Level Setup screen, 43-2
Last, column on Tabular Statistics screen, 21-6,
31-10,31-11
Layer, field on Display Setup menu, 6-18, 6-20,
31-19
Layer 2, user program to force packets up to Layer
3 and down to Layer 1, 38-24
Layer Setup, 8-3-8-7
how to save, 8-5
Personality packages, 8-3
reside on user and hard disks, 8-3
Protocol Configuration screen, 8-4
protocols, select and load, 8-3
Layer Setup screen, overview, 2-14
Layers
identified on Program Trace, 6-20
passing data between, 2-23
program model, 24-3-24-8
Protocol Spreadsheet, programming block, 28-8
comments in, 28-14
LCN
adjunct to monitor/receive-packet condition,
X.25 Layer 3, 38-18
allocation sequence, 38-5, 38-31
assigned dynamically on per-call basis, 38-4
column on X.25 Packet Level Setup screen,
38-4,38-5
predefined for a particular call address ("path"),
38-4,38-6
trace column, X.25 Layer 3, 38-12
LED's
front panel, 1-5, 1-6,2-20
interface status, 1-5
INTERVIEW status, 1-6
UIA, 1-6, 1-15
Line number, of cursor position in frozen Program
'frace, 6- 21
Line Setup, 5-3-5-17
significance in BERT testing, 11-14
Line Setup screen
disabled. 5-5
menu selections, 5 - 2
Async, 5-18
Bisync, 5-18
ISDN, 5-18
SNA,5-18
SS#7,5-18
X.25,5-18
overview, 2-11
Line utilization, programming example, 21-11
Linkable-object files, 15-6
accessed via Object block-identifier, 28-10
advantage over object files, 15 - 23
Ccode
contents of LOB] files, 15-6
must be compatible with menu selections,
15-23
compiled spreadsheet
accessed via OBJECT block-identifier only,
15-23
contents of LOBJ files, 15 -6, 15 - 23
must be a valid program, 15 - 23
contents of, 15-22,28-10
counters or flags in, 28-12
efficiently use memory and spreadsheet, 28-12 •
in !lib directory, 15-24
search rules for, 28 -11
transparent to unit configuration, 15-23
Linkable-program files, 15-7
C code, in LPGM files, 15-7
changing setups, 4-17
Lists, on Protocol Spreadsheet, 33-1
Load, File Maintenance, menu selections, 15-14
Load key, 3-6, 15-14
Load program, layer-independent action, 31-19
Load Program Edit Timeout, Easy View Setup
menu field, 19-5
Logical DTElDCE
contrasted to physical DTEIDCE, 37-4
IndexA-15
SEP '95
-
-
-------------------------"-----------------------------
Index A: Part J
determines command and response addresses,
37-4
determines order (ascending/descending) of
LCN selection, 38-4
Loop-back C/R bit, adjunct to send-frame action, LAPD, 43 - 22
Loop- back PIF bit
adjunct to resend-frame action
LAPD,43-27
X.25 Layer 2, 37 - 30
adjunct to send-frame action
LAPD,43-22
SDLC,39-25
X.25 Layer 2, 37 - 25
Low, subfield on Trigger Setup menu, 26-7
Low Outgoing Channel #, field on X.25 Packet
Level Setup screen, 38-3
LRC Parity, field on BCC Setup menu, 10-12
LU 6.2, SNA selection, 40-3
M
M, trace column, X.25 Layer 3, 38 -14
Mbit
adjunct to monitor/receive-packet condition,
38-18
adjunct to send-data-packet action, 38-36
position diagrammed, 38-14
m_Io,Yh,Yrmtv, signalled by DDCMP package,
41-2
Make Directory, File Maintenance, menu selection, 15-18
Mark key, 30-5
cursor timing, 6-16
in Easy View, 4-15, 4-17
in Freeze mode displays, 3-14
on File Maintenance screen, 3-7,15-13
used as program tab in spreadsheet, 3-9
Marking text, in Easy View text files, 4-15
Master information, in Easy View script file,
20-21
Master title
Easy View, 4-5
changing the title, 20-22
in Easy View script file, 20-22
Master title date, in Easy View script file, 20-22
IndexA-16
Maximum, column on Tabular Statistics screen,
21-6,31-10
Maximum data rates, data recording, 1-16
Maximum recording times, SCSI drives, 7-5
Memory, capacity, 1-16
Menu date, in Easy View script file, 20-24
Menu information, in Easy View script fIle, 20-23
Menu level, Easy View, 4-5
Menu selections, Easy View, 4-6
Menu title
Easy View, 4-5
changing the title, 20-23
in Easy View script file, 20- 23
Menu-item information, in Easy View script file,
20-24
Menus
overview, 2-9-2-15
See also Separate listing, each menu name
configuring menus, 2-10
Program Menu, 2-9
Printer setup, 16-3-16-5
Record Setup, 7-5-7-12
Message Buffer, field on BERT Setup menu,
11-10
Message fields, diagrammed for Q.931, 44-6
Message Signal Units (MSU's), Layer 3, 47-6
Message type, Q.931, 44-5
Microfloppy disks
compatibility, 1-6
storage capacity, 1-16
write protection, 1-6
MIL, field on Line Setup menu, 5 -17
MIL-I88,5-17
Minimum, column on Tabular Statistics screen,
21-6,31-10
MISC, trace column, X.25 Layer 3,38-14
Miscellaneous Utilities
overview, 2-15
with color mapping options, 18-3-18-6
See also Graphical statistics menu, color graphics
Miscellaneous Utilities screen
black and white enhancements, 18-6
color display, selectable options, 18-4-18-5
background color, 18-5
blink,18-5
character, 18-5
SEP '95
Index A: Part I
controlling color displays from, 18-3-18-6
menu selections, 18-2
MOD 128, 37-4, 38-4, 39-4, 43-4
MOD 8,37-4,38-4,39-4,43-4
Mode
field on Line Setup menu, 5-3, 7-4,11-5,
11-6,11-22,32-12,38-24,43-14
test mode field on Line Setup menu, 1-14
Mode of Operation
field on Frame Level Setup screen, 38-16,
43-10
field on LAPD Frame Level Setup screen, 43-3,
43-4
field on SDLC Frame Level Setup screen, 39-3,
39-4
field on SNNSDLC Frame Level Setup screen,
40-3
field on X.25 Frame Level Setup screen, 37-3,
37-4
field on X.25 Packet LevelSetup screen, 38-3,
38-4
Modem connector, external, 1-10
Monitor mode, setting up, 5 - 3
More to resend, emulate-mode condition
LAPD,43-18
SDLC,39-20
X.25 Layer 2, 37 -19
X.25 Layer 3,38-28
Move, editor command, 30-6
MPM errors, 2-19
MSG-TYPE, trace column, Q.931, 44-5
mstrmenu.txt, format, 20-20
Multi-drop
SDLC
enabled on Frame Level Setup screen, 39-3,
39-5
resend frame, 39-30
reset Nr, 39-31
reset Ns, 39-31
SNA, enabled on Frame Level Setup screen,
40-3
N
N, name, field on Graphical Statistics menu, 22-6
N_DATA, macro, 33-5
N_DATA IND, sent up automatically by Give Data
action at Layer 3, 38-39, 38-44
SEP'95
National Format, field on SS#7 Packet Level Setup screen, 47 - 3
Negative exponent, meaning in BERT formulas,
11-14
Network Indicator, SS#7 Layer 3, 47-9
Network Management (NETM) Headers, SS#7
Layer 3,47-18
Next Page key, 30-4
in Easy View, 4-8, 4-14
in spreadsheet, 3-9
on statistics screens, 3-9
on trace display, 37-6, 38-8, 39-6, 40-4,
44-4,46-4,47-4
Next state, Protocol Spreadsheet, programming
block,28-9
comments in, 28-15
No BCC, appended to transmit string, 10-6
interpreted as bad BCC, 10-6
No display, display mode, 6-28
No more to resend, emulate-mode condition
LAPD,43-18
SDLC,39-20
X.25 Layer 2, 37-19
X.25 Layer 3, 38-28
Not Equal key, 3-6
in Receive string condition, 25-7
used in Suppress field to indicate "display only",
6-11
Nr
acknowledging last Ns, adjunct to send-frame
action
LAPD,43-23
SDLC,39-25
X.25 Layer 2, 37 - 26
calculated automatically, adjunct to send-frame
action
LAPD,43-23
SDLC,39-25
X.25 Layer 2, 37 - 26
repeating last Nr, adjunct to send-frame action
LAPD,43-23
SDLC,39-25
X.25 Layer 2, 37 - 26
reset, emulate - mode action
lAPD, 43- 28
SDLC, for a specific controller address, 39-31
X.25 Layer 2, 37 - 31
trace column
LAPD,43-8
SDLC, 39-10
staggered to indicate two separate numbering
sequences, 37-9, 39-10
IndexA-17
Index A: Part I
X.25 Layer 2, 37-9
tracked for specified addresses in SDLC multidrop, 39-5
value, adjunct to send-frame action
IAPD,43-23
SDLC,39-25
X.25 Layer 2, 37 - 26
Nrerror, emulate-mode condition
LAPD,43-16
SDLC,39-19
X.25 Layer 2, 37-18
NRZI, field on Line Setup menu, 5-17
Ns
calculated automatically, adjunct to send- 1frame action
IAPD,43-24
SDLC,39-27
X.25 Layer 2, 37-27
reset, emulate-mode action
LAPD,43-28
SDLC, for a specific controller address, 39-31
X.25 Layer 2,37-31
same as last-received Nr, adjunct to send-Iframe action
LAPD,43-24
SDLC,39-26
X.25 Layer 2, 37 - 27
skip to correct Ns plus one, adjunct to send- 1frame action
LAPD,43-24
SDLC, 39-27
X.25 Layer 2,37-27
trace column
LAPD,43-8
SDLC,39-10
staggered to indicate two separate numbering
sequences, 37-9,39-10
X.25 Layer 2, 37-9
tracked for specified addresses in SDLC multidrop, 39-5
value, adjunct to send - I -frame action
IAPD,43-23
SDLC,39-26
X.25 Layer 2, 37 - 26
Ns error, emulate-mode condition
LAPD,43-16
SDLC,39-18
X.25 Layer 2, 37 -17
Number of Faults, BERT counter, 11-21
IndexA-18
o
OAM cells, in ATM, 49-17
Object, Protocol Spreadsheet, programming block,
28-8
comments in, 28-14
format of, 28 -11
items that may precede
C regions, 28-8
comments, 28-8
IL BUFS identifier, 28-8
must be used to access compiled spreadsheet,
15-23
placement of, 28-11
used to access linkable-object files, 28-10
Object code
contents of linkable - object files
compiled C code, 15-6
compiled spreadsheet, 15-6
accessed via OBJECT block-identifier only,
15-23
must be a valid program, 15-23
contents of object fIles, 15-6
in linkable-program mes, compiled C code,
15-7
loaded in automatically via Load Program action, 31-19
rerunning object version of program, 2-16
Object files, 15-6, 15-12, 15-15
compared to linkable-object files, 15-6, 15-23
not as versatile as source -code files, 15 -17
use disk - space intensively, 15 -17
Offset, in Freeze mode data displays, 6-27
On Signal, layer-independent condition, 31-8
On/off (power) switch, back panel, 1-10
1 OF, field on Trigger Setup menu, 25-8
One-of character list
effect of not-equal character, 25-8
monitor/receive condition, Layer 1, 32 - 3
Operating environment, 1-17
Operating positions, 1-18
Operations and Maintenance cells. See OAM cells
Operators, relational, in counter conditions, 31-5
Optional interface
Dual-Port DS-OA, 13-1
Dual-Port G.703, 13-1
Dual-Port G.703 Co- Directional, 13-1
Dual-Port Tl, 13-1
Dual-Port V35/EIA-530(449)IEIA-232, 13-1
SEP '95
Index A: Part I
G.703,13-1
ISDN Sffro, 13-1
RS-232,13-1
RS-449, 13-1
RS-485 (RC-824S), 13-1
Tl,13-1
TI'L,13-1
V.35,13-1
X21,13-1
Order of transmission
in relation to binary display, 6-15
in relation to code charts, 5-16
in relation to hex display, 6-14
in relation to pattern sync in BERT, 11-11
Originating Point Code (OPC), SS#7 Layer 3,
47-10
Origination/destination link, message-type condition, 0.931,44-11
OSI
Data Link Layer 2, in ATM, 49-2
Layer Setup, 8-3
Open Systems Interconnection, layered programming, 24-3-24-8
See also Layers
Physical Medium Layer 1, in ATM, 49-2
primitives, 24-8
OSI primitives. See Primitives
Other frame
monitor/receive condition
LAPD,43-11
SDLC,39-13
X.25 Layer 2, 37 -12
send action
LAPD,43-21
SDLC, 39-24
X.25 Layer 2, 37-24
Other packet
monitor/receive condition, X25 Layer 3, 38-17
send action, X25 Layer 3, 38-33
Out of sync, status message in BERT, 11-21
Outsync
called "resync" in BERT, 11-8
Layer 1 action
compared to Capture Off action, 32-13
single-port, 32-13
parameters not selectable in DDCMp, 41-1
subfield on Line Setup menu, 5-8,5-12
Outsync Char, field on Line Setup menu, 3-6
SEP '95
Overhead, Summary subfields on Disk Maintenance menu, 14-8
Overlay, Thst Interface Module, 1-6
Overstrike mode, 3-8
p
PIF, trace column
LAPD,43-8
SDLC, 39-11
SNA-SDLC,40-7
X.25 Layer 2, 37 -10
P/F bit
adjunct to monitor/receive-frame condition
LAPD,43-13
SDLC,39-15
X.25 Layer 2, 37-14
adjunct to resend-frame action
LAPD,43-27
SDLC, 39-31
X.25 Layer 2, 37-30
adjunct to send-frame action
LAPD,43-22
SDLC,39-25
X.25 Layer 2, 37 - 25
Packages Loaded
column on Layer Setup menu, 37 - 3, 38- 3,
43-3,47-3
column on Layer Setup screen, 8-4
Packet fields, diagrammed for X25, 38-10
Packet sent, emulate-mode condition
should be used along with More/No More to Resend,38-29
X.25 Layer 3,38-27
Packet-switching features, for ATM, 49-1
Parity
a consideration when entering BCe parameters,
10-12
adjustment automatic in Sync Chars field, 5-9
always the last bit transmitted, 5 -16
automatic calculation of in receive sync pattern,
5-8
field on Line Setup menu, 5-7, 5-9, 11-15,
25-6,32-4
field on Printer Setup menu, 16-4
in BERT testing, 11-15
in setup, 5-7
Parity errors
monitor/receive condition, Layer 1,32-4
special display of, 5-7
IndexA-19
Index A: Part I
PATH, field on X.25 Packet Level Setup screen,
38-5
Physical Layer Convergence Protocol. See PLCP
framing
Path
adjunct to receive-packet condition, X.25 Layer
3,38-25
adjunct to send-packet action, X.25 Layer 3,
38-32,38-33,38-34
used in all packet types except Restart, 38-34
correspondence at different layers, 34-5,38-34
more "programmable" than LCN, 38-25, 38-34
part of definition of data primitive, 34-5
tied to a set of Call Request parameters on X.25
Packet Level Setup screen, 38-5, 38-24,
38-34
Playback
control leads, 2-20, 9-5
disk data, 2 - 20
EIA leads, storage, 1-16
manual control of, 3-12
source of data selected on Line Setup screen,
5-5
time ticks, 2-20, 9-6
timer values not affected when time ticks enabled,31-10
transfer of data prior to, 7-4
Pattern, field on BERT Setup menu, 11-7
Pattern sync, in half- duplex pseudorandom BERT,
11-11
two default sets, 11 - 12
Pattern Sync Status
field on BERT results screen, 11-20
line on BERT results screen, 11-21
PDU. See Primitive data unit; Primitives
Perc(entage), of Program Trace buffer storing previous data, 6-21
Percentage, in Freeze mode data displays, 6-27
Percentages, computed through the sampling action, 21-11
Performance, optimization, 2-25, 2-26
Personality packages. See Protocol packages; Protocol packages and Layers
PH_ACTIVATE REQ, sent down automatically at
Layer 2 if Layer 1 inactive, 37-34, 39-34,
43-31
PH_DATA, primitives between Layers 1 and 2,
34-9
PH_DATA REQ, sent down automatically by Send
or Resend action at Layer 2, 37-34, 39-34,
43-31
PH_TD_DATA IND, signalled by DDCMP package, 41-2
Physical dimensions, size and weight, 1-4
Physical DTE/DCE
basis of Source column on trace display, 37 -7,
38-12,39-6,40-4,43-6,44-5
contrasted to logical DTE/DCE, 37-4
Physical Layer, in ATM, 49-2
IndexA-20
PLCP framing
for ATM, 49-1
format, 49-18
inATM,49-2
Polarity
field on Line Setup menu, 5 -16
normal versus inverted, 5 -17
Power connector, 1-8
Power switch, back panel, 1-10
Power up, 1-19,2-1
entry into Easy View, 4-3
manual reset, 2-2, 4-3
self tests, 2-1
Pr
acknowledging last Ps, adjunct to send-packet
action, X.25 Layer 3,38-36
calculated automatically, adjunct to send-packet
action, X.25 Layer 3,38-36
repeating last Pr, adjunct to send-packet action,
X.2S Layer 3, 38-36
reset, emulate-mode action, X.25 Layer 3,
38-41
trace column
staggered to indicate two separate numbering
sequences, 38-13
X.25 Layer 3, 38-12
value, adjunct to send-packet action, X.25 Layer3,38-35
Pr error, emulate-mode condition, X.25 Layer 3,
38-27
#pragma quad_display, Dual-Port directive,
creates QUAD softkey, 6-6
#pragma tracebuf, C directive, used to configure
size of trace-buffer arrays, 6-19, 6-25
Preamble, field on BERT Setup menu, 3-6
Preamble characters, in half-duplex BERT, 11-7,
11-9
SEP '95
Index A: Part I
Prev Page key, 30-4
in Easy View, 4-8,4-14
in spreadsheet, 3-9
on statistics screens, 3-9
on trace display, 37 -6, 38- 8, 39-6,40-4,
44-4,46-4,47-4
used to restore previous menu, 3-9
Primary (host) in SDLC, 39-4
Primitive data unit
See also Primitives
and IL buffers, 34- 3
Primitives
as conditions and actions, 34- 3
automatic, 35-1
at Layer 1, 34- 3
below the top layer, 35-1
monitor primitives, 35-1
varies with protocol package, 35-1
currently not accessible at Layer 1, 34-3
indications versus requests, 34-10
Layer 1 not automatic, 34-3
layered programming, 34-3
Layers 1 through 7, listed, 11-13
on spreadsheet
indication of direction, 34-4
indication/confirm, 34-5
path, 34-5
request/response, 34- 5
type, 34-4
OSI,24-8
prefixes, 34-4
several automatic at given layer
LAPD,43-31
SDLC,39-35
X.25 Layer 2, 37 - 34
X.25 Layer 3, 38-44
shared by layers, 34- 3
used for passing data macros downward, 33 - 5
Print prompt, layer-independent action, 31-18
Print timer, layer-independent action, 31-16
statistical log produced by, 21-9
Printer, 16-3-16-5
loading printer setup, 16-8
Printer Setup screen, 16-3-16-5
loading configured menu, 16-8
menu selections, 16-2, 16-3-16-5
characters per line, 16-5
form feed, 16-5
format character buffer, 16- 5
handshake mode, 16-6
lines per page, 16-5
new line, 16-4
number of bits, 16-4
number of pads, 16-5
parity, 16-4
print to file instead of printer, 16-6-16-8
printer type, 16-5
speed,16-4
saving configured menu, 16-7
printing data, 16-10-16-15
from display window, 16-16-16-17
line data, 16-11-16-15
program trace, 16-14-16-15
protocol traces, 16-13-16-15
statistics, 16-15
user traces, 16-17
printing disk files, 16-17-16-18
printing static displays, 16-8
Layer Setup screen, 16-10
program menus, 16-8
Protocol Spreadsheet, 16-8
setup menus, 16-8
Trigger Setup screens, 16-8
RS - 232 printer connector, 16- 3
saving printer setup, 16-7
special characters, data, display of, 16-10
special characters, menus, display of, 16-7
spreadsheet control of, 16-17
Print
File Maintenance, menu selection, 15 - 20
layer-independent action, 31-16
Printer connector, 1-10, 16-3
Print accumulator, layer-independent action,
31-16
Program key, 2-4, 3-4
unit unexpectedly enters Run mode, 2-22
Print counter, layer-independent action, 31-16
statistical log produced by, 21-9
Program trace, 6-19
#pragma tracebuf, 6-19
as customized protocol analysis, 31-19
as debugging tool, 31-19
buffer may be scrolled through in Freeze mode,
6-19
buffer size may be increased, 6-19
generated by trace actions on the Protocol
Spreadsheet, 31-18
Print Easy View text file, 4-15
Print key
in Easy View, 4-14
used to print data, 3-14
used to print programmi~g screens or spreadsheet, 3-6, 16-8
SEP'95
Program files, saving and loading, 23-5
IndexA-21
Index A: Part I
printing, 16-14
run-mode softkey available if Trace action invoked or if state trace requested, 6-19
sample trace, 6-19, 6-21
selecting state names from via Display Setup,
6-20,31-19
specific to Layer!fest selected on Display Setup,
6-20,31-19
Programming
concepts of
branching (changing states), 24-3,28-9
aS! layers, 24-3-24-8
simultaneous tests, 24- 3-24-4
states, 24-3
three-tiered design, 23-1-23-5
program structure, Protocol Spreadsheet,
28-6-28-7
Prompt
field on Trigger Setup menu, 26-3
layer-independent action, 31-12
printing, 31-18
using backslash and double-quote characters
inside of, 31-12
Protocol header
applied to user data by Send action, 34-6
not applied if Data Req primitive used instead of
Send, 34-7
Protocol hex, user program to convert X.25 headers to hexadecimal, 37-35
Protocol packages, 8- 3
general description, 23- 3-23 -4, 24 - 7
user disk, 8-3
Protocol Spreadsheet
comments, 28-14-28-15
constants, 24-8, 29-3-29-7
creating and editing, 23-4-23-5
See also Protocol Spreadsheet editor
editor. See Protocol Spreadsheet editor
files
reading and writing, 30-6-30-10
saving and loading, 23 - 5
function key hierarchy (editor), 30- 2
function key hierarchy (programming), 28-2
function keys, 28-3-28-5
fundamentals, 28-3-28-7
general description of capabilities, 23-1,
23-3-23-4
Layer 1 conditions and actions enabled automatically, 32-1
Mark key, used as program tab, 3-9
overview, 2-13
printing, 16-8
IndexA-22
program format, 28 -10
program structure, 28-6-28-7
special ASCII characters
backslash (\), 3-6
double quote ("), 3-6
space ( ), 3-6
spreadsheet editor, WRITE command, 15-7
syntax errors, 2 -18
unexplained strike-through's, 2-22
use of cursor keys, 3-9
use of softkeys and the Done key, 3-10
variables shared with Trigger Setup menus, 23-5
Protocol Spreadsheet editor, 30-3-30-10
insert mode, 3-8
Mark key, used as program tab, 3-7
WRI'IEcommand,15-7
Protocol Trace, softkey labels under programmer's
control, 6-18
Protocol trace
See also Trace display
display entering Run mode enabled on Display
Setup, 6-18
enabled on Layer Setup screen, 6-17
printing, 16-13
Protocols
compatibility with line setup, 8-4
how to select and load, 8-3
PROTSEL, Protocol Select, Layer Setup function
key used to select protocol-configuration
screen for a given layer, 37-3, 38-3, 47-3
Ps
calculated automatically, adjunct to send -datapacket action, X.25 Layer 3, 38-35
reset, emulate-mode action, X.25 Layer 3,
38-41
same as last-received Pr, adjunct to senddata-packet action, X.25 Layer 3, 38-35
skip to correct Ps plus one, adjunct to senddata -packet action, X.25 Layer 3, 38-35
trace column
staggered to indicate two separate numbering
sequences, 38-13
X.25 Layer 3, 38-12
value, adjunct to send-data-packet action,
X.25 Layer 3, 38-34
Ps error, emulate-mode condition, X.25 Layer 3,
38-26
Q
Q, trace column, X.25 Layer 3,38-13
Qbit
adjunct to monitor/receive-packet condition,
38-18
SEP '95
Index A: Part I
adjunct to send -packet action, 38-36
position diagrammed, 38-13
0.931
diagram of message fields, 44-6
message types, adjunct to om and DCE receive
conditions, 44-9
used with ISDN D channel, 42- 3
QUAD softkey, 6-6
Quotation mark, entry of inside prompt message,
31-12
R
RAM
data storage, 1-16
RAM-to-disk transfer
bit-oriented data, 7-4
character buffer, 7-4
RAM -to-file transfer
bit-oriented data, 7-4
character buffer, 7-4
RC-8245, optional TIM, 13-1
RcvBlkChk
enabled automatically for BOp, 32-4
field on Line Setup menu., 10-3,25-5,32-4,
32-11
field on Line Setup screen, 26-5
must be enabled for BCC conditions to come
true, 32-4
subfield on Line Setup menu, 5-13
Read, editor command, 30-6
formatted, 30-6
unformatted, 30-7
Rec, field on Line Setup menu, 5-5
Receive, emulate - mode condition
LAPD,43-15
Layer 1, 32-3
SDLC, 39-17
X.25 Layer 2, 37 -15
X.25 Layer 3,38-24
does not see the data line directly, 38-24
may specify path as added condition, 38-24
Receive2, emulate-mode condition, Layer 1,
32-8
Receiver, Conditions, Trigg~r Setup menus, 25-5
Record
layer-independent action, 31-20
maximum times, SCSI drives, 7 - 5
start_rcrd"'play, Croutine, 16-6
Record key, 3-12, 7 -12
Record Setup
defaults, 7-4
menu selections, 7-2, 7 - 5-7-11
overview of screen, 2-11
the screen buffer, 7-4
Record Speed, field on Record Setup menu, 7-8
Recording bit - image data, with SCSI hard drive,
2-27
Recording data, 7 - 3-7 -12
format of recorded data, 7 - 3
bit-image data, 7-3
character-oriented, 7-3
manual control of, 3-12
maximum rate, 1-16
medium used, 7-3
record speed
high - speed, 7-8
normal,7-8
screen buffer
manual control of, 7-12
trigger control of, 7 -11
spreadsheet control of, 31-20
trigger control of, 7-11
with EIA lead transitions, 1-16
Redirect run-mode output
Line and Record setups override, 16-6
terminated by recording to disk, 16-6
to disk file instead of printer, 16-6
REJ
monitor/receive condition
LAPD,43-10
SDLC,39-13
X.25 Layer 2, 37-12
X.2S Layer 3, 38-16
send action
LAPD,43-20
SDLC,39-23
X.25 Layer 2, 37 - 23
address required for Send REJ, 37 - 23
X.25 Layer 3, 38-31
Relative pathnames, files and directories, 15-6
Remote Control Setup menu, overview, 2-15
Remote LED, front panel, 1-6
REMOTE RS- 232 connector, 1-10
Rename, File Maintenance, menu selection, 15 - 21
Replace, editor command, 30-9
Request primitives, 34-5
versus "indications", 34-10
IndexA-23
SEP'95
~
. ------------=--___
--.----~'----"-----'"---.'''~------------
,_._lI____
IIlOl_._._ _......_ _....
~_iI!!M'
......
Index A: Part I
Resend frame
effect on Frame Sent condition, 37-18,39-19,
43-17
first in window, 37-30, 39-29, 43-27
action resets resend pointer, 37-30, 39-30,
43-27
in relation to window, 37-5, 38-4,39-5,43-5
LAPD action, 43-26
next in window, 37-30, 39-29, 43-27
default resend, 37-30, 39-29, 43-27
SDLC action, 39-28
to a specific controller address, 39-30
used with More To Resend and No More To Resend conditions, 37 -19,39-20, 43-18
X.25 Layer 2 action, 37 - 28
Resend packet
effect on Packet Sent condition, 38-27
first in window, 38-39
action resets resend pointer, 38-40
next in window, 38-39
default resend, 38-39
programming example, 38-46
used with More To Resend and No More To Resend conditions, 38 - 28
X.25 Layer 3 action, 38-39
Resend pointer, reset automatically by acknowledgement, 37-30, 39-30, 43-27
Resend window, programming example, 38-46
Reset Nr, emulate-mode action
LAPD,43-28
SDLC, for a specific controller address, 39-31
X.25 Layer 2, 37 - 31
Reset Ns, emulate-mode action
LAPD,43-28
SDLC, for a specific controller address, 39-31
X.25 Layer 2, 37 - 31
Reset Pr and Ps, emulate-mode action, X.25 Layer3,38-41
Resetting the INTERVIEW, from the keyboard,
2-2,4-3
Resolution, display, 1-4
Response addressing, adjunct to send -frame action, X.25 Layer 2, 37 - 24
Response primitives, 34-5
Restart ( or start) timeout, layer-independent action, 31-11
Restart (or start) timer, layer-independent action,
31-11
IndexA-24
Resync, 11-9
field on BERT Setup menu, 11-7, 11-21
in full-duplex BERT, 11-7
may be inappropriate on noisy circuit, 11-9
triggered by a fault, 11-21
not available in half-duplex BERT, 11-9
outsync mode in BERT, 11-8
Retransmitted I -frames, sample program to enhance all, 37 - 33
Return key, 3-6, 33-1
in Easy View, 4-7, 4-16
Rev, subfield on Trigger Setup menu, 26-7
RGB video connector, 1-11, 18-3
RI, available for triggering, 32-5
Right Arrow key, 30-4
RNR
monitor/receive condition
LAPD,43-10
SDLC,39-13
X.25 Layer 2, 37 -12
X.ZS Layer 3,38-16
send action
LAPD,43-20
SDLC,39-23
X.25 Layer 2, 37 - 23
address required for Send RNR, 37 - 23
X25 Layer 3,38-31
ROLL, function key, used to roll through packetlevel "causes", 38-20, 38-36
Roll Back key, 3-9, 30-4, 37-5, 38-8, 39-6,
40-4, 44-4, 46-4, 47-4
in Easy View, 4-14
Roll Fwd key, 3-9, 30-4, 37-5, 38-8, 39-6,
40-4,44-4,46-4,47-4
in Easy View, 4-14
Root directory
Easy View, 4-4
filing system, 15-4
RR
monitor/receive condition
LAPD,43-10
SDLC,39-13
X.25 Layer 2, 37 -12
X.25 Layer 3, 38-16
send action
LAPD,43-20
SDLC,39-23
X.25 Layer 2, 37 - 23
address required for Send RR, 37 - 23
X.25 Layer 3,38-31
SEP '95
Index A: Part I
RS-170video connector, 1-11, 18-3
RS-232
connector, REMOTE, 1-10
optional TIM, 13-1
RS-232N.24, test connector, 1-12
RS-449, optional TIM, 13-1
RS-485, optional TIM, 13-1
RTS
available for triggering, 32-5
field on RS- 232 Interface Control menu, 11-4,
11-6
RTS on/off, Layer 1 Emulate DTE action, 32-12
Rub Out key, 3-7, 30-4
in Easy View, 4-16
Run mode, unit fails to enter, 2-22
s
S, scale, field on Graphical Statistics menu, 22-5,
22-7
SABM
sample program to enhance all occurrences on
trace display, 43-30
send action, X.25 Layer 2, 37 - 23
Sample action
on counter, 21-6
clears current value, 21-7
on timer, 21-6
used to compute percentages, 21-11
Sample counter value, layer-independent action,
31-10
Sample test, force data-packet transmit, 38-45
Sample timer, layer-independent action, 31-11
SAP!
adjunct to monitor/receive-frame condition,
LAPO,43-12
adjunct to send-frame action, LAPD, 43-22
trace column, LAPD, 43-6
SAR header, in ATM
AALl,49-5
AAL 3/4, 49-11
Screen display of data
sixteen data lines in center of, 6-5
three divisions of, 6-5
three lines of softkey functions at bottom of,
6-5
two status lines at top of, 6-5
Screen Saver Timeout, Easy View Setup menu
field, 19-5
Script file
format, 20-20
labels, 20-23, 20-25
master information, 20-21
commands, 20- 23
master title, 20-22
master title date, 20- 22
menu information, 20- 23
menu date, 20-23, 20-24
menu-item information, 20-24
commands, 20-25
help-file pathname, 20-25
item date, 20-24
item description, 20-25
item name, 20-24
sample, 20- 27
SCSI drives, maximum recording times, 7 - 5
SCSI hard drive, recording bit-image data, 2-27
SOLC
diagram of frame fields, 39-9
multi - drop operation
enabled on Frame Level Setup screen, 39-3,
39-5
resend frame, 39-30
resetNr, 39-31
reset Ns, 39-31
SDLC Frame Level Setup screen, 39-2
Secondary (drop) in SOLC, 39-4
identified in ADDR column of trace display,
39-8
SELECT, function key, used to select a rolling
packet-level "cause", 38-20, 38-36
Selectable, CRC mode, 10-14
versus Bisync mode, 10-14
Selections, column on Layer Setup screen, 8-4
Selectric, default BCC parameters, 10-10
SAR trailer, in ATM, AAL 3/4, 49-11
Self tests, 2-1
Save, File Maintenance, menu selection, 15-15
Send frame, Layer 2 action
effect on Frame Sent condition, 37-18, 39-19,
43-17
LAPO,43-20
Save key, 3-6, 15-15
Screen buffer, storage capacity, 1-16
SEP '95
IndexA-25
Index A: Part /
SDLC,39-23
SNA,40-3
X.25,37-22
default parameters, 37 - 22, 37 - 23
Send packet, Layer 3 action
does not send packet directly out on line, 38-24,
38-30
effect on Packet Sent condition, 38-27
X.25,38-29
Send string, Layer 1 action, 37-27, 38-38, 39-27,
43-24
dual-port, 32-17
single-port, 32-9
send_key, keyboard routine, 3-12, 6-23
SEND2, secondary port send - string action used
with dual-port TIMs, 32 -17
Service Indicators (SIO's), SS#7 Layer 3, 47-17
Set (and start) timeout, layer-independent action,
31-12
Set counter value, layer-independent action,
31-10
send action, LAPD, 43- 21
Signal
layer-independent action, advantage over flag
or counter, 31-14
layer-independent condition, 31-8
Signalling Channel Control Part (SCCP), SS#7
Layer 3, 47-19
Signalling Link Selection (SLS), SS#7 Layer 3,
47-6,47-10
Size, trace column
LAPD,43-8
SDLC,39-11
SNA -SDLC, 40-6
X.25 Layer 2. 37-10
X.25 Layer 3, 38-14
SMDS
DXI, recording selections, 48-1
DX! (Data Exchange Interface), 10-9,48-1
SNI, recording selections, Tl data, 48-1
SNI (Subscriber Network Interface), 5-9, 48-1
SMDS Frame Mode, BCC Setup screen, 10-4
Set idle character, Layer 1 action, single-port,
32-13
SNA
fields in protocol trace, 40-8
LV 6.2,40-3
multi-drop operation, enabled on Frame Level
Setup screen, 40-3
sample Line Setup, 5 -18
Set Time, field on Dateffime Setup menu, 17-3
SNNSDLC Frame Level Setup screen, 40-2
SETUP, sample program to enhance all occurrences on trace display, 44-13
SNI, SMDS interface, 48-1
Setup files, saving and loading, 23-5-23-6
Softkey labels, user-defined
in Display Window, 6-24
in Protocol Traces, 6-18
in user traces, 6-26
Set Date, field on Dateffime Setup menu, 17 - 3
Set flag bits, layer-independent action, 31-14
Setup menus
AIM Interface Setup, overview, 2-12
BCC Setup, overview, 2-12
BERf Setup, overview, 2-12
Display Setup screen, overview, 2-11
FEB Setup, overview, 2-12
Interface Control Setup, overview, 2-12
Line Setup, overview, 2-11
overview, 2-11
See also Separate entry under name of each
menu
Record Setup, 7 - 5-7-11
overview, 2-11
SIO
monitor/receive condition, LAPD, 43-10
send action, LAPD, 43 - 21
SIl
monitor/receive condition, LAPD, 43-10
IndexA-26
SNRM, send action, SDLC, 39-23
Source, field on Line Setup menu, 5-5, 7-4
Speed
different speeds forTD and RD, 5-16
field on Line Setup menu, 5-15
optimizing high - speed performance, 2 - 26
frame mode, 2-30
selecting monitor and transmit speeds, 5-15
selecting record speed, 7-8
SRC, source, trace column
LAPD,43-6
Q.931,44-5
SDLC,39-8
SS#7 Layer 2, 46- 5
X.25 Layer 2, 37-7
X.25 Layer 3,38-12
SEP '95
Index A: Part I
SREJ
monitor/receive condition
SDLC,39-13
X.25 Layer 2, 37 -12
send action
SDLC,39-23
X.25 Layer 2, 37 - 23
address required for Send SREJ, 37 - 23
SS#7
Layer 1, 45-3-45-6
compression of data, 45-4
Run-time display, 45-3
setup for testing, 45- 3
SS7 Compression Setup for dual port, 45-4
SS7 Suppression Setup for dual port, 45 - 5
suppression of data, 45-5
Layer 2, 46-3-46-12
frame structure and values, 46-11
Run-time display, 46-3
setup for testing, 46- 3
testing in emulate mode, 46-11
testing in monitor mode, 46-7
Layer 3, 47-3-47-22
ANSI format, 47-4
CCnT format, 47-4, 47-10
Circuit Identifier Code (CIC), 47-6, 47-10
Destination Point Code (DPC), 47 -10
Integrated Services Digital Network (ISDN),
47-22
Message Signal Units (MSU's),47-6
incomplete, 47-7
structure and values, 47-12-47-22
Network Indicator, 47-9
Network Management (NETM) Headers,
47-18
Originating Point Code (OPC), 47 -10
Service Indicators (SIO's), 47-17
setting up, 47-3
Signalling Channel Control Part (SCCP),
47-19
Signalling Link Selection (SLS), 47 -6,47 -10
Telephone User Part (TUP), 47-20-47 - 21
testing in Monitor mode, 47 -7-47 - 22
US standard format, 47-10
sample Line Setup, 5-18
Start At Block, subfield on Disk Maintenance
menu, 14-10
Start timeout, layer-independent action, 31-11
Start timer, layer-independent action, 31-11
Start up screen, 2 - 2
Start-stop, data setup, 5-15
SEP '95
Start -stop bit, voltage not affected by inverted
polarity, 5 -17
START/INCL, field on BCC Setup menu, 10-11
Startilncl, field on BCe Setup menu, 10-12
START/N/INCL, field on Bee Setup menu,
10-12,10-15
Start/N/Incl, field on BCC Setup menu, 10-13
startJcrd"play, record routine, 16-6
States
introduction to concept, 24-3
Protocol Spreadsheet, programming block, 28-8
comments in, 28-14
traced along with layers and tests on Program
Trace, 6-20
Statistics
BERT display, accessing the results, 11-19
graphics display
accessing via sofikey, 22-3
printing, 16-15
identification of counters and timers, 21-4
postponed until after run, 21-6
tabular display
accessing via saftkey, 22-3
can scroll through 100 counters, timers, and
accumulators, 21-5
printing, 16-15
tabular menu
cursor movement, 21-4
two cursors, 21-4
Statistics menus, overview, 2-14
Statistics Type, field on Display Setup menu, 22-3
Stats, statistical softkey, linked to Statistics Type
field in Display Setup menu, 22 - 3
Status lines
division of Run-mode screen, 6-5
record/playback field, 5 - 6, 7 -10
in BERT, 11-18
Stop At, field on Record Setup menu, 7-10
Stop Bits
field on Line Setup menu, 25-6, 32-4
subfield on Line Setup menu, 5-15
Stop timeout, layer-independent action, 31-11
Strike-through's, Protocol Spreadsheet, 2-22
String
adjunct to send-frame action
LAPD,43-24
SDLC,39-27
X.25 Layer 2, 37 - 27
IndexA-27
Index A: Part I
adjunct to send-packet action, X.25 Layer 3,
38-33,38-38
relation of string entry in Call Request to
DATA field on Packet Level Setup screen,
38-33
Layer 1 send action, 37-27,38-38,39-27,
43-24
location of IL buffer, 34-6
monitor/receive condition
always in quotation marks on Protocol Spreadsheet, 32-3
Layer 1, 32-3, 32-4
monitored or received, size limit, 32 - 3
referenced in IL buffer, 34-6
send action
always in quotation marks on Protocol Spreadsheet, 32-10, 32-18
no practical size limit, 32-9, 32-18
valid characters, 32-9, 32-18
send2 action, always in quotation marks on Protocol Spreadsheet, 32-18
to be passed down with data primitive, 34-6
Strings on Protocol Spreadsheet, 33-1
Strip, field on BCC Setup menu, 10-13
STX, field on BCC Setup menu, 10-12
Summary of, subfield on Disk Maintenance menu,
14-7
Suppress, field on Display Setup menu, 6-10,
6-13
Suppress not equal, logical equivalent of "display
only", 6-11
Suppress selected trace rows
LAPD action, 43-29, 43-30
Q.931 action, 44-12, 44-13
SDLC action, 39-32, 39- 33
SNA action, 40-3
SS#7 Layer 2 action, 46-10, 46-11
SS#7 Layer 3 action, 47-11,47-12
X.25 Layer 2 action, 37-32, 37-33
X.25 Layer 3 action, 38-42, 38-43
Sync
block checking in ATM Frame Mode, 10-9
block checking in SMDS Frame Mode, 10-9
Sync Char
field on Line Setup menu, 3-6, 11-9
subfield on Line Setup menu, 5-8, 5-9
Sync characters
in half-duplex BERT, 11-7
must be included in transmit string, 33-3
IndexA-28
Sync Pattern
field on BERT Setup menu, 3-6, 11-8, 11-9
not applicable in pseudorandom full-duplex
test, 11-10
used for pattern sync in half-duplex pseudorandom test, 11-11
versus Sync Chars on Line Setup menu, 11-9
in fox or user-defined test, 11-9
Sync symbol, special symbol on data display, 5-8
Synchronization
accidental synching, 5 -13
continuous search for sync (autosync), 5-13
default patterns for standard codes, 5-8
entering a one-character pattern, 5-9
in - sync status message in BERT, 11-21
searched for following Outsync action, 32-13
when receivers do not search for sync, 5 -13
Synchronization point, in half-duplex pseudorandom BERT, 11-11
Syntax errors, Protocol Spreadsheet, 2-18
Isys/ezview_setup, 2-3
IsyS/fiftLhertz, file name, 1-9
!sys!print_setup, loaded during boot-up, 2-3,
16-7
System disk, boot-up, 8-3
T
T, type, field on Graphical Statistics menu, 22-5
Tl
field on LAPD Frame Level Setup screen, 43- 3
field on X.25 Frame Level Setup screen, 37 - 3
optional TIM, 13-1
record setup, 7-8
Tl expired, emulate-mode condition
LAPD, 43-4, 43-16
X.25 Layer 2, 37-4, 37-18
Tl timeout
conditions under which timer expires, 37-4,
43-4
maximum and minimum values, 37-4, 43-4
TEl
adjunct to monitor/receive-frame condition,
LAPD,43-12
adjunct to send-frame action, LAPD, 43- 22
trace column, LAPD, 43-8
Telephone User Part (TUP), SS#7 Layer 3,
47-20--47-21
Temperature, operating, 1-17
SEP '95
Index A: Part I
Test, field on Display Setup menu, 6-20, 31-19
Test connectors
software control, 1-14
Test Interface Module, back panel, 1-12-1-20
TO DCE, 1-12
TODTE,1-12
Test Interface Module
installation, 1-19, 12-1
LED overlay, 1-6
installation, 1-19, 12-1
LED's, back panel, 1-15
software control, 1-14
test connectors, 1-12-1-20
Test Length, field on BERT Setup menu, 11-14
Test Seconds, BERT counter, 11-20
Tests
identified on Program Trace, 6-20
Protocol Spreadsheet, programming block, 28-8
comments in, 28-14
simultaneous, program design, 24-3-24-4
Tick Rate, field on Front-End Buffer Setup menu,
9-7,22-7
Tick rate, 9-6
RDbits, 9-6
should agree with time "Unit" on Statistics
screen, 9-6
TDbits, 9-6
TIM. See Test Interface Module
Time, trace column
LAPD,43-8
Q.931,44-8
SDLC,39-11
SNA-SDLC,4O-6
SS#7 Layer 2, 46-6
SS#7 Layer 3, 47-6
values may be wall time, ticks, or recorded ticks,
37-10,38-14,39-11,40-6,43-8,44-8,
46-6,47-6
X.25 Layer 2, 37 -10
X.25 Layer 3, 38-14
Time of day, layer-independent condition, 31-6
Time Ticks, field on Front-End Buffer Setup
screen, 9-6,31-10,38-14,39-11,40-6,
43-8,44-8,46-6,47-6
Time ticks
effect on capacity of character buffer, 6-27
enabled/disabled on FEB Setup screen, 9- 3
encodable in bit - image or character data, 9-3
gives most accurate timer readings, 31-10
SEP '95
playback, 2 - 20
of bit-image data, 2-20,9-6
of character data, 2-20, 9-6
storage of, 1-16
versus wall-clock timing measurements, 9-8
Time-of-day clock. See Dateffime Setup
TimeIDate Setup, overview, 2-15
Timeout
condition, 'lligger Setup menus, 25-9
field on Trigger Setup menu, 26-8
layer-independent action, 31-11
layer-independent condition, 31-4
maximum value, 31-12
program to increase maximum value, 31-12
restart (or start), 31-11
shared between spreadsheet and Trigger Setup
menus, 31-11
Timeout expired, SDLC condition, 39-4
Timer
accumulated, 31-15
identification postponed until after run, 21-6
identified by name on statistics screen, 21-4
layer-independent action, 31-10
printing line of tabular statistics for, 31-16
Timers, no values displayed, 2 - 23
Timestamp Resolution, field on Front-End Buffer
Setup screen, 9-8
TO DCE, test connector, 1-12
To Disk Number, subfield on Disk Maintenance
menu, 14-11
TO DTE, test connector, 1-12
Total, Summary subfields on Disk Maintenance
menu, 14-9
Trace
as component of custom protocol analysis, 6-21
as debugging tool, 6-20
compared to prompt, 6-20
layer-independent action, 31-18
layer-independent spreadsheet action, 6-20
versus prompt, 31-18
Trace buffer, correlation with character data, 6- 27
Trace display
LAPD,43-5
Q.931,44-3
SDLC,39-6
SNA-SDLC,4O-4
X.25 Layer 2, 37 - 5, 46-3
X.25 Layer 3, 38-8, 47-4
Transitional condition, 31-2, 31-6, 32-1, 32-6
IndexA-29
Index A: Part I
Transitional/status condition, 31-2, 32-1, 32-5
Transmit complete, Layer 1 condition, 32-6
Transmit string
complete version entered only at Layer 1, 33-3
does not appear on display, 2-23
triLflag, name of flag mask on Trigger Setup menus, 25-11, 26-6,31-7
trig_timeout_l, name of timeout on Trigger Setup
menus, 26-8
triLtimeout_2, name of timeout on Trigger Setup
menus, 26-8
Trigger, condition-action grouping on Protocol
Spreadsheet, 31-1
Trigger conditions, EIA, fails to come true, 2-22
Trigger freeze. See Capture data to screen (on/off)
Trigger Setup, variables shared with Protocol
Spreadsheet, 23 - 5
overheating, 1-10,2-24
power-up, warning message, 2-24
Program key, unit unexpectedly enters Run
mode, 2-22
Protocol Spreadsheet, unexplained strikethrough's, 2-22
Run mode, unit fails to enter, 2-22
timers, no values displayed, 2-23
transmit string, does not appear on screen, 2 - 23
trigger conditions, EIA, fails to come true, 2-22
Troubleshooting
application program won't compile, 2-26
application program won't run, 2-26
unit running slow, 2-25, 2-26
TTL, optional TIM, 13-1
TYPE, trace column
LAPD,43-8
SDLC,39-8
X.25 Layer 2, 37-7
X.25 Layer 3,38-12
Trigger Setup menus, 25 - 3
Actions, 26-3-26-12
basic description of capabilities, 23-2
Conditions
Buffer Full, 25-11
combined with other Conditions, 25-4
combining static and instantaneous, 25-4
Counter, 25-11
combined with other Conditions, 25-4
EIA,25-9
combined with other Conditions, 25-4
Flags, 25-10
combined with other Conditions, 25-4
Keyboard, 25 -12
Receiver, 25-5
Timeout, 25-9
Xmit Complete, 25-10
menu selections
(Actions),2
(Conditions), 2
overview, 2-12
transmit string, does not appear on screen, 2-23
Type
field on BCC Setup menu, 10-12
field on Disk Maintenance menu, 7-4
field on Display Setup menu, 6-7
primitives, 34-4
subfield on Disk Maintenance menu, 14-10
Trigger Summary screen, 27 - 3
Unit of time
selection for printout of timer line, 31-17
selection on a statistics screen, 9-7
Triggers
active, 25-4
control of color display, 18-5-18-6
Troub1e - shooting
data plus leads, failure of leads to transition,
2-23
data-plus-leads display, failure of leads to
transition, 2 - 23
layers, passing data between, 2 - 23
IndexA-30
u
U, unit, field on Graphical Statistics menu, 22-7
UIA
LED,I-15
X.21 input jacks, monitored for on/off status,
36-7
UA, send action
SDLC,39-23
X.25 Layer 2, 37-23
Undelete, editor command, 30-8
Unit, column on Tabular Statistics screen, 21-6
Unknown frame, receive condition
LAPD,43-16
SDLC,39-17
X.25 Layer 2, 37-17
Unknown packet, receive condition, X.25 Layer 3,
38-26
Unmarking text, in Easy View text files, 4-17
SEP '95
Index A: Part I
Unresolved reference, error message, 2-22
Up Arrow key, 30-4
Used, Summary subfields on Disk Maintenance
menu, 14-8
User disk, personality packages reside on, 8- 3
User trace
#pragma tracebuf, 6- 25
buffer size may be increased, 6- 2S
display mode, 6-25-6- 27
softkey labels under programmer's control, 6-26
User- assigned BERT pattern, 11-7
lusr directory, filing system, 15-6
lusrldefault
affect on Start Up screen, 2 - 3
boot-up menu configuration, 2-6
default program, 2-6
lusr/user)ntrf
affect on Start Up screen, 2 - 3
creating a user interface, 2-4
Utilities menus, overview, 2-15
See also Separate entry under name of each
menu
v
V, value, field on Graphical Statistics menu, 22-6
V.35, optional TIM, 13-1
Verify Passes, subfield on Disk Maintenance menu,
14-7
Video, ATM transmission, 49- 2
Video connectors
CRT/RGB, 1-11
RS -170 composite video, 1-11
View, File Maintenance, menu selection, 15 - 20
Layer 1 condition, 32-3
Wall clock
accurate to one millisecond, 9-8
controls timers when time ticks are disabled,
31-10
enabled when time ticks are disabled, 9-8
Warning message, during power-up, 2-24
Winchester hard disk
installing new system software, 2-7
storage capacity, 1-16
Window
cleared by Reset Ns action, 37-31,39-31,
43-28
defined, 37-28,38-39,39-28,43-26
empty, emulate -mode condition, 37 -18,
38-27,39-19,43-17
full
effect on Send action, 37-23, 38-31,39-23,
43-20
emulate-mode condition, 37-18, 38-27,
39-19,43-17
not empty, emulate-mode condition, 37 -18,
38-27,39-19,43-17
not fulL, emulate-mode condition, 37-18,
38-27,39-19,43-17
Window Size
field on LAPD Frame Level Setup screen, 43- 3
field on SDLC Frame Level Setup screen, 39-3
field on SNAlSDLC Frame Level Setup screen,
40-3
field on X.25 Frame Level Setup screen, 37 - 3
field on X.25 Packet Level Setup screen, 38- 3
Window size, 37-5, 38-4, 39-5,43-5
Write, editor command, 15-7,30-6
formatted, 30-6
unformatted, 30-7
Write Enable, File Maintenance, menu selection,
15-21
Voice, ATM transmission, 49- 2
Write Protect, File Maintenance, menu selection,
15-21
Voltage selection, back panel, 1-8
Write protection, microfloppies, 1-6
w
Wait for End Of Frame
condition dependent on Rev Blk Chk: ON, 10-5
subfield on Trigger Setup menu, 10-5,25-9
Wait for EOF (end of frame)
adjunct to String or One-of condition, Layer 1,
32-5
SEP '95
x
X.200, CCITT recommendation, 24-5
X.21
call-setup phase, 36-4
changing idle character during transmission,
36-8
clamping/unclamping data leads, 36-9
IndexA-31
Index A: Part I
invoking, 36-10
plus, bell and sync idle, 36-9
send action, 36-8
code and format, 36-8
data -transfer phase, 36-4
invoking, 36-11
send action, 36-7
Layer 1 package, 36-3
leads
controlling C and I, 36-10
monitoring C and I for true or valid status,
36-6
monitoring T and R for valid status, 36-5
optional TIM, 13-1
sending from Layer 2, 36-5, 36-11
user program to convert protocol headers to hexadecimal,37-35
user program to force data packets containing
fox messages out onto the line from Layer 3,
38-45
user program to make Layer 2 "automatic" for
higher layer, 37 - 36
X.25 Frame Level Setup screen, 37 - 2
X.25 Packet Level Setup screen, 38-2, 38-32
Xmit Complete
condition, Trigger Setup menus, 25 -10
Layer 1 condition, 32-6
X.21 bis, lead conversions, 36-4
Xmit Idle Char
field on tine Setup menu, 3-6
subfield on Line Setup menu, 5 -14
X.25
diagram of frame fields, 37-8
diagram of packet fields, 38-10
sample Line Setup, 5-18
XS-3
default BCC parameters, 10-10
default sync pattern, 5-8
SY characters inappropriate for, 5-8
IndexA-32
SEP '95
ADDENDUM
985-80682-01
INTERVIEW® 8000 Series
ATM Technical Manual
-
Asynchronous Transfer Mode (Broadband)
INTERVIEW 8800 PLUS ATM
and
INTERVIEW 8750 ATM EXPRESS
Issue 1, September 1995
GENERAL SIGNAL
Networks
13000 Midlantic Drive
Mount Laurel, New Jersey 08054
Telephone: (609) 234-7900
FAX: {609} n8-8700
Internet: http:/twww.telenex.com
ADDENDUM
©
1995 General Signal Networks
ADDENDUM
985-80736-01
Notice
This is Issue 1 with Errata of the INTERVIEWID 8000 Series ATM Technical Manua~ Asynchronous
Transfer Mode (Broadband), September 1995. (98S-B0682-01). The Errata adds information
about both Class I and Class IIIb single -mode transmit lasers on the AIM - 302-1.
I
The first addendum (November, 1995), 985-B0736-01, to Issue 1 is also incorporated in this
manual. The addendum updates information on the on -line Broadband ATM application
programs in the units and on the Internal Loopback mode.
This technical manual is written to specifications for the INTERVIEW 8800 PLUS ATM unit and
the INTERVIEW 8750 ATM EXPRESS unit with software revision 12.00. Refer to the "ATM
Hardware" section of this manual for specific model descriptions. In most instances, further
software revisions will be accompanied by an addendum to this issue. In cases where new software
does not affect the accuracy of the manual, however, an addendum may not be produced.
Additional technical manuals provided with INTERVIEW 8000 Series ATM units are Volume I
(951-00424-01) and Volume II (951- B0427 -01) of the INTERVIEfV'SlBOOO Series Technical
Manual, June 1994.
Note that the use of DANGER and WARNING in this manual relates to harm which may occur to
the operator or to obseIVers, so extreme care must be taken to heed these warnings. CAUTION is used
to guard against damage which may occur to the unit if proper procedures are not used.
General Signal Networks is a newly formed company by the merger of Telenex, Data Switch, and
Tau-Tron. Telenex Corporation is now General Signal Networks - Mount Laurel; we retain the
same personnel and high standards which have always been hallmarks of Telenex Corporation and
AR Test Systems.
General Signal Networks - Mount Laurel reseIVes the right to improve this manual or the
equipment it describes without prior notice. Any references to upgraded equipment, options,
accessories, and software packages made in the manuals may not apply to your present unit.
Contact Customer Service for information on such upgrades or other purchases.
Any duplication of the material in this manual in any form without written permission from General
•
•
I
Signal Networks - Mount Laurel is strictly forbidden.
For technical information, programming assistance, error decoding, and repairs, contact the factory.
General Signal Networks - Mount Laurel is located in Mount Laurel, New Jersey, approximately
15 miles east of Philadelphia, PA. Local customers should call (609) 234-7900; in the northeastern
United States, call (800) 222-5482; and in the rest of the U.s., call (800) 222-0187. Access us on the
Internet at http://www.telenex.com.
Address questions and comments about this manual and other technical publications to the
Technical Writing Department on extension 3548 at these same telephone numbers.
NOV'95
iii
ADDENDUM
NOV'95
Contents
1
ATM Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
1-1
1.1
1.2
1.3
1.4
1.5
1-1
1-6
1-9
1-13
1-18
1-21
1-23
1.6
1.7
2
IN1ERVIEW 8800 PLUS ATM Model ......................................
2-1
2.1
Physical Dimensions ...... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
ATM (Broadband) Testing .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
WAN Protocol Testing.. . .... . . .. . .................... . ............
Power Up : . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Recording WAN Data While Thsting ATM Data. . . . . . . . . . . . . . . . . . . . . . ..
Testing ATM (Broadband) Data .....................................
Upgrading to an INTERVIEW 8800 PLUS ATM . . . . . . . . . . . . . . . . . . . . . ..
2-3
INTERVIEW 8750 ATM EXPRESS Model ..................................
3-1
3.1
3.2
3.3
3.4
Physical Dimensions. .. .. . . . .. . . . . . ... ..... .. ..... .. . . ... .. .. . ... ..
Power Up .............. ;.........................................
Using the INTERVIEW 8750 ATM EXPRESS ........................
Testing ATM (Broadband) Data .....................................
3-1
3-1
3-2
3-4
ATM (Broadband) Operating Modes ........................................
4-1
4.1
4.2
4.3
4.4
4.5
Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Emulate A Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Internal Loopback A Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Emulate B Mode ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Internal Loopback B Mode .........................................
4-1
4-2
4-3
4-3
4-3
ATM Hardware ..........................................................
5-3
2.2
2.3
2.4
2.5
2.6
2.7
3
4
5
5.1
5.2
5.3
5.4
5.5
SEP'95
Overview..... ........ .. . .... .... ...... .... ............... .......
A'fM Header .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
AAI.. 1 Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
AAI.. 3/4 Protocol .................................................
AAI.. 5 Protocol .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Operations and Maintenance (OAM) Cells.... .. .... ... . . .. . .. .. . .....
ATM Mapping: DS3 Format for PLCP Mapping. . . . . . . . . . . . . . . . . . . . . ..
ATM Cell Enginet (ACE) ................... '. . . . . . . . . . . . . . . . . . . . . ..
Metallic Interfaces - Overview .....................................
Optical Interfaces - Overview ......................................
ATM Interface Modules (AIMs) and Accessories ..... '" .. " . .... ......
Installation of ATM Interface Modules (AIMs) ........................
2-3
2-7
2-8
2-9
2-9
2-11
5-3
5-5
5-6
5-6
5-11
v
6
Cabling the INTERVIEW ATM Models .....................................
6.1
6.2
6.3
6.4
6.5
6.6
6.7
6.8
6.9
6.10
6.11
6.12
7
8
7-1
7.1
7.2
7.3
7.4
7.5
7.6
Testing ATM without Concurrent WAN Protocols ......................
Testing WAN Protocols Concurrently with ATM. . . . . . . . . . . . . . . . . . . . . . ..
Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Monitor Mode.. . ... . . . ... .. . . . . . . . . ... .. . . . . . . . . .. . . . .... . . .. . . ..
Emulate A and Internal Loop A Modes. . . . . . . . . .. . . . . . .. . . . . . . . . . . . ..
Emulate B and Internal Loop B Modes......... .. .. ... ....... ........
7-2
7-2
7-2
ATM Interface Setup - AIM-305-1 ......... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8-1
9.2
9.3
9.4
9.5
9.6
7-3
7-5
7-11
Testing ATM without Concurrent WAN Protocols ...................... 8-2
Testing WAN Protocols Concurrently with ATM. . . . . . . . . . . . . . . . . . . . . . .. 8-2
Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Monitor Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 8-3
Emulate A and Internal Loop A Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. 8-5
ATM Interface Setup - AlM-306-1 ................ . . . . . . . . . . . . . . .. . .. .. . . ..
9.1
vi
6-1
6-3
6-4
6-5
6-14
6-14
6-14
6-16
6-20
6-26
6-34
6-38
ATMInterfaceSetup-AIM-302-1 .........................................
8.1
8.2
8.3
8.4
8.5
9
ATM Interface Modules (AIM) .....................................
Fiber Optic Cables and Accessories Care and Precautions ...............
Fiber Optic Cables and Accessories Cleaning ..........................
Cables, Splitters, Connector Adaptors, and Attenuators .................
Sensitivity of the Single-Mode Fiber Optical Signal .....................
Type of Connectors on the Premises .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Coaxial Cabling Diagram for Monitoring ..... '" .. . ............. ......
Coaxial Cabling Diagrams for Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Single-Mode Fiber Optic Cabling Diagrams for Monitoring. . . . . . . . . . . . ..
Single-Mode Fiber Optic Cabling Diagrams for Emulation. . . . . . . . . . . . . . .
Multi-Mode Fiber Optic Cabling Diagrams for Monitoring ..............
Multi-Mode Fiber Optic Cabling Diagrams for Emulation ...............
6-1
Testing ATM without Concurrent WAN Protocols ......................
Testing WAN Protocols Concurrently with ATM. . . . . . . . . . . . . . . . . . . . . . ..
Mode...........................................................
Monitor Mode...... . . ............. . . .. .. . .... .. . ........ . ........
Emulate A and Internal Loop A Modes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Emulate B and Internal Loop B Modes. . ... . . . . . . . . . .. . . . . .. . . . .. .. ..
9-1
9-2
9-2
9-2
9-3
9-5
9-11
SEP '95
10
ATM Physical Statistics ............................. '" . . . .. ......... . . . . ..
10-1
Softkey Racks .•....•••...............•...•.............••..•.....
DS-3 Framing - 53-Octet Direct ....................................
DS-3 Framing - 57-Octet PLCP ....................................
E3 Framing - 53-Octet Direct ................ . . .. . .. . .. .. . . . . . . . . ..
E3 Framing - 57-Octet PLCP ......................................
STS-l Framing ........... " .. . .. .. . . . ....... . ... . .. ... . .... ... . . ..
Fiber Optical Connectors and Signals. . . . . . . . . . . . . . . . .. . . . . .. . .. .. . . ..
10-2
10-3
Error Injection for Physical Statistics ........................................
11-1
11.1
11.2
11.3
11.4
11-2
11-2
11-5
11-6
10.1
10.2
10.3
10.4
10.5
10.6
10.7
11
MODE. .. . . .. . ....... . . . . .. . . .. . . .. ....... .. . . ... ..... .... ......
EVENT ...................... , .............. ............... .....
RAm ........ , ..... " . . . . . . . . . . . ... . ... ... .. .. . .. ..... . ... . . .. ..
COND. .................... .. . . . . . ............. .................
10-6
10-10
10-13
10-16
10-20
Appendix A ATM Glossary and Acronyms ........................................
A-I
Appendix B ATM Unit Specifications ............................................
B-1
B.l
B.2
B.3
B.4
to
Upgrading ATM (Broadband) Testing . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
Interior Components of PLUS ATM .................................
Interior Components of ATM EXPRESS .............................
ATM MPM Boards .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ..
B-3
B-5
B-7
B-8
List of Tables
Table 1-1
Pre-defined Header Field Values . . . . . . . . . . . . .. .. . . . . . . . . . . . . .. . . . . . . ..
1-8
Table 1-2
Payload Type Indicator Encoding . . .. ... ........... ... .. ...... ....... ..
1-8
Table 1-3
Cycle/Stuff Counter Definition. .. . .. . .. . . . . .. .. . . . . . . . . . .. .. . . . . .. . . ..
1-25
Table 1-4
Path Overhead Identifier Coding. . . . .. . . . . . . . .. . .. . . . .. . .. . . . . . . . . . . ..
1-26
Table 5-1
ATM Interface Accessory Kits ........................................
5-10
Table B-1
Sl-Switch Settings for MPM Boards in the INTERVIEW ATM Models .....
B-8
SEP '95
vii
------.-....
-~------
viii
SEP '95
1 ATM Overview
1 ATM Overview
The INTERVIEW 8800 PLUS ATM and INTERVIEW 8750 ATM EXPRESS units have been
designed especially for ATM broadband testing. Special hardware has been added to a standard
INTERVIEW 8800 TURBO unit to create the 8800 PLUS ATM model.
•
The INTERVIEW 8800 PLUS ATM can decode WAN protocols (serial data) simultaneously
while decoding cell-based protocols at the ATM interfaces.
•
The INTERVIEW 8750 ATM EXPRESS unit has the same full ATM interface capabilities, but
not the WAN-protocol decoding processes.
•
Early INTERVIEW 8000 TURBO Series units may become a fuU-fledged INTERVIEW 8800
PLUS ATM unit through a series of upgrade steps; contact Customer Service for more
information.
The INTERVIEW 8800 TURBO units support applications for monitoring and emulation in ATM
(Asynchronous Transfer Mode) for TIlE1 with no additional hardware required. ATM for Tl is
defined in the ATM Forum DS! ATM UNI (V1.0) Specification and the ITU Documentation 1.432
and G.804. ATM is based on 53-byte cells; the INTERVIEW decodes it using either a PLCP
(Physical Layer Convergence Protocol) to map cells onto the Tl framed data streams (via 576-byte
superframe) or the standard ATM HEC (Header Error Control) framing.
1.1
Overview
Asynchronous Transfer Mode (ATM) is a technology that offers the "bandwidth on
demand" features of packet-switching with the high speeds required for LAN and WAN
networks today. This cell-relay technology operates independently of the type of
transmission being generated at the upper level and of the type and speed of the physical
layer medium being used. This allows sending of virtually any type of transmission (e.g.,
voice, data, video) in a single integrated data stream operating over any medium ranging
from existing Tl!Ellines to SONET OC-3 at speeds of 1.5 to 155 Mbps - and faster.
The technology permits both public (i.e., RBOC, PIT, or local carrier) and private (i.e.,
LAN or LAN-to-internal switch) ATM networks. This capability gives a seamless and
transparent (to the user) connection from one end user to another, whether in the same
building or across two continents.
1-1
SEP '95
---------------_. --_._------_ .._-_.
----
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(A) 051 Layer Similarity
At the end user site, ATM operates with a layered structure similar to the aS!
7-layered model. However, as Figure 1-1 shows, ATM only addresses the lower two
layers of this model:
•
Layer 1 - Physical Medium
•
Layer 2 - Data Link
All other layers are only part of theencapsu!ated information portion of the cell,
which is passed transparently through the ATM network.
APPLICATION LAYER
USER LAYERS
:,
CONVERGENCE SUBLAYER
---ATM ADAPTATION LAYER--SEGMENTATION AND REASSEMBLY SUBLAYER
Comparable to
Physical Medium
and
Data Link
layers of OSI model
ATM LAYER
>
TRANSMISSION CONVERGENCE SUBLAYER
- - -- --- ·PHYSICAL LAYER· --- -- - PHYSICAL LAYER MEDIUM DEPENDENT SUBLAYER
J
Figure 1·1 At the end user site, ATM addresses the lower two layers of the OSI seven-layer model.
1-2
SEP '95
1 ArM OveNiew
These two OSI layers are handled by three layers for ATM:
•
Physical Layer - This layer defines the medium for transmission, any
medium~dependent parameters (e.g., the Quality of Service requirements), and
the framing used to find the data contained within the medium. It is divided into
two sublayers: the Transmission Convergence Sublayer and the Physical Layer
Medium Dependent Sublayer.
•
ATM Layer - This layer provides the basic 53-byte cell format and defines the
cell header content.
•
AIM Adaptation Layer (AAL) - This layer adapts the higher-level data into
formats compatible with the Al'M Layer requirements. It is dependent on the
type of service(s) being transported by the higher layer. It is divided into two
sublayers: the Convergence Sublayer and the Segmentation and Reassembly
Sublayer.
When the end user sends traffic over the ATM network, the higher-level data unit is
passed down to the AAL Layer, which prepares the data for the ATM Layer as
appropriate for the AAL protocol being used. This can include padding the data unit
to a fixed length, adding headers and/or trailers for error checking and higher-level
routing, and segmentation-with or without additional information added to the
subunits. (Note that the AAL is also responsible for reassembly of the data unit when
passing the data back up to the higher-level.)
.
The prepared data unit or segment is then passed down to the ATM Layer, which
affixes a necessary 5-byte ATM header to the segment. This 53-byte ATM cell is then
passed down to the Physical Layer for transmission (HEC framing) or packaging into
a Physical Layer Convergence Protocol superframe (PLCP framing).
The ATM Network is illustrated in Figure 1·2.
SEP'95
1-3
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
AAL - ATM Adaptation Layer
ATM - ATM Layer
PHY - Physical Layer
UNI - User Network lnteiface
NNI - Network Node lnteiface
-Different AAL protocols are usedfor different traffic types: data, voice, videoFIgUre 1·2 Typical ATM Network Illustration.
(8) ATM Physical Layer
The Physical layer puts the information on to a physical medium. The Physical Layer
is divided into two categories: the Physical Medium Dependent Sublayer (PMD) and
the Transmission Convergence Sublayer (TC).
1.
14
Transmission Convergence Sublayer. The TC sublayer performs several functions.
•
Packages ATM cells into transmission frames
•
Generates and receives those frames and their overhead bits
•
Calculates error control information and inserts it into the HEC in the ATM
cell header
•
Checks received HEC information
•
Discards the incoming cell if the first four bytes are neither error-free nor
correctable
•
Scrambles the 48 bytes in the Payload field for certain media, ensuring that
this field is not identical to the HEC pattern to suppress false syncing.
SEP '95
1 ArM Overview
2. Physical Medium Dependent Sublayer.
The PMO sublayer covers information transfer between nodes and handles
timing recovery, line encoding formats, electro-optical conversions, and such.
•
•
Inserts and extracts cells from the Layer medium
Multiplexes cell groups, inserting empty cells if necessary to meet Layer 1
rate requirements
(C) ATM Layer
In s~ple terms, the ATM Layer takes 48 bytes of information and segments it into
the payload of a single cell; to this cell is added a 5-byte header which contains proper
information for routing the payload to its correct destination. The 53-byte ATM cell
is then passed through the network at a very high rate of speed; the end devices
segment and reassemble the information in the cell to preserve its integrity.
The 48-byte ATM payload is user information, but it can be filled with more than
user data. Up to 4 bytes can be used for the adaptation process itself or padding.
The AAL is responsible for formatting user data into this field.
(0) ATM Header
The 5~byte ATM header is added to the 48-byte payload in the ATM Layer. It
consists of several parts. as shown in Fi~ure 1-3 and explained in Section 1.2.
(E) ATM Media
ATM is media-independent, so the media type is governed only by the limitations of
the physical transport.
1. Physical Layer Rates and Uses. Currently, four types of physical media are
defined:
Physical Megia
I!bxsi~w In~rfl!c~
Bit Rate
N~twork .u:~
Standard Twisted Pair (STP) or Fiber
TBA*
lOOMbps
Private Network
62.51125 Micron Multimode Fiber
TBA**
155.52 Mbps
Private Network
62.5/125 Micron Multimode Fiber
OC3
155.52 Mbps
Public Network
Coaxial Cable or Fiber
DS-3
E3
44.736Mbps
34.368 Mbps
51.840Mbps
Public Network
STS-J
* 100 Mbps facilities use 4B/5B Encoding
** 155.52 Mbps facilities use 8B/IOB Encoding
2.
SEP '95
SONET or SDH Interface Rates. ATM cells fit into SONET or SOH frames as
part of the SPE (Synchronous Payload Envelope) to which is added the Path
Overhead and Transport Overhead to make up the SONET or SOH frame.
1-5
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(F) AAl Protocols
Four AAL protocols have been defined for use in ATM networks. These protocols
loosely correspond to specific data classes, but are not necessarily exclusive to that
data type:
•
AAL 0 - Not a defined AAL protocol, simply refers to raw cells with full control
over all bits in the payload
•
AAL 1 - Constant bit rate, connection-oriented, synchronous traffic (e.g.,
uncompressed voice)
•
AAL 2 - Variable bit rate, connection-oriented, synchronous traffic (e.g.,
compressed video); not in common use
•
AAL 3/4 - Variable bit rate, connection-oriented, asynchronous traffic (e.g.,
X.2S data) or connectionless packet data (e.g., SMDS) with additional
information on segmentation and cell order
•
AAL 5 - Variable bit rate, connection-oriented, asynchronous traffic (e.g., X.25
data) or connectionless packet data (e.g., LAN traffic) with a simplified
information scheme for resegmentation
Examples of data flow for the commonly used AAL 1, AAL 3/4, and AAL 5 protocols
are given in Sections 1.3, 1.4, and 1.5, respectively.
1.2
ATM Header
The 5-byte ATM header is added to the 48-byte payload in the ATM Layer. It consists of
several parts. The User Network Interface (UNI) requires a 4-bit Generic Flow Control
element that the Network-Node Interface (NNI) doesn't require. See the illustration in
Figure 1-3.
(1bitJ
~~~~~~--~----~~~~----~f_b_j_m~~~--~@~b=ft_S)---r------g8b~~~~-
~__~--~~--~__~----__--~____~-P-T-I~~~I----H-E-C---+I-----~~~~d~-_
~--------------------------~~~-----------------------------~----
-- ~
____
~____~_~_~~______~_P_T_I~~~I__H_E_C_~I-----~-(1 bit)
~--~~~----~------~~~----~r~b~i~~~I~~~~b~ft~S)~~--
g8b~?~--
~-------------------(=5~~~eS~)----------------------~
------- ~
Figure 1-3 Comparison of UNI Header and NNI Header
1-6
SEP '95
1 ATM OvelView
GFC -
Generic Flow Control (4 bits, UNI only)
Not fully defined as yet, defaults to all zeros. May be used in proprietary flow
control schemes now.
VPI
Virtual Path Identifier (8 bits UNI, 12 bits NNI)
With VCI, used for ATM addressing. Used to deliver "bulk" circuit transport
across networks with local. management of VCls.
-
VCI -
Virtual Circuit Identifier (16 bits)
With VPI, used for ATM addressing.
PTI
Payload Type (3 bits)
Payload Type Indicator (PTI) encoding values are given in Table 1-2.
-
CLP -
Cell-Loss Priority (1 bit)
Reports priority of cells for discarding:
o-keep this cell
1 - this cell can be discarded
Can be set by user to indicate priority. Some networks can "tag" cells at entry if
they exceed the subscribed traffic measures.
HEC -
Header Error Control (8 bits)
Error correcting code to detect multiple header errors and to correct single bit
errors. Used to avoid misdelivery of cells due to corruption of the header. Does
not detect payload errors. Also used for identifying cell boundaries (see footnote
in Table 1-2 regarding PTI encoding).
A listing of pre-defined header field values is found in Thble 1-1.
The User Network Interface (UNI) defines signaling protocols (ITU-T standards) for
point-to-point and point-to-multipoint call setup and management over SVCs (Switched
Virtual Circuits). SVCs are dynamic network connections set up only for the duration of a
call, paving the way for delivery of services such as video-on-demand.
The Network-Node Interface (NNI) defines the protocols between private ATM networks. Work
is in progr~ss on an implementation agreement, which is expected to be published in 1995.
SEP '95
INTERVIEW 8000 Series -ATM (Broadband): 985-80682-01
Table 1-1
Pre-defined Header Field Values t
Value 1.2.3,4
Use
Octet 1
Octet 2
Octet 3
Octet 4
Unassigned cell indication
Meta-signalling (default) 5.7
00000000
00000000
00000000
0000Xxx0
00000000
00000000
00000000
00010aOc
Meta-signalling
OOooyyyy
yyyyOOoo
00000000
oo01QaOc
General Broadcast signalling (default) 5
00000000
00000000
00000000
oo10Qaac
General Broadcast Signalling 6
OOOOyyyy
yyyyOOoo
00000000
00100aac
6.7
POint-to-point signalling (default)
Point-to-point signalling
6
Invalid Pattern
Segment DAM F4 flow cell
7
End-to-End DAM F4 flow cell 7
1
5
00000000
00000000
00000000
01010aac
ooOOyyyy
yyyyOOOO
00000000
01 01 Oaac
xxxxOOoo
00000000
00000000
0000xxx1
OOOOaaaa
aaaaOOOO
00000000
00110aOa
ooOOaaaa
aaaaOOOO
00000000
01oooaOa
a indicates that the bit is available for use by the appropriate ATM layer function.
2 x indicates "don't care" bits.
3 y indicates any VPI value other than 00000000.
4
5
6
7
c indicates that the originating Signalling entity shall set the CLP bit to O. The network may change the value of the
CLP bit.
ReselVed for user signalling with the local exchange.
ReselVed for signalling with other signalling entities (e.g .• other users or remote networkS).
The transmitting ATM entity shall set bit 2 of octet 4 to zero. The receiving ATM entity shall ignore bit 2 of octet 4.
Table 1-2
Payload Type Indicator Encoding
PTI Coding
(MSBfirst)
t
Interpretation
=0
000
User data cell, congestion not experienced, SOU-type
001 *
010
User data cell, congestion not experienced, SOU-type == 1
011
*
=0
User data cell, congestion experienced. SDU-type = 1
User data cell, congestion experienced, SOU-type
100
Segment OAM F5 flow related cell
101
End-te-end OAM F5 flow related cell
110
Reserved for future traffic control and resource management
111
Reserved for future functions
'* This coding indicates this is the end of a SAR-PDU segment for AAL 5
t
Table information fromATM Forum UNI Specification, Subsections 3.4.4 and 3.4.5,
respectively.
1-8
SEP'95
1 ATM Overview
1.3
AAL 1 Protocol
47 bytes
47 bytes
Segment 1
47 bytes
Segment 2
Segment 3
L
(Not Shown)
SARHeader
(1 byte)
SARHeader
(1 byte)
so
(3 bilS)
ATMHeader
...
(5 bytes)
CRe
{3 biIS\
ATM Payload
----
----ATM Payload
-
VCI (2 byteS)
53-byte ATM Cell
Yagun 1-4 AAL 1 protocol: flow of a 141-byte SOU from the end user to the ATM layer.
The AAL 1 example shown in Figure 1·4 follows the flow of a 141-byte message (Service
Data Unit) from the end user to the ATM Layer. The SDU is passed unchanged through
the Convergence Sublayer to the Segmentation and Reassembly Sublayer (SAR). The
steps to accomplish this are documented in the following pages in Figure 1-5 through
Figure 1-7.
SEP '95
1-9
--
----------~----------------------------
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
47 bytes
47 bytes
Segment 1
Segment 2
l.
•
47 bytes
Segments
J
(Not Shown)
Figure 1·5 AAL 1 protocol: the SAR sublayer divides the entire PDU into 47-byte segments from the beginning and adds a I-byte header
to each segment.
Figure 1-5 shows that the SAR sublayer divides the entire PDU into 47-byte segments
from the beginning and adds a I-byte header to each segment. This header adds
information concerning the sequencing of the segments and provides an error-check
mechanism.
The I-byte SAR header consists of the following, as shown in Figure 1-6:
1-10
•
SN - Sequence Number, a 4-bit field which indicates the sequence number
information for this segment.
•
SNP - Sequence Number Protection, a 4-bit field which provides the error-checking
mechanism for the SAR header.
SEP '95
1 ATM Overview
/
/
/
/
/
/
/
SN
SNP
(4 bits)
(4 bits)
/
/
/
/
SC
(3 bits)
I
CRe
(3 bits)
Figure 1-6 AAL 1 protocol: the I-byte SAR header consists of two 4·bit fields: SN and SNP. Each of these fields is in turn subdivided
into a 3·bit and a I-bit field.
The Sequence Number portion of the header is further subdivided into two subfields, as
shown in Figure 1-6:
•
CSI - Convergence Sublayer Indications, a I-bit subfield which is used to convey
CS-specific information. This is not utilized for aU AAL 1 implementations.
•
SC - Sequence Count, a 3-bit sequence number for the entire CS-PDU. This is
generated by the CS and remains constant for an segments created from that
CS-PDU.
The Sequence Number Protection portion of the header is also subdivided into two
subfields, as shown in Figure 1-6:
•
CRe - Cyclical Redundancy Check, a 3-bit sequence that functions as an error check
for the SN field only.
•
EPC - Even Parity Check, a I-bit check of the previous 7 bits of the header, i.e., the
SN field and the CRC subfield.
SEP '95
1-11
INTERVIEW 8000 Series -
ATM (Broadband): 985-B0682-01
SAR-PDU
SAR-PDU
ATM Header
(5 bytes)
vel (2 bytes)
...
ATM Payload
-
53-byte ATM Cell
Figure 1·7 AAL 1 protocol: a 5-byte ATM header is added to the SAR-PDU segment (which becomes the transparent 48·byte payload for
the ATM cell) to create the ATM cell.
This SAR-PDU (segment) becomes the transparent 48-byte payload for the ATM cell. A
5-byte ATM header is then added to the segment to create the ATM cell. This header
contains the information necessary to transport the cell to its destination, identify the
payload type, assign the cell a loss priority, and provide an error-checking mechanism.
The ATM header is defined in Section 1.2.
1-12
SEP '95
1 ATM OVerv;ew .
1.4
CPl
Stag
(1 byte (1 byte
AAL 3/4 Protocol
At
BASize
(2 bytes)
Etag
1 byte) 1 byte)
Length
(2 bytes)
.-
CPCSHeader
(4 bytes}
44 bytes
ST
SN
(2 bits) (4 bits)
44-byte segments
44 bytes
Mid
U
CRe
6 bits (10 bits)
(10 bits)
•
\
SAR
(2
48 bytes
48 bytes
53-byte ATM Cell
Figure 1-8 AAl.3/4 protocol: transformation of a CPCS-SDU message from the end user into a 53-byte ATM cell.
The AAL 3/4 example shown in Figure 1~8 follows the flow of a message (Service Data
Unit) from the end user to the ATM Layer. The steps to accomplish this for a I21-byte
message are documented in the following pages in Figure 1-9 through Figure 1-12.
SEP '95
1-13
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
121 bytes
CPCS-SDU (Message)
CPCS Header
(4 bytes)
CPCS-PDU Payload
~--~~r7~~~~~~~~~-.r~~~~~~~~
PAD
CPCS Trailer
(4 bytes)
(3 bytes)
/
/
/
/
/
/
/
/
/
/
BASize
(2 bytes)
length
(2 bytes)
Figure 1-9 AAL3/4 protocol: The SDU is passed to the Convergence Sublayer, where a 4-byte header and a 4-byte trailer are added to the
front and end of the SDU (PDU Payload).
The SDU is passed to the Convergence Sublayer, where a 4-byte header and a 4-byte
trailer are added to the front and end, respectively, of the SDU (see Figure 1-9). In
addition, the data segment is padded with 0 to 3 bytes of data at the end, as necessary, to
make the entire Protocol Data Unit (PDU) size a multiple of 4 bytes. (In our example, the
pad is 3 bytes.)
The Common Part Convergence Sublayer (CPCS) header consists of the following:
•
CPI - Common Part Indicator, used to interpret the remainder of the fields in the
header and the trailer added for this sublayer (initial value = 0).
•
Stag - Beginning Tag, an "error check" for this segment. The value in this field is
also placed in the Etag field of the trailer, allowing a quick comparison after receipt to
determine if the SDU has been corrupted.
•
SASize- Buffer Allocation Size, encoded to indicate the CPCS-PDU payload length
(in bytes when CPI = 0).
The CPCS trailer consists of the following:
1-14
•
AL - Alignment, used to make the trailer size 4 bytes and passed transparently
through the network.
•
Etag -End Tag (see Btag)
•
Length - Used to indicate the length of the PDU payload. This field is encoded to
indicate the number of counting units in the length of the payload, with the counting
unit size indicated in the CPI of the header (in bytes when CPI = 0).
SEP'95
1 ArM OveNiew
CPCS·PDU
Segment 2 (COM)
Segment 1 (BOM)
L,
Segment 3 (EOM)
.J
w
(Not Shown)
Figure 1·10 AAL3/4 protocol: The entire CPCS-PDU is passed to the Segmentation and Reassembly (SAR) sublayer for further
processing.
Figure 1-10 shows that the entire CPCS-PDU is then passed to the Segmentation and
Reassembly (SAR) sublayer for further processing. This sublayer divides the entire PDU
into 44-byte segments from the beginning and adds a 2-byte header and a 2-byte trailer to
each segment. These headers and trailers add information concerning the segment order
and provide a cyclical redundancy check (CRC) for the segment, as shown in Figure 1-11.
~t;~s_~~)I__(_4_S~_m_)~_________(1_~_~_'_)______~J 1~\____~_L_~_)____~________C_(1R_O~_~_10_)______~~J
,
..................
............
............
............
............
/
............ ......
/
~~
/
/ '
/ '
~~
~~
~~
..... ~
~~
Figure 1-11 AAL3{4 protocol: header and trailer of SAR PDU.
SEP '95
1-15
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
The SAR header (see Figure 1-11) consists of the following:
•
ST - Segment Type, one of the four possible segment types: Beginning of Message
(BaM), Continuation of Message (COM), End of Message (EOM), or Single
Segment Message (SSM).
NOTE: In the example above, the EOM is a full 44 bytes in length. This will
not necessarily be true of all POUs, as the only requirement is that of
maintaining a PDU length divisible by 4 bytes. Therefore, this segment will
contain whatever portion remains after all of the previous 44-byte segments
have been created by the segmentation process padded with zeroes as
necessary.
•
SN - Sequence Number, allowing the stream of SAR Service Oata Units (SOUs) to
be numbered using modulo 16 in order to provide a "loss of segment" check for each
full POU that is segmented.
•
MID - Multiplexing Identification, used to multiplex CPCS connections on a single
ATM Layer connection, when applicable. The MID value is the same for all
SAR-PDUs of a given CPCS-PDU.
The SAR trailer (see Figure 1-11) consists of two parts:
•
U- Length Indication, binary encoded to indicate the number of bytes of the
CPCS-PDU which are contained in the payload portion of the segment. For the BOM
and COM segments this value must be 44. For EOM segments, the value can range
from 4 to 44 as appropriate. For SSM segments, permissible values range from 8 to
44.
•
CRC - Cyclical Redundancy Check, a lO-bit sequence that functions as an error
check for the entire SAR-SDU, including the header, payload, and the U field of the
trailer.
This SAR-PDU is then handed down to the ATM Layer for further processing.
1-16
SEP '95
1 ArM OveNiew
ATM Header
(5 bytes)
Arpil Payload
48 bytes
..
ATM Header
ATMPayload
(5 bytes)
53-byte ATM Cell
F"1gUI'e 1-12 AAL3/4 protocol: The SAR-PDU (segment) becomes the transparent 48-byte payload for the ATM cell.
This SAR-PDU (segment) becomes the transparent 48-byte payload for the ATM cell (see
Figure 1-12). A 5-byte ATM header is then added to the segment to create the ATM cell.
This headetcontains the information necessary to transport the cell to its destination,
identify the payload type.. assign the cell a loss priority. and provide an error-checking
mechanism.
The ATM header is defined in Section 1.2.
SEP'95
1-17
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
1.5
AAL 5 Protocol
~ cpcs-uu
2bytes
(1 b~e)
CPI
(1 byte)
~~"'Ir-+t--'I-('t-b-1-~-)--rI---(4-~-~-~-S)----'
-- -. ...... _-- ...
CPCS-SOU (Message)
'"'I
-.
SAR sublayer
AmH~
(5 bytes)
53-byte ATM Cel!
Figure 1-13 AAL 5 protocol
The AAL 5 example follows the flow of the last 92 bytes of a message (Service Data Unit)
from the end user to the ATM Layer. The procedure is further broken down and
explained in Figure 1-14 and Figure 1-15.
1-18
SEP '95
1 ATM OveNiew
92 bytes
CPC5-S0U (Message)
-------CPCSCPI
UU
(1 byte) (1 byte)
------Length
(2 bytes)
\
\
\
\
\
\
,
CRC-32 (4 bytes)
Figure 1·14 AAL 5 protocol: the SOU is passed to the Convergen<:e Sublayer, where padding and an 8-byte trailer is added to the end of
theSDU
Figure 1-14 illustrates that the SDU is passed to the Convergence Sublayer, where an
8-byte trailer is added to the end of the SDU. In addition, the data segment is padded
with 0-47 bytes of data at the end, as necessary, to place the trailer at the end of the last
48-byte segment. (In our example, the pad is 44 bytes.)
The CPCS trailer consists of the following:
CPCS User-to-User indication, used to transparently transfer CPCS
information from the origination user to the destination user.
•
CPCS-UU -
•
CPI - Common Part Indicator, used to align the CPCS-PDU trailer to the 32-bit
boundary.
•
length - Used to indicate the length in bytes of the CPCS payload (not including the
PAD bytes).
•
CRC -
Cyclical Redundancy Check, a 32-bit error check for the entire contents of the
CPCS-PDU, including the payload, the PAD field, and the first 4 bytes of the trailer.
This entire CPCS-PDU is then handed to the SAR sublayer for segmentation.
SEP '95
1-19
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
SAR sublayer:
divides the
CPCS-PDU into
48-byte segments
.....",-"......o;..,t;.J..."""""""I:..YS connect a fiber to the output of the device before power is applied. Under
no cir~mst4nCeS should the deviee ever be powered witlwut the fiber cable attached. This
insures that all light is confined within the fiber waveguide, virtually eliminating all
potential hazard. The laser beam can bounce off other objects and still be dangerous.
SEP '95
6-3
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
NEVER look in the end of a fiber to see if light is coming out!
Most fiber optic laser wavelengths (1300 nm and 1550 nm) are totally invisible to the
unaided eye and will cause permanent damage to one's vision. Shorter wavelength
lasers (e.g., 780 DID) are visible and are very damaging. Always use instrumentation,
such as an optical power meter to verify light output; the INTERVIEW ATM
single-mode laser output is 1300 nm.
NEVER look into the end of a fiber on a powered device with any sort of magnifying
device, such as a microscope, eye loupe, or magnifying glass; this WILL cause a
permanent, irreversible burn on the retina. Completely disconnect the unit from the
power source to examine a fiber.
6.3
Fiber Optic Cables and Accessories Cleaning
The following equipment and cleaning method are recommended by several fiber optic
cable and accessory manufacturers.
(A) Required Equipment
•
Kimwipes or any lens-grade, lint-free tissue. The type sold for eyeglasses work well.
•
Denatured Alcohol
•
30X Microscope
•
Canned Dry Air
(8) Recommended Cleaning Technique
The following steps are recommended by several manufacturers to clean fiber optic
cable and accessories.
•
Fold the tissue twice so it is four layers thick.
•
Saturate the tissue with alcohol.
•
First clean the sides of the connector ferrule. Place the connector ferrule in the
tissue and apply pressure to the sides of the ferrule. Rotate the ferrule several
times to remove all contamination from the ferrule sides.
•
Move to a clean part of the four-ply tissue, still saturated with alcohol, and put
the tissue against the end of the connector ferrule. Place your fingernail against
the tissue so that it is directly over the ferrule, and scrape the end of the
connector until it squeaks, like a crystal glass that has been rubbed when it is wet.
•
Use the microscope to verify the quality of the cleaning. If it isn't completely
clean, repeat the steps with a clean tissue. Repeat until you have a cleaning
technique that yields good, reproducible results.
•
Mate the connector immediately!
6 Gabling the INTERVIEW ATM Models
•
6.4
Clean, canned, pressurized air can be used to remove lint or loose dust from the
port of a transmitter or receiver to be mated with the connector. Never insert
any liquid into the ports.
Cables, Splitters, Connector Adaptors, and Attenuators
AR Test ~ternsadheres tows convention of color-coordinated cables:
•
coaxialcables are generally all black
•
black cables with black optical connectors are for multi-mode optical testing
•
all-yellow ca1;>les with yellow optical connectors are for single-mode optical testing
•
black splitter cables witl1:yeUow optical connectors are for single-mode optical testing
Coaxial cables and monitor access pads are included in the ATM Interface Module
options.
Telenex Corporation currently offers two interface accessory kits for testing optical ATM
data, OPT-951-311-1 andOPT-9S1·312-1.
•
OPT-9$1-311-1 is for use in single-mode fiber optic and in multi-mode fiber optic
testing
•
OPT-9S1-312-1 is for multi-mode fiber optic testing only
Table 5-1 gives·a complete listing of the cables, splitter cables, connector adaptors,
couplers, and attenuators contained in each of these kits. Their purposes follow.
•
Splitter cables divide or split the signal and its level.
•
Connector adaptors adapt the connector to join another connector type, i.e., from ST
to SC, from ST to FCIPC.
•
Couplers are back-to-back female connectors used to mate two cables with male
connectors on each.
•
Attenuators are devices used to lower (attenuate) tbesignal to the proper level for
receiving. Theattenuatorcontained in thesingle41100e accessory kit attenuates the
signal by -15 dB.
We will look at examples of these pieces of equipment. There are three types of fiber
optic connectors in these kits: ST(ro\lnd),SC (square), and FC!PC (round fiber
contact/physical contact). Note that the cable lengths have been shortened for purposes of
illustration.
SEP'95
6-5
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(A) Coaxial Cabling
The cable illustrated in Figure 6-4 is an RG-59 75 Ohm Coaxial Cable for DS-3, E3,
and STS-l testing. It has two male BNC connectors. (Referred to as "R" in cable
diagrams beginning with Figure 6-21.)
Male BNC
Figure 6-4 RG·59 75 Ohm Coaxial Cable for DS·3, E3. and STS·l, Male to Male (BNC).
Figure 6-5 shows a cut-away versionofPL-985-11302, a monitor access pad for DS-3,
E3, and STS-l. This view allows visibility of the resistor on the front female BNC
connector which connects to the INTERVIEW's AIM; two other female BNC
connectors flank the two sides of the pad with the data flowing in from the left and
out to the right. Use this pad for non-intrusive monitoring as shown in Figure 6-21.
Once the pad has been cabled into the line, it prevents the test equipment from
interfering with the data flow, even when the test equipment is disconnected and
reconnected. (Referred to as "Q" in cable diagrams beginning with Figure 6-21.)
FemaleBNC
(input)
Female BNC
(to INTERVIEW)
FemaleBNC
(output)
Figure 6-5 Monitor Access Pad for DS-3, E3. and STS-I. FemalelFemale/Female (BNC).
6-6
SEP '95
(; Cab1i!1Sl the INTERVIEW ATM Models
(B) SingJe.Mode Fiber Optic Cables, Attenuators, Adaptors, and
COuplers
There are various types of fiber optic cables, attenuators, adaptors, and couplers
designed for single-mode fiber optic testing.
1.
Single-Mode Fiber Optic Cable. Figure 6-6 illustrates single-mode fiber optic cables.
The cable and its two male ST oonnectors are an yellow; this cable is AMP's cable
labeledAMP·LI, 5027fJ6..X. where X indicates the metric length of the cable.
(Referred to as "T" in cable diagrams beginning with Figure 6·21.)
Male ST
Male ST
-x
CAUTION: Fiber optic cables are made
ofglass fibers and will break unless ~
a "gentle" bend (greater than I inch) is in
the cable.
DO NOT TOUCH CONNECTOR
ENDSAND KEEP CONNECTOR
ENDS CAPPED UNLESS IN USE.
fipre 6.6 Single-Mode Fiber Optic Cables (Yellow), Male ST to Male ST (Yellow)_
WARNING: Note the DANGER warning notice on the door of the ATM top enclosure
regarding the I...1SER from the single-mode optical connector. Avoid direct f;XJ2osure to the
~ngl,-mode LA$ER beam as it could damage your ~htfrom both the connector on the
INTERV/EWATM unit and the connector on the cable itself.
WARNING: Keep the single-mode optical switch of the AIM·302-1 in the OFF position until
you have cabled up the single-mode TXILASER connector and are ready to transmit. (LED is
dark when off.)
6-7
SEP '95
-- -
----
---------------_..
_----------------_ _----------------_._._..._._...
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
2.
Single~Mode Fiber Optic
Splitter Cable. The single-mode fiber splitter cable has a black
body with a black cable and yellow connectors, one male ST to two male STs. The cable
shown in Figure 6-7 is used in emulation mode and is equivalent to AMP's cable
labeled 7-107798-6. (Referred to as"W" in cable diagrams beginning with Figure 6-21.)
Take care to note that the split portion of the cable has a cable marked "2" and a cable
marked "1." This distinction is crucial as the cable marked "2" is a 10% tap cable and
the cable marked" 1" is a 90% through cable. When splitting a signal transmitted by
the INTERVIEW (which is a long-reach signal, one above -6 dB), and rerouting it back
to the INTERVIEW, the 10% tap cable "2" must be the cable attached to the unit.
Note that an attenuator is not necessary for the 10% tap cable as the tap sufficiently
lowers the signal level which the INTERVIEW then receives-see subsection 3., below.
CAUTION: Fiber optic cables are made ofglass fibers and will break unless ~ a "gentle" bend (greater than
1 inch) is in the cable.
DO NOT TOUCH CONNECTOR ENDS AND KEEP CONNECTOR ENDS CAPPED UNLESS IN USE.
See CAUTION notices with Figure 6-6 as the danger applies to the Single-Mode Splitter Cable, also.
MaleST
Figure 6-7 Single-Mode Fiber Splitter (Black Body, Black Cable, Yellow Connector), Male ST to 2 Male STs.
6-8
SEP '95
6 Cabling the INTERVIEW ATM Models
3.
Single-Mode Fiber Altenuator. The ST/ST single-mode fiber attenuators are metal
wi\:h a yellow band; one side is a female ST connector and the other side is a male
ST connector. (Referred to as "U" in cable diagrams beginning with
Figure 6-21.)
This attenuator is for use with the INTERVIEW's AIM-302-1 when testing a
single-mode long-reach signal (above -6 dB) which is returned to the
INTERVIEW (The INTERVIEW's ATM Interface Module emits a long-reach
signal of 0 dB.) The -15 dB attenuator included in the kit decreases (attenuates)
the signal by 15 decibels~ to lower it to a level between -6 dB and -38 dB, the
sensitivity range of the INTERVIEW's receiver.
If unsure as to the signal level of the line to be tested, use a signal tester to
determine the decibel level. Otherwise, you may spend many hours of frustration
trying to get the test to work and may risk harm to your equipment.
MaleST
FemaleST
yellow
Figure 6-8 Single-Mode Fiber Attenuator (Metal with Yellow Band), ·15 Db, Female ST to Male ST.
4.
Single-Mode Fiber ST to SC Adaptor. The single-mode ST to SC adaptor
(Figure 6.9) has a blue male SC connector on one end, a female ST connector on
the other end, and a yellow band labeled "SINGLE MODE" in the center.
(Referred to as "V" in cable diagrams beginning with Figure 6-21.)
MaleSC
FemaieST
Figure 6·9 Single-Mode ST to SC Adaptor (Blue Connector, Yellow Band labeled "SINGLE MODE"), Female ST to Male SC.
5.
Si/Jgle-Mode Fiber ST to FC/PC Adaptor. The single·mode ST to FC/PC adaptor
(Figure 6-10) has a male ST connector on one end. a male FC/PC connector on
the other end, and a gold body with a yellow band labeled "SINGLE MODE" in
the center. (Referred to as "P" in cable diagrams beginning with Figure 6-21.)
MaleST
Figure 6-10 Single-Mode ST to FCiPC Adaptor, Male ST to Male FCIPC.
SEP '95
6-9
INTE.RVIEW 8000 Series - ATM (Broadband): 985-B0682-01
6.
Single-Mode (or Multi-Mode) ST to ST Coupler. The single-mode (or multi-mode)
ST to ST coupler is shown in Figure. 6-11; note this is the same coupler as
described and shown in Figure 6-18. It is all metal and has a female ST
connector at either end so as to join two male-ended single-mode (or
multi-mode) cables. (Referred to as "8" in cable diagrams beginning with
Figure 6-21.)
Female ST
Female ST
11;0-5
Figure 6-11 Single-Mode (or Multi-Mode) Coupler (all Metal), Female ST to Female ST.
7.
Single-Mode (or Multi-Mode) SC to SC Coupler. The single-mode (or multi-mode)
SC to SC coupler is shown in Figure 6-12; note this is the same coupler as
described and shown in Figure 6-19. It is all metal and has a female SC
connector at either end (rectangular in shape) so as to join two male-ended
single-mode (or multi-mode) cables. (Referred to as "0" in cable diagrams
beginning with Figure 6-21.)
Female SC
FemaleSC
Figure 6-12 Single-Mode (or Multi-Mode) Coupler (all Metal), Female SC to Female Sc.
8.
Single-Mode (or Multi-Mode) FC/PC to Fe/PC Coupler. The single-mode FC/PC
to FC/PC coupler is shown in Figure 6-13; note this is the same coupler as
described and shown in Figure 6-20. It is all metal and has a female FC/PC
connector (circular) at either end so as to join two male-ended single-mode (or
multi-mode) cables. (Referred to as "N" in cable diagrams beginning with
Figure 6-21.)
Female FCIPC
Female FC/PC
U
Figure 6-13 Single-Mode (or Multi-Mode) Coupler (all Metal), Female FC/PC to Female FC/PC.
6-10
SEP '95
8 Cabling the INTERVIEW ATM Models
(Cl Multi-Mode Fiber OptiC Cables, Adaptors, and Couplers
There are various types of fiber optic cables, attenuators. adaptors, and couplers
designed for multi-mode fiber optic testing. Please note the danger of damage to
one's eyesight with single-mode fiber optic testing is not present when you are testing
with multi-mode fiber optics.
1.
Multi-Mode Fiber Optic Cable. Figure 6-14 illustrates multi-mode fiber optic
cables. The cable and its two male ST connectors are all black and are equivalent
to: AMP's cable labeledAMP-Ll, 502144-X, where X indicates the metric length
of the cable. (Referred to as "X" in cable diagrams beginning with Figure 6-21.)
CAUTION: rIDer optic cables are made ofglass fibers and will break unless atJ.b! a "gentle" bend (greater than 1
inch) is in the cable.
DO NOT TOUCH CONNECTOR ENDS AND KEEP CONNECTOR ENDS CAPPED UNLESS IN USE.
MaleST
MaleST
Figure 6-14 Multi-Mode Fiber Optic Cables (Black), Male ST to Male ST.
SEP '95
6-11
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
2.
Multi-Mode Fiber Optic Splitter Cable. The multi·mode fiber splitter cable shown
in Figure 6-15 has a black body with a black cable and black connectors, one male
ST to two male STs. It is equivalent to AMP's cable labeled PN 502324-3.
(Referred to as "Z" in cable diagrams beginning with Figure 6-21.)
Take care to note that the split portion of the cable has two cables on one side,
splitting the signa1 equally between them to 50% each.
CAUTION: Fiber optic cables are made ofglass fibers and will break
unless QIJ../)!. a "gentle" bend (greater than 1 inch) is in the cable.
DO NOT TOUCH CONNECTOR ENDS AND KEEP CONNECTOR
ENDS CAPPED UNLESS IN USE.
MaleST
Male ST
MaleST
Figure 6-15 Multi-Mode Fiber Optic Splitter Cable (Black Body, Black Cable, Black Connector), Male ST to 2 Male STs.
6-12
SEP '95
6 eapting the INTERVIEW ATM Models
3.
Multi~Mode Fiber SC to
ST Adaptor. Figure 6-16 illustrates the multi-mode SC to ST
adaptor. It has a beige male SC connector on one end, a metallic male ST connector
on the other end, and a blue body with a yellow band labeled "62.5/125" in the center.
(Referred to as "Y" in cable diagrams beginning with Figure 6-21.)
Male
se
~=J
beige·
Male ST
I",
yellow blue
Figure 6-Hi Multi-Mode ST to SC Adaptor (Beige Connector, Yellow Band on Blue Body), Male SC to Male ST.
4.
Multi~Mode Fiber ST to
FC Adaptor. The multi-mode ST to FC adaptor shown in
Figure 6-17 has a male ST connector on the other end, a male Fe connector on
one end, and a blue boGy with a yellow band labeled "62.5/125" in the center.
(Referred to as "M" in cable diagrams beginning with Figure 6-21.)
MaleST
MaleFC
Figure 6-17 Multi-Mode ST to FC Adaptor. Male ST to Male Fe.
5.
Multi-Mode (or Single-Mode) ST to ST Coupler. The multi-mode (or single-mode) ST
to ST coupler is shown in Figure 6-18; note this is the same coupler as previously
described and shown in Figure 6-11. It is all metal and has a female ST connector at
either end so as to join two male~ended multi~mode (or single-mode) cables.
(Referred to as "S" in cable diagrams beginning with Figure 6-21.)
Female ST
Female ST
&;0-:1
FigBre 6-18 Multi-Mode (or Single-Mode) Coupler (all Metal), Female ST to Female ST
6.
Multi·Mode (or Single-Mode) SC to SC Coupler. The multi-mode (or single-mode) SC
to SC coupler is shown in Figure 6~19; note this is the same coupler as previously
described and shown in Figure 6-12. It is all metal and has a female SC connector at
either end so as to join two male-ended multi-mode (or single-mode) cables.
(Referred to as "0" in cable diagrams beginning with Figure 6-21.)
FemaleSe
FemaleSe
Figure 6-19 Multi·Mode (or Single-Mode) Coupler (all Metal), Female SC 10 Female Sc.
SEP '95
6-13
INTERVIEW 8000 Series -
7.
ATM (Broadband): 985-B0682-01
Multi-Mode (or Single-Mode) FC/PC to FC/PC Coupler. The multi-mode (or
single-mode) FC/PC to FC/PC coupler is shown in Figure 6-20; note this is the
same coupler as previously described and shown in Figure 6-13. It is all metal
and has a female FC/PC connector at either end so as to join two male-ended
multi-mode (or single-mode) cables. (Referred to as "N" in cable diagrams
beginning with Figure 6-21.)
o
Female FCIPC
Female FCIPC
Figure 6-20 Multi-Mode (or Single-Mode) Coupler (all Metal), Female FCIPC to Female FctPC.
6.5
Sensitivity of the Single-Mode Fiber Optical Signal
The sensitivity level of the INTERVIEW's AIM-302-l combined single-mode and
multi-mode fiber optical receiver is a range between ~6 dB and -38 dB. If the signal level is
higher, an attenuator must be used to lower the signal to this range so as not to damage
the equipment-see subsection 6.4(B)3.
The INTERVIEW's AIM-302-1 transmits a single-mode long-reach signal at 0 dB.
You need to know the length of your cable and the type of signal you will be receiving. If
you are unsure as to the type of signal you will be receiving (long-reach, mid-reach, or
short-reach), use a signal-level measuring device to determine the exact range to avoid
hours of frustration and possible damage to your equipment. Mid-reach, short-reach, and
multi-mode transmission can be done without attenuation; long-reach transmission will
probably need attenuation if using a cable less than 10 kilometers in length.
6.6
Type of Connectors on the Premises
Cables tend to have male connectors and the equipment provides female connectors.
Cables can be coupled together with the female-female coupler provided in Telenex
Corporation's optional interface accessory kits.
Coaxial copper (metallic) wire transmissions generally have BNC connectors.
Fiber optical transmissions commonly use ST, SC, or FCIPC connectors. Traditional ST
connectors are round and need a slight twist to lock on. The newer SC connectors are
square in shape and simply snap on. FC/PC connectors are keyed in and then screwed in
to secure the connection; single-mode requires FC/PC (Physical Contact) while
multi-mode can use an FC-type connector only without the actual physical contact.
Adaptors are included in Telenex Corporation's optional interface accessory kits.
6.7
Coaxial Cabling Diagram for Monitoring
The following is a sample cabling diagram for monitoring transmissions with coaxial
(metallic) cables.
6-14
SEP '95
8 Gabling the INTERVIEW ArM Models
Monitoring with a Patch Panel
Mode: Monitor
Connector: Coaxial
DS-3/E3/STS-1
A
lAX
B
TXI
AX
NOTE: Padding Resistors
(or their equivalents) are
required for non-intrusive
monitoring; this does not
disturb the line under test.
Padding
Resistor
------.....
t::=l
TX
..
Workstation
label
Description
From
To
Q
OS-3/E3/ST8-1 Pad for Monitor Access (non-intrusive)
Female/Female/Female (BNC)
Network
Workstation
Workstation
Network
RG-5975 Ohm Coaxial Cables for OS-3, E3, and STS-1,
Male to Male (BNG)
Workstation
Network
A: RXvia Pad
R
B: RXviaPad
Ylgllre 6-21 Monitoring with a Patch Panel (Pad) with Metallic Wire (Coaxial Cables).
SEP '95
6-15
-------------,
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
6.8
Coaxial Cabling Diagrams for Emulation
The next few pages contain sample cabling diagrams for emulating transmissions with
coaxial (metallic) cables. These can be adapted to other specific scenarios.
Emulating a Workstation and Monitoring Transmission Internally
Mode: Emulate A
Connector: Coaxial
Clock Source: Receive Data
DS-3/E3/STS-1
A
'RX
B
TX'
RX
o
Label
Description
From
To
R
RG-59 75 Ohm Coaxial Cables for OS-3, E3, and STS-1,
Male to Male (BNC)
Network
A: TX
A: RX
Network
Figure 6-22 Emulation a Workstation with Metallic Wire (Coaxial Cables} and monitoring transmission internally_
6-16
SEP '95
6 Cabling the INTERVIEW ATM Models
Emulating a Workstation and Monitoring Transmission Externally
Mode: Emulate A
Connector: Coaxial
Clock Source: Receive Data
DS-3/E3/STS-1
A
IRX
B
TXI
RX
Label
Description
From
To
Q
DS-3/E3/STS-1 Pad for Monitor Access (non-intrusive)
Female/Female/Female (BNC)
A: TX
Network
R
RG-59 75 Ohm Cpaxial Cables for OS-3, E3, and STS-l ,
Male to Male (BNC)
Network
Network
A: TX
Pad
A: RX
Pad
Pad
B: RXvia Pad
Figure 6-23 Emulation a Workstation with Metallic Wire (Coaxial Cables) and monitoring transmission externally_
6-17
SEP '95
~"~""
~-~~~"~--"---"--~--"-"--"---"-""-"----------,-".-.--.----
--------
INTERVIEW 8000 Series '- ArM (Broadband): 985-80682-01
Emulating the Network
Mode: Emulate A
Connector: Coaxial
Clock Source: Internal
DS-3/E3/STS-1
A
IRX
TX'
B
RX
o
R
R
Workstation
Label
Description
From
To
R
RG-59 75 Ohm Coaxial Cables for DS-3, E3, and STS-1,
Male to Male (BNC)
Workstation
A: TX
A: AX
Workstation
Figure 6-24 Emulation the Network with Metallic Wire (Coaxial Cables).
6-18
SEP '95
6 Gabling the INTERVIEW ArM Models
Emulating a Network and Monitoring Transmission Externally
Mode: Emulate A
Connector: Coaxial
Clock Source: Receive Data
DS-3/E3/ST8-1
A
IRX
B
TXJ
RX
Workstation
label
Description
From
To
Q
OS-3/E3JSTS-1 Pad for Monitor Access (non-intrusive)
A: TX
Workstation
Workstation
Workstation
A: TX
Pad
A: AX
Pad
Pad
B: RXviaPad
Female!Female!Female (BNC)
RG-5975 Ohm Coaxial Cables for OS-3, E3, and STS-1,
Male to Male (BNC)
R
F'tgUre 6-25 Emulation a Workstation with Metallic Wire (Coaxial Cables) and monitoring transmission externally.
SEP '95
6-19
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
6.9
Single-Mode Fiber Optic Cabling Diagrams for Monitoring
The next few pages contain sample cabling diagrams for monitoring transmissions with
single-mode fiber optic cables. These can be adapted to other specific scenarios.
Monitoring in Repeater Mode
with Single-Mode Fiber
Mode: Monitor
Connector: Fiber
[NOTE: Turn switches ON after cabling is completed.]
WARNING: Single-mode Transmission LASER is. active unless switch ;s OFF. (LED is dark when off.)
Do NOT activate LASER switches until cabling is completed and you are ready to transmit and you
are using Single-Mode Fiber.
labe
Description
T
Single-Mode Fiber Optic Cables
(yellow), Male ST to Male ST
U
Single-Mode Fiber Attenuator (Metal with Yellow Band).
-15 Db, Female ST to Male 8T
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Female STto Male SC
6-20
From
....
B: LASER TX/SM
Workstation
A: LASER TX/8M
To
A" AX
Workstation
B: AX
Network
SEP '95
6 Gabling the INTERVIEW ArM MOdels
DS-3/E3/ST5-1
A
B
IRX
TXt
SONETOC-3c
SINGLe!MULTI-MODE
SONETOC-3c
SINGLE/MULTI-MODE
A
B
I
RX
TXI
I
TXt
RX MM
RX MM
OPTIONAL: "un Attenuators needed
when transmitter is long reach
if distance is less than '" 10Km.
#
//
/I
/I
,
II
/I
/I
/I
II
/I
/I
II
II
/I
•
II
/I
/I
Turn ONonJy
after cabling
is completed.
/I
/I
/I
••
"
"•
••
"
/I
T :
II
II
/I
II
/I
LASER'
TX/SM
••
••
T'
•,
•,
•
T••
••
••
\\.... . '".
J<'
•
II
•.
/I
v
v .1!_____
~R;X
TX
OPTIONAL: "V" Adaptors
for SC connectors
Workstation
Figure 6-26 Monitoring in Repeater Mode with Single-Mode Fiber Optic Cables:
Signal travels in RX A, out TX B, in RX B. out TX A.
SEP'95
6-21
---~----"--,.-------.--,--,
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
Monitoring Using Splitters
Close to Workstation with Single-Mode Fiber
Mode: Monitor
Connector: Fiber
WARNING: Single-mode Transmission LASER is active unless switch is OFF. (LED;s dark when off.'
Do NOT activate LASER switches.
Label
Description
P
Single-Mode Adaptor,
Male ST to Male FC/PC
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
T
Single-Mode Fiber Optic Cables (yellow).
Male ST to Male ST
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Female ST to Male SC
W
Single-Mode Fiber Splitter (Black Body, Black Cable,
Yellow Connector), Male ST to 2 Male STs
Cable marked "2" is 10% Tap,
Cable marked "1" is 90% Through
6-22
From
To
Network
Splitter
Splitter
Network
Network [via cable] B: RX 10% and
Workstation
A: RX 10% and
Workstation
Network
[via cable]
SEP '95
6 Cabling the INTERVIEW ATM Models
SONETOC-ac
SINGLE/MULTI-MODE
SONETOC-3c
SINGLElMUlTi-MODE
A
B
,
f
10% tap marked "2" :
1::
,,••
•
•
:til
t
•
,
•
/I
/I
......
~...
T ..
,••:"-
r
~
/I
/I
t
S
10% tap marked "2"
W
",----,'.- ••• -
..
.... ,/
90% through marked "1"
...•...••.
- •.... _- .....
w
..................
-..........
'\
"'
... _............ _.. - - .... ' ..
,,~... 90%
- .. '" through marked" I"
Jf:
~. "
, \.
.........
.
\\
•
S
•
V
OPTIONAL: uV" Adaptors for SC connectors
or "P" Adaptors for FC/PC connectors
v
TX:..-u._ _.u-..'RX
Workstation
Figure 6·27 Monitoring Using Splitters Oose to Workstation with Single-Mode Fiber Optic Cables.
SEP '95
6-23
INTERVIEW 8000 Series -
ATM (Broadband): 985-80682-01
Monitoring at TELCO Using Splitters
Close to TELCO with Single-Mode Fiber
Mode: Monitor
Connector: Fiber
WARNING: Single-mode Transmission LASER is active unless switch ;s OFF. (LED is dark when off.)
Do NOT activate LASER switches.
Label
Description
S
Single-Mode or Multi-Mode Coupler (alf Metal),
Female ST to Female ST
T
Single-Mode Fiber Optic Cables (yellow),
Male ST to Male ST
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band). Female STto Male SC
W
Single-Mode Fiber Splitter (Black Body, Black Cable,
Yellow Connector), Male ST to 2 Male STs
Cable marked "2" is 10% Tap,
Cable marked "1" is 90% Through
6-24
From
To
Workstation
Splitter
Splitter
Workstation
Workstation
[via cable]
TELCO
B: RX 10% and
TELCO
A: RX 10% and
Workstation
[via cable]
SEP'95
6 Cabling the INTERVIEW ATM Models
SONETOC-3c
SINGLEIMULn-MODE
DS-3/E3/STS-1
A
'RX
TXI
SONETOC-3c
SINGLE/MULn-MODE
A
B
RX
I
B
I
LASER'
TX/SM
TXI
RX MM
,•
r
10% tap marked "2"
t
II
t
•••
••
-.. ---- ..•
.-----,
.r:::;sr:::r ..
i':, 1:~
\~ ...
.. -
,
,•
,••
I
w
11111:_ ...
- .. " _-_ ...
90% through marked" 1"
_ .....•.•.
.....
w
-.~...
~"' .. ~";t~r:Ughmarked"l"
.. -.. . ... --_ .. - . .
.....
V
TX/SM
i
!I
10% tap marked "2"
-• •
T:tI#..-
LASER I
~ ®I:~·®ll ~ ®I;;~·®~I =- J
{;!D 0 01
s
TXI
RX MM
.. ~\:: \
~
\""'&
~ ..
T
~
v
V
V
TX
OPTIONAL:
"vn Adaptors
TX.-u._ _~RX
for SC connectors
RX
TELCO
Workstation
Figure 6-28 Monitoring at TELCO Using Splitters Close to TELCO with Single-Mode Fiber Optic Cables.
SEP'95
6-25
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
6.10 Single-Mode Fiber Optic Cabling Diagrams for Emulation
The next few pages contain sample cabling diagrams for emulating transmissions with
sing1e~mode fiber optic cables. These can be adapted to other specific scenarios.
Emulating a Workstation and Monitoring Transmission Externally
with Single-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Receive Data
[NOTE: Turn switch ON gfjc]:, cabling is completed.]
WARNING: Single-mode Transmission LASER is active unless switch is OFF. (LED is dark when off.)
Do NOT activate LASER switches until cabling is completed and you are ready to transmit using
Single-Mode Fiber.
Label
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
T
Single-Mode Fiber Optic Cables
(yellow), Male ST to Male ST
U
Single-Mode Fiber Attenuator (Metal with Yellow Band),
-15 Db, Female STto Male ST
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Female ST to Male SC
W
Single-Mode Fiber Splitter (Black Body, Black Cable,
Yellow Connector), Male ST to 2 Male STs
Cable marked "2" is 10% Tap,
Cable marked "1" is 90% Through
6-26
From
To
Network
A: RX
A: LASER TX/SM
Network and
B: RX 10%
SEP '95
6 Cabling the INTERVIEW ATM Models
DS-3/E3/STS-1
A
SONETOC-3c
SONETOc-3c
SINGLElMULTt-MODE
SINGLE/MULTI-MODE
A
B
B
'RX
lXl
LASER'
RX
TX/SM
~o 001
u
OPTIONAL: "U~ Attenuators needed
if distance;s less than ~ 10 Km.
tt
tt
//
II
•
,.
T :
(I
#I
,.,. ,.
,.
(I
#I
(I
(I
(I
(I
(I
(I
T II "
II
(I
(I
(I
•
"
/I
OPTIONAL: "V" Adaptors
for SC connectors; also,
may need additional "T"
cable as shown
Figure 6-29 Emulating a Workstation with Single-Mode Fiber Optic Cables and monitoring transmission externally.
SEP '95
6-27
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
Emulating a Workstation and Monitoring Transmission Internally
with Single-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Receive Data
[NOTE: Turn switch ON gftgr. cabling is completed.]
WARNING: Single-mode Transmission lASER is active unless switch is OFF. (LED;s dark when off.)
Do NOT activate lASER switches until cabling is completed and you are ready to transmit using
Single-Mode Fiber.
Label
Description
From
T
Single-Mode Fiber Optic Cables
(yellow), Male ST to Male ST
Network
A: LASER TX/SM
U
Single-Mode Fiber Attenuator (Metal with Yellow Band),
-15 Db, Female ST to Male ST
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Female ST to Male SC
6-28
To
A: RX
Network
SEP '95
6 Cabling the INTERVIEW ATM Models
SONETOC-3c
SINGLE/MULTI.yODE
DS-3!E3/STS-1
A
A
B
'RX
TX'
SONETOc.3c
SINGLEIMULTI·MODE
B
ITX/
RX
•AX MM
TX/
RX MM
LASER'
TXlSM
u
OPTIONAL: "U Attenuators needed
if distance is less than '" 10 Km.
9
.,
//
•
It
II
II
"
II
II
II
It
It
It
.,
"
It
T :
It
"
It
III
II
III
III
II
III
.,""
It
It
II
It
•
III
III
II
"
.."
II
(I
It
It
T
II
•
II
III
II
It
OPTIONAL: "VW Adaptors
for SC connectors
Figure 6-30 Emulating a Workstation with Single-Mode Fiber Optic Cables and monitoring transmission internally.
6-29
SEP '95
---_.....__......_-_.
__._----_._--_ _------_ _._-_ - - - ..
...
...
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
Emulating a Network and Monitoring Transmission Externally
with Single-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Internal
[NOTE: Turn switch ON. cabling is completed.]
WARNING: Single-mode Transmission LASER is active unless switch is OFF. (LED is dark when off.)
Do NOT activate lASER switches until cabling is completed and you are ready to transmit using
Single-Mode Fiber.
label
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
T
Single-Mode Fiber Optic Cables
(yellow), Male ST to Male ST
U
Single-Mode Fiber Attenuator (Metal with Yellow Band),
-15 Db, Female ST to Male ST
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Female ST to Male SC
W
Single-Mode Fiber Splitter (Black Body, Black Cable,
Yellow Connector), Male ST to 2 Male STs
Cable marked "2" is 10% Tap,
Cable marked "1" is 90% Through
6-30
From
Workstation
A: LASER TX/SM
To
A:
RX
Workstation and
B: RX 10%
SEP '95
6 Cabling the INTERVJE.W ArM Models
[)S.3/E3/STS-1
A
B
TX'
lAX
RX
SONETOC·3c
SONETOC-3c
SINGLE/IIWLTJ.MODE
A
I
TXJ
RX MM
SINGLE/MULTI-MODE
B
I
TXJ
RX MM
rt----'-".P 0 0 I
u
OPTIONAL: "U" Aitenuators needed
if distance is less than '" 10 Km.
..
"
"
"
//
T:
.
1#
..""
"
1#
."
It
It
"
II
OPT/ONAL: "V" Adaptors
for SC connectors; also,
may need additional "TB
RX
cable as shown
Workstation
Figure 6-31 Emulating a Network with Single-Mode Fiber Optic Cables and monitoring transmission externally .
6-31
SEP '95
---_..__._-_.._._--_..._..__ ..- - - -..._--_....._-_._-----_..._-_. _---_._--_._.__ _-_._._ _._-_._-_._--._
_.
....
..
..........._.... ---------_.-
INTERVIEW 8000 Series -ATM (Broadband): 985-B0682-01
Emulating a Network and Monitoring Transmission Internally
with Single-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Internal
[NOTE: Turn switch ON lJ/IJ:L cabling is completed.}
WARNING: Single-mode Transmission LASER is active unless switch ;s OFF. (LED is dark when off.)
Do NOT activate LASER switches until cabling ;s completed and you are ready to transmit using
Single-Mode Fiber.
Label
Description
From
T
Single-Mode Fiber Optic Cables
(yellow), Male ST to Male ST
Workstation
B: RX
U
Single-Mode Fiber Attenuator (Metal with Yellow Band),
-15 Db, Female ST to Male ST
V
Single-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Female ST to Male SC
6-32
To
A:
RX
Workstation
SEP '95
6 Cabling the INTERVIEW ArM Models
SONETOC-3c
SINGLEIMULTI-MODE
DS-3IE3/STS-1
A
TXI
B
A
B
IRX
SONETOC-3c
SlNGLElMULTI-MODE
I
RX
TX/
RX MM
I
TXI
AX MM
u
"un
Turn ON only
after cabling (I ,
is completed...
OPTIONAL:
Attenuators needed
jf distance is less than ...., 10 Km.
""
•
•
"
•
• "T
T#
"
(I
(I
II
(I
(I
(I
,
(I
•"
(I
II
(I
(I
(I
(I
"
""
•
,,"
•
(I
It
II
""
"
•"
v
OPTIONAL: ·V" Adaptors
for SC connectors; also,
may need additional " ,
cable as shown
Workstation
Figure 6-32 Emulating a Network with Single- Mode Fiber Optic Cables and monitoring transmission internally.
SEP'95
6-33
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682,-01
6.11
Multi-Mode Fiber Optic Cabling Diagrams for Monitoring
The next few pages contain sample cabling diagrams for monitoring transmissions with
multi-mode fiber optic cables. These can be adapted to other specific scenarios.
Monitoring in Repeater Mode
with Multi-Mode Fiber
Mode: Monitor
Connector: Fiber
WARNING: Single-mode Transmission LASER is active unless switch ;s OFF. (LED;s dark when Off.)
Do NOT activate LASER switches.
Label
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
X
Multi-Mode Fiber Optic Cables (Black), Male ST to Male ST
Y
Multi-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Male SC to Male ST
6-34
From
To
Network
B: TX/MM
Workstation
A: TX/MM
A: RX
Workstation
B: RX
Network
SEP '95
6 CablJng the INTERVIEW ATM Models
DS-3/E3/STS-1
A
'RX
B
TX'
SONETOC-3c
SONETOC-3c
SINGLE/MULTI-MODE
SINGLEIMULTI-MODE
A
B
RX
~o 001
y
OPTIONAL: "sn Couplers and
UYH Adaptors for SC connectors
Workstation
Figu.re 6-33 Monitoring in Repeater Mode with Multi-Mode Fiber Optic Cables:
Signal travels in RX A. out TX/MM B. in RX B, out TXlMM A
SEP '95
6-35
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
Monitoring Using Splitters
Close to Network Termination with Multi-Mode Fiber
Mode: Monitor
Connector: Fiber
WARNING: Single-mode Transmission LASER is active unless switch Is OFF. (LED is dark when off.)
Do NOT activate LASER switches.
Label
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
X
Multi-Mode Fiber Optic Cables (Black), Male ST to Male ST
Y
Multi-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Male SC to Male ST
Z
Multi-Mode Fiber Splitter (Black Body, Black Cable,
Black Connector), Male ST to 2 Male STs
Cables marked "1" and "2" each 50%
From
To
Workstation
Splitter
Splitter
Workstation
Network
B: RXand
Workstation
[via cable]
A: RXand
Network
Workstation
[via cable]
6-36
SEP '95
6 Cabling the INTERVIEW ArM Models
D8-3/E3/ST5-1
A
IRX
81 1
Y
I
TXJ
RX MM
RX MM
. --...
s
B
TXJ
j
RX
~
SONETOC-3c
SINGI.ElMULTI·MODE
A
B
TXt
SONETOC-3c
SINGLE/MULTi-MODE
z
s
ClO
z
S
X
X
~
y
1
OPTIONAL: "S" and "Y" Maptors for SC connectors
1
s
y
RX
Workstation
Figure 6-34 Monitoring Using Splitters Close to Network Termination with Multi-Mode Fiber Optic Cables.
SEP '95
6-37
INTERVIEW 8000 Series - ArM (Broadband): 985-B0682-01
6.12 Multi-Mode Fiber Optic Cabling Diagrams for Emulation
The next few pages contain sample cabling diagrams for emulating transmissions with
multi-mode fiber optic cables. These can be adapted to other specific scenarios.
Emulating a Network and Monitoring Transmission Externally
with Multi-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Internal
WARNING: Single-mode Transmission LASER is active unless switch is OFF. (LED is dark when off.)
Do NOT activate LASER switches.
Label
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
X
Multi-Mode Fiber Optic Cables (Black), Male ST to Male ST
Y
Multi-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Male SC to Male ST
Z
Multi-Mode Fiber Splitter (Black Body, Black Cable,
Black Connector), Male ST to 2 Male ST
Cables marked "1" and "2" each 50%
From
To
Workstation
A:RX
A: TX/MM
Workstation and
B: RX
SEP '95
6-38
---
~~~
~
~
..
-.- .. -- .. -.-.-.-~
-.--•..
-.----~-.--
.~~
- - -..
S cabling the INTERVIEW ATM Models
D8-3/E31STS..1 '
A
IRX
B
TXt
SONETOC-3c
SINGLElMULTf..MODE
A
B
I
AX
AJ~-P 0 0
SONETOC-3c
SINGLE/MULTl"MODE
TXt
RX MM
LASER'
TX/SM
'TX/
AX MM
I
x
OPTIONAL: "S" Couplers and "y"
Adaptors for SC connectors; also.
may need additional "X" cable as
shown
1 - - - - - - t RX
Workstation
Figure 6-35 Emulating a Network with Multi-Mode Fiber Optic Cables and monitoring transmission externally.
SEP '95
6-39
._-_._ _.__._._-----_.__._.__.__._----_._-_ __ _-----....
...
..
-_._-_.
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
Emulating a Network and Monitoring Transmission Internally
with Multi-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Internal
WARNING: Single-mode Transmission LASER Is active unless switch is OFF. (LED is dark when off.)
Do NOT activate LASER switches.
Label
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female 8T
X
Multi-Mode Fiber Optic Cables (Black), Male STto Male ST
Y
Multi-Mode ST to SC Adaptor (Blue Connector,
Yellow Band), Male SC to Male ST
6-40
From
To
Workstation
A: TX/MM
A: RX
Workstation
SEP '95
§ Gabling the INTERVIEW ATM Models
DS-3/E3/STS-1
A
'me
B
TXI
RX
SONETOC..ac
SINGLE/MULTI-MODE
SONEToc-3c
SINGLElMULn-MODE
A
B
'TXt
me MM
LASERI
TXlSM
r4--U'.P 0 0 I
OPTIONAL: "S" Couplers and "Y"
Adaptors for SC connectors
RX
Workstation
Figure 6-36 Emulating a Network with Multi-Mode Fiber Optic Cables and monitoring transmission internally.
SEP '95
6-41
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
Emulating a Workstation and Monitoring Transmission Externally
with Multi-Mode Fiber
Mode: Emulate A
Connector: Fiber
Clock Source: Receive Data
WARNING: Single-mode TransmIssion LASER is active unless switch is OFF. (LED is dark when off.)
Do NOT activate LASER switches.
Labe
Description
S
Single-Mode or Multi-Mode Coupler (all Metal),
Female ST to Female ST
X
Multi-Mode Fiber Optic Cables (Black). Male ST to Male ST
Y
Multi-Mode ST to SC Adaptor (Blue Connector,
Yellow Band). Male SC to Male ST
Z
Multi-Mode Fiber Splitter (Black Body, Black Cable,
Black Connector), Male ST to 2 Male ST
Cables marked "1" and "2" each 50%
6-42
From
To
Network
A: RX
A: TX/MM
Network and
B: RX
SEP'95
(;) Cabling t17e INTERVIEW ATM Models
SONETOC-3c
SINGLElMUL.Tf-MODE
A
DS-3/E3/STS-1
A
'RX
B
TXI
j
RX
TXJ
RX MM
SONETOC-3c
SINGL.ElMUL.Tf-MODE
B
I
TXJ
RX MM
x
OPTIONAL: "S" Couplers and "Y"
AtkJptorsfor SC connectors; also.
may need additional "X" cable as
shown
Figure 6-37 Emulating a Network with Multi-Mode Fiber Optic Cables.
SEP '95
6-43
INTERVIEW 8000 Series -ATM (Broadband): 985-B0682-01
6-44
SEP '95
7 ATM Interface Setup - AIM-302-1
7 ATM Interface Setup -
AIM-302-1
To reach the ATM Interface Setup screen. you must first access the Setup Menu (shown in
Figure 7-1) for the INTERVIEW ATM models. To do so, press 8
and
(If you are in the
Easy View menu system, you must first press (~i!i) before pressing 5'3 and ®J.)
em.
u
**
line Setup Screens
Line Setup
Record Setup
Displa!::J Setup
lLE
Interface Control
Bee
BeC Control
FEBUFE
Front-end Buffer Setup
EERI
Bit Error Rate Test Setup
AIM 302
Coaxial, multi-mode or single mode fiber
Figure 1·1 Softkey F6 on the Set\lp Menu indicates whi<:h ATM Interface Module is installed; shown here is AIM 302 for AIM-302-1
(OPT-9S1-302-1).
Note in Figure 7-1 that!f!l is labeled AIM 302. This means the currently installed AIM is the ATM
Interface Module (AIM): DS·3/E3/STS-l and SONET OC-3c and SDH STM-] Single-Mode and
Multi-Mode Optical (AIM-302-1). Press@ to access the ATM Interface Setup screen for that
installed AIM.
The fields on the ATM Interface Setup screen enable the user to select the mode, along with the
type of connector and framing, and all other parameters to monitor and emulate ATM cells in the
INTERVIEW ATM models as listed in this section. Figure 7-4, Figure 7-5, and Figure 7-8 list all
possible ATM Interface Setup selection parameters when in Monitor mode, Emulate A and
Internal Loop A modes, and Emulate B and Internal Loop B modes, respectively for AIM-302-1.
Each of these selections is discussed in the following pages.
SEP '95
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
7.1
Testing ATM without Concurrent WAN Protocols
Before you set up the ATM interface, consider that you may configure the INTERVIEW
8800 PLUS ATM to use additional processing space for ATM testing which would be
otherwise allocated for WAN testing. Unless you are going to test other underlying WAN
protocols via the Test Interface Module, you may "turn off" the WAN test processors and
allocate that memory to the ATM functions.
From the Setup Menu shown in Figure 7-1, press iTIJ to access the Line Setup screen and
press [ill DISABLE. Then press 8, (B] SETUp, and 1m to access the ATM Interface
Setup screen for the installed AIM.
Note that the Interface Control, BCC Control, Front-end Buffer Setup, and Bit Error Rate Test Setup
lines on the Setup Menu screen (shown in Figure 7-1) do not appear and the softkey labels
for @, ®], IE], and [§J are blank as you have just disabled these standard functions on the
Line Setup screen.
7.2
Testing WAN Protocols Concurrently with ATM
Before you setup the ATM interface on the INTERVIEW 8800 PLUS ATM, press !TIl to
access the Line Setup screen and make your selections as always for the protocol to be
tested via the Test Interface Module. Then press ~, lID SETUp, and @ to access the
ATM Interface Setup screen for the installed AIM.
(Note that on the Setup Menu, @ will only be labeled BERT if BERTDCE or
BERTDTE has been selected as the Mode on the Line Setup Screen;
otherwise (ffi will have no label and no line of explanation for Bit Error Rate
Testing will appear on the screen.)
7.3
Mode·
The Mode selection field allows you to select the expansion unit operating mode. The
choices are~~!:, ~M~~j~, ,~~',tiiiTi;Obe~i~~.j:l ,and!j~ (the
default).
When Mode: • •~.... is displayed, no other fields are selectable or visible. Whichever of
the other modes you select determines which subsequent fields appear.
Figure 7-2 Disable mode; note there are no related fields.
The other modes and their related fields are described in the following subsections.
7-2
SEP '95
7 ATM Interface Setup - AlM-302-1
7.4
Monitor Mode
Figure 7-3 is an example screen with some of the fields available in the Monitor mode. AU
possible Monitor mode fields and their parameters are given in the diagram illustrated in
Figure 7-4.
**
ace Setup
**
Mode:
Maintain:
Reload:
onnector:
raming:
igh Gain Si
11 Mapping:
Line Impedance:
Ce 11 Format:
•
Figure 7·3 Sample Monitor mode ATM Interface SetUp screen for AIM-302-I.
(A) Connector
Select the type of connector you are using. Select from~1 and ;.~£t&;t); the
field defaults to coax. Coaxial connectors deliver electrical signals over copper wire;
fiber connectors deliver optical signals over glass fiber. The type of connector
determines the line framing selections explained in subsection (B), below.
(8) Framing
Select the line framing in this field; the default is DS3 for coax cable and STS-3C for
fiber. If you are using a coaxial connector, the Framing field offers three choices:
!)$;f+'l~?i~3 ,i:~;~~Itl, and'i$t~11n'~ . If you have selected fiber
mode, you may select either~ or_1i';~~1:.
(C) High Gain Side A (and 8)
Use the defaults High Gain Side A:
and B: . . '•.9N for receivers on lines with normal
levels of 0 dB and below. For lines with higher than normal levels, turn off the gain
for Side A, Side B, or both to avoid saturation of the receiver. This field is only
applicable for coaxial connectors.
SEP '95
7-3
INTERVIEW 8000 Series -
ATM (8roadband): 985-80682-01
ATM Interface Setup
Mode:
Select Expansion Unit Operating Mode:
M NIT R EMUlATE A
EMUlATE B
'NT LOOP A
!NT LOOP B
DISABLED
Connector: SeIec1 Connector:
Framing:
Select Line Framing:
DS3 44 736 MBPS
E3 34 368 MBPS
I
High Gain Side A: Select High Gain on Side A:
B: Select High Gain on Side B:
ON
ON
STS·' 51.940 MBPS
I
J
OFF
OFF
Cell Mapping:
SPE CeJIMapping:
Select Cell Mapping Oefineation • Use 57-Octel PLCP for SMOS:
53-0CTET DIRECT 57-OCTET PLCP
Seiect SPE Cell Mapping:
8S COUJMNS 84 COUJMNS
Une Impedance:
Select Une Impedance:
75 OHMS
I
120 OHMS
Maintain:
Maintain Inletface Slate After Run?
Reload:
Expansion Unit Reload Control:
Cell Format:
Select ATM UNI Or SMDS Cell Format:
HEC Correction:
Payload Scrambling:
YES
NEVER
NO
AT RECOMPILE
ATM UNI
EVERY RUN
SMOS
Enable HEC Correction Fot Single-Bit Cell Header Errors?
Enable Scrambling/DeSctambiing For The Cell Payload?
ENABLE
ENABLE
DISABLE
DISABLE
Figure 1-4 ATM Interface Setup menu for Monitor mode for AIM-302-1.
(D) Cell Mapping
This field only appears when a DS3 or E3 coaxial cable is selected in the Framing field.
The cell mapping delineation choices are,~+!#irru~~Bm'i and 1¥;f;1~~~§r:f~i/
Choose the
selection when testing on SMDS (Switched
Multimegabit Data Service) lines; the field defaults to 53-octet direct.
(E) SPE Cell Mapping
This field only appears when an STS-l coaxial cable is selected in the Framing field.
The Synchronous Payload Envelop (SPE) cell mapping delineation choices are
~~li and 'H~~• •
(F) Line Impedance
When an E3 coaxial cable is selected in the Framing field, you must also select the line
impedance in this field; the Una Impedance field only appears when Framing:
<~e,.~~i is selected. Select Line Impedance: l~~ or :1~~; the default is
75 ohms and it is the normal selection. At this writing, 120 ohms is used only in
France.
7-4
SEP '95
ADDENDUM
7 ATM Interlace Setup - AIM..,302-1
(G) Maintain
Ii you wish to maintain the interface state after the run, accept the default, ~~ii~~[I;
otherwise change the Maintain field selection to i,.~fi'f!;j
(H) Reload
You can control the expansion unit software reloading times. Choose Reload:
lJ.'{~~{
iiff-lt_Hi})ii
··''"'-'x,,,,,,,,,,,.,,.
~,",." ll1'#41jW?VpmW
~, or IBifF~W;'
.... ·..
".~"" the default ,.~",,_
'''*'''n is recommended •
h •••
,'. • • ·•••
(I) Cell Format
Select . _ or ~ cell format; the field defaults to ATM User Network
Interface. When Cell Format: ~{ is selected, the next two fields appear.
(J) HEC Correction
Ii you wish to enable Header Error Control correction for single-bit cell header
errors, select W• •t. the default; otherwise, change the HEC Correction field to
The HEe consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when CeO Fonnat: _ _ is selected.
.:nE.
(K) Payload Scrambling
You may enable scrambling and descrambling for the cell payload by selecting the
default tll:IE; otherwise, disable the feature by selecting Payload Scrambling: "11.
This field only appears when Cell Format: ~~ is selected.
7.5
Emulate A and Internal Loop A Modes
The diagram illustrated in Figure 7-5 lists all possible Emulate A mode and Internal Loop
A mode fields and their parameters. Figure 7-6 is an example screen with some of the
fields available in the Emulate A and Internal Loop A modes.
NOTE: Internal Loop A and B modes loop the signalsinternaHy to the
unit. They are useful in testing the unit for correct operation and for
becoming familiar with the unit when unable to connect to a live network.
I
When connected to a live network, be aware that the transmit circuit is
active: the signal you are looping back to test is also being transmitted out
on the network.
(A) Connector
SeleCt the type of connector you are using. Select from ~~il and m.~~); the
field defaults to coax. Coaxial connectors deliver electrical signals over copper wire;
fiber.connectors deliver optical signals over glass fiber. The type of connector
detemrines the line framing selections explained in subsection (B), below.
NOV'95
-------_..-.. -.--.--------.---.----.~---,
7-5
ADDENDUM
INTERVIEW 8000 Series -ATM (Broadband): 985-80682-01
ATM
Mode:
EMUl..ATEA
MONITOR
Select Expansion UnH Operating Mode:
Interfa~!
SelYR
EMULATES
INTlOOPA
I
Connector:
SeIect~:
Framing:
Select Une Framing:
~~z;j§M8PS
TE-
E3 34.368 MBPS
ON
ON
OFF
OFF
I
Cell Mapping:
Select Cell Mapping Delineation· Use 57-octet PlCP for SMOS:
53-OC'TET DIRECT 57-OCTETPLCP
I Une Impedance:
Select Une Impedance:
Monitor Transmission:
Clock Source:
INTERNAlLY
Select Transmil Monitor:
STM-1 155.520 MBPS
I
t SPE Cell Mapping:
Select SPE Cell Mapping:
sa COLUMNS 84 COLUMNS
I
EXTERNALLY
INTERN OSCILLATOR
Select ltansrnit Clock Source:
Build OUt: Select Urle Build Out Based On Cable Length:
Maintain Interlace Stale After Run?
ar
120 OHMS
75 OHMS
I
Maintain:
I
DISABLED
ISTS·3C 155.520 MBPS
I
ST8-151.840MBPS
!
High Gain Side A: Select High Gain on Side A:
B: Select High Gain on Side B:
INTLOOPB
I
LESS THAN 225 FT
Expansion Unit Reload Control:
Cell Format:
Select ATM UNI Or SMOS Cell Format:
EXTERNAL SYNC
GREATER THAN 225 FT
I
I
YES
Reload:
RECEIVE OATA
NO
AT RECOMPILE
NEVER
EVERY RUN
...§t.4~
~
HEC Correction:
Enable HEC Correction For Singte-Bit Cell Headef Errots?
ENABLE DISABLE
Payload Scrambling:
Enable ScramblingJ(lescrambling For The Cell Payload?
ENABLE DISABlE
Tx Idle Cell Type:
Tx Idle Cell Type:
Select CLP=o, CLP=l, Or CU6IQm Xmn Idle Celllype:
UNASSIGNED
IDLE
Select Empty Or CUlltom Xmit Idle Cell Type:
~
EMPTY
~
Transmit Idle Header values:
ACF: Override ACF For Trall$01itted Idle Cells WIth {(x)'FF):
Transmit Idle Header values:
GFC: Override GFC For Transmitted Idle Cells With (o-F): 0
VP:
Override WI For Transmilled Idle CeII3 With (OO-FF):
VC:
Override VCI For Transmitted Idle Cells With (OOOO-FFFF):
PT:
Override PT For Transmitted Idle Cells WIth (0-7):
CLP:
Override CLP For Transmilted Idle Cells With (0-1):
NCI:
00
0000
Ovenide NCI For Transmilled Idle Cells With (OOOOOO-FFFFFF):
00000o
Idle Cell Payload:
Override 48-OGtet Idle Cell Payload value With ((X).FF):
0
00
00
0
NOTES:
Idle Cell Payload:
Override 48-0ctet Idle Cell Payload Value With (00-fF):
00
1 Not available in INT LOOP A mole.
Figure 7·5 ATM Interface Setup menu for Emulate A and Int Loop A modes for AIM-302-1.
7-6
NOV'95
7 ATM Int'r/aptl Setup - AlM-3D2-1
(B) Framing
Select; the line framing in this field; the default is DS3 for coax cable and STS-3C for
fiber. :If you are using a coaxial connector, the Framing field offers three choices:
l~., !i,• • •J.iJiWJ:, and ~~:lA~i. If you are in fiber mode,
you may select elther ..~'(-y~"
\ . , ;,;~tMiliMitJii$.i!d or \1.J~~~"'>'
!!", ,':,;,M!&i!&;:::;;~ii.
.
(C) High Gain Side A (and B)
. Use tbe defaults High Gain Side A: ~.~ and B:
for receivers on lines with normal
levels of 0 dB and below. For lines with higher than normal levels, turn off the gain
for Side A, Side B, or both to avoid saturation of the receiver. This field is only
applioable for coaxial connectors.
(D) Cell Mapping
This field only appears when a DS3 or E3 coaxial cable is selected in the Framing field.
The cell mapping delineation choices are ~~~1 and ~l~_lliti.
Choose the _ _~ selection when testing on SMDS (Switched
Multimegabit Data Service) lines; the field defaults to 53-octet direct.
(E) SPE Cell Mapping
This field only appears when an STS-l coaxial cable is selected in the Framing field.
The Synchronous Payload Envelop (SPE) cell mapping delineation choices are
}~landf~!.
(F) Monitor Transmission
This field only appears when in emulate mode; you must elect whether to monitor the
transrtussion internally or externally.
When you are in Emulate A mode and you select the default Monitor Transmission:
!~~. the INTERVIEW automatically monitors the transmission.
If instead you choose MoniIQr Transmission: t. . . ., the following is applicable for
the connection you are using.
1.
Coaxial connector. When you are using a coaxial connector and you select Monitor
Tl'ansml$$ion: ~,
you must use a monitor pad to split off the monitoring
cable to the DS-3/E3/STS-l B: RX coaxial connection to monitor the
transmission. This cabling situation is illustrated in Figure 6--23.
2
SEP '95
Single-mode fiber connector. When you select Monitor Transmission: 'ii~~il, you
must use a splitter cable to split off the monitoring cable to the single/multi-mode
B: RX fiber connection. This single-mode cabling is illustrated for Emulate A
mode in Figure 6--29. where the splitter cable spJits off from A: TXlSM to B: RX
to monitor the transmission.
7-7
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
3.
Multi-mode fiber connector. When you select Monitor Transmission: i,,~~'t;:, you
must use a splitter cable to split off the monitoring cable to the single/multi-mode
B: RX fiber connection. This multi-mode cabling is illustrated for Emulate A
mode in Figure 6-35, where the splitter cable splits off from A: TXJMM to B: RX
to monitor the transmission.
(G) Line Impedance
When an E3 coaxial cable is selected in the Framing field, you must also select the line
impedance in this field; the Une Impedance field only appears when Framing:
j;t\t,.!!._t~f1i is selected. Select Line Im,)edance: i,ii~: or iiii~; the default is 75
ohms and it is the normal selection. At this writing, 120 ohms is used only in France.
(H) Clock Source
Select the transmit Clock Source: 1~_)~rqff:;!, W;r~BS;lEw~8. or
f,t)w~_1!fit The field defaults to internal oscillator, in which the unit uses
internal crystals for timing; use this selection when emulating the network. When
emulating a workstation, select ClOCk source:@jf~Mi~_!iirim.
(I) Build Out
Select the line build out based on the cable length, whether the cable length is less
than 225 feet or whether it is greater than (or equal to) 225 feet. Choose either Build
Out: !{ii!~~._"t~;ii (the default) or f~_~~;.
(J) Maintain
If you wish to maintain the interface state after the run and maintain the customer
link, accept the default, ~~}!.Th%; otherwise change the Maintain field selection to
'l,~!;~gWJr and the unit will change to Monitor mode afte·r the run.
(K) Reload
You can control the expansion unit software reloading times. Choose Reload:
.~;, orm~1iIi,IR!j!~; the default,
, is recommended.
iMiIi• •\i(\~;1
(L) Cell Format
Select ;~mR or ~iii_[t cell format; the field defaults to ATM User Network
Interface. When Cell Format: ~I~III!ii is selected, the next two fields appear.
(M) HEC Correction
If you wish to enable Header Error Control correction for single-bit cell header
errors, select :i;:i~i, the default; otherwise, change the HEC Correction field to
:;~. The HEC consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when Cell Format(~li..;, is selected.
7-8
SEP '95
7 ATM IntertaceSetup -AlM-302-1
Mode:
Maintain:
Reload:
Connector:
Framins:
HiSh Gain Si e
Cell Mapping:
Ce 11 Format:
nitor Transm
lock Source"
iId Out:
HEC Correction:
Pa~load Scrambling:
Tx Idle Cell T~pe:
Transmit Idle Header Values:
GFC:a VP:~ VC:~ PT:a CLP:E
Idle Cell Pa~load: ~
n?
Fipre 7,,(, Sample Emulate A mode ATM Interface Setup screen for AIM-302-1. These· same fields are applicable for Internal Loop A
mode for AIM-302-l.
(N) PayloadScrambiing
You may enable scrambling and descrambling for the cell payload by selecting the
default lli;:.~~; otherwise, disable the feature by selecting Paytoad Scrambling: :~~1.
This field only appears when Cell Format: _ _ is selected.
(0) Tx Idle Cell Type
The selections presented are dependent upon the cell format selected as described in
subsection (L), above.
1. ATM UNI Cell Format When Cell Format: IlIIIf is selected. you may select
Tx Idle Cell 1'Jpe: lW.JIlJ!I (the default) for CLP=O. ~'1~"I.~ for CLP= 1, or
I[l_.~ to design your own. When ~$.i is selected, six header value
subfields appear, as described below in subsection (P).
2. SMDS Cell Format. When Cell Fonnat:iEI is selected, select Tx Idle Cell Type:
g~J (the default) when the cells are empty or ~~ to design your own.
When f~~* is selected, three header value subfields appear, as described
below in subsection (P).
(P) Transmit Idle Header Values
The subfields presented are dependent upon the cell format selected as described in
subsection (0), above. Each cell format displays its own specific 1i'ansmit Idle
Header Value fields.
SEP '95
7-9
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(P) Transmit Idle Header Values
The subfields presented are dependent upon the cell format selected as described in
subsection (0), above. Each cell format displays its own specific Transmit Idle
Header Value fields.
ATM UN] CeU Formal. When Tx Idle Cell Type: ~it~~t%~ is selected, when you are
emulating (A or B) or using intemalloopback mode, and when you are using the
ATM UNI cell format, six subfields of the Transmit Idle Header Values heading appear.
You can select to transmit your own idle header values for GFC (Generic Flow
Control), VPI (Virtual Path Identifier), VCI (Virtual Circuit Identifier), PT (Payload
Type), CLP (Cell Loss Priority), and the 48-octet Idle Cell Payload value.
1.
GFC. You may override GFC (Generic Flow Control) for transmitted idle cells by
entering a single-digit hex character, O-E, in this field. The default is O.
2.
VP. You may override VPI (Virtual Path Identifier) for transmitted idle cells by
entering a two-digit hex character, oo-FF, in this field. The default is 00.
3.
Vc. You may override VCI (Virtual Circuit Identifier) for transmitted idle cells by
entering a four-digit hex character, OOOO-FFFF, in this field. The default is 0000.
4.
PT. You may override PT (Payload Type) for transmitted idle cells by entering a
single-digit hex character, 0-7, in this field. The default is O.
5.
CLP. You may override CLP (Cell Loss Priority) for transmitted idle cells by
entering a 0 or 1 in this field. The default is 0, indicating the cell must be
transmitted; 1 indicates the cell may be discarded.
6.
Idle Cell Payload. You may override the 48-octet Idle Cell Payload value by entering
a two-digit hex character, oo-FF, in this field. The default is 00.
SMDS CeU Format. When Tx Idle CeIl1\tPe:
is selected, when you are
emulating (A or B) or using internalloopback mode, and when you are using the
SMDS cell format, three subfields of the Transmit Idle Header values heading appear.
7-10
1.
ACE You may override ACF (Address Control Field) for transmitted idle cells by
entering a two-digit hex character, oo-FF, in this field. The default is 00 for an empty
cell; enter 80 for a busy ceIL
2.
NCI You may override NCI (Network Control Information) for transmitted idle
cells by ent~ring a six-digit hex character,OOOOOO-PPPFFF, in this field. The default
is 000000 for empty cells; enter FFFFFO for full cells.
3.
Idle Cell Payload. You may override the 48-octet Idle Cell Payload value by entering
a two-digit hex character, OO-FF, in this field. The default is 00.
SEP'95
ADDENDUM
7 ATM Interface Setup - AlM-302-1
7.6
Emulate B and Internal Loop B Modes
Figure 7-7 is an example screen with some of the fields available in the Emulate Band
Internal Loop B modes. All possible Emulate B mode and Internal Loop B mode fields
and their parameters are given in the diagram illustrated in Figure 7-8. Note that only
fiber optic connectors are available for selection.
NOTE: Internal Loop A and B modes loop the signals internally to the
unit. They are useful in testing the unit for correct operation and for
becoming familiar with the unit when unable to connect to a live network.
I
When connected to a live network, be aware that the transmit circuit is
active: the signal you are looping back to test is also being transmitted out
on the network.
ace Setup
**
Mode:
Maintain:
Reload:
Connector:
Framing:
Cell Format:
-
Tx Idle Cell T~pe:
Transmit Idle Header Values:
ACF:Ea NCI: 000000
Idle Cell Payload:
aa
Figure 7·7 Sample Emulate B mode ATM Interface Setup screen for AIM·302·1. These same fields are applicable for Internal Loop B
modefor AIM-302-1.
(A) Connector
For Emulate B and Internal Loopback B modes, the only viable type of connector is
the default Itllii; there is no other choice. The type of connector determines the
line framing selections explained in subsection (B), below.
(8) Framing
Select the line framing in this field; the default is STS-3C. For both multi- and
single-fiber mode connectors, you may select either i~ii_ii'§~ or
1~,""; framing.
NOV'95
7-11
ADDENDUM
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
.
ATM Interface Setup
Mode:
Select Expansion Unit Operating Mode:
MONITOR
eMULATE A
eMULATE
a
INT lOOP A
INT LOOP
I
Connector:
Select Connector:
Framing:
Select Une Framing:
Monitor Transmission~
Se}e(;l Transmit Monitor.
Clock Source:
Select TtanSmit Clock Souree:
DISABlED
ABER 1
STS-3C 155.520 MBPS
INTERNAlLY
STM-l 155.520 Maps
EXTERNALLY
INTERN OSCIllATOR
Maintain:
Maintain Interface State After Run?
Reload:
Expansion UnH Reload Control:
Cell Format:
a
l
J
YES
NEVER
RECEIVE DATA
EXTERNAL SYNC
NO
AT RECOMPIlE
EVERY RUN
Select ATM UNI Or SMOS Ceil Format:
HEC Correction:
EnabI& HEC Correction For Single-Bit Cell Header Errors?
ENABlE
DISABLE
Payload Scrambling:
Enable ScrambIing/Oesambling For The Ceil Payload?
ENABLE
DISABlE
Tx Idle Cell Type:
Select EIllJIY Or custom Xmil Idle Ceu Type:
Tx Idle CeO "fYpe:
Select Ctp .. o, CLP= 1, Or Custom Xmit IdIt Cell Type:
UNASSIGNED
IDLE
mr
EMPTY
Transmit Idle Header Values:
GFC: Override GFC For Transmitted Idle Cells With (O-F):
~.
...
Transmit Idle Header Values:
AFC: Override AFC For Transmitted Idle Cells WiIh (OO-FF):
0
NCI:
VP:
Override VPI For Transmitted Idle Cells With (OO-FF):
VC:
Override VCI For Transmitted Idle Cells WIth (OOOO-FFFF): 0000
PT:
Override PT For Transmitted Idle Cells With (0-7):
00
Override NCI For Transmitted Idle Cells With (Oooooo-FFFFFF):
00000o
Idle Cell Payload:
Override 48-Octet Idle CeO Payload Value With (OO-FF):
0
00
00
CLP: Override CLP For Transmitted Idle Cells With (0-1): 0
NOTES:
Idle Cell Payload:
Override 48-0ctet Idle Cell Payload Value With (OO-FF):
00
1 ABER is the only viable connector for EMULATE B and
INTERNAL IOOPBACK B modes; no other chOice is available.
2 Monitor Transmission field Is not available in INT LOOP B mote.
Figure 7-8 ATM Interface Setup menu for Emulate Band Int Loop B modes for AIM-302-l.
(C) Monitor Transmission
This field only appears when in emulate mode; you must elect whether to monitor the
transmission internally or externally.
When you are in Emulate B mode using fiber cables and connectors and you select the
default Monitor 1i'ansmission:~il, the INTERVIEW automatically monitors the
transmission.
If instead you choose Monitor Transmission:~ti, the fOllowing is applicable for
the connection you are using.
1.
7-12
Single-mode fiber connector. When you select Monitor Transmission::~', you
must use a splitter cable to split off the monitoring cable to the single/multi-mode
NOV'95
7 ArM Interface Setup - AlM-30?-1
A: RX fiber connection. This cabling is similar to the situation illustrated for
Emulate A mode in Figure 6-29 (single-mode), except that the splitter cable
would split off from B: TXlSM to A: RX to monitor the transmission.
2.
Multi-mode fiber connector. When you select Monitor Transmission: {~, you
must use a splitter cable to split off the monitoring cable to the single/multi-mode
A: RX fiber connection. This cabling is similar to the situation illustrated for
Emulate A mode in Figure 6-35 (multi-mode), except that the splitter cable
would split off from B: TX/MM to A: RX to monitor the transmission.
(0) 010'* Source
(E) Maintain
If you wish to maintain the interface state after the run and maintain the customer
link, accept the default, ~~; otherwise change the Maintain field selection to
~_~ and the unit will change to Monitor mode after the run.
(F) Reload
You can control the expansion unit reloading times. Choose Reload: '0i';k1iM~~!~1
&_:IMJI~, or !Ji.I,.ti; the default, itl~~I, is recommended.
._1
(G) Cell Format
Select
or *~:iiii~ cell format; the field defaults to ATM User Network
Interface. When Cell Format: ~ is selected, the next two fields appear.
(H) HEC Correction
If you wish to enable Header Error Control correction for single-bit cell header
errors, select ~1IIiI~, the default; otherwise, change the HEC Correction field to
~._. The HEC consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when CeO Format: 18B~ is selected.
(I) Paytoad Scrambling
You may enable scrambling and descrambling for the cell payload by selecting the
default r.IC~!; otbetwise. disable the feature by selecting Payload Scramblin9:i~; .
This field only appears when Cell Format: _W2 is selected.
SEP '95
7-13
~------------.--
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(J) Tx Idle Cell Type
The selections presented are dependent upon the cell format selected as described in
subsection (G), above.
1. ATM UNI Cell Format. When Cell Format:l~l is selected, you may select
Tx Idle Cell Type: ~•. (the default) for CLP=O,
for CLP= 1, or
~1i~l~ to design your own. When :::t~";[;J. is selected, six header value
subfields appear, as described below in subsection (K).
2.
SMDS Cell Format. When Cell Format:
is selected, select Tx Idle Cell Type:
iIIBE% (the default) when the cells are empty or l~~lt to design your own.
When ;~!;(• •J~J is selected, three header value subfields appear, as described
below in subsection (K).
(I<) Transmit Idle Header Values
The subfields presented are dependent upon the cell format selected as described in
subsection (J), above. Each cell format displays its own specific Transmit Idle Header
Value fields.
ATM UNf Cell Format. When Tx Idle Cell Type:
is selected, when you are
emulating (A or B) or using internalloopback mode, and when you are using the
ATM UNI cell format, six subfields of the Transmit Idle Header Values heading appear.
You can select to transmit your own idle header values for GPC (Generic Flow
Control), VPI (Virtual Path Identifier), VCI (Virtual Circuit Identifier), PT (Payload
'JYpe), CLP (Cell Loss Priority), and the 48-octet Idle Cell Payload value.
1.
GFC. You may override GFC (Generic Flow Control) for transmitted idle cells
by entering a single-digit hex character, O-F, in this field. The default is O.
2.
VP. You may override VPI (Virtual Path Identifier) for transmitted idle cells by
entering a two-digit hex character, ()(}-FF, in this field. The default is 00.
3.
Vc. You may override VCI (Virtual Circuit Identifier) for transmitted idle cells by
entering a four-digit hex character, OO()(}·FFFF, in this field. The default is 0000.
4.
PT. You may override PI" (Payload Type) for transmitted idle cells by entering a
single-digit hex character, 0-7, in this field. The default is O.
5.
eLp. You may override CLP (Cell Loss Priority) for transmitted idle cells by
entering a 0 or 1 in this field. The default is 0, indicating the cell must be
transmitted; 1 indicates the cell may be discarded.
6.
Idle Cell Payload. You may override the 48-octet Idle Cell Payload value by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
7-14
SEP '95
7 ATM Interface Setup - AlM-302-1
SMDS Cell Format. When Tx Idle Cell Type: ;:i,~~~l~ is selected, when you are
emulating (A or B) or using internalloopback mode, and when you are using the
SMDS cell format, three subfields of the Transmit Idle Header Values heading appear.
SEP '95
1.
ACE You may override ACF (Address Control Field) for transmitted idle cells
by entering a two-rligit hex character, OO-FF, in this field. The default is 00 for an
empty cell; enter 80 for a busy cell.
2.
NCI. You may override NCI (Network Control Information) for transmitted idle
cells by entering a six-digit hex character, OOOOOO-FFFFFF, in this field. The
default is 00000o for empty cells; enter FFFFFO for full cells.
3.
Idle Cell Payload. You may override the 48-octet Idle Cell Payload value by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
7-15
.---------------------------
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
7-16
SEP '95
8 ATM Interface Setup - AlM-305-1
8 ATM Interface Setup - AIM-305-1
To reach the ATM Interface Setup screen, you must fU'St access the Setup Menu (shown in
Figure 8-1) for the INTERVIEW ATM models. To do so, press 8
and ITIJ. (If you are in the
Easy View menu system, you must first press 8 before pressing 5
and (ffi.)
nu
**
Line Setup Screens
Line Setup
Record Setup
Displa\::l Setup
lLE
Interface Control
BQC
BCC Control
FEBUFF
Front-end Buffer Setup
BERI
Bit Error Rate Test Setup
8IM 305
Coaxial
Figure 8-1 Softkey F6 on the Setup Menu indicates which ATM Interface Module is installed; shown here is AIM 305 for AIM-305-1
(OPT-951-305-1).
Note in Figure 8-1 tbat I£ID is labeled AIM 305. This means the currently installed AIM is theATM
Physical Layer Interface Module: DS-3, £3, and STS-l (AIM-305-i). Press@ to access the ATM
Interface Setup screen for that installed AIM.
The fields on the ATM Interface Setup screen enable the user to select the mode, along with the
type of connector and framing, and all other parameters to monitor and emulate ATM ceUs in the
INTERVIEW ATM models as listed in this section. Figure 8-4 and Figure 8-6 list all possible ATM
Interface Setup selection parameters when in Monitor mode and either Emulate A or Internal
Loop A modes, respectively, for AIM-305-1. Each of these selections is discussed in the following
pages.
SEP '95
8-1
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
8.1
Testing ATM without Concurrent WAN Protocols
Before you set up the ATM interface, consider that you may configure the INTERVIEW
8800 PLUS ATM to use additional processing space for ATM testing which would be
otherwise allocated for WAN testing. Unless you are going to test other underlying WAN
protocols via the Test Interface Module, you may "turn off" the WAN test processors and
allocate that memory to the ATM functions.
From the Setup Menu shown in Figure 8-1, press [TIl to access the Line Setup screen and
to access the ATM Interface
press §) DISABLE. Then press S, (ill SETUp, and
Setup screen for the installed AIM.
rm
Note that the Interface Control, BCC Control, Front-end Buffer Setup, and Bit Error Rate Test Setup
lines on the Setup Menu screen (shown in Figure 8-1) do not appear and the softkey labels
for (W, ®J, !E], and IfID are blank as you have just disabled these standard functions on the
Line Setup screen.
8.2
Testing WAN Protocols Concurrently with ATM
Before you setup the ATM interface on the INTERVIEW 8800 PLUS ATM, press [TIl to
access the Line Setup screen and make your selections as always for the protocol to be
tested via the Test Interface Module. Then press ~, [ITJ SETUp, and 1m to access the
ATM Interface Setup screen for the installed AIM.
(Note that on the Setup Menu, (§) will only be labeled BERT if BERTDCE or
has been selected as the Mode on the Line Setup Screen;
otherwise [ffi will have no label and no line of explanation for Bit Error Rate
Testing will appear on the screen.)
BERTDTE
8.3
Mode
The Mode selection field allows you to select the expansion unit operating mode. The
choices are ~B~!t ,~~~ ,(!fitW,.I!::!;, and 1fP~gii (the default).
When Mode:i~i is displayed, no other fields are selectable or visible. Whichever of
the other modes you select determines which subsequent fields appear.
Figure 8-2 Disable mode; note there are no related fields.
The other modes and their related fields are described in the following subsections.
8-2
SEP '95
8 ATM Interface Setup - AlM-805-1
8.4
Monitor Mode
Figure &-3 is an example screen with some of the fields available in the Monitor mode. All
possible Monitor mode fields and their parameters are given in the diagram illustrated in
Figure 84.
tup
Mode:
**
Maintain:
Reload:
Framing:
igh Gain Si
Cell Mapping:
Line Impedance:
Cell Format:
HEC Correction:
Pa~load Scrambling:
FIgUre 8-3 Sample Monitor mode ATM Interface Setup screen for AIM-305-1.
(A) Framing
Selectthe line framing for coaxial cable in this field; the default is OS3. The Framing
field offers three choices: £1f~HII.::iil'%; ,I~{~._;~, and :~~_~,~.
(8) High Gain Side A (and B)
Use the defaults High Gain Siele A:
and 8:00, for receivers on lines with normal
levels of 0 dB and below. For lines with higher than norma11evels. turn off the gain
for Side A, Side B, or both to avoid saturation of the receiver.
(C) Cell Mapping
This field only appears when a OS3 or E3 coaxial cable is selected in the Framing field.
The cell mapping delineation choices are(;,)~¥JOt$1~i:t~ and~'~~~R1i;~;[i.
Choose the j1\1*~#;t· selection when testing on SMDS (Switched
Multimegabit Data Service) lines; the field defaults to 53-octet direct.
(0) SPECell Mapping
This field only appears when an STS-l coaxial cable is selected in the Framing field.
The Synchronous Payload Envelop (SPE) cell mapping delineation choices are
,~ii~ and l%il_.i.
SEP'95
8-3
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
(E) Line Impedance
When an E3 coaxial cable is selected in the Framing field, you must also select the line
impedance in this field; the Une Impedance field only appears when Framing:
l;i\~ji~~;~~:tr::!; is selected. Select Une Impedance:
or \,'iJ~; the default is
75 ohms and it is the normal selection. At this writing, 120 ohms is used only in
France.
AIM Interface Setup
Mode:
Select expansion
Un~
Operating Mode:
EMULATE A
MONITOR
INTLOOPA
DISABLED
I
Framing:
Select Une Framing:
053 44.136 MaPS
E3 34.368 MBPS
STS-t 51.640 MBPS
I
High Gain Side A:
B:
Select High Gain on Side A:
Select High Gain on Side B:
ON
OFF
ON
OFF
I
I SPE Cell Mapping:
Cell Mapping:
Select SPE Cell Mapping:
86 COLUMNS 84 COLUMNS
Select Cell Mapping Delineation - Use 57-Octet PLCP for SMOS:
53-OCTET DIRECT 57-OCTET PLCP
Select Une Impedance:
75 OHMS
120 OHMS
Maintain:
Maintain 1!\IllI1ace Slate After Aun?
Reload:
Expanslon Un~ Reload Control:
Cell Format:
Select ArM UNI Or SMOS Cell Fonnat:
HEC Correction:
Payload Scrambling:
I
I
Une Impedance:
YES
NEVER
NO
AT RECOMPILE
~
EVEAYRUN
SMOS
Enable HEC Correction For Single-Bit Cell Header Errors?
Enable Scrambling/Descrambling For The Cell Payload?
ENABLE
ENABLE
OISASLE
DISABLE
I
Figure 8-4 ATM Interface Setup menu for Monitor mode for AIM-305-1.
(F) Maintain
If you wish to maintain the interface state after the run, accept the default, iW~~.·.
i
otheIWise change the Maintain field selection to
(G) Reload
You can control the expansion unit software reloading times. Choose Reload:
Nad; 3,;~T;~;;, or ~ltl~_t~:; the default,
, is recommended.
(H) Cell Format
Select~_~d or :f!~~,ii cell format; the field defaults to ATM User Network
Interface. When Cell Format: i.:JJiiii; is selected, the next two fields appear.
8-4
SEP'95
ADDENDUM
8 ArM Interlace Setup -
AlM~305-1
(I> HEC Correction
H you wish to enable Header Error Control correction for single-bit cell header
erroI'$, select ~'5, the default; otherwise, change the HEe Correction field to
The HEC consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when Cell Format: • • is selected.
II:..
(J) Payload Scrambling
You may enable scrambling and descrarobling for the cell payload by selecting the
default ~; otherwise, disable the feature by selecting Payload Scrambling: _~:'!.
This field only appears when Cell
is seJected.
Format:"
8.5
Emulate A and Intemal Loop A Modes
Figure 8-5 is an example screen with some of the fields available in the Emulate A and
Internal Loop A modes. All possible Emulate A mode and Internal Loop A mode fields
and their parameters are given in the diagram illustrated in Figure 8-6.
NOTE: Internal Loop A mode loops the signals internally to the unit. It is
useful in testing the unit for correct operation and for becoming familiar
with the unit when unable to connect to a live network.
When connected to a live network, be aware that the transmit circuit is
active: the signal you are looping back to test is also being transmitted out
on the network.
NOV'95
8-5
-------_._,., , - -
ADDENDUM
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
Mode:
Maintain:
Reload:
Framing:
High Ga inS i e
Cell Mapping:
Monitor Transmis
Clock Source'
Bu i 1d Out:
Ce 1 1 Format:
HEC Correction:
Pa~load Scrambling:
ClJSTC>1
Tx Idle Cell T~pe:
Transmit Idle Header Values:
GFC:a VP:0a VC:~ PT:a CLP:a
Idle Cell Pa8load: ~
Figure 8-5 Sample Emulate A mode ATM Interface Setup screen. These same fields are applicable for Internal Loop A mode for
AIM-305-1.
(A) Framing
Select the line framing for coaxial cable in this field; the default is DS3. The Framing
field offers three choices:'~~_V_ii~,ttf:'mili~i~~r;j:';, and ~;.~f::I._$iL
(B) High Gain Side A (and B)
Use the defaults High Gain Side A:
and B:
for receivers on lines with normal
levels of 0 dB and below. For lines with higher than normal levels, turn off the gain
for Side A, Side B, or both to avoid saturation of the receiver.
(C) Cell Mapping
This field only appears when a DS3 or E3 coaxial cable is selected in the Framing field.
The cell mapping delineation choices are
and 'i;!;;1~*~.[{~;~:;~
Choose the
selection when testing on SMDS (Switched
Multimegabit Data Service) lines; the field defaults to 53-octet direct.
(D) SPE Cell Mapping
This field only appears when an STS-l coaxial cable is selected in the Framing field.
The Synchronous Payload Envelop (SPE) cell mapping delineation choices are
;lii~~ and };~f·
8-6
NOV '95
ADDENDUM
8 ArM Interface Setup -
AlM~305-1
(E) Momtor Transmission
This field only appears when in emulate mode; you must elect whether to monitor the
transmission internally or externally. In Emulate A mode when you select the default
MonitOr Transmission: .Ii!lflll~, the INTERVIEW automatically monitors the
transmission.
When you are using a coaxial connector and you select Monitor Transmission: ~:,
you must use a monitor pad to split off a cable to the DS-3/E3/STS-l B; RX coaxial
connection to monitor the transmission generated by the INTERVIEW from the
A: TX connection. This cabling situation is illustrated in Figure 6-23.
(F) Une Impedance
When an E3 coaxial cable is selected in the Framing field, you must also select the line
impeqance in this field; the Une Impedance field only appears when Framing:
1~:I~ is selected. Select Line Impedance: ~ljt.JJ;' or _ ; the default is
75 ohms and it is the normal selection. At this writing, 120 ohms is used only in
France.
(G) Clock Source
.....
1--.1. "'_u_
~JW"'~
Select the transnut
......-..
-..-ce.• ~wrrr~~
i&~;'~.lft!l\~" ,,,Jt;%lA
,.,..... .
.W"" or
Bt~~. The field defaults to internal oscillator, in which the unit uses
internal crystals for timing; use this selection when emulating the network. When
emulating a workstation, select Clock SOurce: lf~%i.J._mt~.
(H) Build Out
Select the line build out based on the cable length, whether the cable length is less
than ~5 feet or whether it is greater than (or equal to) 225 feet. Choose either Build
Out: fi_ _BIB (the default) or t:~~.
(I) Maintain
If you wish to maintain the interface state after the run and maintain the customer
link, accept the default, 111111; othelWise change the MaIntain field selection to
lRit and the unit will change to Monitor mode after the run.
(J) Relqad
You can control the expansion unit software reloading times. Choose Retoad:
~~lR!I~~~, ~:;•• or fu~; the default, i-l~;f~. is recommended.
(K) Cell Format
Select lli~ or ~tr:il;e cell format; the field defaults to ATM User Network
Interface. When CeQ Format: ;ilBt is selected, the next two fields appear.
NOV'95
ADDENDUM
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
AIM Interface Setup
Mode:
Select Expansion Unit Operating Mode:
framing:
Select Una Framing:
MONITOR
093 44.1'38 MBPS
EMULATE A
INTLOOPA
I
I
E3 34.3!lS MBPS
STS-1S1.840MBPS
I
High Gain Side A: SeIeet High Gain on Side A:
B:
SeIecIl10gh Gain on Side B:
ON
OFF
ON
OFF
Cell Mapping:
I
Select Ce8 Mapping Delineation - Use 57-Oc1et PLCP for SMOS:
I
DISABLED
53-QC'TET DIRECT
Une Impedance:
Select una Impedance:
57«TET PLCP
75 OHMS
Select SPE Ce8 Mapping:
86 COLUMNS
84 COlUMNS
I
I
120 OHMS
Monitor Transmission? Select TransmIt Monitor:
SPE Cell Mapping:
INTERNALLY
EXTERNALLY
Clock Source:
Select Transm~ Clock Source:
Build Out:
Select Una Build Out Based On cable Length:
Maintain:
Maintain Interface State After Run?
Reload:
Expansion Unit Reload Control:
INTERN OSCILLATOR
YES
NEVER
Cell Format: Select ATM UNI Or SMOS Cell Format:
RECEIVE DATA
LESS THAN 22S FT
EXTERNAL SYNC
GREATER THAN 22S FT
NO
AT RECOMPILE
EVERY RUN
.§!!!2§.
~
HEC Correction:
Enable HEC Correction For Slngle-OO Cell Header Errors?
ENABLE DISABLE
Payload Scrambling:
Enable ScrambllngtDescrambling For The CeB Payload?
ENABLE DISABLE
Tx Idle Cell TYPe:
Tx Idle Cell Type:
Select Empty Or Custom Xrnit Idle Cell Type:
EMPTY
SeIecI CLF .. O, ClP= 1, Or Custom XrM Idle Cell Type:
UNASSIGNED
IDLE
~
~
Transmit Idle Header values:
AFC; Override AFC For Transmitted Idle Cells WIth (OO-FF):
Transmit Idle Header Values:
GFC: Override GFC For Transmitted Idle Cells With (O-F): 0
VP:
OverrIde VPI For Transmitted !die Cella WI1I1 «()O.FF):
NCI: Override NCI For Transmilled Idle Cells With
00
VC:
Override va For Transmitted Idle Cells With (OCJOO.FFFI'j:
PT:
Override PTForTransmiIted Idle Cells WIth (0-7):
00
(OOOOOO-FFFFFF):
00000o
0000
0
Idle Cell Payload:
Override 48-Octet Idle Cell Payload Value With (OO-FF):
00
CLP: Override CLF For TrsMmltted Idle Cells With (0-1): 0
Idle Cell Payload:
OverrIde 48-0ctet Idle Cell Payload Value With «()O.FF): 00
NOTES;
1 No! available in INT LOOP A more.
FIgUre 8-6 ATM Interface Setup menu for Emulate A and Internal Loop modes for AIM-305-1.
8·8
NOV '95
ADDENDUM
8 ATM Int§rface Setup - AlM-305-1
(L) HEC Correction
If you wish to enable Header Error Control correction for single-bit cell header
errors, select _.~, the default; otherwise, change the HEC Correction field to
~. The HEC consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when Cell Format: ~ is selected.
(M) PaylOad Scrambling
You may enable scrambling and descrambling for the cell payload by selecting the
default It_; otherwise, disable the feature by selecting Payload Scrambling: ,~;:,
This field only appears when Cell Format: ~ is selected.
(N) Tx Idle Cell Type
The selections presented are dependent upon the cell format selected as described in
subsection (K). above.
1. ATM UNI Cell Fonnat. When Cell Format: ~i: is selected, you may select
Txldle Cell ~ . _ 1 (the default) for CLP=O, iI_l~ for CLP= 1, or
_UBI to design your own. When 1~,1 is selected, six header value
subfields appear, as described below in subsection (0).
2.
SMDS Cell Format. When Cell Format: ~~ is selected, select Tx Idle Cell 'J\tpe:
~ (the default) when the cells are empty or ~IIIIJ to design your own.
When !{Ellil is selected, three header value subfields appear, as described
below in subsection (0).
(0) Tran$mit Idle Header Values
The subfields presented are dependent upon the cell format selected as described in
subsection (N), above. Each cell format displays its own specific Thmsmit Idle
Header Value fields.
ATM UNl Cell FonntJt. When Tx Idle Cell 'J\tpe: ~_.1111 is selected, when you are
emulating (A or B) or using intemalloopback mode, and when you are using the
ATM UN! cell format, six subfields of the Transmit Idle Header Values heading appear.
You can select to transmit your own idle header values for GFC (Generic Flow
Control), VPI (Virtual Path Identifier), VCI (Virtual Circuit Identifier). PT (Payload
Type). CLP (Cell Loss Priority), and the 48-octet Idle Cell Payload value.
NOV'95
1.
GFe. You may override GFC (Generic Flow Control) for transmitted idle cells
by entering a single-digit hex character, O-P, in this field. The default is O.
2.
VP. You may override VPI (Virtual Path Identifier) for transmitted idle cells by
entering a two.digit hex character. OO-FE, in this field. The default is 00.
8-9
ADDENDUM
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
3.
Vc. You may override VCI (Virtual Circuit Identifier) for transmitted idle cells by
entering a four-digit hex character, OOOO-FFFF, in this field. The default is 0000.
4.
PT. You may override PT (Payload Type) for transmitted idle cells by entering a
single-digit hex character, 0-7, in this field. The default is O.
5.
CLP. You may override CLP (Cell Loss Priority) for transmitted idle cells by
entering a 0 or 1 in this field. The default is 0, indicating the cell must be
transmitted; 1 indicates the cell may be discarded.
6.
Idle Cell Payload. You may override the 48-octet Idle Cell Payload value by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
When Tx Idle Cell Type: f!~;tl is selected, when you are
emulating (A or B) or using internalloopback mode, and when you are using the
SMDS cell format, three subfields of the Transmit Idle Header Values heading appear.
SMDS Cell Fomuzt.
1.
ACE You may override ACF (Address Control Field) for transmitted idle cells
by entering a two-digit hex character, OO-FE, in this field. The default is 00 for an
empty cell; enter 80 for a busy cell.
8-10
2.
NCL You may override NCr (Network Control Information) for transmitted idle
cells by entering a six-digit hex character, OOOOOO-FFFFFF, in this field. The
default is 00000o for empty cells; enter FFFFFO for full cells.
3.
Idle Cell Payload. You may override the 48-octet Idle Cell Payload value by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
NOV'95
.. ~"
9 ATM Interface Setup - AIM-306-1
9 ATM Interface Setup - AIM-306-1
To reach the ATM Interface Setup screen, you must first access the Setup Menu (shown in
Figure 9-1) for the INTERVIEW ATM models. To do so, press S and lED, SETUP. (If you are in
the Easy View menu system, you must first press lu vu! to get out of Easy View and into program
mode.)
nu
**
Line Setup Screens
Line Setup
Record Setup
Displa~ Setup
Interface Control
BQC
BeC Control
FEBUFF
Front-end Buffer Setup
E£RI
Bit Error Rate Test Setup
AIM 306
Coaxial or multi-mode fiber
Figure 9-1 Saftkey F6 on the Sewp Menu indicates which ATM Interface Module is installed; shown here isAIM 306 for AIM-306-)
(OPT-951-306-1).
Note in Figure 9-1 that lEI is labeled AIM 306. This means the currently installed AIM is theATM
Interface Module (AIM): DS-3, E3, and STS-l Physical and SONEr OC-3c and SDH STM-l
Multi-Mode Optical (AIM-306-1). Press @ to access the ATM Interface Setup screen for that
installed AIM.
The fields on the ATM Interface Setup screen enable the user to select the mode, along with the
type of connector and framing, and aU other parameters to monitor and emulate ATM cells in the
INTERVIEW ATM models as listed in this section. Figure 9-4, Figure 9-6, and Figure 9-8 list all
possible ATM Interface Setup selection parameters when in Monitor mode,_ Emulate A and
Internal Loop A modes, and Emulate B and Internal Loop B modes, respectively for AIM-306-1.
Each of these selections is discussed in the following pages.
SEP '95
9-1
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
9.1
Testing ATM without Concurrent WAN Protocols
Before you set up the ATM interface, consider that you may enable the INTERVIEW
8800 PLUS ATM to use additional processing space for ATM testing which would be
otherwise allocated for WAN testing. Unless you are going to test other underlying WAN
protocols via the Test Interface Module, you may "tum off" the WAN test processors and
allocate that memory to the ATM functions.
From the Setup Menu shown in Figure 9-1, press !TIl to access the Line Setup screen and
press §) DISABLE. Then press ~, !TIl SETUp, and [lli to access the ATM Interface
Setup screen for the installed AIM.
Note that the Interface Control, BCC Control, Front-end Buffer Setup, and Bit Error Rate Test Setup
lines on the Setup Menu screen (shown in Figure 9-1) do not appear and the softkey labels
for IE), §], (E1), and (§} are blank as you have just disabled these standard functions on the
Line Setup screen.
9.2
Testing WAN Protocols Concurrently with ATM
Before you setup the ATM interface on the INTERVIEW 8800 PLUS ATM, press lID to
access the Line Setup screen and make your selections as always for the protocol to be
tested via the Test Interface Module. Then press ~, !TIl SETUp, and (EID to access the
ATM Interface Setup screen for the installed AIM.
(Note that on the Setup Menu, {§] will only be labeled BERT if BERTDCE or
has been selected as the Mode on the Line Setup Screen;
otherwise @ will have no label and no line of explanation for Bit Error Rate
Testing will appear on the screen.)
BERTDTE
9.3
Mode
The Mode selection field allows you to select the expansion unit operating mode. The
choices arei~~y~t ,~~~~ ,~ljIf,:1;\."i'lfbr ,i;ii#~;i.~ ,and~; (the
default).
When Mode:;~ is displayed, no other fields are selectable or visible. Whichever of
the other modes you select determines which subsequent fields appear.
Figure 9-2 Disable mode; note there are no related fields.
The other modes and their related fields are described in the following subsections.
9-2
SEP '95
9 ArM Interlace Setup - AlM-306-1
9.4
Monitor Mode
Figure 9-3 is an example screen with some of the fields available in the Monitor mode. All
possible Monitor mode fields and their parameters are given in the diagram illustrated in
Figure 9-4.
(A) Connector
Select the type of connector you are using. Select from.~; and :;~f%_;ru;; the
field defaults to coax. Coaxial connectors deliver electrical signals over copper wire;
fiber connectors deliver optical signals over glass fiber. The type of connector
determines the line framing selections explained in subsection (B), below.
(B) Framing
Select the line framing in this field; the default is DS3 for coax cable and STS-3C for
fiber. If you are using a coaxial connector, the Framing field offers three choices:
;~~_irI~t/, V1.~lllil, and ~~. If you have selected fiber
mode. you may select either ~ or ;i_1h{~~.
(e) High Gain Side A (and B)
Use the defaults High Gain Side A: 1~.~ and B:
for receivers on lines with normal
levels of 0 dB and below. For lines with higher than normal levels, tum off the gain
for Side A. Side B, or both to avoid saturation of the receiver. This field is only
applicable for coaxial connectors.
**
Maintain:
Re load:
Mode:
nnector:
aming:
igh Gain Si e
11 Mapping:
ine Impedance:
Figu~ 9·3
I
Ce 11 Format:
.M
••••
Sample Monitor mode ATM Interface Setup screen for AIM-3Q6..1.
9-3
SEP '95
_._----------_._..__._-_._---_... _---_._.
__._-----_._---------.-----.---.
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
ATM Interface Setup
Mode'
Select Expansion Un" Opera~ng Mode·
MONITOR
EMULATE A
EMULATE B
INT LOOP A
INT LOOP B
DISABLED
I
Connector. Select Connector:
Framing:
_T
T
Select Uoo Framing:
OS3 44.736 MBPS
E3 34.368 MBPS
ISTs.3C 155.520 MBPS
STS·'51.B40MBPS
STM·' 155.520 MBPS
I
I
High Gain Side A: Select High Gain on Side A: ON
B: Select High Gain on Side B: ON
I
OFF
OFF
SPE
Cell Mapping:
I
Une Impedance:
Select line Impedance:
75 OHMS
Maintain Interlace Stale Aller Run?
Reload:
Expansion UM Aeload Control:
Cell Format: Select ATM UNI Or SMOS Cell
I
86 COLUMNS
84 COLUMNS
I
I
120 OHMS
Maintain:
cen Mapping:
Select SPE Cen Mapping:
Select Cell Mapping Delineation - Use 57-Octel PLCP for SMOS:
S3-OCTET DIRECT 57-OCTET PLCP
YES
NEVER
NO
AT RECOMPILE
Fonnat:-=r=.
EVERY RUN
SMOS
HEC Correction:
Enable HEC Correction For Single-Sit Cell Header Errors?
ENABLE
DISABLE
Payload Scrambling: Enable ScramblingiOescrambling For The Ceo Payload? ENABLE DISABLE
I
Figure 9-4 ATM Interface Setup menu for Monitor mode for AIM-306-l.
(0) Cell Mapping
This field only appears when a DS3 or E3 coaxial cable is selected in the Framing field.
The cell mapping delineation choices are
and I~~I~~~l.rl@;'i
Choose the
selection when testing on SMDS (Switched
Multimegabit Data Service) lines; the field defaults to 53-octet direct.
(E) SPE Cell Mapping
This field only appears when an STS-l coaxial cable is selected in the Framing field.
The Synchronous Payload Envelop (SPE) cell mapping delineation choices are
~I~ and;ii;~.~.
(F) Line Impedance
When an E3 coaxial cable is selected in the Framing field, you must also select the line
impedance in this field; the Une Impedance field only appears when Framing:
'ii)1\~:~.~r" is selected. Select Une Impedance: ¥~~ or ,~~; the default is
75 ohms and it is the normal selection. At this writing, 120 ohms is used only in
France.
9-4
SEP '95
ADDENDUM
9 ArM Interface Setup - AJM-3()6..1
(G) Maintain
If you wish to maintain the interface state after the run, accept the default, &I~ll!l';~;
otherwise change the Maintain field selection to ~1t~iI~~
(H) Reload
You can control the expansion unit software reloading times. Choose Reload:
'W,@~~_-...• ~~ ,..'-,.~"' ·,WR~' ~wn¥i2f'1Mifil."i
;~:, or ~i\1rllj~fl'
"~""
.·,.~~,.·,~,· ·.,~;· y"'e~~' the default, ~~l'~ii!0i!iJt
.....-:;.~•.~,,'.:..,.>.,,-...~,.;->.<,~>~~., is recommended •
l}•.••
...
....
•.
(L) Cell Format
Select r~ or ~~,a cell format; the field defaults to ATM User Network
Interface. When Cell Format . _ is selected, the next two fields appear.
(M) HEC Correction
If you wish to enable Header Error Control correction for single-bit cell header
errors, select IIIDt the default; otherwise, change the HEC Correction field to
~._. The HEC consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when Cell Format" is selected.
(N) Payload Scrambling
You may enable scrambling and descrambling for the cell payload by selecting the
default IlllBll; otherwise, disable the feature by selecting Payload Scrambling: .~:.j.
This field only appears when Cell Format: ~.!Jr:ti is selected.
(0) Tx Idle Cell Type
The selections presented are dependent upon the cell format selected as described in
subsection (L). above.
1. ATM UN! CeO Format. When Cell Format:" is selected, you may select
TxldleCellType: _1111 (the default) forCLP=O. ~I; forCLP=l, or
\!~
to design your own. When l1~ is selected, six header value
subfields appear, as described below in subsection (P).
2
-.1
SMDS ceO Format. When Cell Format: fl~!ifil-l is selected, select Tx Idle cell 'TYPe:
~~ (the default) when the cells are empty or
to design your own.
When ~.liii'II is selected. three header value subfields appear, as described
below in subsection (P).
(P) Transmit Idle Header Values
The SUbfields presented are dependent upon the cell format selected as described in
subsection (0), above. Each cell format displays its own specific Transmit Idle
Header Value fields.
ATM.UNI Cell Format. When Tx Idle cell Type: ~r~jl is selected. when you are
emulating (A or B) or using internalloopback mode, and when you are using the
ATM UNI cell format, six subfields of the 1hmsmit Idle Header Values heading appear.
You can select to transmit your own idle header values for GFC (Generic Flow
Control), VPI (Virtual Path Identifier), VCI (Virtual Circuit Identifier), PT (payload
Type), CLP (Cell Loss Priority), and the 48-octet Idle Cell Payload value.
NOV'95
9-9
ADDENDUM
INTERVIEW 800Q Series - ATM (Broadband): 985-80682-01
1.
GFC. You may override GFC (Generic Flow ContrOl) for transmitted idle cells
by entering a single-digit hex character, O-F, in this field. The default is O.
2.
VP. You may override VPI (Virtual Path Identifier) for transmitted idle cells by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
3.
VC. You may override VCI (Vutual Circuit Identifier) for transmitted idle cells by
entering a four-digit hex character, OOOO-FFFF, in this field. The default is 0000.
4.
PT. You may override PT (Payload 1YPe) for transmitted idle cells by entering a
single-digit hex character, ·0-7, in this field. The default is O.
5.
CLP. You may override CLP (Cell Loss Priority) for transmitted idle cells by
entering a 0 or 1 in this field. The default is 0, indicating the cell must be
transmitted; 1 indicates the cell may be discarded.
6.
Idle CeO Paylotzd. You may override the 48-0ctet Idle Cell Payload value by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
When Tx Idle eeliType: iltm Jill is selected, when you are
emulating (A or B) or using intemalloopback mode, and when you are using the
SMDS ceD format, three subfields of the TransmIt Idle Header Values heading appear.
SMDS CeO FormIIt.
1. ACE You may override ACF (Address Control Field) for transmitted idle cells
by entering a two-digit hex character, OO-FF, in this field. The default is 00 for an
empty cell; enter 80 for a busy cell.
9-10
2.
NCI. You may override NCI (Network Control Information) for transmitted idle
cells by entering a six-digit hex character, OOOOOO-FFFFFF, in this field. The
default is 00000o for empty cellS; enter FFFFFO for full cells.
3.
Idle CeO Paylotzd. You may override the 48-octet Idle Cell Payload value by
entering a two-digit hex character, OO-FF, in this field. The default is 00.
NOV'95
ADDENDUM
9ATM Interface Setup - AlM-306-1
9.6
Emulate B and Internal Loop B Modes
Figure 9-7 is an example screen with some of the fields available in the Emulate Band
Internal Loop B modes. All possible Emulate B mode and Internal Loop B mode fields
and their parameters are given in the diagram illustrated in Figure 9-8. Note that only
fiber optic connectors are available for selection.
NOTE: Internal Loop A and B modes loop the signals internally to the
unit. They are useful in testing the unit for correct operation and for
becoming familiar with the unit when unable to connect to a live network.
I
When connected to a live network, be aware that the transmit circuit is
active: the signal you are looping back to test is also being transmitted out
on the network.
(A) Connector
.,IM;
For Emulate B and Internal Loopback B modes, the only viable type of connector is
the default
there is no other choice. The type of connector determines the
line framing selections explained in subsection (B), below.
Maintain:
Reload:
de:
Connector:
Framing:
Cell Format:
Monitor Transm
Clock Source;
111111
Tx Idle Cell T~pe: ~
Transmit Idle Heade~
ACF:aa
NCl: 000000
Idle Cell
Pa~load:
~
.i
Figure 9-7 Sample Emulate B mode ATM Interface Setup screen for AIM·306-1. These same fields are applicable for Internal Loop B
mode for AIM·306·l.
(8) Framing
Select the line framing in this fieJd; the default is STS-3C. For both multi- and
single-fiber mode connectors, you may select either ~ or
\_~'ifriPr".='»'~
.
"~'m}",~"lAlUg;.., frammg.
NOV '95
9-11
ADDENDUM
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(C) Monitor Transmission
This field only appears when in emulate mode; you must elect whether to monitor the
transmission internally or externally.
When you are in Emulate B mode using fiber cables and connectors and you select the
default Monitor Transmission:~~,~, the INTERVIEW automatically monitors the
transmission.
If instead you choose Monitor Transmission: ;.~1, you must use a splitter cable to
split off the monitoring cable to the single/multi-mode A: RX fiber connection. This
cabling is similar to the situation illustrated for Emulate A mode in Figure 6-35
(multi-mode), except that the splitter cable would split off from B: TXlMM to A: RX
to monitor the transmission.
(D) Clock Source
Select the transmit Clock Source: \~~~.Ii, ;;:;;;;r~;fI~;iligili%:, or
$iM~~~_jii}Mt The field defaults to internal oscillator, in which the unit uses
internal crystals for timing; use this selection when emulating the network. When
emulating a workstation, select Clock Source: ~Iit~firtli,~i.:.
(E) Maintain
If you wish to maintain the interface state after the run, accept the default,
otherwise change the Maintain field selection to !!t%1J!I9,)i::
';lj~~if::i
(F) Reload
You can control the expansion unit software reloading times. Choose Reload:
irm~itl!.') if?~ ~~T.~;, or It;i~i~lli;l; the default, ili;'1i~~;jt;J, is recommended.
(G) Cell Format
Select ~"'i or ~f;llI~i: cell format; the field defaults to ATM User Network
Interface. When Cell Format !li:• •t is selected, the next two fields appear.
(H) HEC Correction
If you wish to enable Header Error Control correction for single-bit cell header
errors, select tli...t the default; otherwise, change the HEC Correction field to
:~1. The HEC consists of one byte; this process uses the standard CRC-8
algorithm over the four bytes of the header for correction. This field only appears
when Cell Formatii,'mB;; is selected.
(I) Payload Scrambling
You may enable scrambling and descrambling for the cell payload by selecting the
default ~ ; otherwise, disable the feature by selecting Payload Scrambling: [~?i .
This field only appears when Cell Format t~t,~ is selected.
9-12
NOV'95
ADDENDUM
9 ATM IntfJrface Setup - AJM-306-1
ATMlnterface SttVP
Mode:
Select E>\pansi\)n Unit Operatjng Mode:
Framing:
MONITOR
Seh!cI LIne Framing;
EMUlATE A
STs.3C 15S.520MBPS
Monitor Transmission! SeIec:t Transmit MoI'liIor:
I!'lTEANAU.V
Clock SOurce:
STM·1155.520 MBPS
EXTel'lNAU.Y
INTERN OSClUATOFl
RECeIVE DATA
EXTERNAl. SYNC
Maintain:
Cell Format: Seteet AlM UNI Or SMDS cell Format.
HEC Conection:
SUDS
ENABI.!
Enable HEC CO'fecIion For Singte.Bit Cell Header I!rront?
Payload Scrambling: Enable Scta~ For The Cell PlIyIoad'?
Tx kite Cell 1Jpe: SaledCU'''o. CLP.,t. Or Cus1omlCmitklleCeliType:
ENAI3I..E
UNASSIGNED
OlSASl.E
OlSABLE
IDlE
CUSTOM
!
Transmit Idle Header vatues:
GfC:
Ovenide $FC For T~ Idle Cells With (o.F):
VP:
O¥enide VPI For Trarnsmilled Idle Cells WIlh (OO-FF): 00
VC:
OverrIdeVCfForT~IdteCellsWllh~: 0000
PT:
Override PT For Transmitted Idle Cells WIlh (0.1):
CLP:
O¥enide CLP For Transmiftelevel Physical Statistics softkey rack is used for error injection in Emulate mode.
10.2 DS-3 Framing - 53-Octet Direct
When using DS-3 framing at 44.736 Mbps and 53-octet Direct cell mapping, select fED,
DS3, when in the Framing field and [BJ. 53-octet Direct, in the Cell Mapping field on the
ATM Interface Setup screen. After making the other applicable field selections, press ~.
As the pre-loaded application program begins to run. press 1m. PHYSTAT, to display the
Physical Layer Statistics screen for DS-3 direct framing as illustrated in Figure 10-4;
Figure 10-5 is the second page of the statistical display for DS~3 framing. 'lbggle between
the two displays by pressing (II) and GfIl. The error injection softkeys (discussed in
Section 11) apply only in Emulate Mode; they are not currently accessible from application
programs. See Section 10.1 for their accessibility.
SEP'95
10-3
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
~
. =
2). 020~j~02
0. 02180D?J0 2.8021[+021
8. 02180E80 0. 8120 t::: + 2121
2. 2800[02J
0.~.z0E-00
.... Test
conds ....
.Error-Free Seconds.
Signal-Fault Seconds
· .Errored Seconds ...
.... Signal Fault ...
· ..... DS3 OOF ......
...... DS3 AIS ......
.. . DS3 Idle Code ...
· .. DS3X-b it RAT. ..
LOC .....
110
.......
..
iii-
.......
-
.
'"
i2 . [-j000Ci28
0. 0008E00
21.0[j88[812
12.008[3[80
.
.
.
.
.
.
For More Stat
Figure 10-4 AlM 302 Physical Layer Statistics screen for DS-3 direct framing, first page; see Figure. 10-5 for second page.
The statistical categories for DS-3 framing which appear on the displays illustrated in
Figure 10-4 and Figure 10-5 are defined as follows.
(A) Signal Fault
A DS3 Signal Fault is declared in Monitor mode and Emulate A mode when a loss of
signal occurs. LOS detection is the occurrence of 175 ± 75 zeros prior to
B3ZS/HDB3 decoding.
In all other cases, it is declared when a DS3 Out Of Frame (OOF) occurs.
Many statistics are ignored during a Signal Fault second.
(8) DS300F
DS3 Out Of Frame (or lost frame alignment) occurs for DS-3 when 3 out of 16 F-bits
are in error or when 2 out of 3 M-frames contain M-bit errors.
(e) DS3 AIS
The internal DS-3 framer detects Alarm Indication Signals. A DS-3 AIS is a signal
with valid multiframe and M-subframe alignment signals and valid P-bits. The
information bits are set to a 1010... sequence, starting with a binary one after each
M-bit, F-bit, X-bit, and C-bit. The C-bits are set to binary zero (Cl =C2=C3=O) in
the third M-subframe (C31, C32, C33). The X-bits are set to binary one
(Xl=X2=l).
10-4
SEP '95
10 ArM Physical Statistics
(D) DS3 Idle Code
The internal DS-3 framer detects the Idle Code signal. A DS-3 Idle Code signal is a
signal with valid multiframe and M-subframe alignment signals and valid P-bits. The
infornlfltion bits are set to a 1100... sequence. starting with a binary one after each
M-bit, F-bit, X-bit, and C-bit. The C-bits are set to binary zero (C1=C2=C3=O) in
the third M-subframe (C31, C32, C33). The remaining C-bits (three C-bits in
M-subframes 1. 2, 4, 5, 6, and 7) may be individually set to one or zero, and may vary
with time. The X-bits are set to binary one (Xl=X2=1).
(E) DS3 X·bit RAI
A X -bit Remote Alarm Indication (RAJ) is set if the internal DS-3 framer detects
both Xl and X2 low in an M -frame. The Xl and X2 bits of the DS3 multiframe are
used to indicate received enored multiframes to the remote end. These bits are set
to binary one (Xl = X2= 1) during error free condition and to binary zero
(Xl=X2=O) if LOS, COF, MS, or slips are detected in the inCOming signal. The
maximum allowed rate of change for the X-bits is once per second.
(F) LOC
Loss Of Cell Delineation (LOC) is active in any mode when the HEC alignment
framing method (53-byte ceUs) is active. Cell delineation is lost if seven consecutive
HEC errors occur at the current cell delineation position.
F.gure If)..S AIM 302 Pbysical Layer Statistics screen for ns..3 direct framing,. second page.
SEP '95
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
(G) Line Code Violations
B3ZS decoding: A line Code Violation is a bipolar rule violation and an occurrence
of three or more zeros.
HDB3 decoding: Aline Code Violation is the count of LCVs according to CCI1T
recommendation 0.161.
(H) DS3 Frame Errors
DS3 Frame Errors is the count of F-bit and M-bit errors in the DS3 multiframe. The
M-bits are the multiframe alignment signal 010 (MI=O, M2=1, M3=O) used to locate
all seven M-subframes within the DS3 multiframe. The F-bits are the M-subframe
alignment signall00l (F1=l, F2=0, F3=0, F4=1) used to identify the overhead bit
positions.
(I) DS3 Parity Errors
DS3 Parity Errors is the count of P-bit errors in the DS3 multiframe. PI and P2 carry
parity information calculated over the 4704 payload bits in the preceding DS3
multiframe. PI =P2= 1 if the digital sum of all payload bits is one, and PI = P2=0 if
the digital sum of all payload bits is zero.
(J) DS3 Path Parity Errs
. DS3 Path Parity Errors is the count of C-bit path parity errors. The CP-bits (bits C31,
C32, and C33) are used to carry path (end-to-end facility) parity information. The
network terminating equipment (NTE) that originates the DS3 signal must set these
bits (C31 =C32=C33) to the same values as the P-bits. The CP-bits must not be
modified along the DS3 facility or they will be considered to be errored.
(K) DS3 FEBE Errors
This is the count of DS3 FEBE Errors. Bits C4I, C42, and C43 are used to carry Far
End Block Error (FEBE) information. All three FEBE bits are set. to binary one
(C41 =C42=C43= 1) if no errors are detected in the M-bits, or F-bits, or indicated by
the CP-bits. If any error condition (errored M-bits, errored F-bits, or parity in
CP-bits) is detected within the DS3 multiframe, the FEBE bits must be set to any
combination of ones or zeros (except 111).
10.3 OS-3 Framing - 57-Octet PLCP
When using DS-3 framing at 44.736 Mbps and 57-octet PLCP cell mapping, select (B),
DS3, when in the Framing field and @, 57-octet PLCp, in the Cell Mapping field on the ATM
Interface Setup screen. After making the other applicable field selections, press S.
As the pre-loaded application program begins to run, press @, PHYSTAT, to display the
Physical Layer Statistics screen for DS-3 PLCP framing as illustrated in Figure 10-6;
Figure 10-7 is the second page of the statistical display for DS-3 framing. Toggle between
10-6
SEP'95
10 A TM Physical Statistics
the two displays by pressing (I(J and {IIJ. The error injection softkeys (discussed in
Section 11) apply only in Emulate Mode; they are not currently accessible from application
programs. See Section 10.1 for their accessibility.
The statistical categories for DS-3 framing which appear on the displays illustrated in
Figure 10-6 and Figure 10-7 are defined as follows.
(A) Signal Fault
A DS3 Signal Fault is declared in Monitor mode and Emulate A mode when a loss of
signal occurs. LOS detection is the occurrence of 175 ± 75 zeros prior to
B3ZSIHDB3 decoding.
In all other cases, it is declared when a DS3 Out Of Frame (OOF) occurs.
Many statistics are ignored during a Signal Fault second.
(8) DS300F
DS3 Out Of Frame (or lost frame alignment) occurs for DS-3 when 3 out of 16 F-bits
are in error or when 2 out of 3 M-frames contain M-bit errors.
o ~ r21~["::'
~~~2
~ C~J~~=_ ~ 3~
:;:
G~
4
:21L ~=-~:.=- - ~~
?
.... est
conds ....
. Error-Free Seconds.
Signal-Fault Seconds
· .Errored Seconds ...
.... Signal Fault ... .
· ..... DS3 OOF ......
..... . DS3 AlS ......
... DS3 Idle Code ...
.... .. PLCP OaF .....
.... .. PLCP LOF .....
· ... PLCP LOF 2-3 ...
.
.
.
.
.
.
... D53 X-bit RAI ... .
... . PLCP Gl RAI .... .
Figure 10-6 AIM 302 Physical Layer Statistics screen for D5·3 PLCP framing, first page; see Figure 10·7 for second page.
(C) DS3AIS
The internal DS·3 framer detects Alarm Indication Signals. A DS-3 AIS is a signal
with valid multiframe and M-subframe alignment signals and valid P-bits. The
information bits are set to a 1010... sequence, starting with a binary one after each
SEP '95
10-7
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
M-bit, F-bit, X-bit, and C-bit. The C-bits are set to binary zero (Cl=C2=C3=O) in
the third M-subframe (C31, C32, C33). The X-bits are set to binary one
(X1=X2=1).
(D) DS3 Idle Code
The internal DS-3 framer detects the Idle Code signal. A DS-3 Idle Code signal is a
signal with valid multiframe and M -subframe alignment signals and valid P-bits. The
information bits are set to a 1100... sequence, starting with a binary one after each
M-bit. F-bit, X-bit, and C-bit. The C-bits are set to binary zero (Cl =C2=C3=O) in
the third M-subframe (C31, C32, C33). The remaining C-bits (three C-bits in
M-subframes 1, 2, 4, 5, 6, and 7) may be individually set to one or zero, and may vary
with time. The X-bits are set to binary one (Xl=X2=l).
(E) PLCP OOF
The PLCP OOF is set if the PLCP OOF state has been entered (a loss of frame
alignment) for 57-octet PLCP formats.
(F) PLCP LOF
A PLCP Loss Of Frame is indicted when eight consecutive PLCP frames are out of
frame.
(G) PLCP LOF 2-3
A PLCP WF 2-3 is detected if PLCP LOF is high for three consecutive one-second
latching signals (loss of frame condition lasts for 2 to 3 seconds).
(H) DS3 X..bit RAI
A X-bit Remote Alarm Indication (RAJ) is set if the internal DS-3 framer detects
both Xl and X2low in an M-frame. The Xl and X2 bits of the DS3 multiframe are
used to indicate received errored multiframes to the remote end. These bits are set
to binary one (Xl =X2= I) during error free condition and to binary zero
(Xl =X2=O) if LOS, OaF, AIS, or slips are detected in the incoming signal. The
maximum allowed rate of change for the X-bits is once per second.
(I) PLCP G1 RAI
The PLCP G 1 RAI count is the number of times that the Remote Alann Indication
(RAJ) (Yellow Alarm) has been observed. RAJ is indicted when the RAI bit in the
PLCP G1 octet has been active for ten consecutive PLCP frames.
10-8
SEP '95
10 ATM Physical Statistics
. . .. est econds ....
. Error-Free Seconds.
Signal-Fault Seconds
.. Errored Seconds ...
Line Code Violations
.. D53 Frame Errors ..
. DS3 Parit~ Errors ..
D53 Path Parit~ Errs
.PLCP Frame Errors ..
.. PLCP SIP Errors ...
.. PLCP FEBE Errors ..
.• D53 FEBE Errors ...
. PLCP FESt All Ones.
CP I
Figure t(l.7 AIM 302 Physical Layer Statistics screen for 05·3 PLCP framing. second page.
(J) Une Code Violations
B3ZS decoding: A line Code Violation is a bipolar rule violation and an occurrence
of three or more zeros.
HDB3 decoding: A Line Code Violation is the count of LCVs according to CCIIT
recommendation 0.161.
(K) DS3 Frame Errors
DS3 Frame Errors is the count of F-bit and M-bit errors in the DS3 multiframe. The
M-bits are the multiframe alignment signal 010 (MI=O, M2=1, M3=O) used to locate
all seven M-subframes within the DS3 multiframe. The F-bits are the M-subframe
alignment signal 1001 (FI = 1, F2=O, F3= 1, F4=O) used to identify the overhead bit
positions.
(L) DS3Parity Errors
DS3 Parity Errors is the count of P-bit errors in the DS3 multiframe. PI and P2 carry
parity information calculated over the 4704 payload bits in the preceding DS3
multiframe. PI::.\l P2= 1 if the digital sum of all payload bits is one, and PI = P2=O if
the digital sum of all payload bits is zero.
SEP '95
10-9
INTERVIEW 8000 Series - ArM (Broadband): 985-80682-01
(M) DS3 Path Parity Errs
DS3 Path Parity Errors is the count of C·bit path parity errors. The CP-bits (bits C31,
C32, and C33) are used to carry path (end-to-end facility) parity information. The
network terminating equipment (NTE) that originates the DS3 Signal must set these
bits (C31 =C32=C33) to the same values as the P-bits. The CP-bits must not be
modified along the DS3 facility or they will be considered to be errored.
(N) PLCP Frame Errors
A PLCP Frame Error is detected if there is an error in either the Al or A2 octets of
.the PLCP frame pattern for 57-octet PLCP formats.
(0) PLCP BlP Errors
A PLCP BIP-8 Error is detected when an errored Bl octet occurs in the PLCP
frames.
(P) PLCPFEBE Errors
A PLCP FEBE Error is registered if any valid non-zero Far End Block Error value (1
through 8) is detected in the G 1 octet in 57-octet PLCP formats.
Far End Block Errors are carried in the first four bits of the G1 byte. It counts the
number of bits (binary 000 to 1000) in the previous BIP-8 that didn't match the even
parity check. A FEBE setting of 1111 is used to indicate BIP/FEBE is not active.
Other values are invalid.
(a) D83 FEBE Errors
This is the count ofDS3 FEBE Errors. Bits C41, C42, and C43 are used to carry Far
End Block Error (FEBE) information. All three FEBE bits are set to binary one
(C41 =C42=C43= 1) if no errors are detected in the M-bits, or F-bits. or indicated by
the CP-bitS. If any error condition (errored M-bits, errored F-bits, or parity in
CP-bits) is detected within the DS3 multiframe. the FEBE bits must be set to any
combination of ones or zeros (except 111).
(R) PLCP FEBE All Ones
A P1CP FEBE All Ones is counted when a 01 octet is detected with the FEBE value
is 0xF. This is also considered to be an Invalid FEBE.
(8) PLCP Invalid FEBE
An Invalid FEBE is registered if a G 1 octet has any invalid FEBE value (9 through
F).
10.4 E3 Framing - 53-Octet Direct
When using E3 framing at 34.368 Mbps and 53-octet Direct cell mapping, select 1m, E3,
when in the Framing field and lTIl. 53-octet Direct, in the Cell Mapping field on the ATM
Interface Setup screen. After making the other applicable field selections, press ~.
10-10
SEP'95
10 ATM PhYsical Statistics
As the pre-loaded application program begins to run, press IfID. PHYSTAT, to display the
Physical Layer Statistics screen for E3 direct framing as illustrated in Figure 10-8;
Figure 10-9 is the second page of the statistical display for E3 framing. Toggle between the
two displays by pressing mil and (Ill. The error injection softkeys (discussed in Section
11) apply only in Emulate Mode; they are not currently accessible from application
programs. See Section 10.1 for their accessibility.
Pb~sical
LA~er Stats
· ... Test Seconds ....
. Error-Free Seconds.
Signal-Fault Seconds
.. Errored Seconds ...
? ~ ;}20t +~ A~
:~ ~ v.~li_~[""" i~-'~~
.=~., 0C:·~Jr=· l-~2
':' ~
~_:2~-1t~ ~>':~
=.-1 ~ ~~C::-'~T~~;:
.I. .
Signa 1 Fau 1t ...
· ...... E3 AIS ......
· ...... E3 OOF ......
· ...... E3 LOF ......
..... E3 LOF 2-3 ....
'1
.
.
.
.
~~ ~ ~:! :;~.~~:~~~~~
~-'I
--;:~J---;t.-''";lL
'...,,.
~_~_'_'<_l
;:: ~
-
~
__ o:.
1"71
'L...
~ ;~-~:~~:E3::~
~-:. ::"1~1=-"~~~2
z~
.
~-:. ~~~~:~_"J8
• . . . . . . . . LOC . . . . . . . . . •
Line Code Violations
F'agure 10-8 AIM 302 Physical Layer Statistics screen for E3 direct framing. first page.
The statistical categories for £3 direct filming which appear on the displays illustrated in
Figure 10-8 and Figure 10-9 are defined as follows.
(A) Sig_1 Fault
m
An
Signal Fault is declared in Monitor mode and Emulate A mode when a loss of
signaloccurs. LOS detection is the occurrence of 175 ± 75 zeros prior to
B3ZSlHDB3 decoding.
In all other cases, it is declared when a E3 Out Of Frame (OOF) occurs.
Many statistics are ignored during a Signal Fault second.
(8) E3AIS
The Alarm Indication Signal means that tbe internal E3 framer has detected an AlS.
It is set if an unframed all·ones pattern is present for two consecutive frames with
detection as defined in ccm recommendation G.775.
SEP '95
·10-11
INTERVIEW 8000 Series - ATM (8roadband): 985-80682-01
(e) E300F
An E3 Out of Frame alarm means a loss of frame alignment. This bit is set when four
consecutive errored A1/A2 framing patterns are observed.
(0) E3l0F
An E3 Loss Of Frame condition occurs where mux cannot find framing (OaF) for 24
consecutive E3 frames.
(E) E3 lOF 2-3
An E3 LOF 2-3 error is detected if E3 LOF is high for three consecutive one-second
latching signals.
(F) LOe
Loss Of Cell Delineation (LOC) is active in any mode when the HEC alignment
framing method (53-byte cells) is active. Cell delineation is lost if seven consecutive
HEC errors occur at the current cell delineation position.
(G) Une Code Violations
B3ZS decoding: A Line Code Violation is a bipolar rule violation and an occurrence
of three or more zeros.
HDB3 decoding: A Line Code Violation is the count of LCVs according to
recommendation 0.161.
- . .~
~
0.02lr:'l0E00
0.0000E00 0. 000E+00
0. (2)00E00 0. 000E+210
0. 0000E00 0. 000E+00
I ...
.
a. L10\?J8E02
2. 0CJ2liZE02
o . (J2:3D~02
.... Test Seconds ....
.Error-Free Seconds.
Signal-Fault Seconds
.. Errored Seconds ...
2.0000Ec:m ~) . 0F10~_ +(]0 • . . . EM BIP Errors ....
z, . 08lJ0E0!21 tJ ~ 000:: 'T0'~
... B1 BIP Errors ... .
2.0000E00 0.000:::+00
MA FEBE Errors ...
... MA FERF Errors .. .
0.0000[00 0.000E+80
ccrrr
2 . 0lZ22E.J8
1'1
I
0. 02102E00
;(~ . 8Z~J0l08
0 . 8202[02:
(3 • ZZ1[2hj~00
0. 0000E00 liM"". . . . . Pa~. T~pe Mismatch .. . . . . .-
Figure 10·9 AIM 302 Physical layer Statistics screen for E3 framing, second page.
10-12
SEP '95
10 ArM Physical Statistics
(H) EM BIP Errors
An EM BIP-8 Error is detected if there is an error in the BIP-8 code (EM octet)
checking.
The Bit Interleaved Parity 8 is an error checking code applied fur quick isolation of
faults. Each bit in the B octets is set to 1 or 0 as necessary to obtain even parity over
the previous frame. This is the same as the parity bit in an async character, but
instead of a character the parity check covers the entire frame. That is, if there are
an even number of Is in the first position of all octets, the first bit of the B octet is O.
If the ll,umher of Is in the second position of all octets is odd, the second bit of the B
octet is set to 1 to make the count (parity) even.
(I) B1
alp Errors
A Bl SIP Error is detected if there is an error in the BIP-8 code (Bl octet, section
overhead) checking.
(J) MA FEBE Errors
A MA FEBE Error is detected if the Front End Block Error bit in the MA octet is set
in a E3 frame.
(I<)
MA FERF Errors
A MA FERF Error is detected if the Far End Receive Failure bit in the MA octet is
set in a E3 frame.
(L) Pay. Type Mismatch
A Payload Type Mismatch error is detected if the received value in the payload type
bits ofthe MA octet do not equal 010 for seven consecutive frames.
10.5 E3 Framing - 57-Octet PLCP
When using E3 framing at 34.368 Mbps and 57-octet PLCP cell mapping, select @, E3,
when in the Framing field and @. 53-octet PLCP, in the Cel Mapping field on the ATM
Interface Setup screen. After making the other applicable field selections, press 8.
As the pre-loaded application program begins to run, press@ PHYSTAT. to display the
Physical Layer Statistics screen for E3 PLCP framing as illustrated in Figure 10-10;
Figure 10-11 is the second page of the statistical display for E3 framing. Toggle between
the two displays by pressing !:mIl and IJIU. The error injection softkeys (discussed in
Section 11) apply only in Emulate Mode; they are not currently accessible from application
programs. See Section 10.1 for their accessibility.
The statistical categories for E3 PLCP framing which appear on the displays illustrated in
Figure 10-10 and Figure 10-11 are defined as follows.
SEP'95
~~---
~~-------~------.------.
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
:;
I!
=
2.1. 02.180E821
21.212.12.121E00 0.0l18E+08
8 . 2.18r:;~j[0rj (/) . 02.18r +E0
2.1 . [W) 218 D?H2 ;3.00[:"1[+00
.... Test Seconds ....
. Error-Free Seconds.
Signal-Fault Seconds
.. Errored Seconds ...
2.1.2.12.12.1[-2.10
8.82.10[+013
0.020[+021
.... Signal Fault ... .
.... Out-of-Frame ... .
.. Alarm Ind Signal ..
. . . . . . PLCP OOF ..... .
.... .. PLCP LOF ..... .
.... PLCP LOF 2-3 ... .
.... A-bit yellow ... .
... . PLCP yellow .... .
For More Stats
Figure 10-10 AIM 302 Physical Layer Statistics screen for E3 PLCP framing, first page.
(A) Signal Fault
An E3 Signal Fault is declared in Monitor mode and Emulate A mode when a loss of
signal occurs. LOS detection is the occurrence of 175 ± 75 zeros prior to
B3ZS/HDB3 decoding.
In all other cases, it is declared when a E3 Out Of Frame (OOF) occurs.
Many statistics are ignored during a Signal Fault second.
(8) Out-of-Frame
An E3 Out-of-Frame alarm means a loss offrame alignment. This bit is set when
four consecutive errored Al/A2 framing patterns are obsetved.
(C) Alarm Ind Signal
The Alarm Indication Signal means that the internal E3 framer has detected an AlS.
It is set if an unframed all-ones pattern is present for two consecutive frames with
detection as defined in CCIIT recommendation G.775.
(0) PlCP OOF
The PLCP OOF is set if the PLCP OOF state has been entered (a loss of frame
alignment) for 57-octet PLCP formats.
(E) PlCP lOF
A PLCP Loss Of Frame is indicted when eight consecutive PLCP frames are out of
frame.
10-14
SEP '95
10 ATM Physical Statistics
(F) PLCP LOF 2·3
A PLCP LOF 2-3 is detected if PLCP LOF is high for three consecutive one-second
latching signals (loss of frame condition lasts for 2 to 3 seconds).
(G) A-bit Yellow
E3 A-bit yellow is set if the internal E3 framer detects the A-bit high in a G .751 E3
frame.
(H) PLCP Yellow
The PLCP Yellow count is the number of times that the Remote Alarm Indication
(Yellow Alarm) has been observed. Yellow alarm is indicted when the RAJ bit in the
PLCPG1 octet bas been active for ten consecutive PLCP frames.
onds ....
. Error-Free Seconds.
Signal-Fault Seconds
.. Errored Seconds ...
I
Line Code Violations
.... Frame Errors ....
.PLCP Frame Errors ..
.. PLCP BIP Errors ...
.. PLCP FEBE Errors ..
I ...
FEBE All Ones ....
.. . . Inval id FEBE ... .
I.
I·
Frgure 10-11 AIM 302 PhYSical Layer Statistics screen for £3 PLCP framing. second page.
(I) Line Code Violations
83Z$ decoding: A line Code Violation is a bipolar rule violation and an occurrence
of three or more zeros.
HDB3 decoding: A Line Code Violation is the count of LCVs according to ccrrr
recommendation 0.161.
(J) Frame Errors
Frame errors or errored FAS (Frame Alignment Signal) patterns are counted. Loss
of fra,me alignment is assumed when four consecutive Frame Alignment Signals are
incorrectly received in their predicted positions.
SEP'95
10-15
-----------------_._-_._--_._----_._-------------.................
INTERVIEW 8000 Series -ATM (Broadband): 985-B0682-01
(I<) PLCP Frame Errors
A PLCP Frame Error is detected if there is an error in either the Alar A2 octet of
the PLCP frame pattern for 57-octet PLCP formats.
(L) PLCP BIP Errors
A PLCP BIP-8 Error is detected when an errored B1 octet occurs in the PLCP
frames.
(M) PLCP FEBE Errors
A PLCP FEBE Error is registered if any valid non-zero Far End Block Error value (1
through 8) is detected in the G1 octet in 57-octet PLCP formats.
Far End Block Errors are carried in the first four bits of the G 1 byte. It counts the
number of bits (binary 000 to 1000) in the previous BIP-8 that didn't match the even
parity check. A FEBE setting of 1111 is used to indicate BIP/FEBE is not active.
Other values are invalid.
(N) FEBE AU Ones
A PLCP FEBE All Ones is counted when a G1 octet is detected with the FEBE value
is 0xR This is also considered to be an Invalid FEBE.
(0) Invalid FEBE
An Invalid FEBE is registered if a Gl octet has any invalid FEBE value (9 through F).
10.6 STS ..1 Framing
When using STS-l framing at 51.840 Mbps for coaxial signals, select @, STS-1, when in
the Framing field on the ATM Interface Setup screen. After making the other applicable
field selections, press ~.
As the pre-loaded application program begins to run, press (ill, PHYSTAT, to display the
Physical Layer Statistics screen for STS-l framing as illustrated in Figure 10-12;
Figure 10-13 is the second page of the statistical display for STS-l framing. Toggle
between the two displays by pressing u;u and r=:J. The error injection softkeys (discussed
in Section 11) apply only in Emulate Mode; they are not currently accessible from
application programs. See Section 10.1 for their accessibility.
Note that STS is byte-oriented; the digital unit within STS is an octet (8 bits). Octet may
sound the same as a byte, but "byte" implies a character or other unit that has meaning by
itself, and bytes sometimes are more than 8 bits. "Octet" is used to indicate an eight-bit
unit, even if it has no logical meaning on its own, like 8 bits from a graphic image file.
Many overhead octets are logical units, and in some cases will be referred to as bytes.
10-16
SEP'95
~..
10 ATM Phvsical Statistics
NOTE: These same physical statistics are applicable for and are displayed
with fiber optical connectors and signals.
Ph~sical
~R~er Stats
.... Test Seconds ....
. Error-Free Seconds.
Signal-Fault Seconds
.. Errored Seconds ...
Rate
.... Signal Fault ... .
· ..... STS LOP ...... .
..... . Line AlS ..... .
..... . Path AlS ....•.
· ..... STS OOF ...... .
· ..... STS LOF ...... .
.... STS LOF 2-3 .... .
· ..... Path RDl ..... .
· ........ LOC ........ .
ine Cod V
Figure 10--12 AIM 302 Physical Layer Statistics screen for STS-l framing. first page.
The statistical categories for STS-l framing which appear on the displays illustrated in
Figure 10-12 and Figure 10-13 are defined as follows.
(A) Signal Fault
An STS-l Signal Fault is declared in Monitor mode and Emulate A mode when a loss
of signal occurs. LOS detection is the occurrence of 175 ± 75 zeros prior to
B3ZSlHDB3 decoding.
In all other cases, it is declared when a STS-l Out Of Frame (OOF) occurs.
Many statistics are ignored during a Signal Fault second.
(8) STS LOP
The H bytes point to the start of the payload. An STS Loss of Pointer is recorded if a
valid pointer as defined in TR-NWT-000253 cannot be found in the Hl/H2 pointer of
the STS-lISTS-3c/STM-l frame.
(C) Une AIS
A Line Alarm Indication Signal is detected when the the three Least Significant Bits
of the K2 octet of the STS frame are set to 111 for five consecutive frames.
SEP '95
10-17
INTERVIEW 8000Series-ATM (Broadband): 985-80682-01
(D) Path AIS
A Path Alarm Indication Signal is given if an all-ones pattern is detected in the HI
and HZ octets for three consecutive frames.
(E) STSOOF
An STS Out Of Frame is detected if four consecutive errored AI/A2 framing patterns
are observed. For STS-3c and STM -1, the pattern observed consists of the third Al
octet and the first A2 octet.
(F) STS LOF
An STS Loss Of Frame is detected when STS OOF is active for 24 consecutive
SONET frames.
(G) STS LOF 2-3
STS LOF 2-3 is detected if STS LOF is high for three consecutive one-second
latching signals.
(H) Path RDI
A Path Yellow alarm (Remote Defect Indicator) is detected if the path yellow bit in
the G 1 octet is set for ten consecutive frames.
_IW
____
' _11
_ __ _,_............
lOO!J
...._ ._ _
~
i'll~
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
AIS is used in the digital network to alert downstream equipment that an
upstream failure has been detected. The SONET signal format provides
different AISs for various layers of functionality including DS n (n = 1, 1C, 2, or
3) and DSO AISs. An STE sends Line AIS to alert the downstream Line
Terminating Equipment (LTE) than a failure has been detected and to initiate
automatic protection switching (when APS is provided as a feature).
On entering an LOS or LOF state on the incoming signal, Line AIS shall be
generated downstream by an STE within 125 micro-seconds. An STE generates
Line AIS by constructing an OC-n signal that contains valid Section overhead
and a scrambled all-ones pattern for the remainder of the signal. Note that Line
AIS generated as described provides convenient generation of AIS for upper
layers (e.g., Path AIS and DS1 AIS).
Line AIS on an incoming signal shall be detected by an LTE as all ones in bits 6,
7, and 8 of the K2 octet in five consecutive frames, at which point the LTE shall
enter a Line AIS state.
Line AIS deactivation shall occur (i.e., an STE shall cease generating Line AIS)
within 125 micro-seconds of the STE exiting the failure state that caused the Line
AIS to be sent downstream.
Removal of Line AIS on an incoming signal shall be detected by an LTE as any
pattern other than the code 111 in bits 6, 7, and 8 of the K2 octet in five
consecutive frames. The detection of the removal of Line AIS shall cause the
LTE to exit the Line AIS state. For verification purposes, it suffices to use a
consistent non-Ill pattern to test compliance with this requirement.
The Line AIS signal maintains operation of the downstream regenerators and,
therefore, prevents generation of unnecessary alarms. At the same time, data
and orderwire communication is retained between the regenerators and the
downstream LTE.
To summarize, on an incoming signal an LTE shall:
Take this Action
Activate Line AIS
Deactivate Line AIS
When K2-octet Has
bit 6 bit 7 bit 8
1
1
Fora
Duration of
How
Soon
five consecutive
frames
within
125 micro-seconds
Enabling the L AIS condition forces the Line AIS condition to be transmitted.
•
L RDI- Forces an STS-3c/STM-l Line RDI (Line FERF) condition to be
generated.
An indication returned to a transmitting Line Terminating Equipment (LTE)
upon receipt of a Line AIS code or detection of an incoming line failure at the
11-10
SEP '95
11 Error Injection for Physical Statistics
receiving LTE. Line RDI (Remote Defect Indicator) alerts the upstream LTE
that a failure has been detected along the downstream line.
Line RDI shall be generated within 125 micro-seconds of the LTE entering an
LOS. LOp, or Line AIS state on the incoming signal. AN LTE generates Line
RDI by inserting the code 110 in bit positions 6, 7, and 8 of the K2 octet.
All LTEsshall detect incoming Line RDI. Line RDI is detected when a 110
pattern is detected in bits 6, 7, and 8 of the K2 octet for five consecutive frames,
at which point the LTE shall enter a Line RDI state.
The LTE indicates that removal of Line RDI by inserting the code 000 in bits 6,
7, and 8 of the K2 octet within 125 micro--seconds of exiting the failure state or
Line AIS state of the incoming signal.
When bits 6, 7, and 8 of the K2 octet are also used for APS mode indication, the
code 000 inserted to indicate Line RDI removal shan be inserted for a minimum
of 50 ms. After a maximum of 200 ms, the appropriate APS mode indication
shaH be inserted.
Removal of Line RDI is detected by a 000 pattern in bits 6, 7, and 8 of the K2
octet in five consecutive frames. The detection of the removal of Line RDI shall
cause the LTE to exit the Line RDI state.
As an objective, removal of Line RDI should be detected by any pattern other
than the code 110 in bits 6, 7, and 8 of the K2 octet in five consecutive frames.
For verification purposes, it suffices to apply a consistent non-l10 code to test
compliance with this objective.
To summarize, on an incoming signal an LTE shall:
Take this Action
When
bit 6
Activate Une RDI
Deactivate Line ROI
K2:0Ctet Has
bit 7
bit 8
000
Fora
Duration of
How
Soon
five consecutive
frames
within
125 micro-seconds
Enabling the L RDI condition forces the Line RDI condition to be transmitted.
•
P RDI- Forces the transmission of the STS-3cISTM-1 Path RDI (Path Yellow)
condition.
STS Path RDI alerts the upstream STS PTE that a downstream failure indication
has been declared along the STS Path. When STS-based services are carried in
the STS SPE, STS Path RDI can be used to initiate trunk conditioning on the
affected STS Path service.
Path RDI shan be generated within 250 micro-seconds by an STS PTE upon
entering LOS, LOF, LOP, or LOC state, or upon detecting Line AIS or Path AIS,
by setting bit 5 in the Path Status octet (Gl) to one.
SEP'95
11-11
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
This bit retains this value for the duration of the RDI condition. Transmission of
the RDI signal shall cease within 250 micro*seconds when the STS PTE no longer
detects the above failure states or line AlS or Path AlS. An STE PTE shall
deactivate STS Path RDI by setting bit 5 in the Gl octet to zero.
All STS PTEs shall detect incoming STS Path RDI. An STS PTE detects STS
Path RDI when a one is in bit 5 of the Gl octet for ten consecutive frames, at
which point the S1'S PTE shall enter the STS Path RDI state.
Removal of S1'S Path RDI is detected by an STS PTE by a zero in bit 5 of the G I
octet for ten consecutive frames, at which point the S1'S PTE shall exit the STS
Path RDI state.
To summarize, on an incoming signal when LOS, LOF, LOP, LOe, Une AIS, or Path AtS is
detected, an STE shall:
.
To Take This Action:
How
Soon
Set bit 5 of
the G1-octet to
Fora
Duration of
Activate Path RDt
within
250 micro.seconds
1
ten consecutive
frames
Deactivate Path RDI
within
250 micro*seconds
0
ten consecutive
frames
Enabling the P RDI condition forces the Path RDI (Path Yellow) condition to be
transmitted.
•
P FERF -
Forces transmission of the STS-3c1STM-I Path FERF condition.
A Path Far End Receive Failure Errors (FERF) condition is reported when the
value nine is detected in bits I through 4 of the Path Status octet (G I).
•
PAIS - Forces transmission of the STS-3c1STM-I Path AIS condition.
A Path Alarm Indication Signal (AIS) is set if an all.anes pattern is detected in
the HI and H2 octets for three consecutive frames. Ordinarily the HI and H2
octets are used for concatenation indication.
•
SPE UN - Forces transmission of the STS-3c/STM-l "STS Path Unequipped"
condition.
Code 00 (HEX) in the STS Path Signal Label (C2 octet) indicates STS Path
Unequipped. This code is originated by the NE if the path connection is not
provisioned (idle). Any code received, other than the code 0, constitutes an
"Equipped" condition.
Enabling the SPE UN condition forces 0 to be transmitted in the C2 octet.
11-12
SEP'95
.'-'.
Appendixes
Appendix A ATM GlossarY and Acronyms
Appendix A ATMGlossary and Acronyms
The information in this section of glossary terms and acronyms has been compiled from various sources.
Note that the terms included are for general information purposes only; this manual does not necessarily
refer to or use each one individually within the context of this document.
AAL
ATM Adaptation Layer.
This is a set of four standard protocols that translate user traffic from the higher layers of the
protocol stack into a size and format that can be contained in the payload of an ATM cell and
return it to its original form at the destination. Each AAL consists of two sublayers concerned
with segmenting large Protocol Data Units into ATM cells: the Segmentation and Reassembly
(SAR) sublayer and the Common Part Convergence Sublayer (CPCS).
AAL 1
ATM Adaptation Layer 1.
AAL 1 is a protocol that addresses Constant Bit Rate (CBR) traffic, such as digital voice and
video. It is used for applications that cannot tolerate either cell loss or delay. It requires an
additional byte of header information for sequence numbering, leaving 47 bytes of the cell for
the payload.
.
AAL 2
ATM Adaptation Layer 2.
AAL 2 is used with time-sensitive, Variable Bit Rate (VBR) traffic such as packetized voice. It
allows partial payloads to be sent with ftllers so as to accommodate timing requirements of the
application.
AAL3/4
ATM Adaptation Layer 3/4.
This is an AAL protocol that handles traffic that can tolerate delay but not cell loss, i.e., bursty
connection..oriented traffic (error messages) or variable-rateconnectionless traffic (IAN ftle
transfers). To this end, AAL 3/4 performs error detection on each cell, using an error-checking
mechanism that uses 4 bytes of each 48-byte payload. ATM cells may be multiplexed in AAL 3/4.
AAL5
ATM Adaptation Layer 5.
Using a conventional5-byte header, AAL 5 accommodates bursty LAN data traffic with less
overhead than AAL 3/4. However, unlike AAL 3/4, it does not allow multiplexing of ATM
cells.
ABR
Available Bit Rate.
AIM
ATM Interface Module.
A module which resides on the top enclosure of the INTERVIEW 8800 PLUS ATM unit; it
houses the ATM interface connectors.
AIS
Alarm Indication Signal.
A DS-3 AIS is a signal with valid multiframe and M-subframe alignment signals and valid
P-bits. (DS-3 53-octet direct framing)
SEP'95
A-1
--- - - - - - - - - - - - - " - - - - - - - - -_ _ _......_ _z_ _ _ _ _
_
INTERVIEW 8000 Series - ArM (Broadband): 985-80682-01
AL
Alignment.
This is a I-byte subfield used to make the CPCS trailer size 4 bytes and passed transparently
through the network for AAL 3/4.
ATM
Asynchronous Transfer Mode.
This type of framing is used in B-ISDN and SONET based on 53-byte cells (a 5-byte header with
a 48-byte payload). It is a high-speed, connection-oriented switching and multiplexing
technology used to transmit different types of traffic simultaneously (voice, video, and data); it is
asynchronous in that information streams can be sent independently without a common clock.
Bl
This is a section overhead (SOH) byte carrying a BIP-8 parity check.
B2
This is a line overhead (LOH) byte carrying a BIP-8 parity check.
B3
This is a path overhead (POH) byte carrying a BIP-8 parity check.
BASize
Buffer Allocation Size.
This 2-byte portion of the CPCS header is encoded to indicate the CPCS-PDU payload length
in AAL 3/4.
BECN
Backward Explicit Congestion Notification.
This is a signalling bit in the Frame Relay header.
B-ICI
B-ISDN Inter-Carrier Interface.
This interface is a carrier-to-carrier interface between ATM networks.
BIP
Bit Interleaved Parity.
This is an error checking method where each of n bits is parity of every nth bit in the data
block: each bit in this field reflects an "even parity" on all the bits in the same position (1-8) of
the bytes in the previous PLCP frame, excluding the AI, A2, and P bytes. A BIP-8 applies
eight separate checks longitudinally on the data.
B-ISDN
Broadband Integrated Services Digital Network.
This technology suite is geared to multimedia with two transmission schemes: STM
(Synchronous Transfer Mode) and ATM. It allows ATM access at rates greater than 100 Mbps.
BNC
Connectors (male) on coaxial cables for DS3, E3, and STS-l metallic interface testing to mate
with metallic interface connectors (female) on ATM Interface Modules.
Btag
Beginning Tag.
Btag is a 1-byte "error check" for the segment in the CPCS header in AAL 3/4. The value in
this field is also placed in the Etag field of the trailer, aJIowing a quick comparison after
receipt to determine if the PDU has been corrupted.
CAC
Connection Admission Control.
This process is one in which new calls are limited to preserve the quality of service. It uses two
means of controlling the setup of virtual circuits--overbooking and full booking. Overbooking
allows one connection to exceed permissible traffic limits and assumes that other active
connections are not using the maximum available resources; fun booking limits network access
once maximum resources are committed and only adds connections that specify acceptable
traffic parameters.
A-2
SEP '95
Appendix A· ATM G/os§fW and Acronyms
CBR
Constant BitRate.
This is used in ATM for voice or sync data (video) which requires a continuous flow of bits
with low variation in cell delay. It requires guaranteed throughput rates and service levels.
CDV
Cell Delay Variation.
Expressed in fractions of a second, this ATM User Network Interface traffic parameter
measures the allowable variance in delay between one cell and the next. When emulating a
circuit, CDV measurements allow the network to determine if cells are arriving too quickly or
too slowly.
Cell
An ATM cell consists of 53 bytes or "octets." Of these, the first five constitute the header and
the remaining 48 carry the data payload.
CES
Circuit Emulation Service.
CIR.
Committed Information Rate.
This is the minimum throughput rate guaranteed by the Frame Relay carrier; however, users
can "burst" above this rate as necessary if bandwidth is available.
CLP
Cell Loss Priority.
The CLP is a priority bit in an ATM cell header. When the CLP= 1, it deflIles the cell to have
a low priority, an indication that the cell may be discarded. When the CLP=O, the cell has a
high priority and may not be discarded. It is used to help control traffic flow so switches and
end-stations are not overwhelmed and cells are not dropped indiscriminately. CLP is also a
Transmit Idle Header Values subfield on the INTERVIEW 8800 PLUS ATM unit's ATM
Interface Setup screen.
CLR
Cell Loss Ratio.
CLS
. ConnectionLess Service.
CPCS
Common Part Convergence Sublayer.
This sublayer of the ATM Adaptation Layer pads the Protocol Data Unit (PDU) to Nx48
bytes, maps control bits, and adds the Frame Check Sequence (FCS) in readiness for
segmentation and reassembly (SAR). It remains the same regardless of the type of traffic.
CPCS-UU
CPCS User-to-User indication.
This is used'to transparently transfer CPCS information from the origination user to the
destination user in the SDU trailer added in AAL 5.
CPE
Customer I'remises Equipment.
This describes equipment or hardware in use at the customer site.
CPI
Common Part Indicator.
The CPI is a I-byte subfield used to interpret the remainder of the fields in the CPCS header
and the trailer added forthe CPCS sublayer in AAL 3/4. For AAL 5, it is used to align the
CPCS-PDU trailer to the 32-bit boundary.
SEP'95
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
CRC
Cyclical Redundancy Check.
- In AAL 1, this is a 3-bit sequence that functions as an error check for the SN field only.
- In the SAR trailer in AAL 3/4, the CRC is a 10-bit sequence that functions as an error check
for the entire SAR-SDU, including the header, payload, and the LI field of the trailer.
- In AAL 5, it serves in the CPCS trailer as a 32-bit error check for the entire contents of the
CPCS-PDU, including the payload, the PAD field, and the first 4 bytes of the trailer. - In
OAM cells, the CRC is a lO-bit error check for the OAM payload, including the type indicators
and the function-specific fields.
CRS
Cell Relay Service.
CSI
DCC
. ConvergenceSublayer Indications.
This is a I-bit subfield which is used to convey CS-specific information for AAL 1. It is not
utilized for all AAL I implementations.
Here are four different definitions for DCC:
Data Country Code.
This code is supported in Private Address Format - 1.
or
Data Communications Channel.
This channel is an overhead connection in D bytes for SONET management.
or
Digital Cross Connect.
This is generic Digital Access and Cross-connect System (DACS).
or
Direct Connect Card.
This card is a data interface module on a T-1 bandwidth manager.
DS-3
Metallic Interface (44.736 Mbps) for ATM, with E3 (34.368 Mbps).
DXI
Data eXchange Interface.
This interface defines a format for passing data that has gone through the ATM convergence
sublayer between a router and a CSU/DSU or other device with ATM segmentation and
reassembly (SAR) capability. It is also a serial protocol for SNMP for any speed.
E1
This is the European standard for digital transmission service at 2.048 Mbps.
E3
This is the European standard for digital transmission service at 34.368 Mbps; E3 transports
sixteen E1 circuits. Metallic interface (34.368 Mbps) for ATM, with DS-3 (44.736 Mbps).
EFCI
Explicit Forward Congestion Indication.
This indicator is used to help control traffic flow so that switches and end-stations are not
overwhelmed and cells are not dropped indiscriminately. See FECN.
EPC
Even Parity Check.
This is a I-bit check of the previous seven bits of the AAL 1 header, i.e., the SN field and the
CRC subfield.
A-4
SEP '95
Etag
End Tag
Etag is a 1~byte "error check" for the segment in the CPCS trailer in AAL 3/4. The value in
this field is the same as the one which has been placed in the Btag field of the header. allowing
a quick comparison after receipt to determine if the PDU has been corrupted.
FEBE
Far End Block Error.
This is an alarm signal with counts of the BIP errors received.
PECN
Forward Explicit Congestion Notification.
This notifieris a Signalling bit in the Frame Relay header used to help control traffic flow so
that switches and end·stations are not overwhelmed and cells are not dropped indiscriminately.
FERF
Far End Receive Failure.
This is an alarm signal with errors detected in the Far End Receive Failure bit.
FRS
GCRA(I,L)
Frame Relay Service or Frame Relay Switch.
Generic Cell Rate Algorithm (Increment parameter, limit parameter).
This algorithm enables an ATM entity to measure andlor control negotiated service usage.
GFC
Generie Flow Control.
This is the firstbalf-byte in an ATM header at the User Network Interface. It is used to help
control traffic flow so that switches and end·stations are not overwhelmed and cells are not
droppe~ indiscriminately. Also, GFC is a Transmit Idle Header Values subfield on the
INTERVIEW 8800 PLUS ATM unifs ATM Interface Setup screen.
HEC
Header Error Control.
This code is an error checking device for the ATM header contained in a single byte in the
header. It contains the information for the ATM physical layer's transmission convergence
sublayer to perform error detection on the cell header. If errors are found, the cell is dropped
before the processing moves up to the ATM layer for routing.
ICD
International Code Designator.
This designator is supported in Private Address Format - 1.
ICIP
Intercarrier Interface Protocol.
This protocol services the connection between two public networks.
IE
IEC
Information Element.
Inter-Exchange Carrier.
This is a long distance company which carries traffic between Local Access and Transport
Areas (LATAs).
IETF
Internet Engineering Task Force.
This body adopts Requests For Comment (RFCs).
ILMI
Interim Local Management Interface.
This is the Permanent Vinual Connection (PVC) management in AIM.
IP
Internet Protocol.
This is the network layer 2 basis for protocols such as TCP and UDP.
IWF
InterWorking Functions.
This is the conversation process between Frame Relay and X25, between Frame Relay and
ATM, and so on.
SEP'95
A-5
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
LAN
Local Area Network.
LAN is a data communications network spanning a limited geographical area (a few miles at
most), providing communication between computers and peripherals, with some switching to
direct messages.
LB
Leaky Bucket algorithm.
This algorithm is a form of flow control: it checks an arriving data stream against the
traffic-shaping parameters specified by the sender as follows: The data is stored in a memory
buffer (bucket) which is allowed to fill, but not overflow. The data is allowed to flow out (leak)
allowing more data to be added to the buffer. Excess data is either dropped or routed to
another memory buffer which performs the same process, keeping the traffic parameters
intact.
LEC
Local Exchange Carrier.
An LEC is a TELCO.
Length
Used to indicate the length of the PDU payload. This field is encoded in the CPCS trailer in
AAL 3/4 to indicate the number of counting units in the length of the payload, with the
counting unit size indicated in the CPI of the header. For AAL 5, it is also a 2-byte field in the
CPCS trailer used to indicate the length of the CPCS payload (not including the PAD bytes).
LI
Length Indication.
The LI is the 6-bit field which is binary encoded in the SAR trailer in AAL 3/4 to indicate the
number of bytes of the CPCS-PDU which are contained in the payload portion of the segment.
For the BOM and COM segments this value must be 44. For BOM segments, the value can
range from 4 to 44 as appropriate. For SSM segments, permissible values range from 8 to 44.
LOC
Loss of Cell (delineation).
This condition indicates a loss of cell alignment.
LOF
Loss of Frame.
A LOF condition occurs when the mux cannot fmd framing (OOF) for 2.5 seconds.
LOS
Loss of Signal.
This is an indication that there is no received data; no incoming signal is detected.
MAN
Metropolitan Area Network.
This is an area network which typically runs at 100 Mbps.
MBS
Maximum Burst Size.
This is the number of cells that may be sent at the Peak Cell Rate (PCR) without exceeding
the Sustainable Cell Rate (SCR).
MF
Multi-Frequency.
This is tone signalling on analog circuits.
MIB
Management Information Base.
This is a description of a network for management purposes as defined by OSI, the seven-layer
protocol model defined by the International Organization for Standardization.
MID
. Message IDentifier or Message IDentification.
This is a sequence number shared by all Layer 2 Protocol Data Units holding segments of one
Layer 3 Protocol Data Unit as defined for SMDS. For AAL 3/4, it is the same for all segments
of the same frame.
A-6
SEP '95
ABpti!1dixA ArM Glossary and Acronyms
MID
NLPID
Multiplexing Identification.
This is used to multiplex CPCS connections on a single ATM Layer connection, when
applicable. in the SAR header in AAL 3/4.
Network Layer Protocol IDentifier.
This is a control field in the frame header which identifies encapsulated protocols.
NNI
Network-Network Interface.
This interface is between carriers or a carrier and a private network as defined for Frame Relay.
NNI
Network-NOde Interface.
This is a point-to-point interface between two switches for SDH, SONET, or B-ISDN networks.
NPC
Network Parameter ControL
NRM
Network Resource Management.
NSAP
Network Service Access Point.
This is a logical address of a user in an OS! protocol stack.
NT
Network Termination.
An NT is a device on the customer premises end of the local loop, such as a CSU or a DSU.
OA&M
Operations, Administration, and Maintenance.
OA&M cells perform a range of diverse network management functions. Such functions
include fault and performance management (operations); addressing. data collection, and
usage monitoring (administration); and analysis, diagnosis. and repair of network faults
(maintenance). OAM cells do not aid in segmentation and reassembly.
oc-!
Optical Carrier level l.
OC-! is a SONET rate of 51.84 Mbps which matches STS-l.
OC-3
Optical Carrier level 3.
OC-3 is a SONET rate of 155.52 Mbps which matches STS-3.
OC-3c
Optical interface for ATM which transmits OC-3 optical signals.
OOF
Out Of Frame.
This condition occurs with a loss of frame alignment.
PCR
Peak Cell Rate.
This is a traffic parameter applied per Virtual Circuit. Virtual Path, or channel for ATM. It is
the maximum rate at which cells can be transmitted across a virtual circuit, specified in cells
per second·and defined by the intelVal between the transmissions of the last bit of one cell and
the first bit of the next.
PDN
Public Data Network.
A PDN is generally a packetized network.
PDU
Protocol Data Unit.
This is an informational packet or frame which, in the appropriate format. can then be
segmented and encapsulated in the payload of an ATM cell.
SEP'95
A-7
--~--------
_____
....._____
._m_J&_Qil~
____
JIj . . . .
..
_t.¥.'' ' ' ' '_ _
........
~1I_1II _~1!'''''II
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
PRY
PHYsical Layer.
The physical layer of the OSI protocol stack is Layer 1; the physical layer of the ATM protocol
stack is the bottom layer, which defines the interface between ATM traffic and the physicaJ
media. The ATM PHY consists of two sublayers: the physical mediumdependent (PMD) sublayer and the transmission convergence (TC) sublayer.
PLCP
Physical Layer Convergence Protocol.
The PLCP is the part of the physical layer that adapts transmission medium to handle a given
protocol sublayer. It is a protocol specified within the TC sublayer that defines how cells are
formatted within a data stream for a particular transmission facility, such as TI, T3, or OC-n.
PMD
Physical Medium-Dependent sublayer.
The ATM PRY sub layer which defines the actual speed at which ATM traffic can be
transmitted across a given physical medium is the PMD. It also defines a sublayer in layer 1 of
LAN protocols.
IT! (also PT)
Payload Type Identifier.
Tl¥s is a control field in the ATM header which identifies the type of data in the payload:
Bit 3 = discriminate cells
Bit 2 = 0 to indicate congestion in data cells
Bit 1 = carried transparently end-end in AAL 5
PVC
Permanent Virtual Connection or Permanent Virtual Circuit.
A PVC is an assigned connection over a packet, frame, or cell network. Such connections are
not switch able by the user; they are virtual links with fIXed end-points as defined by the
network manager. A single virtual path may support multiple PVCs.
QoS
Quality of Service.
There are five broad quality of services classes as defined by the ATM Forum's UNI 3.0:
Class 1 - specifies performance requirements.
Class 2 - specifies necessary service levels for packetized video and voice.
Class 3 - specifies interoperability requirements with other connection-oriented protocols.
Class 4 - specifies interoperability requirements with other connectionless protocols.
Class 5 - addresses interoperability with applications that do not require a particular class of service.
RDI
Remote Defect Indicator.
This is a yellow alarm signal with remote errors detected in STS-l framing at 51.840 Mbps for
coaxial signals. A Path Yellow alarm (Remote Defect Indicator) is detected if the path yellow bit in
the Gl octet is set for ten consecutive frames; Line Remote Defect Indicator Errors are detected if
the three Least Significant Bits of the K2 octet are set to 110 for five consecutive frames.
SAP
Service Access Point.
The logical address of a session within a physical station is a Service Access Point. It is part of
a header address at an interface between sublayers.
SAR
Segmentation And Reassembly.
The SAR is protocol sublayer that converts Protocol Data Units into appropriate lengths and
formats them to fit the payload of an ATM cell (segmentation). At the destination end, it
extracts the payloads from the cells and converts them back into PDUs (reassembly), which can
then be passed higher up the protocol stack for use in other applications.
A-a
SEP '95
ARpendix A ATM Glo§§!ly and Acronyms
SC
Sequence Count.
This is a 3-bit sequence number for the entire CS-PDU for AAL 1. This is generated by the
CS and remains constant for all segments created from that CS-PDU.
SC
Type of fiber optic connector, square in appearance. (See also S1; round fiber optic
connector.)
SCR
Sustainable Cell Rate.
SCR is a traffic parameter for ATM; it represents the maximum throughput that bursty traffic
can achieve within a given virtual circuit without risking any cell loss.
SDH
Synchronous Digital Hierarchy.
This international version of SONET is a digital multiplexing plan in which all levels are
synched to the same master dock.
SDU
Service Data Unit.
An SOU is an information packet or segment which is passed down to become the payload of
the adjacent lower layer in a protocol stack.
SIP
SMOS Interface Protocol.
SMDS
Switched Multi-megabit Data Service.
This is a data service offered on a Metropolitan Area Network by a carrier; it is a service mark
of Bellcore.
SN
Sequence Number.
This is a 4-bit field of the l-byte Segmentation And Reassambly (SAR) header in AAL 1 which
indicates the sequence number information for tbe>segment. In AAL 3/4, the 4-bit SN field in
the SAR header allows the stream of SAR Service Data Units (SDUs) to be numbered using
modulo 16 in order to provide a Hloss of segment" check for each full PDU that is segmented.
SNP
Sequence Number Protection.
This is a 4-bit field which provides the error-checking mechanism for the Segmentation And
Reassambly (SAR) header in AAL 1.
SNAP
SubNetwork Access Protocol.
SNAP is an access protocol which identifies an encapsulated protocol and user.
SNMP
Simple Network Management Protocol.
SNMP is a Layer 4 and 5 management protocol which started in TCP/IP; it now extends to
many LAN devices.
SONET
Synchronous Optical Network.
SONET is an international suite of standards for transmitting digital information over optical
interfaces. "Synchronous" indicates that all component portions of the SONET signal can be
tied to a single reference clock.
SSCS
Service-Specific Convergence Sublayer.
This sublayer is the portion of the convergence sublayer that is dependent upon the type of
traffic that is being converted. Examples are the Frame Relay service-specific convergence
sublayer (FR-SSCS) and the Switched Multimegabit Data Service service-specific convergence
sublayer (SMDS-SSCS).
SEP '95
A-9
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
ST
Segment Type.
This is a 2-bit field found in the SAR header in AAL 3/4; it consists of one of the four possible
segment types: Beginning of Message (BOM), Continuation of Message (COM), End of
Message (EOM), or Single Segment Message (SSM).
ST
Type of fiber optic connector, round in appearance. (See also SC, square fiber optic connector.)
STS-l
Metallic Interface (51.84 Mbps) for ATM.
STM
Synchronous Transfer Mode.
This is one of several possible formats for SONET and B-ISDN. It is a communications
method that transmits a group of different data streams which are synchronized to a single
reference clock; all data receives the same amount of bandwidth. STM is the standard method
carriers use to assign time slots or channels within a Tl/Elleased line.
SVC
Switched Virtual Connection or Switched Virtual Circuit.
This is a temporary logical connection in a packet/frame network; it is a virtual link, having
variable end-points, which is established through an ATM network. With an SVC, the user
defines the end-points when the call is initiated, as opposed to a Permanent Virtual Circuit
(PVC) in which the end-points are predefined by the network manager. A single virtual path
may support multiple SVCs.
Tl
Tl is a digital transmission service with a basic data rate of 1.544 Mbps.
T3
T3 is a digital transmission service with a basic data rate of 44.736 Mbps for transport of 28 Tl
circuits.
TCorTCS
Transmission Convergence (Sublayer).
This sublayer is a part of the ATM physical layer. It defines a protocol for preparing cells for
transmission across the physical media defined by the physical media-dependent (PMD)
sublayer. The function of the TC sublayer differs according to the physical medium.
TDM
Time Division Multiplexing.
This is also known as Synchronous Transfer Mode.
TE
Terminal Equipment.
A TE is any piece of equipment that supports native ISDN or B-ISDN formats without a
terminal adapter.
TM
Traffic Management.
This consists of various mechanisms that control traffic flow so that switches and end-stations
are not overwhelmed and cells are not dropped indiscriminately.
TS
Traffic Shaping.
This allows the sender to specify the throughput and the priority of information entering the
ATM network; it allows the sender to monitor progress to ascertain if service levels are met.
UNI
User Network Interface.
This is the protocol defined by the ATM Forum to define connections between an ATM user
(end-station) and the ATM network (switch). UNI version 3.0, (1993) specifies the complete
range of ATM traffic characteristics, including cell structure, addressing, signaling, adaptation
layers, and traffic management. It is the demark point of ATM, SDH, and B-ISDN at
customer premises.
A-10
SEP '95
Appendix A ArM G10ssaa and Acronyms
UPC
Usage Parameter Control.
This prevents congestion by not admitting excess traffic onto the network when all resources
are in use. It changes the Cell Loss Priority (CLP) bit of cells that exceed traffic parameters to
they are dropped; it is a flow control in an ATM cell.
VBR
Variable Bit Rate.
This type of data traffic can tolerate delays and fluctuating throughput. It is packetized bandwidth
on demand, not dedicated bandwidth. It is information that can be represented digitally by groups
of bits (as opposed to bit streams). Most data applications generate VBR traffic.
VC
Vutuai Chap.nel (Circuit).
This is a defined route between two end-points in an ATM network, but it may travel over
several virtual paths; a portion of a virtual path or a virtual channel that is used to establish a
single virtual connection between two end-points.
VCC
Virtual Channel (Circuit) Connection.
This is a unique numerical tag used to identify every virtual channel across an ATM network,
defined by a 16-bit field in the ATM cell header.
VCI
Virtual Channel (Circuit) Identifier.
This is part of a packet/frame/cell address in an ATM header.
VP
Virtual Path.
This is a group of virtual channels, which can support multiple virtual circuits.
VPC
Virtual Path Connection.
This is a virtual connection established using only the Virtual Path Identifier (VPI).
VPI
Virtual. Path Identifier.
A VPI is an 8-bit field in the ATM cell header that indicates the virtual path over which a cell
is to be routed.
WAN
Wide Area Network.
This is the T-l, T-3 or broadband backbone that covers a large geographical area.
SEP '95
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
A-12
SEP '95
ARpendlx B ATM Unit Specifications
Appendix B ATM Unit Specifications
SEP'95
8-1
INTERVIEW 8000 Series - ATM (Broadband): 985-B0682-01
Interface Module (AIM) access door
IU$CU-Tft tai JD
D\IIIIIDn~$CIIII"","
0000000000
tOS ,Of, 103
*
1001 1C7lM,2'" H$
,,3
IIII:lQ
00
1H 114
-
.....\
Figure B-1 INTERVIEW 8800 PLUS ATM modeL Note ATM Interface Module (AIM) hinged access door on top left of unit,
B-2
SEP '95
lWp!ndlx B ATM Unit Specifications
Appendix B ATM Unit Specifications
The INTERVIEW 8800 PLUS ATM model, as shown in Figure B-1, has been designed specifically
for ATM broadband testing, while simultaneously testing WAN protocols. As such, it has some
unique hardware.
The INTERVIEW 8800 PLUS ATM model has a Bus Bridge Board on the MPM board in Slot 9.
This is the ATM-connection to the base unit. The bridge board connects to the new AIM Cell
Engine .... (ACE ..... ) board housed in the ATM enclosure on the top of the cover. The hinged~door
to the ATM enclosure gives access to the ATM Interface Modules (AIMs), which are also housed in
the enclosure, as indicated in Figure B-1.
The INTERVIEW 8750 ATM EXPRESS model has the same appearance as and tests ATM the
same as the INTERVIEW 8800 PLUS ATM. However, it has no WAN-testing capabilities. As
shown in Figure B·3; it has neither an FEB board nor a DMA MPM (and it therefore also weighs
slightly less than the PLUS ATM unit). Any references made to ATM testing by the INTERVIEW
8800 PLUS ATM model also apply to ATM testing with the INTERVIEW 8750 ATM EXPRESS
model.
B.1
Upgrading to ATM (Broadband) Testing
Any standard INTERVIEW 8000 TURBO Series unit can be upgraded to become an
INTERVIEW 8800 PLUS ATM unit in the following steps:
•
upgrade the unit to an 8800:
OPT-9S1-536-X
•
upgrade the 8800 to an ATM.ready unit:
OPT-951-301-1
•
upgrade the 8800 ATM-ready unit to an 8800 PLUS ATM:
OPT-951-300-1
Some of the latest 8800 TURBO production units already have ATM~ready hardware, so
only the last step would be necessary for those units. Likewise, an 8800 TURBO would not
require the first step.
Contact Customer Service for information on the upgrade status of your hardware.
SEP '95
8-3
INTERVIEW 8000 Series - ATM (Broadband): 985-80682-01
Slot 1: Optional MUX Board
Slot 2: GBM Board
Slot 3: CPM Board
6, 7: MPM Boards
8: MPM Board with DMA Card
9: MPM Board with
Bus Bridge Board
to connect to
ATM Cell Engine'"
Power
(DANGER)
Hard __~~I+
Disk
Drive
__"":'~::J
Slot 0: Optional
ISDN Halt-card
Board Position
(Between Hard Drive
and Slot 1)
Area behind
LED Display
(DANGER)
Figure B-2 Viewing interior components of the INTERVIEW 8800 ATM base unit.
8-4
SEP '95
Appendix B ATM Unit Specfflcations
B.2
Interior Components of PLUS ATM
The inside of your INTERVIEW reveals three potentially hazardous areas. DO NOT
TOUCH THESE AREAS OR INJURY MAY RESULT! These three danger areas include
the mechanical fan at the center back of the unit (physical hazard), the power supply at the
back right side of the unit (230V shock hazard), and the area directly behind the LED
display (l90V shock hazard). See Figure B-2 for their locations. The front of the power
supply supports two DB-25 connectors for power to the ATM top enclosure.
In addition to these three potentially hazardous components, on the left near the front of
your unit is the SCSI hard disk drive; one cable (labeled 3 in Figure B-2) runs over the top
of the drive and is connected to the CPM board.
Immediately behind the hard disk drive is the TIM (Thst Interface Module) holder; its
cable runs around the side of the unit .and connects to the hard., A-5
IWF,A-5
IE,A-5
L AIS. softkey, 11·9
L RDI, softkey, 11-10
LAN,A-6
LAN Emulation, emulation application program,
2-6
LAN Emulation protocols, in application program,
IEC,A~5
IETF,A-S
ILMI,A-5
ATM (Broadband) testing, management protocol,
2-3
in application program, 2-5
Injecting errors, in application program, 2-7
Installation, ATM Interface Module, 5-11
Interface accessory kits, 5-7, 5-9
Interface Control screen, unavailable for INTERVIEW 8750 ATM EXPRESS, 3-3
Interfaces
metallic, overview, 5-5
optical, ovelView, 5-6
Internal Loop A mode
for AIM-302-I, 7-5
sample setup screen, 7-9
setup screen selections, 7-6
SEP '95
L
2-5
LAN encapsulation, VBR data application, INTERVIEW 8800 PLUS ATM, 2-3
LANE, emulation application program, 2-6
LASER, danger from, 5-5,5-7, 5-8, 6-2
LB,A-6
LEC,A·6
Length, 1-14, 1-19, A-6
LI,A-6
Line AIS, statistics for ATM Interface Module,
STS-1,1O-17
Line Code Violations, statistics for ATM Interface
Module
DS-3 direct, 10-6
ATM Index-13
DS-3 PLCp, 10-9
E3 direct, 10-12
E3 PLCp, 10-15
STS-l,1O-18
Line FEBE Errors, statistics for ATM Interface
Module, STS-1, 10-20
Line Impedance, field on ATM Interface Setup
screen
for AIM-302-1
Emulate A mode, 7-8
Internal Loop A mode, 7-8
Monitor mode, 7-4
for AIM-305-1
Emulate A mode, 8-7
Internal Loop A mode, 8-7
Monitor mode, 8-4
for AIM - 306-1
Emulate A mode, 9-7
Internal Loop A mode, 9-7
Monitor mode, 9-4
Line RDI Errors, statistics for ATM Interface Module, STS-l, 10-20
Line Setup screen
disabled,2-10
for the INTERVIEW 8800 PLUS ATM, for allocating memory, 2-10
DISABLE softkey, 2-10
unavailable for INTERVIEW 8750 ATM EXPRESS, 3-3
Line violations, statistics, 10-1
LOC,A-6
statistics for ATM Interface Module
DS-3 direct, 10-5
E3 direct, 10-12
STS-l,1O-18
LOF,A-6
LOS,A-6
Lost cells, in application program, 2-7
M
MA FEBE Errors, statistics for ATM Interface
Module, E3 direct, 10-13
MA FERF, softkey, 11-8
MA FERF Errors, statistics for ATM Interface
Module, E3 direct, 10-13
MA TIME, softkey, 11-8
ATM Index-14
Maintain, field on ATM Interface Setup screen
for AIM-302-1
Emulate A mode, 7-8
Emulate B mode, 7-13
Internal Loop A mode, 7-8
Internal Loop B mode, 7-13
Monitor mode, 7-5
for AIM-305-1
Emulate A mode, 8-8
Internal Loop A mode, 8-8
Monitor mode, 8-4
for AIM - 306-1
Emulate A mode, 9-7
Emulate B mode, 9-13
Internal Loop A mode, 9-7
Internal Loop B mode, 9-13
Monitor mode, 9-5
MAN,A-6
Management protocol, ILMI, ATM (Broadband)
testing, 2-3
MBS,A-6
Media, ATM, 1-5
Memory allocation, with the INTERVIEW 8800
PLUS ATM, for ATM (Broadband) testing, 2-9
Metallic interfaces, overview, 5-5
MF,A-6
MIB,A-6
MID, 1-16, A-6
Misinserted cells, in application program, 2-7
MODE, softkey, 11-2
Mode field
AIM-302-1, 7-2, 8-2
AIM-30S-1,8-2
AIM-306-1,9-2
Monitor mode, 4-1
for AIM-302-1, 7-3-7-5
sample setup screen, 7-3
setup screen selections, 7-4
for AIM-305-1, 8-3-8-5
sample setup screen, 8-3
setup screen selections, 8-4
for AIM-306-1, 9-3-9-5
sample setup screen, 9-3
setup screen selections, 9-4
Monitor Transmission, field on ATM Interface Setup screen
for AIM-302-1
Emulate A mode, 7-7
Emulate B mode, 7-12
SEP '95
Internal Loop A mode, 7-7
Internal Loop B mode, 7-12
for AIM-305-1
Emulate A mode, 8-7
Internal Loop A mode, 8-7
for AIM -306-1
Emulate A mode, 9-7
Emulate B mode, 9-11
Internal Loop A mode, 9-7
Internal Loop B mode, 9-11
Monitoring
cable diagrams
with coaxial cables, 6-14-,.6-15
with multi-mode optical cables, 6-34-6-37
with single-mode opticiJ. cables, 6-20-6-25
in repeater mode, 4-1
with splitter cables, 4-1
MPM board, view as a component, B-4, B-6
for AIM-306-1
Emulate A mode, 9-10
Emulate B mode, 9-14
Internal Loop A mode, 9-10
Internal Loop B mode, 9-14
Nibble-stuffing, D8-3 PLCP framing, 1-23
NLPID,A-7
NNI,A-7
NPC,A-7
NRM,A-7
NSAP,A-7
NT,A-7
o
MPM boards, switch settings
for ATM EXPRESS units, B-8
for PLUS ATM units, B-8
OA&M,A-7
See also OAM Cells
MULHEC, softkey, 11-3,11-4, U-5
OAM cells, in ATM, 1-21
Multi-mode optical cables, 6-11
adaptor, 6-13
coupler, 6-13,6-14
splitter, 6-12
OC-1,A-7
Multi-mode optical interfaces
Emulate A mode, 4-2
Emulate B mode, 4-3
Internal Loopback A mode, 4-3
Internal Loopback B mode, 4-3
Monitor mode, 4-2
OOF,A-7
Multimode fiber optical cables, 5-7, 5-9
Multimode optical cables, 6-5
N
NCI, lfansmit Idle Header Values subfield, field on
ATM Interface Setup screen, SMDS cell format
for AIM-302-1
Emulate A mode, 7-10
Emulate B mode, 7-15
Internal Loop A mode, 7-10
Internal Loop B mode, 7-15
for AIM-305-1
Emulate A mode, 8-9
Internal Loop A mode, 8-9
SEP'95
OAM. See OA&M
OC-3,A-7
OC-3c, 5-7, 5-8, 5-9,64,6-2, A-7
Operating modes, 4-1
Operations and Maintenance cells. See OAM cells
Optical accessory kits, 5-10
Optical cables
multi-mode, 6-11
adaptor, 6-13
cou~er,6-13.6-14
splitter, 6-12
single-mode, 6-7
adaptor, 6-9
attenuator, 6-9
coupler, 6-10
splitter, 6-8
Optical interfaces, overview, 5-6
Optical signal, long-reach, 5-7
OSI
Data Link Layer 2, in ATM, 1-2
Physical Medium Layer 1, in ATM, 1-2
Out-of-Frame, statistics for ATM Interface Module,
E3 PLCP, 1()..14
ATM Index-15
p
Physical Layer, in ATM, 1-3
PAlS, softkey, 11-12
Physical Layer Convergence Protocol. See PLCP
framing
P FERF, softkey, 11-12
Physical Layer Statistics, 10-1
P RDI, softkey, 11-11
PHYSTAT softkey, 10-3, 10-6,10-11,10-13,10-16
Packet -switching features, for ATM, 1-1
PLCp,A-8
Path AlS, statistics for ATM Interface Module,
STS-l,10-18
Path configuration, in application program, 2-5
PLCP BIP Errors, statistics for ATM Interface
Module
OS-3 PLcp, 10-10
E3 PLCp, 10-16
Path FEBE Errors, statistics for ATM Interface
Module, STS-l, 10-19
PLCP FEBE All Ones, statistics for ATM Interface
Module, OS-3 PLCp, 10-10
Path PERF Errors, statistics for ATM Interface
Module, STS-l, 10-20
PLCP FEBE Errors, statistics for ATM Interface
Module
OS-3 direct, 10-6
OS-3 PLcp, 10-10
E3 PLCp, 10-16
Path RDI, statistics for ATM Interface Module,
STS-l,10-18
PAY CRC, softkey, 11-3,11-4,11-5
Pay. Type Mismatch, statistics for ATM Interface
Module, E3 direct, 10-13
Payload Scrambling, field on ATM Interface Setup
screen
for AIM-302-1
Emulate A mode, 7-9
Emulate B mode, 7-13
Internal Loop A mode, 7-9
Internal Loop B mode, 7-13
Monitor mode, 7-5
for AIM-305-1
Emulate A mode, 8-8
Internal Loop A mode, 8-8
Monitor mode, 8-5
for AIM-306-1
Emulate A mode, 9-9
Emulate B mode, 9-13
Internal Loop A mode, 9-9
Internal Loop B mode, 9-13
Monitor mode, 9-5
PCM board, view as a component, B-4, B-6
PCR,A-7
PON,A-7
POU,A-7
PHY,A-8
Physical dimensions, size and weight
INTERVIEW 8750 ATM EXPRESS, 3-1
INTERVIEW 8800 PLUS ATM, 2-3
Physical indicators
alarms, ATM (Broadband) testing, 2-3
errors, ATM (Broadband) testing, 2-3
ATM Index-16
PLCP Frame Errors, statistics for ATM Interface
Module
OS-3 PLCp, 10-10
E3 PLCp, 10-16
PLCP framing
for ATM,l-1, 2-7
inATM,1-3
PLCP Gl RAI, statistics for ATM Interface Module, OS - 3 PLCp, 10-8
PLCP Invalid FEBE, statistics for ATM Interface
Module, OS-3 PLcp, 10-10
PLCP LOF, statistics for ATM Interface Module
OS-3 PLcp, 10-8
E3 PLCp, 10-14
PLCP LOF 2-3, statistics for ATM Interface Module
OS - 3 PLCp, 10-8
E3 PLCp, 10-15
PLCP mapping, for OS3 format, 1-23
PLCP OOF, statistics for ATM Interface Module
OS-3 PLCp, 10-8
E3 PLCp, 10-14
PLCP Yellow, statistics for ATM Interface Module,
E3 PLCp, 10-15
PMO,A-8
Power up
INTERVIEW 8750 ATM EXPRESS, 3-1
screen display, 3-2
INTERVIEW 8800 PLUS ATM, 2-8
screen display, 2-8
Precautions, with fiber optical cables and accessories,6-3
SEP '95
Program menu, INTERVIEW 8750 ATM EX~
PRESS, 3-2
altered screen display, 3--3
Programming, for INTERVIEW 8000 Series units,
2-9
Protocol testing (WAN), INTERVIEW 8800 PLUS
ATM,2-7
n
TIansmit Idle Header Values subfield, field on
ATM Interface Setup screen, ATM UNI cell
format
for AIM-302-1
Emulate A mode, 7-10
Emulate B mode, 7-14
Internal Loop A mode, 7-10
Internal Loop B mode, 7-14
for AIM-305-1
Emulate A mode, 8-9
Internal Loop A mode, 8-9
for AIM-306-1
Emulate A mode, 9-10
Emulate B mode, 9-14
Internal Loop A mode, 9-10
Internal Loop B mode, 9·14
PTI, 1-7, A-8
PVC,A-8
Reload, field on ATM Interface Setup screen
for AIM-302-1
Emulate A mode, 7-8
Emulate B mode, 7-13
Internal Loop A mode, 7-8
Internal Loop B mode, 7·13
Monitor mode, 7-5
for AIM-305-1
Emulate A mode, 8-8
Internal Loop A mode, 8-8
Monitor mode, 84
for AIM-306-1
Emulate A mode, 9-9
Emulate B mode, 9-13
Internal Loop A mode, 9-9
Internal Loop B mode, 9-13
Monitor mode, 9-5
Repeater mode, for monitoring. 4-1
RFC-1483, in application program, 2-5
RFC-1577, in application program, 2-5
RG-59, coaxial cables, 6-6
RX
connector for DS- 3/E3ISTS-l, metallic receive
connectors for Side A and Side B. 5~8. 5-9
connector for SONEr OC- 3c and SDH STM -1,
single- and multi -mode receive fiber optic,
5-8, 5~9
Q
QoS,A-8
s
QOS measurements, ATM (Broadband) testing.
cell-level testing, 2-3
SAP,A-8
Quality.Of Service measurement, in application
program, 2-7
SAR header, in ATM, AAL 3/4, 1-16
R
FU\11E,softkey, 11-1, 11-5
Rate, statistics column heading, 10-1
Raw cells, in application program, 2-5
Rcvd A, statistics column heading, 10-1
Rcvd B, statistics column heading, 10-1
Rcvd T, statistics column heading, 10-1
RDI,A-8
Reassembled packets, in apJ,>lication program, 2-5
Recording WAN data, while simultaneously testing
ATM (Broadband), 2·9
SEP '95
SAR,A-8
SAR trailer, in ATM, AAL 3/4, 1-16
SC, 1-11, A-9
SC connectors, 6-5
SCR,A-9
SDH,A-9
SDH frames, ATM, 1-5
SDU,A-9
Service-level testing
CBR, ATM (Broadband) testing, 2-3
content, ATM (Broadband) testing, 2-3
encapsulated protocols, ATM (Broadband) testing,2-3
format, ATM (Broadband) testing, 2-3
VBR, ATM (Broadband) testing, 2-3
Setup Menu, 7-1, 8-1, 9-1
ATM Index-17
SETUP softkey, 3-3
Sig Label Mismatch, statistics for ATM Interface
Module, STS-1, 10-20
Signal
type and sensitivity, 6-14
type and strength, 6-1
Signal Fault, statistics for ATM Interface Module
DS-3 direct, 104
DS-3 PLCp, 10-7
E3 direct, 10-11
E3 PLCp, 10-14
STS-1,10-17
STS-3cISTM-1,10-20
Signal levels, 5-7
Signal-fault seconds, statistics, 10-1
Signalling and management, B- ISDN signalling,
ATM (Broadband) testing, 2-3
Signalling Circuit, emulation application program,
2-6
SINGLE, softkey, 11-2
Single-mode fiber optical cables, long-reach, 5-7
Single-mode optical cables, 6-5,6-7
adaptor, 6-9
attenuator, 6-9
coupler, 6-10
splitter, 6-8
Single-mode optical interfaces
Emulate A mode, 4-2
Emulate B mode, 4-3
Internal Loopback A mode, 4-3
Internal Loopback B mode, 4-3
Monitor mode, 4-1
1 FEBE, 11-6, 11-8, 11-9
AlS, 11-7, 11-9
Bl, 11-3, 11-4,11-5
B2,114
B21,11-5
B22,11-5
B2 3,11-5
B2ALL,11-5
B3, 114, 11-5
BURS,!; 11-2
CLP ON, 11-6,11-8,11-9
COND, 11-6, 11-8, 11-9
CONTIN,11-2
EM BIP, 11-3
EVEN'!; 11-2
G1 RAI, 11-7
IDLE, 11-2, 11-7
LAIS, 11-9
LRDI,11-10
MA FERF, 11-8
MA TIME, 11-8
MODE,11-2
MUL HEC, 11-3,11-4,11-5
PAIS, 11-12
P FERF, 11-12
PRDI,l1-11
PAY CRC, 11-3,11-4,11-5
RATE, 11-1, 11-5
SINGLE,11-2
SNG HEC, 11-3, 11-4
SPE UN, 11-12
XRAI,11-7
SONET,A-9
SONET frames, ATM, 1-5
SNMp, A-9
SPE Cell Mapping, field on ATM Interface Setup
screen
for AIM-302-1
Emulate A mode, 7-7
Internal Loop A mode, 7-7
Monitor mode, 7-4
for AIM-305-1
Emulate A mode, 8-7
Internal Loop A mode, 8-7
Monitor mode, 8-3
for AIM-306-1
Emulate A mode, 9-6
Internal Loop A mode, 9-6
Monitor mode, 9-4
SNp, 1-10, A-9
SPE UN, softkey, 11-12
Softkey racks, for physical layer statistics, 10-2
Splitter cable, colors, 6-5
Softkeys
oFEBE, 11-6, 11-8, 11-9
Splitter cables, for monitoring, 4-1
SIp, A-9
SMDS,A-9
in application program, 2-5
on -line application programs, 2-4
VBR data application, INTERVIEW 8800 PLUS
ATM,2-3
SN, 1-10, 1-16, A-9
SNAP,A-9
SNG HEC, softkey, 11-3, 11-4
ATM Index-18
SSCS,A-9
SEP'95
ST, 1-16, A-I0
ST connectors, 6-5
Static electricity. precautions, 5-11
Statistics
AIM 302
OS- 3 direct, sample screen
first page, 10-4
second page, 10-5
OS-3 PLCp, sample screen
first page, 10-7
second page, 10-9
E3, sample screen, first page, 10-11
E3 direct, sample screen, second page, 10-12
E3 PLcp, sample screen
first page, 10-14
second page, 10-1S
STS-I, sample screen
first page, 10-17
second page, 10-19
ATM Interface Module
OS-3direct
OS3 AIS, 10-4
OS3 Frame Errors, 10--6
OS3 Idle Code, 10-5
OS300F, 10-4
OS3 Parity Errors, 10-6
OS3 Path Parity Errs, 10-6
OS3 X-bit RAI, 10-5
Line Code Violations, 10-6
LOC,10-5
PLCP PEBE Errors, 10-6
Signal Fault, 10-4
DS-3PLCP
OS3 AIS, 10-7
OS3 FEBE Errors, 10-10
OS3 Frame Errors, 10-9
DS3 Idle Code, 10-8
OS300F, 10-7
DS3 Parity Errors, 10-9
OS3 Path Parity Errs, 10-10
DS3 X -bit RAJ, 10-8
Line Code Violations,! 0-9
PLCP BIP Errors, 10-10
PLCP FEBE All Ones, 10-10
PLCP FEDE Erro~ 10-10
PLCP Frame Errors, 10-10
PLCP G 1 RAI, 10-8
PLCP Invalid FEBE, 1'0-10
PLCP LOF, 10-8
PLCPLOF2-3,1O-8
PLCP OOF, 10-8
Signal Fault, 10-7
SEP '95
E3direct
Bl BIPErrors, 10-13
E3 AIS, 10-11
E3 LOF, 10·12
E3 LOF2-3, 10-12
E3 OOF, 10-12
EM BIP Errors, 10-13
Line Code Violations, 10-12
LOC, 10-12
MA FEBE Errors, 10-13
MA FERF Errors, 10-13
Pay. 1)rpe Mismatch, 10-13
Signal Fault, 10-11
E3PLCP
A-bit Yellow, 10-15
Alarm Ind Signal, 10-14
FEBE All Ones, 10-16
Frame Errors, l()..IS
Invalid FEBE, 10-16
Line Code Violations, 10-15
Out-of-Frame,10-14
PLCP BIP Errors. 10-16
PLCP PEDE Errors, 10-16
PLCP Frame Errors, 10-16
PLCP LOp, 10-14
PLCP LOF 2-3, 10-15
PLCP OOp, 1()"14
PLCPYellow, 10-15
Signal Fault, 10-14
STS-l
B1 SIP Errors, 10-19
B2 BIP Errors, 10-19
B3 BIP Errors, 10-19
Line AIS, 10-17
Line Code Violations, 10-18
Line FEBE Errors, 10-20
Line ROI Errors, 10-20
LOC,10-18
Path AIS, 10·18
Path PEDE Errors, 10-19
Path PERF Errors, 10-20
Path RDI. 10-18
Sig Label Mismatch, 10-20
Signal Fault, 1()"17
STS LOF, 10-I8
STS LOF 2-3.10-18
STS LOp, 10-17
STS OOF, 10-18
STS-3c/STM-l. Signal Fault, 10-20
column heading
C for "Current", 10-1
Rate, 10-1
RcvdA,lO-1
Rcvd S, 10-1
Rcvd T, 10-1
ATM Index-19
DS-3framing
53-octet d~ect,
57-octet PLCp, 10:'6
"'-.
E3framing
53 -octet direct, 10-10
57 -octet PLCP, 10-13
error conditions, 10-1
error injection, 11-1
error-free seconds, 10-1
errored seconds, 10-1
in application program
average cells per last 12 seconds, 2-5
history display of past 12 seconds, 2-5
maximum and minimum cells per second and
occurrence time, 2-5
number of cells in the last second, 2-5
of 12 bins sized automatically or by user, 2-5
ratio of cells to maximum line rate as floating
point exponential, 2-5
ratio of cells to maximum line rate as percentage, 2-5
total average cells per second, 2-5
total cells received, 2-5
line violations, 10-1
physical layer, softkey racks, lO-2
signal-fault seconds, 10-1
STM -1 framing, 10-20
STS-l framing, 10-16, 10-20
test duration, 10-1
Vt.J··
Statistics, Trace, and Emulation, application program, ATM (Broadband), Constant Bit Rate
Performance Test, 2-7
'-.'
STM,A-lO
STM-l, 5-7,5-8,5-9,6-1,6-2
STM -1 framing, statistics for, 10-20
STS LOF, statistics for ATM Interface Module,
STS-l,1O-18
STS LOF 2-3, statistics for ATM Interface Module, STS-l, 10-18
STS LOp, statistics for ATM Interface Module,
STS-l, lO-17
STS OaF, statistics for ATM Interface Module,
STS-l,10-18
STS-1, 5-7, 5-8, 5-9, 6-1, 6-2, 6-6
ATM Interface Module
sample statistics screen, .
first page, 10-17
second page, 10-19
statistics
B1 BIPErrors, 10-19
ATM
Index..;~W
B2 BIP Errors, 10-19
B3 BIP Errors, 10-19
Line AIS, 10-17
Line Code Violations, 10-18
Line FEBE Errors, 10-20
Line RDI Errors, 10-20
LaC, 10-18
Path AIS, 10-18
Path FEBE Errors, 10-19
Path FERF Errors, 10-20
Path RDI, 10-18
Sig Label Mismatch, 10-20
Signal Fault, 10-17
STS LOF, 10-18
STSLOF2-3,1O-18
STS LOp, 10-17
STS OOF, 10-18
STS-l framing. statistics for, 10-16, 10-20
STS-3c!STM-l, ATM Interface Module, statistics,
Signal Fault, 10-20 .
Successful cell transfers, in application program, 2-7
SVC,A-lO
T
Tl,A-lO
TllEl, in ATM, 1-1
TIIEI testing, for ATM, 2-7
T3,A-lO
TC,A-lO
TCS, A-lO
TDM,A-10
TE,A-I0
Test duration, statistics, 10-1
Testing of WAN protocols, simultaneously with
~, 7-2,8-2,9-2
Testing WAN protocols
INTERVIEW 8800 PLUS ATM, 2-7
simultaneously with ATM, 5-3. .i
TM, A-lO
' ! ~.,
i
Top enclosure, houses~CE ~nd.AIM boards, 5-3
Trace and Statistics, application program, ATM
(Broadband); 2,-5
.,
Ttap'builder, in application program, 2-5
TS, A-lO
TX, connector for DS';::':;1E3/sTS-t-metallic transmit connector for Side A, 5-8, 5-9
SEP '95
TX Idle Cell Type. field on ATM Interface Setup
:, , •ve, A-11
screen
. ,c, (:_ '!l !,~.~:' Transmit Idle Header Values subfielq. fiel(t~n; .
for AIM - 302 -1
' r ~.,' . ,
ATM Interface Setup screen, An;{UN'l celL
Internal Loop A mode, 7-9
format
'.'''. c
'.
Internal Loop B mode, 7-14
for AIM-302-1
for AIM-30S-I, Intemal Loop A mode. 8-8)",
Emulate A mode, 7·10
for AIM-306-1
Emulate B mode, 7-14
Internal Loop A mode, 9-9
Internal Loop A mode, 7-10
Internal Loop B mode, 9.13
Internal Loop B mode, 7·14
for AIM-305-1
Tx Idle Cell Type, field on ATM Interface Setup '.
Emulate A mode, 8-9
screen
Internal Loop A ~ode.8-9
for AIM-302-1
for AIM-306-1 .
.
,
Emulate A mode, 7-9
Emulate A mode, 9.;10
Emulate B mode, 7-14
Emulate B mode; 9-14
for AIM-30S-I, Emulate A mode, 8-8.
Internal Loop A mode. 9-10 .
for AIM-306-1
InternalLoopB'mode.9:'14
Emulate A mode, 9-9
Ve.c,A.ll
-,
)
Emulate B mode, 9.13
':. L " - '
. Vq;,}-7, A-ll
TX/MM, connector for SO~T OC- 3cand SDa
.:. :-in application program, 2-5
STM-1, multimode transmit fiber optic, 5-8,
Vide9; ATM transmission,·l-!
S-9t;·
.Voice, ATM transmission, 1-1
TXlSM, connector for SONET OC- 3c and SDH
STM-l, single-mode transmit fiber optic, 5-8
' \ ,"
VP.A-ll
Transmit Idle Header Values subfietd, field on
ATM Interface Setup screen, ATM UNI cell
. format
tor AIM-302-1
Emulate A mode, 7-10
Emulate B mode, 7-14
UNI,A-I0
Internal Loop A mode, 7-10
UNI 3.1 signalling, in application program, 2·5
.' L ./'" ,c. 'In....
LVrnal Loop B mode, 7-14
";' y~ "~','<.:,-;,.
for AIM-3OS-1
UPC, A-II
Emulate A mode, 8·9
Upgrade path, for early units, B-3
Internal Loop A mode, 8·9
for AIM - 306-1
Upgrades, to INTERVIEW 8800 PLUS ATM, 1-1
\; [ . :
Emulate A mode, 9·10
Using the INTERVIEW 8750 ATME¥PRI£S~l3-2,. .' , T, ::Emulate Bmode, 9-14
... ' " 'InternalLoopAmode,g-10
;'r
-:'i'> , ',-, ~'InternalLoopBmode,9~14 ., "
u
v
. :~VPC,A-ll
~_:'~
,{
'l
y./;;i;~''''·jVPI~1-7,A-ll
. . ; , ,.,,1[,,1::: l"~".
Variable bit-rate data a p p l i c a t i o n ' ; ,·ip application program, 2-5
Frame Relay testing, INTERVIEW 8800 PLUS
J' . . l/:
ATM,2-3
'. ,
LAN encapsulation t~stini]NTERVIEW 8800 .. ' . >;~', '
PLUS ATM, 2-3 -.. ;.
t'.:;!~
~
SMDS testing, INTERVIEW 8800PLUSATM,~'>;' ;:,WAN, A·ll
." ,:~,
2-3
. ::;. (.'.
'i! ~.i;' :.WANdata, recording simultaneously whil.t:{testing
VBR, A-ll
'HI, ATM (Broadband), 2 - 9 . , > :"
.
W
,,",1
A~_~Broadband) tes~~s~e7:1~v,~~~~~.,;:) .;\,W~N ~t~l testing, INTERVIEW 8800 PLUS ',I
,",' , . ~1-'-': .,-" ._/}_:<~ J·jl."
"-;':1!'C;)-r- fH
I\.
:, \'
SEP'95
ATM Index;~,1
WAN protocols, simultaneous testing with ATM,
5-:-3; 7-2;~2. 9-2
Wamingstidcet. inside top encfosQ.re door, 5-4 .
x
X RAI. softkey. 11-7
ATM Ind&)(-22
SEP '95
Source Exif Data:
File Type : PDF File Type Extension : pdf MIME Type : application/pdf PDF Version : 1.3 Linearized : No XMP Toolkit : Adobe XMP Core 4.2.1-c041 52.342996, 2008/05/07-21:37:19 Create Date : 2002:12:31 18:45:06Z Creator Tool : Acrobat 4.0 Import Plug-in for Windows Modify Date : 2016:11:09 19:24:15-07:00 Metadata Date : 2016:11:09 19:24:15-07:00 Producer : Adobe Acrobat 9.0 Paper Capture Plug-in Format : application/pdf Document ID : uuid:7d3fbcad-83ef-174c-a8df-0173c3cb33cc Instance ID : uuid:e5f5f916-acd2-a549-8240-fc9c971fa4a7 Page Layout : SinglePage Page Count : 1020 Creator : Acrobat 4.0 Import Plug-in for WindowsEXIF Metadata provided by EXIF.tools