| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1732.1 | answers | TOOK::ANWARUDDIN | Anwar | Tue Oct 29 1991 13:04 | 130 |
| My comments start with >>>>>.
>>>> Chapter 4 of the DECmcc Director Use manual defines
>>>> time qualifiers - what is required and what is optional etc.
Any insight to the following problems/issues (2 to 8) will be
greatly appreciated. Note that "Recording" was successfully set up
and all the examples (including # 1) are issued for the same
time period (except with different syntax).
2- If the "In Domain" qualifier is not provided, it fails, but the
Error message is misleading. It is complaining about time! when it
is missing "IN DOMAIN" qualifier.
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45 EVERY :15
UNTIL 17:15
Node4 MKODR1 Circuit SYN-0
AT 25-OCT-1991 17:47:27 Statistics
Cannot read attributes.
MCC Error = 0, T1.0.0,
%MCC-S-COMMON_EXCEPTIO, success with
common exception reply,
Show,
Node4 MKODR1 Circuit SYN-0 ,
Show,
Node4 MKODR1 Circuit SYN-0 ,
Requested data not available for
specified time
>>>> If you do not specify the domain, the request for counters is forwarded to the DECnet Phase
>>>> IV AM. The AM does not save "past" attributes and so it returns an exception. Hence the message.
3 - If you just provide begin and end time it doesn't work.
I don't quite understand why you have to have the "EVERY"qualifier?
Why can't it find one a set of statistics for duration of that
interval (ie: for 1/2 hour) ??
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45 UNTIL -
_MCC> 17:15, IN DOMAIN MKO
%MCC-E-NOPERIODICITY, a period was found with no periodicity.
>>>> The syntax requires it. It has nothing to do with PA. PA does
>>>> not even see this request. Please see the Director Use manual.
4 - This also fails with very misleading error. (I believe it is
looking for "Until" and "Every" qualifiers. But it implies
that RECORDING failed!).
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45, IN DOMAIN MKO
Node4 MKODR1 Circuit SYN-0
AT 25-OCT-1991 17:54:12 Statistics
Requested data not available for specified time
>>>>> PA requires a DURATION to calculate statistics! What you have specified is
>>>>> a time instant (i.e, start and end times are the same).
5 - Don't quite understand when and why you need to use "Duration"
qualifier? In this example it is still looking for "EVERY"
qualifier.
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45 DURATION -
_MCC> 0:30 UNTIL 17:15, IN DOMAIN MKO
%MCC-E-NOPERIODICITY, a period was found with no periodicity.
>>>> Whenever you use UNTIL you must use the EVERY qualifier. You may omit the
>>>> duration but not the EVERY qualifier. The "Duration" qualifier is used
>>>> to specify a time interval.
6 - How about Relative Time??
What is the correct syntax?
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START -1:00, IN DOMAIN MKO
Node4 MKODR1 Circuit SYN-0
AT 25-OCT-1991 17:03:12 Statistics
Software logic error detected
Or:
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START (-1:0), IN
DOMAIN MKO
Node4 MKODR1 Circuit SYN-0
AT 25-OCT-1991 17:05:28 Statistics
Requested data not available for specified time
>>>>> Again you are specifying a time instant. Specify the DURATION in
>>>>> order to get a "time interval".
>>>>> MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START (-1:0) -
>>>>> DURATION 0:30:0, IN DOMAIN MKO
7 - In the PA documentations it is stated that "If you are specifying a
sequence of times, enclose the time you specify in parentheses {()},
after AT START and FOR START". Things seems to work fine
without this rule. Or is there any secret to it?
>>>>> If you want to display statistics at 9:00, 10:15 & 14:35 for a duration of
>>>>> 10 mins, how would you do it? Note that the repeat factor (EVERY qualifier)
>>>>> is not constant.
8 - In the PA documentations, it describes the "AT" qualifier as follow:
"Specifies the exact time at which you want to start the
operation. Can be in the future". It fails to specify
IT CAN NOT BE IN THE PAST.
Should it work with the past data? or the documentation just
missed it?
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, AT START 16:45 -
_MCC> every 0:15:0 UNTIL 17:15, IN DOMAIN MKO
%MCC-W-TIME_ALREADY_PA, scheduled time has already passed
>>>>> We will update the document. You cannot schedule something in the
>>>>> past!
|
| 1732.2 | | MEHR::MEHR | | Thu Oct 31 1991 20:08 | 176 |
|
Hi Anwar,
My comments start with ****.
>>>> Chapter 4 of the DECmcc Director Use manual defines
>>>> time qualifiers - what is required and what is optional etc.
**** Okay. But the TIME syntax is used the most with PA. The PA documentation
**** should also be improved and should have more meaningful examples.
2- Misleading Error message:
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45 EVERY :15
UNTIL 17:15
Node4 MKODR1 Circuit SYN-0
AT 25-OCT-1991 17:47:27 Statistics
Cannot read attributes.
MCC Error = 0, T1.0.0,
%MCC-S-COMMON_EXCEPTIO, success with
common exception reply,
Show,
Node4 MKODR1 Circuit SYN-0 ,
Show,
Node4 MKODR1 Circuit SYN-0 ,
Requested data not available for
specified time
>>>> If you do not specify the domain, the request for counters is forwarded to the DECnet Phase
>>>> IV AM. The AM does not save "past" attributes and so it returns an exception. Hence the message.
**** Another example of confusing error messages!
3 - MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45 UNTIL -
_MCC> 17:15, IN DOMAIN MKO
%MCC-E-NOPERIODICITY, a period was found with no periodicity.
>>>> The syntax requires it. It has nothing to do with PA. PA does
>>>> not even see this request. Please see the Director Use manual.
**** That is my point. I am not saying it is PA's problem.
**** The TIME syntax is too hard to use, too many rules and ifs and buts.
**** It is not user friendly. Believe me I have read all the documentation,
**** and still can't remember it all! I Know I brought this up before and I
**** know I was agreed with, and was told it will improve (don't know when!)
**** But when I hear 'please read the documentation' I need to speak up
**** again and state that this is not a user problem, not when too
**** many customers are complaining about it ( 'it' being the "TIME" syntax -
**** which effects the PA the most).
4 - MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45,
IN DOMAIN MKO
Node4 MKODR1 Circuit SYN-0
AT 25-OCT-1991 17:54:12 Statistics
Requested data not available for specified time
>>>>> PA requires a DURATION to calculate statistics! What you have specified is
>>>>> a time instant (i.e, start and end times are the same).
**** I don't understand "(i.e, start and end times are the same)" !?
**** Why can't "END Time" default to Now? So duration will be 16:45 to NOW;
**** whatever number of hours that comes out!
**** (I believe you though)!
5 - "Duration":
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START 16:45 DURATION -
_MCC> 0:30 UNTIL 17:15, IN DOMAIN MKO
%MCC-E-NOPERIODICITY, a period was found with no periodicity.
>>>> Whenever you use UNTIL you must use the EVERY qualifier. You may omit the
>>>> duration but not the EVERY qualifier. The "Duration" qualifier is used
>>>> to specify a time interval.
**** What if I don't use UNTIL do I still have to use EVERY?
**** That is not what the documentation implies. Director Use Manual, Page 4-20,
**** " DECmcc begins the period of interest at the specific START time,
**** then adds the DURATION time interval to the START time to automatically
**** compute the end of the time period."
**** But:
**** MCC> show node4 mkodr1 cir syn-0 all statistics, for start 12:00 duration -
_NCG_MCC>> :30:0
Node4 mkodr1 Circuit syn-0
AT 29-OCT-1991 14:20:46 Statistics
Cannot read attributes.
MCC Error = 0, T1.0.0,
%MCC-S-COMMON_EXCEPTIO, success with
common exception reply,
Show,
Node4 mkodr1 Circuit syn-0 ,
Show,
Node4 mkodr1 Circuit syn-0 ,
Requested data not available for
specified time
**** What is wrong here?
6 - Relative Time:
>>>>> Again you are specifying a time instant. Specify the DURATION in
>>>>> order to get a "time interval".
>>>>> MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, FOR START (-1:0) -
>>>>> DURATION 0:30:0, IN DOMAIN MKO
**** Okay.
**** But when I issue this exact command, I get the data for these time periods:
**** AT 29-OCT-1991 14:16:24 Statistics
AT 29-OCT-1991 14:16:29 Statistics
AT 29-OCT-1991 14:16:36 Statistics
AT 29-OCT-1991 14:16:42 Statistics
AT 29-OCT-1991 14:16:49 Statistics
AT 29-OCT-1991 14:16:55 Statistics
AT 29-OCT-1991 14:17:01 Statistics
AT 29-OCT-1991 14:17:08 Statistics
AT 29-OCT-1991 14:17:14 Statistics
AT 29-OCT-1991 14:17:20 Statistics
...............................
**** It is calculating the statistics for every 6-7 seconds! I thought I asked
**** it to start one hour before and calculate for every half hour, which
**** means I get 2 results! What am I doing wrong?
8 - In the PA documentations, it describes the "AT" qualifier as follow:
"Specifies the exact time at which you want to start the
operation. Can be in the future". It fails to specify
IT CAN NOT BE IN THE PAST.
Should it work with the past data? or the documentation just
missed it?
MCC> SHOW NODE4 MKODR1 CIR SYN-0 ALL STATISTICS, AT START 16:45 -
_MCC> every 0:15:0 UNTIL 17:15, IN DOMAIN MKO
%MCC-W-TIME_ALREADY_PA, scheduled time has already passed
>>>>> We will update the document. You cannot schedule something in the
>>>>> past!
**** The goal is not to schedule something in the past! the goal is to
**** read the past data. I do not find anywhere that tells the user
**** you can NOT use AT for the past data. Since you can use FOR qualifier
**** for both past and future, the user would think the same applies for AT.
**** Unless the user is told otherwise. it is not obvious, believe me!
Thanks for the answers,
Mahnaz
|
| 1732.3 | Do PAST Time Statistics WORK???? | CSC32::WOESTEMEYER | Why??...Why not!!! | Mon Nov 18 1991 16:12 | 83 |
| Well a continuation of note 1732, which did not have an answer.
Attached is a log file where statistics are being requested on
data that has been recorded. Hpe some one out there has an answer
to this question, ie how can it be done. The documentation show
about 3 different methods, none of which seem to work.
Steve Woestemeyer
CSC/CS
------------------------------------------------------------------
display
! Default Entity =
! Default Qualifier =
! Prompt = MCC>
! Indentation = 42
!
! Symbol Name Symbol Value
! ----------- ------------
! BR : bridge
! CN : concentrator
! N4 : node4
! SH : show
! ST : station
! TS : terminal_server
!
!No notify requests are currently in progress
!Command procedure verification is OFF
!Logging is ON, Logging file is MCC.LOG
!
show domain test member .dna_node.keroon
!Using default ALL IDENTIFIERS
!
!Domain KEROON_NS:.test Member KEROON_NS:.dna_node.keroon
!AT 18-NOV-1991 13:58:16 Identifiers
!
!Examination of attributes shows
! MemberName = KEROON_NS:.dna_node.keroon
!
show record node4 .dna_node.keroon line sva-0 partition counters, in domain test
!
!Node4 KEROON_NS:.dna_node.keroon Line sva-0
!AT 18-NOV-1991 13:59:08
!
!Recording parameters for the partition "Counters" :
! Recording state = SUSPENDED,
! State since = 18-NOV-1991 13:39:04.96,
! Polling period = 0 00:05:00.00,
! Begin time = 18-NOV-1991 12:05:00.00,
! End time = 20-NOV-1991 00:00:00.00,
! Keep age = 45 00:00:00.00,
! Request time = 18-NOV-1991 12:00:59.94,
! Requested by = "WOESTEMEYER",
! Time of last successful poll = "18-NOV-1991 13:35:00.07",
! Number of successful polls = 19,
! Time of last failed poll = "NONE",
! Last poll failure reason = "N/A",
! Number of failed polls = 0,
! Last historical expiration time = "18-NOV-1991 13:35:00.07",
! Time of last expiration failure = "NONE",
! Last expiration failure reason = "N/A",
! Number of expiration failures = 0
!
!
show node4 .dna_node.keroon line sva-0 all stati, for start (18-nov-1991:12:10:00) every 00:05:00 duration 00:05:00 until 18-nov-1991:13:00, in domain test
!
!Node4 KEROON_NS:.dna_node.keroon Line sva-0
!AT 18-NOV-1991 14:04:27 Statistics
!
!Cannot read attributes.
! MCC Error = 0, T1.0.0,
! %MCC-S-COMMON_EXCEPTIO, success with
! common exception reply,
! Show,
! Node4 KEROON_NS:.dna_node.keroon Line
! sva-0 ,
! Show,
! Node4 KEROON_NS:.dna_node.keroon Line
! sva-0 ,
! Requested data not available for
! specified time
!
use log off
!
|
| 1732.4 | RECORDING everything needed? | PATS::WOODCOCK | | Tue Nov 19 1991 18:54 | 17 |
| Hi,
PAST stats do work. We use it every day. Are you recording all that needs to
be recorded? "Circuit" stats are achieved by recording LINE CHAR., CIRCUIT
CHAR., and CIRCUIT COUNTERS. This is a MINIMUM for getting these stats which
would amount to the same command you issued except substitue LINE with CIRCUIT.
I think LINE and CIRCUIT stats are essentially the same if the circuit makeup
is simple (ie. one line for one circuit) so this may not make a difference, but
I'm not positive. Also the LINE SPEED must be set for any circuit which is
not ENET based.
Another indication of a potential problem is that the recording was SUSPENDED.
Was your command issued for a scope of time before the record suspended (didn't
get a chance to see the tail end of your command)?
best regards,
brad...
|
| 1732.5 | not recording enought!!!! | CSC32::WOESTEMEYER | Why??...Why not!!! | Thu Nov 21 1991 10:53 | 12 |
| Thanks to Brad,
Problem was due to close reading of the PA use manual, the only
partition being recorded was counters. Started recording
characteristics and now it works fine.
By the way has anyone else noticed a case sensitivity in the historian?
Just changing the entity name from upper to lower case will in a 'show
record' will make it either work or not work depending on how the
entity was register/added to the domain.
|
| 1732.6 | Release Notes! | TOOK::R_SPENCE | Nets don't fail me now... | Thu Nov 21 1991 16:34 | 6 |
| The case sensitivities are noted in the release notes.
BTW, Brad, for those of us oldtimers here, ENET refers to the
Engineering Net, not Ethernet :-)
s/rob
|