On Wed, Jun 4, 2014 at 8:05 AM, Peter Lothberg <roll at stupi.se> wrote:
> My tunnels to you have been administratively shutdown as they have never
> been up before.
Why are there tunnels that are shutdown?
I shut them down as the tunnels were configured, but your end never came up. It has been mentioned a few times on the list, but nothing seemed to change. So, rather than put the configuration in a note somewhere (and lose it) I just shut them down.
(I can't grasp the concept, it's either up and working, or not at all?)
> shutdown". Here is the configuration in my router for the tunnels to you:
When I do something like "show decnet interfaces" those tunnels that are not working show up as 2 lines, rather than several. There are other reasons too, but this is what works for me :-)
> tunnel source FastEthernet0/0
You can put an IP address here, the same way as destination, and I
could check if I had teh corresponding tunnel.
I don't use the IP as my Cisco 1841 (previously a DECbrouter90) is behind a Cisco 800. However, my static IP is: 120.146.225.243.
> tunnel path-mtu-discovery
This does *NOT* work on the boxes I have, they are to small to run the
newer SW. (This is a no_op anyway, as there is no fragmentation code,
if the path_mtu is smaller than 576+gre+ip, packet is lost...)
I had the same issue when I was originally running my DECbrouter90 (before the power supply gave up). I have switched this option off.
Regards, Tim.
My tunnels to you have been administratively shutdown as they have never
been up before.
Why are there tunnels that are shutdown?
(I can't grasp the concept, it's either up and working, or not at all?)
shutdown". Here is the configuration in my router for the tunnels to you:
tunnel source FastEthernet0/0
You can put an IP address here, the same way as destination, and I
could check if I had teh corresponding tunnel.
tunnel path-mtu-discovery
This does *NOT* work on the boxes I have, they are to small to run the
newer SW. (This is a no_op anyway, as there is no fragmentation code,
if the path_mtu is smaller than 576+gre+ip, packet is lost...)
--P
On Wed, Jun 4, 2014 at 6:50 AM, Peter Lothberg <roll at stupi.se> wrote:
Out of the configured tunnels from the Cisco in Uppsala, there is only one
active tunnel not to area59....
interface Tunnel1099
description tunnel to Mark G Thomas <mark at misty.com> (Area 23)
no ip address
logging event subif-link-status
decnet cost 10
tunnel source Ethernet0
tunnel destination 71.246.8.102
is it safe to remove the rest, assuming they are "historical"?
Hi Peter,
The other tunnels are all up:
a12rtr>show decnet neigh
Net Node Interface MAC address Flags
0 9.1023 Tunnel52 0000.0000.0000 A
0 23.1023 Tunnel59 0000.0000.0000 A
0 42.1022 Tunnel51 0000.0000.0000 A
0 52.1023 Tunnel50 0000.0000.0000 A
0 61.1023 Tunnel53 0000.0000.0000 A
0 12.2 FastEthernet0/0 aa00.0400.0230
0 12.3 FastEthernet0/0 aa00.0400.0330
My tunnels to you have been administratively shutdown as they have never been up before. The tunnel to Mark Darvill does not appear to be working correctly at the moment, he likely sorting out his network or configuration.
For interests sake I have just set all the tunnel interfaces to you to "no shutdown". Here is the configuration in my router for the tunnels to you:
interface Tunnel54
description HECnet tunnel for Peter Lothberg Reston VA (Area 59) [Version:218]
no ip address
decnet cost 20
tunnel source FastEthernet0/0
tunnel destination 199.0.131.2
tunnel path-mtu-discovery
!
interface Tunnel55
description HECnet tunnel for Peter Lothberg Stockholm Sweden (Area 59) [Version:218]
no ip address
decnet cost 20
tunnel source FastEthernet0/0
tunnel destination 192.108.200.213
tunnel path-mtu-discovery
!
interface Tunnel56
description HECnet tunnel for Peter Lothberg Uppsala (Area 59) [Version:218]
no ip address
decnet cost 20
tunnel source FastEthernet0/0
tunnel destination 130.238.19.60
tunnel path-mtu-discovery
!
Regards, Tim.
Out of the configured tunnels from the Cisco in Uppsala, there is only one
active tunnel not to area59....
interface Tunnel1099
description tunnel to Mark G Thomas <mark at misty.com> (Area 23)
no ip address
logging event subif-link-status
decnet cost 10
tunnel source Ethernet0
tunnel destination 71.246.8.102
is it safe to remove the rest, assuming they are "historical"?
-P
On 4 Jun 2014, at 00:58, Jordi Guillaumes i Pons <jg at jordi.guillaumes.name> wrote:
My personal experience with the RaspPi and the SD cards is the card slot in the Pi brokes with ease, so I avoid switching the cards as much as posible. Any minimal lost of contact between the card and the slot leads to a corrupted and (usually) unrecoverable filesystem, so my VAXen are in a real HD, and my cards are really microSDs inserted into an adapter, which is inserted into the Pi and is never moved out.
Hmm, never actually changed the SD card in my Pi, it's sort of a fire-and-forget device for me, seems very reliable though (uptime = 334 days, and the last reboot was due to a power outage) - aside from the physical problems you pointed out..
El 03/06/2014, a les 23.30, Sampsa Laine <sampsa at mac.com> va escriure:
I can second that, HPIVAX has been up for like 18 months, no problems whatsoever.
Sampsa
My personal experience with the RaspPi and the SD cards is the card slot in the Pi brokes with ease, so I avoid switching the cards as much as posible. Any minimal lost of contact between the card and the slot leads to a corrupted and (usually) unrecoverable filesystem, so my VAXen are in a real HD, and my cards are really microSDs inserted into an adapter, which is inserted into the Pi and is never moved out.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
On 3 Jun 2014, at 22:54, Vern Brownell <vern at brownell.com> wrote:
Hi Fred,
I ve been running SIMH with OpenVMS 7.3 on a Pi for over a year now and it has been rock solid. Just checked with SH SYS, it s been up for 224 days straight with a fair amount of daily activity and no noticeable degradation in performance. Runs more reliably than my AXP hardware. FWIW YMMV.
And 8GB SD cards are now about $5 on AMZN.
Best of luck,
I can second that, HPIVAX has been up for like 18 months, no problems whatsoever.
Sampsa
El 03/06/2014, a les 21.38, Fred <fcoffey at misernet.net> va escriure:
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
Is it as simple as perhaps mounting the VAX .dsk via NFS and letting SIMH use that, instead of the card?
I'm using an USB disk for the emulators (actually, all my rootfs is in that disk). On my "testing" raspi I mount an NFS partition, just as you said.
Jordi Guillaumes i Pons
jg at jordi.guillaumes.name
HECnet: BITXOV::JGUILLAUMES
Hi Fred,
I ve been running SIMH with OpenVMS 7.3 on a Pi for over a year now and it has been rock solid. Just checked with SH SYS, it s been up for 224 days straight with a fair amount of daily activity and no noticeable degradation in performance. Runs more reliably than my AXP hardware. FWIW YMMV.
And 8GB SD cards are now about $5 on AMZN.
Best of luck,
Vern
On Jun 3, 2014, at 12:38 PM, Fred <fcoffey at misernet.net> wrote:
Hi all,
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
Is it as simple as perhaps mounting the VAX .dsk via NFS and letting SIMH use that, instead of the card?
Thanks,
Fred
----
Lets call it for what it is - "legacy" is a term that people use in a
polite but derogatory manner to imply that the future direction they
prefer is not that which they view as the current direction.
On Jun 3, 2014, at 3:38 PM, Fred <fcoffey at misernet.net> wrote:
Hi all,
For those of you who are running SIMH on Raspberry Pi, how are you getting around the fact that lots of writes on your SD card will eventually trash it? I am considering moving my VAX instance to my Raspi, but didn't want to eat an SD card ... ;)
It s worth doing the experiment to see whether (and when) this is a problem in practice. Flash storage devices like SD cards do wear leveling , and if that s implemented reasonably well, you can get a lot of life out of a card. The other consideration is that they only cost a couple of dollars, so why worry about it (given adequate backup)?
paul
