On 2013-11-17 17:55, Steve Davidson wrote:
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Hmm.. Eventually that would be easy, but the one snag right now is that I still do not have a resolver library for RSX finished. Once I've done this, I can do any such automation quite easily.
It might be that I could set it up using a DECnet-SMTP gateway right now. I just need to check this out a little. Let me come back to you in a day or so. Right now I'm trying to understand how network booting PDP-11s work...
Johnny
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
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
Johnny,
How much effort would be involved for your procedures to send email to a
distribution list announcing a change to the network database? I could
hook that at my end to the running of NetUpdateV2.COM which already
makes use of the file NODENAMES.DAT, that the current procedure
produces. The subject would have to be unique so that the parser could
deal with it. A mail message that looked something like this:
To: @netupdate.dis
Subject: NETUPDATE
Content would be ignored. To subscribe all anyone would have to do
would be to submit a HECnet email address to you. I will volunteer one
right now to test with - SGC::SYSTEM.
Regards,
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Johnny Billquist
Sent: Friday, November 15, 2013 14:22
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Node data update
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II
(KA630) with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
On Fri, 15 Nov 2013, Johnny Billquist wrote:
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II (KA630)
with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
OpenVMS 7.3 booted from MOIRA.
Johnny
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
Afternoon all,
I can't find manuals for the KA41-A based 3100s, so I am flying completely blind.
When I power on the unit, it behing self tests. It never seems to stop self testing. It stays on 0001 1011 for the LEDs and the console repeatedly reports its doing self-tests. I can't find anything that would tell it to not leave the permanent self-test mode. I have removed the communications option for testing purposes but I highly doubt that's related to what's causing this.
Is there some obvious switch I am missing that tells this to exit self-test mode?
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On 2013-11-15 15:49, Cory Smelosky wrote:
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II (KA630)
with 13M RAM in a BA123.
Updated the CPU, thanks. Care to tell what OS?
Johnny
Sent from mobile device that advertises itself for no good reason
On 15 Nov 2013, at 10:20, "Paul_Koning at Dell.com" <Paul_Koning at Dell.com> wrote:
On Nov 15, 2013, at 8:21 AM, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
That's hard to believe.
Yeah. Swapping cards out fixed it anyway. MOYA is now semi functional.
Certainly MOP should deal just fine, unless someone implemented it very badly. Ditto any other DEC protocol. After all, DEC invented the spanning tree algorithm, so handling its implications was just elementary network algorithm design for all of us.
paul
Well, I have recent experience of the problem. That's why I mentioned it.
We did do a LAN reconfiguration at the office. We added a dozen Cisco catalyst switches to get rid of the cable spaghetti we had between racks.
After the reconfiguration I was going to boot some of our Alphas and VAXen - which were now connected to the Catalyst switches - from the Infoserver. Earlier there was no problems at all, but now the boot didn't work at all. As there were no other changes made, I suspected the Catalysts. When monitoring what happened during the boot I found out that when the Ethernet adapter resets the link, the Catalyst starts the spanning tree listening period and blocks all traffic to and from the port until the listening period has ended. Unfortunately that seems to be too long a time for the protocol and the boot never continues.
This was verified on other Catalysts as well.
The solution is to disable spanning tree on the port where a booting node is connected. Then the booting problem is gone.
I think it is an overkill from Cisco to implement spanning tree on every possible switch port. I can understand the point, though, because there are too many LAN users nowadays which don't have a clue of what is happening in the LAN.
Regards,
Kari
On 15.11.2013 17:20, Paul_Koning at Dell.com wrote:
On Nov 15, 2013, at 8:21 AM, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
That's hard to believe.
Certainly MOP should deal just fine, unless someone implemented it very badly. Ditto any other DEC protocol. After all, DEC invented the spanning tree algorithm, so handling its implications was just elementary network algorithm design for all of us.
paul
.
On Nov 15, 2013, at 8:21 AM, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
That's hard to believe.
Certainly MOP should deal just fine, unless someone implemented it very badly. Ditto any other DEC protocol. After all, DEC invented the spanning tree algorithm, so handling its implications was just elementary network algorithm design for all of us.
paul
Hey Johnny,
Update the extended data for MOYA please. She is a MicroVAX II (KA630)
with 13M RAM in a BA123.
Thanks!
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
If you connect the MicroVAX ethernet port to a Cisco switch port, check that the Cisco switch port has spanning tree _disabled_
MOP booting and other low level protocols don't cope well with the spanning tree listening period the switch will enforce when the link is reset.
Regards,
Kari
On 15.11.2013 15:15, Cory Smelosky wrote:
Sent from mobile device that advertises itself for no good reason
On 15 Nov 2013, at 06:14, "Kari Uusim ki" <uusimaki at exdecfinland.org> wrote:
Hi Cory,
You don't happen to use a Cisco switch when you connect the MicroVAX to your LAN?
Yes, actually. There Are 2 Cisco switches in the way.
Regards,
Kari
On 15.11.2013 5:55, Cory Smelosky wrote:
Hello all,
I'm trying to get a MicroVAX II to cluster with MORIA. It's not going so
well:
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:48:59.18 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Volunteered to load request on ESA0 from MOYA
Requested file: DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:49:04.72 %%%%%%%%%%%
Message from user SYSTEM on MOIRA
LANACP MOP V3 Downline Load Service
Load succeeded for MOYA on ESA0
System image, DISK$MOIRA:<SYS10.>[SYSCOMMON.SYSLIB]NISCS_LOAD.EXE (VAX
image)
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.07 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) received VAXcluster membership
request from node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.08 %%%%%%%%%%%
22:50:58.07 Node MOIRA (csid 00010001) proposed addition of node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:50:58.62 %%%%%%%%%%%
22:50:58.61 Node MOIRA (csid 00010001) completed VAXcluster state
transition
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:07.99 %%%%%%%%%%%
22:51:07.99 Node MOIRA (csid 00010001) lost connection to node MOYA
MOIRA::CSMELOSKY$
%%%%%%%%%%% OPCOM 14-NOV-2013 22:51:27.59 %%%%%%%%%%%
22:51:27.49 Node MOIRA (csid 00010001) timed-out lost connection to node
MOYA
The moment it joins the cluster, it immediately loses connectivity.
There's between 5 and 10 milliseconds of latency between the two...but
that shouldn't matter...should it?
As I don't have a SCSI Qbus adapter, and I didn't get the TK50+TQK50 with
it, I can only MOP boot it. 60M disk is also not a lot.
.
