2120-0209_SQ739_SCSI_MSCP_Disk_and_Tape_Controller_Oct91.pdf

2120-0209_SQ739_SCSI_MSCP_Disk_and_Tape_Controller_Oct91.pdf

DISTRIBUTED LOGIC CORPORATION

MODEL SQ739

DISK AND TAPE CONT'ROLLER

INSTALLATION AND OPERATION MANUAL

Part Number 2120-0209

MODEL SQ739

DISK AND TAPE CONTROLLER

INSTALLATION AND OPERATION MANUAL

REVISION B

21-0ctober-91

Update manual for firmware changes

~Rnmm

DISTRIBUTED LOGIC CORPORATION

Date

21-June-Si

21-0ctober-91

Part Number 2 i 20-0209

Revisions

Release initiai Reiease

Update manual for firmware changes

DEC, LSI-11, Micro/PDP-11 ,PDP-11 ,MicroVAX II, MicroVAX III, RT-11, RSX, 11 M,

RSTS/E, DSM(Mumps), Ultrix, MicroVMS, MSCP, TMSCP, MU Driver, DU Driver are registered trademarks of Digital EQuipment Corportion.

Page 2

Table Of Contents

1 - Introduction •...•..

0 • • • • • • • • • • • • • • • •

2 - Specifications

0 0 • • • o • • •

4

5

Controller Specification •.....................•..................•................................ 5

Controller Characteristics ......•..•......•.•..................................................... 6

3 - Host Adapter Installation ••..••......• 9

Host Adapter Configuration .......•..•.•........................................................ 1 0

Jumper Configuration .................................................................. 11

Switch Configuration ......•.•... ~ •..................................................... 11

4 - Operation ..••••.•.

0 • • •

12

Serial Port Initiation ..................•.•.... ~ ..................................................... 12

Virtual Terminal Initiation .......•.................•.............................................. 13

Virtual Terminal - LSI/11 Based Systems ........•............................... 13

Virtual Terminal - MicroVAX II and MicroVAX III ............................. 14

IP and SA Addresses ...............................•............................................. 15

MSCP Emulation ......................................................................... 15

TMSCP Emulation ....................................................................... 1 5

5 - Oilog On-Board Diagnostics •...........••.•.•.........•.............................................. 16

Diagnostic Main Menu ............................................................................ 16

Controller Utility Menu ........................................................................... 1 6

Option #1 .....•............................................................................ 16

Option #2 ..•..•...................•........................................................ 17

Option #3 .................................................................................. 1 8

Option #4 ....•............................................................................. 1 8

Controiier Configuration Menu ................................................................. 1 9

Unit Mapping Menu ...................•........................................................... 20

6 - Host Based Diagnostics

0 0 . 0 • •

23

Startup - LSI/11 Systems •............•....•.................................................... 23

Disk Emulation Diagnostics ...................................................•...............•. 23

Front End Test - ZRCFB3 ............................................................. 23

Disk Exerciser - ZRCDA 1 ............................................................. 25

Tape Emulation Diagnostics .......••........................................................... 29

Front End Test for TK50 - ZTKACO ..........................................•.... 29

TK50 Data Reliability Test - ZTKBBO ...•....................................•..... 30

MicroVAX II System Diagnostics .•....................•...................................... 32

MOM Diagnostic for Tape ............................................................ 32

MOM Diagnostics for Disk ........................................................... 32

7 - Errors and Troubleshooting ••.. 33

8 - Error Logs ••..•

0 • • • • • •

34

Host Memory Access Error log ............................................................... 34

Disk Transfer Error Log .......................................................................... 35

Disk SOl Error Log ................................................................................. 36

Tape Transfer Error Log .......................................................................... 37

Exabyte EXB-8200 Error Log Definition .......................................... 38

9 - Standard Error Codes •••...•........•........................•.....•.................................... 40

Self Test Error Codes ............................................................................. 40

Fatal SA Error Codes .............................................................................. 40

VMS Error Codes .................................................................................. 42

MSCP ....................................................................................... 42

TMSCP ..................................................................................... 43

Page 3

1 - Introduction

Tne SQ739 is a high performance dual-wide Obus Host Adapter which supports the SCSI interface.

The host adapter is compatible \-,ith the DEC Mass Stoiage Controi Protocoi (MSCP; for disk and tape devices (TMSCP). The host adapter supports the DEC Obus systems including the 11/23,

11173, MicroVAX II, MicroVAX III and MicroPDP11 computers. It also supports the DU and MU driver of the associated DEC operating systems including; RT-11, RSX11 M. RSXll M

+

!

RSTS/E.

OSM(Mumps), Ultrix, Unix, MicroVMS, and VMS.

The 5Q739 can support up to seven (7) SCSI disk or tape nodes with a maximum support of eight

(8) mapped logical units. The SCSi implementation supports bus arbitration, disconnect/reconnect, synchronous and asynchronous data transfer with a maximum transfer rate of 4.0MB/sec. The

SQ739 features a full 22 bit OBUS DMA addressing capability and supports non-block mode in addition to block mode OMA transfers with a maximum burst rate of 3.3MB/sec.

The host adapter has on-board diagnostic/configuration capability that includes utilities to configure the user defined parameters of the S0739, format and test SCSI devices, and a mapping menu for selection of logical units. All user defined parameters are stored in non-volatile Electrically

Erasable/Programmable ROM (EEPROM) and are retrieved upon power-up of the module. The host adapter also includes boot support of popular devices including OU, MU, MS, MT, OM, DR, OL.

Also included is a special FT boot which configures the console device into a virtual terminal for support of the on-board diagnostics. r~-------------------------------------'

SQ739

Q

B

U

s

,4AddrlData

~

I

(16)

i

I.

Ext

Addr

(6)

~I

~

I

"~

Control

(14)

)1

J1

J2

SCSI Bus

Terminal

Figure 1 - SQ739 Simplified Diagram

Page 4

2 - Specifications

Controller Specification

Mechanical:

Dual-Wide Module 5.22 x 8.88 inches

Bus Interface:

Addressing:

IP/SA Address:

Interrupt Vector:

DEC Qbus

18 or 22-bit addressing support

DU 172150, 160334, 1.60340, or user-defined

MU 174500, 160404, 160410, or user-defined

Software Programmable 0 - 774

Interrupt Priority:

Qbus DMA Burst:

Qbus DMA Mode:

Command Queue:

Jumper selectable BR4 to BR7

2 to 16 words user-defined, up to 3.3MB/sec

Block Mode or Non-Block Mode

DU 16 entry command queue with elevator seek algorithm

M U 8 entry command queue

2KB Fifo Data Buffer:

Bootstrap Capability: Disk

Tape

Utility

DK,DL,DM,DR,DB,DU

MT,MS,MU

FT

Diagnostic Capability: Full power-up self-test diagnostics including MicroProcessor, RAMFIFO,Qbus

Interface and SCSI Interface. On-Board Configuration/Diagnostic menu supports, format and test of SCSI devices.

DEC MSCP and TMSCP. Emulation:

Software Support: Compatible with DU and MU drivers utilized in RT-11, RSX11 M, RSX11 M +,

RSTS/E, DSM 11, Unix, Ultrix, MicroVMS, and VMS operating systems. Also compatible with XXDP+ diagnostics ZRCF?? Front End Tests 1 - 8, ZRCD??

Disk Exerciser, ZTKA?? TK50 Front End Tests 1 - 8, and ZTKB?? Tests 1 - 6

TK50 Data Reliability Test.

LED Indicators:

I/O Interface:

Terminator Power and Self-Test/Activity

Single-Ended SCSI (Small Computer Systems Interface) compatible ANSI specification X3T9.2/85-52 Rev 48 for sequential and direct access devices.

Cable Requirements: Maximum cable length of 6.0 meters with no more than 0.1 meters STUB to connecting devices. Characteristic impedance of 100 ohms

+

/-1 0%.

I/O Connectors: Standard 50 pin flat ribbon connector for SCSI I/O, 10 pin connector for the on-board configuration/diagnostic (RS-232).

Page 5

SCSI Device Support: Maximum of 7 SCSI NODES using

8 devices with any mix of disk or tape devices.

MultHnitiator Support; Supports MuitHnitiator configurations including TERM PWR support and removable termination.

SCSI Transfer Rate: 3.5 MB/sec Asynchronous, 4.0 MB/sec Synchronous

Operatiiig Ternperature:40 to i 04 degrees Fahrenheit (5 to 50 degrees Celsius)

Relative Humidity: 10 to 90% Non-condensing

