HECnet

hecnet@lists.dfupdate.se

15586 discussions

Alternatives to bridge when running via a dynamic IPaddress

by hvlems＠zonnet.nl

Which is where a dongle was originally designed for: occasionally browsing Inteernet resources where stability of the transmission pipe over any extended interval is unnecessary. Simply put a dongle is not an infrastructure component. There's no friendly neighbour to help you out?

14 years, 3 months

Alternatives to bridge when running via a dynamic IP address

by mark＠wickensonline.co.uk

On 15/09/11 22:03, hvlems at zonnet.nl wrote: Won't the IP address remain unchanged as long as you keep the router up and running? Or would thet be too costly? ------Origineel bericht------ Van: Mark Wickens Afzender: owner-hecnet at Update.UU.SE Aan: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: [HECnet] Alternatives to bridge when running via a dynamic IP address Verzonden: 15 september 2011 22:53 Guys, Might as well explore this as an option. The 3G network enabled Vigor 2800 router that I will be using at the DEC Legacy event appears to be working reasonably well, but unsurprisingly there does appear to be some fluctuation in the IP address. This means that an alternative to Johnny's bridge program might be called for. I have a dynamic DNS reference set up and now updating periodically, hecnet.no-ip.org, the question is what can I use as an alternative to the bridge program which will cope with IP address changes? I seem to remember Multinet tunnels being mentioned in the past, do they support dnydns, or any other technology? Thanks for the help, Mark. Unfortunately not. I've seen three IP address changes in about the same number of hours. I don't know whether this poor performance is down to the completely haphazard location of the dongle, or whether it's always this rubbish but you don't realise when all you're doing is browsing the internet. My experience of using a 3G dongle for anything other than web browsing is very limited! Regards Mark.

14 years, 3 months

Alternatives to bridge when running via a dynamic IP address

by hvlems＠zonnet.nl

Won't the IP address remain unchanged as long as you keep the router up and running? Or would thet be too costly? ------Origineel bericht------ Van: Mark Wickens Afzender: owner-hecnet at Update.UU.SE Aan: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: [HECnet] Alternatives to bridge when running via a dynamic IP address Verzonden: 15 september 2011 22:53 Guys, Might as well explore this as an option. The 3G network enabled Vigor 2800 router that I will be using at the DEC Legacy event appears to be working reasonably well, but unsurprisingly there does appear to be some fluctuation in the IP address. This means that an alternative to Johnny's bridge program might be called for. I have a dynamic DNS reference set up and now updating periodically, hecnet.no-ip.org, the question is what can I use as an alternative to the bridge program which will cope with IP address changes? I seem to remember Multinet tunnels being mentioned in the past, do they support dnydns, or any other technology? Thanks for the help, Mark.

14 years, 3 months

Alternatives to bridge when running via a dynamic IP address

by mark＠wickensonline.co.uk

Guys, Might as well explore this as an option. The 3G network enabled Vigor 2800 router that I will be using at the DEC Legacy event appears to be working reasonably well, but unsurprisingly there does appear to be some fluctuation in the IP address. This means that an alternative to Johnny's bridge program might be called for. I have a dynamic DNS reference set up and now updating periodically, hecnet.no-ip.org, the question is what can I use as an alternative to the bridge program which will cope with IP address changes? I seem to remember Multinet tunnels being mentioned in the past, do they support dnydns, or any other technology? Thanks for the help, Mark.

14 years, 3 months

Satellite configuration/NCP crash

by gerry77＠mail.com

On Thu, 15 Sep 2011 15:46:29 -0400, you wrote: Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. PEDRIVER uses DECnet? I thought that clustering used their own Ethernet packets and that DECnet was merely used for some management functions like SYSMAN. PEDRIVER does NOT use DECnet (Ethertype 0x6003), but a specific SCA protocol (0x6007). If for some reason a NI clustered node looses communication with other cluster members, its activities are temporarily paused and a timer is started; when the timer expires (after RECNXINTERVAL seconds, default 20), the surviving cluster reconfigures itself and goes on without the lost node. Meanwhile, if the lost node reestablishes cluster communications within that interval, everything goes on as before; on the other hand, if the lost node retries to connect after the remaining cluster has reconfigured itself, it receives a sort of negative acknowledge from the cluster connection manager (CNXMAN) and is then forced to crash with a specific CLUEXIT bugcheck code. This is to ensure integrity of the locking database and such. The OP had a different crash (SSRVEXCEPT) which is symptom of a bug, not of a "normal" cluster reconfiguration crash. HTH, :-) G. P.S. The new IPCI interface to PEDRIVER should work in a similar way.

14 years, 3 months

Satellite configuration/NCP crash

by mark＠wickensonline.co.uk

