| Title: | CSGUK_SYSTEMS |
| Notice: | No restrictions on keyword creation |
| Moderator: | KERNEL::ADAMS |
| Created: | Wed Mar 01 1989 |
| Last Modified: | Thu Nov 28 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 242 |
| Total number of notes: | 1855 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 17.1 | 6300 DIAGNOSTICS + TK70. | KERNEL::MOUNTFORD | Fri Mar 17 1989 00:03 | 106 | |
From: KERNEL::COMICS::BEDDALL "Peter Beddall - Product and Technology Group 16-Mar-1989 0949" 16-MAR-1989 09:53
To: @6200.DIS,BEDDALL
Subj: Booting 6300 diagnostics from TK50
+-------------+
| | | | | | | |
|d|i|g|i|t|a|l| C U S T O M E R S U P P O R T C E N T R E
| | | | | | | |
+-------------+
INTEROFFICE MEMORANDUM
To: 6xxx Engineers Date: 16-MAR-1989
From: Peter Beddall
cc: Ext: 7833 3804
Loc/mail stop: UVO Basingstoke
DECnet: COMICS::BEDDALL
Subject: Diagnostics for 6300 Systems
Currently the TK50 that Galway are shipping with all new 6300
systems fails to boot the Diagnostic Supervisor. The failure is
shown below. One work-around that appears to work is halt the CPU
and restart it at 10000. Operation then seems to continue normally.
ESASE are currently investigating the failure, and I will update you
all with their findings as necessary.
Please note that this failure is only for booting the TK50, it is
still possible to boot the diagnostic supervisor off other media
without problem.
It is worth noting that Galway ship V11.4 of the supervisor, I have
obtained V11.6 which can be copied from:
comics::sys$public:elsaa_v1106.exe
There are also some associated release notes. I do not yet know if
this version fixes the 6300 supervisor boot problem.
If you have any problems then please give me a call.
Cheers
Pete
Details on 6300 Boot failure.
-----------------------------
>>> B CSA1/R5:10
A message is printed indicating that the system software is being loaded. A
message to remove the current volume is issued, this is usual for boots
from tape. The tape is removed and reloaded, and the boot continues.
After a few moments, instead of the expected message announcing the VAX
Diagnostic Supervisor, confidentiality and the supervisor version ( in this
case ZZ-ELSAA-11.4-591 ), a different message is sent to the screen:
?? Unexpected trap or interrupt thru SCB vector 0060
PC at error: 00038241(X)
PSL at error: 00000004(X) ; CUR=KERNEL,PRV=KERNEL,IPL=00(X),Z
User return PC: none found!
However, the console is NOT back at the console prompt but at the Diagnostic
supervisor prompt.
The command,
DS> SHO MEM
gives the following output:
DS> SHO MEM
00000000 (%D0) : Reserved page
00000200 (%D512) : Beginning of diagnostic region
0000FA00 (%D64000) : APT Ptext buffer
0000FE00 (%D65024) : APT Mailbox
00010000 (%D65536) : Beginning of Diagnostic Supervisor
0003D400 (%D250880) : End of Supervisor load image
000D5200 (%D872960) : Start of ULTRIX buffer space
000DB400 (%D898048) : Start of Supervisor memory pool
003F31A0 (%D4141472) : Start of IRP Look-aside list
003F3200 (4045Kb) : Top of run-time Diagnostic Supervisor
02000000 (32768Kb) : Top of physical memory
This is the same output as for the correct diagnostic boot.
However, if an operation involving the tape is issued, it fails almost
immediately, as follows,
DS> LOAD EVSBA
%RMS-F-DEV, bad device, or inappropriate device type (R0=000184C4)
DS>
This is the failing case seen here. The conditions necessary for failure seem
to be a TBK70/TK70 and one of the TK50 cartridges, AQ-FK60A-ME.
| |||||
| 17.2 | 62xx/63xx Sid & Systype reg. | KERNEL::MOUNTFORD | Wed May 31 1989 09:02 | 59 | |
This information is applicable to the 6200 and 6300 series systems.
SID REGISTER (IPR 3E) - Location CVAX
---------------------
31 24 23 08 07 00
+----------------+----------------+----------------+----------------+
! TYPE ! RESERVED ! UCODE REV !
+----------------+----------------+----------------+----------------+
\ / \ /
-------------- --------------
^ ^
This field is always 0A, This field shows the
indicating CVAX chip microcode revision level
of the CVAX chip
EXAMPLE CVAX Revision Bits 7:0
+---------------------+ ------------------------
| >>> E/I 3E | 3.0 02
| I 0000003E 0A000003 |---------+ 3.1 02
| >>> | | 3.2 02
+---------------------+ +------------------> 4.2 03
4.4 04
SYSTYPE REGISTER - Location EEPROM (20040004)
----------------
31 24 23 16 15 08 07 00
+----------------+----------------+----------------+----------------+
! SYS TYPE ! REV LEVEL ! RESERVED ! LICENSE ID !
+----------------+----------------+----------------+----------------+
\ / \ / \ / \ /
-------------- -------------- -------------- --------------
^ ^ ^ ^
This field has a This field shows This field was This field reflects
value of 2 for the CPU console RESERVED, but the CPU LICENSE ID.
KA62A/B CPU code REV LEVEL now appears to It will be 1 for a
modules encoded in the be used for timesharing system,
form x.y; upper 6300 CPU's 2 for a VAXSERVER
nibble=x, lower (KA62B)
nibble=y
EXAMPLE 1 EXAMPLE 2
+---------------------+ +---------------------+
| >>> E/U 20040004 | | >>> E/U 20040004 |
| P 20040004 02310001 | | P 20040004 02400202 |
| >>> | | >>> |
+---------------------+ +---------------------+
This example shows a This example shows a
console code REV LEVEL console code REV LEVEL
of 3.1 and a timesharing of 4.0 and a VAXSERVER
6200 CPU 6300 CPU
| |||||
| 17.3 | 62xx/63xx Sid & Systype in errorlogs. | KERNEL::MOUNTFORD | Wed May 31 1989 09:03 | 30 | |
Error Log Report Generator Version V05-000
---------------
**************************** ENTRY 39. ****************************
ERROR SEQUENCE 3026. LOGGED ON: SID 0A000002 <----+
DATE/TIME 20-MAR-1989 22:58:13.57 SYS_TYPE 02310001 |
\/ |
SCS NODE: LOOKIN, XMI NODE # 2. +------+ |
NON-FATAL BUGCHECK KA62A CPU REV# 2. FW REV# 49.<----decode incorrect--+ |
| |
+-----------------------------------------+
(body of errorlog entry removed)
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Error Log Report Generator Version V5.1-1
--------------
**************************** ENTRY 4. ****************************
ERROR SEQUENCE 3081. LOGGED ON: SID 0A000002 <----+
DATE/TIME 8-MAY-1989 10:25:28.20 SYS_TYPE 02310001 |
+--note the change (see table in previous entry---+
|
TIME STAMP KA62A CPU REV# 3. FW REV# 3.1
SCS NODE: LOOKIN, XMI NODE # 2.
| |||||
| 17.4 | 6000-series summary | KERNEL::BARTLEY | Wed Jul 12 1989 17:42 | 517 | |
VAX 6000-400 SYSTEM ADVISORY
John Stevens
CSSE Mid-Range Systems Engineer
ABSTRACT
The Tables presented here give a concise overview of
the similarities and differences between the various CPUs on
the Calypso platform, and provide information on diagnostics,
Documentation, and Logistics for the VAX 6000-400.
DIGITAL EQUIPMENT CORPORATION - INTERNAL USE ONLY
Table 1. Similarities in the platforms for VAX6200, VAX6300, and VAX6000-400
-------------------------------------------------------------------
At the System level:
Same Cabinet and Control Panel
Same Power and Battery Back Up unit
Same Backplanes (XMI and VAXBI)
Same I/O Expansion capabilities (VAXBI Expander)
* Same AC Power requirements
* Same Site Preparation
** Same Configuration rules
At the Module level:
Same Memory (MS62A (XMA) 32MEG/Module)
Same I/O Adapters (DWMBA, the XBIA, XBIB pair)
Same I/O Controlers
Same XTC
* Voltage Freq. # of I Thermal Dissip Recept. Physical
Nominal Nom Phas AC Type size
V Hz Amps Watts Btu/h In[cm] Weight
[KJ/h] H W D Lbs[kgs]
208 60 3 8 1,600 5,440 L21-20R 60X30X30 700
380/416 50 3 4 1,600 [5,712] 516R6W [154x78x76] [318]
** 1. To get self test trace CPU must be in slot 1.
2. Side 2 of Vector must be next to side 1 of Memory.
Table 2. Differences between the VAX6200, VAX6300 and the VAX6000-400
------------------------------------------------------------
VAX SYSTEMS
6200 6300 6000-400
PERFORMANCE 2.8/CPU 3.8/CPU 6.8/CPU
CYCLE TIME 80 nsec 60 nsec 28 nsec
TECHNOLOGY CMOS I CMOS II CMOS II
(2.0 Micron) (1.5 Micron) (1.5 Micron)
ATTACH PROCESS 50 mil 50 mil 25 mil
CHIPS
Processor CVAX CVAX DC520 (Rigel)
System Support SSC SSC RSSC
Floating Point CFPA CFPA F_Chip
XMI Interface XCPGA XCPGA REXMI (1 XCA and 2 XDPs)
Cache Control VC Chip
MODULE DATA PATHS 32 BIT 32 BIT 64 BIT
PRIMARY CACHE
Size 1 KB on Chip 1 KB on Chip 2 KB on Chip
Organization 2-Way Set Assoc 2-Way Set Assoc Direct Mapped
Data Contents I Stream I Stream I & D Stream
Access Time 2 Cycles 2 Cycles 1 Cycle
Fill Size Longword Longword Quadword
BACHUP CACHE
Size 256 KB (64KX4) 256 KB (64KX4) 128 KB (16KX4)
Organization Direct Mapped Direct Mapped Direct Mapped
Data Contents I & D Stream I & D Stream I & D Stream
Access Time 2 Cycles 2 Cycles 3 Cycles
Fill Size Hexaword Hexaword Octaword
Write Buffers 2 Octaword 2 Octaword 4 Octaword
LOAD PATH DEV. TK50 TK70 TK70
ETHERNET DEV. DEBNA DEBNA DEBNI
CONSOLE DEV. LA100 VT320, LA75 VT320, LA75
LED READING Binary Binary Binary Coded Decimal
on=0, off=1 on=0, off=1 on=0, off=1
Table 3. VAX 6000-400 DOCUMENTATION SUMMARY
----------------------------------
Order no. Users Title
EK-640EA-IN Cust/FS VAX 6000-400 Installation Guide
EK-640EA-OM Cust/FS VAX 6000-400 Owner's Manual
EK-640EA-HR Cust/FS VAX 6000-400 Mini-Reference
EK-640EA-TM SMCust/FS VAX 6000-400 System Technical User's Guide
EK-640EA-MG SMCust/FS VAX 6000-400 Options and Maintenance
EK-640EA-TD FS(internal) VAX 6000-400 Proprietary Technical Reference
EK-640EA-UP FS VAX 6000 Series Upgrade Manual
EM01850-01 FS VAX 6000-400 Field Maintenance Print Set
MP01850-01 Cust VAX 6000-400 Customer Maint. Print Set
Documentation in languages other than english.
EK-640GA-IN Cust/FS VAX 6000--400 Installationsanleitung
EK-640SA-IN Cust/FS VAX 6000--400 Guia de instalacion
EK-640FA-IN Cust/FS VAX 6000--400 Guide d'installation
Table 4. VAX 6000-400 DIAGNOSTIC KITS
----------------------------
AQ-FK87A-ME Vax 6400 Console TK50
AQ-FK88A-DE Vax 6400 Complete Diag Set TK50
AV-FK90A-TE Vax 6400 Diag Release Notes
BB-FK89A-DE Vax 6400 Compl Diag Set 16MT9
Table 5. AREA CONTACTS FOR DIAGNOSTIC DISTRIBUTION
-----------------------------------------
US AREA A1 CONTACT DIRECT DTN NODE
CEA RLO CORINE PARRISH 312-640 421-5640 DDMAIL::PARRISH
CSC/AT IPO MARGARET WILSON 404-953-0959 435-2201 MARGARET WILSON@IPO
CSC/COL CXO FRANK MENDEZ 719-548 522-5587 NEXUS::MENDEZ
ECA OHF NANCY CONLEY 313-347 471-5721 NANCY CONLEY@OHF
IN-DEC MADDY VEGA 508-467 262-8274 SENIOR::VEGA
MAA PHH PAT KOZLOWSKI 215-283 328-4241 PAT KOZLOWSKI@PHH
NYA WAYNE WOLFRUM 201-884 332-3954 KYOA::WOLFRUM
NEA PEARL MAGIERA 508-441 288-6624 NERSW5::MAGIERA
SCA DLO CAROLYN DUERKSEN 214-702 483-4606 DPDMAI::DUERKSEN
SOA ATO KATHY JENKINS 404-257 351-2256 ODIXIE::KJENKINS
SWA PEGGIE ROSE-KOZO 714-261-4418 SWAM1::ROSE_KOZO
WEA SUSAN BROWN 408-496 521-3014 WR1FOR::BROWNSU
WRO PATTI PETERS 408-496 521-3021 JULIET::PETERS_PA
FEDERAL
SYSTEMS DER RICK TOMASZEWSKI 301-306 379-6615 TOMASZEWSKI@DER
GIA CONTACT FOR DIAGNOSTIC DISTRIBUTION
SUSAN DUGDALE 508-264 244-6736 AKOV12::DUGDALE
CXO LOIS SNOVER 719-548 522-5289 BSS::SNOVER
CXO SONNY NEWSON 719-548 522-5499 SONNY NEWSON@CXO
CXO JOHN ZINN 719-548 522-5014 JOHN ZINN@CXO
Table 6. VAX6000-400 DIAGNOSTIC PROGRAMS V1.0
Device
Diag Rev Level Diagnostic Title
ERSAA 12.0-339 VAX6000-400 Diagnostic Supervisor
ERKAX 0.5 3 VAX6000-400 Manual Tests
ERKMP 1.1 3 VAX6000-400 Multiprocessor Exerciser
DWBUA Macrodiagnostic
EVCBB 2.6 3 VAX DWBUA (BI to Unibus) Diagnostic
DMB32 Macrodiagnostics
EVAAA 10.0 2R VAX Printer Diagnostic
EVDAJ 3.0 2R DMB32 Online Asyn Port Test
EVDAK 4.0 3 DMB32 Standalone Funct Verif
EVDAL 4.0 2R DMB32 Online Sync Port Test
EVDAN 1.0 2R DMB32 Online Data Comm Test
DSB32 Macrodiagnostics
EVDAP 1.1 3 DSB32 Level 3 Diagnostic
EVDAPMIC
EVDAPTST
EVDAQ 1.0 2R DSB32 Level 2 Diagnostic
DHB32 Macrodiagnostics
EVDAR 1.4 3 DHB32 Functional Diagnostic
EVDAS 2.0 2R Async DMB32 Class Functional Diagnostic
DR11-W (Unibus) Diagnostics
EVDRB 5.0 2R VAX DR11-W Online Diag
EVDRE 5.0 3 VAX DR11-W Repair Level Diag
DRB32 Macrodiagnostics
EVDRH p3.1 3 DRB32-M,-E Functional Diagnostic
EVDRI 3.0 3 DRB32-W Functional Diagnostic
DUP11 MacroDiagnostics
EVDUP 2.0 3 DUP11 Repair Level Part 1
EVDUQ p3.0 3 DUP11 Repair Level Part 2
DEBNA Macrodiagnostics
EVDWC p3.1 2R VAX NI Exerciser
EVDYD 2.3 2R DEBNA Online Func Diag
CIBCA-AA and CIBCA-BA Macrodiagnostics
EVGAA 5.1 3 CIBCI,CIBCA Functional Diag - Part 1
EVGAB 5.1 3 CIBCI,CIBCA Functional Diag - Part 2
EVGDA 2.0 3 CIBCA EEPROM Prgm. & Update Utility
CIBCA-AA Macrodiagnostics
EVGCA 3.1 3 T1015 Repair Level Diag Part 1
EVGCB 2.3 3 T1015 Repair Level Diag Part 2
EVGCC 2.4 3 T1015 Repair Level Diag Part 3
EVGCD 3.2 3 T1015 Repair Level Diag Part 4
EVGCE 4.2 3 T1025 Repair Level Diag
CIBCA-BA Macrodiagnostics
EVGEE 1.2 3 CIBCA-BA Repair Level Diag Part 1
EVGEF 1.1 3 CIBCA-BA Repair Level Diag Part 2
EVGEG 1.3 3 CIBCA-BA Repair Level Diag Part 3
XMA Online Memory Diagnostic
EVKAM 10.0 2R VAX Memory User Mode Test
VAX CPU Cluster Exerciser
EVKAQ 3.0 2 VAX Basic Instructions Exerciser - Part 1
EVKAR 3.0 2 VAX Basic Instructions Exerciser - Part 2
EVKAS 3.0 2 VAX Floating Point Instr. Exer - Part 1
EVKAT 3.0 2 VAX Floating Point Instr. Exer - Part 2
EVKAU 3.0 3 VAX Privileged Arch. Instr. Test - Part 1
EVKAV 3.0 3 VAX Privileged Arch. Instr. Test - Part 2
DWBLA/TU81 Macrodiagnostics
EVMBA 6.0 2R VAX TU81 Data Reliability
EVMBB 4.0 3 VAX Front-end/Host Funct Diag
TBK50 Macrodiagnostics
EVMDA 2.1 2R TK50/TK70 Tape Exerciser
Table 6 Cont. VAX6000-400 DIAGNOSTIC PROGRAMS V1.0
Device
Diag Rev Level Diagnostic Title
KDB50 (BDA) Macrodiagnostics
EVRAE 3.0 2R VAX Genrc Mscp Disk Exerciser
EVRLB 7.1 3 VAX RA60/80/81 Formatter
EVRLF 9.2 3 UDA50/KDB50 Basic Subsys Diag
EVRLG 9.1 3 UDA50/KDB50 Disk Drive Exerciser
EVRLJ 2.0 3 VAX UDA50-A/KDB50 Sub Exe
EVRLK 3.1 3 VAX Bad Block Replace Utility
EVRLL 2.0 3 Disk Drive Internal Error Log Utility
RV20 Macrodiagnostics
EVRVA 2.0 3 RV20 Level 3 Functional Diagnostic
EVRVB 2.0 2R RV20 Level 2R Diagnostic
VAX Diagnostic Standalone Autosizer
EVSBA X6.7 3 VAX Diagnostic Standalone Autosizer
KA62A Rom-Based Diagnostics
ST0 V1.0 XRP VAX6000-400 Processor Selftest
ST1 V1.0 XMI VAX6000-400 Processor (XRP) CPU/MEM
ST2 V1.0 XBI ROM-Based Self-Test Diagnostic
ST3 V1.0 XMA ROM-Based Diagnostic
p=prelease version
NOTE
DIAGNOSTICS MAY BE COPIED FROM:
VOLKS::RIGEL$:<file_name>
beginning in July 1989 and ending February 1990.
Table 7. VAX6000-400 DIAGNOSTIC PROGRAM PROBLEMS/RESTRICTIONS at FRS.
-----------------------------------------------------------
1. After booting VDS from a TK70 or TK50 and then running the
auto-sizer (EVSBA), a wait of about 2 minutes will occur after
issuing any other command such as DIR, LOAD, etc. After this
time, you should see the led on the tape drive begin to blink
normally.
2. Intermittent autosizer (EVSBA) hang.
EVSBA will hang intermittently during the sizing of the
HSC's. This problem has been noticed in both the DEFAULT and
SELF section.
3. EVGAA fails in Test 1
EVGAA fails in Test 1 with an intermittent unexpected hard
error interrupt through SCB 60. An RER on and IDENT
transaction is occurring which is driving hard error. The
following error has been seen when running this test with
either a CIBCA-AA or CIBCA-BA in the system:
?? Unexpected trap or interrupt thru SCB vector 0060
PC at error: 0002A90C(X)
PSL at error: 00000004(X) ; CUR=KERNEL,PRV=KERNEL,IPL=00(X),Z
User return PC: 0000474B(X)
4. EVGAB fails intermittently when running infinite passes of all
tests with MM on.
EVGAB receives an unexpected hard error interrupt (similar
to EVGAA) when it executes with MM on. Like EVGAA, this test
fails because of a RER on IDENT transaction. This problem has
only been seen with MM on when running with a CIBCA-BA in the
system. The following error is reported:
.. Program: EVGAB - CI Functional Part II, revision 5.1, 12 tests,
at 07:01:16.56.
Testing: _PAA0
Event Flag 1 SET = Load CI MICROCODE
Event Flag 2 SET = Print Queue Entries
EEprom Revision = 0002 Functional Revision = 0004
?? Unexpected trap or interrupt thru SCB vector 0060
PC at error: 0000477E(X)
PSL at error: 00000005(X) ; CUR=KERNEL,PRV=KERNEL,IPL=00(X),Z,C
User return PC: 0000477E(X)
DS>
Table 7 Cont. VAX6000-400 Diagnostic Release Notes V1.1
-----------------------------------------
5. EVGEG fails in Test 22: Transmit with External Loopback Set
Test
EVGEG fails running multiple passes of Test 22 in QA mode.
******** EVGEG CIBCA Repair Level Diagnostic Part III - 1.3 ********
Pass 1, test 22, subtest 0, error 6, 1-JAN-1989 03:08:46.89
Hard error while testing PAA0: Detected Transmit Channel Error
Maintenance Status Field Register 7:[0000000B(X)]
; RCV_STATUS_ERROR,XMIT_ATTN,XMIT_STATUS_ERROR
Transmit Status:[00000001(X)] ; STATUS=0(X),XMTR_BUSY
Current Byte Count = 0FFC
PMCSR:[00000000(X)] ;
PSR:[00008400(X)] ; Nrspe,Unin
BIBER:[00000008(X)] ; Upe
******** End of Hard error number 6 ********
.. Aborted program at pass 1, test 22, subtest 0, PC 00009BF9.
6. EVDUQ fails Test 21.
EVDUQintermittently fails T21 when running multiple passes
(usually 50 or more passes). When it fails, it hangs the
system so the only way to restart is to reboot the system.
7. VDS "SET CPU" prolbem
In a mustiprocessor invironmetn, the VDS "SET CPU" command
will transfer control to an attached processor. Once there,
However, it will not allow you to examine GPRs of the attached
processot as well as certain I/O space.
8. EVDAP.A is a save-set of four EVDAP files.
The following four files make up the EVDAP.A save-set:
EVDAP.EXE, EVDAP.HLP, EVDAPTST.EXE, and EVDAPMIC.EXE. The
save-set must be BACKUP restored in order to get the executable
image to run.
Table 8. RSL
---
Part Description Qty Qty
Number Per Sys SD Kit
VAX 6000-400 UNIQUE Processor RSL
---------------------------------
T2015 CPU Module Scalar 1-6 1
T2017 CPU Module Vector 1-2 1 * avail q4fy90
Calypso COMMON RSL
------------------
XMI RSL
-------
54-18172-01 XMI Clock/Arbiter Mod. 1 1
70-24373-01 XMI Card Cage 1 0
XBI Adapter RSL
---------------
T1043 BI Adapter (XBIB) 2 1
T2012 BI Adapter (XBIA) 2 1
Memory RSL
----------
T2014-BA 32MB Memory Array (XMA) 1-4 1
Power Supply RSL
----------------
H405-E AC Input Box, 60Hz 3Ph * 1 0
H405-F AC Input Box, 50Hz 3Ph * 0 0
H7214-A +5V 600W Regulator 3 1
H7215-A +5V 200W Regulator 2 1
12-24701-06 Fan, H7206A 1 0
12-27848-01 Blower, 24V 2 0
54-16574-01 VAX8200 Console Sw Bd 1 1
20-29176-01 XTC Power Seq. Module 1 1
20-28997-01 TK50 Pwr Filter Module 1 0
H7206-A PAL BOX 1 1
* The H405-E/F are being modified and a new revision will be out shortly.
Battery Back-up Option RSL
--------------------------
H7231-N Battery Back-up Option 1 0
BI Card Cage RSL
----------------
H9400-AA BI Card Cage, 6 slots 2 0
17-01038-01 FBE Cable 1 0
20-24486-01 Term, BI Near End 1 0
20-24487-01 Term, BI Far End 1 0
TK70 RSL
--------
TK70-AX Tape Drive 1 0
T1035-00 TBK70 Modules 1 0
Table 8. Cont. RSL
Part Description Qty Qty
Number Per Sys SD Kit
-------------------------------------------------------------------
Miscellaneous Parts
-------------------
12-11255-18 Air Filter 1 0
12-17119-01 Key, Plastic 2 0
12-19245-00 Battery, TOY 3-Cell 1 0
12-24023-01 ESD Cable w/Wrist Strap 1 0
12-25024-11 Air Flow Ass'y 1 0
12-26339-01 Key, Cabinet Door 2 0
16-28393-01 Transformer,(50HZ Only) 1 0
17-01844-01 Temp Sensor Ass'y 1 0
Cables
------
17-00849-08 Cable, BI#1 BKPLN - BI#2 BKPLN 1 0
17-01446-01 Cable, H7206A/J04 - XMI PS Bulk 1 0
17-01447-01 Cable, H7206A/J03 - BI PS Bulk 1 0
17-01496-01 Cable, Ethernet, BI - Bulkhd 1 0
17-01497-02 Cable, XMI PS's - H7206A/J14 1 0
17-01498-01 Cable, XTC/J03 - H7206A/J16 1 0
17-01501-01 Cable, H405/J02 - H7206A 1 0
17-01523-01 Cable, DC, BI - H7215/J03 1 0
17-01525-01 Cable, Voltage Sense (Bus bars) 2 0
17-01549-01 Cable, H405/J01 - H7206A/J13 1 0
17-01566-01 Cable, DC, H7215/J03 - XMI 1 0
17-01567-01 Cable, XTC/J5 - Console Term. Port 1 0
17-01568-02 Cable, XTC/J4 - XMI Backplane/J6 1 0
17-01569-01 Cable, H7206A/J11 - BI#1 BKPLN 1 0
17-01570-01 Cable, H7206A/J02 - Blowers 1 0
17-01666-01 Cable, BI PS's - H7206A/J09 1 0
17-01814-01 Cable, Cntrl Box Bulkhd (TK50) - BI 1 0
17-01816-01 Cable, XTC/J2 - Cntrl Box Bulkhd (SW) 1 0
17-01817-01 Cable, TK50 - Cntrl Box Bulkhd 1 0
17-01818-01 Cable, Cnsl Sw Bd - Cntrl Box Bulkhd 1 0
17-01897-01 Cable, IBUS Harness 180" 2 0
17-01897-02 Cable, IBUS Harness 7" 2 0
17-01897-03 Cable, IBUS Harness 25" 2 0
( H7231N Option Cables )
17-00962-01 Cable, H7206A/J12 - H7231N/J18 1 0
17-01833-01 Cable, H405/J06&J07 - H7231N/J20 1 0
70-20396-2F Cable, H7206A/J06 - H7231N/J09 1 0
| |||||
| 17.5 | KERNEL::MOUNTFORD | Thu Jul 13 1989 16:29 | 3772 | ||
Hello all ,
Some information about a new product announcement coming
shortly
Frank
Attached is the most up to date information I have on the Hyperion
(VAX 6300) systems.
This product will be announced on January 10th 1989.
Complimenting this announcement are the following other announcements:
o Announcing the TA90 Tape subsystem
o Announcing the SA550 Storage Array
o Announcing the RV64 Optical Jukebox System
o Announcing the HSC40 Storage Controller
o Announcing the HSC5X-DA data channel
o Announcing VAX Performance Advisor V2.0
Articles on all of these will follow over the next few days.
Best Regards,
Tony.
****************************************************************
* *
* DISTRIBUTION *
* *
* This document contains Company Confidential information *
* on VAX 6300 Series. CTS should take care with Distribution *
* to non-DEC persons as information in this document is *
* constantly being updated. Whilst trying to ensure that all *
* the information contained within is correct we take no *
* responsibility for inadvertant errors. *
* *
****************************************************************
Compiled by : Tony Adair - @AYO
DTN 823-3149
ENET: EAYV01::ADAIR
December 1988 Rev 1.2
[1m REVISION HISTORY [0m
December 1st 1988 Rev 1.0 created.
December 2nd 1988(Rev 1.1) Changed Menus format to Standard type.
December 14th 1989(Rev 1.2) Corrected errors within last Rev namely TK50
references and reference to VAX 6200. Added
new upgrade part numbers for Ultrix,ELN and
fileservers. Changed VMS part from QA-001AA-H5
to QA-001AC-H5.
[1m TABLE OF CONTENTS i [0m
Page
1 PRODUCT DESCRIPTION . . . . . . . . . . . . . . . . 1
1.1 VAX 6300 Series Relative Performance Chart . . . . 2
2 VAX 6300 SYSTEM ARCHITECTURE OVERVIEW . . . . . . . 3
2.1 Processor Nodes . . . . . . . . . . . . . . . . . 3
2.2 I/O Nodes . . . . . . . . . . . . . . . . . . . . 3
2.3 Memory Nodes . . . . . . . . . . . . . . . . . . . 3
3 VAX 6300 PRODUCT DESCRIPTION . . . . . . . . . . . 4
3.1 VAX 6300 System Components . . . . . . . . . . . . 4
3.1.1 VAX 6300 System Block Diagram . . . . . . . . . . 5
3.2 KA62B CPU . . . . . . . . . . . . . . . . . . . . 6
3.2.1 MS62A Memory . . . . . . . . . . . . . . . . . . . 8
3.3 XMI Bus . . . . . . . . . . . . . . . . . . . . . 9
3.3.1 14 Slot XMI Backplane . . . . . . . . . . . . . 10
3.4 VAXBI Bus/H9400 Card Cage . . . . . . . . . . . . 11
3.4.1 6 Slot VAXBI Backplane . . . . . . . . . . . . . 11
3.5 DEBNA VAXBI Ethernet Adapter . . . . . . . . . . . 12
3.6 TK70 Tape Drive . . . . . . . . . . . . . . . . . 12
3.7 H7231-N Battery Backup Unit . . . . . . . . . . . 12
3.8 Software . . . . . . . . . . . . . . . . . . . . . 12
3.9 Supported Boot Devices . . . . . . . . . . . . . . 12
3.10 CI Boot . . . . . . . . . . . . . . . . . . . . 12
4. Customer Installability And Customer Upgrades . . 13
5. VAXBI NODE ID ASSIGNMENT . . . . . . . . . . . . . . 14
5.1 Dual VAXBI Channel System Node ID Assignment . . . 14
6 CONFIGURATION RULES . . . . . . . . . . . . . . . . 15
6.1 XMI Configuration Rules . . . . . . . . . . . . . 15
6.1.1 KA62B . . . . . . . . . . . . . . . . . . . . . 15
6.1.2 MS62A . . . . . . . . . . . . . . . . . . . . . 15
6.1.3 XMI Backplane . . . . . . . . . . . . . . . . . 15
6.1.4 DWMBA/BI Expansion . . . . . . . . . . . . . . . 16
6.1.5 Miscellaneous . . . . . . . . . . . . . . . . . 16
6.2 VAXBI Configuration Rules . . . . . . . . . . . . 17
6.2.1 DWMUA . . . . . . . . . . . . . . . . . . . . . 18
6.2.2 DEBNA . . . . . . . . . . . . . . . . . . . . . 19
6.2.3 CIBCA . . . . . . . . . . . . . . . . . . . . . 19
6.2.4 TBK70 . . . . . . . . . . . . . . . . . . . . . 20
6.2.5 H7231-N Battery Backup Unit. . . . . . . . . . . 20
6.2.6 DMB32/DHB32 . . . . . . . . . . . . . . . . . . 20
6.2.7 KLESI/TU81E . . . . . . . . . . . . . . . . . . 20
6.2.8 DRB32 . . . . . . . . . . . . . . . . . . . . . 21
6.2.9 KDB50 . . . . . . . . . . . . . . . . . . . . . 21
}[1m TABLE OF CONTENTS ii[0m
7 PANEL SPACE SPECIFICATIONS . . . . . . . . . . . . 22
7.1 Panel Space And VAXBI Slot Usage By VAXBI Options 22
7.2 System IO Panel Space Availability . . . . . . . 23
7.2.1 VAX 6300 Kernel Cabinet . . . . . . . . . . . 23
8 DC POWER SPECIFICATIONS . . . . . . . . . . . . . 24
8.1 VAX 6300 Series System DC Power Capacity . . . . 24
8.1.1 XMI Option DC Power Specifications . . . . . . . 25
8.2 VAXBI Option DC Power Specifications . . . . . . 25
8.3 VAX 6300 Series System AC/Thermal Specs . . . . 25
8.4 VAX 6300 Series System Physical Sizes . . . . . 26
8.5 VAX 6300 Series System Environmental Requirements 26
9. VAXBI EXPANDER CABINET . . . . . . . . . . . . . . 27
9.1 Technical Description . . . . . . . . . . . . . 27
9.2 Cabinet Description . . . . . . . . . . . . . . 27
9.3 Cabinet Internal Dimensions . . . . . . . . . . 27
9.4 Cabinet View (Front View) . . . . . . . . . . . 28
9.5 Cabinet View (Distribution Inserts). . . . . . . 29
9.6 SPECIFICATIONS . . . . . . . . . . . . . . . . . . 30,31
10. SYSTEM BUILDING BLOCKS . . . . . . . . . . . . . . 32
10.1 Generic Format . . . . . . . . . . . . . . . . . 32
SYSTEM BUILDING BLOCK MENUS
System Building Block Menus. . . . . . . . . . . . 33-
CPU Upgrades with US equivalents . . . . . . . . .
[1mPage 1[0m
[1m 1 Product Description [0m
The VAX 6300 Series are follow-on products to the highly successful
VAX 6200 Series which was announced April 1988. The VAX 6300 Series
doubles the performance of the VAX 6200 Series from 11 to 22 VUPs.
This is accomplished by supporting up to six processors, each with a
33% performance improvement over the VAX 6200 CPUs. The VAX 6200
Series span the range from 2.8 to 11 x 11/780, whereas the VAX 6300
Series range from 3.8 to 22 x 11/780.
The VAX 6300 processor board differs from the VAX 6200 in two ways:
The VAX 6300 utilizes the faster CMOS II technology on its CVAX CPU
and CFPA; the VAX 6200 implements CMOS I technology. Secondly, the
VAX 6300 has a 60ns clock versus the 80ns clock used in the VAX 6200.
On a systems level, the VAX 6300 Series is identical to the VAX 6200
Series with the following exceptions: The VAX 6300 includes a TK70
console tape and the new TBK70 controller, versus the TK50 which is
embedded in all VAX 6200 systems.
The VAXFileserver 6300 is being offered in several new
configurations.
VAXFileserver 6300 systems include additional software
licenses tailored to worksystem environments.
It should be noted that every VAX 6200 system configuration has been
duplicated with an equivalent VAX 6300 system in order to facilitate
backlog conversions.
[1mPage 2 [0m
[1m1.1 VAX 6300 SERIES RELATIVE PERFORMANCE CHART* [0m
+-----------------------------------------------------------
|
|
|-----------------------------------------------------+
| | VAX 6360
|-----------------------------------------------------+
|
|-------------------------------------------+
| | VAX 6350
|-------------------------------------------+
|
|---------------------------------+
| | VAX 6340
|---------------------------------+
|
|-----------------------+
| | VAX 6330
|-----------------------+
|
|---------------+
| | VAX 6320
|---------------+
|
|-------+
| | VAX 6310
|-------+
|
+--------|---------|---------|---------|---------|---------|
0 4 8 12 16 20 24
CPU Performance
* The VAX-11/780 equals one unit of performance on this chart.
[1mPage 3[0m
}[1m2 VAX 6300 System Architecture Overview [0m
The VAX 6300 system consists of a number of single module functional units
which communicate over a high speed system bus called the XMI. Memory
is a global resource equally accessible by any node on the bus. There can
be multiple CPUs on the XMI all of which run totally independent of each
other but share one common physical memory and I/O address space. Cache
coherency is fully maintained by hardware.
The smallest addressable unit of data is one byte, and the XMI has 30
address bits. XMI address space is divided into 2 halves by bit 29 of the
address. When bit 29=0 an address is said to fall into memory space. When
bit 29=1 the address is said to fall within I/O space. This matches the
maximum physical address as defined by the VAX architecture and allows
up to 256MB of physical memory to be addressed. The XMI architecturally
allows up to 16 nodes but is physically constrained to 14 nodes.
There are currently 3 different types of XMI nodes which exhibit the
following characteristics:
}[1m2.1 Processor Nodes [0m
Processor nodes contain a CPU which executes instructions and manipulates
data contained in XMI memory. The processor node can execute any
instruction set compatible with the VAX style byte addressing and
memory locking mechanisms. A processor node will most likely have a cache
which must force all write data back to main memory. Any cached processor
module must also monitor write traffic on the XMI and invalidate any
location in its own cache which is written into main memory. Processor
nodes must also be capable of responding to interrupt requests generated
either by other processors or by I/O nodes.
}[1m2.2 I/O Nodes [0m
I/O nodes generally respond to I/O space references by either mapping
the data onto another bus or by interpreting data as a command. I/O
nodes can also become a commander on the XMI and access global XMI
memory. I/O nodes may generate interrupt sequences directed toward
processor nodes. I/O nodes do not respond to commands directed toward
memory space.
}[1m2.3 Memory Nodes [0m
Memory nodes act only as responders on the XMI. They respond to read and
write requests directed toward memory address space, which are generated
either by processor or I/O nodes. There is one memory module under
development which may be configured for 32MB of ECC protected memory.
[1mPage 4[0m
}[1m3 VAX6300 Product Description [0m
The VAX 6300 is a general-purpose computer system based on the KA62B
processor module which use the XMI Bus as a processor/memory and I/O
Sub-system Bus. The I/O sub-system bus used on the VAX 6300 will be one
or more VAXBI buses. The VAX 6300 is designed to support multi-processing
of up to six KA62B processors.
The VAX 6300 system will be based on a kernel configuration that offers
1 or 2 VAXBI channels, an Ethernet device, a TK series tape drive, a single
KA62B processor and 32MB of memory in a 60" high cabinet with power
system.
The VAX 6300 series of products is an improved performance replacement to
the current 6200 series products.
Like other VAX systems, the VAX 6300 can support many users in a time-
sharing environment, as well as numerous peripheral devices.
The VAX 6300:
o Uses the KA62B processor
o Executes the full VAX instruction set
o Uses as its system bus the XMI bus, a high-bandwidth bus designed
for multi-processing
o Allows for memory expansion
o Provides VAXBI adapters to connect VAXBI peripheral devices
o Has an extensive self-test that runs automatically
The VAX 6300 series systems are basically identical except for the number of
KA62B processors. The third position in the product identifier number
denotes the number of processors. EX: VAX 6310 has 1 CPU, a VAX 6340 has 4.
[1m3.1 VAX 6300 System Components[0m
o KA62B CPU processor module(s)
o MS62A 32MB memory module(s)
o TK70 Tape drive
o Input/output controllers
o Adapters for other buses
o Power supplies and cooling blower(s)
[1mPage 5[0m
[1m3.1.1 VAX 6300 SYSTEM BLOCK DIAGRAM [0m
.............
: :
............. :
: : :
............. :.: .............
: : : : :
............. :.: ............. :
: : : : : :
............ :.: ............ :.:
: : : : : :
+-----------+ :.: +-----------+ :.:
| | : | | :
| Processor |.: | Memory |.:
| (1 to 6) | | |
+-----------+ +-----------+
/\ /\
| |
| |
/____________________\/__________________\/________________________\
< 100 MB/s High-performance System Interconnect
>
\------------------------------------------------------------------/
/\ /\
| |
| |
| |
\/ \/
/...........................\ /............................\
\ / \ /
/............................\ /............................\
\ / \ /
/____________________________\ /____________________________\
< 10 MB/s VAXBI Bus > < 10 MB/s VAXBI Bus >
\----------------------------/ \----------------------------/
/\ /\ /\ /\ /\ /\
| | | | | |
| | | | | |
\/ \/ \/ \/ \/ \/
....... ....... ....... ....... ........ .........
: : : : : : : : : : : :
+------+: +------+: +------+: +------+: +-------+: +--------+:
|Ether-| |Local | |DSA | |DSA | |VAX- | |Parallel|
|net | |Comm. | |Tapes | |Disks | |cluster| |Port |
+______+ +______+ +______+ +______+ +_______+ +________+
[1mPage 6[0m
}[1m3.2 KA62B CPU[0m
The processor on the KA62B implements the VAX base instruction set,and
the Packed Decimal and H-Floating are emulated by the operating system,
except that PDP-11 compatibility mode is not supported by hardware or
microcode.
The KA62B is a one-board processor that will form the basis of the initial
series of systems. It is based on the CVAX chip set developed by HLO and
is expected to provide 3.8 X 780 performance. In a VAX 6300 system the
KA62B communicates with main memory over on the XMI bus. VAXBI I/O devices
are accessed over the XMI through an XMI-to-VAXBI adapter (DWMBA).
The CVAX chip set implements a 32-bit, virtual memory microprocessor
conforming to the VAX architecture. The chip set consists of the CVAX
CPU single chip microprocessor, the CVAX FPA floating point processor and
the MicroVAX SSC system support chip. This custom chip set combined with
a high-density (>20K gates) "SEA-OF-GATES" gate array implement the
following functionality:
A VAX central processor that supports the MicroVAX chip subset of the VAX
instruction set and data types, as well as full VAX memory management with
demand paging and 4GB of virtual memory.
A floating point accelerator with the MicroVAX chip subset of the VAX
floating point instruction set and data types.
A VAX-compatible console.
Full power-up self-testing.
Booting from all supported VAXBI devices.
A VAX standard Time Of Year (TOY) clock with battery back-up (power is
provided by the XMI TOY BBU PWR pin).
An interval timer with 10Ms interrupts.
Two programmable timers, similar in function to the VAX standard interval
timer.
An octaword write buffer that decreases bus and memory controller
bandwidth needs by packing writes into larger (and therefore more
efficient) blocks prior to sending them to main memory.
Hexword cache fill logic that loads the second-level cache with eight
longwords of data on each cache miss.
XMI write monitoring logic that uses a duplicate tag store to efficiently
flag write addresses that must be invalidated in the second-level cache.
Full set of error recovery and logging capabilities as defined by the XMI
specification.
[1mPage 7[0m
The KA62B CPU module contains a CVAX central processor chip, a CFPA
chip, an SSC, a Second-level cache and an XMI interface. The SSC
(System Support Chip) contains a serial line interface that serves as
console, and a ROM interface to support self-test, console, and boot
functions. The SSC also contains a time of year clock and an interval
timer.
The XMI interface consists of the XMI corner components ( an XCLOCK and
seven XLATCHes) and a single gate array (LSI Logic 223-pin Compacted
Array). The gate array provides the complete interface between the CVAX
DAL ("CDAL") and the XCI (the user side of the XMI corner).
[1mPage 8 [0m
}[1m3.2.1 MS62A Memory [0m
VAX 6300 memory is all located in XMI address space. Each XMI memory
node consists of the memory array(s), and the controller for the array(s).
Each MS62A memory node is a single XMI module.
Option Description
------ -----------
MS62A-AB 32MB memory
[1m Page 9[0m
}[1m 3.3 XMI Bus [0m
The XMI Bus is a 64-bit synchronous bus. Events occur on the XMI bus at
fixed 64-nanoseconds bus cycles.The raw bandwidth of the XMI
at 64 ns is 125Mbyte/Second. The usable bandwidth, which depends on the
transaction length is listed below.
The XMI will be implemented using VAXBI connector technology using 180
backplane pins for XMI signals, clock signals and power distribution.
120 pins will be available to XMI modules for external communications.
Interconnection of backplanes to form a longer XMI is not possible because
the backplane lines are terminated at each end.
Using the same connector technology as the VAXBI backplane, the XMI bus
itself is physically run across the A, B and C segments of the backplane
connector. The D and E segments are reserved for option I/O in all but 4
slots of the backplane. Slots 6-9 in the 14 slot backplane do not have I/O
pins because the clock and arbitration system is physically mounted
on the back of the backplane in the area of the D and E connectors.
Currently the DWMBA is the only XMI option that utilizes the I/O pins.
All XMI modules have a node identification which is used to determine
their I/O space CSR addresses as well as to identify the commander that
generates any XMI transaction. Each XMI module determines its node ID
by sensing the state of 4 backplane pins that are unique in each slot.
The XMI backplane has been designed such that the slot number is the same
as the node ID. Using this scheme XMI node numbers start from 1 at the
right side of the cardcage as viewed from the module insertion side of the
cardcage.
TRANSACTION TYPE MBYTES/SECOND
---------------- -------------
LONGWORD READ 31.25
LONGWORD WRITE 31.25
QUADWORD READ 62.50
QUADWORD WRITE 62.50
OCTAWORD READ 83.30
OCTAWORD WRITE 83.30
HEXWORD READ 100.00
[1m Page 10 [0m
[1m 3.3.1 14 Slot XMI Backplane[0m
-+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- ------
| | | | | | | | | | | | | | |
A | | | | | | | | | | | | | | | A
| S | S | S | S | S | S | S | S | S | S | S | S | S | S |
-| L | L | L | L | L | L | L | L | L | L | L | L | L | L |-
| O | O | O | O | O | O | O | O | O | O | O | O | O | O | X
B | T | T | T | T | T | T | T | T | T | T | T | T | T | T | B M
| | | | | | | | | | | | | | | I
-| a | a | a | a | a | a | a | a | a | a | a | a | a | a |-
| n | n | n | n | n | n | n | n | n | n | n | n | n | n |
C | d | d | d | d | d | d | d | d | d | d | d | d | d | d | C
| | | | | | | | | | | | | | |
-| N | N | N | N | N | N | N | N | N | N | N | N | N | N |- ------
| O | O | O | O | O | O | O | O | O | O | O | O | O | O |
D | D | D | D | D | D | D | D | D | D | D | D | D | D | D | D
| E | E | E | E | E | E | E | E | E | E | E | E | E | E | I
-| | | | | | | | | | | | | | |- /
| # | # | # | # | # | # | # | # | # | # | # | # | # | # | O
E | | | | | | | | | | | | | | | E
| 14| 13| 12| 11| 10| 9 | 8 | 7 | 6 | 5 | 4 | 3 | 2 | 1 |
-+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- ------
^ ^ ^ ^
| | | |
-------------
^
No I/O pins in these slots
14 Slot XMI Backplane (Module Side)
[1m Page 11[0m
}[1m 3.4 VAXBI Bus/H9400 Card Cage[0m
The VAXBI Bus is a 32-bit synchronous bus. Events occur on the VAXBI bus at
fixed 200-nanosecond intervals. The maximum data transfer rate, as
implemented by the BIIC, is 13.3 Mbytes per second for 16-byte transfers.
The H9400 card cage has the capacity for 6 VAXBI modules. When installing
the I/O transition header the mounting screws must be torqued to 6 inch
pounds +/- 1.
VAXBI 6 Slot Backplane
-+---+---+---+---+---+---+-
| | | | | | |
A | | | | | | | A
| S | S | S | S | S | S |
-| L | L | L | L | L | L |- B
| O | O | O | O | O | O | I
B | T | T | T | T | T | T | B
| | | | | | |
-| a | a | a | a | a | a |- ------
| n | n | n | n | n | n |
C | d | d | d | d | d | d | C
| | | | | | |
-| N | N | N | N | N | N |-
| O | O | O | O | O | O | I
D | D | D | D | D | D | D | D /
| E | E | E | E | E | E | O
-| | | | | | |-
| # | # | # | # | # | # |
E | | | | | | | E
| 6 | 5 | 4 | 3 | 2 | 1 |
-+---+---+---+---+---+---+- ------
6 Slot VAXBI Backplane (Module Side)
[1m Page 12[0m
[1m 3.5 DEBNA VAXBI Ethernet Adapter[0m
The Ethernet device for all VAX 6300 systems is the DEBNA-M, which supports
one Ethernet port and has up to 5M-bits per second of peak hardware
throughput capability.
[1m 3.6 TK70 Tape Drive[0m
The console load device for all VAX 6300 systems is the TK70, which is
a 5.25" 296MB streaming tape drive connected to the processor/memory via the
VAXBI TBK70 tape controller. The TK70 data rate is 125Kbytes/second with an
access time from insertion of a cartridge of 1 minute (min) to 35 minutes
(max).
}[1m 3.7 H7231-N Battery Backup Unit[0m
The optional battery backup unit (BBU) supplies 200 watts of power to
system memory and to the cooling blower for ONLY 10 minutes during a power
failure. With a BBU, the computer can restart the operating system at the
point where power failed, if power returns within 10 minutes. This
will allow up to eight 16MB array cards or eight 32MB array cards to be
backed up. If the memory limits are exceeded the H7231 will shut down to
avoid damage. The Battery light on the control panel indicates the
status of the unit. Without battery backup, the computer reboots the
operating system after a power failure.
The BBU supplies +300v (nominal) power to the power supply when the AC
line voltage drops.
}[1m 3.8 Software[0m
Any application software that runs on any VAX should run on a VAX 6300 with
the following exceptions:
o VAX 6300 does not support compatibility mode, in hardware or in
microcode.
o There are numerous minute differences between the VAX 6300 and
other VAXes, in areas that are not architecturally specified in
the VAX SRM. Examples are: accessing I/O space, machine check
details, and some Internal Processor Registers. The differences
are defined in the KA62B Technical Manual.
o Some I/O devices will not be supported on VAX 6300, including
all MASSBUS and Q-bus devices.
o Only a few Unibus devices will be supported
o Only VMS support is required of the Unibus devices. Engineering
will not support Unibus on ULTRIX or ELN systems.
}[1m 3.9 Supported Boot Devices[0m
Boot ROM programs are available for the following standard disks. This is
a partial list. More boot programs are expected.
o RAxxx, connected via KDB50.
o RAxxx, connected via CI Interface.
o TK70 (Console Load Device)
o DEBNA (supported by VAXeln only)
While you can boot from an RA60 ,it can not be the system device on
systems with 128MB or more of memory.
[1m 3.10 CI Boot[0m
When booting through the CIBCA-A,the microcode is loaded from the TK70 into
the CIBCA-A. When booting through a CIBCA-B, microcode loading is not
required. The console code is adaptive for either a CIBCA-A or CIBCA-B.
[1mPage 13[0m
}[1m 4 Customer Installability And Customer Upgrades[0m
The VAX 6300 systems are not customer installable.
The XMI and VAXBI module mechanical strategy makes customer replacement and
addition of modules relatively easy. Significant features include:
o XMI and VAXBI Modules do not have attached cables. All I/O cables
connect to modules through the XMI and VAXBI backplane.
o XMI and VAXBI modules do not have DIP switches or other
mechanical adjustments.
o Unused module slots may be empty -- no bus grant modules are
needed and no filler modules are needed for cooling.
o Adding a module does not require changing the backplane (although
I/O cables must usually be added).
o A new module may be installed in any empty backplane slot.
There is no relationship between physical location and
performance.
o Self-test will help the customer in all phases of maintaining the
system.
[1m Page 14[0m
}[1m 5 VAXBI NODE ID ASSIGNMENT [0m
Node ID assignments are made primarily to ensure that the VAX 6300 systems
are assembled and configured in a consistent manner. The node ID placements
can be moved in the field without affecting system operation as long as
none of the configuration rules are violated.
}[1m 5.1 Dual VAXBI Channel System Node ID Assignment[0m
(REAR) (REAR)
H9400-AF BI # 0 H9400-AF BI # 1
|-------------------------------------| |-------------------------------------|
||----| |----|| ||----| |----||
||9 | | 9|| ||9 | | 9||
||6 | | 6|| ||6 | | 6||
||6 +--+ +--+ +--+ +--+ +--+ +--+ 6|| ||6 +--+ +--+ +--+ +--+ +--+ +--+ 6||
||- |1 | |2 | |3 | |4 | |5 | |6 | -|| ||- |1 | |2 | |3 | |4 | |5 | |6 | -||
||B +--+ +--+ +--+ +--+ +--+ +--+ A|| ||B +--+ +--+ +--+ +--+ +--+ +--+ A||
||----| |----|| ||----| |----||
| 1 2 1 2 1 2 1 2 1 2 1 2 | | 1 2 1 2 1 2 1 2 1 2 1 2 |
| ||---||---||---||---||---||---|| | | ||---||---||---||---||---||---|| |
| || | || | || | || | || | || | || | | || | || | || | || | || | || | || |
| C || | || | || | || | || | || | || | | C || | || | || | || | || | || | || |
| || | || | || | || | || | || | || | | || | || | || | || | || | || | || |
| ||---||---||---||---||---||---|| | | ||---||---||---||---||---||---|| |
| || | || | || | || | || | || | || | | || | || | || | || | || | || | || |
| D || | || | || | || | || | || | || | | D || | || | || | || | || | || | || |
| || | || | || | || | || | || | || | | || | || | || | || | || | || | || |
| ||---||---||---||---||---||---|| | | ||---||---||---||---||---||---|| |
| || | || | || | || | || | || | || | | || | || | || | || | || | || | || |
| E || | || | || | || | || | || | || | | E || | || | || | || | || | || | || |
| || | || | || | || | || | || | || | | || | || | || | || | || | || | || |
| ||---||---||---||---||---||---|| | | ||---||---||---||---||---||---|| |
| K2 K2 K2 K2 K2 K2 | | K3 K3 K3 K3 K3 K3 |
| J1 J2 J3 J4 J5 J6 | | J1 J2 J3 J4 J5 J6 |
|-------------------------------------| |-------------------------------------|
[1mPage 15[0m
[1m 6 CONFIGURATION RULES[0m
[1m 6.1 XMI Configuration Rules[0m
[1m 6.1.1 KA62B[0m
A) The first KA62B processor must go in K1J1 to ensure that
the XMI bus is properly defaulted during IDLE cycles. The
total number of KA62B's limited to 6 and is dependent
on the total number of MS62A's and DWMBA's in the
configuration.
B) Requires 1 XMI slot, no IO panel
[1m 6.1.2 MS62A[0m
A) Maximum of 8 MS62A-AB's per system.
B) Memory comes standard in all systems. The MS62A-AB contains
32MB on one XMI module.
C) The MS62A memory can be configured into slots K1J2/K1J13
and is dependent on the number of KA62B's and DWMBA's
in the configuration.
D) MS62A's cannot be configured in the end slots of the
XMI backplane. An MS62A configured in an end slot will
attempt to default the XMI as soon as the +5B is up. This
configuration rule goes along with the backplane change
which tied the XMI HOLD L pullup to the +5B.
E) The number of MS62A's can be either be odd or even because
the console automatically interleaves memory. It is
preferred that memories be 1, 2, 4, 6 or 8 to ensure system
performance qualities.
F) VAX 6350 and VAX 6360 systems can only have a maximum of
six memory boards due to XMI slots.
[1m6.1.3 XMI BACKPLANE[0m
A) XMI slots K1J6 thru K1J9 are strictly KA62B and MS62A
expansion slots, they cannot be used for XMI IO adapters.
The reason for this being the XMI Arbiter (daughter)
module attaches to the backplane from the backside covering
zones D and E where IO cable would connect to the XMI.
B) "Any XMI module that ties XCLOCKEN to +5B" or "any XMI
module that powers its XLATCHes on +5v" cannot be
configured in an end slot of the XMI backplane.
C) NO VAXBI modules can be configured into the XMI backplane,
BI modules plugged into and powered up in the XMI backplane
will have a disastrous result.
D) The XMI card cage K1 is number right to left J1-J14 facing
the front of the CPU cabinet.
[1m Page 16[0m
[1m 6.1.4 DWMBA/BI Expansion[0m
A) 2 BI channels are standard on every system.
B) Maximum of 6 BI channels is allowed per system.
In the VAX 6350 and VAX 6360 the maximum amount
allowed is 4 BI channels due to XMI slots.
C) All add-on BI channels have 5 usable slots.
D) DWMBA's can not be placed in slots K1J5 or K1J10 because
Self-Test will not pass if a DWMBA is placed in either of
these slots.
E) The XMI bus can support up to a maximum of 8 DWMBA's IO
adapters however electricaly only 6 can be used.
F) The DWMBA can be placed in slots K1J1/K1J4 and K1J11/K1J14
G) A maximum of 1 DWMBA-BA/BB (expansion cabinets) are allowed
per system.
H) A maximum of 3 DWMBA-CA's per DWMBA-BA/BB except for the
VAX 6350 and VAX 6360 which can only have 1.
I) The first DWMBA adapter must be configured into K1J14.
The total number of DWMBA's limited to 6 and dependent on
the number of KA62B's and MS62A's in the configuration.
J) The first DWMBA is located in slot K1J14 of the XMI
backplane and connects to K2J1, the first VAXBI channel.
K) The second DWMBA is located in the next slot K1J13 and
connects to K3J1, the second VAXBI channel.
[1m 6.1.5 Miscellaneous[0m
A) The console will connect to the CPU cabinet to it's own
specific I/O slot.
B) The console will only turn on the DWMBA B-Buffer control
when the following conditions exist on a BI channel.
1) The hardware device rev in the XDEV Reg. of the
XBIA is 2 <rev B) or greater.
2) The hardware device rev in the BI device reg. of
the XBIB is )A (hex) or greater (rev J).
3) There is no DWBUA on that channel.
C) The console cable used must be 25' in order to maintain EMI
compliancy.
[1mPage 17 [0m
[1m 6.2 VAXBI Configuration Rules[0m
General Rules
A) The NODE ID's are installed in VAXBI cages K2 and K3 and are
numbered 1 through 6.
B) All multi-module VAXBI options are configured so that the module
connected to the Node ID goes to the right of the other modules
contained in the option.
C) All VAXBI modules of a multi-module option must be placed in
contiguous slots without crossing cage boundaries per VAXBI
architectural rules.
[1m Page 18[0m
[1m 6.2.1 DWMUA [0m
A) Maximum 1 DWMUA per system.
B) NO other BI devices allowed on the same BI as the DWBUA.
B) Requires 1 BI slot, no IO panel.
C) Maximum 1 H9652-xx per system configuration.
D) Maximum 2 BA11-AW/AX per DWBUA-CA and a maximum of
2 DD11-DK 9-slot Unibus backplanes per BA11-AW/AX.
E) When a DWBUA is added to a system, the total number of
KA62B's and DWMBA's must be 5 or less. This means that the
DWBUA can only be supported on single and dual processor
systems.
F) Only the following Unibus devices would be supported:
DUP11 Max 3 per system
DR11-W Max 4 per system
LP11 Max 4 per system
G) Any Unibus device with a Slave Synch timeout value less
than 80 usecs may fail if the device driver uses byte
offset or auto purge.
Any Unibus device that has a Slave Synch timeout value less
than 40 usecs may fail even if the device driver does not
use byte offset or auto purge.
H) A VAXBI expansion cabinet (DWMBA-BB) is not allowed on
a system that has a DWMUA
I) Any Unibus device which depends on the historical VAX
architectural requirement that byte and word references
of read-modify-write type (.mb or .mw access type) will
be implemented by a sequence of DATIP-DATO (B) may fail,
since the KA62B will produce a non-interlocked sequence
of a DATI followed by a DATO or DATOB.
[1m Page 19[0m
[1m 6.2.2 DEBNA[0m
A) Maximum 4 per system and limited to a maximum of 2 per BI
channel.
B) Requires 1 BI slot, IO panel is single. Cab kit for the CPU
cabinet is CK-DEBNA-LD and for the BI Expander cabinet it
is CK-DEBNA-LJ.
C) One standard in every system and it always goes in the CPU
cabinet in slot K3J6 and the IO panel always goes in
its own location.
Additional DEBNA's must be placed in a Quad sized hole.
D) There are only 3 +13.5v pigtails in the CPU cabinet. Adding a
4th DEBNA in the CPU cabinet will require a DELNI between
it and the H4005.
E) The BI Expander cabinet has 2 +13.5v pigtails per 6-slots of
BI. Also in the BI Expander cabinet, the IO panels for
additional DEBNA's must be placed in a Quad sized hole.
F) Cabinet Kit that is included in the CPU cabinet is the
CK-DEBNA-LD.
G) Cabinet kit for the VAXBI Expansion Cabinet is the
CK-DEBNA-LJ.
[1m 6.2.3 CIBCA [0m
A) Maximum of 1 per system and limited to a maximum of 1 per
VAXBI channel.
B) Requires 2 adjacent BI slots, IO panel is a Quad. In both
the CPU and Expander cabinets unused Quad IO panel space
should be used before octal spaces.
C) Standard in Cluster SBB's and it always
goes into K2J4/K2J5.
D) In non-clustered SBB's and preconfigured systems
maximum of one may be added per system. This add-on
CIBCA will always be the CIBCA-BA. The CIBCA-AA will only
be used as the embedded connection.
E) The CIBCI is not supported on the VAX 6300
[1m Page 20[0m
[1m 6.2.4 TBK70/TK70[0m
A) 1 standard with every system, NO additional TBK,s are
allowed.
B) Requires 1 BI slot, no IO panel. The TBK is always placed
in K2J6.
[1m 6.2.5 H7231-N Battery Backup[0m
A) Maximum of 1 H7231-N BBU may be added per system.
[1m 6.2.6 DMB32/DHB32[0m
A) Maximum of 8 total (DMB32 and DHB32) per system .
B) Maximum of 4 total (DMB32 and DHB32) per VAXBI channel.
C) Maximum of 2 total (DMB32 and DHB32) in the CPU cabinet.
D) Maximum of 1 DHB32-EIA232 in the CPU cabinet and requires a
CK-DHB32-AJ cab kit which is used in both the CPU and BI
Expander cabinets.
E) The DMB32 requires a CK-DMB32-LJ cab kit which is used in
both the CPU and BI Expander cabinets.
F) The DHB32-DEC423 requires a CK-DMB32-LJ cab kit which is
used in both the CPU and BI Expander cabinets.
Note: DMB32 IO Panel is 4 PU. DHB32-EIA232 IO Panel is 8 PU.
DHB32-DEC423 is 4 PU. Each DHB32 supports 16 asynchronous
communication lines. Therefore 8 DHB32,s support a maximum
of 128 directly connected asynchronous DEC 423 lines.
[1m 6.2.7 KLESI/TU81E[0m
A) Maximum of 4 per system.
B) Maximum of 2 per BI channel.
C) Requires 1 BI slot, IO panel is single. In the CPU or BI
Expander cabinets, the IO panel must be placed in a Quad
sized hole.
D) TU81E-BB is used in both the CPU and BI Expander
cabinets.
[1m Page 21[0m
[1m 6.2.8 DRB32[0m
A) Maximum of 8 DRB32's per system.
B) Maximum of 4 DRB32-M's per BI channel.
C) Maximum of 2 (DRB32-E and DRB32-W) per channel.
D) Maximum of 2 DRB32's in the CPU cabinet.
E) DRB32-M requires 1 BI slot and no IO panel.
F) DRB32-E requires 2 adjacent BI slots, IO panel is Quad.
(Includes the DRB32-M)
G) DRB32-W requires 2 adjacent BI slots, no IO panel.
(Includes the DRB32-M)
H) The required cab kit for the CPU and BI Expander cabinets
is CK-DRB32-LJ.
[1m 6.2.9 KDB50[0m
A) Maximum of 8 per system.
B) Maximum 2 per BI channel.
C) Requires 2 adjacent BI slots, IO panel is Quad.
D) One is standard in the non-clustered SBB's.
When standard it always goes into K2J4/K2J5.
E) The KDB50-C is used in both the CPU and BI Expander
cabinets.
F) In the CPU and BI Expander cab, unused quad IO panel
space should be used before octal spaces.
[1m Page 22[0m
[1m 7 PANEL SPACE SPECIFICATIONS [0m
7.1 Panel Space And VAXBI Slot Usage By VAXBI Options
PU = IO Panel Unit
# of
Option Modules PUs Notes
------ ------- -----
CIBCA 2 2 Embedded in 6**C* Cluster SBBs.
DEBNA 1 1
TBK70 1 0
DHB32 1 8 EIA232 IO Panel
DHB32 1 4 DEC423 IO Panel
DMB32 1 4 8-Async, 1-Sync, 1-Printer
DRB32-M 1 0 Cables directly to user's I/O
DRB32-E 2 2 Traditional PUs on bulkhead
DRB32-W 2 0 Cables directly to user's I/O
DWBUA 1 0 Cables to the Unibus cabinet via cabinet
sidewalls
KDB50 2 2 1-4 RA** disks
KLESI-B 1 1 For TU81E-B only
[1m Page 23[0m
}[1m 7.2 System IO Panel Space Availability[0m
[1m 7.2.1[0m VAX 6300 Kernel cabinet, not to scale:
+-------------------------------------+
| |
| |
| +-------+ +---+ +--------+ |
| |1 2 3 4| |5 6| |7 8 9 10| E |
| +-------+ +---+ +--------+ |
| |
| |
| +-------+ +---+ +--------+ |
| |1 2 3 4| |5 6| |7 8 9 10| D |
| +-------+ +---+ +--------+ |
| |
| +------------------+ +---+ +---+ |
| | | |1 2| |3 4| C |
| | | +---+ +---+ |
| | | +---+ +---+ |
| | BLOWER | |1 2| |3 4| B |
| | | +---+ +---+ |
| | | |
| | | Con Eth |
| +------------------+ |
| +--------|
|+-------------------------+ | |
|| | | H7206 |
|| H7231-N BBU | | PAL |
|+-------------------------+ | |
| +--------|
| +-------|
| 10.25" space |H405-x |
| +-------|
+-------------------------------------+
(Rear View of CPU Cabinet)
A) Con = Console
B) Eth = DEBNA Ethernet connection panel
[1m Page 24[0m
[1m 8.1 VAX 6300 Series System DC Power Capacity[0m
Current (in amps) for the System: 62AMB-YE/YJ (Basic Kernel)
Channel: +5V +5VB +12V -12V -5.2V -2V XMI Power
------ ------ ----- ----- ----- -----
Gross avail: 120.00 120.00 4.00 2.50 20.00 7.00 (pwr reg max)
- XTC 0 0.60 1.00 0.10 0 0
- DCARD 0 0.70 0 0 0 0
- XMI BkPl 2.50 0 0 0 0 0
- KA62B-AA 8.00 0 0 0 0 0
- MS62A-AB 0 7.50 0 0 0 0
- DWMBA-A 3.00 0 0 0 0 0 (BI Channel #0)
- DWMBA-A 3.00 0 0 0 0 0 (BI Channel #1)
- TK50-AA 1.20 0 2.00 0 0 0
------ ------ ----- ----- ----- -----
Net avail: 102.30 111.20 1.00 2.40 20.00 7.00
Channel: +5V +5VB +12V -12V -5.2V -2V BI Channel #0
------ ----- ----- ----- ----- -----
Gross avail: 120.00 0 4.00 2.50 20.00 7.00 (pwr reg max)
BI cage power 50.00* 0 3.00** 2.50* 15.00** 7.00* (cage max)
- DWMBA-B 6.00 0 0 0.10 0 0
- TBK50 6.72 0 0.50 0 0 0
- BI terminators 1.00 0 0 0 0 0
------ ----- ----- ----- ----- -----
Net avail: 36.28 0 2.50* 2.40* 15.00* 7.00*
Channel: +5V +5VB +12V -12V -5.2V -2V BI Channel #1
------ ----- ----- ----- ----- -----
Gross avail: 120.00 0 4.00 2.50 20.00 7.00 (pwr reg max)
BI cage power 50.00* 0 3.00** 2.50* 15.00** 7.00* (cage max)
- DWMBA-B 6.00 0 0 0.10 0 0
- DEBNA-M 6.72 0 0.50 0 0 0
- BI terminators 1.00 0 0 0 0 0
------ ----- ----- ----- ----- -----
Net avail: 36.28 0 2.50* 2.40* 15.00* 7.00*
* Power must be divided between the two BI card cages.
** Current from regulators exceeds the maximum for a single H9400.
[1mPage 25[0m
[1m 8.1.1 XMI Option DC Power Specifications[0m
The following data is accurate as of the date of this specification. It is
listed for reference only. Data is subject to change without notice.
Power Requirements for XMI Options
Option Current (Amps) used for the XMI voltages:
Name +5 +5B +12 -12 -5.2 -2
------ ----- ----- ----- ----- ----- -----
KA62B-AA 8.00 0.00 0.00 0.00 0.00 0.00
MS62A-AB 0.00 7.50 0.00 0.00 0.00 0.00
XTC 0.00 0.60 1.00 0.10 0.00 0.00
DCARD 0.00 0.70 0.00 0.00 0.00 0.00
XMI BkPl 2.50 0.00 0.00 0.00 0.00 0.00
DWMBA-A 3.00 0.00 0.00 0.00 0.00 0.00
[1m 8.2 VAXBI Option DC Power Specifications[0m
The following data is accurate as of the date of this specification. It is
listed for reference only. Data is subject to change without notice.
Power Requirements for VAXBI Options
Option Current (Amps) used for the VAXBI voltages:
Name +5 +5B +12 -12 -5.2 -2
----- ----- ----- ----- ----- ----- -----
CIBCA-AA 8.00 0.00 0.00 0.00 2.00 1.00
CIBCA-BA 9.00 0.00 0.00 0.00 2.00 1.00
DEBNA-M 6.72 0.00 0.50 0.00 0.00 0.00
TBK50-M 6.72 0.00 0.50 0.00 0.00 0.00
DHB32-M 5.34 0.00 0.42 0.42 0.00 0.00
DMB32-M 6.75 0.00 0.29 0.42 0.00 0.00
DRB32-E 9.80 0.00 0.00 0.00 0.00 0.00
DRB32-M 8.00 0.00 0.00 0.00 0.00 0.00
DRB32-W 11.80 0.00 0.00 0.00 0.00 0.00
DWBUA-M 8.29 0.00 0.00 0.04 0.00 0.00
DWMBA-B 6.00 0.00 0.00 0.10 0.00 0.00
KDB50-C 11.94 0.00 0.03 0.00 3.76 0.14
KLESI-B 7.00 0.00 0.00 0.00 0.00 0.00
BI Term 0.50 0.00 0.00 0.00 0.00 0.00
All BI data listed is based on the standard current
calculation method described in the VAXBI SRM.
}[1m 8.3 VAX 6300 Series System AC Power/Thermal Specs[0m
-Thermal Dissipation-
Config. AC Freq Volts AC Rec.Type Watts BTU/hr
Kernel min/max min/max AMPS NEMA
-------- ------- -------- ----- -------- ----- -----
63AMB-YJ 47-63 Hz 380/416 4 516R6W 1600 5440
[1m Page 26[0m
[1m 8.4 VAX 6300 Series System Physical Sizes[0m
Height Width Depth Weight
Config. (in.) (in.) (in.) (lbs.)
------------ ----- ----- ----- ------
63***/YJ 60.5 30.5 30.0 700
NOTES:
1. All dimensions and weights are estimates and are approximate.
[1m Page 27[0m
[1m VAXBI EXPANDER CAB [0m
[1m 9.1 TECHNICAL DESCRIPTION[0m
The BI Expander Cabinet (H9657-EA/EB) offers facilities for
I/O expansion in increments of six VAXBI slots with a minimum of
six slots (as constituted by a single H9400 VAXBI card cage
assembly. Additional capacity may be added to the basic cabinet
in increments of six VAXBI slots by installing the VAXBI
Expander Upgrade Kit (Option H9657-EU) to a maximum of 24 slots.
VAXBI backplanes may be operated as separate "channels" or
ganged together to form extended channels of 12, 18 or 24 slots
by use of Flexible Backplane Extenders (FBE's) in place of the
backplane (GIF and GOM) terminators normally used.
This cabinet will use the same VAXBI interfacing developed
for the 8800/8500. Each Channel will require a separate adapter
module pair and interface cabling to interface to the main
system (NBIA/NBIB). This option (DWMBA) also contains the H9657-
EU.
The BI Expander cabinet physically attaches to the host
system by means of the filler strip provided with the Expander
Cabinet (shipped "loose" inside the packaging of the Expander
Cabinet).
[1m 9.2 Cabinet Description[0m
The VAXBI Expander Cabinet is housed in a single bay and a
half Corporate Cabinet frame. The cabinet will/can contain:
o Up to a maximum of four VAXBI cages (H9400)
o Up to a maximum of four MPS regulators (H7189)
o MPS Power Distribution Backplane
o Air mover subsystem
o AC input box (H405-A/B)
o System Power Controller Box (SPC)
o 10 Octal and 6 quad I/O panel inserts
o DEC Power Bus for power up/down
o H7066-A module
o Load resistor assemblies (2)
o No EMM (Environmental Monitoring Module) option
}[1m 9.3 Cabinet Internal Dimensions [0m
The usable interior dimensions are:
Height 130.17 cm. (51.25 in.)
Width 63.5 cm. (25.0 in.)
Depth 63.5 cm. (25.0 in.)
[1m Page 28[0m
}[1m 9.4 Cabinet View [0m
Maximum card cage configuration shown
+--+-----------------------------+--+
| | | |
| | BLOWERS | |
| | | |
| +-----------------------------+ |
| +------+-+------+------+------+ |
| | | | * | * | * | |
| | |S| | | | |
| |H7189A|L|H7189A|H7189A|H7189A| |
| | |M| | | | |
| | | | | | | |
| +------+-+------+------+------+ |
| | | |
+--++------+------+------+------++--+
| || | * | * | * || |
| ||++++++|++++++|++++++|++++++|| |
| | ||||||||||||||||||||||||||| | |
| | ||||||||||||||||||||||||||| | |
| | ||||||||||||||||||||||||||| | |
| | H9400 |H9400 |H9400 |H9400 | |
| | ||||||||||||||||||||||||||| | |
| | |(K4)|||(K3)|||(K2)|||(K1)| | |
| | ||||||||||||||||||||||||||| | |
| ||++++++|++++++|++++++|++++++|| |
| || | | | || |
+--++------+------+------+------++--+
+--+-----------------------------+--+
| | | |
| | | |
| +------+ +----+----+---+---+ |
| | | | | H | H | H | |
| | | | S | 7 | 7 | 7 | |
| | H405 | | P | 1 | 0 | 0 | |
| |(Rear)| | C | 7 | 6 | 6 | |
| | | | | 6 | 0 | 1 | |
+--+------+----+---------+---+---+--+
FRONT VIEW
The primary power input and space for 10 octal and
6 quad I/O panel units will be provided at the cabinet rear.
* Configured into cabinet using H9657-EU upgrade kits
[1m Page 29[0m
[1m 9.5 BI Expander Cabinet, not to scale[0m
7.2.2 BI Expander Cabinet, not to scale:
H9657-E Expander Cabinet
+------------------------------+ +------------------------------+
| |S| | | |
| |L| | | |
| |M| | | |
| |_| | | |
| | | |
| | | |
| | | |
| +-----++-----++-----++-----+ | | |
| |BI 2 ||BI 3 ||BI 4 ||BI 5 | | | |
| | || || || | | | |
| | || || || | | | |
| | || || || | | | |
| | || || || | | | +--------------------------+ |
| | || || || | | | |F 1 2 3 4 5 6 7 8 9 10 | |
| | || || || | | | |--------------------------| |
| | || || || | | | |--------------------------| |
| +-----++-----++-----++-----+ | | |E 1 2 3 4 5 6 7 8 9 10 | |
| | | |--------------------------| |
| | | |--------------------------| |
| | | |D 1 2 3 4 5 6 7 8 9 10 | |
| | | |--------------------------| |
| | | |--------------------------| |
| | | |C 1 2 3 4 5 6 7 8 9 10 | |
| | | |--------------------------| |
| | | |----------------+---------| |
| | | |B 1 2 3 4 5 6 | | |
| | | |----------------| POWER | |
| | | |----------------| CONTROL | |
| | | |A 1 2 3 4 5 6 | | |
| | | |----------------+---------| |
+------------------------------+ +------------------------------+
(FRONT) (BACK)
[1mPage 30[0m
[1m 9.6 S p e c i f i c a t i o n s[0m
Processors/Memory/VAXBI Channels
Processors Memory VAXBI Channels
~~~~~~~~~~ ~~~~~~ ~~~~~~~~~~~~~~
VAX 6310 1 32 to 256 MB 2 to 6
VAX 6320 2 64 to 256 MB 2 to 6
VAX 6330 3 64 to 256 MB 2 to 6
VAX 6340 4 64 to 256 MB 2 to 6
VAX 6350 5 128 to 224 MB 2 to 4
VAX 6360 6 128 to 192 MB 2 to 4
Maximum I/O bandwidth 60 Mbytes/sec*
Cache 1 Kbyte on chip**
256 Kbytes on board**
Instruction pre-fetch
buffer 3 Longwords**
Internal data path 64 bits
Cycle time 60 nsec
Total VAXBI slots available 10 standard; up to 30*
Total VAXBI channels 2 standard; up to 6*
Ethernet connections 1 to 4
Local disk connections Up to 32*
VAX Instruction Set
32-bit registers 16
Basic operations 304
Priority interrupt
levels 32
Addressing modes 9
Data types Integer, F, D, G, H*** floating point, packed
decimal***, character string, variable bit
fields, and numeric strings.***
Main Memory
Virtual address capacity 4 Gbytes
Data protection 8-bit ECC code per Quadword
Memory cycle 448 nsec-Quadword write
512 nsec-Octaword write
1024 nsec-Hexword read
Battery backup Optional
Operating Environment
(with TK70 in use)
Temperature 15oC to 32oC (59oF to 90oF)
Humidity 20% to 80%
Altitude 2,400 m (8,000 ft)
Maximum heat dissipation 5,440 BTU/hr
Power requirements
Input voltage 208 VRMS (60 Hz), 380/416 VRMS (50 Hz)
Frequency tolerance 47-63 Hz
Phases 3
Surge current 60 A
Maximum ac power
consumption 1.6 kW
Physical Characteristics
Dimensions: Height 154 cm (60.5 in)
Width 78 cm (30.5 in)
Depth 76 cm (30 in)
Weight 318 kg (700 lb)
* Two VAXBI channels are supported within the systems cabinet.
A VAXBI expansion cabinet is required to grow to six VAXBI channels.
** Per processor
*** Emulated by operating system software
}[1m The following pages contain the System Building Block
Menus. These menus are subject to change up to announcement
Date of the product. Missing parts include Layered Product
S/W parts and SSP options.[0m
PLEASE USE FOR YOUR OWN PURPOSES INITIALLY
[1m Page 32 [0m
[1m 10 SYSTEM BUILDING BLOCKS[0m
The SBB's will use the standard format with the following field
definitions. (Only those letters/numbers that will be used by Calypso are
listed.)
[1m 10.1 GENERAL FORMAT [0M
a a b c d - e f
--- - - - - -
| | | | | |
| | | | | +-------- E = 60 Hz power, non-clustered
| | | | | J = 50 Hz power, non-clustered
| | | | | P = 60 Hz power, clustered
| | | | | T = 50 Hz power, clustered
| | | | |
| | | | +---------- Y = base level system
| | | | X = hardware only system
| | | | A = VMS paid up license
| | | | B = Ultrix paid up license
| | | | D = VMS rental license
| | | | E = Ultrix rental license
| | | |
| | | +-------------- Version (A-Z)
| | |
| | +---------------- M = XMI bus, not clustered
| | C = Clustered
| |
| +------------------ CPU number (A=1xCPU, B=2xCPU,
| C=3xCPU, D=4xCPU,
| E=5xCPU, F=6xCPU)
|
|
|
|
|
+--------------------- 63* = Hyperion
*the next character (b) for MSB systems will
always be alphabetic.
[1m Page 33 [0m
VAX 6300 SERIES VAXcluster SYSTEMS
-----------------------------------
Step 1 Select appropriate system and part number. All VAX 6300
Systems Series Systems include a TK70 load device. A system device
is required for a fully supported system. For optimum backup
performance, a high-capacity tape drive is recommended. If
system does not include appropriate devices, it may not be
maintainable. Contact local Field Service for details.
-----------------------------------------------------------
All 6300 Series VAXcluster Systems include
-Integral Floating Point
-Two VAXBI Channels
-CIBCA VAXcluster port and one set of CI cables
-DEBNA 802.3/Ethernet Communications Interface
-TK70 Tape Drive and Interface
-One Full Year Product Warranty*
Select appropriate VAXcluster System and part number.
------------------------------
| VAX 6310 VAXcluster System |
------------------------------
63ACB-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63ACB-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6310 Processor
-32 Mbytes 1M-chip ECC MOS Memory
------------------------------
| VAX 6320 VAXcluster System |
------------------------------
63BCA-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63BCA-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6320 Processor
-32 Mbytes 1M-chip ECC MOS Memory
------------------------------------------------------------
63BCB-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63BCB-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6320 Processor
-64 Mbytes 1M-chip ECC MOS Memory
------------------------------
| VAX 6330 VAXcluster System |
------------------------------
63CCA-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63CCA-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6330 Processor
-64 Mbytes 1M-chip ECC MOS Memory
------------------------------
| VAX 6340 VAXcluster System |
------------------------------
63DCA-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63DCA-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6340 Processor
-64 Mbytes 1M-chip ECC MOS Memory
------------------------------------------------------------
63DCB-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63DCB-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6340 Processor
-128 Mbytes 1M-chip ECC MOS Memory
------------------------------
| VAX 6350 VAXcluster System |
------------------------------
63ECA-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63ECA-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6350 Processor
-128 Mbytes 1M-chip ECC MOS Memory
------------------------------
| VAX 6360 VAXcluster System |
------------------------------
63FCA-DT One-year VMS, VAXcluster, and DECnet Full
Function Licenses
63FCA-AT Paid-up VMS, VAXcluster, and DECnet Full
Function Licenses
-VAX 6360 Processor
-128 Mbytes 1M-chip ECC MOS Memory
-----------------------------------------------------------
*Standard Warranty recommended, see Services section.
___________________________________________________________________________
Step 2 If ordering a new VAXcluster system, select one of the
VAXcluster following part numbers. If adding on to an existing
Building Blocks VAXcluster, no additional hardware is required; however,
optional devices may be selected as required.
-----------------------------------------------------------
HSC70 Building HSS70-AB Includes HSC70 Storage Controller, SC008
Block Star Coupler, HSC5X Disk Interface, and
one set of BNCIA-20 cables.
-----------------------------------------------------------
HSC50 Building HSS50-AB Includes HSC50 Storage Controller, SC008
Block Star Coupler, HSC5X Disk Interface, and
one set of BNCIA-20 cables.
___________________________________________________________________________
Step 3 Select a system device and backup device from the following
Mass Storage table. Note that the TA79 and TA81 combinations require an
HSC5X-CA tape interface. The TA90 is a supported backup
device, see Section 6 for ordering information. For complete
disk offering see Section 6.
-----------------------------------------------------------
Suggested Backup Devices
System Device
-----------------------------------------------------------
TU81-Plus TA79 TA81
-----------------------------------------------------------
RA60 RA60-FD RA60-FD RA60-FD
(1 Disk/4 HI Cab) TU81E-BB TA79-BJ TA81-AB
HSC5X-CA HSC5X-CA
-----------------------------------------------------------
RA82 RA82-AD RA82-CD RA82-AD
(1 Disk/No Cab*) TU81E-BB TA79-BJ TA81-AB
HSC5X-CA HSC5X-CA
------------------------------------------------------------
SA482 SA482-AD SA482-AD SA482-AD
(4 Disks/SA Cab) TU81E-BB TA79-BJ TA81-AB
HSC5X-CA HSC5X-CA
------------------------------------------------------------
SA600** SA600-HD SA600-HD SA600-HD
(4 Disks/SA Cab) TU81E-BB TA79-BJ TA81-AB
HSC5X-CA HSC5X-CA
------------------------------------------------------------
SA600** SA600-JD SA600-JD SA600-JD
(8 Disks/SA Cab) TU81E-BB TA79-BJ TA81-AB
HSC5X-CA/DA HSC5X-CA/DA
------------------------------------------------------------
*RA82-AD configured in TU81E and TA81 cabinets.
**Cables required, see SA600 description in Section 6.
________________________________________________________________________
Step 4 VMS and DECnet Full Function (with VMS Services for MS-DOS)
Software licenses included with system. Select media and documentation
and Startup Service Package; refer to Software and Services
sections for details. Order media and documentation
separately for qualified layered products at no charge
when Startup Service Package is purchased; additional
packages are also available. Refer to Section 13, Software,
for license configuration and software product information.
-----------------------------------------------------
Media and QA-001AC-H5 VMS Media and Extended Documentation Kit,
Documentation including VAXcluster and DECnet Documentation
QA-A93AA-H5 VMS Services for MS-DOS Media and
Documentation
--------------------------------------------------------
____________________________________________________________________________
Step 5 Select additional memory and battery backup if required.
CPU Options VAX 6310/6320/6330/6340 systems can be expanded to a
maximum of 256 Mbytes. VAX 6350/6360 systems can
be expanded to a maximum of 192 Mbytes(due to XMI slots).
------------------------------------------------------------
32 Mbytes of MS62A-AB Maximum eight per VAX 6310/6320/6330/6340
Memory systems. Maximum six per VAX 6350/6360
systems. Total number of memory boards
must equal one, two, four, six, or eight.
The total number of processors, VAXBI
channels, and 32-Mbyte memory modules
cannot exceed 14.
VAX 6310 includes one.
VAX 6320 includes one or two.
VAX 6330 includes two.
VAX 6340 includes two or four.
VAX 6350 includes four.
VAX 6360 includes four.
-------------------------------------------------------
Battery Backup H7231-N Maximum one per system.
________________________________________________________________________
Step 6 DEBNA Ethernet Controller included with each system.
Commmunications Select additional devices if required. Connection of
Devices system to Ethernet requires an Ethernet transceiver
cable (ex. BNE3L-20) and an H4005 or port on a DELNI.
See Networks and Communications Buyer's Guide for details.
---------------------------------------------------------
DEBNA 802.3/ DEBNA-M One included; maximum two per VAXBI channel,
Controller four per system. Connection of
system to Ethernet requires a transceiver
cable (ex. BNE3L-20). Internal VAXBI
channels are limited to a total of three
H4005 connections. Additional internal
connections require a port on a DELNI and
cannot be directly connected to an H4005.
DEBNA Cab Kits CK-DEBNA-LD Required with DEBNA-M if placed on internal
VAXBI channel.
CK-DEBNA-LJ Required with DEBNA-M if placed on external
VAXBI channel.
----------------------------------------------------------
DECserver 550 DSRVS-** Each terminal server requires an Ethernet
DECserver 200 DSRVB-** transceiver cable (BNE3L-20) and an H4005
or port on a DELNI. See the Networks and
Communications Buyer's Guide for ordering
information; additional items (BN20*-2E
and CX***-A* for DSRVS and QA-VCBAA-HM for
DSRVB) are required.
----------------------------------------------------------
DMB32/DHB32 Total of two DMB32s/DHB32s per CPU cabinet; maximum four
Controllers per external VAXBI channel. Total of eight DMB32s/DHB32s
per system.
----------------------------------------------------------
DMB32 DMB32-M Eight-line asynchronous communications/
printer controller.
DMB32 Cab Kit CK-DMB32-LJ Required with DMB32-M.
DHB32 DHB32-M 16-line asynchronous communications
controller.
DHB32 Cab Kits CK-DHB32-AJ Required with DHB32-M for EIA-232 connection.
CK-DHB32-LJ Required with DHB32-M for DEC-423 connection.
------------------------------------------------------------
___________________________________________________________________________
Step 7 VAXcluster (CI) port and BNCIA-20 cable set included with
Additional system for connection to VAXcluster. Select additional
VAXcluster options if required. See Storage Section for more details
Options
-----------------------------------------------------------
HSC70 Storage HSC70-AB Supports up to eight of any combination of
Controller HSC5X interfaces; BNCIA-** cable set
required.
-----------------------------------------------------------
HSC50 Storage HSC50-AB Supports up to six of any combination of
Controller HSC5X interfaces; BNCIA-** cable set
required.
-----------------------------------------------------------
HSC50/70 Disk HSC5X-BA Supports up to four RA disk drives.
Interface -----------------------------------------------------------
HSC50/70 Tape HSC5X-CA Supports up to four of any combination of
Interface TA81 and TA79 tape units. HSC50/70 supports
up to eight of any combination of TA81 and
TA90/TA79 tape units and TA90/TU79 add-on units.
-----------------------------------------------------------
HSC50/70 Tape HSC5X-DA Supports up to four TA90 tape units. HSC50/70
Interface supports up to eight of any combination of
TA81 and TA90/TA79 tape units and TA90/TU79
add-on units.
-----------------------------------------------------------
HSC50 Power HSC5X-EB Expansion of over three HSC5X-*A on the HSC50
Supply requires a power supply.
------------------------------------------------------------
VAXcluster The VCS connects to the console ports of each VAXcluster
Console System node with a fiber-optic link to provide a single, central
point of control for all cluster-wide console functions.
Refer to VAXcluster Options for details.
___________________________________________________________________________
Step 8 Select additional mass storage devices if required. See
Additional Storage section for details.
Mass Storage -----------------------------------------------------------
VAXBI Disk KDB50-C Maximum two per VAXBI channel, total of
Controller eight per system.
-----------------------------------------------------------
RA Disks/ Maximum four disk drives per KDB50. See RA60/82 and
Storage Arrays SA482/550/600/650 descriptions for ordering information.
-----------------------------------------------------------
RV20 Optical Maximum two RV20 masters per VAXBI channel; eight per
Drive system. Maximum three additional RV20 slaves per master.
See RV20 description for ordering information.
-----------------------------------------------------------
RV64 Optical Maximum...?
Jukebox
See RV64 description for ordering information.
-----------------------------------------------------------
TU81-Plus Tape TU81E-BB Maximum two per VAXBI channel; four per
Drive system (cables included).
-----------------------------------------------------------
TA90 Tape Drive Maximum four per HSC5X-DA; cables included. Supports one
TA90 add-on unit. See TA90 description for ordering
information.
-----------------------------------------------------------
TA90 Add-on Maximum one per TA90; cables included for connection to
Tape Unit TA90 tape unit or TA90 add-on tape unit. See TA90
description for ordering information.
-----------------------------------------------------------
TA79 Tape Drive TA79-BJ Maximum four per HSC5X-CA; cables included.
Supports up to three TU79 add-on units.
-----------------------------------------------------------
TU79 Add-on TU79-AJ Maximum three per TA79; cables included for
Tape Unit connection to TA79 tape unit or TU79 tape
unit.
-----------------------------------------------------------
TA81 Tape Drive TA81-AB Maximum four tape units per HSC5X-CA; cables
included for connection to HSC5X-CA.
___________________________________________________________________________
Step 9 A hardcopy console terminal is required unless otherwise
Console available.
Terminal -----------------------------------------------------------
VT3*0-** Suggested Video Terminal
LA75-** Suggested local printer
___________________________________________________________________________
Step 10 Select lineprinters as required. Lineprinters must connect
Lineprinters to an asynchronous line or DMB32 printer port. See System
Printers Section for details.
___________________________________________________________________________
Step 11 Select terminals as required equal to the number of
Terminals communications lines. A cable (ex. BC16E-25) must be ordered
with each terminal unless otherwise provided.
___________________________________________________________________________
Step 12 Two internal VAXBI channels included; maximum six VAXBI
I/O Expansion channels per VAX 6310/6320/6330/6340 systems. Maximum
four VAXBI channels per VAX 6350/6360 systems.
There are six slots and 26 panel units available for expansion.
The total number of processors, VAXBI channels, and
32-Mbyte memory modules cannot exceed 14.
-----------------------------------------------------------
External Third DWMBA-BB Adds third VAXBI channel; maximum one per
VAXBI Channel system. Includes H9657-ED VAXBI
Expansion Cabinet and H9657-EU VAXBI
Expansion Kit. Provides five VAXBI slots
and 52 panel units and space for additional
channels/slots.
-----------------------------------------------------------
External Fourth,DWMBA-CA For VAX 6310/6320/6330/6340 adds fourth,
Fifth, or Sixth fifth or sixth VAXBI channels; maximum
VAXBI Channel three per system. For VAX 6350/6360 adds
fourth VAXBI channel; maximum one per
system. Includes H9657-EU VAXBI Expansion
Kit. Provides five VAXBI slots. Requires
DWMBA-BB third VAXBI channel.
____________________________________________________________________________
Step 13 Before adding VAXBI options to the system, determine the
Configuring available mounting space and power requirements from
Information the following tables; see VAXBI Options Requirements
Page in this section.
------------------------------------------------------------
VAX 6300 Series VAXcluster Systems
5V 12V -12V -5.2V -2V Nodes PU
____________________________________________________________________________
VAXBI Channel #1,#2 10 VAXBI Slots 86.00 4.00 2.40 20.00 7.00 29
____________________________________________________________________________
USED
____________________________________________________________________________
DEBNA 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 1
____________________________________________________________________________
CIBCA 2 VAXBI Slots 9.00 0.00 0.00 2.00 1.00 1 2
____________________________________________________________________________
TK70 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 0
____________________________________________________________________________
AVAILABLE 6 VAXBI Slots 63.56 4.00 2.40 18.00 6.00 26
____________________________________________________________________________
VAX 6300 SERIES VMS SYSTEMS
---------------------------
Step 1 Select VAX 6300 Series BASE SYSTEM. The configuring guidelines
Systems apply to both systems. All VAX 6300 Series Systems include a
TK70 load device. A system device is required for a
fully supported system. For optimum backup performance, a
high-capacity tape drive is recommended. If system does
not include appropriate devices, it may not be maintainable.
Contact local Field Service for details.
-----------------------------------------------------------
All VAX 6300 Series BASE SYSTEMS include
-Integral Floating Point
-Two VAXBI Channels
-DEBNA 802.3/Ethernet Communications Interface
-KDB50 Disk Controller
-TK70 Tape Drive and Interface
-One Full Year Product Warranty*
Select appropriate BASE SYSTEM and part number.
----------------------------
| VAX 6310 VMS Base System |
----------------------------
63AMB-DJ One-year VMS and DECnet End Node Licenses
63AMB-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6310 Processor
-32 Mbytes 1M-chip ECC MOS Memory
----------------------------
| VAX 6320 VMS Base System |
----------------------------
63BMA-DJ One-year VMS and DECnet End Node Licenses
63BMA-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6320 Processor
-32 Mbytes 1M-chip ECC MOS Memory
----------------------------------------------------------
63BMB-DJ One-year VMS and DECnet End Node Licenses
63BMB-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6320 Processor
-64 Mbytes 1M-chip ECC MOS Memory
----------------------------
| VAX 6330 VMS Base System |
----------------------------
63CMA-DJ One-year VMS and DECnet End Node Licenses
63CMA-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6330 Processor
-64 Mbytes 1M-chip ECC MOS Memory
----------------------------
| VAX 6340 VMS Base System |
----------------------------
63DMA-DJ One-year VMS and DECnet End Node Licenses
63DMA-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6340 Processor
-64 Mbytes 1M-chip ECC MOS Memory
---------------------------------------------------------
63DMB-DJ One-year VMS and DECnet End Node Licenses
63DMB-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6340 Processor
-128 Mbytes 1M-chip ECC MOS Memory
----------------------------
| VAX 6350 VMS Base System |
----------------------------
63EMA-DJ One-year VMS and DECnet End Node Licenses
63EMA-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6350 Processor
-128 Mbytes 1M-chip ECC MOS Memory
----------------------------
| VAX 6360 VMS Base System |
----------------------------
63FMA-DJ One-year VMS and DECnet End Node Licenses
63FMA-AJ Paid-up VMS and DECnet End Node Licenses
-VAX 6360 Processor
-128 Mbytes 1M-chip ECC MOS Memory
-----------------------------------------------------------
*Standard Warranty recommended, see Services section.
__________________________________________________________________________
Step 2
For Base System select a system device and backup device
from the following table. All Base Systems include a
TK70 load device. See Section 6 for complete disk offering.
Suggested System Device Backup Device
---------------------------------------------
TU81-Plus
---------------------------------------------
RA60 (1 Disk/4 HI Cab) RA60-FD
TU81E-BB
---------------------------------------------
RA82 (1 Disk/No Cab*) RA82-AD
TU81E-BB
---------------------------------------------
SA482 (4 Disks/SA Cab) SA482-AD
TU81E-BB
---------------------------------------------
SA600**(4 Disks/SA Cab) SA600-HD
TU81E-BB
---------------------------------------------
SA600**(8 Disks/SA Cab) SA600-JD
TU81E-BB
---------------------------------------------
*RA82-AD configured in TU81E cabinet.
**Cables required, see SA600 description in Section 6.
________________________________________________________________________
Step 3 VMS and DECnet End Node (with VMS Services for MS-DOS)
Software licenses included with VAX 6300 Series Base systems.
Select media and documentation and
Startup Service Package; refer to Software and Services
sections for details. Order media and documentation
separately for Qualified layered products at no charge
when Startup Service Packaage is purchased; additional
packages are also available.
-----------------------------------------------------
Media and QA-001AC-H5 VMS Media and Extended Documentation Kit,
Documentation including VAXcluster and DECnet Documentation
QA-A93AA-H5 VMS Services for MS-DOS Media and
Documentation
--------------------------------------------------------
________________________________________________________________________
Step 4 Select additional memory and battery backup if required.
VAX 6310/6320/6330/6340 systems can be expanded to a maximum
of 256 Mbytes. VAX 6350/6360 systems can be
expanded to a maximum of 192 Mbytes (due to XMI slots).
CPU Options --------------------------------------------------------
32 Mbytes of MS62A-AB Maximum eight per VAX 6310/6320/6330/6340
Memory systems. Maximum six per VAX 6350/6360
systems. Total number of memory boards
must equal one, two four, six, or eight.
The total number of processors, VAXBI
channels, and 32-Mbyte memory modules
cannot exceed 14.
VAX 6310 includes one.
VAX 6320 includes one or two.
VAX 6330 includes two.
VAX 6340 includes two or four.
VAX 6350 includes four.
VAX 6360 includes four.
-------------------------------------------------------
Battery Backup H7231-N Maximum one per system.
________________________________________________________________________
Step 5 DEBNA Ethernet Controller included with each system.
Communications Select additional devices if required. Connection of
Devices system to Ethernet requires an Ethernet transceiver
cable (ex. BNE3L-20) and an H4005 or port on a DELNI.
See Networks and Communications Buyer's Guide for details.
---------------------------------------------------------
DEBNA 802.3/ DEBNA-M One included; maximum two per VAXBI channel,
Controller four per system. Connection of system
to Ethernet requires a transceiver
cable (ex. BNE3L-20). Internal VAXBI
channels are limited to a total of three
H4005 connections. Additional internal
connections require a port on a DELNI and
cannot be directly connected to an H4005.
DEBNA Cab Kits CK-DEBNA-LD Required with DEBNA-M if placed on internal
VAXBI channel.
CK-DEBNA-LJ Required with DEBNA-M if placed on external
VAXBI channel.
----------------------------------------------------------
DECserver 550 DSRVS-** Each terminal server requires an Ethernet
DECserver 200 DSRVB-** transceiver cable (BNE3L-20) and an H4005
or port on a DELNI. See the Networks and
Communications Buyer's Guide for ordering
information; additional items (BN20*-2E
and CX***-A* for DSRVS and QA-VCBAA-HM for
DSRVB) are required.
----------------------------------------------------------
DMB32/DHB32 Total of two DMB32s/DHB32s per CPU cabinet; maximum four
Controllers per external VAXBI channel. Total of eight DMB32s/DHB32s
per system.
----------------------------------------------------------
DMB32 DMB32-M Eight-line asynchronous communications/
printer controller.
DMB32 Cab Kit CK-DMB32-LJ Required with DMB32-M.
DHB32 DHB32-M 16-line asynchronous communications
controller.
DHB32 Cab Kits CK-DHB32-AJ Required with DHB32-M for EIA-232 connection.
CK-DHB32-LJ Required with DHB32-M for DEC-423 connection.
-----------------------------------------------------------
___________________________________________________________________________
Step 6
Additional Mass Select additional mass storage devices as required.
Storage -----------------------------------------------------------
VAXBI Disk KDB50-C One included; maximum two per VAXBI channel,
Controller eight per system.
-----------------------------------------------------------
RA Disks/ Maximum four disk drives per KDB50. See RA60/82 and
Storage Arrays SA482/550/600/650 descriptions for ordering information.
-----------------------------------------------------------
RV20 Optical Maximum two RV20 masters per VAXBI channel; eight per
Drive system. Maximum three additional RV20 slaves per RV20
master. See RV20 description for ordering information.
-----------------------------------------------------------
RV64 Optical Maximum....?
Jukebox
See RV64 description for ordering information.
-----------------------------------------------------------
TU81-Plus Tape TU81E-BB Maximum two per VAXBI channel,four per
Drive system(cables included)
___________________________________________________________________________
Step 7 A hardcopy console terminal is required unless otherwise
Console available.
Terminal -----------------------------------------------------------
VT3*0-** Suggested video terminal.
LA75-** Suggested local printer.
___________________________________________________________________________
Step 8 Select lineprinters as required. Lineprinters must connect
Lineprinters to an asynchronous line or DMB32 printer port. See System
Printers section for details.
___________________________________________________________________________
Step 9 Select terminals as required equal to the number of
Terminals communications lines. A cable (ex. BC16E-25) must be ordered
with each terminal unless otherwise provided. See Terminals
and Printers section for details.
___________________________________________________________________________
Step 10 Two internal VAXBI channels included with each system.
I/O Expansion Maximum six VAXBI channels per VAX 6310/6320/6330/6340 systems.
Maximum four VAXBI channels per VAX 6350/6360 systems.
Five VAXBI slots and 25 panel units are available for
expansion in the Preconfigured System and six slots and
26 panel units are available in the Base Systems. The
total number of processors, VAXBI channels, and 32-Mbyte
memory modules cannot exceed 14.
-----------------------------------------------------------
External Third DWMBA-BB Adds third VAXBI channel; maximum one per
VAXBI Channel system. Includes H9657-EC/ED VAXBI
Expansion Cabinet and H9657-EU VAXBI
Expansion Kit. Provides five VAXBI slots
and 52 panel units and space for additional
channels/slots.
-----------------------------------------------------------
External Fourth,DWMBA-CA For VAX 6310/6320/630/6340 systems adds fourth,
Fifth, or Sixth fifth or sixth VAXBI channels; maximum
VAXBI Channel three per system. For VAX 6350/6360 systems
adds fourth VAXBI channel; maximum one per
system. Includes H9657-EU VAXBI Expansion
Kit. Provides five VAXBI slots. Requires
DWMBA-BA/BB third VAXBI channel.
____________________________________________________________________________
Step 11 Before adding VAXBI options to the system, determine the
Configuring available mounting space and power requirements from
Information the following tables; see VAXBI Options Requirements
Page in this section.
------------------------------------------------------------
VAX 6300 Series VMS Base Systems
5V 12V -12V -5.2V -2V Nodes PU
____________________________________________________________________________
VAXBI Channel #1,#2 10 VAXBI Slots 86.00 4.00 2.40 20.00 7.00 29
____________________________________________________________________________
USED
____________________________________________________________________________
DEBNA 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 1
____________________________________________________________________________
KDB50 2 VAXBI Slots 11.94 0.03 0.00 3.76 0.14 1 2
____________________________________________________________________________
TK70 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 0
____________________________________________________________________________
AVAILABLE 6 VAXBI Slots 60.62 3.97 2.40 16.24 6.86 26
____________________________________________________________________________
VAX FILESERVER 6300 SERIES VMS SYSTEMS
--------------------------------------
All VAX Fileserver 6300 Series VMS Base Systems include
-Integral Floating Point
-32 Mbytes 1M-chip ECC MOS memory
-Two VAXBI Channels
-DEBNA 802.3/Ethernet Communications Interface
-KDB50 Disk Controller
-TK70 Tape Drive and Interface
-Paid-up VMS File/Application Server License
-Paid-up DECnet Full-Function License
-Paid-up VAXcluster License
-Paid-up VMS/ULTRIX Connection License
-Paid-up NMCC/VAX ETHERnim Licenses License
-Paid-up Distributed File Services License
-Paid-up Distributed Queue Services License
-Paid-up Remote System Manager License
-Distributed Name Services License
-One Full Year Product Warranty*
---------------------------------
|VAX Fileserver 6310 VMS System |
---------------------------------
63AMP-AJ
---------------------------------
|VAX Fileserver 6320 VMS System |
---------------------------------
63BMN-AJ
*Standard Warranty recommended, see Services section.
___________________________________________________________________________
Step 2 Select a system device and back-up device from the
Mass Storage following table.
---------------------------------------------------------
Suggested System Device Backup Device
---------------------------------------------
TU81-Plus
---------------------------------------------
RA60 (1 Disk/4 HI Cab) RA60-FD
TU81E-BB
---------------------------------------------
RA82 (1 Disk/No Cab*) RA82-AD
TU81E-BB
---------------------------------------------
SA482 (4 Disks/SA Cab) SA482-AD
TU81E-BB
---------------------------------------------
SA600**(4 Disks/SA Cab) SA600-HD
TU81E-BB
---------------------------------------------
SA600**(8 Disks/SA Cab) SA600-JD
TU81E-BB
---------------------------------------------
*RA82-AA/AD configured in TU81E cabinet.
**Cables required, see SA600 description in Section 6.
________________________________________________________________________
Step 3 VMS VAXserver, VMS/ULTRIX Conection, DECnet Full Function,
Software VAXcluster, NMCC/VAX ETHERnim, Disributed File Services,
Distributed Queue Services, Remote System Manager, and
Distributed Name Services licenses included with
with systems. Select media and documentation
and Startup Service Packages; refer to Section 13, Software,
and Chapter 10, Services for details. Order media and
documentation separately for qualified layered products
at no charge when Startup Service Package is purchased.
-----------------------------------------------------
Media and QA-001AC-H5 VMS Media and Extended Documentation Kit,
Documentation including VAXcluster and DECnet Documentation
QA-A93AA-H5 VMS Services for MS-DOS
QA-VHRAA-H5 VMS/ULTRIX Connection
QA-514AA-H5 NMCC/VAX ETHERnim
QA-VERAA-H5 Distributed File Servies
QA-VENAA-H5 Distributed Queue Services
QA-B13AA-H5 Remote System Manager
QA-VERAA-H5 Distributed Name Services
--------------------------------------------------------
________________________________________________________________________
Step 4 Select additional memory and battery backup if required.
CPU Options Systems can be expanded to a maximum of 256 Mbytes.
32 Mbytes of --------------------------------------------------------
Memory MS62A-AB One included; maximum eight per system.
Total number of memory boards must equal
one, two, four, six, or eight. The total
number of processors, VAXBI channels,
and 32-Mbyte memory modules cannot exceed 14.
-------------------------------------------------------
Battery Backup H7231-N Maximum one per system.
________________________________________________________________________
Step 5 DEBNA Ethernet Controller included with each system.
Commmunications Select additional devices if required. Connection of
Devices system to Ethernet requires an Ethernet transceiver
cable (ex. BNE3L-20) and an H4005 or port on a DELNI.
See Networks and Communications Buyer's Guide for details.
---------------------------------------------------------
DEBNA 802.3/ DEBNA-M One included; maximum two per VAXBI channel;
Controller four per system. Connection of
system to Ethernet requires a transceiver
cable (ex. BNE3L-20). Internal VAXBI
channels are limited to a total of three
H4005 connections. Additional internal
connections require a port on a DELNI and
cannot be directly connected to an H4005.
DEBNA Cab Kits CK-DEBNA-LD Required with DEBNA-M if placed on internal
VAXBI channel.
CK-DEBNA-LJ Required with DEBNA-M if placed on external
VAXBI channel.
-------------------------------------
DECserver 550 DSRVS-** Each terminal server requires an Ethernet
DECserver 200 DSRVB-** transceiver cable (BNE3L-20) and an H4005
or port on a DELNI. See the Networks and
Communications Buyer's Guide for ordering
information; additional items (BN20*-2E
and CX***-A* for DSRVS and QA-VCBAA-HM for
DSRVB) are required.
----------------------------------------------------------
DMB32/DHB32 Total of two DMB32s/DHB32s per CPU cabinet; maximum four
Controllers per external VAXBI channel. Total of eight DMB32s/DHB32s
per system.
----------------------------------------------------------
DMB32 DMB32-M Eight-line asynchronous communications/
printer controller.
DMB32 Cab Kit CK-DMB32-LJ Required with DMB32-M.
DHB32 DHB32-M 16-line asynchronous communications
controller.
DHB32 Cab Kits CK-DHB32-AJ Required with DHB32-M for EIA-232 connection.
CK-DHB32-LJ Required with DHB32-M for DEC-423 connection.
-----------------------------------------------------------
___________________________________________________________________________
Step 6
Additional Mass Select additional mass storage devices as required.
Storage -----------------------------------------------------------
VAXBI Disk KDB50-C One included with system. Maximum two per
Controller VAXBI channel; eight per system.
-----------------------------------------------------------
RA Disks/ Maximum four disk drives per KDB50. See RA60/82 and
Storage Arrays SA482/600/550/650 descriptions for ordering information.
-----------------------------------------------------------
RV20 Optical Maximum two RV20 masters per VAXBI channel; eight per
Drive system. Maximum three additional RV20 slaves per RV20
master. See RV20 description for ordering information.
-----------------------------------------------------------
RV64 Optical Maximum....?
Jukebox
See RV64 description for ordering information.
----------------------------------------------------------
TU81-Plus Tape TU81E-BB Maximum two per VAXBI channel, four per
Drive system (cables included).
___________________________________________________________________________
Step 7 A hardcopy console terminal is required unless otherwise
Console available.
Terminal -----------------------------------------------------------
VT3*0-** Suggested Video Terminal
LA75-** Suggested Local Printer
___________________________________________________________________________
Step 8 Select lineprinters as required. Lineprinters must connect
Lineprinters to an asynchronous line or DMB32 printer port. See System
Printers section for details.
___________________________________________________________________________
Step 9 Select terminals as required equal to the number of
Terminals communications lines. A cable (ex. BC16E-25) must be ordered
with each terminal unless otherwise provided.
___________________________________________________________________________
Step 10 Two internal VAXBI channels included with system.
I/O Expansion Maximum six VAXBI channels per system. Six VAXBI slots
and 26 panel units are available for expansion. The total
number of processors, VAXBI channels, and 32-Mbyte memory
modules cannot exceed 14.
-----------------------------------------------------------
External Third DWMBA-BB Adds third VAXBI channel; maximum one per
VAXBI Channel system. Includes H9657-EC/ED VAXBI
Expansion CAbinet and H9657-EU VAXBI
Expansion Kit. Provides five VAXBI slots
and 52 panel units and space for additional
channels/slots.
-----------------------------------------------------------
External Fourth,DWMBA-CA Adds fourth, fifth or sixth VAXBI channels;
Fifth, or Sixth maximum three per system. Includes H9657-EU
VAXBI Channel VAXBi Expansion Kit. Provides five VAXBI
slots. Requires DWMBA-BA/BB third VAXBI
channel.
____________________________________________________________________________
Step 11 Before adding VAXBI options to the system, determine the
Configuring available mounting space and power requirements from
Information the following tables; see VAXBI Options Requirements
Page in this section.
------------------------------------------------------------
VAX Fileserver 6310/6320 Base Systems
5V 12V -12V -5.2V -2V Nodes PU
____________________________________________________________________________
VAXBI Channel #1,#2 10 VAXBI Slots 86.00 4.00 2.40 20.00 7.00 29
____________________________________________________________________________
USED
____________________________________________________________________________
DEBNA 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 1
____________________________________________________________________________
KDB50 2 VAXBI Slots 11.94 0.03 0.00 3.76 0.14 1 2
____________________________________________________________________________
TK70 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 0
____________________________________________________________________________
AVAILABLE 6 VAXBI Slots 60.62 3.97 2.40 16.24 6.86 26
____________________________________________________________________________
VAX 6300 SERIES ULTRIX-32 SYSTEMS
---------------------------------
Step 1 Select appropriate system and part number. All VAX 6300
Systems Series Systems include a TK70 load device. A system device
is required for a fully supported system. For optimum
backup performance, a high-capacity tape drive is recommended.
If system does not include appropriate devices, it may not
be maintainable. Contact local Field Service for details.
-----------------------------------------------------------
All ULTRIX-32 Systems include
-Integral Floating Point
-Two VAXBI Channels
-DEBNA 802.3/Ethernet Communications Interface
-KDB50 Disk Controller
-TK70 Tape Drive and Interface
-One Full Year Product Warranty*
Select appropriate System and part number.
----------------------------------
| VAX 6310 ULTRIX-32 Base System |
----------------------------------
63AMB-EJ One-year ULTRIX-32, 64-User Upgrade,
and DECnet-ULTRIX Licenses
63AMB-BJ Paid-up ULTRIX-32, 64-User Upgrade,
and DECnet-ULTRIX Licenses
-VAX 6310 Processor
-32 Mbytes 1M-chip ECC MOS Memory
----------------------------------
| VAX 6320 ULTRIX-32 Base System |
---------------------------------
63AMB-EJ One-year ULTRIX-32, 64-User Upgrade,
and DECnet-ULTRIX Licenses
63AMB-BJ Paid-up ULTRIX-32, 64 User Upgrade,
and DECnet-ULTRIX Licenses
-VAX 6320
-32 Mbytes 1M-chip ECC MOS Memory
___________________________________________________________________________
Step 2 Select a system device and back-up device from the
Mass Storage following table.
---------------------------------------------------------
Suggested System Device Backup Device
---------------------------------------------
TU81-Plus
---------------------------------------------
RA60 (1 Disk/4 HI Cab) RA60-FD
TU81E-BB
---------------------------------------------
RA82 (1 Disk/No Cab*) RA82-AD
TU81E-BB
---------------------------------------------
SA482 (4 Disks/SA Cab) SA482-AD
TU81E-BB
---------------------------------------------
SA600**(4 Disks/SA Cab) SA600-HD
TU81E-BB
---------------------------------------------
SA600**(8 Disks/SA Cab) SA600-JD
TU81E-BB
---------------------------------------------
*RA82-AA/AD configured in TU81E cabinet.
**Cables required, see SA600 description in Section 6.
________________________________________________________________________
Step 3 ULTRIX-32, 64-User Upgrade, and DECnet-ULTRIX licenses
Software included with systems. Select media and documentation
and Startup Service Packages; refer to Section 13, Software,
and Chapter 14, Services for details. Order media and
documentation separately for qualified layered products
at no charge when Startup Service Package is purchased.
-----------------------------------------------------
Media and QA-VEYAB-H5 ULTRIX-32 Media and Documentation
Documentation recommended for the first VAX system of
each CPU type.
QA-VEYAY-H5 ULTRIX-32 64 User Media and Documentation
QA-716AA-H5 DECXnet-ULTRIX Media and Documentation
--------------------------------------------------------
________________________________________________________________________
Step 4 Select additional memory and battery backup if required.
CPU Options System can be expanded to a maximum of 128 Mbytes.
--------------------------------------------------------
32 Mbytes of MS62A-AB One included; maximum four per system.
Memory Total number of memory boards must
equal one, two or four.
-------------------------------------------------------
Battery Backup H7231-N Maximum one per system.
________________________________________________________________________
Step 5 DEBNA Ethernet Controller included with each system.
Communications Select additional devices if required. Connection of
Devices system to Ethernet requires an Ethernet transceiver
cable (ex. BNE3L-20) and an H4005 or port on a DELNI.
See Networks and Communications Buyer's Guide for details.
---------------------------------------------------------
DEBNA 802.3/ DEBNA-M One included; maximum two per VAXBI channel,
Controller three per system. Connection of
system to Ethernet requires a transceiver
cable (ex. BNE3L-20). Internal VAXBI
channels are limited to a total of three
H4005 connections. Additional internal
connections require a port on a DELNI and
cannot be directly connected to an H4005.
DEBNA Cab Kits CK-DEBNA-LD Required with DEBNA-M if placed on internal
VAXBI channel.
CK-DEBNA-LJ Required with DEBNA-M if placed on external
VAXBI channel.
-------------------------------------
DECserver 550 DSRVS-** Each terminal server requires an Ethernet
DECserver 200 DSRVB-** transceiver cable (BNE3L-20) and an H4005
or port on a DELNI. See the Networks and
Communications Buyer's Guide for ordering
information; additional items (BN20*-2E
and CX***-A* for DSRVS and QA-VCBAA-HM for
DSRVB) are required.
----------------------------------------------------------
DMB32/DHB32 Total of two DMB32s/DHB32s per CPU cabinet; maximum four
Controllers per external VAXBI channel. Total of eight DMB32s/DHB32s
per system.
----------------------------------------------------------
DMB32 DMB32-M Eight-line asynchronous communications/
printer controller.
DMB32 Cab Kit CK-DMB32-LJ Required with DMB32-M.
DHB32 DHB32-M 16-line asynchronous communications
controller.
DHB32 Cab Kits CK-DHB32-AJ Required with DHB32-M for EIA-232 connection.
CK-DHB32-LJ Required with DHB32-M for DEC-423 connection.
-----------------------------------------------------------
___________________________________________________________________________
Step 6
Additional Mass Select additional mass storage devices as required.
Storage -----------------------------------------------------------
VAXBI Disk KDB50-C One included with system. Maximum two per
Controller VAXBI channel; eight per system.
-----------------------------------------------------------
RA Disks/ Maximum four disk drives per KDB50. See RA60/82 and
Storage Arrays SA482/550/600/650 descriptions for ordering information.
-----------------------------------------------------------
RV20 Optical Maximum two RV20 masters/TU81-Plus tapes per VAXBI channel;
Disk four per system. Maximum three additional RV20 slaves per RV20
master. See RV20 description for ordering information.
-----------------------------------------------------------
TU81-Plus Tape TU81E-BB Maximum two TU81-Plus tapes/RV 20 masters
Drive per VAXBI channel; maximum four per system
(cables included).
___________________________________________________________________________
Step 7 A hardcopy console terminal is required unless otherwise
Console available.
Terminal -----------------------------------------------------------
VT3*0-** Suggested Video Terminal
LA75-** Suggested Local Printer
___________________________________________________________________________
Step 8 Select lineprinters as required. Lineprinters must connect
Lineprinters to an asynchronous line or DMB32 printer port. See ULTRIX-32
SPD.
___________________________________________________________________________
Step 9 Select terminals as required equal to the number of
Terminals communications lines. A cable (ex. BC16E-25) must be ordered
with each terminal unless otherwise provided.
___________________________________________________________________________
Step 10 Two internal VAXBI channels included; maximum six VAXBI
I/O Expansion channels per system. Six VAXBI slots and 26 panel units
are available for expansion.
-----------------------------------------------------------
External Third DWMBA-BB Adds third VAXBI channel; maximum one per
VAXBI Channel system. Includes H9657-EC/ED VAXBI
Expansion Cabinet and H9657-EU VAXBI
Expansion Kit. Provides five VAXBI slots
and 52 panel units and space for additional
channels/slots.
-----------------------------------------------------------
External Fourth,DWMBA-CA Adds fourth, fifth or sixth VAXBI channels;
Fifth, or Sixth maximum three per system. Includes H9657-EU
VAXBI Channel VAXBi Expansion Kit. Provides five VAXBI
slots. Requires DWMBA-BA/BB third VAXBI
channel.
____________________________________________________________________________
Step 11 Before adding VAXBI options to the system, determine the
Configuring available mounting space and power requirements from
Information the following tables; see VAXBI Options Requirements
Page in this section.
------------------------------------------------------------
VAX 6310/6320 ULTRIX-32 Systems
5V 12V -12V -5.2V -2V Nodes PU
____________________________________________________________________________
VAXBI Channel #1,#2 10 VAXBI Slots 86.00 4.00 2.40 20.00 7.00 29
____________________________________________________________________________
USED
____________________________________________________________________________
DEBNA 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 1
____________________________________________________________________________
KDB50 2 VAXBI Slots 11.94 0.03 0.00 3.76 0.14 1 2
____________________________________________________________________________
TK70 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 0
____________________________________________________________________________
AVAILABLE 6 VAXBI Slots 60.62 3.97 2.40 16.24 6.86 26
____________________________________________________________________________
VAX FILESERVER 6300 SERIES ULTRIX-32 SYSTEMS
--------------------------------------------
Step 1 Select appropriate system and part number. All VAX 6300
Systems Series Systems include a TK70 load device. A system device
is required for a fully supported system. For optimum
backup performance, a high-capacity tape drive is recommended.
If system does not include appropriate devices, it may not
be maintainable. Contact local Field Service for details.
--------------------------------------------------------
All VAX Fileserver 6300 Series ULTRIX-32 Base Systems include
-Integral Floating Point
-32 Mbytes 1M-chip ECC MOS memory
-Two VAXBI Channels
-DEBNA Ethernet Communications Interface
-KDB50 Disk Controller
-TK70 Tape Drive and Interface
-Paid-up ULTRIX-32 Two User Base License
-Paid-up DECnet-ULTRIX License
-Paid-up ULTRIX-32 Base Server License
-One Full Year Product Warranty*
---------------------------------------
|VAX Fileserver 6310 ULTRIX-32 System |
---------------------------------------
63AMP-BJ
---------------------------------------
|VAX Fileserver 6320 ULTRIX-32 System |
---------------------------------------
63BMN-BJ
*Standard Warranty recommended, see Services section.
___________________________________________________________________________
Step 2
Mass Storage For Base Fileserver systems select a system device and back-up
device from the following table.
---------------------------------------------------------
Suggested System Device Backup Device
---------------------------------------------
TU81-Plus
---------------------------------------------
RA60 (1 Disk/4 HI Cab) RA60-FD
TU81E-BB
---------------------------------------------
RA82 (1 Disk/No Cab*) RA82-AD
TU81E-BB
---------------------------------------------
SA482 (4 Disks/SA Cab) SA482-AD
TU81E-BB
---------------------------------------------
SA600**(4 Disks/SA Cab) SA600-HD
TU81E-BB
---------------------------------------------
SA600**(8 Disks/SA Cab) SA600-JD
TU81E-BB
---------------------------------------------
*RA82-AA/AD configured in TU81E cabinet.
**Cables required, see SA600 Description in Section 6.
________________________________________________________________________
Step 3 Paid-up ULTRIX-32 two user, DECnet-ULTRIX, and ULTRIX-32
Software Base Server Licenses included. Select media and documentation
and Startup Service Packages; refer to Section 13, Software,
and Section 14, Services for details. Order media and
documentation separately for qualified layered products
at no charge when Startup Service Package is purchased.
-----------------------------------------------------
Media and QA-VEYAB-H5 ULTRIX-32 Media and Documentation
Documentation QA-716AA-H5 DECnet-ULTRIX Media and Documentation
--------------------------------------------------------
________________________________________________________________________
Step 4 Select additional memory and battery backup if required.
CPU Options Systems can be expanded to a maximum of 128 Mbytes.
32 Mbytes of --------------------------------------------------------
Memory MS62A-AB One included; maximum four per system.
Total number of memory boards must equal
one, two, or four.
-------------------------------------------------------
Battery Backup H7231-N Maximum one per system.
________________________________________________________________________
Step 5 DEBNA Ethernet Controller included with each system.
Comm Devices Select additional devices if required. Connection of
system to Ethernet requires an Ethernet transceiver
cable (ex. BNE3L-20) and an H4005 or port on a DELNI.
See Networks and Communications Buyer's Guide for details.
---------------------------------------------------------
DEBNA 802.3/ DEBNA-M One included; maximum two per VAXBI channel,
Controller three per system. Connection of system
to Ethernet requires a transceiver
cable (ex. BNE3L-20). Internal VAXBI
channels are limited to a total of three
H4005 connections. Additional internal
connections require a port on a DELNI and
cannot be directly connected to an H4005.
DEBNA Cab Kits CK-DEBNA-LD Required with DEBNA-M if placed on internal
VAXBI channel.
CK-DEBNA-LJ Required with DEBNA-M if placed on external
VAXBI channel.
-------------------------------------
DECserver 550 DSRVS-** Each terminal server requires an Ethernet
DECserver 200 DSRVB-** transceiver cable (BNE3L-20) and an H4005
or port on a DELNI. See the Networks and
Communications Buyer's Guide for ordering
information; additional items (BN20*-2E
and CX***-A* for DSRVS and QA-VCBAA-HM for
DSRVB) are required.
----------------------------------------------------------
DMB32/DHB32 Total of two DMB32s/DHB32s per CPU cabinet; maximum four
Controllers per external VAXBI channel. Total of eight DMB32s/DHB32s
per system.
----------------------------------------------------------
DMB32 DMB32-M Eight-line asynchronous communications/
printer controller. No synchronous line
support.
DMB32 Cab Kit CK-DMB32-LJ Required with DMB32-M.
DHB32 DHB32-M 16-line asynchronous communications
controller.
DHB32 Cab Kits CK-DHB32-AJ Required with DHB32-M for EIA-232 connection.
CK-DHB32-LJ Required with DHB32-M for DEC-423 connection.
-----------------------------------------------------------
___________________________________________________________________________
Step 6
Additional Mass Select additional mass storage devices as required.
Storage -----------------------------------------------------------
VAXBI Disk KDB50-C One included with system. Maximum two per
Controller VAXBI channel, eight per system (cables
included).
-----------------------------------------------------------
RA Disks/ Maximum four disk drives per KDB50. See RA60/82 and
Storage Arrays SA482/550/600/650 descriptions for ordering information.
-----------------------------------------------------------
RV20 Optical Maximum two RV20 masters/TU81-Plus tapes per VAXBI channel;
Drive four per system. Maximum three additional RV20 slaves per RV20
master. See RV20 description for ordering information.
-----------------------------------------------------------
TU81-Plus Tape TU81E-BB One included with Preconfigured system.
Drive Maximum two TU81-Plus tapes/RV20 masters
VAXBI channel; four per system (cables
included).
___________________________________________________________________________
Step 7 A hardcopy console terminal is required unless otherwise
Console available.
Terminal -----------------------------------------------------------
VT3*0-** Suggested Video Terminal
LA75-** Suggested Local Printer
___________________________________________________________________________
Step 8 Select lineprinters as required. Lineprinters must connect
Lineprinters to an asynchronous line or DMB32 printer port. See ULTRIX-32
SPD.
___________________________________________________________________________
Step 9 Select terminals as required equal to the number of
Terminals communications lines. A cable (ex. BC16E-25) must be ordered
with each terminal unless otherwise provided.
___________________________________________________________________________
Step 10 Two internal VAXBI channels included with system.
I/O Expansion Maximum six VAXBI channels per system. Six VAXBI slots
and 26 panel units are available for expansion.
-----------------------------------------------------------
External Third DWMBA-BB Adds third VAXBI channel; maximum one per
VAXBI Channel system. Includes H9657-EC/ED VAXBI
Expansion Cabinet and H9657-EU VAXBI
Expansion Kit. Provides five VAXBI slots
and 52 panel units and space for additional
channels/slots.
-----------------------------------------------------------
External Fourth,DWMBA-CA Adds fourth, fifth or sixth VAXBI channels;
Fifth, or Sixth maximum three per system. Includes H9657-EU
VAXBI Channel VAXBi Expansion Kit. Provides five VAXBI
slots. Requires DWMBA-BB third VAXBI
channel.
____________________________________________________________________________
Step 11 Before adding VAXBI options to the system, determine the
Configuring available mounting space and power requirements from
Information the following tables; see VAXBI Options Requirements
Page in this section.
------------------------------------------------------------
VAX Fileserver 6310/6320 Base Systems
5V 12V -12V -5.2V -2V Nodes PU
____________________________________________________________________________
VAXBI Channel #1,#2 10 VAXBI Slots 86.00 4.00 2.40 20.00 7.00 29
____________________________________________________________________________
USED
____________________________________________________________________________
DEBNA 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 1
____________________________________________________________________________
KDB50 2 VAXBI Slots 11.94 0.03 0.00 3.76 0.14 1 2
____________________________________________________________________________
TK70 1 VAXBI Slot 6.72 0.00 0.00 0.00 0.00 1 0
____________________________________________________________________________
AVAILABLE 6 VAXBI Slots 60.62 3.97 2.40 16.24 6.86 26
____________________________________________________________________________
States - European 50Hz - 60Hz
-----------------------------
Note that Pre-configured package systems are set to no print
in European price files.
VAX 6310 SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47B-AK/AN KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 1-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
SV-6B47B-AL/AM KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 1-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22A-AK/AN KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22A-AL/AM KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63AMB-AE/AJ KDB50 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63AMB-DE/DJ KDB50 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
63AMB-BE/BJ KDB50 32MB Ethernet ---- ULTRIX 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet Return to
Paidup Factory
63AMB-EE/EJ KDB50 32MB Ethernet ---- ULTRIX 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet Return to
Rental Factory
VAXcluster SBBs
63ACB-AP/AT CIBCA 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63ACB-DP/DT CIBCA 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6320 32MB SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47A-BK/BN KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47A-BL/BM KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22A-BK/BN KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22A-BL/BM KDB50 32MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63BMA-AE/AJ KDB50 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63BMA-DE/DJ KDB50 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
63BMA-BE/BJ KDB50 32MB Ethernet ---- ULTRIX 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet Return to
Paidup Factory
63BMA-EE/EJ KDB50 32MB Ethernet ---- ULTRIX 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet Return to
Rental Factory
VAXcluster SBBs
63BCA-AP/AT CIBCA 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63BCA-DP/DT CIBCA 32MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6320 64MB SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47B-BK/BN KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47B-BL/BM KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22B-BK/BN KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22B-BL/BM KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63BMB-AE/AJ KDB50 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63BMB-DE/DJ KDB50 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
63BMB-BE/BJ KDB50 64MB Ethernet ---- ULTRIX 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet Return to
Paidup Factory
63BMB-EE/EJ KDB50 64MB Ethernet ---- ULTRIX 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet Return to
Rental Factory
VAXcluster SBBs
63BCB-AP/AT CIBCA 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63BCB-DP/DT CIBCA 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6330 SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47A-CK/CN KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 3-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47A-CL/CM KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 3-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22A-CK/CN KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22A-CL/CM KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 2-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63CMA-AE/AJ KDB50 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63CMA-DE/DJ KDB50 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
VAXcluster SBBs
63CCA-AP/AT CIBCA 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63CCA-DP/DT CIBCA 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6340 64MB SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47A-DK/DN KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47A-DL/DM KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22A-DK/DN KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22A-DL/DM KDB50 64MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63DMA-AE/AJ KDB50 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63DMA-DE/DJ KDB50 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
VAXcluster SBBs
63DCA-AP/AT CIBCA 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63DCA-DP/DT CIBCA 64MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6340 128MB SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47B-DK/DN KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47B-DL/DM KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22B-DK/DN KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22B-DL/DM KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63DMB-AE/AJ KDB50 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63DMB-DE/DJ KDB50 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
VAXcluster SBBs
63DCB-AP/AT CIBCA 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63DCB-DP/DT CIBCA 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6350 SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47A-EK/EN KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47A-EL/EM KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22A-EK/EN KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22A-EL/EM KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63EMA-AE/AJ KDB50 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63EMA-DE/DJ KDB50 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
VAXcluster SBBs
63ECA-AP/AT CIBCA 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63ECA-DP/DT CIBCA 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAX 6360 SYSTEMS
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47A-FK/FN KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B47A-FL/FM KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
SV-6B22A-FK/FN KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Paid-up Factory
TK70
SV-6B22A-FL/FM KDB50 128MB Ethernet LA100 VMS 1 Year
(60HZ/50HZ) 4-RA90 (DEBNA) and DECnet E/N Return to
TU81-Plus Stand Rental Factory
TK70
Standalone SBBs
63FMA-AE/AJ KDB50 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Paidup Factory
63FMA-DE/DJ KDB50 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet E/N Return to
Rental Factory
VAXcluster SBBs
63FCA-AP/AT CIBCA 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Paidup Factory
63FCA-DP/DT CIBCA 128MB Ethernet ---- VMS 1 Year
(60HZ/50HZ) TK70 (DEBNA) DECnet F/F Return to
Rental Factory
VAX 6300 SYSTEM DESCRIPTIONS
RTVAX SYSTEMS
rtVAX 6310
63AMP-CE/CJ DRB32 32MB Ethernet ---- VAXELN 1 Year
(60HZ/50HZ) TK70 (DEBNA) Runtime Return to
Paidup Factory
rtVAX 6320
63BMN-CE/CJ DRB32 32MB Ethernet ---- VAXELN 1 Year
(60HZ/50HZ) TK70 (DEBNA) Runtime Return to
Paidup Factory
rtVAX 6330
63CMN-CE/CJ DRB32 64MB Ethernet ---- VAXELN 1 Year
(60HZ/50HZ) TK70 (DEBNA) Runtime Return to
Paidup Factory
rtVAX 6340
63DMN-CE/CJ DRB32 128MB Ethernet ---- VAXELN 1 Year
(60HZ/50HZ) TK70 (DEBNA) Runtime Return to
Paidup Factory
VAX 6300 SYSTEM DESCRIPTIONS
VAXFILESERVER CONFIGURATIONS
VAXFileserver 6310
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47P-AK/AN KDB50 32MB Ethernet LA100 VMS (1) 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and Return to
TU81-Plus Stand Factory
TK70
SU-6B47P-AK/AN KDB50 32MB Ethernet LA100 ULTRIX (2) 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and Return to
TU81-Plus Stand Factory
TK70
Standalone SBBs
63AMP-AE/AJ KDB50 32MB Ethernet ---- VMS (1) 1 Year
(60HZ/50HZ) TK70 (DEBNA) Return to
Factory
63AMP-BE/BJ KDB50 32MB Ethernet ---- ULTRIX (2) 1 Year
(60HZ/50HZ) TK70 (DEBNA) Return to
Factory
VAXFileserver 6320
Storage Comm.
Devices Mem. Device Console Software Warranty
Pre-Configured ------- ---- ------ ------- -------- --------
SV-6B47N-BK/BN KDB50 32MB Ethernet LA100 VMS (1) 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and Return to
TU81-Plus Stand Factory
TK70
SU-6B47N-BK/BN KDB50 32MB Ethernet LA100 ULTRIX (2) 1 Year
(60HZ/50HZ) 4-RA82 (DEBNA) and Return to
TU81-Plus Stand Factory
TK70
Standalone SBBs
63BMN-AE/AJ KDB50 32MB Ethernet ---- VMS (1) 1 Year
(60HZ/50HZ) TK70 (DEBNA) Return to
Factory
63BMN-BE/BJ KDB50 32MB Ethernet ---- ULTRIX (2) 1 Year
(60HZ/50HZ) TK70 (DEBNA) Return to
Factory
(1) (2)
VAX/VMS VAXSERVER LIC PU VMS/ULTRIX CONNECTION ULT 2-USER BASE LIC
VMS DECNET F/F PU RMT SYS MGR V2 LIC W/WARR DECNET ULTRIX LIC
VAXCLUSTER LIC PU VAX DIST NAME SER LIC W/WARR 2-USR BASE SERVER LIC
VAX ETHERNIM N/W MNT APPL VAX DIST FILE SER LIC W/WARR
VAX DIST QUE SER LIC W/WARR
VAX 6300 SYSTEM DESCRIPTIONS
PERFORMANCE ENHANCEMENT PACKAGES (Upgrades)
63BUN-AE 6310 SVR-6320 SVR VMS UPG
63BUN-BE 6310 SVR-6320 SVR ULTX UPG
63AUC-AE 6310 SVR-6310 VMS PDUP
63AUC-BE 6310 SVR-6310 ULTRIX PDUP
63BUC-AE 6320 SVR-6320 VMS PDUP
63BUC-BE 6320 SVR-6320 ULTRIX PDUP
Model Number Description
------------ -----------
63BUA-AE 6310-6320 32MB VMS UPG PDUP
63BUA-DE 6310-6320 32MB VMS UPG PPL
63CUA-AE 6320-6330 VMS UPG PDUP
63CUA-DE 6320-6330 VMS UPG PPL
63DUA-AE 6330-6340 64MB VMS UPG PDUP
63DUA-DE 6330-6340 64MB VMS UPG PPL
63EUA-AE 6340-6350 VMS UPG PDUP
63EUA-DE 6340-6350 VMS UPG PPL
63FUA-AE 6350-6360 VMS UPG PDUP
63FUA-DE 6350-6360 VMS UPG PPL
63BUA-BE 6310-6320 ULTRIX UPG PDUP
63BUA-EE 6310-6320 ULTRIX UPG PPL
63BUD-AE 6210-6320 32MB VMS UPG PDUP
63BUD-DE 6210-6320 32MB VMS UPG PPL
63CUB-AE 6220-6330 VMS UPG PDUP
63CUB-DE 6220-6330 VMS UPG PPL
63DUC-AE 6230-6340 64MB VMS UPG PDUP
63DUC-DE 6230-6340 64MB VMS UPG PPL
63EUB-AE 6240-6350 VMS UPG PDUP
63EUB-DE 6240-6350 VMS UPG PPL
TK70 UPGRADE KIT (for VAX 6200)
Model Number Description
------------ -----------
TBK70-UA TK50-TK70 UPGRADE KIT
Distribution List:
NAME: LESLIE DOCHERTY @AYO <DOCHERTY.LESLIE AT A1 AT AYOV26 AT AYO>,
NAME: JOHN VEITCH @AYO <VEITCH.JOHN AT A1 AT AYOV26 AT AYO>,
NAME: CHRIS FLOYD@AYO <FLOYD.CHRIS AT A1 AT AYOV26 AT AYO>,
NAME: STEPHEN CRAIG @AYO <CRAIG.STEPHEN AT A1 AT AYOV26 AT AYO>,
NAME: RICHARD GELVIN @AYO <GELVIN.RICHARD AT A1 AT AYOV26 AT AYO>,
NAME: JOHN MORRISON@AYO <MORRISON.JOHN AT A1 AT AYOV26 AT AYO>,
NAME: ALAN WALKER@AYO <WALKER.ALAN AT A1 AT AYOV26 AT AYO>,
NAME: ISSAH ZENUWAH @AYO <ZENUWAH.ISSAH AT A1 AT AYOV26 AT AYO>,
NAME: JOHN MCNULTY @AYO <MCNULTY.JOHN AT A1 AT AYOV26 AT AYO>,
NAME: JOHN MCCORMACK @AYO <MCCORMACK.JOHN AT A1 AT AYOV26 AT AYO>,
NAME: Les Henderson @AYO <HENDERSON.LES AT A1 AT AYOV26 AT AYO>,
NAME: GORDON FITZSIMMONS @AYO <FITZSIMMONS.GORDON AT A1 AT AYOV26 AT AYO>,
NAME: JOHN DUNLOP @AYO <DUNLOP.JOHN AT A1 AT AYOV26 AT AYO>,
TONY ADAIR @AYO,
NAME: DANNY MCGEACHY @AYO <MCGEACHY.DANNY AT A1 AT AYOV26 AT AYO>,
ALISON JOHNSON@EOO,
KIRSTY SCOTT@AYO,
MARCO PINNA@GBI,
FIONA MACNEILL@SBP,
PASCAL METOYER@PAO,
ULF KNUTSSON@SOO,
MICHAEL SODERBERG @SOO,
NAME: LESLIE DOCHERTY @AYO <DOCHERTY.LESLIE AT A1 AT AYOV26 AT AYO>,
CHANTAL JOUVENOT @TDC,
NISSIM FEDIDA @ISO,
FRIEDRICH KRAUS @MGO,
RUDI PILL @MGO,
NAME: PETER KNIGHT@AYO <KNIGHT.PETER AT A1 AT AYOV26 AT AYO>,
JOHN THOMSON@UBO,
NAME: RICHARD GELVIN @AYO <GELVIN.RICHARD AT A1 AT AYOV26 AT AYO>,
NICK JACOBS @RDL,
BRUNO BERNING @UNT,
STEVE DANTON @USH,
GEORG ZIEGLER @SUO,
JOHN CASHMAN @DBO,
CATHERINE KAUFMANN @ZUO,
RAINER PFANDKE @MUT,
CHRISTOPHE CARREAU @AEO,
CHANTAL PIETROKOWSKY @AEO,
JIM BUTLER @SBP,
NAME: STEPHEN CRAIG @AYO <CRAIG.STEPHEN AT A1 AT AYOV26 AT AYO>,
HUBERT ZELLER @FRS,
HEINZ WEBER @COO,
ROD WEBB @ESO,
NAME: ALAN WALKER@AYO <WALKER.ALAN AT A1 AT AYOV26 AT AYO>,
VAN-BAC VU @EVB,
CEES VERBAAN @UTO,
WILLY TILMANS @BRO,
DAVID TARR @KRR,
THEO STREICHER @VNO,
BENGT STAHL @GOO,
HANS SODERLUND @SOO,
RUDOLF SIEGEL @NBO,
DETLEF SCHULZE @HAO,
HEINER SCHMIDT @FRN,
IVANO SANTAMBROGIO @MIO,
TOD RILEY @DBO,
LES RENCONTRE @OLO,
HUBERT REISENAUER @VNO,
VITTORIO RE @TNO,
MAHENDRA RAVAL @LDO,
NAME: CAMPBELL RAMSAY @AYO <RAMSAY.CAMPBELL AT A1 AT AYOV26 AT AYO>,
PHILIPPE POLROT @PAO,
NEDRA PILLOW @HLO,
LOTHAR PFAFF @FRA,
MATTI PATARI @FNO,
JOSE OLIVEIRA @XIP,
KENNETH OERKE @SQO,
ROBERT NICOLAS @PAO,
CLAUDE MOSCARDO @PAO,
NAME: JOHN MORRISON@AYO <MORRISON.JOHN AT A1 AT AYOV26 AT AYO>,
CHARLES MONK @RDL,
CHRIS MITCHELL @BSO,
PAUL MILLS @WLO,
JEAN MICHEL @PAO,
NAME: HARRY MCCORMICK@AYO <MCCORMICK.HARRY AT A1 AT AYOV26 AT AYO>,
NAME: JOHN MCCORMACK @AYO <MCCORMACK.JOHN AT A1 AT AYOV26 AT AYO>,
MICK MADDY @BIO,
GORDON LYNCH @EDO,
MARTIN LOMAS @RDL,
HEINZ KOTTMANN @COO,
PAULI KARJALAINEN @FNO,
STEVE JONES @VBO,
JAN JOHANSEN @NWO,
THEIS JENSEN @DMO,
THEIS PASSER JENSEN @DMO,
NAME: Les Henderson @AYO <HENDERSON.LES AT A1 AT AYOV26 AT AYO>,
GHISLAIN GUYOLLOT @ETO,
EMILIO GONZALEZ @ZQO,
SVEN FREESE @MGO,
NAME: GORDON FITZSIMMONS @AYO <FITZSIMMONS.GORDON AT A1 AT AYOV26 AT AYO>,
CHRISTIAN DURIEZ@LYO,
KRIS DEROECK @BRO,
TOM VAN DER ZWET @GWO,
BERTH-AKE DAHLGREN @UGO,
CTSLZO @LZO,
ROB CODNER @ISO,
ERIC CLAUDE @ZUO,
GUIDO CALABRESE @RIO,
STEVE BUXTON @VBE,
RICHARD BUSSEY @HHL,
GILLES BRAVARD @GVO,
JOHAN ULLENIUS@SOO,
NOLAN BENNETT @NWO,
ROLF BENGTSSON @SOO,
HANS-DIETER BENDER @HBO,
NAME: Bobby Bell @AYO <BELL.BOBBY AT A1 AT AYOV26 AT AYO>,
DETLEF BEIER @BEO,
MIKE ASHFORD @HHL,
LARRY AMBROSE @ACO
| |||||
| 17.6 | KERNEL::MOUNTFORD | Thu Jul 13 1989 16:34 | 301 | ||
VAX 6300/VAXSERVER 6300 SYSTEM MAINTENANCE ADVISORY
1.0 Purpose of Document
This document provides a general description of the VAX 6300 and
Vaxserver 6300 systems. VAX 6300 is an enhanced VAX 6200 system.
It is intended as a guide to assist VAX 6200 trained field service
engineers in the maintenance of the VAX 6300.
2.0 Product Description
The VAX 6300 systems are based on the existing VAX 6200 series of
systems. The VAX 6300 CPU module is an enhancement to the VAX 6200
module that results in an increase in speed of approximately 33% (over
the VAX 6200). VAX 6300 systems will be offered in 1 to 6 CPU
configurations, VAX 6310 to VAX 6360.
The VAX 6300 will also be offered in a Vaxserver configuration.
Vaxserver 6300s will be offered in 1 and 2 CPU processor config-
urations.
Logins will be limited on the Vaxserver systems. If there are no
current logins and a login is established on the system console no
other logins will be permitted. However if there are no current
logins and a login is established via a remote terminal, one more login
is permitted via the system console. Logins are intended primarily for
system management purposes.
An unlimited number of users will be able to access the Vaxserver
files via file server protocol from their host system.
2.1 VAX 6200/6300 Differences Overview
The VAX 6300 systems are based on the the VAX 6200 systems. The
performance enhancements include a faster CVAX CPU and CFPA by
shrinking CMOS I to CMOS II and changing the clock crystals from 50
MHZ to 66.67 MHZ. Additionally the VAX 6200 cache RAMs have been
replaced in the VAX 6300 by 35ns cache RAMs.
Differences between the VAX 6300 and Vaxserver 6300's are the
EPROM that contains the System Type Register. This is changed to
implement the VMS licensing restrictions. There are no other
functional differences between the VAX 6300 and Vaxserver 6300
systems.
Both the VAX 6300 and Vaxserver 6300 will also contain a TK70
console tape and a new TBK70 controller (T1035 module).
2.2 VAX 6300/Vaxserver 6300 CPU Differences
With the exception of the EPROM, the Vaxserver 6300 is functionally
the same as the VAX 6300 system. The Vaxserver is currently offered as
a single CPU configuration or a dual CPU configuration.
The differences between the VAX 6300 and Vaxserver 6300 are
summarized in Table-1 below.
-3-
Table-1
-------
VAX 6300 VAXSERVER 6300
----------------------------------------------------------------
Elements | KA62B-AA | KA62B-AB
----------------------------------------------------------------
CPU Module | T2011-YA | T2011-YC
----------------------------------------------------------------
Console PROM | 23-016E9-00 | 23-017E9-00
----------------------------------------------------------------
2.3 Mixed Configurations
No combinations of VAX 6200 (T2011-00), Vaxserver 6200 (T2011-YB),
VAX 6300 (T2011-YA), and Vaxserver 6300 (T2011-YC) are supported
nor recommended. Any attempt to boot such combinations will result
in unsuccessful booting or unreliable system performance.
Note: All cpu modules types installed in any single VAX 6XXX must be
of the same type.
To verify the cpu types present, use the console prompt to do
the following:
Procedure I
-----------
>>>SHOW CONFIG
Type Rev
1+ KA62A (8001) 8001 !KA62A = VAX 62XX
2+ KA62A (8001) 8001
3+ MS62A (4001) 0002
(etc.)
Note: Under SHOW CONFIG there is no distinction between the VAX 6200
and the Vaxserver 6200.
>>>SHOW CONFIG
Type Rev
1+ KA62B (8001) 8001 !KA62B = VAX 6300
2+ KA62B (8001) 8001
3+ MS62A (4001) 0002
(etc.)
>>>SHOW CONFIG
Type Rev
1+ KA62B-S (8001) 8001 !KA62B-S = VAXSERVER 6300
2+ KA62B-S (8001) 8001
3+ MS62A (4001) 0002
(etc.)
-4-
Procedure II
------------
NOTE:The cpu being checked must be selected prior to doing the
SYSTYPE register examine.
>>> SET CPU n !n=cpu node number !Selects cpu being
!examined.
>>> E/U 20040004<CR>
02310001 !VAX 6200
02310002 !VAXSERVER 6200
02400201 !VAX 6300
02400202 !VAXSERVER 6300
3. Operating Systems
3.1 VMS Vaxserver
The first version of VMS that will officially support the VAX 6300
systems is VMS V5.1.
NOTE: Under VMS V5.1 any attempt to boot a mixed configurations
of cpu modules will result in an error message after the VMS banner.
%SMP-F-CPUTYP, CPU #nn and PRIMARY CPU are of different processor
types.
3.1.1. Booting VMS with mixed cpu types VAX 6300/Vaxserver 6300.
If the first CPU is a VAX 6300 CPU and the second CPU a Vaxserver 6300,
warning messages are printed on the console during the boot sequence
and no logins are allowed on any terminal except the console.
After the VMS banner the following message is printed:
%SMP-F-CPUTYP, CPU #nn and PRIMARY CPU are of different processor
types
During the boot sequence when the licenses are loaded the
following messages are printed out:
%LICENSE-E-NOAUTH DEC VAX-VMS use is not authorized on this node
-LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
-LICENSE-I-SYSMGR, please see your system manager
If an attempt is made to login, the following message is printed out
and you are logged out on all terminals except the console:
%LICENSE-I-EXCEEDED, attempted usage exceeds active license limits
If the SHOW CPU/ALL command is type in from the console the second
CPU is in the the BOOT_REJECT state.
-5-
3.1.2. Booting VMS with mixed cpu types Vaxserver 6300/VAX 6300.
If the first CPU is a Vaxserver CPU and the second CPU is a
VAX 6300 CPU the system boots with no license warnings and 1
interactive login is allowed. The only error indications are
the SMP-F-CPUTYP warning message after the VMS banner and if the
SHOW CPU/ALL command is typed, the second CPU will be in the
BOOT_REJECT state. It will appear that you have an operational
single cpu Vaxserver system. However the integrity of the system
can not be guaranteed with this mixed configuration.
3.1.3. Booting VMS with both cpu types VAX 6300
If both CPUs were VAX 6300 CPUs the results are the same as in
3.1.1 except for the SHOW CPU/ALL command. In this case both CPUs
are in the run state.
It is very easy to see that something is wrong in examples 3.1.1.
and 3.1.3., but in example 3.1.2. the only error indication is the
SMP-F-CPUTYP message during the boot sequence. The warning message
is there but it is easy to miss. The scenario in test 3.1.2. would be
the worst case because field service and or the customer may not
realize that different CPU types have been installed in the system.
3.2 ULTRIX-32
The first version of ULTRIX that will officially support the VAX 6300
systems is V3.0.
3.3 VAX/ELN
The first version of ELN that will officially support the VAX 6300
systems is 3.2.
4.0 DIAGNOSTICS
Diagnostics for the VAX 6300 and Vaxserver 6300 will be the same
as those used on the VAX 6200 systems. The following diagnostics
will be updated to recognize the VAX 6300 systems:
ELSAA VDS
EVSBA Autosizer
ELKAX Functionality
ELKMP Calypso MP Exerciser
EVKAQ VAX Basic Instructions Exerciser
EVKAR VAX Basic Instructions Exerciser
EVKAS VAX Floating Point Instructions Exerciser
EVKAT VAX Floating Point Instructions Exerciser
EVKAU VAX Privileged Architecture Exerciser
EVKAV VAX Privileged Architecture Exerciser
Available Jan 1989, Rel. 34
----------------------------------------------------------------
-6-
5.0 MAINTENANCE
The VAX 6300 system maintenance strategy for both the VAX 6300 and
Vaxserver 6300 is the same as that established for the VAX 6200
systems. All procedures currently used for VAX 6200 systems should be
followed for the VAX 6300 systems. See section 10 for documentation
and part numbers.
6.0 FIELD SERVICE TOOLS
Software tools DIAGNOSTICS, UETP, VAXSIM, SPEAR, or RHM are the
same for both the VAX 6200 systems and the VAX 6300 systems.
7.0 SITE PREPARATION
The same site preparation procedures and considerations that were
established for the VAX 6200 systems apply to the VAX 6300 systems.
These consist of site layout, electrical, and environmental
requirements. Refer to VAX 6200 Installation Guide.
8.0 INSTALLATION
Installation of a VAX 6300 system will follow the same procedures
as outlined in the VAX 6200 Installation Guide.
9.0 CD KITS
9.1 Vaxserver 6300
The CD kit will contain two (2) EPROMs, EPROM installation
instructions, a new module label and brady markers to mark the new
module revision. P/N for the kit is A2-W1394-10.
9.2 VAX 6300
The VAX 6300 CD kit, P/N A2-W1379-10, will contain a T2011-YA cpu
module. All other parts for the VAX 6300 are common parts to the
VAX 6200.
10.0 DOCUMENTATION
Title Document Number Available
-----------------------------------------------------------------------
VAX 6200 Owner's Manual EK-620AA-OM To be updated Q4FY89
VAX 6200 Installation Guide EK-620AA-IN To be updated Q4FY89
VAX 6200 Mini-Reference Manual EK-620AA-HR To be updated Q4FY89
VAX 6200 System Technical
User's Guide EK-620AA-TM To be updated Q4FY89
VAX 6200 Options & Maintenance EK-620AA-MG To be updated Q4FY89
VAX 6200 Maintenance Prints MP-01845-01 To be updated Q3FY89
VAX 6200 Self Maintenance
Print Set MP-01848-01 To be updated Q3FY89
TBK70 Maintenance Card EK-TBK70-MC001 1/89
TBK70 Technical Manual EK-TBK70-TM001 1/89
NOTE: MP-01845-01 available to internal Digital personnel only.
| |||||
| 17.7 | CALYPSO/HYPERION RD CONNECTIONS | KERNEL::BLAND | toward 2000 ... | Thu Jul 13 1989 16:59 | 30 |
There have been some queries in the last few days regarding the
cabling of CALYPSO/HYPERION systems for RDC/RHM purposes .
Below is a configuration known to work .
---------
| | BC22D-xx ----------------- BC22F-xx
| 6200/ |--------------| A2 A1 |-------------------- CONSOLE
| 6300 | | MDS01 | TERMINAL
| | | B1 B2 |_______
--------- ----------------- | BC22F-xx
|____________ MODEM
The MDS01 comes with two BC22F-xx cables ( cant remember the length,
might be 25 feet ) . The engineer needs to disconnect the BC22D-xx
from the console terminal and plug it into A2 on the MDS01,then
connect up the two BC22F's as shown .
If the customer wants to use the "USER PORT" facility then he
will need to install another BC22F-xx between B1 and a terminal
port somewhere on the system .
Dave W & Norm Bland
| |||||
| 17.8 | * LOS Order * | KERNEL::PETTET | Norm Pettet CSC Basingstoke | Wed Jul 19 1989 11:16 | 23 |
The following Documentation is ordered, no expected delivery date
as yet.
VAX 6000-400 DOCUMENTATION ORDER
--------------------------------
# off Order no. Users Title
1 EK-640EA-IN Cust/FS VAX 6000-400 Installation Guide
1 EK-640EA-OM Cust/FS VAX 6000-400 Owner's Manual
25 EK-640EA-HR Cust/FS VAX 6000-400 Mini-Reference
1 EK-640EA-TM SMCust/FS VAX 6000-400 System Technical User's Guide
1 EK-640EA-MG SMCust/FS VAX 6000-400 Options and Maintenance
1 EK-640EA-TD FS(internal) VAX 6000-400 Proprietary Technical Reference
The following manual is not available at present
EK-640EA-UP FS VAX 6000 Series Upgrade Manual
Cheers.....Norm
| |||||
| 17.9 | Bad H7214-A | KERNEL::BLAND | toward 2000 ... | Sat Jul 22 1989 14:34 | 110 |
From: KERNEL::TIMA_MGR 13-APR-1989 11:57:20.72
To: KERNEL::BLAND
CC:
Subj: GRAM: H7214 Switching Transformer Problem (BLITZ)
The attached information is from the CSSE RAMP Group
The following information will be available in the CSSE STARS database
================================================================================
Date: 12 April, 1989
From: Pete Wishneusky
Dept: RAMP/CSSE
Loc: OGO 1-2/E13
Ext: 276-9541
Net: CSSE::WISHNEUSKY
Subject: H7214 Switching Transformer Problem
Be advised, a number of H7214-A regulators used in the 6200
series of computer products (CALYPSO) were shipped containing a
potentially non-compliant switching transformer. The part (DEC
P/N 16-26664-01) is the main (largest) transformer mounted on
the H7214-A regulator approximately in the center of the printed
circuit board. As many as 5000 transformers received from the
vendor are suspected of having reduced (insufficient) spacing
between two EMI shields (primary referenced and secondary
referenced single turn windings of copper foil) between which
three layers of insulating tape are wound. For those
transformers suspected narrower insulating tape was used and the
"creepage" distance between the two foils fails to meet IEC-435
requirements (6 mm minimum creepage).
The reduced spacing introduces a greater risk of an electrical
breakdown (primary to secondary) occurring in the transformer.
The breakdown (most likely between the shields will provide a
conduction path from the positive primary (+150 VDC) rail to DC
ground on the secondary side of the transformer, or more simply,
a primary to ground fault.
Extensive testing performed both by Engineering and CSSE has
established the occurrence of such an electrical breakdown,
although undesired, does not pose a safety hazard to either
computer users or Field Service Personnel.
Such a breakdown could, however, interfere with normal computer
operation and may contribute to unecessary computer failure.
-1-
One very likely consequence of such a transformer failure is
actuation of the input fuse local to the H7214-A. It has been
noted however, that on certain occasions, the H7214-A will
continue to provide regulated DC output power EVEN AFTER THE
INPUT FUSE HAS CLEARED. If such a condition should arise on any
given H7214-A, there is no visible indication given that the
fuse has opened and that the transformer breakdown has
occurred. It is for this reason, among others, that this BLITZ
note is sent.
It is requested (by this note) that Field Service inspect
customer systems for the presence of suspect switching
transformers in the H7214-A regulators on a "next call" basis.
If a regulator is identified as containing a suspect transformer
(see transformer datecode information below), make arrangements
to replace the regulator so that it can be sent back to Field
Service Logistics for appropriate repair. When returning a
regulator to FSL for the reason stated, be sure to indicate the
reason ("bad datecode on T3") on the accompanying Red/Yellow tag.
The suspect datecodes on the transformer are within the range
8830 to 8852. The datecode is clearly marked on the "top" of
the transformer's outer core wrappings (a white fibrous tape)
along with the DEC part number (16-26664-01). The datecode is
the last four digits in a seven digit string stamped on the
white core wrapping tape. The datecode will appear as below:
(for example): 597 - 8837
This datecode is 8837 (37th week of 1988)
For any further information regarding the problem stated above,
please contact me at the E-Net address given above, or call DTN
276-9541
-2-
==================================== END =======================================
| |||||
| 17.10 | EEPROM Patch 3.5 for Calypso | KERNEL::BLAND | toward 2000 ... | Sun Oct 22 1989 10:31 | 11 |
I have copied PATCH_V31_P35.ROM (EEPROM PATCH 3.5 for CALYPSO),
to COMICS SYS$PUBLIC. Could not copy the release notes (protected !!!).
It appears that there was a 3.4 patch that improved the diag coverage
for the CFPA. I believe that this patch has been included in 3.5.
Patch 3.5 also provides console support and booting over the ETHERNET
for the DEBNI.
Regards, Norman Bland
| |||||
| 17.11 | EEPROM Patch 4.3/4.4 for HYPERION | KERNEL::BLAND | toward 2000 ... | Sun Oct 22 1989 11:34 | 16 |
PATCH_V41_P43.ROM and PATCH_V41_P44.ROM are now available for
HYPERION.
Have protection problems with some files so I have not yet copied
any of these.
The 4.3 EEPROM patch does the same for HYPERION as the 3.4 patch
did for CALYPSO (don't think this was released).
The 4.3 patch also adds support for DEBNI but there are bugs associated
with the ETHERNET boot code.
The 4.4 EEPROM patch for HYPERION corrects the ETHERNET boot code
bugs and adds support for a new (but as far as I know, unannounced)
adapter for the XMI.
Regards, Norman Bland
| |||||
| 17.12 | We have EEPROM Patch 4.4 | KERNEL::BLAND | toward 2000 ... | Mon Oct 23 1989 18:38 | 5 |
OK the patch for Hyperion EEPROM ie PATCH_V41_P44.ROM and the release
notes 4-4_patch_notes.lis, are now in COMICS SYS$PUBLIC.
Regards, Norman Bland
| |||||
| 17.13 | SET SYSTEM SERIAL NUMBER. | KERNEL::MOUNTFORD | Fri Jan 19 1990 11:24 | 10 | |
Just to remind me as much as anything:
To change system serial number after 62??-63?? upgrade:
set term to vt100
hit ESC key
then DEL key
then type set system serial (which should then prompt for info).
| |||||
| 17.14 | Subj: VAX 6000 Module and Backplane Cleaning | COMICS::ROBB | Wed Feb 07 1990 20:33 | 64 | |
Subj: VAX 6000 Module and Backplane Cleaning
+-------------+
| | | | | | | |
|d|i|g|i|t|a|l| Product and Technology Group
| | | | | | | |
+-------------+
Interoffice Memorandum
To: 6000 Engineers Date: 6-FEB-1990
From: Peter Beddall
cc: Ext: 781 4158
Loc/mail stop: UCG Basingstoke
DECnet: COMICS::BEDDALL
Subject: VAX 6000 Backplane & Module Cleaning
Last year there were some changes made to the cleaning practices of
VAXBI, NMI and XMI modules and backplanes. Just to clear up any
confusion that may still exist in the field, this memo details the
part numbers of the NEW cleaning materials. Any of the OLD cleaning
materials should never be used and should be safely disposed of.
The old materials contained a lubricant like oil, which allowed
contaminants to stick to any newly cleaned contact surface areas,
possibly making the original problem, for which the modules were
cleaned, worse.
The NEW part numbers for the cleaning materials are:-
Gold Wipes 49-01603-02
4 segment paddle wipes 12-26321-05 (NMI Backplanes)
5 Segment paddle wipes 12-26321-06 (BI/XMI Backplanes)
Existing parts, still valid are:-
5 segment wipe handle 47-00116-02
4 segment wipe handle 47-00116-01
Solvex Gloves 29-26403-00
Old Parts that must no longer be used:-
5 Segment wipe 12-26321-03
4 segment wipe 12-26321-01
Please note that the new gold wipe part number has sometime been
quoted incorrectly as 49-01013-00. It should be 49-01603-02.
I hope this may help clear up any confusion, if not please let me
know.
regards
Pete Beddall
| |||||
| 17.15 | adapter errors with no error bits set | COMICS::ROBB | Mon Mar 19 1990 15:56 | 243 | |
PROBLEM/SOLUTION ARTICLE OUTLINE
-------------------------------------------------------------------------------
TITLE: 6000-xxx ADAPTER ERRORS WITH NO ERROR BITS SET IN REGISTERS
PRODUCT: VMS, version 5.0 5.1 5.2 5.3
6200 6300 6400 6000-400 6000-300 6000-200
LAYERED PRODUCT:
DATE: 19-MAR-1990
SYMPTOMS/PROBLEM:
Adapter errors appear in errorlog with no error bits set.
These errors appear on either or both XMI ( DWMBA ) .
Another symptom on the system may be the system loosing time.
See seperate stars article
ANALYSIS:
The error log entry from the XBI that does not have any error bits
set is the the result of multiple CRD errors experienced by the
adapter. When the XBI interrupts and the only error is a CRD error
VMS does not make an entry in the error log. Instead it includes the
error information in the internal CRD buffers. Unfortunately the
XBI remembers that another CRD (I can't remember how many it actually
remembers, probably only one) has occurred before the first has been
serviced. VMS comes along and resets the error conditions but cannot
reset the state that will cause another interrupt to occur. When the
subsequent interrupt does occur there an no error bits set.
Interrupting without an error bity being set can be an error condition
and the event is put in the error log.
Unfortunatly with CRD errors there is no entry made in errorlog
unless there is a machine check or crash at which time the CRD buffers are
flushed.
The buffers are also flushed at shutdown
CRD's are logged in a CRD buffer in memory which can hold up to 16 footprints
Providing the footprints match a previously logged footprint all that happens
is a counter is incremented for that footprint. It is therefore possible to
have thousands of CRD's without anything being visible in errorlog. The only
way to see them is to anal/sys and look at the live system or shut the system
down to cause the buffers to be flushed. It will then be possible to see them
in errorlog after the reboot.
Example errorlog entry including the shutdown flushing the CRD buffers.
******************************* ENTRY 57. *******************************
ERROR SEQUENCE 0. LOGGED ON: SID 0B000004
DATE/TIME 4-JAN-1978 09:54:52.52 SYS_TYPE 02100101
SCS NODE: SILV03 VAX/VMS V5.2
ADAPTER ERROR KA64A CPU FW REV# 4. CONSOLE FW REV# 1.0
XMI NODE # 1.
SW FLAG 00000400
NO ERROR FOUND
DWMBA DATA - XMI NODE #14.
PHYS ADR 21F00000
NODE 14.
XDEV 00022001
DWMBA
DEVICE REV = 2.
XBE 00000381
XFADR 00000C54
FAILING ADDR = 00000C54(X)
FAILING LENGTH = 0.
AREAR 61F0000C
FAILING ADDR RESPONDER = 21F0000C(X)
RESPONDER FAILING LENGTH = 1.
AESR 80410000
XBI CABLE OK
READ CMD
FAILING COMMANDER = NODE #1.
AIMR 88FFA01F
IBUS CPU DATA PE INTRPT ENABLED
IBUS DMA-B C/A PE INTRPT ENABLED
IBUS DMA-A C/A PE INTRPT ENABLED
TRANSACTION TMO INTRPT ENABLED
COMMAND NOACK/NXM INTRPT ENABLED
RER INTRPT ENABLED
RSE INTRPT ENABLED
NRR INTRPT ENABLED
CRD INTRPT ENABLED
WR DATE NOACK INTRPT ENABLED
RD/ID DATA NOACK INTRPT ENABLED
WSE INTRPT ENABLED
PARITY ERROR INTRPT ENABLED
CORRECTED CONFIRM INTRPT ENABLED
ENABLED IVINTR TRANSACTIONS
AIVINTR 00000002
IVINTR DESTINATION = 0002(X)
ADG1 00000000
BCSR 80000017
IBUS PE INTRPT ENABLED
SELF-TEST LED
BI INTLCK RD FAILURES INTRPT ENABLED
ENABLE XBI INTERRUPTS
BESR 00000010
MS TRANSACTION FAILED
BI INTERRUPT STATUS = 0.
XBI INTERRUPT STATUS = 0.
BIDR 00000002
INTERRUPT DESTINATION = 0002(X)
DIAGNOSTIC DATA = 0000(X)
BTIM 47E69198
BI DMA FAILING ADDR = 07E69198(X)
FAILING LENGTH = 1.
BVOR 00000400
XBI VECTOR OFFSET = 04(X)
BVR 00000138
XBI VECTOR = 004E(X)
BDCR1 00000000
RSVD 00000000
******************************* ENTRY 59. *******************************
ERROR SEQUENCE 2. LOGGED ON: SID 0B000004
DATE/TIME 27-FEB-1990 17:32:54.18 SYS_TYPE 02100101
SCS NODE: SILV03 VAX/VMS V5.2
ADAPTER ERROR KA64A CPU FW REV# 4. CONSOLE FW REV# 1.0
XMI NODE # 1.
SW FLAG 00000400
NO ERROR FOUND
DWMBA DATA - XMI NODE #13.
PHYS ADR 21E80000
NODE 13.
XDEV 00022001
DWMBA
DEVICE REV = 2.
XBE 00000341
XFADR 00000C54
FAILING ADDR = 00000C54(X)
FAILING LENGTH = 0.
AREAR 61E8000C
FAILING ADDR RESPONDER = 21E8000C(X)
RESPONDER FAILING LENGTH = 1.
AESR 80410000
XBI CABLE OK
READ CMD
FAILING COMMANDER = NODE #1.
AIMR 88FFA01F
IBUS CPU DATA PE INTRPT ENABLED
IBUS DMA-B C/A PE INTRPT ENABLED
IBUS DMA-A C/A PE INTRPT ENABLED
TRANSACTION TMO INTRPT ENABLED
COMMAND NOACK/NXM INTRPT ENABLED
RER INTRPT ENABLED
RSE INTRPT ENABLED
NRR INTRPT ENABLED
CRD INTRPT ENABLED
WR DATE NOACK INTRPT ENABLED
RD/ID DATA NOACK INTRPT ENABLED
WSE INTRPT ENABLED
PARITY ERROR INTRPT ENABLED
CORRECTED CONFIRM INTRPT ENABLED
ENABLED IVINTR TRANSACTIONS
AIVINTR 00000002
IVINTR DESTINATION = 0002(X)
ADG1 00000000
BCSR 80000017
IBUS PE INTRPT ENABLED
SELF-TEST LED
BI INTLCK RD FAILURES INTRPT ENABLED
ENABLE XBI INTERRUPTS
BESR 00000010
MS TRANSACTION FAILED
BI INTERRUPT STATUS = 0.
XBI INTERRUPT STATUS = 0.
BIDR 00000002
INTERRUPT DESTINATION = 0002(X)
DIAGNOSTIC DATA = 0000(X)
BTIM 47E502BC
BI DMA FAILING ADDR = 07E502BC(X)
FAILING LENGTH = 1.
BVOR 00000200
XBI VECTOR OFFSET = 02(X)
BVR 00000134
XBI VECTOR = 004D(X)
BDCR1 00000000
RSVD 00000000
******************************* ENTRY 75. *******************************
ERROR SEQUENCE 24631. LOGGED ON: SID 0B000004
DATE/TIME 27-FEB-1990 17:52:40.70 SYS_TYPE 02100101
SCS NODE: SILV03 VAX/VMS V5.2
CORRECTABLE MEMORY ERROR KA64A CPU FW REV# 4. CONSOLE FW REV# 1.0
XMI NODE # 1.
XMI NODE 8.
ECC SYND 002C
CORRECTED DATA BIT = 44.
LOWEST ADR 21C00000
HIGHEST ADR 21C00000
CRD COUNT 00000025
CRD COUNT = 37.
******************************* ENTRY 76. *******************************
ERROR SEQUENCE 24632. LOGGED ON: SID 0B000004
DATE/TIME 27-FEB-1990 17:52:40.70 SYS_TYPE 02100101
SCS NODE: SILV03 VAX/VMS V5.2
FATAL BUGCHECK KA64A CPU FW REV# 4. CONSOLE FW REV# 1.0
XMI NODE # 1.
OPERATOR, Operator requested system shutdown
******************************* ENTRY 77. *******************************
SUMMARY OF MEMORY ERRORS LOGGED BY SID 0B000004
NODE# BIT# CORRECTED UNCORRECTED
ERRORS ERRORS
08. D44 37.
SUMMARY OF ALL ENTRIES LOGGED BY SID 0B000004
MEMORY ERROR 1.
AVOLUME MOUNT 177.
SYSTEM START-UP 2.
ERRLOG.SYS CREATED 1.
SOLUTION:
If the CRD errors are excessive then identify the array causing the CRD's
and replace the array.
At some time in the future a software work around will make this second
interrupt invisible.
| |||||
| 17.16 | system loosing time | COMICS::ROBB | Mon Mar 19 1990 15:58 | 54 | |
PROBLEM/SOLUTION ARTICLE OUTLINE
-------------------------------------------------------------------------------
TITLE: Calypso / Rigel / 6000 loosing time
PRODUCT: VMS, version 5.x 6000-xxx 6000-200 6000-300 6000-400 6200 6300 6400
DATE: 19-MAR-1990
SYMPTOMS/PROBLEM:
Calypso family ( 6000 ) systems loosing time.
This time loss can be from a few minutes to hours per day. The loss can
appear to be erratic and can vary depending on the number of users on the
system
Also see stars article "6000 adapter errors with no error bits set."
ANALYSIS:
Systems with large amounts of CRD errors in a memory array can cause the system
to loose time.
CRD errors ( INT54 ) occur at IPL 26 (1A) while interval timer interrupts at
IPL 22 (16)
This can cause the system to miss interval timer interrupts while taking care
of the CRD errors.
Unfortunatly with CRD errors there is no entry made in errorlog
unless there is a machine check or crash at which time the CRD buffers are
flushed. The buffers are also flushed at shutdown
CRD's are logged in a CRD buffer in memory which can hold up to 16 footprints
Providing the footprints match a previously logged footprint all that happens
is a counter is incremented for that footprint. It is therefore possible to
have thousands of CRD's without anything being visible in errorlog. The only
way to see them is to anal/sys and look at the live system under SDA or shut
the system down to cause the buffers to be flushed.
SOLUTION:
Identify and replace memory array causing CRD errors.
If there are no errors in the errorlog it may be necessary to shut the system
down to cause the CRD buffers to flush to the errorlog. It should then be
possible to:-
$ anal/err/sum/noful
| |||||
| 17.17 | c76 in XFADR | KERNEL::ROBB | Mon Mar 26 1990 12:29 | 170 | |
How to get around the incorrect value of C76 in XFADR which is seen in quite
a number of error log entries.
See explanation in the examples.
Ken Robb.
******************************* ENTRY 400. *******************************
ERROR SEQUENCE 510. LOGGED ON: SID 0B000004
DATE/TIME 24-MAR-1990 08:55:33.79 SYS_TYPE 02100101
SCS NODE: BEVX04 VAX/VMS V5.2
MACHINE CHECK KA64A CPU FW REV# 4. CONSOLE FW REV# 1.0
XMI NODE # 2.
REVISION 00000000
SW FLAGS 00008000
00402000
XMI TTO CNAK ERROR
CACHE/VBOX SUBSYS ENABLED FOR ALL CPUS
LOGGING OFF 00000000
00000000
ACTIVE CPUS 00000004
HW REVISION 01000000
34304820
SERIAL NUMBER 30373339
38303130
RESRC DISABLE 0000
PHYS ADR 21900000
NODE 2.
XDEV 00088082
KA64A
DEVICE REV = 8.
XBE 8080A081
READ CMD
FAILING COMMANDER = NODE #2.
TRANSACTION TIMEOUT
COMMAND NOACK
PARITY ERROR
ERROR DETECTED
XFADR 00000C76 !This value appears frequently in errorlog
!while PCERR appears to have correct value
!To see what is realy in here use
!anal/err/brief which will get it correct
!See next entry for an example
FAILING ADDR = 00000C76(X)
FAILING LENGTH = 0.
XGPR 00000002
RCSR 412C0001
XCA REVISION = 1.
WRITE BUFFER ENABLED
AUTO RETRY ENABLED
SELF INVALIDATES DISABLED
XMI INTERPROCESSOR INTERRUPTS ENABLED
NORMAL TIMEOUT SELECTED: 16.77MS
CACHE RAM SPEED = FAST
CRD INTERRUPTS ENABLED
CORRECTED CONF INTERRUPTS ENABLED
THIS NODE IS BOOT PROCESSOR
COMMANDER RECEIVED NOACK
LOCKOUT TIME SELECT SET AT: 256 CYC
XDP1 PE ON XMI BUS
INTERLOCK LOCKOUT AVOIDANCE ENABLED
CONSOLE IPL = 15.
BCSTS 042A0000
CYCLE TYPE = DAL BUS
DMA CACHE FILL
PREDICTED PARITY BIT = 01(X)
BACKUP CACHE TAG COMPARE SET
PRIMARY CACHE TAG HIT (1ST HALF)
BCCTL 00000008
BACKUP CACHE TAG STORE DISABLED
PRIMARY CACHE TAG STORE DISABLED
REFRESH ENABLED
TWO CYCLE RAM SPD = FAST
BCERR 079530E8
ERROR ADDR REG: NON-APPLICABLE
PCSTS 00000888
PRIMARY CACHE DISABLED
PRIMARY CACHE REFRESH ENABLED
MICROTRAP 1 SET
BUS ERROR SET
BACKUP CACHE MISS
PCERR 21B00008
P-CACHE ERROR ADDR = 21B00008(X)
SSCBTR 00017700
DAL BUS TIMEOUT = 96000. uSEC
VINTSR 00000001
XVP UNIT PRESENT
VECTOR MODULE RESET = 0.
VECTOR INTERFACE FUNCTION ENABLED
ERROR COUNTERS
XMI TTO CNAK 00000001
STACK FRAME
FAULT CODE 80000011
MCHK FAULT CODE = 0011(X)
_DAL BUS OR DATA PE DURING READ
RESTART BIT SET
VADDR 80A64BA2
VIRTUAL ADDR = 80A64BA2(X)
VIBA 80A5D114
MBOX PREFETCH VA = 80A5D114(X)
SISR/ICCS 00400000
INTERVAL TIMER ENABLED
INTERNAL STATE 0600050E
RN = 0E(X)
OPCODE = 05(X)
EBOX DATA LEN = BYTE
ADR TYPE = READ
DELTA PC = 06(X)
SC 00000004
PC 80A5D111
ERROR PSL 041F0008
N-BIT
INTERRUPT PRIORITY LEVEL = 31.
PREVIOUS MODE = KERNEL
CURRENT MODE = KERNEL
INTERRUPT STACK
ADAPTER DATA
XMA NODE # 6.
PHYS ADR 21B00000
NODE 6.
XDEV 00024001
MS62A
DEVICE REV = 2.
XBE 80800000
PARITY ERROR
ERROR DETECTED
SEADR 08000002
4 WAY INTERLEAVE
_ADDRESSING POSITION 1.
STARTING ADR = 0. MB
ENDING ADR = 128. MB
MCTL1 02024000
MEMORY VALID
MEMORY SIZE = 0.MB ARRAY
RAM TYPE = 1MB
MECER 00000000
ECC ERROR SYNDROME = 0.
MECEA 00000000
ERROR ADDRESS = 00000000(X)
MCTL2 00000025
DIABLED HOLD
ARB SUPPRESS MODE:
_ASSERTED WHEN 1 CMD IN QUE
REFRESH RATE = 1.
!This is the same error log entry as previous one.
******************************* ENTRY 400. *******************************
ERROR SEQUENCE 510. LOGGED ON: SID 0B000004
DATE/TIME 24-MAR-1990 08:55:33.79 SYS_TYPE 02100101
SCS NODE: BEVX04 VAX/VMS V5.2
MACHINE CHECK KA64A CPU FW REV# 4. CONSOLE FW REV# 1.0
XMI NODE # 2.
PHYS ADR XDEV XBE XFADR **************
21900000 00088082 8080A081 61B00008!Gets it right
XGPR RCSR BCSTS BCCTL
00000002 412C0001 042A0000 00000008
BCERR PCSTS PCERR SSCBTR
079530E8 00000888 21B00008 00017700
VINTSR
00000001
FAULT CODE VADDR VIBA SISR/ICCS
80000011 80A64BA2 80A5D114 00400000
INTERNAL STATE SC PC PSL
0600050E 00000004 80A5D111 041F0008
******************************* ENTRY 401. *******************************
| |||||
| 17.18 | cache parity errors | COMICS::ROBB | Thu Jun 14 1990 16:19 | 238 | |
From: KERNEL::COMICS::LINDLEY "Brian Lindley, U.K. Support 833-4568 12-Jun-1990 1616" 12-JUN-1990 16:21:04.79
To: @6000
CC: LINDLEY
Subj: 6300 Cache Tag Parity Errors
I have been asked that the following should only be distributed to
support personnel, until an official statement is released. CSSE are
interested in getting any information about the crashes and dumps,
that are detailed below. Please contact me if you have any
information related with 6300 Tag Parity Errors, if they are causing
system crashes. Usually the error is logged as a soft machine check
and everything carries on O.K.
Originally this problem was thought to be confined to Rev B. or Rev.
C of the T2011-YA. It has also been seen on Rev D. of the module.
CSSE have enough modules that exhibit the problem for testing, its
crash dumps that they want !
Regards
Brian
COMPANY CONFIDENTIAL
FOREWORD
The following information is the result of several days
of intense crash analysis by the Corporate Support Group.
This information is PRELIMINARY and COMPANY CONFIDENTIAL.
PROBLEM STATEMENT
A HYPERION (63xx) cache coherency failure has been
exhibited in several crash dumps recently analyzed by
Corporate Support Systems Engineering.
Engineering is in the process of verifying Corporate
Support's findings; thus no official statement can yet be made
to either customers or field personnel and dissemination of
these initial findings should be limited to those with a "need
to know".
The purpose of this "unofficial" problem statement for
Support Personnel only.
TECHNICAL ANALYSIS
Early assessment of the failure indicates the cache-tag
chips fail to detect what should be a write "hit" in the
second-level cache. The false "miss" results in that
second-level cache data NOT being updated. If the CPU
subsequently issues a READ to the same address, before that
slot is replaced, it may result in a cache "hit" and the stale
data is used. The write buffers are loaded regardless of
cache write "hit/miss" status and ultimately flushed to main
memory keeping it coherent.
All of the crashes analyzed thus far resulted from stale
data being returned from STACK references. No other failure
mode has yet been documented, but obviously any scenario is
possible.
CONTRIBUTING FACTORS
Only CPUs with an incidence of Cache Tag Parity Errors
seem to exhibit this failure which is believed to be a cache
tag component failure.
WORK AROUND
The only recommended course of action upon determining a
HYPERION CPU has caused a crash exhibiting the "cache
coherency failure" footprint is to SWAP the CPU.
SUPPORTING CRASH INFORMATION
Two INVEXCEPTION crashes have been identified which
exhibit the HYPERION cache coherency failure. The crashes
occur at MMG$PAGEFAULT+010E and at MMG$PAGEFAULT+091. The
KERNEL stack footprint identifies the crash as a cache
coherency failure. Please refer to the reference and template
stack information and related pagefault listings attached.
In both cases the stack must be "rebuilt" to a previous
point in time from the crash in order to understand the
failure mechanism. Please refer to the "reference process
pagefault stack" which is waiting for MMG LOCK. The values on
that stack in, in conjunction with a failing HYPERION CPU,
result in the template crash stack frames.
In the MMG$PAGEFAULT+010E crash, a process has
pagefaulted and is in MMG$PAGEFAULT. It has acquired the MMG
spinlock via a JSB to SMP$ACQUIRE and ultimately ends up in
MMG$GETPAGLOC. The "false cache write miss" occurs at line
493 where R3 is pushed on the stack. When the code returns
from MMG$FREWSLE it POPS R3 off the stack.. R3 is then used
as a source address for R0 (BICL at line number 512). The
stage is set for the crash to occur in MMG$NOTRANSITION line
number 578 when R0 is used as an index off MMG$GLGPTBASE to
source R3. The INVEXCEPTION occurs at the next instruction
(MMG$PAGEFAULT+010E) when R3 is used indirectly by the ROTL.
Although the popped value of R3 was subsequently overwritten,
it appears that R3 received what was the RETURN PC from the
JSB to SMP$ACQUIRE, not the contents of R3 (SVAPTE) pushed on
the stack prior to the BSBW to MMG$FREWSLE. Both would have
occupied the same VA on the STACK. This is supported by the
contents of R0 which was 01A0311. The value of the I-STREAM
data at the LOCK macro expansion label 3002$-2 (return PC) is
08DA0311. After the BICL at line 512, R0 would contain
005A0311. R0 is subsequently BICL again at line 577 resulting
in R0 contents of 01A0311. This is the MMG$PAGEFAULT+010E
FOOTPRINT.
In the MMG$PAGEFAULT+091 crash, a process has pagefaulted
and is in MMG$PAGEFAULT. When it went to acquire the MMG
LOCK, it was apparently owned by some other process and this
process had to "spin" counting down the timeout value on the
stack (refer to reference stack, address 7FFE77C4).
Eventually it acquired the lock and proceeded to process the
pagefault. It pushed R3,R2,R1 on the stack and BSBW'd to
MMG$FREWSLE The return PC would have been saved on the stack
at 7FFE77C8. While in MMG$FREWSLE another subroutine was
called. This is where the HYPERION "false write cache miss"
occured. The return PC was not stored in the second-level
cache. When the process RSB'd the MMG spinlock timeout value
previously occupying that stack location was returned instead
of the return PC causing the INVEXCEPTION with the failing PC
equal to the failing VA (02AEA4EC).
Template Stack for processes PAGEFAULTED, wating to acquire MMG
spinlock
KERNEL stack:
7FFE77A4 80174B8D MMG$FRE_TRYSKIP+000AA
7FFE77A8 80174C68 MMG$MAKEWSLE+0003C
7FFE77AC 80174725 MMG$PGFLTWAIT+002A9
7FFE77B0 7FFEDC00 CTL$GL_DCLPRSOWN
7FFE77B4 80174750 MMG$PGFLTWAIT+002D4
7FFE77B8 10943F9D
7FFE77BC 80173B6A MMG$RELPFN+0003B
7FFE77C0 80174BB9 MMG$DELWSLEPPG+00002
SP => 7FFE77C4 02AEA46E
7FFE77C8 8013C000 CPUDD
7FFE77CC 00000008 ;saved ipl
7FFE77D0 0093682E ;r1
7FFE77D4 80173FCC MMG$PAGEFAULT+00024
7FFE77D8 40A03E35 ;r0
7FFE77DC 0093682E ;r1
7FFE77E0 0002B600 ;r2
7FFE77E4 00000080 ;r3
7FFE77E8 00004600 ;r4
7FFE77EC 00000800 ;r5
7FFE77F0 00000004 ;\
7FFE77F4 00036A00 ;| page fault
7FFE77F8 0000039D ;| exception
7FFE77FC 03C00000 ;/
Template stack for MMG$PAGEFAULT+10E INVEXCEPTION crash
7FFE7780 0000FA0B
7FFE7784 0001939A
7FFE7788 0000A09A
7FFE778C 7FF3A39C
7FFE7790 7FF3A360
7FFE7794 7FFE7798 CTL$GL_KSTKBAS+00598
7FFE7798 80BA7632 EXE$EXCEPTION+00047
7FFE779C 00080009 UCB$M_MNTVERPND+00009
SP => 7FFE77A0 00000004
7FFE77A4 7FF3A360
7FFE77A8 FFFFFFFD
7FFE77AC 001A0311 ;r0 <<******* this is the FOOTPRINT
7FFE77B0 00000001 ;r1
7FFE77B4 00000001
7FFE77B8 00000005 ;arg count
7FFE77BC 0000000C ;access violation
7FFE77C0 00000001 ;reason MASK
7FFE77C4 8F6B4A44 ;failed VA
7FFE77C8 80BB76B6 MMG$PAGEFAULT+0010E
7FFE77CC 00C80008 ;exception psl
7FFE77D0 00009E00 ;r2
7FFE77D4 83D5E13C ;r3
7FFE77D8 00000001 ;r0
7FFE77DC 82CD6000 ;r1
7FFE77E0 00000000 ;r2
7FFE77E4 7FF3A34C ;r3
7FFE77E8 00000001 ;r4
7FFE77EC 00000001 ;r4
7FFE77F0 00000000 ;\
7FFE77F4 00009E00 ;| pagefault
7FFE77F8 00009DFE ;| exception
7FFE77FC 03C00004 ;/
Template stack for MMG$PAGEFAULT+91 INVEXCEPTION crash
7FFE7778 7FFAC208
7FFE777C 7FFAC400
7FFE7780 7FFAD300
7FFE7784 7FFE911C
7FFE7788 7FFE90C4
7FFE778C 7FFE7790 PAGVA+00190
7FFE7790 80164032 EXE$EXCEPTION+00047
7FFE7794 00080009 XWB$M_STS_ABORT+00009
SP => 7FFE7798 00000004
7FFE779C 7FFE90C4
7FFE77A0 FFFFFFFD
7FFE77A4 00000001 ;r0
7FFE77A8 000001F3 ;r1
7FFE77AC 00000001
7FFE77B0 00000005 ;arg count
7FFE77B4 0000000C ;access violation
7FFE77B8 00000001 ;reason mask
7FFE77BC 02AEA4EC ;exception VA \ 2AEAxxx is the
7FFE77C0 02AEA4EC ;exception PC / expected FOOTPRINT
7FFE77C4 00480009 ;exception PSL
7FFE77C8 80174039 MMG$PAGEFAULT+00091 (MMG$FREWSLE)
7FFE77CC 853FF6AC ;r1
7FFE77D0 7FFAD200 ;r2
7FFE77D4 81C057A4 ;r3
7FFE77D8 08000104 ;r0
7FFE77DC 7FFE9098 ;r1
7FFE77E0 00000000 ;r2
7FFE77E4 7FFAD300 ;r3
7FFE77E8 FFFFFEFC ;r4
7FFE77EC 000000CE ;r5
7FFE77F0 00000004 ;\
7FFE77F4 7FFAD300 ;| pagefault
7FFE77F8 8012DFDD ;| exception
7FFE77FC 09400009 ;/
| |||||
| 17.20 | XBIB PROBLEM | KERNEL::BLAND | toward 2000 ... | Thu Aug 09 1990 12:28 | 91 |
Author : BARBARA GILBERT
User type : AIM
Location : TIMA
Vaxmail address : TIMA::GILBERT
The attached information is from the CSSE Mid-Range Support Group.
It contains important information regarding, XBIB CAUSING MEMORY AND/OR
IO ADAPTER ERRORS.
This information can be found through TIMA STARS
Database: CSSE_TIME_CRITICAL
============================[ Start Message ]==============================
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT CASE
| | | | | | | |
+---------------------------+
TITLE: XBIB CAUSING MEMORY AND/OR IO ADAPTER ERRORS.
DATE:3-AUG-1990
AUTHOR: Jim Vermette TD #: 000363
DTN: 240-6496
ENET: VOLKS::VERMETTE CROSS REFERENCE #'s: NONE
DEPARTMENT: CSSE MID-RANGE SUPPORT (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: ALL PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
PROBLEM:
Multiple BI errors, INTR60 (READ ERROR RESPONSE, WRITE ERROR INTERRUPT),
BI ADAPTER INTERRUPTS (NACK to MULTI-RESPNODER CMD RECVD) and MEMORY
CONTROLLER ERROR, have been exhibited on 6000 series systems. It is
also likely that the system will expierence UNEXPECTED I/O ADAPTER INT
bugchecks. Due to the variety of these errors occurring on the BI Bus,
Customer Service Engineers are involved in extensive troubleshooting,
module swapping, and even system swaps.
It has been determined that a problem exist within the XBIB
(T1043) module.
Currently their is a suspicion that the problems may be
caused by a PAL located on the XBIB. The problem, at this
point in time, appears to be a chip vendor related issue. This
is only a preliminary analysis.
Texas Instrument and National Semiconductor manufactured chips
are suspected to be related to this problem. Another vendor
type chip, AMD, used in this application, does not seem to be
related to the problem.
RESOLUTION/WORKAROUND:
If you are experiencing the above mentioned symptoms it is advised
that you check all XBIB modules for the chip type. The location
of the chip in question is at E8. Holding the module component side
facing up and with the BI corner at the lower right hand corner,
the chip is located about half way up the module between the BI
corner and the top right hand corner of the module. E8 is etched
just below the chip.
If the module contains a TI or NS chip at E8 and the system is
experiencing the above mentioned symptoms, order a new XBIB.
Be aware that there is not a guarantee that you will receive an
XBIB with an AMD chip.
ADDITIONAL COMMENTS:
It should be noted that these problems are being seen on new
systems only but may also be present in systems with newly
replaced XBIBs. The PAL problem is marginal and it is possible
that a TI or NS PAL will work.
Engineering is continuing to work this problem. CSSE will continue
to pursue an immediate resolution to the problem and will inform
Customer Services as soon as a solution is in place.
*** DIGITAL INTERNAL USE ONLY ***
=============================[ End Message ]===============================
| |||||
| 17.21 | Subj: XBIB ( T1043 ) Revision "K" information | COMICS::ROBB | Tue Nov 13 1990 20:25 | 83 | |
From: KERNEL::COMICS::LINDLEY "Brian Lindley, U.K. Support 833-4568 13-Nov-1990 1743" 13-NOV-1990 17:49:06.03
To: @6000
CC: LINDLEY
Subj: XBIB ( T1043 ) Revision "K" information
Gentlemen,
I recently distributed a mail in which a problem pertaining to
XBIB, the T1043, was described. The mail was titled "XBIB
Causing Multiple BI Errors", and detailed the symptoms such as
INT60 errors, BI adapter errors, memory controller errors and
even Unexpected I/O Adapter interupt bugchecks. I have
included the original message at the end of this one for
clarification.
The situation now is that the problem has been identified and
an ECO to the T1043 will be implemented shortly. The new
revision of the module is rev "K", and Nijmegan assure me that
that this will be available in early December. However, in the
meantime I am afraid, we still have to keep changing the T1043
until this latest revision becomes available.
A quick check for revision "K" is the presence of 23-050L5 at
location E18. Please contact if you require any more
information.
Regards
Brian
********************************************************************************
From: COMICS::LINDLEY "Brian Lindley, U.K. Support 833-4568 04-Oct-1990 1023" 4-OCT-1990 10:27:09.69
To: @6000
CC:
Subj: XBIB Causing Multiple BI errors
PROBLEM:
Multiple BI errors, INTR60 (READ ERROR RESPONSE, WRITE ERROR
INTERRUPT), BI ADAPTER INTERRUPTS (NACK to MULTI-RESPNODER CMD
RECVD) and MEMORY CONTROLLER ERROR, have been exhibited on 6000
series systems. It is also likely that the system will
expierence UNEXPECTED I/O ADAPTER INT bugchecks. Due to the
variety of these errors occurring on the BI Bus, Customer
Service Engineers are involved in extensive troubleshooting,
module swapping, and even system swaps.
It has been determined that a problem exist within the XBIB
(T1043) module.
Currently their is a suspicion that the problems may be caused
by a PAL located on the XBIB. The problem, at this point in
time, appears to be a chip vendor related issue. This is only a
preliminary analysis.
Texas Instrument and National Semiconductor manufactured chips
are suspected to be related to this problem. Another vendor
type chip, AMD, used in this application, does not seem to be
related to the problem.
RESOLUTION/WORKAROUND:
If you are experiencing the above mentioned symptoms it is
advised that you check all XBIB modules for the chip type. The
location of the chip in question is at E8. Holding the module
component side facing up and with the BI corner at the lower
right hand corner, the chip is located about half way up the
module between the BI corner and the top right hand corner of
the module. E8 is etched just below the chip.
If the module contains a TI or NS chip at E8 and the system is
experiencing the above mentioned symptoms, order a new XBIB. Be
aware that there is not a guarantee that you will receive an
XBIB with an AMD chip.
ADDITIONAL COMMENTS:
It should be noted that these problems are being seen on new
systems only but may also be present in systems with newly
replaced XBIBs. The PAL problem is marginal and it is possible
that a TI or NS PAL will work.
| |||||
| 17.22 | Replacing CPU module on 6000 | KERNEL::ROBB | Mon Dec 03 1990 15:44 | 148 | |
Use this method when replacing one CPU with a CPU that has a higher rev
EEPROM on any 6000 system.
>>> I
F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
A A . . M M M M . . . P P P TYP
o o . . + + + + . . . + + + STF
. . . . . . . . . . . E E B BPD
. . . . . . . . . . . + + + ETF
. . . . . . . . . . . E E B BPD
. . . . . . . . . + . . . . + . XBI D +
. . . . . . . . . + . + . . + . XBI E +
. . . . A4 A3 A2 A1 . . . . . . ILV
. . . . 32 32 32 32 . . . . . . 128 Mb
ROM = 4.1 EEPROM = 2.0/4.2 SN = GA92700138
?2D For Secondary Processor 3
?53 EEPROM revision mismatch. Secondary processor has revision 2.0/4.4
?2D For Secondary Processor 3
?59 System serial number mismatch. Secondary processor has GA01200276
!Note new CPU in slot 3 has a higher rev EEPROM than the original processors in
!slot 1 and 2.
!An update all from CPU 1 would **DOWNGRADE** the new CPU in 3.
!Use the example below to upgrade the EEPROM of all processors on the system to
!the highest.
>>> SH ALL
Type Rev
1+ KA62B (8001) 8004
2+ KA62B (8001) 8002
3+ KA62B (8001) 8004
7+ MS62A (4001) 0002
8+ MS62A (4001) 0002
9+ MS62A (4001) 0002
A+ MS62A (4001) 0002
D+ DWMBA/A (2001) 0002
E+ DWMBA/A (2001) 0002
XBI D
1+ DWMBA/B (2107) 000A
6+ DEBNA (410F) 0250
XBI E
1+ DWMBA/B (2107) 000A
4+ CIBCA (0108) 41C1
6+ TBK70 (410B) 0307
Current Primary: 1
/NOENABLED-
/NOPRIMARY-
F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
. . . . A4 A3 A2 A1 . . . . . . ILV
. . . . 32 32 32 32 . . . . . . 128 Mb
/INTERLEAVE:DEFAULT
/SCOPE /SPEED: 1200 /BREAK
English
DEFAULT /XMI:E /BI:4 /NODE:0000000F DU0
STB /XMI:E /BI:4 /NODE:0000000F DUB
!Make a note of serial no, speed and boot information.
>>> SET CPU/NEXT_PRIMARY 3
>>> INIT
.
.
.
!Set to the new CPU
!Do a show boot here just to make sure you are on the new CPU. Please let me
!know if there are any problems with this procedure at this point. K.R.
>>> SH ALL
Type Rev
1+ KA62B (8001) 8004
2+ KA62B (8001) 8002
3+ KA62B (8001) 8004
7+ MS62A (4001) 0002
8+ MS62A (4001) 0002
9+ MS62A (4001) 0002
A+ MS62A (4001) 0002
D+ DWMBA/A (2001) 0002
E+ DWMBA/A (2001) 0002
XBI D
1+ DWMBA/B (2107) 000A
6+ DEBNA (410F) 0250
XBI E
1+ DWMBA/B (2107) 000A
4+ CIBCA (0108) 41C1
6+ TBK70 (410B) 0307
Current Primary: 3
/NOENABLED-
/NOPRIMARY- 1,2
F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
. . . . A4 A3 A2 A1 . . . . . . ILV
. . . . 32 32 32 32 . . . . . . 128 Mb
/INTERLEAVE:DEFAULT
/SCOPE /SPEED: 1200 /BREAK
English
DEFAULT /XMI:E /BI:4 /NODE:0000000 DU1
!In this case the speed was the same but the boot information is different
!Still on CPU 3
>>> ^[<DEL>SET SYSTEM SERIAL
System Serial Number>>> GA92700138
Serial number read as: GA92700138
Update EEPROM? (Y or N) >>> Y
?72 System serial number updated.
>>> SET BOOT DEFAULT /XMI:E/BI:4/NODE:F DU0
>>> SET BOOT STB /XMI:E/BI:4/NODE:F DUB
!Now copy from CPU3 to the rest.
>>> UPDATE ALL
>>> SET CPU/PRIMARY/ALL
>>> I
F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
A A . . M M M M . . . P P P TYP
o o . . + + + + . . . + + + STF
. . . . . . . . . . . E E B BPD
. . . . . . . . . . . + + + ETF
. . . . . . . . . . . E E B BPD
. . . . . . . . . + . . . . + . XBI D +
. . . . . . . . . + . + . . + . XBI E +
. . . . A4 A3 A2 A1 . . . . . . ILV
. . . . 32 32 32 32 . . . . . . 128 Mb
ROM = 4.1 EEPROM = 2.0/4.4 SN = GA92700138
>>>
!All CPUs now at the same higher revision EEPROM with correct serial number.
| |||||
| 17.23 | Subj: VMS SYSGEN problem with VAX 6000 Configurations | COMICS::ROBB | Sun Dec 16 1990 09:25 | 44 | |
From: KERNEL::COMICS::LINDLEY "Brian Lindley, U.K. Support 833-3659 10-Dec-1990 1647" 10-DEC-1990 16:49:40.27
To: @6000
CC: LINDLEY
Subj: VMS SYSGEN problem with VAX 6000 Configurations
Gentlemen,
The following problem pertains to all VAX 6000-XXX systems.
Problem Description
The VMS SYSGEN Autoconfigure utility will incorrectly configure
a CIBCA if it is preceeded on the BI bus by a DEBNA, DEBNI or
TBK70 (BVP devices). The failure will occur either if the DEBNx
or TBK70 is in the BI slot directly preceeding the CIBCA and if
the DEBNx or TBK70 is in the last slot on the BI (XMI:E) and
the first slot on the next BI (XMI:D).
The results of the above configurations are Port Timeouts on
the PAA0: device. The Timeout errors will be seen if booting
either standalone backup or VMS.
Booting the system via the CIBCA will not cause this condition
to occur regardless of the configuration. Reason, the boot
device is not configured by SYSGEN's Autoconfigure.
The actual VMS failure is due to the SCB Interrupt Handler
Vector for the CIBCA driver. Upon initialization the SCB is
loaded with a "fake vector" pointing to a Null routine. Once
the CIBCA driver is loaded the correct Interrupt Service
routine Vector should be loaded into the SCB. The problem is
SYSGEN never loads the correct vector and leaves the "fake
vector" to handle interrupts.
Status/Solution
VMS Engineering has accepted responsibilty for the resolution
and has scheduled the modification to the SYSGEN utility
correcting the failure. This will be incorporated in the next
release of VMS.
Regards
Brian
| |||||
| 17.24 | Subj: XBIB causing memory and/or IO Adapter Errors | COMICS::ROBB | Sun Dec 16 1990 09:26 | 33 | |
From: KERNEL::COMICS::LINDLEY "Brian Lindley, U.K. Support 833-3659 10-Dec-1990 1658" 10-DEC-1990 17:00:48.83
To: @6000
CC: LINDLEY
Subj: XBIB causing memory and/or IO Adapter Errors
Gentlemen,
The following is an update to a mail message I sent out
recently with regard to the XBIB (T1043) module.
PROBLEM:
Multiple BI errors, INTR60 (READ ERROR RESPONSE, WRITE ERROR
INTERRUPT), BI ADAPTER INTERRUPTS (NACK to MULTI-RESPNODER CMD
RECVD) and MEMORY CONTROLLER ERROR, have been exhibited on 6000
series systems. It is also likely that the system will
experience UNEXPECTED I/O ADAPTER INT bugchecks.
RESOLUTION/WORKAROUND:
The solution is to the Master Sequencer (T1043 E18,
23-007L5-00) component. The "new" version of the Master
Sequencer is ( E18, 23-050L5-00). The T1043 XBIB containing the
new Master Sequencer is revision "K".
T1043s at revision "K" will be available through a "P1"
specifying revision "K" on December 3, 1990. A FCO Program
retrofitting ALL field SPARES ONLY, is planned to commence in
the January timeframe, or as soon as material is available.
Regards
Brian
| |||||
| 17.25 | MARIAH UPGRADE POTENTIAL PROBLEM | KERNEL::BLAND | toward 2000 ... | Wed Jan 09 1991 00:18 | 83 |
Author : RODNEY BOYLE
User type : USER
Location : CSSE
Vaxmail address : CSSE::BOYLE
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT CASE
| | | | | | | |
+---------------------------+
TITLE: H7214 Power Supply
DATE: January 7,1991
AUTHOR: Jerry Wernicki TD #: 000542
DTN: 293-5667
ENET: MSBCS::WERNICKI CROSS REFERENCE #'s:
DEPARTMENT: CSSE Mid Range (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE:(U.S./EUROPE/GIA) PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
PROBLEM:
When performing a full power and package upgrade from an existing
VAX 6000-XXX system to a VAX 6000-5XX or when installing an add-on
VAXBI Backplane in the H9657 cabinet, there is a potential to short
out the power supply.
The reason for the short is that both 10/32 x 7/16 and 10/32 x 5/16
screws are used in the cabinet. There is a potential that the
engineer could use the wrong size screw to attach the bus bars to
the H7214.
If the 10/32 x 7/16 screws are used to attach the bus bars to the
regulator the screw will touch a coil inside the regulator and short
the output of the H7214 to ground.
IT IS IMPERATIVE THAT THE 10/32 x 5/16 SCREWS BE USED ON THE POWER
CABLE CONNECTIONS.
RESOLUTION/WORKAROUND:
The following has or will be done to help avoid this situation:
1. All documentation (XMI Conversion Manual and the BI
Installation Manual) have CAUTION advisories embedded
in the text for reminders.
2. We are looking into having inserts placed into all
H7214 parts that warn of the possibility.
or
Placing an insert highlighting this possibility in
the Full Power and Package Upgrade and BI addons when
they are shipped from the factory.
3. A techtip has been generated regarding the problem.
ADDITIONAL COMMENTS:
In most circumstances when the 10/32 x 7/16 screws are used instead of
the 10/32 x 5/16 the regulator crowbars and there is no damage to the
regulator. Once the proper screws are used the regulator will function.
However, on occasion, sufficient force used on the 10/32 x 7/16 screws
will cause the screw to damage the internal coil and damage the
windings. It will be necessary to replace the regulator should the
this happen.
***************** DIGITAL INTERNAL USE ONLY **************
| |||||
| 17.26 | ELSAA Problems with VAXPAX 42 | KERNEL::BLAND | toward 2000 ... | Tue Feb 05 1991 09:46 | 97 |
From: BEEZER::TIMA_MGR 5-FEB-1991 02:25:20.63
To: KERNEL::BLAND
CC:
Subj: GRAM: VAX Diagnostics Supervisor ELSAA.EXE & ERSAA.EXE (blitz)
Author : RODNEY BOYLE
User type : USER
Location : CSSE
Vaxmail address : CSSE::BOYLE
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT CASE
| | | | | | | |
+---------------------------+
TITLE: VAX DIAGNOSTIC SUPERVISOR ELSAA.EXE and ERSAA.EXE
DATE: 04-JAN-1991
AUTHOR: JIM VERMETTE TD #: 000579
DTN: 247-2555
ENET: VOLKS::VERMETTE CROSS REFERENCE #'s:
DEPARTMENT: CSSE SYSTEM SUPPORT (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: U.S./EUROPE/GIA PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
PROBLEM:
- VAX Diagnostic Supervisor (ELSAA) version 14.1, release 42
Systems affected: 58xx, VAX 62xx, 63xx
- VAX Diagnostic Supervisor (ERSAA) version 14.1, release 42
Systems affected: VAX 64xx
- Level 3 XMI Adapter Diagnostic Failures
A problem has been discovered with the VDS within the channel services
routine which causes general purpose registers to be corrupted or stack
imbalance. Only level 3 diagnostic programs which test XMI adapters are
affected. It does not affect BI adapter diagnostics. The affected
programs use the $DS_CHANNEL service functions, CHC$_STATUS or CHC$_ENINT.
The symptom has been seen while testing the CIXCD with program EVGAA - CI
Functional Test Part I, in test 1, as follows:
?? Access control violation Fault through SCB vector: 20(X)
Virtual Address: 00000005(X)
Fault type: 00000000(X)
PC at error: 00004D16(X)
PSL at error: 00000000(X) ; CUR=KERNEL,PRV=KERNEL,IPL=00
User return PC: 00004D16(X)
The problem may cause other XMI I/O Adapter diagnostics to show different
symptoms.
RESOLUTION/WORKAROUND:
A workaround for this problem includes utilizing the VDS EXAMINE/DEPOSIT
commands to change the following locations:
The permanent modification will be incorporated within the next release of
the VDS.
For ELSAA,
DS> EXAMINE/BYTE 2714C ; Should be 40
DS> DEPOSIT/BYTE 2714C 20
DS> EXAMINE/BYTE 27889 ; Should be D0
DS> DEPOSIT/BYTE 27889 05
For ERSAA,
DS> EXAMINE/BYTE 2730C ; Should be 40
DS> DEPOSIT/BYTE 2730C 20
DS> EXAMINE/BYTE 27A49 ; Should be D0
DS> DEPOSIT/BYTE 27A49 05
ADDITIONAL COMMENTS: N/A
*** DIGITAL INTERNAL USE ONLY ***
| |||||
| 17.27 | FCO 63xmx-0003 correction BLITZ | KERNEL::BLAND | toward 2000 ... | Tue Mar 12 1991 12:59 | 65 |
<<< SASE::WRKD:[NOTES$LIBRARY]CALYPSO.NOTE;3 >>>
-< CALYPSO -- VAX 6000-xxx Family Notes >-
================================================================================
Note 821.4 Incorrect Procedure on 63XMX-0003. 4 of 4
VOLKS::JACKSON "KEN" 56 lines 11-MAR-1991 11:37
-< 63XMX-F003 correction BLITZ >-
--------------------------------------------------------------------------------
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT CASE
| | | | | | | |
+---------------------------+
TITLE: 63XMX-F003 FA Document Correction
DATE: 05-MAR-1991
AUTHOR: Ken Jackson TD #: 000614
DTN: 858-2554
ENET: VOLKS::JACKSON CROSS REFERENCE #'s: NONE
DEPARTMENT: VAX SYSTEMS SUPPORT CSSE (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: PRIORITY LEVEL:1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
PROBLEM:
Procedures in the 63XMX-F003 FCO FA document are incorrect.
Use of these procedures could cause all CPU modules with in
the system being upgraded to become inoperable.
RESOLUTION/WORKAROUND:
DO NOT use SAVE/RESTORE EEPROM and/or UPDATE ALL commands
on multiple CPU systems. The new XMI based systems necessitated
changes to the processor console ROM for support. When these
modules are cycled into the field as add-on options, spares, or
the results of an FCO, it may result in VAX 6000 systems having
processor modules with console ROMS at different revisions in the
same system. You may see console ROM mismatch messages printed
during system initialization. These DO NOT identify a problem.
These should be considered informational for listing ROM revisions.
DO NOT use "SAVE/RESTORE EEPROM" and/or "UPDATE ALL" commands on
multiple CPU systems. Instead, use "Patch Update Utility",
EVUCA.
NOTE
----
EVUCA requires VAX Diagnostic Supervisor (VAX/DS) version 14.0
or later and binary filed ELUCB .BIN must be present for VAX
6000-3XX.
ADDITIONAL COMMENTS:
Saved boot specifications and system serial number should be
documented prior to installing the FCO.
FA-04928-01 Rev. C is the corrected version of the FCO document.
*** DIGITAL INTERNAL USE ONLY ***
| |||||
| 17.28 | 6000 DIAGS MAY TEST WRONG DRIVE | KERNEL::JAMES | Alan James CSC Basingstoke | Wed Mar 20 1991 08:49 | 235 |
Subj: GRAM: Diagnostics May Format the System Disk (blitz)
Author : RODNEY BOYLE
User type : USER
Location : CSSE
Vaxmail address : CSSE::BOYLE
+---------------------------+TM
| | | | | | | |
| d | i | g | i | t | a | l | TIME DEPENDENT BLITZ
| | | | | | | |
+---------------------------+
BLITZ TITLE: Diagnostic may format the SYSTEM DISK
DATE: 18-MAR-1991
AUTHOR: JOHN KOWALL TD #: 000633
DTN: 522-3881
ENET: GENRAL::KOWALL CROSS REFERENCE #'s:
DEPARTMENT: Continuation Engineering (PRISM/TIME/CLD#'s)
INTENDED AUDIENCE: ALL PRIORITY LEVEL: 1
(U.S./EUROPE/GIA) (1=TIME CRITICAL,
2=NON-TIME CRITICAL)
=====================================================================
PROBLEM:
WARNING! Three versions of VAX Diagnostic 6000 Supervisors may test
the wrong drive!!! This may be the System Disk.
Products affected are from diagnostic release revision C only:
ELSAA - version 14.4-2438, VAX Diagnostic Supervisor
Systems affected: 58xx, VAX 6000-2xx, 6000-3xx
EMSAA - version 14.4-703, VAX Diagnostic Supervisor
Systems affected: VAX 6000-5xx
ERSAA - version 14.4-1127, VAX Diagnostic Supervisor
Systems affected: VAX 6000-4xx
NOTE: Also anyone with a proxy may have copied the above supervisors plus
EBSAA - version 14.4-2185
The part numbers for the Rev. C "SSB" release media (it will continue
to ship until May) are as follows:
AG-PDWVC-RE VAX 6000 CONSOLE CD-ROM
AG-PDWWC-RE VAX 6000 CMPLT DIAG CD-ROM
AQ-PDYPC-ME VAX 6000 CONSOLE TK50
AQ-PDWXC-DE VAX 6000 CMPLT DIAG TK50
BB-PDWYC-DE VAX 6000 CMPLT DIAG 16MT9
Caution: There are several EDIT versions of these supervisors now in
circulation. All read 14.4. You should run the D.S. to verify
what version you have and then determine if it must be patched
before running the following diagnostics:
EVRLB - VAX RA60/80/81 FORMATTER
EVRLF - UDA50/KDB50 BASIC SYBSYS DIAG
EVRLG - UDA50/KDB50 DISK DRIVE EXERCISER
EVRLJ - VAX UDA50/KDB50/KDM70 EXERCISER
EVRLK - VAX BAD BLOCK REPLACE UTILITY
The problem with the diagnostics EVRLB, EVRLF,EVRLG, EVRLJ, and EVRLK and
the supervisors have now been corrected. In order to aide you in determining
whether or not you have a good or bad version of these files, I have listed
the versions below. Two versions of diagnostic supervisor and diagnostics
are INCOMPATIBLE with each other:
1/ Early release 43 supervisors (14.4-*) with release 42 diags.
SSB release "C"
2/ Early release 43 supervisors (14.4-*) with early release 43 diags.
If you have copied any of these files from:
YODA::SYS$ARCHIVE: or
YODA::RELD$0:[ARCHIVE...] or
YODA::RELD$0:[43...]
Then, those diagnostics should be deleted.
The most serious symptom occurs with EVRLB, which will always format drive #0.
Diagnostic Version Review
_________________________
GOOD GOOD GOOD
Bad Versions Release 42 Release 43 Release C
Delete Versions Versions after patching
EBSAA 14.4-2185 14.1 14.4-PAT1 14.4-PAT2
ELSAA 14.4-2438 14.1 14.4-PAT1 14.4-PAT2
EMSAA 14.4-704 -- 14.4-PT1 14.4-PT2
ERSAA 14.4-1127 14.1 14.4-PAT1 14.4-PAT2
EVRLB 8.2 8.0 8.3 8.0
EVRLF 10.3 10.0 10.4 10.0
EVRLG 10.2 10.0 10.3 10.0
EVRLJ 4.2 4.0 4.3 4.0
EVRLK 4.2 4.0 4.3 4.0
=====================================================================
Symptom:
Drive #0 is always tested, regardless of which disk units were selected for
testing. In the case of the formatter, EVRLB, drive #0 would always be
formatted. If drive #0 does not exist, no diagnostic can be run, an error
message similar to the following will appear:
******** EVRLF - VAX UDA50/KDB50 BASIC SUBSYSTEM DIAGNOSTIC - 10.1 ********
Pass 1, test 3, subtest 0, error 5000, 8-FEB-1990 08:24:27.10
Device fatal error while testing DUC95: DM PROGRAM REPORTING AN ERROR
DISK FUNCTION DM PC: 5344 Controller at address 100362 (O) DRIVE _DUC95
UNABLE TO FIND REQUESTED DRIVE FOR TESTING
THE FOLLOWING IS VISIBLE ON THE PORTS
CONTROLLER PORT 0 -- DRIVE 95
CONTROLLER PORT 1 -- NO DRIVE ATTACHED
CONTROLLER PORT 2 -- NO DRIVE ATTACHED
CONTROLLER PORT 3 -- NO DRIVE ATTACHED
******** End of Device fatal error number 5000 ********
=====================================================================
RESOLUTION/WORKAROUND: Wait/Copy/Patch
Wait:
The diagnostic release "D" will be available from SSB which is
scheduled for May 6,1991). It will have release 43 (D) diagnostics.
Copy:
The Diagnostics Supervisors can be copied over the network:
COPY YODA::DISK$DS:[DS.GLOBAL.RELEASE.REVC_COM]*.EXE *
Patch:
The following procedures can be used to apply patches to the Rev. C
versions of diagnostic supervisors:
I. CD-ROM booting
A. Apply the patches by hand.
Do the following:
1)Boot the diagnostic supervisor from CD-ROM
2)Type the commands from the appropriate command file.
or
B. Load the patch command file from another drive.
Do the following:
1)Copy the appropriate patch command file and
autosizer (EVSBA.EXE) to another drive
2)Boot the diagnostic supervisor from CD-ROM
3)Run the autosizer (RUN EVSBA)
4)Set the load path to access the command file
(SET LOAD dev:[dir])
5)Execute the command file (@E%SAA.COM)
II. Non CD-ROM booting
A. Use the VMS PATCH utility to permanently apply the patches to the
supervisor executable E%SAA.EXE. Copy the patched supervisor to
the boot device:[directory].
or
B. Apply the patches via automatic command file executed at boot time
Do the following:
1)Copy the appropriate patch command file to the boot
device:[directory] with the name VDSSCRIPT.COM
2)Boot the diagnostic supervisor, specifying autocom feature
B/R5:8010 ...
or
C. Apply the patches by hand.
Follow procedure A from part I above.
or
D. Load the patch command file from a drive other than the boot drive.
Follow procedure B from part I above.
The order of the above steps must be followed exactly. The command files are
modifying code which accesses the device ptables, so once the patches are
applied the ptables must be rebuilt. This is why the autosizer is run after
the patches are applied. Some sites may use command files to ATTACH devices,
so the command file should be executed in place of running the autosizer.
In some cases, the diagnostic supervisor attaches device ptables in the boot
path, which the autosizer does not subsequently reattach. If this happens,
a "File Read Error" will result when trying to load diagnostics, take a
directory, or get help. This can be recovered from by reattaching
the suspect ptable, or resetting the load path (SET LOAD) to the device name
which the autosizer built.
The command files for patching REV "C" supervisors and the patched
supervisors which are in the final Release 43 are available world readable
from:
YODA::DISK$DS:[DS.GLOBAL.RELEASE.REVC_COM]
ELSAA.COM EMSAA.COM ERSAA.COM
EBSAA.EXE ELSAA.EXE EMSAA.EXE ERSAA.EXE
=====================================================================
ADDITIONAL COMMENTS:
Please note that the physical labels on the CD-ROMs do not match their volume
labels. The physical label will read 6000_CONS_C and 6000_DIAG_C, but the
volume label (service name of CD-ROM) will read 6000_CONS_B and 6000_DIAG_B.
*** DIGITAL INTERNAL USE ONLY ***
| |||||