Power Requirements:

+

5 Volts at 1.5 Amps

+

12 Volts at .1 Amps

Controller Characteristics

Mechanical

The SQ739 is fully contained on a single DUAL height module 5.22 inches (13.2cm) wide by 8.88

(22.56) high. The controller utilizes a single dual slot in a Q-BUS backplane minimizing slot utilization.

Base Address

The S0739 supports the full addressing range of 160000 177774 "'\lith a combination of switch settings and a user defined selection. The SQ739 has 2 switches with 4 combinations for each emulation. The first three (3) switch combinations selects a pre-defined base address while the last combination selects the user defined address stored in EEPROM.

MSCP Emulation IP/SA Address

TMSCP Emulation IP/SA Address

Controller Emulation

172150, 160334, 160340, user-defined

174500, 160404, 160410, user-defined

The controller emulates the DEC DU and MU devices. The disk emulation responds with RA80,

RA81, RA82 RA90, and RA70 drive types depending upon the capacity of the unit selected. The tape emulation responds with TK50 drive type only. interrupt Vector

The host interrupt vector is host programmable and supports the full range of 0 - 774.

DMA Address Range

The SQ739 supports a full

22~bit address for up to 4M Bytes of addressable memory.

Obus DMA Burst Rate

The S0739 supports a burst rate of up to 3.3MB/sec with a maximum allowable burst of 16 words.

The burst rate is user defined and is stored in EEPROM.

Page 6

Obus DMA Dwell Rate

The S0739 supports OMA dwell times of 200ns to 3.2us. The OMA dwell rate is user defined and stored in EEPROM.

OBUS Interrupt Priority Level

The interrupt priority level is jumper selectable on the module and supports BR4 to BR7.

SCSI Bus Transfer Rate

The S0739 supports both asynchronous and synchronous data transfers on the SCSI bus with a maximum transfer rate of 4.0MB/sec. The synchronous transfer rate has been preset on the controller to maximize data throughput for the Obus.

SCSI Drive Support

The S0739 supports up to seven (7) nodes on the SCSI bus with up to eight (8) units. The controller supports up to four (4) logical units (LUN) on a single SCSI node and is user defined in

EEPROM. The S0739 supports any combination of disk and tape drives on the SCSI bus.

SCSI Multiple Initiator

The S0739 supports multiple initiator applications. The host adapter SCSI node 10 is user defined and stored in EEPROM.

SCSI 1/0 Interface

The S0739 supports the SCSI single-ended interface and utilizes the driver/receiver capability of the NCR 53C90A SCSI Interface Chip. The SCSI bus must be terminated at each end of the cable with 220 ohms to

+

5 volts and 330 ohms to ground. The S0739 supports the TERM PWR line

(PIN 26) which is required for some applications where termination cannot be accomplished on the devices or host adapters. The termination can be removed on the S0739 when the module is not a terminating node on the SCSI bus.

SCSI Specification Support

The module supports the ANSI

X3T9.2/85-52

Rev 4B & the SCSI-II ANSI

X3T9.2/86-109

Rev 10G

X3T9/89-042 Command Sets for direct access devices and sequential access devices.

SCSI Single-Ended Cable Requirements

The host adapter supports the single-ended SCSI bus specification of up to 6.0 meters in length with no more than a 0.1 meter stub to any connected device. The ideal impedance match for singleended SCSI is 132 ohms which, in general, is not available today. Therefore, it is recommended that a cable with a characteristic impedance of 100 ohm

+

1- 10% twisted-pair be utilized. To minimize impedance mismatch, cables of different impedances must not be mixed on the same SCSI bus. A minimum conductor size of 28 AWG should be used to minimize noise effects.

Suggested non-shielded flat cable: Spectra 455-248-50 Twist-n-Flat

Page 7

SCSI Single-Ended Pin Assignments

, DB2

DB3

DB4

DBS

:oa6

DB7

DBP

Ground

Ground

Ground

TPWR

'6

8

10

12

14

16

18

20

22

24

26 o

1

' Data Bus Bit

2

Data Bus Bit 3

Data Bus Bit 4

Data Bus Bit S

Data

HUS

Bit 6

Data Bus Bit 7

Data BusParity

1/0

Ground

1'0 Ground

1'0 Ground

Termination Power

ATN

Ground

BSY

ACK

RST

MSG

SEL

C/D

REQ

I/O

' 32

34

36

38

40

42

44

46

48

50

Attent.Lon

I/O Ground

Busy

Acknowledqe

Reset

Message

Select

Command/Data

Request

Input70utput

All odd pins except pin 25 are connected to 1/0 ground.

1/0 Connector

The S0739 incorporates a single 50-pin flat ribbon connector iocated at the top of the module for connection to the SCSI peripherals. The mating connector is 3M 3452-5000 or equivalent.

Power Requirements

The S0739 requires

+

5 volts

+ /-

5 % at 1.5 amps and

+

12 volts

+

/-10% at .100 amps.

Environmentai Requirement$

Acceptable operating environment for the module is 50 to 104 degrees Fahrenheit with humidity 10 to 90

%

non-condensing.

Shipping Weight

The 5Q739 is shipped in anti-static packaging with a INSTALLATION AND OPERATION MANUAL.

Shipping weight is

5 pounds.

Page 8

3 - Host Adapter Installation

Refer to Page 11 to install the jumpers and configure the switches for the desired options. Once completed, continue with the following installation procedure.

Ensure that all power has been removed from the system, disks and tapes before installing the host adapter. Damage may result if the host adapter is installed while power is applied.

Select the backplane slot into which the S0739 is to be installed. There are several backplane assemblies available from DEC and other manufacturers.

Some Obus based systems utilize a serpentine backplane which has all the slots wired for Obus in a serpentine fashion starting in the upper left slot and proceeding left to right, down, right to left, down and so on.

Some backplanes also incorporate a C/O bus or M EM ORY bus in the C/O connector of the backplane. The host adapter can only be installed in the AlB Obus Slot for proper operation. If the host adapter is installed in a O/CD slot, no grant card is required in the CD connector.

Refer to the system manuals for clarification of the type of backplane incorporated in the system.

If the serial port on the adapter is to be connected, connect the serial cable to J2 on the host adapter.

Install the peripherai cable into J1 on the host adapter ensuring that pin 1 of the connector matches.

CAUTION - Damage may result to the peripheral and/or the host if the SCSI cable is installed backwards.

Ensure that the S0739 is oriented with the components facing ROW 1 of the backplane and gently press both sides until the module connectors are firmly seated in the backplane.

CAUTION - Damage may result to the peripheral and/or the host if the controller is installed backwards.

Connect SCSI cable to the SCSI peripheral ensuring proper orientation of PIN 1. Also, ensure that the SCSI bus has been properly terminated at both ends of the cable. Failure to properly terminate the bus can result in system failure or intermittent operation.

Refer to the peripheral manual for proper operating procedure before attempting to apply power to the peripheral and computer system.

Apply power to the system and peripherals. The ACTIVITY led will illuminate if SELF TEST has completed successfully. The 50739 will continue with self test until the host adapter is initialized by the operating system at which time the led will blink with I/O ACTIVITY.

If a SELF TEST ERROR occurs the activity led will blink an error code (refer to Page 39). The error code will also be output to the RS232 port J2 and will be displayed if a terminal has been connected.

Page 9

Host Adapter Configuration

/

../'

~

!!

/1--1

-_---..1

.....

~

SY/1

-

--

IEJN

-=aoo

- 0

. . . "z

-=-0

JP3 t='I

JPl

~

~

J

11111111111111111 11111111111111111

-

Figure 2 - 8Q739 Host Adapter Configuration

Page 10

Jumper Configuration

Jumper JPl-3

BR level

BR4 •

BR5

BR6

BR7

JP1 JP2 JP3

IN IN IN

OUT IN IN

IN OUT IN

IN IN OUT

JumperJP4

Shield Ground

Connected to lOGIC Ground

JP4

IN

Disconnected from lOGIC Ground • OUT

Switch Configuration

IP/SA Base Address

MSCP Base Address

172150··

160334

160340

User Defined in

EEPROM

SW1-1

OFF

ON

OFF

ON

SWl-2

OFF

OFF

ON

ON

SWl-3 SWl-4

OFF OFF

ON

OFF

OFF

ON

ON ON

TMSCP Base Address

174500·

160404

160410

User Defined in

EEPROM

Bootstrap Address/Select

Bootstrap Address

Disabled •

Enabled

Bootstrap Select

173000·

