- HECnet - lists @ Update

Alternatives to bridge when running via a dynamic IP address

by bqt＠softjar.se

The question is how long does it take to detect, and is a reboot every time acceptable? Johnny On 2011-09-15 23:40, Steve Davidson wrote: This issue has been dealt with here. The declab.net site runs a dedicated VAX with Multinet that polls the other end at predetermined intervals. When the other ends' address changes this end makes change to the Multinet database and reboots. This software has been in use for well over a year and appears to work very well. It does require the use of DynDNS at the end that changes addresses so that this end can do the lookup. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: Thursday, September 15, 2011 17:14 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Alternatives to bridge when running via a dynamic IP address 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. -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

13 years, 10 months

1
0
0 0

Alternatives to bridge when running via a dynamic IP address

by jeep＠scshome.net

This issue has been dealt with here. The declab.net site runs a dedicated VAX with Multinet that polls the other end at predetermined intervals. When the other ends' address changes this end makes change to the Multinet database and reboots. This software has been in use for well over a year and appears to work very well. It does require the use of DynDNS at the end that changes addresses so that this end can do the lookup. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Mark Wickens Sent: Thursday, September 15, 2011 17:14 To: hecnet at Update.UU.SE Subject: Re: [HECnet] Alternatives to bridge when running via a dynamic IP address 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.

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by hvlems＠zonnet.nl

It should happen before disk access across the CI bus is even possible. ------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: Re: [HECnet] Satellite configuration/NCP crash Verzonden: 15 september 2011 23:29 On 15/09/11 22:27, Peter Coghlan wrote: Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. I would have thought that shutting off decnet will not affect SCS traffic. If it happend that it did, AND there were two or more nodes in the cluster trying to communicate and failing, I would expect one or more nodes that lost quorum to hang for RECNXINTERVAL seconds (by default, 20). After that, one or modes might bugcheck with a CLUEXIT exception. A SSRVEXCEPT exception much more likely indicates something is wrong with the software. Regards, Peter Coghlan. If it helps in the discussion the crash happened very quickly.

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by hvlems＠zonnet.nl

In a scsi cluster the cluster traffic is passed across another bus, like FDDI, ethernet (and possibly memory channel). That is the main difference between SCSI and DSSI. Likewise there is mo decnet over scsi as there is decnet over dssi (and the older CI) ------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 23:27 Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. I would have thought that shutting off decnet will not affect SCS traffic. If it happend that it did, AND there were two or more nodes in the cluster trying to communicate and failing, I would expect one or more nodes that lost quorum to hang for RECNXINTERVAL seconds (by default, 20). After that, one or modes might bugcheck with a CLUEXIT exception. A SSRVEXCEPT exception much more likely indicates something is wrong with the software. Regards, Peter Coghlan.

13 years, 10 months

1
0
0 0

Alternatives to bridge when running via a dynamic IPaddress

by mark＠wickensonline.co.uk

On 15/09/11 22:23, hvlems at zonnet.nl wrote: 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? Possibly. The alternative is a local company, but they don't have a fixed IP address either. Obviously over an ADSL connection we are more likely to get a reliable IP address. However, the problem with this solution is that configuring NAT was an issue last time - they're router was managed by an external company, which put a spanner in the works at the time... However, it might be worth a try again. Regards, Mark.

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by mark＠wickensonline.co.uk

On 15/09/11 22:27, Peter Coghlan wrote: Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. I would have thought that shutting off decnet will not affect SCS traffic. If it happend that it did, AND there were two or more nodes in the cluster trying to communicate and failing, I would expect one or more nodes that lost quorum to hang for RECNXINTERVAL seconds (by default, 20). After that, one or modes might bugcheck with a CLUEXIT exception. A SSRVEXCEPT exception much more likely indicates something is wrong with the software. Regards, Peter Coghlan. If it helps in the discussion the crash happened very quickly.

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by HECNET＠beyondthepale.ie

Unless youLre running an NI cluster. If PEDRIVER is loaded shutting the decnet circuit used by it must crash the node. I would have thought that shutting off decnet will not affect SCS traffic. If it happend that it did, AND there were two or more nodes in the cluster trying to communicate and failing, I would expect one or more nodes that lost quorum to hang for RECNXINTERVAL seconds (by default, 20). After that, one or modes might bugcheck with a CLUEXIT exception. A SSRVEXCEPT exception much more likely indicates something is wrong with the software. Regards, Peter Coghlan.

13 years, 10 months

