22 Feb
2002
22 Feb
'02
2:51 a.m.
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
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
%SYSBOOT-I-SYSBOOT Mapping PAGEFILE.SYS on the System Disk
%SYSBOOT-I-SYSBOOT SAVEDUMP parameter not set to protect the
PAGEFILE.SYS%VAXcluste
r, 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
OpenVMS (TM) VAX Version V7.2 Major version id = 1 Minor version id =
0
%VAXcluster, PE boot driver timer control value = 00002710
%VAXcluster, PE boot driver initialization failed, maximum retry limit
exceeded
%EXECINIT, error initializing boot device - R0 = 00000054
?06 Halt instruction executed
PC = 85CBC5BF
--
Saku Set?l?
System Planning Manager
Kolumbus Oy http://www.kolumbus.com/
Elisa Communications Group
22 Feb
22 Feb
8:49 a.m.
----- Original Message -----
From: "Saku Setala" <setala(a)elisa.fi>
To: "Julius Sridhar" <vance(a)ikickass.org>
Cc: <classiccmp(a)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.
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
>> 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 
4:16 p.m.
Hi Geoff, thanks for replying.
On Sat, 23 Feb 2002, Geoff Roberts wrote:
All those retries are a Bad Thing. Looks more like a
hardware problem.
That's what I suspected in the beginning. So I swapped the hub and network
cables and aui-rj45 transceiver. I also swapped the DEBNT card on 6300.
No difference whatsoever. Tried even flipping the "heartbeat" on from the
tranceiver. No different.
The boot server is a Microvax 3100/40. Two diskless Microvax 3400 boot
happily from it without any problems.
The R5 looks funny becouse I need to specify the Tertiary loader filename.
With R5:0 it just freezes.
I've pulled out earlier all the extra cards from the 6300, so only bare
minimum left.
>> SHOW CONF
Type Rev
1+ KA62B (8001) 8002
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
Thanks for your time,
--Saku
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
5:59 p.m.
----- Original Message -----
From: "Saku Setala" <setala(a)setala.net>
To: <classiccmp(a)classiccmp.org>
Sent: Saturday, February 23, 2002 4:46 PM
Subject: Re: Still trying to netboot 6300
Hmm, interesting.
Have you tried whipping up a crossover cable and going direct from MV to
6300?
Just wondering if the switch ports are trying to force full duplex or
getting the autonegotiate wrong somehow.
All those
retries are a Bad Thing. Looks more like a hardware problem.
That's what I suspected in the beginning. So I swapped the hub and network
cables and aui-rj45 transceiver. I also swapped the DEBNT card on 6300.
No difference whatsoever. Tried even flipping the "heartbeat" on from the
tranceiver. No different.
The boot server is a Microvax 3100/40. Two diskless
Microvax 3400 boot
happily from it without any problems.
The R5 looks funny becouse I need to specify the Tertiary loader filename.
Oh? Why?
With R5:0 it just freezes.
I'm definitely gonna have to dig out my 6300 manual. I don't think that
should happen.
I've pulled out earlier all the extra cards from
the 6300, so only bare
minimum left.
>>> SHOW CONF
Nothing there that should upset it. Interesting.
Geoff in Oz
7:19 p.m.
Hi again,
On Sat, 23 Feb 2002, Geoff Roberts wrote:
Because without it does not work, just freezes.
That's what I've been trying to figure out - why this happens.
Hmm, interesting.
Have you tried whipping up a crossover cable and going direct from MV to
6300?
Just wondering if the switch ports are trying to force full duplex or
getting the autonegotiate wrong somehow.
There's now a HUB. Not a switch. No-brains-device, half duplex only.
The R5 looks
funny becouse I need to specify the Tertiary loader filename.
Oh? Why? With R5:0 it
just freezes.
I'm definitely gonna have to dig out my 6300 manual. I don't think that
should happen. I've pulled out earlier all the extra cards
from the 6300, so only bare
minimum left.
>>> SHOW CONF
Nothing there that should upset it. Interesting.
Geoff in Oz
8338
days inactive
8339
days old
4 comments
3 participants
participants (3)
-
geoffrob＠stmarks.pp.catholic.edu.au -
setala＠elisa.fi -
setala＠setala.net