[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| 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 |
481.0. "V.1.1 IFT ERROR:SOFTWARE LOGIC ERROR DETECTED" by ROM01::NINNI (Don't worry...be happy) Mon Nov 19 1990 13:30
I'm working on DECmcc v.1.1 IFT
DECmcc (X1.1.0)
Default Entity =
Default Qualifier =
Prompt = MCC>
Indentation = 42
Symbol Name Symbol Value
----------- ------------
STDSTAT : for start (-00:00) duration 00:01:00
I have the following problem, when i try to start a statistic collection
Show Node4 RAISSA All Statistic, STDSTAT
Node4 RAISSA
Statistic
AT 19-NOV-1990 12:16:56
Software logic error detected
!
! <1> = THE TRAFFIC ANALYSIS ON THE NODE4 ENTITY DOESN'T WORK
!
Show Node4 RAISSA Remote Node All Statistic, STDSTAT
Node4 RAISSA Remote Node HATOR
Statistic
AT 19-NOV-1990 12:17:57
Examination of Attributes shows:
Duration = 60 Secs
Outbound Average Message Size = -- Attribute Not Available
Inbound Average Message Size = -- Attribute Not Available
Outbound Message Rate = -- Attribute Not Available
Inbound Message Rate = -- Attribute Not Available
User Level Outbound Byte Rate = 0.117 Bytes/Sec
User Level Inbound Byte Rate = 0.55 Bytes/Sec
Outbound Average Packet Size = -- Attribute Not Available
Inbound Average Packet Size = -- Attribute Not Available
Outbound Packet Rate = 0.1 Packets/Sec
Inbound Packet Rate = 0.1 Packets/Sec
Total Outbound Byte Rate = -- Attribute Not Available
Total Inbound Byte Rate = -- Attribute Not Available
Count of Response Timeouts = 0
Count of Receive Connect Resource Errors = -- Attribute Not Available
Count of Connect Requests Received = 0
Count of Connect Requests Sent = 0
!
! <2> = THE TRAFFIC ANALYSIS OF THE SUB-ENTITIES WORKS FINE
!
Show Node4 RAISSA Remote Node RAISSA All Statistic, STDSTAT
Node4 RAISSA Remote Node RAISSA
Statistic
AT 19-NOV-1990 12:19:00
Examination of Attributes shows:
Duration = 60 Secs
Outbound Average Message Size = -- Attribute Not Available
Inbound Average Message Size = -- Attribute Not Available
Outbound Message Rate = -- Attribute Not Available
Inbound Message Rate = -- Attribute Not Available
User Level Outbound Byte Rate = 0 Bytes/Sec
User Level Inbound Byte Rate = 0 Bytes/Sec
Outbound Average Packet Size = -- Attribute Not Available
Inbound Average Packet Size = -- Attribute Not Available
Outbound Packet Rate = 0 Packets/Sec
Inbound Packet Rate = 0 Packets/Sec
Total Outbound Byte Rate = -- Attribute Not Available
Total Inbound Byte Rate = -- Attribute Not Available
Count of Response Timeouts = 0
Count of Receive Connect Resource Errors = -- Attribute Not Available
Count of Connect Requests Received = 0
Count of Connect Requests Sent = 0
!
! <3> = AGAIN FOR THE SAME REASON OF THE <2> POINT
!
exit
THE QUESTIONS ARE
1) IS IT NORMAL THAT I CAN'T OBTAIN STATISTICS FROM THE NODE WHERE MCC
IS RUNNING (raissa)?
2)WHY CAN'T I OBTAIN ALL THE STATISTICS OF A REMOTE NODE, ALSO IF I HAVE
ALL THE COUNTERS AVAILABLE?
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 481.1 | V1.1 IFT PA errors | TOOK::ANWARUDDIN | Anwar | Mon Nov 19 1990 18:59 | 11 |
| In answer to your questions:
1. You can generate statistics for the node on which MCC is
running. The exception you got indicates there was a problem
in PA. Could you please try without the symbol?
2. The reason some of the attributes are "not available" when
you show remote node statistics is that not all counters
defined for the remote node entity are returned by the AM.
The counters you see when you do a SHOW REMOTE NODE ALL COUNT
are a subset of all counters defined for that subentity.
|