2 Aug
2007
2 Aug
'07
10:07 p.m.
So, I've been trying for a few days to get my VAX 7000/640 (currently
with only one processor, so a 610 I guess) to MOP boot into a VMS
cluster.
I'm running OpenVMS hosted off SIMH, and have tried both 7.2 and 7.3,
and have successfully booted my VAX 4000/100 off the setup. I've also
successfully booted the firmware update utility (LFU) and the
file "ISL_LVAX_073.SYS" that comes on the install CD, through MOP.
However, when I try to do a mop boot, the system just halts and says
boot failure:
---------------------------------------------------------------------
>> b -fl 0,0,0 exa0
Initializing...
F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
A M . . . . . . P TYP
o + . . . . . . + ST1
. . . . . . . . B BPD
o + . . . . . . + ST2
. . . . . . . . B BPD
+ + . . . . . . + ST3
. . . . . . . . B BPD
+ . . . . . + . . + . . . + C0 XMI +
. . . . . . . . . . . . . . . . C1
. . . . . . . . . . . . . . . . C2
. . . . . . . . . . . . . . . . C3
. A0 . . . . . . . ILV
. 512 . . . . . . . 512MB
Firmware Rev = V4.3-4842 SROM Rev = V3.1-0 SYS SN = AB25002CX0
Booting...
Connecting to boot device exa0
Created device: exa0.0.0.1.0
Attempting MOP boot.
Requesting MOP Assistance Volunteer.
MOP Assistance Volunteer found.
Loading...
...
Load complete!
Image size: 133241
Host name: SIMV73
Host address: aa-00-04-00-06-04
bootstrap code read in
base = 154000, start = 0
boot device name = exa0.0.0.1.0
boot flags 0,0,0
boot device type = 69
controller ID = a
unit number = 0
node ID = 0
channel = 0
slot = 1
hose = 0
jumping to bootstrap at 154000
CPU:0 Console entry reason: HALT instruction in kernel mode
Entry PC: 006B6368 Entry PSL:041F0600
>> boot failure
---------------------------------------------------------------------
I've tried it omitting the -flags part, and with -fl 1, but they all
give the same error.
Anyone have any useful hints? Or, another VAX 7000 to try repeating my
(failing) experiment on?
Thanks,
Pat
--
Purdue University ITAP/RCAC --- http://www.rcac.purdue.edu/
The Computer Refuge --- http://computer-refuge.org
3 Aug
3 Aug
3:44 p.m.
On Aug 2, 2007, at 10:07 PM, Patrick Finnegan wrote:
So, I've been trying for a few days to get my VAX
7000/640 (currently
with only one processor, so a 610 I guess) to MOP boot into a VMS
cluster.
I'm running OpenVMS hosted off SIMH, and have tried both 7.2 and 7.3,
and have successfully booted my VAX 4000/100 off the setup. I've also
successfully booted the firmware update utility (LFU) and the
file "ISL_LVAX_073.SYS" that comes on the install CD, through MOP.
However, when I try to do a mop boot, the system just halts and says
boot failure:
...
...
CPU:0 Console entry reason: HALT instruction in kernel
mode
Entry PC: 006B6368 Entry PSL:041F0600
Neither of my 7000s are set up at the moment, but I may be able to
rig up some temporary power to give this a try over the weekend.
Have you tried MOP-booting the machine from a *BSD host running
mopd? I believe mopd can produce fairly verbose log messages that
might be helpful, to see what's going on from the server's perspective.
-Dave
--
Dave McGuire
Port Charlotte, FL
Farewell Ophelia, 9/22/1991 - 7/25/2007
>> boot failure
---------------------------------------------------------------------
I've tried it omitting the -flags part, and with -fl 1, but they all
give the same error.
Anyone have any useful hints? Or, another VAX 7000 to try
repeating my
(failing) experiment on?
4:01 p.m.
On Friday 03 August 2007, Dave McGuire wrote:
On Aug 2, 2007, at 10:07 PM, Patrick Finnegan wrote:
It looks like this is my problem...
Page 4 of http://h18000.www1.hp.com/info/SP2978/SP2978PF.PDF
"VAX-11/7xx, VAX 6000, VAX 7000, VAX 8xxx, VAX
9000, and VAX 10000 series systems require a sys-
tem disk that is accessed via a local adapter or
through a local CI or DSSI connection. These sys-
tems cannot be configured to boot as satellite nodes."
So it looks like some DSSI gear (easier) or a whole bunch of CI gear
(harder) is going to be required to get this thing booting VMS.
Pat
--
Purdue University Research Computing --- http://www.rcac.purdue.edu/
The Computer Refuge --- http://computer-refuge.org
Anyone have any useful hints? Or, another VAX
7000 to try
repeating my
(failing) experiment on?
Neither of my 7000s are set up at the moment, but I may be able to
rig up some temporary power to give this a try over the weekend.
Have you tried MOP-booting the machine from a *BSD host running
mopd? I believe mopd can produce fairly verbose log messages that
might be helpful, to see what's going on from the server's
perspective.
5:07 p.m.
On Aug 3, 2007, at 4:01 PM, Patrick Finnegan wrote:
It looks like this is my problem...
Page 4 of http://h18000.www1.hp.com/info/SP2978/SP2978PF.PDF
"VAX-11/7xx, VAX 6000, VAX 7000, VAX 8xxx, VAX
9000, and VAX 10000 series systems require a sys-
tem disk that is accessed via a local adapter or
through a local CI or DSSI connection. These sys-
tems cannot be configured to boot as satellite nodes."
Holy cow, I never knew that! 8-| Mine boot via CI from an HSJ50.
So it looks like some DSSI gear (easier) or a whole
bunch of CI gear
(harder) is going to be required to get this thing booting VMS.
Well I'll yank one of the DSSI adapters out of one of my 7000s
over the weekend and get it out to you...you should have it up and
running before the end of next week.
-Dave
--
Dave McGuire
Port Charlotte, FL
Farewell Ophelia, 9/22/1991 - 7/25/2007
5:54 p.m.
Patrick Finnegan wrote:
It looks like this is my problem...
Page 4 of http://h18000.www1.hp.com/info/SP2978/SP2978PF.PDF
"VAX-11/7xx, VAX 6000, VAX 7000, VAX 8xxx, VAX
9000, and VAX 10000 series systems require a sys-
tem disk that is accessed via a local adapter or
through a local CI or DSSI connection. These sys-
tems cannot be configured to boot as satellite nodes."
I don't know what you problem is but I'm sure that I
believed that booting a VAX 6000/7000 series system over
the net was possible. Specifically, I think I used to do
this with a VAX 6000 while at DEC.
This suggests that I'm not completely crazy:
http://64.223.189.234/node/285
A real manual suggests I'm not completely nuts too:
http://www.sysworks.com.au/disk$cddoc04mar21/decw$book/d32va233.p28.decw
$book
For booting from an InfoServer you have to pick the right
image (i.e. "big" VAXen and "little" VAXen need different
forms of TLC).
You also say:
I've also
successfully booted the firmware update utility (LFU) and the file
"ISL_LVAX_073.SYS" that comes on the install CD, through MOP.
So you have booted your VAX 7000 over MOP.
Obviously I'm missing something ...
Antonio
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.476 / Virus Database: 269.11.2/933 - Release Date:
02/08/2007 14:22
9:43 p.m.
On Friday 03 August 2007 17:54, Antonio Carlini wrote:
You also say:
Yes, the machine can mop boot, but it can't be mop booted as a satellite
node of a vaxcluster.. it has to have local/shared disk over CI or
DSSI.
Pat
--
Purdue University ITAP/RCAC --- http://www.rcac.purdue.edu/
The Computer Refuge --- http://computer-refuge.org
I've also
successfully booted the firmware update utility (LFU) and the file
"ISL_LVAX_073.SYS" that comes on the install CD, through MOP.
So you have booted your VAX 7000 over MOP.
Obviously I'm missing something ... 
10:14 p.m.
Patrick Finnegan wrote:
On Friday 03 August 2007, Dave McGuire wrote:
That's weird, because I've *definitely* booted a VAX 6610 from a cluster
using mop.
Peace... Sridhar
On Aug 2, 2007, at 10:07 PM, Patrick Finnegan
wrote:
It looks like this is my problem...
Page 4 of http://h18000.www1.hp.com/info/SP2978/SP2978PF.PDF
"VAX-11/7xx, VAX 6000, VAX 7000, VAX 8xxx, VAX
9000, and VAX 10000 series systems require a sys-
tem disk that is accessed via a local adapter or
through a local CI or DSSI connection. These sys-
tems cannot be configured to boot as satellite nodes."
So it looks like some DSSI gear (easier) or a whole bunch of CI gear
(harder) is going to be required to get this thing booting VMS. Anyone have any useful hints? Or, another VAX
7000 to try
repeating my
(failing) experiment on?
Neither of my 7000s are set up at the moment, but I
may be able to
rig up some temporary power to give this a try over the weekend.
Have you tried MOP-booting the machine from a *BSD host running
mopd? I believe mopd can produce fairly verbose log messages that
might be helpful, to see what's going on from the server's
perspective.
6231
days inactive
6232
days old
6 comments
4 participants
participants (4)
-
arcarlini＠iee.org -
mcguire＠neurotica.com -
pat＠computer-refuge.org -
ploopster＠gmail.com