175000

AutoBoot Select

Autoboot Select

Disabled •

Enabled

SWl-5

OFF

ON

SWl-6

OFF

ON

SWl-7

OFF

ON

SW1-8 Not Used

Note - • denotes default settings

Page 11

4

~

Operation

This section of the manual describes the operation of the system, including estabiishing communication with the host computer, the host adapter and connected peripherals! bootstrapping devices and configuring the host adapter.

Refer to Section 6 for a description of supported diagnostics.

Refer to Section 8 for error codes and description of error log formats.

The On-Board diagnostics can be started via the RS-232 serial port J2 or via the virtual terminal.

This section describes the method for using either method.

Serial Port Initiation

Install a serial cable to J2 and connect to a terminal ensuring that the baud rate has been set to

9600 baud, 8 data bits, 1 stop bit and no parity. The serial communication will begin immediately upon power-up or a Qbus INIT. Please note that the system must be in console mode when activating the serial port. Also, upon resumption of normal operation, the serial cable must be removed for proper operation of the host adapter.

9 7 5 3

1 o o o o o

[0 o o o o

10 8 6 4 2

Figure 3 - Seriai Port Connector

8Q739

XMT 3 '-

RS232C

ReV

2 XMT

7~

9~

GND 2

IE-/---t--i----t--+--~~

\j

I

1:::-

SHIELD

Figure 4 - Cable Pinout

Page 12

Virtual Terminal Initiation

The virtual terminal is used to communicate between the console of the host computer and the onboard diagnostics via the computer console terminal. The virtual terminal is initiated differently depending upon the type of system. For LSI-11 based systems the virtual terminal can be started via the boot prompt •••. The procedure for starting the virtual terminal on a MicroVAX system involves depositing keyword values in the SA register.

Virtual Terminal - LSI/11 Based Systems

The virtual terminal utilizes the system console as the terminal for serial communications. The system console must be placed on ODT (Online-Debugging Technique) mode. The boot procedure is initiated at the console by entering 775000G or 773000G, depending on which boot address has been selected (see section 3 for details on enabling and selecting the boot address). At this point, the host adapter will respond to the boot attempt by transferring the bootstrap program on-board, to host memory. The system console will respond with a ' · ' as the boot prompt if the DMA transfer was successful (see section 7 for more information if the prompt does not appear). Once the ••• prompt has been output to the console, enter • FT' which is the designation for the virtual terminal connection. Immediately, the on-board diagnostic will print the banner and prompt for

(C)RT or (P)PRINTER.

Example:

@

775000G

<&

FT<cr>

; start boot procedure

; prompt is received

; start virtual terminal

Dilog On-Board Diagnostic

Diagnostic Main Menu

MSCP IP/SA Address

TMSCP IP/SA Address

172150

Disabled

Model

Revision

SQ739

B

Boot Address 175000

Autoboot Disabled

(P)printer or (C)RT

? :

An alternate method of starting the virtual terminal involves the deposit of 77777 octa!' in the host adapters SA register. This can be utilized if the bootstrap has not been enabled. Once the keyword

(77777) has been entered, the host adapter will DMA the bootstrap program into host memory. The user must then start the bootstrap program by entering 2000G on the console terminal. The console will then respond with the •• ' prompt as in the preceding example.

Example:

@ 777721

501000000

0

@

<

cr

>

77772152/005400

77777

<

cr

>

@

2000G

• FT <cr>

The console will respond with the banner as in the preceding example.

Page 13

Virtual Terminal - Micro VAX II and Micro VAX III

The host adapter does not contain a bootstrap program for the MicroVAX systems. Therefore the user can only initiate the virtual terminal by the deposit of the keyword in the configured SA register. The on board bootstrap MUST be disabled for proper operation of the MicroVAX system:

Upon the power-up of the system, the MicroVAX will enter into self-test diagnostics. Upon successful completion of the diagnostics, the user must enable the I/O map before the on-board diagnostic program can be initiated. The I/O map can a~temat!ve!y be enabled by booting a nonexistent device. Once the

110

map has been enabled, the user must deposit 3FFF into the configured

SA register. Once input, the host adapter will DMA the VAX virtual terminal driver to host memory.

The user then initiates the virtual terminal by starting execution at location 200. Alternatively, the user can start the program at 218 for GPX (Graphics Workstation) support. If the on-board diagnostic banner does not appear, refer to section 7 for troubleshooting hints.

Example: with IPISA address of 20001940

> > > D/P/L 20088004 80000001 <cr> ; setup I/O map

> > >

D/PIW

20001F40 20 <cr> ; enable mapping

> > >

D/PIW

20001940 0 <cr>

> > >

D/PIW

20001942 3FFF <cr>

; write IP to reset host adapter

; write keyword to initiate DMA

; start virtual terminal driver > > > S 200 <cr> or

> > > S 218 < cr > ; start terminal driver for GPX

If the virtual terminal is successful, then the following screen will be displayed:

Dil09 On-Board Diagnostic

Diagnostic Main Menu

MSCP IP/SA Address

TMSCP IP/SA Address

172150

Disabled

Kodel

Revision

SQ739

B

Boot Address

175000

Autoboot Disabled

(P)printer or (C)RT ? :

Alternatively, the virtual terminal may be initiated by attempting to boot a nonexistent disk drive.

This will automatically setup the I/O maps and reset the host adapter. Once the console returns with the 'NO SUCH DEVICE' error message, the user can initiate the virtual terminal by depositing the keyword in the SA register and starting the virtual terminal driver described above.

Page 14

Example:

> > > B DUDO <cr>

NO SUCH DEVICE

; boot nonexistent drive

> > >

DIPIW

20001942 3FFF <cr> ; deposit keyword

> > > S 200 < cr>

; start program

IP and SA Addresses

IP REGISTER

OCTAL ADDRESS

MSCP Emulation

SA REGISTER

OCTAL ADDRESS

IP REGISTER

MICROVAX

172150

160334

160340

160344

160354

160360

160364

172152

160336

160342

160346

160356

160362

160376

20001468

200000DC

200000EO

200000E4

200000EC

200000FO

200000FC

TMSCP Emulation

IP REGISTER SA REGISTER

OCTAL ADDRESS OCTAL ADDRESS

174500

160404

160410

160414

160444

160450

160454

174502

160406

160412

160416

160446

160452

160456

IP REGISTER

MICROVAX

20001940

20000104

20000108

2000010C

20000124

20000128

2000012C

SA REGISTER

MICROVAX

2000146A

200000DE

200000E2

200000E6

200000EE

200000F2

200000FE

SA REGISTER

MICROVAX

20001942

20000106

2000010A

2000010E

20000126

2000012A

2000012E

Page 15

5 - Diloo On-Board Diagnostics

Once the On-Board Diagnostic Menu has been booted. the user must initially input the type of terminal the diagnostic is utilizing. If the (C)rt is entered, the banner will appear at the top of each page and the screen is formatted for appearance. A (P)printer selection will disable the screen formatting to minimize paper usage. There is no default for the terminal type, the user must input a variable to continue.

Upon terminal selection, the main menu will appear and the user must select an item from the menu. If the user inputs a <CR> at any selection prompt, the diagnostic will return to the previous menu. A <CR> input at other prompt times will either return to the previous menu or the default value is used. If at any time the user inputs a CTRl C ( .. C)

I

the diagnostic will return to the

Diagnostic Main menu.

Diagnostic Main Menu

The diagnostic main menu displays the current menus supported by the on-board diagnostics. The user must enter a selection at the prompt to access the lower level menus. A <CR> entered at the main menu prompt will cause a return to the initial (P)printer or (C)RT prompt.

Diagnostic Main Menu

1 Controller Utility Menu

2 - Controller Configuration Menu

3 - Unit Mapping Menu

Enter Selection (CR to Exit)

Controller Utility Menu

The Controller Utility Menu contains the SCSI

110

utilities currently supported by the diagnostic. The user must select the utility or enter a < CR > to exit and return to the main menu.

Controller Utility Menu

1 - SCSI Direct Command

2 - Write/Read SCSI Unit

3 Format SCSI Unit

4 - SCSI Bus Scan

Enter a Selection (CR to Exit)

Option #1

The SCSI Direct Command allows the user the ability to issue a single SCSI command. This is sometimes useful in troubleshooting or during system configuration to check on the status of the connections to all of the peripherals. The menu item will prompt the user for the NODE ID and the

LUN. Once entered, a default 6 byte SCSI command is displayed and the user is prompted for any changes. Changes to the SCSI COB (Command Data Block) are entered as HEX bytes ONLY. If the user inputs an INVALID character, the program will display an error message and prompt again.

Once all bytes have been modified, the user will be prompted to enter any data that is to be written,

Page 16

then Execute SCSI Command. A (Y)es answer will execute the SCSI command, a eN) will return the user to the NODE 10 prompt.

