3 Aug
2007
3 Aug
'07
7: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.