| 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 |
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 879.1 | QUIVER::HAROKOPUS | Fri Apr 01 1994 13:42 | 3 | ||
See note 875.
-Bob
| |||||
| 879.2 | Address capture by port on DECrepeater 90's | NAC::FORREST | Fri Apr 01 1994 21:12 | 16 | |
Bob, I don't think this question has anything to do with DECagent and HUBwatch rev levels. It depends more on what is being used to query the DECrepeater 90C - DECbridge, DECagent V2.0, or DEChub 900 agent. The DECrepeater 90C (and 90T, 90FA, 90FL) captures the last source address to come through on each port. It will report that address if queried on the backplane for the last address. Alternatively, the 90C can be given an address and told to report whether a match was found. So the answer depends on which module is hub bus master, and how often it polls each slot and port. I'm not sure what the address aging algorithm is that is used by each bus master. | |||||
| 879.3 | Off by 1 | QUIVER::HAROKOPUS | Fri Apr 01 1994 22:25 | 4 | |
OOps. I answered the wrong note. My answer applies to note
878 not 879. Please ignore .1
Bob
| |||||