Example:

SCSI Direct Command

SCSI Node [00] : O<CR>

SCSI LON [ 00 ] : O<CR>

Bytes in COB (hex) 06

SCSI COB Byte 00-00,00,00,00,00,00

Any Changes

(YIN)

? N<CR>

Any Data to write

(YIN)

? N<CR>

Execute SCSI Command

(YIN)

? Y<CR>

Completed with no Errors

More Commands

(YIN)

? N<CR>

*** <CR> to continue ***

Option #2

The WRITE/READ SCSI UNIT menu item allows the user to test a SCSI unit. The utility supports both disk and tape units and determines unit type before testing. The utility will first prompt the user for NODE ID and the LUN of the required unit. Once the NODE 10 and LUN have been input, the utility will select the unit and determine unit type (disk or tape) and select the proper test for the unit. The tape exerciser will write/read a 63K byte record to the unit. The disk exerciser will write/read a pattern across the disk surface sequentially. Either test is aborted by entering a CTRL C r'C) which returns to the Diagnostic Main menu.

Example:

WritelRead SCSI Unit

SCSI Node [00] : O<CR>

SCSI LON [00]: O<CR>

Testing Unit: SEAGATE ST12SN

Length of Test (Continuous/Long(l-S minutes)/Quick) ? Q<CR>

Read Only Test (Y/N) ? N<CR>

Write/Read Test

WARNING - Data will be overwritten<beep>

Proceed (Y/N) ? Y<CR>

SEAGATE ST12SN

Write Test Started

Press <Control-C> to abort

Write Test Completed

Read Test Started

Press <Control-C> to abort

Read Test Completed

**** CR to continue ****

Page 17

Option #3

The SCSI Format Unit menu item allows the user to select and format a specified SCSI unit. The user will enter the NODE 10 and the LUN of the unit. Once the NODE tD and LUN have been entered, the utility will scan the device and display the type of device selected. The user will be prompted with a wafning message. The utiiity will format the selected unit and display any errors that are encountered.

Example:

Format SCSI Unit

SCSI Node (00] : O<CR>

SCSI LUN [00] : O<CR>

Testing Unit: SEAGATE ST12SN

WARNING - Data will be overwritten<beep>

Proceed

(YIN)

? Y<CR>

Format Started

Completed with no Errors

**** CR to Continue ****

Option #4

The SCSI Bus Scan menu item allows the user to scan the attached SCSI bus for all devices and display the manufacturer and model of each device found. The utility scans each node starting with o and cycles through each logical unit

(0 thru

3) on each node. The utility will display each nodelLUN combination that is present on the SCSI bus. The utility does not prompt the user for any input.

Example:

SCSI Bus Scan

o

1

2

3

4

5

6

7

Node LUN o

o

o

o o o

o o

Type Current Device

Disk SEAGATE ST12SN

Not Found

Not Found

Not Found

Not Found

Not Found

Not Found

Host DILOG SQ739

**** CR to Continue ****

Page 18

Controller Configuration Menu

The Controller Configuration Menu contains the utility to change the configuration of the host adapter pertaining mainly to the aBUS interface. The utility allows the enabling/disabling of emulations, user defined address,burst and dwell rate, etc .. The user will be prompted for any changes to the current setup. The user can respond with Y, N or D. The 0 input will cause the default values to be used. If a Y or 0 was input, the user will be prompted to save the changes. A

(Y)es answer will write the values to the EEPROM for storage. A (N)o will return to the utility menu.

Once the data has been saved to EEPROM, the diagnostic will return to the utility menu.

The Emulation (E/D) prompt is used to enable/disable the specific emulation. If disabled, the selected aBUS address will not respond to the host processor and all SCSI nodes mapped to the emulation will not be utilized. The User Defined IP/SA Address is used to select the address that will be used when the switches are selected for user defined( i.e. SW1-3 and SW1-4 ON). This allows any address to be specified in the range 160000 - 177774 while maintaining a Quick method of setup for the first three(3) common address·s.

The DMA Burst Size prompts the user for the number of words transferred during one DMA operation. The user can input from 2 to 16. It is recommended that the burst rate be limited to 8 with older controllers which may not have adequate buffering.

The DMA Dwell Count is used to set the time to wait between dma bursts. This time period allows other DMA devices on the aBUS to transfer data to host memory. The allowable values are from 1 to 16 which allows for a dwell of between 200ns and 3.2us. It is recommended that a larger dwell count be utilized if the aBUS contains many PIO or interrupt driven controllers.

The Fast File Search prompt is used to enable the fast file search capability of 8MM Helical Scan

Devices. With this feature enabled, the tape unit will space in high speed search mode between tape marks allowing for a x10 increase in throughput. NOTE - a correctly reported TMSCP tape position is not possible. As most stand-alone backup programs require correct tape position to be returned to the host, it is recommended that the feature be disabled. The microcode does include an automatic enable during operating system startup that will override the EEPROM variable. This allows the operating system to take full advantage of the increase in throughput while still maintaining compatibility with the stand-alone backup utilities.

Auto Configuration on the SCSI Bus into MSCP/TMSCP Units on Boot allows self-configuring of the

SCSI bus devices. Note .: All devices must be powered on and able to respond to a SCSI bus inquiry command at boot time. Any devices not found at that time cannot be added without rebooting the system.

(The default values for the controller configuration are outlined in the example below)

Page 19

Example: controller Configuration Menu

MSCP Emulation (E/D)

User Defined MSCP IP/SA Address

TMSCP Emulation (E/D)

User Defined TMSCP IP/SA Address

DIna

Burst Size

Dma Dwell Count (x200ns)

Fast File Search (E/D)

Auto Configure SCSI Bus into

MSCP/TMSCP Units on Boot (E/D)

Enabled]

172150]

Enabled]

[ 174500]

(16] :

(01] :

(Disabled]

[Disabled]

Any

Changes (Y/N/Default) ?

D<CR>

Save Changes (Y/N) ? Y<CR> set in switch set in switch

Unit Mapping Menu

The Unit Mapping Menu is used to map the SCSI devices to MSCP and/or TMSCP unit numbers.

The SQ739 supports mapping of any SCSI node to any IT)MSCP unit number in the range 0 to 252.

The user can specify a SCSI NODE

10 and

LUN to be mapped along with the device type and the

IT)MSCP unit number. This information is stored in EEPROM and used on power-up to configure the host adapter. The utility supports a default setup mode (D) at the Changes prompt which will map

SCSI NODE 0 to MSCP unit 0 and set the host adapter NODE 10 to 7. If the user enters a

<

