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.
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
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
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
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 <mark at wickensonline.co.uk>
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
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 <mark at wickensonline.co.uk>
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
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
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.
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
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 <mark at wickensonline.co.uk> 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
