| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3231.1 | Yes, but only from the command line interface | TOOK::PURRETTA | | Tue Jun 23 1992 17:21 | 16 |
|
To answer your question, yes. But you can't manage the extentions software
from the map. You must use FCL.
The WaveI software is DECnet phaseIV with phaseV extensions.
Thus, you must register it as a NODE4, and all your map operations will
be useing the DNA4 AM. You can not register it as a PhaseV node because
the WaveI software will reject a PhaseV request sent to it at the top level
or Global Entity level. So, I would suggest if you want to manage the
extensions software, either select FCL from the applications pull-down,
or simply run MCC from the FCL or command line interface. That way you
can switch between NODE4 and NODE commands. Using FCL and the DNA5 AM you
can give commands like:
MCC> Show NODE waveI routing circuit *
|
| 3231.2 | protocol version skew error | HLFS00::TIMMERMANS_A | | Wed Jun 24 1992 04:43 | 96 |
| Hello,
With every sho NODE command I end up with the response:
show node .utoric routing circuit *
Using default ALL IDENTIFIERS
Node UTRNET_NS:.utoric Routing Circuit *
AT 24-JUN-1992 09:36:25 Identifiers
Connection rejected because of Protocol Version Skew, could be a Phase
IV Node
This is the output of the NODE4 show command
sho node4 .utoric all att
Node4 50.843
AT 24-JUN-1992 09:39:08 All Attributes
Name = UTORIC
Address = 50.843
State = On
Delay = 0
Physical Address = AA-00-04-00-4B-CB
Active Links = 4
nmfoperationalState = Enabled
Seconds Since Last Zeroed = >65535 Seconds
User Bytes Received = 108368 Bytes
User Bytes Sent = 116085 Bytes
Total Messages Received = 200667 Messages
Total Messages Sent = 202563 Messages
Connects Received = 1896 Connects
Connects Sent = 1896 Connects
Response Timeouts = 6 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 21 Links
Aged Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Node Out-of-Range Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Verification Reject = 0
Counter Creation Time = 23-JUN-1992 15:27:01.99
Identification = "DECnet-VAX V5.4E1, VMS
v5.4-1A"
Management Version = V4.0.0
Incoming Timer = 45 Seconds
Outgoing Timer = 60 Seconds
Delay Factor = 80
Delay Weight = 5
Inactivity Timer = 60 Seconds
Maximum Links = 32 Links
NSP Version = V4.1.0
Retransmit Factor = 10
Maximum Area Cost = 1022
Maximum Area Hops = 30
Broadcast Routing Timer = 180 Seconds
Buffer Size = 576 Bytes
Maximum Address = 1023
Maximum Area = 63
Maximum Broadcast NonRouters = 64
Maximum Broadcast Routers = 32
Maximum Buffers = 100
Maximum Circuits = 16
Maximum Cost = 1022
Maximum Hops = 30
Maximum Visits = 63
Routing Timer = 600 Seconds
Routing Version = V2.0.0
Type = EndNodeIV
Default Access = Both
Pipeline Quota = 10000
Alias Maximum Links = 32
Incoming Proxy = Enable
Outgoing Proxy = Enable
Maximum Path Splits = 1
Location = -- Attribute Not Available
Implementation Desc = -- Attribute Not Available
Responsible Person = -- Attribute Not Available
Phone Number = -- Attribute Not Available
MAIL Account = -- Attribute Not Available
Remarks = -- Attribute Not Available
Text File = -- Attribute Not Available
Node could not open required file: Permanent Database.
File = Permanent Database,
System Error Message = "%NML-E-OPENIN, error opening
SYS$COMMON:[SYSEXE]NETNODE_LO
CAL.DAT;
as input
-RMS-E-FNF, file not found"
What am I doing wrong??
Adrie
|
| 3231.3 | looks like it *is* a Phase IV node. | TOOK::MCPHERSON | Life is hard. Play short. | Wed Jun 24 1992 09:07 | 28 |
| From the response you got back w/the SHOW NODE4 .utoric all attr, it looks like
utoric *is* a phase IV node. At least it reports itself as an Endnode IV.
Why is it registered as a NODE ?
/doug
<<< Note 3231.2 by
HLFS00::TIMMERMANS_A >>>
-< protocol version skew error >-
Hello,
With every sho NODE command I end up with the response:
show node .utoric routing circuit *
Using default ALL IDENTIFIERS
Node UTRNET_NS:.utoric Routing Circuit *
AT 24-JUN-1992 09:36:25 Identifiers
Connection rejected because of Protocol Version Skew, could be a Phase
IV Node
> Type = EndNodeIV
|
| 3231.4 | registered as NODE4 | HLFS00::TIMMERMANS_A | | Wed Jun 24 1992 09:28 | 14 |
| Hi Doug,
Why is it registered as a NODE ? It's registered as a NODE4.
This node is running DECnet-VAX PhaseIV extension.
Identification = "DECnet-VAX V5.4E1, VMS v5.4-1A"
A customer want to manage the NCL part of this PhaseIV extension via
DECmcc. I am unable to register this as a PhaseV node in DECmcc. But
from the first reply I understand that if the node is registered as
a PhaseIV node you are still able to give PHASEV commands in DECmcc.
Adrie
|
| 3231.5 | NETMAN.COM | TOOK::PURRETTA | | Wed Jun 24 1992 13:52 | 5 |
| It's possible that you have not replaced the NETMAN.COM file on
the target node with the one provided by MCC. We found a version
negotiation problem with the default one and are providing a fixed
version with our kits. It's mentioned in the release notes in the
DECnet PhaseV section.
|
| 3231.6 | It works!!! | HLFS00::TIMMERMANS_A | | Fri Jun 26 1992 08:49 | 5 |
| It works.
Thanks,
Adrie
|