On 14 Feb 2013, at 08:39, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
On 14.2.2013 15:19, b4 at gewt.net wrote:
----- Original Message -----
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Thursday, February 14, 2013 4:35:59 AM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
Version mismatch between DECnet kit and the o/s perhaps?
I run DECnet phase V on three True64 systems, V5.0A, V5.1A and -B.
No problems. What decnet kit are you using?
Whatever version was included with the xxa31a kit...I was unable to find the proper DECnet kit. If you have it, could you give it to me please?
The xxa-kit is a WAN drivers kit. That's not a full DECnet-plus kit. The correct kit is called dna51a .
I can make the kit online tomorrow if nobody else is quicker.
That would explain the issue. ;)
OSF1 missy.gimme-sympathy.org V5.1 732 alpha
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 01:04:49
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
I cannot for the life of me figure out /why/ it would segfault...
----- Original Message -----
From: "Cory Smelosky" <b4 at gewt.net>
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 4:43:58 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13 Feb 2013, at 16:22, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
DECnet-plus (or as called in Tru64unix ; DECnet-OSI) includes everything needed to communicate with DECnet Phase IV nodes. It is only a matter of configuration.
You can use the DECnet-plus for OpenVMS documentation, because NCL vocabulary is exactly the same on both platforms. On Tru64unix the other DECnet related commands differ from OpenVMS; like
SET HOST -> dlogin
DIR -> dls
etc
The DECnet-plus documentation resides at:
http://h71000.www7.hp.com/doc/decnetplus.html
Are you trying to configure your Tru64unix system to communicate with HECNET Phase IV nodes?
If so, why don't you just use the provided configuration tool? That's a lot easier than trying to accomplish the configuration manually.
Yes. And I would use the tool...except it segfaults when I run it.
On 13.2.2013 22:26, b4 at gewt.net wrote:
Can you point me to documentation that mentions how to integrate it with Phase IV? Targeted for Tru64 as well? ;)
Finding documentation that meets both criteria is proving difficult...
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 3:21:29 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
If you have all or some entities already created, you cannot do it again.
You should first shut the DECnet-plus (DECnet-OSI) down to remove all
the entities before you can try to create and enable them again.
There should be template scripts on the system which you can edit to
make them suit your configuration.
It would help a lot to read the DECnet-plus manuals to get a clear
picture of how it works and how to manage it.
On 13.2.2013 20:47, b4 at gewt.net wrote:
bash-4.0# ncl < start_routing.ncl
Node 0 CSMA-CD
AT 2013-02-13-13:27:14.048-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: Already Exists
Node 0 CSMA-CD Station csmacd-1
AT 2013-02-13-13:27:14.062-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: A Station with this name already exists
Node 0
AT 2013-02-13-13:27:14.091-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.114-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.121-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.126-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: No such Entity Instance exists
bash-4.0# cat start_routing.ncl
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set node 0 routing circuit circuit-1 enable phaseiv address true
set node 0 routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable node 0 routing circuit circuit-1
If the stuff already exists, why is the second half of the script failing?
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 1:39:27 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13.2.2013 20:23, b4 at gewt.net wrote:
------------------------------------------------------------------------
*From: *b4 at gewt.net
*To: *hecnet at update.uu.se
*Sent: *Wednesday, February 13, 2013 1:09:03 PM
*Subject: *[HECnet] DECnet-Plus and Phase IV Issues
Hello!
I (think) I am following the correct NCL syntax here...but..
ncl> create node 0 routing circuit csmacd-0 type = csma-cd
ncl> set node 0 routing circuit csmacd-0 data link entity csma-cd
Here should be the data link entity defined completely as is done below.
It would be more clear if you use another name for the routing circuit
entity than is used for the csma-cd station entity.
ncl> set node 0 routing circuit csmacd-0 enable phaseiv address true
ncl> enable node 0 routing circuit csmacd-0
Node 0 Routing Circuit csmacd-0
AT 2013-02-13-13:05:26.514-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: Error specific to this entity's class
REASON: Open Port Failed
Description: The Open Port call to the specified Data Link failed
Any ideas what i'm doing wrong?
____
This is the script:
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set routing circuit circuit-1 enable phaseiv address true
set routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable routing circuit circuit-1
.
.
.
All right.
I don't have the Tru64 kits online anymore. Therefore I always have to dig them out of my cellar when needed.
On 14.2.2013 15:56, hvlems at zonnet.nl wrote:
The dna51a kit is what I had in mind Kari.
I'll put up the entire cd.
-----Original Message-----
From: Kari Uusim ki <uusimaki at exdecfinland.org>
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 15:39:35
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 14.2.2013 15:19, b4 at gewt.net wrote:
----- Original Message -----
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Thursday, February 14, 2013 4:35:59 AM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
Version mismatch between DECnet kit and the o/s perhaps?
I run DECnet phase V on three True64 systems, V5.0A, V5.1A and -B.
No problems. What decnet kit are you using?
Whatever version was included with the xxa31a kit...I was unable to find the proper DECnet kit. If you have it, could you give it to me please?
The xxa-kit is a WAN drivers kit. That's not a full DECnet-plus kit. The
correct kit is called dna51a .
I can make the kit online tomorrow if nobody else is quicker.
OSF1 missy.gimme-sympathy.org V5.1 732 alpha
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 01:04:49
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
I cannot for the life of me figure out /why/ it would segfault...
----- Original Message -----
From: "Cory Smelosky" <b4 at gewt.net>
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 4:43:58 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13 Feb 2013, at 16:22, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
DECnet-plus (or as called in Tru64unix ; DECnet-OSI) includes everything needed to communicate with DECnet Phase IV nodes. It is only a matter of configuration.
You can use the DECnet-plus for OpenVMS documentation, because NCL vocabulary is exactly the same on both platforms. On Tru64unix the other DECnet related commands differ from OpenVMS; like
SET HOST -> dlogin
DIR -> dls
etc
The DECnet-plus documentation resides at:
http://h71000.www7.hp.com/doc/decnetplus.html
Are you trying to configure your Tru64unix system to communicate with HECNET Phase IV nodes?
If so, why don't you just use the provided configuration tool? That's a lot easier than trying to accomplish the configuration manually.
Yes. And I would use the tool...except it segfaults when I run it.
On 13.2.2013 22:26, b4 at gewt.net wrote:
Can you point me to documentation that mentions how to integrate it with Phase IV? Targeted for Tru64 as well? ;)
Finding documentation that meets both criteria is proving difficult...
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 3:21:29 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
If you have all or some entities already created, you cannot do it again.
You should first shut the DECnet-plus (DECnet-OSI) down to remove all
the entities before you can try to create and enable them again.
There should be template scripts on the system which you can edit to
make them suit your configuration.
It would help a lot to read the DECnet-plus manuals to get a clear
picture of how it works and how to manage it.
On 13.2.2013 20:47, b4 at gewt.net wrote:
bash-4.0# ncl < start_routing.ncl
Node 0 CSMA-CD
AT 2013-02-13-13:27:14.048-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: Already Exists
Node 0 CSMA-CD Station csmacd-1
AT 2013-02-13-13:27:14.062-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: A Station with this name already exists
Node 0
AT 2013-02-13-13:27:14.091-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.114-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.121-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.126-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: No such Entity Instance exists
bash-4.0# cat start_routing.ncl
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set node 0 routing circuit circuit-1 enable phaseiv address true
set node 0 routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable node 0 routing circuit circuit-1
If the stuff already exists, why is the second half of the script failing?
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 1:39:27 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13.2.2013 20:23, b4 at gewt.net wrote:
------------------------------------------------------------------------
*From: *b4 at gewt.net
*To: *hecnet at update.uu.se
*Sent: *Wednesday, February 13, 2013 1:09:03 PM
*Subject: *[HECnet] DECnet-Plus and Phase IV Issues
Hello!
I (think) I am following the correct NCL syntax here...but..
ncl> create node 0 routing circuit csmacd-0 type = csma-cd
ncl> set node 0 routing circuit csmacd-0 data link entity csma-cd
Here should be the data link entity defined completely as is done below.
It would be more clear if you use another name for the routing circuit
entity than is used for the csma-cd station entity.
ncl> set node 0 routing circuit csmacd-0 enable phaseiv address true
ncl> enable node 0 routing circuit csmacd-0
Node 0 Routing Circuit csmacd-0
AT 2013-02-13-13:05:26.514-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: Error specific to this entity's class
REASON: Open Port Failed
Description: The Open Port call to the specified Data Link failed
Any ideas what i'm doing wrong?
____
This is the script:
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set routing circuit circuit-1 enable phaseiv address true
set routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable routing circuit circuit-1
.
.
.
There were 100m modules for them. I owned a few. :)
-brian
On 2/14/2013 7:44 AM, hvlems at zonnet.nl wrote:
Yes, big loud ruggedized and extremely reliable, that is a Gigaswitch.
At Fuji we had four of them, all FDDI. We didn't have lfastethernet cards for them, can't remember if they existed at all.
We went to fast ethernet via the DEChub 900 series. It had concentrators and 4 port fast ethernet modules.
-----Original Message-----
From: Brian Hechinger <wonko at 4amlunch.net>
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 07:21:53
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] NT 4 on AlphaServer es40
On Feb 13, 2013, at 19:58, <Paul_Koning at Dell.com> wrote:
On Feb 13, 2013, at 7:47 PM, Dave McGuire wrote:
...
There are faster network interfaces for VAXen, just not Ethernet. It
still wouldn't be an "apples to apples" comparison, but it'd be closer.
True -- FDDI would fit the bill. The hard part is finding the infrastructure. And while FDDI to 10 Mb/s Ethernet bridges are common enough, FDDI to fast Ethernet is probably harder to find. (I'm not sure what DEC products, if any, offer that. Gigaswitch, perhaps?)
Was gigs switch that big honkin' modular backplane deal? Whatever that was called took 100m modules as well as FDDI modules and bridged it. I used to have one of those. Never got it running due to the sheer hugeness of the bastard.
The dna51a kit is what I had in mind Kari.
I'll put up the entire cd.
-----Original Message-----
From: Kari Uusim ki <uusimaki at exdecfinland.org>
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 15:39:35
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 14.2.2013 15:19, b4 at gewt.net wrote:
----- Original Message -----
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Thursday, February 14, 2013 4:35:59 AM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
Version mismatch between DECnet kit and the o/s perhaps?
I run DECnet phase V on three True64 systems, V5.0A, V5.1A and -B.
No problems. What decnet kit are you using?
Whatever version was included with the xxa31a kit...I was unable to find the proper DECnet kit. If you have it, could you give it to me please?
The xxa-kit is a WAN drivers kit. That's not a full DECnet-plus kit. The
correct kit is called dna51a .
I can make the kit online tomorrow if nobody else is quicker.
OSF1 missy.gimme-sympathy.org V5.1 732 alpha
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 01:04:49
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
I cannot for the life of me figure out /why/ it would segfault...
----- Original Message -----
From: "Cory Smelosky" <b4 at gewt.net>
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 4:43:58 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13 Feb 2013, at 16:22, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
DECnet-plus (or as called in Tru64unix ; DECnet-OSI) includes everything needed to communicate with DECnet Phase IV nodes. It is only a matter of configuration.
You can use the DECnet-plus for OpenVMS documentation, because NCL vocabulary is exactly the same on both platforms. On Tru64unix the other DECnet related commands differ from OpenVMS; like
SET HOST -> dlogin
DIR -> dls
etc
The DECnet-plus documentation resides at:
http://h71000.www7.hp.com/doc/decnetplus.html
Are you trying to configure your Tru64unix system to communicate with HECNET Phase IV nodes?
If so, why don't you just use the provided configuration tool? That's a lot easier than trying to accomplish the configuration manually.
Yes. And I would use the tool...except it segfaults when I run it.
On 13.2.2013 22:26, b4 at gewt.net wrote:
Can you point me to documentation that mentions how to integrate it with Phase IV? Targeted for Tru64 as well? ;)
Finding documentation that meets both criteria is proving difficult...
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 3:21:29 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
If you have all or some entities already created, you cannot do it again.
You should first shut the DECnet-plus (DECnet-OSI) down to remove all
the entities before you can try to create and enable them again.
There should be template scripts on the system which you can edit to
make them suit your configuration.
It would help a lot to read the DECnet-plus manuals to get a clear
picture of how it works and how to manage it.
On 13.2.2013 20:47, b4 at gewt.net wrote:
bash-4.0# ncl < start_routing.ncl
Node 0 CSMA-CD
AT 2013-02-13-13:27:14.048-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: Already Exists
Node 0 CSMA-CD Station csmacd-1
AT 2013-02-13-13:27:14.062-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: A Station with this name already exists
Node 0
AT 2013-02-13-13:27:14.091-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.114-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.121-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.126-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: No such Entity Instance exists
bash-4.0# cat start_routing.ncl
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set node 0 routing circuit circuit-1 enable phaseiv address true
set node 0 routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable node 0 routing circuit circuit-1
If the stuff already exists, why is the second half of the script failing?
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 1:39:27 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13.2.2013 20:23, b4 at gewt.net wrote:
------------------------------------------------------------------------
*From: *b4 at gewt.net
*To: *hecnet at update.uu.se
*Sent: *Wednesday, February 13, 2013 1:09:03 PM
*Subject: *[HECnet] DECnet-Plus and Phase IV Issues
Hello!
I (think) I am following the correct NCL syntax here...but..
ncl> create node 0 routing circuit csmacd-0 type = csma-cd
ncl> set node 0 routing circuit csmacd-0 data link entity csma-cd
Here should be the data link entity defined completely as is done below.
It would be more clear if you use another name for the routing circuit
entity than is used for the csma-cd station entity.
ncl> set node 0 routing circuit csmacd-0 enable phaseiv address true
ncl> enable node 0 routing circuit csmacd-0
Node 0 Routing Circuit csmacd-0
AT 2013-02-13-13:05:26.514-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: Error specific to this entity's class
REASON: Open Port Failed
Description: The Open Port call to the specified Data Link failed
Any ideas what i'm doing wrong?
____
This is the script:
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set routing circuit circuit-1 enable phaseiv address true
set routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable routing circuit circuit-1
.
.
.
On 2/13/2013 11:00 AM, Gregg Levine wrote:
Hello!
Group I protest insulting an amusing and almost properly done
spin-off. And as I said that episode wasn't done that way, it was done
using the advanced hardware bought for an interesting film......
It started out as a really fine program but several seasons in it really turned into a soap opera. :)
-brian
On 14.2.2013 15:19, b4 at gewt.net wrote:
----- Original Message -----
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Thursday, February 14, 2013 4:35:59 AM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
Version mismatch between DECnet kit and the o/s perhaps?
I run DECnet phase V on three True64 systems, V5.0A, V5.1A and -B.
No problems. What decnet kit are you using?
Whatever version was included with the xxa31a kit...I was unable to find the proper DECnet kit. If you have it, could you give it to me please?
The xxa-kit is a WAN drivers kit. That's not a full DECnet-plus kit. The correct kit is called dna51a .
I can make the kit online tomorrow if nobody else is quicker.
OSF1 missy.gimme-sympathy.org V5.1 732 alpha
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 01:04:49
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
I cannot for the life of me figure out /why/ it would segfault...
----- Original Message -----
From: "Cory Smelosky" <b4 at gewt.net>
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 4:43:58 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13 Feb 2013, at 16:22, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
DECnet-plus (or as called in Tru64unix ; DECnet-OSI) includes everything needed to communicate with DECnet Phase IV nodes. It is only a matter of configuration.
You can use the DECnet-plus for OpenVMS documentation, because NCL vocabulary is exactly the same on both platforms. On Tru64unix the other DECnet related commands differ from OpenVMS; like
SET HOST -> dlogin
DIR -> dls
etc
The DECnet-plus documentation resides at:
http://h71000.www7.hp.com/doc/decnetplus.html
Are you trying to configure your Tru64unix system to communicate with HECNET Phase IV nodes?
If so, why don't you just use the provided configuration tool? That's a lot easier than trying to accomplish the configuration manually.
Yes. And I would use the tool...except it segfaults when I run it.
On 13.2.2013 22:26, b4 at gewt.net wrote:
Can you point me to documentation that mentions how to integrate it with Phase IV? Targeted for Tru64 as well? ;)
Finding documentation that meets both criteria is proving difficult...
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 3:21:29 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
If you have all or some entities already created, you cannot do it again.
You should first shut the DECnet-plus (DECnet-OSI) down to remove all
the entities before you can try to create and enable them again.
There should be template scripts on the system which you can edit to
make them suit your configuration.
It would help a lot to read the DECnet-plus manuals to get a clear
picture of how it works and how to manage it.
On 13.2.2013 20:47, b4 at gewt.net wrote:
bash-4.0# ncl < start_routing.ncl
Node 0 CSMA-CD
AT 2013-02-13-13:27:14.048-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: Already Exists
Node 0 CSMA-CD Station csmacd-1
AT 2013-02-13-13:27:14.062-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: A Station with this name already exists
Node 0
AT 2013-02-13-13:27:14.091-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.114-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.121-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.126-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: No such Entity Instance exists
bash-4.0# cat start_routing.ncl
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set node 0 routing circuit circuit-1 enable phaseiv address true
set node 0 routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable node 0 routing circuit circuit-1
If the stuff already exists, why is the second half of the script failing?
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 1:39:27 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13.2.2013 20:23, b4 at gewt.net wrote:
------------------------------------------------------------------------
*From: *b4 at gewt.net
*To: *hecnet at update.uu.se
*Sent: *Wednesday, February 13, 2013 1:09:03 PM
*Subject: *[HECnet] DECnet-Plus and Phase IV Issues
Hello!
I (think) I am following the correct NCL syntax here...but..
ncl> create node 0 routing circuit csmacd-0 type = csma-cd
ncl> set node 0 routing circuit csmacd-0 data link entity csma-cd
Here should be the data link entity defined completely as is done below.
It would be more clear if you use another name for the routing circuit
entity than is used for the csma-cd station entity.
ncl> set node 0 routing circuit csmacd-0 enable phaseiv address true
ncl> enable node 0 routing circuit csmacd-0
Node 0 Routing Circuit csmacd-0
AT 2013-02-13-13:05:26.514-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: Error specific to this entity's class
REASON: Open Port Failed
Description: The Open Port call to the specified Data Link failed
Any ideas what i'm doing wrong?
____
This is the script:
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set routing circuit circuit-1 enable phaseiv address true
set routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable routing circuit circuit-1
.
.
.
Yes no problem. As soon as I'm home I'll make them available.
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 13:19:58
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
----- Original Message -----
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Thursday, February 14, 2013 4:35:59 AM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
Version mismatch between DECnet kit and the o/s perhaps?
I run DECnet phase V on three True64 systems, V5.0A, V5.1A and -B.
No problems. What decnet kit are you using?
Whatever version was included with the xxa31a kit...I was unable to find the proper DECnet kit. If you have it, could you give it to me please?
OSF1 missy.gimme-sympathy.org V5.1 732 alpha
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 01:04:49
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
I cannot for the life of me figure out /why/ it would segfault...
----- Original Message -----
From: "Cory Smelosky" <b4 at gewt.net>
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 4:43:58 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13 Feb 2013, at 16:22, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
DECnet-plus (or as called in Tru64unix ; DECnet-OSI) includes everything needed to communicate with DECnet Phase IV nodes. It is only a matter of configuration.
You can use the DECnet-plus for OpenVMS documentation, because NCL vocabulary is exactly the same on both platforms. On Tru64unix the other DECnet related commands differ from OpenVMS; like
SET HOST -> dlogin
DIR -> dls
etc
The DECnet-plus documentation resides at:
http://h71000.www7.hp.com/doc/decnetplus.html
Are you trying to configure your Tru64unix system to communicate with HECNET Phase IV nodes?
If so, why don't you just use the provided configuration tool? That's a lot easier than trying to accomplish the configuration manually.
Yes. And I would use the tool...except it segfaults when I run it.
On 13.2.2013 22:26, b4 at gewt.net wrote:
Can you point me to documentation that mentions how to integrate it with Phase IV? Targeted for Tru64 as well? ;)
Finding documentation that meets both criteria is proving difficult...
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 3:21:29 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
If you have all or some entities already created, you cannot do it again.
You should first shut the DECnet-plus (DECnet-OSI) down to remove all
the entities before you can try to create and enable them again.
There should be template scripts on the system which you can edit to
make them suit your configuration.
It would help a lot to read the DECnet-plus manuals to get a clear
picture of how it works and how to manage it.
On 13.2.2013 20:47, b4 at gewt.net wrote:
bash-4.0# ncl < start_routing.ncl
Node 0 CSMA-CD
AT 2013-02-13-13:27:14.048-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: Already Exists
Node 0 CSMA-CD Station csmacd-1
AT 2013-02-13-13:27:14.062-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: A Station with this name already exists
Node 0
AT 2013-02-13-13:27:14.091-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.114-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.121-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.126-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: No such Entity Instance exists
bash-4.0# cat start_routing.ncl
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set node 0 routing circuit circuit-1 enable phaseiv address true
set node 0 routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable node 0 routing circuit circuit-1
If the stuff already exists, why is the second half of the script failing?
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 1:39:27 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13.2.2013 20:23, b4 at gewt.net wrote:
------------------------------------------------------------------------
*From: *b4 at gewt.net
*To: *hecnet at update.uu.se
*Sent: *Wednesday, February 13, 2013 1:09:03 PM
*Subject: *[HECnet] DECnet-Plus and Phase IV Issues
Hello!
I (think) I am following the correct NCL syntax here...but..
ncl> create node 0 routing circuit csmacd-0 type = csma-cd
ncl> set node 0 routing circuit csmacd-0 data link entity csma-cd
Here should be the data link entity defined completely as is done below.
It would be more clear if you use another name for the routing circuit
entity than is used for the csma-cd station entity.
ncl> set node 0 routing circuit csmacd-0 enable phaseiv address true
ncl> enable node 0 routing circuit csmacd-0
Node 0 Routing Circuit csmacd-0
AT 2013-02-13-13:05:26.514-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: Error specific to this entity's class
REASON: Open Port Failed
Description: The Open Port call to the specified Data Link failed
Any ideas what i'm doing wrong?
____
This is the script:
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set routing circuit circuit-1 enable phaseiv address true
set routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable routing circuit circuit-1
.
.
----- Original Message -----
From: hvlems at zonnet.nl
To: hecnet at Update.UU.SE
Sent: Thursday, February 14, 2013 4:35:59 AM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
Version mismatch between DECnet kit and the o/s perhaps?
I run DECnet phase V on three True64 systems, V5.0A, V5.1A and -B.
No problems. What decnet kit are you using?
Whatever version was included with the xxa31a kit...I was unable to find the proper DECnet kit. If you have it, could you give it to me please?
OSF1 missy.gimme-sympathy.org V5.1 732 alpha
-----Original Message-----
From: b4 at gewt.net
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 01:04:49
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] DECnet-Plus and Phase IV Issues
I cannot for the life of me figure out /why/ it would segfault...
----- Original Message -----
From: "Cory Smelosky" <b4 at gewt.net>
To: hecnet at Update.UU.SE
Cc: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 4:43:58 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13 Feb 2013, at 16:22, Kari Uusim ki <uusimaki at exdecfinland.org> wrote:
DECnet-plus (or as called in Tru64unix ; DECnet-OSI) includes everything needed to communicate with DECnet Phase IV nodes. It is only a matter of configuration.
You can use the DECnet-plus for OpenVMS documentation, because NCL vocabulary is exactly the same on both platforms. On Tru64unix the other DECnet related commands differ from OpenVMS; like
SET HOST -> dlogin
DIR -> dls
etc
The DECnet-plus documentation resides at:
http://h71000.www7.hp.com/doc/decnetplus.html
Are you trying to configure your Tru64unix system to communicate with HECNET Phase IV nodes?
If so, why don't you just use the provided configuration tool? That's a lot easier than trying to accomplish the configuration manually.
Yes. And I would use the tool...except it segfaults when I run it.
On 13.2.2013 22:26, b4 at gewt.net wrote:
Can you point me to documentation that mentions how to integrate it with Phase IV? Targeted for Tru64 as well? ;)
Finding documentation that meets both criteria is proving difficult...
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 3:21:29 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
If you have all or some entities already created, you cannot do it again.
You should first shut the DECnet-plus (DECnet-OSI) down to remove all
the entities before you can try to create and enable them again.
There should be template scripts on the system which you can edit to
make them suit your configuration.
It would help a lot to read the DECnet-plus manuals to get a clear
picture of how it works and how to manage it.
On 13.2.2013 20:47, b4 at gewt.net wrote:
bash-4.0# ncl < start_routing.ncl
Node 0 CSMA-CD
AT 2013-02-13-13:27:14.048-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: Already Exists
Node 0 CSMA-CD Station csmacd-1
AT 2013-02-13-13:27:14.062-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: Error specific to this entity's class
REASON: Already Exists
Description: A Station with this name already exists
Node 0
AT 2013-02-13-13:27:14.091-05:00I-----
FAILED IN DIRECTIVE: Create
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.114-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.121-05:00I-----
FAILED IN DIRECTIVE: Set
DUE TO: No such Entity Instance exists
Node 0 Routing
AT 2013-02-13-13:27:14.126-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: No such Entity Instance exists
bash-4.0# cat start_routing.ncl
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set node 0 routing circuit circuit-1 enable phaseiv address true
set node 0 routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable node 0 routing circuit circuit-1
If the stuff already exists, why is the second half of the script failing?
----- Original Message -----
From: "Kari Uusim ki" <uusimaki at exdecfinland.org>
To: hecnet at Update.UU.SE
Sent: Wednesday, February 13, 2013 1:39:27 PM
Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues
On 13.2.2013 20:23, b4 at gewt.net wrote:
------------------------------------------------------------------------
*From: *b4 at gewt.net
*To: *hecnet at update.uu.se
*Sent: *Wednesday, February 13, 2013 1:09:03 PM
*Subject: *[HECnet] DECnet-Plus and Phase IV Issues
Hello!
I (think) I am following the correct NCL syntax here...but..
ncl> create node 0 routing circuit csmacd-0 type = csma-cd
ncl> set node 0 routing circuit csmacd-0 data link entity csma-cd
Here should be the data link entity defined completely as is done below.
It would be more clear if you use another name for the routing circuit
entity than is used for the csma-cd station entity.
ncl> set node 0 routing circuit csmacd-0 enable phaseiv address true
ncl> enable node 0 routing circuit csmacd-0
Node 0 Routing Circuit csmacd-0
AT 2013-02-13-13:05:26.514-05:00I-----
FAILED IN DIRECTIVE: Enable
DUE TO: Error specific to this entity's class
REASON: Open Port Failed
Description: The Open Port call to the specified Data Link failed
Any ideas what i'm doing wrong?
____
This is the script:
create csma-cd
create csma-cd station csmacd-1 communication port tu0
enable csma-cd station csmacd-1
create routing circuit circuit-1 type csma-cd
#
# The following command sets the inactive area address, which is used
# to enable transmission and receipt of ISO 8473 Inactive Subset PDUs,
# also known as Null Internet. This functionality is disabled by
# default. To enable Null Internet, remove the comment character
# from the following command.
#
create node 0 routing type endnode
set node 0 routing phaseiv address = 9.3
enable node 0 routing
set routing circuit circuit-1 enable phaseiv address true
set routing circuit circuit-1 data link entity csma-cd station csmacd-1
enable routing circuit circuit-1
.
.
Yes, big loud ruggedized and extremely reliable, that is a Gigaswitch.
At Fuji we had four of them, all FDDI. We didn't have lfastethernet cards for them, can't remember if they existed at all.
We went to fast ethernet via the DEChub 900 series. It had concentrators and 4 port fast ethernet modules.
-----Original Message-----
From: Brian Hechinger <wonko at 4amlunch.net>
Sender: owner-hecnet at Update.UU.SE
Date: Thu, 14 Feb 2013 07:21:53
To: hecnet at Update.UU.SE<hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: Re: [HECnet] NT 4 on AlphaServer es40
On Feb 13, 2013, at 19:58, <Paul_Koning at Dell.com> wrote:
On Feb 13, 2013, at 7:47 PM, Dave McGuire wrote:
...
There are faster network interfaces for VAXen, just not Ethernet. It
still wouldn't be an "apples to apples" comparison, but it'd be closer.
True -- FDDI would fit the bill. The hard part is finding the infrastructure. And while FDDI to 10 Mb/s Ethernet bridges are common enough, FDDI to fast Ethernet is probably harder to find. (I'm not sure what DEC products, if any, offer that. Gigaswitch, perhaps?)
Was gigs switch that big honkin' modular backplane deal? Whatever that was called took 100m modules as well as FDDI modules and bridged it. I used to have one of those. Never got it running due to the sheer hugeness of the bastard.
On Feb 13, 2013, at 19:58, <Paul_Koning at Dell.com> wrote:
On Feb 13, 2013, at 7:47 PM, Dave McGuire wrote:
...
There are faster network interfaces for VAXen, just not Ethernet. It
still wouldn't be an "apples to apples" comparison, but it'd be closer.
True -- FDDI would fit the bill. The hard part is finding the infrastructure. And while FDDI to 10 Mb/s Ethernet bridges are common enough, FDDI to fast Ethernet is probably harder to find. (I'm not sure what DEC products, if any, offer that. Gigaswitch, perhaps?)
Was gigs switch that big honkin' modular backplane deal? Whatever that was called took 100m modules as well as FDDI modules and bridged it. I used to have one of those. Never got it running due to the sheer hugeness of the bastard.
