T.R | Title | User | Personal Name | Date | Lines |
---|
1709.1 | DO IT !!! | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Thu Oct 24 1991 15:38 | 0 |
1709.2 | Please DO IT, but document it clearly in the RELEASE_NOTES, and Userguide for PA | VIDOAN::DOAN | EIS/Network Consulting Group of the 90's | Thu Oct 24 1991 15:50 | 11 |
| Hi,
I support the default duration of 1 minute, but another thing that
is REALLY needed is the CONSISTENCY in specifying the time parameters
while using the PA because it's very difficult ( impossible !!) to
memorize the complex syntax that we're having in V1.1 (especially for
retrieving the historical data from the MIR to get statistics.
Thien Doan
Network Consulting Group
|
1709.3 | inform the user | JETSAM::WOODCOCK | | Thu Oct 24 1991 17:09 | 18 |
| Hi,
I really don't have a strong preference for either but 5 minutes seems a
bit much for a generic default for a user to have to WAIT on. Whatever
you decide though, how about TELLING the user what is being done:
Ex.
MCC> show node4 XXXX all statis
Using default duration of 1 minute...
just a thought,
brad...
|
1709.4 | We can do this even better | TNPUBS::JONG | Steve Jong/T and N Publications | Thu Oct 24 1991 21:29 | 4 |
| I've said it before and I'll say it again: an in-progress message is
necessary here. Simplest would be a box analogous to the "Looking
into" box that would say "Gathering statistics for ..." Better would
be a countdown timer ("Statistics due in n:nn minutes")
|
1709.5 | | GRANMA::JPARKER | | Thu Oct 24 1991 22:47 | 5 |
| RE: 1 minute duration. Yes, do it. I usually set a lower duration
anyway. In either case, a status message is very much desired.
Jeff.
|
1709.6 | Go for 1 minute default + provide "count-down" | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri Oct 25 1991 01:22 | 8 |
| I like Steve's idea of the count-down timer, if you have time to code
something like this for V1.2. I'm also assuming that we will still be
able to "CANCEL" if desired.
In-progress messages, pointer "watches", and other such amenities make
using DECmcc much more of a pleasure.
-Dan
|
1709.7 | and not just for PA, please? | ASD::HOWER | Helen Hower | Fri Oct 25 1991 11:25 | 5 |
| If countdown timers or other 'work in progress, please wait' type flags are
implemented, they should be made generic if at all possible. Other FMs (and
maybe AMs?) could use the ability to display such flags during long operations
so the user knows they're still alive! :-)
Helen
|
1709.8 | | TOOK::STRUTT | Management - the one word oxymoron | Fri Oct 25 1991 19:01 | 5 |
| How about a default of 10seconds.
I can wait 10 seconds - longer and I get bored or assume the machine's
failed....
Colin
|
1709.9 | | ENUF::GASSMAN | | Mon Oct 28 1991 12:37 | 14 |
| It depends on who the consumer of the stats are. When doing some
real-time tuning, a refresh rate of 1 second is not unreasonable.
A 10 second refresh is good for monitoring things with rapid rates
of change, such as bandwidth utilization and number of active session
links - but for everyday background stats to glance at once in a while,
the 1 minute default is probably good. The countdown visual idea is
good. Another helpful feature might be some 'standard value' buttons
so the user can click on 1, 10, or 60 seconds right from the display.
The MCC concept of shuting down if the interval can't be met (ie,
polling counters on a long delay link) should be modified to allow
stats to be updated on a 'best available' basis.
bill
|
1709.10 | Simplify it | TOOK::R_SPENCE | Nets don't fail me now... | Tue Nov 12 1991 17:18 | 11 |
| I like Bill's suggestion of providing a very simply way of getting
a few common durations so that the existing operations time ....
can be avoided most of the time.
I also believe that (while we are talking about time and statistics)
when a user does a OPERATIONS SHOW STATISTICS, the system ought
to know that it has to use relative time and not complain to the
user to fix it. Then they have to fix it back for the next operation
(usually SHOW COUNTERS).
s/rob
|