1
0
0 0

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?

13 years, 10 months

1
0
0 0

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.

13 years, 10 months

1
0
0 0

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.

13 years, 10 months

1
0
0 0

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.

13 years, 10 months

1
0
0 0

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.

13 years, 10 months

1
0
0 0

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 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

13 years, 10 months

1
0
0 0

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

13 years, 10 months

1
0
0 0

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.

13 years, 10 months

1
0
0 0

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.

13 years, 10 months

1
0
0 0

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 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

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by mark＠wickensonline.co.uk

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

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by hvlems＠zonnet.nl

The output of $ mc ncp show circ ewa-0 char will tell you whether it worked: the attribute service must have the value enabled. If that is not the case check: $ mc ncp list circ ewa-0 char The service enabled value must be present and reboot the system to make it effective. You'll see decnet opcom messages only on OPA0 or on a terminal where the command $ REPLY/ENABLE was entered. Hans

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by mark＠wickensonline.co.uk

On Thu, 15 Sep 2011, hvlems at zonnet.nl wrote: Yes the NCP commands work on a standalone VMS (VAX and Alpha) system. Possinle reasons for the failure (that I can think of....): - wrong circuit name - DECnet not configured - phase 5 running, not phase 4 - insufficient privileges - wrong circuit name NCP>show active circuits Active Circuit Volatile Summary as of 15-SEP-2011 10:53:46 Circuit State Loopback Adjacent Name Routing Node EWA-0 on 8.400 (GORVAX) EWA-0 11.2 (MAISA) EWA-0 20.1 (WOPR) EWA-0 1.300 (CTAKAH) EWA-0 1.13 (MIM) - DECnet not configured $$ dir maisa:: Directory MAISA::SYS$SPECIFIC:[FAL$SERVER] INFO.TXT;3 NETSERVER.LOG;62 NETSERVER.LOG;61 NETSERVER.LOG;60 NETSERVER.LOG;59 NETSERVER.LOG;58 NETSERVER.LOG;57 NETSERVER.LOG;56 NETSERVER.LOG;55 NETSERVER.LOG;54 NETSERVER.LOG;53 TEST.EXE;2 Total of 12 files. - phase 5 running, not phase 4 NCP>show executor characteristics Node Volatile Characteristics as of 15-SEP-2011 10:55:56 Executor node = 4.249 (SLAVE) Identification = HP DECnet for OpenVMS Alpha Management version = V4.0.0 Incoming timer = 45 Outgoing timer = 60 Incoming Proxy = Enabled Outgoing Proxy = Enabled NSP version = V4.1.0 Maximum links = 32 Delay factor = 80 Delay weight = 5 Inactivity timer = 60 Retransmit factor = 10 Routing version = V2.0.0 Type = area Routing timer = 600 Broadcast routing timer = 180 Maximum address = 1023 Maximum circuits = 16 Maximum cost = 1022 Maximum hops = 30 Maximum visits = 63 Maximum area = 63 Max broadcast nonrouters = 64 Max broadcast routers = 32 Maximum path splits = 1 Area maximum cost = 1022 Area maximum hops = 30 Maximum buffers = 100 Buffer size = 576 Nonprivileged user id = DECNET Nonprivileged password = SALISPENTS Default access = incoming and outgoing Pipeline quota = 4032 Alias maximum links = 32 Path split policy = Normal Maximum Declared Objects = 31 - insufficient privileges $$ show proc/priv 15-SEP-2011 10:56:45.84 User: SYSTEM Process ID: 20200260 Node: SLAVE Process name: "SYSTEM" Authorized privileges: ACNT ALLSPOOL ALTPRI AUDIT BUGCHK BYPASS CMEXEC CMKRNL DIAGNOSE DOWNGRADE EXQUOTA GROUP GRPNAM GRPPRV IMPERSONATE IMPORT LOG_IO MOUNT NETMBX OPER PFNMAP PHY_IO PRMCEB PRMGBL PRMMBX PSWAPM READALL SECURITY SETPRV SHARE SHMEM SYSGBL SYSLCK SYSNAM SYSPRV TMPMBX UPGRADE VOLPRO WORLD BTW you must use LAT, IP or a locally attached terminal to perform this trick. Logged in via a DECserver providing the serial console: $ telnet decserv 2005 %TELNET-I-TRYING, Trying ... 192.168.1.200 %TELNET-I-SESSION, Session 01, host decserv, port 2005 $$ What happens if you do this, assuming that EWA-0 is correct:: $ mc ncp def circ ewa-0 service enabled $ mc ncp set circ ewa-0 state off $ mc ncp set circ ewa-0 state on $$ mcr ncp NCP>define circuit ewa-0 service enabled NCP>define circuit ewa-0 state off NCP>define circuit ewa-0 state on NCP>show active circuits Active Circuit Volatile Summary as of 15-SEP-2011 10:53:46 Circuit State Loopback Adjacent Name Routing Node EWA-0 on 8.400 (GORVAX) EWA-0 11.2 (MAISA) EWA-0 20.1 (WOPR) EWA-0 1.300 (CTAKAH) EWA-0 1.13 (MIM) NCP>exit That doesn't crash the system, although there is no indication that the state is dropped. Should I proceed with the commands required based on the fact that the commands you gave me didn't cause a crash? Thanks for the help, much appreciated Mark. Hans -----Original Message----- From: Mark Wickens Sender: owner-hecnet at Update.UU.SE Date: Thu, 15 Sep 2011 10:14:28 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: [HECnet] Satellite configuration/NCP crash Guys, 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. This is the first part of the procedure to enable the MOP server. The second part is to configure the MOP service for the VAX satellite. The Alpha is running OpenVMS 8.3 Thanks for the help, Mark. The log is: $$ mcr ncp NCP>define circuit ewa-0 service enabled state on NCP>set circuit ewa-0 state off NCP> %%%%%%%%%%% OPCOM 15-SEP-2011 10:03:37.64 %%%%%%%%%%% Message from user DECNET on SLAVE DECnet event 4.7, circuit down, circuit fault

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by hvlems＠zonnet.nl

