VAX-VMS Migration Notes:
Menu: Original uVAX-4300 |
New VAX-6420 | Example Boots
Our original uVAX-4300 based system
+------+------+------+
| RZ28 | RZ28 | RZ28 | SCSI bus
| #50 | #51 | #52 +------------+
+------+------+------+ |
|
+-----------------+ +------+------+------+ +---+---+
| uVAX-4300 | | RF71 | RF71 | RF71 | | HSD05 |
| CPU +-------x------+ #0 | #1 | #2 +---------------+ #5 +-DT/e
| DSSI#0--+--DT/i | +------+------+------+ +-------+
| | DS0 DS1 DS2
| DSSI#1--+--A----x-DT/e +------+------+------+------+------+ +-------+
| +--B----x------+ RF71 | RF71 | RF71 | RF71 | RF71 +-+ HSD05 +-DT/e
| Internal Bus | | #10 | #11 | #12 | #13 | #14 | | #15 |
+-----------------+ +------+------+------+------+------+ +---+---+
| Q-Bus Adapters | |
| KZQSA +--A----x-ST/e +------+------+------+ |
| SCSI#0--+--B----x------+ | RZ28 | RZ28 | RZ28 +------------+
| | | | #150 | #151 | #152 | SCSI bus
+-----------------+ | +------+------+------+
|
+--------+--------+ |
ST/e-+ RRD42 | Exa8mm +-+
| dka200 | mka300 | <<<--- VMS names
+--------+--------+
Legend:
DSSI#0 = Embedded DSSI (SHAC) controller #0
DSSI#1 = Embedded DSSI (SHAC) controller #1
SCSI#0 = Optional Q-Bus/SCSI Controller (KZQSA)
DT/i = DSSI Bus Terminator Internal
DT/e = DSSI Bus Terminator External
ST/e = SCSI Bus Terminator External
RF71 = 350 Megabyte DSSI based Hard Drive
RZ28 = 1.2 Gigabyte SCSI based Hard Drive
DS = Disk Shadow (example: DS0 is a shadow set volume composed of mirror
disks #0 and #10. If one of the drives crash, the mate drive can carry
on independently). This requires an optional "Shadow License".
RRD42 = CD ROM
Exa8mm = Exabyte 8mm Tape
Notes:
1. DSSI#1-A may connect to more DSSI Bus #1 devices, or to the DSSI bus of
another CPU (if both CPUs are part of a VAXcluster)
2. every DSSI port must be connected to either a DSSI terminator or a DSSI cable
which is coonected to one or more DSSI devices with a termination at the end
of the chain.
3. to the best of my knowledge, the internal DSSI terminators cannot be
removed.
4. Wether physically visible or not, there is always a terminator at each end of
both DSSI and SCSI busses.
5. both HSD05 units have been optioned to respond to DSSI #5
6a.to boot drive #0 (on dssi bus #0 ), type "b dia0"
6b.to boot drive #51 (on dssi bus #0, hsd05 #5 ), type "b dia51"
6c.to boot drive #10 (on dssi bus #1 ), type "b dib10"
6d.to boot drive #151 (on dssi bus #1, hsd05 #15), type "b dib151"
Our new VAX-6000-420 based system
DS5a
+------+------+------+
| RZ28 | RZ28 | RZ28 | Internal
| #50 | #51 | #52 +------------+
+------+------+------+ SCSI Bus |
|
+-----------------+ +------+------+------+ +---+---+
| VAX-6420 | | RF71 | RF71 | RF71 | | HSD05 |
| CPU +-------x------+ #0 | #1 | #2 +---------------+ #5 +-DT/e
| DSSI#0--+--DT/i | +------+------+------+ +-------+
| | DS0 DS1 DS2
| DSSI#1--+--DT/i | +------+------+------+------+------+ +-------+
| +-------x------+ RF71 | RF71 | RF71 | RF71 | RF71 +-+ HSD05 +-DT/e
| XMI Bus | | #10 | #11 | #12 | #13 | #14 | | #15 |
+-----------------+ +------+------+------+------+------+ +---+--++
| |
+------+------+------+ Internal | ST/e
External +------+ RZ28 | RZ28 | RZ28 +------------+
SCSI bus | | #150 | #151 | #152 | SCSI bus
| +------+------+------+
| DS5b
+--------+--------+ |
ST/e-+ RRD42 | Exa8mm +-+
| dia153 | mu154 | <<<--- VMS names
+--------+--------+
Legend:
DSSI#0 = XMI based DSSI (KFMSA) controller #0
DSSI#1 = XMI based DSSI (KFMSA) controller #1
DT/i = DSSI Bus Terminator Internal
DT/e = DSSI Bus Terminator External
ST/e = SCSI Bus Terminator External
RF71 = 350 Megabyte DSSI based Hard Drive
RZ28 = 1.2 Gigabyte SCSI based Hard Drive
DS = Disk Shadow (example: DS0 is a shadow set volume composed of mirror
disks #0 and #10. If one of the drives crash, the mate drive can carry
on independently). This requires an optional "Shadow License".
RRD42 = CD ROM
Exa8mm = Exabyte 8mm Tape
Notes:
1. DSSI#1-A may connect to more DSSI Bus #1 devices, or to the DSSI bus of
another CPU (if both CPUs are part of a VAXcluster)
2. every DSSI port must be connected to either a DSSI terminator or a DSSI cable
which is coonected to one or more DSSI devices with a termination at the end
of the chain.
3. to the best of my knowledge, the internal DSSI terminators cannot be
removed.
4. Wether physically visible or not, there is always a terminator at each end of
both DSSI and SCSI busses.
5a.both HSD05 units have been optioned to respond to DSSI #5
5b.the internal SCSI head/tail termination has been removed in HSC05 #15 so that
an external cable could be used to connect to the CD-ROM adn 8mm Tape. This
method was cheaper than buying a SCSI adapter for our VAX-6420
6a.Note that the CD-ROM and 8mm Tape are now being managed by HSD15 #15.
6b.This means that the VMS names for these devices has changed since they where
moved from the Q-Bus SCSI controller (KFQZA)
6c.When mounting the CD-ROM from VMS you must use the /NOWRITE switch since VMS
now thinks that the CD-ROM is an RF series drive capable of writing.
6d.VMS now thinks that the 8mm tape is a TU81 capable of using the /DENSITY
switch. You should always use /DENSITY=6250. Other values work but seem to
transfer data more slowly.
7a.to boot drive #0 (on dssi bus #0 ), type "b /x:4 /n:20000 di0"
7b.to boot drive #51 (on dssi bus #0, hsd05 #5 ), type "b /x:4 /n:20005 di33"
7c.to boot drive #10 (on dssi bus #1 ), type "b /x:4 /n:30000 dia"
7d.to boot drive #151 (on dssi bus #1, hsd05 #15), type "b /x:4 /n:30005 di97"
Example Boots
uVAX-3500
>>>b dua0 boots drive 0 of first (a) controller (depends on Q-Bus address)
>>>b dub1 boots drive 1 of second (b) controller (depends on Q-Bus address)
Notes:
1. The KFQSA (Q-Bus/DSSI Adapter) is a programmable device that can appear to
the Q-Bus like multiple device controllers.
2. The KDA-50 (Q-Bus/MSCP Adapter) is not programmable so it always looks like
one controller.
uVAX-4300
>>>b dia0 boots drive with MSCP drive number 0 on DSSI Bus #0
>>>b dib10 boots drive with MSCP drive number 10 on DSSI Bus #1
Notes:
1. drive numbers are in decimal
2. diaX is on DSSI bus #0 (embedded controller)
3. dibX is on DSSI bus #1 (embedded controller)
4. Sometimes the MSCP Drive number is the DSSI node number which means that the
number is restricted to the range 0-7
5. Sometimes the MSCP Drive number is programmed in drive firmware which means
that the number is restriced to the range 0-9999
VAX-6420
>>>b /x:4 /b:0 /n:20001 di0
| | | | +---- MSCP UNITNUM (0=0)
| | | +-------- DSSI ID# 1
| | +------------ 2=DSSI Bus #0 (a.k.a. port 1)
| | 3=DSSI Bus #1 (a.k.a. port 2)
| +----------------- no BI slot selected
+---------------------- KFMSA in XMI slot 4
>>>b /x:4 /b:0 /n:30001 dia
| | | | +---- MSCP UNITNUM (a=10)
| | | +-------- DSSI ID# 1
| | | 2=DSSI Bus #0 (a.k.a. port 1)
| | +------------ 3=DSSI Bus #1 (a.k.a. port 2)
| +----------------- no BI slot selected
+---------------------- KFMSA in XMI slot 4
Notes:
1. drive numbers are in hexadecimal (9=9, a=10, b=11, etc.)
2a.The first example could be a boot from an RFxx series drive if...
DSSI Plug #1 is installed
MSCP FORCEUNI=0 (drive MSCP is not forced to be DSSI plug number)
MSCP UNITNUM=0
2b.The first example could be a boot from HSD Based SCSI drive #0 with a DSSI
ID# of 1
3a.The second example could be a boot from an RFxx series drive if...
DSSI Plug #1 is installed
MSCP FORCEUNI=0 (drive MSCP is not forced to be DSSI plug number)
MSCP UNITNUM=10
3b.The second example could be a boot from HSD Based SCSI drive #10 with a DSSI
ID# of 1
4. To boot either an RFxx series drive with an MSCP number of 151, or an
HSD Based SCSI drive with a SCSI ID# of 151, you must boot di97 because a
hexadecimal number is required.
proof: 151/16 = 9 with a remainder of 7
Documentation Links
Back
to VAX-VMS Storage Notes
Back
to
Computer
Back
to VAX-VMS
Back
to Home
Neil Rieck
Kitchener - Waterloo - Cambridge, Ontario, Canada.
