| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 540.1 | Well you asked for it... | WAKEME::ANIL | | Mon Dec 10 1990 20:40 | 28 |
| Try the following:
show node4 nssg line una-0 outbound utilization, at every 0:1:00 until
17:17:00, for start +00:00 duration = 00:00:10
This command will repeat every hour from 1 am to 5:17 pm and will calculate
statistic over a period of 10 seconds.
See the figure below for an explanation:
+--- For start = +00:00 +--- For start = +00:00
| (Always start |
| relative NOW) |
| +-------- DURATION | +-------- DURATION
| | (period over | |
| v which Stats | v
|<- ->| are to be |<- ->|
v v calculated ) v v
+------------------------+---------- . . . ----+---------
^ ^ ^
|<--------- ^ ---------->| |
NOW | UNTIL
+------ EVERY
P.S. I am not trying to justify the above time sytax, just trying to
make the audience undertand the existing time syntax!
Hope its clear ;)
|
| 540.2 | oops, that command will repeat every 1 minute ... | WAKEME::ROBERTS | Keith Roberts - DECmcc Alarms Team | Tue Dec 11 1990 08:55 | 18 |
| RE: 540.1
>> show node4 nssg line una-0 outbound utilization, at every 0:1:00 until
>> 17:17:00, for start +00:00 duration = 00:00:10
This command is not correct .. the 'at every' specifies every minute.
It should be :
show node4 nssg line una-0 outbound utilization, at every 1:00:00 -
until 17:17:00, for start +00:00:00 duration 00:00:10
I'm not sure .. the command may need 'for start (+00:00:00)' .. I know
'at start' needs the parens.
/keith
|
| 540.3 | Use of Time in PA | TOOK::ANWARUDDIN | Anwar | Tue Dec 11 1990 11:03 | 23 |
| re: .0
The default duration to calculate statistics is 5 mins.
>>> show node4 nssg line una-0 outbound utilization, at every 0:1:00 until
17:17:00
This command is requesting `outbound utilization' for a duration of 5 mins
every 1 min. The request should be
show node4 nssg line una-0 outbound utilization, at every 0:1:30 until
17:17:00, for start (+0:00) dura 0:1:00
It is a good idea to make the repeat factor( at every) a little larger than
the duration ( about 30 secs) because of traffic, overhead etc. If it equals
the duration, you will miss every other sample with the message saying that
schedule time has passed. `start (+0:00)' indicates that time is deferred.
It means that the start time is relative to the time specified on the `at'
clause. If you do not specify start (+0:00), you will only get the first
value and the subsequent computations will fail.
Hope this helps.
|
| 540.4 | info on start time | GOSTE::CALLANDER | | Wed Dec 12 1990 12:00 | 9 |
| okay one more two cents.
the for start (+0:00) should automatically default, therefore isn't
needed. Also the for start time does not require parenthesis **and
yes we listened, in the final V1.1 release neither will an AT start
time as long as it is only one time, lists will still require the
parens though**.
|
| 540.5 | How about calculating a default? | NSSG::R_SPENCE | Nets don't fail me now... | Wed Dec 12 1990 13:57 | 10 |
| Gee, shouldn't MCC reduce the duration to a reasonable default if
the intervale is less than 5 minutes? How does the end used decide
what a reasonable number is if it should be "a little less"?
All I wanted to do was display the utilization every minute while
doing a load test. It seems to me that I should only have to tell
it how often I want to see an answer and when to stop if I want it
to do it for a while.
s/rob
|
| 540.6 | ex | JETSAM::COURTRIGHT | | Fri Jan 11 1991 10:05 | 33 |
|
I can't seem to get the statistics to work using the command below I
get back the included error or error in binary time???????
thanks
dave courtright
show node4 bbpk01 line syn-0 outbound utilization, for start 13:00:00 every 1:00:00 until 15:00:00,in domain .pko-24
!
!Node4 bbpk01 Line syn-0
!AT 10-JAN-1991 14:00:00 Statistics
!
!Cannot read attributes.
! MCC Error = 0, T1.0.0,
! %MCC-S-SPECIALIZED_EXC, success with
! management module-specific exception
! reply,
! Show,
! Node4 bbpk01 Line syn-0 ,
! Show,
! Node4 bbpk01 Line syn-0 ,
! Internal error in DECnet Phase IV AM.,
! VMS Error = %SYSTEM-F-ACCVIO,
! access violation,
! reason mask=!XB,
! virtual
! address=!XL,
! PC=!XL, PSL=!XL
!
exit
!
|
| 540.7 | Change FOR to AT! | WAKEME::ANIL | | Fri Jan 11 1991 14:02 | 47 |
| Try the following:
show node4 bbpk01 line syn-0 outbound utilization, At start 13:00:00 every 1:00:00 until 15:00:00,in domain .pko-24
~~~
Don't realy understand the error you got but the above will
accomplish what you want to do.( I.e. calculate the statistics
"outbound utilization" every 1 hour between 13 hrs and 15 hrs, today!)
- Anil Navkal
<<< Note 540.6 by JETSAM::COURTRIGHT >>>
-< ex >-
I can't seem to get the statistics to work using the command below I
get back the included error or error in binary time???????
thanks
dave courtright
show node4 bbpk01 line syn-0 outbound utilization, for start 13:00:00 every 1:00:00 until 15:00:00,in domain .pko-24
!
!Node4 bbpk01 Line syn-0
!AT 10-JAN-1991 14:00:00 Statistics
!
!Cannot read attributes.
! MCC Error = 0, T1.0.0,
! %MCC-S-SPECIALIZED_EXC, success with
! management module-specific exception
! reply,
! Show,
! Node4 bbpk01 Line syn-0 ,
! Show,
! Node4 bbpk01 Line syn-0 ,
! Internal error in DECnet Phase IV AM.,
! VMS Error = %SYSTEM-F-ACCVIO,
! access violation,
! reason mask=!XB,
! virtual
! address=!XL,
! PC=!XL, PSL=!XL
!
exit
!
|
| 540.8 | for to at and a new problem | JETSAM::COURTRIGHT | | Fri Jan 11 1991 14:24 | 7 |
| I did try at and have a new error...
show node4 bbpk01 line syn-0 outbound utilization, at start 00:00:01 every 1:00:00 until 14:00:00, in domain .pko-24
!%MCC-E-ATSYNTAXERR, syntax error in AT qualifier clause
!
exit
!
|
| 540.9 | Sorry I goofed.. | WAKEME::ANIL | | Fri Jan 11 1991 15:56 | 26 |
| Silly me!
Try the following: (I tried it this time before putting it here!)
show node4 bbpk01 line syn-0 outbound utilization, at start +00:00:01 every 1:00:00 until +14:00:00, in domain .pko-24
Now lets see what it is saying:
Start 1 second from now, do it every hour, for next 14 hours.
Now I am not sure what thought you wanted to express, but
if you can tell us the "thought", I am sure we could give you
another wonderful command that will let you do what you want!!
- Anil Navkal
BTW:
The statistics will be calculated over a "Duration" of 5 minutes. So
you will get the first value an hour and 5 minutes and 1 second from now!
All subsequent values will be an hour appart. Hope this TIME I am clear!!
|
| 540.10 | tried and failed | JETSAM::COURTRIGHT | | Mon Jan 14 1991 15:37 | 18 |
|
I tried the command with at and for start and enclosed the errors.
I started recording last friday and would like any commands that
would show stats for the past, present and future.
thanks in advance
djc
show node4 bbpk01 line syn-0 outbound utilization, at start +00:00:01-
every 1:00:00 until +14:00:00, in domain .pko-24
!%MCC-E-ATSYNTAXERR, syntax error in AT qualifier clause
!
show node4 bbpk01 line syn-0 outbound utilization, for start +00:00:01-
every 1:00:00 until +14:00:00, in domain .pko-24
!%MCC-E-DEFER_EVERYUNTI, EVERY and UNTIL not currently supported in Deferred Scope of Interest time
!
exit
!
|
| 540.11 | When in doubt try a space! | WAKEME::ANIL | | Mon Jan 14 1991 18:12 | 28 |
| Well I should have know better before jumping in! Anyway now that
I am fully trapped....
RE:
Part 1
======
>> show node4 bbpk01 line syn-0 outbound utilization, at start +00:00:01-
>> every 1:00:00 until +14:00:00, in domain .pko-24 ^
|
Add an extra space here. FCL does not like a line continuation -----+
at this spot. |
|
Following command will works as typed :-) |
V
show node4 bbpk01 line syn-0 outbound utilization, at start +00:00:01 -
every 1:00:00 until +14:00:00, in domain .pko-24
Part 2:
======
RE:
> (I) would like any commands that would show stats for the
> past, present and future.
I will leave this to the PA PL! ;)
- Anil Navkal
|
| 540.12 | Some examples of use of time in PA | TOOK::ANWARUDDIN | Anwar | Mon Jan 14 1991 19:16 | 39 |
| re: .10
The AT time clause is used to schedule SHOWs either starting NOW or
in the future. The FOR clause is used to lookup counters that were
previously recorded in the MIR. One of the things you specify with
the FOR clause is the `duration' over which to calculate statistics.
If you don't specify duration, PA uses a default of 5 mins. Here
are some examples:
1. Show node4 bbpk01 packet rate, at every 0:10:00 until 14:00
This command gives you packet rate every 10 mins starting
NOW (whenever you type the command) until 2:00 pm. The
packet rate is calculated over a default duration of 5 mins.
2. Show node4 bbpk01 packet rate, at every 0:10:00 until 14:00, -
for start (-0:00) duration :1:0
Same as 1., but the duration is 1 minute. Notice that there
is a start (-0:00) after the `for'. This tells the system to
use deferred time.
3. Show node4 bbpk01 packet rate, at start 11:00 every 0:10:00 until 14:00, -
for start (-0:00) duration :1:0
Same as before, but now I am starting at 11 am which is
in the future.
3. Show node4 bbpk01 packet rate, for start (13-Jan-1991:12:00) every 1:00:0 -
until 13-jan-1991:23:00:00 duration 1:00, in domain .pko-24
This command shows past time statistics starting from 12 noon on
13th Jan 1991 until 11 pm the same day. You will see 11 displays.
Notice that there is no AT clause used here because past time
statistics are requested.
Hope this helps.
|
| 540.13 | () on start time in EFT kit | GOSTE::CALLANDER | | Tue Jan 15 1991 14:04 | 16 |
|
FYI --
Anil the kit you are using doesn't require that the start time for
an AT clause to be in parenthesis, but....the EFT kit that is out
there requires you to enter the start time inside of parens (start
time is actually a list of start times).
ex:
AT start= (time) every = time until=time
The = are optional, but in the EFT kit the () are not, the final
1.1 release will not require the () when entering only one start
time.
|
| 540.14 | There I go again! | WAKEME::ANIL | | Tue Jan 15 1991 14:19 | 4 |
| Thanks Jill. Sorry about the making an already complicated issue even more
complicated! :(
- Anil
|
| 540.15 | Acc-vio? That's not good. | TOOK::CAREY | | Tue Jan 15 1991 17:28 | 18 |
|
Re: .6
I defer to all the AT, UNTIL, FOR, DURATION and everything else
we've been seeing here. I'm sure some combination works!
But way back when you were showing an access violation buried deep in
the response you received from the original command.
That Accvio was from the DNA4_AM. We had a small problem with
handling time semantics. Apparently not so small if the timeframe is
sufficently obscure. You shouldn't see this anymore. It may not work,
but with the next kit, it should blow up in a slightly more
intelligible way....
-Jim Carey
|
| 540.16 | we have found a problem | JETSAM::COURTRIGHT | | Thu Jan 17 1991 10:44 | 6 |
| I've found a system clock problem with my system which has turned
out to be a hardware problem. It won't stay in time, this was probably
the major reason why I've had so many problems with commands. I'll
be back as soon as we get it fixed......
thanks for all your help and very fast responses..
djc
|