- HELP
EVDOA LEVEL II DIAGNOSTIC
TESTS THE ASYNCHRONOUS FUNCTIONALITY OF THE CPI32-A
THIS RELEASE, V1.0, OF THIS DIAGNOSTIC PROVIDES ONLY ONE METHOD
OF LOOPING BACK DATA: INTERNAL LOOPBACK.
!!! NOTE !!!
If the level II and level III diagnostics run without error and
users still cannot get onto the CPI check the help information on
the T1 link and PBX parameters. Type HELP EVDOA PBX
- REQUIREMENTS
ALL TWENTY_FOUR LINES MUST BE AVAILABLE BEFORE THIS DIAGNOSTIC
CAN BE RUN. THE REASON FOR THIS IS THAT INTERNAL LOOPBACK, WHEN
ESTABLISHED, COVERS ALL TWENTY_FOUR LINES. THE ONLY GUARANTEED
METHOD OF ENSURING THAT ALL TWENTY-FOUR LINES ARE AVAILABLE, AND
REMAIN AVAILABLE, IS TO ALLOCATE ALL OF THEM, AS FOLLOWS:
$ ALLOCATE TXA0
$ ALLOCATE TXA1
.
.
$ ALLOCATE TXA6
$ ALLOCATE TXA7
$ ALLOCATE TXB0
$ ALLOCATE TXB1
.
.
$ ALLOCATE TXB6
$ ALLOCATE TXB7
$ ALLOCATE TXC0
$ ALLOCATE TXC1
.
.
$ ALLOCATE TXC6
$ ALLOCATE TXC7
NOTE: THE ABOVE EXAMBLE PRESUPPOSES THAT THE THREE
ASYNCH PORTS ARE CALLED TXA, TXB, AND TXC. THIS,
OF COURSE, IS A CONFIGURATION DEPENDENT VARIABLE.
THERE IS NO REASON WHY THE PORTS NEED BE CALLED TX,
NOR THAT THEY BE CONSECTIVE.
- HARDWARE
VAX PROCESSOR WITH MINIMUM CONFIGURATION (11/780,11/750,11/730)
256 kB MEMORY (MINIMUM)
CPI32 COMPUTER-PBX INTERFACE COMPRISING:
A. M7884 UNIBUS INTERFACE,
B. M7883 T1 INTERFACE,
C. H3026 DISTRIBUTION PANEL,
D. BC02D-0F CABLE, AND
E. 70-XXXXX CABLE.
- SOFTWARE
VAX DIAGNOSTIC SUPERVISOR (11/780=ESSAA, 11/750=ECSAA, 11/730=
ENSAA) MUST BE RESIDENT IN MEMORY. THE SUPERVISOR MUST FIRST BE
LOADED, AND SUCCESSIVE DIAGNOSTICS CAN THEN BE LOADED AND RUN
WITHOUT RE-LOADING THE SUPERVISOR.
- PREREQUISITES
- HARDCORE FULLY TESTED
- FUNCTIONAL DW780, DW750 OR DW730
- ATTACH
THE FOLLOWING IS AN EXAMPLE OF HOW TO ATTACH THE DEVICE TO
BE TESTED, AND TO LOAD AND RUN EVDAC (ANSWERS TO HARDWARE QUESTIONS
ARE TYPED IN OCTAL) :
$ RUN ESSAA ; FOR (11/780)
or
$ RUN ECSAA ; FOR (11/750)
or
$ RUN ENCAA ; FOR (11/730) START SUPERVISOR
DIAGNOSTIC SUPERVISOR. ZZ-ESSAA- 6.13-965 22-DEC-1984 09:40:14.80
DS> ATT DW780 HUB DW0 3 4 ; FOR VAX/780 ATTACH THE UBA ON THE SBI
or
DS> ATT DW750 HUB DW0 ; FOR VAX/750 TESTING
or
DS> ATT DW730 HUB DW0 ; FOR VAX/730 TESTING
DS> LOAD EVDOA ;LOAD THE CPI32A DIAGNOSTIC
DS> ATTACH CPI32A DW0 TXA 760000 400 4 377 9600 A
DS> ! ***************************** NOTE ********************************
DS> ! * VMS V4.0 does not handle the second two sets of CPI ports *
DS> ! * correctly. It does not allow the diagnostic to set maintenance *
DS> ! * mode on lines 2 - 7. Therefore if this is a V4.0 system leave *
DS> ! * the next two command lines commented out. *
DS> ! *******************************************************************
DS> !ATTACH CPI32A DW0 TXB 760000 400 4 377 9600 A
DS> !ATTACH CPI32A DW0 TXC 760000 400 4 377 9600 A
DS> SELECT TXA
DS> ! ***************************** NOTE ********************************
DS> ! * VMS V4.0 does not handle the second two sets of CPI ports *
DS> ! * correctly. It does not allow the diagnostic to set maintenance *
DS> ! * mode on lines 2 - 7. Therefore if this is a V4.0 system leave *
DS> ! * the next two command lines commented out. *
DS> ! *******************************************************************
DS> !SELECT TXB
DS> !SELECT TXC
DS> START
THE PROGRAM SHOULD NOW BE RUNNING.
!!! NOTE !!!
If the level II and level III diagnostics run without error and
users still cannot get onto the CPI check the help information on
the T1 link and PBX parameters. Type HELP EVDOA PBX
- EVENT_FLAG
TWO EVENT FLAGS ARE USED BY THIS PROGRAM TO ENABLE THE OPERATOR TO
INFORM THE PROGRAM OF ITS LOOPBACK CAPABILITIES. EVENT FLAG 1
INFORMS THE PROGRAM, WHEN SET, THAT BULKHEAD LOOPBACK IS DESIRED.
THIS CAPABILITY IS NOT AVAILABLE IN THIS RELEASE. EVENT FLAG 2
INFORMS THE PROGRAM, WHEN SET, THAT REMOTE LOOPBACK IS DESIRED.
THIS CAPABILITY IS NOT AVAILABLE IN THIS RELEASE.
IN THIS RELEASE ALL TESTING IS PERFORMED USING INTERNAL
LOOPBACK. DETAILS ON BULKHEAD LOOPBACK AND REMOTE LOOPBACK
ARE AVAILABLE IN HELP FUTURE_RELEASES.
THE LOOP FLAG, WHEN SET, CAUSES THE PROGRAM TO REPEAT THE
SUBTEST THAT INCLUDED THE ERROR. THIS ENABLES USING A SCOPE
FOR TROUBLE SHOOTING.
IN ADDITION TO THE ABOVE MENTIONED DIAGNOSTIC SUPERVISOR
DEFINED EVENT FLAGS, TWO DIOGNOSTIC DEFINED EVENT FLAGS
MAY BE USED. THESE ARE THE "RETRY" AND THE "SAY" FLAGS.
THE "RETRY" EVENT FLAG IS FLAG NUMBER 13. WHEN SET, THIS FLAG
CAUSES THE DIAGNOSTIC TO BEHAVE IN A MANNER SIMILAR TO THE
"LOOP" FLAG, EXCEPT THAT, UPON SUCCESS, THE DIAGNOSTIC WILL
CONTINUE PAST THE ERROR. IF THIS FLAG IS SET AND THE LOOP
FLAG IS SET, THEN THE LOOP FLAG TAKES PRECEDENCE.
THE "SAY" EVENT FLAG SHOULD NOT BE USED. IT IS INTEDED TO
BE USED BY PROGRAMMERS DEVELOPING THIS DIAGNOSTIC. IT WILL
DO NO HARM, BUT IT WILL OUTPUT MESSAGES IN DETAIL.
- SECTIONS
THERE IS ONLY ONE SECTION TO THIS DIAGNOSTIC : DEFAULT.
THIS SECTION CONTAINS TWO TESTS:
TEST 1 IS A SILO MODE INTERNAL LOOPBACK TEST;
TEST 2 IS A DMA MODE INTERNAL LOOPBACK TEST.
DESCRIPTIONS OF THESE TESTS ARE AVAILABLE UNDER:
TEST_1, AND TEST_2, RESPECTIVELY.
- TEST_1
Single Line Silo Mode
THIS TEST ATTEMPTS TO SEND A TEST MESSAGE 26 CHARACTERS LONG
THROUGH THE LOOPBACK.
THE TEST MESSAGE IS: "ABCDEFGHIJKLMNOPQRSTUVWXYZ"
EXCEPT FOR THE PATTERN SENSITIVITY SUBTEST 3, FOR WHICH
THE PATTERNS ARE: 28 CHARACTERS OF PATTERNS P0 THROUGH P11
WHERE:
P0 = ^B 10101010101010101010101010101010
P1 = ^B 01010101010101010101010101010101
P2 = ^B 11001100110011001100110011001100
P3 = ^B 00110011001100110011001100110011
P4 = ^B 11110000111100001111000011110000
P5 = ^B 00001111000011110000111100001111
P6 = ^B 11111111000000001111111100000000
P7 = ^B 00000000111111110000000011111111
P8 = ^B 11111111111111110000000000000000
P9 = ^B 00000000000000001111111111111111
P10 = ^B 11111111111111111111111111111111
P11 = ^B 00000000000000000000000000000000
Test Steps -
Lower then raise DTR
TEST 1 - SUBTEST 1 - Establish connection
Purge typeahead
Send connection character - X3C
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Receive a response
Check for queueing errors ERROR 3
Check for completion errors ERROR 4
Check for X41 - indicating success
Check for X42 - indicating expected failure ERROR 5
Any other respones indicates unexpected failure ERROR 6
TEST 1 - SUBTEST 2 - Send a single test message
Clear receive buffer
Send the test message
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Receive the test message
Check for queueing errors ERROR 3
Check for comletion errors ERROR 4
Check for different length errors ERROR 5
Check for data errors ERROR 6
TEST 1 - SUBTEST 3 - Pattern sensitivity test
Purge typeahead
Initialize pattern counter
For all patterns on each line do:
Clear receive buffer
Send a pattern
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Receive the pattern
Check for queueing errors ERROR 3
Check for completion errors ERROR 4
Check for length errors ERROR 5
Check for data errors ERROR 6
Break back to supervisor
Bump pattern counter
TEST 1 - SUBTEST 4 - Speed sensitivity test
Read the default characteristics (speed) of first line
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Save line characterists for later restoral
Initialize speed counter
For each speed: 2400, 4800, 9600, and 19200 do:
Lower then raise DTR
Issue set speed qiow
Check for queueing errors ERROR 3
Check for completion errors ERROR 4
Establish connection
Purge typeahead
Send connection character - X3C
Check for queueing errors ERROR 5
Check for completion errors ERROR 6
Receive a response
Check for queueing errors ERROR 7
Check for completion errors ERROR 8
Check for X41 - indicating success
Check for X42 - indicating expected failure ERROR 9
Any other respones indicates unexpected failure ERROR 10
Send test message
Check for queueing errors ERROR 11
Check for completion errors ERROR 12
Receive test message
Check for queueing errors ERROR 13
Check for completion errors ERROR 14
Check for size errors ERROR 15
Check for data errors ERROR 16
Bump speed counter
Restore line speed
Check for queueing errors ERROR 17
Check for completion errors ERROR 18
- TEST_2
Single Line DMA Mode
THIS TEST ATTEMPTS TO SEND A TEST MESSAGE 68 CHARACTERS LONG
THROUGH THE LOOPBACK. THE TEST MESSAGE IS:
"ABCDEFGHIJKLMNOPQRSTUVWXYZ012345667890!@#$%ABCDEFGHIJKLMNOPQRSTUVWXYZ"
THIS TEST ATTEMPTS TO SEND A TEST MESSAGE 26 CHARACTERS LONG
THROUGH THE LOOPBACK.
EXCEPT FOR THE PATTERN SENSITIVITY SUBTEST 3, FOR WHICH
THE PATTERNS ARE: 68 CHARACTERS OF PATTERNS P0 THROUGH P11
WHERE:
P0 = ^B 10101010101010101010101010101010
P1 = ^B 01010101010101010101010101010101
P2 = ^B 11001100110011001100110011001100
P3 = ^B 00110011001100110011001100110011
P4 = ^B 11110000111100001111000011110000
P5 = ^B 00001111000011110000111100001111
P6 = ^B 11111111000000001111111100000000
P7 = ^B 00000000111111110000000011111111
P8 = ^B 11111111111111110000000000000000
P9 = ^B 00000000000000001111111111111111
P10 = ^B 11111111111111111111111111111111
P11 = ^B 00000000000000000000000000000000
THIS LENGTH MESSAGE WILL FORCE THE DRIVER TO OPERATE IN DMA MODE
TEST STEPS -
Lower then raise DTR
TEST 2 - SUBTEST 1 - Establish connection
Purge typeahead
Send connection character - X3C
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Receive a response
Check for queueing errors ERROR 3
Check for completion errors ERROR 4
Check for X41 - indicating success
Check for X42 - indicating expected failure ERROR 5
Any other respones indicates unexpected failure ERROR 6
TEST 2 - SUBTEST 2 - Send a single test message
Clear receive buffer
Send the test message
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Receive the test message
Check for queueing errors ERROR 3
Check for comletion errors ERROR 4
Check for different length errors ERROR 5
Check for data errors ERROR 6
TEST 2 - SUBTEST 3 - Pattern sensitivity test
Purge typeahead
Initialize pattern counter
For all patterns on each line do:
Clear receive buffer
Send a pattern
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Receive the pattern
Check for queueing errors ERROR 3
Check for completion errors ERROR 4
Check for length errors ERROR 5
Check for data errors ERROR 6
Break back to supervisor
Bump pattern counter
TEST 2 - SUBTEST 4 - Speed sensitivity test
Read the default characteristics (speed) of first line
Check for queueing errors ERROR 1
Check for completion errors ERROR 2
Save line characterists for later restoral
Initialize speed counter
For each speed: 2400, 4800, 9600, and 19200 do:
Lower then raise DTR
Issue set speed qiow
Check for queueing errors ERROR 3
Check for completion errors ERROR 4
Establish connection
Purge typeahead
Send connection character - X3C
Check for queueing errors ERROR 5
Check for completion errors ERROR 6
Receive a response
Check for queueing errors ERROR 7
Check for completion errors ERROR 8
Check for X41 - indicating success
Check for X42 - indicating expected failure ERROR 9
Any other respones indicates unexpected failure ERROR 10
Send test message
Check for queueing errors ERROR 11
Check for completion errors ERROR 12
Receive test message
Check for queueing errors ERROR 13
Check for completion errors ERROR 14
Check for size errors ERROR 15
Check for data errors ERROR 16
Bump speed counter
Restore line speed
Check for queueing errors ERROR 17
Check for completion errors ERROR 18
- PBX
The following information is not needed to run the diagnostics
however it is intended to aid in finding a missmatch between the
CPI32-A and the PBX after both diagnostics have run without error.
Parameters vary with PBX vendor however some general information is
usefull. If a connection cannot be made from a terminal connected to
the PBX vendors data access module (DAM) thru the PBX to the VMS system
verify that parameters on the VMS system are correct. Look at the
help section on parameters. Then check with PBX personnel to insure
that the PBX parameters are set correctly.
HELP EVDOA PBX ALARM ;T1 trunk is declared out of service?
HELP EVDOA PBX PARAMETERS ;Are parameters set correctly?
- ALARM
The quality of the link between the CPI and the PBX is monitored by the
PBX. If frame (the 193rd bit of the T1 frame follows a pattern) loss
is detected by the PBX it records it as a framming error (RED ALARM).
After some number of frame losses the PBX may declare the T1 link
out of service. The number of frame losses before out of service is
a setable parameter at the PBX. INSURE THAT THIS PARAMETER IS SET HIGH.
A UNIBUS init or power failure for example cause a frame loss. The
following activities at the CPI will cause a frame loss to be seen
at the PBX:
o The booting of a 730 system causes 5 bus inits to the CPI.
o The switching of the UETP switch on the distributation panel.
One each time it is turned on and the UETP is started.
o Starting the level II diagnostic. Every time the cleanup code
is done followed by the init code.
o Most test in the level III diagnostic will cause atleast 1
framming error. This is why the level III is run with the
loopback connector in and the T1 link disconnected.
- PARAMETERS
Inorder for communication to occur between the host VMS system and a
terminal thru the CPI parameters must be set in several places. Verify
that parameters have been set in the following places.
o Parameters in the terminal match parameters in the Data
Access Module.
o The Data Access Module is understood to be a data connection
at the PBX.
o The T1 trunk is understood to be a data trunk at the PBX.
o The phone # associated at the PBX with the T1 link agrees
with the one being used.
o The set term commands have been executed on the VMS system.
o The set term commands should look like;
SET TERM TXxx:/MODEM/HANG/NOBROAD/NOAUTOBAUD/SPEED=xxxx/PERM
o The level II diagnostic ran correctly insures the device is
sysgen connected to the driver correctly.