| 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 |
Given the following comments from the DEC extended repeater MIB:
Address Database Port Address Table
-----------------------------------
"This table maintains a database of source addresses of readable
frames received from all repeater ports appearing in the agent's
port table. This information reveals the repeater port to which a
given station is connected.
This table augments the information found in the IETF repeater MIB's
Address Tracking Group [6]. The Address Tracking Group maps one address
per port. A repeater port may actually connect to multiple stations
(e.g. a port associared with a 10BASE2 MAU). The Address Database Port
Address Table can map multiple addresses to a single port.
The number of entries in this table is dynamic depending upon the
number of distinct source addresses learned by the repeater.
It is recommended that the agent automatically delete from this table
entries for addresses which have not been seen bythe repeater for some
reasonable amount of time. The method and timeliness in which this is
accomplished is implementation dependent".
What is the method and timeliness for removing the entries from the
table.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3581.1 | Periodic age task | NETCAD::PAGLIARO | Rich Pagliaro, Networks BU, HPN | Mon Jun 03 1996 13:00 | 5 |
Without getting into a line by line description of the
code...Approximately every 2 minutes a task is scheduled which inspects
every entry in the address database and removes all addresses which
have not been seen in the last 2 to 4 minutes.
| |||||