| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
I'm a new user of Probewatch so this probably a silly question but
here goes anyway.
I've just put Probewatch for Windows on my laptop and it works just
fine, however one thing I find a little lacking is the minimum polling
time that I can set is 15 seconds. Many of the protocols which we use,
such as LAT, SCA and IPX will break in an approximately 1 second time
frame, is there any way that I can reduce the polling time to detect
peaks of a 1 second duration. (Or does the value displayed on the graph
reflect a peak over n seconds which has occurred in the last 15 seconds,
and if so what is n)
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1723.1 | KAOFS::S_HYNDMAN | Acronym Decoder Ring Architect | Fri Nov 25 1994 14:16 | 10 | |
The Packet Probe is continuously monitoring the ethernet segment.
What you are adjusting is the frequency that Probewatch queries the
probe for information using SNMP ( I think of it as reading counters in
the probe). If you are worried about being notified for certain
events, peaks etc. you can set up alarms using the watchdog for
thresholds etc.
Scott
| |||||
| 1723.2 | data normalized over 15 seconds | NAC::FORREST | Fri Dec 02 1994 20:41 | 6 | |
The minimum resolution on graphs is 15 seconds; the data captured by
the probe during a 15 second interval is normalized by PROBEwatch
to get a per second rate. However, like Scott suggests you can set
thresholds to detect abnormalities. Offhand, I don't know the minimum
time interval for the probe to check thresholds, but I have set it at 5
seconds previously.
| |||||