| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3351.1 | >>> show node4 help... <<< | KITFOX::BALL | | Tue Jul 14 1992 17:26 | 146 |
| Hi -
( 1 ) I am currently running DECmcc V1.2.0 on an OpenVMS Vax V6.0
system and have not yet seen that error.
<kitfox_darryl_2> man/e
DECmcc (V1.2.0)
MCC> show node4 kitfox all cha
Node4 4.992
AT 14-JUL-1992 16:05:24 Characteristics
Examination of Attributes shows:
Identification = "DECnet for OpenVMS VAX V6.0"
Management Version = V4.0.0
Incoming Timer = 45 Seconds
Outgoing Timer = 60 Seconds
Incoming Proxy = Enable
Outgoing Proxy = Enable
NSP Version = V4.1.0
Maximum Links = 32 Links
Delay Factor = 80
Delay Weight = 5
Inactivity Timer = 60 Seconds
Retransmit Factor = 10
Routing Version = V2.0.0
Type = EndNodeIV
Routing Timer = 600 Seconds
Broadcast Routing Timer = 180 Seconds
Maximum Address = 1023
Maximum Circuits = 16
Maximum Cost = 1022
Maximum Hops = 30
Maximum Visits = 63
Maximum Area = 63
Maximum Broadcast NonRouters = 64
Maximum Broadcast Routers = 32
Maximum Path Splits = 1
Maximum Area Cost = 1022
Maximum Area Hops = 30
Maximum Buffers = 100
Buffer Size = 576 Bytes
NonPrivileged User = ""
NonPrivileged Password = ""
Default Access = Both
Pipeline Quota = 10000
Alias Maximum Links = 32
MCC> show node4 kitfox all attr
Node4 4.992
AT 14-JUL-1992 16:08:39 All Attributes
Name = KITFOX
Address = 4.992
State = On
Physical Address = AA-00-04-00-E0-13
nmfoperationalState = Enabled
Seconds Since Last Zeroed = 10361 Seconds
User Bytes Received = 5284 Bytes
User Bytes Sent = 5128 Bytes
Total Messages Received = 500 Messages
Total Messages Sent = 552 Messages
Connects Received = 52 Connects
Connects Sent = 52 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 24 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 = 14-JUL-1992 13:15:59.34
Identification = "DECnet for OpenVMS VAX V6.0"
Management Version = V4.0.0
NonPrivileged Password = ""
NonPrivileged User = ""
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
Initial Name = KITFOX
Initial Address = 4.992
Initial Management Version = V4.0.0
Initial NonPrivileged Password = ""
Initial NonPrivileged User = ""
Initial Maximum Address = 1023
Initial Type = EndNodeIV
Initial State = On
MCC>
>>Also, why does MCC always respond with the node address (as in the above
>>example) instead of the registered name or the node4 synonym? This
>>is very irritating, especially when one reads the characteritics
>>for several nodes using a wildcard. It doesn't seem to matter whether
>>I use the registered name or node synonym in the command.
( 2 ) The PhaseIV Access Module always uses the address because on
the actual phase4 network everything must have an address
but everything does not have to have a name. So everything
is handled by address.
The Acess Module allows:
MCC> show node4 1.82
MCC> show node4 1106
MCC> show node4 foo
MCC> show node4 .foo
>> is there any logical/parameter that can be set to change this?
( 3 ) At this time no there isn't...
- darryl
|
| 3351.2 | bu other access modules use the name!!!! | COL01::LUNT | | Wed Jul 15 1992 05:23 | 8 |
| Hello Darryl,
Thanks for the reply. I can understand why the
AM has to use the address to talk with the node, but
other access modules return the name in the output. Would
it be difficult to have this change put on the wish list?
Julie Ann
|
| 3351.3 | >>> using names... <<< | KITFOX::BALL | | Thu Jul 16 1992 11:16 | 14 |
| Hi Julie Ann -
>> Would it be difficult to have this change put on the wish list?
It's now on the wish list... I can't make any promises about
it's priority or when it will be done though. You are correct
it would be nice.
- darryl
|
| 3351.4 | ok, but the entity error???? | COL01::LUNT | | Fri Jul 17 1992 04:17 | 6 |
| Hi Darryl,
Ok, that is acceptable. But do you or anyone else have an
idea on the error I get when showing statistics?
Julie Ann
|
| 3351.5 | | TOOK::STRUTT | Management - the one word oxymoron | Wed Jul 22 1992 18:35 | 20 |
| re: .0 (and .4)
� Buffer Size = 576 Bytes
� administrativeState =
�%MCC-E-NOENTITY, no corresponding entity instance exists
�
� Default Access = Both
This seems a little wierd to me. "administrativeState" does not seem
to fit. Indeed, if I look at another node, running VMS V5.5, I get:
Buffer Size = 576 Bytes
Default Access = Both
Pipeline Quota = 10000
so it looks like either some "unexpected" stuff appeared in the NICE
protocol, or perhaps that your dictionary does not match the software
(e.g. AM) that you are running.
How reproducible is this?
Colin
|
| 3351.6 | get a dump if you want help | TOOK::CALLANDER | MCC = My Constant Companion | Tue Aug 11 1992 13:24 | 13 |
| Colin, you are right on. The noentity error means that we can't
find the info specified in the dictionary. Now the problem with
figuring out which is causing the problem is that the error
gets broadcast to the display by the FCL so sometimes it appears before
or in the middle of the actual attribute causing the problem.
Juile Ann, if you turn on the fcl log bits (define mcc_fcl_pm_log 8)
and
take a look at the dump the codes, it will show us which attribute
is the problem. Take the dump and put it as a response.
thanks
jill
|
| 3351.7 | used by circuit am | TOOK::PURRETTA | | Tue Aug 11 1992 14:59 | 11 |
| Like Jill said, the dump would be helpful. However I may be able to
provide some info about this attribute.
administrativeState is an orphaned attribute in DNA4 and DNA5
and used only by the circuit AM for NMF support. At one time,
someone must have performed some operation using the CIRCUIT AM
against this node. The AdministrativeState attribute is written
to DNS for storage when set. It'd be interesting to see what the
value is from the dump.
John
|