Description:
|
hubAddressChunk OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (408))
ACCESS read-only
STATUS obsolete
DESCRIPTION
"The hubAddressChunk object returns an opaque
chunk of the address table. Each chunk can be
interpreted as an array of records in the form:
mac address [6 bytes], port number [2 bytes],
inactivity time [4 bytes]
On a Get, the returned chunk can include empty
(unused) entries. Instances are chunk numbers,
which start at 1 and go to 52. Each chunk can
hold 34 addresses.
A returned chunk might look like:
Address Port Inactivity Time
080009001234 1 0
080009002345 2 10000
080009003456 1 20000
000000000000 1 0
080009009876 EMPTY 0
080009004567 EMPTY 15000
.
.
.
080009005678 EOL 959000
A value of EMPTY in the Port field indicates an
unused (i.e. aged out) entry in the table. When
the EOL (End Of List) bit is set in the Port
field, that entry is the last entry in the table.
It is possible for EOL to be seen in any entry.
EOL (0x4000) and EMPTY (0x8000) are bit masks
which are ORed with the port number in the port
field of the entry. It is possible for both the
EOL and EMPTY bits to be set in the same entry.
The remainder of the chunk after the EOL entry
will be zeroed.
The inactivityTime and Address fields are
meaningless if the EMPTY bit is set in the Port
field. In this case, inactivityTime and Address
are not guaranteed to be zeroed. The Manager may
start with any chunk it likes and request the
chunks in any order. It may perform multiple
requests for the same chunk. The agent does not
save state from previous requests.
A request of chunk #1 would return the contents of
the first 34 address table entries, whether they
are all full, all empty, or some full and the rest
empty. A request of chunk #2 will return entries
#35 through #68. And so on.
The address table can change between Get requests.
An address' location can change, or an address
could age out and then be added back in at a
different location in the table. Thus, the
Manager could see the address twice in the table."
|
|
iso(1)
