Still trying to netboot 6300

From: Geoff Roberts <geoffrob_at_stmarks.pp.catholic.edu.au>
Date: Fri Feb 22 16:49:34 2002

----- Original Message -----
From: "Saku Setala" <setala_at_elisa.fi>
To: "Julius Sridhar" <vance_at_ikickass.org>
Cc: <classiccmp_at_classiccmp.org>
Sent: Saturday, February 23, 2002 3:21 AM
Subject: Re: Still trying to netboot 6300


> Ok, now got a little further using TERTIARY_VMB.EXE
> .. and to next problem.
>
> >>> B/R5:101/X:D/B:6 ET0
> Initializing system.
> F E D C B A 9 8 7 6 5 4 3 2 1 0 NODE #
> A A . . M M M . . . . . . P TYP
> o o . . + + + . . . . . . + STF
> . . . . . . . . . . . . . B BPD
> . . . . . . . . . . . . . + ETF
> . . . . . . . . . . . . . B BPD
>
> . . . . . . . . . + . . . . + . XBI D +
> . . . . . . . . . . . . . . + . XBI E +
>
> . . . . B1 A2 A1 . . . . . . . ILV
> . . . . 32 32 32 . . . . . . . 96 Mb
>
> ROM = 6.0 EEPROM = 2.0/6.0 SN = GA92000372
>
> Loading system software.
>
> Filename: TERTIARY_VMB.EXE
>
> The filename for NICDrom MOP boot is: TERTIARY_VMB.EXE
> * Passing control to transfer address
>
> %VAXcluster, system loaded from node VAXVMS (AA-00-04-00-01-04)
> %VAXcluster, PE boot driver timer control value = 00002710
> %VAXcluster, creating channel, disk server VAXVMS
> %VAXcluster, opening virtual circuit, disk server VAXVMS
> %VAXcluster, PE boot driver successfully initialized, disk server VAXVMS
>
> Bootfile:SYSBOOT.EXE
>
> SYSBOOT> CONTINUE
>
> %SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk%VAXcluster,
> checking
> for listen timeout
> %VAXcluster, checking for listen timeout
> %VAXcluster, listen timeout, disk server VAXVMS
> %VAXcluster, no connection to disk server VAXVMS
> %VAXcluster, closing virtual circuit, disk server VAXVMS
> %VAXcluster, attempting to reconnect to a disk server
> %VAXcluster, creating channel, disk server VAXVMS
> %VAXcluster, opening virtual circuit, disk server VAXVMS
> %VAXcluster, connected to disk server VAXVMS

All those retries are a Bad Thing. Looks more like a hardware problem.

1) What is the boot server? Vax of some kind?
2) Might be a flaky cable or transceiver. Looks like it's trying to do it
right, but the msgs are not getting through.
3) 6K ethernet hardware is strictly half duplex, make sure your boot server
isn't trying to use full duplex.
4) 10Base2 transceivers have a switch to alter a ethernet particular
characteristic, cannot remember what it's called offhand, but vaxen do
strange things if it's in the wrong place.

Does the 6K have a CIBCA (CI device for talking to a HSC) in it? If so take
it out (usually 2 cards in the BI cage).
Shouldn't bother it, but I vaguely recall some odd problems during boot if
it's not terminated.
I'll post some working boot strings, I haven't had to play with mine for
years so memory fails me at the moment. Your R5 value looks odd to me but
all my 6K's boot off hard disk or HSC so it doesn't mean you have it wrong.
.
I'll see if I can scan and post a couple pages from the 6K user manual.

Hope this helps

Geoff in Oz
Received on Fri Feb 22 2002 - 16:49:34 GMT