| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 397.1 | I've had this too ... | BRSIS6::BUTTIENS | Roger Buttiens | Wed Oct 10 1990 09:36 | 8 |
| Norm,
I've had this too ... but only once. For succeeding registrations I fell into
trouble that is described in note 395.*
Perhaps you can try this ?
/Roger.
|
| 397.2 | Silly rabbitt ... | CLAUDI::PETERS | | Wed Oct 10 1990 12:30 | 5 |
|
Make sure the node is registered with NCP SET/DEF that will produce that
fine and informative error message. Another way to get that error (and
you are guiltless here) is to try and register a Phase V node with the
node4 entity directive. /Claudia
|
| 397.3 | I have the same pb. | TENERE::LAVILLAT | | Wed Nov 07 1990 06:52 | 88 |
|
I have exactly the same problem as described in .0
I did my DNS setup well enough to register all my nodes except one that
always fail with "Internal error in DECnet Phase IV AM.".
I can perform a show on this node, it was correctly defined with NCP
and it is a NodeIV.
Any help ?
Thanks,
Pierre.
PS: A show all attr. on this #$@!% node.
MCC> show node4 hoggar all attr
Node4 63.209
ALL ATTRIBUTES
AT 7-NOV-1990 09:43:28
Address = 63.209
Name = HOGGAR
Active Links = 2
Delay = 1
Physical Address = AA-00-04-00-D1-FC
State = On
Aged Packet Loss = 0 Packets
Connects Received = 6 Connects
Connects Sent = 6 Connects
Counter Creation Time = 6-NOV-1990 15:31:14.55
Maximum Logical Links Active = 11 Links
Node Out-of-Range Packet Loss = 0 Packets
Node Unreachable Packet Loss = 0 Packets
Oversized Packet Loss = 0 Packets
Packet Format Error = 0
Partial Routing Update Loss = 0
Received Connect Resource Errors = 0
Response Timeouts = 3 Timeouts
Seconds Since Last Zeroed = >65535 Seconds
Total Messages Received = 12741 Messages
Total Messages Sent = 12747 Messages
User Bytes Received = 144750 Bytes
User Bytes Sent = 144922 Bytes
Verification Reject = 0
Alias Maximum Links = 32
Broadcast Routing Timer = 180 Seconds
Buffer Size = 576 Bytes
Default Access = Both
Delay Factor = 80
Delay Weight = 5
Identification = "DECnet-VAX V5.3, VMS V5.3 "
Inactivity Timer = 60 Seconds
Incoming Proxy = Enable
Incoming Timer = 45 Seconds
Management Version = V4.0.0
Maximum Address = 1023
Maximum Area = 63
Maximum Area Cost = 1022
Maximum Area Hops = 30
Maximum Broadcast NonRouters = 64
Maximum Broadcast Routers = 32
Maximum Buffers = 100
Maximum Circuits = 16
Maximum Cost = 1022
Maximum Hops = 30
Maximum Links = 32 Links
Maximum Path Splits = 1
Maximum Visits = 63
NonPrivileged User = "DECNET"
NSP Version = V4.1.0
Outgoing Proxy = Enable
Outgoing Timer = 60 Seconds
Pipeline Quota = 10000
Retransmit Factor = 10
Routing Timer = 600 Seconds
Routing Version = V2.0.0
Type = EndNodeIV
Initial Address = 63.209
Initial Management Version = V4.0.0
Initial Maximum Address = 1023
Initial Name = HOGGAR
Initial NonPrivileged Password = "no access rights"
Initial NonPrivileged User = "DECNET"
Initial State = On
Initial Type = EndNodeIV
MCC>
|
| 397.4 | Fixed | TENERE::LAVILLAT | | Mon Nov 12 1990 12:04 | 22 |
|
Since I found what was wrong I will reply myself, it may help someone else.
In fact, as expected, the problem was with DNS (and this surely because I did
something wrong some day).
My node had an old link in the .DNA_NODESYNONYM directory, plus one in the
.DNA_BACKTRANSLATION directory. I removed both links and the register command
succeeded.
Conclusion:
If one node4 fail to register but other succeed, check that this node does not
conflict with another's synonym (this with DNS> SHOW .DNA_NODESYNONYM K LINK),
or does not have a backtranslation in its corresponding
.DNA_BACKTRANSLATION.%Xyy.%Xzz directory.
Hope this will help,
Pierre.
PS: Feel free to reply if I misunderstood my problem, or wrote something wrong.
|
| 397.5 | Some explanation | TOOK::JESURAJ | | Mon Nov 12 1990 18:40 | 58 |
| REF .-1
>Conclusion:
>If one node4 fail to register but other succeed, check that this node does not
>conflict with another's synonym (this with DNS> SHOW .DNA_NODESYNONYM K LINK),
True. Synonym are unique and they must be valid the PHASE IV names. In
fact they should be names of teh existing nodes.
>or does not have a backtranslation in its corresponding
>.DNA_BACKTRANSLATION.%Xyy.%Xzz directory.
When a node is registered, MCC creates a backtranslation softlink.
In that algorithms, it first forms the soft link's name, and then
checks whether such a link exists. If it does not exist then MCC will create
one. If the link exists, MCC verifies whether that link points to the same
object that is being registered. If the link points to the same
object, then MCC will go ahead, else it will flag an error.
Example:
Suppose you have registered a node as follows:
REGISTER NODE4 .DNA_NODE.FOO SYN FOO
This creats a back transalation based on the address of FOO pointing
to the DNS object .DNA_NODE.FOO.
After that by mistake some has deleted entry .DNA_NODE.FOO using
DNS$CONTROL, the back tranaltion will still be there pointing to
DNA_NODE.FOO.
Now if you register,
REGISTER NODE4 .MY_NODE.FOO SYN FOO
MCC will flag an error as the back translation is pointing to
the object .DNA_NODE.FOO not to MY_NODE.FOO
However, if you register using,
REGISTER NODE4 .DNA_NODE.FOO SYN FOO
it should work ok.
Hope this helps.
Jesuraj
|
| 397.6 | disappearing objects handled... | SMAUG::SMARTIN | | Tue Nov 13 1990 12:36 | 6 |
| It's too bad the feature of DNS that causes DNS to delete soft-links
that point no-where, wasn't used when creating the synonym soft links.
That way after some period of time (specified when the softlink was
created) the soft link would go away if it's target disappeared.
Sally
|
| 397.7 | Coming soon to a DECmcc near you... | ALLZS::MORRISON | The Network IS the System | Tue Nov 13 1990 13:31 | 7 |
| > It's too bad the feature of DNS that causes DNS to delete soft-links
> that point no-where, wasn't used when creating the synonym soft links.
That oversight is currently being looked into. We just discovered that
this wasn't done quite recently, and I understand that it will be fixed.
Wayne
|
| 397.8 | Could DECmcc be more specific? | PARZVL::KENNEDY | MaryEllen - CT Engineering | Tue Nov 13 1990 17:29 | 13 |
| It seems that this error during Registration:
The requested operation cannot be completed
MCC Service Error = Internal error in DECnet Phase IV AM.
could mean that the node is not in the NETNODE_REMOTE database, or that there
is an existing softlink (or ...?).
It would be preferable if DECmcc could signal a more specific error message -
e.g. duplicate .DNA_BACKTRANSLATION softlink detected, remote node is unknown...
It would save a lot of troubleshooting time and support calls.
_Mek
|