----- Original Message ----- From: "Gregg Levine" <gregg.drwho8 at gmail.com> To: hecnet at update.uu.se Sent: Wednesday, February 13, 2013 8:17:33 PM Subject: Re: [HECnet] DECnet-Plus and Phase IV Issues 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. Wanted to teach me to read documentation, eh? ;) Anyway... ncl> show routing all Node 0 Routing AT 2013-02-13-21:01:02.044-05:00I----- Status UID = C06C438A-7646-11E2-B395-08002BC32EA5 State = On Area Addresses = { } Characteristics Version = V3.0.0 Type = Endnode Maximum Buffers = 65535 Generate Checksums = False Lifetime = 63 Probe Rate = 1000 ES Cache Width = 3 DNA Address Format = True Manual Network Entity Titles = { } Segment Buffer Size = 570 PhaseIV Buffer Size = 576 PhaseIV Address = 9.3 PhaseIV Prefix = 49:: PhaseIV Maximum Visits = 63 ES Cache Holding Time = 600 Inactive Selector = 33 Initialization Timer = 6 Holding Multiplier = 3 Default ESHello Timer = 600 Multicircuit ESHello Timer = 10 Poll ESHello Rate = 50 Routing Mode = Integrated ES Cache Size = 1024 Counters Address Unreachable PDUs Discarded = 3 PDU Format Errors = 0 Error Reports Generated = 0 Unsupported Options = 0 PhaseIV Translation Failures = 0 Creation Time = 2013-02-13-20:35:02.265-05:00I----- As routing is up, it /has/ to be related to the circuit or not having services running or something. b4 at maelona ~ $ arp -a madison.gimme-sympathy.org (10.10.10.1) at 00:0c:29:41:2a:75 [ether] on eth0 ? (10.10.10.18) at aa:00:04:00:03:24 [ether] on eth0 GEWT::B4$ set host 9.3 %SYSTEM-F-UNREACHABLE, remote node is not currently reachable ncl> show routing circuit circuit-1 all Node 0 Routing Circuit circuit-1 AT 2013-02-13-21:05:30.171-05:00I----- Identifiers Name = circuit-1 Status UID = C0721350-7646-11E2-B395-08002BC32EA5 State = On Data Link SDU Size = 1492 Data Link Port = CSMA-CD Port %XFFFFFC0029826188 Characteristics Type = CSMA-CD Data Link Entity = CSMA-CD Station csmacd-1 Enable PhaseIV Address = True Manual Data Link SDU Size = 1492 Manual Routers = { } Inactive Area Address = { } Use PhaseIV Prime = False Counters Data PDUs Received = 12 Data PDUs Fragmented = 0 Data PDUs Transmitted = 0 Circuit Changes = 3 Initialization Failures = 0 Corrupted Hello PDUs Received = 0 Control PDUs Sent = 5 Control PDUs Received = 121 Creation Time = 2013-02-13-20:35:02.303-05:00I----- ncl> show csma-cd station csmacd-1 all Node 0 CSMA-CD Station csmacd-1 AT 2013-02-13-21:06:53.588-05:00I----- Identifiers Name = csmacd-1 Status UID = 2641D5D8-7644-11E2-B395-08002BC32EA5 Communication Port = tu0 Hardware Address = 08-00-2b-c3-2e-a5 State = On MAC Address = aa-00-04-00-03-24 (9.3) Address Filters = { aa-00-04-00-03-24 (9.3) , 09-00-2b-00-00-0f , 09-00-2b-02-01-04 , ab-00-00-04-00-00 , 09-00-2b-00-00-04 , cf-00-00-00-00-00 } Receive Mode = Normal Counters Octets Received = 52200 Octets Sent = 7613 PDUs Received = 241 PDUs Sent = 71 Multicast Octets Received = 51484 Multicast Octets Sent = 7265 Multicast PDUs Received = 227 Multicast PDUs Sent = 64 Initially Deferred PDUs Sent = 0 Single Collision PDUs Sent = 0 Multiple Collisions PDUs Sent = 0 Excessive Collisions = 0 Carrier Check Failures = 0 Late Collisions = 0 Collision Detect Check Failures = 0 Frame Check Errors = 3 Frame Size Errors = 0 Send Data Length Errors = 0 Alignment Errors = 0 Frames Too Long = 0 Receive Data Length Errors = 0 Unrecognized Individual Destination PDUs = 0 Unrecognized Multicast Destination PDUs = 252 Data Overruns = 0 Unavailable Station Buffers = 0 Unavailable User Buffers = 0 Station Failures = 0 Creation Time = 2013-02-13-20:16:24.627-05:00I----- All I see is that this should be working. ;) ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature fought the Time Wars, time and again."