Yes the NCP commands work on a standalone VMS (VAX and Alpha) system. Possinle reasons for the failure (that I can think of....): - wrong circuit name - DECnet not configured - phase 5 running, not phase 4 - insufficient privileges BTW you must use LAT, IP or a locally attached terminal to perform this trick. What happens if you do this, assuming that EWA-0 is correct:: $ mc ncp def circ ewa-0 service enabled $ mc ncp set circ ewa-0 state off $ mc ncp set circ ewa-0 state on Hans -----Original Message----- From: Mark Wickens Sender: owner-hecnet at Update.UU.SE Date: Thu, 15 Sep 2011 10:14:28 To: <hecnet at Update.UU.SE> Reply-To: hecnet at Update.UU.SESubject: [HECnet] Satellite configuration/NCP crash Guys, 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. This is the first part of the procedure to enable the MOP server. The second part is to configure the MOP service for the VAX satellite. The Alpha is running OpenVMS 8.3 Thanks for the help, Mark. The log is: $$ mcr ncp NCP>define circuit ewa-0 service enabled state on NCP>set circuit ewa-0 state off NCP> %%%%%%%%%%% OPCOM 15-SEP-2011 10:03:37.64 %%%%%%%%%%% Message from user DECNET on SLAVE DECnet event 4.7, circuit down, circuit fault

13 years, 10 months

1
0
0 0

Satellite configuration/NCP crash

by mark＠wickensonline.co.uk

Guys, 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. This is the first part of the procedure to enable the MOP server. The second part is to configure the MOP service for the VAX satellite. The Alpha is running OpenVMS 8.3 Thanks for the help, Mark. The log is: $$ mcr ncp NCP>define circuit ewa-0 service enabled state on NCP>set circuit ewa-0 state off NCP> %%%%%%%%%%% OPCOM 15-SEP-2011 10:03:37.64 %%%%%%%%%%% Message from user DECNET on SLAVE DECnet event 4.7, circuit down, circuit fault

13 years, 10 months

1
0
0 0

HecNET via 3G Dongle

by mark＠wickensonline.co.uk

Johnny, Thanks for the update. Will you be around on the weekend 8/9th Oct to update your end with an IP address? If possible could we try and update tonight or tomorrow night - I have bought 3G access for three days, so it would be useful to see if it all hangs together before the big day. Is there any diagnostics I can run to check whether the bridge is connected at this end? Can you check the state of the bridge at your end - I cant currently see hecnet from my end - I've looked at the setup but can't see any reason why it shouldn't be working Thanks, Mark.

13 years, 10 months

1
0
0 0

HecNET via 3G Dongle

by bqt＠softjar.se

