| 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 |
A customer w/ Hubwatch/windows 4.1 says that from the time he starts
up Hubwatch to the time he sees a picture of his hub varies wildly
for different hubs. Some take 15 seconds, others over a minute.
All are DH900s running the latest firmware. Strangely, the hub nearest
the NMS takes the longest. One far across the network takes 20 seconds.
With a sniffer, he believes he sees lots of snmp traffic to the pc
when connecting to the 'slow' hub, but virtually none connecting to
the 'fast' hub. (But I can't verify this)
What are some reasons that could account for the time differences?
TIA, Dan
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3123.1 | Network Utilization | NETRIX::"[email protected]" | Steven Freke | Thu Jan 04 1996 16:06 | 11 |
Dan At a stab in the dark, one would suggest that it would depend on how busy the network is. I have seen our PC here sometimes take a few seconds, when the lan is reasonably free, but when utilization gets higher, I saw a slightly longer response. One question I would be interested in hearing the answer to would be, once hubwatch has a loaded, does it continue to run slow or does it "speed" up. Steven Freke UK CSC, Basingstoke [Posted by WWW Notes gateway] | |||||
| 3123.2 | The answer is: It depends. | SLINK::HOOD | My God, what have I done to my spleen? | Thu Jan 04 1996 16:10 | 17 |
The biggest difference would be what is plugged into the hub. HUBwatch first goes out and asks the agent what's in the slot table. Then it tries to access all the agents in the hub. One of the biggest wastes of time is trying to get the freakin leds to as-near-to-the-right-state-as-we-get-em. If you got a hub filled with things that implement pcomLedProgram, it doesn't take too much to get the led state. For other modules, we gotta get tons of information and try to re-create the led status. Anyhow, the short answer is: - How many modules are in the hub. - What kinds of modules are in the hub. Tom Hood cVa | |||||