| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I have noticed that there is a different way to work between NCP and
DECmcc on Node4 entities.
I'd like to understand why it happens with your help.
Giuseppina
I have done the following commands' sequence, zeroing counters on the
specific node:
<1> from NCP: SHOW NODE nodename COUNTERS (two times)
<2> from NCP: TELL nodename SHOW NODE nodename COUNTERS
<3> from NCP: SHOW NODE nodename COUNTERS
<4> from MCC: SHOW NODE4 nodename ALL COUNTERS
<5> from MCC: SHOW NODE4 nodename REMOTE NODE nodename ALL COUNTERS
<6> from NCP: SHOW NODE nodename COUNTERS
<1>
$ mcr ncp
zero node *
show node RAISSA counters
Node Counters as of 19-NOV-1990 11:21:57
Executor node = 46.697 (RAISSA)
5 Seconds since last zeroed
0 Bytes received
0 Bytes sent
0 Messages received
0 Messages sent
0 Connects received
0 Connects sent
0 Response timeouts
0 Received connect resource errors
0 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
show node RAISSA counters
Node Counters as of 19-NOV-1990 11:21:57
Executor node = 46.697 (RAISSA)
5 Seconds since last zeroed
0 Bytes received
0 Bytes sent
0 Messages received
0 Messages sent
0 Connects received
0 Connects sent
0 Response timeouts
0 Received connect resource errors
0 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
! <1> = The results of the command SHOW demonstrate that "SHOW NODE .."
! command doesn't use the DNA Stack.
!
<2>
tell RAISSA show node RAISSA counters
Node Counters as of 19-NOV-1990 11:21:59
Executor node = 46.697 (RAISSA)
7 Seconds since last zeroed
21 Bytes received
19 Bytes sent
7 Messages received
8 Messages sent
1 Connects received
1 Connects sent
0 Response timeouts
0 Received connect resource errors
2 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
! <2> = With the TELL command, I use the DNA stack; the bytes send and
! received counters change, but the reported values are referred
! to the time before the answer has been sent.
!
<3>
show node RAISSA counters
Node Counters as of 19-NOV-1990 11:21:59
Executor node = 46.697 (RAISSA)
7 Seconds since last zeroed
106 Bytes received
103 Bytes sent
11 Messages received
12 Messages sent
1 Connects received
1 Connects sent
0 Response timeouts
0 Received connect resource errors
2 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
! <3> = In order to know how many bytes (sent and received) are
! trasmitted for a "TELL nodename SHOW nodename counter" request
! i need to do a SHOW command again (after <1> and <2>)
!
exit
$ !
$ ! What does it happen with DECmcc?
$!
<4>
$ mcc
DECmcc (X1.1.0)
show node4 RAISSA all counters
Node4 46.697
Counters
AT 19-NOV-1990 11:22:10
Examination of Attributes shows:
Counter Creation Time = 19-NOV-1990 11:21:52.85
Seconds Since Last Zeroed = 18 Seconds
User Bytes Received = 106 Bytes
User Bytes Sent = 103 Bytes
Total Messages Received = 11 Messages
Total Messages Sent = 12 Messages
Connects Received = 1 Connects
Connects Sent = 1 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
Maximum Logical Links Active = 2 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
!
! <4> = This command is like to SHOW NODE ... in NCP language
! The counters don't change
!
<5>
show node4 RAISSA remote node RAISSA all counters
Node4 RAISSA Remote Node 46.697
Counters
AT 19-NOV-1990 11:22:13
Examination of Attributes shows:
Counter Creation Time = 19-NOV-1990 11:21:52.01
Seconds Since Last Zeroed = 21 Seconds
User Bytes Received = 106 Bytes
User Bytes Sent = 103 Bytes
Total Messages Received = 11 Messages
Total Messages Sent = 12 Messages
Connects Received = 1 Connects
Connects Sent = 1 Connects
Response Timeouts = 0 Timeouts
Received Connect Resource Errors = 0
! <5> = The counters don't change
exit
<6>
$ mcr ncp
show node RAISSA counters
Node Counters as of 19-NOV-1990 11:22:16
Executor node = 46.697 (RAISSA)
24 Seconds since last zeroed
106 Bytes received
103 Bytes sent
11 Messages received
12 Messages sent
1 Connects received
1 Connects sent
0 Response timeouts
0 Received connect resource errors
2 Maximum logical links active
0 Aged packet loss
0 Node unreachable packet loss
0 Node out-of-range packet loss
0 Oversized packet loss
0 Packet format error
0 Partial routing update loss
0 Verification reject
! <6> = You can see that the counters' values are the same of the
! previous call to the NCP (see <3>).
!
exit
I have obtained the following results:
QUESTION: (From <1> to <6>) I can assume two things:
a) The two MCC operations "show node4 XYZ ..." and
"show node4 XYZ remote node XYZ ..." are equivalent. Is it
true?
b) The obtained values with the two commands are the same
but i'd like to know if they change for the presentation
only, or they are physically duplicated.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 480.1 | Some help with mapping MCC -> NCP entities | NAC::SCHLENER | Mon Nov 19 1990 16:28 | 46 | |
I spent a little time looking at the results. Basically, DECnet Phase
IV AM (That which responds to the NODE4 requests) supports most of what
NCP Phase IV does (I should know - I wrote the NICE encoder/decoder for
DECnet Phase IV AM).
The key with your information is understanding the point of reference.
Bascially, MCC doesn't use the concept of "executor" like NCP does.
MCC, in theory, doesn't care what node it resides on.
The NODE4 global entity identifies the executor (the point of reference).
Basically, NODE4 is just like using TELL node-id when using NCP.
So if you do an MCC> SHOW NODE4 xyz counters, that maps directly to
NCP> TELL xyz SHOW EXEC COUNTERS.
The concept of the node entity in NCP and the remote node entity in MCC
are the same.
SO...
a basic entity equivalence table
MCC NCP
--- ---
NODE4 executor (TELL node-id)
REMOTE NODE NODE
CIRCUIT CIRCUIT
LINE LINE
ADJACENT NODE CIRCUIT circuit-id ADJACENT
NODE node-id
OBJECT OBJECT
AREA AREA
LINK LINK
LOCAL SINK LOGGING
OUTBOUND STREAM node-id REMOTE SINK LOGGING ... SINK NODE
If you work on that mapping, you'll notice how things start to match
up.
So for instance an MCC> SHOW NODE4 nodename REMOTE NODE nodename2 ALL
COUNTERS would map to a NCP> TELL nodename SHOW NODE nodename2 COUNTERS.
Let me know if you'd like some more MCC -> NCP mappings. I'm pretty
good at it!
Cindy
| |||||