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 |
Does anyone have any ideas or experiences on how many simultaneous traps could possibly be handled by HUBwatch? I can undestand trap messages might be lost before arriving at a HUBwatch station, if there is a potential 'bottleneck' path somewhere in a network. However, I just would like to know about a processing capacity of HUBwatch itself. A customer uses VS4000 M90 with 128MB memory. _Tak
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
1178.1 | No idea. | NACAD::GALLAGHER | Tue Jul 05 1994 10:15 | 14 | |
I suspect the answer is no, nobody has any idea how many simultaneous traps can be handled by HUBwatch. We haven't been at all concerned about how many traps can be handled because: - traps are relatively infrequent events, - the stations required for HUBwatch have a lot of message handling capability, and - there's not much that can be done about increasing the trap handling capability if it turns out to be inadequate. Do you have a special configuration in mind where this becomes an issue? -Shawn | |||||
1178.2 | exactly... | NACAD::WILSON | Wed Jul 06 1994 15:12 | 6 | |
Shawn is definitely correct and all of his points are true. We have no idea how many traps can be handled. Sorry for not replying sooner but I've been on vacation. :^) Karen |