[Info-vax] Sharing CDROM on Alpha Server

[nw.jo...@ieee.org]

On Saturday, January 16, 2021 at 9:34:57 PM UTC-5, Stephen Hoffman wrote:
> On 2021-01-17 00:22:58 +0000, nw.jo... at ieee.org said: 
> 
> > I have been experimenting with mop-loading NetBSD from a Linux system, 
> > but it panics when it tries to mount root after 7500 packets 
> > successfully sent over the net. (I'm using TCP/IP not DECNet). So I 
> > thought I would try booting the NetBSD install CDROM from my Alpha 
> > server. Nowhere in the manuals can I find out how to set up MOP or NFS 
> > server under VMS. Is this something that is so old that support has 
> > been dropped? I suppose I could leave mopd on the Linux machine and 
> > just try to get the ISO image under NFS if that would work. 
> > Any help appreciated,
> The OpenVMS doc is utter shite, here. Unfortunately. I know how this 
> stuff works, and I can't find references. This stuff is, however, 
> supported, as it's how Alpha cluster satellites, terminal servers, and 
> other boxes boot. 
> 
> 
> 
> MOP: 
> 
> The general sequence enables MOP service on the device using the LANCP 
> utility, then maps the MAC to the host and its settings, then loads the 
> device settings into the volatile (live) database, then loads all node 
> settings into the volatile database. 
> 
> LANCP> SET DEVICE {device} 
> /MOPDLL=(ENABLE,EXCLUSIVE,KNOWNCLIENTSONLY,SIZE=1482) 
> LANCP> DEFINE NODE {name} /ADDRESS={MAC-address} /BOOT_TYPE=OTHER 
> /FILE={filename} 
> LANCP> SET DEVICE {device} /PERMANENT 
> LANCP> SET NODE /ALL /PERMANENT 
> 
> The download files are usually placed in LAN$DLL: 
> 
> Logs are sometimes useful for determining what happened... 
> 
> LANCP> SHOW LOG 
> 
> https://wiki.vmssoftware.com/LANCP 
> 
> Above assumes you're not running a fossil version of OpenVMS; V8.4 is 
> prolly the oldest you want to run nowadays. 
> 
> 
> 
> NFS server: 
> 
> http://h30266.www3.hpe.com/odl/i64os/network/tcpip57eco2/6526/6526pro_contents_005.html#toc_chapter_22 
> 
> 
> HPE Hobbyists had access to some patches for TCP/IP Services V5.7 IIRC, 
> and you'll want those. NFSv3 client support was added with V5.7 ECO2, 
> though NFSv3 server was around a bit longer. But there've been bugs 
> fixed, too. Get the patches. Or run the VSI OpenVMS Alpha or OpenVMS 
> I64 hobbyist kits, with the patches. 
> 
> 
> The above will at least give you some search targets, not that I've 
> been able to locate all that much. 
> 
> I'd initially thought maybe Vnetek might have some how-to documentation 
> related to DECservers, but that website is now gone. 
> 
> 
> 
> -- 
> Pure Personal Opinion | HoffmanLabs LLC
Thanks for the above, Stephen, it has got me further but there is a
funny thing...

I just set up MOP on the alpha - (I am running VMS 7.1) and I get the
following status report from BONZO2, a microvax running NetBSD under SimH:

BONZO2# moptrace -a

Dst          : ab:0:0:2:0:0      MOP Remote Console Multicast
Src          : aa:0:4:0:12:4   
Proto        : 6002 MOP Remote Console
Length       : 0087 (135)
Code         :   07 System ID
Reserved     :   00
Receipt Nbr  : 0000
Maint Version: 4.0.0
Maint Funcion: 0041 ( Loop DLC )
Hardware Addr: 8:0:2b:bb:88:6b 
Comm Device  :   b6 (null) '(null)'
Data Link Typ:   01 Ethernet
Software ID  :   ff Standard operating system
Info Type    : 00c9 (201)
Info Data    :   04 41 56 4d 53
Info Type    : 00ca (202)
Info Data    :   08 56 37 2e 31 20 20 20 20
Info Type    : 00cb (203)
Info Data    :   08 52 4f 42 49 4e 20 20 20
Info Type    : 00cc (204)
Info Data    :   04 14 04 00 00
Info Type    : 00cd (205)
Info Data    :   08 00 00 00 00 00 00 00 00
Info Type    : 00ce (206)
Info Data    :   08 16 01 01 07 01 00 a1 00
Info Type    : 00cf (207)
Info Data    :   08 00 00 00 00 00 00 00 00
Info Type    : 00d0 (208)
Info Data    :   04 00 00 00 00
Info Type    : 00d1 (209)
Info Data    :   14 5b 0d 5b 00 00 00 00 00 03 00 00 00 10 20 17 00
                    01 01 06 00

I assume this  is a service announcement since it occurs from the alpha
without an attempt to netboot from the real microvax.

Howebver, when I check status of MOP on the Alpha, I get a funny address
for BONZO:

LANCP> sho node /all

Node Listing, volatile database:

(Catchall entry):

BONZO (10-00-D4-20-BF-E0):  ==================> I have tried entering
both with colons and hyphens, same thing.
  MOP DLL:  Load file:   08002B04FD07.SYS
            Load root:   (None specified)
            Boot type:   Other

PERMANENT:

ROBIN (10-00-D4-DD-11-D6):
  MOP DLL:  Load file:   MOPBOOT.SYS
            Load root:   (None specified)
            Boot type:   Other
LANCP>

The problem with upgrading to later VMS, or applying patches, is that I
don't have a hobbyist licence and I don't think they are issuing them
any more - this was  live system when it went out of production owned by
my company.

Does the weird MAC address ring any bells?

cheers,

Nigel