On 2011-09-14 09:45, Mark Wickens wrote: On 14/09/11 06:29, hvlems at zonnet.nl wrote: The 3G dongle has a different P address and probably in another network. The router must know this. Iif you use DHCP then all nodes behind the new router will get a proper address, default gateway, and DNS server address(es). You wrote that you added a dongle. How does the router now know to use that as its iway to the internet in stead of the wired way? I.e. How is its default route configured? Yes, the router uses the 3G dongle as a substitute to the ADSL connection if it is dropped (or removed). The whole set up of the router remains the same, but clearly the IP address that the router presents itself to the internet is different, as are the nameservers. DHCP is served by a different box, so that remains unaffected. For the most part it works beautifully. You have two "issues". First of all, telnet is not a useful tool to test anything here, since telnet uses tcp, while the bridge uses udp. Second, your connection through the dongle is not accepted by Update, since the bridge program knows the remote IP address, and do not accept packets from random nodes on the internet. So you need to let me know what IP address you have, so that I can put that in my bridge config file. Johnny -- Johnny Billquist || "I'm on a bus || on a psychedelic trip email: bqt at softjar.se || Reading murder books pdp is alive! || tryin' to stay hip" - B. Idol

13 years, 10 months

1
0
0 0

HecNET via 3G Dongle

by wonko＠4amlunch.net

I forget, does the bridge use tcp or udp? Does the bridge program tell you anything? -brian On Sep 13, 2011, at 19:09, Mark Wickens wrote: Well, After a very convoluted route I've got my draytek router up and running with a 3G dongle. I can browser the internet, use telnet etc, but it appears the bridge traffic is not getting through. $$ dir mim:: %DIRECT-E-OPENIN, error opening MIM::*.*;* as input -RMS-E-FND, ACP file or directory lookup failed -SYSTEM-F-UNREACHABLE, remote node is not currently reachable If I manually try and telnet to psilo.update.uu.se port 4711 I get a network is unreachable. If I ping the same address the ping gets through. Is this something to do with a restriction on port numbers? Is there anything we can do about this, or try? Thanks for the help, Mark. Here's a transcript of what I tried. I can also use ssh no problems. atom:/usr/local/bridge# telnet psilo.update.uu.se 4711 Trying 130.238.19.25... Trying 2001:6b0:b:fff0::19... telnet: Unable to connect to remote host: Network is unreachable atom:/usr/local/bridge# ping 130.238.19.25 PING 130.238.19.25 (130.238.19.25) 56(84) bytes of data. 64 bytes from 130.238.19.25: icmp_seq=1 ttl=47 time=132 ms 64 bytes from 130.238.19.25: icmp_seq=2 ttl=47 time=128 ms 64 bytes from 130.238.19.25: icmp_seq=3 ttl=47 time=134 ms On 11/09/2011 20:52, Johnny Billquist wrote: On 2011-09-11 21.45, Mark Wickens wrote: Guys, Looking to tap into your collective knowledge. I'd like to set up a 3G dongle for the DEC Legacy event. The plan will be to add my machine as an area router then other participants machines into that area. Steve Davidson has pointed out that there are decnet numbers allocated for experimental purposes. I think I understand how to setup my 3G dongle to connect to the internet via an ubuntu machine. I am happy setting up a DHCP and DNS server on the same machine. The bit I don't understand is how I would fit the hecnet bridge into this network. Normally on my DSL router I have a port redirection rule setup on port 4711 to point to a Debian based box on my LAN. How would I achieve the same effect on a linux box? If I run the bridge on the same box, does this negate the need for a rule? If all this works, is there a restriction of one decnet area per lan segment? Can I run two areas on my side of the bridge? Thanks for the help, Mark In general, if/when you have a setup like that, it's the same as if you connect your computer directly to the internet. So, your Linux box is at the same location your DSL router is. So, there are no rules to setup to pass a packet through the router. The reason for the rule is that your DSL router acts as a firewall (and possibly NAT), which is what you need to circumvent for the bridge. No firewall/NAT box in between means no need to punch a hole through it. So you should be able to run the bridge directly on that box, and it should work. All however, also depends on what your mobile operator might be doing... Area number for experimental is probably not going to help you, though. You already have an area. Adding more nodes to it is hardly any different than having a new area setup, except that if you setup a new area, you will need an area router for it. I don't really see much point in the "experimental" area we have reserved, but since we have plenty of areas anyway, there is no harm in it. Anyone using that area can expect things to not work though, as someone else might also be using the same area, and conflict/confusion might follow. As for having several different areas on the same lan, no problem. Johnny

13 years, 10 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet