HECnet

hecnet@lists.dfupdate.se

15562 discussions

by gregg.drwho8＠gmail.com

On Wed, Feb 13, 2013 at 8:04 PM, <b4 at gewt.net> wrote: 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 Hello! Because I arranged that. Along with the weather. In fact I also arranged for a mass protest of elves all over Dave's place after the crowd left. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."

12 years, 4 months

NT 4 on AlphaServer es40

by dibi58＠gmail.com

never mind, just read the cisco notes, my bad, is a 3500XL, but I do have some FDDI modules for a 7505, if I can ever get it to run ;-) is probably harder, if not impossible to find fddi for the vax3100 server On 2/13/13, Dave McGuire <mcguire at neurotica.com> wrote: On 02/13/2013 08:05 PM, Dan B wrote: good, I happen to have a cisco 3500, the problem will be to find fddi interfaces for both the vax and the catalyst ... What model, specifically? The 35xxXL models don't have FDDI options. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 4 months

NT 4 on AlphaServer es40

by mcguire＠neurotica.com

On 02/13/2013 08:05 PM, Dan B wrote: good, I happen to have a cisco 3500, the problem will be to find fddi interfaces for both the vax and the catalyst ... What model, specifically? The 35xxXL models don't have FDDI options. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 4 months

NT 4 on AlphaServer es40

by dibi58＠gmail.com

good, I happen to have a cisco 3500, the problem will be to find fddi interfaces for both the vax and the catalyst ... On 2/13/13, Dave McGuire <mcguire at neurotica.com> wrote: On 02/13/2013 07:58 PM, Paul_Koning at Dell.com 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?) The only thing I've ever found that would bridge FDDI to Ethernet *well* was the Cisco Catalyst family. It's easy to go FDDI<->100Mbps Ethernet with that hardware. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 4 months

DECnet-Plus and Phase IV Issues

by b4＠gewt.net

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

12 years, 4 months

NT 4 on AlphaServer es40

by mcguire＠neurotica.com

On 02/13/2013 07:58 PM, Paul_Koning at Dell.com 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?) The only thing I've ever found that would bridge FDDI to Ethernet *well* was the Cisco Catalyst family. It's easy to go FDDI<->100Mbps Ethernet with that hardware. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 4 months

NT 4 on AlphaServer es40

by Paul_Koning＠Dell.com

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?) paul

12 years, 4 months

11/44 vs. 11/84, was Re: [HECnet] NT 4 on AlphaServer es40

by mcguire＠neurotica.com

On 02/13/2013 12:53 PM, Johnny Billquist wrote: I can believe that the 11/84 made the 11/44 obsolete, however. They fulfill the same niche, with the 11/84 being faster, smaller and probably cheaper. How is the 11/84 smaller? It was available in two chassis: one that's takes up about two feet of rack space, and one standard 6U box. The 11/44 is a 6U box as well. Were there other packagings of these machines of which I'm unaware? -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 4 months

NT 4 on AlphaServer es40

by mcguire＠neurotica.com

On 02/13/2013 04:29 PM, Johnny Billquist wrote: I have been thinking about this, anybody knows if a 100 NIC adapter attached to the AUI port would actually go 100MB full duplex on the VAX ? The AUI port already defines you at 10 Mb/s. You need a different ethernet controller, as the speed is decided by the controller and not the PHY. On the Alpha it does, but I have never tried the VAX, I would think it should, it does in the Stromasys and Simh emulators, but I'm guessing. That is because Alphas actually might have a 100 Mbit/s ethernet controller. No VAX that I know of do. An emulated machine is a totally different topic. There you are still emulating a 10 Mb/s interface, even though it might map towards a 100 Mb/s physical backend. 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. -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 4 months

DECnet-Plus and Phase IV Issues

by b4＠gewt.net

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

12 years, 4 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet