Just a little bit of trolling...
It seems like IBM has finally caught up with DEC in respect to file management. The latest and newest version of zOS delivers us...
Tada!
PDSE member generations!
http://www-01.ibm.com/support/knowledgecenter/#!/SSLTBW_2.1.0/com.ibm.zos.v…
(For the ones who don't understand IBM-esse, they are going to support a sort of "file versioning").
Now I'll go back to RSX11 and VMS to look for more "cutting edge" features IBM could add to zOS...
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
Must be a link to SG1:
$ ncp sho act area
Active Area Volatile Summary as of 27-SEP-2014 12:58:35
Area State Circuit Next node to area
3 reachable 3.47 (RVDSXL)
7 reachable TCP-19-41 19.41 (SG1)
19 reachable TCP-19-41 19.41 (SG1)
20 reachable TCP-19-41 19.41 (SG1)
--
Regards, Rok
Mark. One short observation. You are setting the mac address of the interface used by simh to some random value. Have you tried setting it to the value that DECnet later expects to actually set it to, to see if that makes it any better?
Johnny
On 2014-09-22 20:29, Robert Jarratt wrote:
That is my user mode router, it may not be a problem on your side. I am
not at home to investigate. Is anyone else getting failures from area 5?
------------------------------------------------------------------------
From: Mark Wickens <mailto:mark at wickensonline.co.uk>
Sent: 22/ 09/ 2014 08:52
To: hecnet at Update.UU.SE <mailto:hecnet at Update.UU.SE>
Subject: [HECnet] Ubuntu 14.04 SIMH Network Woes
As Johnny knows I've been experiencing some configuration issues since
installing Ubuntu 14.04 on the server that hosts the SIMH instance that
is SIMVAX. I attempted a Kubuntu upgrade but that failed so I had no
resort other than to backup the existing root partition and re-install
from scratch.
I've been unable to configure the networking correctly since the
re-install. The symptom is adjacency up and down messages, coming in
consecutively every minute or so. I've tried numerous combinations of
configuration that have not solved the connectivity issues. When
adjacency is up I'm able to DIR MIM:: successfully.
%<----------%<---------%<----------
$ dir mim::
Directory MIM::DU4:[DECNET]
LOGIN.CMD;1 HECNET.CMD;1 MAKEFILE.;33 MAKEFILE.;43
FIX.LOG;52 MAKEFILE.;34 FIX.LOG;53 NODENAMES.DAT;2
FIX.LOG;61 NODENAMES.DAT;3 FIX.LOG;54 FIX.LOG;55
FIX.LOG;65 FIX.LOG;56 MAKEFILE.;32 MAKEFILE.;44
FIX.LOG;57 FIX.LOG;58 NODENAMES.DAT;4 FIX.LOG;59
%<----------%<---------%<----------
My SIMH boot is as follows:
%<----------%<---------%<----------
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 7154ca1f
NVR: buffering file in memory
libpcap version 1.2.0
Eth: opened OS device eth3
Listening on port 2023
Loading boot code from ka655x.bin
KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0
%<----------%<---------%<----------
I upgraded to SIMH master on the suggesting of Mark Pizolatto when I
wrote the SIMH mailing list with an autoboot failure issue that I've had
for as long as I remember (that turned out to be because I was using an
old kernel ROM image).
My networking configuration on the HP Microserver is as follows:
2 x 1000MB Network Cards
eth2 - The internal card is dedicated to Ubuntu and configured
statically at 192.168.1.126 via ifconfig (I uninstalled NetworkManager
because I have no need for dynamic configuration).
eth3 - A PCI express card that is not configured for Ubuntu. It is
brought up on the understanding that SIMH will provide the necessary
configuration.
My /etc/network/interfaces is as follows:
%<----------%<---------%<----------
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
iface eth2 inet static
address 192.168.1.126
netmask 255.255.255.0
gateway 192.168.1.2
dns-nameservers 192.168.1.2
dns-search hecnet.eu
%<----------%<---------%<----------
My /etc/rc.local script brings up the interfaces:
%<----------%<---------%<----------
# Enable the first network interface for linux use
ifconfig eth2 up
# Bring up the second network interface it's for SIMH use - it is not
configured
ifconfig eth3 up
/bin/bash /usr/local/bridge/bridge.sh
/bin/bash /usr/local/vax/vax.sh
%<----------%<---------%<----------
As you can see it is also responsible for bringing up Johnny's bridge
and the SIMH instance.
After configuration the networking looks like this:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ ifconfig -a
eth2 Link encap:Ethernet HWaddr b4:99:ba:bf:46:e3
inet addr:192.168.1.126 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b699:baff:febf:46e3/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:5150326 errors:0 dropped:90 overruns:0 frame:0
TX packets:7498843 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2519783275 (2.5 GB) TX bytes:9795156712 (9.7 GB)
Interrupt:18
eth3 Link encap:Ethernet HWaddr 00:27:19:b1:6f:84
inet6 addr: fe80::227:19ff:feb1:6f84/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:131318 errors:0 dropped:49269 overruns:0 frame:0
TX packets:3582 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32216834 (32.2 MB) TX bytes:488874 (488.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:45875 errors:0 dropped:0 overruns:0 frame:0
TX packets:45875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5883368 (5.8 MB) TX bytes:5883368 (5.8 MB)
%<----------%<---------%<----------
I have no reason to think that the bridge isn't working, when I run it
from the command line I can see that connectivity takes place. I am
running a fresh compile of the latest version with debug on:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ sudo ./bridge -p 4711 -d /usr/local/bridge
d: 4711
Config filename: /usr/local/bridge/bridge.conf
Adding router ''local''. 00000008:32521
Adding router ''update''. 1913ee82:4711
Adding DECnet bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding DECnet bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Adding LAT bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding LAT bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Host table:
0: local 0.0.0.0:0 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1 Throttle: 0(000)
1: update 130.238.19.25:4711 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1
Throttle: 0(000)
Hash of known destinations:
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 0
%<----------%<---------%<----------
The SIMH vax.ini script contains the following. You can see that xq is
defined as eth1 which in SIMH parlance is the 2nd ethernet interface and
from the start-up trace it can be seen that the correct network
interface, eth3, is being picked up and used.
%<----------%<---------%<----------
msw at hpm:/usr/local/vax/data$ more vax.ini
;add CPU microcode
;load -r /usr/local/vax/data/ka655.bin
;
; Attach non-volatile RAM to a file
attach nvr /usr/local/vax/data/nvram.bin
;
; This virtual machine has 512m memory
set cpu 512m
;
; Define disk drive types. RA92 is largest-supported VAX drive.
set rq0 ra92
set rq1 ra92
;set rq2 ra92
set -B rq2 rauser=300000
;set -B rq3 rauser=20000
;set rq3 cdrom
;
; Attach defined drives to local files
attach rq0 /usr/local/vax/data/d0.dsk
attach rq1 /usr/local/vax/data/d1.dsk
attach rq2 /usr/local/vax/data/dsa3-archive.dsk
;attach rq3 /tmp/d3.dsk
;
; Attach the CD-ROM to its file (read-only)
;attach -r rq3 /usr/local/vax/data/vaxvmscd.iso
;attach -r rq3 /usr/local/vax/data/softwareproducts1.iso
;attach -r rq3 /usr/local/archive/OpenVMS/7.3-VAX/SPL1-VAXBINJUN043.iso
;
; Disable unused devices. It's also possible to disable individual devices,
; using a construction like "set rq2 disable" if desired.
;
set rl disable
set ts disable
;
; Attach Ethernet to a network interface
set xq mac=00:27:19:b1:6f:84
attach xq eth1
set vh enable
att vh 2023
set cpu idle=VMS
set cpu conhalt
dep bdr 0
;
; Now start the emulator
boot cpu
exit
%<----------%<---------%<----------
I have tried both the same and different MAC addresses in the SIMH
configuration for 'xq mac' compared to the actual network card. Alas, no
joy:
%<----------%<---------%<----------
%%%%%%%%%%% OPCOM 22-SEP-2014 08:45:55.13 %%%%%%%%%%%
Message from user DECNET on SIMVAX
DECnet event 4.18, adjacency down
On 2014-09-22 10:30, Mark Wickens wrote:
As an addendum I fired up the RX2660 server running OpenVMS 8.4.
This is TSR2 on 4.12.
There are no adjacency up messages for this box and the bridge doesn't
seem to communicate with it (no debugging generated).
I can directory the remote FAL server directory and SET HOST between the
two boxes which are on the same LAN - but I cannot see MIM:: from TSR2,
only from SIMVAX:: when the adjacencies are up.
I assume the bridge is listening on that same LAN? If so, this sounds weird.
However, unless it's an area router, you might hit into problems there too...
Johnny
Phew! :-)
In that case I would suggest doing some packet sniffing and seeing if packets are getting dropped. There are "keep alive" packets called Ethernet Hello that get sent out every 15 seconds, if some of those get missed for any reason then it can have this effect.
Regards
Rob
On 22 September 2014 20:44, Mark Wickens <mark at wickensonline.co.uk> wrote:
Hi Rob
It's not specific to your end point - it's across the board. MIM is going up and down as well.
Sorry if that worried you!
Regards, Mark
On 22/09/14 19:29, Robert Jarratt wrote:
That is my user mode router, it may not be a problem on your side. I am not at home to investigate. Is anyone else getting failures from area 5?
From: Mark Wickens
Sent: 22/ 09/ 2014 08:52
To: hecnet at Update.UU.SE
Subject: [HECnet] Ubuntu 14.04 SIMH Network Woes
As Johnny knows I've been experiencing some configuration issues since
installing Ubuntu 14.04 on the server that hosts the SIMH instance that
is SIMVAX. I attempted a Kubuntu upgrade but that failed so I had no
resort other than to backup the existing root partition and re-install
from scratch.
I've been unable to configure the networking correctly since the
re-install. The symptom is adjacency up and down messages, coming in
consecutively every minute or so. I've tried numerous combinations of
configuration that have not solved the connectivity issues. When
adjacency is up I'm able to DIR MIM:: successfully.
%<----------%<---------%<----------
$ dir mim::
Directory MIM::DU4:[DECNET]
LOGIN.CMD;1 HECNET.CMD;1 MAKEFILE.;33 MAKEFILE.;43
FIX.LOG;52 MAKEFILE.;34 FIX.LOG;53 NODENAMES.DAT;2
FIX.LOG;61 NODENAMES.DAT;3 FIX.LOG;54 FIX.LOG;55
FIX.LOG;65 FIX.LOG;56 MAKEFILE.;32 MAKEFILE.;44
FIX.LOG;57 FIX.LOG;58 NODENAMES.DAT;4 FIX.LOG;59
%<----------%<---------%<----------
My SIMH boot is as follows:
%<----------%<---------%<----------
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 7154ca1f
NVR: buffering file in memory
libpcap version 1.2.0
Eth: opened OS device eth3
Listening on port 2023
Loading boot code from ka655x.bin
KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0
%<----------%<---------%<----------
I upgraded to SIMH master on the suggesting of Mark Pizolatto when I
wrote the SIMH mailing list with an autoboot failure issue that I've had
for as long as I remember (that turned out to be because I was using an
old kernel ROM image).
My networking configuration on the HP Microserver is as follows:
2 x 1000MB Network Cards
eth2 - The internal card is dedicated to Ubuntu and configured
statically at 192.168.1.126 via ifconfig (I uninstalled NetworkManager
because I have no need for dynamic configuration).
eth3 - A PCI express card that is not configured for Ubuntu. It is
brought up on the understanding that SIMH will provide the necessary
configuration.
My /etc/network/interfaces is as follows:
%<----------%<---------%<----------
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
iface eth2 inet static
address 192.168.1.126
netmask 255.255.255.0
gateway 192.168.1.2
dns-nameservers 192.168.1.2
dns-search hecnet.eu
%<----------%<---------%<----------
My /etc/rc.local script brings up the interfaces:
%<----------%<---------%<----------
# Enable the first network interface for linux use
ifconfig eth2 up
# Bring up the second network interface it's for SIMH use - it is not
configured
ifconfig eth3 up
/bin/bash /usr/local/bridge/bridge.sh
/bin/bash /usr/local/vax/vax.sh
%<----------%<---------%<----------
As you can see it is also responsible for bringing up Johnny's bridge
and the SIMH instance.
After configuration the networking looks like this:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ ifconfig -a
eth2 Link encap:Ethernet HWaddr b4:99:ba:bf:46:e3
inet addr:192.168.1.126 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b699:baff:febf:46e3/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:5150326 errors:0 dropped:90 overruns:0 frame:0
TX packets:7498843 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2519783275 (2.5 GB) TX bytes:9795156712 (9.7 GB)
Interrupt:18
eth3 Link encap:Ethernet HWaddr 00:27:19:b1:6f:84
inet6 addr: fe80::227:19ff:feb1:6f84/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:131318 errors:0 dropped:49269 overruns:0 frame:0
TX packets:3582 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32216834 (32.2 MB) TX bytes:488874 (488.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:45875 errors:0 dropped:0 overruns:0 frame:0
TX packets:45875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5883368 (5.8 MB) TX bytes:5883368 (5.8 MB)
%<----------%<---------%<----------
I have no reason to think that the bridge isn't working, when I run it
from the command line I can see that connectivity takes place. I am
running a fresh compile of the latest version with debug on:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ sudo ./bridge -p 4711 -d /usr/local/bridge
d: 4711
Config filename: /usr/local/bridge/bridge.conf
Adding router ''local''. 00000008:32521
Adding router ''update''. 1913ee82:4711
Adding DECnet bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding DECnet bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Adding LAT bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding LAT bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Host table:
0: local 0.0.0.0:0 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1 Throttle: 0(000)
1: update 130.238.19.25:4711 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1
Throttle: 0(000)
Hash of known destinations:
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 0
%<----------%<---------%<----------
The SIMH vax.ini script contains the following. You can see that xq is
defined as eth1 which in SIMH parlance is the 2nd ethernet interface and
from the start-up trace it can be seen that the correct network
interface, eth3, is being picked up and used.
%<----------%<---------%<----------
msw at hpm:/usr/local/vax/data$ more vax.ini
;add CPU microcode
;load -r /usr/local/vax/data/ka655.bin
;
; Attach non-volatile RAM to a file
attach nvr /usr/local/vax/data/nvram.bin
;
; This virtual machine has 512m memory
set cpu 512m
;
; Define disk drive types. RA92 is largest-supported VAX drive.
set rq0 ra92
set rq1 ra92
;set rq2 ra92
set -B rq2 rauser=300000
;set -B rq3 rauser=20000
;set rq3 cdrom
;
; Attach defined drives to local files
attach rq0 /usr/local/vax/data/d0.dsk
attach rq1 /usr/local/vax/data/d1.dsk
attach rq2 /usr/local/vax/data/dsa3-archive.dsk
;attach rq3 /tmp/d3.dsk
;
; Attach the CD-ROM to its file (read-only)
;attach -r rq3 /usr/local/vax/data/vaxvmscd.iso
;attach -r rq3 /usr/local/vax/data/softwareproducts1.iso
;attach -r rq3 /usr/local/archive/OpenVMS/7.3-VAX/SPL1-VAXBINJUN043.iso
;
; Disable unused devices. It's also possible to disable individual devices,
; using a construction like "set rq2 disable" if desired.
;
set rl disable
set ts disable
;
; Attach Ethernet to a network interface
set xq mac=00:27:19:b1:6f:84
attach xq eth1
set vh enable
att vh 2023
set cpu idle=VMS
set cpu conhalt
dep bdr 0
;
; Now start the emulator
boot cpu
exit
%<----------%<---------%<----------
I have tried both the same and different MAC addresses in the SIMH
configuration for 'xq mac' compared to the actual network card. Alas, no
joy:
%<----------%<---------%<----------
%%%%%%%%%%% OPCOM 22-SEP-2014 08:45:55.13 %%%%%%%%%%%
Message from user DECNET on SIMVAX
DECnet event 4.18, adjacency down
Hi Rob
It's not specific to your end point - it's across the board. MIM is going up and down as well.
Sorry if that worried you!
Regards, Mark
On 22/09/14 19:29, Robert Jarratt wrote:
That is my user mode router, it may not be a problem on your side. I am not at home to investigate. Is anyone else getting failures from area 5?
From: Mark Wickens
Sent: 22/ 09/ 2014 08:52
To: hecnet at Update.UU.SE
Subject: [HECnet] Ubuntu 14.04 SIMH Network Woes
As Johnny knows I've been experiencing some configuration issues since
installing Ubuntu 14.04 on the server that hosts the SIMH instance that
is SIMVAX. I attempted a Kubuntu upgrade but that failed so I had no
resort other than to backup the existing root partition and re-install
from scratch.
I've been unable to configure the networking correctly since the
re-install. The symptom is adjacency up and down messages, coming in
consecutively every minute or so. I've tried numerous combinations of
configuration that have not solved the connectivity issues. When
adjacency is up I'm able to DIR MIM:: successfully.
%<----------%<---------%<----------
$ dir mim::
Directory MIM::DU4:[DECNET]
LOGIN.CMD;1 HECNET.CMD;1 MAKEFILE.;33 MAKEFILE.;43
FIX.LOG;52 MAKEFILE.;34 FIX.LOG;53 NODENAMES.DAT;2
FIX.LOG;61 NODENAMES.DAT;3 FIX.LOG;54 FIX.LOG;55
FIX.LOG;65 FIX.LOG;56 MAKEFILE.;32 MAKEFILE.;44
FIX.LOG;57 FIX.LOG;58 NODENAMES.DAT;4 FIX.LOG;59
%<----------%<---------%<----------
My SIMH boot is as follows:
%<----------%<---------%<----------
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 7154ca1f
NVR: buffering file in memory
libpcap version 1.2.0
Eth: opened OS device eth3
Listening on port 2023
Loading boot code from ka655x.bin
KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0
%<----------%<---------%<----------
I upgraded to SIMH master on the suggesting of Mark Pizolatto when I
wrote the SIMH mailing list with an autoboot failure issue that I've had
for as long as I remember (that turned out to be because I was using an
old kernel ROM image).
My networking configuration on the HP Microserver is as follows:
2 x 1000MB Network Cards
eth2 - The internal card is dedicated to Ubuntu and configured
statically at 192.168.1.126 via ifconfig (I uninstalled NetworkManager
because I have no need for dynamic configuration).
eth3 - A PCI express card that is not configured for Ubuntu. It is
brought up on the understanding that SIMH will provide the necessary
configuration.
My /etc/network/interfaces is as follows:
%<----------%<---------%<----------
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
iface eth2 inet static
address 192.168.1.126
netmask 255.255.255.0
gateway 192.168.1.2
dns-nameservers 192.168.1.2
dns-search hecnet.eu
%<----------%<---------%<----------
My /etc/rc.local script brings up the interfaces:
%<----------%<---------%<----------
# Enable the first network interface for linux use
ifconfig eth2 up
# Bring up the second network interface it's for SIMH use - it is not
configured
ifconfig eth3 up
/bin/bash /usr/local/bridge/bridge.sh
/bin/bash /usr/local/vax/vax.sh
%<----------%<---------%<----------
As you can see it is also responsible for bringing up Johnny's bridge
and the SIMH instance.
After configuration the networking looks like this:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ ifconfig -a
eth2 Link encap:Ethernet HWaddr b4:99:ba:bf:46:e3
inet addr:192.168.1.126 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b699:baff:febf:46e3/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:5150326 errors:0 dropped:90 overruns:0 frame:0
TX packets:7498843 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2519783275 (2.5 GB) TX bytes:9795156712 (9.7 GB)
Interrupt:18
eth3 Link encap:Ethernet HWaddr 00:27:19:b1:6f:84
inet6 addr: fe80::227:19ff:feb1:6f84/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:131318 errors:0 dropped:49269 overruns:0 frame:0
TX packets:3582 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32216834 (32.2 MB) TX bytes:488874 (488.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:45875 errors:0 dropped:0 overruns:0 frame:0
TX packets:45875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5883368 (5.8 MB) TX bytes:5883368 (5.8 MB)
%<----------%<---------%<----------
I have no reason to think that the bridge isn't working, when I run it
from the command line I can see that connectivity takes place. I am
running a fresh compile of the latest version with debug on:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ sudo ./bridge -p 4711 -d /usr/local/bridge
d: 4711
Config filename: /usr/local/bridge/bridge.conf
Adding router ''local''. 00000008:32521
Adding router ''update''. 1913ee82:4711
Adding DECnet bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding DECnet bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Adding LAT bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding LAT bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Host table:
0: local 0.0.0.0:0 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1 Throttle: 0(000)
1: update 130.238.19.25:4711 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1
Throttle: 0(000)
Hash of known destinations:
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 0
%<----------%<---------%<----------
The SIMH vax.ini script contains the following. You can see that xq is
defined as eth1 which in SIMH parlance is the 2nd ethernet interface and
from the start-up trace it can be seen that the correct network
interface, eth3, is being picked up and used.
%<----------%<---------%<----------
msw at hpm:/usr/local/vax/data$ more vax.ini
;add CPU microcode
;load -r /usr/local/vax/data/ka655.bin
;
; Attach non-volatile RAM to a file
attach nvr /usr/local/vax/data/nvram.bin
;
; This virtual machine has 512m memory
set cpu 512m
;
; Define disk drive types. RA92 is largest-supported VAX drive.
set rq0 ra92
set rq1 ra92
;set rq2 ra92
set -B rq2 rauser=300000
;set -B rq3 rauser=20000
;set rq3 cdrom
;
; Attach defined drives to local files
attach rq0 /usr/local/vax/data/d0.dsk
attach rq1 /usr/local/vax/data/d1.dsk
attach rq2 /usr/local/vax/data/dsa3-archive.dsk
;attach rq3 /tmp/d3.dsk
;
; Attach the CD-ROM to its file (read-only)
;attach -r rq3 /usr/local/vax/data/vaxvmscd.iso
;attach -r rq3 /usr/local/vax/data/softwareproducts1.iso
;attach -r rq3 /usr/local/archive/OpenVMS/7.3-VAX/SPL1-VAXBINJUN043.iso
;
; Disable unused devices. It's also possible to disable individual devices,
; using a construction like "set rq2 disable" if desired.
;
set rl disable
set ts disable
;
; Attach Ethernet to a network interface
set xq mac=00:27:19:b1:6f:84
attach xq eth1
set vh enable
att vh 2023
set cpu idle=VMS
set cpu conhalt
dep bdr 0
;
; Now start the emulator
boot cpu
exit
%<----------%<---------%<----------
I have tried both the same and different MAC addresses in the SIMH
configuration for 'xq mac' compared to the actual network card. Alas, no
joy:
%<----------%<---------%<----------
%%%%%%%%%%% OPCOM 22-SEP-2014 08:45:55.13 %%%%%%%%%%%
Message from user DECNET on SIMVAX
DECnet event 4.18, adjacency down
That is my user mode router, it may not be a problem on your side. I am not at home to investigate. Is anyone else getting failures from area 5?
From: Mark Wickens
Sent: 22/ 09/ 2014 08:52
To: hecnet at Update.UU.SE
Subject: [HECnet] Ubuntu 14.04 SIMH Network Woes
As Johnny knows I've been experiencing some configuration issues since
installing Ubuntu 14.04 on the server that hosts the SIMH instance that
is SIMVAX. I attempted a Kubuntu upgrade but that failed so I had no
resort other than to backup the existing root partition and re-install
from scratch.
I've been unable to configure the networking correctly since the
re-install. The symptom is adjacency up and down messages, coming in
consecutively every minute or so. I've tried numerous combinations of
configuration that have not solved the connectivity issues. When
adjacency is up I'm able to DIR MIM:: successfully.
%<----------%<---------%<----------
$ dir mim::
Directory MIM::DU4:[DECNET]
LOGIN.CMD;1 HECNET.CMD;1 MAKEFILE.;33 MAKEFILE.;43
FIX.LOG;52 MAKEFILE.;34 FIX.LOG;53 NODENAMES.DAT;2
FIX.LOG;61 NODENAMES.DAT;3 FIX.LOG;54 FIX.LOG;55
FIX.LOG;65 FIX.LOG;56 MAKEFILE.;32 MAKEFILE.;44
FIX.LOG;57 FIX.LOG;58 NODENAMES.DAT;4 FIX.LOG;59
%<----------%<---------%<----------
My SIMH boot is as follows:
%<----------%<---------%<----------
MicroVAX 3900 simulator V4.0-0 Beta git commit id: 7154ca1f
NVR: buffering file in memory
libpcap version 1.2.0
Eth: opened OS device eth3
Listening on port 2023
Loading boot code from ka655x.bin
KA655X-B V5.3, VMB 2.7
Performing normal system tests.
40..39..38..37..36..35..34..33..32..31..30..29..28..27..26..25..
24..23..22..21..20..19..18..17..16..15..14..13..12..11..10..09..
08..07..06..05..04..03..
Tests completed.
Loading system software.
(BOOT/R5:0 DUA0
%<----------%<---------%<----------
I upgraded to SIMH master on the suggesting of Mark Pizolatto when I
wrote the SIMH mailing list with an autoboot failure issue that I've had
for as long as I remember (that turned out to be because I was using an
old kernel ROM image).
My networking configuration on the HP Microserver is as follows:
2 x 1000MB Network Cards
eth2 - The internal card is dedicated to Ubuntu and configured
statically at 192.168.1.126 via ifconfig (I uninstalled NetworkManager
because I have no need for dynamic configuration).
eth3 - A PCI express card that is not configured for Ubuntu. It is
brought up on the understanding that SIMH will provide the necessary
configuration.
My /etc/network/interfaces is as follows:
%<----------%<---------%<----------
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
iface eth2 inet static
address 192.168.1.126
netmask 255.255.255.0
gateway 192.168.1.2
dns-nameservers 192.168.1.2
dns-search hecnet.eu
%<----------%<---------%<----------
My /etc/rc.local script brings up the interfaces:
%<----------%<---------%<----------
# Enable the first network interface for linux use
ifconfig eth2 up
# Bring up the second network interface it's for SIMH use - it is not
configured
ifconfig eth3 up
/bin/bash /usr/local/bridge/bridge.sh
/bin/bash /usr/local/vax/vax.sh
%<----------%<---------%<----------
As you can see it is also responsible for bringing up Johnny's bridge
and the SIMH instance.
After configuration the networking looks like this:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ ifconfig -a
eth2 Link encap:Ethernet HWaddr b4:99:ba:bf:46:e3
inet addr:192.168.1.126 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::b699:baff:febf:46e3/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:5150326 errors:0 dropped:90 overruns:0 frame:0
TX packets:7498843 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2519783275 (2.5 GB) TX bytes:9795156712 (9.7 GB)
Interrupt:18
eth3 Link encap:Ethernet HWaddr 00:27:19:b1:6f:84
inet6 addr: fe80::227:19ff:feb1:6f84/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:131318 errors:0 dropped:49269 overruns:0 frame:0
TX packets:3582 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:32216834 (32.2 MB) TX bytes:488874 (488.8 KB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:45875 errors:0 dropped:0 overruns:0 frame:0
TX packets:45875 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:5883368 (5.8 MB) TX bytes:5883368 (5.8 MB)
%<----------%<---------%<----------
I have no reason to think that the bridge isn't working, when I run it
from the command line I can see that connectivity takes place. I am
running a fresh compile of the latest version with debug on:
%<----------%<---------%<----------
msw at hpm:/usr/local/bridge$ sudo ./bridge -p 4711 -d /usr/local/bridge
d: 4711
Config filename: /usr/local/bridge/bridge.conf
Adding router ''local''. 00000008:32521
Adding router ''update''. 1913ee82:4711
Adding DECnet bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding DECnet bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Adding LAT bridge local.
Trying to match local
Matching against: local
Found match: local == local
Adding LAT bridge update.
Trying to match update
Matching against: local
Matching against: update
Found match: update == update
Host table:
0: local 0.0.0.0:0 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1 Throttle: 0(000)
1: update 130.238.19.25:4711 (Rx: 0 Tx: 0 (Drop rx: 0)) Active: 1
Throttle: 0(000)
Hash of known destinations:
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Setting existing hash to bridge 1
Setting existing hash to bridge 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 1
Adding new hash entry. Port is 0
%<----------%<---------%<----------
The SIMH vax.ini script contains the following. You can see that xq is
defined as eth1 which in SIMH parlance is the 2nd ethernet interface and
from the start-up trace it can be seen that the correct network
interface, eth3, is being picked up and used.
%<----------%<---------%<----------
msw at hpm:/usr/local/vax/data$ more vax.ini
;add CPU microcode
;load -r /usr/local/vax/data/ka655.bin
;
; Attach non-volatile RAM to a file
attach nvr /usr/local/vax/data/nvram.bin
;
; This virtual machine has 512m memory
set cpu 512m
;
; Define disk drive types. RA92 is largest-supported VAX drive.
set rq0 ra92
set rq1 ra92
;set rq2 ra92
set -B rq2 rauser=300000
;set -B rq3 rauser=20000
;set rq3 cdrom
;
; Attach defined drives to local files
attach rq0 /usr/local/vax/data/d0.dsk
attach rq1 /usr/local/vax/data/d1.dsk
attach rq2 /usr/local/vax/data/dsa3-archive.dsk
;attach rq3 /tmp/d3.dsk
;
; Attach the CD-ROM to its file (read-only)
;attach -r rq3 /usr/local/vax/data/vaxvmscd.iso
;attach -r rq3 /usr/local/vax/data/softwareproducts1.iso
;attach -r rq3 /usr/local/archive/OpenVMS/7.3-VAX/SPL1-VAXBINJUN043.iso
;
; Disable unused devices. It's also possible to disable individual devices,
; using a construction like "set rq2 disable" if desired.
;
set rl disable
set ts disable
;
; Attach Ethernet to a network interface
set xq mac=00:27:19:b1:6f:84
attach xq eth1
set vh enable
att vh 2023
set cpu idle=VMS
set cpu conhalt
dep bdr 0
;
; Now start the emulator
boot cpu
exit
%<----------%<---------%<----------
I have tried both the same and different MAC addresses in the SIMH
configuration for 'xq mac' compared to the actual network card. Alas, no
joy:
%<----------%<---------%<----------
%%%%%%%%%%% OPCOM 22-SEP-2014 08:45:55.13 %%%%%%%%%%%
Message from user DECNET on SIMVAX
DECnet event 4.18, adjacency down
Hello!
Mark this is an early morning (for here) out of the blue guess, but
could it be something not quite right on your router?
As for your Ubuntu issues..... It might even be that distribution.
That family can be extremely hard to configure for applications that
aren't normally part of their own packaging....
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Mon, Sep 22, 2014 at 4:30 AM, Mark Wickens <mark at wickensonline.co.uk> wrote:
As an addendum I fired up the RX2660 server running OpenVMS 8.4.
This is TSR2 on 4.12.
There are no adjacency up messages for this box and the bridge doesn't seem
to communicate with it (no debugging generated).
I can directory the remote FAL server directory and SET HOST between the two
boxes which are on the same LAN - but I cannot see MIM:: from TSR2, only
from SIMVAX:: when the adjacencies are up.
Mark.