CR> at the select item prompt, all entries have been completed and the diagnostic will then prompt to save the changes. The USei must respond with a {Y)es or (N;o to continue. if a device is ready at the specified SCSI node, information about the drive will be displayed. Otherwise, WNot Found w will be displayed.

Note: If the Auto-configure option has been enabled, the current unit mapping is not displayed.

Instead, the devices on the SCSI bus are polled and displayed as they will be mapped if the system is booted. If the Auto-Configure option is disabled, the current unit mapping will be used again.

Example:

Unit Mapping Menu

1

2

3

4

5

6

7

8

9

Item Node

LON

o

7

(T)MSCP Type Device Name o

DUOOO

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

Disk SEAGATE ST125N

Host DILOG SQ739

Any

Changes (Y/N/Default/Remove/Scan) ? Y<CR>

Page 20

Select Item

Disk or Tape l<CR>

D<CR>

SCSI Node [01] l<CR>

SCSI LUN [00] O<CR>

MSCP Unit Number [001]

151<CR> select Item (CR to end)

Unit Mapping Menu

Item Node LUN

1

2

3

4

5

6

7

8

9 o

1

7

o

o

<CR>

(T)MSCP

Type Device Name

DUOOO

DU151

(Item not

(Item not

(Item not

(Item not

(Item not

(Item not

Disk

Disk

Mapped)

Mapped)

Mapped)

Mapped)

Mapped)

Mapped)

Host

SEAGATE ST125N

Not Found

DILOG SQ739

Save Changes

(YIN)

? Y<CR>

Unit Mapping Menu

1

2

3

4

5

6

7

8

9

Item Node LUN

o

1

7

(T)MSCP

Type Device Name o

DUOOO o

DU151

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

Disk SEAGATE ST125N

Disk Not Found

Host DILOG SQ739

Any

Changes (Y/N/Default/Remove/Scan) ? R<CR>

Select Item to Delete (CR to end) 2<CR>

Select Item to Delete (CR to end) : <CR>

5

6

7

8

9

1

2

3

4

Unit Mapping Menu

Item Node LUN (T)MSCP

0

7

Type Device Name

0 DUOOO

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

(Item not Mapped)

Disk SEAGATE ST125N

Host DILOG SQ739

Save Changes

(YIN)

?

Y<CR>

Page 21

Unit Mapping Menu

Item Node LUN

.,

2

o

1 o

o

(T)MSCP

CUOOO

MUOOO

Type Device Name

Disk SEAGATE

ST12SN

Tape EXABYTE EXB-8200

Auto Configure Option Enabled

****

CR to continue

****

The proper selection of a SCSI NODE 10 on a peripheral device is important to the overall performance of the system.

Be advised that the SCSI bus has an arbitration priority scheme that gives the highest priority device to NODE 7 and the lowest to NODE

O.

It is therefore recommended that the amount of activity on a SCSI device should be the determining factor when selecting the

SCSI node 10. If the system is configured for 4 disk devices and a single tape device, place the

SCSI tape device at a lower priority than the SCSI disk devices. The disks should also be configured dependent upon the

!/O

activity of the device. For example, the system disk should always be the highest priority SCSI peripheral to guarantee a minimum throughput under heavy

110 activity. With the flexibility of the SCSI Mapping Menu on the SQ739, maximum 110 throughput can be maintained for any given configuration.

Page 22

6 - Host Based Diagnostics

The S0739 supports a variety of DEC diagnostics to functionally test the host adapter. This section describes the procedure for the setup and execution of the supported diagnostics.

Startup - LSI/11 Systems

Install the host adapter as described in the Section 3. Apply power to the system and verify that both LED's on the S0739 are ON (refer to section 7 for troubleshooting if either LED's fail to light).

Install the XXDP

+

diagnostic medium into the drive and boot the system. When booting has completed successfully

I

the XXDP

+

sign-on message will appear.

XXDP-SM Small Monitor Version 2

Boot from XXX (where XXX is the boot device)

28kw Memory

Obus System

Restart Addr: 152010

This is XXDP-SM Type "H" or "HIL" for Help

Disk Emulation Diagnostics

The MSCP emulation of the S0739 supports two (2) DEC RC25 diagnostics including the ZRCF??

Front End Test and the ZRCD?? Disk Exerciser. The host adapter also supports a limited number of

MOM diagnostics for the DEC KDA50-Q controller.

Front End Test - ZRCFB3

The host adapter supports tests 1 thru 8 of the ZRCFB3 diagnostic. These tests will initialize the host adapter and extensively test the interrupt and DMA capability. Once the XXDP

+

prompt has appeared" . ", start the diagnostic by entering:

.R ZRCFB3<cr>

The system will echo the filename and load the file from the boot medium .

. R ZRCFB3

ZRCFB3.BIN

Once the diagnostic has been loaded, the diagnostic startup message will appear at the console device.

DRSSM-FO

CZRCF A 0

RC25 Front EndlHost Diagnostic

Unit is AZTEC RC25 Platter

RSTRT ADR 145676

DR>

Page 23

The diagnostic is started by entering the fo!!o\A'(ing command line:

DR> STA/FLA:PNT:HOErrES: 1-8

<

CR >

The above command

Hne instructs the diagnostic supervisor to run only tests 1 through 8, printing the total number of passes and halting in the case of an error. The supervisor will then prompt for hardware or software changes.

Change HW (L)

?

The diagnostic must be informed of the new hardware parameters of the system under test. Enter the following:

Change HW (L)

?

Y < CR >

Enter the numbei of host adapters which are to be tested.

#

Units (D)

?

1 <CR>

The diagnostic been selected: will then prompt the user to enter the following for the number of units that have

Unit 0

IP Address

(0)

172150 ? <CR>

Vector

(0)

154

?

< CR >

BR Level

(0)

5

?

4<CR>

Platter Address[es]

(0)

?

O<CR>

; or configured IP address

; or selected BR level

; aiways enter 0

The planer address is the unit number of the disk under test. Since the host adapter does not suppon the tests which require a disk, this question is irrelevant but must be answered before the diagnostic will stan. Once the hardware questions have been answered, the supervisor will prompt for any software changes:

Change SW (L) 7

The software question will always be answered NO because the host adapter DOES NOT suppon the test which require a disk drive.

Change SW (L) ? N<CR>

The diagnostic will print each test as it runs and will inform the user of any errors encountered.

The test can be stopped at any time by typing a CTLR C. For Example,

Testing Unit #: 0

Test 1

Test 2

Test 3

Test 4

Test 5

Test 6

Test 7

Test 8

IP _Register: 172150 Planer

Register Existence Test

Step 1 ReadIWrite Powerup Diagnostics

Diagnostic Wrap Test

Vector and BR Level Test

Step 1-3 readIWrite Diagnostic

Purge Poll Test

Small Ring Test

Large Ring Test

#:

0

Page 24

When the diagnostic has completed all the tests, the end of pass message will be printed and the diagnostic will restart until a CTRL C is executed. The diagnostic supervisor can be exited by typing

EXIT at the DR> prompt.

DZRCF EOP 1 o

Total Errors

"C

DR> EXIT <CR>

Disk Exerciser - ZRCDA 1

The host adapter is compatible with the DEC 'RC25 multi-drive exerciser ZRCD?? The diagnostic will initialize the host adapter and exercise the disk drives by issuing random LBN's with random byte counts. This diagnostic also supports up to four (4) host adapters and four (4) units on each host adapter.

Start the diagnostic when at the XXDP

+

prompt "." by issuing the following command line:

.R ZRCDA1 <CR>

The system will echo the filename during the loading process .

. R ZRCDA1 <CR>

ZRCDA1.BIN

Once the diagnostic has been loaded, the startup message will appear at the console device:

DRSSM-FO

CZRCD_A_O

RC25 Disk Exerciser

Unit is Single RC25 Platter

RSTRT ADR 145676

DR>

The ZRCDA 1 diagnostic requires a patch to load the proper unit size from the host adapter.

Patch 1

Patch 2

Patch 3

Patch 4

Address

26070

26072

30644

30704

37552

Value

16237

50

1003

1003

1416

Change To

12737

143326

1367

1367

240

Start the test after the diagnostic supervisor prompt DR> appears at the console device.

DR> STA/FLA:HOE < CR >

The above command line instructs the diagnostic supervisor to begin execution of the diagnostic.

The supervisor will then prompt for hardware or software changes.

Change HW (L) ?

Page 25

The diagnostic must be informed of the new hardware parameters of the system under test. Enter the following:

Change HW (l)

?

Y < CR >

Enter the number of host adapters which are to be tested.

# Units (D) ? 1 <CR>

The diagnostic will then prompt the user to enter the following for the number of units that have been selected:

Unit 0

IP Address

(0)

172150

?

< CR >

Vector

(0)

154

?

<CR>

BR level

(0)

5 1 4<cr>

; or configured IP address

; or selected BR level

Platter Address (Unit Plug) (D) 0 ? < CR >

Allow Writes To Customer Data Area on this Platter (l) 1 Y < CR

> ; enable writes

•• WARNING - CUSTOMER AREA MAY BE OVERWRITIEN ! ...

CONFIRM (l) ? Y < CR >

The platter address is the unit number of the disk drive under test. The customer data area is the host data area of the disk drive and is used to test the controller. Backup any data on the disk drive, if necessary, before continuing with the diagnostic.

After the hardware questions are answered, the supervisor will prompt the user for any software changes:

CHANGE SW (l) ?

The user can take the default software values because the drives are larger than an RC25, If the tests are being run on a smaller unit, some of the software values may have to be changed to prevent errors from occurring.

If the selected unit is fully formatted, use the default values by typing NO to the software Query:

CHANGE SW (l) 1 N <CR>

To change the software default values, answer YES to the software query:

CHANGE SW (l) ? Y < CR >

The user will then be prompted by the supervisor to input the following information:

ERROR LIMIT

(0

FOR NO LIMIT) (D) 321

<

CR

>

Page 26

Enter the error limit that must be reached before a unit is deselected by the diagnostic. The default value of 32 is used.

TRANSFER LIMIT IN MEGABYTES