Hi, I'm happy to report that the issues with the MOP configuration were fixed by Hans suggestion to make the configuration changes to the permanent database then rebooting. The satellite is now booting, although the system disk image I had created and transferred to the Alpha is not of the node clustered, so I have more work to do. The satellite node has it's own system disk currently, which is booting, so it would make sense to get that configuration correct, then go through the pain of transferring the system disk image (via an intermediary VAX) back to a drive in the Alpha. As always a learning experience. Thanks for the help, Mark. On 15/09/11 13:38, hvlems at zonnet.nl wrote: Mark, there is a mistake in your first ncp command: it uses SET instead of DEFINE. The ncp define command operates on the permanent database Set modifies the volatile database, somewhat similar to the way SYSGEN works where you WRITE CURRENT (define) or WRITE ACTIVE (set). What is the output of these commands: $ mc ncp show circ ewa-0 char $ mc ncp list circ ewa-0 char The example in the cluster manual tries to minimize decnet downtime. That's why it uses a set circ state off and set circ state on sequence. The state off command crashes your system for some reason. The only reason I can think of is that it is already a cluster member and a boothost. The only way to modify circuit or line attributes is to add or modify them to/in the permanent database and either reboot the entire system or shutdown decnet: $ mc ncp set exec state off Followed by $ @sys$manager:netstart. However if there are active cluster members (also in a SCSI cluster) then shutting decnet will (and must) crash the node. -----Original Message----- From: Mark Wickens<mark at wickensonline.co.uk> Sender: owner-hecnet at Update.UU.SE Date: Thu, 15 Sep 2011 11:55:36 To:<hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Satellite configuration/NCP crash I tried the commands you gave, and this time it crashed again: NCP>set circ ewa-0 service enabled NCP>set circ ewa-0 state off NCP> %%%%%%%%%%% OPCOM 15-SEP-2011 11:39:48.02 %%%%%%%%%%% Message from user DECNET on SLAVE DECnet event 4.7, circuit down, circuit fault

14 years, 3 months

Satellite configuration/NCP crash

by marc＠bluevine.net

Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. PEDRIVER uses DECnet? I thought that clustering used their own Ethernet packets and that DECnet was merely used for some management functions like SYSMAN. --Marc

14 years, 3 months

Satellite configuration/NCP crash

by hvlems＠zonnet.nl

Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. ------Origineel bericht------ Van: Peter Coghlan Afzender: owner-hecnet at Update.UU.SE Aan: hecnet at Update.UU.SE Beantwoorden: hecnet at Update.UU.SE Onderwerp: Re: [HECnet] Satellite configuration/NCP crash Verzonden: 15 september 2011 21:30 I'm following the procedure in the Cluster manual, pp10-9, to configure a VAX satellite from an alpha boot node, and I'm getting a system crash. My question is whether I need to run this procedure with the Alpha in standalone mode, or whether this is a situation requiring a patch, or whether I can get away with something different. NCP commands should work fine when the system is running in normal multiuser mode. The worst that should happen from entering something incorrect is an error message or cutting yourself off if you happen to be logged on via decnet. If a system crash results from doing something in NCP, there is a software error and it is time to go looking for patches or upgrading to a newer version or downgrading to a stable version. Regards, Peter Coghlan.

14 years, 3 months

Satellite configuration/NCP crash

by HECNET＠beyondthepale.ie

I'm following the procedure in the Cluster manual, pp10-9, to configure a VAX satellite from an alpha boot node, and I'm getting a system crash. My question is whether I need to run this procedure with the Alpha in standalone mode, or whether this is a situation requiring a patch, or whether I can get away with something different. NCP commands should work fine when the system is running in normal multiuser mode. The worst that should happen from entering something incorrect is an error message or cutting yourself off if you happen to be logged on via decnet. If a system crash results from doing something in NCP, there is a software error and it is time to go looking for patches or upgrading to a newer version or downgrading to a stable version. Regards, Peter Coghlan.

14 years, 3 months

Satellite configuration/NCP crash

by hvlems＠zonnet.nl

Mark, there is a mistake in your first ncp command: it uses SET instead of DEFINE. The ncp define command operates on the permanent database Set modifies the volatile database, somewhat similar to the way SYSGEN works where you WRITE CURRENT (define) or WRITE ACTIVE (set). What is the output of these commands: $ mc ncp show circ ewa-0 char $ mc ncp list circ ewa-0 char The example in the cluster manual tries to minimize decnet downtime. That's why it uses a set circ state off and set circ state on sequence. The state off command crashes your system for some reason. The only reason I can think of is that it is already a cluster member and a boothost. The only way to modify circuit or line attributes is to add or modify them to/in the permanent database and either reboot the entire system or shutdown decnet: $ mc ncp set exec state off Followed by $ @sys$manager:netstart. However if there are active cluster members (also in a SCSI cluster) then shutting decnet will (and must) crash the node. -----Original Message----- From: Mark Wickens <mark at wickensonline.co.uk> Sender: owner-hecnet at Update.UU.SE Date: Thu, 15 Sep 2011 11:55:36 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] Satellite configuration/NCP crash I tried the commands you gave, and this time it crashed again: NCP>set circ ewa-0 service enabled NCP>set circ ewa-0 state off NCP> %%%%%%%%%%% OPCOM 15-SEP-2011 11:39:48.02 %%%%%%%%%%% Message from user DECNET on SLAVE DECnet event 4.7, circuit down, circuit fault

14 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet