- HELP
EVDYD is a level 2R functional diagnostic for the Digital Ethernet
Backplane Interconnect (BI) Network Adapter (DEBNT). This diagnostic can
only be run on one DEBNT at a time. EVDYD will verify the following:
the operation of the Ethernet port driver, the ability of the DEBNT to
transmit and receive frames, the ability of the DEBNT to generate correct
CRC checks, and the Ethernet address filtering capabilities of the DEBNT.
- SETUP
EVDYD requires that the system not be running DECNET or LAT when
the program is executing. Stopping DECNET and the LAT will cause all
communication between this system and another other system or terminal
server over the Ethernet to stop. In addition, the system must have
the MAXBUF parameter set at 1600 and process running EVDYD must have
a BYTLM of at least 30000.
- DECNET
Note: DECNET should not be stopped unless you know how to restart
it. Consult the System Manager for starting DECNET.
The diagnostic requires complete control of the driver. Therefore
DECNET can not be active. To stop DECNET issue the following
commands:
$ MCR NCP
NCP> SET EXECUTOR STATE OFF
NCP> EXIT
- LAT
Note: The LAT should not be stopped unless you know how to restart
it. Consult the System Manager for starting the LAT.
The diagnostic requires complete control of the driver. Therefore the
LAT can not be active. To stop the LAT issue the following commands:
$ MCR LATCP
LCP> STOP
LCP> EXIT
- MAXBUF
The MAXBUF parameter in system parameter file must be increase to 1600
in order to run EVDYD. To increase the parameter issue the following
commands:
$ MCR SYSGEN
SYSGEN> USE CURRENT
SYSGEN> SET MAXBUF 1600
SYSGEN> WRITE CURRENT
SYSGEN> EXIT
- BYTLM
The BYTLM parameter in the user authorization file for the process which
is executing EVDYD must be increase to 30000. The system authorization
file is usually kept in the SYS$SYSTEM area. To increase the parameter
issue the following commands:
$ set def SYS$SYSTEM:
$ MCR authorize
UAF> MODIFY user_name/BYTLM=30000
UAF> EXIT
Now return to the area you were running the diagnostic from.
- ATTACH
The following is the attach procedure that must be executed to run
this diagnostic:
For the 82xx,83xx:
ATTACH DEBNT HUB ETa BIn
ATTACH LANCE ETa ETan
Where:
a = a controller designator (ie: ETA,ETB)
BIn = BI node number (hex)
n = a unit number
For the 85xx,88xx:
ATTACH NBIA HUB NBIAn LAn
ATTACH NBIB NBIAn NBIBn BIn BINn
ATTACH DEBNT NBIBn ETa BIn
ATTACH LANCE ETa ETan
where: (NBIA)n = unit number 0-1
(LA)n = logical adapter number 0-1
(NBIB)n = unit number 0-3
(BI)n = BI # 0-1
(BIN)n = BI node # 0-F
- DEVICE
- DEBNT
The DEBNT module is a dual functional adapter. This BI adapter
contains a Ethernet port as well as a TK50 Streaming tape
drive port. The TK50 is not used during this diagnostic and
is covered by EVMDA. The Ethernet hardware is implemented using
the Lance Chip Set.
- EVENT
Test 7 - Stress Test - is the only test that can be effected by an
event flag. If event flag 3 is set, then the test will be run with the
DEBNT in external loopback. Otherwise, the test will be run in internal
loopback.
- SECTIONS
EVDYD is broken up into the following seven tests. Type
HELP EVDYD SECTIONS test-name
for details on a particular test.
- TRANSMIT_CRC
The function of this test is to verify the correct operation of the
LANCE's CRC circuitry. The DEBNT is put into internal loopback mode
with transmit CRC enabled. A write QIO is issued causing the frame to
be transmitted with the LANCE appending a CRC to the frame. The frame
is received and given to the DEBNT software driver which then calculates
its CRC. The driver checks that the CRC is correct and then buffers the
data. This data is then compared with what was sent.
NOTE
While in internal loopback, the LANCE can only calculate
a frame's CRC on transmit or receive.
This test will use fixed size frames of 28 bytes data/4 bytes CRC.
- RECEIVE_CRC
This test is used to verify the correct operation of the LANCE's
CRC circuitry on frame reception. Two frames will be transmitted. On
the first transmit the diagnostic will calculate and append good CRC to
the frame. No CRC error is expected - the data that was transmitted
will be compared to the data that was received. On the second transmit
the diagnostic will append bad CRC to the frame and expect a CRC error
to occur - the proper return status will be checked and the data will
not be compared for this transmit. Receive CRC generation will be
enabled for both transmits.
- PROMISCUOUS_ADDRESS
The purpose of this test is to make sure that the DEBNT can enter
promiscuous mode.
This test uses the internal loopback mode to receive its own
transmissions by looping inside the DEBNT . This test is accomplished by
having the DEBNT read a buffer in host memory into a transmit buffer.
The DEBNT then transmits the frame in internal loopback mode with
promiscuous mode enabled.
There will be four (4) transmissions of the test frame, each of
which will contain a destination address as follows:
1st dest <-- physical address
2nd dest <-- multicast address
3rd dest <-- non enabled physical address
4th dest <-- non enabled multicast address
All test frames are expected to be received and loaded into host memory.
Data that was transmitted will be compared with the data that was
received in host memory.
- ENABLE_ALL_MULTICAST
This test is to verify that the LANCE's address logic can accept
all multicast addresses. The DEBNT will be configured in internal
loopback mode, with the "accept all multicast" option set. Four
transmissions will be made with the destination of each frame containing
the following:
1st dest <-- physical address
2nd dest <-- multicast address
3rd dest <-- non enabled physical address (shouldn't rcv)
4th dest <-- non enabled multicast address
All test frames with the exception of the non enabled physical address
are expected to be received. The data that was transmitted will be
compared with the data that was received in host memory.
- STATION
The purpose of this test is to verify the ability of the DEBNT to
correctly distinguish frames destined for it. Fourteen frames will be
transmitted with the DEBNT in internal loopback mode.
1st dest <-- physical address
2nd dest <-- broadcast address
3rd-5th dest <-- multicast address
6th dest <-- non enabled physical address (shouldn't rcv)
7th-9th dest <-- multicast address
10th dest <-- non enabled multicast addr (shouldn't rcv)
11th-14th dest <-- multicast address
All test frames with the exception of the non enabled physical and
multicast addresses are expected to be received. The frames will
contain a sequence number to distinguish one from another. The data
that was transmitted will be compared with the data that was received in
host memory. A compare error will indicate that a frame was erroneously
rejected or accepted by the LANCE's address filtering logic.
This test will be repeated as described above but with the
complemented multicast addresses in the station address ram.
- NO_RECEIVE_BUFFERS_AVAILBLE
This test is to verify that the DEBNT correctly detects a receive
buffer unavailable interrupt. This is indicated by the RCBI bit of
PCSR0 being set.
This test is accomplished by having the DEBNT software set up the
DEBNT receive buffer logic to cause an RCBI interrupt after receipt of
- 1 datagram"s. The DEBNT will read a buffer in host memory into a
transmit buffer and then transmit the datagram in internal loopback mode
with the source and destination addresses the same.
The RCBI bit in PCSR0 will be checked for correct status after each
transmit.
- STRESS
This test is designed to verify that the DEBNT can stand some
stressful, bursty activity. Three frames at a time will be transmitted
in internal/external loopback. The test will wait for all frames to be
received and then check them against what was transmitted.
There will be seven bit fault patterns. Data transfer will be
repeated until all bit fault patterns have been exhausted.
The following seven data patterns will be used:
FFFF
0000
AAAA
5555
3333
0F0F
00FF
This test will run, by default, in internal loopback mode. To run
this test in external loopback mode SET EVENT FLAG 3