(0

FOR NO LIMIT) (D) 27 <CR>

Enter the number of bytes to be transferred between the controller and the diagnostic. Effectively, this selects the time required to reach an END OF PASS.

SUPPRESS PRINTING ERROR lOG MESSAGES (l) 7 <CR>

The default value should be used unless multiple errors occur and more information is required to resolve the problem.

RUN OM EXERCISER INSTEAD OF MULTI-DRIVE SUBTEST (l) N7 <CR>

The default must always be taken because the controller does not support Diagnostic Mode (OM) of operation.

RANDOM SEEK MODE (l) Y 7 < CR >

The best possible test is to seek randomly across the entire disk surface. Therefore, the default value should be used.

STARTING TRACK (l) Y 7 <CR>

The starting track number is to be entered. Because the controller does not emulate the RC25, the questions regarding starting and ending track numbers do no apply. If the unit under test is fully formatted and is more than

40 megabytes, the diagnostic will not overflow the cylinder address.

ENDING TRACK (D) 1641? < CR >

Enter the ending track number. If the unit is larger than an RC25 unit (40 megabytes), the default can be used.

READ-COMPARES PERFORMED AT THE CONTROLLER (l) Y7 < CR >

A ·Yes· typed here will cause the controller to compare the data read with host memory.

THE REMAINING QUESTIONS APPLY ONLY TO UNPROTECTED PLA TIERS.

The user can use the default values for the remaining questions.

WRITE ONLY (l) N7 < CR >

The disk drive under test is never a write only disk; therefore, always take the default.

WRITE-COMPARES PREFORMED AT THE CONTROllER (l) N? <CR>

Page 27

The controller will perform write checks if the default is taken.

CHECK ALL WRITES AT HOST BY READING (L) Y? < CR >

The diagnostic will NOT issue read commands to check the data just written if the default is taken.

Otherwise, the diagnostic sorrvVare wili perform the write check function.

USER DEFINED DATA PATTERN (L) N? <CR>

The data pattern used in the diagnostic is worst case. To ensure prompt testing, always use the default value.

SELECT PREDEFiNED DATA PATTERN '(0 FOR SEQUENTIAL SELECTION) (D) 0: < CR >

Always use the default value.

The test will begin after the hardware and

~oftware questions are answered.

INIT SUBTEST START

ABOUT TO VERIFY VECTOR 154(0) FOR DEVICE 172150(0) ... COMPLETED

The diagnostic will run until the transfer limit is reached. After the limit has been reached, the diagnostic will print status information about the unit under test and display the END OF PASS:

CZRCD EOP 1 o

TOTAL ERRORS

Page 28

Tape Emulation Diagnostics

The TMSCP emulation of the SQ739 supports two(2) DEC TK50 diagnostics including the ZTKA??

Front End Test and the ZTKB?? Reliability Test. The host adapter also supports a limited number of

MOM diagnostics for the DEC TK50 controller.

Front End Test for TK50 - ZTKACO

Start the diagnostic when at the XXDP

+

prompt·.· by issuing the following command line:

.R ZTKACO<CR>

The system will echo the filename during the loading process .

. R ZTKACO<CR>

ZTKACO.BIN

Once the diagnostic has been loaded, the startup message will appear at the console device:

DRSSM-FO

CZTKA_C_O

TK50 Front End Test

Unit is TK50Q

RSTRT ADR 145676

DR>

The ZTKACO diagnostic requires a patch to load the proper unit size from the host adapter.

Patch 1

Address

44154

44156

Value

16537

2260

Change To

12737 o

Start the test after the diagnostic supervisor prompt DR> appears at the console device.

DR> STA/FLA:PNT:HOEfTES: 1-8 < CR >

The above command line instructs the diagnostic supervisor to begin execution of the diagnostic running tests 1 to 8 only

I

printing the total number of passes and halting in the case of an error.

The supervisor will then prompt for hardware or software changes.

Change HW (L) ?

The diagnostic must be informed of the new hardware parameters of the system under test. Enter the following:

Change HW (L) ? Y < CR >

#

UNITS (D) ? 1 <CR>

UNIT 0

TKIP ADDRESS (0) 174500 ? <CR>

TK VECTOR (O) 260

?

< CR >

; or configured IP address.

Page 29

T/MSCP UNIT NUMBER

(0)

0 ? <CR>

CHANGE SW (L) ?

The diagnostic will then prompt for any software switch register changes to be entered. The diagnostic does not require any changes, enter NO.

CHANGE SW (L) 7 N<CR>

Tha diagnostic wiii print each test as

it

runs. Tests 1 to 8 perform the functions described below.

TEST 1 - REGISTER EXISTENCE TEST

TEST 2 DIAGNOSTIC WRAP TEST

TEST 3 - STEP 1-3 INITIALIZATION TEST

TEST 4 - VECTOR AND INTERRUPT TEST

TEST 5 - BR LEVEL TEST

TEST 6 - PURGE AND POLL TEST

TEST 7 - LARGE RING TEST

TEST

8 -

EXTENDED ADDRESS TEST

To stop the execution of the diagnostic, type a CTRL-C (AC). To exit the diagnostic supervisor, enter EXIT at the DR prompt.

DR>EXIT<CR> program will return to the XXDP

+

prompt

TK50 Data Reliability Test - ZTKBBO

The SQ739 supports the TK50 Data Reliability diagnostic test 1 to 6 only. These tests will check the data reliability of the subsystem by performing several read, write and repositioning functions.

Start the diagnostic when at the XXDP

+

prompt • .• by issuing the following command line:

.R ZTKBBO<CR>

The system will echo the filename during the loading process .

. R ZTBBCO<CR>

ZTKBBO.BIN

Once the diagnostic has been loaded, the startup message will appear at the console device:

CZTKBBO TK50 Data Reliability Test

Unit is TK50

RSTRT ADR 145676

DR>

The diagnostic is started by entering the command line:

DR> START IFLAG :PNT {fEST: 1-6 < CR >

This command instructs the diagnostic supervisor to start the diagnostic and run test 1 through 6 only, printing the total number of passes and halting in the case of an error .. The supervisor will

Page 30

then prompt for hardware and software changes. The user must enter the number of units under test.

CHANGE HW (l) ? Y<CR>

# UNITS

(D)

? 1 <CR>

UNIT 0

TKIP ADDRESS

(0)

174500 ?<CR>

TK VECTOR (0) 260? <CR>

T/MSCP UNIT NUMBER (0) 0 ?<CR>

CHANGE SW (l) ? Y < CR >

ENABLE TIME OF DAY CLOCK (l) N ? <CR>

CHANGE CONTROLLER PARAMETERS (l) N ? < CR >

CHANGE PRINTING PARAMETERS el) N ? <CR>

CHANGE TEST PARAMETERS (l) N ? Y < CR >

DATA PATIERN (0) 0 ?<CR>

RUN TEST 3 ONLY (l) Y ? N<CR>

ENABLE DATA COMPARES IN TEST 5 (l) N ?<CR>

ENABLE PRINT READ BUFFER IN TEST 5 (l) N ? < CR >

CHANGE COMMAND SEQUENCE (l) N

?

< CR >

The diagnostic will print each test header as it is run. Tests 1 through 6 perform the functions described below.

TEST 1 - BASIC FUNCTION TEST

TEST 2 - QUICK VERIFY READM'RITE TEST

TEST 3 - COMPLEX READM'RITE TEST

TEST 4 - WRITE INTERCHANGE TEST

TEST 5 - READ UNKNOWN TAPE

TEST 6 - START ISTOP WRITEIREAD TEST

To stop execution of the diagnostic, type a CTRl-C (AC) at the console.

To exit the Data Reliability test type EXIT at the DR prompt as shown below.

DR>EXIT<CR>

Page 31

MicroVAX II System Diagnostics

MOM Diagnostic for Tape

The SQ739 host adapter does support and is compatible with the ioiiowing MicroVAX II MOM diagnostics listed below.

Service Functional (1i i )

Verify Functionai (1 J

- Run tests 1-8 only

- Run tests 1-8 only

For additional information regarding MOM diagnostics, refer to the MicroVAX Diagnostic Monitor

Users Guide, order number AA-FM7S8-0N.

MOM Diagnostics for Disk

NONE SUPPORTED

Page 32

7 - Errors and Troubleshooting

The SCSI cable that connects the host adapter to the drives must be terminated at both ends. Since the host adapter is already terminated, this must be one end of the cable. If several drives are attached to the cable, the drive at the end of the cable must be the only drive with termination.

If you are experiencing problems, option 1 of the configuration menu allows a single SCSI command to be given directly to the drive. This is documented in Section S.

For example, a SCSI Test Unit Ready command is as follows:

6 bytes - 0,0,0,0,0,0

Enter and execute this command. If it cannot be executed, the system may return SCSI Request

Sense command information. Consult the drive manual to decode this information. NOTE: After a

SCSI bus reset, the SCSI Test Unit Ready command will usually return an error indicating that the bus was reset. Execute the SCSI command again to clear this error.

The SCSI Request Sense command information returned from a SCSI command that failed is error status returned from the drive. This allows drive vendors to give general SCSI status and vendor unique information. General SCSI status is summarized in the four bits of word three of the returned information. This is called the SENSE KEY and is as follows:

0- NO SENSE. No specific information to return

1 - RECOVERED ERROR. last command completed successfully but with some drive recovery action.

2 - NOT READY. Drive not ready.

3 - MEDIUM ERROR. Media error.

4- HARDWARE ERROR. Drive has detected a hardware fault.

S - ILLEGAL REQUEST. The SCSI command is incorrect for the drive.

6 - UNIT ATTENTION. SCSI bus was reset or drive media was changed.

7 - DATA PROTECT. Drive is write protected.

Consult the drive manual for additional Request Sense information to further isolate the problem.

Symptom

Check

Controller address not found - Is emulation enabled in Diagnostic Main Menu ?

- Is correct IP/SA address set in switch or Diagnostic Main Menu?

- Is self-test light on ?

SCSI device not found

- Is SCSI cable connected ?

- Is SCSI cable connection inverted ?

- Is device at a unique node address ?

- Is the termination power LED on ?

- Is device mapped into (T)MSCP unit in Diagnostic Main Menu?

- Is device found using SCSI bus Scan in Diagnostic Main Menu ?

Data errors - Is SCSI cable terminated at both ends?

- Is SCSI cable length greater than 1 8 feet ?

- Is SCSI drive power source adequate ?

Page 33

8 - Error Loos

The error logs that are generated by the host adapter conform to the MSCP and TMSCP specification. The host/device dependent area contains information saved by the host adapter about the specific error. This information can then be used to aid the user in troubleshooting the problem.

The format of the error log is consistent throughout the section. The error log outline contains the contents of the error log while the boxes at the far left are the BYTE OFFSET of the longword.

Host Memory Access Error Log

31

Host Memory Access Error Log

o

Controller Dependent Information

Buffer Low

Undefined

Host DMA Address

Q

Status

28

I

Byte Count

Modifiers

32

I

Burst

I

Dwell Buffer Hi

36

Page 34

Disk Transfer Error Log

31

MSCP Disk Transfer Error Log

Undefined

COB Byte 3

COB Size

I

COB Byte 2 COB Byte 1

Unit 10

COB Byte 8

COB Byte 4

I

COB Byte 7 COB Byte 6

SCSI Inquiry Byte 16 to 19

Logical Block Number

Ucode Rev

COB Byte 0

COB Byte 3

COB Byte 5

o

0

16

20

24

28

32

36

40

Controller Dependent Information

Request Sense Command Information

31

Byte 14

Byte 18

Byte 22

Not Used

Byte 13

Byte 17

Byte 12

Byte 16

Byte 21 Byte 20

Internal Error Byte 24

Sense Key

Byte 15

Byte 19

Byte 23

0

44

48

52

56

Internal Error ;; 01 H SCSI Check Condition

= 02H SCSI Parity Error

=

03H aBUS NXM Error

=

04H Reassign Bad Block Executed

=

06H Odd Byte Count Error

=

07H Odd Address Error

=

08H Invalid Logical Block Number (LBN)

=

09H SCSI Target did not respond

= OAH SBIC Fatal Error

=

OBH SCSI Bus Reset Detected

=

ODH SCSI Parity Error (Recoverable)

= 13H Operation Timeout

=

15H SCSI Device Busy Timeout

=

16H Self Test Error

=

1 9H Fatal Port Error

=

1 AH Fatal Controller Error

Page 35

Disk SOl Error Log

31

MSCP Disk Transfer Error Log

Undefined

CDS Byle 3

I

" n D D ...... ' l

COB Size

('nD

9ytC"

1

'-''"'........ I.e;;; •

Unit Number

COB Byte 8

COB Byte 4

I

COB Byte 7

COB Byte 6

SCSI Inquiry Bytes 16 to

19

Logical Block Number

Assy Rev

CDB Byte 0

COB Byte 3

COB Byte 5 o

I

0

16

20

28

32

36

40

Controiier Dependent Information

Request Sense Command Information

31

Byte 14

Byte 18

Byte 22

Not Used

Byte 13

Byte 17

Byte 21

Byte 12

Byte 16

Byte 20 .

Internal Error Byte 24

Sense Key

Byte 15

Byte 19

Byte 23

0

44

48

52

56

Internal Error = 01 H SCSI Check Condition

=

02H SCSI Parity Error

=

03H aBUS NXM Error

=

04H Reassign Bad Block Executed

=

06H Odd Byte Count Error

= 07H Odd Address Error

= 08H Invalid Logical Block Number (LBN)

=

09H SCSI Target did not respond

=

OAH SBIC Fatal Error

=

OBH SCSI Bus Reset Detected

=

OOH SCSI Parity Error (Recoverable)

=

13H Operation Timeout

= 1 5H SCSI Device Busy Timeout

=

1 6H Self Test Error

=

19H Fatal Port Error

= 1 AH Fatal Controller Error

Page 36

Tape Transfer Error log

31

TMSCP Tape Transfer Error log

Current Tape Position o

0

32

36

40

CONTROLLER DEPENDENT INFORMATION

Request Sense Command Information

31 0

COB Byte 2 COB Byte 1 COB Byte 0 COB Size

Sense Key COB Byte 5 CDS Byte 4

COB Byte 3

Byte 20

Byte 19 Byte 13 Byte 12

Byte 16 Internal Error Op Code Byte 21

44

48

52

56

Internal Error

=

01 H SCSI Check Condition

=

02H SCSI Parity Error

= 03H aBUS NXM Error

= 05H Transfer Request

>

64KB

=

09H SCSI Target did not respond

= OAH SBIC Fatal Error

=

=

=

=

OBH SCSI Bus Reset Detected

OEH SCSI Reservation Conflict

10H Serious Exception Found

13H Operation Timeout

=

=

16H Self Test Error

=

1 7H TMSCP Unit Available

=

18H TMSCP No Volume

=

1 9H Fatal Port Error

1

AH Fatal Controller Error

Page 37

46

47

48

49

50

51

Exabyte

EXB-8200 Error Log Definition

Bvte Definition

36

44

45

Current Tape Position

SCSI Command Size

8!t 7-0 06 Six (5) Byte Command

12 Twelve(12) Byte Command i 0 Ten

(i

OJ

Byte Command

SCSI Command Opcode

Bit 7-0 00 Test Unit Ready

03 Request Sense

08 Read

10 Write Filemark

12 Inquiry

19 Erase

1 B Load/Unload

01 Rewind

05 Read Block Limits

OA Write

11 Space

15 Mode Select

1 A Mode Sense

SCSI CDB Byte 1

SCSI CDB Byte 2

SCSI CDB Byte 3

SCSI CDB Byte 4

SCSI CDB Byte 5

Sense Key

Bit 7 Ale Mark

Bit

6

End Of Media

Bit 5 Incorrect Length Indicator

Bit

4

Not Used

Bit 3-0 0 No sense

2 Not Ready

4 Hardware Error

6

Unit Attention

8 Blank Check

A Copy Aborted

C Not Used

E Not Used

1 Not Used

3 Medium Error

5 Illegal request

7 Data protect

9 Exabyte

B Aborted Command

D Volume Overflow

F Reserved

52

53

Sense Code (Additional)

Bit 7-0 02 Not Ready

Sense Qualifier (additional)

Bit 7-0 00 Voiume not Mounted 01 Busy Rewinding or Loading

Page 38

54

55

56

SCSI Status

Bit 7 Power Fail

Bit 6 SCSI Bus Parity Error

Bit 5 Formatted Buffer Parity Error

Bit 4 Media Error

Bit 3 Error Counter Overflow

Bit 2 Tape Motion Error

Bit 1 Tape Not Present

Bit 0 Beginning of Tape

SCSI Status

Bit 7 Transfer Abort Error

Bit 6 Tape Mark Detect Error

Bit 5 Write Protect

Bit 4 Write Filemark Error

Bit 3 Underrun Error

Bit 2 Write Error 1

Bit 1 Servo System Error

Bit 0 Formatter Error

SCSI Status

Bit 7-2 Reserved

Bit 1 Write Splice Error

Bit 0 Write Splice Error

Page 39

9 - Standard

EiiOi

Codes

Self Test Error Codes

If an error occurs during se!f=test, an eiior code wiii be fiashed on the activity LED (02) and sent to the terminal port if enabled. A long flash represents a ·1· while a short flash indicates a ·0·. The flashes are decoded starting with the most significant bit (MSB). The error code can be identified by the following error code table,

Error Code

0

1

2

3

4

5

6

7

8

9

Description

EEPROM Checksum Error

Ram Error

Disk aBIC Error

Tape aBIC Error

SBIC Error

Fifo Error

Serial Port Error aBUS Interrupt Error aBUS DMA Error

SCSI Term Power Error

Fatal SA Error Codes

The SA error codes will be posted in the SA register upon detection of a fatal error which prevents the proper operation of the host adapter. Bit 15 set in the SA register indicates a fatal error while the low byte indicates the type of failure.

Hex

8001

8002

8006

B007

8009

BOOA

8013

B01C

801x

Octal

100001

Description

Envelope/Packet Read Error

100002 EnvelopelPacket Write Error

100006

Ring Read Error

100007

Ring Write Error

100011 Host Access Timeout

100012 Credit Limit Exceeded

100023 Step 1 Init Error

100034 Step 3 NXM Error

1001 xx Fatal Firmware Error (see below)

Page 40

804C

8040

804E

804F

8050

8051

8052

8053

8054

8055

8056

8057

8058

8059

805A

Hex

8041

8042

8043

8044

8045

8046

8047

8048

8049

804A

804B

Octal

100101

100102

100103

100104

100105

100106

100107

100110

100111

100112

100113

100114

100115

100116

100117

100120

100121

100122

100123

100124

100125

100126

100127

100130

100131

100132

Description

Out of range opcode in io _prep

Out of range opcode in io _busy

Out of range opcode in a-bus interrupt

Out of range SCSI phase

Out of range opcode in SCSI reselect

OBIC interrupt wlhsi full set

OBIC interrupt wlhsi holding set

SCSI interrupt wIno status

OBIC interrupt twice on command

OBIC interrupt w/wrong ack

OBIC interrupt wIno status

SCSI interrupt interrupt w/wrong ack

SCSI reselect interrupt w/wrong ack

SCSI reselect interrupt w/wrong current command

SCSI chip illegal command

SCSI gross error

SCSI unexpected phase execute routine is off a-bus timeout

SCSI timeout

SCSI unknown reselect

SCSI flush queue failed

SCSI bus reset will not work other OBI C has error write_ip during diagnostics auto configure failure wIno nodes for host

Page 41

VMS Error Codes

MSCP

MSCP error log sample. Only accurate system descriptions have been inciuded aiong with special meanings in bold italics for the SQ739.

*******************************

ENTRY

ERROR SEQUENCE 14"

DATE/TIME 18-OCT-1991 09:53:07.60

SYSTEM UPTIME: 0 DAYS 00:05:35

SCS NODE:

ERLSLOGMESSAGE ENTRY KA630

2.

*******************************

LOGGED ON: SID 08000000

SYS TYPE 01010000

VAX/VMS V5.4-2

I/O SUB-SYSTEM, UNIT DUA3:

MESSAGE TYPE

0001

MSLGSL CMD REF

AD1AOO02

MSLGSW-UNIT

0003

MSLGSW-SEQ NUM

MSLGSB-FORMAT

0000

03

MSLGSB:FLAGS 01

MSLGSW_EVENT

MSLGSQ_CNT_ID

0023

33375153

010D2039

MSLGSB CNT SVR

MSLGSB-CNT-HVR

KSLGSW-MULT UNT

MSLGSQ:UNIT:ID

MSLGSB UNIT SVR

MSLGSB-UNIT-HVR

MSLG$L-VOL SER

MSLGSL::HDR:CODE

MSLG$Z SOl

REQUEST

MODE

ERROR

CONTROLLER

RETRY

FO

IF

0000

00000028

02010000

RA80

00

00

2D4F4D53

00000000

02

OA

00

00

00

SK MSCP MESSAGE

UNIT #3.

SEQUENCE #0.

SOl ERROR

SEQUENCE NUMBER RESET

UNRECOVERABLE ERROR

UNIT OFFLINE

NO MEDIA LOADED/DISABLED VIA SWITCH

80739 reversed in ascii code

MASS STORAGE CONTROLLER

KDA50-Q

SCSI

CDS

bytes 3/2/1/0

SCSI

CDS

bytes 4/5

SCSI CDS byte 6

SCSI CDS byte 7

SCSI inquiry bytes

16 to

19

LOGICAL BLOCK #0.

GOOD LOGICAL SECTOR.

Sense k.ey

Sense byte 12

Sense byte 13

Sense byte 14

Sense

b~e

15

DEVICE DEPENDENT INFORMATION

LONGWORD 1. 3COOOOOO

LONGWORD 2. 07001000

LONGWORD 3. 008D0122

Sense

b~es

20/19/18/17

Sense

b~es

24/23/22/21

NA/NA/internal error/Sense byte 25

This error log indicates a MSCP error of 23 which is no media. The SCSI command was a read (COB 28,00,00,00,00,00,00,00). The SCSI read command had an internal error of 01 which is a SCSI check condition. The sense bytes from the SCSI request sense that was automatically done after the read had a sense key of 2, which is a NOT READY condition.

Page 42

TMSCP

TMSCP error log sample. Only accurate system descriptions have been included along with special meanings in bold italics for the 5Q739.

******************************* ENTRY

ERROR SEQUENCE 22.

DATE/TIME 18-OCT-1991 10:02:14.22

SYSTEM UPTIME: 0 DAYS 00:14:42

SCS NODE:

ERL$LOGMESSAGE ENTRY KA630

10. *******************************

LOGGED ON: SID 08000000

SYS TYPE 01010000

VAX/VMS Vs.4-2

I/O SUB-SYSTEM, UNIT _MUAO:, CURRENT·LABEL ""

MESSAGE TYPE

MSLG$L CMD REF

MSLG$W-UNIT

MSLG$W-SEQ NOM

MSLG$B-FORMAT

MSLG$B:FLAGS

MSLG$W_EVENT

MSLG$Q_CNT_ID

MSLG$B CNT SVR

MSLG$B-CNT-HVR

MSLG$W-MULT UNT

MSLG$Q:UNIT:ID

MSLG$B UNIT SVR

MSLG$B -UNI

iiVR

MSLG$ B-LEviL

MSLG$B-RETRY

MSLG$L-GAP CNT

MSLG$B -FMTR SVR

MSLG$B:FMTR:HVR

0002

AB6FOOOs

0000

0000

OS

TAPE MSCP MESSAGE

UNIT #0.

SEQUENCE #0.

APE TRANSFER LOG

01

0023

UNIT OFFLINE

NO MEDIA LOADED/DISABLED VIA SWITCH

33375153

3092039

80739 reversed in

TAPE CLASS DEVICE

ascii code

TQKsO

OS

SEQUENCE NUMBER RESET

UNRECOVERABLE ERROR

04

0001

33377173

03032039

TKsO

OS

80739 reversed in ascii code

TAPE CLASS DEVICE

04

00

01

00000000

05

04

TKsO DEVICE/CONTROLLER DEPENDENT INFORMATION

DRIVE FLAGS

TRK NUMBER

PHYSICAL

BLK#

LOGICAL

BLK#

TAPE POSITION

DRIVE STATE

RD

/WRT STATE

OPERATION FLGS

CNTRLR STATUS

DRIVE ERR CODE

08

00

0000

SA

020000

0004

3C02

2100

01

00

CDB byte

0

CDBbyte1

CDB byte3/CDB byte 2

CDBbyte4 sense key/CDB byte 5/NA sense byte 13/sense byte 12 sense byte 19/sense byte 20 opcode/ sense byte 21 internal error sense byte 16

This error log indicates a TMSCP error of 23 which is no media. The SCSI command was a read (CDS 08,OO,OO,OO,5A,OO). The SCSI read command had an internal error of 01 which is a

SCSI check condition. The sense bytes from the SCSI request sense that was automatically done after the read had a sense key of 2, which is a NOT READY condition. The TMSCP opcode is 21 which is a read.

Page 43

Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement